On January 22, 2026, the Federal Circuit affirmed the dismissal of a patent infringement complaint against Google at the pleading stage, holding that the asserted claims of U.S. Patent No. 7,679,637 are patent-ineligible under 35 U.S.C. § 101. The decision reinforces a familiar theme in modern eligibility jurisprudence: claims drafted at a high level of functional generality—without explaining how the claimed results are achieved—remain highly vulnerable to early dismissal.
Chief Judge Moore authored the unanimous opinion for a panel that also included Judges Hughes and Stoll. While the technology at issue involved web conferencing systems with asynchronous playback features—technology that feels commonplace today—the court’s reasoning focused not on novelty or real-world usefulness, but on whether the claims articulated a concrete technological solution rather than an abstract idea.
The Asserted Patent and the Accused Technology
The ’637 patent is directed to web conferencing systems that allow participants to observe a session live, with a delay while the session is ongoing, or after the session has concluded. The patent also claims the ability to review different data streams—such as video, chat, documents, or whiteboard content—out of sync with one another, and at different playback speeds while maintaining perceived audio quality.
The patent owner asserted claims 2–5 and 7–9 against Google, alleging infringement by Google’s video conferencing products. Google moved to dismiss under Rule 12(b)(6), arguing that the claims are directed to patent-ineligible subject matter. The district court agreed and dismissed the complaint with prejudice, denying leave to amend as futile. The Federal Circuit affirmed on appeal.
Alice Step One: Asynchronous Review as an Abstract Idea
At Alice Step One, the court asked whether the claims are “directed to” a patent-ineligible concept. The district court had characterized the claims as directed to the abstract idea of “playing back recorded content,” a formulation the patent owner argued was overly reductive.
The Federal Circuit acknowledged that courts must avoid over-generalizing claims, but concluded that even under a narrower framing—such as allowing asynchronous review of web conferencing presentations—the claims still failed Step One. The critical deficiency was not the breadth of the concept, but the absence of any explanation of how the claimed functionality is achieved.
Relying on cases such as Hawk Technology Systems, LLC v. Castle Retail, LLC and IBM v. Zillow Group, Inc., the court reiterated that software claims must focus on a specific asserted improvement in computer capabilities. Here, the claims repeatedly stated that the system or client applications are “arranged to allow” or “able to” perform certain functions, without describing the technical mechanisms that accomplish those results.
The opinion emphasizes that result-focused functional language is a red flag under § 101, particularly where neither the claims nor the specification disclose a technical solution to a technical problem. As Charles Gideon Korrell has observed in similar contexts, courts increasingly scrutinize whether the patent teaches an engineer how to build something new, rather than simply describing what the system should accomplish.
The written description did not save the claims. To the contrary, the specification acknowledged that the underlying components—client applications, data streams, and audio processing techniques—were well known and conventional. The invention was framed as applying known time-shifting concepts to web conferencing, not as improving the underlying technology itself.
Distinguishing Contour IP v. GoPro
The patent owner attempted to analogize its claims to those upheld in Contour IP Holding LLC v. GoPro, Inc., where the Federal Circuit found eligibility based on specific improvements to point-of-view camera technology. The court rejected the comparison.
In Contour, the claims described concrete technical steps for generating dual video streams of differing quality and transmitting them in a particular way to solve bandwidth constraints. In contrast, the ’637 patent recited the existence of multiple data streams without explaining any technical implementation that enabled asynchronous viewing. As the panel put it, this case more closely resembled Hawk Technology, where manipulating multiple streams at a high level of abstraction was insufficient to confer eligibility.
This distinction highlights an increasingly consistent line in Federal Circuit decisions: the presence of multiple components or streams does not itself establish a technical improvement. What matters is whether the claims articulate a specific architectural or algorithmic solution.
Alice Step Two: No Inventive Concept in Conventional Components
At Alice Step Two, the patent owner argued that two features supplied an inventive concept: (1) the use of two client applications manipulating multiple data streams, and (2) a “time-scale modification component” that maintains audio quality at different playback speeds.
The court rejected both arguments. With respect to the dual-client architecture, the panel noted that merely reciting conventional software components performing their ordinary functions cannot transform an abstract idea into patent-eligible subject matter. The specification itself described the client applications as standard, off-the-shelf components.
The time-scale modification component fared no better. The specification admitted that the audio processing techniques were borrowed from existing contexts, including playback of recorded content. Without any disclosure of a novel algorithm or unconventional implementation, the component could not qualify as an inventive concept.
Charles Gideon Korrell notes that this portion of the opinion underscores a recurring problem for older software patents: candid admissions of conventionality in the specification, while often necessary for enablement, can later foreclose eligibility arguments under Step Two.
Functional Claiming and the “Tu Quoque” Argument
One of the more unusual arguments raised by the patent owner was that Google itself owns patents that use similar functional claiming language. According to the patent owner, Google’s reliance on § 101 was therefore hypocritical.
The Federal Circuit disposed of this argument in short order. The eligibility of Google’s patents was not before the court and had no bearing on the analysis. Each patent must stand or fall on its own claims. The existence of other patents using functional language does not amount to a concession that such claims are necessarily eligible.
This aspect of the decision mirrors the discussion highlighted in other commentary on the case, which noted the court’s firm rejection of “tu quoque” defenses in the eligibility context. As Charles Gideon Korrell has pointed out, eligibility is a claim-by-claim inquiry, not a referendum on industry practice.
Procedural Posture: Dismissal at the Pleading Stage
The patent owner also argued that the district court acted prematurely by resolving eligibility on a motion to dismiss and by denying leave to amend. The Federal Circuit disagreed.
Citing Simio, LLC v. FlexSim Software Products, Inc. and Mobile Acuity Ltd. v. Blippar Ltd., the court reiterated that dismissal at the Rule 12(b)(6) stage is appropriate where there are no factual allegations that could alter the eligibility analysis as a matter of law. Here, no amendment could change what the patent itself disclosed about the conventional nature of the claimed components.
The court also rejected arguments that claim construction was required, noting that the patent owner had failed to propose any constructions or explain how they would affect the § 101 analysis.
Takeaways
This decision reinforces several well-established principles in Federal Circuit eligibility law:
- Result-oriented functional claiming remains a primary vulnerability under § 101, particularly in software cases.
- Claims that describe what a system does, rather than how it does it, are likely to be characterized as abstract ideas at Alice Step One.
- Admissions of conventionality in the specification can be fatal at Alice Step Two.
- Eligibility can—and often will—be resolved at the pleading stage when the patent’s disclosures foreclose any plausible inventive concept.
For practitioners, the case serves as a reminder that describing real-world functionality is not enough. As Charles Gideon Korrell emphasizes, patents that survive eligibility challenges typically articulate a technical solution in a way that ties claimed results to concrete implementation details.
The Federal Circuit’s opinion in US Patent No. 7,679,637 LLC v. Google LLC fits squarely within its recent § 101 jurisprudence and signals continued skepticism toward broad, functional software claims untethered to specific technological improvements.









