Virtamove v. Oracle: Container Patent Suit Transferred to Austin After 286 Days
Virtamove, Corp. asserted two container virtualisation patents — US7784058B2 and US7519814B2 — against Oracle’s Cloud Infrastructure and Kubernetes Engine products in the Western District of Texas. After 286 days before Judge Alan Albright, the case was transferred intradistrict to the Austin division and assigned a new docket number.
Container virtualisation patents drive Virtamove’s cloud enforcement push against Oracle
Virtamove, Corp. filed suit against Oracle in the Waco division of the Western District of Texas on 20 December 2024, asserting infringement of US7784058B2 and US7519814B2 — two patents covering container-based application virtualisation and secure OS-level isolation techniques. The accused products are Oracle Cloud Infrastructure (OCI) and Oracle Kubernetes Engine (OKE), placing this case squarely within the fast-moving cloud-native and container orchestration IP landscape.
Rather than a merits dismissal or settlement, this case concluded its initial chapter through an intradistrict transfer. On 2 October 2025 — 286 days after filing — the Waco docket was closed and the matter reassigned to the Austin division of the same court under docket number 1:25-CV-1601. A transfer of this kind does not resolve the underlying claims; it relocates jurisdiction within the same district, typically reflecting caseload management or venue considerations specific to the Austin bench.
The 286-day period elapsed before transfer suggests that preliminary motion practice and scheduling were likely underway before reassignment. The public record does not disclose whether either party moved for transfer or whether the court acted sua sponte. With Judge Alan Albright presiding in Waco and the case now before a different Austin judge, the transition may affect claim construction scheduling and overall litigation pace — details that practitioners monitoring this dispute will need to track on the new docket.
Filing to Case Transferred in 286 days
286 days before intradistrict transfer to Austin — case continues under new docket 1:25-CV-1601
Intradistrict transfer to Austin: what changes and what does not
What an intradistrict transfer actually means
An intradistrict transfer moves a case between divisions of the same federal district court — here from Waco to Austin within the Western District of Texas. Jurisdiction, applicable law, and substantive claims remain unchanged. The transferring judge’s prior orders typically carry forward, but a new judge assumes control of future proceedings. No merits ruling has been made; the case is simply repositioned within the same court structure.
No merits adjudicationAustin division brings a different judicial environment
The Waco division under Judge Alan Albright has historically been one of the busiest patent dockets in the US, known for aggressive scheduling and reluctance to grant stays pending IPR. The Austin division operates under different judges with distinct scheduling practices. This shift may alter the pace of claim construction, discovery timelines, and the likelihood of early dispositive motion rulings. Parties should audit all prior scheduling orders against the Austin court’s standard practices.
Scheduling dynamics shiftLitigation continues on new docket 1:25-CV-1601
The case proceeds in the Austin division under docket number 1:25-CV-1601. Both parties retain their existing claims and defences — Oracle’s invalidity and non-infringement positions, and Virtamove’s infringement assertions against OCI and OKE, all carry over. A new scheduling conference before the Austin judge is typically expected, and parties may seek to re-negotiate deadlines. Practitioners should monitor the Austin docket for Markman hearing dates and any IPR filings.
Active — monitor Austin docketContainer and cloud IP enforcement risk remains live for Oracle
The transfer does not reduce Oracle’s exposure under the asserted patents. US7784058B2 and US7519814B2 cover foundational container virtualisation techniques directly implicated by OCI and OKE architectures. Cloud infrastructure competitors operating similar container orchestration stacks should treat this case as a live signal: Virtamove’s enforcement posture appears robust, and the Austin transfer suggests continued litigation rather than settlement proximity.
Enforcement risk continuesFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Virtamove, Corp. | Company | Container virtualisation IP licensing entity — holder of US7784058B2 and US7519814B2Search in Eureka ↗ |
| Defendant | Oracle | Individual | Oracle Corporation — provider of Oracle Cloud Infrastructure (OCI) and Kubernetes Engine (OKE)Search in Eureka ↗ |
| Plaintiff counsel | Amy Hayden | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Christian W. Conkle | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Daniel B. Kolko | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jacob R. Buczko | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | James Milkey | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | James S. Tsuei | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jefferson Cummings | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jonathan Ma | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Linjun Xu | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Mackenzie Paladino | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Marc A. Fenster | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Neil A. Rubin | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Qi (Peter) Tong | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Reza Mirzaie | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff law firm | BC Law Group, PC | Law Firm | Representing Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Russ August Kabat LLP | Law Firm | Representing Virtamove, Corp.Search in Eureka ↗ |
| Defendant counsel | Bas de Blank | Attorney | Counsel for OracleSearch in Eureka ↗ |
| Defendant counsel | Darryl Adams | Attorney | Counsel for OracleSearch in Eureka ↗ |
| Defendant counsel | Diana Rutowski | Attorney | Counsel for OracleSearch in Eureka ↗ |
| Defendant counsel | Jared Bobrow | Attorney | Counsel for OracleSearch in Eureka ↗ |
| Defendant counsel | Parth Sagdeo | Attorney | Counsel for OracleSearch in Eureka ↗ |
| Defendant counsel | Shane D. Anderson | Attorney | Counsel for OracleSearch in Eureka ↗ |
| Defendant law firm | Orrick Herrington & Sutcliffe LLP | Law Firm | Representing OracleSearch in Eureka ↗ |
| Defendant law firm | Slayden Grubert Beard PLLC | Law Firm | Representing OracleSearch in Eureka ↗ |
| Presiding judge | Judge Alan D Albright | Judge | Texas Western District CourtSearch in Eureka ↗ |
Official order — verbatim text
The transfer order — assigning docket number 1:25-CV-1601 in the Austin division — is a purely procedural disposition. It signals no view on the merits of Virtamove’s infringement claims or Oracle’s defences. The phrasing ‘Intradistrict Transfer’ confirms that subject-matter jurisdiction, venue, and substantive claims are preserved in full. Practitioners should note that any claim construction orders or scheduling agreements reached under Judge Albright in Waco will need to be confirmed or reset by the receiving Austin judge.
US7784058B2 & US7519814B2 — Container Virtualisation and OS-Level Isolation
US7784058B2 (application no. 10/946536) and US7519814B2 (application no. 10/939903) are both US utility patents covering container-based application virtualisation and OS-level isolation techniques — foundational methods that underpin modern containerised cloud infrastructure. Both applications were filed in the mid-2000s, predating the widespread commercial adoption of Kubernetes and Docker, giving the claims potentially broad reach over contemporary container runtime implementations used in cloud platforms.
The strategic significance of these patents lies in their timing and scope: mid-2000s priority dates combined with claims directed to OS-level container isolation place them squarely over the technical approaches used in products like Oracle Kubernetes Engine. For the cloud infrastructure sector, these patents represent a credible enforcement risk against any vendor offering managed container services, serverless compute, or PaaS environments that depend on namespace-based workload isolation — a near-universal architectural pattern in 2024-era cloud platforms.
Should you run an FTO against US7784058B2 and US7519814B2?
Any company deploying Kubernetes-native services, managed container platforms, or OS-level virtualisation in a multi-tenant cloud environment should treat these two Virtamove patents as priority FTO targets. The asserted claims — covering container-based application virtualisation and secure process isolation — map directly to architectural patterns used across AWS EKS, Google GKE, Azure AKS, and equivalent managed container offerings, not only Oracle’s OCI and OKE products.
PatSnap Eureka’s FTO Search Agent enables R&D and IP teams to map US7784058B2 and US7519814B2 claim elements against your specific container runtime stack, identify prior art that may support invalidity arguments, and surface related Virtamove portfolio patents that could represent additional exposure. Running this analysis now — before the Austin docket produces claim construction orders — positions your team to inform design-around decisions before the claim scope is judicially fixed.
Run a freedom-to-operate analysis on US7784058B2 to assess your product’s exposure
Run FTO in Eureka →Similar Container & Cloud Infrastructure Patent Cases in TXWD
Cases asserting container virtualisation and cloud infrastructure patents in the Western District of Texas, including comparable enforcement actions against major cloud vendors.
What this case signals for the cloud infrastructure IP landscape
Virtamove’s assertion against Oracle’s container stack reflects a broader enforcement wave targeting foundational virtualisation IP in cloud-native platforms.
Container orchestration patents are active enforcement vectors in 2024–25
This case confirms that legacy container and OS-level virtualisation patents — filed in the mid-2000s — remain enforceable against modern Kubernetes and cloud infrastructure stacks. Companies deploying OCI-equivalent architectures should audit their container runtime and namespace isolation implementations against the US7784058B2 and US7519814B2 claim sets.
Intradistrict transfers shift judicial dynamics without ending risk
Moving from Waco to Austin within TXWD changes the presiding judge and scheduling environment but preserves all claims intact. Oracle’s legal team must adapt to Austin’s distinct procedural norms while Virtamove’s enforcement momentum continues. Neither party gains a substantive advantage from the transfer itself — the merits battle is simply relocated.
Virtamove v Oracle — key questions answered
Virtamove, Corp. filed a patent infringement action against Oracle in the Waco division of the Western District of Texas on 20 December 2024, asserting US7784058B2 and US7519814B2 against Oracle Cloud Infrastructure and Oracle Kubernetes Engine. On 2 October 2025, after 286 days, the case was transferred intradistrict to the Austin division and assigned new docket number 1:25-CV-1601. No merits ruling was issued.
Virtamove asserted two US patents: US7784058B2 (application no. 10/946536) and US7519814B2 (application no. 10/939903). Both cover container-based application virtualisation and OS-level process isolation techniques — foundational methods directly implicated by Oracle Cloud Infrastructure (OCI) and Oracle Kubernetes Engine (OKE).
The intradistrict transfer moves the case from the Waco division (before Judge Alan Albright) to the Austin division of the same court, under new docket 1:25-CV-1601. All substantive claims, defences, and prior filings remain intact. The transfer is procedural — it does not resolve the infringement dispute — but it changes the presiding judge and may affect scheduling, claim construction timing, and IPR coordination strategies.
Virtamove’s complaint identifies Oracle Cloud Infrastructure (OCI) and Oracle Kubernetes Engine (OKE) as the accused products. These are Oracle’s primary cloud compute and managed container orchestration offerings, both of which rely on OS-level virtualisation and namespace-based container isolation — the technical approaches covered by the asserted Virtamove patents.
The intradistrict transfer itself does not reset the one-year IPR filing bar under 35 U.S.C. § 315(b), which runs from the date the complaint was served — not from any procedural transfer. However, a new scheduling order from the Austin judge may affect the pace of district court proceedings and thus the strategic calculus for filing IPR petitions against US7784058B2 and US7519814B2. Practitioners should verify the exact complaint service date immediately.
PatSnap Eureka searches patents and litigation data to answer instantly.