DCT

1:25-cv-01272

NovaCloud Licensing LLC v. Amazon.com Inc

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:25-cv-01272, D. Del., 10/17/2025
  • Venue Allegations: Venue is alleged to be proper in the District of Delaware as both Plaintiff and Defendants are Delaware entities. The complaint further alleges that Amazon maintains a regular and established place of business in the district, including a 3.8 million square foot fulfillment center and other offices.
  • Core Dispute: Plaintiff alleges that Defendants’ cloud computing and content delivery network services infringe six U.S. patents related to network resource allocation, packet distribution, and multimedia file delivery.
  • Technical Context: The patents-in-suit address technologies fundamental to cloud computing infrastructure, including dynamic network routing, load balancing, and adaptive bitrate streaming, which are core components of modern Infrastructure-as-a-Service (IaaS) and content delivery networks.
  • Key Procedural History: The complaint states the asserted patents originated from Ericsson's research portfolio. It alleges that Amazon was made aware of the portfolio in February 2024 during interactions with Ericsson, prior to Plaintiff's acquisition. Plaintiff and Amazon subsequently engaged in licensing discussions from June 2024 through October 2025 but were unable to reach an agreement.

Case Timeline

Date Event
1996-01-01 Amazon.com, Inc. incorporated
2006-01-01 Amazon Web Services, Inc. incorporated
2007-03-01 U.S. Patent No. 8,145,721 Priority Date
2008-01-23 U.S. Patent No. 8,401,028 Priority Date
2011-10-07 U.S. Patent No. RE47,612 Priority Date
2012-03-27 U.S. Patent No. 8145721 Issued
2012-05-04 U.S. Patent No. 8,825,867 Priority Date
2012-10-04 U.S. Patent No. 8,949,206 Priority Date
2013-03-19 U.S. Patent No. 8401028 Issued
2014-03-24 U.S. Patent No. 10,225,173 Priority Date
2014-09-02 U.S. Patent No. 8825867 Issued
2015-02-03 U.S. Patent No. 8949206 Issued
2015-11-24 Original patent for RE47,612 (U.S. 9,197,907) Issued
2017-11-20 U.S. Patent No. RE47,612 Reissue Application Filed
2019-03-05 U.S. Patent No. 10225173 Issued
2019-09-17 U.S. Patent No. RE47,612 Issued
2024-01-01 NovaCloud Licensing, LLC formed
2024-02-01 Amazon becomes aware of the patent portfolio from Ericsson
2024-06-01 NovaCloud initiates discussions with Amazon
2024-08-01 NovaCloud and Amazon meet to discuss patent portfolio
2025-10-17 Complaint Filed

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

U.S. Patent No. 8,145,721 - “Bit Streams Combination of Downloaded Multimedia Files”

  • Patent Identification: U.S. Patent No. 8,145,721, “Bit Streams Combination of Downloaded Multimedia Files,” issued March 27, 2012 (the “’721 Patent”). (Compl. ¶23).

The Invention Explained

  • Problem Addressed: The patent addresses the challenge of making “a more efficient use of available resources when downloading a multimedia file,” particularly over a bandwidth-limited connection. (’721 Patent, col. 1:8-12, as cited in Compl. ¶26).
  • The Patented Solution: The invention proposes a method where a multimedia file is split into two parts for delivery. A first, lower-quality part is coded for immediate streaming, allowing real-time playback. A second, higher-quality part is downloaded separately via a second bit stream. The user device can play the lower-quality version immediately while the full-quality version downloads in the background, with the two parts ultimately being combined to yield the original file. (’721 Patent, abstract; ’721 Patent, col. 2:25-40).
  • Technical Importance: This technique sought to balance the user's desire for instant media playback with the technical and resource constraints of early mobile data networks. (Compl. ¶26).

