DCT

7:26-cv-00064

InterDigital Inc v. Amazon.com Inc

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 7:26-cv-00064, W.D. Tex., 02/23/2026
  • Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Defendants are registered to do business in Texas, have transacted business in the District, and have committed acts of infringement in the District. Allegations point to Defendants' maintenance of corporate offices, fulfillment centers, and at least three actively-staffed data centers in Austin and San Antonio, which are used to operate the accused cloud services.
  • Core Dispute: Plaintiff alleges that Defendant’s Amazon Web Services, primarily the CloudFront Content Delivery Network (CDN) and associated services, infringe six patents related to foundational aspects of CDN technology, including cache management, content acceleration, DNS-based routing, and configuration management.
  • Technical Context: Content Delivery Networks are a critical component of modern internet infrastructure, responsible for efficiently distributing high-bandwidth content, such as streaming video and software, to a global user base with low latency.
  • Key Procedural History: The Asserted Patents were part of an intellectual property portfolio acquired by InterDigital from Edgio (formerly Limelight Networks) in early 2025, with the assignment to plaintiff DRNC Holdings, Inc. recorded in January 2025.

Case Timeline

Date Event
2007-09-07 ’259 Patent Priority Date
2008-11-01 Amazon CloudFront Launch Date (approx.)
2010-09-01 ’128 Patent Priority Date
2011-04-05 ’259 Patent Issue Date
2011-08-16 ’701 and ’769 Patents Priority Date
2012-10-01 ’416 Patent Priority Date
2013-10-29 ’565 Patent Priority Date
2013-11-12 ’769 Patent Issue Date
2014-06-03 ’128 Patent Issue Date
2014-10-21 ’701 Patent Issue Date
2015-04-21 ’416 Patent Issue Date
2018-10-30 ’565 Patent Issue Date
2025-01-05 Asserted Patents assigned from Edgio, Inc. to DRNC Holdings, Inc.
2026-02-23 Complaint Filing Date

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

U.S. Patent No. 7,921,259 - "Content Network Global Replacement Policy," issued April 5, 2011

The Invention Explained

  • Problem Addressed: The patent describes a problem wherein content owners using CDNs lacked direct control over how their content was managed within the edge servers' cache memory (Compl. ¶60). Conventional CDNs relied on generic, autonomous policies (like evicting the least recently used content) that could prematurely remove important or large files, leading to inefficient re-fetching from the origin server (’259 Patent, col. 2:24-33).
  • The Patented Solution: The invention proposes a system where a content provider can, via a central system, define and set a specific "replacement policy" for its content on a CDN's edge servers (Compl. ¶61). This allows the provider to control the "movement of content... into and out of the data store" (’259 Patent, claim 1). The specification describes policies that can lock content to prevent deletion, pre-load content before it is requested, or, for large media files, retain only the initial portion of the file in the cache to enable quick playback while the rest is fetched (’259 Patent, col. 5:1-5; Compl. ¶61).
  • Technical Importance: This approach provided content providers with granular, policy-based control over CDN caching, moving beyond the one-size-fits-all, automated policies prevalent at the time.

Key Claims at a Glance

  • The complaint asserts at least independent claim 11 (Compl. ¶103).
  • Claim 11 is a system claim directed to a "content delivery system" with the following essential elements:
    • A "content server" for storing a plurality of content files.
    • An "edge server" of a content delivery network in communication with the content server, having "cache memory" for storing content files.
    • A "replacement policy module" for managing content in the cache memory, which includes a "controller" allowing a content owner to "set the parameters" for updating content stored at the edge server.
  • The complaint reserves the right to assert additional claims (Compl. ¶108).

U.S. Patent No. 10,116,565 - "End-to-End Acceleration of Dynamic Content," issued October 30, 2018

