Book a demo

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

Try now
Google v. K.Mizra: Thread Protocol Patent Dismissal | PatSnap
Patent Litigation

Google v. K.Mizra: Voluntary Dismissal After 187 Days

Google LLC filed suit against K.Mizra LLC in the Northern District of California over two patents covering the Thread networking protocol, implicating Nest Hub, Vertex AI Studio, and Google TV Streamer. The action was voluntarily dismissed without prejudice after 187 days, before K.Mizra served an answer or summary judgment motion.

Resolution time
187days
187 days from filing to voluntary dismissal — a notably short lifecycle for patent infringement litigation
Patents asserted
2
US8438120B2 and US8144717B2 — Thread networking protocol patents asserted across Nest and Vertex AI products
Outcome
Voluntary dismissal
Dismissed without prejudice under Rule 41(a)(1)(A)(i) before defendant answered or moved for summary judgment
Cost ruling
Not recorded
No cost or fee ruling recorded in the available public record
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Google's Thread Protocol Action Against K.Mizra Ends Early

Google LLC initiated this infringement action on 24 September 2025 in the Northern District of California before Judge Trina L. Thompson, asserting US8438120B2 and US8144717B2 against K.Mizra LLC. The patents relate to the Thread networking protocol, and the accused products include Google's Nest Hub, Hub Max, Wifi Pro, Google TV Streamer, Vertex AI Studio, and Vizier — a broad range spanning consumer smart-home hardware and AI infrastructure.

The recorded Basis of Termination is Voluntary dismissal. The docket order states that Google filed a notice of dismissal under Federal Rule of Civil Procedure 41(a)(1)(A)(i), dismissing the action without prejudice on the grounds that K.Mizra had not yet served an answer or a motion for summary judgment. The specific terms underlying the decision to dismiss are not disclosed in the available record.

The case closed on 30 March 2026, only 187 days after filing — a notably compressed timeline that suggests the dispute was resolved or strategically reconsidered well before any substantive court proceedings. What drove Google's decision to withdraw at this early stage, and whether the parties reached any private arrangement, is not disclosed in the public record.

See Complete Case & Patent Analysis →
Case at a glance
PlaintiffGoogle, LLC
DefendantK.Mizra, LLC
CourtCalifornia Northern District Court
JudgeTrina L Thompson
FiledSeptember 24, 2025
ClosedMarch 30, 2026
Duration187 days
OutcomeVoluntary dismissal
Verdict causeInfringement Action
BasisVoluntary dismissal
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 Voluntary dismissal in 187 days

187 days from filing to voluntary dismissal — a notably short lifecycle for patent infringement litigation

Case timeline: Complaint filed SEP 24 2025 — 187 days total Horizontal timeline showing the three key events in Google, LLC v K.Mizra, LLC from filing to resolution. Source: PACER, California Northern District Court. SEP 24 2025 Complaint filed Pre-trial proceedings MAR 30 2026 Voluntary dismissal 187 DAYS TOTAL
Patent at issue

US8438120B2 & US8144717B2 — Thread networking protocol technology

Publication No.US8438120B2
Application No.US12/597257
Patent details
ProductThread networking protocol for low-power mesh network communication in IoT devices
Cited in actionSeptember 24, 2025

Publication No.US8144717B2
Application No.US12/159753
Patent details
ProductWireless mesh networking protocol methods and systems for smart-home connectivity
Cited in actionSeptember 24, 2025
Technical brief · sourced from PatSnap patent database
Patent figure
Representative claim (1 of 3 independent)
1. A method of determining hyperparameters of a classifier in a machine learning system by iteratively producing an estimate of a target hyperparameter vector, each iteration comprising the steps of: drawing a random sample of hyperparameter vectors from a set of possible hyperparameter vectors, updating the estimate of the target hyperparameter vector by using the random sample, and selecting, from the random sample of hyperparameter vectors, a hyperparameter vector producing a best result in the present and any previous iterations, and wherein the step of updating the estimate of the target hyperparameter vecto…
Technical background
FIELD OF THE INVENTION The present invention relates to hyperparameter estimation. More in particular, the present invention relates to a method and device for determining hyperparameters of classifiers in machine learning systems and applications. BACKGROUND Classifiers are used in machine learning systems to classify physical objects and/or their (typically digital) representations. Machine learning systems may, for example, be used to assist fruit picking robots. The classifier of the machine learning system is…
Patent family
4 family members across 3 jurisdictions (US, WO, EP)
PatSnap Eureka · FTO Search Agent
Should you run an FTO against US8438120B2 and US8144717B2?

