DCT

3:26-cv-10585

Equinix Inc v. NovaCloud Licensing LLC

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 3:26-cv-10585, N.D. Cal., 09/16/2026
  • Venue Allegations: Venue is asserted as proper in the Northern District of California because Defendant NovaCloud Licensing, LLC maintains a regular and established place of business in the district and is subject to personal jurisdiction there.
  • Core Dispute: Plaintiff Equinix, Inc. seeks a declaratory judgment that its network infrastructure and monitoring products do not infringe five U.S. patents owned by Defendant NovaCloud Licensing, LLC related to network management, configuration, and monitoring.
  • Technical Context: The technology at issue involves foundational elements of modern digital infrastructure, including the dynamic selection of network resources, policy-based network management, cross-domain VPN configuration, and hierarchical system configuration.
  • Key Procedural History: Plaintiff Equinix initiated this declaratory judgment action following a six-month period of communications with Defendant NovaCloud. Equinix alleges that NovaCloud, a non-practicing entity that acquired the patents from Ericsson, is engaged in a broad litigation campaign against Equinix's industry peers. The action was precipitated by a July 17, 2026 letter in which NovaCloud allegedly identified specific claims of the five patents-in-suit as "relevant" to specific Equinix products, which Equinix characterizes as an effective charge of infringement creating a justiciable controversy.

Case Timeline

Date Event
2004-06-30 U.S. Patent No. 7,869,447 Priority Date
2005-04-08 U.S. Patent No. 8,606,738 Priority Date
2006-02-17 U.S. Patent No. 8,407,348 Priority Date
2008-01-23 U.S. Patent No. 8,401,028 Priority Date
2011-01-11 U.S. Patent No. 7,869,447 Issues
2013-03-19 U.S. Patent No. 8,401,028 Issues
2013-03-26 U.S. Patent No. 8,407,348 Issues
2013-12-10 U.S. Patent No. 8,606,738 Issues
2014-12-29 U.S. Patent No. 9,847,903 Priority Date
2017-12-19 U.S. Patent No. 9,847,903 Issues
2024-01-01 NovaCloud acquires patent portfolio from Ericsson (approximate date) Compl. ¶11
2025-05-01 NovaCloud begins patent assertion campaign (approximate date) Compl. ¶12
2026-03-01 NovaCloud begins targeting Equinix (approximate date) Compl. ¶13
2026-04-13 NovaCloud emails Equinix's CLO with a draft NDA Compl. ¶13
2026-05-01 Equinix responds with edits to the NDA Compl. ¶16
2026-07-17 NovaCloud sends letter to Equinix's CEO identifying specific patents and claims Compl. ¶18
2026-08-20 Parties hold a videoconference to discuss the NDA Compl. ¶21
2026-09-14 NovaCloud sends follow-up correspondence to Equinix Compl. ¶23
2026-09-16 Complaint for Declaratory Judgment filed Compl. p. 1

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: March 19, 2013

The Invention Explained

  • Problem Addressed: The patent's background section describes the limitations of static and DNS-based methods for "pooling" network resources, where a host selects a gateway or server from a list. These static methods are unable to account for dynamic network conditions like traffic load, node status, or topology changes, which can lead to inefficient resource allocation and poor quality of service (QoS) (’028) Patent, col. 1:12-24; ’028 Patent, col. 2:15-32).
  • The Patented Solution: The invention proposes a "selection node" that acts as a centralized, intelligent decision-maker. This node receives a service request from a host, dynamically retrieves data about the current status and capabilities of multiple "edge nodes" from a database, selects the most appropriate edge node based on that real-time data, and then provides the identity of the selected node back to the host (’028 Patent, abstract; ’028 Patent, col. 2:52-65). This process is illustrated in the signaling flow of Figure 1 (’028 Patent, Fig. 1).
  • Technical Importance: This shift from static configuration to dynamic, data-driven selection was intended to improve network resilience, optimize load balancing, and enable more reliable delivery of QoS-sensitive services (’028 Patent, col. 7:48 - col. 8:6).

