Novacloud Licensing LLC v. Microsoft Corp

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: NovaCloud Licensing, LLC (Delaware)
  • Defendant: Microsoft Corporation (Washington)
  • Plaintiff's Counsel: McKOOL SMITH, P.C.
• Case Identification: 2:25-cv-01228, E.D. Tex., 02/27/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Microsoft conducts substantial business in the district, including operating data centers, owning millions of dollars in property, leasing "store-within-a-store" retail locations, and offering its accused services to customers within the district.
• Core Dispute: Plaintiff alleges that Defendant's Azure cloud computing infrastructure and associated services infringe five U.S. patents related to network resource management, packet distribution, and cloud application configuration.
• Technical Context: The technology at issue concerns methods for managing and optimizing large-scale data centers and cloud networks, which are foundational to modern cloud computing services.
• Key Procedural History: The complaint states that the asserted patents originated from Ericsson's research. It notes that Microsoft interacted with Ericsson in February 2024 regarding this patent portfolio and that Plaintiff NovaCloud engaged in unsuccessful licensing discussions with Microsoft between June 2024 and October 2025.

Case Timeline

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

U.S. Patent No. 8,401,028 - Selection of an Edge Node in a Fixed Access Communication Network (Issued Mar. 19, 2013)

The Invention Explained

• Problem Addressed: The patent's background section describes the inefficiency of conventional "static pooling" and DNS-based methods for selecting network gateway or server nodes Compl. ¶32 '028 Patent, col. 1:12-2:46 These static methods cannot account for dynamic network conditions, such as the current load on network elements, which can lead to suboptimal performance and resource allocation Compl. ¶35 '028 Patent, col. 2:24-34
• The Patented Solution: The invention proposes a centralized "selection node" that makes an intelligent, dynamic choice of an "edge node" (e.g., a server or gateway) for a host requesting a network service '028 Patent, abstract This selection node receives a request, obtains data from a "dynamically updated database" containing information about the status and capabilities of the various edge nodes, and selects the most appropriate node based on that current data before responding to the host '028 Patent, col. 3:4-10 '028 Patent, claim 1
• Technical Importance: This approach enables load-aware resource allocation in distributed networks, improving efficiency and reliability by directing traffic to nodes best equipped to handle it at a given moment.

Key Claims at a Glance

• The complaint asserts infringement of at least Claim 1 Compl. ¶34 Compl. ¶71
• The essential elements of independent Claim 1 include:
  • At a selection node, receiving a request for a network service from a host entity.
  • Obtaining data from a dynamically updated database, where the data relates to the status and capabilities of a plurality of 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 that identifies the selected edge node.
• The complaint generally alleges infringement of "at least one claim," preserving the right to assert others Compl. ¶2

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 Sep. 2, 2014)

The Invention Explained

• Problem Addressed: The patent background discusses the scalability challenges of traditional "stateful" server load balancing '867 Patent, col. 1:58-2:14 Maintaining a state table for every connection can exhaust memory and processing resources, especially with high traffic volumes, and synchronizing state for redundancy is complex '867 Patent, col. 2:15-38
• The Patented Solution: The invention discloses a two-level system for distributing packets to servers '867 Patent, abstract A "static first level" module uses a stateless method (e.g., a hash function) to select a group of servers for an incoming packet flow. The packet is then sent to a "distributed stateful second level" system associated with that group, which uses a state table to select a specific server within the group, thereby maintaining "stickiness" for the flow '867 Patent, col. 2:40-3:33 This architecture distributes the burden of state management.
• Technical Importance: This hybrid approach allows load balancing systems to scale more efficiently by separating the coarse-grained, stateless group selection from the fine-grained, distributed stateful server selection.

Key Claims at a Glance

• The complaint asserts infringement of at least Claim 1 Compl. ¶41 Compl. ¶80
• The essential elements of independent Claim 1 include:
  • Receiving a packet at a static first level packet distribution module.
  • Statically selecting a group of servers for the packet without using state that assigns the flow to the group.
  • Distributing the packet to a distributed stateful second level packet distribution system implemented on distinct hardware.
  • Statefully selecting a server from the selected group by accessing state that assigns the flow to that server.
  • Distributing the packet to the selected server.
• The complaint generally alleges infringement of "at least one claim," preserving the right to assert others Compl. ¶3

U.S. Patent No. 9,900,262 - Methods, Nodes and Computer Program for Enabling of Resource Component Allocation (Issued Feb. 20, 2018)

