Thales patent eligibility ruling

HMD display
Not the Thales Head Mounted Display!

A recent Federal Circuit case, Thales Visionix Inc. v United States, continues the process of restoring sanity to the ongoing “Alice” patent eligibility mess.

As previously discussed, since the Supreme Court’s 2014 “Alice” decision, patent law has been burdened with an unworkable “is it abstract?” test for patent eligibility. This test is similar to a medieval test to determine witches:  Step 1:determine if the test subject is a witch abstract”;  Step 2:if so, does the witch float? is there something more?”

The Federal Circuit, charged with cleaning up patent law, has been slowly chipping away at this nonsense. In two earlier cases (Enfish and Rapid Litigation), the Federal Circuit established at least a few reasonable step 1 rules (such as read the entire claim), and now we have another.

Thales Visionix had a patent on a motion-tracking Head Mounted Display (HMD).  This patent claimed a HMD arrangement of inertial sensors and signal processing elements, used in the F-35 fighter jet. Any enemy pilot blown up by this HMD system might not consider this to be “abstract”, but a lower US court was not so easily impressed. They used their own “Alice: it’s abstract” weapon to shot down the HMD patent.

In the absence of rules (the Supreme Court thoughtfully declined to provide any), lower courts have often used a type of “guilt by association” logic, where if a given patent claim has some elements in common with another claim previously ruled to be abstract, then that claim is also abstract. The lower court argued that the Thales patent claims were abstract because the claims allegedly “used mathematical equations (previously determined to be abstract) for determining the relative position of a moving object to a moving reference frame”.

However the Federal Circuit disagreed.  They determined that just because a claim contains a patent ineligible (abstract) concept (e.g. mathematical equations) does not mean that the entire claim is (step 1) “abstract.” Rather, the question is if the patent ineligible concept (math, natural law) is being used to improve some other technique. If so, then the claim as a whole is not abstract. This is similar to their earlier, more biotech-focused, ruling in the Rapid Litigation case.

So as a medieval logic analogy, just because a woman has a cat does not automatically mean that the woman is a witch, if the cat is unusually good at catching mice. If improved mouse catching can be shown, the step 1 conclusion is that the woman is not a witch. There is no need to go on and subject the poor woman to a step 2 “witch float” test.  This is good, because there is a high casualty rate at step 2.

Sending Alice to Planet Blue

Planet Blue -- Neptune perhaps?
Planet Blue — Neptune perhaps?

Forget “patent invalid because abstract”, the Planet Blue decision finds the real issue is preemption, and non-preemptive software claims are not abstract.

As previously discussed, in recent years the Supreme Court (SCOTUS) issued a series of confused rulings such as the “Alice” and “Mayo” decisions.  SCOTUS ruled that “abstract” inventions were not patentable, but didn’t define “abstract”, thus making the issue very subjective and bringing much confusion to software and biotech patents.

Fortunately, perhaps realizing that they did more harm than good, SCOTUS has recently started to decline further cases of this type.  They are apparently now leaving it to the Federal Circuit (the court right below SCOTUS) to clean things up.

Over the past few months, the Federal Circuit has initiated a number of damage control efforts, including their “Enfish”, “Bascom”, and “Rapid Litigation” decisions.  Now with another case, “Mcro, Inc. v. Bandi Namco Games, we have still more damage control. (Mcro calls itself “Planet Blue”, so we will call this the “Planet Blue” decision.)

The “Planet Blue” patent involved some improved methods of lip synchronization for animated cartoons, and their claims covered some novel but general rules to do this.  A lower court had originally invalidated these as being abstract, but the Federal Circuit reversed and said that the claims were OK.

As per their earlier Enfish decision, the Federal Circuit did not simply assume that software is “abstract” (under Alice step 1).  Instead, they asked the broader question, why is “abstract” a problem anyway?  As they interpreted it, “The concern underlying the exceptions to § 101 is not tangibility, but preemption.”  [Emphasis added]

Some history about patents and “preemption”: Back in1853 Samuel Morse, inventor of the telegraph, tried to get a claim for the use of electromagnetism for any method of printing characters or signs. However, this particular claim omitted any other details. The 1853 SCOTUS said “no”, because claims where “it matters not by what process or machinery the result is accomplished” (e.g. are preemptive) are not going to be allowed.

