Book a demo

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

Try now
BillSure LLC v. VMware, Inc. — Network Resource Verification Patent | PatSnap
Explore in Eureka
Case ID7:25-cv-00016
FiledJan 2025
ClosedMar 2025
Patent Litigation

BillSure LLC v. VMware, Inc. — Dismissed With Prejudice in 75 Days

BillSure LLC filed a patent infringement action against VMware, Inc. in the Western District of Texas, asserting US8005457B2 covering methods and systems for verifying network resource usage records. The case closed just 75 days after filing, when BillSure voluntarily dismissed all claims with prejudice before VMware filed any answer or dispositive motion.

Resolution time
75days
75 days — resolved before defendant filed any responsive pleading
Patents asserted
1
US8005457B2 — method and system for verifying network resource usage records
Outcome
Voluntary dismissal
Plaintiff voluntarily dismissed all claims with prejudice under Rule 41(a)(1)(A)(i); no re-filing permitted
Cost ruling
Own Costs
Court ordered each party to bear its own costs, expenses, and attorney fees
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

A pre-answer dismissal with prejudice signals swift resolution pressure

BillSure LLC, holder of US8005457B2, filed suit against VMware, Inc. in the Western District of Texas on January 15, 2025, alleging infringement of a patent directed at methods and systems for verifying network resource usage records. The Western District of Texas is a venue with significant patent litigation history, and the filing suggests BillSure viewed VMware’s virtualisation and cloud infrastructure products as potentially within the scope of the asserted claims.

The case closed on March 31, 2025, just 75 days after filing. BillSure filed a Notice of Voluntary Dismissal With Prejudice on March 28, 2025, invoking Rule 41(a)(1)(A)(i), which permits a plaintiff to dismiss an action unilaterally — without court approval — so long as the defendant has not yet served an answer or a motion for summary judgment. Because VMware had not done so, the dismissal was self-effectuating. The ‘with prejudice’ designation means BillSure permanently surrendered its right to re-assert the same claims against VMware on this patent.

A dismissal with prejudice at this early stage — before any substantive defence was filed — typically suggests either a negotiated resolution, a strategic reassessment of claim viability, or pre-litigation pressure that resolved outside the docket. The public record is silent on whether any commercial arrangement accompanied the dismissal. What is clear is that VMware incurred no adjudicated liability and each party bears its own legal costs, a standard outcome under self-effectuating Rule 41 dismissals.

Case at a glance
Case no.7:25-cv-00016
PlaintiffBillSure LLC
DefendantVMware, Inc.
CourtTexas Western
JudgeN/A
FiledJanuary 15, 2025
ClosedMarch 31, 2025
Duration75 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 Western District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Voluntary dismissal in 75 days

75 days — resolved before defendant filed any responsive pleading

Case timeline: Complaint filed JAN 15 2025, FEB–MAR — 75 days total Horizontal timeline showing the three key events in BillSure LLC v VMware, Inc. from filing to resolution. Source: PACER, Texas Western District Court. JAN 15 2025 Complaint filed Pre-trial proceedings MAR 31 2025 Voluntary dismissal 75 DAYS TOTAL
Dismissal terms

Dismissed with prejudice: what the Rule 41 filing means for both parties

Legal mechanism

Rule 41(a)(1)(A)(i) — self-effectuating dismissal, no court order needed

Under FRCP 41(a)(1)(A)(i), a plaintiff may voluntarily dismiss an action by filing a notice alone, provided the defendant has not yet served an answer or motion for summary judgment. Because VMware had served neither, BillSure’s notice was immediately operative — the court’s order simply confirmed the procedural effect. No judicial merits determination was made.

No merits adjudication
Plaintiff outcome

With prejudice: BillSure cannot re-file against VMware on this patent

Dismissal with prejudice operates as a final judgment on the merits for res judicata purposes. BillSure permanently waived its right to reassert US8005457B2 claims against VMware in any future action. This is a materially stronger concession than a without-prejudice dismissal, which would have preserved the option to re-file. The public record does not disclose whether any consideration was exchanged.

Permanent bar on re-filing
Defendant outcome

VMware exits without adjudicated liability or cost award

VMware, Inc. secured a clean exit: no finding of infringement, no damages exposure, and no adverse cost ruling. The court ordered each party to bear its own costs and fees. VMware filed no answer and no dispositive motion, suggesting it incurred minimal litigation spend before the case resolved. The patent’s enforceability against VMware is permanently foreclosed under this case.

No liability, own costs
Commercial implications

US8005457B2 remains active — other defendants remain at risk

The dismissal resolves only BillSure’s claims against VMware. US8005457B2 remains an issued, enforceable patent. Companies operating network billing verification, usage metering, or cloud resource accounting systems should assess whether their implementations fall within the patent’s claim scope. BillSure’s willingness to file and then dismiss with prejudice suggests ongoing assertion activity in this technology space is possible.

