DCT

2:26-cv-02141

Optimnet LLC v. Amazon.com Services LLC

Log In
Key Events
Amended Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 7:25-cv-00532, W.D. Tex., 02/24/2026
  • Venue Allegations: Venue is alleged based on Defendants maintaining regular and established places of business in the Western District of Texas, including data centers, corporate offices, and fulfillment centers, and committing acts of infringement within the District.
  • Core Dispute: Plaintiff alleges that Defendants’ core cloud infrastructure and content delivery services infringe four patents related to distributed data recovery, secure cloud computing, fault tracing, and on-demand content delivery network (CDN) configuration.
  • Technical Context: The patents-in-suit address foundational technologies for operating large-scale, resilient, and secure cloud computing platforms, which are critical to the modern digital economy.
  • Key Procedural History: The Asserted Patents originated with the Electronics and Telecommunications Research Institute (ETRI) of Korea. Plaintiff OptimNet LLC asserts it is the exclusive licensee with all substantial rights to enforce the patents, based on a 2024 exclusive license from ETRI to Arista Holdings Co., Ltd. and a 2025 assignment of those rights from Arista to OptimNet.

Case Timeline

Date Event
2009-12-18 U.S. Patent No. 8,543,864 Priority Date
2011-11-03 U.S. Patent No. 8,788,846 Priority Date
2011-12-29 U.S. Patent No. 9,104,565 Priority Date
2012-04-05 U.S. Patent No. 9,112,934 Priority Date
2013-09-24 U.S. Patent No. 8,543,864 Issued
2014-07-22 U.S. Patent No. 8,788,846 Issued
2015-08-11 U.S. Patent No. 9,104,565 Issued
2015-08-18 U.S. Patent No. 9,112,934 Issued
2024-04-23 ETRI grants exclusive license to Arista Holdings Co., Ltd.
2025-02-06 Amazon releases 2024 financial results cited in complaint
2025-06-04 Arista assigns license rights to OptimNet LLC
2026-02-24 Complaint Filed

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

U.S. Patent No. 8,543,864 - "Apparatus and Method of Performing Error Recovering Process in Asymmetric Clustering File System"

  • Patent Identification: U.S. Patent No. 8,543,864, "Apparatus and Method of Performing Error Recovering Process in Asymmetric Clustering File System," issued September 24, 2013 Compl. ¶61

The Invention Explained

  • Problem Addressed: The patent's background describes the problem of data recovery in distributed file systems where a central metadata server managing the recovery process can become a performance bottleneck when a data server fails (’864 Patent, col. 1:56-59).
  • The Patented Solution: The invention proposes a distributed error recovery method to solve this problem. When a data server fails, a data server in a separate, non-failed "data server group" takes charge of the recovery. This designated data server receives a list of data chunks to be recovered, requests the necessary surviving data and parity chunks from other servers, reconstructs the lost data, and stores the recovered chunk. This offloads the intensive recovery task from the central metadata server, distributing the workload across the cluster ’864 Patent, abstract ’864 Patent, col. 2:5-16
  • Technical Importance: This distributed approach to data recovery enhances the efficiency, speed, and scalability of fault tolerance in large-scale storage systems ’864 Patent, col. 1:61-65

Key Claims at a Glance

The complaint references infringement of "the method of claim 1" Compl. ¶75 The essential elements of independent method claim 1 are:

  • dividing a plurality of data servers into a plurality of data server groups, each data server group including at least one data server;
  • receiving a chunk list requiring recovery by a one or more data servers included in data server groups other than a data server group including a failed data server;
  • requesting chunk data necessary for recovering an erroneous chunk from the one or more data servers in the data server groups other than the data server group including the failed data server; and
  • recovering the erroneous chunk based on the chunk data by the one or more data servers in the other data server groups.

U.S. Patent No. 8,788,846 - "Cloud Computing System and Cloud Server Managing Method Thereof"

  • Patent Identification: U.S. Patent No. 8,788,846, "Cloud Computing System and Cloud Server Managing Method Thereof," issued July 22, 2014 Compl. ¶82

The Invention Explained

  • Problem Addressed: The patent addresses the need to protect privacy and provide security for sensitive computations within a multi-tenant cloud computing environment (’846 Patent, col. 1:43-45; Compl. ¶86).
  • The Patented Solution: The invention describes a cloud system with two distinct server types: "general servers" and "secure servers." A client application is divided into a "general code" and a "secret code." The "secret code" is encrypted with a public key before being sent to the cloud. Only a "secure server," which possesses the corresponding private key, can decrypt and execute the sensitive "secret code." A "management server" orchestrates the process, directing work to the appropriate server type. This partitions the workload, ensuring that sensitive operations are confined to a trusted execution environment ’846 Patent, abstract ’846 Patent, col. 4:45-67
  • Technical Importance: This architecture enables confidential computing, allowing users to process sensitive data on shared cloud infrastructure while maintaining cryptographic control over the code that accesses it ’846 Patent, col. 1:46-48

Key Claims at a Glance

