Dynamic Mesh Networks Inc v. Cisco Systems Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Dynamic Mesh Networks, Inc. d/b/a MeshDynamics (California)
  • Defendant: Cisco Systems, Inc., Cisco WebEx LLC, WebEx Communications, Inc. (Delaware, California)
  • Plaintiff's Counsel: Daignault Iyer LLP
• Case Identification: 2:25-cv-00783, E.D. Tex., 08/12/2025
• Venue Allegations: Venue is alleged to be proper in the Eastern District of Texas because Defendant Cisco has regular and established places of business in the district, including a large campus in Richardson, Texas.
• Core Dispute: Plaintiff alleges that Defendant's SD-WAN networking equipment and Webex VoIP collaboration products infringe three patents related to reliable real-time data transmission and self-forming networks.
• Technical Context: The technologies at issue concern methods for improving the performance and reliability of networks carrying real-time traffic, such as video and voice, particularly in environments where network connections may be unstable.
• Key Procedural History: The complaint alleges that in 2009, Plaintiff met with senior decision-makers at Cisco to discuss a potential partnership, during which Plaintiff disclosed its technology and then-pending patent applications that later matured into the patents-in-suit. The complaint also alleges that Plaintiff sent a notice letter identifying the patents-in-suit to Cisco's CEO on June 22, 2022, which may be relevant to allegations of willful infringement.

Case Timeline

Date	Event
2005-11-04	Priority Date for '762 Patent
2007-03-15	Cisco acquires WebEx Communications, Inc.
2008-11-24	Priority Date for '852 Patent and '000 Patent
2009-01-01	Approximate date of pre-suit communications between Plaintiff and Cisco
2013-07-02	'762 Patent Issue Date
2013-08-20	'852 Patent Issue Date
2015-06-02	'000 Patent Issue Date
2022-06-22	Plaintiff sends notice letter to Cisco
2025-08-12	Complaint Filing Date

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

U.S. Patent No. 8,514,852 - "Real time package transforms to avoid re-transmission"

Issued August 20, 2013 Compl. ¶29

The Invention Explained

• Problem Addressed: The patent addresses the problem of latency and throughput loss in networks transmitting real-time data streams (like video), which occurs when data packets are corrupted or lost and must be re-transmitted from the source '852 Patent, col. 1:33-50 Compl. ¶30
• The Patented Solution: The invention proposes modifying a standard data packet to create a "container packet" that includes redundant "repair/recovery information" and pointers to that information within the packet itself '852 Patent, col. 3:6-14 This allows an intermediate relay station or the final receiving device to detect an error, use the embedded redundant data to repair the packet on the fly, and forward it without requesting a costly re-transmission from the original source '852 Patent, abstract Compl. ¶30 The process includes adding redundant data, adding a position offset reference number to point to it, and revising checksums accordingly Compl. ¶32
• Technical Importance: This method was designed to enhance the reliability and efficiency of real-time data transmission over networks prone to errors, such as multi-hop wireless mesh networks Compl. ¶30

Key Claims at a Glance

• The complaint asserts independent claim 1 Compl. ¶50
• The essential elements of method claim 1 include:
  • modifying said packet by adding redundant information to the packet;
  • modifying at least one packet header to add a position offset reference number that points to redundant information;
  • revising all checksums within the packet as modified to agree with the packet contents as modified;
  • transmitting the packet through a network;
  • modifying the packet, including modifying all checksums, to return the packet's format to that of the standard packet format;
  • if the modified packet is determined to have a checksum mismatch as received, modifying the packet by retrieving the redundant information pointed to by said position offset reference number and replacing a portion of the packet with said redundant information; and
  • revising all checksums within the packet as modified to agree with the contents of the modified packet.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 9,049,000 - "Real-time packet transforms to avoid re-transmissions"

Issued June 2, 2015 Compl. ¶34

The Invention Explained

