Posts Tagged: "Akamai v. Limelight"

The central issue before the Federal Circuit was whether there was a genuine issue of material fact that TSA’s performance of those steps could be attributed to Travel Sentry, such that Travel Sentry could be held singularly responsible for directly infringing Tropp’s method claims. Slip Op. at 13. The district court had answered this question in the negative… The Federal Circuit rejected the district court’s interpretation of divided infringement as too narrow and, accordingly, vacated its summary judgment of non-infringement.

The key issue in the present appeal, in light of Akamai V, is whether TSA’s performance of the final two steps of the patented method claims can be attributed to Travel Sentry, such that Travel Sentry is responsible for infringing the relevant claims… Under Akamai V, direct infringement under § 271(a) occurs where all steps of a claimed method are performed by a single entity. When more than one actor is involved in practicing the steps, the court considers whether the acts of one entity are attributable to the other such that a single entity is effectively responsible for the infringement. An entity will be held responsible for another’s performance of method steps where it directs or controls that performance. This is a question of fact.

The Court vacated the judgment against Mankes and remanded the case for further consideration. Because the law was in a state of flux, the Plaintiff pled facts that arguably would have supported an infringement theory under the law applicable when it was filed. The plaintiff could not have known the facts necessary to support a complaint under the law as it exists now. Because of this, the Court declined to affirm or reverse, and instead remanded the case to the district court for reconsideration under the new standards. Presumably, this would also give the Plaintiff an opportunity to amend the complaint.

The opinion provides guidance in terms of when divided infringement actually imposes liability for patent infringement. When a mastermind offloads one or more steps of a claimed method to another entity, then the actions of that other entity are vicariously attributed to the mastermind only if the relationship is one of a principal-agent or joint enterprise, or if there is a contract between the parties requiring or mandating the other entity to perform the offloaded method step. Whether other terms that limit the vicarious nature of a contract might impose liability will have to be litigated in the future.