DCT

7:26-cv-00338

Headwater Research LLC v. Google LLC

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 7:26-cv-00338, W.D. Tex., 08/27/26
  • Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Google maintains a regular and established place of business in the District, including a corporate office and personnel in Austin who develop, market, and sell the accused Google Cloud services.
  • Core Dispute: Plaintiff alleges that Defendant's Google Cloud platform infringes a patent related to the integrated design and provisioning of network service plans.
  • Technical Context: The technology concerns systems for creating, managing, and enforcing policy-based rules for access control, usage accounting, and notifications in cloud computing environments.
  • Key Procedural History: The complaint alleges that Google has been aware of Plaintiff's broader patent portfolio since at least March 2023 due to extensive litigation Plaintiff has pursued against Google's major customers and business partners (including Samsung, Verizon, and AT&T) involving patents with the same lead inventor.

Case Timeline

Date Event
2009-01-28 Earliest Priority Date Claimed by '804 Patent
2022-01-01 Headwater litigation campaign against Google's partners begins
2023-03-01 Headwater serves complaint against Samsung in "103 Case"
2024-04-30 U.S. Patent No. 11,973,804 Issues
2026-08-27 Complaint Filed

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

  • Patent Identification: U.S. Patent No. 11,973,804, "Network service plan design," issued April 30, 2024.

The Invention Explained

  • Problem Addressed: The patent's background describes the conventional process for developing network service plans as disjointed and inefficient, with separate teams for control, accounting, and notification policies working in "silos," which slows deployment and leads to less coherent plan design ʼ804 Patent, col. 1:5-24
  • The Patented Solution: The invention is an integrated and hierarchical design environment that allows for the unified creation of access-control, accounting, and notification policies ʼ804 Patent, abstract This system uses a hierarchy of reusable design objects (such as filters, components, and policies) that can be combined into service plans and catalogs ʼ804 Patent, FIG. 5 The system is designed to automatically translate these high-level policy designs into the specific provisioning instructions required by various network elements and end-user devices to implement the service plan ʼ804 Patent, FIG. 2 ʼ804 Patent, col. 2:5-13
  • Technical Importance: This integrated approach was designed to streamline the creation and deployment of complex, flexible service plans for mobile and cloud networks, a process that was previously slow and fragmented ʼ804 Patent, col. 1:15-24

Key Claims at a Glance

  • The complaint asserts at least Claim 1 of the '804 Patent Compl. ¶44
  • The essential elements of independent Claim 1, as synthesized from the patent's description, appear to be a system comprising:
    • A processor and memory providing a hierarchical design environment for creating a network service plan.
    • The environment is configured to define one or more classification objects (e.g., filters) for classifying network traffic.
    • The environment is configured to associate the classification objects with policy events, where each event defines an action to be performed based on a corresponding policy state.
    • A provisioning instruction translator configured to translate the completed network service plan into provisioning instructions for network elements.
  • The complaint does not explicitly reserve the right to assert other claims, but the phrasing "at least claim 1" suggests this possibility Compl. ¶44

III. The Accused Instrumentality

Product Identification

  • The Accused Instrumentalities are "Google Cloud servers and services," including the infrastructure and functionality for Google's online cloud storage, compute, database management, identity, policy, authorization, access-control, usage-metering, notification, and billing/cost-management services Compl. ¶27

Functionality and Market Context

  • The complaint alleges that Google Cloud is built upon a "policy-based authorization and access-control architecture" Compl. ¶3 This architecture is used to authenticate and authorize requests made to Google Cloud services based on policies maintained by Google's servers Compl. ¶3
  • The accused systems are also alleged to measure customer consumption of services, apply quota and billing policies, and bill customers accordingly Compl. ¶4 Furthermore, they allegedly generate and deliver notifications to users regarding their usage relative to defined limits, thresholds, and budgets Compl. ¶5
  • Plaintiff alleges this policy-based system is "fundamental to Google's ability to sell cloud services at scale" Compl. ¶6 and cites significant and rapidly growing revenue from the Google Cloud business segment Compl. ¶8

