OptimNet LLC v. Cisco Systems Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: OptimNet LLC (Texas)
  • Defendant: Cisco Systems, Inc. (Delaware)
  • Plaintiff's Counsel: Russ August & Kabat
• Case Identification: 2:25-cv-00935, E.D. Tex., 09/04/2025
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant is registered to do business in Texas, has committed acts of infringement in the District, and maintains regular and established places of business in the District, including a large campus in Richardson, Texas.
• Core Dispute: Plaintiff alleges that Defendant's networking products and software platforms infringe five patents related to technologies for managing data traffic in optical, Ethernet, and virtualized network environments.
• Technical Context: The technologies at issue concern methods for improving the scalability, efficiency, and reliability of complex computer networks, which are foundational to modern data centers and telecommunications infrastructure.
• Key Procedural History: The asserted patents originate from the Electronics and Telecommunications Research Institute (ETRI). The complaint alleges that ETRI was involved in developing the ITU-T G.8032 standard for Ethernet Ring Protection Switching (ERPS) and submitted an IPR declaration committing to license its relevant patents on reasonable and non-discriminatory (RAND) terms, potentially framing this as a dispute involving standard-essential patents (SEPs). The complaint also alleges Defendant's knowledge of some asserted patents based on their citation during the prosecution of Defendant's own patents.

Case Timeline

Date	Event
2007-06-25	'623 Patent Priority Date
2009-07-24	'807 Patent Priority Date
2009-11-19	ETRI submits IPR Declaration for G.8032 Standard
2010-10-29	'887 Patent Priority Date
2012-02-14	'623 Patent Issued
2012-04-18	'101 Patent Priority Date
2013-12-27	'961 Patent Priority Date
2014-01-28	'807 Patent Issued
2014-07-15	'887 Patent Issued
2016-04-12	'101 Patent Issued
2018-07-10	'961 Patent Issued
2025-09-04	Complaint Filed

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

U.S. Patent No. 8,116,623 - "Multi-Ring Network Operating Method and System"

The Invention Explained

• Problem Addressed: The patent describes that conventional methods for connecting multiple network rings face a trade-off. Using purely electrical switches creates data throughput bottlenecks, while using purely optical switches can lead to wavelength collisions or signal degradation over distance Compl. ¶21 '623 Patent, col. 1:51-67
• The Patented Solution: The invention proposes a hybrid optical cross-connect (OXC) apparatus that possesses multi-casting capabilities in both the optical and electrical domains. Data that does not require signal regeneration or wavelength conversion is cross-connected within the high-speed optical domain. Signals that do require such processing are handled in the electrical domain, providing a more efficient and scalable method for managing traffic across multiple rings Compl. ¶21 '623 Patent, col. 2:1-11 Figure 11 illustrates an embodiment with both optical components (WSS) and an electrical cross-connect switch '623 Patent, FIG. 11
• Technical Importance: This hybrid approach aimed to combine the speed of optical switching with the signal processing flexibility of electrical switching, addressing a key scalability and cost challenge in expanding optical networks.

Key Claims at a Glance

• The complaint asserts at least independent Claim 1 Compl. ¶23
• The essential elements of Claim 1 are:
  • A method of cross-connecting at least two ring networks.
  • Cross-connecting the input working and protection rings of a first network to the output working and protection rings of a second network.
  • Splitting an input multi-wavelength optical signal into portions using an optical coupler.
  • Transmitting the signal to a wavelength selective switch (WSS) that selectively passes portions of the signal to an output of the second ring network.
  • Providing a multi-casting function in both an optical and an electrical domain, where signals not requiring reproduction are cross-connected in the optical domain, and signals requiring reproduction are cross-connected in the electrical domain.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 8,638,807 - "Method for Managing Ethernet Ring Network of VLAN-Based Bridge"

The Invention Explained

• Problem Addressed: The patent states that while Ethernet Ring Protection (ERP) technology existed, there was no defined management method for registering VLAN IDs and updating the necessary filtering databases in VLAN-aware bridges to make the ERP controller operational Compl. ¶32 '807 Patent, col. 2:8-16
• The Patented Solution: The invention provides a specific method for managing an Ethernet ring network by registering VLAN IDs and updating VLAN entries in a filtering database. This allows a VLAN-based bridge to properly operate Ethernet ring protection, including in hierarchical networks with major and sub-rings '807 Patent, abstract '807 Patent, col. 2:17-23
• Technical Importance: This technology provided a necessary management framework to implement standardized ring protection protocols, such as G.8032, in increasingly complex, VLAN-segmented enterprise and carrier networks.

