United States: Latest Post-Alice Guidance From The Federal Circuit

On Thursday, May 12, 2016, the Federal Circuit reversed a lower court's finding of invalidity under 35 U.S.C. § 101, as an unpatentable abstract idea, of a software patent concerning a "self-referential" database in Enfish v. Microsoft. In so doing, the Federal Circuit provided some helpful guidance on avoiding Alice rejections for software patents.  This is only the second §101 decision from the Federal Circuit in a high tech case since the Supreme Court's Alice v. CLS Bank decision in June, 2014 that has upheld the validity of a patent.

Importantly, in Enfish the Federal Circuit gave teeth to the first step of the test developed by the Supreme Court in Mayo v. Prometheus, which was adopted in Alice as the standard for analysis of subject matter eligibility.  In the nearly two years since the Supreme Court's Alice decision many district courts, Patent Trial and Appeal Board (PTAB) panels, and Patent Examiners have generally considered the inquiry required by this first step – whether the challenged claims cover an abstract idea (and are therefore directed to ineligible subject matter absent the presence of "significantly more" in the claim) – to be met in software cases.

The Federal Circuit in Enfish rejected the notion that software patents should automatically fail the first step of the Alice analysis.  The Court reiterated that there is no definitive rule for establishing what constitutes an "abstract idea," and that both the Supreme Court and the Federal Circuit rely on comparing claims at issue to claims already found abstract to make that determination. Helpfully, for patent practitioners, the Federal Circuit spent some time explaining that software patents are not inherently abstract, but can, in their own right, be directed toward improvements to computer functionality. Consequently, there should not be a default assumption that the first step of the Mayo analysis is satisfied for all software patent claims because "[s]oftware can make non-abstract improvements to computer technology just as hardware improvements can, and sometimes the improvements can be accomplished through either route."

For applications under examination (or re-examination) at the USPTO, the Enfish ruling may have shifted some of the burden from the patentee to the Examiner.  Instead of declaring all software claims as meeting step one of the Mayo test, and focusing the inquiry on the "something more" of step two, the Federal Circuit held that the relevant question is "whether the claims are directed to an improvement to computer functionality versus being directed to an abstract idea, even at the first step of the Alice analysis." This subtle change in the question asked of software patents may result in a profound change in the USPTO's approach to software patents.  Potentially, we may find that some of the burden shifts, from the patentee being required to prove that their invention is not abstract to the USPTO  being required to prove that the invention provides no improvement to computer functionality.  This would go some way to put the burden under § 101 inline with the burdens under § 102 and § 103.

The Federal Circuit provided fodder against those Examiners requiring physical components introduced into claims that logically do not require it.  The fact that "the improvement provided by the invention is not defined by reference to 'physical' components does not doom the claims." The Federal Circuit found that to do otherwise would risk resurrecting the bright-line machine-or-transformation test.  The Court held that "[m]uch of the advancement made in computer technology consists of improvements to software that, by their very nature, may not be defined by particular physical features but rather by logical structure and processes."

The Federal Circuit placed significant emphasis on the patent specification's explanation of the benefits of the invention over the prior art and quoted parts of the patent specification that characterized the prior art and the differences between those and the present invention. In fact, the specification used the phrase the "present invention" when describing the features that were an improvement over the prior art, which the Federal Circuit used as a basis for confirming that the court's "characterization of the 'invention' for the purposes of the § 101 analysis has not been deceived by the 'draftman's art.'" For some software patents, patent practitioners may benefit from explicitly characterizing the prior art and explaining the benefits provided by the invention, even at the expense of narrowing the invention in the process.

Lastly, the claim concentrated on by the Federal Circuit was a means-plus-function claim.  The lower court interpreted the "means for configuring" language of the claim under 35 U.S.C. § 112 ¶ 6, importing a four-step algorithm into the claim.  In so doing, the lower court introduced, into the claims, the specific improvements over the prior art. Based on this case, and until more guidance is provided by the Supreme Court on subject matter eligibility, patent practitioners may find it worthwhile to think about including a means-plus-function claim – while being sure to include the necessary description in the specification to support such a claim under 35 U.S.C. §112(a) (pre-AIA 35 U.S.C. §112, ¶1) – if only to provide a path to subject matter eligibility.

This case is the first case since DDR to find claims patent eligible under § 101 and is therefore rather significant.  DDR had a profound effect on prosecution through the USPTO and this case, Enfish, is likely to have a similar effect.