Any company developing or shipping Thread-compatible products — Matter hubs, smart speakers, mesh network routers, IoT sensors, or AI-enabled home devices — should assess freedom to operate against US8438120B2 and US8144717B2. This case demonstrates that K.Mizra is actively pursuing enforcement against major Thread implementers, and the without-prejudice dismissal means the claims remain live.

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)(i), Plaintiff Google LLC (“Plaintiff”) hereby dismisses this action WITHOUT PREJUDICE. According to Rule 41(a)(1)(A)(i), a plaintiff may dismiss an action without a court order by filing “a notice of dismissal before the opposing party serves either an answer or a motion for summary judgment.” Fed. R. Civ. P. 41(a)(1)(A)(i). Defendant K.Mizra LLC (“Defendant”) has neither served an answer nor a motion for summary judgment. Accordingly, Plaintiff voluntarily dismisses this action against Defendant WITHOUT PREJUDICE.
Source: PACER Docket, Case 3:25-cv-08107, California Northern District Court

Google's notice invokes the self-executing dismissal mechanism under FRCP 41(a)(1)(A)(i), which requires no court order and takes effect upon filing when the opposing party has not yet answered. The explicit without-prejudice designation preserves Google's right to refile. No merits findings, claim constructions, or validity rulings were issued, leaving both patents fully intact for future proceedings.

PACER case 3:25-cv-08107 · Public docket record Explore in Eureka ↗
Dismissal terms

Voluntarily dismissed: what the early exit means for both parties

Legal mechanism

Rule 41(a)(1)(A)(i): dismissal as of right, no court approval needed

Under FRCP 41(a)(1)(A)(i), a plaintiff may dismiss an action without a court order by filing a notice of dismissal before the opposing party serves an answer or summary judgment motion. Because K.Mizra had done neither, Google's notice was self-executing and immediately terminated the action. No judicial merits analysis was conducted.

Pre-answer voluntary dismissal
Prejudice status

Without prejudice: Google retains the right to refile

A dismissal without prejudice does not adjudicate the underlying claims and leaves Google free to refile the same action in the future. A dismissal with prejudice would have barred refiling. The public record states explicitly that this dismissal is WITHOUT PREJUDICE, but does not disclose whether any conditions or agreements between the parties inform that characterisation.

Refiling not barred
Defendant outcome

K.Mizra exits without a merits ruling — exposure persists

K.Mizra obtains no court judgment in its favour. Because the dismissal is without prejudice, the Thread protocol patent claims remain live and could be re-asserted. K.Mizra also filed no answer, so no counterclaims or invalidity defences entered the public record during this proceeding.

No merits adjudication
Commercial implications

Thread protocol IP risk remains open for the smart-home sector

The two Thread networking patents — US8438120B2 and US8144717B2 — were never adjudicated. Their validity and scope remain untested by this proceeding. Companies deploying Thread-based products, including Matter-compatible smart-home devices, should monitor these patents and any future enforcement activity by either party.

Patents unadjudicated
Legal analysis based on PACER docket records for case 3:25-cv-08107 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffGoogle, LLCCompany/Search in Eureka ↗
DefendantK.Mizra, LLCCompany/Search in Eureka ↗
Plaintiff counselEvan Matthew McLeanAttorneyCounsel for Google, LLCSearch in Eureka ↗
Plaintiff counselMichael A. LavineAttorneyCounsel for Google, LLCSearch in Eureka ↗
Plaintiff counselPeter Young KimAttorneyCounsel for Google, LLCSearch in Eureka ↗
Plaintiff counselSachin M PatelAttorneyCounsel for Google, LLCSearch in Eureka ↗
Plaintiff counselTharan Gregory LanierAttorneyCounsel for Google, LLCSearch in Eureka ↗
Plaintiff law firmJones DayLaw FirmRepresenting Google, LLCSearch in Eureka ↗
Plaintiff law firmJones Day (Chicago)Law FirmRepresenting Google, LLCSearch in Eureka ↗
Plaintiff law firmJones Day (Washington)Law FirmRepresenting Google, LLCSearch in Eureka ↗
Defendant counselBart StarrAttorneyCounsel for K.Mizra, LLCSearch in Eureka ↗
Defendant counselBrian BoermanAttorneyCounsel for K.Mizra, LLCSearch in Eureka ↗
Defendant counselDenise M. DeMoryAttorneyCounsel for K.Mizra, LLCSearch in Eureka ↗
Defendant counselEric R. CarrAttorneyCounsel for K.Mizra, LLCSearch in Eureka ↗
Defendant counselMatthew C. HolohanAttorneyCounsel for K.Mizra, LLCSearch in Eureka ↗
Defendant counselTristan Douglas LewisAttorneyCounsel for K.Mizra, LLCSearch in Eureka ↗
Defendant law firmBunsow DeMory LLPLaw FirmRepresenting K.Mizra, LLCSearch in Eureka ↗
Defendant law firmSheridan Ross PCLaw FirmRepresenting K.Mizra, LLCSearch in Eureka ↗
Presiding judgeJudge Trina L ThompsonJudgeCalifornia Northern District CourtSearch in Eureka ↗
R&D signals

