Book a demo
Jenam Tech v. Google — Idle TCP Connection Detection Patent Appeal | PatSnap
Explore in Eureka
Case ID23-1487
FiledFeb 2023
ClosedJan 2024
Patent Litigation

Jenam Tech v. Google: Federal Circuit Appeal Dismissed by Mutual Agreement

Jenam Tech, LLC appealed to the U.S. Court of Appeals for the Federal Circuit against Google, LLC over two patents covering methods for detecting idle TCP connections. The parties reached agreement to dismiss the appeal under Fed. R. App. P. 42(b) within 334 days, with each side bearing its own costs.

Resolution time
334days
334 days — resolved faster than most Federal Circuit patent appeals
Patents asserted
2
US10306026 and US10069945 — idle TCP connection detection methods
Outcome
Appeal Dismissed
By agreement under Fed. R. App. P. 42(b) — costs not shifted to either party
Cost ruling
Own costs
Each side bears its own costs — no cost award to plaintiff or defendant
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Mutual dismissal in a Federal Circuit TCP networking patent appeal

Jenam Tech, LLC filed this appeal at the U.S. Court of Appeals for the Federal Circuit on 9 February 2023, challenging a lower-level patentability determination relating to two patents — US10306026 and US10069945 — which cover methods, systems, and computer program products for detecting idle TCP connections. The defendant and appellee was Google, LLC, represented by a six-attorney team from Paul Hastings, LLP. The underlying verdict cause was an invalidity or cancellation action, suggesting the patents had been challenged on patentability grounds before a tribunal such as the Patent Trial and Appeal Board.

The appeal closed on 9 January 2024 when the parties filed a joint agreement to dismiss under Federal Rule of Appellate Procedure 42(b). The court’s order confirmed two things: the proceeding is dismissed, and each side shall bear its own costs. This structure — mutual dismissal with no cost shifting — is a hallmark of a privately negotiated resolution, whether a licensing settlement, a covenant not to sue, or some other commercial arrangement, though the specific terms remain confidential and are not disclosed in the public record.

The 334-day duration from filing to dismissal is consistent with parties reaching an agreement before full appellate briefing or oral argument concluded. Early resolution at the Federal Circuit typically signals either a deterioration in one party’s confidence in the appeal or, more commonly, a commercial settlement that made continued litigation economically irrational. What drove the agreement — licensing terms, portfolio cross-licensing, or simply a desire to avoid further legal spend — cannot be confirmed from the public docket.

Case at a glance
Case no.23-1487
DefendantGoogle, LLC
CourtCourt of Appeals for the Federal Circuit
Judge/
FiledFebruary 9, 2023
ClosedJanuary 9, 2024
Duration334 days
OutcomeAppeal Dismissed
Verdict causePatentability
BasisAppeal Dismissed
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Court of Appeals for the Federal Circuit via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to dismissal in 334 days

334 days — resolved faster than most Federal Circuit patent appeals

Case timeline: Complaint filed May 13 2025, JUL–AUG — 334 days total Horizontal timeline showing the three key events in Jenam Tech, LLC v Google, LLC from filing to voluntary dismissal. Source: PACER, Court of Appeals for the Federal Circuit. FEB 9 2023 Complaint filed JUL–AUG 2023 Pre-trial proceedings JAN 9 2024 Dismissed with prejudice 334 DAYS TOTAL
Dismissal terms

Appeal dismissed by mutual agreement — costs lie where they fall

Legal mechanism

Fed. R. App. P. 42(b) — what a voluntary dismissal means here

Rule 42(b) permits parties to voluntarily dismiss an appeal by agreement filed with the court. Unlike a court ruling on the merits, this order carries no precedential weight on the underlying patent validity questions. The patents’ status following dismissal depends on what was resolved at the lower tribunal level — the appeal’s dismissal does not itself cancel the patents.

No merits ruling
Cost ruling

Each side bears own costs — what the public record is silent on

The order specifies that each party bears its own appellate costs. This is a neutral cost outcome — neither party was awarded fees under 35 U.S.C. § 285 or Rule 39. However, this dismissal was agreed without the court specifying whether it is with or without prejudice. The public record is silent on whether Jenam Tech retains the right to refile related claims; that distinction may have been resolved in a private side agreement between the parties.

No cost shifting
Patentability context

Underlying invalidity action — what was at stake in this appeal

The verdict cause is classified as an invalidity/cancellation action, consistent with an inter partes review or post-grant proceeding at the PTAB targeting US10306026 and US10069945. An appeal to the Federal Circuit in this posture typically challenges a PTAB finding that one or more claims are unpatentable. Dismissal before a Federal Circuit decision means no appellate ruling on the validity of the asserted claims was issued.

PTAB appeal context
Commercial signal

Joint agreement suggests private resolution, not litigation fatigue alone

A bilateral Rule 42(b) dismissal with symmetric cost-bearing is structurally consistent with a licensing deal, a covenant not to sue, or a broader IP settlement between the parties. If Google resolved the matter commercially, it may have acquired a license or secured agreement that the patents would not be further asserted. Neither outcome can be confirmed from the public record, but the symmetric cost order suggests neither side extracted a clear litigation victory.

