Notes on Patentability of Business Methods and Computer-Implemented Inventions

Overview of the Topic

The session focuses on patentability of business methods and computer-implemented inventions. The lecturer emphasizes that this material is part of the assignment and prepares students to reason through how to assess patent eligibility in this area.
Central tension: business methods and abstract ideas vs. genuine technical innovation. The discussion traces how courts and statutes historically treat monopolies, patents on methods, and the boundary between allowed and excluded subject matter.
The thread runs from traditional notions of patents on concrete inventions to modern concerns about patents on purely business processes or software-driven methods.

Key Concepts and Definitions

Patentability framework (general): an invention must involve a technical contribution beyond an abstract idea or mere scheme, and it must meet novelty, inventive step (non-obviousness), utility, and industrial applicability.
Business method: a technique for conducting business, often involving processing of financial data or management of business processes; historically controversial as a candidate for patent protection.
Computer program as such: widely treated as excluded subject matter in many jurisdictions, but there is an exception for inventions that make use of or involve a computer program and thereby provide a technical contribution.
Computer-implemented invention vs. computer program as such:
- Computer program as such: the software alone, without a broader technical contribution, is typically not patentable.
- Computer-implemented invention: a software-driven method or system that yields a technical, practical result beyond the software itself.
Abstract idea: a broad concept (e.g., a mathematical formula, a fundamental economic principle) that, by itself, is not patentable; may become patentable if transformed or applied in a technical way to produce a tangible result.
Artificial state of affairs: a technical construct or environment created by the invention that has practical utility; crucial to distinguishing patentable inventions from mere ideas.
“Actual contribution” vs. “form”: in evaluating patentability, focusing on what the claim actually contributes technically (not just how it’s framed) is essential.
Technical contribution: a contribution that solves a technical problem or provides a tangible improvement in a computer- or machine-based context.
International perspectives: the US, UK, Australia, and New Zealand have differing approaches, but there is a shared movement toward requiring a technical contribution and away from broad patenting of abstract business methods.

Historical Context and Early Monopolies

Early view: monopolies and patents historically targeted physical transformations or concrete technical processes (e.g., transforming raw material into a different state).
Patents on bookkeeping and methods: concerns arise when patents could lock out competitors by controlling basic methods (e.g., bookkeeping processes) rather than truly transformative inventions.
The tension between protecting genuine innovation and avoiding monopolies over abstract ideas or fundamental business practices.

The Idea of Business Method Patents

Business method patents: patent protection for methods of doing business, often implemented by computers or software.
Core question: can a business method be patented if it solves a technical problem or yields a tangible, useful result?
Practical examples discussed: insurance plans, newspaper layouts (layout changes as a “technical” result in the old sense), and other everyday business activities used to illustrate where lines may be drawn.
The risk discussed: post-State Street, a flood of business-method patents emerged, including patents for things like customer loyalty schemes, shipping processes, or even floor-reservation systems—often criticized as “patents on business models” rather than true inventions.

Landmark US Cases (Evolution of the US stance on business methods and software)

State Street Bank v. Signature Financial Group (landmark, late 1990s)
- Core idea: data-processing and financial data transformation can be patented if it produces a practical result (e.g., transformation of data into a stream of revenue or a final accounting value).
- Practical outcome: “the transformation of data in a financial context” can be treated as a patentable invention when it produces a useful, concrete, tangible result (e.g., final share price derived from data processing).
- Impact: opened the door to many business-method patents, contributing to a wave of applications.
- Textual note from lecture: data processing that transforms data into a final dollar amount is a patentable practical application; the judge emphasized the need for a concrete, tangible result and real-world utility.
Repercussions and subsequent questions about State Street
- The decision led to a “tsunami” of business-method patents and prompted courts to consider stricter standards for what counts as a patentable contribution.
- Questions arose about whether all business-model ideas could be patented simply because they are implemented by a computer.
Bilski v. Kappos (2010)
- Central issue: is there a universal test for patent-eligibility of abstract ideas, including business methods?
- Holding: The Supreme Court rejected the exclusive use of the machine-or-transformation (MOT) test as the sole test for patent eligibility of processes; it acknowledged that an abstract idea implemented using a computer is not automatically patentable.
- Significance: reinforced that mere transformation or mere implementation on a computer is not enough; the claim must contain a practical application that integrates the idea into a technical context.
Alice Corp. v. CLS Bank International (2014)
- Core principle: abstract ideas implemented on a computer are not patentable unless there is an “inventive concept” that amounts to more than well-known, generic computer implementation.
- Outcome: clarified that a method claim that is essentially an abstract idea, even when implemented by a computer, can be non-patentable unless there is an additional element that amounts to a practical improvement in technology or a technical contribution.
- Practical takeaway: the mere addition of a computer to perform the abstract idea does not make it patentable; there must be a real-world technical effect.
The “device” or system claims in computer-implemented cases
- Courts consider both method claims and system claims; a method claim that’s abstract remains non-patentable unless it includes a technical improvement. The system claims’ patentability depends on whether the claimed invention provides a technical contribution beyond the abstract idea.
Summary takeaway from US cases
- After State Street, a flood of business-method patents emerged, but later Supreme Court decisions (Bilski, Alice) narrowed the scope, clarifying that abstract ideas implemented on a computer require a meaningful technical contribution to be patentable.

Key UK and Commonwealth Perspectives

Aerotel/Macrossan (Aerotel v Telco Holdings; four-step test for patentable subject matter in the UK)
- Four-step approach (as articulated in Aerotel):
  1) Proper construction of the claim to identify the contribution.
  2) Determine the problem to be solved.
  3) Decide whether the contribution falls solely within excluded subject matter (e.g., business method, mental process, etc.).
  4) Check whether the actual contribution is technical in nature and has industrial applicability.
- Purpose: to guide the assessment of exclusions from patentability and isolate the technical contribution.
Merrill Lynch and Company v. Opti (UK): Computerized trading systems and business-methods examples
- A key example where a computerized system for trading or processing data was considered non-patentable if the actual contribution lay in the computer program itself rather than in a technical improvement.
- Illustrates the emphasis on actual technical contribution rather than the mere automation of a business method.
Symbian Ltd. v Controller General (UK)
- Example where improvements to computer operations (e.g., increasing speed or reliability) that go beyond mere computerization can be patentable because they provide a technical benefit.
- Demonstrates that not all computer-implemented improvements are non-patentable; a genuine technical contribution matters.
Australia and other Commonwealth jurisdictions
- Australia continued to evaluate whether a computer-implemented method or business-method-related invention provided a technical contribution and met the standard for patentability; debates persisted about how to draw the line between abstract ideas and patentable technical improvements.
- The lecture notes mention a 2022 Australian High Court decision on an electronic gaming machine with mixed computer-implemented and physical components, illustrating ongoing debates about what constitutes a technical invention versus a mere abstract idea or business method.
Practical takeaways from UK/Commonwealth practice
- The four-step Aerotel test helps identify whether a claim has a technical contribution and falls outside exclusions.
- A “computer program as such” exclusion remains important; however, an invention that improves the functioning of a computer or produces a technical effect can be patentable.
- The actual contribution must be technical in nature, not merely a clever business concept dressed up as software.

New Zealand Perspective and the Patents Act 2013

Section 11: Computer programs as such
- The Act excludes computer programs as such from patentability, but there is room for inventions that make use of or involve a computer program to be patented if they have a technical contribution.
- This mirrors the general approach of other common-law countries: separate the unpatentable program itself from patentable inventions that use or embed a program to produce a technical effect.
The ICONs (Factors) for assessing patentability in NZ (per the lecture, adapted from the NZ Patents Act and guidance, often cross-referenced with UK US practice)
- ICON 1: Identify the actual contribution of the claim (in substance, not merely its form).
- ICON 2: Determine whether the contribution falls solely within an excluded subject matter (e.g., a mere business method).
- ICON 3: Assess whether the actual contribution is technical in nature (i.e., there is a technical contribution beyond the abstract idea).
- ICON 4: Consider whether the invention has industrial applicability and provides a practical or tangible result.
- Additional factors discussed in class: the problem solved, the advantages of the solution, novelty, and the utility, and any other matters relevant to the exam question.
Practical considerations and examples given in NZ context
- Computer programs as such are excluded, but a computer-implemented invention may be patentable if it yields a technical contribution beyond the software itself.
- Comparisons with UK and US: NZ leans toward a balanced approach, not overbroadly excluding software-based innovations but not granting patents to abstract business methods merely because they involve a computer.
General direction for NZ students
- In NZ, like in many jurisdictions, a key question is whether there is a technical contribution that goes beyond a mere automation of a business method.
- Students should focus on the actual technical contribution, the problem solved, and the tangible improvements to technology or industry practice.