The Invention Explained

  • Problem Addressed: The patent addresses latency and throughput inefficiencies when a CDN edge server (or "PoP") needs to fetch uncached content from an upstream server, such as another PoP or the content's origin (Compl. ¶67). Establishing a new long-haul connection for each request incurs significant delay due to connection setup handshakes (e.g., TCP, SSL) and the "slow-start" nature of TCP, which gradually increases transmission speed (’565 Patent, col. 8:36-40; ’565 Patent, col. 9:1-10).
  • The Patented Solution: The invention describes a system that maintains a "persistent connection mesh" between PoPs (’565 Patent, Abstract). These connections are "pre-warmed," meaning they are kept open and have already negotiated a high-throughput rate by increasing their "congestion window" (’565 Patent, claim 9). When a first PoP receives a request for uncached content, it can retrieve that content from a second PoP through this persistent, high-speed connection, bypassing the setup delays and slow-start penalties of an on-demand connection (Compl. ¶68; '565 Patent, col. 10:1-15).
  • Technical Importance: This architecture significantly accelerates the delivery of uncached or dynamic content by front-loading the latency costs associated with establishing long-distance network connections.

Key Claims at a Glance

  • The complaint asserts at least independent claim 9 (Compl. ¶111).
  • Claim 9 is a system claim for accelerating uncached content with the following essential elements:
    • A "first POP" with edge servers configured to receive a content request.
    • A "second POP" with edge servers.
    • A "connection" between the first and second POP that is "available... prior to the content request being received".
    • The connection is "pre-warmed to increase the congestion window".
    • A content portion is transmitted through this connection from the second POP to the first POP in response to the request.
  • The complaint reserves the right to assert additional claims (Compl. ¶116).

Multi-Patent Capsules

  • U.S. Patent No. 8,745,128, "Optimized Content Distribution Based on Metrics Derived from End User," issued June 3, 2014

    • Technology Synopsis: The patent is directed to improving DNS-based routing for CDNs (Compl. ¶73). It addresses the problem of non-optimal server selection that occurs when routing decisions are based on the IP address of a user's recursive DNS resolver, which may be geographically distant from the user (Compl. ¶74). The solution involves modifying the DNS request to include the end user's actual IP address, allowing the authoritative DNS server to make a more accurate, performance-based server selection (’128 Patent, Abstract).
    • Asserted Claims: At least independent claim 10 (Compl. ¶119).
    • Accused Features: Amazon Route 53 and its integration with CloudFront for DNS-based routing (Compl. ¶118).

  • U.S. Patent No. 9,015,416, "Efficient Cache Validation and Content Retrieval in a Content Delivery Network," issued April 21, 2015

    • Technology Synopsis: The patent describes a method to improve cache efficiency by using checksums for validation (Compl. ¶80). Instead of automatically purging content when its Time-to-Live (TTL) expires, an edge server requests a checksum of the fresh content from an upstream server (Compl. ¶82). If the checksum matches the checksum of the cached (expired) content, the cached version is served immediately, avoiding a full re-download from the origin and reducing latency (’416 Patent, Abstract).
    • Asserted Claims: At least independent claim 19 (Compl. ¶127).
    • Accused Features: Amazon CloudFront infrastructure that, upon TTL expiration, uses an upstream ETag/checksum to validate a cached object's freshness before deciding whether to retain or replace it (Compl. ¶127).

  • U.S. Patent No. 8,868,701, "Configuration Management Repository for a Federation of Distributed Platforms," issued October 21, 2014

    • Technology Synopsis: The patent addresses the challenge of deploying and maintaining consistent customer configurations across servers operated by different service providers in a federated CDN environment (Compl. ¶88). It proposes a central configuration management repository that serves as an authoritative control point, storing configurations and identifying which servers should receive them (Compl. ¶90). The system automates the deployment of a selected configuration to servers across provider boundaries (’701 Patent, Abstract).
    • Asserted Claims: At least independent claim 1 (Compl. ¶135).
    • Accused Features: Amazon CloudFront's configuration-propagation features and services like Lambda@Edge, which are alleged to deploy applications and configurations across identified sets of servers (Compl. ¶135).

  • U.S. Patent No. 8,583,769, "Configuration Management Repository for a Distributed Platform," issued November 12, 2013

    • Technology Synopsis: This patent is directed to a system for centrally storing, tracking, and deploying server configurations across a large, distributed platform like a CDN (Compl. ¶95). It addresses shortcomings of prior art systems, such as the inability to perform incremental updates or easily revert to prior versions (Compl. ¶96). The invention provides a repository that maintains configurations and mappings to server sets, and upon receiving a modification, deploys it to the correct servers while retaining versioning and performance data to allow for automatic rollbacks if performance degrades (Compl. ¶¶97-98).
    • Asserted Claims: At least independent claim 1 (Compl. ¶143).
    • Accused Features: Amazon CloudFront's associated configuration-management and deployment features, which allegedly allow for storing configurations with server mappings, receiving modifications, and deploying changes to the edge (Compl. ¶143).

III. The Accused Instrumentality

Product Identification

  • The complaint collectively defines the "Accused Instrumentalities" as a suite of Amazon Web Services and related hardware (Compl. ¶2, fn. 1). The central accused instrumentality is Amazon's CloudFront content delivery network (CDN) (Compl. ¶2). This includes its multi-tier caching architecture of globally distributed "edge locations" (PoPs) and "regional edge caches" (Compl. ¶53).

Functionality and Market Context

  • The complaint alleges CloudFront is configured and administered through the AWS Management Console and associated APIs, which function as its control plane (Compl. ¶54). Specific accused features that work in concert with CloudFront include:
    • Origin Shield: An additional caching layer to consolidate requests to the origin server (Compl. ¶55).
    • Lambda@Edge: A service that allows custom code (applications) to be deployed and executed at edge locations (Compl. ¶57; Compl. ¶135).
    • Amazon Route 53: A DNS service used for routing user requests to AWS resources, including CloudFront distributions (Compl. ¶2; Compl. ¶118).
    • Origin Servers: Services like Amazon S3 and AWS Elemental MediaPackage that store the original content fetched by CloudFront (Compl. ¶53).
  • The complaint positions the Accused Instrumentalities as the foundational infrastructure for Amazon's own large-scale services, such as Amazon Prime Video, and as a commercial service offered to third-party customers (Compl. ¶¶17, 48). A diagram provided in the complaint illustrates the data flow from viewers to edge locations, then to regional edge caches, and finally to an origin server (Compl. p. 37).

IV. Analysis of Infringement Allegations

’259 Patent Infringement Allegations

Claim Element (from Independent Claim 11) Alleged Infringing Functionality Complaint Citation Patent Citation
a content server storing a plurality of content files Amazon S3, AWS Elemental MediaPackage, or other customer-designated HTTP servers act as origin servers storing the original content files. ¶53 col. 6:3-14
an edge server of a content delivery network... having cache memory for storing content files Amazon CloudFront edge locations (PoPs) contain servers that cache and deliver content to end users. ¶¶2, 53 col. 6:20-24
a replacement policy module for managing content stored within the cache memory... The AWS Management Console and CloudFront APIs provide cache-control and management services that manage how long content stays in the cache before expiration. ¶¶54, 102 col. 8:60-65
including a controller for allowing a content owner to set the parameters for updating content stored at the edge server... The AWS console and APIs allow customers to configure cache behavior by setting parameters such as Minimum, Maximum, and Default TTL (Time to Live). ¶103; Compl. p. 35 col. 8:60-65

A screenshot from Amazon's developer guide shows the user interface for controlling cache duration via TTL settings, which Plaintiff alleges constitutes the claimed controller (Compl. p. 35).

’565 Patent Infringement Allegations

Claim Element (from Independent Claim 9) Alleged Infringing Functionality Complaint Citation Patent Citation
a first POP comprising a first plurality of edge servers... configured to receive a content request from a user device Amazon CloudFront "edge locations" which are points of presence (PoPs) containing edge servers that receive content requests from viewers. ¶53 col. 1:33-35
a second POP comprising a second plurality of edge servers Amazon CloudFront "Regional Edge Caches," which are larger, upstream PoPs that sit between the edge locations and the origin servers. ¶53 col. 1:35-37
a connection... available between the first POP and the second POP prior to the content request being received... The network connections and transport mechanisms between CloudFront edge locations and the Regional Edge Caches that are part of the AWS global edge network. ¶111 col. 9:12-32
the connection is pre-warmed to increase the congestion window The established network path between the edge locations and regional caches allegedly avoids the slow-start penalties associated with creating a new long-haul connection for each request. ¶69 col. 9:12-32

A diagram from the complaint depicts this two-tiered architecture, showing "Edge locations" as the first tier and "Regional edge caches" as the second, upstream tier from which the first tier can fetch content (Compl. p. 37).

Identified Points of Contention

  • Scope Questions (’259 Patent): A central question may be whether standard industry cache-control mechanisms, such as setting TTL values, constitute the claimed "replacement policy module" that allows a content owner to "set the parameters for updating content." The defense may argue these are merely standard cache expiration settings, not the more complex "replacement policy" described in the patent's specification (e.g., partial file retention).
  • Technical Questions (’565 Patent): The dispute may focus on whether the connection between a CloudFront edge location and a regional edge cache meets the claim limitation of being "pre-warmed to increase the congestion window." The analysis will likely require evidence on the specific network protocols and connection management techniques employed by AWS, and whether they differ from the persistent, high-throughput mesh described in the patent.

V. Key Claim Terms for Construction

For the ’259 Patent:

  • The Term: "replacement policy module"
  • Context and Importance: This term is the central novel element of claim 11. Its construction will determine whether Amazon's standard cache-control settings fall within the claim's scope. Practitioners may focus on this term because the infringement theory hinges on equating Amazon's TTL settings with the patent's more feature-rich "replacement policy."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: Claim 11 itself defines the module as "including a controller for allowing a content owner to set the parameters for updating content stored at the edge server," which could be argued to cover any user-configurable cache control (’259 Patent, claim 11).
    • Evidence for a Narrower Interpretation: The specification describes specific functions for the policy, such as "partial retention, pre-loading, and purging" and policies based on "geographic region, time of delivery, content type, file size," etc. (Compl. ¶¶61-62; ’259 Patent, col. 3:13-30). A defendant may argue that the term should be limited to a module capable of performing these more advanced functions, not just basic TTL expiration.

For the ’565 Patent:

  • The Term: "pre-warmed to increase the congestion window"
  • Context and Importance: This term defines the key technical characteristic of the "connection" that allegedly provides the acceleration benefit. The infringement case for claim 9 depends on demonstrating that the connection between AWS edge and regional caches is not just persistent, but is actively managed in this specific way to maximize throughput.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The background section discusses the problem of the "slow-start congestion window" in conventional connections, suggesting that any connection designed to overcome this specific problem could be considered "pre-warmed" (’565 Patent, col. 8:36-54).
    • Evidence for a Narrower Interpretation: The detailed description explains that pre-warmed connections are those that "have previously sent and received data" such that "the throughput need not operate in a pessimistic state," explicitly linking the "pre-warmed" state to prior data transmission that has already maximized the connection's throughput (’565 Patent, col. 9:22-28).

VI. Other Allegations

  • Indirect Infringement: For each asserted patent, the complaint alleges induced infringement (Compl. ¶¶104, 112, 120, 128, 136, 144). The allegations state that Defendants encourage and instruct customers to use the Accused Instrumentalities in infringing ways through technical documentation, developer guides, console workflows, and marketing materials.
  • Willful Infringement: The complaint alleges that Defendants had knowledge of the asserted patents and their infringement "at least as of the filing of this Complaint" (Compl. ¶¶106, 114, 122, 130, 138, 146). This forms the basis for a claim of post-suit willful infringement.

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

This case presents a broad challenge to the foundational technologies of Amazon's CloudFront CDN, based on a portfolio of patents originating from a pioneering CDN provider. The resolution will likely depend on the following key questions:

  1. A core issue will be one of definitional scope: can patent claims directed at specific CDN functionalities from the late 2000s and early 2010s be construed to read on the features of a modern, highly-integrated cloud services platform? For example, does a user-configurable TTL setting in the AWS console meet the definition of a "replacement policy module," or is there a fundamental mismatch in the level of control and functionality envisioned by the patent?

  2. A key evidentiary question will be one of technical implementation: does the accused AWS architecture operate in the specific manner required by the claims? For instance, what technical evidence will demonstrate that the connection between an AWS edge location and a regional edge cache is "pre-warmed to increase the congestion window," as opposed to using a different, non-infringing method of connection optimization?

  3. A central dispute will likely be one of system integration and attribution: given the modular and customer-configurable nature of AWS, how will infringement be proven for system claims that require multiple components to work together? The case may turn on whether the combination of services like CloudFront, Route 53, and Lambda@Edge, as configured by Amazon or its customers, practices the claimed methods and systems.

Loading Complaint