By Michael Borella –
More than a decade after Alice Corp. v. CLS Bank Int’l, the two-step framework for patent eligibility under 35 U.S.C. § 101 remains as contentious as ever. Courts, commentators, and the U.S. Patent and Trademark Office have all acknowledged the difficulty of applying a test that turns on undefined terms such as “abstract idea,” “directed to,” and “significantly more.” But within this legal wreckage, a specific and recurring failure mode deserves closer attention than it has received. Particularly, how a challenger can readily neutralize a patentee’s otherwise strong eligibility argument for a software invention (i.e., a claimed technical improvement described as such in the specification) by asserting in a conclusory fashion that the improvement is to an abstract idea recited by the claim.
The sleight of hand works like this. The patentee points to Enfish, LLC v. Microsoft Corp. and its progeny, argues that the claims are directed to an improvement in computer functionality, and sets forth the specification’s disclosure of the technical problem and its solution. The challenger, rather than disputing that the claims recite an improvement at all, responds that whatever improvement exists is merely an improvement an underlying abstract idea. Invoking SAP America, Inc. v. InvestPic, LLC and BSG Tech LLC v. BuySeasons, Inc., for example, the challenger merely states that an advance an abstract idea cannot confer eligibility no matter how innovative the claimed invention. With that single unreasoned characterization, the patentee’s entire pro-eligibility argument often evaporates.
In many cases, notably those involving software inventions that reduce computational resource usage, this characterization is analytically improper. A claimed invention that reduces processor cycles, memory consumption, bandwidth, or latency is directed to a change in the physical operation of a machine. Calling that change an improvement to an abstract idea does not make it one. Yet the current § 101 framework allows the assertion to succeed with remarkably little scrutiny, both in the courts and at the USPTO.
The Federal Circuit has repeatedly held that improvements to computer functionality are not abstract. In Enfish, the Federal Circuit found claims to a self-referential database table eligible because they were “directed to a specific improvement to the way computers operate.” The Court cautioned against describing claims at “a high level of abstraction and untethered from the language of the claims,” warning that doing so would render the “directed to” inquiry meaningless because “all inventions at some level embody, use, reflect, rest upon, or apply laws of nature, natural phenomena, or abstract ideas.”
McRO, Inc. v. Bandai Namco Games America Inc. extended this reasoning to claimed rules that improved an existing technological process for animating lip synchronization. Finjan, Inc. v. Blue Coat Systems, Inc. and Ancora Technologies, Inc. v. HTC America, Inc. found improvements to computer security eligible, with Ancora emphasizing the specific placement of a verification structure in a memory location not previously used for that purpose. Core Wireless Licensing S.A.R.L. v. LG Electronics, Inc. and Data Engine Technologies LLC v. Google LLC held that improved user interfaces can constitute technical improvements. And in Koninklijke KPN N.V. v. Gemalto M2M GmbH, the Federal Circuit found claims to an improved error-checking technique eligible because they recited a specific implementation that improved the functionality of the error detection process itself.
More recent decisions have characterized the pro-eligibility argument as having two parts – the improvement must be described in the specification, and the claims must reflect it. In Contour IP Holding, LLC v. GoPro, Inc., the Court reversed a summary judgment of ineligibility where the claims recited a point-of-view camera generating high- and low-quality video streams in parallel, with the lower-quality stream enabling real-time wireless preview on a remote device. The specification described the technological problem of streaming video from a resource-constrained camera, and the claims recited the specific means of solving it; that combination placed the claims on the Enfish side of the line. Conversely, in Recentive Analytics, Inc. v. Fox Corp., the Court held claims applying generic machine learning to television scheduling ineligible precisely because neither the claims nor the specification explained how any improvement to the underlying technology was accomplished. And in U.S. Patent No. 7,679,637 LLC v. Google LLC, No. 24-1520 (Fed. Cir. Jan. 22, 2026), the Court stated that while the eligibility inquiry focuses on the claims, “the claim itself need not explicitly recite the improvement,” and endorsed looking to the written description to understand the problem addressed and whether a technological improvement is embodied in the claims. Taken together, these decisions confirm that the specification’s technical disclosure is not window dressing, but rather evidence the challenger or tribunal is expected to consult.
The USPTO codified this line of authority in the 2019 Revised Patent Subject Matter Eligibility Guidance, now reflected in M.P.E.P. § 2106.04(d). Under Step 2A, Prong Two, a claim that integrates a judicial exception into a practical application is not directed to that exception. The first and most prominent example of such integration is “an improvement in the functioning of a computer, or an improvement to other technology or technical field.” M.P.E.P. § 2106.04(d)(1) and § 2106.05(a) instruct examiners to evaluate the specification to determine whether it describes a technical problem and explains how the claimed invention solves it. An August 2025 memorandum to the examining corps reinforced the point, reminding examiners that the claim need not explicitly recite the improvement described in the specification and directing them to consult the specification and confirm that the claim reflects the disclosed improvement.
On paper, then, one with a genuine technical improvement described in the specification and represented in the claim should be well positioned. In practice, the picture is far murkier.
The countervailing argument used by challengers traces back to two 2018 decisions. In SAP America, the court held claims to improved statistical analysis of investment data ineligible, stating that even assuming the techniques were “groundbreaking,” a pioneering abstract idea is not enough. In BSG Tech, the Court held that “a claimed invention’s use of the ineligible concept to which it is directed cannot supply the inventive concept,” and that an alleged advance that lies entirely in the realm of abstract ideas cannot confer eligibility.
Both holdings are defensible on their facts. The claims in SAP America were directed to mathematical analysis of financial information with the results displayed, and the claims in BSG Tech recited a method of indexing information in a database using conventional structures. Neither specification credibly described an improvement to the operation of a computer.
The problem is what happened next. These cases handed challengers and examiners a template that can be deployed against any software claim, regardless of what the specification actually discloses. In district court briefing, the pattern is now routine. The defendant frames the abstract idea broadly, characterizes every claimed benefit as flowing from that idea, and cites SAP America and BSG Tech for the proposition that such benefits are irrelevant. At the USPTO, the corresponding move appears in countless Office actions as a single conclusory sentence, something to the effect of “the alleged improvement is an improvement to the abstract idea itself, not to the functioning of a computer or to another technology.”
Note the asymmetry. To establish a technical improvement, the patentee must engage with the claim language, the specification, and often expert testimony explaining the state of the art and the nature of the advance. To defeat that showing, the challenger needs only a characterization. No claim construction, no engagement with the written description, no explanation of why a reduction in memory usage or processing time is not a change in how the machine operates. The characterization (often a mischaracterization) does all the work, and decision makers too frequently accept it at face value.
A pronounced flaw in the “improvement to the abstract idea” argument is its circularity, and this flaw is most visible in cases involving computational resource efficiency. Consider a claim to a data structure, encoding scheme, or scheduling technique that measurably reduces processor load, memory footprint, or network bandwidth. These are physical, measurable phenomena. A processor that executes fewer instructions consumes less power and completes tasks sooner. A memory system that stores a compressed representation of data uses less silicon. Reducing network utilization increases throughput and reduces delay for all communications carried by that network.
These effects occur in a machine, not in the mind of a mathematician. The Federal Circuit recognized as much in Enfish, where the claimed self-referential table achieved “increased flexibility, faster search times, and smaller memory requirements,” and in Uniloc USA, Inc. v. LG Electronics USA, Inc., where a reduction in communication latency was held to be a patent-eligible improvement to computer functionality. Similarly, in Cellspin Soft, Inc. v. Fitbit, Inc., allegations that the claimed arrangement reduced the hardware and power requirements of the capturing device were credited.
Now observe how the challenger’s argument operates against such a claim. First, the challenger defines the abstract idea at a level of generality high enough to encompass the improvement. If the claim reduces memory usage through a novel indexing arrangement, the abstract idea becomes “organizing and storing data.” If the claim reduces bandwidth through a selective transmission protocol, the abstract idea becomes “sending only necessary information.” Second, having drawn the abstract idea to swallow the technical contribution, the challenger points out that the claimed benefit flows from that contribution, and therefore from the abstract idea. Third, the challenger concludes that under BSG Tech or similar authority that the improvement “lies entirely in the realm of abstract ideas.”
This reasoning is entirely circular. The conclusion that the improvement is abstract depends on the premise that the abstract idea includes the improvement, and that premise was constructed by the challenger for exactly that purpose. Any invention can be dissolved this way. The claims in Diamond v. Diehr improve upon “the abstract idea of curing rubber at the right time.” The claims in McRO improve upon “the abstract idea of matching mouth shapes to sounds.” The claims in Ancora improve upon “the abstract idea of verifying a license.” The Federal Circuit warned against precisely this maneuver in Enfish and again in Thales Visionix Inc. v. United States, yet the “improvement to the abstract idea” formulation invites decision makers to commit the error while appearing to apply binding precedent.
The tell, in resource-efficiency cases, is that the claimed benefit is verifiable on hardware. One can run the prior art technique and the claimed technique on the same machine and measure the difference in cycles, watts, bytes, or time. Where a computer merely executes an unchanged process faster than a human could, as in Bancorp Services, L.L.C. v. Sun Life Assurance Co. of Canada, the improvement is attributable to the computer, not the invention. In these situations, eligibility is properly denied so long as the process was not reasonably performable by a human in the first place.[1] When the specification describes, and the claims capture, a change to the physical behavior of a computing system that results in a technical improvement, the SAP America line of cases simply does not fit. That the improvement can be described in abstract terms proves nothing, because as Enfish reminds us, every invention relies on underlying judicial exceptions.
If the circularity problem is troubling in litigation, where the patentee at least has briefings and oral arguments to expose it, it is worse in prosecution. Examiners operating under time constraints frequently dispose of an applicant’s eligibility arguments with the conclusory sentence described above, without addressing the specification’s description of the technical problem or explaining why the asserted benefit is not technical. This practice sits uneasily with M.P.E.P. § 2106.04(d)(1), which directs the examiner to evaluate whether the specification sets forth an improvement and whether the claim reflects it. A bare assertion that the improvement is to the abstract idea evaluates nothing.
PTAB review of such rejections has been inconsistent, with some panels demanding that examiners engage with the disclosed improvement and others affirming on the same conclusory rationale. The practical consequence is perverse. Applicants can respond by overloading claims with hardware recitations and implementation minutiae that add nothing inventive but make the claims look less abstract. Claim quality degrades, prosecution costs rise, and the resulting patents protect the invention less faithfully than the original claims would have.
Three corrective principles would go a long way. First, the party asserting that an improvement encompasses the abstract idea should bear the burden of engaging with the specification and articulating, with specificity, why the asserted benefit is not a technical one. A characterization unsupported by analysis should carry no weight.
Second, measurable reductions in computational resource usage should be treated as presumptively technical. This is not a radical proposition, as it follows directly from Enfish, Uniloc, KPN, and Cellspin. A challenger remains free to show that the claims fail to capture the improvement or that the specification’s assertions are implausible, but the physical nature of the benefit should not be in serious dispute.
Third, decision-makers should heed Diehr‘s instruction to consider the claim as a whole, rather than first filtering out the allegedly abstract components and then asking what remains to be improved. The filtering approach guarantees the circular result, because the improvement is always found among the components that were filtered out.
The Alice framework has always tolerated a certain amount of rhetorical gamesmanship, but the “improvement to the abstract idea” gambit is a particularly corrosive example. It targets the one doctrine, the Enfish technical-improvement line, that gives software patentees a principled path to eligibility. Until courts and the USPTO require those who invoke SAP America, BSG Tech, and the like to actually demonstrate that a claimed improvement is abstract, rather than merely to assert it, inventors of genuinely technical advances, including those that make computers demonstrably faster, smaller, and more efficient, will remain exposed to a one-sentence dismissal of their strongest argument.
Thus, the irony is complete. A doctrine allegedly created to weed out patents that claim inventions too abstractly is now enforced through arguments that reason too abstractly.
[1] Put another way, a resource-intensive task like training a large language model is not something that a human ever has performed or even could perform. Therefore, it is deeply reliant on the computing hardware on which it executes, without which there would be no model. Alternatively, a computer performing an unchanged human process is almost certainly to fail as obvious under § 103, so why bother using the vague and problematic analysis of § 101 for this purpose?













