Over the last several days I have heard of an alarming trend from the United States Patent and Trademark Office — Patent Examiners are canceling Notices of Allowance and yanking previously granted claims back into prosecution while citing the United States Supreme Court’s ruling in Alice v. CLS Bank. In some instances granted claims are being pulled back into prosecution only to be rejected as lacking patent eligible subject matter even after the issue fee has been paid. I have also been told that an Examiner in one case has issued a new Examiner’s Answer to include a new Alice 101 rejection.
Rejecting claims after the issue fee has been paid represents an extraordinary disconnect from the initial USPTO guidance that essentially said that Alice changed nothing from a substantive point of view. I was shocked that the USPTO issued such guidance because if you actually read the Supreme Court’s decision in Alice you could hardly walk away with the belief that nothing had changed.
In the immediate aftermath of the Supreme Court’s decision in Alice the USPTO told examiners that the reason Alice’s claims were determined to be patent ineligible was because “the generically-recited computers in the claims add nothing of substance to the underlying abstract idea.” The USPTO, by and through the Deputy Commissioner for Patent Examination Policy, Andrew Hirshfeld, then went on to point out to patent examiners that there is no new category of innovation that is patent ineligible, nor is there any new or special requirements for the eligibility of either software or business methods. Hirshfeld explained: “Notably, Alice Corp. neither creates a per se excluded category of subject matter, such as software or business methods, nor imposes any special requirements for eligibility of software or business methods.”
I feel like a very broken record. In an IPWatchdog article I wrote back in 2012, I commented on the currently fractured patent-eligibility landscape in the split Federal Circuit panel decision in CLS Bank International v. Alice Corp. Pty. Ltd. where a claimed trading platform for exchanging business obligations survived a validity challenge under 35 U.S.C. § 101. See The Fractured Landscape of Patent Eligibility for Business Methods and Systems in CLS Bank International. That fracture got even worse in the subsequent en banc ruling which can only be described as lengthy, tumultuous, and confusing, with a brief per curiam opinion, as well as six full opinions.
With the Supreme Court’s most recent foray into the patent-eligibility world in Alice Corp. v. CLS Bank International, we now have a complete and utter disaster as to what data processing claims can (or more unfortunately cannot) survive scrutiny by Our Judicial Mount Olympus under 35 U.S.C. § 101. I once had respect for Justice Thomas’ view on patent law jurisprudence, having considered his substandard opinion in Myriad on the patent-eligibility of certain “isolated” DNA claims to be an “isolated” aberration. But having now read his mind-boggling Opinion for the Court in Alice Corp., I’ve now thrown my previously “cheery” view of Thomas’ understanding of patent law jurisprudence completely into the toilet. I have even less kind words to say about the three Justices that signed onto Justice Sotomayor’s disingenuous concurring opinion that accepts retired Justice Steven’s equally disingenuous suggestion in Bilski that 35 U.S.C. § 273 (in which Congress acknowledged implicitly, if not explicitly the patent-eligibility of “business methods” under 35 U.S.C. § 101) is a mere “red herring.” See Section 273 is NOT a Red Herring: Steven’s Disingenuous Concurrence in Bilski.
The Supreme Court’s decision in Alice Corp. operates from the view that “ignorance is bliss” when it come to the patent statutes, as well science and technology. I don’t share that view and never will. So in the format that I began with in shredding Justice Alito’s “comedic” opinion in Limelight Networks, here are my “ignorance is not bliss” candidates for Alice Corp., in all their ugliness.
We can return to the beginning of the analysis and revisit preemption. As stated, the Court sees § 101 as protecting the big ideas that are fundamental to commerce, science, and technology, patents that would preempt and “block” innovation. The Court realizes that every patent preempts and blocks in some degree, because that’s what patent claims do. Rather, the risk of preemption must be “disproportionate.” Alice,slip op. at 5. This is a definitely a much higher bar than the standard set forth in the CLS plurality opinion, “Does the claim pose any risk of preempting an abstract idea?” CLS, 717 F.3d at 1282 (Lourie, J., concurring),cited approvingly in Accenture Global Services, GmbH v. Guidewire Software, Inc., 728 F.3d 1336 (Fed. Cir. 2013).This requirement for a high level of preemption risk is necessary because we can never know a priori (e.g., when a patent application is filed, when it is reviewed by a patent examiner) exactly what will happen in the future, and how important and preemptive the patent will be in regards to other developments in the same field or in other fields. Most truly fundamental “building block” inventions are not recognized as such for many years after the fact. Thus, we must tolerate preemption in two ways:
The kind of preemption that is inherent or recognizable based on the claim language. To borrow a phrase from Donald Rumsefld, this is the “known known” risk of preemption.
The “known unknown” preemption that we cannot determine because we cannot know what will happen in the future: whether the technology will be successful in the marketplace, whether others will adopt it, or design around it, or any other myriad factors that influence how “fundamental” an invention will be.
If a patent claim is ineligible if there is “any risk” of preemption, then the “exclusionary principle . . . will swallow all of the patent law.” Alice,slip op. at 5. A court or a patent examiner certainly cannot evaluate the level of “known unknown” preemption, and hence should not use speculations (or hand-waving) about this kind of preemption risk to invalidate a patent. The disproportionate risk of preemption only comes from patents that claim Abstract Ideas in the sense of fundamental building blocks, not just run-of-the-mill abstract ideas. It’s only when the known known type of preemption covers an Abstract Idea that the claim is ineligible. The ordinary type of preemption that comes from patent claims is an accepted part of the patent system—that’s the whole point of claims, to define the metes and bounds of the invention so that others are preempted from making, using, and selling what’s inside the bounds.
~ ‘The report of my death was an exaggeration’ –Mark Twain
Mark Twain, American humorist.
With apologies to the great humorist, the report of the death of software patents is an exaggeration. Some commentators quite quickly suggested that the Supreme Court’s decision in Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. ___, No. 13-298 (June 19, 2014), will “invalidate the majority of all software patents in force today” and is “bad news for software patents”. That interpretation may make good copy, but it is simplistic and overblown. While the Court invalidated Alice’s patents, the decision certainly does not invalidate the majority, or even a large percentage, of software patents, nor does it radically restrict the kinds of inventions that can be patented going forward. The decision is a modest and incremental clarification in the patent law, and a not wholesale revision.
The Court set forth a two-step test grounded in Bilski v. Kappos and Mayo v. Prometheus. While the Court may not have defined a clear boundary for so called “abstract ideas” specifically, it did squarely place this case within the “outer shell” of the law set forth in Bilski and Mayo. In doing so it articulated an approach that focuses not on finding the boundary line, but rather on the core properties of an ineligible patent claim. In Part I of this two-part post, I will focus on just the first step of the test, whether a claim recites a patent-ineligible “abstract idea.” In Part II, I’ll address issues regarding preemption, mental steps, and the application of Alice to software patents.
At least initially, the USPTO instructions to examiners seems extremely patentee friendly, which I must say comes as a surprise given the largely anti-patent rhetoric that has come from the White House over the last 16 months. Indeed, the USPTO has told examiners that the reason Alice’s claims were determined to be patent ineligible was because “the generically-recited computers in the claims add nothing of substance to the underlying abstract idea.”
The USPTO then went on to point out to patent examiners that there is no new category of innovation that is patent ineligible, nor is there any new or special requirements for the eligibility of either software or business methods. Hirshfeld explained: “Notably, Alice Corp. neither creates a per se excluded category of subject matter, such as software or business methods, nor imposes any special requirements for eligibility of software or business methods.”
Hirshfeld also explained that there is now a slight change in the way applications are to be examined when claims involve abstract ideas. Essentially, Alice stands for the proposition that the same analysis should be used for all types of judicial exceptions and the same analysis should be used for all categories of invention. Still, even recognizing this shift in analysis, Hirshfeld told examiners: “[T]he basic inquiries to determine subject matter eligibility remain the same as explained in MPEP 2106(I).” (emphasis added). Therefore, nothing has changed as far as the USPTO is concerned.
On Thursday, June 19, 2014, the United States Supreme Court issued its much anticipated decision in Alice v. CLS Bank. In a unanimous decision authored by Justice Thomas the Supreme Court held that because the claims are drawn to a patent-ineligible abstract idea, they are not eligible for a patent under Section 101.
In what can only be described as an intellectually bankrupt opinion, the Supreme Court never once used the word “software” in its decision. This is breathtaking given that the Supreme Court decision in Alice will render many hundreds of thousands of software patents completely useless. While the Supreme Court obviously didn’t want to make this decision about software, the holding does make it about software because each of the ways software has been claimed were ruled to result in patent ineligible claims. On first read I don’t see how any software patent claims written as method or systems claims can survive challenge. For example, these claims to IBM’s Watson computer, which is really akin to the first generation omnipotent Star Trek computer, seem to be quite clearly patent ineligible. See Is IBM’s Watson Still Patent Eligible. It is impossible to see how the Watson claims remain patent eligible in light of this ruling and how the Alice claims were written. The only potential solace for IBM and others would be if the Federal Circuit narrowly interprets this decision noticing that the Supreme Court seemed almost preoccupied by the fact that the patent claims covered a financial process. Still, the structure of the claims are nearly identical, with Alice’s claims actually having more recited structure, if anything.
More difficult to understand is how the Court could issue a decision that doesn’t even use the word software. Software is clearly patent eligible if you read the patent statute. Software is mentioned throughout the statute. It was specifically mentioned in the America Invents Act in 2011. Tax strategies are not patent eligible in and of themselves, but the AIA says that software is not patent ineligible just because it incorporates a tax strategy. This is the type of analysis the Supreme Court engaged in the Bilski decision finding that business methods are patentable.
When the Supreme Court hands down a decision bearing on a hotly contested area of law, it means the work has just begun for any agency tasked with administering its consequences. Last term, the Court rendered such a decision in Association for Molecular Pathology v. Myriad Genetics, adding a new wrinkle to the already confounding question of patentable subject matter under §101 of the Patent Act.
As companies consider current cases related to patents before the Supreme Court, they would be wise to learn from the challenges the USPTO faced in implementing the Myriad decision. And for the reasons set forth below, we believe that the USPTO and the entire business community are well served by engaging in rigorous public debate about the guidelines that should be established to implement the decision from the Supreme Court.
For more than a decade, the legal, technical and academic communities have debated the boundaries, legality and wisdom surrounding the issue of software patentability. The debate, to say the least, has been spirited with many organized movements, websites, articles, blogs and law review articles, as well as a lot of lobbying dollars, devoted to both sides of the debate. Yet, as the U.S. Supreme Court currently reviews the U.S. Court of Appeals for the Federal Circuit’s en banc May 10, 2013, decision in CLS Bank v. Alice, we take the opportunity here to dispel some myths, state some of facts and offer a test with respect to software patentability.
This is not your Parent’s Software Industry
There are those who argue against the patentability of software as a whole – never mind finding a test as to what software (or computer-implemented) claims should be patentable. We disagree. Why? Well, the notion that software should not be patentable necessarily indicates that the software industry itself is not capable of innovation worthy of patent protection! Yet, in a country where patent rights are guaranteed by the Constitution, should not all fields of innovation be treated equally under the law? Should we not avoid becoming a country where one field of endeavor (e.g., pharmaceuticals or electronics) is deemed more “patent worthy” than other fields (i.e., computer science and information technology)!? To answer these questions in the negative seems silly to us.