Book a demo

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

Try now
DataCloud Technologies v. Teradata Patent Dismissal | PatSnap
Explore in Eureka
Case ID1:25-cv-00559
FiledMay 2025
ClosedJul 2025
Patent Litigation

DataCloud Technologies v. Teradata: Four-Patent Suit Dismissed With Prejudice in 71 Days

DataCloud Technologies, LLC filed a four-patent infringement action against Teradata Corporation in Delaware, asserting patents covering network anonymity, data organisation, file descriptor disambiguation, and remote file access. The case closed with a voluntary dismissal with prejudice just 71 days after filing — before Teradata filed any responsive pleading.

Resolution time
71days
71 days — resolved well below the median lifecycle for Delaware District Court patent cases
Patents asserted
4
US7209959B1, US6651063B1, US6560613B1 and US7398298B2 — four patents covering data management and network access technologies
Outcome
Voluntary dismissal
Voluntarily dismissed with prejudice under Rule 41(a)(1)(A)(i); DataCloud’s claims permanently extinguished
Cost ruling
No Cost Award
No answer or summary judgment motion filed; cost allocation not addressed in public record
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Four-patent infringement suit ends before Teradata files its first response

DataCloud Technologies, LLC initiated this infringement action on 6 May 2025 in the District of Delaware before Judge Gregory B. Williams, asserting four United States patents against Teradata Corporation. The patents span data management systems, network anonymity communications, file descriptor disambiguation, and remote electronic file access — a portfolio consistent with licensing-focused assertion strategies targeting enterprise data infrastructure vendors.

On 16 July 2025, DataCloud filed a voluntary notice of dismissal with prejudice pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(i). That procedural route is only available before the opposing party has served an answer or a motion for summary judgment — Teradata had filed neither, confirming the case closed at the earliest possible stage. A dismissal with prejudice under this rule is self-executing and does not require a court order, though it permanently bars DataCloud from re-filing the same claims against Teradata.

The 71-day lifecycle and the ‘with prejudice’ designation together suggest a resolution — likely a licensing agreement or negotiated settlement — was reached privately. The public record does not disclose any financial terms. The speed of resolution before any substantive litigation activity is consistent with defendants who engage early in licensing discussions, though the specific driver of the dismissal remains unknown from available filings.

Case at a glance
Case no.1:25-cv-00559
DefendantTeradata
CourtDelaware
JudgeGregory B. Williams
FiledMay 6, 2025
ClosedJuly 16, 2025
Duration71 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 / Delaware District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Voluntary dismissal in 71 days

71 days — resolved well below the median lifecycle for Delaware District Court patent cases

Case timeline: Complaint filed MAY 6 2025, JUN–JUL — 71 days total Horizontal timeline showing the three key events in DataCloud Technologies, LLC v Teradata from filing to resolution. Source: PACER, Delaware District Court. MAY 6 2025 Complaint filed Pre-trial proceedings JUL 16 2025 Voluntary dismissal 71 DAYS TOTAL
Dismissal terms

Voluntary dismissal with prejudice: what the Rule 41 filing means for both sides

Legal mechanism

Rule 41(a)(1)(A)(i) — self-executing dismissal with no court order required

Federal Rule of Civil Procedure 41(a)(1)(A)(i) allows a plaintiff to dismiss an action without a court order before the defendant serves an answer or a motion for summary judgment. DataCloud invoked this rule to file a self-executing notice — the case closed immediately on filing. Teradata had not answered, preserving DataCloud’s right to use this mechanism but the ‘with prejudice’ election permanently forecloses refiling.

Rule 41(a)(1)(A)(i) invoked
Plaintiff outcome

With prejudice: DataCloud permanently barred from re-asserting these claims against Teradata

A voluntary dismissal ‘with prejudice’ functions as a final adjudication on the merits for claim-preclusion purposes. DataCloud cannot refile the same four patents against Teradata in any U.S. federal court. This is a meaningful distinction from a without-prejudice dismissal, which would preserve the option to refile. The with-prejudice designation strongly suggests a negotiated resolution was reached — plaintiffs rarely permanently surrender claims without receiving value in return.

Claims permanently extinguished
Defendant outcome

Teradata exits without filing a single pleading — no merits ruling required

Teradata Corporation avoided any substantive engagement with the merits of the asserted patents. No invalidity defences, no claim construction positions, and no non-infringement arguments entered the public record. The pre-answer timing of the dismissal means there is no finding — positive or negative — regarding the four patents. Teradata’s exposure to these specific claims from DataCloud is now permanently resolved.

No merits adjudication
Commercial implications

Early resolution limits precedent but signals licensing risk for peers in enterprise data

The absence of any claim construction or invalidity ruling leaves the four DataCloud patents without any public-record weakening. Other enterprise data analytics, cloud warehouse, or data management vendors facing similar assertions from DataCloud cannot rely on this case for defensive precedent. The rapid, pre-answer resolution is consistent with a licensing-driven strategy and suggests DataCloud may pursue other defendants in the enterprise data infrastructure space.

