# Enfish v. Microsoft: Software Can Clear Alice Step One as a Real Technological Improvement

> The Federal Circuit held that a self-referential database design was not an abstract idea, establishing that Alice step one is a meaningful filter for claims that improve computer functionality.

Topic: Patents  |  Author: Lidiia Levitska  |  Source: Intellectual Property Law (outsideipcounsel.com)
Canonical: https://outsideipcounsel.com/blog/enfish-v-microsoft-software-eligibility-step-one/


*Enfish, LLC v. Microsoft Corp.*, 822 F.3d 1327 (Fed. Cir. 2016), is the decision that gave software patents a foothold after *Alice*. In the two years following the Supreme Court's *Alice* ruling, district courts had invalidated computer-implemented claims almost reflexively, often treating every software claim as an "abstract idea" at step one and moving straight to a search for an inventive concept. The Federal Circuit, in an opinion by Judge Hughes, corrected that drift. It held that step one of the *Alice/Mayo* framework is a genuine filter, and that claims directed to a specific improvement in the way a computer functions — there, a "self-referential" database table — are not abstract at all. The case remains the leading authority for arguing eligibility on the theory that an invention improves the computer itself.

## At a glance

- **Case:** *Enfish, LLC v. Microsoft Corp.*, 822 F.3d 1327 (Fed. Cir. 2016), Docket No. 15-1244
- **Court:** U.S. Court of Appeals for the Federal Circuit, on appeal from the Central District of California
- **Decided:** May 12, 2016
- **Opinion:** Judge Hughes, for a panel of Judges Moore, Taranto, and Hughes
- **Subject matter:** Patents claiming a "self-referential" logical model for a computer database (U.S. Patents Nos. 6,151,604 and 6,163,775)
- **Holding:** Claims directed to a specific improvement in computer functionality — a self-referential database structure — are not directed to an abstract idea and satisfy *Alice* step one

## The self-referential table

Enfish's patents claimed an innovative way to organize information in a relational database. In a conventional relational model, different kinds of data are stored in separate tables — one table for people, another for their employers, another for documents — and the tables are related to one another through defined relationships fixed in advance. Enfish's "self-referential" model discarded that rigid structure. It stored all data entities in a single table, and, crucially, defined the columns of that table using rows within the same table. The model was, in the patents' words, self-referential: the table described its own structure.

The patents asserted concrete advantages for this design. Because a new type of data did not require creating and pre-defining a new table, the database could be "configured on-the-fly." The single-table approach enabled faster searching, more efficient storage of unstructured data, and greater flexibility in modeling relationships. These were not abstract aspirations; they were specific improvements the patents attributed to the claimed data structure.

Enfish sued Microsoft for infringement. The district court granted summary judgment that the claims were invalid under 35 U.S.C. § 101, reasoning that they were directed to the abstract idea of "storing, organizing, and retrieving memory in a logical table" and lacked any inventive concept. The Federal Circuit reversed on eligibility.

## Step one is not a formality

The most important doctrinal contribution of *Enfish* is its insistence that *Alice* step one does real work. Some courts had read *Alice* to mean that essentially all software claims are "directed to" an abstract idea, so that eligibility always turned on step two's search for an inventive concept. The Federal Circuit rejected that shortcut. It warned that describing claims at a "high level of abstraction" untethered from their actual language would make step one swallow every invention, since "all inventions at some level embody, use, reflect, rest upon, or apply laws of nature, natural phenomena, or abstract ideas."

The proper step-one inquiry, the court held, asks whether the "focus" of the claims is a specific improvement to the functioning of a computer, or instead an abstract idea for which the computer is merely a tool. That framing matters because it directs courts to the character of the claimed advance. Where the claims are directed to an improvement in computer capabilities, they are not abstract and the analysis ends at step one — there is no need to hunt for an inventive concept under step two.

Applying that test, the court found Enfish's claims focused on "a specific improvement to the way computers operate, embodied in the self-referential table." The claims were not about using a computer to perform a task that humans could do; they claimed a particular data structure that improved the computer's storage and retrieval of information. That the improvement was realized in software, rather than in physical hardware, did not make it abstract. Software that improves computer functionality is no less eligible than hardware that does the same.