Key Claims at a Glance

  • The complaint identifies claim 1 as being asserted by NovaCloud Compl. ¶18 Compl. ¶39
  • The essential elements of independent claim 1 include:
    • At a selection node, receiving from a host entity a request for a network service.
    • Obtaining data from a dynamically updated database relating to the status and capabilities of a plurality of edge nodes.
    • On the basis of the retrieved data, selecting an edge node that provides a path between the host entity and the requested service.
    • Sending a response to the host entity that includes information identifying the selected edge node.
  • The complaint does not explicitly reserve the right to assert dependent claims for this patent, but seeks a declaration of non-infringement for "any claim" of the patent Compl. ¶37

U.S. Patent No. 8,606,738 - "Policy-Based Management in Communication Network"

  • Issued: December 10, 2013

The Invention Explained

  • Problem Addressed: The patent addresses conflicts that arise when a network device—a Policy Enforcement Point (PEP)—must enforce rules from multiple, independent sources of policy, known as Policy Decision Points (PDPs). For example, a user's privacy preferences (one PDP) may conflict with an operator's business rules (another PDP), and prior art methods for resolving this were inflexible or overly complex (’738 Patent, col. 3:31-54).
  • The Patented Solution: The invention introduces a new architectural component called a "policy strategy point" (PSP). The PSP acts as a mediator. It receives potentially conflicting decisions from multiple PDPs, applies a configurable "decision strategy" (an algorithm) to reconcile them, and generates a single, authoritative "resulting decision." This final decision is then sent to the PEP to be enforced, as depicted in Figure 3 (’738 Patent, abstract; ’738 Patent, Fig. 3; ’738 Patent, col. 4:25-33).
  • Technical Importance: This architecture decouples policy conflict resolution from policy enforcement, allowing network operators to flexibly manage rules from different stakeholders (e.g., users, regulators, business partners) without hard-coding priorities into network devices.

Key Claims at a Glance

  • The complaint identifies claim 1 as being asserted by NovaCloud Compl. ¶18 Compl. ¶45
  • The essential elements of independent claim 1 include:
    • A policy enforcement point requesting decisions from a plurality of policy decision points through a policy strategy point.
    • Each policy decision point generating a decision.
    • Configuring the policy strategy point with a decision strategy comprising an algorithm for determining a resulting decision.
    • The policy strategy point generating the resulting decision by applying the decision strategy to the received decisions.
    • The policy strategy point communicating the resulting decision to the enforcement point for execution.
  • The complaint does not explicitly reserve the right to assert dependent claims for this patent, but seeks a declaration of non-infringement for "any claim" of the patent Compl. ¶43

U.S. Patent No. 7,869,447 - "Method and System for Multi-Domain Virtual Private Network Configuration"

  • Issued: January 11, 2011
  • Technology Synopsis: The patent addresses the problem of configuring a Virtual Private Network (VPN) that spans multiple, independent network domains. The proposed solution involves systems and methods for domains to provide and exchange information about their internal VPNs, allowing a request to configure a VPN in one domain to be automatically matched with corresponding VPNs in other domains (’447 Patent, abstract; ’447 Patent, col. 1:16-25).
  • Asserted Claims: Claim 1 Compl. ¶18 Compl. ¶51
  • Accused Features: The complaint identifies Equinix Fabric, Fabric Router, and Fabric Cloud Router as the accused products, arguing they operate as a "single-provider network" and do not involve the claimed "at least two VPN provider domains" Compl. ¶18 Compl. ¶51

U.S. Patent No. 8,407,348 - "Monitoring Network Usage"

  • Issued: March 26, 2013
  • Technology Synopsis: The patent describes a method for monitoring a user's network service usage against a Service Level Agreement (SLA). The method collects specific data values over time, including the duration a service was "active," its "average loading," and the duration it was "saturated," each relative to predefined thresholds (’348 Patent, abstract; ’348 Patent, col. 2:3-11). This provides a detailed statistical summary of usage without storing continuous raw data.
  • Asserted Claims: Claim 1 Compl. ¶18 Compl. ¶57
  • Accused Features: The complaint identifies Equinix SmartView as the accused product. It argues that SmartView is a Data Center Infrastructure Monitoring (DCIM) portal for physical assets (e.g., power, temperature) and does not perform the claimed monitoring of a "network service" or its usage characteristics Compl. ¶18 Compl. ¶57

