Jump to content

Software patent debate

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 173.65.73.222 (talk) at 01:48, 29 October 2012 (Copyright). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The software patent debate is the argument dealing with the extent to which it should be possible to patent software and computer-implemented inventions as a matter of public policy. Policy debate on software patents has been active for years.[1] The opponents to software patents have gained more visibility with less resources through the years than their pro-patent opponents.[2] Arguments and critiques have been focused mostly on the economic consequences of software patents.

One aspect of the debate has focused on the proposed European Union directive on the patentability of computer-implemented inventions, also known as the "CII Directive" or the "Software Patent Directive," which was ultimately rejected by the EU Parliament in July 2005.

Arguments for patentability

There are several arguments commonly given in defense of software patents or in defense of the patentability of computer-implemented inventions.

Promotes research and development

  • The basic principles of patent law were developed before computers were invented and have served societies for centuries. In the United States, the U.S. Constitution mandates that patent law promote "the progress of science and useful arts."[3] Supporters of software patents argue that inventions in the software arts are useful to modern life and therefore deserve the same incentive provided for inventions in other useful arts (i.e., to promote investment in research and development).[citation needed]

Public disclosure

  • A patent must publicly disclose the invention and so educate the public and advance the state of the art of the invention. Thus patents accelerate software development by making previously unknown and not obvious software inventions public.[citation needed]
  • Patents must disclose how to make and use an invention in sufficient detail so that other persons of ordinary skill in the art of the invention can make and use the invention without undue experimentation.[4] Furthermore, patents are only valid if the inventions they disclose were not known by the public prior to the filing of the patent application, or if the inventions were not obvious to those of ordinary skill in the art at the time the patent application was filed. (U.S. laws are somewhat different from other countries. In the U.S. the focus is on when the invention was made, not when the patent application was filed. This is changing, based on the America Invents Act).
  • Patents can be invalidated if they lack sufficient detail.[5]
  • The time delay between when a software patent application is filed, and when it becomes public is 18 months.[6] This is a compromise position allowing U.S. innovators to develop their software before revealing details about it and giving competitors an unfair look at their research and development, and providing the public notice within a fair amount of time to allow others to develop their own technology.[citation needed] The format in which software inventions are disclosed in patents (plain language text, flow charts, line drawings, etc.) allows a person with reasonable programming skills to recreate software capable of performing the ideas patented, as required by law.[citation needed] Copyleft publications by contrast, provide a different type of information addressing a different legal standard with different incentives.

Protection

  • Organizations should be able to protect their intellectual property.
  • In the U.S., the congress has stated that "anything under the sun made by man" deserves patent protection[7] to promote innovation.
  • Some aspects of software are also covered by copyright law, but those are largely different from the protection of ideas and innovation in the useful arts provided by patent law.[8]
  • Inventions can only be patented if they are non-obvious. This reduces the chance of patents being granted on mere algorithms with no technical effect[citation needed] or the granting of "trivial" patents with no inventive step.[9]

Economic benefit

  • Software patents resulting from the production of patentable ideas can increase the valuation of small companies.[10] Patent lawsuits are one of the tools available to combat large players in the software marketplace and allow innovative small companies to build a market of their own or at least receive fair compensation for their investment.[citation needed]
  • Patents encourage competitors to research and develop new and improved inventions, as a means of avoiding the licensing fees and restrictions requirements that prior patent holders can impose.[citation needed]

International law

Patent challenges

  • Granted patents can be revoked if found to be invalid.
  • If members of the public feel that an examiner has allowed an overly general claim in a patent, they may file an interpartes examination in the U.S., an opposition in Europe, or a lawsuit in Court, to argue that claims are overly broad and should not be allowed.
    • Opposition proceedings in Europe can take 2 to 5 years to complete and can be very expensive.[citation needed]

Patents protect functionality. Copyright on the other hand only protects expression. Substantial modification to an original work, even if it performs exactly the same function, would not be prevented by copyright. To prove copyright infringement also requires the additional hurdle of proving copying which is not necessary for patent infringement.

Arguments against patentability

Opponents of software patents argue that:

Hinders Research and Development

  • Some scientific studies and expert reviews have concluded that patent systems paradoxically hinder technological progress[13] and allows monopolies and powerful companies to exclude others from industrial science in a manner that is irreconcilable with anti-trust laws.[14]

