Posts Tagged: "software patents"

I think the reality is that software patents in some form are here to stay for the foreseeable future; it is also true that things that used to be considered patent-eligible no longer are. Assuming that’s right, we need a way to identify which claims are patent-eligible… Yes, software can be patentable, but it has to provide a technical solution to a technical problem.

How patent claims can be invalidated without a proper and thorough claim construction is baffling. It flies in the face of everything patent law stands for and does nothing but encourage patent examiners, PTAB judges and district courts to do a facial check based on a gut feeling, nothing more… That type of subjective, half-baked analysis is antithetical to the patent process and the Federal Circuit should be ashamed for engaging in such a review. The only way to competently determine what a claim is directed to and whether the claim adds significantly more, whatever that means, is to do a proper, thorough and competent claim construction, period. Seriously, if the Court is going to publish a decision like this that is heavy on conclusions, non-existent on analysis, and almost certainly drafted by an intern or Staff Attorney, then why even make it a non-precedential opinion?

The Alice/Mayo framework is the decisional approach adopted by the United States Supreme Court for determining whether a patent claim exhibits, such as software patent claims, embody patent eligible subject matter… Over the last six months the Federal Circuit has provided a great deal of clarity, with 9 judges (Judges Moore, Taranto, Hughes, Chen, Newman, O’Malley, Reyna, Stoll, and Plager) signing on to decisions that found software patent claims to be patent eligible. What follows is a a summary of the significant developments over the last six months.

In a nutshell, if you are going to write a patent application in such a way that at the end of the it the reader is left wondering what the innovation is, what the problem being solved is, or the technical particulars on how the innovation actually solves the problem, you should not expect a patent. In other words, if you write your patent applications without actually defining the technological solution and how it is implementing the desired functionality you describe, and how that is an improvement, you will not get a patent because the claims will be patent ineligible. On the other hand, if you write your patent applications to describe (and claim) an invention that is adequately described so that someone of skill in the art will understand what is innovative (i.e., how and why), thick with technical disclosure and explanation as to how computer functionality is being improved, or even generic components are working in unconventional ways, then you will get a patent because your claims will be patent eligible.

The ’510, ‘984, and ‘797 patents were each held eligible for similar reasons. Again, the court found that even if the claims were directed to an abstract idea, they would be eligible under step two of the Alice framework. The Court again relied on the unique and unconventional distributed architecture found in the specification and construed into the claim in the previous proceeding. This architecture allowed for load distribution – a technological and unconventional solution to a technological problem. While the ‘984 claims contained generic components and functions, the overall ordered combination of the limitations were unconventional and solved the technological problem.

Earlier today the United States Patent and Trademark Office issued a new memorandum to patent examiners on recent software patent eligibility decisions from the Federal Circuit. The memo sent to the patent examining corps from Robert Bahr, who is Deputy Commissioner for Patent Examination Policy, explains that this most recent memorandum provides examiners with discussion of McRo, Inc. v. Bandai Namco Games America and BASCOM Global Internet Services v. AT&T Mobility.

Join us on Thursday, November 3, 2016 at 2pm ET for a discussion on drafting patent applications to overcome Alice, with JiNan Glasgow of Neopatents and Gene Quinn of IPWatchdog. In addition to taking as many of your questions as possible we will address the following: (1) Brief overview of Alice, Enfish, TLI Communications, BASCOM, McRo and FairWarning IP. (2) What these most recent Federal Circuit cases teach about drafting software patents. (3) How to cope with being unexpectedly assigned to an Art Unit.

This article reviews the 50 years of controversy on software patents. Because there continues to be a cloud over computer-implemented inventions, the article makes the argument, through indisputable facts, that computer-implemented inventions are no different from inventions that have been patented since the beginning of the Patent System in 1790. Finally, the article reviews three innovative patented computer-implemented inventions and explains why the phrase “software patent” is meaningless.

Simply stated, the industry and the public deserve better than Judge Mayer. His anti-patent views so cloud his judgment that he twists, exaggerates and misrepresents in order to attempt to impose his radical views into the law. There is no place for a judge like that. It is time for him to leave the Court. If he chooses not to do that it would seem appropriate for the Court to do what they would with an attorney who grossly exaggerates and mischaracterizes cases and rulings.

The concept of the central clearing house in financial systems could be completely obviated with the use of blockchain. Blockchain is a distributed database system that decentralizes the financial ledger; instead of the ledger being held and checked by the clearing house, each member of the blockchain network receives an updated ledger every time a transaction is made on the system. It’s a peer-to-peer system which reduces financial transaction risk through massive redundancy. With every member of the blockchain system holding a copy of the ledger for every transaction that has been completed, going back to the beginning of the blockchain, it becomes easier to identify malicious activity on the financial network or prevent transactions if users don’t have enough cryptocurrency. New transactions are recorded on blocks, which are added to the blockchain. Blockchain systems like bitcoin often reward those in the blockchain system who offer their computing resources to record new blocks; this incentivized process is known as mining.

Affinity Labs of Texas, LLC, lost two cases at the Federal Circuit last week, both in decisions authored by Judge Bryson, which Chief Judge Prost and Judge Wallach joining the opinions. Although the patents at issue in the two cases were different, they shared a similar specification. In the DirecTV decision, the Federal Circuit followed the Alice/Mayo framework and found the claims patent ineligible. Perhaps of note, the Court rebuffed Affinity’s arguments regarding novelty, explaining patent eligibility does not turn on novelty of the claims. In the Amazon decision the Federal Circuit ruled that basic user customization is insufficient to qualify as inventive under Mayo and Alice.

In a September 13, 2016 decision relating to subject matter eligibility of software patents under 35 U.S.C. § 101, the Federal Circuit vacated the district court’s order granting Defendants’ motion for judgment on the pleadings under Fed. R. Civ. P. 12(c), and held that McRO’s patents were eligible for protection under 35 U.S.C. § 101. The disputed patent claims recited a method for “automatically . . . producing accurate and realistic lip synchronization and facial expressions in animated characters.” The McRO patents identified that a problem in the prior art was that animators, even using the assistance of computers, had to manually manipulate the character model for lip movement. The McRO patents solved this problem by using rules to automatically depict more realistic synchronization of lip movements and speech.

It is hard to ignore the fact that the Federal Circuit again continued to point out that the innovation at issued was an improvement. This should give patent practitioners important clues into how to characterize software related innovations so as to maximize the likelihood of prevailing in Alice inspired challenges and rejections. Hopefully the United States Patent and Trademark Office will not ignore McRo and will issue guidance to patent examiners. Taking a “nothing to see here” approach to this case would be inexcusable.

Those who make the argument that medical software is abstract, or trivial, are just wrong. Medical software has been developed to benefit both patients and medical practitioners by providing better diagnostics, which ultimately lead to new and better treatments… In the context of medical technology, the proper evaluation and effective treatment of patients depend upon complex correlations assessed over prescribed times. This, in turn, relies upon the generation of predictive models from a comparison of an individual patient’s signs and symptoms against a database of studied human wellness parameters, which contain patterns of diagnosis, chosen treatment, and outcome. These efforts are far from trivial.

Bahr explained a number of things, including the reason the USPTO has not updated patent eligibility guidance to address the pro-patent decision of the Federal Circuit in BASCOM v. AT&T. Many in the industry have been critical of the fact that the USPTO, which has been otherwise quick to provide guidance with respect to important precedential decisions, did not provide examiners with guidance in this case which found the software claims at issue patent eligible. Bahr explained that the USPTO did not think the case changed anything they had previously told patent examiners, which is why no further guidance had been issued.