PulseLink Systems LLC v. Zoom Communications Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: PulseLink Systems, LLC (Texas)
  • Defendant: Zoom Communications, Inc. (Delaware)
  • Plaintiff's Counsel: Farnan LLP
• Case Identification: 1:26-cv-01040, D. Del., 08/14/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant, Zoom Communications, Inc., is a Delaware corporation and therefore resides in the district for patent venue purposes.
• Core Dispute: Plaintiff alleges that Defendant's cloud-based communications platform, including its contact center, video conferencing, and desktop application products, infringes three U.S. patents related to dynamic call routing, adaptive media-stream compression, and cross-protocol interoperability.
• Technical Context: The lawsuit concerns core technologies in the unified communications as a service (UCaaS) and contact center as a service (CCaaS) markets, which involve routing customer interactions, managing real-time video quality, and integrating disparate communication systems.
• Key Procedural History: The complaint notes that Plaintiff previously filed a separate patent infringement suit against Defendant in the Eastern District of Texas on April 27, 2026, concerning different patents. The complaint also alleges that Plaintiff provided Defendant with notice of the currently asserted patents on March 27, 2026, and that the parties' representatives met to discuss the matter on June 29, 2026, prior to the filing of this complaint.

Case Timeline

Date	Event
2008-09-29	U.S. Patent No. 8,369,324 Priority Date
2013-02-05	U.S. Patent No. 8,369,324 Issued
2013-03-15	U.S. Patent No. 9,544,340 Priority Date
2017-01-10	U.S. Patent No. 9,544,340 Issued
2018-07-17	U.S. Patent No. 11,108,911 Priority Date
2021-08-31	U.S. Patent No. 11,108,911 Issued
2026-03-27	Plaintiff allegedly sent formal notice of patents to Defendant
2026-04-27	Plaintiff filed prior lawsuit against Defendant in E.D. Tex.
2026-06-29	Representatives for Plaintiff and Defendant allegedly met
2026-08-14	Complaint Filed

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

U.S. Patent No. 11,108,911 - "System and method for flexible routing"

The "'911 Patent" was issued on August 31, 2021.

The Invention Explained

• Problem Addressed: The patent's background describes a problem in conventional communication systems, such as contact centers, which relied on static or preconfigured paths and could not dynamically select a destination based on information carried within an incoming communication request Compl. ¶24 '911 Patent, col. 7:22-30
• The Patented Solution: The invention is a rules-based routing framework that receives a session request containing a "routing attribute." This attribute is used to look up a destination in a "dynamic routing framework," which then applies defined rules to route the session Compl. ¶25 '911 Patent, abstract This decouples the destination selection from a fixed call path, allowing the network to adapt routing on a per-session basis without rewriting underlying logic Compl. ¶24 '911 Patent, col. 4:36-44
• Technical Importance: This technology enables more intelligent, flexible, and efficient routing of communications in contact centers and unified communications systems Compl. ¶29

Key Claims at a Glance

• The complaint asserts claims 11, 13, 14, 15, and 16 Compl. ¶95 Claim 11 is the sole independent claim among those asserted.
• Independent Claim 11 (Method):
  • Receiving a request to establish a first communication session with a second communication device, where the request comprises a first routing attribute.
  • Looking up the first routing attribute in a dynamic routing framework.
  • Identifying a third communication device or destination based on the lookup and one or more rules defined in the framework.
  • Routing the first communication session to the identified third communication device or destination, where the destination is identified based on the lookup.
• The complaint asserts dependent claims 13, 14, 15, and 16, which add limitations related to using multiple routing attributes, logical operators, user-interface-based attribute selection, and insertion of the attribute by a network application Compl. ¶¶26-27

U.S. Patent No. 8,369,324 - "Variable compression queue"

The "'324 Patent" was issued on February 5, 2013.

The Invention Explained