Cost and loss of R&D funds

  • The high cost to acquire a patent relative to the investment to be made for "manufacture", "distribution", etc., means millions of software developers are unable to participate in the pluses of the patent system while feeling the brunt of potentially each and every single such patent exclusivity grant.
  • The cost of determining if a particular piece of software infringes any issued patents is too high and the results are too uncertain.[citation needed]
  • Should a software developer hire a patent attorney to perform a clearance search and provide a clearance opinion, there is no guarantee that the search could be complete. Different patents and published patent applications may use different words to describe the same concepts and thus patents that cover different aspects of the invention may not show up in a search. The cost of a clearance search may not prove to be cost effective to businesses with smaller budgets or individual inventors.[15]
  • Developers may be forced to pay license fees for standards that are covered by patents.
  • For the U.S. the economic benefit is dubious. A study in 2008 found that American public companies’ total profits from patents (excluding pharmaceuticals) in 1999 were about $4 billion, but that the associated litigation costs were $14 billion.[16]
  • It is argued that traditional copyright has provided sufficient protection to facilitate massive investment in software development.[17]
  • Copyright is the right of an author(s) to prevent others from copying their creative work without a license. Thus the author of a particular piece of software can sue someone that copies that software without a license (if the software is copyrightable). Copyright protection is given automatically and immediately without the need to register the copyright with a government, although registration does strengthen protection. Copyrighted material can also be kept secret.

Software is different

  • Software programs are different than other electromechanical devices because they are designed solely in terms of their function. The inventor of a typical electromechanical device must design new physical features to qualify for a patent. On the other hand, a software developer need only design new functions to create a working embodiment of the program.[18]
  • Software is a component of a machine. The computer’s hardware is generic; it performs functions that are common to all of the software that is capable of being executed on the computer. Each software program that is capable of executing on the computer is a component of the computer.[18]
  • Computers "design" and build the structure of executable software. Thus, the software developer does not design the executable software's physical structure because she merely provides the functional terms.[18]

Trivial patents

  • Anecdotal evidence suggests that some software patents cover either trivial inventions or inventions that would have been obvious to persons of ordinary skill in the art at the time the invention was made.[19]
  • Patent examiners rarely have a comprehensive knowledge of the specific technologies disclosed in the patent applications they examine. This is in large part due to the enormous number of micro-niches in the software field and the relatively limited number of examiners. So, patents are sometimes allowed on inventions that appear to be trivial extensions of existing technologies.[20]
  • Legal actions involving patent claims are very expensive, slow and unpredictable.[citation needed]

Open source disadvantage

  • The free and open source software community, and many companies that use and contribute to open source, oppose software patents because they can impede or prohibit the distribution of free software. They contend that patents threaten to undermine F/OSS, regardless of innovations produced by F/OSS collaborations.

Software patents usefulness as an information source is limited

  • Some patent disclosures in the software field are not readable to some programmers; as a result, patents are rarely used as a source of technical information by software developers.[21]

Patent examination is too slow

  • For 2005, the projected average pendency for patent applications in the "Computer Architecture, Software & Information Security" department of the U.S. Patent and Trademark Office was 3 and a half years.[22]
  • In Europe, the average time taken to grant a patent in any field of technology was almost 4 years in 2005,[23] with the computer related fields probably being greater than the average. By the time patent applications issue as patents, the inventions claimed therein will be perceived to be already in the public domain. This hurts inventors who see their inventions copied without permission, investors who fail to earn a suitable return on the salaries they paid to inventors, and the public which is faced with the uncertain prospects as to exactly what inventions are in the public domain and which inventions will be covered by a pending patent application.[citation needed]
  • Patents may be very different from the published applications, so the published application may only serve as a guide to the final scope of protection.[citation needed]

U.S. Court Cases

Bilski

The most prominent case believed to influence the future of software patents was by the Supreme Court of the United States. Bilski, as the case is commonly known, dealt with the legality of patenting business methods. Bilski and his partner Warsaw applied for and were denied a patent for their business method of hedging risks in commodities trading.[24] They sought to offer consumers a flat rate energy billing scheme and then balance the risk with the supplier of energy. The patent examiner rejected the patent on the grounds that it was not implemented in a specific apparatus and was purely abstract in nature.[25] Bilski brought the rejection to the patent office's appeals board who affirmed the rejection, although citing the error of the examiner for basing his analysis on the technological arts. The case was then heard en banc in front of the US Federal Circuit Court and the rejection was again affirmed, with Bilski's patent request failing the so-called "machine-transformation" test.

The case was heard by the US Supreme Court on November 9, 2009 and issued an opinion on appeal (as Bilski v. Kappos[26][27][28]) that affirmed the judgment of the CAFC, but revised many aspects of the CAFC's decision. In their decision, handed down on June 28, 2010, the Supreme Court rejected the machine-or-transformation test as the sole test of process patent eligibility based on an interpretation of the language of § 101.[29]

See also

