Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
Jenam Tech v. Google: TCP Connection Detection Patent Dismissal | PatSnap
Patent Litigation

Jenam Tech v. Google: Nine-Patent TCP Detection Dispute Ends in Dismissal

Jenam Tech, LLC filed suit against Google LLC in the Northern District of California asserting nine patents covering TCP idle connection detection methods. The dispute, which consolidated six related actions, ended after 779 days with all of Jenam's infringement claims dismissed with prejudice and Google's counterclaims dismissed without prejudice.

Resolution time
779days
779 days — a case resolved before trial in the N.D. California
Patents asserted
9
US10951742B1 and 8 further patents asserted covering TCP connection detection
Outcome
Case Dismissed
All infringement claims dismissed with prejudice; defendant counterclaims dismissed without prejudice
Cost ruling
Own Costs
Each party bears its own costs, expenses, and attorneys' fees
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Six consolidated TCP patent cases against Google end in dismissal

Jenam Tech, LLC initiated this patent infringement action against Google LLC on October 12, 2021, in the Northern District of California before Judge Jon S. Tigar. Jenam asserted nine patents — including US10951742B1, US10306026B1, US10069945B1, US10075565B1, US10742774B1, US10075564B1, US9923995B1, US9923996B1, and US10375215B1 — covering methods, systems, and computer program products for sharing information to detect idle TCP connections and connection time periods. The case was consolidated with five related actions (Case Nos. 4:21-cv-09318, 4:21-cv-02836, 4:21-cv-02837, 4:21-cv-02838, and 4:21-cv-02839).

The recorded basis of termination is 'Case Dismissed.' The docket order states that, pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(ii), the parties filed a stipulation dismissing all six consolidated actions: all infringement claims Jenam raised or could have raised are dismissed with prejudice, while all claims, defenses, or counterclaims raised by Google are dismissed without prejudice. Each party bears its own costs, expenses, and attorneys' fees. The specific terms underlying the parties' agreement to stipulate are not disclosed in the available record.

The case ran for 779 days before resolution — a substantial pre-trial period in a multi-patent, multi-action consolidation. The asymmetric dismissal structure — plaintiff's claims with prejudice, defendant's counterclaims without prejudice — is a notable feature of the stipulated disposition, though what drove the parties to this arrangement is not disclosed in the public record. Google retains the ability to reassert any counterclaims it voluntarily dismissed, while Jenam Tech is permanently barred from re-litigating the same infringement theories against Google on these nine patents.

See Complete Case & Patent Analysis →
Case at a glance
DefendantGoogle, LLC
CourtCalifornia Northern District Court
JudgeJon S. Tigar
FiledOctober 12, 2021
ClosedNovember 30, 2023
Duration779 days
OutcomeCase Dismissed
Verdict causeInfringement Action
BasisCase 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 / California Northern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Case Dismissed in 779 days

779 days — a case resolved before trial in the N.D. California

Case timeline: Complaint filed OCT 12 2021 — 779 days total Horizontal timeline showing the three key events in Jenam Tech, LLC v Google, LLC from filing to resolution. Source: PACER, California Northern District Court. OCT 12 2021 Complaint filed Pre-trial proceedings NOV 30 2023 Case Dismissed 779 DAYS TOTAL
Patent at issue

US10951742B1 — TCP idle connection detection methods and systems

Publication No.US10951742B1
Application No.US17/079397
Patent details
ProductMethods and systems for sharing information to detect idle TCP connections
Cited in actionOctober 12, 2021

Publication No.US10306026B1
Application No.US16/040517
Patent details
ProductMethods and systems for sharing information to detect TCP connection time periods
Cited in actionOctober 12, 2021

Publication No.US10069945B1
Application No.US15/915053
Patent details
ProductComputer program products for TCP connection idle detection
Cited in actionOctober 12, 2021

Publication No.US10075565B1
Application No.US15/915052
Patent details
ProductMethods for detecting at least one time period for a TCP connection
Cited in actionOctober 12, 2021

Publication No.US10742774B1
Application No.US16/368811
Patent details
ProductSystems and methods for TCP connection monitoring and idle detection
Cited in actionOctober 12, 2021

