DCT

7:26-cv-00388

High Iq Networks LLC v. Dell Tech Inc

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 7:26-cv-00388, W.D. Tex., 09/22/2026
  • Venue Allegations: Plaintiff alleges venue is proper because Defendant Dell Technologies Inc. is incorporated in Texas and has its principal place of business in Round Rock, Texas, within the Western District of Texas, thereby residing in the district. Venue is also alleged for both Defendants based on their commission of infringing acts and maintenance of a regular and established place of business within the district, including their global headquarters.
  • Core Dispute: Plaintiff alleges that Defendant’s networking switches, modular server chassis, and associated operating systems infringe six patents related to carrier-grade Ethernet transport, ring network architectures, and network management.
  • Technical Context: The technology at issue addresses methods for improving the efficiency, reliability, and security of modern packet-based data networks, which form the backbone of data centers and enterprise infrastructure.
  • Key Procedural History: The complaint asserts six patents, three of which have expired (U.S. Patent Nos. 6,731,607; 6,952,397; 8,009,684), for which Plaintiff seeks damages for infringement that occurred during their statutory terms. The complaint notes that some of the accused technology was acquired by Dell through its 2011 acquisition of Force10 Networks.

Case Timeline

Date Event
2000-08-01 ’607 Patent Priority Date
2001-06-07 ’397 Patent Priority Date
2004-05-04 ’607 Patent Issue Date
2005-10-04 ’397 Patent Issue Date
2006-03-02 ’931 and ’684 Patents Priority Date
2006-08-22 ’303 Patent Priority Date
2007-03-08 ’673 Patent Priority Date
2010-02-09 ’303 Patent Issue Date
2010-10-05 ’931 Patent Issue Date
2011 Dell acquires Force10 Networks
2011-01-25 ’673 Patent Issue Date
2011-08-30 ’684 Patent Issue Date
2020-06 Dell OME-M Version 1.20.00 with switch replacement API released
2022-10-19 ’607 Patent Expiration Date
2023-10-31 ’397 Patent Expiration Date
2026-03-02 ’684 Patent Expiration Date
2026-07-01 Dell Technologies Inc. redomesticates from Delaware to Texas
2026-09-22 Complaint Filing Date
2028-01-31 ’303 Patent Expiration Date
2028-06-22 ’931 Patent Expiration Date
2029-01-20 ’673 Patent Expiration Date

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

U.S. Patent No. 7,660,303 - Point-to-Multipoint Functionality in a Bridged Network

  • Patent Identification: U.S. Patent No. 7,660,303, "Point-to-Multipoint Functionality in a Bridged Network," issued February 9, 2010 Compl. ¶25

The Invention Explained

  • Problem Addressed: In standard Layer-2 bridged networks, all connected devices can typically communicate with one another (multipoint-to-multipoint). However, in certain applications like ISP access networks, it is desirable to prevent direct communication between different customers for security reasons, allowing them to communicate only with the central ISP gateway. ’303 Patent, col. 1:46-60
  • The Patented Solution: The invention configures switch interfaces as either a "first type" (e.g., a "hub" connected to the main network) or a "second type" (e.g., "spokes" connected to customers). It then applies "type indications" to data frames based on their ingress interface. Forwarding rules are enforced based on these indications: frames from spokes are prevented from being sent to other spokes but are allowed to go to hubs. This effectively creates a secure point-to-multipoint topology on top of a standard bridged network. ’303 Patent, abstract ’303 Patent, col. 2:38-60
  • Technical Importance: This approach allowed network operators to enforce security and isolation between subscribers on a shared Layer-2 network without the added complexity and management overhead of provisioning a separate virtual network for each subscriber Compl. ¶¶4-6

Key Claims at a Glance

  • The complaint asserts independent apparatus claim 11 and its method counterpart, claim 1 Compl. ¶41
  • Essential elements of independent claim 11 include:
    • A group of switches coupled in a Layer-2 bridged network.
    • Network interfaces configured as at least one "first type" and a plurality of "second type" interfaces.
    • A frame processor operative to:
      • Create and update a forwarding database using a frame's source address and a "type indication."
      • Label received frames with corresponding first and second type indications.
      • Compare a frame's type indication with the destination address's type designation in the database to determine forwarding eligibility.
      • Enforce forwarding rules: permit frames with a first type indication to be transmitted through any interface, while preventing frames with a second type indication from being transmitted through other second-type interfaces.
  • The complaint also affirmatively asserts dependent claims 15, 16, and 17 Compl. ¶41