The complaint alleges infringement of at least one claim Compl. ¶89 The essential elements of independent system claim 1 are:

  • a management server configured to manage a plurality of servers and distribute service resources;
  • wherein, each of the servers corresponds to one of a secure server type and a general server type,
  • the secure server type of server decrypts an encrypted code of a program provided from a client, and
  • secret code of the program is executed by one or more secure server type of servers and general code of the program is executed by one or more general server type of servers.

U.S. Patent No. 9,104,565 - "Fault Tracing System and Method for Remote Maintenance"

  • Patent Identification: U.S. Patent No. 9,104,565, "Fault Tracing System and Method for Remote Maintenance," issued August 11, 2015 Compl. ¶103
  • Technology Synopsis: The patent addresses the problem of accurately tracing faults in a complex network environment, such as a smart home Compl. ¶107 The solution involves creating a "resource relation map" that models the dependencies between various network resources (e.g., devices, services, links). When a fault occurs, the system traces the fault by probing resources along paths determined by the dependency map to identify the root cause (’565 Patent, abstract; ’565 Patent, col. 2:6-12).
  • Asserted Claims: At least one claim is asserted Compl. ¶110
  • Accused Features: The accused features are Amazon CloudWatch and AWS X-Ray, which provide monitoring, observability, and distributed tracing capabilities for cloud applications (Compl. ¶¶37-39; Compl. ¶112).

U.S. Patent No. 9,112,934 - "Apparatus and Method for Configuring On-Demand Content Delivering Overlay Network"

  • Patent Identification: U.S. Patent No. 9,112,934, "Apparatus and Method for Configuring On-Demand Content Delivering Overlay Network," issued August 18, 2015 Compl. ¶122
  • Technology Synopsis: The patent addresses the need for on-demand configuration of content delivery networks (CDNs) Compl. ¶126 The invention is an apparatus that acts as a control plane, receiving a configuration request from a content provider, assessing available network resources (nodes), and then dynamically configuring a "content delivery overlay network" based on the provider's needs and the available resources (’934 Patent, abstract; ’934 Patent, col. 2:4-17).
  • Asserted Claims: At least one claim is asserted Compl. ¶129
  • Accused Features: The accused feature is Amazon CloudFront, which is Amazon's global CDN service Compl. ¶26 Compl. ¶131

III. The Accused Instrumentality

Product Identification

  • The Accused Instrumentalities are components of Amazon Web Services (AWS), including Amazon Simple Storage Service (S3), Amazon Elastic Compute Cloud (EC2), the AWS Nitro System, Amazon CloudFront, Amazon CloudWatch, and AWS X-Ray Compl. ¶16 No probative visual evidence provided in complaint.

Functionality and Market Context

  • The complaint describes these services as the foundation of modern cloud computing. EC2, powered by the Nitro System, provides scalable virtual computing capacity by offloading virtualization functions to dedicated hardware for enhanced performance and security Compl. ¶¶17 Compl. ¶19 S3 is a highly durable object storage service that stores data redundantly across physically distinct "Availability Zones" Compl. ¶33 CloudFront is a global CDN that accelerates content delivery Compl. ¶26 CloudWatch and X-Ray are observability services for monitoring and debugging distributed applications Compl. ¶¶37 Compl. ¶39
  • The complaint alleges these services are of central economic importance to Amazon, citing AWS segment sales of $107.6 billion in 2024 Compl. ¶22, and are foundational to major internet companies such as Netflix and Airbnb Compl. ¶23 Compl. ¶24 Compl. ¶35

IV. Analysis of Infringement Allegations

The complaint references claim-chart exhibits that are not provided with the filed complaint. The following tables summarize the infringement theories as narrated in the complaint.

'864 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
dividing a plurality of data servers into a plurality of data server groups... Amazon’s global infrastructure is divided into Regions and Availability Zones (AZs), which the complaint maps to "data server groups." An AZ is one or more discrete data centers with redundant power, networking, and connectivity. ¶33 col. 9:16-18
receiving a chunk list requiring recovery by a one or more data servers included in data server groups other than a data server group including a failed data server... The complaint alleges that when a device or server fails in one AZ, the recovery process is managed by AWS systems in other, non-failed AZs to ensure data durability. ¶33; ¶70 col. 9:19-24
requesting chunk data necessary for recovering an erroneous chunk from the one or more data servers... To reconstruct data from a failure, the S3 service must read the surviving data or parity chunks from other devices, which are often stored in different AZs. ¶33; ¶70 col. 9:25-28
recovering the erroneous chunk based on the chunk data by the one or more data servers in the other data server groups. S3 is advertised as providing "11 nines" of durability by redundantly storing data and automatically recovering from failures by reconstructing data using surviving chunks from multiple devices and locations. ¶33; ¶70 col. 9:29-32