Key Claims at a Glance

  • The complaint asserts independent claim 1. (Compl. ¶74; Compl. ¶28).
  • Claim 1 of the ’721 Patent recites a method with the following essential elements:
    • Connecting to a user device upon receiving a request for a downloading service.
    • Receiving a request to download a multimedia file via two bit streams.
    • Adapting the file by dividing it into a "first part" with a "first coding" and a "second part" with a "second coding," where the first part is coded based on throughput requirements for streaming.
    • Storing both parts.
    • Setting up separate conditions for streaming the first part and downloading the second part.
    • Streaming the first part and downloading the second part when their respective conditions are fulfilled.
  • The complaint states infringement of claims "including but not limited to Claim 1," reserving the right to assert additional claims. (Compl. ¶74).

U.S. Patent No. 8,401,028 - “Selection of an Edge Node in a Fixed Access Communication Network”

  • Patent Identification: U.S. Patent No. 8,401,028, “Selection of an Edge Node in a Fixed Access Communication Network,” issued March 19, 2013 (the “’028 Patent”). (Compl. ¶31).

The Invention Explained

  • Problem Addressed: The patent describes novel techniques for “allocating pooled nodes to a host in a fixed access network.” (’028 Patent, col. 1:8-10, as cited in Compl. ¶34). It addresses the limitations of static resource pooling, which cannot account for dynamic changes in network conditions, topology, or node load. (’028 Patent, col. 1:46-52).
  • The Patented Solution: The invention discloses a method where a central "selection node" receives a service request. Instead of using static information, this node obtains data from a "dynamically updated database" containing the current "status and capabilities" of a plurality of edge nodes. Based on this real-time data, it selects an optimal edge node to service the request and informs the host. (’028 Patent, abstract; ’028 Patent, col. 2:49-67).
  • Technical Importance: This approach enables dynamic, load-aware, and topology-aware network resource allocation, improving efficiency and reliability over static methods. (Compl. ¶37).

Key Claims at a Glance

  • The complaint asserts independent claim 1. (Compl. ¶80; Compl. ¶36).
  • Claim 1 of the ’028 Patent recites a method with the following essential elements:
    • At a selection node, receiving a request for a network service from a host entity.
    • Obtaining data from a dynamically updated database regarding the status and capabilities of multiple edge nodes.
    • Selecting an edge node from the plurality based on the retrieved data to provide a path for the service.
    • Sending a response to the host entity that identifies the selected edge node.
  • The complaint reserves the right to assert claims beyond Claim 1. (Compl. ¶80).

U.S. Patent No. 8,825,867 - “Two Level Packet Distribution with Stateless First Level Packet Distribution to a Group of Servers and Stateful Second Level Packet Distribution to a Server within the Group”

  • Patent Identification: U.S. Patent No. 8,825,867, “Two Level Packet Distribution with Stateless First Level Packet Distribution to a Group of Servers and Stateful Second Level Packet Distribution to a Server within the Group,” issued September 2, 2014. (Compl. ¶39).
  • Technology Synopsis: The patent discloses a two-level system for distributing network packets to servers while maintaining "stickiness" (ensuring packets from the same flow are processed by the same server). A "stateless" first level directs a packet flow to a group of servers without using stored state information. A "stateful" second level then uses stored state to select a specific server within that group to process the packet. (’867 Patent, abstract; Compl. ¶42; Compl. ¶44).
  • Asserted Claims: Independent Claim 1. (Compl. ¶86).
  • Accused Features: The complaint accuses Amazon’s AWS Global Accelerator and Load Balancer services of implementing this two-level packet distribution architecture. (Compl. ¶14; Compl. Ex. 9).

U.S. Patent No. 8,949,206 - “System and Method for Creating Multiple Versions of a Descriptor File”

  • Patent Identification: U.S. Patent No. 8,949,206, “System and Method for Creating Multiple Versions of a Descriptor File,” issued February 3, 2015. (Compl. ¶47).
  • Technology Synopsis: The technology aims to reduce storage and maintenance costs by avoiding the creation of multiple master versions of a content file. Instead, it creates multiple "descriptor files" (e.g., streaming manifests) by receiving a source descriptor file and a set of rules, and then manipulating the descriptor file based on those rules "without transcoding" the underlying media content. (’206 Patent, abstract; Compl. ¶50).
  • Asserted Claims: Independent Claim 1. (Compl. ¶92).
  • Accused Features: The complaint alleges that AWS Elemental MediaTailor infringes by manipulating media manifests to create personalized versions (e.g., with targeted ads) without re-encoding the primary video content. (Compl. ¶14; Compl. Ex. 10).

