Book a demo

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

Try now
TG-2006 Holdings v. pCloud AG — Business Tracking System Patent | PatSnap
Explore in Eureka
Case ID2:24-cv-00069
FiledFeb 2024
ClosedMar 2025
Patent Litigation

TG-2006 Holdings v. pCloud AG: Dismissed With Prejudice After 398 Days

TG-2006 Holdings, LLC brought a patent infringement action against Swiss cloud storage provider pCloud AG in the Eastern District of Texas, asserting two patents covering systems and methods for tracking information in a business environment. After 398 days — and before pCloud filed any answer — TG-2006 voluntarily dismissed the case with prejudice, permanently closing its claims.

Resolution time
398days
398 days from filing to closure — resolved before defendant answered
Patents asserted
2
US9454741B2 and 1 further patent asserted — business environment tracking system
Outcome
Voluntary dismissal
Voluntary dismissal with prejudice — plaintiff may not refile these claims
Cost ruling
Each Party Bears Own Costs
No fee award — each side responsible for its own costs, expenses, and attorneys’ fees
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Cloud storage provider exits Texas infringement action with prejudice bar

On 1 February 2024, TG-2006 Holdings, LLC filed suit against pCloud AG in the U.S. District Court for the Eastern District of Texas (Judge Rodney Gilstrap) alleging infringement of US9454741B2 and US9805323B2 — both directed at systems and methods for tracking information in a business environment. pCloud AG, a Switzerland-based cloud storage provider, was the sole defendant. Plaintiff was represented by Isaac Phillip Rabicoff of Rabicoff Law LLC; pCloud filed no appearance of counsel on the public docket.

On 5 March 2025 — 398 days after filing — TG-2006 filed a Notice of Voluntary Dismissal With Prejudice under Federal Rule of Civil Procedure 41(a)(1)(A)(i). Because pCloud had not yet answered the complaint or moved for summary judgment, the dismissal was self-executing under the rule. Judge Gilstrap accepted and acknowledged the dismissal, closing all claims with prejudice and ordering each party to bear its own costs, expenses, and attorneys’ fees.

The dismissal with prejudice is a permanent bar: TG-2006 cannot reassert these two patents against pCloud on the same claims. The fact that pCloud never answered is consistent with a pre-litigation or early-stage resolution, though the public record does not disclose whether a confidential settlement drove the exit or whether TG-2006 simply elected to abandon the action. The 398-day gap before dismissal — longer than many early settlements — suggests some degree of negotiation or strategic reassessment occurred off the record.

Case at a glance
Case no.2:24-cv-00069
DefendantpCloud AG
CourtTexas Eastern
JudgeRodney Gilstrap
FiledFebruary 1, 2024
ClosedMarch 5, 2025
Duration398 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 / Texas Eastern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Voluntary dismissal in 398 days

398 days from filing to closure — resolved before defendant answered

Case timeline: Complaint filed FEB 1 2024, AUG–SEP — 398 days total Horizontal timeline showing the three key events in TG–2006 Holdings, LLC v pCloud AG from filing to resolution. Source: PACER, Texas Eastern District Court. FEB 1 2024 Complaint filed Pre-trial proceedings MAR 5 2025 Voluntary dismissal 398 DAYS TOTAL
Dismissal terms

Dismissed with prejudice: what the voluntary exit means for both parties

Legal mechanism

Rule 41(a)(1)(A)(i): self-executing dismissal before answer

Under FRCP 41(a)(1)(A)(i), a plaintiff may voluntarily dismiss without a court order if the defendant has not yet answered or moved for summary judgment. The dismissal takes effect upon filing the notice. Here, the court accepted and acknowledged it as a formality. Critically, TG-2006 specified ‘with prejudice,’ converting what is normally a no-strings exit into a permanent bar on refiling the same claims against pCloud.

Rule 41(a)(1)(A)(i) — pre-answer
Plaintiff outcome