'846 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
a management server configured to manage a plurality of servers and distribute service resources... AWS provides a managed compute platform (EC2) where customers can launch and manage virtual server instances, with AWS managing the underlying resource allocation. ¶17; ¶91 col. 9:62-64
wherein, each of the servers corresponds to one of a secure server type and a general server type... The complaint maps the AWS Nitro System, with its dedicated hardware (Nitro Cards) for security and virtualization, to the claimed "secure server type," and other compute resources to the "general server type." ¶19; ¶93 col. 10:1-2
the secure server type of server decrypts an encrypted code of a program provided from a client... The Nitro System is alleged to provide an enhanced security model with dedicated hardware that isolates virtualization resources, which the complaint contends performs the function of the "secure server type." ¶19-21; ¶93 col. 10:3-5
secret code...is executed by...secure server type...and general code...is executed by...general server type... The Nitro System offloads traditional virtualization functions (e.g., networking, storage) from the host CPU to dedicated hardware. This division of labor is alleged to correspond to the claimed execution of "secret" and "general" code on different server types. ¶19; ¶93 col. 10:5-10
  • Identified Points of Contention:
    • For the '864 Patent, a central question may be whether Amazon's high-level, abstracted architecture of "Availability Zones" can be mapped to the patent's more granular concept of "data server groups." It also raises the question of whether a data server itself orchestrates recovery, as claimed, or if a separate control plane service (analogous to the patent's metadata server) manages the process.
    • For the '846 Patent, a key dispute may be whether the AWS Nitro System's function of offloading infrastructure virtualization tasks to dedicated hardware is equivalent to the patent's concept of a "secure server" executing a client-provided, encrypted "secret code." The analysis may turn on the distinction between application-level code segmentation (patent) and infrastructure-level function offloading (accused product).

V. Key Claim Terms for Construction

  • Term ('864 Patent): "data server"

    • Context and Importance: Claim 1 requires a "data server" to receive a recovery list and perform the recovery. Infringement will depend on whether an entity within AWS that performs this function can be classified as a "data server" as distinct from a control-plane or metadata service. Practitioners may focus on this term to determine if the accused architecture aligns with the patent's distributed recovery model.
    • Intrinsic Evidence for a Broader Interpretation: The specification describes data servers as managing data of a file ’864 Patent, col. 1:26-28, which could support an interpretation covering any node involved in storing or processing file data chunks.
    • Intrinsic Evidence for a Narrower Interpretation: The figures and description distinguish the "data servers" (20a-20n) from the "metadata server" (10) ’864 Patent, FIG. 1 This could support a narrower definition limited to primary storage nodes, potentially excluding higher-level management services that orchestrate recovery.

  • Term ('846 Patent): "secure server type"

    • Context and Importance: The complaint maps the AWS Nitro System to this term. The case's outcome may depend on whether this hardware-accelerated virtualization platform fits the definition of a "server type" that decrypts and executes a client's "secret code."
    • Intrinsic Evidence for a Broader Interpretation: The patent uses functional language, stating the secure server "decrypts an encrypted code provided from a client" ’846 Patent, abstract This could support reading the term on any component that performs this trusted decryption and execution function.
    • Intrinsic Evidence for a Narrower Interpretation: The patent describes a system where servers are classified as one of two "types" and that "secure server type of servers share a public key and a private key" ’846 Patent, col. 10:33-35 This suggests a server-level classification and key-sharing scheme, which may not align with how the Nitro System's hardware components are integrated and managed within an EC2 instance.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges both induced and contributory infringement for all asserted patents. The inducement claims are based on allegations that Amazon provides instructional materials, user guides, technical support, and marketing that encourage customers to use the accused services in an infringing manner (e.g., Compl. ¶69; Compl. ¶75). The contributory infringement claims add that the accused services are especially made or adapted for infringement and are not staple articles of commerce suitable for substantial non-infringing use (e.g., Compl. ¶73; Compl. ¶74).
  • Willful Infringement: Willfulness is alleged for all asserted patents, based on Defendants' alleged knowledge "through at least the filing and service of the Complaint" (e.g., Compl. ¶77). This primarily establishes a basis for post-filing willfulness, though the complaint also makes a general allegation of being "willfully blind" without providing specific facts to support pre-suit knowledge.

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

  • A central issue will be one of architectural mapping: can the specific system architectures described in the patents—originating from the early 2010s—be persuasively mapped onto the complex, multi-layered, and highly abstracted architecture of modern Amazon Web Services? This applies to mapping AWS "Availability Zones" to "data server groups" (’864 patent) and the AWS Nitro system to a "secure server type" (’846 patent).
  • A key evidentiary question will be one of functional operation: does the accused functionality in AWS products perform the specific steps required by the claims, or is there a fundamental mismatch in technical operation? For instance, does an AWS "data server" actually orchestrate recovery as required by the '864 patent, or does a control-plane service perform that role? Does the Nitro hardware execute client-provided "secret code" as contemplated by the '846 patent, or does it only offload generic infrastructure tasks?
  • The dispute will likely center on definitional scope: can claim terms rooted in the context of earlier distributed systems, such as "data server" and "secure server type", be construed broadly enough to read on the components of a modern hyperscale cloud platform, or will their meaning be narrowed by the patents' specifications to embodiments that differ from the accused systems?