VirtaMove v. Google and Amazon — Software Patent Claims Invalid as Indefinite

Background

VirtaMove accused Google and Amazon of infringing patents concerning software containerization—the use of isolated computing environments to let applications run across servers and operating systems. The Google action involved U.S. Patent Nos. 7,519,814 and 7,774,762, while the Amazon action involved the ’814 patent. The cases were transferred from the Western District of Texas and related in the Northern District of California.

At an October 1 technology tutorial and claim-construction hearing, the parties asked the court to interpret several disputed claim terms. Google and Amazon argued that three terms were indefinite, meaning the patent language failed to tell a skilled reader where the claims’ boundaries lay with reasonable certainty. Because each challenged term appeared in an independent claim, an indefiniteness ruling could dispose of every asserted claim.

The Court’s Holding

Judge Noël Wise held that Google and Amazon proved indefiniteness by clear and convincing evidence. For claim 17 of the ’762 patent, the court found that “an incompatible computer platform” lacked an objective boundary. VirtaMove’s proposed construction depended on whether an application was “not intended” to execute on a platform, but the patent did not identify whose intention controlled or provide an objective way to determine it. The related phrase “the second incompatible computer platform” inherited the same defect.

For claim 1 of the ’814 patent, the court held “disparate computing environments” indefinite. The specification used “disparate” in shifting ways and did not supply a workable standard for deciding when two environments were sufficiently different. VirtaMove’s expert could not identify an objective boundary, and the company’s proposed examples did not cure that uncertainty.

Those findings invalidated claims 17–20 of the ’762 patent and claims 1–30 of the ’814 patent, including every asserted dependent claim. The court construed one additional root-file-system term but declined to reach most remaining disputes because the indefiniteness rulings were dispositive. It directed the parties to confer about next steps and set a status conference.

Key Takeaways

• A functional patent term can be indefinite when its scope turns on an unexplained subjective intention rather than an objective technical test.
• Repeated use of a relative word such as “disparate” does not establish a claim boundary if the specification uses the word inconsistently.
• When an indefinite term appears in an independent claim, the defect generally reaches dependent claims that incorporate the same limitation.
• A claim-construction order can effectively end an infringement case even before the court enters final judgment.

Why It Matters

The ruling illustrates a drafting risk for software patents that describe compatibility and computing environments through broad, relative language. Patent owners need claim terms that let engineers and competitors determine what falls inside the monopoly without relying on a litigant’s after-the-fact explanation. For accused technology companies, claim construction remains an important path to resolving a case when the patent itself supplies no objective dividing line.