Likely private settlement
Legal analysis based on PACER docket records for case 23-1487 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffJenam Tech, LLCCompanyPatent assertion entity — holder of US10306026 and US10069945 for TCP idle detectionSearch in Eureka ↗
DefendantGoogle, LLCCompanyGoogle, LLC — global technology company and internet services providerSearch in Eureka ↗
Plaintiff counselDerek DahlgrenAttorneyCounsel for Jenam Tech, LLCSearch in Eureka ↗
Defendant counselAlexa LowmanAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselChetan BansalAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselJoseph PalysAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselNaveen ModiAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselQuadeer AhmedAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselStephen Blake KinnairdAttorneyCounsel for Google, LLCSearch in Eureka ↗
Presiding judgeJudge /Chief JudgeCourt of Appeals for the Federal Circuit — Chief JudgeSearch in Eureka ↗
Official verdict

Stipulation of dismissal — official text

“The parties having so agreed, it is ordered that: (1) The proceeding is DISMISSED under Fed. R. App. P. 42 (b).(2) Each side shall bear their own costs”
Source: PACER Docket, Case 23-1487, Court of Appeals for the Federal Circuit · Filed January 9, 2024

The court’s order is purely procedural: it confirms the parties’ agreement and imposes no finding on patent validity, infringement, or claim construction. The symmetric cost order — each side bears its own costs — reflects a negotiated exit rather than a litigation outcome. No precedent on the patentability of the idle TCP connection detection claims was established. The absence of a merits ruling leaves the underlying patents’ legal status dependent entirely on what the lower tribunal determined before this appeal was filed.

PACER case 23-1487 · Public docket record Explore in Eureka ↗
Patent at issue

US10306026 & US10069945 — Idle TCP Connection Detection Methods

Publication No.US10306026
Application No.US16/040517
Patent details
AssigneeJenam Tech, LLC
ProductUS10306026 — idle TCP connection detection, methods and systems
Publication typeB2 — grant (with prior publication)
Cited in actionFebruary 9, 2023

Publication No.US10069945
Application No.US15/915053
Patent details
AssigneeJenam Tech, LLC
ProductUS10069945 — idle TCP connection detection, computer program products
Publication typeB2 — grant (with prior publication)
Cited in actionFebruary 9, 2023

US10306026 (application no. US16/040517) and US10069945 (application no. US15/915053) both protect methods, systems, and computer program products for sharing information to detect an idle TCP connection. TCP — Transmission Control Protocol — is the foundational connection protocol for internet communications. Detecting idle or stale connections is operationally critical for server resource management, cloud infrastructure efficiency, and mobile network performance. These patents sit at the intersection of networking protocol implementation and software-defined connection management.

For any company operating large-scale internet infrastructure, cloud services, or connection-intensive applications, this patent family represents a meaningful validity and infringement risk vector. The fact that Jenam Tech pursued Google — one of the world’s largest operators of TCP-dependent infrastructure — to the Federal Circuit level suggests the patentee believed the claims had commercial scope broad enough to cover hyperscale deployments. The resolution without a merits ruling leaves the claim scope legally unresolved, which is relevant for any third party operating in the same technical space.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should your product team run an FTO against US10306026 and US10069945?

Any engineering or product team building connection management features, session keep-alive systems, load balancers, proxies, or mobile network gateways that handle TCP connection state should consider a freedom-to-operate review against this patent family. The claims appear directed at software-implemented detection of idle TCP connections — a function embedded in a wide range of server, cloud, and networking products. The absence of a Federal Circuit validity ruling means these patents have not been definitively invalidated at the appellate level.

PatSnap Eureka’s FTO Search Agent can map your product’s connection management architecture against the claim language of US10306026 and US10069945, identifying overlap risk and surfacing prior art that could support a design-around or invalidity argument. Eureka’s claim monitoring tools also allow your IP team to track continuation filings from this family, ensuring you are alerted if related claims with potentially broader scope enter prosecution or grant.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US10306026 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar Federal Circuit patent appeals in TCP and networking protocol technology

PatSnap Eureka tracks related litigation across truck body equipment, vehicle accessories, and comparable infringement actions in the Georgia district system.

🔍
Access 40+ similar cases in PatSnap Eureka
Jenam Tech, LLC patent enforcement history, Court of Appeals for the Federal Circuit case history, Jenam Tech, LLC’s full IP portfolio, and comparable case analysis
TCP patent appeals 2020–2024Google PTAB appeal dismissalsNetworking protocol PAE casesJenam Tech prior litigation
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the networking and cloud IP landscape

A quick Federal Circuit exit in a TCP patent dispute involving Google carries meaningful signals for patent holders and product teams in the networking and cloud infrastructure space.

TCP connection management remains an active patent assertion target

The assertion of two patents covering idle TCP connection detection against a hyperscaler like Google confirms that seemingly foundational networking protocol patents continue to attract enforcement activity. Product and engineering teams building connection management layers, keep-alive mechanisms, or session-monitoring tools should treat this patent family as a live monitoring priority.

Early Federal Circuit dismissals signal commercial resolution pressure

When parties agree to dismiss a Federal Circuit appeal this quickly — before full briefing in many cases — it typically suggests the economics of the dispute shifted. Whether through licensing or a covenant not to sue, Google appears to have resolved its exposure to these patents without a court ruling on validity. This pattern is common when the cost of appeal outweighs the cost of resolution.

🔒
Full strategic analysis in PatSnap Eureka
Includes sector IP trends, Judge Treadwell’s case history, and FTO risk assessment for the truck equipment space
Jenam Tech filing patternsTCP patent family exposureGoogle PTAB settlement signals
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Jenam v Google — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Run your own FTO analysis on TCP networking patents

Use PatSnap Eureka to map US10306026 and US10069945 against your product architecture and monitor for continuation filings. Track enforcement patterns from patent assertion entities active in the networking and cloud infrastructure space.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.