DCT

7:26-cv-00307

Headwater Research LLC v. Oracle Corp

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: Headwater Research LLC v. Oracle Corp, 7:26-cv-00307, W.D. Tex., 08/07/2026
  • Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Defendant Oracle resides in the district, has committed acts of infringement in the district, and maintains a regular and established place of business, including its corporate headquarters, in Austin, Texas.
  • Core Dispute: Plaintiff alleges that Defendant's Oracle Cloud Infrastructure services infringe three patents related to simplified network architecture and virtualized policy and charging systems.
  • Technical Context: The lawsuit concerns foundational technologies for cloud computing, specifically policy-based access control and billing systems that are essential for managing multi-tenant cloud environments at scale.
  • Key Procedural History: The complaint does not specify any prior litigation, Inter Partes Review (IPR) proceedings, or licensing history related to the Asserted Patents.

Case Timeline

Date Event
2009-01-28 Priority Date for U.S. Patent No. 8,583,781
2011-01-01 Headwater Research LLC formed
2013-03-15 Priority Date for U.S. Patent No. 10,803,518
2013-03-15 Priority Date for U.S. Patent No. 11,494,837
2013-11-12 U.S. Patent No. 8,583,781 Issued
2020-10-13 U.S. Patent No. 10,803,518 Issued
2020-12-01 Oracle announces HQ relocation to Austin, TX
2022-11-08 U.S. Patent No. 11,494,837 Issued
2026-08-07 Complaint Filed

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

U.S. Patent No. 8,583,781 - "Simplified service network architecture"

  • Issued: November 12, 2013

The Invention Explained

  • Problem Addressed: The patent addresses the complexity and cost associated with deploying and managing network services, particularly in mobile networks, which traditionally require dedicated and often proprietary hardware and software stacks for functions like billing, access control, and policy enforcement '781 Patent, col. 1:19-50
  • The Patented Solution: The invention proposes a "simplified service network architecture" where many service control and policy functions are managed by a 'service processor' on the end-user device, which communicates with a centralized 'service controller' '781 Patent, col. 4:6-14 This architecture aims to reduce reliance on complex core network equipment by distributing intelligence to the endpoint, enabling more flexible and cost-effective service delivery '781 Patent, FIG. 16
  • Technical Importance: This architecture represented a shift toward virtualizing network functions and moving intelligence to the network edge, a precursor to modern software-defined networking (SDN) and cloud-native network management principles '781 Patent, col. 2:20-30

Key Claims at a Glance

  • The complaint asserts at least independent claim 1 Compl. ¶41
  • Essential elements of independent claim 1 (a method claim) include:
    • Collecting a plurality of service usage measurements for a communications device.
    • Comparing the measurements to a device-assisted implementation of a service policy to verify the implementation.
    • Wherein the service policy assists in routing communications associated with a first network data service over a particular path or to a particular destination.

U.S. Patent No. 10,803,518 - "Virtualized policy and charging system"

  • Issued: October 13, 2020

The Invention Explained

  • Problem Addressed: The patent describes the challenge of integrating policy and charging control systems with an operator's existing IT and network infrastructure, which can be complex and vendor-specific '518 Patent, col. 3:35-4:30
  • The Patented Solution: The invention discloses a system architecture that decouples policy management into distinct "policy elements." A "network element" acts as an intermediary, communicating "first policy information" and "second policy information" between a "policy enforcement function" and the respective first and second policy elements '518 Patent, abstract This modular approach, depicted in various system diagrams, allows for flexible and independent evaluation of different policy layers (e.g., access control policies and billing policies) '518 Patent, FIG. 2
  • Technical Importance: This virtualized architecture allows for more scalable and adaptable policy and charging systems, particularly in cloud environments where policies from different domains (e.g., security, cost, performance) must be managed cohesively '518 Patent, col. 25:1-26:24

Key Claims at a Glance

  • The complaint asserts at least independent claim 1 Compl. ¶54
  • Essential elements of independent claim 1 include:
    • A policy enforcement function.
    • A first policy element.
    • A second policy element.
    • A network element communicatively coupled to the other three components.
    • The network element is configured to communicate first policy information between the enforcement function and the first policy element, and second policy information between the enforcement function and the second policy element.

U.S. Patent No. 11,494,837 - "Virtualized policy and charging system"

  • Issued: November 8, 2022

The Invention Explained

As a continuation of the same family as the '518 Patent, the '837 patent describes a similar virtualized system for managing network policies and charging. It discloses an architecture with distinct, independent policy elements and a network element that facilitates communication between those policy elements and a policy enforcement function '837 Patent, abstract

Key Claims at a Glance

  • Asserted Claims: The complaint asserts at least independent claim 1 Compl. ¶67
  • Accused Features: The complaint alleges that Oracle's OCI IAM, OCI Compute, and OCI Billing and Cost Management systems infringe the '837 patent Compl. ¶65

III. The Accused Instrumentality

Product Identification

Oracle Cloud Infrastructure ("OCI") services, including OCI Identity and Access Management ("OCI IAM"), OCI Compute, and OCI Billing and Cost Management Compl. ¶24

Functionality and Market Context

  • The accused instrumentality is Oracle's large-scale cloud computing platform Compl. ¶2 OCI IAM is described as the core policy-based authorization and access-control system for OCI Compl. ¶3
  • The complaint alleges OCI IAM utilizes a two-layer policy structure: a "first policy element" comprising written policy language and a "second policy element" comprising a predefined administrator-role grant system. These are allegedly evaluated in parallel but separately to determine access rights for API requests Compl. ¶4
  • OCI Compute provides the underlying computing resources (e.g., Virtual Machines, Bare Metal Instances), while OCI Billing and Cost Management handles metering and charging for service usage Compl. ¶5 Compl. ¶7 The complaint alleges this layered policy enforcement is fundamental to Oracle's ability to sell cloud services at scale Compl. ¶6
  • No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint references claim-chart exhibits that are not provided Compl. ¶41 Compl. ¶54 Compl. ¶67 The infringement allegations are therefore summarized in prose.

