CAFC Reverses IPSec Claim Construction, Revives Patent Owner’s Infringement Case Against Apple

The U.S. Court of Appeals for the Federal Circuit (CAFC) issued a decision Monday in MPH Technologies Oy v. Apple Inc., reversing a district court’s narrow construction of key claim terms and its finding of indefiniteness. The ruling revives MPH Technologies’ patent infringement claims against Apple, which had been stipulated away following the district court’s adverse claim construction rulings.

MPH Technologies Oy filed a patent infringement lawsuit against Apple in the U.S. District Court for the Northern District of California, accusing Apple of infringing five related ‘949 patents, as well as a separate patent, U.S. Patent No. 7,937,581. The ‘949 patent family covers methods for securely forwarding messages between computers through an intermediate device, while the ‘581 patent addresses maintaining secure connections for mobile terminals that switch network addresses. MPH asserted the ‘949 patent family against Apple’s secure messaging services and asserted the ‘581 patent against Apple’s virtual private network offerings.

At claim construction, U.S. District Judge Trina L. Thompson construed the “secure” terms in the ‘949 patent family as limited to the Internet Protocol security (IPSec) protocol and construed the term “unique identity” as limited to Security Parameters Index (SPI) values, which are specific to IPSec. The district court also held that claims 6, 7, and 8 of the ‘581 patent were indefinite, based on the limitation covering “the secure connection.” Following those rulings, MPH and Apple stipulated to judgment of noninfringement for the ‘949 patent family and invalidity for the ‘581 patent.

Writing for the court, Circuit Judge Kara Stoll, joined by Circuit Judges Alan Lourie and Todd Hughes, described the IPSec construction question as “a very close issue” given how frequently the ‘949 patent’s specification discusses the protocol. The district court had emphasized that IPSec appears in the specification nearly 200 times and pointed to language describing use of the standard protocol as an essential idea of the invention. The CAFC found that these references did not outweigh explicit language elsewhere in the specification disclaiming any such limitation.

The court pointed to language stating “[t]he invention was not restricted to the details of the figures and accompanying text, or any existing protocols, such as the currently standardised IPSec.” The opinion also noted that the specification separately stated that other control protocols could conceivably be used between the relevant computers. Since the inventor expressly stated the invention was not restricted to IPSec, the CAFC held that the number of references to the protocol in the specification could not justify reading an IPSec requirement into the broader claim term “secure.” The court also distinguished the district court’s reliance on GPNE Corp. v. Apple Inc., noting that the specification in that earlier case repeatedly and exclusively used a single term to refer to the claimed devices, unlike the specification at issue here.

The Federal Circuit also rejected Apple’s argument that dependent claim 8 of the ‘949 patent supported a narrower construction because it referenced “the IPSec connection.” The court agreed with MPH that this language likely resulted from a scrivener’s error during prosecution, as claim 8 originally depended on a different claim that expressly referenced IPSec. The court also rejected the related construction limiting “unique identity” to SPI values after rejecting the IPSec limitation on the term “secure.” Since the district court’s construction of “unique identity” depended entirely on its construction of “secure,” the Federal Circuit concluded that both limitations were improper. The CAFC vacated the stipulated judgment of noninfringement covering the ‘949 patent family and remanded for further proceedings.

The CAFC next considered whether a person of ordinary skill in the art could determine with reasonable certainty the scope of the disputed limitation in the ‘581 patent requiring the mobile terminal to send a secure message “in the secure connection” after changing network addresses. The district court had found the term indefinite for lacking antecedent basis, reasoning that the secure connection established earlier in the claim between the terminal’s original address and a security gateway differed from the secure connection referenced later after the terminal moved to a new address. The court concluded that the claim did not sufficiently identify which secure connection was being referenced.

The CAFC disagreed, walking through the claim limitations alongside the patent’s figures and specification. The court determined that the claim, read in light of the specification, described a single secure connection between the mobile terminal and the security gateway that persists even as the terminal’s address changes. The opinion noted that the district court itself had separately observed that reading the claim to describe two different secure connections would mean “the solution that the new invention is supposed to solve is not really solved.” The CAFC also rejected Apple’s argument that reading the connection as singular would create a claim with irreconcilably conflicting endpoints, finding that reading was inconsistent with the specification. The court reversed the indefiniteness determination, vacated the stipulated judgment of invalidity, and remanded for further proceedings.

The CAFC considered Apple’s remaining arguments and found them unpersuasive. Accordingly, the court reversed the district court’s claim constructions, vacated both stipulated judgments, and remanded the case for further proceedings consistent with its opinion. There were no concurring or dissenting opinions issued, and costs were awarded to MPH as the prevailing appellant.

Image Source: Deposit Photos
Image ID: 10042948
Author: almoond