DCT

2:25-cv-00029

Carma Technology Corp v. Uber Tech Inc

Log In
Key Events
Amended Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 2:25-cv-00029, E.D. Tex., 08/14/2025
  • Venue Allegations: Venue is alleged to be proper in the Eastern District of Texas because Defendant Uber, through its subsidiary Uber Freight US LLC, maintains a regular and established place of business in Frisco, Texas, and has committed alleged acts of infringement in the district.
  • Core Dispute: Plaintiff alleges that Defendant's ridesharing and ground transportation services infringe five patents related to managing transportation networks, including features for matching users, proxy communications, goods delivery, and safety monitoring.
  • Technical Context: The technology concerns networked systems that use mobile devices, GPS, and server-side algorithms to optimize transportation by matching available vehicle capacity (supply) with requests from riders and shippers (demand).
  • Key Procedural History: The complaint alleges that Defendant had pre-suit knowledge of the asserted patent family through multiple channels, including direct notice via a claim chart in 2016, and through Defendant's own patent prosecution activities dating back to at least 2015, where it repeatedly cited Plaintiff's patents and publications.

Case Timeline

Date Event
2007-02-12 Earliest Priority Date for all Asserted Patents
2010-11-23 U.S. Patent No. 7,840,427 Issues
2014-01-01 Uber launches UberPOOL carsharing service
2015-03-01 Complaint alleges Uber was aware of '427 Patent via its own patent prosecution
2016-08-30 Carma sends notice letter and claim chart for '427 Patent to Uber
2020-08-11 U.S. Patent No. 10,741,071 Issues
2021-02-09 U.S. Patent No. 10,916,138 Issues
2021-05-25 U.S. Patent No. 11,017,668 Issues
2021-11-02 U.S. Patent No. 11,164,456 Issues
2024-05-02 Uber cites '456 Patent in an Information Disclosure Statement
2025-08-14 Complaint Filed

II. Technology and Patent(s)-in-Suit Analysis

For ease of reference, this analysis utilizes the common specification of the '427 Patent, as directed by the complaint Compl. p. 14, n.1

