Join Gene Quinn, patent attorney and the President & CEO of IPWatchdog, Inc., on Thursday, February 14, 2019, at 12pm EST for a free webinar discussion Drafting Software Patents: Lessons from Key Lighthouse Cases. Joining Gene will be John White, patent expert, lecturer and partner with Berenato & White, and Megan McLoughlin, patent attorney with LexisNexis IP.
Four years after the Alice decision, we seem to just now be detecting the full impact of the decision. The initial response by the USPTO resulted in an somewhat expected increase in the percentage of applications with eligibility rejections from business-method art units. Three years after Alice, eligibility rejections became much more common across the remaining computer-related technology centers (i.e. 2100, 2400, and 2600)… The sudden increase in eligibility rejections from other computer-related technology centers may have a number of causes. For example, case law from the Federal Circuit and the USTPO began to expanded the application of Alice to inventions that appear abstract despite not being directed to a traditional business-method concept… The increase in the percentage of office actions with eligibility rejections in TC 2100 was much higher than the increase in other computer related technology centers TC 2400 and TC 2600. Given that TC 2100 is a primarily software-focused technology center, this trend discrepancy suggests that post-Alice eligibility assessments performed by software examiners present increased challenges for patenting software based inventions.
If there was a theme that emerged in 2017 it is the necessity to have what is specifically innovative disclosed in the claims. While not a particularly new concept, there were cases in 2017 where the Federal Circuit acknowledged that a patent eligible innovation may well have been disclosed in the specification, but which was not found in the claims. With many legacy software patents the description of the technology (if one actually existed) was only in the specification while the claims were written to be quite broad. The Federal Circuit requires both a thick technical description of the innovation and why it is an improvement (see Enfish) and incorporation of what is innovative into the claims… What follows picks up where my 2016 article left off and provides summary and analysis of the notable software patent eligibility cases decided by the Federal Circuit in 2017.
One of the great aspects of the Unitary Patent is that it follows the normal EPO procedure up to grant. And indeed, the search and the examination processes will be precisely the same as those you’ve been used to with the current EP and PCT procedures, and will be performed by the same examiners. One of the strengths of the EPO is that we allocate examiners to applications according to their technical expertise, regardless of the filing route through which applications arrive. It will only be at the end of the procedure, when the application proceeds to grant, that applicants will have to indicate if they want to have a single Unitary Patent instead of a bundle of patents for individual member states, as is the case for the European patent. So it’s extremely straightforward, cost effective, and much simpler to administer post grant than the current European patent. My impression is that many U.S. applicants already understand the logic and advantages of this very well, sometimes even a little better than European applicants, as the geographical size and the GDP of the market covered by the Unitary Patent is very similar to that of the U.S. patent.
We try to be precise and stick to CII because “software” in itself is a term which lacks precision. It can refer to a high level program, a machine level program, or it can be an executable program. But if we speak about a computer-implemented invention the core of the discussion is rather on the technology. We have a general purpose computer and we program it, and when it runs it executes the instructions and performs certain functions. So the essence of our approach is to ask what the software does. Software of course can do a variety of things, many of which can be totally out of the patentable area if they’re purely abstract or purely business oriented. But when software solves a technical problem you are definitely in the area where a patent is possible. That is the core element of our approach.