Publication No.US10075564B1
Application No.US15/915047
Patent details
ProductComputer program products for sharing TCP connection state information
Cited in actionOctober 12, 2021

Publication No.US9923995B1
Application No.US15/694802
Patent details
ProductMethods for detecting idle TCP connections using shared information
Cited in actionOctober 12, 2021

Publication No.US9923996B1
Application No.US15/694803
Patent details
ProductSystems for detecting idle TCP connections using shared network information
Cited in actionOctober 12, 2021

Publication No.US10375215B1
Application No.US16/040522
Patent details
ProductMethods and systems for sharing information for TCP connection time period detection
Cited in actionOctober 12, 2021
Technical brief · sourced from PatSnap patent database
Patent figurePatent figure
Representative claim (1 of 4 independent)
1. An apparatus, comprising: a non-transitory memory storing instructions; and one or more processors in communication with the non-transitory memory, wherein the one or more processors execute the instructions to: identify, at a first node, first information on which at least a first duration for detecting a first type of time period is based; allocate a first resource for a first non-Transmission Control Protocol (non-TCP) connection; generate a first non-TCP packet including a first parameter field identifying first metadata for use in determining a second duration for detecting the first type of time period;…
Technical background
RELATED APPLICATIONS This application is a continuation of, and claims priority to U.S. patent application Ser. No. 16/914,267 entitled “METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR SHARING INFORMATION FOR DETECTING AN IDLE TCP CONNECTION,” filed on Jun. 26, 2020, which in turn is a continuation of, and claims priority to U.S. patent application Ser. No. 16/368,811 entitled “METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR SHARING INFORMATION FOR DETECTING AN IDLE TCP CONNECTION,” filed on Mar. 28, 2019,…
Patent family
14 family members across 1 jurisdiction (US)
PatSnap Eureka · FTO Search Agent
Should you run an FTO against US10951742B1 and the Jenam Tech TCP portfolio?

Any company operating networking infrastructure, cloud communication services, load balancers, or application servers that actively manage TCP connection lifecycles should treat this nine-patent portfolio as a live enforcement risk. The with-prejudice dismissal protects only Google. If your products or platforms implement methods for detecting idle TCP connections or monitoring connection time periods — whether in software, hardware, or firmware — an FTO analysis against each of the nine asserted patents is commercially prudent before scaling deployment.

Run FTO in Eureka
Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Official verdict

Official order — verbatim text

Pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(ii), Plaintiff, Jenam Tech, LLC, and Defendant, Google LLC, hereby stipulate to the dismissal of the following consolidated and related actions: • Case No. 4:21-cv-07994-JST • Case No. 4:21-cv-09318-JST • Case No. 4:21-cv-02836-JST • Case No. 4:21-cv-02837-JST • Case No. 4:21-cv-02838-JST • Case No. 4:21-cv-02839-JST All claims of infringement that Plaintiff raised or could have raised in each of the above actions are dismissed WITH PREJUDICE. All claims, defenses, or counterclaims that Defendant raised in each of the above actions are dismissed WITHOUT PREJUDICE. Each Party will bear its own costs, expenses, and attorneys’ fees.
Source: PACER Docket, Case 4:21-cv-07994, California Northern District Court

The stipulation covers six consolidated district court actions simultaneously and draws a deliberate asymmetry: Jenam Tech's infringement claims exit with prejudice — a final bar — while Google's counterclaims exit without prejudice, preserving Google's defensive positions for potential future use. The each-party-bears-own-costs provision confirms no fee-shifting was ordered. The specific commercial or licensing terms, if any, that motivated the parties' agreement to this structure are not disclosed in the available record.

PACER case 4:21-cv-07994 · Public docket record Explore in Eureka ↗
Dismissal terms

Case dismissed: what the stipulated resolution means for both parties

Legal mechanism

Rule 41(a)(1)(A)(ii) stipulated dismissal explained

A Rule 41(a)(1)(A)(ii) dismissal is a voluntary dismissal by stipulation — both parties agree in writing to end the case, and court approval is not required for it to take effect. Here, the stipulation covers six consolidated actions simultaneously. The asymmetric structure — plaintiff's claims dismissed with prejudice, defendant's counterclaims without — is permitted under Rule 41 and reflects the parties' negotiated terms, though those terms are not disclosed in the public record.