## Distinguishing Alice and drawing the line

*Enfish* carefully positioned itself against *Alice*. In *Alice*, the claims recited a generic computer performing generic functions to carry out the fundamentally human, abstract practice of intermediated settlement; the computer added nothing beyond conventional operation. Here, by contrast, the claimed invention resided in how the computer itself stored and organized data — the innovation was directed at the machine's operation, not at a business method that happened to run on a machine. The court also drew support from the specification, which disparaged the prior art's rigid, multi-table model and touted the self-referential design's technical benefits, confirming that the claims' focus was a technological improvement.

The court did not hold that all database or software claims are eligible. It grounded eligibility in the specificity of the improvement and the claims' focus on computer functionality. Later cases would test how concrete an asserted improvement must be, and *Enfish* itself cautioned that claims reciting only a desired result, without a particular way of achieving it, may still be abstract. But *Enfish* established the governing question — improvement to the computer versus computer as a tool — that practitioners have invoked ever since.

## Open questions

*Enfish* opened a durable line of eligibility argument but left its boundaries contested. How specific must a claimed "improvement to computer functionality" be, and how much must the claim itself recite versus rely on the specification to supply? The Federal Circuit's later decisions have both extended *Enfish* (finding eligibility in claims that improve computer or network operation) and cabined it (rejecting claims that recite only results or that use conventional components in conventional ways). The case also left unresolved how the "improvement" inquiry maps onto claims that improve a technological process outside the computer itself, as opposed to the computer's internal operation. Those questions continue to drive § 101 litigation.

## Implications

- **Argue eligibility at step one first.** The strongest software eligibility position is that the claims are not abstract at all because they improve computer functionality — winning at step one avoids the harder inventive-concept inquiry of step two.
- **Software improvements count.** An advance need not be embodied in new hardware; a better data structure or algorithm that improves how the computer operates is eligible subject matter.
- **The specification matters.** Detailing the technical problem in the prior art and the specific benefits of the claimed design helps establish that the claims' focus is a technological improvement.
- **Claim the mechanism, not just the result.** Claims that recite a particular way of achieving an improvement fare far better than claims that recite only a desired outcome, which courts may still find abstract.

## Frequently asked questions

**What did Enfish decide about Alice step one?** It held that step one of the Alice/Mayo test is a meaningful gatekeeper, not a formality. A court must actually ask whether the claims are directed to an abstract idea, and claims aimed at a specific improvement in the way a computer operates are not abstract, so they pass step one and never reach step two.

**Why were Enfish's software claims patent-eligible?** The claims were directed to a self-referential logical model for a computer database that improved how the computer stored and retrieved data. Because the invention was a specific improvement to computer functionality rather than an abstract concept merely implemented on a computer, it was not directed to an abstract idea under step one.

**How is Enfish different from Alice?** In Alice the computer was a generic tool used to carry out an abstract business practice. In Enfish the claimed advance was in the computer's own operation — a better data structure — so the claims improved the functioning of the computer itself rather than using a computer as a mere instrument.

## Authorities and sources

- *Enfish, LLC v. Microsoft Corp.*, 822 F.3d 1327 (Fed. Cir. 2016), Docket No. 15-1244 (decided May 12, 2016). [Official Federal Circuit opinion (PDF)](https://www.cafc.uscourts.gov/opinions-orders/15-1244.opinion.5-10-2016.1.pdf); [BitLaw full-text opinion](https://www.bitlaw.com/source/cases/patent/Enfish.html).
- Panel composition, Hughes authorship, and the step-one holding corroborated by [Wikipedia: Enfish, LLC v. Microsoft Corp.](https://en.wikipedia.org/wiki/Enfish,_LLC_v._Microsoft_Corp.).
- Framework applied from *Alice Corp. Pty. Ltd. v. CLS Bank International*, 573 U.S. 208 (2014), via [Justia](https://supreme.justia.com/cases/federal/us/573/208/).