• Problem Addressed: The patent addresses problems in transmitting real-time media data through a finite transmission queue, where fixed-size data blocks and fixed compression settings can lead to inefficient bandwidth use, delays, and data loss when network conditions fluctuate Compl. ¶36 '324 Patent, col. 1:41-50
• The Patented Solution: The patent discloses a media transmission pipeline that dynamically adapts to network conditions. It groups uncompressed data into blocks, compresses them, and places them in a queue. Crucially, the system determines the connection status and, if unacceptable, adaptively reconfigures the transmission by either changing the number of data elements grouped into a block or increasing the degree of compression before the data is sent Compl. ¶¶37-38 '324 Patent, col. 2:56-63
• Technical Importance: This approach allows real-time media streams to remain responsive to live network and device conditions, improving transmission quality and reliability over relying on a fixed encoder configuration Compl. ¶40

Key Claims at a Glance

• The complaint asserts claims 1 and 4 Compl. ¶110 Claim 1 is an independent method claim.
• Independent Claim 1 (Method):
  • Receiving a plurality of unbulked and uncompressed data elements for transmission.
  • Grouping first and second pluralities of the elements into first and second blocks.
  • Setting at least the first block's size using a predetermined characteristic, with the first and second block sizes being different.
  • Compressing the blocks into corresponding compressed blocks.
  • Locating the first compressed block in a transmission queue.
  • Determining connection status.
  • Sending the first compressed block in response to an acceptable status.
  • In response to an unacceptable status, changing the number of data elements in the first block or increasing its degree of compression.
• The complaint also asserts dependent claim 4, which specifies that the "predetermined characteristic" for setting the block size is the "number of data elements in the block" Compl. ¶39

U.S. Patent No. 9,544,340 - "Application programming interface enabling communication features for different communication protocols"

The "'340 Patent" was issued on January 10, 2017.

Technology Synopsis

The patent addresses the technical problem of interoperability between browser-based web sessions (e.g., using WebRTC) and native enterprise communication systems (e.g., using SIP/H.323) Compl. ¶48 The patented solution is a collaboration architecture that provides a protocol-agnostic communications interface and API, allowing heterogeneous endpoints to participate in and control a common communication session without requiring the native applications to implement the browser's protocol Compl. ¶49

Asserted Claims

The complaint asserts at least claim 1 Compl. ¶126

Accused Features

The accused features are the Zoom platform components, including Zoom Cloud, Zoom Meetings, the Zoom Web App, and the Conference Room Connector, which allegedly work together to allow browser-based participants and standards-based SIP/H.323 room systems to join and participate in the same meeting Compl. ¶74

III. The Accused Instrumentality

Product Identification

The complaint identifies the "Accused Products" as Zoom's cloud-based communications platform, including the Zoom Contact Center and Flow Designer, the Zoom Workplace Desktop App and its Media Engine, and Zoom Meetings and Conference Room Connector Compl. ¶3

Functionality and Market Context

The complaint alleges that the accused products provide a leading platform for cloud-based communication and collaboration Compl. ¶7 Compl. ¶21 The functionality relevant to the asserted patents includes:

• Contact Center Routing: The Zoom Contact Center allegedly uses a "Flow Designer" with "Skills-Based Routing" to direct customer communications to qualified agents. This is accomplished using an administrator-configured series of widgets (e.g., Collect Input, Condition, Data Table) and rules-based "Agent Routing Profiles" to dynamically select a destination based on attributes like language or technical skill Compl. ¶¶30-33 Compl. ¶¶60-64 A diagram in the complaint illustrates a high-level network design for the Zoom Contact Center, showing the data flow between a consumer, the Zoom Data Center, and an agent Compl. p. 25
• Adaptive Media Transmission: The Zoom Workplace Desktop App allegedly includes a "Media Engine" that captures, encodes, and transmits real-time video. It is alleged to use a "Reactive QoS Layer" and "Adaptive Codec" to monitor network conditions and respond to degradation by adjusting video stream properties like resolution, frame rate, or bitrate Compl. ¶¶41-46 Compl. ¶¶67-73 A text box in the complaint provides a specific example of the "Reactive QOS layer" reducing frame rate in response to high CPU utilization Compl. p. 32
• Cross-Protocol Conferencing: Zoom's architecture, including the Zoom Web App and Conference Room Connector, is alleged to create a unified meeting environment where users on browsers (using WebRTC) can join the same session as dedicated room systems (using SIP/H.323) Compl. ¶¶51-52 Compl. ¶¶74-77 A screenshot in the complaint shows an interface for inviting a SIP/H.323 room system to a meeting by dialing its IP address Compl. p. 37

