Software patents under United States patent law

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Computer programs, software and
patent law
Scale of justice 2.svg
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

Neither software nor computer programs are explicitly mentioned in United States patent law. Patent law changed to address new technologies and decisions of the United States Supreme Court and United States Court of Appeals for the Federal Circuit (CAFC) in the latter part of the 20th century sought to clarify the boundary between patent-eligible and patent-ineligible subject matter for a number of new technologies including computers and software.[citation needed]

The status eligibility of software for patent protection per se has not been directly addressed by either the courts or the legislature.[citation needed] In fact, in the recent Supreme Court decision in Alice v. CLS Bank, the Court painstakingly avoided the issue, and one Justice in the oral argument repeatedly insisted that it was unnecessary to reach the issue.[1] The expression "software patent" itself has not been clearly defined. The United States Patent and Trademark Office (USPTO) has permitted patents to be issued whose description included nothing but the steps of involved in the execution of software on a general purpose computer.[citation needed] Courts have both upheld such patents as valid and struck down such patents as invalid.[citation needed]

On June 19, 2014 the United States Supreme Court ruled in Alice Corp. v. CLS Bank International that "merely requiring generic computer implementation fails to transform [an] abstract idea into a patent-eligible invention." [2][3][4]

The ruling continued

[...] the mere recitation of a generic computer cannot transform a patent-ineligible abstract idea into a patent-eligible invention. Stating an abstract idea “while adding the words ‘apply it’” is not enough for patent eligibility.[] Nor is limiting the use of an abstract idea “‘to a particular technological environment.’”[]. Stating an abstract idea while adding the words“apply it with a computer” simply combines those two steps, with the same deficient result. Thus, if a patent’s recitation of a computer amounts to a mere instruction to“implemen[t]” an abstract idea “on . . . a computer,” [] that addition cannot impart patent eligibility.

Law[edit]

Article 1, section 8 of the United States Constitution establishes that the purpose of intellectual property is to serve a broader societal good, the promotion of "the Progress of Science and the useful Arts" :

Article 1, section 8 United States Constitution:

To 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;

Section 101 of title 35, United States Code, provides:

Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.[5]

However, there are restrictions on subject matter eligibility under Section 101 and in general the line between what is deemed patent eligible under Section 101 and what is ineligible changes is a matter of ongoing judicial activity.[6]

History[edit]

In the late 1960s and early 1970s, the USPTO and the United States Court of Customs and Patent Appeals (CCPA) were at odds over the patent-eligibility of technical advances whose departure from the prior art was only in the use of a software algorithm. The USPTO rejected such claims and declined to patent them, but the CCPA repeatedly reversed the USPTO's rulings and ordered the issuance of patents. The USPTO's position was hampered during the 1960s by the uncertainty over whether the Supreme Court could review decisions of the CCPA, because it was unclear whether it was an Article III court. That question was resolved, however, in Brenner v. Manson, in which the Court held that it had certiorari jurisdiction to review CCPA decisions.[7] That decision also began a string of decisions in which the Supreme Court reversed decisions of the CCPA, and then its successor court the United States Court of Appeals for the Federal Circuit (CAFC), which had reversed decisions of the USPTO denying a patent to an applicant.[8]

In the first of the Supreme Court's computer software decisions (the "patent-eligibility trilogy"), Gottschalk v. Benson,[9] the Court reversed the CCPA's reversal of a USPTO decision, thus denying a patent on an algorithm for converting binary-coded decimal numbers into pure binary numbers. In so ruling, the Court looked back to 19th century decisions such as O’Reilly v. Morse,[10] which held that abstract ideas could not be made the subject of patents. The Court's 1978 ruling in Parker v. Flook,[11] was similar in principle. These cases also established that the "clue" to whether a patent might be granted on a process was whether the process was carried out with a particular apparatus or else effectuated a transformation of an article from one state or thing to another state or thing. In Flook, where the sole departure from the prior art was concededly the formula or algorithm, no transformation was alleged, and it was conceded that the implementing apparatus was old or conventional, the process was simply not the kind of process that could be patented.

