Sable Networks Inc v. Dell Tech Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Sable Networks, Inc. (California) and Sable IP, LLC (Delaware)
  • Defendant: Dell Technologies Inc. (Delaware), Dell Inc. (Delaware), and EMC Corporation (Massachusetts)
  • Plaintiff's Counsel: Berger & Hipskind LLP
• Case Identification: 6:20-cv-00569, W.D. Tex., 06/26/2020
• Venue Allegations: Venue is alleged to be proper as Defendants are headquartered in the district, have transacted business in the district, have regular and established places of business in the district, and have committed acts of infringement in the district.
• Core Dispute: Plaintiff alleges that Defendant's networking switch and edge devices infringe four patents related to efficient data packet management, including network tunneling, failure recovery, virtual router implementation, and penalization of misbehaving traffic.
• Technical Context: The patents address foundational technologies for managing data flow in complex computer networks, which are critical for the performance, reliability, and security of modern internet infrastructure.
• Key Procedural History: The complaint asserts that the underlying technology was developed by internet pioneer Dr. Lawrence G. Roberts. It notes that the patents-in-suit have been cited in the patent applications of numerous major technology companies. Specifically, the complaint alleges Defendant had pre-suit knowledge of the '209 patent because it was cited during the prosecution of a patent issued to EMC Corporation, which is now part of Dell. Subsequent to the filing of the complaint, Inter Partes Review (IPR) proceedings have resulted in the disclaimer or cancellation of all asserted claims of U.S. Patent Nos. 6,977,932, 7,630,358, and 8,243,593, a fact which will be central to the disposition of the counts related to those patents.

Case Timeline

Date	Event
2001-06-12	Priority Date for U.S. Patent No. 7,428,209
2001-07-09	Priority Date for U.S. Patent No. 7,630,358
2002-01-16	Priority Date for U.S. Patent No. 6,977,932
2004-12-22	Priority Date for U.S. Patent No. 8,243,593
2005-12-20	U.S. Patent No. 6,977,932 Issued
2008-09-23	U.S. Patent No. 7,428,209 Issued
2009-12-08	U.S. Patent No. 7,630,358 Issued
2011-12-27	EMC patent citing the '209 patent Issued Compl. ¶112
2012-08-14	U.S. Patent No. 8,243,593 Issued
2020-06-26	Complaint Filed

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

U.S. Patent No. 6,977,932 - System and Method for Network Tunneling Utilizing Micro-Flow State Information

The Invention Explained

• Problem Addressed: The patent describes that conventional network tunneling techniques, such as Multi-protocol Label Switching (MPLS), do not maintain state information for individual "micro-flows" within a larger data tunnel, making it difficult to provide granular Quality of Service (QoS) ʼ932 Patent, col. 2:10-16 Furthermore, managing flow state for millions of individual micro-flows is described as a "prohibitively time consuming and processor intensive task" ʼ932 Patent, col. 2:39-44
• The Patented Solution: The invention proposes a two-tiered system using "micro-flow blocks" and "aggregate flow blocks" (AFBs) to manage flow state information efficiently ʼ932 Patent, col. 3:1-14 Each micro-flow is associated with a flow block containing an identifier that points to a corresponding AFB. The AFB stores information and statistics common to a larger group of flows, such as those in a particular network tunnel ʼ932 Patent, abstract ʼ932 Patent, FIG. 11 This structure avoids the need to search and update millions of individual flow entries when managing the tunnel as a whole.
• Technical Importance: This hierarchical approach to flow state management was designed to enable scalable network tunneling with sophisticated QoS capabilities, addressing a critical need as internet traffic volume and complexity increased ʼ932 Patent, col. 2:63-65

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶82
• Claim 1 of the '932 Patent recites the following essential elements:
  • creating a flow block having flow state information for a received first data packet of a micro-flow;
  • storing a tunnel identifier for the micro-flow in the flow block, which identifies a selected network tunnel;
  • indexing an aggregate flow block using the tunnel identifier, where the aggregate flow block has tunnel specific information;
  • transmitting the data packet using the selected network tunnel based on the tunnel specific information;
  • wherein statistics for the selected network tunnel are stored using the aggregate flow block.