References

  1. ^ Nichols, Kenneth (1998). Inventing Software: The Rise of "computer-related" Patents. Greenwood Publishing Group. p. 15. ISBN 1-56720-140-7.
  2. ^ Välimäki, Mikko (2005). The Rise of Open Source Licensing. Turre Publishing. ISBN 952-91-8779-3.
  3. ^ "United States Constitution - Article I". Cornell Law School. Retrieved 2008-06-19.
  4. ^ "35 U.S.C. 112 Specification. - Patent Laws". United States Patent Office. Retrieved 2008-06-21.
  5. ^ 2165 "The Best Mode Requirement - 2100 Patentability". United States Patent Office. Retrieved 2008-06-19. {{cite web}}: Check |url= value (help)
  6. ^ "1120 Eighteen Month Publication of Patent Applications".
  7. ^ "Diamond v. Chakrabarty, 447 U.S. 303 (1980)". US Supreme Court Center. Retrieved 2008-06-19.; but in "in Re Bilski, CAFC 08/833,892 (2008)" (PDF). United States Court of Appeals for the Federal Circuit. Retrieved 2008-11-05. [dead link] dissents Mayer, Dyk and Linn cite the full context as "A person may have “invented” a machine or a manufacture, which may include anything under the sun made by man, but it is not necessarily patentable under section 101 unless the conditions of the title are fulfilled.", with different interpretations.
  8. ^ "Patents for Software-Related Inventions". KuesterLaw. Retrieved 2008-06-19.
  9. ^ "Computer-Implemented Inventions (CII)". European Patent Office. Retrieved 2008-06-09.
  10. ^ "Ways in Which Patents can Help Your E-Commerce Business". World International Property Organization. Retrieved 2008-06-19.
  11. ^ Jürgen Betten "Patentschutz von Computerprogrammen" GRUR 1995, 775-789
  12. ^ Daniele Schiuma "TRIPS und das Patentierungsverbot von Software "als solcher" " GRUR Int 1998 852-858
  13. ^ Jaffe, Adam B.; Lerner, Joshua. Innovation and its discontents: how our broken patent system is endangering innovation and progress. ISBN 978-0-691-11725-6
  14. ^ http://www.jstor.org/pss/1821293
  15. ^ Mulligan, Christina and Lee, Timothy B., Scaling the Patent System (March 6, 2012). NYU Annual Survey of American Law, Forthcoming. Available at SSRN: http://ssrn.com/abstract=2016968
  16. ^ "Patent medicine - Why America's patent system needs to be reformed, and how to do it". Economist. 2011-08-20. Retrieved 2011-09-26.
  17. ^ "The Basics". NoSoftwarePatents.com. Retrieved 2008-06-19.
  18. ^ a b c Robert Plotkin. "Intellectual Property and the Process of Invention: Why Software is Different" (PDF). Law Office of Robert Plotkin. Retrieved 2011-09-30.
  19. ^ James Bessen & Michael J. Meurer "Patent Failure: How Judges, Bureaucrats, and Lawyers Put Innovators at Risk" Princeton University Press, 2008, ISBN 978-0-691-13491-8: many people have focused solely on patent examination quality as the objective of reform, based largely on anecdotal evidence of trivial, obvious, or otherwise invalid patents. Although we support efforts to improve patent examination quality (large numbers of questionable patents create conditions in which poor patent notice is unavoidable), our analysis suggests that this is only part of the problem and the patent system cannot likely be fixed by addressing only this issue. Of course, the notice problems that we find central to the poor performance of the patent system are not the only ones looking for a remedy. We argue, however, that many proposed reforms, including reforms directed toward improving patent examination quality, are unlikely to be effective unless patent notice is improved generally.
  20. ^ James Bessen & Michael J. Meurer "Patent Failure: How Judges, Bureaucrats, and Lawyers Put Innovators at Risk" Princeton University Press, 2008, ISBN 978-0-691-13491-8: It is possible, however, that features of software technology make it particularly susceptible to the patenting of obvious ideas, especially given the legal doctrines of non-obviousness developed by the Federal Circuit. For one thing, the general-purpose nature of software technology—again, because the technology Abstract Patents and Software 213 is abstract, similar techniques can be used in a wide range of applications— makes it inevitable that techniques known in one realm might be applied in another, yet the documentary evidence that the Federal Circuit requires for a demonstration of obviousness might not be published.
  21. ^ "Software patents need shelter from the storm". ZDNet - Tech News.
  22. ^ "Table 4: Patent Pendency Statistics". United States Patent Office.
  23. ^ "The patent process". European Patent Office.
  24. ^ Appendix of I re Bernard L. Bilski and Rand Warsaw, Text of patent application serial number 08/833892, US Court of Appeals for the Federal Circuit, 2007
  25. ^ BPAI decision rejecting the patent application (retrieved December 21, 2008).
  26. ^ http://www.ipwatchdog.com/2009/11/09/bilski-arguments-complete-at-the-us-supreme-court/id=7217/
  27. ^ Transcript of Oral Argument (PDF) in In re Bilski (Retrieved November 10, 2009)
  28. ^ http://www.scotuswiki.com/index.php?title=Bilski_v._Kappos Links to Briefs in In re Bilski (Retrieved November 10, 2009)
  29. ^ Bilski v. Kappos, No. 08-964, 561 U.S. ___ (2010), slip op. at 8.

Papers

Articles

Neutral sites

Sites in favor of patents on computer-implemented inventions

Sites against software patents