I. Patentability
  1. Home
  2. Legal texts
  3. Case Law of the Boards of Appeal
  4. Case Law of the Boards of Appeal of the European Patent Office
  5. I. Patentability
  6. D. Inventive step
Print
Facebook Twitter Linkedin Email

D. Inventive step

Overview

D. Inventive step

You are viewing the 9th edition (2019) of this publication; for the 10th edition (2022) see here

1.Introduction
2.Problem and solution approach

3.Closest prior art

3.1.Determination of closest prior art in general
3.2.Same purpose or effect
3.3.Similarity of the technical problem
3.4.Most promising starting point
3.4.1General
3.4.2Most promising springboard
3.5.Further criteria for determining the closest prior art
3.5.1Defective disclosure
3.5.2Confidential disclosure in the application
3.5.3Speculative character
3.5.4Old prior art documents
3.5.5Improvement of a production process for a known product
3.6.Consequences of choosing a certain starting point

4.Technical problem

4.1.Determination of the technical problem
4.2.Alleged advantages
4.3.Formulation of the technical problem
4.3.1No pointer to the solution
4.3.2Problem formulated in the patent application as starting point
4.3.3Formulation of partial problems – lack of unity
4.4.Reformulation of the technical problem
4.4.1General
4.4.2Subsequently invoked technical effect
4.5.Alternative solution to a known problem
4.6.Solving a technical problem – post-published documents
5."Could-would approach"
6.Ex post facto analysis

7.Expectation of success, especially in the field of genetic engineering and biotechnology

7.1.Reasonable expectation of success
7.2.Try and see situation

8.Skilled person

8.1.Definition of the skilled person
8.1.1Definition
8.1.2Competent skilled person – group of people as "skilled person"
8.1.3Definition of the person skilled in the art in the field of biotechnology
8.1.4Identification of the skilled person in the case of computer-implemented inventions
8.2.Neighbouring field
8.3.Skilled person – level of knowledge
8.4.Everyday items from a different technical field

9.Assessment of inventive step

9.1.Treatment of technical and non-technical features
9.1.1Technical character of an invention
9.1.2Inventions having both technical and non-technical features
9.1.3Problem and solution approach when applied to "mixed" inventions
a)General issues
b)The Comvik approach
c)Non-technical features and technical contribution
d)Non-technical features and interaction with technical subject matter
e)Technical implementation of excluded subject-matter
9.1.4The aim to be achieved in the formulation of the technical problem
9.1.5Credible technical effects
9.1.6Assesment of features relating to a presentation of information
a)Mental activities based on data visualisation
b)Display of data and user preferences
9.1.7Assesment of features relating to meta methods for software production
9.1.8Assesment of features relating to mathematical algorithms
9.2.Combination invention
9.2.1Existence of a combination invention
9.2.2Partial problems
9.3.Combination of teachings
9.4.Technical disclosure in a prior art document
9.5.Features not contributing to the solution of the problem
9.6.Substitution of materials – analogous use
9.7.Combination of documents
9.8.Chemical inventions
9.8.1Problem and solution approach in chemical inventions
9.8.2Structural similarity
9.8.3Broad claims
9.8.4Intermediate products
9.8.5Predictable improvements resulting from amorphous forms as compared to crystalline forms
9.8.6Synergistic effects
9.9.Equivalents
9.10.Selection inventions
9.11.Problem inventions
9.12.New use of a known measure
9.13.Obvious new use
9.14.Need to improve properties
9.15.Disclaimer
9.16.Optimisation of parameters
9.17.Small improvement in commercially used process
9.18.Analogy process – envisageable product
9.19.Examples of lack of inventive step
9.19.1Foreseeable disadvantageous or technically non-functional modifications
9.19.2Technical standards
9.19.3Reversal of procedural steps
9.19.4Purposive selection
9.19.5Automation
9.19.6Enhanced effect
9.19.7Simplification of complicated technology
9.19.8Choice of one of several obvious solutions
9.19.9Several obvious steps
9.19.10Selection from obvious alternatives
9.19.11Putting the closest prior art device into practice
9.19.12Animal testing and human clinical trials

10.Secondary indicia in the assessment of inventive step

10.1.General issues
10.2.Technical prejudice
10.3.Age of documents – time factor
10.4.Satisfaction of a long-felt need
10.5.Commercial success
10.6.Market competitors
10.7.Simple solution
10.8.Surprising effect – bonus effect
10.9.Comparative tests
New decisions
T 2825/19

Assessment of technicality of programs for computers: "further technical considerations" in the sense of opinion G 3/08