For those interested, the following paragraphs describe the more technical aspects of the claims of the patents at issue in Enfish.

The Federal Circuit concentrated on claim 17 of U.S. Pat. No. 6,151,604 (the '604 Patent).  Claim 17 of the '604 Patent is a means-plus-function claim that recites "means for configuring said memory according to a logical table...."  The district court interpreted the "means for configuring" language, under 35 U.S.C. § 112 ¶ 6, as requiring a four-step algorithm taken from the specification of the '604 Patent.  The Court held that the claims were "directed to a specific improvement to the way computers operate, embodied in the self-referential table."

To understand the significance of a "self-referential" table, traditional databases are relational, i.e., each entity in a database has its own separate database table of rows and columns that contains information associated with that entity.  For example, a typical business order entry database would include a table that describes a customer with columns for name, address, phone number, and the like.  Another table would describe an order with columns for the product, the customer, date, sales price, and the like.  The order table and the customer table will be linked by the customer identification information.  The "self-referential" table structure described in the patents allows information that normally is found across multiple relational tables to be stored in a single table.  Some of the information that appears in columns in relational tables may be translated into rows of a self-referential table.

Claim 17 of the '604 Patent recites as follows:

A data storage and retrieval system for a computer memory, comprising:

means for configuring said memory according to a logical table, said logical table including:

a plurality of logical rows, each said logical row including an object identification number (OID) to identify each said logical row, each said logical row corresponding to a record of information;

a plurality of logical columns intersecting said plurality of logical rows to define a plurality of logical cells, each said logical column including an OID to identify each said logical column; and

means for indexing data stored in said table.

The lower court interpreted the "means for configuring" language of the claims under 35 U.S.C. § 112 ¶ 6, importing a four-step algorithm into the claim:

  1. Create, in a computer memory, a logical table that need not be stored contiguously in the computer memory, the logical table being comprised of rows and columns, the rows corresponding to records, the columns corresponding to fields or attributes, the logical table being capable of storing different kinds of records.
  2. Assign each row and column an object identification number (OID) that, when stored as data, can act as a pointer to the associated row or column and that can be of variable length between databases.
  3. For each column, store information about that column in one or more rows, rendering the table self-referential, the appending, to the logical table, of new columns that are available for immediate use being possible through the creation of new column definition records.
  4. In one or more cells defined by the intersection of the rows and columns, store and access data, which can include structured data, unstructured data, or a pointer to another row.

The Federal Circuit disagreed with the lower court's conclusion "that the claims were directed to the abstract idea of 'storing, organizing, and retrieving memory in a logical table' or, more simply, 'the concept of organizing information using tabular formats.'" The Federal Court concluded that "the claims are not simply directed to any form of storing tabular data, but instead are specifically directed to a self-referential table for a computer database.  For claim 17, this is reflected in step three of the "means for configuring" algorithm."

Interestingly, without the importing of limitations from the specification by the lower court as part of the analysis of the means-plus-function claim language required under 35 U.S.C. §112, ¶6, this conclusion on the specificity of the claims likely would not have been possible.

The Federal Circuit put great emphasis on the content of the specification of the '604 Patent, including the patentee's statement that "the present invention comprises a flexible, self-referential table that stores data," and the detailed analysis of the differences between the prior art and the invention and how the prior art was inferior to the invention. The Court relied on a recent Apple case which found that a specification's disparagement of the prior art is relevant to the determination of the scope of an invention. The Federal Circuit dismissed the notion that the invention's ability to run on a general-purpose computer dooms the claims.  The Court found that, unlike the claims in Alice, or claims in other cases which found subject matter ineligibility, the claims in Enfish were directed to an improvement in the function of a computer. The Court described the prior cases as involving claims that merely added conventional computer elements to well-known business practices.

The Federal Circuit concluded that the claims of the '604 Patent are not directed to an abstract idea under step one of the Alice analysis and that proceeding to step two was therefore unnecessary. The Court did caution that when there is a close call under step one of the Alice analysis, a discussion of whether the claimed invention provides concrete technological improvements may be necessary, but in this instance, the case was so clear that there was no need.

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
Michael D. Van Loy, PhD
Howard Wisnia
Robert T.S. Latta
 
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
Check to state you have read and
agree to our Terms and Conditions

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.

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 by clicking here .

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.

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.