DCT

1:24-cv-00888

Social Positioning Input Systems LLC v. Dispatchit Inc

Key Events
Complaint
complaint

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:24-cv-00888, W.D. Tex., 08/06/2024
  • Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Defendant maintains an established business presence in the district, specifically in Austin.
  • Core Dispute: Plaintiff alleges that Defendant’s delivery management platform infringes a patent related to methods for remotely programming a positional information device with location data.
  • Technical Context: The technology addresses simplifying the process of entering destination addresses into navigation systems by using a remote server to look up and transmit coordinates directly to a user's device.
  • Key Procedural History: The complaint notes that the patent-in-suit was examined and allowed over numerous prior art references and has since been cited as relevant prior art in patent applications by major technology companies. This is presented to support the patent’s validity and pioneering nature.

Case Timeline

Date Event
2006-04-28 Earliest Priority Date for '365 Patent
2016-02-16 U.S. Patent No. 9,261,365 Issues
2024-08-06 Complaint Filed
2026-04-28 Nominal Expiration Date for '365 Patent

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

  • Patent Identification: U.S. Patent No. 9,261,365, "DEVICE, SYSTEM AND METHOD FOR REMOTELY ENTERING, STORING AND SHARING ADDRESSES FOR A POSITIONAL INFORMATION DEVICE," issued February 16, 2016.

The Invention Explained

  • Problem Addressed: The patent describes the state of the art in 2006, where manually programming addresses into GPS devices was problematic due to inconsistent address recognition formats, different user interfaces across devices, and the difficulty and safety risks of entering data while driving (Compl. ¶13; ’365 Patent, col. 1:54-2:42).
  • The Patented Solution: The invention provides a system where a user can communicate a desired location to a remote server, which then resolves the location into coordinates and transmits them directly to the user's "positional information device" (e.g., a GPS unit) for automatic programming and route guidance (’365 Patent, Abstract; col. 4:3-11). The system is also described as enabling the sharing of addresses between different GPS devices owned by the same user (’365 Patent, col. 11:30-45).
  • Technical Importance: The technology aimed to remove the friction and inconsistency of manual address entry for navigation devices by centralizing the lookup and programming function on a remote server accessible via a communications network (’365 Patent, col. 2:38-44).

Key Claims at a Glance

  • The complaint asserts at least independent claim 1 (Compl. ¶27).
  • The essential elements of Claim 1, a method for receiving location information, are:
    • Sending a request from a "requesting positional information device" to a server for an address that is stored in a "sending positional information device."
    • The request includes a "first identifier" of the requesting device.
    • Receiving the retrieved address at the "requesting positional information device" from the server.
    • The method requires that the server uses the "first identifier" to determine a "second identifier" for the "sending positional information device," and then uses that to retrieve the address from the "sending positional information device."
  • The complaint does not specify assertion of any dependent claims.

III. The Accused Instrumentality

Product Identification

  • Defendant’s "Dispatch Connect, a delivery management platform/software" (Compl. ¶27).

Functionality and Market Context

  • The complaint describes Dispatch Connect as a platform that allows "shippers" (dispatchers) to monitor drivers' locations in real-time on a mobile device such as a smartphone or laptop (Compl. ¶27). The complaint includes a screenshot from the Defendant’s website, which advertises "Dispatch Delivers In Austin," to support allegations of an established business presence in the district (Compl. ¶7, Fig. 1). This suggests the platform is used for commercial logistics and last-mile delivery services.

IV. Analysis of Infringement Allegations

The complaint references a claim chart in an "Exhibit B" to detail its infringement allegations; however, this exhibit was not included with the filed complaint (Compl. ¶¶27, 33). The following analysis is based on the narrative allegations.

