Posts Tagged: "software patents"

Despite the turmoil surround software patent eligibility I believe with great certainty that software will remain patent eligible in the United States. The extreme decisions of the PTAB and viewpoints of those on the Federal Circuit opposed to computer implemented methods will not prevail because they are inconsistent with the Patent Act and long-standing patent law jurisprudence. After all, the Supreme Court itself explicitly found software patent eligible in Diamond v. Diehr. In the meantime, while we wait for the dust to settle, we need to engage in a variety of claiming techniques (i.e., methods, computer readable medium, systems claims, means-plus-function claims and straight device claims). Thus, if you are interested in moving forward with a patent application it will be advisable to file the application with more claims than would have been suggested even a few months ago. Patent attorneys also must spend increased time describing the invention from various viewpoints, which means specifications should increase in size. This all means that there is no such thing as a quick, cheap and easy software patent application – at least if you want to have any hope of obtaining a patent in this climate.

One application assigned to IBM would protect a system of allocating software resources to a user’s network account once their presence is detected at a facility. An patent awarded by the USPTO protects an IBM invention involving a visual-based help tool for button icons within software applications. IBM is also involved in developing a number of systems to aid computer users on a personal basis. One application describes a system of ordering computer icons on a user interface based on contextual factors, like the time of the week. Two related applications would protect a system of analyzing web applications for possible malicious data, protecting millions of computer browsers. Lastly, we also look at a newly devised system of filtering online shopping reviews based on the characteristics of an individual shopper.

Under what authority does the PTAB ignore specifically recited structure? The authority that the PTAB seems to be relying on to ignore claim terms is unclear and not explained in the opinion in any satisfactory way. It does, however, seem that the fact that the invention can be implemented in any type of computer system or processing environment lead the PTAB to treat the method as one that could be performed on a “general purpose computer,” rather than a specific purpose computer. Thus, the PTAB picks up on the arbitrary and erroneous distinctions between general purpose computer and specific purpose computer without as much as a thought and wholly without factual explanation.

The New Zealand Government recently announced a proposed change to patent law involving the patentability of computer programs. The Government is calling it a clarification of the law. One opposition party is calling it a humiliating backdown. Others see it as unequivocally ruling out software patents in New Zealand.

In a one-page memorandum to the Patent Examining Corps dated May 13, 2013, Deputy Commissioner for Patent Examination Policy Drew Hirshfeld had a simple message to respond to the Federal Circuit’s en banc non-decision in CLS Bank v. Alice Corp. The message was this: “there is no change in examination procedure for evaluating subject matter eligibility.”

Why have claims if the claims don’t matter. Essentially Judge Lourie, and the Canadian Patent Office too, are saying ignore the claims and read the specification to determine what the innovation is and then without regard to the language of the claims make your determination. Under this viewpoint claims are simply irrelevant. Yet we know that claims are not irrelevant, and such a view is directly contrary to the Patent Act itself. Ignoring claims is utterly ridiculous given inventions are not patentable. Patent claims are supposed to be evaluating NOT the entirety of the invention. The sine quo non of patents are the claims. It is black letter law that the claims define the exclusive right granted. Ignoring the claims shows reckless disregard for the well established law and is nothing short of judicial activism.

The first thing that any student of the Federal Circuit likely notices when reading CLS Bank is that Judge Lourie not only joined the dominant concurrence, but he also wrote the opinion. The same Judge Lourie who wrote the first opinion in Mayo, after which the Supreme Court asked the Federal Circuit to reconsider, and who then wrote the second opinion in Mayo. The same Judge Lourie who wrote the first opinion in Myriad, after which the Supreme Court asked the Federal Circuit to reconsider, and who then wrote the second opinion in Myriad[12]. All of those opinions interpret §101 broadly. What changed?

All the Judges rely on the same Supreme Court precedents in Gottschalk v Benson, Parker v. Flook, Diamond v. Diehr, Bilski v. Kappos, and Mayo v. Prometheus. All the Judges recognize the same judicial exception to statutory subject matter under §101 for laws of nature, natural phenomena, and abstract ideas. All the Judges recognize that a claim must include “meaningful limitations” that go beyond an abstract idea. Hollow field-of-use limitations and insignificant pre or post-solution activity don’t count. However, this is where their similarities end.