U.S. Patent No. 10,225,173 - “Method to Provide Elasticity in Transport Network Virtualisation”

  • Patent Identification: U.S. Patent No. 10,225,173, “Method to Provide Elasticity in Transport Network Virtualisation,” issued March 5, 2019. (Compl. ¶55).
  • Technology Synopsis: The patent describes a method for providing elasticity in a virtualized, multi-domain network. It involves receiving information about the "elasticity capability" of physical network paths, summarizing those physical paths into "virtual links," and then producing a virtual network topology that associates "elasticity parameters" with those virtual links. (’173 Patent, abstract; Compl. ¶58).
  • Asserted Claims: Independent Claim 1. (Compl. ¶98).
  • Accused Features: The complaint targets AWS Elastic Fabric Adapter (EFA), alleging it provides network elasticity by abstracting and managing physical network paths as virtual links with associated performance capabilities. (Compl. ¶14; Compl. Ex. 11).

U.S. Patent No. RE47,612 - “Adaptive Ads with Advertising Markers”

  • Patent Identification: U.S. Patent No. RE47,612, “Adaptive Ads with Advertising Markers,” issued September 17, 2019. (Compl. ¶63).
  • Technology Synopsis: The patent addresses dynamic ad insertion in content streams. The method involves receiving a content stream that may contain advertising markers, segmenting the stream, and determining if client demographic information is available. It then generates a manifest that combines the content segments with advertisements selected based on the available information (e.g., targeted, local, or generic ads). (Compl. ¶66; Compl. ¶68).
  • Asserted Claims: Independent Claim 27. (Compl. ¶104).
  • Accused Features: The complaint accuses AWS Elemental MediaTailor and MediaPackage, which are used for video processing and ad insertion, of infringing the claimed method. (Compl. ¶14; Compl. Ex. 12).

III. The Accused Instrumentality

Product Identification

  • The complaint accuses Amazon's general datacenter and network infrastructure, with a specific focus on a suite of AWS services: Amazon Route 53, AWS Elemental MediaTailor, AWS Elemental MediaPackage, AWS Elastic Fabric Adapter (EFA), and AWS Global Accelerator/Load Balancer. (Compl. ¶14; Compl. ¶72).

Functionality and Market Context

  • The accused services form a significant part of Amazon's cloud computing platform. AWS Elemental MediaPackage and MediaTailor are described as services for just-in-time video packaging, origination, and ad insertion for adaptive bitrate streaming. (Compl. Ex. 7, p. 2; Compl. Ex. 10, p. 3). A diagram in the complaint illustrates MediaTailor's workflow, showing it receiving a manifest, requesting personalized ads from an ad server, and returning a new manifest with ads inserted. (Compl. Ex. 10, p. 3).
  • Amazon Route 53 is identified as a Domain Name System (DNS) service that routes end-user traffic to application endpoints based on factors like geoproximity, latency, and health. (Compl. Ex. 8, p. 2).
  • AWS Global Accelerator and Application Load Balancers are presented as a two-level system for routing and distributing client traffic. (Compl. Ex. 9, p. 2). A network diagram shows the Global Accelerator directing traffic from a mobile device across the AWS global network to regional load balancers. (Compl. Ex. 9, p. 7).
  • AWS EFA is described as a network device for Amazon EC2 instances that provides a high-performance, low-latency network transport protocol designed for elasticity and scalability. (Compl. Ex. 11, p. 2).
  • Collectively, these services are alleged to be integral to modern cloud applications, including streaming services, SaaS applications, and communication tools. (Compl. ¶11).