In Planet Blue, the Federal Circuit (possibly giving up on the more recent rulings as being hopelessly confused), has essentially gone back to the 1853 Morse case for some coherent guidance.  The Federal Circuit ruled that with regards to the Planet Blue claims, “The claim uses the limited rules in a process specifically designed to achieve an improved technological result in conventional industry practice… Claim 1 of the ’576 patent, therefore, is not directed to an abstract idea.” In other words, this passes Alice “step 1”, and you get a free “get out of abstract patent eligibility rejections” card.

The big win here is that “preemption” is a more objective issue, and by changing the analysis from “abstract” to “preemption”, we remove a lot of randomness from the patent process. To me, this looks like an important ruling, and good news for software patents, biotech patents, and indeed all types of patents.

Rapid Litigation: Biotech patent win

Cleaning up a legal mess
Rapid Litigation v Cellzdirect: Federal Circuit cleaning up a patent mess

In Rapid Litigation v Cellzdirect, the Federal Circuit has further cleaned up the patent eligibility mess caused by SCOTUS’s Alice and Mayo decisions.

In 2012 and 2014, the Supreme Court (SCOTUS), which wanted to invalidate a few pesky financial and medical diagnostics patents, decided to use legal “nuclear weapons” rather than legal “fly swatters“.  The SCOTUS legal nuclear weapons were the now infamous two-step “abstract material” patent eligibility test.  Step 1 of this test is summarized below:

Step 1) Determine if the patent is directed to “abstract” subject material.  If not then congratulations, the patent passes this test and is patent eligible.  

SCOTUS refused to define “abstract material”. This allowed the USPTO and the lower courts to run amok and start randomly invalidating patents. This, in turn, started to damage US biotech and software startups, which need patents to get funding, as well as for protection from larger competitors.

The Federal Circuit, one step below SCOTUS, and charged with cleaning-up patent law, waited several years for SCOTUS to correct itself, to no avail.  However, their recent (mid-2016) series of patent eligibility decisions, first Enfish, then Bascom, now Rapid Litigation (Celsis) v Cellzdirect suggest that the Federal Circuit is now getting serious about damage control.

“Abstract” is just as undefined for biotech as it is for software, but for biotech, it seems have more of a “natural law-ish” flavor.  Arguably a technologically illiterate approach since everything involves natural laws, but alas SCOTUS has no STEM majors.

Fortunately, some Federal Circuit judges are STEM majors, and they have the power to do at least some damage control by providing official interpretations/clarifications of SCOTUS decisions. Here they clarified that in step 1, “directed to” is not the same thing as “involving”.

The patent in this case, 7,604,929, was about an improved method of freeze storing liver cells (cryopreservation of hepatocytes).  Before the patent, everyone in the field believed that freezing damages living cells, and that multiple freeze-thaw cycles should be avoided.  The inventors discovered that some hepatocytes were resistant to this problem, and used this discovery to invent an improved hepatocyte cryopreservation method.  This method first freeze-thawed the cells, then used a density gradient to select for the freezing resistant cells, and then refroze these resistant cells again, producing very freeze resistant hepatocytes.

An earlier court had ruled this patent invalid by arguing that discovering that some hepatocytes could survive multiple freeze-thaw cycles involved a “law of nature”. However, the Federal Circuit pointed out that “involved” isn’t enough grounds to invalidate a patent, because the ‘929 methods also claimed other steps, such as using density gradients.  So “directed to” is more than just “involves“.

This Federal Circuit decision makes it harder to invalidate biotech patents, at least in the most common cases where the claims also have other steps in addition to the “natural law” steps.  The fact that the ‘929 claims were relatively simple helps to further clarify the legal issues.

Bascom: another Alice software win

Bascom - fish delivering mail
Bascom – fish delivering mail

The Bascom court decision helps software patents by suggesting that step 2 of the Alice test should follow established obviousness rules.

US software patents got another win from the Federal Circuit Court this week.  This court, which has a Congressional mandate to clarify patent law, made an important clarification to the Alice (software patent killer) “abstract subject matter” test in the Bascom v AT&T case (Bascom).

As you may recall from our last “Enfish” episode, the Supreme Court (SCOTUS) “Alice” decision created a judge-ordered incoherent two-step test that any given patent must pass in order to be patent eligible under 35 USC 101 rules.  To simplify:

Step 1) Determine if the patent is directed to “abstract” subject material.  If not then congratulations, the patent passes this test.  

Step 2) But if the patent is found to be “abstract” in step 1, then determine if the patent contains “something extra” beyond just “abstract” subject material.  If there is nothing extra, then reject the patent as being “abstract”.   

