Background: The Case That Changed Software Patents
In 2014, the United States Supreme Court issued a unanimous decision in Alice Corporation Pty. Ltd. v. CLS Bank International that fundamentally altered the landscape of software and business method patents. More than a decade later, its effects are still felt in every USPTO examination and patent infringement case involving software-related inventions.
What Was the Dispute About?
Alice Corporation held patents on a computer-implemented system for managing settlement risk in financial transactions — essentially using a third-party intermediary to ensure both sides of a trade fulfilled their obligations. CLS Bank, which operated a similar system, argued that Alice's patents were invalid because they covered an abstract idea.
The core question before the Supreme Court: Can you patent the idea of using a computer to perform a well-known financial concept?
The Supreme Court's Ruling
The Court ruled unanimously against Alice Corporation. In doing so, it applied and clarified the two-step framework originally established in Mayo Collaborative Services v. Prometheus Laboratories (2012), now commonly called the "Alice/Mayo test":
- Step One: Is the claim directed to a patent-ineligible concept — an abstract idea, a law of nature, or a natural phenomenon?
- Step Two: If yes, does the claim include an "inventive concept" — something that transforms the abstract idea into a patent-eligible application?
The Court found that Alice's claims were directed to the abstract idea of intermediated settlement, and that simply implementing this idea on a generic computer did not constitute a sufficient inventive concept to make the patents valid.
The Impact on Software Patent Applications
The Alice decision created immediate and lasting turbulence for software patents. In the years following the ruling:
- USPTO examiners began applying the Alice/Mayo framework aggressively, rejecting a significant portion of software and business method applications under Section 101 (patent eligibility)
- Existing software patents faced new vulnerability in post-grant proceedings and litigation
- Courts invalidated many previously granted software patents, particularly those with broad, abstract claims
What Makes a Software Patent Survive Alice?
Not all software patents are dead — but drafting them requires precision. Claims that have survived post-Alice scrutiny tend to:
- Describe a specific technical improvement to computer functionality (not just using a computer to do something abstract)
- Solve a problem that is specifically rooted in computer technology
- Include concrete, detailed steps rather than broad functional language
- Demonstrate that the claimed method could not be performed practically without a computer
The Ongoing Debate
The Alice ruling remains controversial. Critics argue it has created excessive uncertainty, making it difficult for software innovators — particularly startups — to secure reliable IP protection. Proponents argue it appropriately reins in overly broad patents that stifle competition rather than promote innovation.
Congress has considered legislative reform to Section 101 on multiple occasions, though no comprehensive changes have been enacted to date. In the meantime, the USPTO has issued updated guidance aimed at providing more clarity to examiners and applicants, though the fundamental framework established by Alice remains intact.
Lessons for Inventors and Practitioners
If you are developing a software-based invention, the Alice decision underscores the importance of working with a patent attorney who has deep experience in software patent prosecution. Strategic claim drafting — focusing on technical specificity and concrete improvements — remains the most reliable path to obtaining and defending a software patent in the post-Alice era.