Alice v. CLS Bank

Alice Corp. v. CLS Bank International (S.Ct. 2014) is the most consequential patent eligibility case in the modern era: THE PATENT AT ISSUE: Alice Corporation held patents on a method, computer system, and computer-readable medium for 'intermediated settlement' — using a third-party intermediary to reduce settlement risk in financial transactions; THE CLAIMED INVENTION: when two parties agree to exchange financial obligations, a computer system maintained by a third party creates 'shadow' records tracking what each party owes; if both parties can meet their obligations at close of day, the exchange settles; if not, the transaction is cancelled — preventing systemic risk from one party defaulting; THE QUESTION: were Alice's claims directed to patent-eligible subject matter under 35 U.S.C. § 101?; THE UNANIMOUS HOLDING (Justice Thomas): Alice's claims were directed to an abstract idea — the concept of intermediated settlement, a 'fundamental economic practice long prevalent in commerce'; implementing that abstract idea on a generic computer did not transform it into a patent-eligible invention; the computer components (computer, data storage, processor) added 'nothing of substance' to the abstract idea itself; STAKES: hundreds of thousands of software and fintech patents were filed using the approach Alice used; Alice threatened to invalidate a substantial fraction of the entire software patent portfolio held by US companies; since Alice, thousands of patents have been invalidated under § 101; THE FRAMEWORK ALICE APPLIED: the Court applied the Mayo Collaborative Services v. Prometheus Laboratories (S.Ct. 2012) framework: Step 1 — is the claim directed to an abstract idea, law of nature, or natural phenomenon? Step 2 — do the additional claim elements, individually or as an ordered combination, transform the claim into a patent-eligible application?

The Alice/Mayo framework has been applied thousands of times since 2012-2014: STEP 1 — IS THE CLAIM DIRECTED TO AN ABSTRACT IDEA?: the claim is analyzed as a whole; if the 'focus' of the claim is an abstract concept, it fails Step 1; abstract ideas include: mathematical concepts (algorithms, formulas, relationships); certain methods of organizing human activity (economic practices, commercial interactions, social activities, legal obligations); mental processes (concepts performed in the mind); WHAT IS NOT AN ABSTRACT IDEA: claims directed to specific machines/devices; claims directed to specific physical transformations; claims directed to specific chemical compositions; STEP 2 — DO ADDITIONAL ELEMENTS AMOUNT TO 'SIGNIFICANTLY MORE'?: assuming Step 1 is failed, the court looks for elements that transform the claim; elements that DO NOT provide 'significantly more': generic computer implementation ('apply it'); well-understood, routine, conventional activity; mere instructions to 'implement' an abstract idea; elements that DO provide 'significantly more': a specific technical improvement to computer technology (Enfish; McRO); non-generic hardware (a specific machine); a specific unconventional combination of steps that improves technology; THE PROBLEM WITH 'ABSTRACT IDEA': the Court has never defined 'abstract idea' with precision; Federal Circuit decisions are often inconsistent; patentability can turn on claim drafting and framing; HOW COURTS EVALUATE: compare to prior § 101 cases (analogizing to cases finding eligibility or ineligibility); look at the 'directed to' question at the claimed concept level; avoid reading claims too broadly or too narrowly; consider the specification to understand what the invention actually is.

Post-Alice § 101 case law has created a complex landscape of eligible and ineligible software inventions: PATENTS THAT SURVIVED (eligible): Enfish, LLC v. Microsoft Corp. (Fed. Cir. 2016): database table with self-referential structure — claims directed to a specific technical improvement in database technology (performance improvement), not merely an abstract idea + generic computer; McRO, Inc. v. Bandai Namco Games America (Fed. Cir. 2016): 3D character animation (lip-sync); claims directed to a specific technological technique for automating computer animation (using a new set of rules for phoneme-to-morpheme mapping); Finjan, Inc. v. Blue Coat Systems (Fed. Cir. 2018): malware detection scanning; claims directed to a new type of virus scan result (behavior-based profile) that is a real-world, specific technical product; Core Wireless Licensing v. LG Electronics (Fed. Cir. 2018): specific improved user interface for mobile phone (summary window allowing direct access to application functions); PATENTS THAT DID NOT SURVIVE (ineligible): Intellectual Ventures v. Capital One Bank (Fed. Cir. 2016): organizing financial information by category — abstract method of organizing economic activity; content delivery to mobile devices based on budgets — abstract idea of managing customer information + conventional computer components; Electric Power Group v. Alstom (Fed. Cir. 2016): collecting, analyzing, and displaying power grid data — mere data collection + analysis on generic computer; Secured Mail Solutions v. Universal Wilde (Fed. Cir. 2017): generating and encoding transaction identifiers for mail pieces — abstract idea of encoding/verifying information; KEY PATTERN: survival depends on whether the claim is anchored to a specific technical improvement (not just applying abstract thinking to a computer) or a non-conventional arrangement of computer components.

The USPTO issued revised guidance in 2019 that restructured how examiners apply Alice/Mayo: BACKGROUND: after Alice (2014), the USPTO issued interim guidelines; many applicants complained that examiners were applying Alice too broadly and rejecting legitimate software patents; the 2019 Revised Guidance was intended to provide more structure and predictability; 2019 REVISED GUIDANCE STEP 2A, PRONG 1: ask whether the claim recites a judicial exception; the USPTO specifically listed abstract idea groups: (a) mathematical concepts (formulas, algorithms, mathematical calculations); (b) certain methods of organizing human activity (fundamental economic principles, commercial/legal interactions, managing personal behavior); (c) mental processes (concepts performed in the human mind, even if using a computer); 2019 GUIDANCE STEP 2A, PRONG 2 (THE ADDITION): even if the claim recites a judicial exception, it is NOT directed to a judicial exception if the claim AS A WHOLE integrates the recited judicial exception into a practical application; PRACTICAL APPLICATION: whether the additional elements reflect a specific, particular way of applying the judicial exception; result in an improvement to the functionality of a computer or other technology; are applied with or by a particular machine (not generic); particular transformation of an article to a different state or thing; other meaningful limitations beyond limiting the application to a particular technological environment; STEP 2B (formerly Step 2): look at whether additional elements add significantly more beyond the judicial exception; PRACTICAL IMPACT: prong 2 of Step 2A gave applicants a new avenue to argue eligibility: that the claim integrates the abstract idea into a practical application even if the abstract idea itself remains abstract; reduced the rate of § 101 rejections at the USPTO; federal courts are not bound by USPTO guidance — this only applies to examination.

Skilled patent drafters have developed specific strategies to improve § 101 survivability: TECHNICAL IMPROVEMENT FRAMING: frame the invention as a technical improvement to computer technology rather than as a concept that happens to run on a computer; describe the specific technical problem being solved (performance bottleneck, security vulnerability, efficiency limitation); describe how the specific technical solution improves computer/network/software performance; SPECIFIC TECHNICAL ELEMENTS: recite specific technical components, not generic ones ('data processor' vs. 'a specialized cache with reduced-latency read circuit'); describe specific hardware, specific protocols, specific data structures; avoid 'generic computer' language; UNCONVENTIONAL COMBINATION: even if individual steps are known, an unconventional ordered combination may be patent-eligible; McRO survived because the specific combination of steps was not conventional; CLAIM STRUCTURE MATTERS: claim directed to a technological process or system implementing the concept differently from conventional practice; consider system claims (specific hardware + interactions) alongside method claims; avoid claiming the abstract concept directly (math formula, economic principle); TECHNICAL EFFECT IN SPECIFICATION: describe the technical problem and technical solution explicitly in the specification; include performance data showing the technical improvement; describe what makes the claimed approach non-obvious from a purely technical perspective; PREEMPTION CHECK: would allowing this patent preempt all ways to implement the abstract concept?; claims that preempt all implementations of an abstract idea are most vulnerable; narrowly directed claims (specific technical implementations) are more defensible; PROSECUTION STRATEGY: during examination, argue that the claim is directed to a specific practical application; point to technical improvements achieved; cite post-Alice Federal Circuit cases where similar technology was found eligible; distinguish the specific technical implementation from the abstract concept.