CASELAW-EPO - reviews of EPO Boards of Appeal decisions

T 0045/24-An allegedly optional feature which turned out to be essential

chat_bubble 1 comments access_time 4 minutes

EP 3 280 251 B1 relates to  a system for intelligent watering that includes components configured to facilitate easy interface and operation.

Brief outline of the case

The OD decided that claim 1 as granted lacked N over D7=US2014/0039697, a document not mentioned on the ISR established by the EPO. The patent was maintained according to AR1d.

The board decided that all the requests on file were either not compliant with Art 123(2) or not admissible. The patent was thus revoked.

The case is interesting as the board held that claim 1 as maintained infringed Art 123(2).

The OD’s decision

The opposition division found that, owing to the use of “may” in paragraph [0056] (“the user terminal may include …”), some features were disclosed as optional rather than as forming a single entity.

The opponent’s point of view

The opponent argued that adding the “user interface” (330) and the “operation manager”(340) to claim 1 without the other components of the system shown in Figure 5, in particular the “memory” (314), “processor” (312) and “device interface” (320), resulted in an unallowable intermediate generalisation.

The application as filed, see in particular paragraph [0021], describes a specific manner of providing operating instructions to “deployed components”, namely in that the owner or operator programs these instructions.

In contrast, feature 1dv) merely specifies that the instructions are “received” by the sensor equipment without an indication of how they are generated or provided. This formulation also encompasses scenarios in which the instructions are provided automatically by another system or device, which is not directly and unambiguously disclosed in the application as filed.

The proprietor’s point of view

The proprietor argued that the “device interface” disclosed in Figure 5 and paragraph [0056] corresponded to the “remote interface” for communication with the sensor equipment recited in claim 1.

In the proprietor’s view, the two interfaces had the same function and were therefore the same feature.

The proprietor argued that, when the application was read as a whole and, in particular, in view of paragraphs [0058] and [0059], the skilled person would understand that the instructions could be provided in several ways, with user input being only one possibility.

Moreover, the term “program” as used in the application did not refer to programming in the narrow sense of writing code but, instead, merely to the provision of instructions by the user.

Therefore, there was no need to incorporate any further feature into claim 1.

The board’s decision

In the board’s view, the skilled person would recognise a technical, functional and structural relationship between the components shown in Figure 5.

Accordingly, a statement in the description suggesting that a feature is merely optional cannot be understood as referring to the embodiment shown in that figure; otherwise, the same reasoning would render the memory and processor optional, which would be inconsistent with the skilled person’s technical understanding of the user terminal disclosed in the application as filed. This is in line with the reasoning set out in T 1878/19, Reasons 1.3.2.

Aside from the absence of any explicit disclosure – in the application as filed – that the remote interface and the device interface are one and the same component, the remote interface in claim 1 as well as in paragraphs [0005] and [0075] is described as being included in the processing circuitry (310).

By contrast, the “device interface” is shown in Figure 5 as a component separate from the processing circuitry and communicating directly with the gateway (40) and the operation manager (340).

Thus, it is not directly and unambiguously derivable from the application as filed that the remote interface and the device interface, despite having overlapping functions, are one and the same component.

The board was of the view that, when reading the disclosure of the application as a whole, it is clear that the instructions to the sensors are programmed by the user, as stated in paragraph [0021]. Paragraphs [0058] and [0059] do not suggest that the instructions may be provided in another way.

For these reasons, the board agreed with the opponent that feature 1dv) infringed Art 123(2).

Comments

The whole description contains a lot of sentences in which the term “may” is used. Throwing “may” into nearly every sentence in the description might in some legal systems avoid being faced with an objection of added matter, but not at the EPO.

In T 532/20, see Catchword, commented in the present blog, the board concluded that features might be prima facie disclosed as being optional, but careful analysis of the disclosure can lead to the conclusion that the features are actually not optional, but essential. If the essential features are not present in the claim, an objection of added subject-matter can be fully justified, as it boils down to an intermediate generalisation.

From T 1203/13, Reasons 2, penultimate §, it is possible to conclude that if everything is optional, nothing is optional.

The boards of appeal have heavily criticised the so-called essentiality test, now three point test, cf. Guidelines H-V, 3.1, but in the present case, and in T 532/20, optional features might be held essential.

T 0045/24

Share this post

Comments

1 reply on “T 0045/24-An allegedly optional feature which turned out to be essential”

Leave a Reply

Your email address will not be published. Required fields are marked *