IV. Analysis of Infringement Allegations

The complaint does not include the claim chart exhibit it references Compl. ¶44 The following analysis is based on the narrative allegations in the complaint mapped to the apparent elements of Claim 1.

No probative visual evidence provided in complaint.

  • Identified Points of Contention:
    • Scope Questions: The infringement analysis may raise the question of whether Google's internal system for managing enterprise cloud computing policies constitutes a "network service plan design" system within the meaning of the patent, which describes its invention with numerous examples drawn from consumer-facing mobile and data plans ʼ804 Patent, FIG. 1
    • Technical Questions: A potential point of contention is whether the architecture of the Google Cloud policy system embodies the specific "hierarchical design environment" described in the patent, including its distinct levels of filters, components, policies, and plans ʼ804 Patent, FIG. 5 The analysis will question what evidence the complaint provides that the accused system's structure maps to the claimed hierarchy.

V. Key Claim Terms for Construction

  • The Term: "network service plan"

    • Context and Importance: This term is central to the patent's scope. The dispute may turn on whether the term is broad enough to cover internal, enterprise-focused cloud service policies (like Google's IAM and billing rules) or if it is limited to the consumer-facing mobile service plan context heavily featured in the patent's examples.
    • Intrinsic Evidence for a Broader Interpretation: The specification describes the invention as applying to plans for "voice, data, messaging and app plans" in an "integrated, hierarchical design environment," which could be argued to encompass any rule-based system for managing network services ʼ804 Patent, col. 5:14-17
    • Evidence for a Narrower Interpretation: The patent's figures and user interface examples predominantly show consumer-oriented plans like "Voice 30" for "$1.99" or "Facebook Day" for "$0.99," which could suggest a narrower construction limited to such offerings ʼ804 Patent, FIG. 1

  • The Term: "hierarchical design environment"

    • Context and Importance: Practitioners may focus on this term because the infringement case may depend on whether Google's policy management tools are structured in the specific hierarchical manner claimed by the patent.
    • Evidence for a Broader Interpretation: The specification describes the hierarchy in general terms as organizing "classification objects and policy events" in "multiple hierarchical levels" to allow for "ascendant inheritance of object properties" ʼ804 Patent, col. 5:29-35
    • Evidence for a Narrower Interpretation: Figure 5 of the patent explicitly illustrates a specific five-level hierarchy of "Catalogs," "Plans & Bundles," "Service Policies," "Policy Components," and "Filters." A party could argue the term is limited to a system possessing this particular structure ʼ804 Patent, FIG. 5

VI. Other Allegations

  • Indirect Infringement: The complaint alleges that Google induces infringement by actively encouraging and instructing its customers to use Google Cloud's policy-based features in a way that infringes the '804 patent Compl. ¶46 These acts allegedly include "providing information and instructions on the use of the Accused Instrumentalities" Compl. ¶46
  • Willful Infringement: The complaint alleges willfulness based on pre-suit knowledge. It claims Google has monitored Headwater's patent portfolio since at least March 2023 due to extensive, ongoing litigation against Google's "customers and business partners" involving related patents Compl. ¶10 The complaint further alleges Google had knowledge of the '804 patent since its issuance on April 30, 2024, or was willfully blind to its infringement Compl. ¶9 Compl. ¶11

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

  • A core issue will be one of definitional scope: can the term "network service plan," which is described in the patent with examples rooted in consumer mobile services, be construed to cover the internal policy and billing rule architecture of an enterprise-grade cloud computing platform like Google Cloud?
  • A key evidentiary question will be one of structural equivalence: does Google Cloud's policy management system operate using the specific multi-level "hierarchical design environment" that is a central feature of the patented invention, or is there a fundamental mismatch in the operational architecture of the accused system and the patent's claims?
  • A central question for willfulness will be one of knowledge and intent: can Plaintiff demonstrate that Google's alleged monitoring of litigation involving its business partners gave it pre-suit knowledge of the specific infringement alleged in this case, or that it was willfully blind to that infringement, sufficient to meet the standard for enhanced damages?