9.1.3 Problem and solution approach when applied to "mixed" inventions
Overview
You are viewing the 9th edition (2019) of this publication; for the 10th edition (2022) see here |
- 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 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).
- Case law 2019
-
In T 144/11 the board stated that what the board had held in T 1463/11 demonstrated that a careful analysis of which parts of a claimed feature involve a business requirement could help to resolve the grey area between technical and non-technical features. A corollary of this approach, and what is seen in practice, is that a problem of the type "implement the business requirement" will normally never lead to an allowable claim. Either the implementation will be obvious or have no technical effect, or if not, the implementation will have a technical effect that can be used to reformulate the problem essentially to "achieve the effect of the implementation". However, the implementation-type problem is just a starting point that might have to be modified when the implementation is considered. It helps when a technical problem is not apparent at the outset. Examining the business requirements like that and correctly establishing what is to be implemented ensures that all technical matter arising from the idea of the invention and its implementation is taken into account for inventive step. In the board's view, another constraint is that the technical skilled person must receive a complete description of the business requirement, or else he would not be able to implement it and should not be providing any input in the non-technical domain.