• Technology Synopsis: The patent discloses techniques for "improved resource management and resource utilization in shared environments" '262 Patent, col. 4:9-11 The method involves a resource manager determining a performance metric for an application, instructing host systems to measure that metric, receiving "resource frames" containing the measurements from the hosts, and then determining resource allocation based on an "operations profile" formed from these frames '262 Patent, abstract '262 Patent, claim 1
• Asserted Claims: Claim 1 is asserted Compl. ¶48 Compl. ¶89
• Accused Features: The complaint accuses Microsoft's cloud infrastructure and services, such as Azure Monitor and Azure Research Manager, which are used for performance monitoring and resource management Compl. ¶13

U.S. Patent No. 10,225,173 - Method to Provide Elasticity in Transport Network Virtualisation (Issued Mar. 5, 2019)

• Technology Synopsis: The patent discloses a method to provide "elasticity" in a virtualized, multi-domain network '173 Patent, abstract The method involves receiving information about the "elasticity capability" of physical network paths, summarizing these physical paths into "virtual links," and then producing a virtual network topology where these virtual links are associated with elasticity parameters that represent the underlying physical paths' ability to expand or contract resources '173 Patent, col. 2:6-13 '173 Patent, claim 1
• Asserted Claims: Claim 1 is asserted Compl. ¶55 Compl. ¶98
• Accused Features: The complaint accuses Microsoft's cloud infrastructure and services, including Azure Traffic Manager and Microsoft OneWAN, which manage virtual networks and traffic across different network domains Compl. ¶13

U.S. Patent No. 10,430,172 - Re-Configuration in Cloud Computing Environments (Issued Oct. 1, 2019)

• Technology Synopsis: The patent discloses a system for the "re-configuration of hosted applications in cloud computing environments" '172 Patent, col. 1:14-15 It describes a "software template" containing a flow of actions for tasks like scaling. This template has a non-editable portion (defined by the cloud manager) and a portion where the application itself can add custom actions via a programming interface, enabling dynamic and coordinated re-configuration between the cloud platform and the application '172 Patent, abstract '172 Patent, claim 1
• Asserted Claims: Claim 1 is asserted Compl. ¶62 Compl. ¶107
• Accused Features: The complaint accuses Microsoft's Azure cloud infrastructure, which uses templating systems for defining, deploying, and re-configuring cloud applications and infrastructure Compl. ¶66

III. The Accused Instrumentality

Product Identification

The complaint identifies the accused instrumentalities generally as "Microsoft's datacenter and network infrastructure and/or cloud computing services" Compl. ¶66 Specific examples named include Azure Traffic Manager, Azure Application Gateway for Containers, Azure Monitor, Microsoft OneWAN, and Azure Research Manager Compl. ¶13

Functionality and Market Context

The accused services form the backbone of Microsoft's Azure cloud platform, providing Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS) offerings Compl. ¶10 Functionally, these services are alleged to manage network traffic routing, distribute workloads across servers, monitor application and infrastructure performance, and dynamically allocate or reconfigure resources within Microsoft's global network of data centers Compl. ¶13 Compl. ¶66 The complaint supports its venue allegations by referencing Microsoft's physical data center presence in the Eastern District of Texas Compl. ¶27 Compl. ¶28 Compl. ¶29 A screenshot from the Collin County Appraisal District website shows Microsoft Corporation's property at an Aligned Data Center in Plano, Texas Compl. p. 4

IV. Analysis of Infringement Allegations

The complaint references, but does not include, claim chart exhibits detailing the infringement allegations Compl. ¶71 Compl. ¶80 The narrative infringement theory is summarized below.

'028 Patent Infringement Allegations

The complaint alleges that Microsoft's Azure infrastructure, particularly services like Azure Traffic Manager, infringes Claim 1 of the '028 Patent Compl. ¶71 The theory suggests that when a user requests a cloud service, Microsoft's system acts as a "selection node" by receiving the request, obtaining real-time data on the "status and capabilities" (e.g., latency, load, health) of its various global edge nodes or data centers from a "dynamically updated database," and using this data to select an optimal node to serve the user. The system then sends a response identifying that selected node, allowing the user to connect Compl. ¶34 Compl. ¶71

'867 Patent Infringement Allegations

The complaint alleges that Microsoft's infrastructure, such as the Azure Application Gateway, infringes Claim 1 of the '867 Patent Compl. ¶80 The infringement theory posits that Microsoft's services employ a two-level distribution method. A first-level component statelessly selects a "group of servers" (e.g., an Azure backend pool) for a given data flow. The data is then distributed to a stateful second-level system, operating on distinct hardware, which accesses state information to select a specific server within that pool to process the flow, thereby maintaining session "stickiness" Compl. ¶41 Compl. ¶80

