DCT
4:24-cv-00126
Push Data LLC v. State Farm Mutual Automobile Insurance Co
Key Events
Complaint
Table of Contents
complaint
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Push Data LLC (Delaware)
- Defendant: State Farm Mutual Automobile Insurance Company (Delaware)
- Plaintiff’s Counsel: Beaty Legal PLLC
- Case Identification: 4:24-cv-00126, E.D. Tex., 02/14/2024
- Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas on the grounds that Defendant has committed acts of infringement in the District and maintains multiple established places of business there.
- Core Dispute: Plaintiff alleges that Defendant’s State Farm mobile application infringes four patents related to location-aware, preference-based push notifications and content delivery.
- Technical Context: The patents address early methods for providing geographically relevant information to mobile devices by using location data and user preferences to trigger push notifications, effectively creating a "geographical web browser."
- Key Procedural History: The complaint alleges all four patents-in-suit descend from a common patent application filed in 1998. The patents expired in 2018. The complaint alleges Defendant had knowledge of the patents and its infringement since at least the filing of the complaint.
Case Timeline
| Date | Event |
|---|---|
| 1998-11-17 | Earliest Priority Date for all Patents-in-Suit |
| 2006-01-03 | U.S. Patent No. 6,983,139 Issues |
| 2006-06-06 | U.S. Patent No. 7,058,395 Issues |
| 2007-05-01 | U.S. Patent No. 7,212,811 Issues |
| 2007-11-06 | U.S. Patent No. 7,292,844 Issues |
| 2010-04-01 | Approx. Date of Accused State Farm App Development |
| 2014-01-01 | Approx. Date Asserted Features Became Common in Android |
| 2018-11-17 | Expiration Date for all Patents-in-Suit |
| 2024-02-14 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 7,058,395 - GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS
- Issued: June 6, 2006
The Invention Explained
- Problem Addressed: At the time of the invention, no technology existed to automatically control a network application, like a web browser, by using local broadcast information that was selectively filtered for a user (Compl. ¶14; ’395 Patent, col. 2:57-62). Existing systems required users to manually select an icon or navigate to access location-specific information, and location data from cellular networks was too coarse to provide individualized content (Compl. ¶14, ¶16; ’395 Patent, col. 3:23-26).
- The Patented Solution: The invention describes a system where a mobile unit can receive information based on its precise geographical position (e.g., from GPS) and user-defined preferences (Compl. ¶15, ¶19). A network server uses this location and preference data to identify relevant content and then sends an "unsolicited pushed message" to the mobile unit, notifying the user of the content's availability without requiring the device to maintain a continuous, active connection to the server (’395 Patent, Abstract; ’395 Patent, col. 4:21-30). This allows a user to "surf the web" by physically moving through different geographic areas (Compl. ¶55).
- Technical Importance: The invention provided a framework for location-based services that automatically pushed relevant data to users, a foundational concept for modern mobile applications that provide geographically-aware alerts and content (Compl. ¶12, ¶63).
Key Claims at a Glance
- The complaint asserts independent claims 1 and 22 (’395 Patent, col. 23:1-24:52).
- Claim 1 (Method) includes the elements of:
- Receiving a user interest indication and a location indication for a particular mobile unit.
- Identifying an information item that matches both the interest and the location.
- Causing information about that item to be transmitted to the mobile unit via one or more "unsolicited pushed messages" without needing to maintain an "active user-interactive client-server application layer session."
- Claim 22 (Method) includes the elements of:
- Causing a "communication push message" to be sent to a mobile unit, where the message identifies a target application and contains information about further content available for download.
- The push message is not a direct server response to a client request.
- Receiving a client-request packet from the mobile unit in response to a user selecting an indication presented by the target application.
- Sending the further content to the mobile unit in response to that client-request packet.
- The complaint reserves the right to assert dependent claims (Compl. ¶84).
U.S. Patent No. 7,292,844 - GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS
- Issued: November 6, 2007
The Invention Explained
- Problem Addressed: The technology described in the ’844 Patent addresses the same technical problems as the ’395 Patent: the lack of systems to automatically deliver geographically relevant information to mobile users without manual navigation or the limitations of coarse cellular location data (Compl. ¶14, ¶16; ’844 Patent, col. 2:57-62, col. 3:23-26).
- The Patented Solution: The ’844 Patent also discloses a system for a "geographical web browser" that uses a mobile unit's location and user preferences to trigger the delivery of relevant information (’844 Patent, Abstract). The claims focus on specific client-server interactions, including a multi-step process where a device can operate over different wireless networks (e.g., cellular and a local network like Wi-Fi) to request, be notified of, and then pull content from a server (Compl. ¶46; ’844 Patent, col. 24:55-26:22).
- Technical Importance: This patent further details methods for efficient, location-aware data synchronization between a mobile application and a server, particularly in an environment with multiple wireless network types (Compl. ¶38, ¶53).
Key Claims at a Glance
- The complaint asserts independent claims 1 and 25 (’844 Patent, col. 23:1-26:22).
- Claim 1 (Method) is substantially similar to Claim 1 of the ’395 Patent, including the elements of:
- Receiving user interest and location indications.
- Identifying a matching information item.
- Causing an "unsolicited pushed message" to be sent without maintaining an active client-server session.
- Claim 25 (Method) includes the elements of:
- A remote server receiving a first request from a handheld device via a first wireless network.
- The server transmitting a response indicating content availability.
- The server receiving a second request from the device, which is "automatically generated... without requiring user action," via a second wireless network.
- The server coupling the available content to the device via the second wireless network.
- The complaint reserves the right to assert dependent claims (Compl. ¶105).
U.S. Patent No. 7,212,811 - GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS
- Patent Identification: U.S. Patent No. 7,212,811, issued May 1, 2007.
- Technology Synopsis: This patent, part of the same family, also describes methods for delivering geographically relevant information to mobile devices. It addresses the problem of enabling location-based content delivery without requiring constant user interaction or relying on imprecise location data from the pre-GPS/Wi-Fi era (Compl. ¶14, ¶16). The solution involves using a device's location and user preferences to trigger push notifications for relevant server-side content (’811 Patent, Abstract).
- Asserted Claims: The complaint asserts at least independent claims 1 and 5 (Compl. ¶124, ¶128).
- Accused Features: The complaint alleges infringement based on the State Farm App's client-server communication methods, which allegedly involve a multi-step request, notification, and automated data pull sequence (Compl. ¶122).
U.S. Patent No. 6,983,139 - GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS
- Patent Identification: U.S. Patent No. 6,983,139, issued January 3, 2006.
- Technology Synopsis: As another member of the same patent family, this patent addresses the technical challenge of automatically filtering and pushing location-relevant web content to mobile users (Compl. ¶14). The patented solution describes a system where a mobile unit's physical movement triggers the delivery of information that has been filtered according to the user's location and pre-stated interests, avoiding the need for manual browsing (’139 Patent, Abstract).
- Asserted Claims: The complaint asserts at least independent claims 22, 43, and 90 (Compl. ¶145, ¶147).
- Accused Features: Infringement allegations against the ’139 Patent target the same general client-server functionalities of the State Farm App as the other asserted patents, focusing on a multi-step process for delivering updated, relevant content to the mobile application (Compl. ¶143).
III. The Accused Instrumentality
Product Identification
- The "Accused Instrumentalities" are identified as the State Farm mobile application ("State Farm App") and its associated ecosystem, including Defendant's servers and client-side software operating on mobile devices (Compl. ¶66, ¶78).
Functionality and Market Context
- The complaint alleges that the State Farm App operates in a client-server environment, connecting through various networks such as cellular and Wi-Fi (Compl. ¶66, ¶81, ¶102).
- The core accused functionality involves a method where a remote server receives requests from the mobile app, responds with notifications about available content, and then, following an automatically generated second request from the app, delivers that content to the mobile device (Compl. ¶80, ¶101).
- The complaint alleges that original versions of the State Farm App were developed around April 2010 (Compl. ¶79, ¶100).
IV. Analysis of Infringement Allegations
No probative visual evidence provided in complaint.
The complaint references infringement analysis in Exhibits E, F, G, and H, but these exhibits were not filed with the complaint. The analysis is therefore based on the narrative infringement theory provided in the body of the complaint.
’395 Patent Infringement Allegations
- The complaint alleges that the Accused Instrumentalities perform a method that infringes at least claims 1, 4, and 22 of the ’395 Patent (Compl. ¶86). The alleged method involves a remote server receiving a first request from a mobile device, the server responding with a notification that content is available, the server then receiving a second, automatically generated request from the device, and finally, the server coupling the content to the device (Compl. ¶80). This process is alleged to occur in an environment with at least two wireless access stations, such as a cellular and a Wi-Fi network (Compl. ¶81). This sequence suggests an alignment with the notification and content-pull steps recited in claim 22.
’844 Patent Infringement Allegations
- The complaint alleges that the Accused Instrumentalities perform the same multi-step client-server method described above, infringing at least claims 1, 25, 32, 37, and 46 of the ’844 Patent (Compl. ¶107). The alleged sequence of a server receiving a first request, responding with a notification, receiving a second automatically generated request, and coupling content appears to map to the elements of independent claim 25 of the ’844 patent, which explicitly recites this sequence of events (Compl. ¶101; ’844 Patent, col. 25:47-26:22).
Identified Points of Contention:
- Scope Questions: A central question may be whether modern push notification systems (e.g., Apple Push Notification Service or Google Firebase Cloud Messaging), which mediate communication between an app server and a mobile device, fall within the scope of the claimed invention. The patents describe a server identifying relevant information and generating an "unsolicited pushed message," raising the question of how that claimed architecture maps onto today's platform-based notification services.
- Technical Questions: The infringement theory hinges on the accused app performing a specific multi-step data synchronization process, including a second request that is "automatically generated by the handheld device" (’844 Patent, col. 26:12-14). A key technical question will be what evidence demonstrates that the State Farm App performs this specific sequence, as opposed to a more generic background refresh or data update triggered by a standard operating system notification.
V. Key Claim Terms for Construction
The Term: "unsolicited pushed messages" (from ’395 Patent, Claim 1)
- Context and Importance: This term is fundamental to the patents' novelty, distinguishing the invention from user-initiated data requests. The definition will be critical to determining whether modern mobile app notifications, which are often triggered by server-side events but delivered through a platform intermediary, qualify as "unsolicited" in the manner contemplated by the 1998-era invention.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification describes these messages as a way to "selectively generate... an unsolicited push message... to notify the user of relevant results" (’395 Patent, Abstract). This could support a broad reading that covers any server-initiated notification of new content, regardless of the underlying delivery mechanism.
- Evidence for a Narrower Interpretation: The patent explains the message is generated "when the user enters a geographical area where the search is satisfied" (’395 Patent, Abstract). This context suggests the term may be limited to messages triggered specifically by a change in the user's geographic location meeting a pre-defined interest, potentially narrowing its scope relative to general-purpose app notifications.
The Term: "without the need to continuously maintain an active user-interactive client-server application layer session" (from ’395 Patent, Claim 1; ’844 Patent, Claim 1)
- Context and Importance: This limitation defines the efficiency of the push notification system. Its construction will determine whether the accused system, which relies on modern mobile operating systems that manage background connections, operates "without" such a session as the term is used in the patent.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent incorporates by reference a co-pending application describing "virtual sessions," where a physical connection is "only establishes the cellular connection when it is actually being used for network communications" (’395 Patent, col. 2:15-18). This could support a reading that any system not requiring a persistent, always-on application-layer link for notifications meets this limitation.
- Evidence for a Narrower Interpretation: The phrase "user-interactive" could be interpreted to mean a session actively managed by a foreground application with an engaged user. This might allow a defendant to argue that persistent background connections managed by the mobile operating system for push services are a different type of "session" not contemplated by the claim.
The Term: "a second request... which is automatically generated by the handheld device" (from ’844 Patent, Claim 25)
- Context and Importance: This term is central to the alleged infringement method. The dispute will likely focus on whether the accused app's behavior after receiving a notification—such as a background data refresh—constitutes an "automatically generated" request as required by the claim.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim language does not specify the mechanism of automation, only that it is generated "without requiring user action" (’844 Patent, col. 26:13-14). This could support an interpretation that any software-initiated data pull following a notification, whether by the app itself or the underlying OS, meets this element.
- Evidence for a Narrower Interpretation: The patent's context is a "geographical web browser" where content is updated based on location. This could support an argument that the "automatic" generation must be directly and specifically tied to the content of the push notification itself, rather than being part of a routine, scheduled, or general-purpose background refresh process common in modern apps.
VI. Other Allegations
- Indirect Infringement: The complaint does not plead a separate count for indirect infringement. It makes general allegations that State Farm is "providing and/or causing to be used" the infringing products (Compl. ¶78, ¶99). However, the complaint does not provide sufficient detail for analysis of the specific knowledge and intent elements required for induced or contributory infringement.
- Willful Infringement: The complaint alleges that Defendant has had knowledge of the patents and its infringement "since at least the filing of the Original Complaint in this action, or shortly thereafter" (Compl. ¶65). This allegation appears to form the basis for a claim of post-suit willfulness only, as no facts supporting pre-suit knowledge are alleged.
VII. Analyst’s Conclusion: Key Questions for the Case
- A core issue will be one of definitional scope: can the claim term "unsolicited pushed messages," conceived in the context of 1998 technology, be construed to cover notifications delivered through modern, intermediary-based mobile operating system platforms like Apple's APNS and Google's FCM? The outcome may depend on whether the court focuses on the server-initiated nature of the notification or the specific client-server architecture described.
- A second key issue will be one of technical operation: does the State Farm App’s method for updating content after receiving a notification constitute the specific, multi-step sequence recited in claims like claim 25 of the ’844 Patent? The case may turn on evidence showing whether the app generates a distinct "second request" that is "automatically generated" in direct response to the notification, or whether it performs a more generic background data synchronization that is not functionally equivalent to the claimed method.
Analysis metadata