U.S. Patent No. 7,808,931 - High Capacity Ring Communication Network

  • Patent Identification: U.S. Patent No. 7,808,931, "High Capacity Ring Communication Network," issued October 5, 2010 Compl. ¶26

The Invention Explained

  • Problem Addressed: Traditional ring network architectures, while reliable, were often limited by the bandwidth capacity of a single ring. As data demands grew, there was a need to scale network capacity beyond what a single ring could provide. ’931 Patent, col. 1:31-41 Compl. ¶¶3-4
  • The Patented Solution: The patent describes a network with multiple, overlapping "concentric" communication rings connecting a plurality of nodes. To send a data packet, an ingress node first identifies the egress node and the set of rings that are common to both. It then selects a specific ring and a direction of travel ("ringlet") on that ring, based on information in the packet's header (e.g., a VLAN ID). By distributing traffic across multiple parallel rings, the total capacity of the network is increased. ’931 Patent, abstract ’931 Patent, col. 2:25-45
  • Technical Importance: This technology provided a way to build high-capacity, resilient ring networks capable of meeting modern bandwidth demands by aggregating the capacity of multiple lower-speed rings Compl. ¶6

Key Claims at a Glance

  • The complaint asserts independent apparatus claim 29 and its method counterpart, claim 1 Compl. ¶66

  • Essential elements of independent claim 29 include:

    • A ring node for a network with at least three communication rings in a "concentric layout," with the node connected to at least three of said rings.
    • At least three line cards arranged to communicate with the respective rings.
    • A network processor arranged to:
      • Accept a data packet and determine its egress ring node.
      • Identify a subset of "common rings" connected to both the ingress and egress nodes.
      • Select, based on a packet header field, a "ringlet" of a ring from among the common rings.
      • Forward the data packet to the egress node over the selected ringlet.

  • The complaint also affirmatively asserts dependent claims 2, 4, and 18, along with independent network claim 15 Compl. ¶66

  • Multi-Patent Capsule: U.S. Patent No. 7,876,673

    • Patent Identification: U.S. Patent No. 7,876,673, "Prevention of Frame Duplication in Interconnected Ring Networks," issued January 25, 2011 Compl. ¶27
    • Technology Synopsis: When two networks are connected by two or more "interconnect nodes" for redundancy, flooded traffic (like broadcast or unknown unicast frames) can be duplicated as each node forwards a copy. The invention describes a system where the interconnect nodes coordinate to select a single forwarder for a given data packet based on a predefined mapping function, preventing the delivery of duplicate frames to the second network Compl. ¶6 ’673 Patent, abstract
    • Asserted Claims: Independent apparatus claim 18, independent method claim 1, and independent network claim 35 are asserted, along with dependent claims 20 and 22 Compl. ¶89
    • Accused Features: The Dell Enterprise SONiC EVPN Multihoming products, which allegedly use a designated forwarder election to prevent duplicate delivery of flooded frames when two or more switches attach a segment to a fabric Compl. ¶8 Compl. ¶37

  • Multi-Patent Capsule: U.S. Patent No. 6,952,397

    • Patent Identification: U.S. Patent No. 6,952,397, "Communication in a Bidirectional Ring Network with Single-Direction Receiving," issued October 4, 2005 Compl. ¶28
    • Technology Synopsis: In bidirectional ring networks, nodes traditionally required two high-speed interfaces to receive traffic from both clockwise and counter-clockwise directions, increasing cost and complexity. This invention proposes a node that can transmit traffic in both directions but is configured to receive traffic from only one direction at any given time, reducing hardware requirements while still allowing the network to reroute traffic upon a failure ’397 Patent, abstract Compl. ¶6
    • Asserted Claims: Independent device claim 9, independent network claim 1, and independent method claim 12 are asserted, along with dependent claim 15 Compl. ¶115
    • Accused Features: The OS6 Ethernet Ring Protection Products, which implement the ITU-T G.8032 standard, allegedly for communication in a bidirectional ring where a "Ring Protection Link" (RPL) owner node blocks traffic from one direction Compl. ¶8 Compl. ¶37 Compl. ¶¶122-123

  • Multi-Patent Capsule: U.S. Patent No. 8,009,684

    • Patent Identification: U.S. Patent No. 8,009,684, "High Capacity Ring Communication Network," issued August 30, 2011 Compl. ¶29
    • Technology Synopsis: As a continuation of the ’931 Patent, this invention also relates to high-capacity networks built from multiple rings. It specifically addresses "asymmetric layouts," where not all nodes connect to all rings. The invention describes a topology with an "anchor ring" common to all nodes, with additional sub-rings connected to only a subset of nodes, providing a more flexible and scalable architecture for network expansion ’684 Patent, abstract Compl. ¶132
    • Asserted Claims: Independent network claim 14 and independent method claim 1 are asserted, along with dependent claims 16 and 18 Compl. ¶132
    • Accused Features: The OS6 Ethernet Ring Protection Products when deployed in multi-ring and sub-ring topologies, which allegedly create an asymmetric layout with a major ring (anchor) and attached sub-rings Compl. ¶37 Compl. ¶136

  • Multi-Patent Capsule: U.S. Patent No. 6,731,607

    • Patent Identification: U.S. Patent No. 6,731,607, "Network Interface Auto-Configuration in an Access Multiplexing System," issued May 4, 2004 Compl. ¶30
    • Technology Synopsis: Replacing a central switching unit in a multi-card chassis typically requires an on-site technician to manually reprogram the new unit. This invention provides a system where backup configuration parameters are stored in the memory of the line cards. Upon startup, a new (replacement) switching unit automatically queries the line cards, retrieves the backup configuration, and updates its own non-volatile memory, thereby restoring service without manual intervention ’607 Patent, abstract Compl. ¶6
    • Asserted Claims: Independent claims 1 and 12 are asserted Compl. ¶150
    • Accused Features: The PowerEdge MX7000 SmartFabric Products, which allegedly feature a "SmartFabric module replacement workflow" where a replacement switching module receives its configuration from the existing "master" module in the fabric Compl. ¶8 Compl. ¶37 Compl. ¶¶156-159

