Computer programs, software and patent law
Topics
Software patent Debate Free software List of patents
Treaties
TRIPS Agreement Patent Cooperation Treaty European Patent Convention
Countries
Canada United Kingdom United States
Case law
European Patent Office United Kingdom
Related topics
Business methods

Patent law
Overviews
Patents History Economics Societal views
Basic concepts
Application Prosecution Licensing Infringement Valuation
Patentability
Novelty Inventive step and non-obviousness Inventorship Industrial applicability Patentable subject matter Person skilled in the art Prior art Utility
Additional requirements
Sufficiency of disclosure Unity of invention
By region / country
Patent Cooperation Treaty Australia Canada China Europe Germany Japan Netherlands United States
By specific subject matter
Biological Business method Chemical Insurance Software Tax
See also
Category Glossary

A suggested definition of software patent has been proposed by the Foundation for a Free Information Infrastructure (FFII) as being a "patent on any performance of a computer realised by means of a computer program".^[1] There is no legal or conclusive definition for a software patent.^[2]

Globally the situation is more complex and reflects varying cultural views of invention itself.^{[citation needed][vague]} Most countries place some limits on the patenting of inventions involving software, but there is no one legal definition of a software patent. For example, U.S. patent law excludes "abstract ideas", and this has been used to refuse some patents involving software. In Europe, "computer programs as such" are excluded from patentability, thus European Patent Office policy is consequently that a program for a computer is not patentable if it does not have the potential to cause a "further technical effect" beyond the inherent technical interactions between hardware and software.^[3]

There is a debate over the extent to which software patents should be granted, if at all. Important issues concerning software patents include:

• Whether software patents should be allowed, and if so, where the boundary between patentable and non-patentable software should lie;^[4]
• Whether the inventive step and non-obviousness requirement is applied too loosely to software;^[5] and
• Whether patents covering software discourage, rather than encourage, innovation.^[6]

Background[edit]

A patent is a set of exclusionary rights granted by a state to a patent holder for a limited period of time, usually 20 years. These rights are granted to patent applicants in exchange for their disclosure of the inventions. Once a patent is granted in a given country, no person may make, use, sell or import/export the claimed invention in that country without the permission of the patent holder. Permission, where granted, is typically in the form of a license which conditions are set by the patent owner: it may be gratis or in return for a royalty payment or lump sum fee.

Patents are territorial in nature. To obtain a patent, inventors must file patent applications in each and every country in which they want a patent. For example, separate applications must be filed in Japan, China, the United States and India if the applicant wishes to obtain patents in those countries. However, some regional offices exist, such as the European Patent Office (EPO), which act as supranational bodies with the power to grant patents which can then be brought into effect in the member states, and an international procedure also exists for filing a single international application under the Patent Cooperation Treaty (PCT), which can then give rise to patent protection in most countries.

These different countries and regional offices have different standards for granting patents. This is particularly true of software or computer-implemented inventions, especially where the software is implementing a business method.

Early example of a software patent[edit]

On 21 May 1962, a British patent application entitled "A Computer Arranged for the Automatic Solution of Linear Programming Problems" was filed.^[7] The invention was concerned with efficient memory management for the simplex algorithm, and could be implemented by purely software means. The patent was granted on August 17, 1966 and seems to be one of the first software patents.^[8][9]

Jurisdictions[edit]

Substantive law regarding the patentability of software and computer-implemented inventions, and case law interpreting the legal provisions, are different under different jurisdictions.

Software patents under multilateral treaties:

• Software patents under TRIPs Agreement
• Software patents under the European Patent Convention
• Computer programs and the Patent Cooperation Treaty

Software patents under national laws:

• Software patents under United States patent law
• Software patents under United Kingdom patent law

Australia[edit]

In Australia, pure or abstract methods of doing business are not considered to be patentable, but if the method is implemented using a computer, it avoids the exclusion for business methods.^{[10][non-primary source needed]}

Canada[edit]

In Canada, courts have held that the use of a computer alone neither lends, nor reduces patentability of an invention. However, it is the position of the Canadian Patent Office that where a computer is an "essential element" of a patent's claims, the claimed invention is generally patentable subject matter.^[11]

Europe[edit]

Within European Union member states, the EPO and other national patent offices have issued many patents for inventions involving software since the European Patent Convention (EPC) came into force in the late 1970s. Article 52 EPC excludes "programs for computers" from patentability (Art. 52(2)) to the extent that a patent application relates to a computer program "as such" (Art. 52(3)). This has been interpreted to mean that any invention that makes a non-obvious "technical contribution" or solves a "technical problem" in a non-obvious way is patentable even if that technical problem is solved by running a computer program.^[12]