The Federal Circuit is one step down from SCOTUS.  The Federal Circuit doesn’t have enough clout to overrule SCOTUS, but does have enough clout to overrule the USPTO and the lower courts.  More importantly, the Federal Circuit has both the clout and mandate to “clarify” SCOTUS decisions.

The USPTO and the lower courts were often ignoring Alice step 1 and just assuming that a patent had “abstract” subject matter. The previous Federal Circuit “Enfish” decision pointed out that this was improper.  By contrast, the newer Federal Circut “Bascom” case is now clarifying that another common practice, just asserting that the patent fails Alice step 2 because it lacks an undefined “something extra”, isn’t right either.

More specifically, in Bascom, the Federal Circuit pointed out that based on earlier SCOTUS decisions (e.g. Mayo v. Prometheus, which SCOTUS used for “Alice”), Alice step 2 tests if the claim is “well-understood, routine or conventional”.  According to the Federal Circuit’s interpretation, SCOTUS was probably thinking about something similar to an obviousness test.   The Federal Circuit also pointed out that there are well-established rules for establishing obviousness, which the USPTO and the lower courts were (also) ignoring.

Specifically, the Bascom case was an appeal of a lower court decision that had earlier found the Bascom patent claims to be “abstract” and therefore invalid.  The lower court’s arguments (in simplified form) were that the Bascom patent claim language words described conventional computer pieces, and therefore the Bascom claims failed Alice step 2 due to lack of “something more”.  

In Bascom, the Federal Circuit Court, after “clarifying” Alice by pointing out that SCOTUS’s Alice step 2 resembled an obviousness test, then pointed out that the lower court had failed to follow established rules to determine obviousness (35 USC 103 rules).  These 35 USC 103 rules require that the combination of the pieces and the motive for combining the pieces also be considered.  Here conventional pieces, arranged in a non-conventional way, are often not obvious.

The Federal Circuit then looked at the Bascom claims, determined that they were not obvious, and (again somewhat simplifying) therefore had “something more” that satisfied step 2 of the Alice test.  They then overruled the lower court and found the Bascom patent to be “not abstract” and therefore valid under 35 USC 101.

If this holds up, the Bascom decision could almost bring some sanity to the Alice test.  Stay tuned…

Enfish for Alice: a software win

Einfish is good news for software patents
Enfish is good news for software patents

The recent Enfish court decision improves the outlook for US software patents.

Good news for software patents.  The negative impact of the 2014 SCOTUS (Supreme Court of the US) “Alice” decision (invalidating some business method and financial software patents) has been somewhat mitigated by the recent “Enfish” court decision.

What is “abstract?”  “You keep using that word, I do not think it means what you think it means.” Inigo Montoya, “The Princess Bride”.

In “Alice”, SCOTUS did not make business-method and financial software patents patent ineligible.  Instead, they determined that “abstract” subject matter is patent ineligible.  Unfortunately, SCOTUS refused to define the meaning of “abstract”, and then further confused things by using circular logic.  The present two-step, circular-logic, SCOTUS mandated test for patent eligibility is:

Step 1) Determine if the patent is directed to “abstract” subject material.  If not then congratulations, the patent passes this test.   

Step 2) But if the patent is found to be “abstract” in step 1, then determine if the patent contains “something extra” beyond just “abstract” subject material.  If there is nothing extra, then reject the patent as being “abstract”.    

No one knows what “abstract” means.  Unfortunately since late 2014, the USPTO has been generally assuming that patents for software running on standard computers must be abstract under step 1.  Many USPTO examiners (and judges) have been totally skipping step 1 of the two-step Alice test.  They just assume that a given software patent is abstract, and start their Alice test at step 2 “something more”.  This makes it much easier to reject the patent.

What is “something more?”  It is also undefined, but financial and business software generally seems to be lacking.  We could substitute “evil spirits” for “abstract”, and “charisma” for “something more”.  We could almost as validly say that lately, many USPTO examiners and judges have been rejecting most business and financial method patents because 1) assumption of evil spirits and 2) a further lack of charisma.  It is easier to understand if you don’t expect logic.

In 1982, Congress established the Federal Circuit Court to bring more logic and consistency to patent law.  In the recent (May 12, 2016) “Enfish v Microsoft” (Enfish) decision, the Federal Circuit has finally started to do its job.  The Enfish court has ruled that examiners and judges can’t just arbitrarily skip step 1 of the two-step Alice test.  Specifically, the Enfish court ruled that it is improper to assume that software running on standard computers is “step 1” abstract.