Voluntary stipulated dismissal
Patent holder outcome

Jenam Tech permanently barred from re-filing these infringement claims

All infringement claims that Jenam Tech raised or could have raised across all six consolidated actions are dismissed with prejudice. This means Jenam Tech cannot re-litigate these specific infringement theories against Google on the nine asserted patents. It is a final disposition on the merits of Jenam's infringement position against Google. The specific terms underlying the agreement to accept this outcome are not disclosed in the available record.

Infringement claims — with prejudice
Defendant outcome

Google's counterclaims exit without prejudice — options remain open

All claims, defenses, and counterclaims raised by Google LLC are dismissed without prejudice. This preserves Google's ability to reassert any counterclaims — such as invalidity challenges — in a future proceeding if circumstances warrant. Google is not bound by any merits finding on its defensive positions. Each party bears its own costs, expenses, and attorneys' fees, meaning no fee-shifting occurred in Google's favour.

Counterclaims — without prejudice
Commercial implications

Asymmetric dismissal structure signals negotiated risk allocation

The split dismissal — plaintiff with prejudice, defendant without — is a structural signal that the parties negotiated the resolution rather than simply walking away. For the networking and cloud infrastructure sector, this case closes one enforcement vector for these nine TCP connection detection patents against Google. Other potential defendants in adjacent technology spaces should note that these patents remain in force; only the Google-specific infringement claims are extinguished.

Patent enforcement risk — sector watch
Legal analysis based on PACER docket records for case 4:21-cv-07994 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffJenam Tech, LLCCompany/Search in Eureka ↗
DefendantGoogle, LLCCompany/Search in Eureka ↗
Plaintiff counselCory EdwardsAttorneyCounsel for Jenam Tech, LLCSearch in Eureka ↗
Plaintiff counselDeepali A. BrahmbhattAttorneyCounsel for Jenam Tech, LLCSearch in Eureka ↗
Plaintiff counselDerek F. DahlgrenAttorneyCounsel for Jenam Tech, LLCSearch in Eureka ↗
Plaintiff counselJames M. LennonAttorneyCounsel for Jenam Tech, LLCSearch in Eureka ↗
Plaintiff counselMariam ClaytonAttorneyCounsel for Jenam Tech, LLCSearch in Eureka ↗
Plaintiff counselNadiia LoizidesAttorneyCounsel for Jenam Tech, LLCSearch in Eureka ↗
Plaintiff counselTimothy DevlinAttorneyCounsel for Jenam Tech, LLCSearch in Eureka ↗
Plaintiff law firmDevlin Law Firm LLCLaw FirmRepresenting Jenam Tech, LLCSearch in Eureka ↗
Defendant counselAnjali SrinivasanAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselBrian L. FerrallAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselEdward Andrew BayleyAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselJason S. GeorgeAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselKatie Lynn JoyceAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselKristin Elizabeth HucekAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselMatthew Mickle WerdegarAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselMichael E. JonesAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselMichelle Sabrina YbarraAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselPatrick C. ClutterAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselRobert Addy Van NestAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselRyan K. M. WongAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselRylee Kercher OlmAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant law firmKeker, Van Nest & Peters LLPLaw FirmRepresenting Google, LLCSearch in Eureka ↗
Defendant law firmPotter Minton PCLaw FirmRepresenting Google, LLCSearch in Eureka ↗
Presiding judgeJudge Jon S. TigarJudgeCalifornia Northern District CourtSearch in Eureka ↗
R&D signals

R&D signals in the TCP connection management patent space

Forward-looking patent and innovation intelligence derived from the Jenam Tech v. Google TCP connection detection portfolio — relevant to network infrastructure, cloud, and communication platform R&D teams.

Patent portfolio

Jenam Tech's TCP detection family: portfolio depth and filing trajectory

Jenam Tech assembled a nine-patent family spanning multiple application cycles from US15/694802 through US17/079397, all directed at TCP connection idle detection and time-period monitoring. Mapping this family's prosecution history and any continuation or divisional applications can reveal whether additional claims are pending — and whether the assertion scope may widen beyond the nine patents litigated here.

