T 1550/18 (Denying port write requests/INTEL) 15-06-2023

1. The invention

The application relates to computing platforms, such as personal computers, comprising means to output data from the platform, which data may be sensitive (see description, page 1, lines 10 to 17).

The application aims to prevent a person operating the computing platform from outputting data from the platform (ibid., lines 18 to 20). It achieves this by denying write requests to a selected output port when the port is identified as being in a read-only mode (claim 1, last paragraph).

2. Clarity of claim 1 of the main request; Article 84 EPC 1973

The claimed method being one of "denying" certain write requests is inappropriately characterised by the term "deterring". The board however considers that this has no influence on the clarity of the claimed method as a whole, which is defined by the method steps that follow.

3. Right to be heard; Article 113(1) EPC 1973

3.1 In its response received on 18 December 2017, the applicant had argued (see par. 12 to 15) that D3 did not represent an enabling disclosure, as it was highly ambiguous in its technical teaching and hardly rose above the level of ill-informed speculation (par. 15).

3.2 The appealed decision however does not address or even mention said argument put forward by the applicant.

3.3 The board agrees that D3 does not contain any infor­mation which could be accepted as disclosing the method of claim 1 of the main request.

3.4 In D3, a lay person states (post #1) that his computer will not boot from his standard boot drive, and that his Windows 98SE installation CD does not allow writing to the C: drive, even after switching his C: and D: drive. The error which he gets when trying to copy a file from any drive to any drive, floppy or hard disk, is "Write protect error writing to drive ? - Abort, Retry, Fail?". The system's motherboard is a Gigabyte GA-6VX7-4X.

An attempt to restore the Master Boot Record (MBR) also results in a "Write protect error" (post #3).

One person indicates that a turned on virus protection in the BIOS can prevent writing the MBR (post #4).

After resetting the CMOS, the original poster's system works again (post #5)

3.5 It is evident to the board that D3 only discloses that, in some cases, on a computer with the indicated mother­board, floppy and hard disk drives can effectively become "write protected", and that this situation could possibly be reversed by resetting the CMOS.

D3 further contains an indication that an activated virus protection in the BIOS might prevent writing the Master Boot Record. D3 contains however no disclosure of such a virus protection mechanism.

3.6 Although D3 might be accepted as disclosing that an operation involving a write request to a particular ("selected") port has failed for unclear reasons under undefined circumstances, it does not disclose any dedicated method. It certainly does not disclose a method for denying or allowing write requests, let alone write requests to an output port on the basis of identifying the output port to be in a read-only mode. D3 also does not specifically disclose any output port.

3.7 According to the board, a statement from a user that he gets an error "Write protect error writing drive c:" does not imply that the error message was produced by any particular method, let alone a "method of deterring output" (see reasons for the appealed decision, point 11.1, second paragraph).

3.8 D3 does not disclose a BIOS, let alone a BIOS which could be equated with a driver filtering write requests to selected output ports of a computing platform (ibid., third paragraph). D3 merely contains a statement from a participant in the discussion that the virus protection setting in the BIOS on the original poster's computer can prevent writing a Master Boot Record (MBR). The virus protection scheme itself is however not disclosed, and in any case an MBR is a specific part of a bootable disk, not the connector to which the disk is attached.

3.9 The board further holds that one cannot equate a state­ment from a user that he attempted to install Windows with a disclosure of a driver receiving a write request to a selected output port (ibid., fourth paragraph).

3.10 Equally, a statement from the user that he receives a write protection error (which the appealed decision speculates is due to virus protection being enabled in the BIOS) does not disclose a method having been carried out, let alone one denying a write request when a selected output port specified in the write request is identified as being in a read-only mode (ibid., fifth paragraph).

3.11 Finally, a statement from a user that resetting the CMOS re-established the pre-existing situation only discloses that resetting the CMOS could make non-writable drives writable again. It does not disclose allowing a write request when a selected output port specified in the write request is not identified as being in a read-only mode (ibid., sixth paragraph).

3.12 The board therefore considers that (1) D3 does not disclose the subject-matter of claim 1 of the main request and (2) the appealed decision has not addressed the applicant's reasoning in this respect.

3.13 In analogy to catchword 2 of R 10/18, this board con­siders that a department of first instance is pre­sumed to have taken into account a party's submissions that it did not address in the reasons for its deci­sion, meaning that it, first, took note of them and, second, considered them, i.e. assessed whether they were re­le­vant and, if so, whether they were correct. An excep­tion may apply if there are indications to the contra­ry, e.g. if a department of first instance does not address in the reasons for its decision submissions by a party that, on an objective basis, are decisive for the outcome of the case.

In the present case, as the above analysis has shown, arguments from the applicant were disregarded that, on an objective basis, were decisive for the outcome of the present case. Thereby, Article 113(1) EPC 1973 was infringed.

3.14 The board further sees no reason, starting from the arguments put forward in the appealed decision and considering all documents cited thus far, to judge that the present main claim is not allowable.

3.15 In particular, the board points out that the Gigabyte GA-6VX7-4X motherboard mentioned by the original poster in D3 uses an AMI BIOS (see D7, page 5), which does contain a "virus protection" setting. However, firstly this "virus protection" does not prevent writing to the connector of a hard disk drive, but only displays a war­ning (which can be ignored) that a program attempts to write the boot sector or partition table of a hard disk drive (see D7, top of page 50).

3.16 Even such motherboard or such BIOS is therefore rela­tive­ly distant from the subject-matter of claim 1 of the main request.

A "firewall" with egress or outbound filtering would seem to be closer to the claimed subject-matter. No document describing a firewall was however cited during the search or examination procedure. Furthermore, an inventive step reasoning based on such a document would require a different kind of reasoning than was used in the appealed decision, with no certainty that lack of inventive step could be proven even starting from such document.

3.17 The board therefore holds that not only was the appli­cant's right to be heard infringed (Article 113(1) EPC 1973) but also would the first instance decision likely have been different if the applicant's right to be heard had been respected. There was thus a causal relationship between the infringement of the right to be heard and the decision handed down in the case.

The infringement consequently is considered to constitute a substantial procedural violation justifying the reimbursement of the appeal fee (Rule 103(1)(a) EPC) and a fundamental deficiency requiring, in the absence of special reasons for doing otherwise, an immediate remittal of the case to the department of first instance without a decision on the merits (Article 11 RPBA 2020).