Headwater Research LLC v. Google LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Headwater Research LLC (Texas)
  • Defendant: Google LLC (Delaware)
  • Plaintiff's Counsel: Russ August & Kabat
• Case Identification: 7:25-cv-00369, W.D. Tex., 12/08/2025
• Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Google resides in the district and has a regular and established place of business, citing a corporate office and a retail store in Austin, Texas.
• Core Dispute: Plaintiff alleges that Defendant's mobile electronic devices, cellular networks, and Google Fi service infringe seven U.S. patents related to mobile device management, provisioning, security, and activation.
• Technical Context: The technology addresses the management of mobile device services, data usage, and network access in an environment characterized by rapidly increasing mobile data consumption.
• Key Procedural History: The complaint alleges that Google had pre-suit knowledge of the asserted patents through extensive prior litigation involving the same or related patents. These include lawsuits filed by Headwater against Samsung (a Google Android partner) and major wireless carriers like Verizon, T-Mobile, and AT&T (who sell Google's devices). The complaint notes jury verdicts against Samsung and alleges Google participated in these prior cases. It also alleges Samsung filed inter partes review (IPR) petitions against U.S. Patent Nos. 9,609,510 and 11,405,429.

Case Timeline

Date	Event
2008-01-01	Dr. Raleigh forms Headwater to develop mobile operating systems and cloud technology.
2009-01-28	Earliest Priority Date for '935, '510, '930, '055, '429, '464, and '155 Patents.
2011-01-01	Plaintiff Headwater Research LLC is formed.
2014-01-28	U.S. Patent No. 8,639,935 Issues.
2017-03-28	U.S. Patent No. 9,609,510 Issues.
2018-05-15	U.S. Patent No. 9,973,930 Issues.
2021-08-17	U.S. Patent No. 11,096,055 Issues.
2022-08-02	U.S. Patent No. 11,405,429 Issues.
2024-04-01	Headwater serves its complaint against Samsung in the '228 Case.
2024-04-23	U.S. Patent No. 11,966,464 Issues.
2024-05-14	U.S. Patent No. 11,985,155 Issues.
2024-07-01	Headwater serves preliminary contentions against Samsung in the '228 Case.
2025-02-01	Headwater serves complaints against Verizon, T-Mobile, and AT&T.
2025-04-01	Jury returns a verdict in the '103 Case against Samsung.
2025-05-01	Headwater serves preliminary contentions in cases against carriers.
2025-07-01	Jury returns a verdict in the '352 Case.
2025-12-08	Complaint Filing Date.

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

U.S. Patent No. 8,639,935 - Automated device provisioning and activation

• Issued: January 28, 2014.

The Invention Explained

• Problem Addressed: The patents address problems arising from the rapid growth in mobile data demand, focusing on improving end-user wireless devices and the services that support them Compl. ¶10 Compl. ¶¶12-14 This includes challenges in how wireless services are provided to consumers and the need to manage device activation and provisioning efficiently Compl. ¶10 '055 Patent, col. 1:21-41
• The Patented Solution: The invention provides a system for managing device services through a combination of on-device software agents (a "Service Processor") and network-based servers (a "Service Controller") Compl. ¶15 '055 Patent, FIG. 16 This architecture allows for automated device provisioning and activation by having the device store credentials and send access requests to the network, which then enables and configures services according to predefined policies '055 Patent, abstract '055 Patent, FIG. 43A
• Technical Importance: This approach laid the groundwork for technologies that help device manufacturers and wireless carriers manage data usage, reduce network congestion, and extend battery life, enabling more flexible and cost-effective service models Compl. ¶16

Key Claims at a Glance

• The complaint asserts infringement of at least independent claim 1 of the '935 patent Compl. ¶50
• The complaint does not provide the full text of the asserted claims, precluding a detailed breakdown of claim elements.

U.S. Patent No. 9,609,510 - Automated Credential Porting For Mobile Devices

• Issued: March 28, 2017.

The Invention Explained

• Problem Addressed: The technology addresses the need to seamlessly transfer a user's service credentials when they switch to a new mobile device, which is a significant point of friction for consumers and carriers Compl. ¶10 Compl. ¶12
• The Patented Solution: The invention describes a method for automatically porting credentials for mobile devices. This likely involves the device and network coordinating to transfer service entitlements, policies, and identifiers (like a phone number) from a user's old device or service to a new one, a process particularly relevant for technologies like eSIM Compl. ¶2
• Technical Importance: Automating credential porting is critical for simplifying the device upgrade and carrier switching process, improving the user experience, and reducing operational costs for service providers Compl. ¶15

Key Claims at a Glance

• The complaint asserts infringement of at least independent claim 1 of the '510 patent Compl. ¶62
• The complaint does not provide the full text of the asserted claims, precluding a detailed breakdown of claim elements.

U.S. Patent No. 9,973,930 - End user device that secures an association of application to service policy with an application certificate check

• Issued: May 15, 2018 Compl. ¶32
• Technology Synopsis: The patent describes a security mechanism on an end-user device. It secures the link between a specific software application and its governing service policy by using a certificate check, which likely verifies the application's authenticity before applying specific data usage or access rules Compl. ¶32
• Asserted Claims: At least claim 1 is asserted Compl. ¶74
• Accused Features: The accused features are functionalities within Google's mobile devices and operating systems that manage application-specific policies Compl. ¶74

U.S. Patent No. 11,096,055 - Automated device provisioning and activation

• Issued: August 17, 2021 Compl. ¶33
• Technology Synopsis: Continuing the theme of the '935 patent, this invention covers the automated provisioning and activation of devices. It describes a system where a device uses stored credentials to request and activate services on a network, managed by a "Service Processor" on the device and a "Service Controller" in the network '055 Patent, abstract '055 Patent, FIG. 16
• Asserted Claims: At least claim 1 is asserted Compl. ¶86
• Accused Features: The accused features are related to the provisioning and activation processes for Google's devices and services, such as Google Fi Compl. ¶86

U.S. Patent No. 11,405,429 - Security techniques for device assisted services

• Issued: August 2, 2022 Compl. ¶34
• Technology Synopsis: This patent discloses security techniques for services that are managed or assisted by the device itself. The invention describes creating secure execution environments on a device to protect the integrity of service policy enforcement and monitoring agents from tampering '429 Patent, abstract '429 Patent, FIG. 1
• Asserted Claims: At least claim 1 is asserted Compl. ¶98
• Accused Features: The accused features involve security architectures within Google's Android operating system and devices that manage device-assisted services Compl. ¶98

U.S. Patent No. 11,966,464 - Security techniques for device assisted services

• Issued: April 23, 2024 Compl. ¶35
• Technology Synopsis: As a continuation of the '429 patent, this invention further details security techniques for device-assisted services. It likely elaborates on methods for creating and maintaining secure partitions on a device's processor to ensure service policies are enforced reliably '464 Patent, abstract
• Asserted Claims: At least claim 1 is asserted Compl. ¶110
• Accused Features: The accused features are security functionalities within Google's devices and the Android operating system that pertain to device-assisted services Compl. ¶110

U.S. Patent No. 11,985,155 - Communications device with secure data path processing agents

• Issued: May 14, 2024 Compl. ¶117
• Technology Synopsis: The patent describes a communications device that uses secure agents to process data within a protected data path. This ensures that service usage is securely monitored and reported, and that service policies are enforced correctly, by creating a trusted path for data between the device's applications and the network modem '155 Patent, abstract
• Asserted Claims: At least claim 1 is asserted Compl. ¶122
• Accused Features: The accused features are the systems and methods within Google's devices and operating system for managing the flow of data for network access Compl. ¶122

III. The Accused Instrumentality

Product Identification

The Accused Instrumentalities are identified as Google's mobile electronic devices (e.g., phones and tablets), cellular networks, servers, services, and eSIM-enabled devices that operate on Google's network, including its mobile virtual network operator (MVNO) service, Google Fi Compl. ¶2 Compl. ¶38

Functionality and Market Context

The complaint alleges that the accused products provide mobile connectivity and data services, which have seen explosive growth in demand since 2011 Compl. ¶¶12-13 The complaint includes a chart illustrating the significant historical and projected growth in mobile data traffic to underscore the market importance of the technologies at issue Compl. p. 6 The core of the infringement allegations centers on the functionality of the Android operating system and back-end services like Google Fi, which together manage device provisioning, activation, and enforcement of service policies Compl. ¶20 Compl. ¶21

IV. Analysis of Infringement Allegations

The complaint references claim-chart exhibits that were not provided with the complaint document. Accordingly, the infringement allegations are summarized below in prose, and claim-chart tables are omitted.

'935 Patent Infringement Allegations

The complaint alleges that Google's products and services directly and indirectly infringe the '935 patent, which is directed to "Automated device provisioning and activation" Compl. ¶45 Compl. ¶49 The infringement theory, detailed in the unprovided Exhibit 8, appears to be that the process by which Google's devices (running Android and using services like Google Fi) are activated and configured for network service meets the elements of claim 1 of the '935 patent Compl. ¶50

'510 Patent Infringement Allegations

The complaint alleges that Google's products, particularly eSIM-enabled devices and services like Google Fi, infringe the '510 patent, titled "Automated Credential Porting For Mobile Devices" Compl. ¶57 Compl. ¶61 The infringement theory, contained in the unprovided Exhibit 9, likely maps the elements of claim 1 to the functionality within Google's ecosystem that allows users to transfer their service credentials and phone number to new or different devices Compl. ¶62

Identified Points of Contention

• Scope Questions: A central question for the court may be whether the terms used in the patents, such as "service processor" and "service controller", can be construed to read on Google's distributed, cloud-based architecture. The patents describe a specific client-server model '055 Patent, FIG. 16, and a potential dispute is whether the disparate components of the Android OS and Google's cloud services collectively perform the functions of the claimed "service processor" and "service controller", respectively.
• Technical Questions: The complaint makes broad allegations about "provisioning," "activation," and "credential porting" but provides little technical detail on how Google's products actually perform these functions Compl. ¶49 Compl. ¶50 A key technical question will be what evidence Plaintiff can produce in discovery to show that the accused Android and Google Fi systems practice the specific steps and sequences required by the asserted claims.

V. Key Claim Terms for Construction

Because the full asserted claims are not provided in the complaint, this analysis is based on recurring terms from the patent titles and the specification of the related '055 patent.

The Term: "service processor"

• Context and Importance: This term appears central to the patented system, referring to the on-device componentry that enforces policies. Its construction will be critical because the infringement case may depend on whether components of the Android operating system and Google apps meet the definition. Practitioners may focus on this term to determine if it requires a single, integrated software agent as depicted in some figures, or if it can cover a collection of disparate processes.
• Intrinsic Evidence for a Broader Interpretation: The specification of the related '055 patent describes the "Service Processor" as an embodiment that includes a collection of distinct functional agents, such as a "Policy Control Agent" and a "Billing Agent" '055 Patent, FIG. 22A This could support an interpretation where the term covers any collection of software on the device that performs these functions.
• Evidence for a Narrower Interpretation: Figures in the '055 patent depict the "Service Processor 115" as a discrete, defined block of components operating within the device architecture '055 Patent, FIG. 16 This could support a narrower construction requiring a more integrated and distinct software module than simply the general functionalities of an operating system.

The Term: "device credentials"

• Context and Importance: This term is fundamental to patents covering "provisioning" and "credential porting." The scope of infringement will hinge on whether this term is limited to network access keys (like a SIM profile) or also includes a broader set of service policies, user data, and integrity checks.
• Evidence for a Broader Interpretation: The '055 patent's description of an authorization sequence includes steps like "verify device service plan standing" and "verify device access control integrity standing" '055 Patent, FIG. 43B, block 4334 This suggests "credentials" may encompass a wide array of information beyond a simple network key, potentially supporting a broader construction.
• Evidence for a Narrower Interpretation: The abstract of the '055 patent states the device stores "a set of device credentials for activating the communications device for a service on a network" '055 Patent, abstract This language may be used to argue that the term should be limited to only those credentials essential for initial network activation, supporting a narrower construction.

VI. Other Allegations

Indirect Infringement

The complaint alleges that Google induces infringement by actively encouraging and instructing its customers to use the Accused Instrumentalities in their normal, infringing manner Compl. ¶49 Compl. ¶52 Compl. ¶61 It also alleges contributory infringement, stating the accused products are not staple articles of commerce suitable for substantial noninfringing use Compl. ¶51 Compl. ¶63

Willful Infringement

The complaint makes extensive allegations of willful infringement, asserting that Google had pre-suit knowledge of the patents. The alleged bases for knowledge include Google's deep involvement with partners (Samsung, Verizon, AT&T, T-Mobile) that Headwater had previously sued over the same patent families Compl. ¶¶18-28, Google's alleged receipt of claim charts from those litigations Compl. ¶18 Compl. ¶23, its corporate representative's testimony in a prior case Compl. ¶22 Compl. ¶27, and patent marking notices in software that was licensed from Plaintiff's predecessor Compl. ¶51 The complaint further alleges Google engaged in "efficient infringement" by continuing its conduct despite this knowledge Compl. ¶20 Compl. ¶25

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

• A core issue will be one of willful infringement: the complaint presents a detailed narrative of Google's alleged pre-suit knowledge stemming from years of litigation against its key Android and carrier partners. The central question for the court and jury will be whether this extensive, albeit indirect, exposure to the patents is sufficient to prove the subjective recklessness required for willfulness, or if Google can establish a good-faith belief of non-infringement or invalidity that negates such a finding.
• A key legal question will be one of claim construction and architectural mapping: can the patent claims, which appear to describe a specific "Service Processor" and "Service Controller" architecture, be construed broadly enough to cover the functionality of Google's distributed Android OS and cloud-based services like Google Fi? The case may turn on whether the court finds a functional correspondence or a fundamental architectural mismatch.
• An evidentiary question will be one of technical implementation: assuming the claims are construed broadly, the infringement analysis will depend on whether Plaintiff can demonstrate through discovery that the accused Google products and services actually perform the specific steps of "automated provisioning," "credential porting," and "security" as recited in the patent claims. The complaint's high-level allegations will need to be substantiated with evidence of the accused systems' precise operation.