PAE portfolio watch
Technology landscape

Filing trends in TCP connection lifecycle and idle detection technology

TCP connection state management — including idle detection, keep-alive optimisation, and connection timeout signalling — is an active R&D area driven by cloud scalability demands. Tracking patent filing trends in this domain across cloud platform operators, networking chip vendors, and CDN providers can surface emerging claim landscapes and identify where freedom-to-operate gaps may be developing.

Networking IP trends
Competitor IP posture

Google's defensive patent activity in TCP and networking protocols

Google LLC, as a defendant in this consolidated action, brings substantial defensive patent infrastructure to networking and protocol technology disputes. Analysing Google's own patent portfolio in TCP connection management and networking protocol optimisation reveals the defensive prior art landscape and signals where Google is building proprietary IP to insulate its cloud and infrastructure products from future assertion.

Google networking IP
White space

Adjacent R&D opportunities near TCP idle detection claim scope

The Jenam Tech patents focus on information-sharing methods for detecting idle states and time periods in TCP connections. Adjacent white-space opportunities may exist in QUIC and HTTP/3 connection management, WebSocket lifecycle optimisation, and stateful connection tracking in containerised microservice environments — areas where TCP-centric claim language may not extend, offering lower-risk innovation space for engineering teams.

White space — QUIC/HTTP3
Related litigation

Similar TCP networking patent infringement cases in N.D. California

Cases involving TCP connection management and networking protocol patents litigated in the Northern District of California, including other Jenam Tech assertion actions.

🔍
Access 40+ similar cases in PatSnap Eureka
Jenam Tech, LLC patent enforcement history, California Northern District Court case history, Jenam Tech, LLC's full IP portfolio, and comparable case analysis
Jenam Tech other actionsTCP patent N.D. Cal casesPAE networking IP suitsGoogle IP dismissal cases
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the TCP networking patent IP landscape

A nine-patent assertion against one of the world's largest infrastructure operators, resolved without trial. Here is what it means for IP strategy.

With-prejudice bar limits Jenam Tech's Google enforcement permanently

The dismissal with prejudice of all infringement claims Jenam Tech raised or could have raised against Google closes this enforcement avenue entirely. Any company monitoring Jenam Tech's assertion activity should note that Google is no longer a viable target for these nine patents — but other parties are not protected by this outcome.

Nine TCP detection patents remain active and enforceable against others

The dismissal resolves only the Google dispute. US10951742B1 and the eight co-asserted patents remain in force. Companies operating networking infrastructure, cloud services, or communication platforms that rely on TCP connection management should assess whether their implementations fall within the claims of these patents.

🔒
Full strategic analysis in PatSnap Eureka
Unlock deeper strategic signals on TCP networking patent enforcement trends and PAE activity in the N.D. California district court.
Jenam Tech filing activityTCP patent invalidity riskGoogle counterclaim strategy
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

Track TCP networking patent enforcement — before the next filing

The nine Jenam Tech TCP connection detection patents remain enforceable. Use PatSnap Eureka to monitor assertion activity, run FTO analysis against your networking stack, and receive alerts on continuation filings that may expand this patent family's scope.

Disclaimer

This page is compiled from public court dockets and third-party patent and litigation data via PatSnap Eureka, and is provided for general informational purposes only. The information shown — including party names, patent and application numbers, dates, case status, outcomes, and any analysis — may be incomplete, may not reflect the most recent filings or legal status, and may contain errors or omissions. Verify all details against official court records (for example, PACER) and the relevant patent office before relying on them.

Nothing on this page constitutes legal advice or a legal opinion on the validity, infringement, enforceability, or scope of any patent or case, and no attorney‑client relationship is created by its use. Any description of an outcome (such as a dismissal, settlement, or consent judgment) is a general summary, not a legal determination. All patents, trademarks, and company or law‑firm names are the property of their respective owners. PatSnap makes no warranty as to the accuracy or completeness of this content and disclaims, to the fullest extent permitted by law, all liability for reliance on it. For advice on a specific matter, consult qualified legal counsel.

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

Related Litigation Cases

Help us improve this page

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