Jenam Tech v. Google: TCP Patent Appeal Dismissed After 334 Days
Jenam Tech, LLC appealed a patentability challenge against Google, LLC at the Court of Appeals for the Federal Circuit, asserting US10075565B1 covering idle TCP connection detection methods. The parties agreed to dismiss the appeal under Fed. R. App. P. 42(b), with each side bearing its own costs — closing the Federal Circuit chapter in under a year.
Federal Circuit TCP patent appeal exits quietly by agreement
Jenam Tech, LLC filed this appeal at the United States Court of Appeals for the Federal Circuit on 9 February 2023, docketed as Case No. 23-1486. The underlying dispute centred on US10075565B1, a patent covering methods, systems, and computer program products for sharing information to detect an idle TCP (Transmission Control Protocol) connection. The respondent was Google, LLC, represented by Paul Hastings, LLP. The appeal arose from an invalidity or cancellation action — placing the patent’s patentability squarely at issue.
The appeal closed on 9 January 2024, a span of 334 days from filing. Termination was by agreed dismissal under Federal Rule of Appellate Procedure 42(b), which permits parties to dismiss an appeal upon their own stipulation. The court’s order confirmed dismissal and specified that each side shall bear its own costs — meaning neither party extracted a cost award from the other. No substantive ruling on the patent’s validity was issued by the Federal Circuit.
The 334-day duration and cost-neutral exit are consistent with a negotiated resolution reached before full briefing concluded or oral argument was scheduled. The absence of a merits ruling leaves the underlying patentability questions legally unresolved in public record — whether US10075565B1 survived or was cancelled at the tribunal below remains the operative question for anyone monitoring this patent’s enforceability. The specific terms driving the parties’ agreement, and whether any commercial arrangement accompanied the dismissal, are not disclosed in the public record.
Filing to dismissal in 334 days
334 days — resolved within a single calendar year at the Federal Circuit
Appeal dismissed by stipulation — no merits ruling issued
What Fed. R. App. P. 42(b) dismissal means
Rule 42(b) of the Federal Rules of Appellate Procedure allows parties to jointly dismiss a pending appeal by filing a signed agreement. Unlike a court-imposed dismissal, it reflects a deliberate bilateral decision to end the appellate proceeding. No judgment on the merits is entered — the Federal Circuit neither affirmed nor reversed the decision below. The underlying tribunal’s outcome therefore stands, but without Federal Circuit endorsement.
Agreed dismissal — no merits rulingPublic record is silent on with/without prejudice
The court order does not specify whether dismissal was with or without prejudice. A dismissal with prejudice would bar Jenam Tech from reasserting the same appeal; without prejudice could theoretically preserve options. In Federal Circuit practice, Rule 42(b) dismissals are generally treated as terminating the specific appellate proceeding. The public docket does not clarify, so practitioners should not assume either outcome without further investigation.
Prejudice terms: not stated on recordEach side bears own costs — no prevailing party
The order explicitly provides that each side shall bear their own costs. In Federal Circuit appeals, costs typically follow the prevailing party under Fed. R. App. P. 39. A mutual cost-bearing arrangement is a hallmark of negotiated resolution and suggests neither party was willing to concede prevailing-party status. It also avoids a fee-shifting trigger under 35 U.S.C. § 285, which requires a final judgment on the merits.
Cost-neutral exitValidity of US10075565B1 remains publicly unresolved
Because the Federal Circuit dismissed without ruling on the merits, no precedential or non-precedential opinion addresses the validity of US10075565B1. The appeal stemmed from an invalidity or cancellation action — meaning a lower tribunal (likely the PTAB) had already issued a ruling. That ruling now stands as the last substantive word on patentability, unless further proceedings are initiated. Parties licensing or designing around this patent should verify the current PTAB status.
PTAB ruling stands unchallenged at Federal CircuitFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Jenam Tech, LLC | Company | Patent assertion entity — holder of US10075565B1 (idle TCP connection detection)Search in Eureka ↗ |
| Defendant | Google, LLC | Company | Google, LLC — global technology company and cloud/networking services providerSearch in Eureka ↗ |
| Plaintiff counsel | Derek Dahlgren | Attorney | Counsel for Jenam Tech, LLCSearch in Eureka ↗ |
| Defendant counsel | Joseph Palys | Attorney | Counsel for Google, LLCSearch in Eureka ↗ |
| Defendant counsel | Naveen Modi | Attorney | Counsel for Google, LLCSearch in Eureka ↗ |
| Defendant counsel | Quadeer Ahmed | Attorney | Counsel for Google, LLCSearch in Eureka ↗ |
| Defendant counsel | Stephen Blake Kinnaird | Attorney | Counsel for Google, LLCSearch in Eureka ↗ |
| Presiding judge | Judge / | Chief Judge | Court of Appeals for the Federal Circuit — Chief JudgeSearch in Eureka ↗ |
Stipulation of dismissal — official text
The order’s language — ‘The parties having so agreed’ — confirms this was a bilateral stipulated dismissal, not a unilateral withdrawal or court-imposed termination. Fed. R. App. P. 42(b) requires a signed agreement, meaning Google actively consented to the exit rather than opposing the appeal to secure a merits victory. The explicit cost-neutrality clause prevents either side from claiming prevailing-party status. No substantive ruling on US10075565B1’s validity was issued, leaving the patent’s enforceability governed solely by the underlying tribunal’s record.
US10075565B1 — Idle TCP Connection Detection Methods
US10075565B1 (application number US15/915052) protects methods, systems, and computer program products for sharing information used to detect an idle TCP connection. TCP (Transmission Control Protocol) is the foundational transport-layer protocol governing most internet communication; idle connection detection governs how networked systems identify and manage connections that are no longer actively exchanging data. The patent’s claims address a specific technical problem in connection-state management — relevant to servers, proxies, load balancers, and cloud infrastructure at scale.
For major cloud and internet infrastructure providers like Google, efficient TCP connection lifecycle management is operationally significant — affecting latency, resource utilisation, and service reliability across billions of simultaneous connections. A patent asserting novel methods in this space carries enforcement potential against a wide range of networking products, middleware, and cloud services. The patentability challenge brought by Google — and the subsequent Federal Circuit appeal — suggests the claim scope was commercially material enough to warrant sustained inter-partes review or post-grant proceedings.
Should your team run an FTO against US10075565B1?
Any R&D or product team developing TCP connection management features — including idle timeout logic, connection-state sharing across distributed systems, or proxy/load balancer connection handling — should assess exposure against US10075565B1. The patent’s reach extends to software implementations, not just hardware, meaning SaaS platforms, networking middleware vendors, and cloud-native infrastructure teams are potential targets. The unresolved PTAB posture makes claim-level analysis essential before assuming the patent is invalid.
PatSnap Eureka’s FTO Search Agent allows you to map your product’s connection-state management logic against the specific claim language of US10075565B1, flagging overlapping claim elements and surfacing related family members you may not have identified. Eureka’s claim monitoring feature can alert your team to prosecution amendments or reissue activity that could affect scope — critical when the underlying validity record is still being settled across parallel proceedings.
Run a freedom-to-operate analysis on US10075565B1 to assess your product’s exposure
Run FTO in Eureka →Similar TCP and networking protocol patent cases at the Federal Circuit
PatSnap Eureka tracks related litigation across truck body equipment, vehicle accessories, and comparable infringement actions in the Georgia district system.
What this case signals for the networking patent IP landscape
A cost-neutral Federal Circuit exit on a TCP protocol patent raises questions about enforcement strategy and portfolio positioning in foundational internet infrastructure IP.
Agreed Federal Circuit exits often mask downstream licensing activity
When parties stipulate to dismiss a patentability appeal with no cost award, it is consistent with a parallel commercial agreement — licensing, cross-licensing, or covenant not to sue — being reached. Product and legal teams monitoring Jenam Tech’s enforcement activity should track any subsequent licensing disclosures or new assertion campaigns involving the same patent family.
TCP-layer patents remain a live enforcement category against cloud providers
Patents covering TCP connection management — a foundational networking protocol — have attracted assertion activity against major infrastructure providers. US10075565B1’s claims on idle connection detection sit at the intersection of network efficiency and cloud service reliability, areas where Google and peers continue to invest heavily. Similar claims warrant proactive FTO review for teams building connection-state management features.
Jenam v Google — key questions answered
The Federal Circuit appeal was dismissed by agreement of the parties under Fed. R. App. P. 42(b) on 9 January 2024, approximately 334 days after filing. No merits ruling on the patentability of US10075565B1 was issued. Each side was ordered to bear its own costs.
US10075565B1 covers methods, systems, and computer program products for sharing information used to detect an idle TCP (Transmission Control Protocol) connection. The patent addresses connection-state management in networked computing environments, relevant to servers, proxies, and cloud infrastructure.
The public record does not disclose the reason. A stipulated dismissal under Fed. R. App. P. 42(b) with cost-neutral terms is consistent with a negotiated resolution — potentially including a licensing agreement or covenant not to sue — but no such arrangement has been publicly confirmed.
No. The Federal Circuit issued no substantive ruling on validity. The appeal arose from an invalidity or cancellation action, meaning a lower tribunal — likely the PTAB — had already ruled. That ruling stands as the operative patentability record. Practitioners should consult the underlying PTAB proceeding to determine current claim status.
Under Fed. R. App. P. 39, costs normally follow the prevailing party. A mutual cost-bearing order signals that neither side was awarded prevailing-party status, which also avoids triggering fee-shifting analysis under 35 U.S.C. § 285. This outcome is typical of bilaterally negotiated dismissals rather than one-sided withdrawals.
PatSnap Eureka searches patents and litigation data to answer instantly.