Gideon Korrell Breaks Down Patent Eligibility Lessons from the Google ’637 Case

On January 22, 2026, the Federal Circuit affirmed the dismissal of a patent infringement case against Google LLC at the pleading stage. The court held that claims from U.S. Patent No. 7,679,637 were not eligible under § 101. Writing for a unanimous panel, Chief Judge Kimberly A. Moore emphasized a familiar issue in patent law: claims written in broad, functional terms without explaining how they work are likely to fail early.

As Gideon Korrell explains, the case highlights how courts continue to apply strict scrutiny to software patents, especially when they lack clear technical detail.

Understanding the ’637 Patent

The ’637 patent focused on web conferencing systems. It described technology that allows users to:

• Watch sessions live or with a delay

• Replay sessions after they end

• View different data streams (video, chat, documents) separately

• Adjust playback speeds while maintaining audio quality

While these features may seem useful, the court did not focus on usefulness. Instead, it examined whether the patent described a real technical improvement.

Alice Step One: Is It Just an Abstract Idea?

Under the Alice Corp. v. CLS Bank International framework, courts first ask whether a claim is directed to an abstract idea.

Here, the patent owner argued the claims were specific to web conferencing. However, the court found that even a narrower interpretation like “asynchronous playback” still failed. The reason was simple:

• The claims described results, not methods

• They said systems were “able to” perform tasks

• They did not explain how those tasks were achieved

Gideon Korrell often points out that this kind of language raises red flags. If a patent tells you what to do but not how to do it, courts are likely to treat it as abstract.

Why Technical Detail Matters

The court also reviewed the patent’s specification and found that:

• The components were already known

• The system relied on existing technologies

• There was no new technical mechanism described

This made it clear that the patent was applying known ideas rather than improving technology. In modern patent law, that distinction is critical.

Comparing to Other Cases

The patent owner tried to rely on Contour IP Holding LLC v. GoPro, Inc., where claims were found eligible. But the court rejected this comparison.

In Contour, the claims included:

• Specific technical steps

• A clear solution to a technical problem

In contrast, the ’637 patent only described outcomes. The court instead found it closer to Hawk Technology Systems, LLC v. Castle Retail, LLC, where abstract claims also failed.

Alice Step Two: Is There an Inventive Concept?

At Step Two, the court looked for something inventive. The patent owner argued two features mattered:

• Use of multiple client applications

• A component to maintain audio quality

The court disagreed. It found that:

• These components were standard and widely used

• The patent did not introduce any new algorithm or design

As Gideon Korrell notes, simply combining known elements is not enough. There must be a clear and unconventional technical solution.

Procedural Lessons: Early Dismissal

Another important takeaway is how quickly the case ended. The court confirmed that dismissal at the Rule 12(b)(6) stage is appropriate when:

• The patent itself shows no inventive concept

• No additional facts could change the outcome

The court also noted that claim construction was unnecessary because the patent owner failed to show how it would affect eligibility.

Key Takeaways for Patent Drafting

This case reinforces several practical lessons:

• Avoid purely functional language

• Clearly explain how the invention works

• Highlight specific technical improvements

• Be cautious about describing elements as “conventional”

For software patents in particular, detail matters more than ever.

Conclusion

The Federal Circuit’s decision in the ’637 case reflects a consistent trend in patent law. Courts are not persuaded by broad descriptions of functionality. They expect patents to show real technical innovation.

As Gideon Korrell explains, successful patents are those that connect results to concrete implementation. Without that link, even useful ideas may not survive eligibility challenges.