Patent remains enforceable
Legal analysis based on PACER docket records for case 7:25-cv-00016 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffBillSure LLCCompanyPatent assertion entity — holder of US8005457B2 covering network resource usage verificationSearch in Eureka ↗
DefendantVMware, Inc.CompanyVMware, Inc. — enterprise virtualisation and cloud infrastructure providerSearch in Eureka ↗
Plaintiff counselIsaac RabicoffAttorneyCounsel for BillSure LLCSearch in Eureka ↗
Plaintiff law firmRabicoff Law LLCLaw FirmRepresenting BillSure LLCSearch in Eureka ↗
Presiding judgeJudge N/AJudgeTexas Western District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Before the Court is Plaintiff’s Notice of Voluntary Dismissal With Prejudice (Doc 9) filed March 28, 2025. In its notice, Plaintiff indicates voluntarily dismissing claims against the Defendant with prejudice under Federal Rule of Civil Procedure 41(a)(1)(A)(i). (Id.). Rule 41(a)(1)(A)(i) allows a plaintiff to voluntarily dismiss an action without a court order by filing a notice of dismissal before the opposing party serves an answer or a motion for summary judgment. Fed. R. Civ. P. 41(a)(1)(A)(i). The Defendant has not served an answer or a motion for summary judgment. Plaintiff’s notice is therefore “self-effectuating and terminates the case in and of itself; no order or other action of the district court is required.” In re Amerijet Int’l, Inc., 785 F.3d 967, 973 (5th Cir. 2015), as revised (May 15, 2015). Each party shall bear its own costs, expenses, and attorney fees. All pending motions are DENIED as MOOT. The Court therefore ORDERS the Clerk of Court CLOSE this action.”
Source: PACER Docket, Case 7:25-cv-00016, Texas Western District Court

The court’s order confirms that BillSure’s Rule 41(a)(1)(A)(i) notice was self-effectuating — no judicial merits review occurred. The ‘with prejudice’ designation, chosen by the plaintiff rather than imposed by the court, is the dispositive element: it forecloses any future action by BillSure against VMware on US8005457B2. The cost neutrality order is standard for unilateral pre-answer dismissals. The absence of any answer or summary judgment motion from VMware confirms the case resolved at its earliest procedural stage.

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

US8005457B2 — Method and System for Verifying Network Resource Usage Records

Publication No.US8005457B2
Application No.US11/219030
Patent details
ProductMethod and system for verifying network resource usage records
Cited in actionJanuary 15, 2025

US8005457B2, filed under application number US11/219030, protects a method and system for verifying network resource usage records. The patent addresses the technical challenge of accurately validating usage data generated by network infrastructure — a function critical to billing integrity, service assurance, and audit compliance in telecommunications and cloud environments. The invention’s claims likely encompass processes for cross-referencing, reconciling, or authenticating usage records against network-side data sources.

For cloud infrastructure providers, telcos, and managed service operators, usage record verification sits at the intersection of billing accuracy and regulatory compliance. VMware’s virtualisation and cloud management platforms generate and process resource consumption data at scale, making them a plausible target for a patent of this scope. The patent’s continued enforceability means any vendor offering network usage metering, billing mediation, or resource accounting functionality should assess claim exposure — particularly as cloud-native architectures increasingly automate usage verification workflows.

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 US8005457B2?

Any organisation developing or deploying systems that verify, reconcile, or audit network resource usage records should consider an FTO assessment against US8005457B2. This includes cloud billing platforms, telco mediation layers, virtualisation management tools, and SaaS usage metering engines. The patent’s assertion against VMware — one of the largest virtualisation vendors globally — signals that the holder views enterprise-scale implementations as within scope.

PatSnap Eureka’s FTO Search Agent enables R&D and IP teams to map product workflows against the claim language of US8005457B2, surface prior art that may limit claim scope, and identify design-around opportunities. With the patent still active and the case history suggesting ongoing assertion intent, an early FTO review is a lower-cost alternative to reactive litigation defence.

PatSnap Eureka FTO Search

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

Run FTO in Eureka →
Related litigation

Similar patent cases: network resource verification in W.D. Texas

Related patent infringement actions asserting network resource verification and usage metering patents in the Western District of Texas and comparable venues.

🔍
Access 40+ similar cases in PatSnap Eureka
BillSure LLC patent enforcement history, Texas Western case history, BillSure LLC’s full IP portfolio, and comparable case analysis
Network billing patent casesVMware infringement actionsW.D. Texas Rule 41 dismissalsBillSure LLC litigation history
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the network resource verification IP landscape

A 75-day lifecycle with a with-prejudice exit is rarely random. Here is what it suggests for practitioners and product teams.

Pre-answer dismissals with prejudice often signal off-docket resolution

When a plaintiff dismisses with prejudice before the defendant files any responsive pleading, it typically indicates either a negotiated licence, a commercial settlement, or a credible invalidity argument surfaced in early counsel discussions. The public record here is silent, but the pattern is consistent with structured resolution rather than unilateral abandonment.

US8005457B2 is still live — FTO analysis remains relevant for cloud and telco stacks

This dismissal does not affect the patent’s validity or enforceability against any other party. Organisations operating usage metering, network billing verification, or cloud resource accounting infrastructure should treat US8005457B2 as an active risk asset and consider an FTO assessment before deploying or scaling affected systems.

🔒
Full strategic analysis in PatSnap Eureka
Unlock deeper analysis of network resource verification patent enforcement trends and W.D. Texas district court dismissal patterns.
BillSure assertion historyVMware patent exposure mapW.D. Texas dismissal trends
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

BillSure v VMware — key questions answered

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

Is your network metering stack clear of US8005457B2?

US8005457B2 remains enforceable against any party — not just VMware. PatSnap Eureka’s FTO Search Agent maps your product’s usage verification workflows against active patent claims and flags risks before they become litigation events.

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.