DCT

1:19-cv-02012

Geographic Location Innovations LLC v. Mobike Inc

Key Events
Complaint
complaint

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:19-cv-02012, D. Del., 10/23/2019
  • Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant is a Delaware corporation and is therefore deemed a resident of the District.
  • Core Dispute: Plaintiff alleges that Defendant’s app-based bicycle sharing service infringes a patent related to systems for remotely requesting, determining, and transmitting location information to a user's positional device for route guidance.
  • Technical Context: The technology concerns telematics and remote data management for navigation systems, a field that has become central to mobile, location-based applications and services.
  • Key Procedural History: The complaint indicates that the Plaintiff is the owner of the patent-in-suit by assignment. No other significant procedural events, such as prior litigation or administrative proceedings involving the patent, are mentioned.

Case Timeline

Date Event
2006-04-28 Earliest Priority Date for U.S. Patent No. 7,917,285
2011-03-29 U.S. Patent No. 7,917,285 Issued
2019-10-23 Complaint Filed

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

  • Patent Identification: U.S. Patent No. 7,917,285 (“the ’285 Patent”), “Device, System and Method for Remotely Entering, Storing and Sharing Addresses for a Positional Information Device,” issued March 29, 2011.

The Invention Explained

  • Problem Addressed: The patent’s background section describes the difficulty, inconvenience, and potential safety hazards of manually entering destination addresses into GPS devices, particularly when a user is driving or when different devices use inconsistent interfaces (’285 Patent, col. 1:43-col. 2:14).
  • The Patented Solution: The invention proposes a system where a user’s positional device (e.g., a GPS unit) transmits a request for a location to a remote server. The server determines the coordinates for that location and transmits the "determined address" back to the device, which can then calculate and display a route, thereby bypassing the need for manual address entry by the user (’285 Patent, Abstract; col. 2:32-55).
  • Technical Importance: This architecture aimed to enhance the safety and user-friendliness of navigation systems by centralizing the task of address lookup and resolution on a remote server, a foundational concept for many modern telematics services (’285 Patent, col. 2:26-30).

Key Claims at a Glance

  • The complaint asserts infringement of at least independent claim 13 of the ’285 Patent (Compl. ¶13).
  • The essential elements of Claim 13 are:
    • A server configured to receive a request for an address of a location, determine the address, and transmit it to a positional information device.
    • A positional information device comprising a locational module (e.g., GPS), a communication module to receive the address from the server, a processing module to determine route guidance, and a display module.
    • A communications network coupling the server and the device.
    • A further requirement that the server receives a time and date with the location request and transmits this time and date back with the determined address, with the device then displaying the determined address at that associated time and date.
  • The complaint notes that Plaintiff may assert infringement of other claims in the future (Compl. ¶13).

III. The Accused Instrumentality

Product Identification

  • The accused instrumentality is Defendant's "cycle-booking service Mobike – Smart Bike Sharing," which includes the Mobike mobile app, its associated website, and backend server hardware (the "System") (Compl. ¶13).

Functionality and Market Context

  • The Mobike System allows a user to locate and rent a nearby shared bicycle using a smartphone app (Compl. ¶13). The app on the user’s smartphone sends a request to Mobike’s servers for the locations of available cycles (Compl. ¶15). The servers determine these locations and transmit them back to the smartphone, which then displays the bike locations on a map and can provide route guidance to a selected bike (Compl. ¶¶16, 19). A screenshot provided in the complaint shows the Mobike app's main interface, which displays a map populated with icons representing available bikes (Compl. p. 3).
  • The complaint alleges the system functions by using the smartphone's built-in GPS capabilities to determine the user's position and its network transceiver to communicate with the servers (Compl. ¶¶17-18). A screenshot of the app's permissions shows it requests access to the device's location services (Compl. p. 5).

IV. Analysis of Infringement Allegations

’285 Patent Infringement Allegations

