CAFC Affirms Rule 12(b)(6) 101 Dismissal for Google in Precedential Ruling on Software Claims

“The CAFC said even if it were to narrow the district court’s view of the claims, they are still directed to ‘the patent-ineligible abstract idea of allowing asynchronous review of presentations, rather than any specific technological improvement.”

CAFCThe U.S. Court of Appeals for the Federal Circuit (CAFC) on Thursday, January 22, issued a precedential decision affirming a district court ruling that granted Google’s motion to dismiss a patent owner’s infringement suit for failure to state a claim. The CAFC agreed with the district court that the software claims in question were directed to a patent-ineligible abstract idea. The opinion was authored by CAFC Chief Judge Moore and joined by Judges Hughes and Stoll.

U.S. Patent No. 7,679,637 LLC sued Google in the U.S. District Court for the Western District of Washington for infringing certain claims of its patent, titled “Time-shifted Web Conferencing.” Google moved to dismiss under Federal Rule of Civil Procedure 12(b)(6), arguing the asserted claims are patent- ineligible under 35 U.S.C. § 101. The district court granted Google’s motion, finding that the claims were directed to the abstract idea of “playing back recorded content.”

On appeal to the CAFC, U.S. Patent No. 7,679,637 argued that this is an “over-generalization” of the claims, which recite a “specific asserted improvement that allows a presentation to be reviewed asynchronously . . . at the same time.” But the CAFC said even if it were to narrow the district court’s view of the claims, they are still directed to “the patent-ineligible abstract idea of allowing asynchronous review of presentations, rather than any specific technological improvement, because they do not ‘describe how the alleged goal of [asynchronous review] is achieved,’” citing to Hawk Tech. Sys., LLC v. Castle Retail, LLC, 60 F.4th 1349, 1357 (Fed. Cir. 2023).

Analyzing the claim language at step one of the Alice-Mayo framework, the CAFC found that they recite what the claims do, but not how they do it. Neither do they contain any “specific technological improvement discernible to a skilled artisan from the patent or the prosecution history.” While the patent owner argued the claims “expressly explain how the systems need to be set up to accomplish the improvement,” the CAFC said “they do not explain how the client applications achieve the recited manipulation of the data streams to enable asynchronous review.”

Furthermore, the written description does not provide any greater insight, and instead “suggests the invention is nothing more than the abstract idea of applying known time-shifting functions to web-conferencing systems to solve ‘great inefficiencies’ resulting from participants waiting for others to join a presentation or from participants missing part of a presentation.”

The opinion distinguished the case from Contour IP Holding LLC v. GoPro, Inc., noting that there, the claims disclosed “improving POV camera technology through specific means of generating high- and low-quality video streams in parallel and transferring a low-quality video stream to a remote device.” The present case is more like Hawk Technology Systems, where the CAFC agreed with a district court’s finding that Hawk’s U.S. Patent No. 10,499,091, titled “high-quality, reduced data rate streaming video product and monitoring system,” should be dismissed for failure to state a claim because the patent was invalid as ineligible. The CAFC held those claims, which also involved the manipulation of multiple data streams “fail[ed] to recite a specific solution to make the alleged improvement—conserving bandwidth while preserving quality—‘concrete’ and were ‘recited at such a level of result-oriented generality that those claims amount[ed] to a mere implementation of an abstract idea.’”

U.S. Patent No. 7,679,637 LLC also attempted to argue that Google uses “functional claiming” in its own video conferencing patents and therefore “necessarily believes this approach to claim drafting does not result in subject matter ineligible claims,” but the CAFC said that the “subject matter eligibility of Google’s patent claims is not before us and has no bearing on our analysis of the ’637 patent.” Moore added: “Moreover, we reject the notion that the mere existence of factually distinguishable Google-owned patents somehow amounts to a sweeping concession by Google that all patents involving functional claiming approaches are necessarily patent-eligible.”

Moving to step two of Alice-Mayo, the patent owner argued the district court overlooked the two inventive concepts contained in the claims, specifically: “1) a two client application system allowing for the manipulation of multiple data streams and (2) a ‘time-scale modification component.’”

