Posts Tagged: "computer implemented methods"

In two cases written by Judge Chen (DDR Holdings, LLC v. Hotels.com L.P., 2013-1505 (Chen, Wallach, Meyer (dissent) and Bascom Global Internet Services, Inc., v. AT&T Mobility LLC, 2015-1763 (Newman, O’Malley, Chen)) the patents were found to be patent-eligible principally because analysis typically regarded as being under Mayo step 2 demonstrated that the claims added “something more” to the abstract ideas than merely well-understood and conventional steps. In effect, Judge Chen’s opinions focus on whether the narrowness of the claim is adequate. If it is, the claim is not abstract. How narrow is “narrow enough” is, like “abstract”, not defined, but this approach bears a closer resemblance to the original limiting principle of the abstract idea doctrine – preemption – than many recent decisions.

Where the claims are directed to an improvement to computer functionality, they are not abstract under the first step of Alice, and thus no step-two analysis is necessary. Here, the Federal Circuit found that Enfish’s self-referential table was directed to a specific improvement in computer capabilities, unlike Alice, where the claimed technology only added a computer to a traditional business practice. For this reason, the Court held that Enfish’s claims were not abstract under the first step of Alice, and therefore did not warrant the application of step two.

Bahr tells examiners that based on the Federal Circuit ruling they “may determine that a claim direct to improvements in computer-related technology is not direct to an abstract idea under Step 2A of the subject matter eligibility examination guidelines (and is thus patent eligible), without the need to analyze the additional elements under Step 2B.” (emphasis in the original) Bahr goes on to tell examiners that a claim that is “directed to an improvement to computer-related technology (e.g., computer functionality) is likely not similar to claims that have been previously identified as abstract by the courts.”

From there the Federal Circuit said: ”We do not read Alice to broadly hold that all improvements in computer-related technology are inherently abstract and, therefore, must be considered at step two. Indeed, some improvements in computer-related technology when appropriately claimed are undoubtedly not abstract, such as a chip architecture, an LED display, and the like. Nor do we think that claims directed to software, as opposed to hardware, are inherently abstract and therefore only properly analyzed at the second step of the Alice analysis. Software can make non-abstract improvements to computer technology just as hardware improvements can, and sometimes the improvements can be accomplished through either route.”

Showing a bowl of spaghetti on one of his first few PowerPoint slides set the tone. The law as it applies to software patent eligibility is a tangled mess. “The Supreme Court has continually taken cases in this area and rather than clarify they have continued to hang on,” Schecter explained referencing the fact that the Supreme Court seems committed to the belief that their 101 jurisprudence is consistent and reconcilable. Of course, that is not the case. “There are too many cases that conflict with each other.” He is right. Schecter would go on to say that we are at a point where a legislative fix seems necessary.

the Courts have found it difficult to use the Mayo two-part test in the examination of a patent’s validity thus creating great uncertainty… One should not confuse the uncertainty of the complex U.S. patent system with the clarity of the Alice decision. There is no reason to believe any new legislation will provide any improvement in deciding what should, and what should not, be patentable.

A case currently pending before the Federal Circuit is anticipated to provide greater guidance into the answer to this question, namely, how district courts should determine whether a claim is directed to an abstract idea. The case, McRo, Inc. v. Bandai Namco Games America, No. 2015-1080, recently heard oral argument on December 11, 2015. The panel’s questioning indicated that its anticipated decision may provide greater insight into how district courts are to determine whether a claim is, in fact, directed to an abstract idea. The patents are directed to automatic three-dimensional lip-synchronization for animated characters. Whereas prior art lip-synchronization required manually synchronizing an animated character’s lips and facial expressions to specific phonemes, the patents are directed to rules for automating that process.

Over the last decade, there has been a movement among the software developer community to employ some form of “agile development” rather than the traditional software development methodology. The belief is that these agile methodologies lead to higher quality software and faster development cycles. More recently, the implementation of agile software development has transitioned not only from small startups to large companies, but also from enterprises developing noncritical, consumer apps to those developing software for medical, aviation, military, and financial systems, where the presence of errors pose high human or economic risk. With these transitions, intellectual property (IP) law practitioners must adopt their traditional lawyering approaches to capturing and securing IP (especially patent) rights. A failure to recognize and adapt to the agile software development environment will result in a failure of IP law practitioners’ essential job function—helping to create or sustain client profitability and enable long-term business growth.

On December 18, 2015, several amici filed a brief in support of appellants in Netflix, Inc. v. Rovi Corp. et al., No. 15-1917 at the Federal Circuit. The amici Broadband iTV, Inc., Double Rock Corporation, Island Intellectual Property, LLC, Access Control Advantage, Inc., and Fairway Financial U.S., Inc. are all former practicing entities and patent holders that built, developed, and commercialized computer-implemented technology and maintain an interest in the patented results of their research and development that solved real world problems faced by their respective businesses. The district court found the five patents-at-issue in this case, generally relating to video-on-demand technology, patent-ineligible as allegedly directed to the abstract ideas.

Don’t be afraid to make the technical disclosure long, dense and difficult to read, at least for those without technical training. In my opinion one of the biggest reasons the Supreme Court has embarked upon this path to render much innovation patent ineligible is because they actually understand the inventions in question. In Bilski, for example it was little more than thinking, observing and acting. In Alice they convinced themselves it was just little more than ledger accounting. Dumbing down the technical disclosure so even a Justice of the Supreme Court can understand is a mistake, at least in my humble opinion.

”There should be no serious question that computer-implemented inventions such as software constitute patent-eligible subject matter under § 101,” Paul Clement wrote in a brief filed on behalf of IBM to the Supreme Court in 2014. Ultimately, the IBM brief would argue that the abstract idea doctrine is unworkable, which it is. Sadly, nearly 18 months after the Supreme Court’s landmark decision in Alice v. CLS Bank we are no closer to having a working understanding about when and under what circumstances software is patent eligible.

It is not as easy to get software patents as it once was, but software is still patent eligible in the United States. Broadly speaking, software patents are any patents that covers a computer implemented process.

Functional claim language is increasingly being used by practitioners to capture the metes and bounds of an invention, especially in computer-implemented inventions. Sometimes using functional language in a claim limitation is unavoidable. Functional language does not, in and of itself, render a claim improper. However, as recently experienced in Williamson v. Citrix (en banc) and Robert Bosch, using functional language carries a significant risk of having the claim invalidated as indefinite following a determination that the claim invokes § 112(f) even when the patentee does not intend to have the claim treated under § 112(f).

It would be extremely unsettling if the Supreme Court has weakened Judge Lourie’s resolve to independently and properly interpret the Patent Act. If there is another explanation for his flip-flop on matters of patent eligibility I would love to hear it, but so far an explanation for diametrically different opinions has not been forthcoming. I don’t expect Judge Lourie to make a speech or hold a press conference like a politician, but if he is going to make diametrically opposite decisions in the same case, on the same facts, relating to the same claims, he owes litigants and the industry an explanation. Without an explanation it makes the entire process seem nothing more than arbitrary and capricious.

Based on the Supreme Court decision and the Patent Office guidelines it is clear to me that the Alice Supreme Court decision is a major victory for patenting computer-implemented (software) inventions. When the Supreme Court unanimously agreed that the critical issue is whether there is an inventive concept (and not on how an invention is implemented) the Supreme Court finally ended the debate on whether computer-implemented inventions are patentable.