4:26-cv-02487
Yopima LLC v. Roadie Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Yopima, LLC (Delaware)
- Defendant: Roadie, Inc. (Delaware)
- Plaintiff's Counsel: Ramey LLP
- Case Identification: 4:26-cv-02487, S.D. Tex., 08/05/2026
- Venue Allegations: Venue is alleged to be proper based on Defendant maintaining a regular and established place of business within the Southern District of Texas and having committed acts of infringement in the district.
- Core Dispute: Plaintiff alleges that Defendant's crowdsourced delivery platform infringes a patent related to systems and methods for comparative geofencing.
- Technical Context: The technology concerns methods for efficiently managing location tracking for devices entering and moving within defined geographic areas (geofences) and for enabling server-side comparison of data associated with users in different zones.
- Key Procedural History: The filing is a First Amended Complaint, submitted following a court order. The complaint alleges that Defendant has been on notice of the patent and the infringement allegations since the original complaint was filed and served on March 27, 2026. Plaintiff identifies itself as a non-practicing entity and mentions prior settlement licenses with other, unnamed entities.
Case Timeline
| Date | Event |
|---|---|
| 2013-05-21 | Priority Date for '038 Patent |
| 2015-08-25 | '038 Patent Issued |
| 2026-03-27 | Alleged date of Defendant's knowledge via Original Complaint |
| 2026-08-05 | First Amended Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
- Patent Identification: U.S. Patent No. 9,119,038, titled "Systems and Methods for Comparative Geofencing," issued August 25, 2015 (the "'038 Patent").
The Invention Explained
- Problem Addressed: The patent's background section describes problems with conventional geofencing on portable devices, noting that such systems "tend to consume a great deal of resources" by performing location queries at frequent intervals, regardless of how far a user is from a target area Compl. ¶12 '038 Patent, col. 5:50-58 '038 Patent, col. 7:6-17 This process is described as wasteful of battery life, bandwidth, and CPU cycles Compl. ¶13 A further limitation identified is that conventional systems typically reference only one space at a time, making it difficult to compare different geofenced areas Compl. ¶14 '038 Patent, col. 14:60-col. 15:2
- The Patented Solution: The invention recites a client-server architecture that aims to shift computational burdens from the portable device to a server to enable more efficient and complex location analytics Compl. ¶¶15-18 On the device side, the device monitors for entry into a broad, first geofenced region. Upon entry, it transmits an arrival notification to a server that includes the device's specific location within one of several smaller, predefined subregions inside the larger region '038 Patent, claim 13 This "inverts" the conventional design by having the device perform a simple, broad check, while offloading the fine-grained, multi-zone analysis to the server Compl. ¶18 The server-side component receives these notifications from multiple devices, identifies which devices are in which subregions, and is configured to compare user information across those subregions to generate a "comparison metric" Compl. ¶17 '038 Patent, claim 1
- Technical Importance: The described solution aims to conserve mobile device resources while enabling sophisticated, real-time comparative analytics of user populations across multiple distinct, but related, geographic zones Compl. ¶20 '038 Patent, abstract
Key Claims at a Glance
The complaint asserts infringement of at least claims 1, 7, and 13 Compl. ¶34
Independent Claim 1 (Server-side Method):
- Receiving an identification of a first region, a distinct second region, and a third region that includes the first two.
- Receiving arrival notifications from a plurality of devices that have entered the third region.
- Receiving user information for the users of said devices.
- Identifying a first subset of devices within the first region and a second subset within the second region.
- Comparing user information across the two subsets.
- Transmitting a comparison metric based on the comparison.
Independent Claim 7 (Server-side System):
- A computing device comprising a processor executing a location analyzer configured to perform the functions recited in the method of claim 1.
Independent Claim 13 (Device-side Method):
- Receiving, by a portable device, an identification of a first geofence defining a first region.
- Determining a current location of the device.
- Comparing the current location to the first geofence.
- Transmitting an arrival notification to a second computing device, responsive to determining the device is within the first region.
- The arrival notification must include an identification of the device's current location within one of a plurality of subregions of the first region, which are themselves defined by geofences.
The complaint expressly reserves the right to assert additional claims Compl. ¶49
III. The Accused Instrumentality
Product Identification: The complaint identifies the "Roadie Platform" as the Accused Instrumentality. This platform comprises the "Roadie Driver" mobile application ("App") and the server infrastructure that Roadie operates to manage deliveries Compl. ¶23
Functionality and Market Context: The Roadie Platform is a crowdsourced delivery service where independent drivers use the Roadie Driver App to find and perform deliveries ("Gigs") for business customers Compl. ¶2 Compl. ¶23 To receive offers, each driver defines a "Gig notification area" by setting an address and a distance, which the complaint alleges constitutes a geofence Compl. ¶25 The App continuously determines the driver's location via GPS Compl. ¶26 When a driver arrives at a specific Gig pickup location (which the complaint maps to a "subregion"), the driver must use the App's "swipe to arrive" control. This action transmits an "arrival notification" from the driver's device to Roadie's servers Compl. ¶27 The complaint alleges that Roadie's servers use this location and arrival data to execute location-analysis and matching software Compl. ¶29
No probative visual evidence provided in complaint.
IV. Analysis of Infringement Allegations
The complaint provides an element-by-element mapping for the asserted independent claims.
- '038 Patent Infringement Allegations (Claim 13)
| Claim Element (from Independent Claim 13) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| receiving, by a portable computing device, an identification of a first geofence defining a first region | The Roadie Driver App receives the identification of the driver's "Gig notification area," defined by the driver's address and set distance. | ¶36 | col. 24:37-39 |
| determining a current location of the portable computing device | The App determines the device's location using GPS for tracking pickups and deliveries and for "heartbeat" location information. | ¶37 | col. 24:40-41 |
| comparing the current location of the portable computing device to the identified first geofence | The App compares the driver's location to the "Gig notification area" to surface nearby delivery opportunities and track progress. | ¶38 | col. 24:42-44 |
| transmitting, by the portable computing device to a second computing device, an arrival notification, responsive to determining that the current location of the portable computing device is within the identified first region | When a driver arrives at a Gig pickup place, the "swipe to arrive" control transmits an arrival notification to Roadie's servers. This is alleged to be responsive to being within the larger "Gig notification area" because all pickup places are offered to the driver only if they are within that area. | ¶39 | col. 24:45-49 |
| the arrival notification including an identification of the current location of the portable computing device within one of a plurality of subregions of the first region defined by a corresponding plurality of geofences | The arrival notification identifies the specific Gig pickup place where the driver has arrived. This pickup place is alleged to be one of a plurality of possible geofenced subregions (pickup places) within the larger "Gig notification area." | ¶40 | col. 24:49-54 |
- '038 Patent Infringement Allegations (Claim 1)
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| receiving an identification of... a first region... a second region... and a third region | Roadie's servers allegedly receive the geofenced pickup location (first region), the geofenced delivery location (second region), and the driver's overall "Gig notification area" (third region). | ¶47 | col. 23:50-57 |
| receiving... a plurality of arrival notifications from a corresponding plurality of devices | Servers receive arrival and location information from drivers' devices when they are within the third geofence (the "Gig notification area"). | ¶47 | col. 23:58-62 |
| receiving... user information for a user of each of the plurality of devices | Servers receive driver information including profile, vehicle, and route-direction data. | ¶47 | col. 23:2-4 |
| identifying a first subset of the plurality of devices that are within the first region and a second subset... within the second region | Servers identify the subset of drivers' devices within pickup regions and the subset within delivery regions. | ¶47 | col. 23:5-9 |
| comparing user information of the users of the first subset... and... the second subset | Roadie's "matching algorithm" is alleged to compare driver information across these subsets. | ¶47 | col. 23:10-15 |
| transmitting... a comparison metric | Servers transmit a "comparison-based output" that pairs a driver with Gigs to create an optimized route. This output is alleged to be the claimed metric. | ¶47 | col. 23:16-21 |
- Identified Points of Contention:
- Causation Question (Claim 13): The claim requires transmitting the arrival notification "responsive to determining that the current location... is within the identified first region." The complaint alleges the transmission occurs when a driver swipes to arrive at a subregion (the pickup place). A central dispute may be whether this act is legally responsive to being within the much larger first region (the notification area), or if there is a disconnect in the causal link required by the claim.
- Scope Question (Claim 1): The infringement theory for the server-side claims hinges on whether Roadie's logistical "matching algorithm" performs the "comparing user information" to generate a "comparison metric" as taught by the '038 Patent. The patent's specification heavily emphasizes comparing user demographics (e.g., age, gender) for analytical purposes, while the complaint alleges Roadie compares operational data (e.g., driver location, route) for logistical optimization. The case may turn on whether the claim term "comparison metric" can be construed to cover a route-matching output.
V. Key Claim Terms for Construction
The Term: "subregions of the first region" (Claim 13)
- Context and Importance: The plaintiff's entire device-side infringement theory depends on mapping the driver's broad "Gig notification area" to the "first region" and mapping specific, transient "Gig pickup places" to the "subregions." The construction of this term will determine if that mapping is viable.
- Intrinsic Evidence for a Broader Interpretation: The specification provides flexible examples, stating a subregion may be "a restaurant, nightclub, or individual building," while a region may be "a neighborhood, street, campus, city, or any other size area" '038 Patent, col. 15:18-22 This language suggests a loose, hierarchical relationship that may support the plaintiff's interpretation.
- Intrinsic Evidence for a Narrower Interpretation: Many embodiments in the '038 Patent describe a system where subregions are part of a more structured, persistent framework for comparative demographic analysis, not transient, single-purpose locations like a package pickup point. A party could argue that the term implies a set of pre-defined, related zones used for the comparative purposes central to the patent's overall disclosure.
The Term: "comparison metric" (Claim 1)
- Context and Importance: This term is the output of the claimed server-side method. The plaintiff alleges Roadie's route-pairing output is this metric Compl. ¶47 A court's definition of this term will be critical to the viability of the server-side infringement claims.
- Intrinsic Evidence for a Broader Interpretation: The claim term itself is not explicitly limited to a particular type of data. The claim recites comparing "user information," which could be interpreted broadly to include the logistical data (e.g., location, route direction) the complaint alleges Roadie uses Compl. ¶47
- Intrinsic Evidence for a Narrower Interpretation: The patent is titled "Systems and Methods for Comparative Geofencing" and its detailed description, including Figure 4B, focuses heavily on comparing user demographics like gender ratios and average age to provide analytics about different locations '038 Patent, Fig. 4B '038 Patent, col. 12:25-45 A defendant may argue that the term "comparison metric" should be construed in light of this stated purpose and is limited to an analytical or statistical output, not a logistical instruction like an optimized route.
VI. Other Allegations
Indirect Infringement: The complaint alleges both induced and contributory infringement.
- Inducement: The claim is based on Roadie's alleged knowledge since receiving the original complaint on March 27, 2026. The complaint alleges Roadie encourages infringement by continuing to operate its platform, onboarding new drivers, providing step-by-step instructions (e.g., "swipe to arrive"), and paying drivers for completing Gigs using the allegedly infringing workflow Compl. ¶¶53-56
- Contributory: The complaint alleges the Roadie Driver App is a material part of the invention, is not a staple article of commerce, and is "especially made and adapted" for practicing the patented method, with no substantial non-infringing uses Compl. ¶¶59-60
Willful Infringement: Willfulness is alleged based on Defendant's continued operation of the Roadie Platform without change after gaining knowledge of the '038 Patent and the specific infringement allegations from the original complaint Compl. ¶63
VII. Analyst's Conclusion: Key Questions for the Case
This case appears to center on the plaintiff's mapping of the accused system's functionality onto the patent's claims. The key questions for the court will likely be:
A question of causal mapping: Is the transmission of an "arrival notification" triggered by a driver's action at a specific pickup point (a "subregion") legally "responsive to determining" that the device is within the much larger geofenced notification area (the "first region"), as required by the strict language of claim 13?
A question of definitional scope: Can the term "comparison metric" from claim 1, which the patent specification heavily illustrates with examples of demographic and statistical analysis, be construed broadly enough to encompass the logistical output of a route-optimization algorithm that matches drivers to deliveries?