Jenam Tech LLC v. Google LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Jenam Tech, LLC (Texas)
  • Defendant: Google LLC (Delaware)
  • Plaintiff's Counsel: Devlin Law Firm LLC
• Case Identification: 6:21-cv-00271, W.D. Tex., 03/17/2021
• Venue Allegations: Plaintiff alleges venue is proper because Defendant Google maintains an established place of business in the Western District of Texas, specifically an office in Austin.
• Core Dispute: Plaintiff alleges that a wide range of Defendant's software and hardware products infringe a patent related to methods for cooperatively managing network connection timeouts between two nodes.
• Technical Context: The technology addresses the management of idle network connections, such as those using Transmission Control Protocol (TCP), to conserve network and server resources while maintaining connection stability.
• Key Procedural History: The asserted U.S. Patent No. 10,951,742 is subject to a terminal disclaimer. The patent issued on March 16, 2021, and this complaint was filed the following day. Notably, on March 16, 2022, the assignee filed a disclaimer for several claims, including independent claims 1 and 78, which are the only claims explicitly asserted in the complaint. This disclaimer renders the asserted claims unenforceable from the date the disclaimer was filed.

Case Timeline

Date	Event
2010-02-27	Earliest Priority Date (''742 Patent)
2021-03-16	'742 Patent Issued
2021-03-17	Complaint Filed
2022-03-16	Disclaimer of Asserted Claims 1 and 78 Filed

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

No probative visual evidence provided in complaint.

U.S. Patent No. 10,951,742 - Methods, Systems, and Computer Program Products for Sharing Information for Detecting at Least One Time Period for a Connection

The Invention Explained

• Problem Addressed: The patent background describes the long-standing problem of managing idle Transmission Control Protocol (TCP) connections '742 Patent, col. 2:39-48 Standard "keep-alive" mechanisms are not part of the core TCP specification, leading to inconsistent implementations where network nodes do not cooperate, which can waste bandwidth or cause firewalls to prematurely terminate connections they perceive as inactive '742 Patent, col. 2:5-17 '742 Patent, col. 2:35-38
• The Patented Solution: The invention proposes a method for two nodes to cooperatively manage a connection by explicitly sharing information about timeouts. A first node sends a packet containing "metadata" to a second node '742 Patent, abstract This metadata allows the second node to determine an appropriate duration for detecting an idle period, enabling both ends of the connection to manage resources and activity in a coordinated manner, rather than relying on uncoordinated, implementation-specific timers '742 Patent, abstract '742 Patent, col. 6:18-30 The claims are directed not to standard TCP, but to "non-TCP" and "TCP-variant" connections.
• Technical Importance: This technology aims to improve network efficiency and reliability by providing a standardized, cooperative framework for managing connection lifecycles, a critical function in large-scale networked systems.

Key Claims at a Glance

• The complaint asserts independent claims 1 and 78 Compl. ¶ 17
• Independent Claim 1 recites an apparatus for managing a "non-TCP connection," with key steps including:
  • Identifying information for a "first duration" for detecting a time period.
  • Allocating a resource for a "first non-Transmission Control Protocol (non-TCP) connection."
  • Generating a "first non-TCP packet" with a parameter field identifying "first metadata" for determining a "second duration."
  • Setting up the connection by sending the packet to a second node to provide the metadata.
  • Detecting time periods based on these durations and "at least partially clos[ing]" the connection by releasing the resource.
• Independent Claim 78 recites a similar method for managing a "first Transmission Control Protocol-variant (TCP-variant) connection."

III. The Accused Instrumentality

Product Identification

The complaint accuses a broad and diverse set of Google products and services Compl. ¶ 7 The "Accused Software" includes Google Edge Network, Google Cloud, Chrome, Android, Duo, Google Ads, YouTube, and Google Maps. The "Accused Products" include hardware such as Pixel phones, laptops, and Chromebooks that run this software Compl. ¶ 7

Functionality and Market Context

The complaint does not describe the specific functionality of any accused product. It alleges in a conclusory manner that the listed products and services infringe by being made, used, or sold by Google Compl. ¶ 13 All substantive allegations of infringement are deferred to a claim chart exhibit that was not included with the complaint Compl. ¶ 17

IV. Analysis of Infringement Allegations