• The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 7,428,209 - Network Failure Recovery Mechanism

The Invention Explained

• Problem Addressed: The patent identifies that traditional failure recovery mechanisms in large networks are "extremely slow," often taking around 30 seconds for network topology to reconverge after a failure ʼ209 Patent, col. 2:19-24 During this time, traffic continues to be routed to the failed component and dropped, which is unacceptable for time-critical applications like video or voice calls ʼ209 Patent, col. 2:24-29
• The Patented Solution: The invention discloses a method where, upon detection of a failure along a route, a message is directed immediately back to the source of the traffic (e.g., an ingress module in a router) ʼ209 Patent, col. 3:49-52 This message informs the source of the failure, allowing it to instantly reroute subsequent data packets to an alternate path, thus avoiding the failed component without waiting for network-wide topology updates ʼ209 Patent, col. 3:52-60 The message can also carry the data from the original packet that encountered the failure, enabling the source to resend it and prevent data loss ʼ209 Patent, abstract
• Technical Importance: This direct-feedback mechanism allows for significantly faster failure recovery (estimated at 10ms or less), minimizing data loss and improving the reliability of services sensitive to network interruption ʼ209 Patent, col. 3:59-64

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶109
• Claim 1 of the '209 Patent recites the following essential elements:
  • sending, via a first route, a first set of information from an ingress module to a first egress module;
  • detecting a failure of said first egress module;
  • directing a message to said ingress module informing it of the failure;
  • in response to the message, selecting an alternate egress module;
  • sending a future set of information from the ingress module to the alternate egress module;
  • preventing other sets of information for the same flow from being sent to the failed first egress module.
• The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 7,630,358 - Mechanism for Implementing Multiple Logical Routers Within A Single Physical Router

• Technology Synopsis: The patent discloses a system for implementing multiple "logical routers" within a single piece of physical router hardware. The invention allows these logical routers to appear as interconnected, standalone routers to the external network while using more efficient "internal links" for communication between them, combining the benefits of multi-router architectures with the efficiency of a single device Compl. ¶¶52, 57
• Asserted Claims: The complaint asserts at least independent claim 1 Compl. ¶129
• Accused Features: The complaint accuses Dell's PowerSwitch S-Series and Z-Series devices of infringement Compl. ¶119 The accused functionality is Virtual Routing and Forwarding (VRF), which allegedly "partitions a physical router into multiple virtual routers" and "acts like a logical router" Compl. ¶¶121-122 Compl. p. 32 A Dell diagram illustrates how a network with VRF segments traffic compared to a network without it Compl. p. 33

U.S. Patent No. 8,243,593 - Mechanism for Identifying and Penalizing Misbehaving Flows in a Network

• Technology Synopsis: The invention provides a method for identifying and controlling undesirable network traffic (such as P2P file sharing) based on its behavioral statistics (e.g., data volume, flow duration) rather than ancillary factors like port numbers, which can be easily disguised Compl. ¶¶62-63 Once a flow is determined to be exhibiting undesirable behavior, the system can enforce a penalty, such as an increased packet drop rate, to control it Compl. ¶¶64, 68
• Asserted Claims: The complaint asserts at least independent claim 4 Compl. ¶153
• Accused Features: The complaint accuses Dell EMC SD-WAN Edge 3000 and 600 Series devices of infringement Compl. ¶138 The alleged infringing functionality is provided by "factory-integrated" VeloCloud software, which performs "deep application recognition," monitors performance metrics, and can take "On Demand Remediation" to penalize misbehaving flows Compl. ¶¶144, 147, 152 A marketing slide shows a "Measure, Steer, Remediate" capability for assured application performance Compl. p. 41

III. The Accused Instrumentality

Product Identification

• For the '932 Patent: Dell EMC PowerSwitch N1500, N2000, N3000, and N4000 Series devices ("Dell '932 Products") Compl. ¶71
• For the '209 Patent: Dell EMC PowerEdge MX infrastructure products with the Dell EMC SmartFabric OS10 or later network operating system ("Dell '209 Products") Compl. ¶91

Functionality and Market Context

