9. Appréciation de l'activité inventive

Catchword:

Complementing automatisation with human intervention. Providing means enabling a skilled artisan to actively intervene in an automated process and provide a backup to pre-programmed procedures - Obvious measures - (yes) (Points 2.19 to 2.33)

Catchword:

The board is not convinced that there is a credible increase in the speed of the mapping of the retrieved data to a particular application type over the whole scope of the claim since a plurality of associations/catalogues are implicitly needed in the method in claim 1 compared to the single catalogue used in the acknowledged prior art, and the claim does not specify any implementation for which a speed can be determined over the whole scope of the claim. In the current case, the results of the acknowledged prior art appears to be quite different from that of the invention. The method of claim 1 attempts to identify applications for a database, whereas the prior art attempts to identify data formats for all kinds of applications, i.e. not limited to applications using databases comprising tables. Therefore a speed comparison with the speed of the mapping achieved by the prior art is not meaningful. One question that arises is whether the method of claim 1 has the potential to cause technical effects. But the mapping and display of the data record in a respective column of the user interface resulting from the claimed method is not specifically adapted for any technical use (see G 1/19, point 94). Since the board does not see any technical effect from the implementation of the claimed method in a computer system derivable over the whole scope of the claim, the claimed subject-matter does not achieve a technical effect over the prior art acknowledged in the application.

Catchword: 

A neural network defines a class of mathematical functions which, as such, is excluded matter. As for other "nontechnical" matter, it can therefore only be considered for the assessment of inventive step when used to solve a technical problem, e.g. when trained with specific data for a specific technical task.

Catchwords: 

No technical effect of the distinguishing features over the disclosure of document D1 can be derived over the whole scope of claim 1 (see decision G 1/19 of 10 March 2021, sections 82 and 95).

Catchword: 

The mere change, by an operator, of the degree of abstraction of a graphical view ("condensation") of a power grid does not credibly assist a user in performing a technical task by means of a continued and/or guided human-machine interaction process within the meaning of T 336/14 and T 1802/13 and thus cannot bring about a technical effect (see points 3.2 to 3.6 of the Reasons).

Catchword:

Die Verbesserung der Nutzerzufriedenheit z. B. bei einer TV-Live-Übertragung ist im Allgemeinen eine nicht-technische, administrative Aufgabe, für die üblicherweise ein TV-Stationsmanager als Fachperson zuständig ist (siehe Gründe 5.6 der Entscheidung).

Catchwords: 

If the claimed non-technical features do not interact with claimed technical features such that they produce a further technical effect, for the assessment of inventive step one may - either include the corresponding aim to be achieved in a non-technical field in the formulation of the problem as part of the framework of the technical problem that is to be solved, - or else take the corresponding business scenario as the starting point for the problem and solution approach (see reasons 3.2.2).

Catchword:

Improved patient compliance to a pharmaceutical formulation cannot be used to establish an overall technical effect if it is the result of a "broken technical chain", namely an alleged chain of technical effects starting with information provided to a patient which is then broken by the patient's mental activities (see points 2.4 and 2.5).

Catchword: 

If non-technical features have both a technical and a non[1]technical effect, the technical effect must be taken into account when assessing inventive step, but the technical effect must be clearly derivable from the application as a whole (Reasons 3.6.4 (1)).

Catchword: 

While a feature might, in certain contexts, be seen as technical, the technical effect of a feature must be assessed as a whole and in the context of the claimed invention (reasons 2.7.4).

Catchword:

The business person sets the framework of the problem to be solved by their business model (insurance conditions) and thus reduces - by setting specific boundary conditions - the degrees of freedom of the skilled computer specialist. The technically skilled person, who has to solve the objective technical problem of implementation, therefore has no latitude in selecting the corresponding (physical) parameters (reasons 3.6.10).

Catchword:

According to the Comvik approach the non-technical features of a claim may be incorporated into a goal to be achieved in a non-technical field. Subsequently, the approach invokes what might be described as the legal fiction that this goal, including the claimed non-technical features, would be presented to the skilled person, who would be charged with the task of technically implementing a solution which would achieve the stated goal. The question whether the skilled person would "arrive" at the non-technical features does not therefore arise, as these features have been made known to the skilled person, as part of the goal to be achieved. The relevant question for the assessment of inventive step is whether it would be obvious for the skilled person to implement a technical solution corresponding to the claimed subject-matter (Reasons, point 3.12).

Catchword:

In case T 625/11, the board concluded that the determination, as a limit value, of the value of a first operating parameter conferred a technical character to the claim which went beyond the mere interaction between the numerical simulation algorithm and the computer system. The nature of the parameter thus identified was, in fact, "intimately linked to" the operation of a nuclear reactor, independently of whether the parameter was actually used in a nuclear reactor (T 625/11, Reasons 8.4). The board is of the opinion that, in the case at hand, no technical effect is achieved by the method's functionality as the method merely produces a test rod pattern (i.e. a fuel bundle configuration) design and data "indicative of limits that were violated by the proposed test rod pattern design during the simulation". Contrary to case T 625/11, no parameter is identified that is "intimately linked to" the operation of a nuclear reactor. A rod pattern design appears to have non-technical uses such as for study purposes. These are "relevant uses other than the use with a technical device", and therefore a technical effect is not achieved over substantially the whole scope of the claimed invention (G 1/19, points 94 and 95). The data "indicative of limits that were violated by the proposed test rod pattern design during the simulation" do even not, or at least do not entirely, reflect the physical behaviour of a real system underlying the simulation (see G 1/19, point 128). The board notes that, due to the breadth of the wording of claim 1 of the main request, the obtained rod pattern design might violate any number of limits by an almost unlimited amount. Hence, this is not an "exceptional case" in which calculated effects can be considered implied technical effects (see decision G 1/19, points 94, 95 and 128).

Catchword:

The appellant argued that the claimed features relating to the abstract business concept neither could have been provided by the business person to the technical expert for programming, nor would the technical expert have corresponding knowledge starting from a networked standard computer system. The appellant thereby alleged that there was to be considered an imaginary third person who came up with the concept of the invention to be implemented on a computer system. The Board notes that when assessing inventive step in the field of computer implemented business related inventions following the COMVIK approach and the corresponding case law, there is no room for such a third expert. When analysing the features of a claim and answering the question of whether they provide a technical contribution, each such feature has to be judged to be either a contribution of the technical expert or of the non‑technical business person in order to conclude whether there is an inventive technical contribution.

Catchword:

Während eine Fachperson im Allgemeinen Dokumente nicht kombinieren würde, wenn dies zu einem Verzicht auf eine wesentliche Funktion der Erfindung im nächstliegenden Stand der Technik führen würde, gilt dies in der Regel nicht für Kombinationen, bei denen ein wesentliches Merkmal durch ein dieselbe Funktion erfüllendes alternatives Merkmal ersetzt wird (Punkte 1.3.2 und 1.3.3 der Gründe).

Catchword:

An encoding or compression algorithm contributes to the technical character of the claimed compression method if it is used for the purpose of reducing the amount of data to be stored or transmitted (reasons 7).

Catchword: 
If a claim is unduly broadened with respect to the scope of the examples used to illustrate a technical effect, particularly when this broadening concerns the feature/s allegedly providing that effect, the burden of proof might shift back to the proprietor to prove that the effect observed in the examples would also be obtained throughout the entire scope of the claims. If no evidence is provided in this respect, a conclusion may have to be drawn on the basis of plausibility arguments (reasons 2.2.5-2.2.7).

Catchword:

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)

Catchwords: 

A similarity [of the claimed subject-matter] to a business or administrative solution is not a sufficient reason for denyinCatchwords:  A similarity [of the claimed subject-matter] to a business or administrative solution is not a sufficient reason for denying a technical contribution of a claim feature applied in a technical context and involving technical considerations. Put another way, technical considerations in the technical context cannot be negated merely on the basis of a non-technical analogy. ... The analogy to a post office, essentially invoked by the contested decision, is used in technical literature in order to describe functionality of the transport layer (layer 4) of the OSI model. However, in the Board's view, it would not be sound to assert, only based on this analogy, that communication protocols implementing this layer's functionality lack technical character. (See points 3.2.7 and 3.2.8 of the reasons).

Catchword:

In the Board's judgement it is part of the non-technical requirement specification to keep keys (be it analog or electronic keys) away from people one does not trust. This does not require technical considerations of a technically skilled person. The Board does not consider this to be a technical difference, but to be an administrative consideration within the sphere of a business person when contemplating a secure tender process. It is not regarded as a technical innovation, but a natural choice for the bidders to use individual keys, keep the keys back as long as possible and furnish them as late as possible. And even if this was considered technical, it would, in the Board's view, be obvious to do so. Furthermore, the Board considers that implementing a functionality in the networked e-tender system corresponding to D1 would be, at the claimed level of generality, obvious in view of the above business related requirement specification. The Board notes that the implementation is claimed in functional terms and neither the claim nor the application as a whole provide details on how encryption/decryption is achieved on a technical level. The application apparently relies in this respect on the skilled person's common general knowledge. The Board notes in this regard that if providing necessary software and data structures were beyond the skilled person's skills, the invention would not be sufficiently disclosed (Article 83 EPC). Even if the appellant is correct that using different keys for different bidders is a difference over D1, this would in the Board's view imply - in the light of bidders creating their own individual keys for unlocking/decrypting being obvious - that the keys of different bidders are different, too. Therefore creating individual keys/pass-phrases would inherently require the use of multiple keys for implementation. (See points 4.2 to 4.4 of the reasons)

Catchword:

Claim not allowing a distinction between the ingredients which prevent obesity and those which do not prevent or can even induce it. Identification of the protein hydrolysate as an active ingredient for preventing obesity not distinguishing the claimed subject-matter from the disclosure of the prior art. See reasons, points 1.4 to 1.8.

Catchword: 
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)

Catchword:

Application of decision G 1/19 to
- simulation methods (Reasons, point 2)
- design methods (Reasons, point 4)
- measurement methods (Reasons, point 7)