Gideon Korrell on 6 Takeaways from the Google Patent Decision

Patent eligibility continues to be one of the most discussed topics in intellectual property law, especially when software inventions are involved. A recent decision from the United States Court of Appeals for the Federal Circuit shows how courts are still carefully reviewing software patents under Section 101 of the Patent Act.

On January 22, 2026, the Federal Circuit upheld the dismissal of a patent infringement lawsuit against Google involving U.S. Patent No. 7,679,637. The court found that the patent claims were not eligible for patent protection because they described desired results without clearly explaining the technology used to achieve them.

The decision provides important lessons for inventors, businesses, patent owners, and legal professionals. Gideon Korrell believes the ruling highlights several key points about patent drafting, software innovation, and the challenges of meeting patent eligibility requirements under the Alice framework.

Understanding the Case

The patent in this case covered web conferencing technology. It described systems that allowed users to join live sessions, watch presentations with a delay, and play back different types of content such as video, audio, chat messages, documents, and whiteboard information—at different speeds.

The patent owner claimed that Google's video conferencing products infringed the patent. Google responded by arguing that the patent claims were not eligible for protection under Section 101 because they were based on abstract ideas.

Both the district court and the Federal Circuit agreed with Google. As a result, the case was dismissed before moving forward to later stages of litigation.

Takeaway 1: Functional Claiming Still Creates Problems

One of the biggest lessons from this decision is that functional claiming can still create serious challenges.

The court focused on claim language that described what the system could do rather than explaining how it worked. The claims repeatedly used phrases such as "arranged to allow" or "able to" perform certain functions.

According to Gideon Korrell, courts are paying closer attention to whether a patent explains the technology behind an invention. Simply stating what a system is supposed to accomplish may not be enough. If claims focus only on results, courts may view them as abstract ideas instead of true technological inventions.

For patent applicants, this means it is important to explain the technical details of an invention and not just the outcome it produces.

Takeaway 2: Courts Look for Specific Technical Solutions

The Federal Circuit made it clear that software patents should describe specific technical improvements.

The court was not convinced by the patent's discussion of asynchronous playback and multiple data streams because the claims did not explain the technical methods used to provide those features.

This issue has become increasingly important in software patent cases. Courts often ask whether an invention improves computer technology itself or simply uses existing technology to perform a task.

Gideon Korrell notes that patents are generally stronger when they identify a specific technical problem and clearly explain how that problem is solved. The more detailed the technical explanation, the better the chances of surviving a patent eligibility challenge.

Takeaway 3: Multiple Components Are Not Enough

The patent owner argued that the invention involved several data streams and client applications working together. However, the court said that simply having multiple components does not automatically make a patent eligible.

The judges explained that a patent must show how those components work together in a new and innovative way. Simply listing different parts of a system is not enough to prove a technological improvement.

The court compared this case to earlier software patent decisions and found that the claimed system did not include enough technical detail.

For inventors and businesses, this is an important reminder that patent eligibility is not based on how many parts a system contains. What matters is whether the claims explain a specific improvement in technology.

Takeaway 4: Describing Technology as Conventional Can Hurt a Patent

Another important part of the decision involved the patent specification.

The specification admitted that many of the system's key components were already known and commonly used. These included client applications, data streams, and audio-processing methods.

At Alice Step Two, courts look for an "inventive concept" that turns an abstract idea into patent-eligible subject matter. In this case, the court found that the components described in the patent were conventional and performing ordinary functions.

Gideon Korrell points out that this creates a challenge for patent drafters. Patent specifications must accurately describe existing technology, but statements that emphasize how common certain components are can later be used against the patent in an eligibility analysis.

Patent applicants should carefully explain what makes their invention different while still providing an accurate description of existing technology.

Takeaway 5: Industry Practice Does Not Decide Eligibility

One of the more unusual arguments made by the patent owner was that Google owned patents containing similar functional language.

The patent owner argued that Google's position was inconsistent because its own patents used similar wording.

The Federal Circuit quickly rejected this argument. The court explained that every patent must be evaluated based on its own claims and disclosures.

Gideon Korrell notes that patent eligibility is determined on a patent-by-patent basis. Courts do not decide whether a patent is valid simply because other companies use similar language in their patents. Instead, judges focus on whether the specific patent meets the legal requirements under Section 101.

This part of the decision reinforces an important lesson: common industry practices do not replace legal standards.

Takeaway 6: Patent Cases Can Be Dismissed Early

One of the most important lessons from this decision relates to the legal process itself.

The patent owner argued that the case should have moved forward before the court decided the eligibility issue. The Federal Circuit disagreed and confirmed that Section 101 questions can be resolved at the pleading stage when the patent provides enough information for the court to make a decision.

Because the patent described its components as conventional and did not explain a specific technological solution, the court found that additional proceedings would not change the outcome.

According to Gideon Korrell, this shows why strong patent drafting is so important from the start. A patent that lacks detailed technical explanations may be dismissed before discovery, expert opinions, or claim construction ever take place.

For companies involved in patent litigation, early eligibility challenges remain an effective defense strategy.

What This Decision Means for Future Software Patents

The Federal Circuit's ruling reflects a broader trend in patent law. Courts continue to closely examine software patents that rely on broad functional language without providing detailed technical explanations.

Inventors and businesses seeking patent protection should focus on explaining how their inventions work, not just what they accomplish. Detailed descriptions of system design, software processes, algorithms, and technical improvements can help strengthen a patent under Section 101.

The decision also shows the importance of connecting patent claims to real technological improvements rather than broad ideas or general computer functions.

Conclusion

The Federal Circuit's decision involving U.S. Patent No. 7,679,637 and Google provides valuable insight into the current state of software patent eligibility. The ruling shows that courts continue to apply the Alice framework carefully, especially when claims focus on desired results instead of technical implementation.

As Gideon Korrell explains, the case highlights six important lessons: functional claiming remains risky, technical solutions matter, multiple system components alone are not enough, conventional technology can weaken eligibility arguments, industry practices do not determine patent validity, and Section 101 challenges can end a case at an early stage.

For inventors, patent owners, and legal professionals, the message is straightforward: software patents are more likely to survive eligibility challenges when they clearly explain the technology behind the invention and connect innovative results to specific technical solutions.