In the 1981 case of Diamond v. Diehr, the United States Supreme Court upheld the CCPA's reversal of the USPTO, and ordered the grant of a patent on an invention, a substantial part of which involved use of a computer program which used a well-known formula (the Arrhenius Equation) for calculating the time when rubber was cured and the mold could therefore be opened. The Supreme Court stated that in this case, the invention was not merely a mathematical algorithm, but a process for molding rubber, which was therefore patentable. In the Diehr case, there was no concession that the implementation was conventional, and the process did effectuate a transformation of substances (from uncured rubber to cured rubber).

After this point, more patents on software began to be granted, albeit with conflicting and confusing results. After its creation in 1982, the CAFC charted a course that tried to follow the Diehr precedent. Patents were allowed only if the claim included some sort of apparatus, even rather nominal apparatus at times, such as an analog-to-digital converter front end,[12] or in one case a scratch-pad memory for storing intermediate data.[13] A representative decision from this period is In re Schrader,[14] in which the CAFC set forth probably its best and most detailed formulation of the rule it was attempting to follow.

Dissatisfaction with the perceived artificiality of this rule erupted, however, in rulings beginning with the en banc 1994 decision in In re Alappat,[15] in which the CAFC majority held that a novel algorithm combined with a trivial physical step constitutes a novel physical device. Therefore, a computing device on which is loaded a mathematical algorithm is a "new machine", which is patentable. This ruling was immediately preceded by In re Lowry,[16] which held that a data structure representing information on a computer's hard drive or memory is similarly to be treated as a patent-eligible physical device, and in which the Solicitor General's Office declined the PTO's request to seek certiorari. As a result, the PTO did not even request that the Solicitor General's Office seek certiorari in the Alappat case. Finally, in State Street Bank v. Signature Financial Group,[17] the CAFC ruled that a numerical calculation that produces a "useful, concrete and tangible result", such as a price, is patent-eligible.[18]

"The USPTO gets ready to throw in the towel", cartoon published in IEEE Micro in 1994-1995(?)

The USPTO's reaction to this change was, for the time being at least, to "throw in the towel." The Clinton administration appointed Bruce Lehman as Commissioner of the USPTO in 1994. Unlike his predecessors, Lehman was not a patent lawyer but the chief lobbyist for the Software Publishing Industry.[19] In 1995, the USPTO established some broad guidelines for examining and issuing software patents. The USPTO interpreted the courts as requiring the USPTO to grant software patents in a broad variety of circumstances. Although the U.S. Congress has never legislated specifically that software is patentable, the broad description of patentable subject in the Patent Act of 1952 and the failure of Congress to change the law after the CAFC decisions allowing software patents, was interpreted as an indication of Congressional intent. The reaction of the defeated-feeling USPTO was characterized in the cartoon shown at right, which appeared in IEEE Micro at this time.

The United States Supreme Court remained silent on these decisions and developments for years. The first response appeared in a dissenting opinion in LabCorp v. Metabolite, Inc (2006). Although certiorari had been granted, the Court dismissed it as improvidently granted; the minority argued that the question of statutory subject matter in patent law should be addressed. Justice Breyer's dissent stated:

"[State Street] does say that a process is patentable if it produces a 'useful, concrete, and tangible result.' But this Court has never made such a statement and, if taken literally, the statement would cover instances where this Court has held the contrary."

He continues to directly address the claim that software loaded onto a computer is a physical device:

"...And the Court has invalidated a patent setting forth a process that transforms, for computer-programming purposes, decimal figures into binary figures-even though the result would seem useful, concrete, and at least arguably (within the computer's wiring system) tangible."

At about the same time, in a concurring opinion in eBay Inc. v. MercExchange, L.L.C.,[20] Justice Kennedy (joined by Justices Stevens, Souter, and Breyer)questioned the wisdom of permitting injunctions in support of "the burgeoning number of patents over business methods," because of their "potential vagueness and suspect validity" in some cases.

