In re Apple Inc.

650 F. App'x 771
CourtCourt of Appeals for the Federal Circuit
DecidedJune 9, 2015
Docket2015-136
StatusPublished
Cited by6 cases

This text of 650 F. App'x 771 (In re Apple Inc.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
In re Apple Inc., 650 F. App'x 771 (Fed. Cir. 2015).

Opinion

ON PETITION

Taranto, Circuit Judge.

ORDER

The United States District Court for the Eastern District of Texas entered orders denying motions (a) to sever all of the [772]*772claims against Apple Inc. from the claims against all the remaining defendants in this patent case and (b) to transfer the claims against Apple to the United States District Court for the Northern District of California. Apple now seeks a writ of mandamus directing the district court to grant its motions. We deny the petition.

BackgRound

Plaintiff ContentGuard Holdings, Inc., a small company, is incorporated and headquartered in Plano, Texas, within the Eastern District of Texas. It was originally a partnership created by Xerox Corporation and Microsoft Corporation to continue work done at Xerox’s Palo Alto Research Center on “digital rights management,” which addresses piracy and other challenges presented by distributing digital content over the Internet. As relevant here, ContentGuard owns nine patents on the subject.

In late 2013, ContentGuard filed this action in the Eastern District of Texas to assert those patents against Apple, Amazon.com, Inc., Huawei Technologies Co., Ltd. and Huawei Devices USA, Inc., Motorola Mobility LLC, HTC Corporation and HTC America, Inc., and Samsung Electronics Co. Ltd. and related Samsung entities. DirectTV, LLC and Blackberry Corporation were also named as defendants, but they are no longer in the case. Con-tentGuard alleged, among other things, that Apple and other defendants infringed many or all of the nine patents, directly or indirectly, by providing access to certain software applications (e.g., Google Play, Amazon Kindle) through their online stores or mobile devices. See Content-Guard Holdings, Inc. v. Amazon.com, Inc., No. 2:13-cv-01112-JRG (E.D. Tex. Oct. 17, 2014), ECF No. 244.1

The defendants each moved to sever at least some of the claims, and Apple (six months after the suit commenced) also moved to transfer to the Northern District of California all the claims brought against it. Chief among Apple’s arguments for transfer was that ContentGuard had executed a standard-form click-through Developer Agreement with Apple (for developers writing application software to run on Applets iOS platform) and a clause in the Agreement provides that any litigation “arising out of or relating to this Agreement, the Apple Software, or Your relationship with Apple will take place in the Northern District of California[.]” Apple also invoked the usual multi-factor analysis for transfer motions.2 A large volume of filings from the many parties accumulated as supplemental submissions • continued into March 2015.

On March 19, 2015, the district court denied the defendants’ motions to sever. ContentGuard Holdings, Inc. v. Amazon.com, Inc., No. 2:13-cv-01112-JRG, slip op. at 21 (E.D. Tex. Mar. 19, 2015), ECF No. 456. The district court concluded that the parties were not improperly joined under 35 U.S.C. § 299, noting that “the majority of the Movants appear to also share the Court’s conclusion.” Id. at 17. The court nonetheless said that it would exer[773]*773cise its discretion to order separate trials on certain claims once the record was more complete. Id. at 19.

On April 23, 2015, the district court denied Apple’s motion to transfer. Content-Guard Holdings, Inc. v. Amazon.com, Inc., No. 2:13-cv-01112-JRG, slip op. at 24 (E.D. Tex. Apr. 23, 2015), ECF No. 538 (Transfer Order). The court noted that a valid forum-selection clause should ordinarily be given controlling weight, id. at 7 (quoting Atl. Marine Const. Co., Inc. v. U.S. Dist. Ct. for W. Dist. of Tex., — U.S. -, 134 S.Ct. 568, 581, 187 L.Ed.2d 487 (2013)), but it held that the Developer Agreement’s forum-selection clause did not apply here. It reasoned, among other things, that this litigation was not related to the development and testing of Content-Guard’s application software for which it signed the Agreement. Id. at 8-9. Rather, this case is about whether Apple infringes the asserted patents by certain activities involving its own software and hardware and providing certain other non-Content-Guard software to users. Id.

With the forum-selection clause held inapplicable, the court considered the traditional factors bearing on a transfer analysis. It held that Apple had not met its burden of establishing that the Northern District of California was a clearly more convenient forum and that the existence of “co-pending claims (and suits) before this Court concerning the patents-in-suit .., weighs against transfer.” Id. at 12-23.

Discussion

The legal standard for mandamus is demanding. Apple must show, among other things, that it has a clear and indisputable legal right to the relief it seeks. See Cheney v. U.S. Dist. Ct. for D.C., 542 U.S. 367, 380-81, 124 S.Ct. 2576, 159 L.Ed.2d 459 (2004). Apple has not made that showing.

A

Apple’s challenge to the district court’s denial of transfer relies primarily on the forum-selection clause in the Developer Agreement. It invokes each of the three phrases in the forum-selection clause to which litigation must “relate” to come within the clause. We see no clear and indisputable right to application of the clause on any of the three bases.

Apple contends that this litigation is “related to” ContentGuard’s “relationship with Apple.” The district court rejected' that contention as taking the “relationship with Apple” language out of context and giving it an extraordinarily, and unduly, broad meaning. It noted that the Agreement elsewhere discusses the “relationship” between the parties in terms of making Apple a developer’s agent for the marketing and delivery of the applications to end users. We see no clear error in the district court’s reading of the “relationship” language to cover only litigation relating to that specific type of relationship, not, as Apple suggests, any dispute even about activities undertaken by Apple independently of any dealings with Content-Guard. And although Apple notes that “ContentGuard alleged that the end-user download of apps through Apple’s App Store infringes” the patents, Reply at 4, those allegations concern Apple’s distribution of applications developed by other providers. ContentGuard, which authorized distribution of its own applications by executing the Agreement, is not suing Apple for making ContentGuard’s own applications available.

Apple next argues this litigation is “related to” the “Apple Software” because it involves allegations concerning Apple’s iOS operating system. But the Agreement defines “iOS” as the “operating system provided by Apple for use by You only in connection with Your Application develop[774]*774ment and testing.” The district court, relying on that language, refused “to read the provision of ‘Apple Software’ to, in effect, encompass any use of Apple Software (e.g. iOS) in any context — even if the use is outside the scope of ‘development and testing.’” Transfer Order at 9.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

AQUAPAW BRANDS LLC v. PUSIFICA
W.D. Pennsylvania, 2025
AQUAPAW BRANDS LLC v. FLO PET
W.D. Pennsylvania, 2022
AQUAPAW BRANDS LLC v. YAN-PENG
W.D. Pennsylvania, 2022
AQUAPAW LLC v. ALLNICE
W.D. Pennsylvania, 2022
AQUAPAW BRANDS LLC v. TIKTOKS
W.D. Pennsylvania, 2022

Cite This Page — Counsel Stack

Bluebook (online)
650 F. App'x 771, Counsel Stack Legal Research, https://law.counselstack.com/opinion/in-re-apple-inc-cafc-2015.