But the CAFC said neither concept transforms the claims into something that is patent eligible. The patent owner’s arguments merely repeat its step one assertions, said the opinion, and “the claimed client applications are conventional, well-known components, operating according to their ordinary functions to manipulate conventional data streams.”

Finally, the patent owner argued that the district court improperly decided patent eligibility at the motion to dismiss stage and should have been allowed to amend its complaint, but the CAFC said the patent owner made no factual allegations that would preclude dismissal. “No amendment to the complaint can alter what the ’637 patent itself states regarding the conventionality of the client applications, data streams, and time-scale modification components discussed in the eligibility analysis detailed above,” said the opinion.

The CAFC lastly rejected the patent owner’s argument that Google’s motion to dismiss should have been treated as a summary judgment motion because Google relied on facts outside the complaint to establish what was well-known, routine and conventional and because the district court also should have conducted claim construction prior to dismissal. The district court “was clear it did not rely on any extra-pleading materials” in coming to its decision to grant the motion to dismiss, said the CAFC, and claim construction was not necessary because the patent owner “never proposed any constructions or explained how a proposed construction would change the patent-eligibility analysis.”

Image Source: Deposit Photos
Author: alexmillos
Image ID: 35440567 

Share

Warning & Disclaimer: The pages, articles and comments on IPWatchdog.com do not constitute legal advice, nor do they create any attorney-client relationship. The articles published express the personal opinion and views of the author as of the time of publication and should not be attributed to the author’s employer, clients or the sponsors of IPWatchdog.com.

Join the Discussion

