United States: Software Inventions—Keeping It Eligible

Takeaways and Practical Considerations from the PTO's Preliminary Examination Instructions on Patent-Eligible Subject Matter in view of Alice Corporation Pty. Ltd. v. CLS Bank International, et al.

On June 19, 2014, the United States Supreme Court issued its opinion in Alice Corporation Pty. Ltd. v. CLS Bank International, et al. ("Alice"). Alice's claims were directed to computerized methods, systems, and storage media (embodied with computer instructions) for mitigating settlement risk, that is, the risk that only one party to a financial agreement would satisfy its obligations. The Court struck down the claims at issue as ineligible for patenting, but nonetheless indicated that "there is no dispute" that many computer-implemented inventions are eligible for patenting.

On June 25, 2014, the U.S. Patent and Trademark Office ("PTO") issued preliminary guidance, effective immediately, for examining subject matter eligibility under 35 U.S.C. § 101 for claims involving abstract ideas in light of Alice, including claims directed to computer-implemented inventions involving abstract ideas. See "Preliminary Examination Instructions in view of the Supreme Court Decision in Alice" (available at http://www.uspto.gov/patents/announce/alice_pec_25jun2014.pdf) ("PTO's Preliminary Instructions").

The Two-Part Test for Subject Matter Eligibility—Lots of Mayo

Section 101 of the Patent Act defines the subject matter eligible for patent protection: "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." 35 U. S. C. §101.

The PTO's threshold inquiries for subject matter eligibility under Section 101 remain the same. First, the PTO will determine whether the claim is directed to one of four statutory categories enumerated in § 101 (process, machine, manufacture, or composition of matter), and will reject the claim if it is not. Second, if the claim falls within a statutory category, the PTO will determine whether the claim is directed to a judicial exception (abstract ideas, laws of nature, or natural phenomena) and, if so, assess whether it is directed to a patent-eligible application. In this latter inquiry, the PTO will analyze the claim according to the two-part test of Mayo Collaborative Services v. Prometheus Laboratories, Inc., 566 U.S. _ (2012) ("Mayo") as follows.

Part 1: Determine whether the claim is directed to an abstract idea. PTO Preliminary Instructions at 2.

There is no prevailing definition for what constitutes an abstract idea.1 The PTO's Preliminary Instructions instead lists examples of abstract ideas from the case law to provide useful guideposts:

  • Fundamental economic practices (such as mitigation of settlement risk in Alice);
  • Certain methods of organizing human activities (such as the hedging of risk as in Bilski—recall that the method claim in Bilski did not require computer implementation);
  • An idea in itself (a principle, a motive, an original cause);
  • Mathematical relationships/formulas without more (such as the formula for computing alarm limits in a catalytic conversion process in Flook, and the formula for converting binary-coded decimal numbers into pure binary form in Benson).

Part 2: If the claim includes an abstract idea, determine whether any element or combination of elements is sufficient to ensure that the claim amounts to significantly more than the abstract idea itself. In other words, are there other limitations in the claim that show a patent-eligible application of the abstract idea, e.g., more than a mere instruction to apply the abstract idea? Consider the claim as a whole by considering all claim elements, both individually and in combination. PTO Preliminary Instructions at 3.

For this step, the PTO's Preliminary Instructions list examples based on the Court's statements in Alice of what may or may not be "enough" to qualify as "significantly more" than an abstract idea:

May qualify as "significantly more" than an abstract idea:

  • Improvements to another technology or technical field (such as the mathematical formula applied in a specific rubber molding process using temperature measurements from a thermocouple in Diehr).
  • Improvements in the functioning of the computer itself (same example from Diehr).
  • Meaningful limitations beyond generally linking the use of an abstract idea to a particular technological environment (no specific examples given, but notes that the hardware implementation in Alice was not sufficient).

Does not qualify as "significantly more" than an abstract idea:

  • Adding essentially the words "apply it" (or the like) with an abstract idea, or mere instructions to implement an abstract idea on a computer (simply implementing a mathematical principle on a physical machine such as in Alice is not sufficient).
  • Requiring no more than a generic computer to perform generic computer functions that are well-understood, routine and conventional activities previously known to the industry (simply using a computer to obtain data, adjust account balances, and issue automated instructions such as in Alice is not sufficient).

Takeaways—What Does it Mean?

  • The Court acknowledged that computer-implemented inventions remain eligible for patenting, and the PTO's Preliminary Instructions reflect the Court's guidance in Alice for making the eligibility inquiry.
  • There is still no prevailing definition of what constitutes an abstract idea. The guidance from the Court and the PTO is articulated in terms of examples taken from cases such as Alice, Bilski, Diehr, Benson, and Flook, and the PTO's Preliminary Instructions manifest an intent to utilize such examples for guidance.
  • Where general purpose computers are recited for implementation in claims, the PTO may be expected to assess whether a claim can be boiled down to a central idea (without regard to aspects of computer implementation) and then ask whether that idea was well known, routine or conventional in the industry.2 If the answer is yes, the PTO would then assess whether the claim contains an "inventive concept" in the subject matter eligibility inquiry by looking at the elements individually and in combination to assess whether the claim contains something significantly more than an abstract idea itself that transforms the claim into a patent-eligible application. See Alice, slip op. at 7.
  • The second step "inventive concept" analysis may be viewed as conflating inventiveness and subject matter eligibility. But some may say that the inquiry is not one of applying in depth analyses under Sections 102 and 103 to answer the question of eligibility under Section 101. Rather, the analysis appears to scrutinize claims to determine whether the computer implementation is more than mere window dressing in requiring an "inventive concept sufficient to transform the claimed abstract idea into a patent-eligible application." See Alice, slip op. at 11.

    The PTO's guidance does not recite the "inventive concept" language, but its analysis is expected to be the same.
  • The second prong of the Mayo test, as applied in Alice and as reflected in the PTO's Preliminary Instructions, includes an instruction to analyze a claim element-by-element, as well as in its entirety, to determine whether the additional elements transform the nature of the claim into patent-eligible application. Id., slip op. at 7, 11, 15.

    Some may voice a concern that analysis of claim elements in isolation may make it more likely for the PTO to find a claim ineligible, because it may be easier to assert that any given claim element, particularly where carried out by a general purpose computer, is well known or conventional in the art. This analysis of elements in isolation could then cloud the analysis of the claim as a whole where none of the elements examined in isolation were determined to transform the claim into a patent eligible application.
  • Preemption remains an overarching concern of Section 101 jurisprudence under Alice, particularly for computer-implemented inventions. The Court in Alice reiterated that a wholly generic computer implementation of an abstract idea does not impart patent eligibility because to do so would permit monopolizing the abstract idea itself. Id., slip op. at 13. The PTO's Preliminary Instructions do not expressly discuss the preemption issue, and it will be interesting to observe whether the PTO's examination will invoke comments on preemption similar to the ones in the Court's decisions, such as in Alice.
  • Computer-implemented claims that would otherwise recite elements of organizing human activities or elements capable of reading on mental steps, if the computer implementation aspects were ignored, may be particularly vulnerable to Section 101 scrutiny under the PTO's Preliminary Instructions in light of Alice.

Practical Considerations for Claim Drafting

Computer-implemented inventions can be claimed in numerous ways. For example, in a client-server setting, inventions can be claimed using system claims, method claims, Beauregard claims (i.e., claims directed to computer readable storage media for implementing computerized methods), Lowry claims (claims directed to data structures) and GUI claims (claims directed to graphical user interfaces). Examples of where these claims are applicable are shown in the following diagram.

Given the scrutiny on subject matter eligibility in the courts, it may be beneficial to consider a multitude of claiming opportunities when drafting a patent application.

Though not intended to reflect a comprehensive strategy in view of Section 101 jurisprudence, the following practical considerations (not all of which are reflected in the Alice decision or the PTO Preliminary Instructions) may be beneficial in claim drafting for computer-implemented inventions.

  • Draft method claims that would satisfy the "machine or transformation test" (MoT test) where appropriate. These are claims that are tied to a particular machine or that transform an article (which could be data) into a different state or thing. As an example, instead of drafting "receiving a communication ..." consider "receiving a communication from a radio transmitter ...."
  • Draft claims that do not easily read on mental steps. As an example, instead of drafting "receiving information ..." consider "receiving a data signal ...." As another example, instead of drafting "storing information in a memory ..." consider "storing a data structure in a computer memory ..." or "updating a data structure comprising a database ...."
  • Draft claims in such a way that reflects the integration of the computer with the steps of the approach (e.g., calculating a particular final or interim result) and that goes beyond possible insignificant pre-solution activity (e.g., data gathering) or post-solution activity (e.g., printing, displaying).
  • Utilize Lowry claims, i.e., claims directed to a data structure, where appropriate. As an example, consider "A database system comprising a first data structure ... and a second data structure ...." Also, the Lowry data structure aspect can be included in limitations of method, system and Beauregard claims to enhance the eligibility of those claims.
  • Utilize GUI claims, i.e., claims directed to graphical user interfaces, where appropriate. As an example, consider "A graphical user interface for ..., comprising: a plurality of graphical interface pages arranged in a hierarchical format ...." Also, the GUI aspect can be included in limitations of method, system and Beauregard claims to enhance the eligibility of those claims.
  • Draft claims that do not appear overly preemptive in scope. While limiting a claim to a certain field of use may not in itself impart subject matter eligibility, combining a field of use limitation with other strategies noted above may enhance the eligibility of a claim.
  • Consider avoiding lengthy preambles that may give an impression that the claim is directed to a fundamental concept about economics or human activity. As an example, the preamble language in Alice of claim 33 recited, "A method of exchanging obligations as between parties, each party holding a credit record and a debit record with an exchange institution, the credit records for exchange of predetermined obligations, the method comprising ...." Such language might create an initial impression that a claim is directed to an ineligible fundamental economic process.
  • Highlight the practical application of the claim. This could be done in the preamble and/or the end of the claim, as well as in the specification.
  • After drafting a claim that recites steps implemented by a general purpose computer, assess the claim by temporarily removing the computer implementation aspects and ask whether what remains could be boiled down to a central concept that might be considered exceedingly well known in the art. If so, consider beefing up the claim, e.g., as discussed above.
  • Consider using means-plus-function claims in addition to method claims, system claims, etc. Although a significant number of means-plus-function claims have been susceptible to attacks as indefinite under Section 112(b) for failing to recite sufficient structure in the specification corresponding to the claimed functions, such claims can invoke additional structure from the specification to assist in a Section 101 challenge. Of course, the specification would need to contain sufficient description of underlying structure, e.g., algorithms, for implementing the claimed functions.

In conclusion, the computer industry has changed enormously over the past several decades. This change has not only included incredible technological advancements but also affected how the computer industry has decided to legally protect its core assets. Numerous software companies, especially start-up companies, have secured software and business method patents and rely upon them as significant assets for enforcement, licensing, financing, and other purposes. These companies and their patent attorneys will be studying Alice and the PTO's Preliminary Instructions to understand how they should prepare and prosecute such applications in the future.

Footnotes

[1] The Court itself did not provide such a definition and declined to do so again in Alice. See Alice, slip op. at 10 ("[W]e need not labor to delimit the precise contours of the 'abstract ideas' category in this case.")

[2] See, e.g., Id. at 9 ("On their face, the claims before us are drawn to the concept of intermediated settlement, i.e., the use of a third party to mitigate settlement risk. Like the risk hedging in Bilski, the concept of intermediated settlement is 'a fundamental economic practice long prevalent in our system of commerce.'")

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Registration
Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:
  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.
  • Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.
    If you do not want us to provide your name and email address you may opt out by clicking here
    If you do not wish to receive any future announcements of products and services offered by Mondaq you may opt out by clicking here

    Terms & Conditions and Privacy Statement

    Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

    Use of www.mondaq.com

    You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

    Disclaimer

    Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

    The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

    Registration

    Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

    • To allow you to personalize the Mondaq websites you are visiting.
    • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
    • To produce demographic feedback for our information providers who provide information free for your use.

    Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

    Information Collection and Use

    We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

    We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

    Mondaq News Alerts

    In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

    Cookies

    A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

    Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

    Log Files

    We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

    Links

    This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

    Surveys & Contests

    From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

    Mail-A-Friend

    If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

    Emails

    From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

    *** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .

    Security

    This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

    Correcting/Updating Personal Information

    If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

    Notification of Changes

    If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

    How to contact Mondaq

    You can contact us with comments or queries at enquiries@mondaq.com.

    If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.

    By clicking Register you state you have read and agree to our Terms and Conditions