U.S. Patent No. 9,847,903 - "Method and Apparatus for Configuring a Communication System"

  • Issued: December 19, 2017
  • Technology Synopsis: The patent addresses the complexity of configuring systems with many nodes organized into clusters. It proposes a "common configuration server" that manages multiple clusters in a hierarchical structure, allowing lower-level clusters to inherit configurations from parent clusters. Nodes within a cluster are configured to "pull" their configuration from this common server (’903 Patent, abstract; ’903 Patent, col. 2:41-57).
  • Asserted Claims: Claim 1 Compl. ¶18 Compl. ¶63
  • Accused Features: The complaint identifies Equinix Network Edge, Fabric, and Fabric Cloud Router as the accused products. It argues that Equinix does not operate the claimed "configuration server" and instead uses a "push model" to load configurations, which it contends is the opposite of the claimed "pull model" Compl. ¶18 Compl. ¶63

III. The Accused Instrumentality

Product Identification

  • The complaint seeks a declaratory judgment of non-infringement for Equinix Network Edge, Equinix Fabric, Fabric Router, Equinix Fabric Cloud Router, and Equinix SmartView Compl. ¶30

Functionality and Market Context

  • The complaint describes the accused products as "general-purpose data center, networking, interconnection, and infrastructure monitoring offerings" that serve a wide variety of enterprise customers Compl. ¶30 Equinix positions itself as a "global digital infrastructure company" operating International Business Exchange (“IBX”) data centers that provide colocation and interconnection services to major cloud and network providers Compl. ¶10
  • The functionality of the specific services is described in the context of denying infringement:
    • Network Edge is characterized as a "one-time provisioning platform for virtual network devices triggered by customer orders through a portal or API," rather than a runtime service Compl. ¶39
    • Equinix Fabric, Fabric Router, and Fabric Cloud Router are described as forming a "single-provider network, centrally orchestrated end to end by Equinix" Compl. ¶51
    • SmartView is described as a "data center infrastructure monitoring (DCIM) portal that monitors the physical data center environment like power draw, temperature and humidity" Compl. ¶57
  • No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

'028 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Non-Infringing Functionality Complaint Citation Patent Citation
at a selection node, receiving from a host entity a request for a network service; Equinix's Network Edge is described as a "one-time provisioning platform" where customers place orders, not a runtime service that receives a "request for a network service" from a "host entity." ¶39 col. 11:49-51
sending a response to the host entity, the response including information identifying the selected edge node. The complaint states that in the Network Edge offering, "No identity of a selected physical server is returned to a requesting host." ¶¶39-40 col. 12:2-4
  • Identified Points of Contention:
    • Scope Question: A primary point of contention may be whether a customer-initiated order for a virtual device via a portal or API, which is a provisioning action, falls within the scope of the claim term "receiving from a host entity a request for a network service." The complaint frames this as a distinction between a "provisioning platform" and a "runtime service" Compl. ¶39, raising the question of whether the claim is limited to dynamic, real-time requests from an active machine.
    • Technical Question: The complaint asserts that the identity of a selected physical server is not returned Compl. ¶40 A factual question for the court will be what information is, in fact, returned to the customer or end-user system in response to a provisioning order and whether that information constitutes "information identifying the selected edge node" as required by the claim.

'738 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Non-Infringing Functionality Complaint Citation Patent Citation
a policy enforcement point associated with a plurality of policy decision points Equinix's Network Edge is alleged to implement "ordinary access control lists (ACLs) applied in a traditional manner at a single gateway," not a system with an enforcement point associated with multiple decision points. ¶¶45-46 col. 7:12-16
a policy strategy point that comprises an algorithm for determining a resulting decision The complaint alleges that Network Edge "does not include a policy strategy point that reconciles conflicting decisions using a configurable algorithm." ¶¶45-46 col. 7:24-29
  • Identified Points of Contention:
    • Architectural Question: The core dispute for this patent appears to be a fundamental mismatch in architecture. The case may turn on whether Equinix's use of "ordinary access control lists (ACLs)" and "role-based access controls" Compl. ¶¶45-46 can be characterized as implementing the patent's specific, multi-component structure of a PEP, multiple PDPs, and a mediating PSP, or if they represent a distinct and non-infringing technical approach.
    • Functional Question: Even if some components of Equinix's system could be mapped to the claimed "points," a key question will be whether any component actually performs the claimed function of the "policy strategy point"—specifically, using a configurable algorithm to reconcile conflicting decisions from multiple sources Compl. ¶45