• Problem Addressed: Like the '852 Patent, the '000 Patent addresses inefficiencies caused by the re-transmission of corrupted or lost packets in real-time data streams '000 Patent, col. 1:20-45
• The Patented Solution: The solution is substantively identical to that of the '852 Patent, involving the creation of a packet that contains sufficient repair information to allow a receiving or relaying device to fix errors without requesting a re-transmission '000 Patent, abstract The complaint notes that the claims of the '000 patent address the same technical advancements as the '852 Patent Compl. ¶35
• Technical Importance: The invention aims to improve the efficiency and reliability of transporting real-time streams over networks Compl. ¶35

Key Claims at a Glance

• The complaint asserts independent claim 1 Compl. ¶65
• The essential elements of method claim 1 include:
  • modifying said packet by adding redundant information to the packet;
  • modifying at least one packet header to add a position offset reference number that points to redundant information;
  • revising all checksums within the packet as modified to agree with the packet contents as modified;
  • transmitting the packet through a network, wherein transmitting further comprises checking the modified packet during transmission;
  • if the modified packet is determined to have a checksum mismatch, modifying the packet by retrieving the redundant information and replacing a portion of the packet;
  • calculating new checksums for the packet;
  • revising all checksums within the packet as modified to agree with the contents of the modified packet; and
  • upon receipt, modifying the packet to return the packet's format to that of the standard packet format.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 8,477,762 - "Self-forming VoIP Network"

Issued July 2, 2013 Compl. ¶36

The Invention Explained

• Technology Synopsis: The patent describes a technical solution to a problem in Voice over IP (VoIP) networks where communication is lost if the connection to a central Session Initiation Protocol (SIP) server is terminated Compl. ¶38 The invention enables a "self-forming" network where VoIP nodes in an "isolated cluster" can build and maintain a distributed, local SIP registry by exchanging information with each other, thereby allowing VoIP calls to be established and continued without a central server Compl. ¶39 '762 Patent, abstract

Key Claims at a Glance

• Asserted Claims: The complaint asserts independent claim 1 Compl. ¶80
• Accused Features: The accused features are part of Cisco's Webex VoIP collaboration products Compl. ¶13 Specifically, the complaint targets the "Site Survivability" and "Enhanced Site Survivability" functionalities, which are alleged to provide continued calling capabilities during a cloud outage by using local gateways that form an isolated network, mirroring the invention's functionality Compl. Ex. 6, p. 2

III. The Accused Instrumentality

Product Identification

• The complaint names two categories of accused products: (1) Cisco SD-WAN solutions and equipment that use Forward Error Correction ("FEC"), which are accused of infringing the '852 and '000 patents; and (2) Cisco Webex VoIP collaboration products, accused of infringing the '762 patent Compl. ¶13

Functionality and Market Context

• The accused Cisco SD-WAN products provide a virtual Wide Area Network architecture designed to efficiently connect users and applications Compl. Ex. 4, p. 2 The accused FEC feature is a mechanism used to improve the reliability of real-time traffic, such as voice and video, by sending extra "parity" packets for every group of data packets. This allegedly allows the receiver to reconstruct a lost packet without requiring re-transmission from the source Compl. Ex. 4, p. 2 A diagram from a Cisco blog post illustrates "Forward Error Correction" as one of the "Key Building Blocks of AppQoE" (Application Quality of Experience) integrated with its SD-WAN solutions Compl. Ex. 4, p. 3
• The accused Cisco Webex products are part of a cloud-based calling system that uses VoIP Compl. Ex. 6, p. 2 The specific accused functionalities, "Site Survivability" and "Enhanced Site Survivability," are designed to maintain network connectivity and calling capabilities during an outage of the main cloud service. This is accomplished through the use of on-premises gateways or nodes that provide backup call control for endpoints, allegedly forming an isolated, self-sufficient network Compl. Ex. 6, p. 2 The complaint provides a high-level network diagram illustrating how Webex Calling with Site Survivability routes calls during a cloud outage using on-premises gateways Compl. Ex. 6, p. 2

IV. Analysis of Infringement Allegations

