Posts Tagged: "computer software"

Software is now and will remain patentable in the United States. Software patents have been vilified by many, but they have been granted by the United States Patent and Trademark Office and upheld in federal courts across the United States. The much anticipated Bilski v. Kappos decision at the Supreme Court did nothing to slow down the patentability of software, and in fact even the original Federal Circuit decision wound up, as applied by the USPTO, to make it more likely that adequately written software patent applications would be granted and transformed into issued patents. What has changed over the last several years, however, is the amount of detail that must go into a software patent application in order to satisfy the adequate description requirements under US patent law. So don’t listen to anyone who tells you software cannot be patents in the United States; it certainly can, but it isn’t quite as easy as it used to be.

So now what does SCOTUS’ ruling in Bilski “really” mean to us “mere mortals”? First, we’ve got two “wild cards” to deal with as noted above: (1) Stevens has retired; and (2) what does Scalia’s refusal to join Parts II B-2 and C-2 of Kennedy’s opinion for the Court signify. Some aspects of “wild card” #2 are dealt with above, but as also noted, there are still some aspects which are unclear or at least ambiguous as to how this refusal by Scalia should be viewed. This lack of clarity/ambiguity will require some sorting out by the Federal Circuit, which may come as early as the reconsideration by the Federal Circuit of Prometheus, Classen, or even the appeal in AMP v. USPTO involving the gene patenting controversy. In AMP, District Court Judge Sweet’s invalidity ruling regarding the method claims for determining a pre-disposition to breast/ovarian cancer using the BRCA1 and BRCA2 genes relies at least in part upon the “M or T” test which, as noted above, SCOTUS unanimously relegated to “second class” status in Bilski as not the only test for patent-eligibility.

When embarking on a software development project it is critical to understand that in order to maximize the chance of obtaining a patent you need to approach the task with an engineering mind set, as well as a healthy familiarity with Murphy’s Law. Anything that can go wrong will go wrong, and once you release the process to end users a human element will complicate what should otherwise be a predictable, linear, machine driven response. Embrace the uncertainty and challenges because the fact that software rarely, if ever, works like it should is what makes a working process patentable.

So the fact that a method or process may be performed on a computer is not enough. I dare say that strict adherence to the Federal Circuit test in Bilski would compel a similar ruling that a method or process is not patentable even if it must be performed on a computer. Thus, the take home lesson moving forward must be that it is not enough to recite a computer, or even articulate an invention that necessarily must and only can be performed on a computer. At least for now these types of inventions must be described with a level of particularity that explains the innovation on a system level.

Several years after Arrhythmia, the Federal Circuit seemingly abandoned the Freeman-Walter-Abele test. Sitting en banc in Alappat the Federal Circuit did not apply the Freeman- Walter-Abele test, rather opting for the mathematical subject matter exception.

Amazon Technologies, Inc., received US Patent No. 7,610,382, which relates to a computer implemented method of marking copies of content distributed on a network. More specifically, the patent discloses and claims a variety of embodiments of a method and associated apparatus for programmatically substituting synonyms into text content distributed through a Web service.

The Redmond Giant, Microsoft Corporation, had US Patent Application 20090265604 publish, which seeks to protect a method for displaying a graphical representation of the vitality of a social network. This patent application was filed on April 21, 2008, and is one of many related to social networking that Microsoft has pending presently.

Sure, a computer programmer with time on their hands can write code and freely give it away, but that is not a business model or innovation strategy that will lead to widespread acceptance or use. In order for open source companies to grow they need to rely on investors who fund development, and investors are only going to be interested in funding development if there is a proprietary strategy in place. It is as simple as that.

The reason giant companies hate patent trolls is because they are not capable of being counter-sued. There is no deterrent effect because patent trolls do not make, use or sell anything, they just sue. So giant companies are targets in the same way that smaller companies without patents are targets of big companies with patents. No one should aspire to be a target. A simple truth is that a small business without patents might as well dress themselves up as a buck during hunting season complete with a bulls-eye pre-drawn. So here is the case for every business to get patents, particularly software patents. Ignore it if you like, but you do so at your own peril.

If you are pro-software patent you need to read this book because it will likely give you some wonderful insights that you can use to help you convince non-believers, and maybe even persuade a patent examiner or two. If you are anti-software patent I would also recommend you read this book as well. Plotkin’s positions are somewhat radical in that not only does he think software should be patented, but he wishes should be patentable as well, and that is exactly what will happen as computer automated inventing becomes increasingly more realistic.

Without software a computer is nothing more than a box of miscellaneous pieces that can’t do much of anything. They do make nice sticky-note holders, and they collect dust extremely well, but a computer without software is about as useless as a door without a knob, a clock without hands or a car without an engine. In other words, a computer without software is completely and totally useless. It is the software that directs a computer to do unique and often wonderful things, and it is the software that provides the innovative spark, not the machine. We do nothing but an injustice to ourselves to ignore this reality.

My position is that software must be patentable, or 500 years of patent laws make no sense. The reason that software must be patentable is that software can be an inseparable part of both manufacturing processes and electronic devices. A patent for such items must crucially include the software components of the invention, or the patent would be incomplete.

The United States Supreme Court granted cert. in Bilski v. Doll. This means that the last chapter on business methods and software has not yet been written, which could be good news or bad news depending upon your particular take. I have wondered out loud about allowing software patents as patentable subject matter, which I think is the right thing to do myself.

The trouble with freeware is that there is no margin on free, and while open source solutions are not free, the race to asymptotically approach free is on, hence why I say the race to zero is in full swing. As companies continue to look for the low cost solution, quality is sacrificed.