Return to site

A Close Look at Inventive Step for computer implemented invention

T 0279/21 - DISTRIBUTED TO BOARD CHAIRMEN

· EPO,EPOCaseLaw,COMVIKApproach,ComputerImplementedInventions,InventiveStep

Introduction

The Technical Board of Appeal of the European Patent Office (EPO) rendered its decision in T0279/21, concerning the patent application EP 14734190.3 filed by Swiss Reinsurance Company Ltd. The decision revolved around the inventive step requirement under Article 56 EPC, with a specific focus on the interplay between technical and non-technical elements in computer-implemented inventions. By addressing issues like state-transition-controlled processing, encapsulated data structures, and stochastic rating, the Board reaffirmed the critical importance of distinguishing technical contributions from business or abstract modeling features.

Summary of the Invention

The invention related to a state-transition-controlled processing system for data objects in workflows. This system introduced:

  • Dynamic transitions between process states.
  • Encapsulation of task parameters using "operating tags" that could impose constraints on task execution.
  • A stochastic rating module to guide process transitions.

Unlike traditional workflow engines that often relied on human intervention or predefined steps, this invention aimed to dynamically adjust workflows based on internal and external factors, providing flexibility and reducing reliance on human input.

The applicant emphasized that the encapsulated data structure and stochastic rating module allowed for enhanced process control while ensuring security through controlled access.

Key Legal Points from the Decision

Arguments from the Examining Division

The Examining Division refused the application for lack of inventive step, arguing that:

  • The invention primarily represented abstract modeling and business process concepts, not technical features.
  • Existing prior art (e.g., D1, US 2010/0161558) already disclosed comparable workflow systems, including dynamic task assignment based on object states and user profiles.
  • Implementing such workflow rules was straightforward for a skilled person using routine programming.

Arguments from the Appellant (Patentee)

The appellant countered that:

  • The invention went beyond business process modeling by incorporating technical means such as "operating tags" and a "stochastic rating module."
  • These elements introduced technical solutions for dynamic control and real-time processing, addressing technical problems in decentralized workflow management.
  • The claimed features provided an improvement over prior art, particularly in avoiding the complex folder structures used in D1.

Board’s Analysis

The Board's analysis hinged on the COMVIK approach:

  • The "technical problem" must be formulated based on distinguishing technical features from non-technical ones.
  • "Operating tags" and the stochastic rating module, while novel, did not contribute to technical character. These were seen as reflecting business rules or administrative constraints, which are non-technical in nature.
  • The encapsulated data structure, though a known programming concept, did not impart additional technicality.

The Board cited G 1/19 and T 0894/10 to underline that mere automation of non-technical processes or abstract concepts on a computer does not constitute a technical contribution unless it results in a technical effect beyond standard implementation.

Ultimately, the Board upheld the refusal, concluding that the claimed subject matter lacked an inventive step over D1.

Lessons to Be Learned

Distinction Between Technical and Non-Technical Features

  • For computer-implemented inventions, the EPO strictly evaluates whether claimed features solve a technical problem or merely automate a non-technical process. Elements like "operating tags" must demonstrate how they achieve technical effects beyond routine data handling.

Importance of Technical Contribution

  • The claimed invention must provide a technical contribution that goes beyond known solutions. For example, encapsulation, while useful, is insufficient if it merely implements a known concept without additional technical benefits.

Avoid Reliance on Business Constraints

  • Features that stem from business requirements (e.g., task states, workflow rules) are unlikely to contribute to inventive step unless they lead to a technical advancement.

Crafting Claims with Precision

  • Applicants must clearly define the technical nature of claimed features and ensure that these are sufficiently detailed in the description to avoid interpretation as non-technical abstractions.

Legal Basis and Cited Case Law

  • Article 56 EPC: Assessment of inventive step.
  • COMVIK Approach: Distinction between technical and non-technical features in mixed-type inventions.
  • Case Law:
    • G 1/19: Guidelines for technical character in computer-implemented simulations.
    • T 0894/10: Analysis of workflow representations and their technical contribution.

Conclusion

Decision T 0279/21 highlights the challenges of obtaining patents for computer-implemented inventions, especially those involving workflows or business processes. It reinforces the need for applicants to demonstrate a clear technical effect arising from their claims, beyond routine automation of abstract concepts. This decision serves as a critical reminder for patent practitioners to rigorously assess the technicality of their inventions under EPC standards.

 

Contact

If you have any questions concerning intellectual property issuesor need assistance with patent applications, oppositions, or appeals, please do not hesitate to contact us at Novitech IP. Our team of experienced professionals is here to provide you with expert guidance and support. Reach out to us today to discuss how we can help protect your innovations and navigate the complexities of IP law.

To stay informed about the latest reviewsand updates in IP law, subscribe to our blog. Join our community and receive notifications whenever we publish new reviews and insights on important case law and developments in the field of intellectual property.

Legal Disclaimer

The information provided in this blog post is for generalinformational purposes only and does not constitute legal advice. The summary and analysis of the EPO case are based on publicly available information and are intended to offer insights into the decision and its implications. This content should not be used as a substitute for professional legal advice tailored to your specific circumstances. For advice related to any specific legal matters, you should consult a qualified attorney.