Key Claims at a Glance

• The complaint asserts at least independent Claim 13 Compl. ¶34
• The essential elements of Claim 13 are:
  • A method for managing an Ethernet ring network of a VLAN-based bridge.
  • Setting ring ports and a ring ID for an Ethernet ring node.
  • Determining if the node is a ring protection link (RPL) owner or neighbor.
  • Registering VLAN IDs (VIDs) for traffic and Ring Automatic Protection Switching (R-APS) channels in the Filtering Databases (FDBs) of the ring ports.
  • Performing a topology update of the FDBs.
  • The topology update includes registering VIDs for both a major ring and a sub-ring in the FDBs.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 8,780,887 - "Method of Network-Based Communication in Virtual Network Environment"

• Technology Synopsis: The patent addresses the difficulty of supporting terminal mobility in conventional internet architectures where a new IP address is assigned upon each new connection Compl. ¶43 '887 Patent, col. 3:34-41 It proposes a method for direct, network-based communication using a persistent virtual address within a virtual network environment, facilitated by a tunnel mapping controller '887 Patent, abstract
• Asserted Claims: At least Claim 1 Compl. ¶45
• Accused Features: Cisco Meraki auto VPN software and Meraki virtual devices, including Meraki MX and Meraki Z series devices Compl. ¶45

U.S. Patent No. 9,313,101 - "Method of Controlling Traffic by Time-Based Policy"

• Technology Synopsis: The patent addresses limitations in conventional traffic control policies, which are based only on information contained within a data packet Compl. ¶54 '101 Patent, col. 1:44-51 The invention provides a method for creating and executing a "time-based policy" by adding a time condition to the policy setting, allowing for more varied and dynamic traffic control '101 Patent, col. 1:52-59
• Asserted Claims: At least Claim 1 Compl. ¶56
• Accused Features: All Cisco products that implement time-based policies for traffic control, including Cisco's Identity Services Engine (ISE) and Catalyst Center platforms Compl. ¶56

U.S. Patent No. 10,020,961 - "Method and Apparatus for Network Virtualization"

• Technology Synopsis: The patent addresses the scalability problem in overlay networks like VXLAN, where a full mesh of tunnels is required, leading to a quadratic increase (N*(N-1)) in tunnels as nodes (N) are added Compl. ¶65 '961 Patent, col. 1:39-44 It proposes a method and apparatus to provide expandability, seemingly by using a more hierarchical or managed tunnel structure to reduce this complexity '961 Patent, abstract '961 Patent, col. 1:60-62
• Asserted Claims: At least Claim 1 Compl. ¶67
• Accused Features: Cisco products and software that implement Cisco ACI multi-site functionalities, such as the Cisco Nexus 9000 series switches Compl. ¶67

III. The Accused Instrumentality

Product Identification

The complaint names a wide range of Cisco's networking hardware and software, categorized by the patent they allegedly infringe:

• Cisco Optical Transport Platforms (e.g., NCS 1004, NCS 2000) Compl. ¶23
• Cisco IOS software platforms (IOS Classic, IOS-XE, IOS-XR) running on routers like the ASR 900 and 1000 Series Compl. ¶34
• Cisco Meraki auto VPN software and virtual devices (MX and Z series) Compl. ¶45
• Cisco platforms implementing time-based policies, such as the Identity Services Engine (ISE) and Catalyst Center Compl. ¶56
• Cisco products implementing ACI multi-site, such as Nexus 9000 series switches Compl. ¶67

Functionality and Market Context

The accused products represent a significant portion of Cisco's enterprise and service provider networking portfolio. The complaint alleges these products incorporate standardized and proprietary technologies for routing, switching, and managing network traffic. For example, it alleges that Cisco's IOS platforms implement the ITU-T G.8032 standard for ERPS Compl. ¶34, and that platforms like Catalyst Center and ISE are used to define and enforce network access policies, including time-based ones Compl. ¶56 Compl. Ex. 8, p. 3 A diagram in the complaint shows the Cisco SDA (Software-Defined Access) architecture, where Catalyst Center acts as the central management plane and ISE functions as the policy platform Compl. Ex. 8, p. 2