The Enfish court pointed out that in Alice, SCOTUS didn’t rule that software is automatically abstract.  Further in Alice, SCOTUS also warned against running amok since every patent is somewhat abstract.  So don’t make software automatically fail the two-step Alice test at step 1.  The Federal Circuit further determined that software running on standard computers that improves an existing technology (such as a database) is not abstract at step 1.

This is another important point:  “abstract” is an undefined legal term, and you and I lack the authority to officially define it.  But the Federal Circuit does have the legal authority to define “abstract”.  The USPTO and other judges have to follow this updated definition.  So Enfish is good news for US software patent law.

Software patents in China, Europe, and the US

China-Europe-US
Software patents in China, Europe, and the US

Summary: In general, software patents that deal with technical effects, physical parameters, and improving computer function tend to be favored. By contrast, software patents focused on business methods tend to be disfavored.

China: Before April 2017, China restricted software patents to methods that solve technical problems, control internal or external processes according to the laws of nature, and produce technical effects in accordance with the laws of nature.  Machine readable medium type claims, and game patents, were not allowed. However these guidelines are now somewhat more expansive. For example, business methods that also have a technical aspect may now also be eligible for patent protection.

Europe: Software patents should have a “technical effect” (e.g. controlling industrial aspects, improvements in computer technology, data pertains to physical properties,). Pure methods directed “only” to doing business and computer programs without “technical effect” are not allowed.

United States: The rules are presently incoherent. Traditionally (before 2014-2015) US policy was permissive. Indeed the present written (i.e. statutory) US legal standard is that all types of software patents are permitted. However the latest judicial rulings and USPTO policies are that at least some software patents may represent “abstract ideas” run on “generic computers” that are not patentable unless there is “something more”. Unfortunately the terms “abstract”, “generic computer” and “something more” are effectively undefined (and thus can vary according to the whims of the judge or patent examiner at hand).

How will US software patent rules evolve in the future? This is a bit like reading tea leaves, but the latest US software patent decisions appear to be trending more towards a Chinese or European-like approach. On average, “Business method” software is increasingly being rejected as being “abstract”. However software that exhibits technical effects, operates on data pertaining to physical properties, or improves computer function is often accepted on the basis that it is not “abstract”, not run on “generic computers” or contains “something more”.  Arguably the US, presently lacking coherent rules, may be at least temporarily filling the void by borrowing rules from other countries.  The constitutionality of this approach remains to be determined.

Harming the economy with over-aggressive, haphazard Alice-based 101 rejections

madteaparty
Alice in Wonderland – Mad Tea Party

What to do about “Alice”? The US Supreme Court’s “Alice” decision has invited us all to a Mad Tea Party.  What fun! But, as previously discussed, if you like logical coherency, or even just want to keep from crashing the economy, there are a few problems with this decision.

Attorney Louis Hoffman, writing in ipwatchdog.com, sums up some of these recent”Alice” problems nicely.

Damaging the economy: As Louis points out, some of the most important areas of US technology are based on software, business methods, and biotechnology.  The USPTO has recently taken upon itself to reject many patents in this area.  However this loss of patent coverage can impede the economy by making investments difficult, and/or by driving inventions underground in the form of trade secrets.

http://www.ipwatchdog.com/2016/02/07/uspto-harms-over-aggressive-and-haphazard-application-of-alice/id=65810/

What about actual (written) patent law? Article I, Section 8, Clause 8 of the US Constitution has empowered Congress 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.

Congress has done so, and has determined under 35 USC 101 that:  “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.”

The US Supreme Court has given itself the power to override Congress, however.  In Alice, they chose to exercise this power.  In this regard, Attorney John Duffy writes in Scotusblog:  “The uncertain expansion of judge-made exceptions to patentability” points out some interesting implications of this decision.

If you want to know what’s important about this case, it’s right there: the Court’s acknowledgement that the judge-made “exclusionary principle” has the potential to “swallow all of patent law” because “all patents” are at some level based on the very things that can’t be patented under the judge-made doctrine.

Decisions, decisions: So the Alice decision, read too broadly, produces an unconstitutional result.  At some point, there will be likely corrective action.  However the practical question that some inventors, particularly business method inventors, have to address today is: file a patent and risk an “‘Alice” rejection, or don’t file a patent and be certain that the invention will become public domain?