TG-2006 permanently surrenders its claims against pCloud

By dismissing with prejudice, TG-2006 Holdings irrevocably waived its right to reassert US9454741B2 and US9805323B2 against pCloud AG on the same claims and accused products. This is a more decisive exit than a without-prejudice dismissal, which would permit refiling. The public record does not reveal whether TG-2006 received any consideration — financial or otherwise — before making this permanent concession.

Claims permanently extinguished
Defendant outcome

pCloud walks away — no liability, no fee award, permanent peace

pCloud AG never answered the complaint, suggesting the matter resolved — or was abandoned — before substantive litigation commenced. The court’s order that each party bear its own costs means pCloud received no fee recovery despite being a foreign defendant. However, the with-prejudice bar provides pCloud enduring protection: TG-2006 cannot revive these patent claims against it in any future action.

No liability — costs split
Commercial implications

Business tracking patents remain live — other cloud operators remain exposed

The dismissal resolves only TG-2006’s claims against pCloud. US9454741B2 and US9805323B2 remain in force and could be asserted against other cloud storage or business-information-tracking operators. Companies deploying systems that track, manage, or organise information in a business context should treat this litigation as an indicator that these patents are being actively enforced — and conduct FTO analysis accordingly.

Patents remain enforceable
Legal analysis based on PACER docket records for case 2:24-cv-00069 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffTG–2006 Holdings, LLCCompanyPatent assertion entity — holder of US9454741B2 and US9805323B2Search in Eureka ↗
DefendantpCloud AGCompanySwiss cloud storage provider offering personal and business cloud solutionsSearch in Eureka ↗
Plaintiff counselIsaac Phillip RabicoffAttorneyCounsel for TG–2006 Holdings, LLCSearch in Eureka ↗
Plaintiff law firmRabicoff Law LLCLaw FirmRepresenting TG–2006 Holdings, LLCSearch in Eureka ↗
Presiding judgeJudge Rodney GilstrapJudgeTexas Eastern District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Before the Court is the Notice of Voluntary Dismissal With Prejudice (the “Notice”) filed by Plaintiff TG–2006 Holdings, LLC (“Plaintiff”). (Dkt. No. 6.) In the Notice, Plaintiff voluntarily dismisses the above-captioned case against Defendant pCloud AG (“Defendant”) with prejudice pursuant to Rule 41(a)(1)(A)(i) of the Federal Rules of Civil Procedure. (Id. at 1.) Defendant has not yet answered the Complaint or moved for summary judgment. (Id.) Having considered the Notice, the Court ACCEPTS AND ACKNOWLEDGES that all claims by Plaintiff in the above-captioned case are DISMISSED WITH PREJUDICE. Each party is to bear its own costs, expenses, and attorneys’ fees. All pending requests for relief in the above-captioned case not explicitly granted herein are DENIED AS MOOT. The Clerk of Court is directed to CLOSE the above-captioned case as no parties or claims remain.”
Source: PACER Docket, Case 2:24-cv-00069, Texas Eastern District Court

The court’s order tracks the language of FRCP 41(a)(1)(A)(i) closely, confirming that because pCloud had not answered or moved for summary judgment, TG-2006’s notice was self-executing and required no judicial approval — the court’s acceptance being a formal acknowledgement rather than a grant of relief. The with-prejudice specification is outcome-determinative: it forecloses any future action by TG-2006 on these claims against pCloud, distinguishing this exit from a routine administrative closure. The costs-bear-own ruling leaves neither party with a financial judgment, consistent with an arm’s-length resolution whose terms, if any, remain confidential.

PACER case 2:24-cv-00069 · Public docket record Explore in Eureka ↗
Patent at issue

US9454741B2 & US9805323B2 — Business Information Tracking Systems

Publication No.US9454741B2
Application No.US14/078093
Patent details
Productsystem and method for tracking information in a business environment
Cited in actionFebruary 1, 2024