IV. Analysis of Infringement Allegations

U.S. Patent No. 8,116,623 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
cross-connecting an input working ring and an input protection ring of a first ring network to an output working ring and an output protection ring of a second ring network;	The Cisco NCS 2000 series is alleged to interconnect traffic between two or more rings, such as a main ring and a tributary ring.	¶23; Ex. 2, p. 3	col. 10:27-31
splitting an input multi-wavelength optical signal of the first ring network into at least one portion each having a specific wavelength, by using an optical coupler;	The accused NCS 2000 Flex Spectrum ROADM Line Cards allegedly contain optical couplers that split input signals.	¶23; Ex. 2, p. 5	col. 5:41-44
transmitting the input multi-wavelength optical signal to at least one wavelength selective switch, wherein the wavelength selective switch selectively passes at least one of the portions of the input multi-wavelength optical signal...	The accused ROADM Line Cards allegedly contain a Wavelength Selective Switch (WSS) that selectively routes wavelengths.	¶23; Ex. 2, p. 6	col. 5:61-67
wherein a multi-casting function is provided both in an optical domain and in an electrical domain so that if the input signal does not require signal reproduction...it is cross-connected in the optical domain, and if the input signal requires signal reproduction...it is cross-connected in the electrical domain.	The accused system allegedly performs optical cross-connection via Contentionless Add/Drop line cards and WSS, and performs electrical domain cross-connection via transponder and muxponder cards that perform optical-to-electrical-to-optical (OEO) conversion.	¶23; Ex. 2, pp. 6-10	col. 2:1-11

• Identified Points of Contention:
  • Scope Question: A potential dispute may arise over the term "cross-connected in the electrical domain". The complaint alleges this is met by Cisco's transponder cards performing OEO conversion Compl. Ex. 2, p. 10 The defense may argue that this standard OEO conversion for add/drop functions is not the specific "cross-connect/grooming switch" function envisioned by the patent's embodiments '623 Patent, FIG. 11
  • Technical Question: The claim recites an integrated method. A question for the court may be whether Cisco's modular system, which uses different line cards for different functions (e.g., ROADM cards, Contentionless Add/Drop cards, transponder cards), practices the specific combination of steps required by the method claim.

U.S. Patent No. 8,638,807 Infringement Allegations

Claim Element (from Independent Claim 13)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
setting ring ports of an Ethernet ring node constituting an Ethernet ring, wherein a ring ID of the Ethernet ring is set;	The accused Cisco ASR 1000 series running IOS-XE allegedly allows configuration of an Ethernet Protection Ring, including defining ring ports and a ring ID (instance).	¶34; Ex. 4, p. 4	col. 7:42-45
determining whether the Ethernet ring node is a ring protection link (RPL) owner node or an RPL neighbor node...	The accused products allegedly allow configuration of a node as an RPL "owner" or "neighbor" to manage the ring protection link. A diagram in the complaint illustrates this topology (Compl. Ex. 4, p. 6).	¶34; Ex. 4, p. 6	col. 7:46-51
registering VLAN IDs (VIDs) for performing a traffic channel blocking and a Ring Automatic Protection Switching (R-APS) channel blocking in Filtering Databases (FDBs)...	The accused products allegedly use VLANs to support multiple instances on a G.8032 ring and use FDB mechanisms (e.g., flushing) for blocking.	¶34; Ex. 4, p. 7	col. 7:52-58
performing a topology update of the Filtering Databases;	The accused products allegedly perform an FDB flush upon detecting a signal failure, which constitutes a topology update.	¶34; Ex. 4, p. 9	col. 7:59-60
wherein the performing of the topology update includes: registering VIDs for... a major ring... and registering VIDs for... a sub ring, a lower Ethernet ring of the major ring...	The accused products allegedly support the interconnection of multiple rings (a major ring and a subring) and propagate topology change notifications across them.	¶34; Ex. 4, p. 17	col. 7:61-67

