Headwater Research LLC v. Amazon.com Services LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Headwater Research LLC (Texas)
  • Defendant: Amazon.com Services LLC, and Amazon Web Services, Inc. (Delaware)
  • Plaintiff's Counsel: Russ August & Kabat
• Case Identification: 7:26-cv-00308, W.D. Tex., 08/07/2026
• Venue Allegations: Venue is alleged to be proper based on Amazon residing in the district, committing acts of infringement in the district, and maintaining a regular and established place of business, including an "Austin Tech Hub" and various fulfillment and delivery facilities.
• Core Dispute: Plaintiff alleges that Defendant's Amazon Web Services (AWS) cloud-computing platform and related services infringe three patents related to simplified network architectures and virtualized policy and charging systems.
• Technical Context: The technology at issue relates to policy-based access control, authorization, and service management for devices connected to large-scale data networks, a foundational component of modern cloud computing and Internet of Things (IoT) services.
• Key Procedural History: The complaint details the extensive background of the inventor, Dr. Gregory Raleigh, including the founding of companies acquired by Cisco and Qualcomm, and his shift in focus from radio-centric problems to problems in how wireless services are provided to consumers. No prior litigation, inter partes reviews, or licensing history concerning the Asserted Patents is mentioned.

Case Timeline

Date	Event
2009-02-13	'781 Patent Priority Date
2013-03-15	'518 and '837 Patents Priority Date
2013-11-12	U.S. Patent No. 8,583,781 Issues
2020-10-13	U.S. Patent No. 10,803,518 Issues
2022-11-08	U.S. Patent No. 11,494,837 Issues
2026-08-07	Complaint Filing Date

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

No probative visual evidence provided in complaint.

U.S. Patent No. 8,583,781

• Patent Identification: U.S. Patent No. 8,583,781, entitled "Simplified service network architecture," issued on November 12, 2013.

The Invention Explained

The complaint does not provide a copy of the '781 patent for analysis. The complaint states that the patent is entitled "Simplified service network architecture" and alleges that the written description describes the invention in technical detail Compl. ¶18 Compl. ¶36 The core dispute as framed in the complaint revolves around policy-based access control and service management in large-scale networks Compl. ¶¶3-5

Key Claims at a Glance

• The complaint asserts at least claim 1 of the '781 patent Compl. ¶40
• The complaint does not provide the text of the asserted claims.

U.S. Patent No. 10,803,518

• Patent Identification: U.S. Patent No. 10,803,518, entitled "Virtualized policy and charging system," issued on October 13, 2020.

The Invention Explained

• Problem Addressed: The patent addresses the need for flexible and efficient policy and charging control in complex network environments, such as those involving 3GPP (GPRS/EPC) or 3GPP2 (CDMA/Mobile IP) standards '518 Patent, col. 3:40-50 Traditional architectures often tightly couple policy enforcement with the underlying network hardware, making it difficult to create and manage dynamic service plans.
• The Patented Solution: The invention proposes a virtualized architecture that separates policy logic from the underlying network infrastructure. It introduces a "Service Controller" that communicates with various network elements to manage service and subscriber provisioning '518 Patent, col. 5:21-24 This controller uses a set of defined interfaces to interact with operator systems, allowing it to manage policies, subscribers, and usage records in a centralized, abstract manner, as depicted in the relationship between the Service Controller (122) and various operator interfaces in Figure 1 '518 Patent, Fig. 1 '518 Patent, col. 6:8-14
• Technical Importance: This virtualized approach allows network operators to rapidly define and deploy diverse service plans and manage network resources without being constrained by the specific capabilities of underlying, often proprietary, network hardware elements.

Key Claims at a Glance

• The complaint asserts at least independent claim 1 of the '518 patent Compl. ¶53
• The essential elements of independent claim 1 include:
  • A network system for providing services to end-user devices over a wireless access network.
  • The system comprises a policy enforcement function, a first policy element, a second policy element, and a network element.
  • The network element is communicatively coupled to the other three components.
  • The network element is configured to communicate first policy information between the policy enforcement function and the first policy element.
  • The network element is configured to communicate second policy information between the policy enforcement function and the second policy element.
• The complaint does not explicitly reserve the right to assert dependent claims but makes general allegations of infringement of "the claims" of the patent Compl. ¶52

U.S. Patent No. 11,494,837 (Multi-Patent Capsule)

• Patent Identification: U.S. Patent No. 11,494,837, entitled "Virtualized policy and charging system," issued on November 8, 2022 Compl. ¶20
• Technology Synopsis: As a continuation of the same family as the '518 patent, the '837 patent addresses the same technical problem of managing policy and charging in complex wireless networks '837 Patent, col. 3:40-50 It describes a virtualized system architecture separating policy logic from network hardware, centered around a "Service Controller" that interacts with network elements through defined interfaces '837 Patent, abstract '837 Patent, Fig. 1
• Asserted Claims: The complaint asserts at least claim 1 Compl. ¶66
• Accused Features: The complaint alleges that Amazon's AWS services, including AWS IAM, AWS IoT, and Amazon SNS, infringe the '837 patent Compl. ¶64

