DCT
4:25-cv-09558
Google LLC v. Headwater Research LLC
Key Events
Amended Complaint
Table of Contents
complaint Intelligence
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Google LLC (Delaware)
- Defendant: Headwater Research LLC (Texas)
- Plaintiff’s Counsel: Paul Hastings LLP
- Case Identification: 4:25-cv-09558, N.D. Cal., 09/11/2026
- Venue Allegations: Plaintiff Google alleges venue is proper in the Northern District of California because Defendant Headwater has availed itself of the district by, among other things, engaging in licensing negotiations with California residents, suing other entities for patent infringement in the district, and having inventors and prosecuting attorneys for the patents-in-suit based in the district.
- Core Dispute: Plaintiff Google seeks a declaratory judgment that its Android software features—specifically Battery Saver, Doze Mode, App Standby, and Data Saver—do not infringe two of Defendant Headwater’s patents related to on-device management of network traffic.
- Technical Context: The patents-in-suit relate to device-assisted services for managing data consumption on wireless devices to protect network capacity, a critical technology in an era of widespread smartphone use and mobile data consumption.
- Key Procedural History: This declaratory judgment action follows Headwater's assertion of the patents-in-suit against major wireless carriers, in which Headwater accused Google's Android features. Google and other carriers have petitioned for inter partes review (IPR) of U.S. Patent No. 8,589,541. In response to one IPR, Headwater disclaimed numerous claims of the '541 patent. In two other IPRs, the Patent Trial and Appeal Board (PTAB) instituted review and found a significant number of the '541 patent's claims to be unpatentable.
Case Timeline
| Date | Event |
|---|---|
| 2008-09-01 | Android v. 1.0 (with SyncAdapter and SyncManager) released |
| 2009-01-28 | Earliest Priority Date for the '541 Patent and U.S. Patent No. 9,215,613 |
| 2009-09-01 | Android v. 1.6 released |
| 2013-11-19 | U.S. Patent No. 8,589,541 Issues |
| 2015-12-15 | U.S. Patent No. 9,215,613 Issues |
| 2024-06-04 | Google and others petition for IPR of the '541 patent |
| 2024-09-17 | Headwater disclaims numerous claims of the '541 patent in IPR |
| 2025-10-01 | PTAB finds numerous claims of the '541 patent unpatentable in IPRs |
| 2026-09-11 | Google files First Amended Complaint for Declaratory Judgment |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 8,589,541 - “Device-Assisted Services for Protecting Network Capacity”
- Patent Identification: U.S. Patent No. 8,589,541, “Device-Assisted Services for Protecting Network Capacity,” issued November 19, 2013.
The Invention Explained
- Problem Addressed: The patent describes a "network capacity crunch" driven by the increasing popularity of smart mobile devices that were not fully optimized to preserve network resources, leading to network congestion and degraded performance for users '541 Patent, col. 10:57-65 '541 Patent, col. 11:4-15
- The Patented Solution: The invention proposes an on-device software agent or "service processor" that identifies network "service usage activity," determines if an activity is occurring in the "background," and applies a "policy" to control that background activity '541 Patent, abstract This control can be based on user input or instructions from a network element, allowing for granular management of application traffic to conserve network resources '541 Patent, abstract '541 Patent, Fig. 3
- Technical Importance: This device-assisted approach provided a mechanism for managing network demand at the source—the mobile device itself—offering a more granular and potentially more efficient alternative to purely network-based traffic management solutions '541 Patent, col. 15:40-52
Key Claims at a Glance
- The complaint seeks a declaratory judgment of noninfringement with respect to claims of the '541 patent that have not been disclaimed, specifically referencing dependent Claim 79, which incorporates independent Claim 1 Compl. ¶59
- The essential elements of independent Claim 1, a non-transitory computer-readable medium, include instructions for a processor to:
- identify a service usage activity of the wireless end-user device, the service usage activity being associated with a first software component...the service usage activity comprising one or more prospective or successful communications over a wireless network;
- determine whether the service usage activity comprises a background activity;
- determine at least an aspect of a policy based on a user input obtained through a user interface of the wireless end-user device or based on information from a network element, the policy to be applied if the service usage activity is the background activity, the policy at least for controlling the service usage activity; and
- if it is determined that the service usage activity is the background activity, apply the policy.
- The complaint notes that dependent Claim 79 further requires that applying the policy comprises assisting in "intercepting a stack application programming interface (API) level or application messaging layer request" Compl. ¶59
U.S. Patent No. 9,215,613 - “Wireless End-User Device with Differential Traffic Control Policy List Having Limited User Control”
- Patent Identification: U.S. Patent No. 9,215,613, “Wireless End-User Device with Differential Traffic Control Policy List Having Limited User Control,” issued December 15, 2015.
The Invention Explained
- Problem Addressed: As with its parent patent, the '613 patent addresses the challenge of managing network traffic from various applications on a mobile device, particularly in light of differing network conditions (e.g., WWAN vs. WLAN) and user interaction states (e.g., foreground vs. background) '613 Patent, col. 3:6-14
- The Patented Solution: The invention is a wireless device with both WWAN and WLAN modems that stores a "differential traffic control policy list" distinguishing between a first set of applications and a second set '613 Patent, abstract The device's processors classify the network type and whether an application is in the "user interface foreground," and then selectively allow or deny network access based on the policy list '613 Patent, abstract Crucially, the patent describes an interface that allows a user to "augment" the policy for the first set of applications but not for the second set '613 Patent, col. 2:5-9
- Technical Importance: This technology provides for a more sophisticated on-device policy engine that differentiates control based on network type and application state, while introducing a nuanced level of limited user control over those policies '613 Patent, col. 4:18-29
Key Claims at a Glance
- The complaint seeks a declaratory judgment of noninfringement with respect to claims of the '613 patent, specifically referencing independent Claim 1 and dependent Claim 12 Compl. ¶¶65-66
- The essential elements of independent Claim 1, a wireless end-user device, include:
- A wireless wide area network (WWAN) modem and a wireless local area network (WLAN) modem;
- A non-transient memory to store a differential traffic control policy list distinguishing between a first one or more applications and a second one or more applications and/or services;
- An interface to allow a user to augment the differential traffic control policy for the first one or more applications but not for the second one or more applications and/or services; and
- One or more processors configured to: classify the wireless network type; classify whether a particular application is interacting with the user in the device user interface foreground; and selectively allow or deny Internet service activities based on the application's membership in the first set of applications, the policy, any user augmentation, and the classifications.
III. The Accused Instrumentality
Product Identification
- The complaint identifies the accused instrumentalities as Google devices such as phones, tablets, and wearables that use certain Android software features: "Battery Saver, Doze Mode, App Standby, and Data Saver," collectively referred to as the "Android Features at Issue" Compl. ¶2
Functionality and Market Context
- The complaint alleges that Headwater has accused these specific Android features of infringing the patents-in-suit in separate lawsuits filed against wireless carriers Compl. ¶2
- The complaint provides minimal technical detail on the functionality of the accused Android features, asserting instead that they were developed by Google and do not infringe the patents-in-suit Compl. ¶¶45-48 Compl. ¶55 The names of the features suggest functionalities for conserving battery life and data usage, which often involves managing or restricting network access for certain applications.
- The complaint does not provide sufficient detail for a full analysis of the accused features' operation.
IV. Analysis of Infringement Allegations
No probative visual evidence provided in complaint.
This is a declaratory judgment action, where the "infringement allegations" are Google's assertions of non-infringement.
'541 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Non-Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| identify a service usage activity of the wireless end-user device, the service usage activity being associated with a first software component...the service usage activity comprising one or more prospective or successful communications... | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶59 | col. 110:15-23 |
| determine whether the service usage activity comprises a background activity | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶59 | col. 110:24-25 |
| determine at least an aspect of a policy based on a user input...or based on information from a network element, the policy to be applied if the service usage activity is the background activity... | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶59 | col. 110:26-34 |
| and if it is determined that the service usage activity is the background activity, apply the policy. | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶59 | col. 110:35-37 |
- Identified Points of Contention:
- Technical Questions: The central dispute will be factual and technical: Do the accused Android features, such as "Doze Mode" or "Data Saver," actually perform the specific sequence of identifying a service activity, determining it is a background activity, determining a policy, and then applying that policy as claimed? The complaint's blanket denial suggests Google will argue that its features operate via a different, non-infringing technical mechanism.
- Scope Questions: A likely point of contention will be the scope of the term "background activity." The parties may dispute whether the Android system's classification of application states (e.g., active, idle, standby) maps onto the definition of "background activity" as contemplated by the patent.
'613 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Non-Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| a differential traffic control policy applicable to at least some Internet service activities by or on behalf of the first one or more applications | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶66 | col. 106:14-16 |
| an interface to allow a user to augment the differential traffic control policy for the first one or more applications but not for the second one or more applications and/or services | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶66 | col. 106:17-21 |
| classify a wireless network to which the device currently connects...as at least one of a plurality of network types that the device can connect with | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶66 | col. 106:23-27 |
| classify whether a particular application...is interacting with the user in the device user interface foreground | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶66 | col. 106:28-35 |
| receive an update to at least a portion of the differential traffic control policy list from a network element. (from dependent claim 12) | The complaint asserts that Google devices using the Android Features at Issue do not meet this limitation. | ¶66 | col. 107:1-3 |
- Identified Points of Contention:
- Technical Questions: A key question will be whether the user-facing controls in Android for features like "Data Saver" constitute the claimed "interface to allow a user to augment the...policy for the first one or more applications but not for the second." This raises a question of how granular and differentiated the user controls are in the accused Android features.
- Scope Questions: The dispute may turn on whether the Android OS's method of distinguishing between active and inactive apps is equivalent to the claimed step of classifying whether an application is "interacting with the user in the device user interface foreground."
V. Key Claim Terms for Construction
"background activity" ('541 Patent, Claim 1)
- Context and Importance: This term is the trigger for applying the claimed policy. Its definition is critical to determining whether the accused Android features perform the claimed method, as their primary function is to manage applications that are not in active use.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification suggests a broad meaning, describing background activity as occurring "even when the user is not directly interacting with or benefiting from this type of application" '541 Patent, col. 43:45-52 This could be interpreted to include any network communication not resulting from immediate, direct user input.
- Evidence for a Narrower Interpretation: The specification also provides a list of specific examples of background activities, including "update widgets on a desktop; synchronize user data such as calendars, contacts, email...; check or update email or RSS feeds; access social networking websites" '541 Patent, col. 43:38-42 A party could argue these examples limit the term's scope to similar types of automated or periodic data synchronization tasks.
"interacting with the user in the device user interface foreground" ('613 Patent, Claim 1)
- Context and Importance: This classification step is the primary distinction the claimed device makes to decide whether to apply the traffic control policy. The entire infringement analysis for this patent may hinge on whether an application is deemed to be "interacting" in its foreground state.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim language itself, which contrasts this state with "at least some Internet service activities when not interacting with the user in the device user interface foreground," suggests a binary distinction '613 Patent, col. 106:30-35 This may support an interpretation where any application that is visible and active on the screen is "interacting," regardless of specific user input.
- Evidence for a Narrower Interpretation: Practitioners may focus on the word "interacting," arguing it requires more than mere visibility. The patent does not explicitly define the term, but a defendant could argue that "interacting" implies active user input, such as tapping, typing, or scrolling, and that an application merely displayed on the screen without such input is not "interacting" as required by the claim.
VI. Other Allegations
Indirect Infringement
- Google seeks a declaratory judgment that it does not induce or contributorily infringe the patents-in-suit Compl., Prayer for Relief B Compl., Prayer for Relief C Google bases this on the alleged absence of any underlying direct infringement by users of its devices and further alleges it has not acted with the specific intent for inducement or knowledge for contributory infringement Compl. ¶60 Compl. ¶66 The complaint notes that Headwater has accused Google of inducement in other related lawsuits, establishing a controversy on this issue Compl. ¶6
Willful Infringement
- As this is a declaratory judgment action by the accused infringer, willfulness is not alleged by the plaintiff. However, Google does ask the court for a finding that this is an "exceptional case" under 35 U.S.C. § 285, which would entitle Google to an award of attorneys' fees Compl., Prayer for Relief E This request is likely based on the extensive litigation history and the adverse IPR rulings against the '541 patent.
VII. Analyst’s Conclusion: Key Questions for the Case
- Impact of Parallel Proceedings: With the PTAB having found a substantial number of the '541 patent’s claims unpatentable, a primary question is whether any viable infringement theory for that patent remains. The case may turn on how the district court action is affected by the IPR outcomes, which could potentially moot or significantly narrow the dispute over the '541 patent.
- Definitional Scope: A core issue will be one of claim construction. The viability of Headwater's potential infringement claims will depend on whether key terms like "background activity" ('541 patent) and "interacting with the user" ('613 patent) are construed broadly enough to read on the operation of the accused Android features.
- Functional Equivalence: A key evidentiary question will be one of technical operation. Does the evidence show that Android's "Doze Mode" and "Data Saver" features perform the specific, multi-step logical processes of identifying, classifying, and applying policies as recited in the claims, or is there a fundamental mismatch in their technical implementation compared to the patented methods?
Analysis metadata