T 2058/18

the (technically) skilled person might be considered a multilingual person but not normally a linguist (Reasons 3.13.7).

T 1408/18

Ein Geschäftsmann, der ein Produkt anbieten möchte, welches die Durchführung einer Transaktion mit nur einem Endgerät ermöglicht, würde vorgeben, dass diese erst nach einer Autorisierung durch den Benutzer ausgeführt wird und auch, dem Trend der Zeit entsprechend, dass es wünschenswert wäre, wenn der Benutzer alle erforderlichen Eingaben auf seinem Smartphone vornehmen könnte. Demgegenüber fällt die Verwendung eines TAN-basierten Verfahrens einschließlich der Frage, wie eine sichere Übertragung der TAN ermöglicht werden kann, in die Sphäre des technischen Fachmanns. Denn ausgehend von einer traditionellen PIN basierten Passwort Authentifizierung bildet die Verwendung einer TAN, das heißt eines Einmalpasswortes, eine zweite Sicherheitsebene. Die damit verbundene Interaktion von zwei Applikationen und Kommunikationskanälen zum Erhalten und Bereitstellen einer TAN führt zu einer Zwei-Faktor-Authentisierung, die eine erhöhte Sicherheit gewährleistet. Damit liegen dem TAN-Verfahren unabhängig von seiner konkreten Anwendung technische Überlegungen zugrunde, die über das hinausgehen, was von einem Geschäftsmann an technischem Verständnis erwartet werden kann (vgl. hierzu auch T 1082/13 - Computer implemented system offering replacement services for applying tax legislation/SAP, Entscheidungsgründe 4.8, und T 2455/13 - Überwachung von Kapitalunterlegungshöhen bei Risikoereignissen/SWISS RE, Entscheidungsgründe 3.10 bis 3.12 sowie Orientierungssatz)(siehe Entscheidungsgründe 6.2).

T 755/18

If neither the output of a machine-learning computer program nor the output's accuracy contribute to a technical effect, an improvement of the machine achieved automatically through supervised learning to generate a more accurate output is not in itself a technical effect

T 686/18

Zur Berücksichtigung einer in der Beschreibung des Patents erwähnten Aufgabe, welche die beanspruchte Lösung vorwegnimmt, bei der Formulierung der zu lösenden technischen Aufgabe (Siehe Punkte 3.14 bis 3.19 der Gründe).

T 161/18

1. Die vorliegende, auf maschinellem Lernen insbesondere im Zusammenhang mit einem künstlichen neuronalen Netz beruhende Erfindung ist nicht ausreichend offenbart, da das erfindungsgemäße Training des künstlichen neuronalen Netzes mangels Offenbarung nicht ausführbar ist.

2. Da sich im vorliegenden Fall das beanspruchte Verfahren vom Stand der Technik nur durch ein künstliches neuronales Netz unterscheidet, dessen Training nicht im Detail offenbart ist, führt die Verwendung des künstlichen neuronalen Netzes nicht zu einem speziellen technischen Effekt, der erfinderische Tätigkeit begründen könnte.

T 116/18

1. Die vorliegende, auf maschinellem Lernen insbesondere im Zusammenhang mit einem künstlichen neuronalen Netz beruhende Erfindung ist nicht ausreichend offenbart, da das erfindungsgemäße Training des künstlichen neuronalen Netzes mangels Offenbarung nicht ausführbar ist.

2. Da sich im vorliegenden Fall das beanspruchte Verfahren vom Stand der Technik nur durch ein künstliches neuronales Netz unterscheidet, dessen Training nicht im Detail offenbart ist, führt die Verwendung des künstlichen neuronalen Netzes nicht zu einem speziellen technischen Effekt, der erfinderische Tätigkeit begründen könnte.

T 1861/17

Zum Verhältnis zwischen "subjektiver" und "objektiver" technischer Aufgabe: siehe Punkt 3.4 der Entscheidungsgründe.

T 1234/17

However, the question is whether the mere idea of mapping this acceleration data to gait category is technical, involving any technical considerations or having any overall technical effect. This question arises in many inventions that involve mappings and algorithms. In T 1798/13 (Forecasting the value of a structured financial product/SWISS REINSURANCE COMPANY LTD), points 2.7 to 2.9, the present Board essentially held that it was not enough that an algorithm makes use of a technical quantity in the form of a measured physical parameter (weather data). What matters is whether the algorithm reflects any additional technical considerations about the parameter, such as its measurement. In that case there were none. This was contrasted with T 2079/10 (Steuerung von zellulär aufgebauten Alarmsystemen/SWISSRE) where the invention was seen to lie in the improvement of the measurement technique itself, which involved technical considerations about the sensors and their positions. Such a situation is conceivable in the present case, if the algorithm were to somehow enhance the input data using considerations of e.g. the placement of the sensors. However, the claim only specifies that the data "includes a time series of acceleration vectors" and that this data is "analyzed". There are no further details that could constitute technical considerations about the data or the sensors. (See points 2.11 to 2.13 of the reasons)

