WebSock Global Strategies LLC v. Glorious LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: WebSock Global Strategies LLC (Delaware)
  • Defendant: Glorious LLC (Texas)
  • Plaintiff's Counsel: Rabicoff Law LLC
• Case Identification: 7:26-cv-00127, W.D. Tex., 04/06/2026
• Venue Allegations: Plaintiff alleges venue is proper because Defendant has an established place of business in the district and has committed alleged acts of patent infringement within the district.
• Core Dispute: Plaintiff alleges that Defendant infringes a patent related to methods for establishing symmetrical, bi-directional communication over traditionally asymmetrical protocols like HTTP.
• Technical Context: The technology addresses limitations in standard client-server communication models, particularly for peer-to-peer applications, by enabling a server to initiate communication with a client after an initial connection is established.
• Key Procedural History: The patent-in-suit is a continuation of a prior U.S. patent application, Ser. No. 10/338,630, now U.S. Patent No. 7,403,995, which may be relevant for determining the effective priority date of the asserted claims.

Case Timeline

Date	Event
2003-01-08	Earliest Priority Date (U.S. Pat. App. Ser. No. 10/338,630)
2008-04-24	Application Date for '983 Patent
2010-07-13	Issue Date for '983 Patent
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 and a "server" node can only respond '983 Patent, col. 2:10-12 This model prevents a server from spontaneously sending information to a client, a significant limitation for peer-to-peer applications, especially when a client is behind a Network Address Translation (NAT) router or firewall that blocks unsolicited inbound connections '983 Patent, col. 2:19-21 '983 Patent, col. 2:41-50 Traditional workarounds like "polling"-where the client repeatedly asks the server for updates-are described as inefficient and wasteful of network bandwidth '983 Patent, col. 3:4-7
• The Patented Solution: The invention proposes a method to create a symmetrical communication channel over an asymmetrical protocol. A client first establishes a standard HTTP session over an underlying network connection (e.g., TCP/IP) with a server '983 Patent, abstract The two nodes then "negotiate transactional role reversal" '983 Patent, abstract Following this negotiation, the initial HTTP-layer session is terminated, but the underlying TCP/IP connection is deliberately preserved '983 Patent, Fig. 9, step 512 A new HTTP-layer session is then created over this same preserved connection, but with the roles inverted: the original server now acts as a client, and the original client acts as a server, enabling the original server to initiate requests '983 Patent, Fig. 9, step 514 This creates two oppositely directed communication channels over the same foundational network link, achieving symmetrical bi-directional communication '983 Patent, col. 10:48-54
• Technical Importance: This technique was designed to enable true peer-to-peer communication using the ubiquitous and firewall-friendly HTTP protocol, circumventing the structural limitations of the client-server model without resorting to inefficient polling '983 Patent, col. 3:19-24

Key Claims at a Glance

The complaint asserts "exemplary method claims" without specifying claim numbers Compl. ¶11 Independent claim 1 is representative of the core method.