11 comments so far. Add my comment.

  • [Avatar for Anon]
    Anon
    January 28, 2026 01:08 pm

    We’ve fully moved to the judicial branch abrogating legislative writing (see 35 USC 282).

  • [Avatar for Stephen Schreiner]
    Stephen Schreiner
    January 26, 2026 10:09 pm

    Thanks, lol.

  • [Avatar for Anon]
    Anon
    January 26, 2026 05:35 pm

    Stephen,

    Your comment is good enough to leave up twice as is. Thank you.

  • [Avatar for Stephen Schreiner]
    Stephen Schreiner
    January 26, 2026 11:46 am

    This opinion, authored by Chief Judge Moore, shows the sorry state of affairs in Alice jurisprudence. Because the Supreme Court provided no test or definition of abstract ideas, the CAFC has been forced to develop corollary tests like this “how-to” test for the claims. The CAFC says that the claims must explain “how-to” achieve the result.

    There are two problems with the “how-to” test. First, it improperly conflates §101 with §112, effectively importing enablement and definiteness into the eligibility inquiry. Second, whether a claim explains “how to” achieve a result says nothing about whether it is directed to an abstract idea. There is no analytical basis for treating “how-to” as a meaningful proxy for identifying abstract ideas (whatever that means).

  • [Avatar for Stephen Schreiner]
    Stephen Schreiner
    January 26, 2026 11:20 am

    This case, authored by Chief Judge Moore, shows the sad state of affairs in Section 101 . Because nobody knows what an “abstract idea” is, the CAFC had developed these strange corollary bodies of law like this “how to” test. The CAFC finds that a claim is directed to an abstract idea if the claim does not explain “how to” achieve the result claimed.

    This makes no sense for two reasons. First, the “how to” test conflates Section 101 with Section 112. Moreover, there’s no requirement that claim explains “how to” achieve the result–that’s the job of the specification. The second problem is that whether a claim describes “how to” achieve the result has nothing to do with whether it’s claiming an abstract idea. The “how to” framework makes no analytical sense.

  • [Avatar for Anon]
    Anon
    January 23, 2026 04:23 pm

    Well, I should have read Lab’s reply before submitting my own as clearly the specificity was there.

    Mea culpa.

  • [Avatar for Anon]
    Anon
    January 23, 2026 04:18 pm

    One word (which I am certain that a certain person at PatentDocs would agree with):

    Specificity.

  • [Avatar for Hopeful]
    Hopeful
    January 23, 2026 12:25 pm

    This Fed Cir decision is completely inconsistent with the recent PTO Director Desjardins decision and Alice too. Not a peep about whether the claim(s) in issue would (i) preempt an abstract idea (ii) recited in the claim, such as by claiming a practical application of the claim recited idea that would not do so.

    And no consideration at all of the functional claiming doctrine and how it narrows claims to disclosure in the spec.

    I just cannot understand what the Fed Cir has been doing in this space to trash so many patents for fine inventions.

    Perhaps the PTO Solicitor and Solicitor General will join in as amicus on a request for rehearing en banc. Then, if that does not fix this mess, go to the Supreme Court as amicus with the Solicitor General as in American Axle but with a more focused analysis and precise recommendation for a fix, finally.

  • [Avatar for Model 101]
    Model 101
    January 23, 2026 09:21 am

    Just goes to show how incompetent the judges are.

    It’s either that or corruption.

  • [Avatar for Lab Jedor]
    Lab Jedor
    January 22, 2026 07:13 pm

    Just saying: “Moreover, the written description does not disclose any improvement to the underlying components to enable asynchronous review. ” doesn’t make it so.

    In fact Google (yes) Gemini observes:

    “US Patent 7,679,637 (titled “Time-shifted Web Conferencing”) indeed tackles the “asynchronous” problem by decoupling the data streams.

    While classical film used a physical sprocket lock to keep audio and video together, this patent describes a system where streams like video, audio, and even chat or whiteboarding data are treated as independent “objects” with their own temporal metadata.

    How this “Elegantly” Solves Your Problem
    The patent’s core innovation isn’t just playing two things at once; it’s about independent decompression and scaling. Here is the breakdown of why that matters for your specific goal:

    Separate Frame Counters: Instead of the audio being a “slave” to the video’s master clock, each stream has its own counter. This allows you to “time-shift” one (like pausing the video to look at a slide) while the other (the audio) continues to play live or at a different rate.

    Time-Scale Modification (TSM): This is the “secret sauce” mentioned in the patent. It allows the system to change the playback speed of the audio without changing the pitch. If your video lags behind because of heavy decompression, the TSM component can “speed up” the audio processing to catch up without making the speaker sound like a chipmunk.

    Decoupled Decompression: In a standard player, if the video frame fails to decompress in time, the whole system might stutter. In the ‘637 architecture, the audio decompression engine operates on its own track, ensuring the “sound” of the program remains fluid even if the “picture” is being manipulated or delayed.”

    Anyone with a bit of technical sense can find the technical explanation in the spec, using frame counters, and frame related decompression, and how to decouple.

    The assertion that the specification is silent about this is utterly made up. Perhaps the Judges should take the trouble of actually reading a specification of a case before them. Because it really jumps at you. And not believe merely what the Defendants submit,even if it is Google.

    PS. The above “secret sauce” is what CAFC says is the “missing inventive concept.”

  • [Avatar for Pro Say]
    Pro Say
    January 22, 2026 05:46 pm

    “Functional claiming for me, but not for thee.”
    — Google

    “Functional claiming for Google, but not for thee.”
    — CAFC

Add Comment

Your email address will not be published. Required fields are marked *

Varsity Sponsors

IPWatchdog Events

IPWatchdog LIVE 2026 at the Renaissance Arlington Capital View
March 22 @ 1:00 pm - March 24 @ 7:00 pm EDT
Webinar: Sponsored by LexisNexis
March 31 @ 12:00 pm - 1:00 pm EDT
Webinar: Sponsored by NLPatent
April 2 @ 12:00 pm - 1:00 pm EDT
Webinar: Sponsored by Clearstone IP
April 9 @ 12:00 pm - 1:00 pm EDT

Industry Events

PIUG 2026 Joint Annual and Biotechnology Conference
May 19 @ 8:00 am - May 21 @ 5:00 pm EDT
Certified Patent Valuation Analyst Training
May 28 @ 9:00 am - May 29 @ 5:00 pm EDT

From IPWatchdog