• The Dell '932 Products are network switches that, according to the complaint, use "flow state information to perform a method of network tunneling" Compl. ¶73 The complaint alleges these products utilize "Group Flows" and "Group Type FF Flows" to manage data transmission, which purportedly corresponds to the patent's aggregate flow block technology Compl. ¶77 A diagram from Dell documentation is used to illustrate the packet processing pipeline within the devices (Compl. ¶75, p. 20).
• The Dell '209 Products are infrastructure components that allegedly include a mechanism for failure recovery Compl. ¶93 The complaint alleges this is accomplished through a feature called "Uplink Failure Detection" used with "Virtual Link Trunking" (VLT) Compl. ¶96 This feature is alleged to detect when an uplink connection goes down and, in response, disable the downstream VLT port-channel, thereby rerouting traffic away from the failure Compl. ¶96

IV. Analysis of Infringement Allegations

'932 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
creating a flow block having flow state information for a received first data packet of a micro-flow;	The Dell '932 Products allegedly create a flow block for a received data packet, with processing occurring via an ingress port flow table.	¶75	col. 10:25-44
storing a tunnel identifier for the micro-flow in the flow block, the tunnel identifier identifying a selected network tunnel...;	The products are alleged to store a tunnel identifier for the micro-flow in the flow block, identifying a tunnel to be used for transmission.	¶76	col. 10:45-51
indexing an aggregate flow block using the tunnel identifier, the aggregate flow block having tunnel specific information...;	The products are alleged to "index an aggregate flow block using the tunnel identifier," with Dell's "Group Flows" and "Group Type FF Flows" corresponding to the claimed aggregate flow block.	¶77	col. 10:52-64
transmitting the data packet using the selected network tunnel based on the tunnel specific information;	The products allegedly transmit data packets using the selected network tunnel, enabled by "action buckets" that specify output actions.	¶79	col. 9:18-24
wherein statistics for the selected network tunnel are stored using the aggregate flow block.	The products allegedly utilize an aggregate flow block that "stores statistics for the selected network tunnel," as evidenced by documentation showing fields for "Packets" and "Bytes."	¶78	col. 9:49-55