'852 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
modifying said packet by adding redundant information to the packet;	Cisco's SD-WAN inserts a parity packet ("redundant information") for every four standard network data packets.	¶50; Ex. 4, p. 3	col. 9:20-28
modifying at least one packet header to add a position offset reference number that points to redundant information;	On information and belief, specific FEC sequence numbers or other information in the packet header(s) (encoded "FEC Header") serve as a position offset reference number to maintain packet order and help the receiver identify the parity packet.	¶50; Ex. 4, p. 4	col. 10:49-54
revising all checksums within the packet as modified to agree with the packet contents as modified;	The parity packet is created using XOR operations, and for the modified packet to be valid, it would require a revised checksum. Each data packet and parity packet also includes a CRC or checksum to ensure integrity.	¶50; Ex. 4, p. 5	col. 10:25-30
transmitting the packet through a network;	Cisco's SD-WAN policies transmit the modified packets through the network.	¶50; Ex. 4, p. 6	col. 5:16-18
modifying the packet, including modifying all checksums, to return the packet's format to that of the standard packet format;	If a group of packets is transmitted without error, the receiving end modifies the packet to return it to the standard format by discarding the parity packet.	¶50; Ex. 4, p. 6	col. 5:15-18
if the modified packet... is determined to have a checksum mismatch as received, modifying the packet by retrieving the redundant information... and replacing a portion of the packet...;	The receiving WAN device can reconstruct a lost packet based on the parity value if a checksum mismatch is detected, effectively retrieving redundant information to replace the lost portion.	¶50; Ex. 4, p. 7	col. 3:36-41
and revising all checksums within the packet as modified to agree with the contents of the modified packet.	When a data packet is corrected using FEC, the packet's content is modified. The checksum is then revised and recalculated to reflect the new content of the replaced packet.	¶50; Ex. 4, p. 7	col. 5:32-38

'000 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
modifying said packet by adding redundant information to the packet;	The infringement allegations for the corresponding element of claim 1 of the '852 patent are incorporated by reference.	¶65; Ex. 5, p. 2	col. 10:20-25
modifying at least one packet header to add a position offset reference number that points to redundant information;	The infringement allegations for the corresponding element of claim 1 of the '852 patent are incorporated by reference.	¶65; Ex. 5, p. 2	col. 10:49-54
revising all checksums within the packet as modified to agree with the packet contents as modified;	The infringement allegations for the corresponding element of claim 1 of the '852 patent are incorporated by reference.	¶65; Ex. 5, p. 2	col. 10:25-30
transmitting the packet through a network, wherein transmitting further comprises the steps of checking the modified packet during transmission;	The receiving end examines the sequence numbers of the packets to check if any are missing ("checking the modified packet during transmission").	¶65; Ex. 5, p. 2	col. 5:16-18
if the modified packet is determined to have a checksum mismatch as received, modifying the packet by retrieving the redundant information... and replacing a portion of the packet...;	The infringement allegations for the corresponding element of claim 1 of the '852 patent are incorporated by reference.	¶65; Ex. 5, p. 3	col. 3:36-41
calculating new checksums for packet; and revising all checksums within the packet as modified to agree with the contents of the modified packet;	When a data packet is corrected using FEC, its content is modified. The checksum must be revised and recalculated to reflect the replaced packet's new content.	¶65; Ex. 5, p. 3	col. 7:41-47
upon receipt, modifying the packet to return the packet's format to that of the standard packet format.	If packets are transmitted without error, the packet is modified to return to "standard packet format" by discarding the parity packet.	¶65; Ex. 5, p. 3	col. 7:48-52

