2:18-cv-00057
Sonus Networks Inc v. Metaswitch Networks Ltd
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Sonus Networks, Inc., d/b/a/ Ribbon Communications Operating Company (Delaware)
- Defendant: Metaswitch Networks Ltd (United Kingdom) and Metaswitch Networks Corporation (Delaware)
- Plaintiff’s Counsel: Baker Botts L.L.P.
- Case Identification: 2:18-cv-00057, E.D. Tex., 03/08/2018
- Venue Allegations: Venue is alleged based on Defendants maintaining a regular and established place of business within the Eastern District of Texas.
- Core Dispute: Plaintiff alleges that Defendant’s softswitch and media gateway products infringe five patents related to telecommunications network interconnection, call routing, and system management.
- Technical Context: The technology at issue addresses the challenge of bridging legacy circuit-switched telephone networks with modern packet-switched IP networks for applications like Voice over IP (VoIP).
- Key Procedural History: The complaint alleges that Defendant has been aware of U.S. Patent No. 6,961,334 since at least May 6, 2010, because it was brought to Defendant's attention during the prosecution of one of Defendant's own patents. This allegation may form the basis for a claim of pre-suit willful infringement for that specific patent. For the other four patents, the complaint alleges knowledge only as of the date of the complaint's service.
Case Timeline
| Date | Event |
|---|---|
| 1998-07-31 | ’238 Patent Priority Date |
| 1999-03-30 | ’269 and ’441 Patents Priority Date |
| 2001-03-29 | ’334 and ’627 Patents Priority Date |
| 2002-04-30 | ’238 Patent Issued |
| 2004-08-10 | ’269 Patent Issued |
| 2005-09-27 | ’441 Patent Issued |
| 2005-11-01 | ’334 Patent Issued |
| 2007-01-02 | ’627 Patent Issued |
| 2010-05-06 | Alleged pre-suit knowledge of ’334 Patent by Defendant |
| 2014-01-01 | Earliest date of referenced accused product documentation |
| 2018-03-08 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 6,381,238 - "Apparatus and Method for a Telephony Gateway"
The Invention Explained
- Problem Addressed: The patent’s background section describes prior art telephony gateways as being inflexible and costly because they either relied on a single circuit-switch fabric or used two separate, complex switch fabrics (one for circuit networks, one for packet networks) (Compl. ¶19; ’238 Patent, col. 2:7-11).
- The Patented Solution: The invention proposes a more flexible and efficient gateway architecture built around a single packet switch fabric. All traffic, whether originating from a circuit or packet network, is first converted to packet-based signals. These signals are then transferred by the single packet switch fabric among specialized functional servers: a circuit network server for interfacing with the circuit network, a packet network server for interfacing with the packet network, and a signal processing server for tasks like transcoding (’238 Patent, Abstract; col. 2:13-31).
- Technical Importance: This single-fabric, server-based architecture was intended to reduce the cost and complexity of gateways while increasing their flexibility in handling different types of telecommunications traffic (Compl. ¶19).
Key Claims at a Glance
- The complaint asserts at least independent Claim 1 (Compl. ¶22).
- Essential elements of Claim 1 include:
- a packet switch fabric;
- a circuit network server having a port to the circuit network, a digital signal processor (DSP) for packet adaptation, and a port to the packet switch fabric;
- a packet network server having a port to the packet switch fabric and a port to the packet network;
- a signal processing server having a port to the packet switch fabric and a DSP for performing signal processing;
- wherein the packet switch fabric transfers packet-based signals among the three types of servers.
- The complaint alleges infringement of "one or more claims" of the patent, suggesting the right to assert additional claims is reserved (Compl. ¶21).
U.S. Patent No. 6,775,269 - "Method and System for Routing Telephone Calls between a Public Switched Telephone Network and an Internet Protocol Network"
The Invention Explained
- Problem Addressed: The patent’s background notes that routing telephone calls between different network types involves complex signaling algorithms, which makes modifying services for a customer or group of customers cumbersome (’269 Patent, col. 1:26-30).
- The Patented Solution: The invention describes a method for routing calls using a hierarchical system of data tables. The system determines an address for the calling party, accesses a table associated with that address, and this first table contains pointers that direct the system to one or more additional tables. The final route is determined based on information looked up in these subsequent, pointed-to tables (’269 Patent, Abstract; col. 2:44-54).
- Technical Importance: This nested, table-driven routing structure is intended to allow for more flexible and straightforward modification of a subscriber's services and privileges without requiring complex reprogramming of the core routing logic (Compl. ¶38).
Key Claims at a Glance
- The complaint asserts at least independent Claim 1 (Compl. ¶41).
- Essential elements of Claim 1 include:
- receiving a service request from a first network;
- translating the service request;
- determining a route for the request over a second network;
- generating signaling for the determined route;
- wherein the step of determining the route comprises: determining a calling party's address, accessing a table associated with that address that contains pointers to additional tables, accessing at least one of the additional tables via a pointer, and determining the route based on the information in that additional table.
- The complaint alleges infringement of "one or more claims," reserving the right to assert others (Compl. ¶40).
U.S. Patent No. 6,950,441 - "System and Method to Internetwork Telecommunication Networks of Different Protocols"
Technology Synopsis
This patent describes a softswitch architecture composed of functionally distinct agents. A "signaling agent" is coupled to various networks and is responsible for receiving incoming signaling messages and translating them into a standardized "call model event." A separate "call agent" receives this call model event and manages the call logic, such as requesting resources and generating outgoing signaling messages (’441 Patent, Abstract; Compl. ¶53). This modular design aims to improve interoperability and facilitate cost reduction for telephony services (Compl. ¶53).
Asserted Claims
At least Claim 1 (Compl. ¶56).
Accused Features
The complaint alleges that Defendant’s Universal Media Gateways (UMGs) function as the claimed "signaling agent," while the Metaswitch Telephony Application Server (MTAS) functions as the claimed "call agent" (Compl. ¶¶ 58-59).
U.S. Patent No. 6,961,334 - "Intelligence Engine"
Technology Synopsis
This patent discloses a method for managing network traffic during a controller failure. The system involves an "intelligence engine" that receives an "indicator signal" of a failure associated with a first call agent. In response, the engine accesses a database and reassigns control of the data traffic to a second call agent by changing an IP address entry in that database (’334 Patent, Abstract; Compl. ¶66). The purpose is to enable seamless rerouting of traffic to a backup controller without disrupting other networks (Compl. ¶66).
Asserted Claims
At least Claim 1 (Compl. ¶68).
Accused Features
The complaint maps this invention onto two features of the accused products: the "Emergency Standalone (ESA)" function, which preserves service during network outages by having a gateway assume control, and the "multi-site active-active redundancy" feature of the clustered MTAS, which allegedly redirects traffic upon detecting the unavailability of a call server (Compl. ¶¶ 71, 74).
U.S. Patent No. 7,158,627 - "Method and System for Inhibiting Softswitch Overload"
Technology Synopsis
The patent addresses the problem of softswitch overload. It describes a method where a softswitch monitors operational criteria such as its processing system usage, memory usage, or the number of calls being handled by its subsystems. If any of these criteria exceed a predefined threshold, the system actively limits the number of new calls it will process to prevent a system failure (’627 Patent, Abstract; Compl. ¶81).
Asserted Claims
At least Claim 1 (Compl. ¶84).
Accused Features
The complaint alleges that Defendant's products perform this claimed method by advertising capabilities such as supporting "6,000,000 busy hour call attempts" and maintaining "carrier class reliability of 99.999%," which allegedly requires monitoring and limiting calls to prevent system failure (Compl. ¶¶ 88-91).
III. The Accused Instrumentality
Product Identification
The accused instrumentalities are Metaswitch's Integrated Softswitches (e.g., VP6010 and VP6050), Universal Media Gateways (UMGs) (e.g., MG6010 and MG6050), and the Metaswitch Telephony Application Server (MTAS) (Compl. ¶17).
Functionality and Market Context
These products are alleged to function collectively as a telecommunications gateway and softswitch platform, designed to interconnect legacy circuit-switched telephone networks (e.g., SS7, ISDN) with modern packet-based IP networks (Compl. ¶¶ 24-25). Their alleged functionalities include transforming signaling protocols, routing calls between different network types, providing redundancy and failover capabilities in case of network outages, and managing system load to ensure reliability (Compl. ¶¶ 47, 71, 91). The complaint asserts that these products directly compete with Plaintiff's product portfolio (Compl. ¶17). A screenshot in the complaint describes the "Emergency Standalone (ESA)" function, which preserves service during network outages between a media gateway and its controlling MTAS (Compl. p. 21).
IV. Analysis of Infringement Allegations
'238 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| a packet switch fabric | The "SX6100 ethernet switch blades" and "10 Gigabit Ethernet fabric backplane" included in the Integrated Softswitches and UMGs are alleged to be the packet switch fabric. | ¶¶26, 28 | col. 2:15-16 |
| a circuit network server having a first port for sending and receiving circuit-based signals with the circuit network, the circuit network server having a digital signal processor for providing packet adaptation... | The "circuit switched TDM interfaces" along with their controlling hardware and software on the "rear transmission modules DX6730" and "shelf managers SMC6050" are alleged to comprise the circuit network server. | ¶30 | col. 2:17-22 |
| a packet network server having a first port for sending and receiving packet-based signals with the packet switch fabric and a second port for sending and receiving packet-based signals with the packet network | The Ethernet "packet interfaces" along with their controlling hardware and software on the "DX6730 and/or SMC6050" modules are alleged to comprise the packet network server. | ¶32 | col. 2:22-26 |
| a signal processing server having a port for sending and receiving packet-based signals with the packet switch fabric, the signal processing server having a digital signal processor for performing signal processing... | The "DX6730 resource cards" containing "codecs and digital signal processors" and their associated controlling hardware and software are alleged to comprise the signal processing server. A provided visual lists supported codecs (Compl. p. 10). | ¶33 | col. 2:26-29 |
| wherein the packet switch fabric transfers packet-based signals among the packet network server, the signal processing server, and the circuit network server. | The complaint alleges that the accused gateway products are structured such that the Ethernet backplane transfers signals among the aforementioned alleged server components. | ¶23 | col. 2:29-31 |
Identified Points of Contention
- Scope Questions: Claim 1 recites three distinct server elements: "a circuit network server," "a packet network server," and "a signal processing server." The complaint alleges these elements are met by various functions performed by overlapping hardware modules (e.g., the DX6730 and SMC6050) (Compl. ¶¶ 30-33). A central dispute may be whether a single, multi-function hardware module can satisfy multiple, separately recited "server" limitations, or if the claim requires structurally distinct components.
- Technical Questions: What evidence does the complaint provide that the alleged server components operate as distinct functional entities that communicate through the packet switch fabric, as opposed to operating as a more integrated, monolithic system?
'269 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| A method for routing a telephone call originating at a first network that utilizes a first signaling protocol to a termination in a second network that uses a second signaling protocol comprising: receiving a service request... translating the service request... | The accused softswitch products are alleged to perform these steps because they are "operable to route a telephone call originating at a first network that utilizes a first signaling protocol to a termination in a second network that uses a second signaling protocol" (Compl. ¶43). | ¶¶43, 47 | col. 2:35-41 |
| determining a route for processing the service request over the second network | The complaint alleges this step is met because the products provide "Class 4 and 5 calling functionality," which on "information and belief" includes the use of "routing and translation tables" (Compl. ¶48). | ¶48 | col. 2:44-47 |
| wherein determining the route for processing the request over the second network comprises: determining an address... accessing a table associated with the address, the table comprising a plurality of pointers to a plurality of additional tables... | This multi-step limitation is alleged on "information and belief" based on the products' advertised "Class 4 and 5 calling functionality" (Compl. ¶48). The complaint does not cite specific marketing materials describing a nested, pointer-based table structure. A visual shows the MTAS platform (Compl. p. 15). | ¶48 | col. 2:48-54 |
| in response to accessing the at least one of the additional tables, determining the route for processing the request based on the at least one of the additional tables. | This is also alleged on "information and belief" stemming from the product's general routing capabilities (Compl. ¶48). | ¶48 | col. 2:51-54 |
Identified Points of Contention
- Evidentiary Questions: The core inventive concept of Claim 1 appears to be the specific mechanism for determining a route: using a table with pointers to access other tables. The complaint's infringement theory for this element rests on "information and belief" that providing "Class 4 and 5 calling functionality" necessarily entails using such a structure (Compl. ¶48). A key question for the court will be whether the complaint provides sufficient factual matter, beyond mere inference, to plausibly allege that the accused products implement this specific nested, pointer-based routing method.
V. Key Claim Terms for Construction
For the ’238 Patent
- The Term: "server" (e.g., "circuit network server," "packet network server").
- Context and Importance: The infringement case for the ’238 Patent hinges on whether multiple, separately claimed "server" elements can be found in a single, multi-functional hardware platform. Defendant may argue that the term implies structurally distinct devices, while Plaintiff may argue for a broader, functional definition where different software processes on the same hardware can constitute different "servers."
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent does not explicitly define "server" or require physical separation. The specification describes that each server "may be designed as a combination of integrated circuits and other components and placed on an individual integrated circuit card or module" (’238 Patent, col. 4:3-6), which does not forbid multiple server functions from residing on the same module.
- Evidence for a Narrower Interpretation: Claim 1 recites "a circuit network server," "a packet network server," and "a signal processing server" as distinct elements in a list, which typically implies they are structurally separate. The patent's primary drawing, Figure 3, depicts these servers as distinct boxes (33, 36, 35), which may support an argument that they are conceived of as separate components.
For the ’269 Patent
- The Term: "a table comprising a plurality of pointers to a plurality of additional tables".
- Context and Importance: This term is central to the asserted method claim. The infringement analysis will depend on whether the accused products' routing databases can be characterized as having this specific nested structure. Practitioners may focus on whether a series of independent lookups in different tables is sufficient, or if a direct "pointer" from one table to another is required.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent does not define "pointer," which could allow for an interpretation that includes any form of index or key that leads to a subsequent data lookup in another table, not necessarily a direct memory address.
- Evidence for a Narrower Interpretation: The claim language recites a specific structure: a first table that itself comprises pointers to other tables. The complaint highlights language from the patent describing "nested tables" (Compl. ¶38, citing ’269 Patent, col. 3:19-21), which suggests a direct, hierarchical relationship rather than a sequence of unrelated lookups.
VI. Other Allegations
- Indirect Infringement: The complaint alleges induced infringement for all five patents. The basis for these allegations is that Defendant provides marketing literature and product documentation that encourages and instructs customers on how to use the accused products in an infringing manner (e.g., Compl. ¶¶ 35, 50, 63, 76, 93).
- Willful Infringement: Willfulness is alleged for the ’334 Patent based on pre-suit knowledge. The complaint asserts that Defendant has been aware of the ’334 Patent since at least May 6, 2010, when it was cited during the prosecution of Defendant's own U.S. Patent No. 7,881,282 (Compl. ¶78). For the remaining four patents, the complaint alleges knowledge "at least as early as service of this Complaint," supporting only post-suit willfulness (Compl. ¶¶ 20, 39, 54, 82).
VII. Analyst’s Conclusion: Key Questions for the Case
- A core issue will be one of claim scope versus accused architecture: Can the separately claimed functional "servers" of the ’238 Patent be read onto the allegedly integrated, multi-function hardware modules of the accused gateways, or does the claim language, supported by the patent's figures, require structurally distinct components?
- A second key issue will be one of evidentiary sufficiency: Does the complaint's reliance on the accused products' high-level "Class 4 and 5 calling functionality" provide a plausible factual basis to allege the specific nested, pointer-based table lookup method required by the ’269 Patent, or will this be seen as an unsupported technical conclusion?
- Finally, a central question for damages will be the effect of alleged pre-suit notice: For the ’334 Patent, the court will likely scrutinize the facts surrounding Defendant's alleged awareness of the patent during its own patent prosecution to determine if its subsequent conduct rises to the level of willful infringement justifying enhanced damages.