IV. Analysis of Infringement Allegations

'911 Patent Infringement Allegations

Claim Element (from Independent Claim 11)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving a request to establish a first communication session with a second communication device, wherein the request comprises a first routing attribute for routing the first communication session	Zoom Contact Center allegedly receives an incoming consumer engagement through a Flow entry point. The engagement conveys information like language or technical skill, which serves as the routing attribute.	¶97; ¶98	col. 16:22-29
lookup the first routing attribute for routing the first communication session in a dynamic routing framework	Zoom's "Flow" is described as an administrator-configured, rules-based framework. It allegedly uses a "Data Table" widget to look up call-routing information based on a key derived from the routing attribute.	¶99	col. 6:3-6
route the first communication session to a third communication device or destination based on the first routing attribute and one or more rules defined in the dynamic routing framework, wherein the third communication device or destination is identified based on the lookup of the first routing attribute	Zoom's "Agent Routing Profiles" allegedly evaluate skill categories and apply rules to determine agent eligibility. A "Route To" widget then dynamically routes the engagement to an identified agent, queue, or other destination based on the framework's rules.	¶100	col. 16:31-38

'324 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving a plurality of unbulked and uncompressed data elements for transmission to a destination node	The Zoom Workplace Desktop App's Media Engine allegedly receives uncompressed pixel or picture samples from a local video capture.	¶113	col. 5:4-5
grouping first and second pluralities of those elements into first and second blocks	The Media Engine allegedly groups successive capture intervals into distinct "source-frame blocks" before compression.	¶113	col. 1:26-29
setting at least the first block's size using a predetermined characteristic, with the first and second block sizes different	Resolution is identified as the predetermined characteristic that sets the block size (number of picture locations). A 720p block is alleged to be a different size than a 360p block.	¶114	col. 1:30-34
compressing the blocks into corresponding compressed blocks	The Media Engine allegedly applies H.264/AVC compression to each source-frame block.	¶115	col. 5:44-46
locating the first compressed block in a transmission queue	The Media Engine is alleged to retain the compressed output in an ordered transmit buffer or equivalent scheduling queue before release.	¶115	col. 1:15-17
determining connection status	Zoom's platform allegedly monitors network-quality statistics, callbacks, and diagnostics to determine connection status.	¶116	col. 5:16-18
sending the first compressed block in response to an acceptable status	The Media Engine allegedly sends the queued block when connection status is deemed acceptable, such as when estimated bandwidth is sufficient.	¶116	col. 5:22-26
and, in response to an unacceptable status, changing the number of data elements in the first block or increasing its degree of compression	When connection status is unacceptable, Zoom's "Reactive QoS Layer" and "Adaptive Codec" allegedly adapt the stream by lowering resolution (changing the number of data elements) or reducing the bitrate (increasing compression).	¶117	col. 2:56-63

Identified Points of Contention

• Scope Questions: The infringement analysis for the '911 Patent may turn on whether Zoom's administrator-configured "Flow Designer," which operates at the application layer, meets the definition of a "dynamic routing framework" as contemplated by the patent. A related question is whether a user-defined "skill" in Zoom's system constitutes a "routing attribute" in the manner claimed. For the '340 Patent, a question may arise as to whether Zoom's architecture embodies the specific "protocol-agnostic communications interface" and "feature invoker" structure, or if it represents a different implementation of cross-protocol communication.
• Technical Questions: A central technical question for the '324 Patent will be the operational timing of the accused adaptation. The analysis will question whether Zoom's alleged method of lowering the resolution of subsequent video frames satisfies the claim limitation of "changing the number of data elements in the first block," which could be interpreted to require modification of an already-formed data block, not just the parameters for the next one.