Computer-implemented inventions that only solve a business problem using a computer, rather than a technical problem, are considered unpatentable as lacking an inventive step (see T 258/03). Nevertheless, the fact that an invention is useful in business does not mean it is not patentable if it also solves a technical problem.

A summary of the developments concerning patentability of computer programs under the European Patent Convention is given in (see G 3/08) as a response of the Enlarged Board of Appeal to questions filed by the President of the European Patent Office according to Art. 112(1)b) EPC.

Germany[edit]

In April 2013, the German Parliament adopted a joint motion "against the growing trend of patent offices to grant patents on software programs."^[13]

United Kingdom[edit]

United Kingdom patent law is interpreted to have the same effect as the European Patent Convention such that "programs for computers" are excluded from patentability to the extent that a patent application relates to a computer program "as such". Current case law in the UK states that an (alleged) invention will only be regarded as an invention if it provides a contribution that is not excluded and that is also technical. A computer program implementing a business process is therefore not an invention, but a computer program implementing an industrial process may well be.

India[edit]

In India, a clause to include software patents was quashed by the Indian Parliament in April 2005.^[14] Software Patents are not accepted by the Indian Patent Office.

Japan[edit]

Software-related inventions are patentable. To qualify as an invention, however, there must be "a creation of technical ideas utilizing a law of nature"^[15] although this requirement is typically met by "concretely realising the information processing performed by the software by using hardware resources".^[16] Software-related inventions may be considered obvious if they involve: the application of an operation known in other fields; the addition of a commonly known means or replacement by equivalent; the implementation in software of functions which were previously performed by hardware; or the systematisation of known human transactions.^[17]

In 1999, the allowance rate for business method patents at the Japan Patent Office (JPO) reached an all-time high of roughly 35 percent. Subsequently, the JPO experienced a surge in business method patent filings. This surge was met with a dramatic decrease in the average grant rate of business method patents during the following six years; it lingered around 8 percent between 2003 and 2006 (8 percent is extremely low in comparison to the average of 50 percent across all technical fields). Since 2006, the average grant rate for business method patents has risen to the current rate of roughly 25 percent.^[18]

New Zealand[edit]

In New Zealand computer programs are to be excluded from patentability under a 2010 Patents Bill, but guidelines permitting embedded software are to be drafted once the bill has passed.^{[19][20][21][22][23]} From 2013 computer programs 'as such' are excluded from patentability. The as such wording rules out only those software based patents where novelty lies solely in the software. Similar to Europe.^[24]

Philippines[edit]

In the Philippines, "schemes, rules and methods of performing mental acts, playing games or doing business, and programs for computers" are non-patentable inventions under Sec. 22.2 of Republic Act No. 8293, otherwise known as the "Intellectual Property Code of the Philippines."

Russian Federation[edit]

In Russian Federation according to article #1350 of the Civil Code the following is not patentable

2) scientific theories and math methods;

4) rules of games and methods of playing, intellectual and economic activity;

5) software for computers;

South Africa[edit]

In South Africa, "a program for a computer" is excluded from recognition as an invention by section 25(2) of the Patents Act.^[25] However, this restriction applies "only to the extent to which a patent or an application for a patent relates to that thing as such"^[26] and should not prevent, for example, a product, process, or method which may be implemented on a computer from being an invention, provided that the requirements of novelty and inventiveness are met.

South Korea[edit]

In South Korea, software is considered patentable and many patents directed towards "computer programs" have been issued.^[27] In 2006, Microsoft's sales of its "Office" suite were jeopardized due to a possible patent infringement.^[28] A ruling by the Supreme Court of Korea found that patents directed towards automatic language translation within software programs were valid and possibly violated by its software.^[28]

United States[edit]

The United States Patent and Trademark Office has granted patents that may be referred to as software patents since at least the early 1970s.^[29] In Gottschalk v. Benson (1972), the United States Supreme Court ruled that a patent for a process should not be allowed if it would "wholly pre-empt the mathematical formula and in practical effect would be a patent on the algorithm itself", adding that "it is said that the decision precludes a patent for any program servicing a computer. We do not so hold."^[30] In 1981, the Supreme Court stated that "a claim drawn to subject matter otherwise statutory does not become nonstatutory simply because it uses a mathematical formula, computer program, or digital computer" and a claim is patentable if it contains "a mathematical formula [and] implements or applies the formula in a structure or process which, when considered as a whole, is performing a function which the patent laws were designed to protect".^[31]

