Cloud Systems HoldCo IP v. Phillips North America: Dismissed With Prejudice
Cloud Systems HoldCo IP, LLC asserted US8533326B2 — a patent covering device management, routing, and inter-device connection control — against Phillips North America, LLC in the Western District of Texas. The plaintiff voluntarily dismissed all claims with prejudice after 194 days, before the defendant filed any answer or dispositive motion.
A pre-answer dismissal with prejudice in a Texas device-management patent suit
On November 22, 2023, Cloud Systems HoldCo IP, LLC — a patent assertion entity holding US8533326B2 — filed suit against Phillips North America, LLC in the Western District of Texas, alleging infringement of a patent covering methods for managing, routing, and controlling networked devices and their inter-device connections. The case was assigned case number 7:23-cv-00186 and proceeded before the court for just under seven months.
On May 31, 2024, before Phillips North America served an answer or a motion for summary judgment, Cloud Systems filed a Notice of Voluntary Dismissal With Prejudice under Federal Rule of Civil Procedure 41(a)(1)(A)(i). Because the defendant had not yet responded, the notice was self-effectuating under Fifth Circuit precedent — no court order was required to terminate the case. The court subsequently ordered the clerk to close the action, denied all pending motions as moot, and directed each party to bear its own costs, expenses, and attorney fees.
The 194-day timeline and pre-answer exit suggest the dismissal likely followed either a licensing resolution or a strategic reassessment by plaintiff’s counsel — though the public record is silent on any settlement terms. The with-prejudice designation is significant: Cloud Systems cannot refile the same claims against Phillips North America on this patent. The absence of any fee-shifting order is consistent with the early procedural posture, as an exceptional-case finding under 35 U.S.C. § 285 would have required merits engagement that never occurred.
Filing to Voluntary dismissal in 194 days
194 days — resolved well before the typical 2–3 year district court trial cycle
Dismissed with prejudice: what Rule 41(a)(1)(A)(i) means for both parties
Rule 41(a)(1)(A)(i): self-effectuating, no court order needed
Because Phillips North America had not yet served an answer or a motion for summary judgment, Cloud Systems could invoke Rule 41(a)(1)(A)(i) unilaterally. Under Fifth Circuit authority cited by the court, such a notice is self-effectuating — it terminates the case automatically upon filing. The with-prejudice designation is plaintiff-elected and forecloses any refiling of these specific claims against this defendant.
Rule 41(a)(1)(A)(i) — pre-answer exitWith prejudice bars Cloud Systems from refiling these claims
A dismissal with prejudice operates as a final adjudication on the merits for the dismissed claims, permanently barring the plaintiff from asserting the same causes of action against the same defendant. This distinguishes it from a without-prejudice dismissal, which would preserve the option to refile. Here, Cloud Systems elected the stronger finality designation — which typically signals either a negotiated resolution or a decision that further litigation against this defendant is not commercially viable.
Permanent bar — cannot refile against Phillips NAPhillips North America exits without admissions and bearing own costs
Phillips North America never filed an answer, meaning it made no admissions, no invalidity contentions entered the record, and no claim construction occurred. The court’s own-costs order means neither party can pursue attorney fee recovery in connection with this action. The with-prejudice dismissal gives Phillips a permanent shield against re-assertion of these specific patent claims by this plaintiff, though other licensees or assignees of US8533326B2 are not bound.
No admissions — clean exit for defendantPatent remains enforceable; assertion risk persists for the broader sector
US8533326B2 was not invalidated and its claims were never construed. The patent remains in force and Cloud Systems — or any future assignee — retains the ability to assert it against other companies in the device management, IoT connectivity, and network routing space. Companies with products that manage or route inter-device connections should monitor this patent’s litigation history and consider freedom-to-operate analysis, particularly given the Western District of Texas’s continued role as a patent litigation venue.
Patent survives — sector exposure remainsFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Cloud Systems HoldCo IP, LLC | Company | Patent assertion entity — holder of US8533326B2 covering device management and routing methodsSearch in Eureka ↗ |
| Defendant | Phillips North America, LLC | Company | Phillips North America, LLC — defendant in device-management patent infringement actionSearch in Eureka ↗ |
| Plaintiff counsel | Jeffrey Eugene Kubiak | Attorney | Counsel for Cloud Systems HoldCo IP, LLCSearch in Eureka ↗ |
| Plaintiff counsel | William P. Ramey , III | Attorney | Counsel for Cloud Systems HoldCo IP, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Ramey LLP | Law Firm | Representing Cloud Systems HoldCo IP, LLCSearch in Eureka ↗ |
| Defendant counsel | Jeremy P. Oczek | Attorney | Counsel for Phillips North America, LLCSearch in Eureka ↗ |
| Defendant counsel | Stacey V. Reese | Attorney | Counsel for Phillips North America, LLCSearch in Eureka ↗ |
| Defendant law firm | Bond, Schoeneck & King, PLLC | Law Firm | Representing Phillips North America, LLCSearch in Eureka ↗ |
| Defendant law firm | Stacey V. Reese Law PLLC | Law Firm | Representing Phillips North America, LLCSearch in Eureka ↗ |
| Presiding judge | Judge N/A | Judge | Texas Western District CourtSearch in Eureka ↗ |
Official order — verbatim text
The court’s order confirms the dismissal was self-effectuating under Rule 41(a)(1)(A)(i) — it required no judicial merits determination. The with-prejudice designation, elected by the plaintiff, extinguishes Cloud Systems’ right to refile these specific claims against Phillips North America. Critically, no claim construction, invalidity analysis, or infringement ruling was issued, leaving US8533326B2’s enforceability fully intact against third parties. The own-costs directive forecloses any attorney-fee recovery for either side in connection with this action.
US8533326B2 — Device management, routing, and inter-device connection control
US8533326B2 (application number US11/744095) covers methods for managing, routing, and controlling devices along with the connections between them — a technical domain that intersects IoT device orchestration, network management, and inter-device communication protocols. Patents in this space often claim priority to mid-2000s filing windows, predating the commercial IoT explosion but potentially broad enough to read on contemporary device management implementations. The patent’s exact claim scope was never construed in this proceeding.
The strategic value of this patent lies in its potential applicability across a wide range of networked device products — from industrial control systems and smart building infrastructure to consumer IoT platforms and enterprise device management software. Patent assertion entities holding broad method claims in device routing and management have historically targeted companies commercialising connected-device ecosystems. US8533326B2 has not been invalidated and remains a live enforcement asset, making it relevant to any company whose products involve programmatic device management or inter-device communication routing.
Should your team run an FTO against US8533326B2?
Any company developing or commercialising products that manage, route, or control networked devices — including IoT platforms, smart building systems, industrial automation, enterprise device management solutions, or connected hardware ecosystems — should treat US8533326B2 as a live risk. The patent was asserted in federal litigation and was not invalidated or limited by any court ruling. Its claim scope remains untested in public proceedings, which means the boundaries of infringement exposure are unresolved.
PatSnap Eureka’s FTO Search Agent can map the claim language of US8533326B2 against your product’s technical architecture, identify prior art that could support an invalidity argument, surface any related family members or continuation applications, and flag Cloud Systems HoldCo IP’s broader assertion history. Running a structured FTO before product launch or market expansion in the device management space is a cost-effective way to quantify and manage this specific patent risk.
Run a freedom-to-operate analysis on US8533326B2 to assess your product’s exposure
Run FTO in Eureka →Similar patent cases: device management and routing IP in Texas federal courts
Cases involving device management and inter-device communication patents litigated in the Western District of Texas, including pre-answer dismissal and assertion entity patterns.
What this case signals for the device management and IoT IP landscape
A pre-answer dismissal with prejudice in Texas typically reflects strategic calculation — and leaves the underlying patent fully enforceable against others.
Pre-answer exits often mask licensing activity — monitor downstream filings
Voluntary dismissals filed before any substantive court engagement are frequently consistent with confidential licensing or settlement discussions. The public record here is silent on terms. Companies in adjacent product spaces should track Cloud Systems HoldCo IP’s filing activity and any assignment changes to US8533326B2 as signals of continued assertion strategy.
US8533326B2 remains in force — no invalidity record created
Because Phillips never filed an answer or IPR petition, no invalidity arguments entered the public record. The patent’s claim scope was never tested by a court or the PTAB in this proceeding. For companies in device management and inter-device routing, that means full litigation risk persists. An FTO analysis against US8533326B2 is prudent before product launches in this space.
Cloud v Phillips — key questions answered
Cloud Systems HoldCo IP, LLC filed a patent infringement suit against Phillips North America, LLC in the Western District of Texas asserting US8533326B2. After 194 days, and before Phillips filed any answer or dispositive motion, Cloud Systems voluntarily dismissed the case with prejudice under Rule 41(a)(1)(A)(i). The court ordered each party to bear its own costs.
A dismissal with prejudice permanently bars Cloud Systems from refiling the same claims against Phillips North America based on US8533326B2. It operates as a final adjudication on the merits for the dismissed action. However, Cloud Systems retains the right to assert the patent against other defendants, as the dismissal binds only the parties to this action.
No. The case was dismissed before any answer was filed, meaning no invalidity contentions, claim construction, or merits rulings were issued. US8533326B2 remains in force and enforceable against third parties. The dismissal has no bearing on the patent’s validity.
The public record does not disclose the reason. Pre-answer dismissals with prejudice are frequently consistent with a confidential licensing agreement, a strategic decision that litigation was not commercially viable, or a negotiated resolution. The with-prejudice designation suggests finality was part of any arrangement, but no terms are publicly available.
The Western District of Texas is one of the most active patent litigation venues in the United States and is frequently chosen by patent assertion entities. The court’s familiarity with patent cases and its scheduling practices make it a common filing choice for entities like Cloud Systems HoldCo IP, particularly when using Ramey LLP, a firm with substantial docket presence in that district.
PatSnap Eureka searches patents and litigation data to answer instantly.