T 905/17

No need for a hint to the claimed solution in the closest prior art (see point 3.2.3)

T 787/17

Rechtfertigung der Wahl des Ausgangspunkts zur Prüfung der erfinderischen Tätigkeit (siehe Punkt 5.1 der Entscheidungsgründe).

T 575/17

a) Soll ein Standard-Verfahren oder -Produkt geschützt werden, so muss definiert werden oder durch die Gesamtoffenbarung eindeutig klar sein, auf welchen anerkannten Standard sich das Verfahren oder Produkt bezieht. (Gründe 4.1.4)

b) Gibt es in den gesamten Anmeldeunterlagen keine direkte oder plausible Offenbarung, wie die erwünschte Wirkung der Erfindung erzielt wird und warum durch die beanspruchten Merkmale die Aufgabe gelöst wird, dann kann die Wirkweise auch durch die Lehre von anderen (vorveröffentlichten) Dokumenten abgeleitet werden. (Gründe 5.4.4)

T 2314/16

The specification of the business method ended with how to determine the reward distribution ratio. The features of dividing the advertisement display area into partial areas and allocating each partial area to a user such that when the partial area is clicked on the user gets a reward, were based on technical considerations of the web page system. It was not motivated by any business considerations.

...

In order to come up with this idea, one needs to understand how a web site is built, and in particular how an image map works. Thus, this feature cannot be part of the non-technical requirements. Instead it is part of the solution that has to be evaluated for obviousness. (See point 2.10 of the reasons)

T 2147/16

The mere assumption that an algorithm is optimised for the computer hardware and may have a technical contribution is not sufficient. The implementation of an algorithm in a method for filtering spam messages must have a proved further technical effect or specific technical considerations; such further technical effect must be specifically and sufficiently documented in the disclosure of the invention and be reflected in the claim wording; the algorithm must serve a technical purpose.

T 1684/16

The fact that the skilled person is taught in the prior art to investigate polymorphs in order to isolate the crystalline form having the most desirable properties is in itself not necessarily sufficient to consider a specific polymorphic form having a certain desired property obvious (see point 4.3.4 of the Reasons).

T 1450/16

In the application of the problem-solution approach for the assessment of inventive step, the person skilled in the art within the meaning of Article 56 EPC enters the stage only when the objective technical problem has been formulated in view of the selected "closest prior art". Only then can the notional skilled person's relevant technical field and its extent be appropriately defined. Therefore, it cannot be the "skilled person " who selects the closest prior art in the first step of the problem-solution approach. Rather, this selection is to be made by the relevant deciding body, on the basis of the established criteria, in order to avoid any hindsight analysis (see point 2.1.4 of the Reasons).

T 1294/16

Selection of the "closest prior art": see point 5. RPBA 2020 Article 13(1) and (2): see points 15 to 20. Technical effects: see points 24 to 26 and 35.

T 184/16

Plausibility - (points 2.1 to 2.8, 7.2 and 11)

T 2081/15

Plausible argument of the appellant about the choice of specific, non-obvious hardware implementation, in favour of an inventive step over the prior art (Article 56 EPC).

T 1601/15

Der Fachmann bedarf keiner Anregung, um sein Fachwissen zur Anwendung zu bringen (siehe Punkt 3.5 der Entscheidungsgründe)

T 1148/15

see sections 3 to 6

T 984/15

As to the definition of the skilled person for the assessment of inventive step and the interpretation of technical specifications (such as telecommunications standards): see points 2.2 and 2.7 of the Reasons.

T 919/15

Plausibilität und Berücksichtigung nachgereichter experimenteller Daten im Rahmen der erfinderischen Tätigkeit (siehe Entscheidungsgründe, Punkte 5.5 und 5.6)

T 314/15

selection of the closest prior art - see Reasons 8, 8.1 - 8.4

T 1749/14