• Identified Points of Contention:
  • Scope Question: Claim 13 recites a specific method of "registering" VIDs and "performing a topology update" that includes actions on both major and sub-rings. A central question will be whether the operational behavior and configuration commands of Cisco's G.8032 implementation (Compl. Ex. 4, p. 4) map directly onto this claimed sequence of steps.
  • Technical Question: The final limitation requires registering VIDs for a "sub ring, a lower Ethernet ring of the major ring." The defense may argue that its implementation of interconnected rings does not create the specific hierarchical "major ring/sub-ring" relationship as defined and required by the patent, but rather a peer-to-peer interconnection.

V. Key Claim Terms for Construction

• The Term: "cross-connected in the electrical domain" (from '623 Patent, Claim 1)

• Context and Importance: This term is critical because infringement hinges on whether the functionality of Defendant's standard OEO conversion cards (transponders/muxponders) meets this limitation. Practitioners may focus on this term because Defendant will likely argue its products perform standard add/drop functions, not the integrated hybrid optical/electrical cross-connection taught by the patent.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent summary describes the invention as providing an apparatus where "signals that do require regeneration or wavelength conversion are cross-connected in the electrical domain," which could be read to encompass any OEO process that handles such signals '623 Patent, col. 2:6-9
  • Evidence for a Narrower Interpretation: The patent specification repeatedly references an "electrical cross-connect/grooming switch" as a distinct component that recombines signals for retransmission '623 Patent, col. 8:65-9:6 An embodiment in Figure 11 shows a dedicated "ELECTRICAL CROSS-CONNECT/GROOMING SWITCH (1120)," which may suggest a more specific structure than a standard transponder card '623 Patent, FIG. 11

• The Term: "registering VLAN IDs (VIDs)" (from '807 Patent, Claim 13)

• Context and Importance: The infringement case for the '807 patent depends on showing that Cisco's configuration process for G.8032 rings is equivalent to the claimed act of "registering" VIDs in Filtering Databases. Practitioners may focus on this term to dispute whether Cisco's standard configuration and learning processes are the same as the specific "registration" method taught by the patent.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent's abstract broadly states the goal is to "effectively register[] a VLAN ID and updat[e] a VLAN entry in a VLAN filtering database," which could be interpreted to cover any action that results in the FDB being populated with the necessary VID information '807 Patent, abstract
  • Evidence for a Narrower Interpretation: The detailed description and flowcharts show a specific process involving an "ERP controller" that "requests registration" and uses GVRP/MVRP messages '807 Patent, FIG. 7A-7B This could support an argument that "registering" requires this specific controller-initiated protocol, not just a network administrator configuring a device via a command-line interface.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement for all asserted patents. The allegations are based on claims that Defendant provides product documentation, user manuals, and instructions that actively encourage and guide customers to configure and use the accused products in a manner that directly infringes the patents Compl. ¶24 Compl. ¶35 Compl. ¶46 Compl. ¶57 Compl. ¶68
• Willful Infringement: The complaint alleges willful infringement based on both pre- and post-suit knowledge. Pre-suit knowledge is alleged based on Defendant's awareness of the G.8032 standard and ETRI's associated IPR declarations Compl. ¶6, as well as on specific instances where the asserted patents were cited by the USPTO examiner during the prosecution of Defendant's own patents Compl. ¶7 Compl. ¶48 Compl. ¶70 Post-suit knowledge is based on the filing and service of the complaint itself Compl. ¶26 Compl. ¶37

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

1. Standard-Essentiality and RAND: For at least the '807 patent concerning the G.8032 standard, a central issue will be its status as a Standard-Essential Patent (SEP). The court will likely need to address: did Cisco's implementation of the G.8032 standard require use of the patented technology, and if so, what is the legal effect of ETRI's 2009 commitment to license its patents on reasonable and non-discriminatory (RAND) terms on the calculation of damages and the availability of injunctive relief?

2. Architectural Mismatch: Across several patents (e.g., the '623 and '961), a recurring question will be one of technical and structural equivalence. Does Defendant's modular architecture-which combines distinct hardware and software products like line cards, switches, and management platforms-practice the specific, integrated methods and apparatus structures described in the patents, or does it represent a fundamentally different design that falls outside the scope of the claims?

3. Willfulness and Pre-Suit Knowledge: The willfulness claims heavily rely on allegations of pre-suit knowledge from patent citations and standards-body declarations. A key factual question will be whether this evidence is sufficient to establish that Defendant had the requisite knowledge of infringement, or was willfully blind to it, prior to the lawsuit, which would be critical for any potential enhancement of damages.