No invalidation on record
Legal analysis based on PACER docket records for case 1:25-cv-00559 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffDataCloud Technologies, LLCCompanyPatent assertion entity — holder of US7209959B1, US6651063B1, US6560613B1, and US7398298B2Search in Eureka ↗
DefendantTeradataIndividualTeradata Corporation — enterprise data analytics and cloud warehouse platform providerSearch in Eureka ↗
Plaintiff counselRichard C. WeinblattAttorneyCounsel for DataCloud Technologies, LLCSearch in Eureka ↗
Plaintiff counselStamatios StamoulisAttorneyCounsel for DataCloud Technologies, LLCSearch in Eureka ↗
Plaintiff law firmStamoulis & Weinblatt LLCLaw FirmRepresenting DataCloud Technologies, LLCSearch in Eureka ↗
Presiding judgeJudge Gregory B. WilliamsJudgeDelaware District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Plaintiff DATACLOUD TECHNOLOGIES, LLC by and through undersigned counsel and pursuant to Feb. R. Civ. Proc. 41(a)(I)(A)(i), hereby voluntarily dismisses all claims in its Complaint WITH PREJUDICE for Defendant TERADATA CORPORATION (”Teradata"). Teradata has neither filed an Answer nor filed a motion for Summary Judgment in this matter.”
Source: PACER Docket, Case 1:25-cv-00559, Delaware District Court

The dismissal notice invokes Rule 41(a)(1)(A)(i) and explicitly designates the dismissal as ‘with prejudice.’ The reference to Teradata having neither answered nor moved for summary judgment confirms procedural eligibility for this self-executing mechanism. The with-prejudice election is the legally significant detail: it converts a voluntary exit into a claim-preclusive event, permanently extinguishing DataCloud’s right to assert these four patents against Teradata. No merits findings were made and no court order was required.

PACER case 1:25-cv-00559 · Public docket record Explore in Eureka ↗
Patent at issue

US7209959B1, US6651063B1, US6560613B1 & US7398298B2 — data management and network access portfolio

Publication No.US7209959B1
Application No.US09/542858
Patent details
ProductVirtual domain network anonymity system for client communications
Cited in actionMay 6, 2025

Publication No.US6651063B1
Application No.US09/493911
Patent details
ProductData organisation and management system and method
Cited in actionMay 6, 2025

Publication No.US6560613B1
Application No.US09/500212
Patent details
ProductFile descriptor disambiguation method and system
Cited in actionMay 6, 2025

Publication No.US7398298B2
Application No.US11/690803
Patent details
ProductRemote access and retrieval of electronic files
Cited in actionMay 6, 2025

The four asserted patents originate from application filings in the early 2000s, covering distinct but commercially complementary layers of enterprise data infrastructure. US7209959B1 covers apparatus and methods for communicating through a virtual domain to provide anonymity on a network — relevant to VPN-style and multi-tenant cloud architectures. US6651063B1 addresses data organisation and management systems. US6560613B1 covers the disambiguation of file descriptors, a foundational technique in operating system and storage layers. US7398298B2 addresses remote access and retrieval of electronic files.

Collectively, this portfolio targets functionality embedded across enterprise data warehousing, cloud storage, and analytics platforms — making vendors like Teradata plausible assertion targets. The early-2000s priority dates mean these patents are mature, but their claim scope — if drafted broadly — can still read on modern implementations of data management and network access features. The absence of any IPR challenge in this case means no post-grant validity review has reduced their enforceability in the public record.

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

Should your team run an FTO against the DataCloud patent portfolio?

Any company developing or deploying enterprise data analytics platforms, cloud data warehouses, virtual networking layers, or remote file access systems should treat this portfolio as an active risk. DataCloud has now demonstrated a willingness to litigate — and to resolve — assertions against a major enterprise data vendor. If your product involves multi-tenant data management, file descriptor handling, or virtualised network communication, the four asserted patents warrant direct claim analysis before a demand letter arrives.

PatSnap Eureka’s FTO Search Agent can map each of the four DataCloud patents against your product’s feature set, identify claim elements with potential overlap, and surface prior art that could support an invalidity position. Because no claim construction or IPR record exists for these patents from this case, a clean FTO analysis built on the patent text and prosecution history is the most reliable available baseline for assessing your exposure.

PatSnap Eureka FTO Search

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

Run FTO in Eureka →
Related litigation

Similar patent cases: data management and network access assertions in Delaware

Explore related patent infringement actions involving data management, network access, and file system technologies filed in the Delaware District Court.

🔍
Access 40+ similar cases in PatSnap Eureka
DataCloud Technologies, LLC patent enforcement history, Delaware case history, DataCloud Technologies, LLC’s full IP portfolio, and comparable case analysis
DataCloud v. other defendantsDelaware PAE filing trendsNetwork anonymity patent casesPre-answer dismissal outcomes
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the enterprise data management IP landscape

A rapid, pre-answer dismissal with prejudice in Delaware rarely signals weakness — it more typically signals a deal.

Pre-answer dismissals with prejudice are strong proxies for licensing outcomes

When a plaintiff voluntarily dismisses with prejudice before the defendant files any pleading, it almost always reflects a concluded negotiation. DataCloud permanently surrendered its litigation rights against Teradata — a step no rational plaintiff takes without receiving something in return. Enterprise data vendors receiving demand letters from DataCloud should treat this pattern as evidence of an active licensing campaign.

Four asserted patents remain active threat — no invalidation on the public record

None of the four DataCloud patents — covering network anonymity, data management systems, file descriptor handling, and remote file access — were subjected to any claim construction, invalidity challenge, or IPR in this case. The patents retain full enforceability. Any competitor operating in overlapping technology spaces should conduct FTO analysis before this portfolio re-emerges in a new filing.

🔒
Full strategic analysis in PatSnap Eureka
Unlock deeper analysis on DataCloud’s assertion strategy and Delaware District Court patent campaign trends across enterprise data IP.
Plaintiff filing historyRelated IPR risk analysisComparable settlement values
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

DataCloud v Teradata — key questions answered

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

Track data management patent risks before a demand letter lands

The DataCloud portfolio remains fully enforceable with no IPR or claim construction on record. Use PatSnap Eureka to run FTO searches across all four patents and monitor for new assertions against enterprise data and cloud infrastructure vendors.

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.