throbber
Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 1 of 21
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`HUAWEI TECHNOLOGIES, CO, LTD, et
`al.,
`
`Plaintiffs,
`
`v.
`
`SAMSUNG ELECTRONICS CO, LTD., et
`al.,
`
`Defendants.
`
`
`
`Case No. 3:16-cv-02787-WHO
`
`
`ORDER GRANTING SAMSUNG'S
`MOTION FOR ANTISUIT
`INJUNCTION
`Re: Dkt. Nos. 234, 235, 240, 244, 277, 278
`
`INTRODUCTION
`
`Defendants/counterclaim-plaintiffs Samsung Electronics Co., Ltd., Samsung Electronics
`
`America, Inc., and Samsung Research America, Inc. (collectively, “Samsung”) seek to enjoin
`
`plaintiffs Huawei Technologies Co., Ltd., Huawei Device USA, Inc. and Huawei Technologies
`
`USA, Inc. (collectively, “Huawei”) from enforcing injunction orders issued by the Intermediate
`
`People’s Court of Shenzhen (“Shenzhen Court”). The Shenzhen Court orders found that Samsung
`
`is infringing two of Huawei’s Chinese standard essential patents (“SEPs”), and enjoined
`
`Samsung’s Chinese affiliates from manufacturing and selling its 4G LTE standardized
`
`smartphones in China. As a prerequisite to granting this relief, the Shenzhen Court considered
`
`whether the parties had complied with their obligations to license their SEPs on fair, reasonable,
`
`and nondiscriminatory (“FRAND”) terms. Both parties have asserted breach of contract claims in
`
`this action based on the other’s alleged failure to license their SEPs on FRAND terms.
`
`Under the framework established in E. & J. Gallo Winery v. Andina Licores S.A., 446 F.3d
`
`984 (9th Cir. 2006), Samsung has demonstrated that it is entitled to an antisuit injunction
`
`preventing Huawei from enforcing the injunction orders issued by the Shenzhen Court. Those
`
`orders could render meaningless the proceedings here, and the risk of harm to Samsung’s
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 2 of 21
`
`
`
`operations in China in the interim is great. Its motion is GRANTED.
`BACKGROUND1
`
`I.
`
`FACTUAL BACKGROUND
`The Parties
`A.
`Huawei and Samsung are major players in the world of wireless telecommunications—a
`
`world governed by cellular technology standards, such as the 3G UMTS and 4G LTE standards
`
`developed by the Third Generation Partnership Project (“3GPP”) and promulgated by standard
`setting organizations like the European Telecommunications Standards Institute (“ETSI”).2 Both
`Huawei and Samsung have agreed to license their declared standard essential patents (“SEPs”) on
`
`fair, reasonable, and non-discriminatory (“FRAND”) terms and conditions under ETSI’s
`
`Intellectual Property Rights (“IPR”) Policy. Compl. ¶ 63 (Dkt. No. 1[redacted], Dkt. No. 3-
`
`4[under seal]); see also Samsung’s Answer and Am. Counterclaims ¶ 29 (“Samsung admits that
`
`ETSI members who are subject to a commitment to offer licenses on FRAND terms and
`
`conditions are obligated not to refuse to enter a license for declared, essential patents that is fair,
`
`reasonable, and non-discriminatory.”)(Dkt. No. 91[redacted]; Dkt. No. 90-2[under seal]); id. ¶ 54
`
`(“Samsung admits that SEC has submitted IPR licensing declaration forms to ETSI expressing
`
`SEC’s [Samsung Electronics Co., Ltd.] preparedness to grant licenses on FRAND terms and
`
`conditions for certain patents as set forth in those declarations in accordance with the ETSI IPR
`
`Policy.”); Samsung’s Licensing Declarations (Samsung’s Answer and Am. Counterclaims, Exs.
`
`14, 23–26, 29, 34; Dkt. Nos. 91-14, -18, -23-26, -29, -34); Huawei’s Licensing Declaration
`
`(Huawei’s Compl., Exs. 2.1–2.43, Dkt. Nos. 3-1–13[under seal]).
`
`
`1 Portions of the background are redacted in accordance with the administrative motions submitted
`by both parties. Those motions are addressed at the end of this order.
` 2 Standard Setting Organizations “establish technical specifications to ensure that products from
`different manufacturers are compatible with each other.” Microsoft Corp. v. Motorola, Inc., 696
`F.3d 872, 875 (9th Cir. 2012)(“Microsoft II”)(citing Mark A. Lemley, Intellectual Property Rights
`and Standard–Setting Organizations, 90 Calif. L.Rev. 1889 (2002)). Many courts have
`expounded on the benefits of standards in various industries. See, e.g., Microsoft Corp. v.
`Motorola, Inc., 795 F.3d 1024, 1030 (9th Cir. 2015)(“Microsoft IV”); Apple, Inc. v. Motorola
`Mobility, Inc., 2011 WL 7324582, at *1 (W.D. Wis. June 7, 2011).
`2
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 3 of 21
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Samsung’s Manufacturing Operations in China
`
`B.
`Samsung’s Chinese manufacturing hubs have a production capacity of
`
`
`
`, the second largest worldwide. T. Wang Decl. ¶ 5 (Dkt. No. 240-48[under seal]). In
`
`2015 and 206, Samsung manufactured
`
` in China, of which
`
`
`
`Samsung sold
`
` units of LTE devices in China for a total revenue of
`
`
`
`were imported to the United States. Id. ¶¶ 6, 7. In the same years,
`
`. Id. ¶ 7.
`
`Negotiation History
`C.
`In 2011, the parties began discussing a cross-license for their respective patent portfolios,
`
`but they disagreed on the scope of those licenses. E.g., 3/2/15 Letter from Huawei to Samsung re”
`
`Patent Licensing Negotiation (Stake Decl. ¶ 19, Ex. 19, Dkt. No. 234-10[under seal]). I will not
`
`recount the history of their failure to reach agreement in the ensuing years, since all of the
`
`information has been filed under seal, except to wonder aloud how it can be in the interest of these
`
`important multi-national corporations to slog through unending litigation around the globe rather
`
`than figure out a process to resolve their differences if agreement is impossible.
`
`II.
`
`PROCEDURAL HISTORY
`Huawei filed this action on May 24, 2016, asserting infringement of 11 of its SEPs, and
`
`alleging that Samsung breached “its commitment to enter into a SEP cross-license with [Huawei]
`
`on FRAND terms and conditions.” Compl. ¶¶ 1, 4. Huawei also asks the court to set the terms
`
`and conditions for a global FRAND cross license under the parties’ respective worldwide
`
`portfolios of essential 3G and 4G patents, and to enjoin Samsung from “seeking injunctive relief
`
`against Huawei (including affiliates) in any jurisdiction with respect to any alleged infringement
`of any patent essential to 3GPP standards.”3 Compl. at Prayer for Relief, E. Samsung answered
`and filed counterclaims, including patent infringement claims for its own declared essential SEPs,
`
`declarations of non-infringement and invalidity of Huawei’s patents, and claims for antitrust
`
`
`3 Huawei points out that it has not sought preliminary injunctive relief attempting to halt any of the
`seven remaining actions brought by Samsung in China, which seek injunctive relief against
`Huawei based on its alleged infringement of Samsung’s SEPs. Opp’n at 8.
`
`
`3
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 4 of 21
`
`
`
`violation in violation of section 2 of the Sherman Act,4 and breach of contract. Answer and Am.
`Counterclaims at 47–114.
`The next day,5 Huawei filed 11 separate actions in China, ten of which it filed in the
`Intermediate People’s Court of Shenzhen (“Shenzhen Court”) where Huawei is based. Xie Decl. ¶
`
`3 (Dkt. No. 235-2). Eight of the actions involve 3G and 4G SEPs, including direct counterparts to
`
`patents-in-suit. Id. Each action seeks a determination on whether the SEP is infringed, and if so,
`whether an injunction should issue.6 Id. Samsung countered with fourteen of its own actions in
`China, alleging Huawei is infringing Samsung’s SEPs and seeking injunctive relief. Wang Decl.
`¶¶ 2–8; Xie Decl. ¶ 2 n.1. Seven of those SEP actions remain pending.7 See Xie Decl. ¶ 2 n.1.
`The Chinese actions have proceeded quicker than this one. See Wang Decl. ¶ 9 (describing
`
`status of the various actions). In particular, the Shenzhen court has held trials on two of Huawei’s
`
`SEPs and two of Samsung’s SEPs. Wang Decl. ¶¶ 9, 10. The trials addressed both FRAND
`
`issues and technical issues specific to each SEP. Id. ¶ 9. During these trials, the parties had full
`
`opportunities to present their evidence and argument. Id. ¶ 11; see also id. ¶¶ 12–19 (explaining
`
`the proceedings before the Shenzhen court that form the basis for this motion).
`
`
`4 As part of this claim, “Samsung seeks an order enjoining Huawei from pursuing injunctive relief
`for infringement of patents, including those asserted here and in the parallel Chinese actions, that
`Huawei contends are essential to ETSI and 3GPP standards.” Am. Counterclaims ¶ 322.
` 5 Huawei indicates that it filed the Chinese actions “simultaneously,” and that those actions reflect
`a different date due to the time difference between here and China. And it highlights Samsung’s
`acknowledgement that the actions were “simultaneous[ly]” filed. See Samsung’s Answer and Am.
`Counterclaims ¶ 340 (“Yet simultaneous with its filing of this action, Huawei filed eight actions
`against Samsung in China based on Huawei’s declared essential patents, seeking only injunctions
`as relief for Samsung’s alleged infringement… .”); id. ¶ 543 (“Around the same time as Huawei
`filed its Complaint here, Huawei initiated several patent infringement actions in China, seeking to
`enjoin Samsung from making, using, selling, or importing products that practice 3GPP
`standards.”).
` 6 Huawei has also initiated a rate-setting and royalty payment suit in China. Wang Decl. ¶ 2; Xie
`Decl. ¶ 22.
` 7 The parties filed a total of 42 infringement actions in China, one corresponding to each patent,
`both SEP and non-SEP. Wang Decl. ¶ 5. In parallel with those proceeding, all 42 patents
`underwent invalidation procedures at the Patent Reexamination Board (“PRB”). Id. ¶ 6. Once a
`patent is invalidated by the PRB, it must be withdrawn or dismissed. Id. ¶ 7. Twenty-two
`infringement suits remain between the parties—12 involving Huawei’s SEPs and 7 involving
`Samsung’s SEPs. Id. ¶ 8.
`
`
`4
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 5 of 21
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`On January 11, 2018, the Shenzhen Court issued orders finding that Samsung is infringing
`
`two of Huawei’s Chinese SEPs and enjoining Samsung’s Chinese affiliates from manufacturing
`and selling its 4G LTE standardized smartphones in China.8 Xie Decl. ¶ 7; Jan. 11, 2018
`Shenzhen Court Civil Judgment, certified translation (“Shenzhen Order”)(Stake Decl. ¶ 37, id.,
`Ex. 36, Dkt. No. 277-5[under seal]).9 The Chinese patents are direct counterparts to two of
`Huawei’s asserted patents, U.S. Patent Nos. 8,369,278 and 8,885,587. Xie Decl. ¶ 4. The
`
`Shenzhen Court evaluated the evidence and found that “Huawei’s behaviors had complied with
`
`FRAND principles while Samsung’s behaviors had not complied with FRAND principles.”
`
`Shenzhen Order at 205. The Shenzhen Court decided that Huawei’s six presuit offers to Samsung
`
`“were made within the reasonable range according to the strength of SEPs owned by Huawei” and
`
`that Huawei’s offers “had complied with FRAND principles.” See Shenzhen Order at 200–203.
`
`As to Samsung, the court found that its initial insistence on “binding SEP licensing and non-SEP
`
`licensing … violated FRAND principles for SEP licensing negotiations” and contributed to
`
`“serious[] delay[]” in the negotiations. Shenzhen Order at 180. It also found that “Samsung had
`
`made significant mistakes during technical negotiations,” which “seriously delayed the
`
`negotiations and clearly violated FRAND principles… directly leading to more than six years of
`
`negotiations between both parties without any progress.” Id. at 185. It concluded that Samsung’s
`
`sole SEP licensing offer “did not comply with FRAND principles.” Id. at 204.
`
`Samsung filed a notice of appeal on January 26, 2018. Xie Decl. ¶ 8. It filed this motion
`
`on February 1, 2018. Mot. to Enjoin Huawei from Enforcing the Injunction Issued by the
`
`Intermediate People’s Court of Shezhen (“Mot.”)(Dkt. No. 278-2[redacted]; Dkt. No. 278-1[under
`
`seal]). It claims that if its appeal is unsuccessful, it will have to close its factories in China,
`
`
`8 The Shenzhen court ordered a further continuation of the trial on Samsung’s two SEPs, and
`presumably heard that additional evidence on February 27–28, 2018. Wang Decl. ¶ 9. The parties
`are awaiting decisions in those two suits. Id.
` 9 Huawei noted that Samsung submitted only the order in case number 840, but actually seeks to
`enjoin orders issued in both case numbers 840 and 816. Wang Decl. ¶ 12 n.1. It indicated that
`“[t]he FRAND issues contemplated, evidence and expert opinion presented, and Court’s decision
`were substantively the same in both the 840 and 816 cases.” Id. It also represented that it accepts
`the accuracy of the certified translation “[f]or purposes of this motion only[.]” Opp’n at 6 n.2.
`5
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 6 of 21
`
`
`
`affecting
`
`, be forced into a negotiation at a disadvantage or be
`
`compelled into a global adjudication of all FRAND issues with Huawei, which it stoutly resists.
`
`Since the initial case management conference, Huawei has urged the court to bifurcate the
`
`issues and address the breach of contract and related FRAND issues first, which would likely
`
`moot the patent infringement claims. See Joint Case Management Conference St. at 2–5 (Dkt. No.
`
`67); Minute Entry for Initial CMC held on 9/13/16 (Dkt. No. 75); Huawei’s Br. ISO its Request to
`
`Bifurcate (Dkt. No. 84). Samsung has insisted that bifurcation was not the most efficient course
`
`because the FRAND licensing obligation cannot be determined without “assessing whether and to
`
`what extent [the patents-in-suit] are valid, infringed, enforceable, and essential to the relevant
`
`ETSI standard.” Samsung’s Opp’n to Bifurcation at 2 (Dkt. No. 85). I denied Huawei’s request to
`
`bifurcate, and issued a case management order setting a schedule for the parties to narrow the
`
`issues in preparation for a two-week trial. Order Regarding Case Management Proposals (Dkt.
`
`No. 143).
`
`LEGAL STANDARD
`
`“A federal district court with jurisdiction over the parties has the power to enjoin them
`
`from proceeding with an action in the courts of a foreign country, although the power should be
`
`‘used sparingly.’” Seattle Totems Hockey Club, Inc. v. Nat'l Hockey League, 652 F.2d 852, 855
`
`(9th Cir. 1981). “Such injunctions allow the court to restrain a party subject to its jurisdiction
`
`from proceeding in a foreign court in circumstances that are unjust.” E. & J. Gallo Winery v.
`
`Andina Licores S.A., 446 F.3d 984, 989 (9th Cir. 2006)(“Gallo”). The Ninth Circuit employs “a
`
`three-part inquiry for assessing the propriety of such an injunction.” Microsoft Corp. v. Motorola,
`
`Inc., 696 F.3d 872, 881 (9th Cir. 2012)(“Microsoft II”); see also Gallo, 446 F.3d at 990
`
`(establishing framework for determining whether to issue anti-suit injunction).
`
`First, we determine whether or not the parties and the issues are the
`same in both the domestic and foreign actions, and whether or not
`the first action is dispositive of the action to be enjoined. Second,
`we determine whether at least one of the so-called Unterweser
`factors applies. Finally, we assess whether the injunction’s impact
`on comity is tolerable.
`Microsoft II, 696 F.3d at 881 (citations and internal quotation marks omitted); see id. at 882
`
`6
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 7 of 21
`
`
`
`(referring to three-part inquiry as the “Gallo framework”).
`
`DISCUSSION
`
`Samsung moves to enjoin Huawei from enforcing the injunctions issued in the Shenzhen
`Orders.10 As a preliminary matter, the parties dispute whether Samsung must establish the usual
`requirements for a preliminary injunction, in addition to satisfying the three-part Gallo test for an
`
`anti-suit injunction. Huawei’s Opp’n to Samsung’s Mot. to Enjoin Huawei from Enforcing the
`
`Injunction Issued by the Intermediate People’s Court of Shenzhen at 4, 13, 23 (“Opp’n”)(Dkt. No.
`
`277-4[redacted]; Dkt. No. 277-3[under seal]); Reply ISO Samsung’s Mot. for a Preliminary
`
`Antisuit Injunction at 2 (“Reply”)(Dkt. No. 277-3[under seal]; Dkt. No. 277-4[redacted]). As the
`
`district court noted in Microsoft Corporation v. Motorola, Inc., “[u]nder a literal reading of Gallo,
`
`a showing of irreparable harm, balance of equities, and public interest might still be required to
`
`obtain an anti-suit injunction.” 871 F. Supp. 2d 1089, 1097 n.10 (W.D. Wash. 2012)(“Microsoft
`
`I”); see Gallo, 446 F.3d at 991 (“[Movant] need not meet the usual test of a likelihood of success
`
`on the merits of the underlying claim to obtain an anti-suit injunction . . . . Rather, [movant] need
`
`only demonstrate that the factors specific to an anti-suit injunction weigh in favor of granting the
`
`injunction.”).
`
`The court went on to note two things—the absence of an analysis on the traditional Winter
`
`factors in Applied Medical Distribution Corp. v. Surgical Co. BV, 587 F.3d 909, 913 (9th Cir.
`
`2009), and the fact that the Third Circuit explicitly replaced all four Winter factors with the three-
`
`part Gallo test. Microsoft I, 871 F. Supp. 2d at 1097 n.10. It nonetheless analyzed the remaining
`
`Winter factors “[f]or completeness[.]” Id. But the Ninth Circuit, in affirming the district court’s
`
`grant of the foreign anti-suit injunction, focused only on the three-part Gallo test. Microsoft II,
`
`696 F.3d at 881. But see id. at 883–84 (“Ordinarily, we do not assess at all the likelihood of
`
`success on the merits in a case like this, because when a preliminary injunction is also a foreign
`
`anti-suit injunction, the likelihood-of-success aspect of the traditional preliminary injunction test is
`
`
`10 As previously mentioned, Samsung references one order from the court, but it actually seeks to
`enjoin Huawei from enforcing two orders issued by the Shenzhen court on January 11, 2018. See
`supra note 9.
`
`7
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 8 of 21
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`replaced by the Gallo test.”). The Ninth Circuit’s analysis convinces me that I need only focus on
`
`the three-part inquiry under Gallo, and need not analyze the traditional Winter factors for
`
`obtaining a preliminary injunction.
`
`Because Samsung relies so heavily on that Ninth Circuit decision, see Mot. at 11–17, 19–
`
`21, I will begin with a background of that case.
`
`I.
`
`MICROSOFT V. MOTOROLA
`The decision in Microsoft v Motorola addressed the parties’ obligations with respect to
`
`patents they declared essential to the H.264 video coding standard set by the International
`
`Telecommunications Union (“ITU”). Microsoft II, 696 F.3d at 875–876. The ITU’s Common
`
`Patent Policy requires each member to “submit a declaration to the ITU stating whether it is
`
`willing to ‘negotiate licenses with other parties on a non-discriminatory basis on reasonable terms
`
`and conditions.’” Id. at 876. Motorola submitted numerous declarations to the ITU promising to
`grant licenses to its SEPs on “reasonable and nondiscriminatory,” or “RAND” terms.11 Id.
`“In October 2010, Motorola sent Microsoft two letters offering to license certain of its
`
`standard-essential patents.” 696 F.3d at 876. Motorola attached to the letter a “non-exhaustive
`
`list” of its U.S. and foreign patents that it declared essential to the H.264 standard and included in
`
`its license offer. Id. On November 9, Microsoft filed a breach of contract action against Motorola
`
`based on the theory that it was a third-party beneficiary to Motorola’s RAND obligations, which it
`
`alleged Motorola breached by proposing unreasonable royalty terms. Id. at 878. The next day,
`
`Motorola filed a patent infringement suit, and the two cases were consolidated. Id. In February
`
`2012, the district court granted partial summary judgment for Microsoft, concluding that (1)
`
`Motorola had binding commitments to offer its declared SEPs on RAND terms, and (2) Microsoft
`
`was a third-party beneficiary of those commitments. Id. The court denied summary judgment on
`
`the two remaining issues of whether Motorola’s initial offer letter had to include RAND terms,
`
`and whether its offers breached RAND obligations. Id. at 879. It scheduled those claims for a
`
`
`11 “RAND” and “FRAND” are “legally equivalent abbreviations.” Microsoft II, 696 F.3d at 877
`n.2.
`
`
`8
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 9 of 21
`
`
`
`bench trial in November 2012. Id.
`
`Eight months after the domestic actions were filed, Motorola sued Microsoft in Germany
`
`for infringement of two of its German patents, and it sought to enjoin Microsoft from selling
`
`allegedly infringing products in Germany. 696 F.3d at 879. On May 2, 2012, the German court
`issued its ruling,12 holding that (1) Microsoft did not have a license to use Motorola’s patents, (2)
`any commitment between Motorola and the ITU was not enforceable by Microsoft because
`
`German law does not recognize third-party contractual rights, and (3) Microsoft infringed
`
`Motorola’s German patents. Id. It enjoined Microsoft from “offering, marketing, using or
`
`importing or possessing” the accused products in Germany. Id.
`
`The “German injunction [was] not self-enforcing.” 696 F.3d at 879. Motorola had to
`
`“post a security bond covering potential damages to Microsoft should the infringement ruling be
`
`reversed on appeal[,]” then Microsoft could file a motion to stay the injunction in the German
`
`appellate court. Id. Alternatively, Microsoft could avoid enforcement of the injunction by
`
`employing “the Orange Book procedure,” under which it would make “an unconditional offer to
`
`conclude a license agreement” with Motorola. Id.
`
`On May 14, the district court converted the TRO, see supra note 12, into a preliminary
`
`injunction. Id. at 880. The Ninth Circuit affirmed this decision. I will reference its reasoning as I
`
`analyze each factor.
`
`II.
`
`APPLICATION OF THE GALLO TEST
`The Parties and the Issues are the Same
`A.
`“The threshold consideration for a foreign anti-suit injunction is ‘whether or not the parties
`
`and the issues are the same’ in both the domestic and foreign actions, ‘and whether or not the first
`
`action is dispositive of the action to be enjoined.’” Microsoft II, 696 F.3d at 882 (quoting Gallo,
`
`446 F.3d at 991). The consideration should be approached functionally, “not in a technical or
`
`formal sense, but in the sense that all the issues in the foreign action … can be resolved in the
`
`local action.” Id. at 882–83 (internal quotation marks omitted). “[W]hen the parties in the two
`
`
`12 By this time, Microsoft had already obtained a temporary restraining order (“TRO”) enjoining
`Motorola from enforcing any injunction obtained in the German action. 696 F.3d at 880.
`9
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 10 of 21
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`actions are the same, the two questions of whether ‘the issues are the same’ and whether ‘the
`
`domestic action is dispositive of the foreign action’ collapse into one.” Microsoft I, 871 F. Supp.
`
`2d at 1098.
`
`The Parties Are Functionally the Same
`1.
`Both sides agree that the parties are functionally the same (although not identical). Mot. at
`
`12; Opp’n at 16. Huawei Technologies Co., Ltd. and Samsung Electronics Co., Ltd. are parties to
`
`both actions, and some of their affiliates or subsidiaries are parties in each action. Xie Decl. ¶ 3;
`
`Since “[p]erfect identity of parties is not required for an anti-suit injunction[,]” Microsoft I, 871 F.
`
`Supp. 2d at 1098, this is sufficient to establish that the parties are functionally the same.
`
`The Issues Are Functionally the Same
`2.
`Samsung insists that the primary issue in the Shenzhen cases is at issue here—namely, the
`
`availability of injunctive relief for Huawei’s SEPs, which are subject to contractual licensing
`
`obligations under Huawei’s FRAND commitments. See Mot. at 12–15. It argues that “[e]ach
`
`party acknowledges it has contractual FRAND obligations for its global portfolio of
`
`telecommunications SEPs, contends it has complied with those obligations and that the other party
`
`has not, and has asked this Court to bar the other party from obtaining injunctive relief anywhere
`
`in the world on those SEPs.” Mot. at 12; see Compl. ¶ 1 (“Huawei and Samsung have made
`binding commitments to the European Telecommunications Standards Institute (“ETSI”)—a
`
`3GPP organizational partner which promulgates standards developed by 3GPP—to license these
`
`standard-essential patents (“SEPs”) on terms and conditions that are fair, reasonable, and non-
`
`discriminatory (“FRAND”).)(Dkt. No. 59).
`
`It urges that Microsoft v. Motorola is instructive because it “involved highly similar
`
`facts[.]” Id. at 13. Motorola argued that the U.S. action could not resolve the German action
`
`“because patent law is uniquely territorial and patents have no extraterritorial effect.” Microsoft
`
`II, 696 F.3d at 883. The district court rejected this argument, and the Ninth Circuit agreed.
`
`According to the district court, Microsoft’s contract claim would resolve Motorola’s German
`
`patent claims “because the European Patents at issue in the German Action were included in
`
`Motorola’s October 29 Letter offering a worldwide license for Motorola’s H.264 Standard-
`10
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 11 of 21
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`essential patents, and because Motorola contracted with the ITU to license the European Patents
`
`on RAND terms to all applicants on a worldwide basis.” Id. (quoting district court decision). It
`
`determined that the district court’s decisions on summary judgment (that Motorola’s RAND
`
`declarations to the ITU created a contract enforceable by Microsoft as a third-party beneficiary
`
`and that the contract governed the availability of injunctive relief for declared SEPs) were not
`“legally erroneous,”13 and therefore, it was not “an abuse of discretion for the district court to rule
`that the U.S. contract action might dispose of the German patent action.” Id. at 884.
`
`The Ninth Circuit cited Motorola’s “sweeping promise” in its declarations to the ITU,
`
`which included “a guarantee that the patent-holder [would] not take steps to keep would-be users
`
`from using the patented material, such as seeking an injunction, but [would] instead proffer
`
`licenses consistent with the commitment made.” Id. at 884. The court summarized, “that there
`
`[was] a contract, that it [was] enforceable by Microsoft, and that it encompasse[d] not just U.S.
`
`patents but also the patents at issue in the German suit.” Id. at 885 (emphasis in original). It
`
`concluded that irrespective of the district court’s ultimate determination as to whether Motorola
`
`actually breached its contract, “injunctive relief against infringement is arguably a remedy
`
`inconsistent with the licensing commitment.” Id.
`
`As in Microsoft v. Motorola, Huawei alleges that Samsung breached its contractual
`
`obligations under ETSI, Compl. ¶ 1, and seeks relief barring Samsung from obtaining injunctive
`
`relief on its declared SEPs anywhere in the world. Samsung insists, therefore, that “this action
`
`will necessarily resolve the fundamental issue presented in the Shenzhen injunction action,
`
`namely, whether injunctive relief is appropriate for alleged infringement of SEPs that are subject
`
`to contractual FRAND licensing obligations.” Mot. at 14. It also notes that there is no dispute
`
`that the Chinese SEPs fall within the global portfolios of SEPs, Xie Decl. ¶ 3, and Huawei listed
`
`those Chinese SEPs in the Letters of Assurance attached to its complaint, Huawei’s Licensing
`
`Declarations (Compl., Exs. 2.1–2.43). And it emphasizes that the two Chinese SEPs are direct
`
`counterparts of patents asserted here. Xie Decl. ¶¶ 4, 7.
`
`
`13 It emphasized that it was not deciding whether the district court’s determinations were “proper”
`because those issues were not before it on this interlocutory appeal. Microsoft II, 696 F.3d at 884.
`11
`
`Northern District of California
`United States District Court
`
`

`

`Case 3:16-cv-02787-WHO Document 280 Filed 04/13/18 Page 12 of 21
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`But Huawei underscores critical factual distinctions here; namely, differences in the
`
`positions of the parties and the decision of the foreign court. See Opp’n at 13–15. First, Microsoft
`
`initiated the domestic action and asked the court to set the FRAND rate. Microsoft I, 871 F. Supp.
`
`2d at 1099. In addition, it did not contest the essentiality or infringement of Motorola’s standard-
`
`essential patents. Microsoft Corp. v. Motorola, Inc., 2013 WL 2111217, at *59 (W.D. Wash. Apr.
`
`25, 2013)(“Microsoft III”); id. at *61. So, Huawei contends, “Samsung’s attempt to cast itself in
`
`the role of Microsoft … is perverse.” Opp’n at 13. Samsung did not initiate this action, and it is
`
`contesting the essentiality and infringement of Huawei’s declared SEPs. Second, Huawei
`
`distinguishes its own conduct from Motorola’s. It notes that it filed this action and the Chinese
`
`actions “at the same time,” not as “an end run around this action.” Id. at 14. This is unlike what
`
`happened in Microsoft, where Motorola filed its German suit several months into the U.S. RAND
`
`litigation, in a deliberate effort to force Microsoft to accept non-RAND terms. See Microsoft IV,
`
`795 F.3d at 1046 (“The evidence that the rates Motorola sought were significantly higher than the
`
`RAND rate found by the court suggested that Motorola sought to capture more than the value of
`
`its patents by inducing holdup, and that it filed infringement actions to facilitate that strategy by
`
`preventing Microsoft from using its patents—and therefore from implementing the 802.11 and
`
`H.264 standards—until it obtained a license at a rate significantly higher than the RAND rate.”);
`
`id. (“In the absence of a fear of irreparable harm as a motive for seeking an injunction, the jury
`
`could have inferred that the real motivation was to induce Microsoft to agree to a license at a
`
`higher-than-RAN

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket