Skip to content

Timo Lagerbjelke

Teknik, juridik & innovation

Menu
  • Mina tankar
  • Arkiv
  • Regelverk att känna till.
    • Data Act
    • DORA (Digital Operational Resilience Act)
    • CLOUD Act
    • GDPR
    • EU 2021/821 (Dual-use)
    • NIS2
    • CRA (Cyber Resilience Act)
    • AI-act
  • Om
Menu

Can Software Be Patented? A Guide Based on European Patent Law

Posted on October 1, 2024December 29, 2024 by Timo Lagerbjelke

As an innovation advisor, I frequently receive questions about whether software can be patented. This is a nuanced topic, especially within the European legal framework. In this blog post, I’ll dive into the conditions under which software can be patented, according to European patent law, and what innovators need to know to navigate this complex area.

Patentability of Software Under European Law

The short answer is: yes, software can be patented under European law, but under specific conditions. The European Patent Convention (EPC), particularly Article 52, states that “programs for computers” are not patentable as such. However, this does not mean all software is excluded from patent protection. For software to be patentable, it must provide a “technical effect” that goes beyond the mere execution of a program.

In other words, it’s not the software code itself that is patentable, but the way it contributes to solving a technical problem. This is where many inventors misunderstand the process. Merely automating a process or executing an algorithm is not enough. The software must produce a tangible, technical improvement—whether it’s optimizing hardware performance, improving communication efficiency, or enhancing system security.

Technical Contribution: The Key to Software Patentability

To be eligible for patent protection, the software must directly contribute to a technical aspect. This technical aspect could involve improving the operation of a machine or system, such as enhancing data processing, managing memory usage in a more efficient way, or improving the interaction between software and hardware. The European Patent Office (EPO) is clear about this requirement.

A well-known case that illustrates this principle is IBM’s patent applications (T 1173/97 and T 935/97), where the European Patent Office confirmed that software could be patented if it provides a further technical effect. In this case, IBM argued that their software improved the efficiency of a computer’s operation. The EPO ruled in favor, establishing an important precedent for the patentability of software in Europe.

5 Things to Consider for Patenting Software

  1. Demonstrate a Technical Effect
    The software must solve a technical problem or enhance a technical process. Make sure your invention clearly explains how it improves technology—whether it’s in terms of speed, resource management, or operational efficiency.
  2. Go Beyond Mere Algorithms
    While algorithms are integral to software, patenting requires more than just the algorithm itself. Your software must show how it achieves a tangible technical result.
  3. Include Hardware Interactions
    Software that directly interacts with hardware, such as controlling a machine or system, has a better chance of being patentable. The closer the software is to technical processes, the stronger the case for patentability.
  4. Check for Prior Art
    Before filing, it’s important to perform a thorough patent search. Ensure that your invention is novel and non-obvious, particularly within its technical context.
  5. Keep Detailed Documentation
    Make sure to document the technical problem your software solves, the technical means by which it solves the problem, and any technical improvements your software offers.

Copyright Protection for Software

It’s important to remember that even if your software doesn’t meet the criteria for patent protection, it is still protected by copyright. Copyright automatically applies as soon as the code is written, giving the author exclusive rights to reproduce, distribute, and modify the software. However, copyright protection does not extend to the functional aspects of the software, such as its technical innovations—this is where patent protection can complement copyright

Böcker

  • Att Konkurrera i AI-Åldern: Mina tankar om en aktuell bok

    Att Konkurrera i AI-Åldern: Mina tankar om en aktuell bok

  • En recension av “The Big Picture” by Sean Carroll

    En recension av “The Big Picture” by Sean Carroll

  • “The Hard Thing About Hard Things” av Ben Horowitz

    “The Hard Thing About Hard Things” av Ben Horowitz

  • “Zero to One” av Peter Thiel och Blake Masters

    “Zero to One” av Peter Thiel och Blake Masters

Vad är…

  • Innovationsrådgivarens roll?

    Innovationsrådgivarens roll?

  • Fullstack-utvecklarens roll?

    Fullstack-utvecklarens roll?

  • IT-paralegals roll?

    IT-paralegals roll?

© 2026 Timo Lagerbjelke | Powered by Minimalist Blog WordPress Theme