OptimNet LLC v. Amazon.com Services LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: OptimNet LLC (Texas)
  • Defendant: Amazon.com Services LLC (Delaware) and Amazon Web Services, Inc. (Delaware)
  • Plaintiff’s Counsel: Russ August & Kabat
• Case Identification: 7:25-cv-00532, W.D. Tex., 02/24/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Defendants maintain regular and established places of business in the district, including data centers, corporate offices, and development labs in Austin and San Antonio, and employ a significant number of individuals in the region.
• Core Dispute: Plaintiff alleges that Defendants’ core cloud computing services, including Amazon S3, EC2, CloudFront, and CloudWatch, infringe four patents related to distributed data recovery, secure cloud computing, remote fault tracing, and on-demand content delivery networks.
• Technical Context: The technologies at issue concern foundational architectural principles for large-scale, distributed cloud infrastructure, a market central to the modern internet economy.
• Key Procedural History: The asserted patents originated from the Electronics and Telecommunications Research Institute (ETRI), a Korean government-funded research institute. The complaint details a chain of title wherein ETRI granted an exclusive license to Arista Holdings Co., Ltd., which subsequently assigned all substantial rights to Plaintiff OptimNet LLC, a transaction intended to establish OptimNet's standing to sue for infringement in its own name.

Case Timeline

Date	Event
2009-12-18	’864 Patent Priority Date
2011-11-03	’846 Patent Priority Date
2011-12-29	’565 Patent Priority Date
2012-04-05	’934 Patent Priority Date
2013-09-24	’864 Patent Issue Date
2014-07-22	’846 Patent Issue Date
2015-08-11	’565 Patent Issue Date
2015-08-18	’934 Patent Issue Date
2024-04-23	ETRI grants exclusive license to Arista
2025-06-04	Arista assigns rights to OptimNet
2026-02-24	Complaint Filing Date

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"

The Invention Explained

• Problem Addressed: The patent describes a problem in large-scale clustered file systems where, upon the failure of a single data server, the responsibility for data recovery falls upon a central metadata server, creating a potential performance bottleneck and reducing efficiency (Compl. ¶65; ’864 Patent, col. 1:56-59).
• The Patented Solution: The invention proposes a distributed error recovery method to solve this problem. Instead of relying on the central metadata server, the recovery task is offloaded to other data servers within the cluster. A data server receives a "chunk list" identifying the data to be recovered, requests the necessary data components ("chunks") from other surviving servers, and uses that information to reconstruct the data from the failed server (Compl. ¶65; ’864 Patent, abstract; ’864 Patent, col. 2:6-18).
• Technical Importance: This distributed approach is designed to enhance the speed and scalability of data recovery in large storage systems by parallelizing the workload and avoiding the limitations of a single, centralized recovery point (’864 Patent, col. 1:60-66).

Key Claims at a Glance

• The complaint alleges infringement of at least independent claim 1 (Compl. ¶75).
• Essential elements of independent claim 1 include:
  • Dividing a plurality of data servers into data server groups.
  • Receiving a list of data "chunks" requiring recovery by servers in groups that do not contain the failed server.
  • Requesting the necessary chunk data from other servers.
  • Recovering the erroneous chunk using the received chunk data, with the recovery process performed by servers in the "other data server groups."
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

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

The Invention Explained

• Problem Addressed: The patent addresses the need for enhanced security and privacy in cloud computing environments, where executing programs with sensitive data on multi-tenant infrastructure introduces risk (Compl. ¶86; ’846 Patent, col. 1:29-33).
• The Patented Solution: The invention describes a cloud system with two distinct classes of servers: "general server type" and "secure server type." A client application separates its code into a "general code" and a "secret code." The "secret code" is encrypted using a public key. Only the "secure server type" servers, which possess the corresponding private key, are capable of decrypting and executing the sensitive "secret code." A management server directs workloads, ensuring that only trusted servers handle the encrypted portions of a program (’846 Patent, abstract; ’846 Patent, col. 1:54-59).
• Technical Importance: This architecture creates a hardware- and cryptographically-enforced boundary for processing sensitive information, a foundational concept for what is now widely known as confidential computing, which is critical for regulated industries using the cloud (’846 Patent, col. 1:44-46).

Key Claims at a Glance