The notional business person might come up with the abstract idea of avoiding the customer having to provide PIN and account information to the merchant. The invention however requires a new infrastructure, new devices and a new protocol involving technical considerations linked to modified devices and their capabilities as well as security relevant modifications of the transfer of sensitive information using new possibilities achieved by the modifications to the previously known mobile POS infrastructure. This goes beyond what the notional business person knows and concerns technical implementation details (how to implement) which are more than a straight-forward 1:1 programming of an abstract business idea. (See point 5 of the reasons). This is in the sphere of the technical expert and subject to the assessment of inventive step (see T 1082/13).

T 1472/14

Was der beanspruchte Gegenstand leistet ist lediglich, anthropometrische Daten in einer Datenbank so zu organisieren, dass diese in standardisierter Form oder in Form statistischer Kennwerte zur Abfrage über eine Kommunikationseinrichtung bereitgestellt werden. Der Anspruchs­gegenstand betrifft nur Auswertungsergebnisse, auch wenn solche im Rahmen einer Zweckangabe zur Produktherstellung gesendet werden. Es erfolgt keine Kontrolle des Betriebs einer Herstellungsanlage, sondern es werden lediglich Produktdaten bereit gestellt. Die Kammer bezweifelt, dass das Ziel der Anthropotechnik mit einer Gestaltung der Schnittstelle zwischen Mensch und Maschine hier relevant ist. Die Kammer erkennt in dem beanspruchten Verfahren keinen technischen Effekt, der über die reine naheliegende Automatisierung einer abstrakten Idee zur Standardisierung hinausgeht (vgl. Entscheidungsgründe, Punkt 7).

T 1218/14

The requirement in G 1/03 that an accidental novelty-destroying disclosure has to be completely irrelevant for assessing inventive step is to be understood not as an alternative, or additional criterion, but as a consequence of the criterion that, from a technical point of view, said disclosure is so unrelated and remote that the person skilled in the art would never have taken it into consideration when making or working on the invention (points 2 and 7).

T 737/14

The proper application of the COMVIK approach requires a thorough analysis of the business constraints when formulating the problem to be solved before investigating what the skilled person would have done to solve it. The failure to reflect all aspects of the business method in the problem to be solved led the examining division to argue unconvincingly that the inconvenient distinguishing feature of authorising the access terminal was an alternative whose choice was governed by unspecified business constraints (see reasons 4.2).

T 550/14

The appellant's wish for the Board to define criteria that the examining division should use to prove that a feature is not technical is tantamount to defining the term technical, which the Boards have consistently declined to do. However, as stated in e.g. T 2314/16 - Distributing rewards/RAKUTEN at points 2.6 to 2.8, over the years the case law has provided guidance on the issue of technicality. Recently, the Board has tended to use the framework for discussion given in the CardinalCommerce decision (T 1463/11 - Universal merchant platform/CardinalCommerce) to help classify whether borderline features of a claim are on the technical or the non-technical side. It is thus clear that some discussion can and ought to take place. However, rather like objections against added subject-matter, one is essentially trying to prove a negative which tends to be a rather short exercise. On the other hand, the appellant is trying to prove a positive which involves more argument. Thus an objection from the division should probably start with a prima facie assertion that the feature in question is non-technical, perhaps because it is in one of the exclusions listed in Article 52(2) EPC, or a related or analogous field. If this is uncontested then this would be enough. However the Board considers that it is then up to the appellant to provide arguments why there is a technical effect or that some technical considerations are involved. The division should consider these arguments and give reasons why they are not convincing. As mentioned above, the Board is satisfied that this happened in the present case. One final piece of advice for examining divisions would be where possible to search for and start from a document that already discloses some of the alleged non-technical features, thus avoiding the discussion for these features (see for example, T 756/06 - Displaying a schedule/FUJITSU, point 5 or T 368/05 - Integrated account/CITIBANK, point 8). (See points 3.3 to 3.5 of the reasons)

T 232/14

The Board judges that using ranges of unit identifiers to label a number of (consecutive) unit identifiers of manufactured items is, at the level of generality at which it is claimed, on the business side of the line between technical and non-technical subject-matter (see e.g. T 144/11 - Security rating System / SATO MICHIHIRO, points 2.1, and 3.6 to 3.9).(See point 2.5 of the reasons) The ranges of unit identifiers do have a meaning for the business person. They correspond to batches of units produced on a production line. (See point 2.6 of the reasons) Even if the "determining of ranges of unit identifiers" achieved a technical effect, such as reducing data storage and data bandwidth requirements, it is a matter of routine design for the skilled person, a software programmer or a database expert, based on common general knowledge to store the first and the last element of a list of items, instead of the whole list. (See point 2.9 of the reasons)

