The inventions are all about the capacitive testing of yarns or fabric, wherein the dielectric property of a capacitor arrangement is determined.
It became clear from the pleadings that the defendant’s main request in both cases was that the patent be maintained in amended form only. In my understanding, the expert-opinion of the judge-rapporteur had held that the main request in O2016_010 / EP’250 was allowable, but not in O2016_011 / EP’018.
Novelty has not been an issue anymore, in both cases. Only obviousness, undue extension of subject-matter (interim generalisation) and clarity (of the additional feature) have been discussed. D2 (US 4,843,879; referred to in EP’250, ¶) was apparently agreed to be the closest prior art, and was combined in the assessment of obviousness with either D4 or D11 — both of which have unfortunately not been identified.
For me as a chemist, the highlight of the day was the plaintiff’s emotional release:
That’s not chemistry here; it’s physics!
The formulation of the ‘objective technical problem’ was quite a big deal in the hearing. This is what EP’250 says in ¶ (emphasis added):
It is therefore the aim of the present invention to provide a method for the symmetry adjustment of a device for the capacitive examination of a moving elongated textile test sample which does not have the above disadvantages. The device should be simple, fast, cost-effective and, in particular, automatically adjustable.
Now, can automation be considered as the ‘objective technical problem’? In the plaintiff’s view, the ‘in particular’ is an emphasis of the aim of automation. The defendant disagreed: Automation was an add-on, and the other advantages could well be realised without automation. On the funny side, the following example has been used:
She likes flowers, in particular roses.
Now, imagine that the rose-loving woman visits a florist. Which flowers will she recognise first, amidst all the other flowers? The roses, of course!
Compensation of the ‘necessary expenses’ for the assisting patent attorney pursuant to Art. 3 lit. a and Art. 9(2) CostR-PatC was yet another point of discussion. The plaintiff requested reimbursement of about kCHF 45 for each case and argued, that the defendant triggered the additional costs because the amended claims had only been filed with the rejoinder which then had effectively restarted the whole discussion. I did not get the value in dispute, but the presiding judge indicated that kCHF 45 is about twice as much as the amount that would be awarded for legal respresentation, i.e. ‘according to the tariff’ that is based on the value in dispute.
Now, why is that important?
Since O2012_043, the FPC’s practice is that, as a rule, the ‘necessary expenses’ for the patent attorney may well be within the same order of magnitude of the costs for legal representation. But what about nullity cases? A patent attorney could do that on his/her own, without any legal representative; Art. 29(1) PatCA. Compensation would then be awarded according to the tariff for legal representatives; Art. 9(2) CostR-PatC.
The defendant questioned whether costs incurred for the assisting patent attorney are ‘necessary expenses’ at all, on top of the costs for legal representation according to the tariff, if he/she could have done the whole case on his own.
Use of the technical infrastructure in the court room
It is quite hard for the public to follow the arguments when the representatives just argue with acronyms and references. It’s sometimes frustrating, but I got used to it. But still, one of the basic ideas of a public hearing is to give the public the opportunity to follow the proceedings, isn’t it? But how would you even get a glimpse of what is really at stake when the parties only refer to ‘EP’111’ or ‘D1’ or ‘feature 1da’. That’s not information — it’s just noise.
I was very happy that the recent hearing in case S2018_006 was different (see this Blog here): Whenever someone referred to a specific document, the President put the same on the screen for it to be easily recognisable by the whole audience and the judges; projector and screen are fixedly installed in the ceiling anyway (see yellow arrow in the image below). Much appreciated!
But that’s not only great for the audience; I strongly feel that it is also beneficial for representatives when arguing their case. When referring to a certain paragraph in a specific document in your pleadings, or a technical drawing, you always want to make sure that all the judges are on the same page, right? But how would you know that, with the judges sitting on a podium that even has an elevated front side that makes sure that nobody reveals a hand up there, behind the monitors. Yes, there are fixedly installed monitors (green arrows in the above image).
Now, did they all pick up the document that you are upon to discuss? You never know. So, why not actually use the monitors that each judge has in front of him/her, and the projector/screen for the audience, to make sure that everybody sees what you want to be seen? I could not think of any more powerful way to focus the discussion and thoughts on a specific argument.
Unfortunately, it didn’t work out that way in this hearing even though the defendant suggested it. I hope this was for technical reasons only, and does not indicate a general change of practice again.
If in a patent infringement proceeding the plaintiff files before the instructional hearing a reply limited to the defense of the validity and no pleadings take place at the instructional hearing, the plaintiff may submit new allegations of fact, and therefore also amended patent claims, in the completed reply filed after the instructional hearing without having to meet the requirements of art. 229 para. 1 CPC.
Please find some background information about the subject-matter at stake on this Blog here, and a report about the main hearing of 29 October 2018 on this Blog here.
The only independent claim 1 of CH’755 as granted reads as follows:
Durchflussmessfühler (10) mit einem ein zylindrisches Gehäuse (10) definierenden Durchgang mit einer ersten Durchgangsöffnung (13) und einer zweiten Durchgangsöffnung (29); einem im Durchgang des Gehäuses angeordneten Strömungswiderstand (23), welcher das Gehäuse in einen ersten und einen zweiten Gehäuseteil (11 und 27) unterteilt; einer ersten Anschlussstelle (17) mit einer Verbindung zum Innern des ersten Gehäuseteils (11); und einer zweiten Anschlussstelle (19) mit einer Verbindung zum Innern des zweiten Gehäuseteils; dadurch gekennzeichnet, dass die ersten und zweiten Anschlussstellen (17, 19) in einem Abstand voneinander auf dem gleichen Gehäuseteil angeordnet sind.
Inofficially translated to English language:
Flow sensor (10) with a passage defining a cylindrical housing (10) with a first passage opening (13) and a second passage opening (29); a flow resistor (23) arranged in the passage of the housing which divides the housing into a first and a second housing part (11 and 27); a first terminal (17) having a connection to the interior of the first housing part (11); and a second terminal (19) having a connection to the interior of the second housing part; characterised in that the first and second terminals (17, 19) are spaced apart on the same housing part.
Fig. 1 of CH’755 surely helps to understand what the invention is about:
The defendant denied an infringement, and argued for nullity as a plea in defense.
The verbal limitation of the patent
This is what the hn is all about. Imagine a plaintiff / patentee in infringement proceedings who is confronted with a plea for nullity in defense: When is his last chance to formally assert his patent only to a more limited and presumably valid extent?
First, it is important to understand how the FPC conducts the proceedings. If the defendant raises a plea for nullity in his answer to plaintiff’s statement of claim in infringement proceedings, the FPC invites the plaintiff to file a reply which is strictly limited to only the nullity aspects of the case. What follows next is an instructional hearing. In preparation of that hearing, the limitation of plaintiff’s reply to only the nullity aspects is to assure that the court has a single exchange of opinions at hand for both infringement and nullity. If the case moves on after the instructional hearing, it is again up to the plaintiff to complete his reply. Thereafter, the defendant provides the rejoinder re both infringement and nullity. This is the end of the regular exchange of briefs in which the parties can present facts and arguments without the need to comply with Art. 229(1) CPC (novae). However, the plaintiff may of course comment on new allegations and facts presented by the defendant in his rejoinder — within a deadline set by the FPC (typically two weeks, extendable by one further week; see this Blog here), or under the unconditional right to be heard (within 10 days).
The below is an illustrative summary of this chain of events:
Statement of Claim
w nullity plea in defense
re alleged nullity only
Instructional hearing w/o pleadings
re infringement and nullity
re infringement and nullity
on new factual allegations in the rejoinder, if any
Judge rapporteur’s expert opinion
Note the subtitle to the second reply in the above: The decision holds that the plaintiff may present arguments and facts in his second reply after the instructional hearing not only relating to infringement aspects, but rather also to the nullity aspects of the case.
In the defendant’s view, the plaintiff thus had three chances to deal with validity / nullity of the patent, i.e. in his initial statement of claim and both his replies. The FPC disagreed: There is no reason for a plaintiff to deal with nullity in the beginning. How would he even do so in the absence of any knowledge of the defendant’s potential arguments? Thus, the FPC held that both parties had exchanged their views on both aspects of the case for the first time only after plaintiff’s first reply (limited to nullity). With the second reply and the rejoinder, both without limitations re novae, the double exchange of briefs is concluded.
Undoubtedly, an amended claim is to be considered a new fact (decision 4A_543/2017 of the Supreme Court, ¶2.3); as such, it would be an inadmissible novum after the normal exchange of briefs.
The plaintiff ‘verbally limited’ the claim only in his second reply. The defendant argued that this second reply was limited to only infringement aspects; it should only complement the first reply that had already dealt with nullity. Defendant argued that this was established practice at the FPC. Again, the FPC disagreed: There was not an established practice of the FPC in that sense.
Interestingly, the former President Dieter Brändle had apparently indicated in the instructional hearing that the patent could not be asserted in a more limited form any more after the instructional hearing. Defendant argued that it is against good faith if the limitation was now accepted nevertheless. However, the decision holds that it is up to the whole panel of judges to finally rule on admissibility of new facts; Mr. Brändle only gave his personal, preliminary opinion on this issue at that time. When the defendant had been invited to provide his rejoinder, this came along with an explicit note to deal with plaintiff’s reply as a whole, and that the whole panel of judges would finally decide on admissibility of the limitation of the patent. Thus, the defendant had no procedural disadvantage.
On a sidenote, I am wondering what the last point of time would be for a patentee / plaintiff to limit the claim when faced with a full-fledged counterclaim for nullity, i.e. when there are two parallel tracks of claim and counterclaim:
Statement of Claim
Answer re c’claim
Instructional hearing w/o pleadings
on new factual allegations in the rejoinder re c’claim, if any
Judge rapporteur’s expert opinion
Would the plaintiff’s reply after the instructional hearing then be limited to the infringement part, and the final chance to limit the claim be the rejoinder re c’claim? This remains to be seen in a case to come.
General remarks on claim construction
The decision summarises certain key aspects of claim construction in ¶25 (and, later on, in ¶47). I do readily agree with most of it, but stumbled upon the following:
When case-law refers to ‘broadest interpretation’ of claim features,15 the feature must still be capable of fulfilling its purpose in the context of the invention. This means that the claim must not be interpreted under its wording, but also not in such a way that embodiments are covered which do not achieve the inventive effect.
15 FPC, decision O2013_008 of 25 August 2015, ¶4.2 — ‘elektrostatische Pulversprühpistole’ [see this Blog here]
The decision cites ample case-law, but there is no fn in the last sentence. Now, where does that come from? The sentence somehow reminds me of hn 3 of the ‘Spannschraube’ decision of the German Federal Supreme Court, X ZR 85/96 of 2 March 1999. The German Supreme Court had held:
The scope of protection of a European patent cannot be extended to embodiments which wholly (or to an extent which is practically insignificant) waive the success sought by the patent.
However, the Swiss Supreme Court had to assess the same subject-matter shortly thereafter, and explicitly disagreed; 4C.348/1999 of 12 April 2001: What had been considered to be no infringement in Germany, was well an infringement in Switzerland!
The Swiss Supreme Court did not see any reason to deviate from the literal and technically plausible meaning of the feature — even though an explicit object of the patent that had been recited in the specification was not achieved by such embodiments, i.e. the use of very short clamping screws (see EP 0 319 521 B1, col. 1, l. 54-57):
Der Erfindung liegt die Aufgabe zugrunde, eine Rohrschelle der eingangs genannten Art zu schaffen, die sich auch mit einer sehr kurzen Spannschraube gut handhaben und leicht schliessen lässt.
It remains to be seen whether the present decision might indicate a gradual departure from the old Spannschrauben approach of the Swiss Supreme Court.
The claims at stake can be summarized as follows, structured into features:
Flow sensor (10) with
a passage defining a cylindrical housing (10) having a first through opening (13) and a second through opening (29);
a flow resistor (23) arranged in the passage of the housing, which divides the housing into a first and a second housing part (11 and 27);
a first connection point (17) having a connection to the interior of the first housing part (11);
a second connection point (19) having a connection to the interior of the second housing part;
the first and second connection points (17, 19) being arranged at a distance from one another on the same housing part;
claim 4 as granted:
wherein flanges are provided on the first housing part (11) and on the second housing part (27) for connecting the housing parts with flange pressure surfaces (15, 16, 31, 32) are formed;
first variant of claim 10 as granted:
wherein the connections run partly in the flange pressure surfaces,
second variant of claim 10 as granted:
[wherein the connections] exit through the flange pressure surface as openings on the sealing surface side (17, 19, 21, 33, 35, 37) .
Features a) – f) correspond to claim 1 as granted (marked in bold in the above); the whole set of features, i.e. a) – f) and j) – k), corresponds to the claim as limited with plaintiff’s second reply. Don’t get confused by the missing features g) and h): The parties referred to these features in their feature analysis; but they are irrelevant for the present decision since they only relate to dependent claims 2 and 3 which are not at stake.
The decision holds that claim 1 as granted lacks novelty over document E10, i.e. (JP S61-205023); see Fig. 1:
Next, the decision assesses and acknowledges novelty of the more limited claim over E1 (US 6,585,662 B1) which lacks features j) and k). Defendant had also argued that a prior use of the device of E1 had occured (prior use ‘Jones’). However, the decision holds that this prior use does not need to be assessed any further: Defendant had argued that the prior use disclosed a device according to the teaching of E1. Thus, the decision holds that any such prior use would necessarily also have lacked features j) and k).
Moving on to the assessment of obviousness, the decision emphasizes that it is up to the party that alleges nullity of a patent to make the relevant allegations. The court only examines whether the grounds put forward lead to the invalidity of the patent. Even though obviousness is a question of law, the relevant factual assertions must be made by the party that asserts nullity. In the following, therefore, the decision only deals with the assessment of obviousness starting from document E2 that has been referred to as ‘closest prior art’ by the defendant, i.e. US 4,083,245.
Features f), j) and k) are missing in E2.
With E2 as closest prior art, the decision holds that documents E7 (DE 32 25 114 C1, erroneously referred to as DE 32 25 115 C1 in the decision), E8 (US 1,768,563 A) and E9 (JP H03-21735 U) fail to render the limited claim obvious — mainly because these devices are made from metal / intended for use in high pressure applications, contrary to flow sensors in the medical field which are typically made of plastic, using die casting methods.
In sum, the more limited claim that the plaintiff had submitted with his second reply was thus held to be valid.
Defendant most fiercely contested that the adult version of the flow sensors has flange pressure surfaces and, even if there were flange pressure surfaces, that the connections from the connection points to the inside of the first/second half of the housing run partially into or through the flange pressure surfaces. Defendant referred to the computer tomographic images that had been submitted by the plaintiff:
The above figure shows a cross-section through theflanges of the two halves of the housing. The flow resistor which is clamped between the flanges is marked with 23. Identifiers 45 and 47 mark a groove and comb structure. Defendant argued that the gas-tight connection is made exclusively via the groove/comb structure. However, the flange surfaces would not touch each other (red arrows in the above figure); only the planes of the comb and groove that protrude perpendicularly from the flange surface would be in contact (white arrows in the above figure). Defendant argued that this is intentional because it allows flow resistors of different thicknesses to be used without the housing halves having to be designed differently, contrary to the teaching of the patent in suit. Since, by definition, flange pressure surfaces would have to lie against each other under pressure, flange pressure surfaces are missing in the adult version, in the defendant’s view. And even if the area in which the flow resistor is trapped by the flanges (marked with a yellow arrow in the figure above) were still called the ‘flange pressure surface’, no connections would occur there in any case. Defendant referred to the below figure in this respect (with the white squares / annotations added by the court):
The above figure again shows a cross-section of an adult version of the flow sensor. The thin vertical line is the flow resistor; identifier 33 refers to one of the connections to a connection point which seems to end on the right because it runs diagonally in the Z plane. The decision holds that ‘flange pressure surface’ and ‘flange surface’ are used as synonyms in the patent. A flange pressure surface in the sense of the claim is the surface of a flange facing away from the body part to which the flange is attached and serving to connect the body part to another body part, whereby the connection need not necessarily be made over the entire surface.
Thus, the flange pressure surface of the attacked embodiment runs over the entire width of the flange, i.e. in the above figure from point a) to point b). Consequently, the decision holds that the connections from the connection points to the inside of the first/second housing parts also run through the flange pressure surfaces, as can be seen in the figure above.
The decision holds that the defendant may have improved the teaching of the patent in suit, and the improvement might even be patentable. This does not, however, lead out of the scope of protection of the earlier patent (cf. Art. 36 PatA). In sum, the decision holds that the version for adults is literally covered by the limited claim of the patent. Likewise, the version for children is also held to be literally covered by said claim.
Wording of the injunctive relief
The defendant objected to the wording of the request for injunctive relief, for that it is too indefinite and merely recites the wording of claim features that are under dispute between the parties (such as e.g. the term ‘flange pressure surface’). The decision holds that the features are defined in the reasons of the decision beyond any doubt, so that a mere factual check by the competent authorities is well sufficient. Thus, it is neither necessary nor helpful for each and every feature to be defined in the prayer for relief itself.
Again, this reminds me a bit of the German approach where the mere claim wording is typically used in prayers for injunctive relief, and the exact scope is then to be deduced from the reasons of the decision. I do have some symphathy for the FPC’s approach that keeps the verdict clean and simple, with all the potential ambiguities being resolved by way of definitions given in the reasons.
In sum, the defendant was ordered to abstain from further use of the infringing embodiments, and to provide information and accounting concerning the same.
The parties commented on the decision with the following press releases:
The decision is not yet final; an appeal is pending at the Supreme Court.
Aiming high now: Maybe not only in prosecution, but even in litigation therafter!
We are surely not yet there.
For instance, the German Federal Court of Justice (FCJ) has some reservations, as discussed by judge Klaus GRABINSKI here:
The [EPO] Guidelines stipulate that deviation from this strictly schematic approach should be exceptional. The approach serves the interests of objective and predictable assessment in the examination procedure, in which, under Article 18(2) EPC, only the applicant and one member of the examining division are normally involved. Its appropriateness in this context is not to be questioned here; however, for a court procedure conducted on an adversarial basis between two or more plaintiffs and defendants, its suitability is limited.
But what are these reservations?
Firstly, the choice of a (single) closest prior art as the starting point in the assessment of obviousness, in GRABINSKI’s view:
Experience shows that, in nullity proceedings, the plaintiff generally presents several starting points (documents, public prior uses, etc.) in respect of inventive step. The court then has to assess whether the skilled person would actually have selected these starting points. According to the case law of the German FCJ, the choice of a specific starting point for the consideration of inventive step requires particular justification. This can be derived from the skilled person’s endeavour to find, for a specific purpose, a solution better than or different from the solution provided in the prior art. The test can be applied with one or more starting points (documents, public prior uses, etc.). There is no reason to limit the assessment of inventive step from the outset to the “closest prior art”. Otherwise, there is the risk of an inadmissible ex post evaluation of the prior art with regard to what is “closest”.
However, GRABINSKI holds that the EPO’s approach essentially does not differ much (what I believe is true, and I will come back to this in the below):
Ultimately, the same view would appear to prevail in the [then] current Guidelines for Examination. The authors concede, with reference to several decisions of the boards of appeal, that in some cases there are several equally valid starting points for the assessment of inventive step and that, in the event of refusal, it is sufficient to show, on the basis of relevant prior art in respect of at least one solution, that the claimed subject-matter lacks an inventive step. In such a situation, there is no need to discuss which document is “closest” to the invention; the only relevant question is whether the document used is a feasible starting point for assessing inventive step.
The formulation of the objective technical problem is key in the EPO’s problem-solution approach. Admittedly, this involves a somewhat artificial, retrospective approach. But it does so by design and in the interest of legal certainty, for that it be a reliable tool with predictable results. In my perception, the German FCJ takes a somewhat different approach; the problem(s) it typically refers to is/are not the objective technical problem of the problem-solution approach— at least not necessarily; see e.g. the discussion of the FCJ’s decision X ZR 29/15 - Pemetrexed by Rainer ENGELS here.
But be that as it may, I have no reason to blame the German FCJ for its approach. It may or may not be better suitable to avoid hindsight, or to provide legal certainty for users. There is more than one way to skin a cat, and the German FCJ never said to have adopted the EPO’s problem-solution approach.
However, the Swiss FPC did — repeatedly and in no uncertain terms (see e.g. O2015_018, ¶30):
Le Tribunal fédéral des brevets applique l’approche problème-solution développée par l’Office européen des brevets dans le cadre de l’évaluation de l’activité inventive.
The Federal Patent Court applies the problem-solution approach developed by the European Patent Office in the context of the evaluation of inventive step.
Thus, European patent attorneys in civil proceedings at the FPC can just do what they do all day long in proceedings at the EPO, at least in the assessment of obviousness? Actually, this would not come as a complete surprise since the second permanent judge (Tobias Bremi) and 27 of the non-permanent judges have a technological background and are European patent attorneys by training.
But hold on, it’s maybe not that easy.
Clearly, the FPC has the same reservations with respect to the choice of a (single) closest prior art; see O2013_011 in the hn and ¶5.6, with further reference to T 967/97, as well as S2017_001, ¶4.6.
But I feel that GRABINSKI is right in that this is nothing out of the ordinary in EPO practice (as it should be, taking into account the case-law of the Boards of Appeal); it is just that the term closest prior art used in the problem-solution approach might be misleading in that it suggests that this is always just a single document.
But what concerns me in recent times is the concept of a reasonable expectation of success; see this Blog here. The argument that there had been no reasonable expectation of success is easily made and thus frequently seen. And it is always easy to cast doubts in the assessment of obviousness:
Just imagine what could have gone wrong!
What is worse, such arguments cannot be proven wrong: Indeed, life is risky.
Now, what the heck is actually a reasonable expectation in the skilled person‘s eyes?
The EPO Guidelines
The Guidelines are firm instructions to the first instance bodies of the EPO; see the foreword:
As a general rule, parties may expect the EPO to act in accordance with the Guidelines until such time as they – or the relevant legal provisions – are amended. […] In case of diverging decisions of the Legal or Technical Boards of Appeal, EPO examiners and formalities officers will, as a rule, follow the common practice as described in the Guidelines.
More than 160’000 patent applications are filed with the EPO per year. And obviousness is to be assessed for all these applications; Art. 56 EPC.
If the concept of a reasonable expectation of success was of general importance for the daily practice of the first instance bodies at the EPO, one would readily expect it to be addressed in the Guidelines.
But, interestingly, it is not discussed at all — at least not in the chapter on assessment of obviousness.
The term reasonable expectation of success is only mentioned once in the Guidelines, but only a contrario, in the context of novelty of selection inventions in G-VI, 8:
The concept of seriously contemplating, or ‘ernsthaft in Betracht ziehen’ in German, is fundamentally different from the concept used for assessing inventive step, namely whether the skilled person would have tried, with reasonable expectation of success, to bridge the gap between a particular piece of prior art and a claim whose inventiveness is in question (see G-VII, 5.3), because in order to establish anticipation, there cannot be such a gap (T 666/89).
If you follow the link to G-VII, 5.3 in the hope to learn more about the concept of a reasonable expectation of success, you will be disappointed: There is nothing about reasonable expectation of success. G-VII, 5.3 is all about the could-would approach as we all know it. It reads as follows:
[T]he question to be answered is whether there is any teaching in the prior art as a whole that would (not simply could, but would) have prompted the skilled person, faced with the objective technical problem, to modify or adapt the closest prior art while taking account of that teaching, thereby arriving at something falling within the terms of the claims, and thus achieving what the invention achieves (see G‑VII, 4).
In other words, the point is not whether the skilled person could have arrived at the invention by adapting or modifying the closest prior art, but whether he would have done so because the prior art incited him to do so in the hope of solving the objective technical problem or in expectation of some improvement or advantage (see T 2/83).
Hold on a second.
It is worth reading the second paragraph again. The expectation of some improvement or advantage language is taken literally from T 2/83. But did you notice the other alternative?
I don’t know where the wording in the hope of solving the objective technical problem comes from; this inconsistency has already been discussed by discussed by Wooden, Blaseby and Visser recently. It somehow found its way into the Guidelines already back in 2003. But T 2/83 is silent about hope. The could-would approach clearly is not about hope; it is about an expectation.
Anyway, there is nothing about a reasonable expectation of success. It is only about an expectation of some improvement or advantage.
Now, do these terms maybe both mean essentially the same? I.e., is
success only the short for some improvement or advantage; and
the expectation (implicitly) meant to be reasonable in any event?
If so, fine. But wouldn’t it be good to use the same terms when referring to the same things? It’s a land of confusion anyway.
Or are they not the same? If that was the case, then the concept of a reasonable expectation of success just cannot be of any broader relevance for the first instance bodies at the EPO at all. Else, it would surely be referred to in the Guidelines.
Getting confused? Hold on tight, it’s not getting easier …
Learnings from the FPC
Decision S2017_001 in r 4.7 embraces the EPO’s could-would approach recited above. With reference to Kroher (Singer/Stauder, EPÜ, 7th ed., Art. 56, ¶73-74) the decision further holds that the ‘would’ is satisfied if there is a motivation to arrive at the claimed solution and an expectation of success that this solution actually works:
Dass der Fachmann die erfindungsgemässe Lösung effektiv finden würde gilt als gezeigt, wenn aus den Unterlagen ersichtlich ist, dass der Fachmann einen Anlass hatte (‘motivation’), zur erfindungsgemässen Lösung zu kommen, und er eine Erfolgserwartung hatte, dass die erfindungsgemässe Lösung auch funktioniert (‘expectation of success’).
Noteworthy, this does not even require the ‘expectation of success’ to be reasonable, and that the ‘success’ is realistically achievable — at least not explicitly. Kroher did not put it like this. This is what Kroher exactly says (emphasis added):
Zum Could-would Ansatz gehört auch die Wertung, ob für den Fachmann eine angemessene Erfolgserwartung bestand, ob er auf der Grundlage seines Wissens und Könnens realistisch mit einem Erfolg rechnen konnte oder nicht (vgl Rdn 136).161
First, none of the references cited in the fn actually says that the assessment of a reasonable expectation of success is part of the could-would approach. So, where does this come from?
Second, assuming that it really was part of the could-would approach, then how can it be that examiners and opposition divisions of the EPO deal with more than 160’000 cases per year in the absence of any instructions in the Guidelines? An integral part of the could-would approach did not make it into the Guidelines for decades? I can hardly believe that.
Third, the cross-reference to ¶136 in the Kroher chapter exclusively relates to biotech cases. And this is where it belongs — pretty exclusively, in my perception. Actually, the Boards of Appeal of the EPO have come up with the concept of a reasonable expectation of success in biotech cases. Frankly, I am not aware of any non-pharma or non-biotech case where the reasonable expectation of success argument had ever been successfully invoked to establish non-obviousness.
In sum, Kroher’s conclusion is not readily convincing to me, and it is not supported by the references given. I could only agree, again, if the reasonable expectation of success does not mean anything different than the expectation of some improvement or advantage according to the problem-solution approach.
What troubles me is that the FPC’s concise summary in S2017_001 is not just a summary of Kroher, or any other reference cited by Kroher. Rather, it adds further terms and interpretation, and appears to be more harsh in that the terms ‘reasonable’ and ‘realistic’ are just omitted.
[…] the skilled person would have arrived at the invention by adapting or modifying the closest prior art because the prior art incited him to do so […] in expectation of some improvement or advantage (see T 2/83).
In my understanding, the test is fairly easy. The skilled person could have done a lot. What the could-would approach is all about is to sort out what he actually would have done. Nothing more, nothing less. It does so by requiring prompters (sometimes referred to as pointers) or incentives in the prior art for the skilled person to arrive at the invention.
But be that as it may, a motivation in its broadest sense (according to Google) is
a reason or reasons for acting or behaving in a particular way.
Thus, I feel it is fair to say that the motivation referred to in S2017_001 is nothing more than the prompter or incentive. No need to fiddle around with yet another term in discussing the could-would approach. Talking about incentives, prompters (and pointers) is already complicated enough.
But that’s not the end of the story. The could-would approach cannot and does not just demand for an incentive in the prior art. An incentive to do … what? Adapting or modifying the closest prior art is no value in itself. It’s all about an incentive to achieve something; it must have a goal. The could-would approach consequently asks for an incentive to adapt or modify the closest prior art in expectation of some improvement or advantage — well, actually to solve the objective technical problem.
However, there is no mentioning of a reasonable expectation of success in the could-would approach. I am currently not sure whether the FPC tends to apply a somewhat modified could-would approach, or whether it understands and applies the expectation of some improvement or advantage in the sense of a reasonable expectation of success — a concept that the Boards of Appeal have developed and applied by now only in biotech cases, to the best of my knowledge.
On a sidenote, I do not readily agree with the threshold the FPC seemingly sets as reasonable; see S2017_001 (¶4.7; emphasis added):
Ob eine angemessene Erfolgserwartung gegeben ist, hängt immer stark von den konkreten Umständen und dem betrachteten technischen Gebiet ab und dabei unter anderem erheblich davon, ob es rational möglich ist, eine Vorhersage über den Erfolg zu machen. (Fn: Vgl. z.B. Medimmune Ltd v Novartis Pharmaceuticals UK Ltd & Ors  EWCA Civ 1234 (10 October 2012), Reasons 91-95)
Note, that Medimmune v Novartis in no way puts such emphasis on the predictability of success, which is rather referred to as just one of many circumstances to consider. It reads as follows (¶91):
Whether a route has a reasonable or fair prospect of success will depend upon all the circumstances including an ability rationally to predict a successful outcome, how long the project may take, the extent to which the field is unexplored, the complexity or otherwise of any necessary experiments, whether such experiments can be performed by routine means and whether the skilled person will have to make a series of correct decisions along the way.
We have seen some interesting decisions lately that deal with basic principles in the assessment of inventive step / obviousness. For instance, the Supreme Court provided guidance how to deal with a non-enabling disclosure as a closest prior art document; see this Blog here. But there is yet another decision of potentially wider relevance, i.e. in that it apparently re-defines how to formulate the ‘objective technical problem’.
It’s silly season now, and I could not help but reflect a bit about the typical learning curve of a patent attorney trainee when getting acquainted with such basics. If you are in a rush, feel free to jump over here.
Patent law is somewhat mysterious. The basics of patentability are very simple: The claimed subject-matter shall
be new (‘just don’t claim exactly what has been out there already’); and
involve an inventive step (‘a bit creative, please – not just obvious’);
On the merits, that’s pretty much it. Admittedly, there are some side aspects to observe, e.g.
it should have industrial applicability (‘it should be useful’);
it should not be excluded from patentability by law (‘don’t do what is explicitly forbidden’);
it should be sufficiently disclosed (‘tell the world how to make use of it’).
But that doesn’t seem to be a big deal. A quite common first thought of a patent attorney trainee goes like:
Well, that’s it? Why do I have to wait three years to sit (and pass!) the exam?
Later, one realizes that things are much more complicated than it seemed at first glance — and that it’s probably not a bad idea to test these basic concepts in real cases for a while, and one is grateful for some supervision before actually sitting the exam (while still at least hoping to pass).
Thereafter, it’s like driving a car. Passing the exam does not yet mean that you are a good driver. Still, at some point sooner or later and with some experience in the field, almost everybody will fairly get along on the streets.
It’s the same with patent attorneys: We are said to have quite firm opinions (when we finally have made up our mind), and it’s our bloody job to transfer this opinion to whoever needs to be convinced, every single day.
But patent attorneys constantly fail. Just look at all the negative office actions in the mailbox every day. Still, we know how to play the guitar. No doubt that a case only failed because the specific piece of music was not well perceived by the audience.
But when the common general understanding of how to assess inventive step / obviousness is whobbling, I am getting concerned. That’s my day-to-day business! Do I still play the game correctly?
Assessment of ‘inventive step’
In knowledge of what the invention is, it’s hard (if not impossible) to objectively evaluate whether or not it had been obvious before the invention has seen the light of day. As soon as you are aware of the invention, the unavoidable hindsight bias undermines any objective assessment.
Case law should be predictable, and individual judgments must be ‘right’. That’s a tricky balance — and whenever things are tricky, it’s comfy to have standardized tools at hand. This is where the EPO’s problem-and-solution approach comes into play (Guidelines, G-VII, 5), and which the FPC has repeatedly indicated to apply. It aims to avoid hindsight bias, and it does so with a rigid framework to be worked through. In brief, the problem-and-solution approach involves three main steps:
Step i), i.e. the question of whether or not something should be considered as the ‘closest prior art’, is mostly a major issue in any discussion of inventive step. I won’t dive into this now, but I strongly recommend Oliver Randl’s Post on an his Blog ‘K’s Law‘. (The Blog is dormant now because he became a member of the Boards of Appeal.) His comparison of assessment of inventive step with mountaineering is just great.
Further, one may well discuss for quite a while in step iii) what a skilled person would actually have done or not. The EPO’s could-would approach requires that
[…] the prior art as a whole […] would (not simply could, but would) have prompted the skilled person, faced with the objective technical problem, to modify or adapt the closest prior art while taking into account of that teaching, thereby arriving at something falling within the terms of the claims, and thus achieving what the invention achieves.
The gist is that hindsight should not be an issue if there is a pointer or an objective incentive to combine two pieces of prior art. Fine. But …
The definition of the ‘objective technical problem’
Everything hinges on the definition of the objective technical problem in step ii), and this is what this Post is all about. According to the EPO Guidelines (G-VII, 5.1),
[…] one establishes in an objective way the technical problem to be solved. To do this one studies the application (or the patent), the ‘closest prior art’ and the difference (also called ‘the distinguishing feature(s)‘ of the claimed invention) in terms of features (either structural or functional) between the claimed invention and the ‘closest prior art’, identifies the technical effect resulting from the distinguishing features, and then formulates the technical problem. […]
It is noted that the objective technical problem must be so formulated as not to contain pointers to the technical solution, since including part of a technical solution offered by an invention in the statement of the problem must, when the state of the art is assessed in terms of that problem, necessarily result in an ex post facto view being taken of inventive activity (see T 229/85).
That’s how I’ve learned to play the game. A plain and simple mechanism:
identify the distinguishing feature (e.g. bolt and nut instead of a nail);
identify the technical effect of the distinguishing feature in the context of the invention (e.g. ease of detachability)
define the objective technical problem based on the technical effect of the distinguishing feature (e.g. facilitate detachability)
Does O2015_008 lower the bar?
When re-reading the judgment O2015_008 of 14 March 2018 (commented on this Blog here), I stumbled upon a general remark in ¶66 that I had overlooked before. It reads as follows (translated from French):
Nevertheless, the question must be asked whether the objective problem that is used for the problem-and-solution approach […] finds a basis or motivationin the closest prior art document or is part of the standard problems for the skilled person, and does not incorporate elements of the proposed solution into the patent (cf. T 59/90, r. 8). This is important to avoid hindsight bias.
(A reasoning along these lines, but in less explicit terms, can also be found in ¶33 of the decision O2015_018 of 15 June 2018, with the very same reference to T 59/90; see this Blog here.)
First, I just don’t know for sure what is meant with ‘standard problems’; but maybe this refers to e.g. ‘less expensive’, ‘faster’, ‘more efficient’ or similar things.
But be that as it may, I feel that the whole approach is flawed.
Why should it be required to have a basis or motivation for the ‘objective technical problem’ in the ‘closest prior art’?
Let’s take a simple example:
The invention is a car with an allegedly clever engine — but there is a lot of other stuff recited in the claim, e.g. wheels, mirrors, bumper, a radio, etc.
The ‘closest prior art’ shows almost everything, in particular the allegedly clever engine. So this really is a reasonably chosen ‘closest prior art’. In fact, it is almost novelty destroying. It is only silent about the radio.
Car radios are perfectly known, but in no way mandatory. Thus, there clearly is no implicit disclosure of a radio in the ‘closest prior art’, and one has to deal with it as a matter of obviousness.
In my perception, a proper definition of the objective technical problem will somehow need to address entertainment and/or information in a car, while carefully avoiding to mention a radio.
The alleged invention correctly just cannot survive the problem-and-solution approach because there are a lot of car radios in the prior art as a whole, and the skilled person would surely have integrated them as a straight-forward solution to the objective technical problem to be solved.
But I am not so sure about this if the reasoning in ¶66 of O2015_008 was correct. To be frank, I don’t even have a clue how the objective technical problem should then be defined. There just is no ‘basis or motivation’ towards entertainment or information in that document.
Alternatively, let’s start from a car with wheels, mirrors, bumpers and a radio as the ‘closest prior art’, and then try to combine it with the (not anymore) ‘closest prior art’ showing the engine. Assume the clever engine is just shown somewhere in the smallprint, without any indication of advantages or further explanations. It’s just there, and it’s not immediately apparent why it actually is clever. You will then have a hard time to hunt this April Fool’s joke of an ‘invention’ down with the problem-and-solution approach, in the absence of any pointer towards the invention, i.e. to use the engine from the prior art in a car with wheels, mirrors, bumper and — believe it or not — a radio.
Frankly, this cannot be it. I feel there must be a bug in a test that does not reliably sort out such non-inventions.
Struggling with this, I sought for guidance in T 59/90 (¶8) referred to in ¶66 of O2015_008. But there is none. It might be the last paragraph of ¶8 that appears to support the view taken in ¶66 of O2015_008, at least at first glance. It reads as follows:
Daraus muss geschlossen werden, dass aus [dem nächstliegenden SdT] das der patentgemässen Aufgabe zugrundeliegende Problem nicht bekannt war, und demzufolge auch die Lösung der Aufgabe aus [dem nächstliegenden SdT] in Verbindung mit dem allgemeinen Fachwissen nicht nahegelegt gewesen sein kann.
It must be concluded that the actual technical issue underlying the objective technical problem was not known from [the closest prior art], and therefore the solution of the problem could not have been obvious from [the closest prior art] in connection with the general technical knowledge.
However, the Board did not deal with the formulation of the objective technical problem here. It took the objective technical problem as it had been properly defined beforehand, and then summarized its assessement according to step iii), i.e. the could-would approach.
At closer scrutiny, it turns out that all this was only intended to sum up the reasons in respect of a single attack based on the ‘closest prior art’ per se, only in further view of the common general knowledge of the skilled person. Thus, it had essentially been argued by the opponent that the ‘closest prior art’ in itself would render the claimed subject-matter obvious for the skilled person. In that case, I might agree that the ‘objective technical problem’ needs to have a basis or motivation in the ‘closest prior art’ because it is not combined with yet another document but rather is considered self-contained, only seen with the eyes of the skilled person (common general knowledge). Where else should the pointer come from, if not from the ‘closest prior art’ in such a case?
But as soon as the ‘closest prior art’ is considered in further view of yet another document, the basis or motivation may well be derived from that further document.
And this is exactly what has been done in T 59/90. The Board moved on to assess in ¶9 whether there is any incentive towards the solution of the objective technical problem in any other prior art document:
It remains to be checked whether a suggestion for the solution of the objective technical problem can be derived from any of the other documents on file.
Note that the Board did not touch the wording of the ‘objective technical problem’ when moving on to check the combinations with the other documents on file. This is the problem-and-solution approach; nothing more, nothing less.
Further, I strongly doubt that this decision is of much relevance at all. It had been only distributed to Chairmen of other Boards (classified as ‘C’), and it has been cited by other Boards only once in 25 years (T 1009/96), for an unrelated aspect. And it is not that this Board had cited it by its own volition. Rather, it had to bother with T 59/90 because a party brought it up. It had been argued that a piece of prior art cannot be considered as ‘closest prior art’ at all because it did not deal with the specific problem of the invention. But this is not my point here, and the argument failed anyway. What is more, T 59/90 is not even mentioned in the reference book ‘Case Law of the Boards of Appeal‘. Thus, the decision has effectively been ignored by other Boards for a quarter of a century. Rightly so, because there is nothing special in it.
Concluding, I don’t see that T 59/90 supports the view taken in ¶66 of O2015_008 (except for the special situation where lack of inventive step is argued based on a single reference, i.e. the ‘closest prior art’ per se), and the above example shows how it would almost inevitably lead to obviously wrong results. In my perception, there is no need to spice up the well established framework of the problem-and-solution approach with yet further requirements. Rather, it can and should be applied as set forth in the Guidelines, for that case law remains predictable. And I have no reason to doubt that it leads to ‘right’ decisions — if applied correctly.
UPDATE 26 Sep 2018:
Decision T 910/90 states the following in ¶5.1 (and I fully concur with this):
Dabei kommt es nicht darauf an ob diese Aufgabe bereits im nächstkommenden Stand der Technik angesprochen ist, sondern darauf was der Fachmann beim Vergleich des nächstkommenden Standes der Technik mit der Erfindung als Aufgabe objektiv erkennt.
It does not matter whether this problem is already addressed in the closest prior art; rather, it is decisive what the skilled person objectively recognizes as the problem when comparing the closest prior art with the invention.
However, [the definition of the objective technical problem according to the problem-and-solution approach] is only valid insofar as the technical problem thus determined can reasonably be presumed to be a problem that arises without inventive effort within the general framework of the closest prior art document. Otherwise, this approach would focus the disclosure of the closest prior art and its interpretation in the direction of the invention, and introduce hindsight. (cf. T 59/90, ¶8)
is obvious in view of the state of the art (Art. 56 EPC).
The fate of a patent application thus critically depends on the ‘state of the art’. Now, what is comprised in the ‘state of the art’? The EPO educates its customers in the Inventors’ handbook in plain and simple words:
A prehistoric cave painting can be prior art. A piece of technology that is centuries old can be prior art. A previously described idea that cannot possibly work can be prior art. Anything can be prior art.
Easy, isn’t it? Not so, the closer you look.
In legal terms, the ‘state of the art’ is defined in Art. 54(2) EPC which reads as follows in the three official languages of the EPC (emphasis added):
Den Stand der Technik bildet alles, was vor dem Anmeldetag […] der Öffentlichkeit […] zugänglich gemacht worden ist.
The state of the art shall be held to comprise everything made available to the public […] before the date of filing […].
L’état de la technique est constitué par tout ce qui est été rendu accessible au public avant la date de depot […].
There are at least two issues that have recently been looked at more closely in relation to the term ‘state of the art’ in Switzerland:
How shall a pre-published, non-enabling disclosure be dealt with?
The Swiss Supreme Court recently held that even a non-enabling disclosure well belongs to the ‘state of the art’ (contrary to what the EPO typically does, i.e. to just ignore it; see Guidelines, G-IV, 2). But, in the Supreme Court’s view, such a piece of prior art cannot be assessed with the EPO’s problem-and-solution approach because the objective technical problem in such a case is just to find a working solution for what had been insufficiently disclosed previously, and there is an inherent motivation to search for that solution; see this Blog here.
What actually is the ‘art’ referred to in ‘state of the art’?
At the INGRES annual meeting of July 5, 2018, Hannes Spillmann briefly discussed a clash between two Board of Appeal decisions at the EPO, i.e. T 0172/03 and T 2101/12. The latter explicitly disagrees in its headnote with the headnote of the earlier decision T 0172/03, in the fundamental question of what actually is meant with
state of the art.
Which ‘art’ does Art. 54(2) EPC refer to? Can something described previously be excluded right from the outset just because it is not related to classic ‘technology’? The headnotes of T 0172/03 suggest exactly that (emphasis added):
1. The term ‘state of the art’ in Article 54 EPC should, in compliance with the French and German text, be understood as ‘state of technology’, which in the context of the EPC does not include the state of the art in commerce and business methods. The term ‘everything’ in Article 54(2) EPC is to be understood as concerning such kind of information which is relevant to some field of technology.
2. From these considerations it follows that anything which is not related to any technological field or field from which, because of its informational character, a skilled person would expect to derive any technically relevant information, does not belong to the state of the art to be considered in the context of Articles 54 and 56, even if it had been made available to the general public before the relevant priority date (see points 8 to 10 of the reasons).
Points 8 to 10 of T 0172/03 referred to in hn 2 leave no doubt that the gist really is to just exclude certain publications from any consideration as ‘state of the art’ whatsoever:
[T]he decision under appeal […] identifies the closest prior art as “the existing order placing mechanism” as if such a business scheme qualified as prior art as any other piece of technical information. […]
It can hardly be assumed that the EPC envisaged the notional person skilled in the (technological) art to take notice of everything, in all fields of human culture and regardless of its informational character. A consistent construction of the patentability provisions requires the term “everything” in Article 54(2) to be understood as concerning such kind of information which is relevant to some field of technology.
I am having difficulties to read an element (“art” / “Technik” / “technique”) of the phrase that is to be defined (“prior art” / “Stand der Technik” / “l’état de la technique”) in Art. 54(2) EPC into the definition itself. This is a Catch-22, in my perception; see also T 2101/12, ¶6.6 in this respect.
Luckily, T 2101/12 sets it right again; the hn reads as follows:
I fully concur with this. Whatever has been made available to the public is to be considered ‘state of the art’ in the sense of Art. 54(2) EPC, irrespective of whether it relates to a field of ‘technology’ or not.
It remains to be seen how the case law of the Boards will develop. Note that T 2101/12 only explicitly disagrees with hn 2 of T 0172/03. However, a quotation from hn 1 of T 0172/03 even made it into the EPO Guidelines for Examination (G-VII, 2):
The ‘state of the art’ for the purposes of considering inventive step is as defined in Art. 54(2) (see G‑IV, 1). It is to be understood as concerning such kind of information as is relevant to some field of technology (see T 172/03).
It is not that I have an issue with this quote. Even a non-technological ‘state of the art’ may well be relevant to some field of technology, e.g. when a mere business method as ‘state of the art’ is automated, and it is patentable when this is achieved in a new and non-obvious manner. This is how T 2101/12 approached it. But this understanding clearly is not what T 0172/03 advocated for. Incomplete reference to only part of hn 1 of T 0172/03 is misleading, at best. In my opinion, reference to T 0172/03 should be deleted from the Guidelines completely.
The following is just to name a few examples of state of the ‘art’ not taken from what one would typically consider a ‘field of technology’. Have fun.
I once had a hard time to properly communicate to a client that a U.S. examiner held SpongeBob to anticipate his invention:
The cartoon SpongeBog SquarePants Episode 1 ‘Help Wanted’ teaches a shearing tool which is mounted coaxially, rotatable, wherein the shearing tool comprises at least a bent arm wherein the tool has at least one opening.
The examiner referred to the following screenshot:
See the tool in motion here, if this meets your sense of humor; the screenshot was taken at approx. 1:04 min.
Drawings and pictures can anticipate claims if they clearly show the structure which is claimed. […] The origin of the drawing is immaterial. The drawings must be evaluated for what they reasonably disclose and suggest to one of ordinary skill in the art.
Luckily, the SpongeBob reference was overcome and the application proceeded to grant; US 8,622,507 B1, see the SpongeBob reference on the title page (‘Other Publications’).
2. The Beano
An entry signal system for pets is described and claimed in GB 2 117 179 A (filed March 18, 1983 and claiming priority of March 18, 1982). The applicant had been faced with the comic strip ‘The Beano’ (No. 2015 of February 28, 1981) as ‘state of the art’:
Reference to ‘The Beano, No. 2015, page 1’ is indicated on the title page of GB 2 117 179 A, under the heading ‘Documents cited’.
3. James Bond
On his fourth mission ‘Thunderball‘, James Bond aimed to recover two stolen warheads. They had been taken by the evil SPECTRE organization. The world was held hostage and Bond headed to Nassau where he was forced into a thrilling confrontation with SPECTRE agent Emilio Largo, on board and around his boat, the Disco Volante. Bond used a special breathing apparatus:
This scene was cited as ‘state of the art’ in GB 2 273 053 A; see ‘Documents cited’ on the title page. Indeed, figure 1 of GB’053 shows a stylized special agent with a somewhat similar breathing apparatus:
4. The Holy Bible
If I had prosecuted the following claim (US 10/212,636, claim 2 as filed), I surely had not expected to become best buddies with the examiner:
But being faced with the Holy Bible as ‘state of the art’ might make one’s blood run cold in one’s veins! The rejection read as follows:
[The claim] is rejected under 35 U.S.C. 102(b) as being anticipated by the Holy Bible (Levite, Moses, et al.)
[…] In Genesis, Chapter 41, we are told that Pharaoh appointed Joseph to be his representative and instructed him to enter into contracts to purchase grain. These contracts included an offer with an activity (supply grain) and a benefit (get paid for the grain). Payment was made upon delivery of the grain. The story of Joseph is about 4,500 years old. Neither Joseph nor Pharaoh were considered innovators – the principal / agent relationship is of immemorial antiquity. It no doubt predates civilization itself. The purpose of rejecting this claim using the Bible as reference is to illustrate how ancient the claimed subject matter is. Many of Applicant’s claims could also be rejected using the same reference.
The applicant took up the fight, and his response really is a good read:
On a sidenote, I have once been told (but did not manage to independently verify) that a patent application pertaining to a voice-controlled automated lighting system had been challenged at the EPO with reference to the Holy Bible, too. More particularly, with reference to Genesis, Chapter 1:
And God said, ‘Let there be light’, and there was light.
5. The Law of Agency
Misfortunes never come singly: The claim recited above in (4) had also been rejected in view of the law of agency. The apparently highly motivated examiner held:
Basic agency law teaches that a principal may conduct any business through an agent (representative) that he could conduct in person. This includes entering into contracts. To enter into a contract, one determines a recipient (the other party) and an offer, which includes an activity (e.g., paint my house) and a benefit (consideration). If using an agent, the principal transmits instructions to the agent to provide the offer to the recipient. In any contract, there is the step of determining whether the recipient has performed the activity and providing the benefit to the recipient if the recipient has performed the activity.
6. Donald Duck
In a 1949 Walt Disney comic, a sunken ship had been raised by Donald Duck and his nephews. They pushed ping pong balls into it to lift it up:
A similar technology has actually been used later, for the first time in 1964 when Karl Kroyer lifted a sunken ship with 6’000 sheep right in front of Kuwait’s major fresh water intake in the harbor.
Rumor has it that Kroyer’s patent application was rejected in view of the comic strip (as reported e.g. in the newspaper scan above), allegedly by the Dutch patent office — but I could not find any proof for this. Patents have been granted elsewhere (e.g. in Germany and the U.S.).
Nevertheless, I have no doubt at all that this comic strip would have had to be considered as ‘state of the art’ in the assessment of patentability of Kroyer’s invention.