WebSock Global Strategies LLC v. Uship Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: WebSock Global Strategies LLC (Delaware)
  • Defendant: uShip Inc. (Delaware)
  • Plaintiff's Counsel: Rabicoff Law LLC
• Case Identification: 7:26-cv-00132, W.D. Tex., 04/06/2026
• Venue Allegations: Plaintiff alleges venue is proper because Defendant maintains an established place of business in the district and has committed acts of patent infringement within the district.
• Core Dispute: Plaintiff alleges that Defendant's products infringe a patent related to a method for establishing symmetrical, bi-directional communication between network nodes over the typically asymmetric HTTP protocol.
• Technical Context: The patent addresses challenges in peer-to-peer network communication, particularly when devices are separated by firewalls or Network Address Translation (NAT) systems, which traditionally prevent servers from initiating connections to clients.
• Key Procedural History: The complaint does not mention any prior litigation, inter partes review proceedings, or licensing history related to the patent-in-suit.

Case Timeline

Date	Event
2003-01-08	'983 Patent Priority Date
2008-04-24	'983 Patent Application Filing Date
2010-07-13	'983 Patent Issue Date
2026-04-06	Complaint Filing Date

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

U.S. Patent No. 7,756,983 - "Symmetrical bi-directional communication"

The Invention Explained

• Problem Addressed: The patent's background section describes the inherent asymmetry of the HyperText Transfer Protocol (HTTP), where a "client" node must always initiate a request to a "server" node, which can only respond Compl. ¶9 '983 Patent, col. 2:10-21 This model poses a fundamental problem for peer-to-peer applications where either node may need to initiate communication, especially when a client is behind a firewall or NAT that blocks unsolicited incoming connections '983 Patent, col. 2:45-52 Traditional workarounds like "polling" are described as inefficient and wasteful of network bandwidth '983 Patent, col. 3:4-10
• The Patented Solution: The invention proposes a method to create a symmetrical communication channel over an established, persistent network connection (e.g., TCP/IP) '983 Patent, abstract The process begins with a standard, client-initiated HTTP session. The nodes then negotiate a "transactional role reversal." The initial HTTP session is terminated, but the underlying TCP/IP connection is preserved '983 Patent, col. 10:5-14 '983 Patent, Fig. 9 A new HTTP session is then created over the same preserved connection, but with the roles inverted: the original server now acts as the client, enabling it to initiate requests to the original client, which now acts as a server '983 Patent, col. 10:15-21 '983 Patent, col. 11:51-56 This effectively creates a bi-directional channel, allowing either node to initiate communication.
• Technical Importance: The described technique provides a method to enable true peer-to-peer communication using the ubiquitous HTTP protocol, bypassing the typical client-server restrictions imposed by network intermediaries like NATs without resorting to inefficient polling '983 Patent, col. 3:20-24

Key Claims at a Glance

• The complaint asserts "one or more claims" of the '983 Patent without specifying them Compl. ¶11 Claim 1 is a representative independent method claim.
• Essential Elements of Independent Claim 1:
  • First and second network nodes engage in an asymmetric HTTP transactional session with an underlying network connection, with each node having distinct initial roles (client or server).
  • The asymmetric HTTP transactional session is terminated while maintaining the underlying network connection.
  • The first and second network nodes negotiate a transactional role reversal.
  • The nodes then engage in further communication under a "reversed asymmetric transactional protocol," where each node enacts the initial role of the other.
• The complaint does not explicitly reserve the right to assert dependent claims but refers to infringing "one or more claims" Compl. ¶11

III. The Accused Instrumentality

Product Identification

The complaint does not identify any specific accused products by name Compl. ¶¶11-13 It refers generally to "Defendant products identified in the charts incorporated into this Count below (among the 'Exemplary Defendant Products')" Compl. ¶11 These charts, designated as Exhibit 2, were not provided with the complaint.

Functionality and Market Context

The complaint provides no description of the functionality of the accused products or their market context. It states only that the products "practice the technology claimed by the '983 Patent" Compl. ¶13

IV. Analysis of Infringement Allegations

The complaint alleges direct infringement but relies entirely on claim charts in an unprovided "Exhibit 2" to detail its infringement theory Compl. ¶13 Compl. ¶14 The complaint's narrative lacks a specific description of how any accused product meets the limitations of the patent claims. No probative visual evidence provided in complaint.

• Identified Points of Contention: Given the technology, the infringement analysis may raise several technical and legal questions.
  • Scope Questions: A central question will likely concern the definition of "negotiating transactional role reversal" '983 Patent, claim 1 The dispute may focus on whether the accused system performs a specific, explicit negotiation to "flip" HTTP roles, or if it achieves bi-directional communication through an alternative mechanism (e.g., WebSockets, long polling, or server-sent events) that Plaintiff may argue is equivalent.
  • Technical Questions: A key factual question may be whether the accused products actually terminate an initial HTTP session while preserving the underlying TCP/IP connection to establish a second, role-reversed HTTP session as required by the claims '983 Patent, claim 1 Evidence of the specific network protocols and session management techniques used by the accused products will be central to determining whether they operate in the manner described by the patent.

V. Key Claim Terms for Construction

The complaint does not provide sufficient detail for analysis of specific claim terms in the context of an infringement theory. However, based on the patent's technology, certain terms are likely to be critical.

• The Term: "negotiating transactional role reversal"
• Context and Importance: This phrase appears in independent claim 1 and captures the core of the inventive concept. The definition of what constitutes a "negotiation" and a "role reversal" will be critical to determining the scope of the claim. Practitioners may focus on this term because modern bi-directional communication technologies may not involve an explicit negotiation or a formal reversal of client/server roles in the manner detailed in the patent's embodiments.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent states that the invention provides "symmetrical bi-directional communication" and allows nodes to "act as functional peers" '983 Patent, col. 2:9-10 A party could argue that any process that transforms a standard one-way HTTP channel into a two-way, peer-to-peer channel meets the spirit of a "role reversal."
  • Evidence for a Narrower Interpretation: The detailed description and flowcharts illustrate a specific sequence: an initial HTTP session is established, a "FLIP request" is sent and accepted, the existing HTTP layer is terminated while preserving the TCP connection, and a new HTTP layer is created with reversed roles '983 Patent, col. 10:5-21 '983 Patent, Fig. 9 A party could argue this specific, multi-step process is required to meet the "negotiating" limitation.

VI. Other Allegations

• Indirect Infringement: The complaint does not contain any specific factual allegations to support claims of induced or contributory infringement.
• Willful Infringement: The complaint does not allege pre-suit knowledge or willfulness in the body of the complaint. However, the prayer for relief requests a judgment that the case be declared "exceptional" and an award of attorneys' fees, which is often associated with findings of willful infringement or litigation misconduct Compl. Prayer E(i)

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

This case will likely depend on the resolution of two central questions that bridge claim construction and infringement analysis:

• A core issue will be one of definitional scope: Does the term "negotiating transactional role reversal," as used in the patent, require the specific, multi-step process of terminating one HTTP session and creating a new, role-reversed session on the same underlying connection, or can it be construed more broadly to cover other modern technologies that enable bi-directional communication over HTTP-based protocols?
• A key evidentiary question will be one of technical mechanism: Assuming a construction is reached, what factual evidence will demonstrate that the accused products actually implement the claimed method? The analysis will likely focus on whether the accused system creates two distinct, oppositely-directed HTTP sessions over a single, preserved TCP/IP socket, or whether it uses a single, persistent connection (like a WebSocket) that is inherently bi-directional and may not involve a "role reversal" as claimed.