Due to different treatment of federal patent rights in different parts of the country, in 1982 the U.S. Congress created a new court (the Federal Circuit) to hear patent cases. Following several landmark decisions by this court, by the early 1990s the patentability of software was well established, and in 1996 the USPTO issued Final Computer Related Examination Guidelines stating that "A practical application of a computer-related invention is statutory subject matter. This requirement can be discerned from the variously phrased prohibitions against the patenting of abstract ideas, laws of nature or natural phenomena" (emphasis added).^[32]

The recent expansion of the Internet and e-commerce has led to many patents being applied for and being granted for business methods implemented in software and the question of whether business methods are statutory subject matter is a separate issue from the question of whether software is. Critics of the Federal Circuit believe that the non-obviousness standard is partly responsible for the large increase in patents for software and business methods.^[33] There have been several successful enforcement trials in the USA, some of which are listed in the list of software patents article.

Several successful litigations show that software patents are enforceable in the US. See List of software patents for more examples.

Purpose of patents[edit]

For the U.S., the purpose of patents is laid down in the constitutional clause that gives Congress the power "[t]o promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries;" (Article I, Section 8, Clause 8). For Europe, there is no similar definition. Commonly four patent justification theories are recognised, as laid down for instance by Machlup in 1958,^[34] which include justice to the inventor and benefit for society by rewarding inventors. Disclosure is required in return for the exclusive right, and disclosure may promote further development. However, the value of disclosure should not be overestimated: some inventions could not be kept secret otherwise, and patents also prohibit independent reinventions to be exploited.

There is debate as to whether or not these aims are achieved with software patents.

Proposals[edit]

In seeking to find a balance, different countries have different policies as to where the boundary between patentable and non-patentable software should lie. In Europe, a number of different proposals for setting a boundary line were put forward during the debate concerning the proposed Directive on the patentability of computer-implemented inventions, none of which were found acceptable by the various parties to the debate. Two particular suggestions for a hurdle that software must pass to be patentable include:

• A computer program that utilises "controllable forces of nature to achieve predictable results".^[35][36]
• A computer program which provides a "technical effect".^[37]

In the US, Ben Klemens, a Guest Scholar at the Brookings Institution, proposed that patents should be granted only to inventions that include a physical component that is by itself nonobvious.^[38] This is based on Justice William Rehnquist's ruling in the U.S. Supreme Court case of Diamond v. Diehr that stated that "... insignificant postsolution activity will not transform an unpatentable principle into a patentable process."^{[citation needed]} By this rule, one would consider software loaded onto a stock PC to be an abstract algorithm with obvious postsolution activity, while a new circuit design implementing the logic would likely be a nonobvious physical device. Upholding an "insignificant postsolution activity" rule as per Justice Rehnquist's ruling would also eliminate most business method patents.

Obviousness[edit]

A common objection to software patents is that they relate to trivial inventions.^[39] A patent on an invention that many people would easily develop independently of one another should not, it is argued, be granted since this impedes development.

Different countries have different ways of dealing with the question of inventive step and non-obviousness in relation to software patents. Europe uses an 'Inventive step test'; see the Inventive step requirement in Europe and, for instance, T 258/03.

Criticism[edit]

Compatibility[edit]

There are a number of high-profile examples where the patenting of a data exchange standards forced another programming group to introduce an alternative format. For instance, the Portable Network Graphics (PNG) format was largely introduced to avoid the Graphics Interchange Format (GIF) patent problems, and Ogg Vorbis to avoid MP3. If it is discovered that these new suggested formats are themselves covered by existing patents, the final result may be a large number of incompatible formats. Creating such formats and supporting them costs money and creates inconvenience to users.

Computer-implemented invention (CII)[edit]

Under the EPC, and in particular its Article 52,^[40] "programs for computers" are not regarded as inventions for the purpose of granting European patents,^[41] but this exclusion from patentability only applies to the extent to which a European patent application or European patent relates to a computer program as such.^[42] As a result of this partial exclusion, and despite the fact that the EPO subjects patent applications in this field to a much stricter scrutiny^[43] when compared to their American counterpart, that does not mean that all inventions including some software are de jure not patentable.

Overlap with copyright[edit]

Protection by patent protection and copyright constitute two different means of legal protection which may cover the same subject-matter, such as computer programs, since each of these two means of protection serves its own purpose.^[44] Software is protected as works of literature under the Berne Convention. This allows the creator to prevent another entity from copying the program and there is generally no need to register code in order for it to be copyrighted.