III. The Accused Instrumentality

Product Identification

The complaint identifies several families of Dell networking products, including the Dell PowerSwitch S-Series and N-Series switches, the Dell Networking C9010 chassis switch, and the Dell PowerEdge MX7000 modular chassis Compl. ¶¶7-8 Compl. ¶36 These hardware products are accused in conjunction with the network operating systems that run on them, including Dell SmartFabric OS10, Dell Networking OS9, Dell Networking OS6, and the Dell Enterprise SONiC Distribution Compl. ¶¶7-8.

Functionality and Market Context

  • The complaint alleges that these products are central to Dell's networking business for data center, enterprise, and campus networks Compl. ¶7 The accused functionalities are specific software features within the products' operating systems that Dell markets and supports. These features include:
    • Private VLANs (PVLANs) in OS10, alleged to provide point-to-multipoint communication by creating isolated and promiscuous ports Compl. ¶36a Compl. ¶47
    • Ethernet VPN (EVPN) Multihoming in Dell Enterprise SONiC, alleged to prevent duplicate frame delivery in redundant network connections by electing a designated forwarder Compl. ¶36b Compl. ¶99
    • Force10 Resilient Ring Protocol (FRRP) in OS9, which allegedly allows a switch to participate in up to 255 rings and select the ring for a frame based on its VLAN Compl. ¶8 Compl. ¶36c Compl. ¶7
    • Ethernet Ring Protection (G.8032) in OS6, which provides protection in single-ring, multi-ring, and sub-ring topologies by blocking traffic on a designated Ring Protection Link Compl. ¶36d Compl. ¶122 Compl. ¶136
    • SmartFabric Switch Replacement in the PowerEdge MX7000, a workflow where a replacement switching module allegedly receives its configuration from the master module within the chassis fabric Compl. ¶8 Compl. ¶36e Compl. ¶159
  • The complaint positions these products as part of Dell's Infrastructure Solutions Group, which it states reported approximately $60.8 billion in revenue for the fiscal year ended January 30, 2026 Compl. ¶7

IV. Analysis of Infringement Allegations

'303 Patent Infringement Allegations

Claim Element (from Independent Claim 11) Alleged Infringing Functionality Complaint Citation Patent Citation
Apparatus for communication, comprising a group of switches, which are coupled together in a Layer-2 bridged network... Dell's OS10 Private VLAN Products are documented as spanning a PVLAN domain across two or more switches via an Inter-Switch Link (ISL), which the complaint alleges forms a Layer-2 bridged network. ¶45 col. 1:12-16
...multiple network interfaces, which are configured so that at least one interface... is configured as a first type... and a plurality of other interfaces are configured as a second type... The OS10 software provides a command to configure ports in "promiscuous" mode (alleged first type) or "secondary-port" mode (isolated or community, alleged second type). ¶47 col. 2:40-45
...a frame processor, which is operative: to create an entry comprising a source address...and a number equal to a type indication of the frame to identify the first interface, and to add the entry to a forwarding database... Upon learning a source MAC address, OS10 allegedly creates a forwarding database (MAC address table) entry containing the source address, the receiving interface, and the VLAN number in which the frame arrived, which serves as the type indication. ¶49 col. 8:31-42
...upon receiving frames through the interfaces of the first and second types..., to label the received frames with corresponding first and second type indications... A frame received on a promiscuous port is classified into the primary VLAN, and a frame on an isolated port is classified into the isolated VLAN. The VLAN ID is alleged to be the "type indication" label. ¶56 col. 4:50-55
...to cause the interfaces to forward the frames... by permitting the frames that are labeled with the first type indication to be transmitted through any of the interfaces, while permitting the frames that are labeled with the second type indication to be transmitted through the interfaces of the first type and preventing the frames...from being transmitted through the interfaces of the second type... Dell documentation allegedly states that traffic from an isolated port (second type) is forwarded only to promiscuous or trunk ports, not other isolated ports. Traffic from a promiscuous port (first type) can communicate with all ports. This is the alleged asymmetric forwarding rule. ¶57 col. 5:29-45
...and to update the forwarding database using a database learning process responsively to the source address and to the type indication of the frame. The complaint alleges that MAC address learning in the accused products is responsive to the source address and the VLAN in which the frame arrived, with different replication rules for addresses learned on primary vs. secondary VLANs. ¶58 col. 6:38-42
  • Identified Points of Contention:
    • Scope Questions: A central question will be whether the term "type indication" as used in the patent can be construed to read on a standard VLAN ID used in the accused products. The complaint acknowledges a potential distinction by pleading infringement under the doctrine of equivalents Compl. ¶55, suggesting this will be a key area of dispute.
    • Technical Questions: The infringement theory relies on the accused product's MAC address table learning and replication process being equivalent to the claim's "compare the type designation with a type indication" step Compl. ¶53 The court may need to determine if structuring a database to produce a certain outcome (by replicating entries only into certain VLAN tables) is the same as performing an explicit comparison for each forwarding decision, as recited in the claim.

'931 Patent Infringement Allegations

Claim Element (from Independent Claim 29) Alleged Infringing Functionality Complaint Citation Patent Citation
A ring node for use in a communication network that includes at least three communication rings in a concentric layout... Dell's documentation for the OS9 FRRP Products states that a system can be configured with up to 255 rings. The complaint alleges that multiple rings configured through the same pair of nodes constitutes a "concentric layout" in the functional sense of the patent. ¶70; ¶71 col. 2:25-45
...the ring node comprising: at least three line cards, which are arranged to communicate with the respective at least three communication rings... The accused Dell Networking C9010 is a chassis switch that can be populated with multiple line cards. Because FRRP ring ports can be any Layer 2 port, the complaint alleges they can be placed on three different line cards. ¶76 col. 2:25-45
...and a network processor, which is arranged to... identify a subset of the concentric rings comprising one or more common rings that are connected to both the ring node and the egress ring node... The complaint alleges that the accused C9010 switch identifies common rings by consulting its configured list of member VLANs for each ring it belongs to. The rings whose member VLAN list includes the frame's VLAN are the common rings. ¶79 col. 2:25-45
...to select, responsively to a respective value of at least one of the header fields of the data packet, a ringlet of a ring among the one or more common rings... The VLAN identifier of a data packet determines which FRRP ring will carry it. Because each ring has its own Master node with a specific blocked port, this selection of a ring also determines the direction of travel (the "ringlet"). ¶80 col. 2:25-45
...and to forward the data packet to the egress ring node over the selected ringlet. After determining the destination, the accused switch allegedly transmits the frame out of the appropriate ring port in the direction left open by the ring's protection state, which the complaint equates to forwarding over the selected ringlet. ¶81 col. 2:25-45
  • Identified Points of Contention:
    • Scope Questions: The definition of "concentric layout" will be critical. The complaint advances a functional definition (rings sharing common nodes) Compl. ¶71, while the patent figures depict geometrically concentric rings. The outcome of this construction could determine infringement.
    • Technical Questions: The court will need to analyze if Dell's FRRP protocol, which selects a ring based on a static VLAN-to-ring mapping and determines direction based on that ring's blocked port, is technically equivalent to the claimed step of selecting a ringlet based on a packet's header field. The complaint argues this is a direct response Compl. ¶8, but a court may examine the number of intermediate steps involved.

V. Key Claim Terms for Construction

For the ’303 Patent:

  • The Term: "type indication"
  • Context and Importance: This term is the lynchpin of the infringement allegation against the OS10 Private VLAN Products. The complaint alleges that a standard VLAN ID serves as the "type indication." The viability of the literal infringement claim will depend on whether this pre-existing packet attribute, used for routing, is the same as the "label" with a "type indication" that the patent describes the frame processor as applying.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification suggests flexibility, stating "any suitable type indication may be used," and explicitly provides "a field of the IEEE 802.1Q VLAN tag" as an example of a type indication, which may support Plaintiff's theory ’303 Patent, col. 8:31-37
    • Evidence for a Narrower Interpretation: The claim language recites a process of "labeling the received frames with corresponding... type indications." This could be interpreted to require an affirmative act of adding a new, dedicated label, rather than simply using a pre-existing VLAN ID that was already part of the frame for other purposes ’303 Patent, col. 4:45-47

For the ’931 Patent:

  • The Term: "concentric layout"
  • Context and Importance: The preamble of claim 29 requires "at least three communication rings in a concentric layout." The complaint's infringement theory depends on interpreting this term functionally to mean rings that share common nodes. If the term is construed more narrowly to a specific geometric arrangement, the infringement allegation may fail.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent does not appear to provide an explicit definition of the term in the specification text, arguably leaving it open to a functional interpretation based on the overall invention, which focuses on scaling capacity via parallel rings. The complaint argues for this functional equivalence Compl. ¶71
    • Evidence for a Narrower Interpretation: Figure 1 of the patent, which illustrates the invention, clearly depicts the rings (28A, 28B, 28C) as geometrically concentric circles. A defendant may argue that the claim term should be limited to this disclosed embodiment, as it is the only visual representation of the layout provided ’931 Patent, Fig. 1

VI. Other Allegations

  • Indirect Infringement: For the unexpired ’303, ’931, and ’673 Patents, the complaint alleges both induced and contributory infringement; the counts for the expired ’397, ’684, and ’607 Patents plead only direct infringement. The inducement allegations are based on Dell's publication and distribution of product documentation, user guides, configuration examples, and technical support materials that allegedly instruct customers to configure and use the accused products in an infringing manner Compl. ¶60 Compl. ¶83 Compl. ¶109 Contributory infringement is alleged on the basis that the accused features are a material part of the inventions and are not staple articles of commerce suitable for substantial non-infringing use Compl. ¶61 Compl. ¶84 Compl. ¶110

  • Willful Infringement: Plaintiff alleges that Defendants’ infringement of the unexpired patents ('303, '931, '673) will be willful from the date of service of the complaint. The allegation is based on continued infringement with knowledge of the patents and the complaint's allegations, allegedly in reckless disregard of Plaintiff's rights Compl. ¶63 Compl. ¶86 Compl. ¶112

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

This case appears to present several complex technical and legal questions for judicial determination. Three central issues the court may need to resolve include:

  1. A core issue will be one of definitional scope: can terms rooted in specific patent embodiments, such as "concentric layout" (from the '931 patent) and "type indication" (from the '303 patent), be construed broadly enough to read on the accused products' use of industry-standard mechanisms like shared-node ring architectures and VLAN tagging, or will they be limited to the more specific implementations illustrated in the patents?

  2. A second key question will be one of operational equivalence: does the accused software's method of achieving a result—such as by structuring a forwarding database to prevent spoke-to-spoke traffic ('303 patent) or by electing a single designated forwarder for a network segment ('673 patent)—constitute the same operational "way" as the explicit "comparison" or "mapping function" steps recited in the claims, raising a central question for both literal infringement and the doctrine of equivalents?

  3. Finally, the case will present a question of architectural interpretation: for the auto-configuration technology in the '607 patent, can a modern, integrated switching module that performs its own switching functions also be considered a "line card" storing "backup configuration parameters," as that term is used in a patent that appears to describe a more distinct separation of duties between a central switching unit and its subordinate line cards?