Computer-Implemented Inventions vs. Business Methods (Clarifying the Distinction)

Computer program as such vs. computer-implemented invention
- “Computer program as such” exclusion targets software itself lacking a broader technical contribution.
- A computer-implemented invention claims a method, system, or process that uses software to achieve a technical advantage or to alter the functioning of hardware in a meaningful way.
The role of a technical contribution
- A claim must show an improvement in how a computer or device operates, or an improvement in a technical field, not merely an abstract idea realized by software.
- The “actual contribution” is central: if the core contribution is in the software but does not translate into a technical effect, it will be weaker on patentability grounds.
The concept of artificial state of affairs
- The creation of a technical environment or context that enables a practical application of the idea is important for patentability.
Artificial vs. natural data processing
- Purely abstract data processing without a technical effect is less likely to be patentable; when data processing yields a tangible, concrete result, it may be patentable if it involves a technical contribution.

Methodology for Assessment (Exam-Ready Framework)

US framework (key cases):
- State Street Bank (1998): a financial data transformation can be patentable if it yields a practical result.
- Bilski (2010): rejects an exclusive MOT test; abstract ideas remain non-patentable unless there is a concrete technical application.
- Alice (2014): abstract ideas implemented on a computer require an additional inventive concept that amounts to a technical contribution.
UK/Commonwealth framework:
- Aerotel four-step test (for exclusions from patentability): identify contribution, solve a problem, ensure the contribution is not an excluded subject matter, determine technical character and industrial applicability.
- Merrill Lynch and Symbian illustrate how to treat computerization and improvements to computer operations as patentable when there is a genuine technical contribution; otherwise not.
New Zealand framework:
- Follow a similar approach: assess whether the invention has a technical contribution, not merely a computer-implemented business method; apply ICONs to identify and evaluate the actual contribution.
Practical exam approach:
- Always start by identifying the actual contribution (not the form).
- Check whether the contribution falls within excluded subject matter.
- Determine whether the contribution is technical in nature and provides a tangible improvement.
- Verify industrial applicability and utility.
- Support conclusions with relevant case law from the jurisdiction in question (US, UK, NZ, Australia).

Practical Examples and Scenarios from the Transcript

One-click patent (e-commerce):
- Concept: online shopping with a one-click checkout; early efforts to patent the method of online purchasing, including price selection and quantity changes.
- Aftermath: it spurred discussions about patentability of business methods and the need to evaluate whether there is a genuine technical contribution beyond the business concept.
State Street and financial data processing:
- Example given: computing final share price after market close from data processing; treated as a practical transformation of data into a monetary value.
Insurance scheme and other business-method examples:
- Practical concerns raised about patents on what seem like routine business practices (delivering services, customer engagement strategies, or discount schemes).
DHL as a business model example:
- Question raised: should a business method be patentable if the business model is already highly effective without patent protection?
Notifications about patents for seemingly trivial inventions:
- Mention of patents on teaching janitors, floor-shipping, or color-coded bracelets; used to illustrate the potential flood of questionable patents (the so-called “dumb patents”).
Washing machine improvement example (Symbian and related cases):
- Concept: a new method implemented in a washing machine to improve efficiency or performance; the discussion notes that the improvement, not merely the software, constitutes the technical contribution.
- Related guidance: cases like Symbian illuminate that a computer-implemented improvement to hardware can be patentable if it provides a concrete technical effect.
Loyalty card and other computer-implemented methods in the US:
- A loyalty-card example is used to discuss whether the mere use of a computer program to carry out a standard business process is enough to be patentable.

Implications, Trends, and Practical Wisdom for Exam Prep

The line between patentable innovation and unpatentable abstract ideas remains nuanced and jurisdiction-dependent.
After State Street and the subsequent Supreme Court decisions (Bilski, Alice), there is a clear trend toward requiring a technical contribution and a tangible, practical effect beyond mere automation of a business method.
The UK Aerotel framework remains a practical tool for analyzing claims, especially for excluded subject matter.
NZ and other Commonwealth jurisdictions mirror this cautious, contribution-focused approach while adapting to local statutory language (e.g., computer programs as such under section 11 in NZ).
AI and the frontier: while AI-generated inventions raise new questions about inventorship and authorship, the fundamental tests (actual contribution, technical character, and industrial applicability) still guide examination; the law is still catching up with AI-era concerns.

Ethical, Philosophical, and Real-World Implications

Patents on business models and software can stifle competition and innovation if granted too broadly, especially for concepts that merely automate existing business practices.
A careful, principled approach protects genuine technical innovation while avoiding monopolies on abstract ideas or routine tasks.
The balance between encouraging innovation and preventing “patent thickets” is a live policy concern in many jurisdictions.
In the real world, courts weigh practical effects: whether a patent would meaningfully improve technology or only grant control over a business idea.

Case-Labeled Notes and Takeaways to Memorize for the Exam

State Street Bank v. Signature Financial Group (US): data transformation of financial data can be patentable if it produces a practical, tangible result.
Bilski v. Kappos (US): machine-or-transformation test is not the sole determinant; abstract ideas remain non-patentable unless a true technical contribution exists.
Alice Corp. v. CLS Bank International (US): abstract ideas + generic computer implementation are not patentable; require a technical improvement or application.
Aerotel v Telco Holdings (UK): four-step test for patentable subject matter; emphasis on distinguishing technical contribution from excluded subject matter.
Merrill Lynch v. Opti (UK): computer-implemented business methods may be non-patentable if the actual contribution lies in the software rather than a technical improvement.
Symbian Ltd. v. Comptroller General (UK): improvements to computer operation can be patentable if they provide a technical contribution.
NZ Patents Act 2013 (Section 11): computer programs as such are excluded, but computer-implemented inventions can be patentable if a technical contribution is present; apply ICONs to assess.

Short Quick Reference (Checklist for a Exam Answer)

Identify whether the claim seeks a computer program as such or a computer-implemented invention with a technical contribution.
Apply the Aerotel four-step test (UK) or the US framework (State Street, Bilski, Alice) to determine if there is a valid technical contribution.
Determine whether the actual contribution is technical, not merely an implementation of a known concept on a computer.
Check for a tangible, practical result or improvement in a technical field (e.g., computation of a final share price, optimization of a device’s operation).
Consider industrial applicability and the policy objective of balancing innovation and public access.
Cite relevant case law from the jurisdiction in question to support the argument (e.g., US: State Street, Bilski, Alice; UK: Aerotel, Merrill Lynch, Symbian; NZ: Patents Act 2013 guidance).

Potential Discussion Prompts to Prepare Answers

Should business-method patents be allowed given the risk of “floodgates” of low-quality patents? How does the concept of a technical contribution address this concern?
Is it possible for a purely abstract idea to be patentable if implemented with a sufficiently novel technical improvement? Use examples from the cases discussed.
Compare and contrast the US approach (State Street, Bilski, Alice) with the UK approach (Aerotel, Merrill Lynch, Symbian) and NZ approach (Section 11 ICONs). Where do they converge or diverge?
Analyze a hypothetical software-implemented invention: a new algorithm that optimizes energy use in a consumer appliance through a novel control loop. Discuss whether and how it could meet the test for patentability in NZ/UK/US terms.

Endnotes from the Lecture

The instructor emphasizes not to rely on a single test; the analysis depends on multiple factors including actual contribution, technical character, and industrial applicability.
The lecture ends with an exercise: a set of six questions to structure a student’s assignment, followed by an invitation to discuss and defend individual positions in class.
The lecturer notes the evolving nature of case law and invites students to supplement with independent research for their assignments.