T 2455/13

 Auch der nicht-technische Fachmann hat Kenntnis von den Möglichkeiten einer Realisierung von geschäftsbezogenen Konzepten auf netzwerkbasierten Computersystemen. Er kannte zum Prioritätszeitpunkt eine Vielzahl von rechner- und netzwerkgestützten geschäftlichen Prozessen (z.B. im Bereich der Zahlungsprozesse, Materialwirtschaft und auch der Versicherungswirtschaft), um eine Vorstellung davon zu haben, was konzeptionell auf einer abstrakten Meta-Ebene realisierbar ist. Was der nicht-technische Fachmann jedoch nicht weiß ist, wie genau eine Implementierung auf dem Computer erfolgt. Dies liegt in der Sphäre des Programmierers, des technischen Fachmanns, und ist bei der Prüfung auf erfinderische Tätigkeit zu berücksichtigen (vgl. T 1082/13, Entscheidungsgründe 4.8). Sind Merkmale lediglich auf einer abstrakten Meta-Ebene als Module spezifiziert und repräsentieren Funktionen, wie sie der nicht-technische Fachmann in seinem Konzept zugrunde legen würde, so gibt dieser damit auch keine technischen Merkmale vor. Erst durch die Angabe von tatsächlichen Implementierungs­schritten im Anspruch werden diese Module zu technischen Merkmalen qualifiziert (vgl. Entscheidungsgründe 3.10 bis 3.12).

T 1798/13

The "weather" is not a technical system that the skilled person can improve, or even simulate with the purpose of trying to improve it. It is a physical system that can be modelled in the sense of showing how it works. This kind of modelling is rather a discovery or a scientific theory, which are excluded under Article 52(2)(a) EPC and thus do not contribute to the technical character of the invention (see point 2.10ff.).

T 1082/13

1. The assessment of technical character of a claim does not require a reference to the prior art following the established "whole contents approach" (see reasons, point 1.1).

2. A "timeout" condition claimed in general and broad terms that cover non-technical interpretations is in the domain of the non-technical person and part of the requirements specification given to the technical expert for implementation on a computer system (see reasons, point 2.4).

3. The "notional business person", as introduced in T1463/11, is to be interpreted within the framework of the well established COMVIK-approach according to T0641/00. Consequently, the notional business person knows all about the business related requirements specification and knows about the fact that such business related concepts can be implemented on a computer system. The choice of where to do a calculation in a distributed system is not necessarily technical, but can also be driven by administrative considerations. What the notional business person does not know, however, is how exactly it can be implemented on a computer system. This is in the sphere of the technical expert and subject to the assessment of inventive step.

4. When referring to prejudices, it has to be carefully analysed, whether it is actually a technical prejudice or, in fact, a business prejudice (e.g. just a new way of organising a business transaction that goes against traditional ways of organising it - see reasons, point 4.8).

T 2491/12

The claimed invention is not directed to a real-time problem in the sense of improving a technical process, but rather to automation in the sense of making (non-technical) financial information available quickly. This automation is achieved by mapping the financial concept of derivative transactions on a client-server computer system (see reasons, point 8.2).

T 2049/12

See point 5.8.

G 1/19

A computer-implemented simulation of a technical system or process that is claimed as such can, for the purpose of assessing inventive step, solve a technical problem by producing a technical effect going beyond the simulation’s implementation on a computer. For that assessment it is not a sufficient condition that the simulation is based, in whole or in part, on technical principles underlying the simulated system or process. The answers to the first and second questions are no different if the computer-implemented simulation is claimed as part of a design process, in particular for verifying a design.

OJ Supplementary Publications
Case law 2021
Case law 2020

ABl. EPA 2021, Zusatzpublikation 2
OJ EPO 2021, Supplementary publication 2
JO OEB 2021, Publication supplémentaire 2

Case law 2019

ABl. EPA 2020, Zusatzpublikation 4
OJ EPO 2020, Supplementary publication 4
JO OEB 2020, Publication supplémentaire 4

Previous
Next
Footer - Service & support
  • Service & support
    • Website updates
    • Availability of online services
    • FAQ
    • Publications
    • Procedural communications
    • Contact us
    • Subscription centre
    • Official holidays
    • Glossary
Footer - More links
  • Jobs & careers
  • Press centre
  • Single Access Portal
  • Procurement
  • Boards of Appeal
Facebook
European Patent Office
EPO Jobs
Instagram
EuropeanPatentOffice
Linkedin
European Patent Office
EPO Jobs
EPO Procurement
X (formerly Twitter)
EPOorg
EPOjobs
Youtube
TheEPO
Footer
  • Legal notice
  • Terms of use
  • Data protection and privacy
  • Accessibility