• Identified Points of Contention:
  • Scope Questions: The complaint alleges infringement of the '852 and '000 patents based on Cisco's use of Forward Error Correction. However, the complaint also states that "Cisco's exact specifications of its FEC algorithms and packet structure are not public" Compl. Ex. 4, p. 2 A central dispute will be whether the specific implementation of Cisco's FEC meets the claim limitations. For example, the patents require modifying a header to add a "position offset reference number." The infringement analysis raises the question of whether the "FEC Header" and sequence numbers allegedly used by Cisco Compl. Ex. 4, p. 4 function as the claimed "position offset reference number" or represent a technically different approach to identifying and using redundant data.
  • Technical Questions: A diagram from a Cisco presentation explains its FEC process, showing a "Sender" transmitting a block of four data packets and a parity packet to a "Receiver" Compl. Ex. 4, p. 4 The claims require several specific modification and revision steps both before transmission and after receipt. A key technical question will be what evidence demonstrates that the accused SD-WAN products perform each of these discrete modification steps, such as "revising all checksums" after adding redundant data and again after error correction, as opposed to simply calculating a single checksum on a final packet structure.

V. Key Claim Terms for Construction

• The Term: "position offset reference number" (from '852 Patent, claim 1; '000 Patent, claim 1)
• Context and Importance: This term is central to the infringement theory for the '852 and '000 patents. The patents describe a specific mechanism for pointing to redundant data within a packet. Practitioners may focus on this term because the complaint alleges, on "information and belief," that sequence numbers in a Cisco "FEC Header" meet this limitation Compl. Ex. 4, p. 4 The case may turn on whether a sequence number, which indicates order, can be construed as a "position offset reference number," which suggests a pointer to a location.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification provides an example where "DLEN (the Data Length value...) is utilized as a position offset reference number that points to the duplicate data location" '852 Patent, col. 10:49-53 A party could argue this is just one example and that any number or value that allows the system to locate the redundant data, including a sequence number within a known block structure, serves the function of a "position offset reference number."
  • Evidence for a Narrower Interpretation: The use of the words "position offset" and "reference number" suggests a specific technical meaning: a numerical value that directly indicates a memory or data offset (e.g., a byte count) to the start of the redundant information. A party could argue that a mere sequence number, which primarily denotes order rather than location, does not meet this more specific definition.

VI. Other Allegations

• Indirect Infringement: The complaint alleges that Cisco induces infringement by providing extensive documentation, user guides, advertisements, blog posts, and technical support services that instruct and encourage customers to use the accused features in an infringing manner Compl. ¶¶51-53 Compl. ¶¶81-83 It further alleges contributory infringement, stating that the accused components are specially made for use in an infringing manner and are not staple articles of commerce suitable for substantial non-infringing use Compl. ¶¶59-60 Compl. ¶¶74-75
• Willful Infringement: The complaint alleges willful infringement based on both pre-suit and post-suit knowledge. It claims Cisco had pre-suit knowledge from meetings in 2009 where Plaintiff allegedly disclosed its technology and pending patent applications to Cisco executives Compl. ¶¶41-42 It also alleges knowledge from at least the date of a June 22, 2022 notice letter Compl. ¶44 and the filing of the complaint. The infringement is characterized as "intentional, deliberate, willful, and malicious" Compl. ¶62 Compl. ¶77 Compl. ¶92

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

• A key evidentiary question will be one of technical implementation: given that the complaint acknowledges Cisco's FEC algorithms are not public Compl. Ex. 4, p. 2, the case for the '852 and '000 patents will depend on what discovery reveals about the precise structure of Cisco's SD-WAN packets. Does the accused system in fact use a "position offset reference number" as claimed, or does it employ a technically distinct method for error correction that falls outside the scope of the claims?
• A core issue for the '762 patent will be one of definitional scope: can the patent's concept of an "isolated cluster" of peer nodes that "build" a "local SIP registry by exchanging SIP information" '762 Patent, claim 1 be construed to cover the architecture of Cisco's Webex Survivability feature? The dispute may center on whether the accused on-premises gateways function as a decentralized, peer-to-peer collective as claimed, or as a more conventional, hierarchical failover system that is technically distinct from the patented invention.
• An overarching question will concern intent: do the alleged 2009 pre-suit meetings, where Plaintiff claims it disclosed its technology and pending patents to Cisco Compl. ¶41, provide sufficient evidence of pre-suit knowledge and copying to support the claim for willful infringement and potentially enhanced damages?