Professional Documents
Culture Documents
United States Court of Appeals For The Fifth Circuit: Plaintiff-Appellant
United States Court of Appeals For The Fifth Circuit: Plaintiff-Appellant
United States Court of Appeals For The Fifth Circuit: Plaintiff-Appellant
No. 20-11032
Appeal from the U.S. District Court for the Northern District of Texas
Case No. 3:19-cv-02933 (Hon. Barbara J.G. Lynn)
_______________________________________________________________________________________________
No. 20-11032
- iii -
Case: 20-11032 Document: 00516346263 Page: 4 Date Filed: 06/06/2022
- iv -
Case: 20-11032 Document: 00516346263 Page: 5 Date Filed: 06/06/2022
Defendant-Appellees
1. Avanci, LLC
a. Inception IP, LLC is the parent company of, and wholly
owns Avanci, LLC. Inception Holdings, LLC is the parent company of,
and wholly owns, Inception IP, LLC.
2. Avanci Platform International Ltd.
a. Inception International Limited is the parent company of,
and wholly owns, Avanci Platform International Limited. Inception
Holdings, LLC is the parent company of, and wholly owns, Inception
International Limited.
3. Nokia Corporation
a. Nokia Corporation is a publicly traded company organized
under the laws of Finland. Nokia Corporation is not owned by any
parent corporation, and no other publicly held corporation owns 10%
or more of its stock.
4. Nokia of America Corporation
a. Nokia of America Corporation is a wholly owned subsidiary
of Nokia Solutions and Networks B.V., a company organized under the
laws of the Netherlands, which is a wholly owned subsidiary of Nokia
Solutions and Networks Oy, a company organized under the laws of
Finland.
-v-
Case: 20-11032 Document: 00516346263 Page: 6 Date Filed: 06/06/2022
- vi -
Case: 20-11032 Document: 00516346263 Page: 7 Date Filed: 06/06/2022
- vii -
Case: 20-11032 Document: 00516346263 Page: 8 Date Filed: 06/06/2022
Patrick S. Opdyke
WINSTON & STRAWN LLP
200 Park Ave.
New York, NY 10166
(212) 294-6700
popdyke@winston.com
- viii -
Case: 20-11032 Document: 00516346263 Page: 9 Date Filed: 06/06/2022
- ix -
Case: 20-11032 Document: 00516346263 Page: 10 Date Filed: 06/06/2022
-x-
Case: 20-11032 Document: 00516346263 Page: 11 Date Filed: 06/06/2022
TABLE OF CONTENTS
Page
Certificate of Interested Persons .................................................................. iii
Table of Contents ......................................................................................... xi
Table of Authorities ..................................................................................... xii
Statement of the Issue Presented .................................................................. 1
Introduction .................................................................................................. 1
Argument....................................................................................................... 3
I. Resolution of the issue presented cannot alter the
judgment..................................................................................... 3
II. The panel decision does not conflict with other authority. ........ 7
A. The panel decision does not conflict with other circuit
authority. ........................................................................... 8
B. The panel decision does not conflict with Supreme
Court precedent. .............................................................. 10
III. The Panel’s fact-bound, case-specific decision implicates
no issues of broad concern. ...................................................... 13
A. The panel decision does not threaten competition. ........ 13
B. The panel decision does not threaten the patent
system. ............................................................................ 14
Conclusion ................................................................................................... 16
Certificate of Service .................................................................................... 18
Certificate of Compliance ............................................................................ 19
- xi -
Case: 20-11032 Document: 00516346263 Page: 12 Date Filed: 06/06/2022
TABLE OF AUTHORITIES
Page(s)
Cases
Bell Atl. Corp. v. Twombly,
550 U.S. 544 (2007) ............................................................................... 12
California v. Rooney,
483 U.S. 307 (1987) ................................................................................. 3
Carnegie Mellon Univ. v. LSI Corp.,
2020 WL 5592990 (N.D. Cal. 2020) ......................................................... 5
Chevron, U.S.A., Inc. v. Nat. Res. Def. Council, Inc.,
467 U.S. 837 (1984) ................................................................................. 3
Conwill v. Greenberg Traurig, L.L.P.,
448 F. App’x 434 (5th Cir. 2011) .............................................................. 3
Ericsson, Inc. v. D-Link Sys., Inc.,
773 F.3d 1201 (Fed. Cir. 2014) ................................................................ 9
FTC v. Qualcomm Inc.,
969 F.3d 974 (9th Cir. 2020) ........................................................ 5, 14, 15
HTC Corp. v. Telefonaktiebolaget LM Ericsson,
12 F.4th 476 (5th Cir. 2021)............................................................... 9, 14
HTC Corp. v. Telefonaktiebolaget LM Ericsson,
2019 WL 126980 (E.D. Tex. 2019)......................................................... 15
LaserDynamics, Inc. v. Quanta Computer, Inc.,
694 F.3d 51 (Fed. Cir. 2012) .................................................................... 5
Lujan v. Defs. of Wildlife,
504 U.S. 555 (1992) ................................................................................. 6
Microsoft Corp. v. Motorola, Inc.,
696 F.3d 872 (9th Cir. 2012) (Microsoft I) .............................................. 9
Microsoft Corp. v. Motorola, Inc.,
795 F.3d 1024 (9th Cir. 2015) (Microsoft II) ........................................... 9
Perry v. Thomas,
482 U.S. 483 (1987) ............................................................................... 10
- xii -
Case: 20-11032 Document: 00516346263 Page: 13 Date Filed: 06/06/2022
- xiii -
Case: 20-11032 Document: 00516346263 Page: 14 Date Filed: 06/06/2022
1 Continental did not appeal the district court’s decision not to exercise
supplemental jurisdiction over its contract claims.
-1-
Case: 20-11032 Document: 00516346263 Page: 15 Date Filed: 06/06/2022
-2-
Case: 20-11032 Document: 00516346263 Page: 16 Date Filed: 06/06/2022
allege facts sufficient to establish that the contracting parties intended that
direct licenses be made available to component suppliers, such as
Continental, licenses that would be “redundant” of the licenses available to
the OEMs, which cover the components that Continental supplies to the
OEMs.
That fact-bound, case-specific determination does not conflict with the
prior decisions of this Court, other circuits, or the Supreme Court. Nor would
reconsideration of this alternative ruling by the panel alter the outcome of
this case. Continental falls far short of the high bar for rehearing en banc.
ARGUMENT
I. Resolution of the issue presented cannot alter the judgment.
-3-
Case: 20-11032 Document: 00516346263 Page: 17 Date Filed: 06/06/2022
-4-
Case: 20-11032 Document: 00516346263 Page: 18 Date Filed: 06/06/2022
-5-
Case: 20-11032 Document: 00516346263 Page: 19 Date Filed: 06/06/2022
-6-
Case: 20-11032 Document: 00516346263 Page: 20 Date Filed: 06/06/2022
4 Rehearing on the issue raised by Continental also would not change the
outcome of this case because there are yet other grounds on which
Continental’s complaint would have to be dismissed, including its failure to
allege an antitrust injury or an antitrust violation—as Judge Ho recognized
(Op. 2 n.1), and the district court held (ROA.6689, 6691, 6696).
-7-
Case: 20-11032 Document: 00516346263 Page: 21 Date Filed: 06/06/2022
panel simply concluded that Continental had failed to plead facts plausibly
suggesting that, under the circumstances here, it was an intended beneficiary
of the specific FRAND commitments at issue. Based on Continental’s own
allegations, the panel rightly determined that licensing the relevant patents
“up the chain” directly to Continental would be “redundant” of the licenses
made available to OEMs and thus “unnecessary to effectuate the purpose of
the FRAND commitments” in this particular case. Op. 11. Because
Continental pleaded no facts “suggest[ing] that [the] Patent-Holder
Defendants and SSOs intended to require redundant licensing of third
parties” (id.), Continental failed to establish that it was an intended
beneficiary of the specific contracts at issue here.
Similarly, and again contrary to what Continental suggests (Pet. 10),
the panel accepted “the core tenet of federal jurisdiction that ‘[i]njuries to’ ”
contractual rights, including contractual rights held by third-party
beneficiaries, can be “sufficient for standing purposes.’ ” Op. 12 (quoting
Servicios Azucareros de Venezuela, C.A. v. John Deere Thibodeaux, Inc.,
702 F.3d 794, 800 (5th Cir. 2012)). It simply found that Continental had
failed to plead such an injury here. These fact-bound, case-specific holdings
are entirely consistent with well-established legal principles and with the
purportedly conflicting authority cited by Continental.
A. The panel decision does not conflict with other circuit
authority.
-8-
Case: 20-11032 Document: 00516346263 Page: 22 Date Filed: 06/06/2022
Continental’s view, have “recognized that any business that implements the
standards and seeks a license to an SEP is a third-party beneficiary of the
patent holder’s FRAND promise and can enforce that promise.” Pet. 5. Not
so. None of the decisions that Continental cites purported to resolve any
dispute over a would-be licensee’s status as a third-party beneficiary of a
FRAND commitment. 5
In each case, the would-be licensee was the manufacturer of an end
product that practiced the standard. In each case, the holders of the
standard-essential patents traditionally licensed at that end-product level. In
each case, the would-be licensee undisputedly needed a license for the
patents at issue. In each case, neither the parties nor the Court questioned
whether the would-be licensee properly pleaded that it was an intended
beneficiary of the FRAND promise at issue. Thus, for each of those cases, the
broad statements that Continental cites about who may constitute a third-
party beneficiary of a given FRAND commitment was dicta in a background
discussion, not part of the court’s holding. See HTC, 12 F.4th at 481;
Microsoft II, 795 F.3d at 1031; Ericsson, 773 F.3d at 1209; Microsoft I, 696
F.3d at 879. Because those decisions do not address the pleading issue, they
do not—and cannot—conflict with the panel’s complaint-specific analysis of
the issue in this case.
-9-
Case: 20-11032 Document: 00516346263 Page: 23 Date Filed: 06/06/2022
-10-
Case: 20-11032 Document: 00516346263 Page: 24 Date Filed: 06/06/2022
that the question of whether a party can ‘enforce [an] agreement’ ‘simply
presents a straightforward issue of contract interpretation,’ not ‘standing
under Article III.’ ” Pet. 9–10. But the fact-specific decision in Perry
establishes no such “fundamental principle.” The panel decision, moreover,
is not to the contrary. The panel merely determined that Continental had
failed to allege facts sufficient to establish an injury-in-fact and had thus
failed to establish Article III standing (see Spokeo, Inc. v. Robins, 578 U.S.
330, 338 (2016)), even on the (erroneous) assumption that “Continental is
contractually entitled to a license on FRAND terms.” Op. 11.
Tacitly acknowledging that this determination negates any supposed
departure from Perry’s purported “principle,” Continental argues that “the
panel also disregarded Supreme Court precedent when it concluded that …
Continental did not suffer ‘an injury in fact’ ” even if it were a third-party
beneficiary of Defendants’ contractual FRAND commitments at issue. Pet.
10. Specifically, Continental asserts that the panel ignored the rule that
“[i]njuries to rights recognized at common law,” including contractual rights,
“have always been sufficient for standing purposes.” Id. (quoting Servicios,
702 F.3d at 800). But the panel “d[id] not take issue with … th[at] core tenet
of federal jurisdiction.” Op. 12. Rather, it found, as a matter of fact, that “in
this case” Continental’s allegations showed that it “experienced no such
injury.” Id. (emphasis added). That is because, in the specific circumstances
pleaded here, Continental “does not need” to conclude “licenses from [the
Defendants] to operate.” Id. at 11. As a result, “[o]n the face of Continental’s
complaint, there are no allegations that [the Defendant patent holders] have
-11-
Case: 20-11032 Document: 00516346263 Page: 25 Date Filed: 06/06/2022
-12-
Case: 20-11032 Document: 00516346263 Page: 26 Date Filed: 06/06/2022
the same terms as OEMs; and that Continental simply refused. See
ROA.1730–31, 1736–37. Thus, it was Continental’s allegations—not the
panel’s purported disregard for them—that doomed Continental’s claims.
III. The Panel’s fact-bound, case-specific decision implicates no
issues of broad concern.
-13-
Case: 20-11032 Document: 00516346263 Page: 27 Date Filed: 06/06/2022
it can sell its components without directly licensing the relevant patents; that
the Avanci agreement permits its members to individually license their
patents; and that there is no instance in which the Defendants have
prevented Continental from manufacturing and selling its components. Op.
4-5, 13.
Nothing in the panel decision prevents beneficiaries of FRAND
commitments from asserting claims about those commitments through
breach-of-contract suits. See, e.g., HTC, 12 F.4th at 482. And there was
therefore no need to do what Continental attempted here, namely, to use an
antitrust action to enforce claimed contractual rights without pleading facts
plausibly showing that it was an intended beneficiary of those rights or that
it suffered injury-in-fact.
B. The panel decision does not threaten the patent system.
-14-
Case: 20-11032 Document: 00516346263 Page: 28 Date Filed: 06/06/2022
component does, and whether that supplier has or needs a license. Id. at 996
& n.17. Furthermore, licensing at the end-product level also avoids complex
patent-exhaustion issues. See id. at 984.
Thus, contrary to Continental’s claims (Pet. 12-14), the panel’s
decision reflects—rather than upsets—longstanding licensing practices and
SSO policies. The American National Standards Institute (“ANSI”), for
example, has stated that its intellectual-property-rights policy does not
impose a general component-level licensing requirement. See Decision of the
ANSI Executive Standards Council Appeals Panel at 14 (Feb. 23, 2018),
https://bit.ly/38QLSGK (rejecting proposition that “ANSI’s Patent Policy
requires licensing at the component level”) (emphasis omitted). Similarly,
the European Telecommunications Standards Institute (“ETSI”) has rejected
an across-the-board requirement of component-level licensing; ETSI
requires licensing only of devices that fully implement its standards, i.e., end
products. See, e.g., Reply Br. of Appellant Qualcomm Inc., FTC v. Qualcomm
Inc., No. 19-16122, ECF No. 228, 2019 WL 7187003, at *14–15 (9th Cir.
2019); ETSI Intellectual Property Rights Policy, Art. 6.1,
https://www.etsi.org/intellectual-property-rights.
In sum, “the prevailing industry standard or approach has been to base
FRAND licenses on the end-user device.” HTC Corp. v. Telefonaktiebolaget
LM Ericsson, 2019 WL 126980, at *5 (E.D. Tex. 2019); see also Qualcomm,
969 F.3d at 984 (licensing “exclusively at the OEM level” is “not unique to
Qualcomm”); see also David J. Teece & Edward F. Sherry, On the “Smallest
Saleable Patent Practicing Unit” Doctrine: An Economic and Public Policy
-15-
Case: 20-11032 Document: 00516346263 Page: 29 Date Filed: 06/06/2022
-17-
Case: 20-11032 Document: 00516346263 Page: 31 Date Filed: 06/06/2022
CERTIFICATE OF SERVICE
I certify that this brief was served on all participating counsel on June
6, 2022, via the CM/ECF system.
-18-
Case: 20-11032 Document: 00516346263 Page: 32 Date Filed: 06/06/2022
CERTIFICATE OF COMPLIANCE
I certify that the foregoing document complies with the type-volume
limit of Fed R. App. P. 35(e), the typeface requirement of Fed. R. App. P.
32(a)(5), and the type-style requirements of Fed. R. App. P. 32(a)(6). The
document uses a proportional-spaced typeface, fourteen-point Georgia Pro
font. Based on a count under Microsoft Office Word 2016 for Windows, the
document contains 3,877 words, excluding the parts of the document
exempted by Fed R. App. P. 32(f).
-19-