III. The Accused Instrumentality

Product Identification

• The Accused Instrumentalities are Amazon Web Services ("AWS") and its associated infrastructure, including but not limited to AWS Identity and Access Management ("IAM"), the family of AWS IoT services ("AWS IoT"), and Amazon Simple Notification Service ("SNS") Compl. ¶2 Compl. ¶23

Functionality and Market Context

• The complaint describes the accused systems as a cloud-computing business providing policy-based authorization and access control Compl. ¶¶2-3 AWS IAM is identified as the central system for authenticating and authorizing requests to AWS APIs by evaluating applicable policies Compl. ¶3
• AWS IoT is described as a family of services that connects fleets of end-user devices to Amazon's network, enforcing per-device policies and monitoring device metrics Compl. ¶4
• The complaint alleges that this policy-based access control is fundamental to Amazon's business, enabling it to offer "governance at scale" and to "meter, bill, and charge for usage of its services" Compl. ¶¶5-6 It further alleges significant commercial success, citing that AWS net sales for 2025 alone were approximately $128.7 billion Compl. ¶7

IV. Analysis of Infringement Allegations

The complaint references Exhibits 4, 5, and 6, which it states contain claim charts detailing the infringement of the '781, '518, and '837 patents, respectively Compl. ¶40 Compl. ¶53 Compl. ¶66 As these exhibits were not available for this analysis, a summary of the narrative infringement theory is provided below.

For all asserted patents, the complaint's theory is that Amazon's AWS platform, through the combined operation of services like IAM, AWS IoT, and SNS, implements the patented technologies for managing network services, policies, and charging. The complaint alleges that Amazon directly infringes by operating these systems and also induces infringement by providing these services to its customers and instructing them on their use (Compl. ¶¶38-39; Compl. ¶51-52; Compl. ¶64-65).

V. Key Claim Terms for Construction

Analysis for the '781 patent is not possible as the patent was not provided. The following analysis is for the '518 patent.

• The Term: "policy element"
• Context and Importance: Claim 1 of the '518 patent recites a "first policy element" and a "second policy element," and requires them to communicate different policy information with the "policy enforcement function." The definition of "policy element" will be critical to determining whether distinct components of the AWS architecture (e.g., IAM policies versus billing policies) can be mapped to these separate claim limitations, or if they are merely different aspects of a single, undifferentiated policy system. Practitioners may focus on this term because the patent's distinction between two separate "policy elements" is a core structural feature of the claim.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent specification provides several examples of systems that could be considered policy elements, such as a "Service Design Center (SDC)" for creating service plans, a "CRM" (Customer Resource Management) system, and a "Billing & Provisioning" system '518 Patent, Fig. 32 This variety may support an argument that "policy element" is a broad term encompassing any system component that defines, stores, or manages rules related to service access or charging.
  • Evidence for a Narrower Interpretation: The abstract describes a system where a "first policy element" and a "second policy element" are distinct components between which policy information is communicated by a "network element" '518 Patent, abstract This structural separation, depicted consistently in figures like Figure 1, may support a narrower construction requiring two structurally and functionally discrete system components, not merely two different types of policies within a single system.

VI. Other Allegations

• Indirect Infringement: The complaint alleges that Amazon induces infringement by "inducing customers and developers to use the infringing AWS services" (Compl. ¶38; Compl. ¶51; Compl. ¶64). It further alleges Amazon "actively encourage and instruct their customers to use and integrate the Accused Instrumentalities" and does so "knowing and intending that their customers will commit these infringing acts" Compl. ¶42 Compl. ¶55 Compl. ¶68
• Willful Infringement: The complaint alleges willfulness based on knowledge acquired "at least since receipt of this Complaint" Compl. ¶41 Compl. ¶54 Compl. ¶67 It also makes a broader allegation that Amazon "has known, or has been willfully blind to the fact, that making, using, offering to sell, and selling the Accused Instrumentalities to their customers, would constitute willful infringement" Compl. ¶43 Compl. ¶56 Compl. ¶69

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

• A central question will be one of architectural mapping: can the patents' structured architectures, which recite distinct components like a "policy enforcement function," a "first policy element," and a "second policy element," be read onto Amazon's diffuse and multi-purpose cloud services, or is there a fundamental mismatch between the claimed systems and the accused AWS platform?
• A key evidentiary issue will be one of functional operation: what evidence will demonstrate that components of the AWS platform, such as IAM and its billing systems, perform the specific functions of communicating "first policy information" and "second policy information" to a "policy enforcement function" via a "network element," as explicitly required by the functional language of the asserted claims?
• A third question will concern claim scope: how broadly will the court construe terms like "policy element" and "network element"? The outcome of this construction will likely determine whether Amazon's complex, integrated cloud infrastructure falls within the boundaries of inventions described in the context of more discrete telecommunications network components.