V. Key Claim Terms for Construction

Term: "dynamic routing framework" ('911 Patent)

• Context and Importance: This term is the centerpiece of the asserted routing method. The case may hinge on whether Zoom's "Flow Designer" and associated "Agent Routing Profiles"-a system configured by an administrator through a graphical interface-qualifies as a "dynamic routing framework". Practitioners may focus on this term because its construction will determine if a GUI-driven, application-level rules engine falls within the scope of a claim that also describes attributes carried in protocol headers.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification defines the framework broadly as "any set of rules that define routing of communication sessions" that can be "dynamically defined by the administrator" '911 Patent, col. 6:3-6, which could support including Zoom's system.
  • Evidence for a Narrower Interpretation: Embodiments described in the patent focus on routing attributes located in specific protocol headers, such as a "SIP Via header" or as a parameter in a "SIP URI" '911 Patent, col. 4:25-34 '911 Patent, col. 4:51-52 This could support an argument that the framework is intended to be a more protocol-centric mechanism.

Term: "changing the number of data elements in the first block" ('324 Patent)

• Context and Importance: This term defines one of the two adaptive responses to poor network conditions and is critical to the infringement allegation. The dispute will likely focus on whether adjusting parameters for future blocks (e.g., lowering resolution for the next frame to be captured) meets this limitation.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent's stated goal is to provide "dynamic behavior of buffering and persistence based on available resources" '324 Patent, col. 2:13-14 An interpretation that this is achieved by adjusting the parameters for subsequent data processing could be seen as consistent with this purpose.
  • Evidence for a Narrower Interpretation: The claim language recites changing the number of elements "in the first block," which could be read narrowly to require modification of a data block that has already been composed. The patent's flowchart describes a step to "revisit existing bulk and combine" '324 Patent, Fig. 3, step 344, which may suggest a process of decompressing and re-bundling already-queued data, supporting a narrower interpretation.

VI. Other Allegations

Indirect Infringement

The complaint alleges induced infringement, stating that Zoom provides technical documentation, administrator guides, SDKs, and support articles that direct and encourage customers to configure and use the accused functionalities Compl. ¶87 Compl. ¶90 These materials allegedly instruct users on building routing "Flows" for the '911 patent's technology and describe the "Reactive QoS Layer" for the '324 patent's technology, thereby allegedly demonstrating Zoom's specific intent for customers to perform the infringing acts Compl. ¶88

Willful Infringement

The complaint alleges willful infringement based on pre-suit knowledge. It claims that Zoom received formal notice of the asserted patents and infringement allegations on March 27, 2026, and participated in subsequent discussions, but continued its allegedly infringing activities Compl. ¶¶80-83 Compl. ¶92 The complaint also alleges willful blindness, stating that Zoom, as a sophisticated technology company, knew or should have known its products practiced the patented technologies Compl. ¶84

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

• A core issue will be one of definitional scope: can the term "dynamic routing framework" from the '911 Patent, which is exemplified in the specification using protocol-level attributes, be construed broadly enough to read on the application-level, administrator-configured logic of Zoom's "Flow Designer" product?
• A key evidentiary question will concern technical operation and timing: does Zoom's "Reactive QoS Layer," which allegedly adapts to poor network conditions by adjusting the resolution of subsequent video frames, perform the specific function of "changing the number of data elements in the first block" as required by Claim 1 of the '324 Patent, or does this claim language necessitate the modification of an already-constituted data block, creating a potential mismatch in operational sequence?
• A central architectural question will be whether Zoom's system for connecting browser-based and SIP/H.323 endpoints constitutes the specific "collaboration environment" with a "protocol-agnostic... interface" and "feature invoker" as claimed in the '340 Patent, or if it represents a fundamentally different, non-infringing architecture for achieving cross-protocol interoperability.