In the rapidly shifting landscape of technology and innovation, software has become the lifeblood of progress. From smartphones to AI systems and embedded controllers in machines, software is omnipresent. Yet, when it comes to patent protection for software in Europe, the legal terrain is anything but straightforward.
This article explores the evolution of software patentability in Europe, focusing on key decisions by the European Patent Office (EPO), current examination guidelines, and the divergence in national practices.
The Legal Landscape: Software and the EPC
At the heart of the European patent system lies the European Patent Convention (EPC). Article 52(2)(c) EPC famously excludes “programs for computers” from patentability “as such.” However, the phrase “as such” has created room for legal interpretation, allowing the EPO to develop a body of case law that permits certain types of software-related inventions—particularly those with technical character.
Milestones in EPO Jurisprudence
Let’s look at some pivotal decisions that shaped this legal doctrine.
1. G 3/08 – Clarifying Boundaries
In 2008, the President of the EPO referred several questions to the Enlarged Board of Appeal, essentially asking for clarification on diverging decisions regarding computer-implemented inventions.
Outcome:
The Board in G 3/08 ruled that there was no divergence significant enough to require unification, and thus did not answer the substantive questions. However, the decision emphasized that software is patentable if it contributes to the technical character of an invention.
👉 Takeaway: Merely being implemented on a computer is not enough. There must be a technical contribution beyond standard computing.
2. G 1/19 – Simulations and Technicality
In 2019, a referral came from the Board of Appeal in case T 0489/14, concerning the patentability of simulations.
Key issue: Can a computer-implemented simulation of a physical system be considered a technical invention?
Decision in G 1/19 (March 2021):
The Board ruled that simulations can be patentable only if they contribute to the technical character of the invention—for example, if they are part of a technical process or if their output affects physical reality.
📌 Example: A simulation that improves the design of an aeroplane wing by feeding data into a real-world manufacturing process may have a technical character. But a simulation for pure financial modeling would not.
The COMVIK Approach: The Current Standard
The EPO examination of computer-implemented inventions now primarily follows the COMVIK approach (from decision T 641/00).
Key elements:
- Inventions are assessed by their technical features.
- Only features that contribute to the technical solution of a technical problem are considered for inventive step.
This creates a filter: non-technical features (e.g., pure business rules or abstract mathematics) are ignored when assessing whether the invention is non-obvious.
✅ What qualifies as technical?
- Controlling an industrial process
- Processing physical signals
- Improving computer functioning (e.g., memory usage, data processing speed)
❌ What doesn’t?
- Running a business faster
- Automating tax calculations
- Ranking posts on social media using a preference algorithm
National Divergences in Europe
While the EPO has developed a relatively consistent approach, national courts and offices in Europe sometimes diverge:
- Germany generally aligns with the EPO, but its Federal Court of Justice (BGH) decisions (e.g., “Dynamische Dokumentengenerierung”) occasionally differ on where to draw the line of technicality.
- UK courts, following the Aerotel/Macrossan test, tend to be more conservative, often rejecting patents that would be allowed at the EPO.
- France and Italy lean heavily on EPO practice, but still allow for independent assessment.
This fragmentation creates uncertainty, especially for startups and SMEs aiming to protect their software inventions across Europe.
Real-World Example: Patentable or Not?
Consider two software applications:
- Example A: A logistics app that calculates the fastest delivery route using a new mathematical model.
❌ Likely not patentable, unless it results in technical control over vehicle movement or integrates with sensors. - Example B: A machine learning algorithm that optimizes engine control parameters to reduce fuel consumption.
✅ Likely patentable, as it has a direct technical effect on a physical process.
Conclusion: A Moving Target
The legal evolution of software patents in Europe reflects a balancing act: rewarding true technological innovation while avoiding monopolization of abstract ideas or business methods.
As technology evolves, especially with the rise of AI, quantum computing, and cloud-based systems, the boundaries of “technical character” will continue to be tested. Inventors and practitioners must stay alert to new jurisprudence and be careful in how they draft claims, always emphasizing the technical contribution.
Further Reading and References
- EPO Guidelines for Examination – https://www.epo.org/law-practice/legal-texts/guidelines.html
- G 3/08 decision – Enlarged Board of Appeal
- G 1/19 decision – Enlarged Board of Appeal
- T 641/00 (COMVIK) – Board of Appeal
- UK IPO Manual of Patent Practice – https://www.gov.uk/guidance/manual-of-patent-practice-mopp
- Case law of the Boards of Appeal of the EPO – 10th Edition (2022)