While the Supreme Court has done away with the “useful, concrete and tangible result” test from State Street Bank v. Signature Financial, in Bilski v. Kappos, 8 out of 9 Justices (i.e., everyone except Justice Scalia) signed onto an opinion that recognized that the patent claims in State Street displayed patent eligible subject matter. Indeed, the dissenters in Bilski specifically acknowledged that the claims at issue in State Street did not deal with processes, but dealt with machines. See Footnote 40 of the Steven’s dissent. The import of this is that machines are specifically patent eligible subject matter, so if the claims of State Street are to machines then claims that are similarly configured would also be directed to machines and therefore patent eligible.

Watson? It is an artificially intelligent computer system that is capable of answering questions presented in natural language. It is, in essence, the modern day equivalent to the all knowing Star Trek computer. It is flat out ridiculous to be asking whether the Star Trek omnipotent computer could be patent eligible, that that is where we find ourselves because what makes the computer unique is the software that makes it possible for Watson to perform 80 trillion operations per second. But Federal Circuit Judges say that mere fact that software is fast doesn’t make it patent eligible unless there is some kind of uniqueness to the computer itself. Have we really reached the point where truly astonishing innovations, innovations once thought to be impossible, are not patent eligible? Talk about jumping the shark!

Perpetuating the myth that the computer is where the magic lies does nothing other than ignore reality. Software is what makes everything happen. or crying out loud, software drives a multitude of machines! Maybe the auto mechanic for Judges Judges Lourie, Dyk, Prost, Reyna and Wallach should remove the software from their cars. Perhaps as they are stranded and forced to walk to work they might have time to contemplate the world they seem to want to force upon the rest of us; a world hat clings to mechanical machines completely non-reliant on software. That will be great for the economy!

The only thing we know is this — the Federal Circuit issued an extraordinarily brief per curiam decision, which stated: “Upon consideration en banc, a majority of the court affirms the district court’s holding that the asserted method and computer-readable media claims are not directed to eligible subject matter under 35 U.S.C. § 101. An equally divided court affirms the district court’s holding that the asserted system claims are not directed to eligible subject matter under that statute.” Thus, the asserted claims are not patent eligible.

As a designer, I just like to be hands on, managing the quality of the work and making sure it communicates exactly what we need it to say. And, I’m the same in preparing for court. I like to create demonstratives and be the one giving tutorials to the court – because live presentations are often the best way to communicate how something works. Another visualization technique that’s really effective is storyboarding. Storyboards can show the change in a system over time. If this is the position of the device and this is what you see on screen at time T1, then at time T2, this is the position of the device and this is what you see on screen. And then at time T3, this is the position of the device and this is what you see on screen. Describing actions with pictures removes ambiguity about the user experience and establishes some defense of how the system is claimed to operate.

On March 25, 2013, I spoke on the record with Eric Gould Bear (left) about software innovations, software patents and the trials and tribulations of litigating software patents long after they were first written. In Part I of our interview, titled Designing Into the Path of Disruptive Technology, we discussed the journey from ideas to designs that design a technology platform that could realistically be useful 5, 10 or more years down the road. In Part II of our interview, which appears below, we discuss drafting software patent applications with an eye toward litigation and the unfortunate reality that the top technology innovators simply won’t listen to licensing overtures unless they are first sued.

It’s important to remember that ideas are a dime a dozen. And what matters at the end of the day, in my mind, is what works well for people. It comes down to making sure that your flash of genius is a fit for what’s valuable to real people in everyday life. Whether in a consumer space or in business, it doesn’t matter. The underlying principles of making great design come down to how people act in the world. How do they think about themselves? What do they feel about your product? What do they think about each other? And where are they running into challenges in either accomplishing things or living life to its fullest. So, if it starts with an idea, I would challenge that premise to begin with – because I believe great design often starts with a question as opposed to an answer.