• Independent Claim 1:
  • First and second network nodes engaging in an asymmetric hypertext transfer protocol (HTTP) transactional session with an underlying network connection, with each node enacting distinct initial transactional roles (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 further communicating under a reversed asymmetric transactional protocol, where each node enacts the initial transactional role of the other.
• The complaint notes that Plaintiff may assert other claims, including dependent claims Compl. ¶11

III. The Accused Instrumentality

Product Identification

The complaint refers to "Exemplary Defendant Products" Compl. ¶11 It states these products are identified in charts within an "Exhibit 2," which was not attached to the publicly filed complaint Compl. ¶13

Functionality and Market Context

The complaint does not provide a functional description of the accused products. It alleges in a conclusory manner that the "Exemplary Defendant Products practice the technology claimed by the '983 Patent" and "satisfy all elements of the Exemplary '983 Patent Claims" Compl. ¶13 No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint references claim charts in an unprovided Exhibit 2 to detail its infringement allegations Compl. ¶13 Compl. ¶14 In the absence of these charts, the infringement theory must be inferred from the patent's claims and the complaint's general allegations. The central allegation is that the accused products directly infringe the '983 Patent by establishing a bi-directional communication channel using the claimed method of reversing client-server roles over a persistent underlying network connection Compl. ¶11 Compl. ¶13

Identified Points of Contention

• Scope Questions: A primary question may be whether the accused products' communication protocol performs the specific sequence of (1) terminating an initial HTTP session, (2) maintaining the underlying TCP/IP connection, and (3) creating a new, reversed-role session on that same connection. The defense may argue its technology achieves a similar result through a non-infringing mechanism, such as a protocol upgrade (e.g., WebSocket) that transforms the initial connection rather than terminating and replacing the session layer as claimed.
• Technical Questions: The complaint's lack of technical detail raises the question of what evidence will be presented to show that the accused products actually "negotiate" a role reversal. The analysis will depend on the specific data packets and signals exchanged between the accused products and whether this exchange can be fairly characterized as the "negotiation" and "role reversal" required by the claims.

V. Key Claim Terms for Construction

The complaint does not provide sufficient detail for a full analysis of claim construction disputes. However, based on the technology, certain terms are likely to be central.

• The Term: "terminating said asymmetric HTTP transactional session while maintaining said underlying network connection"

  • Context and Importance: This phrase captures the essence of the patented method. The dispute will likely center on the precise technical meanings of "terminating" the session versus "maintaining" the connection. Practitioners may focus on this term because modern protocols may "upgrade" a connection to be bi-directional rather than performing the discrete terminate-and-maintain steps described in the patent.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent's description is often functional. Language describing the termination of the "HTTP layer session" while "preserving the TCP connection" could be argued to encompass any process that functionally severs the initial client-server message structure while keeping the underlying network socket open for reuse '983 Patent, col. 9:15-19 '983 Patent, Fig. 9, step 512
    • Evidence for a Narrower Interpretation: The detailed flowcharts show a specific sequence: extracting and saving TCP circuit information, explicitly terminating the HTTP session, and then creating a new HTTP session using the saved information '983 Patent, Fig. 9, steps 508-514 This could support an argument that the claim is limited to implementations that follow this discrete, multi-step process.

• The Term: "negotiating transactional role reversal"

  • Context and Importance: The meaning of "negotiating" will be critical. The infringement analysis will turn on whether the accused products engage in a communication process that meets the definition of negotiation.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification discloses sending an "HTTP FLIP request" to the server, which could be a single command or custom header '983 Patent, col. 10:62 This might support a construction where any signaling protocol that results in a role reversal, even if a simple one-way command, constitutes "negotiating."
    • Evidence for a Narrower Interpretation: The term "negotiating" often implies a two-way exchange. The patent's flowcharts depict a "FLIP REQUEST" followed by a "SERVER REPLY," which can be an acceptance ("OK") or a refusal '983 Patent, Fig. 9 This suggests the possibility that a simple, one-way directive without an opportunity for refusal may not qualify as "negotiating."

VI. Other Allegations

Indirect Infringement

The complaint does not contain allegations to support claims of indirect infringement. The sole count is for direct infringement Compl. ¶¶10-14

Willful Infringement

The complaint does not explicitly allege willful infringement or plead facts related to pre-suit knowledge of the patent.

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

• A core issue will be one of technical mechanism: Does the accused product's protocol for establishing bi-directional communication map onto the specific, multi-step process claimed in the '983 Patent-terminating an HTTP session, maintaining the underlying connection, and creating a new reversed-role session-or does it employ a fundamentally different technical approach, such as a single-step protocol upgrade, to achieve a similar outcome?
• A key legal question will be one of definitional scope: Can the term "negotiating," in the context of the patent's specification and flowcharts, be construed broadly to cover any signaling that results in a role reversal, or is it limited to a more formal, two-way communication protocol involving a request and a corresponding acceptance or refusal?
• A central evidentiary question will be whether the Plaintiff can produce evidence from the accused products that demonstrates the specific sequence of operations required by the claims, particularly the preservation of the underlying network connection after the initial HTTP session layer is terminated and before the new, reversed-role session is created.