Identified Points of Contention ('932 Patent):

• Scope Questions: A central question is whether Dell's "Group Flow" and "Group Type FF Flow" functionalities, as described in command-line interface outputs, fall within the scope of the patent's "aggregate flow block." The court may need to determine if these are merely marketing terms or if they represent a technical implementation that meets the claim limitations.
• Technical Questions: The complaint alleges the products "index an aggregate flow block using the tunnel identifier" Compl. ¶77 A technical question is whether the evidence provided demonstrates this specific operation, or if the "Group" functionality operates in a technically distinct manner from the indexing step required by the claim.

'209 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
sending, via a first route, a first set of information from an ingress module to a first egress module for forwarding...;	The Dell '209 Products are alleged to send information from an ingress module to a first egress module for forwarding to an external destination.	¶¶94-95	col. 11:34-40
detecting a failure of said first egress module;	The products' "Uplink Failure Detection" feature allegedly detects when the status of an uplink connection goes down, which is presented as detecting a failure of the first egress module.	¶¶96-97	col. 13:46-52
in response to said failure... directing a message to said ingress module informing said ingress module of said... failure;	When a link goes down, the "VLT module sends the VLT port channel disable request to the Interface Manager ('IFM')," which is alleged to be the informing message.	¶96; ¶98	col. 14:1-10
in response to said message, selecting an alternate egress module capable of forwarding information to said destination;	The complaint alleges the products select an alternate egress module in response to the message.	¶99	col. 16:59-67
sending, via a second route, a future set of information from said ingress module to said alternate egress module...;	The products are alleged to send future information to the selected alternate egress module for forwarding to the destination.	¶100	col. 17:1-9
preventing other sets of information associated with said flow from being sent from said ingress module to said first egress module...;	The products allegedly prevent data from being sent to the failed module by storing an indication in a flow block that such information should not be sent.	¶101; ¶105	col. 22:5-15

Identified Points of Contention ('209 Patent):

• Technical Questions: A key technical question is which entity performs the "selecting" of the alternate path. The claim requires the router (specifically, its ingress module) to select an "alternate egress module." However, evidence cited in the complaint states that failure detection "allows the downstream servers to select alternate paths" Compl. p. 27, which suggests an external device, not the accused router, performs the selection.
• Scope Questions: It raises the question of whether the "VLT port channel disable request" Compl. ¶96 constitutes the specific "message... informing said ingress module of said first egress module failure" as recited in the claim, which further requires the message to be directed along a return route different from the original path.

V. Key Claim Terms for Construction

For the '932 Patent:

• The Term: "aggregate flow block"
• Context and Importance: This term is the central component of the patent's two-tiered efficiency solution. The infringement case for the '932 patent hinges on whether Dell's "Group Flow" feature can be proven to be an "aggregate flow block." Practitioners may focus on this term because its definition will determine if the accused product's architecture maps onto the claimed invention.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification's summary and abstract describe it functionally as a block that "includes tunnel specific information" and "stores statistics for the selected network tunnel" ʼ932 Patent, abstract ʼ932 Patent, col. 3:15-20, which could support an interpretation covering any feature that performs these functions.
  • Evidence for a Narrower Interpretation: The specification consistently discusses the invention in the context of MPLS and Label Switched Paths (LSPs) ʼ932 Patent, col. 2:30-62 Specific embodiments, like FIG. 11, show a particular structure where AFBs can point to other AFBs. This could support an argument that the term is limited to the specific MPLS-related embodiments disclosed.

For the '209 Patent:

• The Term: "selecting an alternate egress module"
• Context and Importance: This term defines the active recovery step. The infringement analysis may turn on whether the accused router itself performs this selection. Practitioners may focus on this term because the complaint's own evidence suggests a downstream server, not the accused router, may be performing the selection.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: A plaintiff could argue that "selecting" should be interpreted broadly to include the router's act of disabling a failed path, which functionally forces traffic to an alternate path, thereby "selecting" it by default.
  • Evidence for a Narrower Interpretation: The patent states that in response to the failure message, "the source reroutes one or more future packets... to an alternate route" ʼ209 Patent, col. 3:55-58 This suggests an active, deliberate rerouting decision made by the source (the ingress module), not merely a passive disabling that allows an external device to choose a new path.

VI. Other Allegations

• Indirect Infringement: The complaint alleges that Dell induces infringement of all four patents by providing customers with products and accompanying documentation, user manuals, and training materials that allegedly instruct users to operate the products in an infringing manner Compl. ¶¶83, 85 Compl. ¶¶110, 113 Compl. ¶¶130, 132 Compl. ¶¶154, 156 For the '209 patent, the complaint specifically alleges pre-suit knowledge based on Dell subsidiary EMC Corporation citing the '209 patent during the prosecution of its own U.S. Patent No. 8,085,794 Compl. ¶112
• Willful Infringement: For all patents-in-suit, the complaint alleges willfulness based on knowledge acquired "at least service of this Complaint or shortly thereafter" Compl. ¶¶84, 111, 131, 155 The allegation of pre-suit knowledge regarding the '209 patent may be used to support a finding of pre-suit willfulness for infringement of that specific patent.

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

1. Claim Enforceability: A threshold issue for three of the four patents-in-suit will be their validity and enforceability. Given that post-filing IPR proceedings resulted in the disclaimer or cancellation of all asserted claims of the '932, '358, and '593 patents, the court must first determine if any legal basis remains for these infringement counts to proceed.

2. Locus of Action: For the '209 patent, a key evidentiary question will be one of functional attribution: does Dell's "Uplink Failure Detection" feature cause the accused router to perform the claimed step of "selecting an alternate egress module," or does it merely signal a failure to an external device (e.g., a server) which then performs the selection, potentially placing the key inventive step outside the accused device?

3. Technical Equivalence: Assuming any claims of the '932 patent are deemed enforceable, a central question will be one of definitional scope: can the term "aggregate flow block", which is rooted in a specific two-tiered data structure, be construed to read on Dell's "Group Flow" feature as described in the provided command-line interface outputs, or is there a fundamental mismatch in their technical architecture and operation?