DCT

6:22-cv-00943

Traxcell Tech v. GoShare Inc

Key Events
Complaint
complaint

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 6:22-cv-00943, W.D. Tex., 09/12/2022
  • Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Defendant has committed acts of infringement and maintains regular and established places of business within the district.
  • Core Dispute: Plaintiff alleges that Defendant’s technology platform for connecting consumers with moving and delivery professionals infringes a patent related to providing on-line and off-line geographic navigation information on a mobile device.
  • Technical Context: The technology relates to mobile navigation systems that integrate real-time network data, such as traffic conditions, to provide optimized routing information to a user's device.
  • Key Procedural History: The complaint notes that the patent-in-suit was assigned to Plaintiff Traxcell Technologies, LLC on October 3, 2016, with the assignment recorded at the USPTO on February 12, 2020, granting Traxcell all rights, including the right to sue for past and future infringement.

Case Timeline

Date Event
2001-10-04 ’147 Patent - Earliest Priority Date
2020-10-27 ’147 Patent - Issue Date
2022-09-12 Complaint Filing Date

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

U.S. Patent No. 10,820,147 - "Mobile wireless device providing off-line and on-line geographic navigation information"

  • Patent Identification: U.S. Patent No. 10,820,147, issued October 27, 2020.

The Invention Explained

  • Problem Addressed: The patent addresses the need for a system that provides mobile users with both on-line navigation (using real-time data from a network) and off-line navigation (using data stored locally on the device), thereby improving reliability and functionality, especially for applications like traffic monitoring and emergency services (’147 Patent, col. 2:48-51, col. 7:1-12).
  • The Patented Solution: The invention proposes a system where a mobile device generates navigation information and can request and receive real-time data, such as traffic congestion, from a network processor. The mobile device's processor then uses this external data to update the navigation information—for example, by re-calculating the optimal route based on current traffic—and presents this updated route to the user (’147 Patent, Abstract; col. 127:53-128:28). This allows the device to provide dynamic, network-aware routing.
  • Technical Importance: This approach combines the self-sufficiency of local device data with the real-time intelligence of a connected network, enabling more sophisticated and accurate location-based services than were possible with purely static or offline maps (’147 Patent, col. 38:22-35).

Key Claims at a Glance

  • The complaint asserts infringement of at least independent claim 1 (Compl. ¶17).
  • Essential elements of independent claim 1 include:
    • A wireless mobile communications device with a radio-frequency transceiver and a processor.
    • The processor is programmed to generate an indication of the device's location and user navigation information.
    • The processor sends the user navigation information to at least one other processor outside the wireless communications network as part of a request for traffic congestion information.
    • The processor receives traffic congestion information from the other processor.
    • The processor updates the user navigation information based on the received traffic data, including by computing a new expected travel time for route segments.
  • The complaint reserves the right to assert other claims (Compl. ¶17).

III. The Accused Instrumentality

Product Identification

  • The accused instrumentality is "GoShare's technology platform for connecting consumers with moving and delivery professionals" (Compl. ¶15). This includes related U.S. wireless networks and components that facilitate the service (Compl. ¶17).

Functionality and Market Context

  • The complaint alleges the accused platform operates by using the identified locations of wireless devices to provide direction (Compl. ¶17). The service connects customers with delivery professionals, which inherently involves location tracking, mapping, and routing functionality to guide drivers and inform customers.
  • The platform is alleged to provide "on- line and off-line navigation" to its customers, which include users in the district and throughout the United States (Compl. ¶18).

IV. Analysis of Infringement Allegations

The complaint references a claim chart in an "Exhibit B" that was not included in the filing documents (Compl. ¶24). The following summary is therefore based on the general infringement theory articulated in the complaint's text. No probative visual evidence provided in complaint.

’147 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
a wireless mobile communications device including: a first radio-frequency transceiver... and a first processor... The smartphone of a GoShare user or driver, which contains a transceiver and processor. ¶17, 18 col. 127:63-66
wherein the first processor is programmed to generate an indication of a location of the wireless mobile communications device... The GoShare application on the smartphone using GPS or other location services to determine its current position. ¶17 col. 128:1-3
and generate user navigation information to the at least one other processor outside the wireless communications network... The GoShare application generating a route to a destination, which is then communicated to GoShare's servers or a third-party mapping service. ¶17 col. 128:10-18
wherein the first processor further sends a request to the at least one other processor outside the wireless communications network for traffic congestion information... The GoShare application requesting real-time traffic data from GoShare's servers or an integrated mapping service. ¶17, 18 col. 128:19-23
wherein the first processor receives the traffic congestion information from the at least one other processor... The GoShare application receiving traffic data (e.g., color-coded traffic overlays, updated ETAs) from the external server. ¶17, 18 col. 128:24-28
and wherein the first processor updates the user navigation information... with a computed value for segments corresponding to the expected time to travel... The GoShare application allegedly re-calculating the route and/or travel time based on the received traffic data. ¶17, 18 col. 128:29-38