The complaint references a claim chart (Exhibit B) to demonstrate infringement, but this exhibit was not provided Compl. ¶ 17 The complaint's narrative infringement theory is limited to the conclusory statement that "each and every element of at least claims 1 and 78 of the '742 patent is found in the Accused Software and Accused Products" Compl. ¶ 17 Without the claim chart or a more detailed narrative, a specific element-by-element analysis is not possible.

• Identified Points of Contention:
  • Disclaimer of Asserted Claims: A post-filing disclaimer has dedicated the asserted claims 1 and 78 to the public, which raises the dispositive question of whether Plaintiff has any enforceable claims remaining in the case as currently pleaded.
  • Scope Questions: A primary dispute may center on the scope of the terms "non-TCP connection" (Claim 1) and "TCP-variant connection" (Claim 78). The infringement analysis will depend on whether Google's widely used protocols (e.g., standard TCP, or the UDP-based QUIC protocol) fall within these definitions. The patent's explicit reference to QUIC as a publication could be a factor in determining the scope of "TCP-variant" '742 Patent, p. 3
  • Technical Questions: The complaint's lack of technical detail raises the question of what evidence supports the allegation that Google's products perform the claimed steps. Specifically, a central question will be whether the accused products generate and send packets containing "metadata" for the express purpose of allowing a receiving node to determine a connection timeout duration, as required by the claims.

V. Key Claim Terms for Construction

• The Term: "non-Transmission Control Protocol (non-TCP) connection"

• Context and Importance: This term from independent claim 1 is foundational to the infringement analysis. Its construction will determine whether the claim is limited to protocols fundamentally different from TCP or if it can read on protocols that deviate from the formal TCP standard (RFC 793). Practitioners may focus on this term because the accused products likely use either standard TCP or well-known protocols like QUIC, and the applicability of this term is therefore a threshold issue.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The abstract distinguishes between "a non-TCP connection," "a TCP-variant connection," and "not a Transmission Control Protocol connection," suggesting these are distinct categories '742 Patent, abstract A party could argue "non-TCP" means any protocol not strictly adhering to the baseline TCP standard.
  • Evidence for a Narrower Interpretation: The presence of a separate claim for "TCP-variant" connections (Claim 78) suggests, under the doctrine of claim differentiation, that "non-TCP" in Claim 1 is intended to cover something other than variants of TCP. A party could argue it is limited to protocols that lack TCP's core characteristics, such as connection-oriented, reliable data transfer.

• The Term: "Transmission Control Protocol-variant (TCP-variant) connection"

• Context and Importance: This term from independent claim 78 appears crafted to cover protocols that are similar to, but not identical to, standard TCP. Google's development and use of the QUIC protocol makes the scope of "TCP-variant" a critical issue for determining infringement.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification discusses "an extension and/or variant of the current TCP" '742 Patent, col. 16:61-62 This could support an interpretation that covers any protocol building upon TCP's principles, potentially including QUIC, which runs on UDP but re-implements many TCP features like reliability and congestion control.
  • Evidence for a Narrower Interpretation: A party could argue the term is limited to protocols that are formally extensions of TCP (e.g., using new TCP options) rather than entirely new protocols like QUIC that operate on a different transport layer (UDP). The patent's own citation to QUIC literature could be used to argue that the inventor was aware of QUIC and that "TCP-variant" should be construed to not read on it to preserve the claim's validity.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that Google aids and abets its partners and customers by distributing the accused software and providing related materials and services Compl. ¶¶18-19 The allegations do not specify any particular instructions or user manuals that would direct users to infringe.
• Willful Infringement: The complaint alleges willful infringement based on "information and belief" of pre-suit knowledge of the '742 patent and on actual knowledge from the date of service of the complaint Compl. ¶¶20-21 No specific facts are provided to support the allegation of pre-suit knowledge, which is notable given the complaint was filed one day after the patent issued.

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

1. Dispositive Legal Issue: What is the legal effect of the Plaintiff's post-filing statutory disclaimer of claims 1 and 78? As these are the only two claims explicitly asserted in the complaint, this action appears to present a fatal, threshold barrier to the continuation of the lawsuit as currently pled.
2. Claim Scope and Construction: Should the case proceed, a core issue will be one of definitional scope: can the terms "non-TCP connection" or "TCP-variant connection" be construed to cover the industry-standard and proprietary protocols (such as QUIC) that power Google's vast ecosystem of products and services?
3. Pleading Sufficiency: A key procedural question is whether the complaint's blanket allegations against dozens of distinct products, supported only by a reference to an unprovided exhibit, satisfy the plausibility standard for pleading patent infringement under federal rules and precedent.