ProductsDesktop Server Red Hat Enterprise Linux OpenStack Platform For IBM POWER For IBM System z For SAP Business Applications Red Hat Satellite Management For Scientific ComputingExtended Update Support High Availability High Performance Network Load Balancer Resilient Storage Scalable File System Smart Management Extended Lifecycle SupportAccelerate Automate Integrate Red Hat JBoss Developer Studio Portfolio Edition Web Framework Kit Application Platform Web Server Data Grid Portal Fuse Red Hat JBoss A-MQ SOA Platform BRMS Data Services Platform JBoss Operations Network JBoss Community or JBoss enterprise
SolutionsWhy Red Hat Why open hybrid cloud? The new IT Public cloud Cloud resource library Private cloud Infrastructure-as-a-Service (IaaS) Platform-as-a-Service (PaaS) Cloud applications and workloadsSolaris to Red Hat Enterprise Linux Migration overview Migrate from your UNIX platform How to migrate to Red Hat Enterprise Linux Upgrade to the latest Red Hat Enterprise Linux release JBoss Enterprise Middleware Benefits of migrating to Red Hat Enterprise Linux Migration services Start a conversation with Red Hat
TrainingClassroom training Red Hat Online Learning Virtual training Remote classroom training On-site team training Online Learning LabsPopular and new courses Red Hat JBoss Administration curriculum Core System Administration curriculum Red Hat JBoss Middleware Development curriculum Advanced System Administration curriculum Linux Development curriculum Cloud Computing, Virtualization, and Storage curriculum
ConsultingSOA and integration Business process management Cloud and Virtualization Custom Software Development Enterprise Data and Storage Systems management Migrations
Red Hat Responds to U.S. Patent and Trademark Office Request for Guidance on Bilski
September 28, 2010
by Legal Team
Yesterday Red Hat has submitted comments to the U.S Patent and Trademark Office regarding interpretation of the Supreme Court’s Bilski decision.
The submission was made in response to the PTO’s request for public comments to assist it in determining how to apply the Supreme Court’s decision in that case. Although the Bilski decision did not expressly address the standards for refusing to allow software patents, interpretation of the decision will determine whether certain patents are granted. Thus the PTO’s approach to examining patent applications will have a substantial effect on the patent landscape.
Red Hat previously submitted an amicus brief in Bilski. Its comments to the PTO indicate its continuing commitment to reform of the patent system to address the harms caused by poor quality software patents.
Red Hat’s comments to the PTO, which were submitted by Rob Tiller, its Vice President and Assistant General Counsel, IP, follow below:
Red Hat appreciates the opportunity to submit comments regarding the Interim Guidance for Determining Subject Matter Eligibility for Process Claims in View of Bilski v. Kappos (Interim Guidance). As the world’s leading provider of open source software and related services to enterprise customers, Red Hat has a keen interest in this issue, particularly as it relates to applications for software patents.
Today there are hundreds of thousands of patents relating to software, and tens of thousands continue to be granted each year. In many cases, these patents have vague and uncertain boundaries. Thus it is virtually impossible to determine whether a new software product could be deemed to infringe an existing patent. This means that introducing any innovative software product entails a risk of a lawsuit based on a vague patent. Such lawsuits often cost millions of dollars to defend, along with the risk of actual damages, treble damages, and injunctions. Far from encouraging innovation, vague software patents discourage it. The problem of vagueness is so endemic in software patents that it warrants action at the threshold level of subject matter eligibility.
In view of this serious problem, Red Hat submits that the Interim Guidance should be revised to recognize that software patents will ordinarily fail to satisfy the requirements of 35 U.S.C. Section 101 as interpreted in Bilski and prior Supreme Court cases. Software is essentially nothing more than a set of mathematical algorithms expressed in a particular programming or machine language. As the Bilski Court recognized, mathematical algorithms, by themselves, are abstract ideas that are not patentable.
As the Supreme Court found in Diehr and reiterated in Bilski, an application of a mathematical formula (as opposed to the formula by itself) may be entitled to patent protection. This does not mean, however, that merely storing or running software on a general purpose computer justifies granting a patent on an otherwise unpatentable algorithm. This is clear from the Supreme Court’s Benson decision, which rejected as an unpatentable abstract idea a mathematical algorithm capable of being used in programming a general purpose computer. Thus the statement in the Interim Guidance that “recitation of some structure, such as a machine…will in most cases limit the claim to such an application” is overly broad and subject to misinterpretation.
The Bilski Court strongly reaffirmed that abstract ideas, including mathematical algorithms, are not patentable. In applying Bilski, the Patent and Trademark Office should recognize the applicability of this principle to software patents. This course is consistent both with the Supreme Court’s teachings and the core patent objective of encouraging innovation.