Identified Points of Contention

  • Scope Questions: A central question may be whether the accused GoShare platform, which likely integrates third-party mapping services (e.g., Google Maps API), itself performs the claimed steps. The defense may argue that the "first processor" (the user's phone) does not "generate" or "update" the navigation information as claimed, but rather requests and displays a route that is fully computed by the external third-party service. This raises the question of whether merely displaying information calculated elsewhere satisfies the claim's active "generate" and "update" limitations.
  • Technical Questions: The complaint does not specify how the GoShare platform "updates the user navigation information... with a computed value for segments corresponding to the expected time to travel." A key factual dispute will be whether the GoShare application on the user's device actually performs this specific computation or if it simply receives and displays a pre-calculated travel time from an external server. Evidence of the specific software operations on the end-user device will be critical.

V. Key Claim Terms for Construction

  • The Term: "generate user navigation information"

    • Context and Importance: This term appears twice in Claim 1 and is fundamental to the invention. The infringement analysis will depend on whether this requires the mobile device's processor to create the route from raw map data itself, or if it can be construed more broadly to cover requesting and receiving a pre-packaged route from an external server. Practitioners may focus on this term to determine if the accused system's reliance on third-party APIs falls within the claim scope.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The specification describes the system as one for "providing" navigation, which could encompass coordinating with external services, not just local computation (’147 Patent, col. 2:48-51).
      • Evidence for a Narrower Interpretation: The claim language states the "first processor is programmed to... generate" the information, which suggests an active, creative step. The detailed description discusses the processor using stored data and algorithms to perform functions, which could imply local computation rather than simple retrieval from a remote source (’147 Patent, col. 128:10-18).
  • The Term: "updates the user navigation information... with a computed value for segments corresponding to the expected time to travel"

    • Context and Importance: This limitation recites a specific type of update based on a "computed value." The case may turn on whether the accused platform performs this exact calculation. If the platform only displays a final ETA from a third party without performing an intermediate computation of segment travel times on the mobile device, it may not infringe.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The patent's overall goal is to provide the user with a traffic-adjusted route. A party could argue that any process that results in the user seeing an updated, traffic-aware travel time meets the spirit of this limitation.
      • Evidence for a Narrower Interpretation: The term "computed value" is specific and appears tied to a calculation for individual "segments." The patent describes detailed processes for calculating travel time based on traffic density and other factors, suggesting a specific technical implementation is envisioned, not just the display of a final number (’147 Patent, col. 116:28-56, Fig. 87).

VI. Other Allegations

  • Indirect Infringement: The complaint alleges inducement by "encouraging or instructing its customers how to use its products and services" that provide the infringing navigation features (Compl. ¶18). Contributory infringement is alleged on the basis that Defendant supplies a "material part" of the infringing system (the platform/app) that is not a staple article of commerce (Compl. ¶18).
  • Willful Infringement: Willfulness is alleged based on Defendant's purported knowledge of the patent and its infringement (Compl. ¶19). The complaint further alleges Defendant continued its infringing activities with "specific intent" and took "deliberate actions to avoid learning" of the infringement, which may support a claim of willful blindness (Compl. ¶19).

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

  • A core issue will be one of infringement locus: does the accused GoShare platform—specifically the software on the end-user's mobile device—perform the active steps of "generating" and "updating" navigation information as recited in Claim 1? Or does it function as a passive terminal that merely requests and displays routes fully calculated by a separate, third-party mapping service, potentially avoiding direct infringement?
  • A key evidentiary question will be one of technical operation: what proof can be shown that the accused product's processor performs the specific step of "updat[ing] the user navigation information... with a computed value for segments corresponding to the expected time to travel"? The outcome may depend on whether this precise calculation is performed on the user's device or entirely on a remote server.
  • The dispute may also raise a question of divided infringement: if the actions satisfying the claim elements are split between the user's device, GoShare's servers, and a third-party mapping service, can Plaintiff demonstrate that one party directs or controls the entire infringing system as required by law?