throbber
Case 2:21-cv-00072-JRG-RSP Document 265 Filed 12/22/21 Page 1 of 6 PageID #: 11840
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`CASE NO. 2:21-cv-00072-JRG
`(Lead Case)
`
`CASE NO. 2:21-cv-00026-JRG
`(Member Case)
`
`
`
`
`
`
`






`
` §
`
`





`
`AGIS SOFTWARE DEVELOPMENT LLC,
`
`v.
`
`T-MOBILE USA, INC., AND T-MOBILE
`US, INC.
`
`
`AGIS SOFTWARE DEVELOPMENT LLC,
`
`v.
`
`UBER TECHNOLOGIES, INC.,
`d/b/a UBER.
`
`
`DEFENDANT UBER TECHNOLOGIES, INC.’S OPPOSITION
`TO PLAINTIFF AGIS SOFTWARE DEVELOPMENT LLC’S
`MOTION FOR LEAVE TO FILE MOTION FOR
`SUMMARY JUDGMENT OF NO INVALIDITY
`
`
`
`
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 265 Filed 12/22/21 Page 2 of 6 PageID #: 11841
`
`
`By omission, AGIS misrepresents the facts underlying its motion for leave. AGIS implies
`
`that Uber did not offer a deposition date for Dr. Siegel prior to the December 13, 2021 summary
`
`judgment deadline. To the contrary, recognizing the compressed schedule, and prior even to the
`
`exchange of rebuttal reports, Uber offered deposition dates for all of its experts during the expert
`
`discovery period. In particular, on November 24, 2021, Uber notified AGIS that Dr. Siegel was
`
`available to be deposed on December 7, 2021, prior to the December 8, 2021 expert discovery
`
`deadline and the December 13 summary judgment deadline. Exhibit 1, November 24, 2021, Email
`
`from C. Ranney (Counsel for Uber) to E. Iturralde (Counsel for AGIS). On November 28, 2021,
`
`Mr. Iturralde responded, stating that AGIS’s counsel was unavailable on December 7-8 “due to
`
`previously scheduled travel and professional commitments,” and asked Uber to “provide later
`
`dates” for the expert depositions. Exhibit 2, November 28, 2021, Email from E. Iturralde to C.
`
`Ranney (emphasis added). Thus, despite having joined a motion to amend the Docket Control
`
`Order on October 7, 2021 (Dkt. No. 163) that set a December 8 expert discovery close and
`
`December 13 summary judgment deadline, which schedule the Court adopted in October (Dkt.
`
`No. 170), AGIS’s counsel failed apparently to plan for these significant dates.
`
`As this Court is aware, on December 3, 2021, AGIS filed an opposed motion for entry of
`
`an amended docket control order, which asked the Court to extend expert discovery to December
`
`22 and the summary judgment deadline to December 23. Dkt. No. 241. In that motion, AGIS
`
`acknowledged that Uber had offered all of its experts for deposition prior to the December 13
`
`summary judgment deadline (and specifically Dr. Siegel for deposition on December 7), but that
`
`AGIS had declined. Id. at 2. In its December 6 opposition, Uber explained that in early October
`
`the parties had filed an agreed motion that set the close of expert discovery for December 8 and a
`
`summary judgment deadline of December 13. Dkt. No. 242 at 2. Uber also explained that AGIS’s
`
`proposed schedule modification would further compress an already compressed schedule to Uber’s
`
`1
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 265 Filed 12/22/21 Page 3 of 6 PageID #: 11842
`
`
`prejudice. Id. at 3-4. Uber, moreover, opposed a schedule that would allow AGIS’s expert to sit
`
`for deposition after the filing of summary judgment motions; such a schedule, Uber wrote, would
`
`provide AGIS with “the unfair advantage of using Uber’s motions as a road map in preparing its
`
`expert for deposition.” Id. at 6.
`
`The Court entered a Sixth Amended Docket Control Order on December 14, 2021. Dkt.
`
`No. 257. In that Order, the Court maintained the December 13, 2021 summary judgment deadline,
`
`but extended expert discovery until December 22, 2022—the date requested by AGIS. Thus, the
`
`Court declined both parties’ request that the summary judgment motion deadline be set after expert
`
`depositions.
`
`In its motion for leave, AGIS essentially asks the Court to reconsider that Order, and, in
`
`doing so, ignores that it was the cause of the Order: Despite having two months to prepare, AGIS
`
`and its counsel ignored the December 8 expert discovery deadline, by (1) refusing to take Uber’s
`
`expert within the period allotted and (2) refusing to put up its own technical expert within the
`
`period allotted. AGIS had the same two months—just like Uber—to notify its experts of the
`
`schedule and to prepare and file summary judgment motions, with or without expert depositions.
`
`On December 13, as required under the Fifth Amended (and now the Sixth Amended)
`
`Docket Control Orders, Uber filed all of its motions for summary judgment and served those
`
`motions on December 14, after receipt of the Court’s Sixth Amended Docket Control Order.
`
`Uber’s summary judgment motions included several grounds for non-infringement, and Uber
`
`complied with the schedule despite lacking AGIS’s infringement expert’s deposition. In its present
`
`motion for leave, however, AGIS provides no explanation as to why Uber should have adhered to
`
`the summary judgment deadline, but good cause exists for AGIS to file after the deadline. In other
`
`words, AGIS provides no explanation as to why it is entitled to operate under a different set of
`
`rules than Uber and receive benefits not afforded to Uber.
`
`2
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 265 Filed 12/22/21 Page 4 of 6 PageID #: 11843
`
`
`Finally, AGIS’s misrepresentations by omission continue in that AGIS fails to apprise the
`
`Court that it had previously deposed Dr. Siegel, that it previously filed motions concerning the
`
`FBCB2 prior art and thus had the information it alleges it needed to support the late-filed summary
`
`judgment motion. Indeed, in the prior Apple litigation, AGIS filed numerous motions concerning
`
`Dr. Siegel and the FBCB2 prior art upon which he bases his invalidity opinions. See AGIS
`
`Software Development LLC v. Huawei, Case No. 2:17-CV-0513-JRG (Lead Case) (E.D. Tex.),
`
`Dkt. Nos. 233, 234, 235 and 236. AGIS, moreover, filed a motion concerning the FBCB2 prior
`
`art in the pending Google litigation. See AGIS Software Development LLC v.Google LLC, Case
`
`No. 2:19-CV-00361-JRG (Lead Case) (E.D. Tex.), Dkt. No. 174. Far from the epiphany AGIS
`
`implies it had after Dr. Siegel’s recent deposition, AGIS knew well how it planned to challenge
`
`Dr. Siegel and the FBCB2 invalidating prior art.
`
`When AGIS chose this Court in which to file this case, it assumed a responsibility to abide
`
`by the Court’s rules and the Court’s management of the case—including by adhering to the Court’s
`
`schedule. Only Uber has accepted that responsibility. It was only Uber and its counsel that
`
`planned for expert discovery within the time allotted by the Court. And it was only Uber and its
`
`counsel that filed all summary judgment motions within the time provided by the Court’s schedule.
`
`AGIS now, without any justification or explanation, asks the Court to turn a blind-eye to its
`
`disregard for the Court’s procedures, its self-help tactics and its history with these issues.
`
`Respectfully, Uber asks that this Court decline to do so and deny AGIS’s motion for leave.
`
`
`
`
`
`3
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 265 Filed 12/22/21 Page 5 of 6 PageID #: 11844
`
`
`Dated: December 22, 2021
`
`
`
`
`By: /s/ Mark N. Reiter
`
`Mark N. Reiter
`Texas State Bar No. 16759900
`mreiter@gibsondunn.com
`Robert A. Vincent
`Texas State Bar No. 24056474
`rvincent@gibsondunn.com
`Nathan R. Curtis
`Texas State Bar No. 24078390
`ncurtis@gibsondunn.com
`Ashbey N. Morgan
`Texas State Bar No. 24106339
`anmorgan@gibsondunn.com
`GIBSON, DUNN & CRUTCHER LLP
`2001 Ross Avenue, Suite 2100
`Dallas, TX 75201-6912
`Telephone: 214.698.3360
`Facsimile: 214.571.2907
`
`
`Melissa R. Smith
`Texas State Bar No. 24001351
`GILLAM & SMITH, LLP
`303 South Washington Avenue
`Marshall, TX 75670
`Telephone: 903.934.8450
`Facsimile: 903.934.9257
`Email: melissa@gillamsmithlaw.com
`
`
`Attorneys for Defendant Uber Technologies, Inc.
`d/b/a Uber
`
`
`4
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 265 Filed 12/22/21 Page 6 of 6 PageID #: 11845
`
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on December 22, 2021, the foregoing was electronically filed in
`
`compliance with Local Rule CV-5(a) and served via the Court’s electronic filing system on all
`
`counsel who have consented to electronic service.
`
`
`
`
`
`/s/ Mark N. Reiter
`Mark N. Reiter
`
`
`
`5
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket