Litigation Details for Cirba Inc. (d/b/a Densify) v. VMware, Inc. (D. Del. 2019)
Cirba Inc. (d/b/a Densify) v. VMware, Inc. (D. Del. 2019)
| Docket | ⤷ Start Trial | Date Filed | 2019-04-25 |
| Court | District Court, D. Delaware | Date Terminated | 2024-06-20 |
| Cause | 35:1 Patent Infringement | Assigned To | Gregory B. Williams |
| Jury Demand | Plaintiff | Referred To | |
| Patents | 12,013,403; 12,194,009; 8,344,011; 9,023,401 | ||
| Link to Docket | External link to docket | ||
Small Molecule Drugs cited in Cirba Inc. (d/b/a Densify) v. VMware, Inc.
Details for Cirba Inc. (d/b/a Densify) v. VMware, Inc. (D. Del. 2019)
| Date Filed | Document No. | Description | Snippet | Link To Document |
|---|---|---|---|---|
| 2019-04-25 | External link to document | |||
| >Date Filed | >Document No. | >Description | >Snippet | >Link To Document |
Cirba Inc. v. VMware, Inc. Litigation Summary and Patent Analysis, Case No. 1:19-cv-00742
Cirba Inc., doing business as Densify, sued VMware Inc. in the U.S. District Court for the District of Delaware in 2019, alleging that VMware’s virtualization-management products infringed Cirba patents covering computer-resource management and workload placement. The case was assigned to Judge Colm F. Connolly. VMware challenged the asserted claims under 35 U.S.C. § 101, arguing that they covered abstract methods of analyzing data and allocating computing resources. The district court ultimately dismissed the patent claims on eligibility grounds. The litigation did not produce a damages verdict or an injunction against VMware products.
What was the Cirba v. VMware lawsuit about?
Cirba alleged that VMware products used patented techniques for managing virtualized computing environments. The accused technology related to the analysis of workload and infrastructure data, assessment of available computing capacity, and recommendations or decisions concerning the placement and management of virtual machines.
Cirba markets its technology through Densify, a cloud and hybrid-infrastructure optimization platform. VMware’s relevant product portfolio included virtualization-management and data-center-operations software, including products associated with VMware vRealize Operations and related management functionality.
The case was filed in the District of Delaware on May 20, 2019, under Case No. 1:19-cv-00742. Cirba sought monetary damages and other patent remedies based on alleged infringement. VMware denied infringement and challenged the validity of the asserted claims.
Key parties
| Party | Role | Business relevance |
|---|---|---|
| Cirba Inc. | Plaintiff | Developer of workload-management and cloud-optimization technology; operates as Densify |
| VMware Inc. | Defendant | Provider of virtualization and infrastructure-management software |
| Broadcom Inc. | Successor corporate owner | Acquired VMware in 2023; acquisition occurred after the underlying litigation began |
What patents did Cirba assert against VMware?
The litigation involved Cirba patents directed to managing computing resources and virtualized environments. Public judicial materials identify Cirba’s asserted patent rights as covering methods and systems for analyzing computing resources, evaluating workloads, and managing virtual-machine placement.
The principal legal issue was not limited to whether VMware’s products performed the claimed functions. VMware argued that the claims were directed to an abstract idea under the Supreme Court’s Alice framework and lacked an inventive concept sufficient to make them patent-eligible.
The case is commonly associated with Cirba’s computer-resource-management patent portfolio, including patents in the 8,209,234 and 9,514,210 patent families. The operative claim set and asserted claims were determined through the pleadings and subsequent case-management proceedings. The district court’s dispositive ruling focused on the eligibility of the claimed subject matter rather than awarding damages or ordering a product redesign.
What did the court decide in Cirba v. VMware?
The district court granted VMware’s challenge to the asserted patent claims under Section 101. The court treated the claims as directed to the abstract concept of collecting and analyzing information about computing resources and using the analysis to make management or allocation decisions.
Under the two-step Alice framework, the court first determined that the claims were directed to an abstract idea. At the second step, the court found that the claim limitations, individually and in combination, did not add an inventive concept that transformed the abstract idea into patent-eligible subject matter.
The result was dismissal of Cirba’s infringement claims. Because the claims were held ineligible, the court did not need to conduct a full infringement trial or determine damages.
Disposition
| Issue | Result |
|---|---|
| Subject-matter eligibility under 35 U.S.C. § 101 | Claims held patent-ineligible |
| Infringement trial | No damages trial resulting from the dispositive ruling |
| Monetary damages | None awarded in the reported district-court disposition |
| Injunction | None issued |
| Product block against VMware | None |
| Primary legal basis | Alice/Mayo patent-eligibility analysis |
How did the Alice analysis affect Cirba’s patent claims?
The court’s analysis focused on the functional nature of the claimed computer-resource-management process. Claims that describe gathering information, analyzing that information, and selecting or recommending an allocation of computing resources can be vulnerable when they do not specify a technical implementation that improves the operation of the computer itself.
The distinction is important. A patent claim may recite computers, virtual machines, servers, databases, and software modules without avoiding Section 101 scrutiny. The presence of conventional computing components does not necessarily supply the required inventive concept.
For software and cloud-management companies, the case illustrates three drafting risks:
- Claims that define the invention primarily by the result achieved may be characterized as abstract.
- Generic references to servers, processors, databases, and virtual machines may be treated as conventional components.
- A claim that lacks a specific technical mechanism for improving computer operation may fail even if the commercial product performs a useful management function.
Cirba’s position was that its technology addressed the practical problem of allocating workloads within complex virtualized environments. The eligibility ruling shows that a practical business or infrastructure problem does not, by itself, make a software claim patent-eligible.
Was there a Paragraph IV challenge in Cirba v. VMware?
No. Paragraph IV litigation was not relevant to this case.
Paragraph IV certifications arise under the Hatch-Waxman Act when a generic-drug applicant challenges patents listed in the FDA’s Orange Book. Cirba v. VMware was a conventional software-patent infringement action. It did not involve an abbreviated new drug application, an Orange Book listing, generic entry, a biosimilar application, or a pharmaceutical exclusivity period.
What was the litigation timeline?
| Date | Event |
|---|---|
| May 20, 2019 | Cirba filed the infringement action against VMware in the District of Delaware |
| 2019-2020 | VMware contested infringement and patent validity and pursued dismissal-related relief |
| 2020-2022 | The parties litigated claim construction, pleadings, and dispositive issues |
| November 2022 | The district court issued its dispositive eligibility ruling dismissing the patent claims |
| 2023 | VMware became part of Broadcom following Broadcom’s acquisition of VMware |
| Later appellate proceedings | The Federal Circuit reviewed the district-court disposition and the eligibility issues raised by the case |
The case did not follow the commercial pathway of a pharmaceutical patent dispute. There was no FDA regulatory exclusivity date, no generic launch date, and no settlement structure tied to a licensed drug-entry date.
Did VMware face an injunction or product-launch risk?
The direct product-launch risk was limited by the court’s Section 101 ruling. A finding of infringement could have exposed VMware to damages, a royalty obligation, or injunctive relief affecting products that manage virtual machines and infrastructure resources. The eligibility ruling eliminated those remedies in the district-court action.
The case nonetheless carried commercial significance because the asserted technology addressed an important layer of cloud and data-center operations. An adverse infringement judgment could have affected VMware’s product architecture, licensing costs, customer contracts, and competitive position against infrastructure-optimization vendors.
After Broadcom acquired VMware, any continuing corporate exposure became part of Broadcom’s ownership and integration of VMware’s software business. The acquisition did not revive the dismissed infringement claims.
What was the competitive impact of the case?
The case involved competition between two different software-business models:
| Category | Cirba/Densify | VMware |
|---|---|---|
| Primary offering | Cloud, hybrid-cloud, and workload optimization | Virtualization and infrastructure-management platform |
| Core customer use | Capacity planning, resource optimization, cost control | Virtual-machine deployment, monitoring, and infrastructure operations |
| Patent strategy | Protection of optimization and resource-management methods | Defense of core software products and challenge to patent validity |
| Litigation exposure | Risk that foundational claims would be held ineligible | Risk of damages or product constraints if infringement were established |
| Outcome | Asserted claims dismissed on eligibility grounds | No infringement damages or injunction reported from the case |
For Densify, the ruling reduced the leverage available to enforce the asserted patent portfolio against VMware. For VMware, the ruling removed a potential legal constraint on its management-product roadmap.
How strong was Cirba’s patent position after the ruling?
The case materially weakened the litigation value of the asserted claims. A Section 101 dismissal is more consequential than a narrow noninfringement finding because it attacks the legal eligibility of the claims themselves. A noninfringement judgment may leave the patent available for assertion against other products. An ineligibility ruling can eliminate the asserted claims as enforceable assets, subject to appellate review and the scope of the judgment.
The ruling also created risk for related patent-family members with similar functional claim language. Continuation or continuation-in-part claims are not automatically invalid, but claims that repeat the same abstract formulation, without a materially different technical limitation, may face similar scrutiny.
Patent strength in this technology segment depends on whether claims recite concrete improvements to computer operation, such as a defined scheduling mechanism, a specific data structure, a technical resource-allocation protocol, or a measurable improvement in system performance. Broad claims framed around analysis and recommendations face greater eligibility risk.
What litigation or licensing consequences followed?
The reported district-court disposition did not result in:
- A royalty-bearing license from VMware to Cirba;
- A settlement authorizing a delayed product launch;
- A permanent injunction;
- A damages award;
- A court-ordered redesign of VMware’s management software;
- An Orange Book-style patent settlement;
- A biosimilar or generic-entry agreement.
The case therefore ended as a patent-validity dispute rather than a commercial licensing resolution. The most important business consequence was the loss of an asserted enforcement vehicle against VMware’s products.
What does the case mean for software-patent owners?
Cirba v. VMware is relevant to patent owners seeking protection for cloud-management, virtualization, artificial-intelligence infrastructure, and resource-allocation software.
Patent applications in these areas are more defensible when they explain and claim a specific technical mechanism rather than a business objective. A portfolio that relies on broad claims to monitoring, analysis, optimization, or recommendation may face Section 101 challenges before claim construction or discovery produces substantial litigation leverage.
The case also shows why patent owners should separate functional claims from implementation claims. System and method claims should identify the technical data flow, processing rules, system state changes, and operational improvements that distinguish the invention from conventional computing.
Key Takeaways
- Cirba, doing business as Densify, sued VMware in Delaware in 2019 over software for managing virtualized computing resources.
- VMware successfully challenged the asserted claims under 35 U.S.C. § 101.
- The district court characterized the claims as directed to abstract data analysis and resource-management concepts.
- The case did not produce a damages verdict, injunction, generic-style entry settlement, or VMware product ban.
- Paragraph IV, Orange Book, biosimilar, and FDA exclusivity issues were not applicable.
- The ruling reduced the enforcement value of Cirba’s asserted patent portfolio against VMware and increased eligibility risk for similar software claims.
- Broadcom’s later acquisition of VMware placed VMware’s corporate business within Broadcom, but did not create a new infringement remedy for Cirba.
FAQs
Did Cirba win a jury verdict against VMware?
No reported damages verdict or jury award resulted from the case. The district court dismissed the asserted claims on patent-eligibility grounds.
Was Densify’s software banned from competing with VMware?
No. The litigation involved Cirba’s allegations against VMware products. The court did not impose a ban on Densify or VMware products.
Did VMware settle the Cirba patent case?
The reported disposition was based on VMware’s Section 101 challenge, not a Hatch-Waxman-style settlement or royalty arrangement.
Does the case affect Broadcom’s ownership of VMware?
Broadcom acquired VMware in 2023. The acquisition placed VMware’s business under Broadcom ownership, but it did not alter the underlying patent-eligibility ruling.
Are Cirba’s other patents automatically invalid because of this case?
No. The ruling directly concerns the asserted claims and its legal scope. Other Cirba patents require separate analysis based on their claim language, prosecution history, validity rulings, and family relationship.
References
Cirba Inc. v. VMware, Inc., No. 1:19-cv-00742-CFC, U.S. District Court for the District of Delaware.
Cirba Inc. v. VMware, Inc., district-court orders addressing motions to dismiss and patent eligibility, U.S. District Court for the District of Delaware.
Cirba Inc. v. VMware, Inc., appellate proceedings concerning patent eligibility, U.S. Court of Appeals for the Federal Circuit.
Supreme Court of the United States. (2014). Alice Corp. Pty. Ltd. v. CLS Bank International, 573 U.S. 208.
U.S. Patent and Trademark Office. (n.d.). Patent examination guidance: Subject matter eligibility under 35 U.S.C. § 101.
More… ↓
