High Iq Networks LLC v. Telefonaktiebolaget LM Ericsson

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: High Iq Networks LLC (Delaware)
  • Defendant: Telefonaktiebolaget LM Ericsson (Sweden) and ERICSSON INC. (Delaware)
  • Plaintiff’s Counsel: Cherry Johnson Siegmund James PLLC
• Case Identification: High Iq Networks LLC v. Telefonaktiebolaget LM Ericsson, 2:26-cv-00867, E.D. Tex., 09/22/2026
• Venue Allegations: Venue is alleged against Ericsson Inc. based on its regular and established places of business within the district, including its U.S. headquarters in Plano and a 5G factory in Lewisville. Venue is alleged against Telefonaktiebolaget LM Ericsson on the basis that it is a foreign corporation not resident in the United States.
• Core Dispute: Plaintiff alleges that Defendant’s Router 6000 Series and associated IP Operating System (IPOS) infringe four patents related to carrier-grade packet transport technologies for managing traffic in and between ring-based telecommunication networks.
• Technical Context: The technology addresses challenges arising from the telecommunications industry's migration from legacy time-division multiplexing (TDM) networks to more flexible and cost-effective packet-based Ethernet transport.
• Key Procedural History: The complaint alleges that Defendant had pre-suit knowledge of the patented technology through a 2011-2012 business collaboration and technology evaluation with the patents’ original assignee, Orckit-Corrigent, which Defendant allegedly discontinued before developing the accused products. The complaint also alleges knowledge of the ’673 Patent from its citation as prior art during the prosecution of Defendant's own patents. One of the asserted patents, the ’397 Patent, has expired, and Plaintiff seeks damages for the pre-expiration period only.

Case Timeline

Date	Event
2001-06-07	’397 Patent Priority Date
2005-10-04	’397 Patent Issue Date
2006-03-02	’931 Patent 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-01-25	’673 Patent Issue Date
2011-11-25	Ericsson approves joint architecture with Orckit-Corrigent
2012-01-01	Ericsson and Orckit-Corrigent conduct joint testing
2015-02-01	Ericsson introduces Router 6000 Series
2023-10-31	’397 Patent Expired
2026-09-22	Complaint Filing Date

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

U.S. Patent No. 7,876,673 - "Prevention of Frame Duplication in Interconnected Ring Networks"

• Patent Identification: U.S. Patent No. 7,876,673, "Prevention of Frame Duplication in Interconnected Ring Networks", issued January 25, 2011 Compl. ¶14

The Invention Explained

• Problem Addressed: When two ring networks are connected by two or more "interconnect nodes" for redundancy, a "flooded" packet (addressed to multiple recipients) is received by each interconnect node Compl. ¶15 Without a coordination mechanism, each node would forward its copy into the second ring, causing duplicate packets and potential forwarding loops Compl. ¶15 '673 Patent, col. 3:55-57
• The Patented Solution: The invention proposes a coordination system where interconnect nodes exchange "synchronization messages" to monitor each other's status Compl. ¶16 The nodes use a shared, "predefined mapping function" applied to a packet attribute (like a VLAN ID) to deterministically select a single node responsible for forwarding that specific packet Compl. ¶16 '673 Patent, col. 7:12-20 This distributes the load. If one node fails, a surviving node can enter a "forward all" state, taking over responsibility for all packets to maintain connectivity Compl. ¶16 '673 Patent, col. 8:62-67
• Technical Importance: This solution enables the creation of resilient, load-balanced, and loop-free connections between packet-based ring networks, a key requirement for building large-scale, carrier-grade Ethernet transport systems Compl. ¶¶8, 11

Key Claims at a Glance

• The complaint asserts independent claim 18 Compl. ¶59
• Claim 18 recites a communication apparatus comprising two or more interconnect nodes, where each node is configured to:
  • Send and receive synchronization messages indicating status.
  • Responsively adopt a forwarding status from the group "forward mine," "forward none," or "forward all."
  • Accept a data packet, extract an attribute, and apply a predefined mapping function to select a single interconnect node for forwarding.
  • Act based on its status: forward only if selected ("forward mine"), refrain from forwarding ("forward none"), or forward regardless of the mapping function ("forward all") Compl. ¶60
• The complaint reserves the right to assert additional claims Compl. ¶57

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. ¶19

The Invention Explained

• Problem Addressed: In certain Layer-2 services, it is necessary to allow multiple "spoke" locations (e.g., different customers) to communicate with a central "hub" (e.g., an ISP's network access point) but prevent them from communicating directly with each other, all within a standard bridged network that learns and forwards based on destination addresses Compl. ¶¶12, 20
• The Patented Solution: The invention designates switch interfaces as either "hub-type" or "spoke-type" Compl. ¶20 '303 Patent, col. 5:37-45 When a frame enters the switch, it is labeled with an indication of its ingress interface type Compl. ¶21 The switch's forwarding database stores this type information along with the learned source MAC address. The core of the invention is a forwarding rule: when a frame is to be sent, the switch compares the destination's stored type with the frame's ingress type. This allows the switch to enforce a policy preventing frames that entered on a spoke-type interface from being forwarded out another spoke-type interface Compl. ¶21
• Technical Importance: This technique enables service providers to build secure, partitioned "hub-and-spoke" services like Virtual Private LAN Service (VPLS) on a standard Layer-2 infrastructure, a foundational capability for offering enterprise VPNs Compl. ¶14 at p. 14

Key Claims at a Glance

• The complaint asserts independent claim 11 Compl. ¶87
• Claim 11 recites an apparatus with a group of switches in a Layer-2 bridged network, where each switch has interfaces configured as a "first type" or "second type," and a frame processor operative to:
  • Create a forwarding database entry with a source address and a "type indication."
  • Label received frames with a corresponding type indication.
  • Compare a destination's stored type designation with a frame's type indication to determine forwarding.
  • Permit frames labeled with the "second type" to be transmitted through "first type" interfaces, but prevent them from being transmitted through other "second type" interfaces.
  • Update the forwarding database based on both the source address and the type indication of the frame Compl. ¶88
• The complaint reserves the right to assert additional claims Compl. ¶57

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. ¶23
• Technology Synopsis: The patent addresses the problem that a single network ring may not provide enough capacity as traffic grows Compl. ¶10 The described solution is to run multiple communication rings in parallel between the same set of nodes in a "concentric layout" and to distribute traffic across these rings, for example, by applying a hashing function to packet header fields. This increases overall capacity in a manner analogous to link aggregation (Compl. ¶¶10, 24; '931 Patent, Abstract).
• Asserted Claims: The complaint asserts independent claim 29 Compl. ¶112
• Accused Features: The accused routers' implementation of IEEE 802.3ad Link Aggregation in combination with G.8032 Ethernet Ring Protection is alleged to create the claimed network of multiple concentric rings and perform the required packet distribution Compl. ¶¶116, 124-125

U.S. Patent No. 6,952,397 - "Communication in a Bidirectional Ring Network with Single-Direction Receiving"

• Patent Identification: U.S. Patent No. 6,952,397, "Communication in a Bidirectional Ring Network with Single-Direction Receiving", issued October 4, 2005 Compl. ¶27
• Technology Synopsis: The patent addresses inefficient bandwidth utilization in bidirectional rings, where a significant portion of capacity can sit idle if traffic is not divided between the clockwise and counter-clockwise paths Compl. ¶9 The solution involves configuring nodes to transmit in both directions but receive in only one selected direction at any given time. The receive direction for each node is chosen specifically to balance the total traffic load carried in each direction around the ring (Compl. ¶¶9, 28; '397 Patent, col. 3:9-18).
• Asserted Claims: The complaint asserts independent method claim 15 Compl. ¶136
• Accused Features: The accused routers' implementation of G.8032 Ethernet Ring Protection, particularly when configured with multiple protection instances on a single physical ring, is alleged to perform the claimed method of selecting receive directions for different traffic flows to balance the load between the two ring rotations Compl. ¶¶143-144

III. The Accused Instrumentality

Product Identification

• The Accused Instrumentalities are the Ericsson Router 6000 Series of IP transport routers, including specific models such as the Router 6273, and the Ericsson IP Operating System (IPOS) that runs on them Compl. ¶¶1, 39 The complaint identifies the Router 6273 as a representative product Compl. ¶35

Functionality and Market Context

• The products are described as high-performance aggregation routers designed for mobile backhaul (LTE, 5G) and converged metro networks Compl. ¶33 Compl. ¶35 All routers in the series run the same IPOS operating system, which provides a common feature set Compl. ¶34
• The complaint alleges these products implement several key networking standards that map to the asserted patents: ITU-T G.8032 (Ethernet Ring Protection), Ethernet VPN (EVPN) with multihoming, Virtual Private LAN Service (VPLS) and Hierarchical VPLS (H-VPLS), and IEEE 802.3ad Link Aggregation Compl. ¶4 The complaint cites product datasheets stating these features are available and released Compl. ¶36 Compl. ¶37
• No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

’673 Patent Infringement Allegations

Claim Element (from Independent Claim 18)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A communication apparatus used in a communication network that includes multiple ring nodes arranged in at least first and second ring networks, the apparatus comprising two or more interconnect nodes that connect the first and second ring networks...	The Ericsson Router 6273 is an aggregation router used in ring topologies. Two Router 6273 units deployed as Ethernet VPN (EVPN) multihoming provider edges serve as the two interconnect nodes connecting an access ring to an aggregation ring.	¶¶62-65	col. 3:55-57
...wherein each interconnect node is configured: to send a synchronization message indicating the status thereof;	Each router sends a BGP Ethernet Segment route, which announces its attachment to the segment and its participation in forwarding. The withdrawal of this route indicates a change in status.	¶68	col. 8:67-9:3
to receive the synchronization messages of the other interconnect nodes;	Each router receives the Ethernet Segment routes from other provider edge nodes attached to the same segment and builds a list of its peers.	¶69	col. 8:67-9:3
responsively to receiving the synchronization messages, taking on a forwarding status selected from a group consisting of: "forward mine"; "forward none"; and "forward all";	In response to the BGP routes, the router takes on one of three conditions: 1) "forward mine" (as the elected Designated Forwarder, it forwards traffic assigned to it); 2) "forward none" (if its attachment is down, it forwards nothing); or 3) "forward all" (if its peer fails, it forwards all traffic for the segment).	¶70	col. 11:4-8
to accept a data packet...; to extract an attribute from the data packet;	The router accepts a data packet and determines the VLAN of the packet from its VLAN tag or service label, which serves as the extracted attribute.	¶¶72-73	col. 7:12-20
to apply a predefined mapping function to the extracted attribute so as to select a single interconnect node for forwarding the data packet to the second ring network;	The "service-carving" rule of EVPN (e.g., (V mod N) = i) is alleged to be a predefined mapping function that uses the VLAN attribute to select one router as the Designated Forwarder (DF) for a given packet.	¶74	col. 6:32-44
and if the interconnect node has a "forward mine" forwarding status, to forward a single copy of the data packet...only if the interconnect node is the selected interconnect node...	In EVPN single-active multihoming, the router selected as the DF forwards the packet, while the other (non-DF) router refrains from forwarding it.	¶75	col. 11:8-15
if the interconnect node has a "forward none" forwarding status, then refraining from forwarding a copy of the data packet regardless of the predefined mapping function...	A router whose segment attachment is down assumes a non-designated-forwarder role for all VLANs and does not forward packets from the first ring to the second.	¶76	col. 11:16-19
and if the interconnect node has a "forward all" forwarding status, then forwarding a singled copy of the data packet to the second ring network regardless of the predefined mapping function...	When a peer router's Ethernet Segment route is withdrawn, the surviving router forwards every packet to the segment, regardless of the packet's VLAN and the original mapping function result.	¶77	col. 11:20-23

• Identified Points of Contention:
  • Scope Questions: The infringement theory hinges on whether complex industry-standard protocols can be mapped to the patent's more general terms. A primary question will be whether the BGP Ethernet Segment routes used in EVPN constitute a "synchronization message indicating the status thereof" as recited in the claim (Compl. ¶68), or if the patent envisioned a simpler, proprietary keep-alive mechanism Compl. ¶17
  • Technical Questions: A potential point of contention is the operation of the "forward all" status. The complaint alleges that when a peer fails, the surviving router forwards traffic "regardless of the predefined mapping function" (Compl. ¶77). A defendant may argue that the EVPN standard's procedure for re-triggering "service carving" upon a peer failure is a new application of a mapping function, not a bypass of it, potentially creating a mismatch with the claim language.

’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...	Router 6273 units are provider-edge switches coupled together in a Hierarchical VPLS (H-VPLS) or Ethernet VPN (E-LAN) bridge domain, which are Layer-2 bridged networks.	¶90	col. 5:59-62
...each switch comprising: 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...	In an H-VPLS deployment, the spoke connection to a customer site is the "first type" interface, while the hub pseudowires connecting to other provider-edge devices are the "second type" interfaces.	¶92	col. 5:37-45
and a frame processor, which is operative: to create an entry comprising a source address of the frame and a number equal to a type indication...to identify the first interface, and to add the entry to a forwarding database...	When the router learns a source address in an H-VPLS domain, it creates a forwarding database entry containing the address and a value identifying the class of the interface (spoke or hub) on which it was learned.	¶94	col. 6:25-37
upon receiving through a first interface... a frame... to look up the destination address in the forwarding database, and to compare the type designation with a type indication of the frame in order to determine whether to forward the frame through the second interface;	The router looks up the destination MAC address. The "split-horizon" rule of H-VPLS requires comparing the stored type of the destination with the type of the ingress interface to prevent forwarding between two hub interfaces.	¶¶96-97	col. 8:14-20
upon receiving frames... to label the received frames with corresponding first and second type indications...	In H-VPLS, the pseudowire label itself serves as the type indication, identifying the class (spoke or hub) of the pseudowire carrying the frame.	¶98	col. 8:31-41
...by 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 that are labeled with the second type indication from being transmitted through the interfaces of the second type...	Frames arriving on a hub pseudowire ("second type") are permitted to be sent to spoke connections ("first type") but are prevented by the split-horizon rule from being sent to other hub pseudowires ("second type").	¶101	col. 7:42-53
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 router's learning process updates the forwarding database for the bridge domain based on the frame's source MAC address and the class of the interface (e.g., spoke or hub) on which it arrived.	¶102	col. 6:49-65

• Identified Points of Contention:
  • Scope Questions: The analysis raises the question of whether the roles within a standard H-VPLS or E-Tree service (e.g., "spoke pseudowire," "hub pseudowire") align with the patent's binary "first type" and "second type" interface definitions (Compl. ¶92). The claim is defined by forwarding behavior, but a defendant may argue the accused protocols operate on different principles or that the alleged mapping is inconsistent with the patent's specific embodiments.
  • Technical Questions: The complaint alleges that in H-VPLS, the pseudowire label itself functions as the claimed "type indication" (Compl. ¶98). The court may need to determine if using an existing service label for routing within an MPLS network is equivalent to the patent's concept of actively "labeling the received frames with corresponding first and second type indications" for the specific purpose of enforcing the spoke-to-spoke forwarding restriction.

V. Key Claim Terms for Construction

’673 Patent

• The Term: "synchronization message"
• Context and Importance: This term is critical because the plaintiff's infringement theory equates the BGP Ethernet Segment routes of the accused EVPN implementation with the claimed "synchronization message" (Compl. ¶68). The defense may argue that a complex BGP routing update is not the simpler status message contemplated by the patent.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification states the purpose of the message is to enable an interconnect node "to determine that the other interconnect node has failed" ('673 Patent, col. 8:67-9:3). A BGP route withdrawal serves this exact function. The patent also notes the messages can be sent "in response to a state change" ('673 Patent, col. 11:4-8), which is consistent with a BGP update triggered by a link failure.
  • Evidence for a Narrower Interpretation: The specification suggests the messages may be used as simple "'keep alive' indications" '673 Patent, col. 12:67-13:1 A defendant could argue this implies a simpler mechanism than the BGP routing protocol, limiting the term's scope to explicit, dedicated status messages.

’303 Patent

• The Term: "first type of the interfaces" / "second type of the interfaces"
• Context and Importance: The entire infringement case for the ’303 Patent rests on mapping the functional roles within H-VPLS or E-Tree (e.g., spoke vs. hub) to these two claimed types (Compl. ¶92). Practitioners may focus on this term because the viability of this mapping will determine infringement.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claims define the types by their forwarding behavior (e.g., preventing second-type to second-type forwarding) rather than by a rigid physical structure. The specification describes "Hub-type interfaces" connecting to "public networks" and "Spoke-type interfaces" connecting to "customer premises equipment" '303 Patent, col. 5:37-45, which can be read as a functional, rather than a strictly physical, description.
  • Evidence for a Narrower Interpretation: The language describing hub interfaces connecting to "public networks" and spoke interfaces to "customer premises equipment" could be used to argue for a narrower construction. A defendant might contend that the "hub pseudowires" in the accused H-VPLS service are internal network-to-network interfaces, not direct connections to a "public network" as described in the patent's embodiment, thereby creating a scope mismatch.

VI. Other Allegations

• Indirect Infringement: The complaint alleges both induced and contributory infringement for all asserted patents. The inducement allegations are based on Defendant designing its IPOS software with the infringing functionalities (e.g., EVPN multihoming, H-VPLS), marketing these features, and providing datasheets, instruction manuals, and deployment services that allegedly instruct and encourage customers to configure and use the products in an infringing manner (Compl. ¶81; Compl. ¶106; Compl. ¶130; Compl. ¶149). Contributory infringement is alleged on the basis that the specific software components (e.g., the EVPN designated-forwarder election function) are not staple articles of commerce and have no substantial non-infringing use Compl. ¶82 Compl. ¶107 Compl. ¶131 Compl. ¶150
• Willful Infringement: The complaint alleges willful infringement based on both pre-suit and post-suit knowledge. Pre-suit knowledge is primarily alleged to stem from a 2011-2012 business engagement between Defendant and Orckit-Corrigent, the original assignee of the patents, where Defendant allegedly conducted due diligence and technical testing of the patented technology (Compl. ¶¶47-52). For the ’673 Patent specifically, knowledge is also alleged from its citation by the USPTO as prior art during the prosecution of Defendant’s own patent applications (Compl. ¶54). Post-suit knowledge is based on the filing of the complaint itself (Compl. ¶55).

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

• A core issue will be one of definitional scope: can the claim terms of the asserted patents, which describe network functions in general terms (e.g., "synchronization message," "first type" interface), be construed to read on the specific, complex implementations found in modern, industry-standard protocols like EVPN and H-VPLS? The case may turn on whether the accused products' standards-based operations are equivalent to the patented inventions or represent a distinct technical evolution.
• A second central question will be evidentiary and historical: what level of knowledge did Ericsson gain from its alleged 2011-2012 evaluation of Orckit-Corrigent’s technology? Discovery into the technical details exchanged, internal Ericsson reviews, and the timeline of Ericsson's subsequent development of its IPOS features will be critical for the willfulness claim, which could significantly impact potential damages.
• A key technical question will be one of functional implementation: do the accused products perform the claimed functions in the same way as described in the patents? For example, with respect to the ’673 patent, does the EVPN failover mechanism—which re-triggers a "service carving" procedure—operate "regardless of the predefined mapping function" as the claim requires, or is this a fundamentally different method of achieving failover?