Publication No.US9805323B2
Application No.US15/277865
Patent details
Productsystem and method for tracking information in a business environment — continuation
Cited in actionFebruary 1, 2024

US9454741B2 (application no. US14/078093) and US9805323B2 (application no. US15/277865) both cover systems and methods for tracking information in a business environment. The later application number of US9805323B2 suggests it is a continuation or divisional of the earlier filing, extending the patent family’s coverage while the original prosecution history applies across both. The technology domain — business information tracking — spans a range of digital workflow, document management, and activity-logging implementations common in cloud and enterprise software.

For cloud storage providers, the breadth of ‘tracking information in a business environment’ is commercially significant. Features such as file versioning, audit logging, user activity tracking, shared-workspace management, and automated workflow triggers could each present potential claim-mapping exposure depending on claim construction. pCloud’s business-tier product offerings, which emphasise team collaboration and file management, are precisely the product category TG-2006 appears to have targeted. With no claim construction order or invalidity ruling on the record, the patents carry undiminished assertion value against the broader cloud sector.

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 US9454741B2 and US9805323B2?

Any organisation developing or commercialising cloud-based business information management, document tracking, workflow automation, or enterprise collaboration tools should treat this patent family as a live risk. TG-2006’s willingness to file in E.D. Texas against a Swiss cloud provider suggests an active enforcement posture, and the with-prejudice closure against pCloud does not limit future assertions against other parties. The absence of any court-issued claim construction makes prior-art and design-around analysis particularly important at this stage.

PatSnap Eureka’s FTO Search Agent can map the independent and dependent claims of US9454741B2 and US9805323B2 against your product feature set, flag prior art that could support IPR institution, and surface continuation applications that may extend this family’s coverage. R&D and product teams building business-environment tracking features should run this analysis before product launch or the next funding milestone — not after receiving a complaint.

PatSnap Eureka FTO Search

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

Run FTO in Eureka →
Related litigation

Similar patent infringement cases — business tracking systems in E.D. Texas

Cases involving business information tracking and cloud software patents litigated before Judge Gilstrap in the Eastern District of Texas, including PAE enforcement actions with comparable dismissal patterns.

🔍
Access 40+ similar cases in PatSnap Eureka
TG–2006 Holdings, LLC patent enforcement history, Texas Eastern case history, TG–2006 Holdings, LLC’s full IP portfolio, and comparable case analysis
PAE v. cloud SaaS — E.D. TexasBusiness tracking patent suitsGilstrap docket — 2024 filingsRule 41 dismissals — tech sector
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the cloud and business-software IP landscape

A with-prejudice exit before answer in E.D. Texas is rarely the full story. Here is what practitioners should take away.

E.D. Texas remains a first-choice venue for patent assertion entities

Judge Gilstrap’s docket continues to attract non-practising entity filings targeting technology companies, including foreign defendants. Cloud and SaaS operators without a strong U.S. presence should assess their E.D. Texas exposure and ensure they have rapid-response outside counsel arrangements in place before receiving a complaint.

With-prejudice voluntary dismissals signal finality — but not necessarily payment

Practitioners sometimes assume a with-prejudice dismissal reflects a settlement payment. That may be true here, but TG-2006 could equally have assessed litigation risk, costs of enforcement against a Swiss entity, or claim scope issues and elected to walk away. Without a disclosed settlement agreement, both readings are equally plausible from the public record.

🔒
Full strategic analysis in PatSnap Eureka
Unlock gated analysis on cloud and business-software patent enforcement trends at district court level, including IPR strategy and comparable PAE outcomes.
Patent scope risk mapIPR viability analysisComparable PAE settlements
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

TG–2006 v pCloud — key questions answered

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

Assess your exposure to this business tracking patent family

US9454741B2 and US9805323B2 remain active enforcement assets. Run an FTO analysis in PatSnap Eureka to map claim scope against your product features and monitor TG-2006 Holdings for new filings before your organisation receives a complaint.

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.