5:22-cv-04826
AGIS Software Development LLC v. Google LLC
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Agis Software Development LLC (Texas)
- Defendant: Google LLC (Delaware)
- Plaintiff's Counsel: McKOOL SMITH, P.C.; Brown Rudnick LLP
- Case Identification: 5:22-cv-04826, E.D. Tex., 11/04/2019
- Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Google is registered to do business in Texas and has committed acts of infringement in the district. The complaint provides extensive details on Google's alleged physical presence, including Google Global Cache servers hosted by local ISPs, Google Wi-Fi services at Starbucks locations, and Google Fi cellular network infrastructure.
- Core Dispute: Plaintiff alleges that Defendant's Android operating system, associated hardware such as Pixel smartphones, and numerous Google applications including Google Maps and Find My Device, infringe six patents related to systems for interactive group communication, location sharing, and ad hoc networking.
- Technical Context: The technology at issue concerns mobile communication systems that enable situational awareness and coordination among groups of users by sharing location and status data on map-based interfaces, a capability relevant to both consumer and professional applications.
- Key Procedural History: The patents-in-suit have been subject to significant post-grant challenges. U.S. Patent No. 8,213,970, was subject to both ex parte reexamination and an inter partes review (IPR), resulting in the cancellation of several claims and amendment of asserted claim 10. The remaining five patents-in-suit are all part of the same patent family and were also the subject of IPR proceedings which, according to the provided patent file histories, resulted in the cancellation of the asserted claims.
Case Timeline
| Date | Event |
|---|---|
| 2004-09-21 | Earliest Priority Date for all Patents-in-Suit |
| 2010-05-20 | Launch of Android 2.2 (one of the earliest accused OS versions) |
| 2012-07-03 | U.S. Patent No. 8,213,970 Issues |
| 2016-08-02 | U.S. Patent No. 9,408,055 Issues |
| 2016-09-13 | U.S. Patent No. 9,445,251 Issues |
| 2016-10-11 | U.S. Patent No. 9,467,838 Issues |
| 2017-05-17 | Google Maps surpasses 1 billion users |
| 2017-08-29 | U.S. Patent No. 9,749,829 Issues |
| 2017-11-14 | U.S. Patent No. 9,820,123 Issues |
| 2019-11-04 | Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 8,213,970 - Method of Utilizing Forced Alerts for Interactive Remote Communications (Issued Jul. 3, 2012)
The Invention Explained
- Problem Addressed: The patent's background section identifies a need for a communication system where a message sender can not only transmit to a group but also confirm receipt from each recipient and require a manual response Compl. ¶81 '970 Patent, col. 1:50-64 Conventional digital messaging services at the time did not provide this closed-loop functionality of forcing an acknowledgment and a subsequent response '970 Patent, col. 1:60-64
- The Patented Solution: The invention is a system and method using "forced message alert software" on a computing device, such as a PDA/cell phone '970 Patent, col. 2:6-9 A sender transmits a message that forces the recipient's device to automatically send back an acknowledgment of receipt '970 Patent, abstract The recipient's device then displays the message along with a list of required manual responses (e.g., "will comply"), and the alert cannot be cleared until the recipient selects and transmits a response from that list '970 Patent, col. 2:25-34 The sender's device can monitor the acknowledgment and response status of all recipients '970 Patent, col. 2:17-25
- Technical Importance: The described technology provides a framework for reliable, acknowledged command-and-control communications, which is particularly valuable for coordinating time-sensitive activities among teams such as first-responders or military personnel Compl. ¶¶81-82
Key Claims at a Glance
The complaint asserts independent method claim 10 Compl. ¶90 The claim was amended during ex parte reexamination. The essential elements of the amended claim include:
- Receiving and identifying an electronic message as a "forced message alert".
- Automatically transmitting an acknowledgment of receipt to the sender.
- Transmitting a "selected required response from the response list" to clear the alert.
- Displaying the received response on the sender's device.
- Providing a list of which recipients have acknowledged the alert.
- Displaying a geographical map with georeferenced entities on the sender's device.
- Obtaining location and status data from the recipient device.
- Presenting a symbol for the recipient on the geographical map at its correct location.
'970 Patent, C1 Reexam., col. 2:22-68
U.S. Patent No. 9,408,055 - Method to Provide Ad Hoc and Password Protected Digital and Voice Networks (Issued Aug. 2, 2016)
The Invention Explained
- Problem Addressed: The patent identifies the need for emergency groups, such as military or first-responders from different organizations, to establish temporary (ad hoc) digital and voice communication networks "easily and rapidly" without the "need for pre-entry of data into a web or identifying others by name, phone numbers or email" '055 Patent, col. 2:5-12 This addresses challenges in coordinating disparate teams at a disaster scene who lack pre-existing communication channels '055 Patent, col. 2:16-34
- The Patented Solution: The invention describes a method where users join a temporary, password-protected network hosted on a server by entering a server IP address and an "ad hoc event name" '055 Patent, abstract Upon joining, each user's device (e.g., a PDA/GPS phone) sends its location and status to the server, which then distributes this information to all other network participants '055 Patent, col. 2:55-65 This allows all members of the ad hoc group to view each other's positions on a map and communicate, creating shared situational awareness on the fly '055 Patent, col. 3:1-12
- Technical Importance: This technology streamlines the creation of secure, temporary communication groups for field coordination, which is critical in emergency scenarios where participants and team structures are dynamic.
Key Claims at a Glance
The complaint asserts dependent claim 8, which relies on independent claim 1 Compl. ¶99 However, the provided patent documents indicate that both claim 1 and claim 8 were cancelled during post-grant proceedings '055 Patent, K1 IPR Cert. '055 Patent, C1 Reexam. Cert. The essential elements of the original independent claim 1 included:
- A first device receiving a message from a second device related to joining a group.
- Based on the message, sending the first device's location to a server and receiving location information for other group members from the server.
- Sending a request for georeferenced map data to a second server.
- Receiving the georeferenced map data.
- Presenting an interactive map with user-selectable symbols representing the locations of other group members.
- Identifying user interaction with a symbol and, based on that interaction, sending data to the corresponding device via the first server.
'055 Patent, col. 14:60 - col. 16:4
Multi-Patent Capsule: Additional Patents-in-Suit
The following four patents share the same title, "Method to Provide Ad Hoc and Password Protected Digital and Voice Networks," and belong to the same family as the '055 Patent. The complaint alleges infringement by the same accused products and functionalities. The provided patent documents indicate that the asserted claims in these patents were also cancelled during IPR proceedings.
U.S. Patent No. 9,445,251 (Issued Sep. 13, 2016)
- Technology Synopsis: The patent describes a method for users to rapidly form temporary, password-protected communication networks for sharing location and status data via a central server. The system is designed to facilitate coordination among groups, such as first responders, without requiring pre-configuration of user information.
- Asserted Claims: Claim 24 Compl. ¶113
- Accused Features: Google applications, including Google Maps, which allegedly allow users to form groups, share locations, view others on a map, and communicate Compl. ¶¶115-117
U.S. Patent No. 9,467,838 (Issued Oct. 11, 2016)
- Technology Synopsis: This patent covers a method for creating ad hoc, password-protected networks for voice and data communication. Users join a server-managed group by providing an event name and password, enabling them to share real-time location and status data on a map-based interface for coordinated activities.
- Asserted Claims: Claim 54 Compl. ¶127
- Accused Features: Google's services, such as Google Maps, are accused of allowing users to establish groups and exchange location and message data via Google's servers Compl. ¶¶129-131
U.S. Patent No. 9,749,829 (Issued Aug. 29, 2017)
- Technology Synopsis: The invention provides a method for individuals to quickly set up temporary, secure digital and voice networks. By connecting to a server with a shared event name and password, participants can coordinate activities by sharing their locations and other data, which are displayed on an interactive map.
- Asserted Claims: Claim 68 Compl. ¶141
- Accused Features: Google applications and services, including Google Maps, are accused of infringing by enabling users to form groups to share locations and communicate via Google's server infrastructure Compl. ¶¶143-145
U.S. Patent No. 9,820,123 (Issued Nov. 14, 2017)
- Technology Synopsis: This patent details a system for establishing ad hoc communication networks where users can join a group via a server using a password. Once joined, the system facilitates the exchange of location, status, and other data among participants for real-time coordination on a map display.
- Asserted Claims: Claim 23 Compl. ¶155
- Accused Features: The complaint accuses Google products like Google Maps of infringing by allowing users to create groups for location sharing and communication, managed through Google's servers Compl. ¶¶157-159
III. The Accused Instrumentality
Product Identification
The complaint names a broad range of Google products and services, collectively termed the "Accused Products" Compl. ¶86 These include:
- Hardware: Google smartphones and tablets (e.g., Nexus and Pixel series) and Chrome-based notebooks.
- Operating Systems: Android OS (versions 2.2-10.0) and Android Wear OS.
- Applications & Services: A suite of Android-based applications such as Google Maps, Find My Device (formerly Android Device Manager), Trust Contacts, Family Link, Hangouts, and Messages.
- Infrastructure: Google's servers that provide the backend services for these applications.
Functionality and Market Context
- The infringement allegations center on two main functionalities. The first is the ability of applications like Google Maps to allow users to form temporary or persistent groups to share their real-time locations, view each other as icons on a map, and communicate Compl. ¶87 Compl. ¶102 The complaint provides a screenshot from the Google Maps application showing a map with user icons and a menu for managing location sharing Compl. p. 47 The second functionality is found in the "Find My Device" service, which allows a user to remotely locate, ring, lock, or erase a lost or stolen device associated with their Google account Compl. ¶87 A screenshot in the complaint depicts the Find My Device interface, showing a map with the device's location and remote control options Compl. p. 39
- The complaint emphasizes the commercial significance of the accused products, noting that the Android operating system is the "most widely used in smartphones" and that its ecosystem includes over two billion monthly active devices Compl. ¶85 Compl. ¶10
IV. Analysis of Infringement Allegations
U.S. Patent No. 8,213,970 Infringement Allegations
| Claim Element (from Independent Claim 10, as amended) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| receiving an electronically transmitted electronic message; | A command, such as "play sound" or "lock," is sent from a user's web browser or another device to a lost Android device via Google's servers. | ¶93 | col. 2:22-23 |
| identifying said electronic message as a forced message alert...which triggers the activation of the forced message alert software application program... | The Android OS on the lost device receives the command and is compelled to execute the corresponding function (e.g., ringing, locking the screen). | ¶93 | col. 2:24-29 |
| transmitting an automatic acknowledgment of receipt to the sender PDA/cell phone... | The lost device reports its status (e.g., its current location, that it is ringing) back to the Find My Device service, which is displayed to the user. | ¶93 | col. 2:30-34 |
| transmitting a selected required response from the response list...to be cleared from the recipient's cell phone display... | The complaint does not provide sufficient detail for analysis of this element. | ¶92 | col. 2:40-47 |
| displaying the response received from the PDA cell phone...on the sender of the forced alert PDA/cell phone; | The user's web browser or app (the "sender") displays the updated status and location of the lost device. The screenshot shows the "Last seen just now" status. | ¶39 | col. 2:48-51 |
| displaying a geographical map with georeferenced entities on the display of the sender PDA/cellphone; | The Find My Device interface displays a map showing the location of the lost device. This is depicted in a screenshot showing "Rachel's phone" on a map of London. | ¶39 | col. 2:58-60 |
| obtaining location and status data associated with the recipient PDA/cellphone; | The Find My Device service obtains the GPS coordinates and status (e.g., battery life, Wi-Fi connection) of the lost device. | ¶39 | col. 2:61-62 |
| and presenting a recipient symbol on the geographical map corresponding to a correct geographical location of the recipient PDA/cellphone... | An icon representing the lost device is displayed on the map at its reported coordinates. | ¶39 | col. 2:63-66 |
- Identified Points of Contention:
- Scope Questions: A primary question may be whether a remote command sent to an unattended device (as in Find My Device) constitutes a "forced message alert" within the meaning of the patent, which describes a system for compelling responses between human operators.
- Technical Questions: The analysis may focus on whether the Find My Device workflow includes the claimed step of a recipient transmitting a "selected required response from the response list" to clear the display. The complaint's allegations do not clearly map any feature of the accused product to this specific limitation, raising the question of a potential mismatch in technical operation.
U.S. Patent No. 9,408,055 Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| receiving a message sent by a second device, wherein the message relates to joining a group; | A user receives an invitation via a Google service (e.g., Maps, Messages) to join a group or share their location with another user. | ¶102; ¶118 | col. 14:62-64 |
| based on receipt of the message...sending first location information to a first server and receiving second location information from the first server... | The user's device sends its GPS location to Google's servers and receives the locations of other group members from the same servers. | ¶102; ¶119 | col. 14:65-15:4 |
| sending, from the first device to a second server, a request for georeferenced map data; | The Google Maps application on a user's device requests map tiles and data from Google's map servers to render the map display. | ¶103 | col. 15:5-7 |
| presenting, via an interactive display..., a first interactive, georeferenced map and a plurality of user-selectable symbols corresponding to the plurality of second devices... | The Google Maps app displays the map and shows icons representing other users in the group at their respective locations. A screenshot shows user icons on a map in the Echo Park area. | ¶106; ¶48 | col. 15:11-19 |
| identifying user interaction with the interactive display selecting one or more of the user-selectable symbols...and...sending data to the one or more second devices via the first server. | A user taps on another user's icon to initiate an action, such as sending a message or getting directions, which is mediated by Google's servers. | ¶107 | col. 15:24-32 |
- Identified Points of Contention:
- Legal Questions: A dispositive issue is that asserted claim 8 and its independent parent claim 1 appear to have been cancelled in post-grant proceedings, which raises the question of whether a valid cause of action exists for this patent.
- Scope Questions: Should the claims be found valid, a point of contention may be whether creating a location-sharing group within a persistent, centralized service like Google Maps constitutes the formation of an "ad hoc" network as described in the patent's specification.
V. Key Claim Terms for Construction
For U.S. Patent No. 8,213,970
- The Term: "forced message alert"
- Context and Importance: This term is central to the invention's purpose. The construction of this term will determine whether the patent's scope is limited to communications requiring a deliberative response from a human recipient or if it can also cover automated commands sent to an unattended device. Practitioners may focus on this term because the infringement theory relies on mapping it to the remote commands of the Find My Device service.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claims focus on the technical sequence: a message triggers an automatic acknowledgment and requires a subsequent action to clear an interface. Language such as "triggers the activation of the forced message alert software" could be argued to encompass any software-compelled action, regardless of human intervention '970 Patent, C1 Reexam., col. 2:27-29
- Evidence for a Narrower Interpretation: The specification repeatedly provides examples of response lists with options like "will comply," "will not comply," and "have complied," which strongly suggest a human operator is the intended recipient who must make a choice '970 Patent, col. 7:25-30 This context may support a narrower construction limited to interactive communications between people.
For U.S. Patent No. 9,408,055
- The Term: "ad hoc... network" (from the title and specification)
- Context and Importance: Although not in the asserted claim, this concept defines the patent's context. The case may turn on whether creating a temporary location-sharing group on a massive, pre-existing, server-based platform like Google Maps falls within the scope of creating an "ad hoc" network. Practitioners may see this as a key battleground over the patent's applicability to modern cloud services.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The abstract and background emphasize the goal of allowing users to "easily and rapidly" form networks to "coordinate their activities eliminating the need for pre-entry of data" '055 Patent, abstract '055 Patent, col. 2:8-12 This focus on the user's experience of rapid, temporary group formation could support arguing that a Google Maps sharing group is functionally "ad hoc."
- Evidence for a Narrower Interpretation: The specification describes the problem in the context of coordinating disparate organizations like police and fire departments at a disaster scene, where pre-existing infrastructure may be unavailable or insufficient '055 Patent, col. 2:16-34 This may suggest the invention was directed toward more decentralized or self-contained networks, rather than groups formed within a global, persistent service.
VI. Other Allegations
- Indirect Infringement: The complaint alleges induced infringement for all six patents-in-suit. It asserts that Google intentionally encourages infringement by providing customers with instructions on how to use the accused features through "training videos, demonstrations, brochures, installations and/or user guides," and support websites Compl. ¶91 Compl. ¶100 Compl. ¶114
- Willful Infringement: Willfulness is alleged for all six patents. The complaint pleads that Google "actually knew or should have known" that its actions constituted an "unjustifiably high risk of infringement" Compl. ¶96 Compl. ¶110 The allegations do not specify any instances of pre-suit notice or knowledge of the patents.
VII. Analyst's Conclusion: Key Questions for the Case
A threshold issue for five of the six asserted patents ('055, '251, '838, '829, '123) will be one of claim viability: given that the asserted claims in this patent family appear to have been cancelled in inter partes review proceedings, what legal basis, if any, remains for these infringement counts to proceed?
For the sole remaining patent ('970), a central question will be one of definitional scope: can the term "forced message alert", which the patent specification ties to a system for compelling responses from human operators, be construed to cover the function of sending remote-control commands to an unattended lost device, as in Google's Find My Device service?
A secondary question will be one of technical equivalence: does the operation of the accused Find My Device service meet every element of the asserted method claim, particularly the requirement for a recipient to select a response from a "response list" to clear the device's display?