Patents, on the other hand, give their owners the right to prevent others from using a claimed invention, even if it was independently developed and there was no copying involved. In fact, one of the most recent EPO decisions^[45] clarifies the distinction, stating that software is patentable, because it is basically only a technical method executed on a computer, which is to be distinguished from the program itself for executing the method, the program being merely an expression of the method, and thus being copyrighted.

Patents cover the underlying methodologies embodied in a given piece of software, or the function that the software is intended to serve, independent of the particular language or code that the software is written in. Copyright prevents the direct copying of some or all of a particular version of a given piece of software, but does not prevent other authors from writing their own embodiments of the underlying methodologies. Copyright can also be used to prevent a given set of data from being copied while still allowing the author to keep the contents of said set of data a trade secret.^{[citation needed]}

Whether and how the numerus clausus principle shall apply to the legal hybrid software^[46] to provide a judicious balance between property rights of the title holders and freedom rights of computing professionals^[47] and the society as a whole,^[48] is in dispute.^[49][50][51]

Free and open source software[edit]

There is strong dislike in the free software community towards software patents. Much of this has been caused by free software or open source projects terminating^[52] when the owners of patents covering aspects of a project demanded license fees that the project could not pay, or was not willing to pay, or offered licenses with terms that the project was unwilling to accept, or could not accept, because it conflicted with the free software license in use.^[53]

Several patent holders have offered royalty-free patent licenses for a very small portion of their patent portfolios. Such actions have provoked only minor reaction from the free and open source software communities for reasons such as fear of the patent holder changing their mind or the license terms being so narrow as to have little use.^[54] Companies that have done this include Apple Inc,^{[citation needed]} IBM,^[55] Microsoft,^[56] Nokia,^{[citation needed]} Novell,^[57] Red Hat,^[58] and Sun Microsystems.^[59]

In 2005 Sun Microsystems announced that they were making a portfolio of 1,600 patents available through a patent license called Common Development and Distribution License.^[60]

In 2006, Microsoft's pledge not to sue Novell Linux customers, openSUSE contributors, and free/open source software developers over patents^[61] and the associated collaboration agreement with Novell^[62] was met with disdain from the Software Freedom Law Center^[63] while commentators from the Free Software Foundation stated that the agreement would not comply with GPLv3.^[64] Meanwhile, Microsoft has reached similar agreements with Dell, Inc. and Samsung,^[65] due to alleged patent infringements of the GNU/Linux operating system. Microsoft has also derived revenue from Android by making such agreements-not-to-sue with Android vendors.^[66]

Unisys case[edit]

In the late 1990s, Unisys claimed to have granted royalty free licenses to hundreds of not-for-profit organizations that used the patented LZW compression method and, by extension, the GIF image format. However, this did not include most software developers and Unisys were "barraged" by negative and "sometimes obscene" emails from software developers.^[67]

Licensing[edit]

Patenting software is widespread in the US. As of 2004, approximately 145,000 patents had issued in the 22 classes of patents covering "computer implemented inventions". (see table to the right).

Many software companies cross license their patents to each other. These agreements allow each party to practice the other party's patented inventions without the threat of being sued for patent infringement. Microsoft, for example, has agreements with IBM, Sun Microsystems (now Oracle Corporation), SAP, Hewlett-Packard, Siemens AG, Cisco, Autodesk^[68] and recently Novell. Microsoft cross-licensed its patents with Sun, despite being direct competitors, and with Autodesk even though Autodesk has far fewer patents than Microsoft.

The ability to negotiate cross licensing agreements is a major reason that many software companies, including those providing open source software, file patents. As of June 2006, for example, Red Hat has developed a portfolio of 10 issued US patents, 1 issued European patent, 163 pending US patent applications, and 33 pending international PCT (Patent Cooperation Treaty) patent applications. Red Hat uses this portfolio to cross license with proprietary software companies so that they can preserve their freedom to operate.^[58]

Other patent holders are in the business of inventing new "computer implemented inventions" and then commercializing the inventions by licensing the patents to other companies that manufacture the inventions. Walker Digital, for example, has generated a large patent portfolio from its research efforts, including the basic patent on the Priceline.com reverse auction technology. US universities also fall into this class of patent owners. They collectively generate about $1.4 billion per year through licensing the inventions they develop to both established and start up companies in all fields of technology, including software.^[69]