U.S. Patent No. 7,840,427 (the '427 Patent) - "Shared transport system and service network," issued November 23, 2010

The Invention Explained

  • Problem Addressed: The patent's background describes the inefficiency of personal and public transportation, citing underutilized vehicle capacity (empty seats), the inconvenience of traditional carpooling, and a general "lack of information about the availability of services and timing between locations" Compl. ¶¶54-55 '427 Patent, col. 2:1-6 '427 Patent, col. 4:6-8
  • The Patented Solution: The invention proposes a networked marketplace that matches transportation supply with demand in near real-time Compl. ¶53 '427 Patent, col. 2:65-3:4 It uses GPS-enabled devices to track vehicles and users, represents journeys as a series of "nodes" (pick-up/drop-off points), and uses algorithms to optimize matching, thereby increasing efficiency and trust Compl. ¶52 Compl. ¶53 The overall system architecture is depicted in the patent's Figure 1 Compl. ¶53
  • Technical Importance: The invention provided a framework for automating and scaling shared transportation, moving beyond manual or geographically limited systems by creating an intelligent, data-driven marketplace Compl. ¶52

Key Claims at a Glance

  • The complaint asserts at least independent Claim 1 Compl. ¶83
  • The essential elements of Claim 1 are:
    • Providing a computer network.
    • Establishing an electronic registry of transport capacity (spare capacity and location of vehicles).
    • Establishing a network of nodes (pick-up and drop-off points).
    • Abstracting a vehicle journey by representing it as a set of said nodes where the journey intersects.
    • Providing an electronic registry of transport demand.
    • Effecting a match in a match engine between a vehicle's capacity and a user's demand for transport between at least two nodes.
  • The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 10,741,071 (the '071 Patent) - "Systems and Methods for Proxy Communication in a Shared Transport System," issued August 11, 2020

The Invention Explained

  • Problem Addressed: In a shared transport system, "riders or drivers may be concerned about their safety if a stranger knows how to contact them via their phone" Compl. ¶61 '427 Patent, col. 4:61-63 This lack of anonymity and security can deter participation.
  • The Patented Solution: The patent describes a proxy messaging system that enables communication between users (e.g., rider and driver) without revealing their personal phone numbers or full names Compl. ¶61 '071 Patent, abstract The system receives a message from a sender, generates a new message containing the original content and a unique identifier, and transmits it to the recipient, thereby masking direct contact information '071 Patent, claim 1 '427 Patent, col. 13:15-54
  • Technical Importance: This technology enhances user trust and security in a ridesharing network by providing a layer of anonymity, which is critical for encouraging interactions between strangers Compl. ¶¶60-61

Key Claims at a Glance

  • The complaint asserts at least independent Claim 1 Compl. ¶114
  • The essential elements of Claim 1 are:
    • Identifying a transport user and a transport provider based on a transport request.
    • Receiving, by a proxy messaging system, a first message from a sender (either the user or provider).
    • Generating, by the proxy system, a second message comprising the contents of the first message and a unique identifier for the sender.
    • Transmitting the second message to the recipient (the other of the user or provider).
  • The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 10,916,138 (the '138 Patent) - "Systems and Methods for Utilizing a Shared Transport Network for Delivery of Goods," issued February 9, 2021

  • Technology Synopsis: The patent describes a method for improving the efficiency of goods delivery within a shared transport network. The system accomplishes this by enabling a transport provider to "chain" multiple deliveries, identifying a second delivery job that is in proximity to the provider after the first delivery is completed Compl. ¶127
  • Asserted Claims: At least independent Claim 1 Compl. ¶128
  • Accused Features: The complaint alleges that Uber's Delivery Products, specifically features within Uber Freight and Uber Eats that allow for "reloads," "back-to-back," and "batched orders," infringe this patent (Compl. ¶¶35; Compl. ¶153; Compl. ¶154).

U.S. Patent No. 11,017,668 (the '668 Patent) - "Systems and Methods for Managing Anomalous Conditions in a Shared Transport System," issued May 25, 2021

  • Technology Synopsis: This patent addresses safety in a ridesharing system by managing "anomalous conditions." It discloses a method for continuously tracking a vehicle's location, analyzing the data for anomalies (e.g., an unexpected long stop or a possible crash), and escalating any detected issues by notifying the user, provider, or security personnel Compl. ¶159
  • Asserted Claims: At least independent Claim 1 Compl. ¶160
  • Accused Features: The complaint identifies Uber's "RideCheck" feature, which proactively monitors trips for events like crashes or unusual stops and provides tools to the rider and driver, as the infringing functionality Compl. ¶¶163-164

U.S. Patent No. 11,164,456 (the '456 Patent) - "Systems and methods for matching pick-up requests with transport providers, tracking trip progress, and enabling provider ratings," issued November 2, 2021

  • Technology Synopsis: The patent claims an end-to-end method for operating a shared transport service. The method encompasses receiving a pickup request, identifying and transmitting it to available providers, displaying provider information (including ratings) to the user, tracking trip progress via GPS, and facilitating post-trip rating and payment Compl. ¶170
  • Asserted Claims: At least independent Claim 1 Compl. ¶171
  • Accused Features: The complaint alleges that the general operation of the Uber Rideshare and Eats Products, which manage the entire lifecycle of a trip from request to payment and rating, infringes this patent Compl. ¶¶173-202

III. The Accused Instrumentality

Product Identification

  • The accused instrumentalities are "Uber Rideshare Products" (e.g., UberX, UberX Shared) and "Uber Delivery Products" (e.g., Uber Eats, Uber Connect, Uber Freight) Compl. ¶¶34-35

Functionality and Market Context

  • The complaint describes the accused products as a technology platform that connects consumers (Riders/Eaters) with independent service providers (Drivers/Couriers) Compl. ¶36 The core functionality involves a mobile application and backend infrastructure that:
    • Matches supply and demand using geographic proximity and other algorithms Compl. ¶89 Compl. ¶104
    • Uses GPS and mapping systems like S2 and H3 to index geographies, calculate ETAs, and provide turn-by-turn navigation Compl. ¶¶96-100
    • Provides in-app, anonymized communication between users and providers Compl. ¶118
    • Includes safety features like "RideCheck" to detect trip anomalies Compl. ¶163
    • Facilitates chained or batched deliveries in its freight and food delivery services Compl. ¶153 Compl. ¶154
  • The complaint alleges these services are supported by a "giant infrastructure consisting of thousands of services and terabytes of data" Compl. ¶86 The complaint includes a screenshot from Uber's website showing a user interface for creating a shipment in Uber Freight Compl. ¶131

IV. Analysis of Infringement Allegations

'427 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
providing a computer network; Uber provides a computer network using a combination of cloud computing and co-located data centers to support its services. ¶86 col. 2:65-3:4
establishing an electronic registry in said computer network of capacity containing an indication of the spare transport capacity and location of a plurality of transport vehicles; Uber's backend system, including its Apache Pinot OLAP system, is alleged to maintain a registry of driver availability (capacity) and location. ¶88; ¶92 col. 7:5-13
establishing a network of nodes in said computer network representing a plurality of pick-up points and a plurality of drop-off points; Uber's system allegedly creates a spatial index of pick-up and drop-off locations, which function as nodes, using global grid systems like S2 and H3. ¶94; ¶96 col. 13:46-50
abstracting a geographic representation of a predetermined transport vehicle journey by calculating places where said predetermined transport vehicle journey intersects said nodes and representing said predetermined transport vehicle journey in the format of a set of said nodes; When matching trips (e.g., for UberX Share or driver destinations), Uber's systems allegedly abstract a journey and determine where it intersects with other routes or nodes. ¶97; ¶98 col. 15:1-11
providing an electronic registry in said computer network of demand containing an indication of the demand for transportation needs of a plurality of transport users; Uber's platform provides a registry of user demand, as users request rides by entering a destination in the app, creating a record of demand. ¶102; ¶103 col. 7:14-23
effecting a match in a match engine in said computer network of said transport capacity...with said transport demand for a journey...between at least two of said nodes. Uber's matching system allegedly matches driver capacity with rider demand for journeys between pick-up and drop-off points (nodes). ¶107; ¶108 col. 7:62-8:2

'071 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
identifying...a transport user and a transport provider based on...a transport request from a transport user device...and determining...a transport provider device...in proximity... The Uber system identifies a rider (transport user) and a nearby driver (transport provider) after the rider makes a request through the Uber app. ¶116 col. 7:35-43
receiving, by a proxy messaging system, a first message from a sender device of a sender, wherein the sender is one of the transport user and the transport provider... Uber's proxy messaging system, part of its UberChat architecture, allegedly receives a message from either a rider or a driver. ¶117; ¶119 col. 13:20-30
generating, by the proxy messaging system, a second message, wherein the second message comprises contents of the first message and a first unique identifier associated with the sender; Uber's system allegedly generates a second message containing the original message content plus an identifier to facilitate anonymized communication. ¶121 col. 13:31-34
transmitting, by the proxy messaging system, the second message to a recipient device of a recipient, wherein the recipient is the other of the transport user and the transport provider. The system then transmits the generated second message to the intended recipient (rider or driver) to complete the anonymized communication. The complaint presents a diagram of Uber's chat architecture to illustrate this flow Compl. ¶119 ¶122 col. 13:35-37
  • Identified Points of Contention:
    • Scope Questions:
      • For the '427 patent, a central dispute may arise over the term "network of nodes". The complaint alleges Uber's use of dynamic, hexagonal grid systems like H3 for spatial indexing constitutes a "network of nodes" Compl. ¶¶94-96 A court may need to determine if this claim term, which the patent illustrates with fixed, named locations (e.g.,'427 Patent, Fig. 8a), can be construed to cover a dynamic, cell-based coordinate system.
      • For the '138 patent, a question of scope may be whether the "reloads," "back-to-back," and "batched orders" features in Uber's delivery products meet the claimed sequence of receiving a second transport request after updating provider characteristics from the first trip Compl. ¶153 Compl. ¶154 The court may examine if Uber's system operates as a series of discrete, sequential requests or as a more continuous, fluid matching process.
    • Technical Questions:
      • For the '071 patent, a key technical question is whether Uber's chat system performs the distinct steps of "generating... a second message" that "comprises contents of the first message and a first unique identifier" as claimed, or if it functions as a more direct pass-through or relay that simply anonymizes the sender's identity without a distinct message "generation" step Compl. ¶¶119-121

V. Key Claim Terms for Construction

Term 1: "network of nodes" ('427 Patent, Claim 1)

  • Context and Importance: This term is fundamental to how the claimed invention geographically represents and organizes the transportation system. Its construction is critical because the infringement allegation for the '427 patent hinges on whether Uber's dynamic, grid-based spatial indexing systems (like H3) fall within the scope of a "network of nodes representing a plurality of pick-up points and a plurality of drop-off points" Compl. ¶¶94-96
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification describes how a driver's route can be "abstracted to stop nodes" and that the system can "present[] the journey at the end of the route in the format of a very useful and concise set of major stops, rather than an incomprehensible list of addresses or geographic co-ordinates" '427 Patent, col. 15:5-11 This suggests "node" is a functional, abstract concept, not necessarily a fixed physical point, which may support a broader construction covering dynamically generated grid cells.
    • Evidence for a Narrower Interpretation: Figure 8a explicitly labels specific, named geographic locations like "Cork Airport" and "Kinsale Roundabout" as points on the network, and the corresponding logical representation in Figure 8b treats these named locations as the fundamental units of the journey (Compl. p. 15, Fig. 1; '427 Patent, Fig. 8a). This may support an argument that "nodes" are discrete, pre-defined, or at least named locations, rather than algorithmically generated grid cells.

Term 2: "proxy messaging system" ('071 Patent, Claim 1)

  • Context and Importance: The infringement analysis for the '071 patent will turn on the operational definition of a "proxy messaging system." Practitioners may focus on this term because the claim requires specific internal functions: receiving a first message, "generating" a second message with specific content (original content + unique ID), and transmitting it. The complaint alleges Uber's "UberChat" system performs these steps Compl. ¶¶119-121
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification introduces the concept in broad, functional terms: "the [] system incorporates a mechanism allowing riders and drivers to contact each other through their phones without knowing the other's phone number or full name" '427 Patent, col. 4:63-5:2 This focus on the functional outcome of anonymity may support a construction that is not strictly limited to a specific multi-step generation process.
    • Evidence for a Narrower Interpretation: Figure 13 of the specification, titled "Transport Community Proxy Message Service," details a specific flowchart for message handling that includes steps like "Evaluate message for automatic approval" and "Operator Review" '427 Patent, Fig. 13 This detailed embodiment suggests a system with more complex logic than simple anonymization and forwarding, which may support a narrower construction requiring these intermediate evaluation steps as part of the "proxy messaging system."

VI. Other Allegations

  • Indirect Infringement: The complaint's five counts focus on allegations of direct infringement, stating that "Uber has directly infringed" by "making, using, selling, offering for sale, and/or importing" the accused products Compl. ¶83 Compl. ¶114 Compl. ¶128 Compl. ¶160 Compl. ¶171 The complaint asserts that Uber's control over its subsidiaries and the technology stack makes it a direct infringer, including under an alter ego theory (Compl. ¶¶26; Compl. ¶29; Compl. ¶87).
  • Willful Infringement: Willfulness is a central allegation for all asserted patents. The complaint alleges that Defendant's infringement has been and continues to be deliberate and willful based on extensive pre-suit knowledge Compl. ¶110 Compl. ¶124 Compl. ¶156 Compl. ¶167 Compl. ¶204 The alleged bases for knowledge include a direct notice letter with a claim chart for the '427 patent sent in 2016, Defendant's own patent prosecution activities where it cited the asserted patent family over 60 times since at least 2015, and Defendant's awareness of Plaintiff's predecessor (Avego) as a direct competitor in the same market Compl. ¶¶63-79

VII. Analyst's Conclusion: Key Questions for the Case

  • A core issue will be one of definitional scope: can the term "network of nodes", which is illustrated in the patent with specific, named geographic locations, be construed to cover the dynamic, cell-based hexagonal grid system that the complaint alleges Uber uses for spatial indexing? The outcome of this claim construction will be critical to the infringement analysis of the foundational '427 patent.
  • A second central question will be one of willfulness: given the complaint's extensive and specific allegations of pre-suit knowledge-stemming from direct notice, competitive monitoring, and Defendant's own patent prosecution history-the court will likely need to closely examine whether Defendant's conduct, if found to be infringing, rises to the level of deliberate or willfully blind infringement warranting enhanced damages.
  • A key evidentiary question will be one of operational equivalence: do Uber's complex, real-time platform services perform the specific, sequential method steps recited in the asserted claims? For example, for the proxy communication claims, does Uber's chat system technically "generate" a new message with a unique identifier, or does it operate in a way that is functionally distinct from the claimed method, raising questions of a fundamental mismatch in technical operation.
Loading Amended Complaint