Identified Points of Contention

• Scope Questions: A primary point of contention for both the '028 and '867 patents may be whether terms conceived for earlier network architectures can be read onto a modern, virtualized, software-defined cloud platform. For example, a question may arise as to whether Azure's distributed traffic management system constitutes a "selection node" as contemplated by the '028 Patent. For the '867 Patent, a question may be whether the accused system's first-level selection is truly "static" as defined by the claim, which requires that the selection "does not involve using state."
• Technical Questions: The analysis may focus on the specific implementation of the accused Azure services. For the '028 Patent, a question is what evidence the complaint provides that Azure consults a "dynamically updated database" of node status and capabilities in the manner required by the claim. For the '867 Patent, a question is whether the first and second levels of packet distribution are implemented on "hardware that is distinct," a term whose meaning could be contested in a highly virtualized cloud environment.

V. Key Claim Terms for Construction

The Term: "dynamically updated database" ('028 Patent, Claim 1)

• Context and Importance: This term is central to the claimed invention's departure from prior static methods. The dispute will likely focus on the meaning of "dynamically updated." Practitioners may focus on this term because its construction will determine whether Azure's methods of monitoring data center health and performance-which may involve periodic polling, event-driven updates, or other complex mechanisms-fall within the claim scope.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification describes the database as containing topology, status, and capability information, and notes it is "dynamically updated" without imposing a specific mechanism or frequency, which may support a broad construction covering any non-static information source '028 Patent, col. 8:56-62
  • Evidence for a Narrower Interpretation: Embodiments describe specific update methods, such as a "Database synchronization function" that listens to OSPF advertisements '028 Patent, col. 9:4-14 This could be used to argue that the term implies a more specific, protocol-driven, real-time update mechanism.

The Term: "statically selecting" ('867 Patent, Claim 1)

• Context and Importance: This term defines the novelty of the first distribution level. The claim clarifies it as a selection that "does not involve using state that assigns the first packet of the flow to the selected group of servers." The case may turn on what constitutes "state" in this context.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent contrasts its "stateless" approach with prior art that uses a state table lookup for every connection '867 Patent, col. 2:5-14 This may support an interpretation where any selection method that avoids a per-flow state table (such as a hash) is "static."
  • Evidence for a Narrower Interpretation: The patent contrasts the "static first level" with the "stateful second level" '867 Patent, abstract A defendant may argue that complex, configurable routing rules in a modern load balancer, even if not a per-flow state table, constitute a form of "state" that goes beyond the simple, stateless selection described in the patent's embodiments.

VI. Other Allegations

Indirect Infringement

The complaint alleges inducement of infringement for all five patents, stating that Microsoft encourages its customers and users to use the accused services in an infringing manner through its "publications" and user documentation Compl. ¶72 Compl. ¶81 Compl. ¶90 Compl. ¶99 Compl. ¶108

Willful Infringement

Willfulness is alleged for all asserted patents. The complaint bases this allegation on Microsoft's awareness of the patents and their infringement "at least as of the filing of this Complaint" Compl. ¶73 Compl. ¶82 Compl. ¶91 Compl. ¶100 Compl. ¶109 The complaint also notes pre-suit interactions between Microsoft and Ericsson, and later between Microsoft and NovaCloud, concerning the patent portfolio, which may be used to argue for pre-suit knowledge Compl. ¶14 Compl. ¶15

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

1. Definitional Scope: A core issue will be one of definitional scope: can claim terms rooted in the context of prior-generation networking, such as the '028 patent's "selection node" or the '867 patent's "statically selecting," be construed to read on the highly distributed, virtualized, and software-defined architecture of a modern cloud platform like Microsoft Azure?
2. Evidentiary Mapping: A key evidentiary question will be one of functional mapping: what evidence will be presented to show that the complex, multi-layered operations of Azure services perform the specific, ordered steps required by the asserted method claims, particularly regarding the source and timing of data used for decisions (for the '028 patent) and the hardware separation between logical functions (for the '867 patent)?
3. Pre-Suit Knowledge and Willfulness: The infringement analysis will likely be influenced by the factual record of pre-suit communications. A central question for willfulness and damages will be what specific knowledge of the asserted patents and their alleged infringement can be established from Microsoft's 2024 interaction with Ericsson and the subsequent licensing discussions with NovaCloud.