In part 1 of this article I discussed software forensics, generally what it is and why it’s needed. One of the big reasons there is such a need for software forensics is to interject objectivity into what is otherwise a battle of experts who are supposed to be unbiased but who may be strongly influenced by, if not outright pressured to support, the positions of their clients. This is just as true of experts in other areas of litigation, but as more complex technologies are at issue in today’s IP cases, lay judges and juries are less capable of weeding through technical intricacies to weigh opposing views of experts. Compounding this reality is the ever increasing popularity of police dramas on television, which elevate the desire for juries to have some kind of objective information they can rely on; something of a smoking gun if you will. Software forensics can often provide that smoking gun and cut through the haze. But the question remains, how do we assure that software forensic tools are reliable and consistent and that the expert witnesses who use them are qualified and honest about their analyses?
Below are a few ideas about this, though each one carries with it potential problems. Perhaps not all of these ideas can definitely be implemented, but if we could insert some or all of them into the current legal system, we might have just results a higher percentage of the time. And applying these ideas to criminal cases might be a particularly good idea, where an expert’s opinion can be the difference between life and death for a person accused of a crime.
The word “forensic” comes from the Latin word “forensis” meaning “of or before the forum.” In ancient Rome, an accused criminal and the accusing victim would present their cases before a group in a public forum. In this very general sense it wasn’t unlike the modern U.S. legal system where plaintiffs and defendants present their cases in a public forum. Of course the rules and procedures of the presentation differ from those days. Also, parties are typically represented by lawyers trained in the intricacies of all of these rules and procedures.
After deliberation, one party would be declared a winner. The party with the best presentation skills, regardless of innocence or guilt, would often prevail. The modern system relies on attorneys representing the parties to make the arguments rather than the parties themselves, under the assumption that lawyers, trained in law and skilled at presenting complex information, will each present their client’s case in the best possible manner and that ultimately a just outcome will occur. I don’t want to say that the truth will prevail, not only because that’s a cliché, but because there’s often some amount of truth in the arguments of both parties. Rather, more often than not, justice will be served.
I believe that this model works very well. Not perfectly, but very well. With regard to highly technical cases, however, the percentages for justice being served go down because the issues become difficult for a judge or jury to grasp. Technical experts can throw around technical jargon, sometimes without realizing it and other times to purposely cause confusion. This is the reason that I believed, when I started out examining code for intellectual property litigation, that two things were required to improve the analysis of software for the legal system.
Justices of the United States Supreme Court. No friends to innovators who require strong patent rights.
As I was putting together the slides for this Powerpoint presentation I thought to myself, “how do I title this page.” I’ll tell you the thought that first jumped into my head, although I ruled it out: “Public Enemy Number One.” Or I suppose “Public Enemy Number One through Nine.” There is little doubt that the Justices of the Supreme Court are indeed public enemies, at least insofar as patent owners are concerned. Unless you are represented by Seth Waxman at the Supreme Court your patent claims are invalid! And even Seth doesn’t always win, although he sure wins a lot for Monsanto.
Let’s start our discussion of SCOTUS decisions with Mayo v. Prometheus. In Mayo the Supreme Court proudly proclaims that they’re not going to take the government’s invitation to apply 102, 103, and 112. Instead the Court decided to limit its handling of the issues to patent eligibility under 101. And as they go through their analysis they admit that the claim in question includes things that are not in nature, but yet they reach the conclusion that the claim is still a law of nature anyway because you’re just adding some extra stuff that already exists. It’s breathtaking. One, that’s not what the law is. Two, that’s not what the statute says. And three, every other Supreme Court throughout history specifically said never do that, and they did it anyway.
Bob Zeidman is the president and founder of Zeidman Consulting, and he is also the president and founder of Software Analysis and Forensic Engineering Corporation. Zeidman is a software expert that I have known for several years and in the wake of the Supreme Court’s decision in Alice v. CLS Bank we talked on the record about the decision, software in general and writing patent applications. What follows is part 3 of our 3 part conversation.
In this final installment we spend time talking about the problems associated with creating software that actually works. For something that Judges and mathematicians seem to say is so trivial software sure doesn’t work nearly as well as it should. Copied code cobbled together leads to broken systems, and programmers simply throw code up without proper vetting and let consumers find the bugs. Sure doesn’t sound like it is all that trivial to me, but then again, I’m not an ivy league educated Supreme Court Justice who is so computer illiterate that I don’t use e-mail.
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.
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.
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.
BEAR: In Judge Michel’s brief, he writes about not confusing §101 with §102 and §103. I’m also looking at this and thinking that patentability questions regarding “abstract ideas” may, perhaps, be better handled under §112 on specificity grounds. What do you think about that?
QUINN: I totally agree. And I think that that was the way that Director Kappos meant it when he was at the Patent Office and the Bilski case came out. That was what he was urging the examiners to do. Do not to make this a §101 issue but instead get the §112 issue. I think that’s the exact right approach because the real question I think they’re struggling with is whether there is an invention there. You can’t know whether there is an invention there until you ask what does somebody of skill in the art understand by reading the disclosure. And what some want to do is make it a §101 question so that they don’t have to do any analysis or heavy lifting.
There are numerous briefs listed on the ABA’s brief publication webpage for Alice Corp. v. CLS Bank that are filed in support of the respondent, most of which make specious claims about software patents blocking innovation, or which make arguments that claims that specifically recite computers, data storage units, devices and more are somehow abstract and imaginary. These arguments should be easy enough to dispose of as ridiculous on their face, but who knows how the Supreme Court will respond. Still, one would hope that the Supreme Court would notice that neither patents generally or software patents specifically have done anything to block innovation in the smartphone industry.
Whereas the Alice supporters feel that the U.S. Patent and Trademark Office’s issuance of software patents are important for protecting and spurring innovation in many fields, the supporters of CLS Bank have largely responded that software patents hurt innovation. But that can’t be! One of the areas critics always say has been allegedly hamstrung by patents, the smartphones industry, is barely over 6 years old. Have patents stopped innovation of smartphones? Hardly. In fact, with every new version companies tout just how much more the phones do and how they are so far superior to the previous model. Thus, it is easy to see that those claiming that software patents block innovation simply ignore market reality and how the functionality of current devices (which is thanks to software) match up with previous generations of devices over the last 6 years. Corporate critics must also ignore their own marketing of new smartphones, which directly contradicts the ridiculous claim that software patents are preventing innovation. Still they make these and other specious arguments as if they are true.
The immense wave of technological innovation that continues to pour out of Samsung makes it a favorite one for us to cover here in IPWatchdog’s Companies We Follow series. Our investigation of Samsung’s recent patent applications and issued patents from the U.S. Patent and Trademark Office showed us some very novel new digital systems for Samsung’s various consumer devices. We wanted to share some of the most intriguing innovations from this company with our readers today.
First, we start by taking a close look at our featured patent application, which describes a system of linking applications on a single electronic device. By linking applications, a user can more easily switch between programs without using a multi-window view, which limits usable space on a touchscreen. Better methods of providing flash storage memory for smartphone devices and reader methods for adding multimedia effects of their choosing to an eBook are reflected in other patent applications we discovered.
When the U.S. Supreme Court finishes hearing arguments in the upcoming case Alice Corporation v. CLS Bank International, it will be asked to judge whether or not software and computer-implemented inventions are eligible to receive patent protections through the U.S. Patent and Trademark Office. Should the Supreme Court uphold the original decision and declares that the Alice’s patents on computer-implemented systems for managing risk in financial transactions are patent ineligible, thousands upon thousands of software patents could become invalidated.
We discussed some of the issues in play with this major case in our previous look at amicus briefs filed with the U.S. Supreme Court for this case. We have also profiled the IBM amicus briefthat argued that the abstract idea doctrine was unworkable. These parties, though largely neutral, had a number of disdain for how the judiciary has handled the issue of software’s patent eligibility under Section 101 of Title 35 of the United States Code. Today, we’re taking a look at briefs filed for either side of this historic case to get a broader sense of the viewpoints involved in this issue. A number of major corporations, non-profit organizations in technological fields and renowned scholars have lent their ideas to these briefs, and readers may find their views on the patent eligibility of software programs to be enlightening.
A quick perusal of the amicus briefs published online by the American Bar Association shows that only a few of the briefs filed are supporting the petitioner, Alice Corporation, in this case. In fact, only three briefs in support of the petitioner are shown on the ABA’s official site listing amicus briefs for this case; there are a total of 40 amicus curiae briefs shown on that site, as of this writing.
Much of this negativism is based on the poor job the US patent examiners have done in weeding out those many patent applications where the so-called invention is just one of the almost infinite, but obvious, ways one can automate a manual or semi-automatic process or procedure. But there are also true inventions that use a computer as part, or all, of the implementation of the invention. There is no reason to throw out the baby with the bathwater. So it is of utmost importance that we examine the many falsehoods related to software patents.
In this new article I intend to provide facts about software and the software industry to debunk these misnomers, myths, misconceptions, and just pure misunderstandings about “software patents”.