Those looking to wittle away at the patentability of software patents, a recent decision by the Court of Appeals for the Federal Circuit (CAFC), Bancorp Services v. Sun Life states that,
To salvage an otherwise patent-ineligible process, a computer must be integral to the claimed invention, facilitating the process in a way that a person making calculations or computations could not…. The computer required by some of Bancorp’s claims is employed only for its most basic function, the performance of repetitive calculations, and as such does not impose meaningful limits on the scope of those claims.
This language appears to imply that speed or efficiency of a computer over a human is insufficient when the tasks being performed are “repetitive calculations.” So when is a computer facilitating a claimed process in a way that a person making calculations or computations could not? Apparently, when these calculations are not repetitive. Of course, it is well known that computers are best at performing repetitive calculations. I am not sure why the type of calculation being performed should matter for patentability.
Such a nebulous standard would be challenging for patent examiners at the Patent Office to apply. It is also a clear departure from the Supreme Court’s decision in Bilski. It bears watching whether the Supreme Court will clarify the situation regarding computer-based inventions any time soon.
I’d love to hear other’s thoughts on the meaning of this language and the effect such a standard would have. Does anyone have thoughts on how to write patents to make sure this standard is met?
The sentiment appears to mirror the “further technical effect” approach found in Europe and the UK: i.e. a technical effect over and above a standard computer implementing a computerised method.
I agree though that the reference to “repetitive calculations” is a bit misleading and could be phrased better. However, I am not holding out hope of clarification from the Supreme Court any time soon.
In the meantime, I guess when drafting an application the key is to avoid the “abstract method description + boilerplate computer architecture” template that was used for many business method and software patents in the early 00s. From what I have seen of the recent US decisions, a technical (e.g. engineering/computer science-level) description that emphasises the differences from a manual method should help avoid patentability objections.