MPH Technologies Oy v. Apple Inc. — Federal Circuit Revives Mobile-Security Patent Claims

Background

MPH Technologies Oy sued Apple over patents directed to keeping communications secure when a mobile device changes its network address. MPH accused Apple’s secure-messaging services of infringing five related patents, referred to as the ’949 patent family, and accused Apple’s virtual-private-network offerings of infringing U.S. Patent No. 7,937,581.

The ’949 family describes forwarding secure messages through an intermediate computer. Although the specifications discuss the IPSec security protocol extensively, the independent claims use broader terms such as “secure connection,” “secure message,” and “unique identity.” The district court nevertheless read those terms as limited to IPSec and treated “unique identity” as limited to the Security Parameters Index values used by IPSec.

The district court separately held asserted claims 6 through 8 of the ’581 patent indefinite. Those claims depend from a method claim in which a mobile terminal establishes a secure connection to a gateway, changes its address, asks the gateway to update the connection, and then sends a secure message through that connection. The district court believed the final reference to “the secure connection” lacked a consistent antecedent. After those rulings, the parties stipulated to noninfringement of the ’949 family and invalidity of the ’581 claims so MPH could appeal.

The Court’s Holding

The Federal Circuit reversed. On the ’949 family, the panel held that the broad “secure” terms were not restricted to IPSec. Independent claim 1 did not name IPSec, while dependent claims added IPSec limitations—strong evidence that the broader claim was meant to reach more than that particular protocol. The specification also called IPSec a preferred implementation, acknowledged that other control protocols could be used, and expressly said that the invention was not restricted to existing protocols such as IPSec.

The court called the issue close because the specification refers to IPSec repeatedly and even describes it as an “essential idea” in one passage. But frequency was not enough to overcome the patent’s express statement that the invention was not protocol-specific. Because the district court’s construction of “unique identity” as an IPSec-specific value depended on its treatment of “secure,” that construction fell as well. The panel vacated the stipulated judgment of noninfringement and returned the infringement case to the district court.

The panel also rejected the indefiniteness ruling on the ’581 patent. Reading the claim step by step and alongside the patent’s diagram, a skilled reader would understand that “the secure connection” remains the connection between the mobile terminal and the security gateway. The device changes addresses and the gateway updates the connection’s endpoint; the secure message then travels through that updated connection toward the other terminal. That sequence supplied reasonable certainty even if the drafting was not mathematically precise. The court therefore reversed the indefiniteness determination, vacated the stipulated invalidity judgment, and remanded.

Key Takeaways

• Repeated discussion of one protocol in a specification does not automatically limit broader claim language to that protocol, especially when the specification expressly preserves other implementations.
• Dependent claims that add a named protocol can reinforce the broader scope of an independent claim that omits it.
• An antecedent-basis problem is not necessarily fatal when the claim sequence and specification let a skilled reader identify the referenced component with reasonable certainty.
• The ruling revives MPH’s infringement theories but does not decide whether Apple actually infringes or whether the patents survive other validity challenges.

Why It Matters

The decision illustrates the line between reading claims in light of the specification and importing details from preferred embodiments into the claims. Technology patents often describe an invention through the dominant standard available when the application was written. If the claim text and specification preserve broader implementations, extensive discussion of that standard alone may not confine the patent to it.

For patent drafters, the opinion underscores the value of expressly stating that examples and protocols are nonlimiting. For accused infringers and patent owners, it also shows why claim differentiation and the specification’s scope-preserving language must be evaluated together. On remand, MPH can again pursue its case under broader constructions, while Apple remains free to contest infringement and validity on grounds the appeal did not resolve.