• The complaint alleges infringement generally and references a claim chart in an un-provided exhibit (Compl. ¶89). Independent claim 1 is representative of the invention.
• Essential elements of independent claim 1 include:
  • A management server that manages and distributes resources to a plurality of servers.
  • Servers corresponding to either a "secure server type" or a "general server type."
  • The "secure server type" decrypts an encrypted code from a client program.
  • The "secret code" of the program is executed by the secure servers, while the "general code" is executed by the general servers.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

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

• Technology Synopsis: The patent describes a system for improved fault tracing in a complex network environment, such as a smart home or building. The system uses pre-defined information about network resources and their relationships to trace a fault's root cause, moving beyond simple log analysis to understand systemic dependencies (Compl. ¶107; ’565 Patent, col. 1:15-21).
• Asserted Claims: The complaint does not specify which claims of the ’565 Patent are asserted (Compl. ¶110).
• Accused Features: The complaint accuses Amazon CloudWatch and AWS X-Ray. These are AWS's monitoring, observability, and distributed tracing services, which are used by customers to diagnose performance issues and identify the root cause of errors in complex, microservice-based applications (Compl. ¶¶37; Compl. ¶39; Compl. ¶112).

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

• Technology Synopsis: The patent discloses an apparatus for managing and dynamically configuring a Content Delivery Network (CDN). The apparatus acts as a central manager that receives configuration requests and resource information, and based on this data, it configures an "overlay network" to deliver content on behalf of a service provider (Compl. ¶126; ’934 Patent, abstract).
• Asserted Claims: The complaint does not specify which claims of the ’934 Patent are asserted (Compl. ¶129).
• Accused Features: The complaint accuses Amazon CloudFront. CloudFront is AWS's global CDN service, which customers configure to deliver their web content, video, and APIs from a network of "edge locations" to end-users with low latency (Compl. ¶¶26; Compl. ¶131).

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are a suite of Amazon's cloud services, including Amazon Simple Storage Service (S3), Amazon Elastic Compute Cloud (EC2) and the underlying AWS Nitro System, Amazon CloudFront, Amazon CloudWatch, and AWS X-Ray (Compl. ¶16).

Functionality and Market Context

• The complaint describes the accused products as foundational elements of Amazon Web Services (AWS). S3 is an object storage service designed for high durability by redundantly storing data across multiple physical locations (Compl. ¶¶32-33). EC2 provides virtual servers for computing, with the Nitro System being the underlying platform that offloads virtualization and security functions to dedicated hardware to improve performance (Compl. ¶¶17, 19). CloudFront is a global CDN that accelerates content delivery (Compl. ¶26), while CloudWatch and X-Ray provide monitoring and distributed tracing to help developers diagnose application failures (Compl. ¶¶37, 39).
• The complaint alleges these services are not only core to AWS's reported $107.6 billion in 2024 sales but are also critical infrastructure for major internet companies such as Netflix, Airbnb, and Twitch (Compl. ¶¶22-25; Compl. ¶42).

IV. Analysis of Infringement Allegations

The complaint references claim chart exhibits that were not provided with the filing; therefore, the infringement theories are summarized below in prose based on the complaint’s narrative allegations.

• ’864 Patent Infringement Allegations (vs. Amazon S3):
  The complaint alleges that Amazon S3’s architecture for data durability infringes the ’864 Patent (Compl. ¶¶70, 74). The infringement theory appears to be that when a server or storage device fails within an AWS Availability Zone (AZ), S3’s automated resilience processes constitute the claimed distributed error recovery method. In this analogy, the other AZs or data centers that hold redundant copies of the data act as the claimed "other data server groups," which participate in reconstructing the lost data, thereby practicing the steps of claim 1. The complaint cites Amazon's own technical documentation on architecting for high availability as evidence that this infringing method is performed (Compl. ¶75).
• ’846 Patent Infringement Allegations (vs. Amazon EC2 with Nitro System):
  The complaint alleges that Amazon EC2, particularly when utilizing the AWS Nitro System, infringes the ’846 Patent (Compl. ¶¶91, 93, 96). The theory suggests a mapping where EC2 instances equipped with security features like Nitro Enclaves function as the claimed "secure server type," capable of processing encrypted code in an isolated environment. Standard EC2 instances are alleged to be the "general server type." The AWS control plane, which manages and allocates these different instance types, is alleged to function as the claimed "management server" that directs workloads based on their security requirements (Compl. ¶¶91-94).