'781 Patent Infringement Allegations

The complaint alleges that Oracle's OCI platform infringes the '781 patent by making, using, and selling a "simplified service network architecture" Compl. ¶¶35, 39-40 The infringement theory suggests that OCI's architecture for managing policy, access, and billing for cloud services embodies the patented method of simplifying service networks.

'518 Patent Infringement Allegations

The complaint alleges that Oracle's OCI IAM system directly infringes the '518 patent's claims for a "virtualized policy and charging system" Compl. ¶¶48, 52-53 The core of the allegation is that OCI IAM's two-layer authorization model maps directly onto the patent's claimed structure. Specifically, the complaint posits that IAM's "written policy language" constitutes the "first policy element" and the separate "administrator-role grant system" constitutes the "second policy element," with the IAM backend acting as the claimed "network element" that communicates between these policy layers and the enforcement function Compl. ¶4

Identified Points of Contention

  • Scope Questions: A central question for the '781 patent will be whether a cloud computing infrastructure like OCI, which manages virtual resources, falls within the scope of a "service network architecture" as contemplated by a patent with a 2009 priority date, whose specification heavily describes mobile telecommunications networks. For the '518 and '837 patents, a key question will be whether OCI's "administrator-role grant system" constitutes a "second policy element" that is distinct from the "first policy element" (written policies) in the manner required by the claims.
  • Technical Questions: An evidentiary question will be what proof exists that the OCI IAM backend performs the claimed function of the "network element"-that is, actively "communicating" distinct policy information between two separate policy elements and a policy enforcement function, as opposed to merely applying rules from different sources in a unified decision process.

V. Key Claim Terms for Construction

For U.S. Patent 8,583,781

  • The Term: "service control gateway"
  • Context and Importance: Asserted apparatus claim 11 of the '781 patent recites a "service control gateway." The infringement analysis may turn on whether any component of Oracle's OCI platform, which is a distributed cloud service, can be characterized as a "gateway" in the sense used by the patent. Practitioners may focus on this term to dispute whether a software-based cloud management plane can be equated with a "gateway" component described in the context of telecommunications hardware.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The claims do not appear to limit the "gateway" to a specific hardware structure, defining it more by its function of communicating policy and service information '781 Patent, claim 11 This may support a broader, more functional definition.
    • Evidence for a Narrower Interpretation: The detailed description repeatedly illustrates the "service control gateway" as a distinct network node, often in diagrams showing hardware components like GGSN/PDSN in a mobile network context ('781 Patent, FIG. 1, FIG. 4). This may support a narrower construction tied to a discrete network appliance rather than a distributed software function.

For U.S. Patent 10,803,518

  • The Term: "first policy element" and "second policy element"
  • Context and Importance: The complaint's infringement theory for the '518 patent is predicated on mapping OCI IAM's "written policy language" to the "first policy element" and its "administrator-role grant system" to the "second policy element" Compl. ¶4 The definitions of these terms will be dispositive, as the case hinges on whether these two aspects of OCI's system are truly distinct "elements" as claimed.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The language of claim 1 and the abstract is high-level and functional, describing the elements without structural limitations '518 Patent, claim 1 '518 Patent, abstract This could support an interpretation where any two distinct sets of policy rules, regardless of their form, could qualify as two "policy elements."
    • Evidence for a Narrower Interpretation: The patent's detailed description provides specific embodiments related to mobile network services, such as policies for data usage and sponsored services '518 Patent, col. 55:42-57:57 The figures also depict distinct architectural components for handling different policies '518 Patent, FIG. 27 This may support a narrower construction where the "policy elements" must be more structurally or functionally distinct than simply being different types of rules within the same IAM system.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges that Oracle induces infringement by providing customers with instructions, documentation, and services that encourage and facilitate use of the accused OCI systems in an infringing manner (Compl. ¶43; Compl. ¶56; Compl. ¶69). The basis for inducement is Oracle's alleged intent that its customers will use the OCI services as designed, which allegedly constitutes infringement (Compl. ¶43; Compl. ¶56; Compl. ¶69).
  • Willful Infringement: Willfulness is alleged based on Oracle's purported knowledge of the patents, dating from "at least since receipt of this Complaint" (Compl. ¶42; Compl. ¶55; Compl. ¶68). The complaint also includes a broader allegation that Oracle "has known, or has been willfully blind to the fact" of infringement, which could potentially extend to pre-suit conduct, though no specific facts supporting pre-suit knowledge are provided (Compl. ¶44; Compl. ¶57; Compl. ¶70).

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

  1. A central issue will be one of definitional scope and functional equivalence: Does Oracle's OCI IAM system, with its "written policy language" and "administrator-role grant system," operate as a "virtualized policy and charging system" containing two distinct "policy elements" as claimed by the '518 and '837 patents, or is there a fundamental mismatch in technical operation and architecture?
  2. A second core issue will be one of technological scope: Can the claims of the '781 patent, which describe a "simplified service network architecture" with a 2009 priority date and a focus on mobile device service management, be construed to cover a modern, distributed cloud computing platform like Oracle's OCI?
  3. An evidentiary question will be one of operational proof: Beyond public-facing documentation, what evidence will emerge from discovery to demonstrate that the internal workings of the OCI IAM backend function as the claimed "network element," which requires it to actively communicate distinct sets of policy information between different logical layers and an enforcement function?
Loading Complaint