Alice update — need true neutral party review

Need for impartial judges
Need for impartial judges

In my opinion, part of the “Alice” patent problem is that few true impartial (i.e. neutral) judges have really been involved yet.

Both the USPTO and Federal judges have at least a subconscious incentive to get complex patents off of their respective desks with a minimum of time and effort.  Why fill your head with complex matters — just say the patent is “abstract”, and the problem is gone.  Instant relief!  So perhaps there is an inherent conflict of interest built into the legal system in this regard.

So, as the Supreme Court itself warned, Alice will continue to swallow up more and more patent law until it finally reaches an opposing force.  Given our legal system, this opposing force may have to be formed by group of middle to large sized companies.  Here, any company that doesn’t depend on either advertising, copyrights, or non-innovative technology might be a potential candidate for such a group.

Perhaps some of the presently pending cases will eventually put some boundaries here.

CLS Bank v. Alice Corporation II: more cutting-edge legal confusion

Confused?  So is everyone else!
Confused? So is everyone else!

Legal confusion:  There remains a lot of legal confusion in the US regarding the question, are software inventions patentable? How to answer this question? We could of course look at the letter of the law (e.g. 35 USC 101), which would give us the rather boring answer that software is patentable. But if someone doesn’t want software to be patentable (and a number of large powerful companies do not), that’s not the answer they want.

How else might we get an answer? In ancient Greece we might consult the Oracle at Delphi, or perhaps sacrifice a goat and examine its entrails. However in the modern US, we know that this is silly. As we all know, the modern US way to decide this is to put this question to a small panel of elderly individuals who know nothing about software or patent law. We call this small panel the Supreme Court of the United States (SCOTUS).

To answer questions, the Oracle at Delphi inhaled vapors, fell into a trance, and then spoke in riddles. These were then interpreted by various priests. In much the same way, SCOTUS (hopefully without the aid of vapors) has given us some confusing and inconsistent rulings, such as the CLS Bank v. Alice Corporation decision, that in essence are riddles that must be interpreted by various priests (e.g. lower courts, the USPTO).

So in “Alice”, SCOTUS told us that “abstract ideas” are patent ineligible, and also told us that “In any event, we need not labor to delimit the precise contours of the “abstract ideas” category in this case. It is enough to recognize that there is no meaningful distinction between the concept of risk hedging in Bilski and the concept of intermediated settlement at issue here. Both are squarely within the realm of “abstract ideas” as we have used that term.

So the ruling in essence is the riddle: “abstract ideas are not allowed“, and “abstract ideas are undefined”. This is a pretty good riddle. So the next step is, now that the Oracle (err… SCOTUS) has spoken, how are the various priests (err… the USPTO and lower courts) going to interpret this riddle?

Some good news on this front. On December 16, 2014, the USPTO issued its “2014 Interim Guidance on Patent Subject Matter Eligibility”, available here:

http://www.gpo.gov/fdsys/pkg/FR-2014-12-16/pdf/2014-29414.pdf

Among other things, the USPTO appears to be heading towards the interpretation that when given incoherent rulings, at least try to minimize damage by applying the rulings narrowly. Thus the latest guidance instructs examiners to perform detailed analysis, and look for specific problems such as financial hedging and mitigating settlement risks, rather than generally rejecting everything. The Guidance also advises examiners that even if a patent hits on a “forbidden area” (judicial exemption), so long as the claim does not seek to tie up the judicial exemption so that others cannot practice it, the claim is probably OK.  (Note added 4-26-16 — sadly the USPTO has not followed their own guidance consistently. The official patent examination “MPEP” rules for eligibility are still literally a blank page).

CLS Bank v. Alice Corporation

Signpost
Confusing directions

What is patentable? Perhaps I was too optimistic in my earlier “Prometheus bound (or at least distinguished)” post.

The May 10 Federal Circuit court decision, “CLS Bank v. Alice Corporation” shows that the Federal Circuit is unfortunately still spinning its wheels with regards to determining basic questions about what is  patent eligible.

The good news is that the decision’s various logical problems, and the logical problems with the underlying Supreme Court decisions, are being widely publicized.  Indeed interest in this decision was so high that the Federal Circuit Court servers crashed under the load of everyone trying to download the decision at once!

If you are interested in seeing the present state of the art in regards to cutting-edge legal confusion, you can download the Federal Circuit decision at:

https://www.eff.org/files/cls_bank_v_alice_en_banc_ruling.pdf