• Identified Points of Contention:
  • Scope Questions: For the ’864 Patent, a potential issue is whether the term "data server group," as defined in the patent, can be construed to encompass a broad architectural concept like an AWS Availability Zone. For the ’846 Patent, a question is whether the functional distinction between a standard EC2 instance and one using a Nitro Enclave maps to the specific claimed architecture of "general" and "secure" server types.
  • Technical Questions: A key technical question for the ’864 Patent is whether S3’s internal, automated data-mirroring and self-healing mechanisms practice the specific, ordered steps of the claimed method (e.g., receiving a "chunk list," "requesting" data). For the ’846 Patent, a question will be whether the AWS control plane operates as the claimed "management server" by making the specific type of execution requests required by the claim.

No probative visual evidence provided in complaint.

V. Key Claim Terms for Construction

• Term: "data server groups" (’864 Patent, Claim 1)
  • Context and Importance: The claim requires that the recovery process be initiated by and performed in "data server groups other than a data server group including a failed data server." The definition of a "data server group" is therefore central to determining if the accused S3 architecture, with its concepts of Availability Zones and regions, meets this structural limitation.
  • Intrinsic Evidence for a Broader Interpretation: The patent states that "each of the plurality of data server groups may include a plurality of data servers," which suggests flexibility in how a group can be constituted (’864 Patent, col. 2:19-21). This could support an argument that any logical or physical grouping, such as an AZ, qualifies.
  • Intrinsic Evidence for a Narrower Interpretation: The specification provides an example where "four data servers 20a, 20b, 20c, and 20n configure a data server group" to store data and parity for a single file stripe (’864 Patent, col. 4:62-64). This could support a narrower construction where a "group" is defined by its participation in a specific RAID-like data protection scheme, not just by its network location.
• Term: "secure server type" (’846 Patent, Claim 1)
  • Context and Importance: The entire inventive concept of the ’846 Patent rests on the dichotomy between a "secure server type" and a "general server type." Whether Amazon's EC2 offerings meet this limitation will depend on how this term is construed. Practitioners may focus on this term because it is the linchpin of the infringement allegation against the EC2/Nitro system.
  • Intrinsic Evidence for a Broader Interpretation: The claim functionally defines the term: "the secure server type of server decrypts an encrypted code of a program provided from a client" (’846 Patent, claim 1). An argument could be made that any server capable of performing this function, such as one with a Nitro Enclave, qualifies, regardless of its underlying implementation.
  • Intrinsic Evidence for a Narrower Interpretation: The specification states that secure servers "retain the public key/private key authentication certificate and share the public key/private key therebetween" (’846 Patent, col. 4:51-54). This language could be used to argue that the term is limited to servers participating in a specific, shared key management infrastructure as described in the patent, which may be narrower than the functionality offered by the accused products.

VI. Other Allegations

• Indirect Infringement: For all asserted patents, the complaint alleges induced infringement. The basis for this allegation is that Amazon provides its customers with extensive documentation, technical support, user guides, and marketing materials that allegedly instruct and encourage them to use the accused services in ways that practice the claimed inventions (Compl. ¶¶69, 75, 90, 111, 130). Contributory infringement is also alleged on the basis that the accused services are especially made or adapted for infringing use and are not staple articles of commerce (Compl. ¶¶73, 95, 114, 133).
• Willful Infringement: The complaint alleges willful infringement based on Defendants' knowledge of the patents and their infringing nature "through at least the filing and service of the Complaint" (Compl. ¶¶77, 98, 117, 136). This frames the willfulness allegation as arising from continued infringement after the lawsuit was filed.

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

1. Architectural Mapping: A primary issue will be one of architectural mapping: do the internal, highly complex, and proprietary systems of Amazon’s cloud services perform the specific, structured methods and contain the distinct components recited in the patent claims? Or, does the complaint rely on high-level functional analogies (e.g., an "Availability Zone" is a "data server group") that may not align with the technical reality of how the accused systems are built and operate?
2. Definitional Scope: The case will likely depend on definitional scope, particularly for claim terms such as "data server group" (’864 Patent) and "secure server type" (’846 Patent). The central question for the court will be whether these terms, rooted in the specific embodiments of the patents, can be construed broadly enough to encompass the independently developed and architecturally distinct infrastructure of a modern hyperscale cloud provider.
3. Standing: While the complaint proactively details the licensing and assignment history from ETRI to the plaintiff (Compl. ¶¶2-12), defendants in patent cases involving exclusive licensees frequently challenge whether "all substantial rights" were properly transferred. This could raise a threshold question of whether OptimNet has the legal standing to bring this suit in its own name.