R&D signals in the Thread networking and smart-home IP space

Forward-looking patent and innovation intelligence derived from Google v. K.Mizra — covering Thread protocol filing trends, K.Mizra's portfolio, and white-space opportunities in IoT mesh networking.

Patent portfolio

K.Mizra's Thread protocol patent portfolio and enforcement posture

K.Mizra LLC is an IP holding entity that has asserted Thread networking patents against Google's Nest and AI product lines. Understanding the full scope of K.Mizra's holdings — including continuations and family members of US8438120B2 and US8144717B2 — is critical for any company operating in the Thread or Matter ecosystem.

NPE enforcement — Thread
Technology landscape

Filing trends in Thread and Matter mesh networking protocols

Thread's adoption as the physical layer beneath the Matter smart-home standard has driven a surge in related patent filings. Mapping recent publication activity around low-power IPv6 mesh networking, border routers, and Thread commissioning reveals which players are building defensive and offensive IP positions in this rapidly growing space.

Thread / Matter filing trends
Competitive IP position

Google's defensive patent posture in smart-home networking

Google holds a substantial patent portfolio covering Nest-line hardware, mesh Wi-Fi, and AI-driven home device management. Analysing Google's filing activity in Thread-adjacent technologies — including Nest Hub, Google TV Streamer, and Vertex AI connectivity — reveals the depth of its defensive IP coverage and potential cross-licensing leverage.

Google Nest networking IP
White space

Design-around and white-space opportunities near Thread patent claims

With US8438120B2 and US8144717B2 unadjudicated, R&D teams have an opportunity to map claim boundaries and identify design-around architectures — particularly in Thread commissioning flows, border router implementations, and low-power mesh node protocols — where the prior art landscape may support novel differentiated approaches.

IoT mesh white space
Related litigation

Similar Thread protocol and IoT networking patent cases

Explore comparable patent infringement actions involving Thread, mesh networking, and IoT connectivity protocols in the Northern District of California and related venues.

🔍
Access 40+ similar cases in PatSnap Eureka
Google, LLC patent enforcement history, California Northern District Court case history, Google, LLC's full IP portfolio, and comparable case analysis
Thread patent — N.D. Cal.IoT mesh networking suitsK.Mizra enforcement historyMatter protocol IP disputes
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the Thread protocol IP landscape

An early exit before answer suggests the commercial calculus shifted fast — the Thread protocol patents remain live and untested.

Thread networking patents remain fully enforceable after this case

US8438120B2 and US8144717B2 received no validity or infringement ruling. Any smart-home or IoT manufacturer shipping Thread-compatible hardware — Nest-class devices, Matter hubs, mesh networking nodes — faces unresolved exposure from these patent claims. A formal FTO analysis is warranted.

Pre-answer dismissals in NPE disputes often signal parallel negotiations

A voluntary dismissal filed before the defendant answers — after only 187 days — is consistent with a rapid commercial resolution or strategic repositioning. The specific terms are not disclosed in the available record. IP teams tracking K.Mizra's enforcement activity should watch for re-filing or related actions in other venues.

🔒
Full strategic analysis in PatSnap Eureka
Unlock deeper IP intelligence on Thread protocol enforcement trends and K.Mizra's patent posture in the Northern District of California.
K.Mizra portfolio depthThread patent family mapRe-filing risk indicators
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Google v K.Mizra — key questions answered

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

Monitor Thread protocol patent risk before your next product launch

US8438120B2 and US8144717B2 remain unadjudicated and enforceable. Run a PatSnap Eureka FTO analysis to assess exposure for Thread and Matter-compatible device portfolios before infringement risk crystallises.

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.