Claim Element (from Independent Claim 13) Alleged Infringing Functionality Complaint Citation Patent Citation
a server configured to receive a request for an address of at least one location not already stored in the positional information device, to determine the address of the least one location and to transmit the determined address to the positional information device Mobike's servers allegedly receive a user's request for cycle locations via the app, determine the locations (addresses) of the cycles, and transmit them to the user's smartphone (Compl. p. 4). ¶¶15, 16 col. 2:46-48
the positional information device including a locational information module for determining location information of the positional information device; The user's smartphone, which contains a location information module (GPS) utilized by the Mobike app (Compl. p. 5). ¶17 col. 5:5-14
a communication module for receiving the determined address of the at least one location from the server; The smartphone's cellular network transceiver, which receives the cycle locations from the Mobike server (Compl. p. 6). ¶18 col. 6:40-54
a processing module configured to receive the determined address...and determine route guidance based on the location of the positional information device and the determined address; The smartphone's processor running the Mobike app, which allegedly determines a travel route to the selected cycle based on the user's location and the cycle's location (Compl. p. 7). ¶19 col. 4:38-43
a display module for displaying the route guidance; The screen of the smartphone, which displays the map and route guidance to the cycle. ¶20 col. 4:18-24
a communications network for coupling the positional information device to the server, The cellular and/or Wi-Fi network that connects the user's smartphone to the Mobike servers. ¶21 col. 8:15-18
wherein the server receives a time and date associated with the requested at least one location and transmits the associated time and date with the determined address...and the positional information device displays the determined address at the associated time and date. The complaint alleges the server receives a time and date with the request for a location, transmits it back with the location data, and the app displays the determined address at the associated time and date. ¶22 col. 10:55-62

Identified Points of Contention

  • Scope Questions: The infringement theory raises a question of claim scope: whether the term "address," which the patent’s specification primarily illustrates with examples of fixed, civic street addresses for vehicle navigation (e.g., ’285 Patent, col. 1:51-52), can be construed to read on the dynamically changing GPS coordinates of a mobile asset like a shared bicycle.
  • Technical Questions: A key factual question relates to the final "wherein" clause of claim 13. What evidence does the complaint provide that the Mobike system specifically transmits a "time and date" associated with the request and that the app then "displays the determined address at the associated time and date"? The complaint makes a conclusory allegation to this effect but does not include a screenshot or other evidence depicting this specific display function, suggesting this may be a point of dispute.

V. Key Claim Terms for Construction

  • The Term: "address"

    • Context and Importance: The interpretation of "address" is central to the dispute. The Defendant may argue the patent is limited to the context of conventional street addresses, while the Plaintiff will likely argue for a broader meaning that covers any form of location data, including the GPS coordinates of the accused bicycles.
    • Intrinsic Evidence for a Broader Interpretation: The patent repeatedly uses the more general term "location information" (’285 Patent, col. 2:39-40) and the claim itself refers to an "address of at least one location," which could be argued to encompass any identifier for a physical point.
    • Intrinsic Evidence for a Narrower Interpretation: The patent’s background section is framed entirely around the problem of entering street addresses into vehicle GPS units, using a specific street address as an example (’285 Patent, col. 1:51-52). This context may be used to argue that "address" should be interpreted more narrowly than raw coordinate data.
  • The Term: "displays the determined address at the associated time and date"

    • Context and Importance: This limitation appears to require a specific user interface function where the location is displayed in direct association with a time and date. Practitioners may focus on this term because it presents a specific factual hurdle for the infringement allegation that may not be met by a general map timestamp.
    • Intrinsic Evidence for a Broader Interpretation: A plaintiff might argue that any display where a location and a relevant time are simultaneously visible on the screen—even if not physically adjacent—satisfies this limitation, as long as they are contextually associated.
    • Intrinsic Evidence for a Narrower Interpretation: A defendant could argue that the term "at" requires a more direct and explicit association, such as displaying the location icon or information with a specific timestamp of the request appended to it. The patent describes transmitting the time and date so that "the GPS device will then display the address at the specified date and time" (’285 Patent, col. 10:57-59), suggesting a direct functional link.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges that Defendant is liable for contributory infringement and inducement, presumably on the basis that Mobike provides the entire system (servers and app) and instructs users, via its app interface and marketing, to perform the steps that allegedly constitute direct infringement (Compl. ¶13).
  • Willful Infringement: The complaint does not contain a specific count for willful infringement or allege any facts that would support a finding of willfulness, such as pre-suit knowledge of the ’285 Patent. The prayer for relief includes a general request for damages pursuant to 35 U.S.C. § 284, which allows for enhancement, but the factual predicate for such enhancement is not pled (Compl. p. 10).

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

This case appears to center on two fundamental questions for the court:

  • A core issue will be one of definitional scope: can the term "address," which is described in the patent’s specification within the context of vehicle navigation to fixed street locations, be construed broadly enough to cover the transient GPS coordinates of a shared bicycle in a mobile app?
  • A key evidentiary question will be one of functional performance: does the accused Mobike app perform the specific, two-part function required by the final clause of Claim 13—transmitting a request-associated time and date back to the device and then displaying the location "at" that time and date—or is there a factual mismatch in the technical operation of the accused system?