IV. Analysis of Infringement Allegations

U.S. Patent No. 8,145,721 Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
adapting said multimedia file for downloading via two bit streams, dividing said multimedia file into a first part, which is coded using a first coding, and into a second part, which is coded using a second coding, other that the first coding... AWS services like MediaConvert transcode video into multiple formats and bitrates for adaptive bitrate (ABR) streaming, creating different quality renditions (e.g., a lower-quality stream and a higher-quality stream) that are stored in Amazon S3. ¶76; Compl. Ex. 7, p. 9 col. 2:30-34
wherein said first part is coded on the basis of the throughput requirements for streaming said first bit stream The complaint alleges that lower-quality renditions in the ABR stack are encoded with parameters optimized for streaming and throughput to accommodate viewers with limited bandwidth. ¶76; Compl. Ex. 7, p. 9; Compl. Ex. 7, p. 11 col. 2:41-45
setting up a first set of conditions for streaming said first part via a first bit stream, and a second set of conditions for downloading said second part via a second bit stream AWS MediaPackage and CloudFront are alleged to conditionally deliver different quality renditions based on a viewer's available bandwidth. ¶76; Compl. Ex. 7, p. 13 col. 2:35-40
streaming said first part to said user device when said first set of conditions is fulfilled When a viewer has limited bandwidth (the first condition), the player device automatically switches to and downloads a lower-bitrate rendition from the ABR stack. ¶76; Compl. Ex. 7, p. 15 col. 2:37-40
downloading said second part to said user device when said second set of conditions is fulfilled When a viewer has improved bandwidth (the second condition), the player device automatically switches to and downloads a higher-bitrate rendition. ¶76; Compl. Ex. 7, p. 17 col. 2:39-42
  • Identified Points of Contention:
    • Scope Questions: A primary question may be whether creating multiple, complete, parallel video files for ABR streaming (e.g., 480p, 720p, 1080p versions) meets the claim limitation of "dividing said multimedia file into a first part... and into a second part." The patent's language, which discusses combining the parts to "yield the original multimedia file," may suggest a base layer/enhancement layer structure rather than the parallel renditions used in modern ABR. (’721 Patent, abstract).
    • Technical Questions: The analysis may turn on whether creating different bitrate versions using the same codec (e.g., H.264) constitutes using a "first coding" and a "second coding, other that the first coding" as required by the claim.

U.S. Patent No. 8,401,028 Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
at a selection node, receiving from a host entity a request for a network service Amazon's Route 53 service functions as a selection node that receives DNS service requests from host entities (e.g., a user's web browser). A diagram illustrates this DNS request flow. ¶82; Compl. Ex. 8, p. 3; Compl. Ex. 8, p. 4 col. 2:50-52
obtaining, from a dynamically updated database, data comprising information relating to the status and capabilities of each edge node... Route 53's health check and monitoring system is alleged to be a dynamically updated database that obtains endpoint status and performance data. A provided diagram shows Route 53 monitoring endpoint health. ¶82; Compl. Ex. 8, p. 5 col. 2:52-57
on the basis of the retrieved data, selecting an edge node from the plurality of edge nodes, the selected edge node providing a path between the host entity and the requested network service Amazon’s Route 53 uses the retrieved health and routing data (e.g., latency, geoproximity, health) to select an edge node (endpoint) to serve the request, according to various routing policies. ¶82; Compl. Ex. 8, p. 8 col. 2:57-61
sending a response to the host entity, the response including information identifying the selected edge node Route 53 sends a DNS response to the host's DNS resolver, which includes the IP address of the selected edge node (web server). ¶82; Compl. Ex. 8, p. 10; Compl. Ex. 8, p. 11 col. 2:61-64
  • Identified Points of Contention:
    • Scope Questions: The construction of "fixed access communications network" may be a point of dispute. The parties may argue whether this term, often associated with wired consumer internet access, can be interpreted to cover the global, heterogeneous infrastructure of a cloud provider like AWS.
    • Technical Questions: A key technical question will be whether Amazon's distributed health monitoring system, which informs routing policies, functions as the claimed "dynamically updated database" from which data is "obtain[ed]." An analysis may focus on whether the accused system's integrated monitoring-and-routing architecture matches the claim's sequence of obtaining data from a database and then selecting a node.

