throbber
Case 2:21-cv-00072-JRG-RSP Document 155 Filed 09/16/21 Page 1 of 8 PageID #: 5152
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`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
`
`














`
`
`CASE NO. 2:21-cv-00072-JRG
`(Lead Case)
`
`
`
`
`
`
`CASE NO. 2:21-cv-00026-JRG
`(Member Case)
`
`
`
`
`UBER TECHNOLOGIES, INC.’S OBJECTIONS TO THE SEPTEMBER 3, 2021
`REPORT AND RECOMMENDATION DENYING UBER’S MOTION
`TO DISMISS U.S. PATENT NO. 10,341,838 FOR IMPROPER VENUE
`
`
`
`
`
`
`
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 155 Filed 09/16/21 Page 2 of 8 PageID #: 5153
`
`Defendant Uber Technologies, Inc. (“Uber”) respectfully objects to the Magistrate’s
`
`Report and Recommendation (“Report”) denying Uber’s Motion to Dismiss U.S. Patent No.
`
`10,341,838 (“the ’838 patent”) for Improper Venue. For the reasons stated below, the conclusion
`
`of the Report should be reversed and Uber’s motion granted.
`
`In response to the Complaint filed by Plaintiff AGIS Software Development LLC
`
`(“AGIS”), Uber moved to dismiss based on multiple grounds, including improper venue as to the
`
`’838 patent. Dkt. 24. With respect to improper venue and the ’838 patent, Uber explained that in
`
`its Complaint, AGIS had failed to present facts that plausibly alleged Uber committed an act of
`
`infringement in the District with respect to the ’838 patent. Indeed, the “Jurisdiction and Venue”
`
`section of the Complaint, provides only boilerplate language regarding an act of infringement:
`
`“Uber has transacted business in the Eastern District of Texas, and has committed acts of direct
`
`and indirect infringement in the Eastern District of Texas.” Dkt. 1 ¶ 5; see also id. ¶ 26.1 In the
`
`“Infringement of the ’838 Patent” section (COUNT IV) of the Complaint, AGIS alleged that Uber
`
`“has and continues to” directly and indirectly infringe at least claim 1 of the ’838 patent. Id. 78-
`
`80. In paragraph 82, AGIS purported to support that allegation by reciting the entirety of claim 1
`
`of the ’838 patent and beginning that recitation with the phrase “Defendant directly infringes
`
`and/or indirectly infringes by practicing [language of claim 1].” Id. ¶ 82.
`
`Claim 1, however, recites “[a] method performed by one or more servers each having one
`
`or more processors, the method comprising: …” Id. Because claim 1 recites a method performed
`
`by one or more servers, and because Uber has no servers in the Eastern District of Texas, AGIS
`
`
`1 Although the Complaint defines “Accused Products” to include “Uber, Uber Driver, Uber Eats,
`Uber Fleet, Uber Freight, Uber Eats Orders, and Uber Eats Man[a]ger Applications and the related
`services and/or servers for the applications” (id.), AGIS has dropped Uber Eats, Uber Eats
`Manager, Uber Eats Orders, and Uber Freight.
`
`
`
`
`
` 1
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 155 Filed 09/16/21 Page 3 of 8 PageID #: 5154
`
`failed to identify an act of infringement in this District, whether by Uber directly or indirectly, and
`
`Count IV of AGIS’s complaint must be dismissed for improper venue.
`
`I.
`
`AGIS Has Not Alleged Any Facts Supporting an Act of Infringement in this District
`
`As this Court is well aware, “[f]or purposes of determining whether venue is proper in a
`
`district other than one in a state in which a defendant is incorporated, a court must determine,
`
`among other things, ‘where the defendant has committed acts of infringement.’” Valeant Pharm.
`
`North America LLC v. Mylan Pharm. Inc., 978 F.3d 1374, 1378 (Fed. Cir. 2020). AGIS bears the
`
`burden to establish venue. In re ZTE (USA) Inc., 890 F.3d 1008, 1013 (Fed. Cir. 2018). That
`
`burden is not carried by boilerplate allegations but must be supported with facts showing that venue
`
`is proper. Westech Aerosol Corp. v. 3M Co., 927 F.3d 1378, 1382 (Fed. Cir. 2019).
`
`A.
`
`AGIS’s Allegations Are Not Directed to Texas or to the ’838 Patent Claims
`
`Both in its Complaint and in its briefing in response to Uber’s motion to dismiss, AGIS
`
`failed to identify a single act of infringement in this District, whether performed by Uber itself or
`
`by Uber’s customers, that ties to the elements of claim 1 of the ’838 patent. First, as to Uber, in
`
`support of its motion, Uber submitted the Declaration of Jeff Rapipong, wherein Mr. Rapipong
`
`explained that “[n]one of the servers that Uber uses for its ride-sharing, food delivery and freight
`
`brokerage technology are located in Texas.” Dkt. 24-2 ¶ 2. AGIS did not directly challenge Mr.
`
`Rapipong’s declaration. Instead, AGIS asserted, and the Report accepted, that Uber “publicly
`
`disclosed that it engages in a ‘classic hybrid cloud approach’ which utilizes co-located data centers
`
`located in the United States and multiple third-party cloud computing services.” Dkt. 43 at 8; Dkt.
`
`142 at 6. AGIS further asserted, and the Report accepted, that Uber has a “massive network”
`
`consisting of “tens of millions of Drivers, consumers, restaurants, shippers, carriers, and dockless
`
`e-bikes and e-scooters, as well as underlying data, technology, and shared infrastructure” that it
`
`“collect[s], use[s], and process[es] a variety of personal data, such as email addresses, mobile
`
`
`
`
`
` 2
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 155 Filed 09/16/21 Page 4 of 8 PageID #: 5155
`
`phone numbers, profile photos, location information” and reliance on “third-party service
`
`providers to host or otherwise process some of our data and that of platform users.” Id.
`
`Based on these assertions, AGIS concluded, and the Report apparently also accepted, that
`
`the “physical infrastructure used by [Uber] appears to be much broader than just the ‘servers,’ as
`
`submitted by Mr. Rapipong and [Uber].” Id. But none of these assertions tie any of the so-called
`
`“massive network” to Texas, much less the sole claim identified in the Complaint—claim 1—of
`
`the ’838 patent. In fact, by focusing on this alleged “massive network,” while disregarding that
`
`the claim focuses only on operating one or more servers, both AGIS and the Report erroneously
`
`side-step what it takes to allegedly infringe the ’838 patent and thereby properly establish venue.
`
`In response to Uber’s motion, AGIS relied on Seven Networks, LLC v. Google LLC, 315
`
`F. Supp. 3d 933, 943 (E.D. Tex. 2018), where this Court held that “not all of the alleged infringing
`
`activity needs to have occurred within the District so long as some act of infringement took place
`
`there.” (Emphasis in original; citations omitted). But here, AGIS has failed to allege any act of
`
`infringement committed by Uber in this District, and the Report erred when it likewise failed to
`
`recognize the absence of any such facts. AGIS’s references to Uber’s broad “infrastructure” does
`
`not translate to plausible allegations that any part of that infrastructure actually exists in this
`
`District or is tied to the elements of claim 1 of the ’838 patent, particularly in view of the unrebutted
`
`Rapipong declaration. Thus, as in Westech Aerosol, 927 F.3d at 1382, where the Federal Circuit
`
`found that the plaintiff failed to plead any facts showing that the defendant had a regular and
`
`established place of business located in the district, AGIS has failed to plead (or otherwise identify)
`
`any fact showing Uber committed an act of infringement in this District. And to be clear, neither
`
`in its motion nor in these objections, does Uber suggest that AGIS must satisfy its burden to prove
`
`
`
`
`
` 3
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 155 Filed 09/16/21 Page 5 of 8 PageID #: 5156
`
`infringement on the merits; rather, AGIS must present facts that plausibly support its allegation of
`
`infringement and, thereby, proper venue.
`
`B.
`
`AGIS’s Indirect Infringement Allegations Are Equally Flawed
`
`AGIS also argued, again relying on Seven Networks, that it need not establish venue only
`
`through acts of direct infringement, and that allegations of indirect infringement can support venue.
`
`Dkt. 43 at 9. In support of this argument, AGIS asserted that “customers and end-users of Uber’s
`
`Accused Products can access the Uber servers from this District” and that Uber has “instruct[ed]
`
`users of the Accused Products to perform at least the method of claim 1 in the ’838 Patent.” Id.
`
`AGIS referred to “training videos, demonstrations, brochures, installations, and/or user guides” as
`
`well as paragraph 87 of its Complaint where it alleged that “the Uber, Uber Driver, and Uber Eats
`
`Applications provides and stores the phone number of users and drivers in the memories of their
`
`respective phones (e.g. through communication with a server).” Dkt. 43 at 15-16 & n.2. This
`
`latter allegation—the storing of phone numbers—is not an element of the ’838 patent claim 1,
`
`which Uber explained in its Reply. Dkt. 51 at 2-3. Indeed, “phone number” appears nowhere in
`
`the claim language of the ’838 patent. Removing this non-element from the argument leaves AGIS
`
`with only boilerplate allegations that Uber induces customers to infringe. 2 But “conclusory
`
`allegations or legal conclusions masquerading as factual conclusions will not suffice to prevent a
`
`motion to dismiss.” McZeal v. Sprint Nextel Corp., 501 F.3d 1354, 1356 (Fed. Cir. 2007). As
`
`with its direct infringement arguments, AGIS’s indirect infringement arguments ignore entirely
`
`that the sole identified claim in the Complaint recites a method performed by one or more servers.
`
`With the servers all located outside of this District, AGIS cannot plausibly allege that an Uber
`
`
`2 In its motion to dismiss, Uber also challenged the sufficiency of AGIS’s pleading of indirect
`infringement. Dkt. 24 at 35-36. The Report only addressed the motion “with respect to the defense
`of improper venue.” Dkt. 142 at 1.
`
`
`
`
`
` 4
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 155 Filed 09/16/21 Page 6 of 8 PageID #: 5157
`
`customer in this District performs the method (or any part of the method) using Uber’s servers.
`
`And the one example AGIS provided—storing phone numbers—again, is not a claim limitation.
`
`Thus, to the extent the Report relied on AGIS’s indirect infringement claims, such reliance was in
`
`error.
`
`C.
`
`AGIS Must Demonstrate Venue for Each Patent Independently
`
`Finally, the Report notes “that although Uber challenges venue with respect to the ’838
`
`Patent, Uber has not alleged improper venue with respect to other patents at issue in this matter.”
`
`Dkt. 142 at 6. That Uber did not challenge venue with respect to the other four asserted patents is
`
`of no matter. AGIS must separately establish venue for each asserted patent. Quartz Auto Techs.
`
`LLC v. Lyft, Inc., 2021 WL 1177886, at *3 (W.D. Tex. Mar. 29, 2021) (dismissing one of five
`
`asserted patents based on lack of proper venue for that one patent); Digit. Equip. Corp. v. Elec.
`
`Memories & Magnetics Corp., 452 F. Supp. 1262, 1266 (D. Mass. 1978) (“[A plaintiff] must
`
`establish proper venue as to each patent allegedly infringed.”); see also Datascope Corp. v. SMEC,
`
`Inc., 561 F. Supp. 787, 789 (D.N.J. 1983). In its briefing, AGIS did not challenge this statement
`
`of law. Thus, to the extent the Report sought to reinforce its decision, even if in part, on Uber’s
`
`challenge to venue related to the ’838 patent alone, Uber’s focused venue challenge provides no
`
`such reinforcement.
`
`* * *
`
`AGIS failed in its Compliant and its briefing to identify a single act of infringement,
`
`whether by Uber directly or indirectly through its customers, that occurred in this District with
`
`respect to the ’838 patent. Venue is therefore improper as to the ’838 patent and dismissal
`
`appropriate. The Report erred in its review of the asserted allegations, unrebutted facts and
`
`unrebutted law. Uber, therefore, respectfully requests that the Court reverse the Report’s
`
`conclusion and grant Uber’s Motion to Dismiss the ’838 Patent for Improper Venue.
`
` 5
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 155 Filed 09/16/21 Page 7 of 8 PageID #: 5158
`
`Dated: September 16, 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, Texas 75670
`Telephone: 903.934.8450
`Facsimile: 903.934.9257
`Email: melissa@gillamsmithlaw.com
`
`Attorneys for Defendant Uber Technologies,
`Inc. d/b/a Uber
`
`
`
`

`

`Case 2:21-cv-00072-JRG-RSP Document 155 Filed 09/16/21 Page 8 of 8 PageID #: 5159
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on September 16, 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 on this 16th day of September, 2021.
`
`
`
`
`
`/s/ Mark N. Reiter
`Mark N. Reiter
`
`
`
`

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