’365 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
A method for receiving location information at a positional information device, the method comprising: sending a request from a requesting positional information device to a server for at least one address stored in at least one sending positional information device, the request including a first identifier of the requesting positional information device; The Dispatch Connect platform, when used by shippers and drivers, is alleged to perform the claimed method. The complaint does not specify which device acts as the "requesting" versus the "sending" device, or where the address is stored. ¶27 col. 13:54-62
and receiving at the requesting positional information device, from the server, a retrieved at least one address to the requesting positional information device wherein the server determines a second identifier for identifying the at least one sending positional information device based on the received first identifier and retrieves the requested at least one address stored in the identified at least one sending positional information device. The platform is alleged to enable the transfer of location information between users (e.g., shipper to driver). The complaint does not provide specific facts on how the accused platform determines identifiers or retrieves data from a specific "sending positional information device." ¶27 col. 13:63 - col. 14:2
  • Identified Points of Contention:
    • Scope Questions: A central dispute may arise over the definition of "positional information device." The patent primarily describes this as a user's mobile GPS unit (’365 Patent, col. 4:12-24). The infringement theory may require one of Defendant's servers to be construed as a "sending positional information device," which raises the question of whether a server fits the patent's definition of a mobile navigation device.
    • Technical Questions: Claim 1 requires a specific data flow: a request is sent for an address stored in a "sending positional information device," which the server then retrieves from that device. A key question for the court will be whether the accused Dispatch Connect platform performs this specific server-mediated, device-to-device retrieval, or if it operates on a more conventional client-server model where a server pushes address data from its own central database to a client device. The complaint lacks the specific factual allegations to resolve this question.

V. Key Claim Terms for Construction

  • The Term: "positional information device"

  • Context and Importance: This term appears in both the "requesting" and "sending" roles in Claim 1. The viability of the infringement case depends on whether the components of the accused "Dispatch Connect" platform, which includes servers and user devices (smartphones, laptops), fall within its scope. Practitioners may focus on this term because the Defendant is likely to argue its backend server is not a "positional information device" in the context of the patent.

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The specification states that the invention’s principles "may be applied to any type of navigation or positional information device including but not limited to a vehicle-mounted device, a GPS receiver coupled to a desktop computer or laptop, etc." (’365 Patent, col. 4:16-21). This language could support an argument that any computing device within the accused system that handles location data qualifies.
    • Evidence for a Narrower Interpretation: The patent repeatedly and consistently frames the invention in the context of a "global positioning system (GPS) device" (’365 Patent, Abstract; col. 1:24). The figures and detailed description focus on handheld or vehicle-integrated units designed for user navigation, suggesting the term is tied to an end-user's mobile navigation-focused hardware.
  • The Term: "at least one address stored in at least one sending positional information device"

  • Context and Importance: This limitation defines the source of the location data. Infringement requires proof that the accused system retrieves an address that is specifically "stored in" a component that qualifies as a "sending positional information device." This is critical because it distinguishes the claimed method from a system where a server generates or retrieves an address from a generic database not associated with a specific "device."

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The claim language itself is open-ended. An argument could be made that if a server is construed as a "positional information device," then any address in its database is "stored in" it, satisfying the limitation.
    • Evidence for a Narrower Interpretation: The specification describes embodiments where a user retrieves an address stored on one of their other vehicles' GPS units, implying the "sending positional information device" is a peer device, not a central server (’365 Patent, col. 13:28-45). This context suggests the address originates from a distinct end-user device, not a centralized platform database.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges inducement and contributory infringement, stating that Defendant provides the "Dispatch Connect" platform and distributes "product literature and website materials" that instruct end users on how to use the platform in an infringing manner (Compl. ¶¶27, 30).
  • Willful Infringement: The complaint alleges Defendant has knowledge of its infringement "at least as of the service of the present complaint" (Compl. ¶25). This allegation appears to be based on the notice provided by the lawsuit itself and does not assert pre-suit knowledge of the patent.

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

  • A core issue will be one of definitional scope: can the term "positional information device", which the patent repeatedly associates with end-user GPS navigation units, be construed broadly enough to read on the server components of Defendant’s "Dispatch Connect" logistics platform?
  • A key evidentiary question will be one of technical implementation: can the Plaintiff demonstrate that the accused platform performs the specific method of retrieving an address from one designated "sending positional information device" to deliver to a "requesting" one, as required by the claim, or does the system use a different architecture, such as a central server pushing data from its own database to clients?