Source: https://pitiptechblog.com/tag/invalidity/
Timestamp: 2019-04-26 00:48:37+00:00

Document:
Federal Circuit Confirms That Abstract Mental Processes Are Not Patentable — CyberSource Corp. v. Retail Decisions, Inc.
Posted on August 19, 2011 by PSMN® | Comments Off on Federal Circuit Confirms That Abstract Mental Processes Are Not Patentable — CyberSource Corp. v. Retail Decisions, Inc.
What constitutes patentable subject matter under 35 U.S.C. § 101 has been a topic of keen interest, especially since the Supreme Court issued its decision in Bilski v. Kappos, 130 S. Ct. 3218 (2010) that rejected the Federal Circuit’s machine-or-transformation test. On Tuesday, the Federal Circuit further clarified what can be patented, affirming a rejection under § 101 of a claim for detecting fraud in credit card transactions over the internet. Written by Judge Dyk, the unanimous decision in CyberSource Corp. v. Retail Decisions, Inc. (Case No. 2009-1358) found that claims involving mental processes that can performed by the human mind are not patent eligible.
Two claims were at issue in CyberSource. They both involved a method for detecting fraud in credit card transactions over the internet by looking at the customer’s IP address. The claims were very broad with no specific algorithms for identifying fraud claimed.
utilizing the map of credit card numbers to determine if the credit card transaction is valid.
The Federal Circuit found that the method of claim 3 was nothing more than an abstract mental process. While the Supreme Court in Bilski rejected the machine-or-transformation test as the sole test of patentability under § 101, the Federal Circuit began its analysis there. It found that the claim recited no machines and did not perform any transformations. Following Bilski, it considered whether the claim was nonetheless patent eligible. It concluded that it was not because the claim recites a mental process, which is unpatentable under the Supreme Court’s decision in Gottschalk v. Benson, 409 U.S. 63, 67 (1972). Here, all of the steps of claim 3 could be performed by the human mind using a pen and paper. The Court suggested that if claim 3 had recited a more complex algorithm that could not have been performed easily using pen and paper, the result may have been different.
Thus, claim 3’s steps can all be performed in the human mind. Such a method that can be performed by human thought alone is merely an abstract idea and is not patent-eligible under § 101. Methods which can be performed entirely in the human mind are unpatentable not because there is anything wrong with claiming mental method steps as part of a process containing non-mental steps, but rather because computational methods which can be performed entirely in the human mind are the types of methods that embody the “basic tools of scientific and technological work” that are free to all men and reserved exclusively to none.
Claim 2 required a slightly different analysis. It basically recited the same method as in claim 3, but it tied it to a computer readable medium. The question was whether tying it to this structure created a machine that was patent eligible under § 101. The Federal Circuit concluded that it was not sufficient because the underlying invention was the method, not a manufacture for storing computer-readable information. To be patent eligible, the machine “must impose meaningful limits on the claim’s scope,” so the “the incidental use of a computer to perform the mental process of claim 3 does not impose a sufficiently meaningful limit on the claim’s scope.” Thus, claim 2 (like claim 3) was not patent eligible under § 101.
Inventors seeking to patent computer software or method claims should consider this decision carefully. If the claims simply recite steps that a human could perform with pen and paper, there is a real chance that the claim might not be eligible for patenting. Merely adding a limitation requiring a computer to perform the steps may not be sufficient to overcome this problem. Courts can look behind the words of the claim to determine what the underlying invention is and whether the use of a computer is meaningful. As always, careful claim drafting is very important if an inventor wants to obtain and enforce his or her patent.
Comments Off on Federal Circuit Confirms That Abstract Mental Processes Are Not Patentable — CyberSource Corp. v. Retail Decisions, Inc.
In the CBT Flint Partners, LLC v. Return Path, Inc. decision last week (No. 2010-1202, -1203), the Federal Circuit considered when a court can rewrite a claim during litigation to fix mistakes in drafting. The Court concluded that a district court has the authority to rewrite claims to correct obvious errors even if there are multiple ways to “fix” the claim, as long as all the possible solutions leave the claim with the same scope and meaning.
a computer in communication with a network, the computer being programmed to detect analyze the electronic mail communication sent by the sending party to determine whether or not the sending party is an authorized sending party or an unauthorized sending party, and wherein authorized sending parties are parties for whom an agreement to pay an advertising fee in return for allowing an electronic mail communication sent by the sending party to be forwarded over the network to an electronic mail address associated with the in-tended receiving party has been made.
The district court determined that there were three possible ways to fix this problem—(1) remove the word “detect”; (2) remove the word “analyze”; or (3) add the word “and” between the words “detect” and “analyze.” Because it felt that it was debatable which solution should be used, it concluded it lacked the authority to rewrite the claim. Thus, it found the claim indefinite under 35 U.S.C. § 112, ¶ 2 and granted summary judgment in favor of the defendant. The Federal Circuit reversed.
The Court determined that the district court erred because the three alternative solutions it was considering were not meaningfully different when viewed from the perspective of one skilled in the art. The concepts of “detecting” and “analyzing” were implicit in the rest of the claim, even if one of these terms was explicitly deleted. Thus, the scope and meaning of the claim were the same regardless of which solution the district court could have adopted. In these situations, the district court does have the authority to fix this kind of obvious mistake.
While this case suggests that courts are willing to bail out patentees and fix mistakes in claims during litigation, patentees should not rely on courts fixing their problems for them. In this particular case, the Federal Circuit found that the three possible solutions were all functionally identical. That will not always be the case, and, it is far more likely it will not be the case.
Obviously, the best practice is not to make mistakes in the first place, but that is often easier said than done. Patentees should be especially vigilant about reviewing the claims during prosecution to make sure that there are no mistakes. In addition, patentees should make sure to review the final, published version from the Patent Office, as mistakes sometimes do happen in the printing process. If a mistake happens after issuance, there are mechanisms to correct a patent (e.g., a certificate of correction). Finally, if a patentee is going to sue on a patent, it is especially important to review the patent again to make sure there are no mistakes. Don’t count on the court to bail you out!
The other takeaway from this case from the defense viewpoint is that courts may be more reluctant to find claims indefinite for obvious mistakes or typographic errors. Significant errors are still likely to doom patent claims, but it is not prudent to count on minor errors sinking them, too.
The bottom line with minor mistakes is that neither side should be confident in how a court will react. It may fix them, but it may not. And how a court will act likely depends on some very specific facts.

References: v. 
 v. 
 § 101
 v. 
 § 101
 v. 
 § 101
 v. 
 § 101
 § 101
 § 101
 v. 
 v. 
 § 112