WebSock Global Strategies LLC v. Stirista LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: WebSock Global Strategies LLC (Delaware)
  • Defendant: Stirista, LLC (Delaware)
  • Plaintiff's Counsel: Rabicoff Law LLC
• Case Identification: 7:25-cv-00242, W.D. Tex., 09/04/2025
• Venue Allegations: Venue is alleged to be proper in the Western District of Texas because the Defendant has an established place of business in the district and has allegedly committed acts of patent infringement there.
• Core Dispute: Plaintiff alleges that Defendant's unspecified products and services infringe a patent related to methods for establishing symmetrical, bi-directional communication between network nodes over protocols that are inherently asymmetrical, such as HTTP.
• Technical Context: The technology addresses challenges in peer-to-peer network communication, particularly for devices behind firewalls or Network Address Translators (NAT), by enabling a device that is normally a "server" to initiate communication with a "client."
• Key Procedural History: The asserted patent is a continuation of a prior application that issued as U.S. Patent No. 7,403,995. This relationship may be relevant for claim construction and estoppel purposes based on the prosecution history of the parent patent.

Case Timeline

Date	Event
2003-01-08	'983 Patent Priority Date (Filing of application no. 10/338,630)
2008-04-24	'983 Patent Application Filing Date
2010-07-13	'983 Patent Issue Date
2025-09-04	Complaint Filing Date

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

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

• Patent Identification: U.S. Patent No. 7,756,983, "Symmetrical bi-directional communication", issued July 13, 2010. ("'983 Patent")

The Invention Explained

• Problem Addressed: The patent's background describes the fundamental asymmetry of the HyperText Transfer Protocol (HTTP), where a "client" node must always initiate a request to a "server" node, which can only respond. This model prevents a server from spontaneously sending data to a client and creates difficulties for peer-to-peer communication, especially when a node is behind a firewall or Network Address Translator (NAT) that blocks unsolicited incoming connections. ("'983 Patent, col. 2:6-21")
• The Patented Solution: The invention proposes a method where two network nodes first establish a standard, client-initiated HTTP session over an underlying network connection (e.g., a TCP socket). The nodes then negotiate a "transactional role reversal." The initial HTTP session is terminated, but the underlying TCP connection is preserved. A new HTTP session is then created over that same connection, but with the roles flipped: the original server now acts as the client, and the original client acts as the server, enabling the original server to initiate requests. ("'983 Patent, abstract; '983 Patent, col. 5:16-30; '983 Patent, figs. 9-10")
• Technical Importance: This technique was designed to enable true peer-to-peer communication using the ubiquitous and firewall-friendly HTTP protocol, effectively circumventing the limitations imposed by its rigid client-server architecture and common network security configurations. ("'983 Patent, col. 3:20-24")

Key Claims at a Glance

• The complaint does not specify which claims are asserted, referring only to "Exemplary '983 Patent Claims" in an unprovided exhibit ("Compl. ¶11"). Independent claim 1 is representative of the patent's core method.
• Independent Claim 1 requires:
  • First and second network nodes engaging in an asymmetric hypertext transfer protocol (HTTP) transactional session with an underlying network connection, where each node has a distinct initial transactional role (client or server).
  • Terminating the asymmetric HTTP transactional session while maintaining the underlying network connection.
  • The first and second network nodes negotiating transactional role reversal.
  • The first and second network nodes communicating under a reversed asymmetric transactional protocol, where each node enacts the initial transactional role of the other.
  • The session uses a network connection traversing hardware that enforces asymmetric communication. ("'983 Patent, claim 1")
• The complaint does not explicitly reserve the right to assert dependent claims but alleges infringement of "one or more claims" ("Compl. ¶11").

III. The Accused Instrumentality

Product Identification

• The complaint does not identify any accused product, method, or service by name. It refers generically to "Defendant products" ("Compl. ¶11"), "Exemplary Defendant Products" ("Compl. ¶11"), and products identified in an unprovided exhibit ("Compl. ¶11; Compl. ¶13").

Functionality and Market Context

• The complaint does not provide any description of the accused instrumentality's functionality, features, or market position. It makes only a conclusory allegation that the "Exemplary Defendant Products practice the technology claimed by the '983 Patent" ("Compl. ¶13"). No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint alleges direct infringement by Defendant's "Exemplary Defendant Products" ("Compl. ¶11") and incorporates by reference "charts comparing the Exemplary '983 Patent Claims to the Exemplary Defendant Products" ("Compl. ¶13") in an unprovided "Exhibit 2" ("Compl. ¶13"). As the specific infringement charts are not included with the complaint, a detailed element-by-element analysis based on the pleading is not possible. The complaint summarily alleges that the accused products "practice the technology claimed by the '983 Patent" and "satisfy all elements of the Exemplary '983 Patent Claims" ("Compl. ¶13").

Without the referenced claim charts, there are no factual allegations in the complaint that map specific features of any accused product to the limitations of the patent claims.

V. Key Claim Terms for Construction

• The Term: "negotiating transactional role reversal" ("'983 Patent, claim 1")
• Context and Importance: This term is the central inventive concept of the patent. The outcome of the case may depend on whether the accused technology performs a process that can be defined as "negotiating" a "reversal" of transactional roles, as opposed to using a different mechanism (e.g., a persistent full-duplex connection) to achieve bi-directional communication.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: A party might argue that the term should be read broadly to cover any process where two nodes agree to switch their client-server communication roles, pointing to general descriptions of the process ("'983 Patent, col. 5:23-30").
  • Evidence for a Narrower Interpretation: A party could argue for a narrower construction limited to the specific mechanism disclosed. The specification describes a distinct process involving an "HTTP FLIP request" sent from the client to the server, which the server must accept before the roles are reversed. ("'983 Patent, col. 9:11-21; '983 Patent, col. 10:27-40; '983 Patent, figs. 9-10"). This evidence may support an interpretation that requires an explicit, multi-step negotiation protocol.

VI. Other Allegations

• Willful Infringement: The complaint does not explicitly allege willful infringement. However, in the prayer for relief, it requests that the case be "declared exceptional within the meaning of 35 U.S.C. § 285" and seeks an award of attorney's fees ("Compl. prayer E.i"). The complaint does not plead any specific facts, such as pre-suit knowledge of the patent, to support this request.

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

1. A Pleading Sufficiency Question: Given that the complaint fails to identify any accused product or provide any factual allegations of infringement beyond incorporating an unprovided exhibit, an initial question is whether the pleading meets the plausibility standards required by Federal Circuit precedent following Twombly and Iqbal.
2. A Definitional Scope Question: A core technical issue will be whether modern bi-directional web communication technologies, which may maintain a single persistent connection for two-way data flow, can be construed as performing the claimed method of "terminating" an initial HTTP session and "negotiating transactional role reversal" to create a separate "reversed" session.
3. An Evidentiary Question: Assuming the case proceeds, a central challenge for the Plaintiff will be to produce evidence demonstrating that the Defendant's products perform the specific, multi-step process of establishing a session, negotiating a role flip, and creating a new, reversed-role session over the same underlying connection, as required by the patent's claims.