Still other patent holders focus on obtaining patents from original inventors and licensing them to companies that have introduced commercial products into the marketplace after the patents were filed. Some of these patent holders, such as Intellectual Ventures, are privately held companies financed by large corporations such as Apple, Microsoft, Intel, Google, etc. Others, such as Acacia Technologies, are publicly traded companies with institutional investors being the primary shareholders.^[70]

The practice of acquiring patents merely to license them is controversial in the software industry. Companies that have this business model are pejoratively referred to as patent trolls. It is an integral part of the business model that patent licensing companies sue infringers that do not take a license. Furthermore, they may take advantage of the fact that many companies will pay a modest license fee (e.g.$100,000 to $1,000,000) for rights to a patent of questionable validity, rather than pay the high legal fees ($2,000,000 or more) to demonstrate in court that the patent is invalid.^{[citation needed]}

See also[edit]

• Agreement on Trade-Related Aspects of Intellectual Property Rights (TRIPS Agreement)
• Open Invention Network (OIN)
• Patent Commons Project
• Proposed directive on the patentability of computer-implemented inventions
• Piano roll blues

References[edit]

External links[edit]

• Software and Business Methods on the WIPO web site
• FFII Annotated Bibliography
• Softwarepatents.eu, an introduction to software patents in Europe and Germany (in German)

Economic studies[edit]

• Bessen; Hunt (2004), An Empirical Look at Software Patents (PDF)  This paper includes a method of identifying software patents that has proved popular with organisations such as the Public Patent Foundation
• Bessen, James; Hunt, Robert M. (March 16, 2004), The Software Patent Experiment (PDF) 
• Hahn, Robert; Wallsten, Scott, A Review of Bessen and Hunt's Analysis of Software Patents (PDF), American Enterprise Institute 
• Bessen, James; Hunt, Robert M. (March 10, 2004), A Reply to Hahn and Wallsten (PDF) 
• Federal Trade Commission (October 2003), To Promote Innovation: The Proper Balance of Competition and Patent Law and Policy, A Report by the Federal Trade Commission (PDF) 
• FTC 2003 Report on Patents and Competition, Foundation for a Free Information Infrastructure (FFII), 2004-08-16  – commentary on the FTC "To Promote Innovation" report, 2003 (translated into English)
• Noel, Michael; Schankerman, Mark (August 2006), CEP Discussion Paper No 740: Strategic Patenting and Software Innovation (PDF), Centre for Economic Performance, London School of Economics and Political Science 
• Miller, Shawn; Tabarrok, Alex (Jan 2014), "Ill-Conceived, Even If Competently Administered: Software Patents, Litigation, and Innovation—A Comment on Graham and Vishnubhakat" (PDF), Econ Journal Watch 

Books[edit]

• Bessen, James; Meurer, Michael (2008). Patent Failure. Princeton University Press. 
• Klemens, Ben (2005). Math You Can't Use: Patents, Copyright, and Software. Brookings Institution Press. 
• Warshofsky, Fred (October 3, 1994). The Patent Wars: The Battle to Own the World's Technology. Wiley. ISBN 978-0471599029. 
• Information Feudalism - Peter Drahos Drahos, Peter (May 1, 2003). Information Feudalism: Who Owns the Knowledge Economy?. The New Press. ISBN 1565848047. 
• Müller, Florian (2006). No Lobbyists As Such: The War over Software Patents in the European Union (PDF).  – 377-page play-by-play memoir of the story of Florian's part in the campaign over the EU software patent directive.
• Leith, Philip (2007). Software and Patents in Europe. Cambridge University Press. 

Papers and presentations[edit]

• Hunt, R, You can patent that? (PDF)  – Overview of the legal history and trends
• Szabo, N., Elemental Subject Matter (PDF)  – How software came to be patentable in the United States
• Pellegrini, François (2007), "Analysis of software patentability in Europe (Chapter 11)", Software Patents - Legal Perspectives (PDF), Amicus Books - ICFAI University Press, pp. 192–209, ISBN 81-314-0653-9 
• Furutani, Hideo (2003), Patentability of Business Method Inventions in Japan Compared with the US and Europe (PDF presentation), Arlington, Virginia; United States Patent and Trademark Office 
• Stallman, Richard M. (May 24, 2004), The Dangers of Software Patents 
• Abecassis, Alexandre. "Patenting Software Innovations: A brief overview of the situation in some jurisdictions of interest" (PDF) (55). Institute of Electrical and Electronics Engineers (IEEE). pp. 24–27. 
• Kahin, Brian (April 1990). "The Software Patent Crisis". Technology Review (Massachusetts Institute of Technology).