This was followed by the decision of the CAFC in In re Bilski, which has opened a new chapter in this history. In Bilski, as the article on that case explains, the CAFC superseded State Street and related decisions with a return to the tests of the patent-eligibility trilogy, although while those decisions had merely treated the machine-or-transformation test as the clue to past decisions the CAFC attempted to make that test dispositive. However, in 2009 the Supreme Court overturned the CAFC's decision in Bilski, stating that the machine-or-transformation test is not the exclusive test of patentability. At the same time, the Court (per Justice Kennedy) held, 5-4, that Bilski's software, business-method patent application was patent ineligible because it was directed to an abstract idea, largely preempting hedging as a business expedient. But the majority declined to rule all business-method patents ineligible. Justice Stevens, in one of his last opinions before retiring from the Court, concurred in the judgment but disagreed with the majority's rationale. Joined by Justices Ginsberg, Breyer, and Sotomayor, he argued that the claimed invention was patent ineligible because it was a business method (advancing much the same analysis as that in Judge Dyk's opinion in the Federal Circuit) and therefore outside the reach of the patent system.

Bilski was followed by the Court's unanimous opinion in Mayo Collaborative Services v. Prometheus Labs, Inc.[21] Although it did not involve a software patent (it concerned a medical assay implementing a natural principle), it stated a methodology for determining patent eligibility that is currently dominant in software cases. It revived the approach of the Flook and Neilson cases, which is to treat the underlying principle, idea, or algorithm on which the claimed patent is based as if it were part of the prior art and to make patent eligibility turn on whether the implementation of it is inventive.

Shortly after that, the CAFC issued a very fragmented en banc decision in CLS Bank International v. Alice Corp. in which the judges were unable to reach a coherent decision on the patentability of the business-method, software claims at issue. The case went to the Supreme Court, which decided it on June 19, 2014. As explained in greater detail in the article on that case, the Court, using the analysis set forth in the Mayo case, held Alice's patents invalid as directed to an abstract idea. As in Bilski, the Court declined to rule business-method patents categorically ineligible, but the Court's requirement for an "inventive concept" for the implementation of the principle underlying the claimed method and its insistence that "merely saying apply it with a computer" is not enough to confer patent eligibility may doom many or most business-method, software patents.[22]

Since the Alice decision, the Federal Circuit and district courts have held a number of business-method patents to be patent ineligible as mere abstract ideas implemented in a conventional way without embodying any inventive concept.

In Digitech Image Technologies, LLC v. Electronics for Imaging, Inc.,[23] the Federal Circuit invalidated a patent on a “device profile” and methods for generating “device profiles.” The device profile was a collection of information about a graphic image, and it was generated by combining data sets containing such information. The court held that the device and method for generating it were abstract ideas and patent ineligible: “Without additional limitations, a process that employs mathematical algorithms to manipulate existing information to generate additional information is not patent eligible.”

In buySAFE, Inc. v. Google, Inc.,[24] the Federal Circuit invalidated under section 101 a patent on a computerized surety system for online transactions. The court said the computer implementation of the underlying surety idea was “not even arguably inventive.” The court concluded: “In short, with the approach to this kind of section 101 issue clarified by Alice, it is a straightforward matter to conclude that the claims in this case are invalid.” The court remarked in passing, however, that if “enough extra is included in a claim, it passes muster under section 101 even if it amounts to a business method.” But the court did not explain or illustrate what would be “enough extra.”

Landmark decisions[edit]

See also[edit]

