4:23-cv-01117
Push Data LLC v. Citibank NA
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Push Data LLC (Delaware)
- Defendant: Citibank N.A. (National Banking Association)
- Plaintiff’s Counsel: Beaty Legal PLLC
- Case Identification: 4:23-cv-01117, E.D. Tex., 12/20/2023
- Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant maintains established places of business within the district, including a specific location in Plano, Texas.
- Core Dispute: Plaintiff alleges that Defendant’s Citibank mobile applications infringe three expired patents related to using a device's geographical location and user preferences to deliver targeted push notifications and other information.
- Technical Context: The technology concerns systems and methods for a "geographical web browser," a foundational concept for modern location-aware mobile applications that provide context-specific content to users.
- Key Procedural History: The complaint states that all three patents-in-suit descend from a common patent application filed in 1998 and expired in 2018. The lawsuit, filed in 2023, therefore seeks only past damages for alleged infringement that occurred before the patents expired. No prior litigation, licensing, or administrative patent challenges are mentioned in the complaint.
Case Timeline
| Date | Event |
|---|---|
| 1998-11-17 | Earliest Priority Date for ’395, ’844, and ’811 Patents |
| 2006-06-06 | ’395 Patent Issued |
| 2007-05-01 | ’811 Patent Issued |
| 2007-11-06 | ’844 Patent Issued |
| 2011-09-22 | Accused "Citi Mobile®" App Released |
| 2018-11-17 | Approximate Expiration Date for ’395, ’844, and ’811 Patents |
| 2023-12-20 | 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"
- Patent Identification: U.S. Patent No. 7,058,395, "GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS," issued June 6, 2006 (Compl. ¶68).
The Invention Explained
- Problem Addressed: At the time of the invention, mobile users had to manually navigate applications to find information specific to their local area; no technology existed to automatically control a network application by selectively filtering locally broadcast information (Compl. ¶14; ’395 Patent, col. 2:50-64).
- The Patented Solution: The patent describes a system where a mobile device maintains a primary network connection (e.g., cellular) while also using an auxiliary channel (e.g., local radio broadcasts or GPS) to receive location-relevant data (Compl. ¶18; ’395 Patent, Abstract). A "packet filter" on the device selectively processes this local data to control information flow on the primary connection, allowing an application like a web browser to automatically display content pertinent to the user's physical location without continuous manual input (’395 Patent, col. 4:25-44; Fig. 1).
- Technical Importance: The invention conceptualized a framework for location-based services before the ubiquity of modern smartphones, anticipating how mobile applications would leverage device location to provide context-aware content (Compl. ¶12-13, ¶47).
Key Claims at a Glance
- The complaint asserts at least claims 4 and 22, with claim 4 depending from independent claim 1 (’395 Patent, Claim 1, 4; Compl. ¶88). Claim 22 is also independent.
- The essential elements of independent claim 1 include:
- Receiving a user interest indication.
- Receiving a location indication for the mobile unit via a packet switched data network.
- Identifying an information item that comports with the user interest and is associated with the identified location.
- Causing information about that item to be sent to a wireless packet access station, which then transmits it to the mobile unit via one or more "unsolicited pushed messages."
- Performing these steps without continuously maintaining an active user-interactive client-server session.
- The complaint’s use of "at least" suggests it may assert other claims, including dependent claims, as the case proceeds (Compl. ¶88).
U.S. Patent No. 7,292,844 - "GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS"
- Patent Identification: U.S. Patent No. 7,292,844, "GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS," issued November 6, 2007 (Compl. ¶91).
The Invention Explained
- Problem Addressed: As a member of the same patent family, the ’844 Patent addresses the same technical problem as the ’395 Patent: the lack of systems to automatically provide location-relevant information to a mobile device by filtering data based on geography (Compl. p. 3, fn. 1; ’844 Patent, col. 2:50-64).
- The Patented Solution: The ’844 Patent similarly discloses a system where a mobile unit receives location-specific information. The claims focus on a specific push notification method where a message containing an application identifier is sent to the device, notifying the user of available content and allowing the user to initiate a download of that content, thereby reactivating a network session (’844 Patent, Abstract; col. 4:25-30).
- Technical Importance: This patent provides an alternative embodiment of the location-based service framework, detailing a specific client-server interaction model for delivering context-aware notifications (Compl. ¶46).
Key Claims at a Glance
- The complaint asserts independent claims 1, 25, 32, 37, and 46 (Compl. ¶111).
- The essential elements of independent claim 1 include:
- Causing a "communication push message" to be wirelessly transmitted to a mobile unit, which includes an application-identifying field and information about content available for download.
- This push message is explicitly defined as not being a server response sent via a user-interactive session and "not sent in response to a client request message."
- Receiving a "client-request packet" from the mobile unit after a user makes a selection.
- Sending the further content to the mobile unit in response to that client-request packet.
U.S. Patent No. 7,212,811 - "GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS"
- Patent Identification: U.S. Patent No. 7,212,811, "GEOGRAPHICAL WEB BROWSER, METHODS, APPARATUS AND SYSTEMS," issued May 1, 2007 (Compl. ¶114).
Technology Synopsis
Belonging to the same family as the other asserted patents, the ’811 Patent addresses the problem of enabling mobile devices to automatically access location-specific content. The invention provides for a system where a mobile unit's geographical position, determined by GPS or local network data, is used to control information flow over a primary network connection, thereby creating a "geographical web browser" (’811 Patent, Abstract; Compl. ¶14, ¶18).
Asserted Claims
The complaint asserts at least independent claim 5 (Compl. ¶130, ¶134).
Accused Features
The complaint alleges infringement by the Citibank App's backend system, which allegedly receives a first request from the app, responds with the availability of content, receives a second automatically generated request, and then delivers the content. This process is alleged to occur in an environment with access to at least two wireless networks, such as cellular and WiFi (Compl. ¶128-129).
III. The Accused Instrumentality
Product Identification
The "Accused Instrumentalities" are identified as "at least the Citibank application as developed for mobile electronic devices," available on both Apple and Android platforms (Compl. ¶66, ¶78).
Functionality and Market Context
- The complaint alleges, on information and belief, that the accused apps engage in a specific multi-step communication method with a remote server. This method involves: (1) the server receiving a first request from the app; (2) the server responding that content is available; (3) the server receiving a second, "automatically generated" request from the app; and (4) the server coupling the content to the app (Compl. ¶82, ¶105, ¶128). This process is alleged to operate over an environment with at least two wireless networks, such as cellular and WiFi (Compl. ¶83, ¶106, ¶129).
- The complaint asserts that the primary "Citi Mobile®" application has been downloaded over 10 million times from the Google Play store, as shown in a provided screenshot (Compl. p. 20). Screenshots also identify other accused apps, such as "Live Well at Citi," which was released in October 2013 (Compl. p. 19, ¶81). Plaintiff alleges that the patented technologies have "significant commercial value" (Compl. ¶62).
IV. Analysis of Infringement Allegations
The complaint references infringement analysis in Exhibits D, E, and F, but these exhibits were not provided with the complaint. The narrative infringement theory is summarized below in prose.
’395 and ’844 Patent Infringement Allegations
Plaintiff's infringement theory, which is stated identically for all three asserted patents, alleges that the Accused Instrumentalities perform a method that maps to the patent claims (Compl. ¶82-83, ¶105-106). The core of the allegation is a four-step client-server interaction: a first request from the mobile device, a response from the server indicating content availability, a second and automatically generated request from the device to pull the content, and the server's subsequent delivery of that content (Compl. ¶82). This entire process is alleged to occur in a multi-network environment (e.g., cellular and WiFi) (Compl. ¶83). A screenshot of the "Citi Mobile®" app in the Google Play store is provided as evidence of the accused product's existence and market presence (Compl. p. 20).
Identified Points of Contention
- Scope Questions: A primary question may be whether the complaint's description of a request-response (pull) model can satisfy claim limitations requiring "unsolicited pushed messages" (’395 Patent, Claim 1) or a message explicitly "not sent in response to a client request" (’844 Patent, Claim 1). The defendant may argue that any notification sent from its server is, by definition, a response to some form of client request, such as a background refresh poll.
- Technical Questions: The complaint's infringement theory hinges on the allegation that the accused app generates a "second request...which is automatically generated by the handheld device" (Compl. ¶82). A key factual dispute may be whether this specific mechanism exists as described, or if the app's communication protocol operates differently. The complaint does not provide technical evidence to support this specific allegation beyond "information and belief."
V. Key Claim Terms for Construction
"unsolicited pushed messages" (’395 Patent, Claim 1)
Context and Importance
The distinction between "pushed" and "pulled" data is central. The infringement theory describes a multi-step request-response interaction (Compl. ¶82). The viability of the infringement claim will depend on whether this interaction can be construed as involving an "unsolicited pushed message." Practitioners may focus on this term because it appears to be a point of mismatch between the claim language and the alleged functionality.
Intrinsic Evidence for Interpretation
- Evidence for a Broader Interpretation: The specification discusses "unsolicited pushed information packets which could trigger, for example, downloading of related information from the Internet" (’395 Patent, col. 4:9-13). This could support an argument that a notification that prompts or triggers a subsequent download request from the app falls within the scope of a "pushed message."
- Evidence for a Narrower Interpretation: The specification also describes push messages as being sent "without the need to maintain an active user-interactive client-server application layer at all times" (’395 Patent, col. 23:31-37). A defendant could argue that a message sent in the context of an app's active or background polling process is not "unsolicited."
"communication push message...is not...sent in response to a client request message" (’844 Patent, Claim 1)
Context and Importance
This negative limitation is critical. To prove infringement, Plaintiff must demonstrate that the accused notification is not a response to a client request. Defendant will likely argue that any notifications sent by its servers are responses to periodic background requests from the mobile app for updated information.
Intrinsic Evidence for Interpretation
- Evidence for a Broader Interpretation: The patent distinguishes its invention from conventional web browsing, where every piece of server content is a direct response to a user-initiated request. Language about reactivating a dormant "virtual session" upon receipt of a push message may support an argument that such a message is not a "response" in the context of an active, ongoing dialogue (’844 Patent, col. 10:34-64).
- Evidence for a Narrower Interpretation: The plain language of the claim explicitly excludes messages sent "in response to a client request message." If the Citibank app is shown to periodically poll the server for new data, any resulting notification from the server could be characterized as a direct "response" to that polling request, potentially placing it outside the claim's scope.
VI. Other Allegations
Indirect Infringement
The complaint does not plead specific facts to support claims of induced or contributory infringement, focusing instead on allegations of direct infringement by Defendant (Compl. ¶78, ¶101, ¶124).
Willful Infringement
The complaint alleges that Defendant has had knowledge of the patents-in-suit "since at least the filing of the Original Complaint in this action" (Compl. ¶65). This allegation, if proven, could support a claim for willful infringement based on post-suit conduct but does not allege any pre-suit knowledge.
VII. Analyst’s Conclusion: Key Questions for the Case
- A core issue will be one of functional and definitional scope: Can the communication protocol alleged in the complaint—a multi-step, pull-based interaction—be construed to meet claim limitations requiring an "unsolicited pushed message" or a message explicitly "not sent in response to a client request"? The resolution will depend on both claim construction and a technical analysis of how the accused Citibank applications actually communicate with their servers.
- A key evidentiary question will be one of technical proof: The complaint's infringement allegations are made "upon information and belief" and describe a specific backend process involving an "automatically generated" second request. A central challenge for the Plaintiff will be to obtain discovery that substantiates this specific technical assertion, which forms the factual basis of its infringement theory.