V. Key Claim Terms for Construction

  • The Term: "request for a network service" (’028 Patent, claim 1)
  • Context and Importance: The definition of this term is central to the infringement analysis of the ’028 Patent. Equinix characterizes its accused Network Edge product as a "one-time provisioning platform" and not a "runtime service" Compl. ¶39 Practitioners may focus on whether this term is limited to a runtime, dynamic network event or if it can be read more broadly to include a customer's initial order to provision a service.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification provides examples of requests such as a DNS query or a DHCP query (’028 Patent, col. 5:44-46; ’028 Patent, col. 5:60-63), which are standard network initiation events that could be seen as aligning with a provisioning context.
    • Evidence for a Narrower Interpretation: The patent's background criticizes "static pooling" and emphasizes the need to account for dynamic "current network conditions" and "load on the transport network" (’028 Patent, col. 2:25-28). This suggests the "request" is intended to trigger a selection based on real-time conditions, which is more aligned with a runtime event than a one-time provisioning order.
  • The Term: "policy strategy point" (’738 Patent, claim 1)
  • Context and Importance: Equinix's non-infringement position for the ’738 Patent hinges on its argument that its products do not contain this element Compl. ¶45 The viability of the infringement case will depend on whether any part of Equinix's system can be found to perform the function of this claimed point.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent functionally describes the strategy point as being arranged for "generating the resulting decision, by applying said decision strategy on said decisions" (’738 Patent, col. 5:12-15). An argument could be made that any logic, however simple, that resolves conflicts between different rules could meet this functional description.
    • Evidence for a Narrower Interpretation: The patent's abstract and figures consistently depict the "policy strategy point" as a distinct architectural entity that mediates between a single enforcement point and a "plurality of policy decision points" (’738 Patent, abstract; ’738 Patent, Fig. 3). The specification explains its purpose is to "resolve said conflicts" from different PDPs (’738 Patent, col. 5:30-39), suggesting it is more than just standard rule processing and is specifically designed for reconciling inputs from multiple, independent policy sources.

VI. Other Allegations

  • Indirect Infringement: The complaint seeks a declaratory judgment that Equinix has not infringed "under any theory of infringement," which includes "indirectly (whether contributorily or by inducement)" Compl. ¶38 Compl. ¶41 Compl. ¶44 Compl. ¶50 Compl. ¶56 Compl. ¶62 As a complaint for declaratory judgment, it does not plead facts that would support an indirect infringement claim, as pleading such facts would be the responsibility of the patentee in a potential counterclaim.
  • Willful Infringement: The complaint does not mention willful infringement. It does, however, request a finding that the case is "exceptional" under 35 U.S.C. § 285 for the purpose of awarding attorneys' fees Compl., Prayer for Relief ¶c

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

  • A primary issue will be one of architectural mapping: does the functionality of Equinix's commercial services—such as the "one-time provisioning platform" for virtual devices Compl. ¶39 or the monitoring of physical data center assets Compl. ¶57—align with the specific, multi-element system architectures recited in the patent claims, or is there a fundamental mismatch in technical design and operation?
  • A second key issue will be one of definitional scope: can claim terms like "request for a network service" (’028 Patent) or a server from which nodes "pull" configuration (’903 Patent) be construed broadly enough to cover the alleged operational models of Equinix's products, which are characterized as provisioning platforms and "push" configuration systems Compl. ¶39 Compl. ¶63?
  • Finally, a threshold procedural question for the court will be to assess the justiciability of the dispute. The court will need to determine if NovaCloud's communications, culminating in the letter identifying specific patents, claims, and products as "relevant," created a "real and immediate controversy" sufficient to support declaratory judgment jurisdiction (Compl. ¶¶18-19; Compl. ¶26).