References[edit]

  1. ^ Alice Corp. Pty. Ltd. v. CLS Bank Int'l, 573 U.S. ___ (2014). During oral argument, Justice Sotomayor repeatedly asked counsel whether Alice was a software case: "Why do we need to reach . . . software patents at all in this case?"; "What's the necessity for us to announce a general rule with respect to software? There is no software being patented in this case."; "Do you think we have to reach the patentability of software to answer this case?" The Court's opinion in Alice does not discuss the patent eligibility of software as such.
  2. ^ http://abcnews.go.com/Technology/wireStory/supreme-court-tosses-software-patent-24210428
  3. ^ http://www.washingtonpost.com/blogs/the-switch/wp/2014/06/19/the-supreme-court-has-unanimously-struck-down-a-software-patent-that-everyone-agreed-was-terrible/
  4. ^ http://www.forbes.com/sites/danielfisher/2014/06/19/patent-lawyers-software-companies-like-alice-corp-ruling-trolls-not-so-much/
  5. ^ 35 U.S.C. 101 Inventions patentable. - Patent Laws
  6. ^ http://www.lexisnexis.com/community/patentlaw/blogs/patentcommentary/archive/2012/03/27/eric-e-bensen-on-the-supreme-court-s-decision-in-mayo-collaborative-servs-v-prometheus-labs.aspx
  7. ^ 383 U.S. 519 (1966).
  8. ^ Almost invariably, the Supreme Court's grant of certiorari in a USPTO case has resulted in reversal of the decision of the court below and reinstatement of a USPTO decision denying a patent.
  9. ^ 409 U.S. 63 (1972)
  10. ^ 56 U.S. (15 How.) 62 (1853).
  11. ^ 437 U.S. 584 (1978).
  12. ^ Arrhythmia Research Tech. v. Corazonix Corp., 958 F.2d 1053 (Fed. Cir. 1992).
  13. ^ See In re Iwahashi, 888 F.2d 1370 (Fed. Cir. 1989).
  14. ^ 22 F.3d 290 (Fed. Cir. 1994).
  15. ^ 33 F.3d 1526 (1994).
  16. ^ 32 F.3d 1579, 1582 (Fed. Cir. 1994).
  17. ^ 149 F.3d 1368 (Fed. Cir. 1998).
  18. ^ See also AT&T Corp. v. Excel Communications, Inc., 172 F.3d 1352 (Fed. Cir. 1999) (similar ruling, upholding patent based on Boolean ANDing).
  19. ^ See Developments in the Economics of Copyright: Research and Analysis (eds. Lisa Takeyama, Wendy J. Gordon, Ruth Towse) at note 34 and accompanying text, available at http://books.google.com/books?id=ecPJSiHIi2kC&pg=PA17&lpg=PA17&dq=%22Business+Software+Alliance%22+%22bruce+lehman%22&source=bl&ots=AB0bhcvwJs&sig=-P1MAbCTwwXxVwDZcTWSN0-DvcU&hl=en&sa=X&ei=_EF6U9DrB6vMsQTZvYDYAg&ved=0CFUQ6AEwBw#v=onepage&q=%22Business%20Software%20Alliance%22%20%22bruce%20lehman%22&f=false .
  20. ^ 547 U.S. 388 (2006).
  21. ^ 132 S. Ct. 1289 (2012).
  22. ^ See Richard H. Stern, Alice v CLS Bank: US Business Method and Software Patents Marching towards Oblivion?, [2014] Eur. Intell. Prop. Rev. 619, 626, suggesting that "most business methods will fail to pass muster under the Flook-Mayo-Alice rationale." See also Richard H. Stern, Alice v. CLS Bank: Are US Business-Method and Software Patents Doomed? Part 1, IEEE Micro, Sept./Oct. 2014, at p. 6 ("A majority of the Court refused to address the patent eligibility of business methods as such. Yet, because of their typical abstractness, and because of the legal analysis that the Court prescribed for implementations of abstract ideas, business-method patents now seem like lemmings marching in the thousands toward oblivion. That is not equally so for all software patents, of which business-method patents are a major subset. The Court left some room for non-business-method software patents.").
  23. ^ — F.3d —, 2014 WL 3377201 (July 11, 2014).
  24. ^ — F.3d —, 2014 WL -- (Sept. 3, 2014).

Further reading[edit]