V. Key Claim Terms for Construction

’721 Patent

  • The Term: "dividing said multimedia file into a first part... and into a second part"
  • Context and Importance: This term is central to the infringement theory against AWS's adaptive bitrate streaming services. The case may depend on whether creating multiple, distinct, full-length renditions of a file at different quality levels constitutes "dividing" a single file into two complementary "parts" as described in the patent.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent's stated goal is to "make better use of the available resources" on limited connections. (’721 Patent, col. 2:5-7). An argument could be made that creating a low-bitrate "part" for streaming and a high-bitrate "part" for later download, even if they are complete renditions, is a functional form of "dividing" the content delivery to achieve this goal.
    • Evidence for a Narrower Interpretation: The abstract states that the second part is "combined with the first part, in order to yield the original multimedia file." (’721 Patent, abstract). This language may support a narrower construction where the "parts" are non-overlapping components (e.g., a base layer and an enhancement layer) that must be algorithmically combined, rather than standalone, alternative renditions.

’028 Patent

  • The Term: "dynamically updated database"
  • Context and Importance: The infringement allegation hinges on mapping Amazon Route 53's health checking system to this claim term. Practitioners may focus on this term because Amazon's system is a distributed monitoring service that directly influences routing, which may differ architecturally from a conventional database that is separately queried.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification describes the system functionally, stating the selection node "obtains... data relating to a plurality of edge nodes." (’028 Patent, abstract). This could support a broad interpretation where any system that serves as a repository for dynamic status and capability information, regardless of its implementation, qualifies as the "database."
    • Evidence for a Narrower Interpretation: The patent's Figure 1 depicts a "Topology DB" and a "Monitor" as distinct entities that feed information to the "Selection logic." (’028 Patent, Fig. 1). This architectural depiction could be used to argue for a narrower definition requiring a distinct, queryable database, rather than an integrated monitoring and routing-policy system.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges inducement to infringe for all asserted patents. The basis for this allegation is that Amazon actively encourages its customers to use the accused services in an infringing manner through its "publications," which include developer guides, user manuals, and other instructional materials. (Compl. ¶77; Compl. ¶83; Compl. ¶89; Compl. ¶95; Compl. ¶101; Compl. ¶107).
  • Willful Infringement: While the complaint does not use the term "willful," it pleads facts that may support a claim for enhanced damages under 35 U.S.C. § 284. (Compl., p. 22, prayer 4). The complaint alleges that Amazon had pre-suit knowledge of the entire asserted patent portfolio as of February 2024, arising from licensing discussions that took place before the complaint was filed. (Compl. ¶17; Compl. ¶25; Compl. ¶33; Compl. ¶41; Compl. ¶49; Compl. ¶57; Compl. ¶65).

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

This dispute will likely center on questions of both technical scope and architectural equivalence, framed by patents filed during the rise of cloud computing and now asserted against a mature, hyperscale cloud platform.

  • A core issue will be one of definitional scope: Can the '721 Patent's concept of "dividing" a file into two complementary "parts" for sequential delivery be construed to cover modern adaptive bitrate streaming, which involves creating multiple, parallel, standalone video "renditions"?
  • A key evidentiary question will be one of architectural equivalence: Does Amazon's distributed, real-time health monitoring system, which directly informs DNS routing policies in Route 53, function as the "dynamically updated database" that is "obtain[ed] from" as recited in the '028 Patent, or is there a fundamental mismatch between the claimed sequence of operations and the accused system's integrated architecture?
  • A broader theme across the case will be whether the specific technical implementations described in the asserted patents, originating from an earlier phase of network technology, can be mapped onto the highly abstracted and scaled-out services of a modern cloud infrastructure like AWS.
Loading Complaint