throbber
Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 1 of 21 PageID #: 914
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`
`The CALIFORNIA INSTITUTE OF
`TECHNOLOGY,
`
`
`
`
`
`SAMSUNG ELECTRONICS CO., LTD., and
`SAMSUNG ELECTRONICS AMERICA,
`INC.,
`
`
`
`
`Plaintiff,
`
`
`
`v.
`
`Civil Action No. 2:21-cv-446
`
`JURY TRIAL DEMANDED
`
`
`
`Defendants.
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO DEFENDANTS’ MOTION TO TRANSFER
`TO THE CENTRAL DISTRICT OF CALIFORNIA
`
`
`
`
`
`
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 2 of 21 PageID #: 915
`
`
`
`TABLE OF CONTENTS
`
`Introduction ......................................................................................................................... 1 
`
`Samsung’s motion to transfer – a thinly disguised effort to seek summary
`adjudication – fails across the board. .................................................................................. 1 
`
`I. 
`
`II. 
`
`A. 
`
`B. 
`
`Samsung is not an intended third-party beneficiary of the PLA. ............................ 2 
`
`Samsung cannot invoke a
`
`
`. .................................................................. 5 
`
`III. 
`
`Samsung’s Claim to a License of the Patents-in-Suit is Unmeritorious. ............................ 6 
`
`A. 
`
`B. 
`
`C. 
`
`D. 
`
`E. 
`
`The PLA does not cover the Patents-in-Suit. .......................................................... 6 
`
`The ’710 Patent was not and could not have been a CIP of the ’852
`Application. ............................................................................................................. 7 
`
`The other Patents-in-Suit also are not CIPs of the ’852 Application. ..................... 8 
`
`The parties’ course of conduct corroborates that the Patents-in-Suit were
`not covered by the PLA. ......................................................................................... 9 
`
`The parties sought to confirm their mutual understanding under the
`
`. ................................................................................................................... 10 
`
`F. 
`
`Samsung admits the IV-Samsung Agreement
`
` ....................................... 13 
`
`G. 
`
`Samsung’s remaining arguments cannot support transfer under § 1404. ............. 13 
`
`IV. 
`
`Conclusion ........................................................................................................................ 15 
`
`
`
`
`
`i
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 3 of 21 PageID #: 916
`
`TABLE OF AUTHORITIES
`
`
`
`
`
`Page(s)
`
`Cases
`
`Agence France Presse v. Morel,
`769 F. Supp. 2d 295 (S.D.N.Y. 2011) ........................................................................................3
`
`Alling v. Universal Mfg. Corp.,
`7 Cal. Rptr. 2d 718 (Cal. Ct. App. 1992) ...............................................................................4, 5
`
`Atl. Marine Constr. Co. v. United States Dist. Court for W. Dist. Tex.,
`571 U.S. 49 (2013) .............................................................................................................13, 14
`
`Autodesk, Inc. v. Alter,
`2018 WL 1335858 (N.D. Cal. Mar. 15, 2018) ...........................................................................3
`
`Gen. Protecht Grp., Inc. v. Leviton Mfg. Co.,
`651 F.3d 1355 (Fed. Cir. 2011)......................................................................................4, 14, 15
`
`Goonewardene v. ADP, LLC,
`434 P.3d 124 (Cal. 2019) ...........................................................................................................2
`
`Implicit, LLC v. Juniper Networks, Inc.,
`2020 WL 10356908 (E.D. Tex. Apr. 22, 2020) .......................................................................15
`
`In re Lab’y Corp. of Am. Holdings,
`2022 WL 1498775 (Fed. Cir. May 12, 2022) ..........................................................................14
`
`Peteet v. Dow Chem. Co.,
`868 F.2d 1428 (5th Cir. 1989) .................................................................................................14
`
`Uniloc USA, Inc. v. Cisco Sys., Inc.,
`2017 WL 959856 (E.D. Tex. Mar. 13, 2017) ....................................................................14, 15
`
`Zix Corp. v. Echoworx Corp.,
`2016 WL 7042221 (E.D. Tex. June 9, 2016) .....................................................................14, 15
`
`Statutes
`
`35 U.S.C. § 120 ............................................................................................................................7, 8
`
`35 U.S.C. § 121 ................................................................................................................................8
`
`35 U.S.C. § 365(c) ...........................................................................................................................8
`
`Cal. Civ. Proc. Code § 1856(c) ........................................................................................................9
`
`
`
`ii
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 4 of 21 PageID #: 917
`
`
`
`Regulations
`
`37 C.F.R. § 1.78 (2001) ...................................................................................................................8
`
`37 C.F.R. § 1.78(a)(2) (2001) ..........................................................................................................7
`
`
`
`iii
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 5 of 21 PageID #: 918
`
`
`
`I.
`
`Introduction
`
`Samsung’s motion to transfer venue is built on a series of unsupported assertions that fail
`
`to coalesce in any way to warrant its requested relief. The Patents-in-Suit1 are indisputably not
`
`covered by any license to Intellectual Ventures or, in turn, to Samsung. None of the Patents-in-
`
`Suit
`
`, nor are the Patents-in-Suit
`
`
`
`. Indeed, the parties to that agreement – Caltech and Cellular Elements (CE) –
`
`expressly agreed that
`
`.
`
`In any event, that is a question for a dispositive motion, which Samsung elected not to
`
`bring to this Court – instead opting for the procedural tactic of embedding its license defense within
`
`a belated transfer motion. This Court can readily dispense of Samsung’s motion to transfer venue
`
`on its face because Samsung cannot invoke
`
` of a Patent License
`
`Agreement (PLA) between two other parties. Samsung is neither a
`
`
`
`. Allowing Samsung to claim rights under the agreement would be
`
`inconsistent with
`
`, and Samsung cannot meet the separate hurdle of showing
`
`that the
`
`deliberately provides
`
`. That clause very
`
`, and Samsung
`
`is not
`
`. Finally, Samsung requests transfer pursuant to § 1404 without providing
`
`a full § 1404 analysis, further revealing the insufficiency of its motion.
`
`II.
`
`Samsung’s motion to transfer – a thinly disguised effort to seek summary
`adjudication – fails across the board.
`
`As shown below in Section III, Samsung can claim no license to the Patents-in-Suit. But
`
`Samsung has not asked the Court to render a ruling on a dispositive motion. To the contrary,
`
`
`1 The “Patents-in-Suit” are U.S. Patent Nos. 7,116,710 (“the ’710 Patent”), 7,421,032 (“the ’032
`Patent”), 7,916,781 (“the ’781 Patent”), and 8,284,833 (“the ’833 Patent”).
`
` 1
`
`
`
`
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 6 of 21 PageID #: 919
`
`
`
`Samsung continues to pursue third-party discovery from Intellectual Ventures on its futile license
`
`defense mission. Such discovery will not change the outcome of that defense, but it does
`
`underscore why Samsung’s transfer motion is an improper vehicle for resolving the license-
`
`existence issue. In any event, there is no basis for Samsung’s contention that its dispute with
`
`Caltech should be
`
`, as Samsung cannot claim it is entitled to the benefits of
`
`.
`
`A.
`
`Samsung is not an intended third-party beneficiary of the PLA.
`
`Samsung concedes it is not a party to the PLA nor
`
`Instead, Samsung asserts it can step into the shoes of CE to invoke
`
`.
`
`. But
`
`it cannot. To be a third-party beneficiary under California law, Samsung must show “(1) that it is
`
`likely to benefit from the contract, . . . (2) that a motivating purpose of the contracting parties is to
`
`provide a benefit to [Samsung], and . . . (3) that permitting [Samsung] to bring its own breach of
`
`contract action against a contracting party is consistent with the objectives of the contract and the
`
`reasonable expectations of the contracting parties.” Goonewardene v. ADP, LLC, 434 P.3d 124,
`
`126-27 (Cal. 2019). The PLA did not contemplate that
`
`
`
`.
`
`In Goonewardene, the plaintiff employee sued ADP, which performed payroll services for
`
`her employer, for claimed wages. Id. at 130. The California Supreme Court rejected her third-party
`
`beneficiary status, holding that even if “a contract between an employer and a payroll company
`
`will in fact generally benefit employees,” “the relevant motivating purpose of the contracting
`
`parties is to provide a benefit to the employer.” Id. at 127 (emphasis added). The court further
`
`found that allowing the employee’s suit would be contrary to the contracting parties’ expectations
`
`given (1) the number of employees, (2) the possibility that each of the employees would have a
`
`dispute with the employer, and (3) the ability of employees to sue the employer. Id.; see also
`
`
`
`2
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 7 of 21 PageID #: 920
`
`
`
`Agence France Presse v. Morel, 769 F. Supp. 2d 295, 303 (S.D.N.Y. 2011) (applying California
`
`law and finding that “users” of Twitter were not third-party beneficiaries of a license to Twitter
`
`that also conferred rights on “Twitter’s partners and sublicensees”); cf. Autodesk, Inc. v. Alter,
`
`2018 WL 1335858, at *4 (N.D. Cal. Mar. 15, 2018) (applying California law and finding that
`
`Autodesk was a third-party beneficiary where “Disney repeatedly indicated that the Agreement
`
`would need to cover Autodesk” during the “course of negotiation [of the Agreement]”).
`
`Setting aside that the PLA does not
`
`, the “motivating purpose” of
`
`the PLA was to
`
`to
`
`. Ex. A §§ 1.2, 1.3. There was no “motivating purpose”
`
`. Given (1) the number of potential sublicensees, (2) the
`
`possibility that each of the sublicensees could have a dispute with CE, and (3) the ability of each
`
`sublicensee to raise claims against CE directly, it would contravene Caltech and CE’s reasonable
`
`expectations to allow any of CE’s future valid sublicensees to invoke provisions related to suing
`
`Caltech. While the PLA contemplates that
`
`
`
` Ex. A § 3.3. The only specifically
`
`enumerated right afforded
`
` is that if the PLA
`
`, the
`
`. Id. This sole recitation of a
`
`
`
` in
`
`the PLA shows the parties knew how to include such language when they intended to confer a
`
`.
`
`Two of the agreements cited by Samsung further demonstrate why the PLA did not
`
`contemplate third-party beneficiaries. First, in stark contrast to the PLA, the IV-Samsung
`
`Agreement specifically
`
` and includes the following
`
`paragraph:
`
`
`
`
`
`3
`
`
`
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 8 of 21 PageID #: 921
`
`
`Ex. C ¶ 11.6. Nothing like this paragraph –
`
`
`
`
`
`
`
`
` – appears in the PLA. Second, the agreement in General Protecht Group
`
`(“GPG”) specifically stated that the Licensor “agrees that [the Licensees’] customers are intended
`
`beneficiaries . . . and . . . can enforce such provisions against [the Licensor].” Gen. Protecht Grp.,
`
`Inc. v. Leviton Mfg. Co., 651 F.3d 1355, 1358 (Fed. Cir. 2011). The PLA entirely lacks
`
`
`
`.
`
`The only license raised in Samsung’s motion to which it is an actual party – its own license
`
`agreement with IV – further undermines the position Samsung takes here. Section 11.3 of the IV-
`
`Samsung Agreement explicitly
`
` Ex. C § 11.3. The existence of § 11.3
`
`
`
`supports the notion that Samsung is not a third-party beneficiary of the Caltech-CE PLA. If, at the
`
`time Samsung and IV entered into the IV-Samsung Agreement, Samsung and IV considered
`
`Samsung to be a third-party beneficiary of the PLA, there would have been no need for the
`
` in the IV-Samsung Agreement, and they certainly would not have
`
`agreed to an
`
`. Rather, the most reasonable interpretation is that
`
`Samsung and IV did not consider Samsung to be a third-party beneficiary of the PLA.
`
`Finally, Samsung’s citation to Alling is of no avail. In that case, defendant Universal
`
`entered into a Purchase Agreement to buy plaintiff William Alling’s company, Luminoptics, and
`
`to use its “best efforts” to manufacture electronic ballasts. Alling v. Universal Mfg. Corp., 7 Cal.
`
`Rptr. 2d 718, 725-27 (Cal. Ct. App. 1992). At the same time, a related company, SLP, co-owned
`
`by Alling, granted Universal an exclusive license to its patents on electronic ballasts. Id. at 727.
`
`
`
`4
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 9 of 21 PageID #: 922
`
`
`
`When Universal was unsuccessful in manufacturing the ballasts, Alling sued Universal and SLP
`
`filed a claim as a third-party beneficiary against Universal. Id. at 729. On appeal, the court found
`
`that SLP could maintain its claim as a third-party beneficiary because “there was substantial
`
`evidence in the record” showing that, “by intent, [SLP] was to be directly and substantially
`
`benefited through the anticipated results of the Purchase Agreement.” Id. at 736. Specifically,
`
`Alling represented and sought to advance the interests of both Luminoptics and SLP in the
`
`negotiations of both the Purchase Agreement and the License Agreement. And “[t]he validity and
`
`effectiveness of [both agreements] were mutually contingent upon each other.” Id. In fact, by their
`
`“express[]” terms, “neither one could go into effect without execution of the other.” Id.
`
`This multi-layered nexus between the agreements, parties, and third-party beneficiary is
`
`absent here. The PLA and IV-Samsung Agreement were negotiated separately, years apart, by
`
`different parties. The contract displays
`
`. And the
`
`“validity and effectiveness” of those agreements are not “mutually contingent upon each other.”
`
`B.
`
`Samsung cannot invoke
`
`
`
`Even if Samsung could show the PLA contemplated third-party beneficiaries, that does not
`
`resolve whether the intended benefits included
`
`
`
`
`
`
`
`.
`
`This necessarily refers to only Caltech or CE. Samsung cannot claim it can receive the benefits of
`
`. See Ex. A § 9.10.
`
`
`
`5
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 10 of 21 PageID #: 923
`
`
`
`III.
`
`Samsung’s Claim to a License of the Patents-in-Suit is Unmeritorious.
`
`Although this Court may deny Samsung’s motion on the grounds that the PLA provided
`
`no rights for third parties to invoke
`
`, Samsung’s assertion that it has a
`
`license to the Patents-in-Suit also fails. Samsung contends it received a license to the Patents-in-
`
`Suit based on
`
`. But neither the PLA between Caltech
`
`and CE nor the IV-Samsung Agreement
`
`.
`
`Samsung does not contest this point. Instead, its entire argument hinges on claiming the
`
`Patents-in-Suit are licensed under the Caltech-CE PLA as continuations-in-part (CIP) of the ’852
`
`Application. Samsung Br. at 8. But that is another false premise: none of the Patents-in-Suit is a
`
`CIP (or continuation or division) of the ’852 Application, as confirmed by the file histories of the
`
`Patents-in-Suit and the course of conduct between Caltech and CE.
`
`A.
`
`The PLA does not cover the Patents-in-Suit.
`
`The PLA licensed
`
`id. at 15-18.
`
`
`
` not and does not cover the Patents-in-Suit.
`
`
`
`
`
`. Id. § 2 (“Patents” definition);
`
`
`
`6
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 11 of 21 PageID #: 924
`
`
`
`
`
`
`
`
`
`B.
`
`The ’710 Patent was not and could not have been a CIP of the ’852
`Application.
`
`Conceding the Patents-in-Suit were not part of the PLA, Samsung instead contends the
`
`asserted ’710 Patent is a CIP of the ’852 Application
`
`. This CIP
`
`argument defies the record and the law. The ’710 Patent was filed on May 18, 2001 as the ’102
`
`Application and listed only U.S. Provisional Application No. 60/205,095 as providing priority.
`
`Ex. D1. Consistent with this, the PTO recognized priority only from provisional application
`
`60/205,095. Ex. D2 (listed under “CONTINUING DATA”); Ex. D3 (same).
`
`Caltech did not take the steps necessary to designate the ’710 Patent as a CIP. Under 35
`
`U.S.C. § 120, in order for a later application to claim the benefit of an earlier-filed application, the
`
`applications must be co-pending, the later application must “contain[] or [be] amended to contain
`
`a specific reference to the earlier filed application,” and the amendment must be made at a time
`
`“as required by the Director” of the PTO or the benefit is waived. Ex. E (35 U.S.C. § 120 (2001));
`
`see also Ex. F (37 C.F.R. § 1.78(a)(2) (2001)) (codifying the “Director’s” requirements to claim
`
`such a benefit). Specifically, for an application to claim the benefit of “one or more prior filed
`
`copending nonprovisional applications,” the application “must contain a reference to each such
`
`prior application, identifying it by application number” and “indicating the relationship of the
`
`applications.” Ex. F (37 C.F.R. § 1.78(a)(2) (2001)). This reference must be submitted during the
`
`pendency of the application, and within the later of four months from the actual filing date of the
`
`application or sixteen months from the filing date of the prior application. Id. (“This time period
`
`is not extendable . . . [and] the failure to timely submit the reference required by 35 U.S.C. 120
`
`
`
`7
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 12 of 21 PageID #: 925
`
`
`
`and this paragraph is considered a waiver of any benefit under 35 U.S.C. 120, 121, or 365(c) to
`
`such prior application.”).
`
`Caltech did not and could not have properly claimed a continuation under 35 U.S.C. § 120
`
`or 37 C.F.R. § 1.78. The ’102 Application (when filed in May 2001) did not include a specific
`
`reference to the application number of a prior, non-provisional application. Caltech never indicated
`
`“the relationship of the [’102 and ’852] applications” while the ’102 Application was pending,
`
`another requirement of 37 C.F.R. § 1.78. Caltech did not indicate it in the first paragraph, nor did
`
`it indicate it in an Application Data Sheet (ADS) that was filed in August 2006. See Ex. D5 at 3
`
`(showing that the space on the ADS that would indicate such a relationship was left blank).
`
`In November 2004, when responding to an Office Action, Caltech’s attorney added the
`
`’852 Application to the first paragraph of the ’102 Application but did not state that the application
`
`was a CIP of the ’852 Application. Ex. D4 at 2. The ’102 Application issued in October 2006 as
`
`the ’710 Patent and did not state it was a CIP of any application. Ex. D7 (’710 Patent, cover page).
`
`Nearly two years after the ’710 Patent issued, the PTO incorrectly issued a Certificate of
`
`Correction stating the ’710 Patent was a CIP of the ’852 Application, Ex. D6, but that was
`
`erroneous and was subsequently rectified by a second Certificate of Correction that issued on July
`
`5, 2022. Ex. G1. This second Certificate corrected the priority claim to read, “This application
`
`claims the priority of U.S. Provisional Application Ser. No. 60/205,095, filed on May 18, 2000.”
`
`Id. Samsung cannot hang its purported license defense on an erroneous and subsequently
`
`superseded Certificate of Correction.
`
`C.
`
`The other Patents-in-Suit also are not CIPs of the ’852 Application.
`
`As the ’710 Patent is not a CIP, its child applications cannot be CIPs, notwithstanding what
`
`is stated on their cover pages. To reflect this, the PTO issued Certificates of Correction for the
`
`other three Patents-in-Suit that clarify that those patents are not continuations or CIPs of the ’852
`
`
`
`8
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 13 of 21 PageID #: 926
`
`
`
`Application. See Exs. G2-G4. For example, the Certificate of Correction for the ’032 Patent states,
`
`“This application is a continuation of U.S. application Ser. No. 09/861,102, filed May 18, 2001,
`
`now U.S. Pat. No. 7,116,710, which claims the priority of U.S. provisional application Ser. No.
`
`60/205,095, filed May 18, 2000.” Ex. G2. There is thus—correctly—no mention of the ’852
`
`Application in any of the Patents-in-Suit.
`
`D.
`
`The parties’ course of conduct corroborates that the Patents-in-Suit were not
`covered by the PLA.
`
`The parties’ conduct and course of performance confirms that neither the Patents-in-Suit
`
`nor their corresponding applications were licensed by the PLA. See Cal. Civ. Proc. Code § 1856(c)
`
`(allowing a contract’s terms to be explained or supplemented by “course of dealing or usage of
`
`trade or by course of performance”). Section 4.1 of the PLA, for example,
`
`. Ex. A § 4.1. Section 6.1 of the PLA
`
`
`
`
`
`
`
` Id. § 6.1. CE and Caltech complied with these duties
`
`for the ’852 Application and the patents that issued therefrom, U.S. Patent No. 7,089,477 and its
`
`continuation, U.S. Patent No. 7,716,552: (1) Caltech
`
`Decl. ¶ 15; (2) CE
`
`Decl. ¶ 12; and (4) CE
`
`, id.; Ex. I; (3) CE
`
`, Farina
`
`, Farina
`
`, id.
`
`On the other hand, Caltech and CE did the opposite when it came to the Patents-in-Suit.
`
`Caltech—
`
`. Id. ¶ 11. Caltech—
`
`. Id. Caltech never
`
`
`
`. This is
`
`especially significant with respect to the ’102 Application, which had already been filed when the
`
`PLA was executed. Had Caltech licensed that application to CE, it would have been obligated to
`
`
`
`9
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 14 of 21 PageID #: 927
`
`
`
`, yet it did not. Id. ¶ 14. Nor did CE
`
`
`
`as it would have been obligated to do. Id. ¶ 11.
`
`All of these actions are consistent with the fact that the PLA did not include the Patents-in-Suit.
`
`Samsung’s Exhibit 8, which Samsung proffers as evidence of
`
`
`
`
`
`evidence that Caltech did not believe that the PLA covered the ’710 Patent or its child applications,
`
` Samsung Br. at 8, is in fact
`
`which are now the Patents-in-Suit. Exhibit 8 actually shows that Caltech
`
`
`
`
`
`
`
`. Ex. H at CALTECH000021032-33; Farina Decl. ¶ 17. Subsequently, those rights
`
`were restored to Caltech.
`
`E.
`
`The parties sought to confirm their mutual understanding under the
`
`
`
`.
`
`As described above, two years after the issuance of the ’710 Patent, the PTO incorrectly
`
`issued a Certificate of Correction stating that the ’710 Patent was a continuation-in-part of the ’852
`
`Application. To avoid any confusion arising from this erroneous Certificate and consistent with
`
`the file history of the ’710 Patent, on September 30, 2011, Caltech and CE agreed to an
`
`Amendment – which superseded the original license – clarifying that
`
`. Ex. B § 3a (
`
`).
`
`Specifically, the parties made clear that the
`
`
`
`
`
` under the PLA. See Ex. B (
`
`). The Amendment added unequivocal
`
`language to the definition of “Patents,” as underlined below:
`
`
`
`
`
`
`10
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 15 of 21 PageID #: 928
`
`
`
`
`
`
`
`
`
`
`
`
`
`Ex. B at 1 (underlining added). Samsung acknowledges this
`
` but suggests that another
`
`amendment in the same document, made to Paragraph 4.4 of the PLA, effectively
`
`
`
`. Samsung Br. at 9. That Paragraph was amended to read as
`
`follows:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Ex. B at 1-2 (emphasized language cited by Samsung).
`
`Samsung’s interpretation is nonsensical and would render the exclusion language a nullity.
`
`The whole purpose of
`
`
`
` – to prevent any potential confusion created by the erroneous Certificate of
`
`Correction:
`
`
`
`11
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 16 of 21 PageID #: 929
`
`
`
`
`Ex. B at 2-3. The statements
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` is to be read as if it had been originally written
`
`that way (i.e.,
`
`) at the time the PLA was first signed in April 2005.
`
`Moreover, Paragraph 4.4 is essentially
`
`
`
`
`
`
`
`
`
`
`
`because including it is not in harmony with its tortured interpretation.
`
`See Samsung Br. at 9.
`
`Samsung claims certain emails show that
`
`
`
`
`
`Id. (citing Samsung’s Exs. 8-10). But all these exhibits show is that the 2004
`
`Certificate of Correction was
`
`Those emails also do not discuss the amended agreement’s
`
`
`
`
`
`which clarified that the
`
`. Consistent with
`
`, the PTO later issued Certificates of Correction to remove all priority
`
`references to the ’852 Application from all four of the Patents-in-Suit. Exs. G1-G4.
`
`
`
`12
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 17 of 21 PageID #: 930
`
`F.
`
`Samsung admits the IV-Samsung Agreement
`
`
`
`
`
`
`
`Samsung does not contend the Patents-in-Suit were directly listed or licensed under
`
`
`
`and relies again on its argument that it obtained rights to the ’852 Application
`
`and that the Patents-in-Suit are CIPs of that application. For the reasons described above, this
`
`provides no license to the Patents-in-Suit. Beyond that, Samsung has not even established which
`
`patents and applications were the subject of the IV-Samsung Agreement. Samsung points to § 8.6,
`
`Samsung Ex. 3, which refers to
`
` that
`
`purports to
`
`.
`
`Samsung Ex. 3 at 11. However,
`
` is blank. Id. at
`
` In its brief, Samsung cites to two standalone pages from its production and calls
`
`them “Att. A.” Samsung Br. at 4, 8 (citing Ex. 4). But those pages
`
`and they are, in fact, a subset of
`
`
`
`
`
` Samsung’s attorney declaration
`
`cannot establish that this
`
`that the ’852 Application was even within the scope of the patents licensed thereunder.
`
`G.
`
`Samsung’s remaining arguments cannot support transfer under § 1404.
`
`Samsung cites Atlantic Marine to argue that when there is a valid
`
` or
`
`,
`
`adjustments may be made to the § 1404 analysis. Atl. Marine Constr. Co. v. United States Dist.
`
`Court for W. Dist. Tex., 571 U.S. 49, 62 (2013); Samsung Br. at 5. But that case involved a dispute
`
`
`
`13
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 18 of 21 PageID #: 931
`
`
`
`between the actual parties to an agreement about the applicability of
`
`, not,
`
`as here, a dispute raised by a stranger to the agreement. And Atlantic Marine makes clear that its
`
`“analysis presupposes a contractually valid
`
`.” 571 U.S. at 62 n.5. Because
`
`Samsung is not a party to the PLA and cannot establish it is an intended third-party beneficiary,
`
`the Court cannot “presuppose a contractually valid
`
`,” Atlantic Marine is
`
`inapposite, and a full § 1404 analysis must be undertaken. Samsung has failed to do to so, and the
`
`Court may deny Samsung’s motion for this reason alone.2
`
`Samsung also cites GPG, Zix, and Uniloc to suggest that it does not need to prove its license
`
`defense now but need only show that it is “one-quarter” of the way there. Samsung wrongly
`
`contends it “far exceeds “the ‘one-quarter’ mark of the viability spectrum.” Samsung Br. at 8
`
`(quoting Uniloc USA, Inc. v. Cisco Sys., Inc., 2017 WL 959856, at *2 (E.D. Tex. Mar. 13, 2017)).
`
`Samsung’s arguments fail that threshold based on its own cited cases. Both GPG and Zix Corp. v.
`
`Echoworx Corp., 2016 WL 7042221 (E.D. Tex. June 9, 2016), involved settlement agreements
`
`between parties to the pending action that were supposed to resolve prior infringement cases. There
`
`was no question in either case that the settlement agreements were made between the parties to the
`
`actions. GPG, 651 F.3d at 1357; Zix, 2016 WL 7042221, at *1.
`
`Uniloc involved a settlement agreement with an explicit clause covering “third party
`
`customers [that] are intended to be third party beneficiaries of the agreement, and are ‘entitled to
`
`enforce the licenses and/or covenants not to sue without joinder of Microsoft as a party.’” Uniloc,
`
`
`2 Samsung’s motion should also be denied under the § 1404 inquiry because Samsung delayed its
`request until more than seven months after the complaint was filed and despite its awareness of its
`IV license and purported defense. See Peteet v. Dow Chem. Co., 868 F.2d 1428, 1436 (5th Cir.
`1989) (holding that the defendant must bring the transfer motion with “reasonable promptness”).
`In re Lab’y Corp. of Am. Holdings, 2022 WL 1498775, at *2 (Fed. Cir. May 12, 2022) (holding
`that an untimely transfer motion was not excusable where the party seeking transfer could identify
`no “material change in facts or law [to] justif[y] its delay in seeking transfer”).
`
`
`
`14
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 19 of 21 PageID #: 932
`
`
`
`2017 WL 959856, at *3 (quoting settlement agreement between Uniloc and Microsoft). Similarly,
`
`the contract in Implicit, LLC v. Juniper Networks, Inc., 2020 WL 10356908 (E.D. Tex. Apr. 22,
`
`2020), involved a covenant not to sue Intel’s customers, and the defendants asserting that contract
`
`as third-party beneficiaries were Intel customers, i.e., the intended beneficiaries of that provision.
`
`Id. at *3.
`
`In contrast, the PLA is
`
`, and Samsung is not a party to it. And
`
`the PLA
`
`
`
`. When all that is offered “is a license and a bare allegation that it
`
`provides a defense to the claims in suit,” such arguments will be rejected. Zix, 2016 WL 7042221,
`
`at *2 (noting that “the Federal Circuit rejected the extreme idea” behind such arguments (citing
`
`GPG, 651 F.3d at 1359)). Here, Samsung points to a license to which it is not a party (unlike in
`
`GPG and Zix) and under which it is not an intended third-party beneficiary (such as in Uniloc and
`
`Implicit), relies on
`
` that is limited to
`
`, and
`
`then makes the bare allegation that the license “provides a defense to the claims in suit” even
`
`though the
`
`. Samsung cannot use these attenuated
`
`assertions to demand transfer and its motion should be denied.
`
`IV. Conclusion
`
`Samsung’s motion should be denied.
`
`
`DATED: August 17, 2022
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`By:
`
`
`
`/s/
`
`Kalpana Srinivasan
`
`
`
`
`
`
`
`Kalpana Srinivasan
` California State Bar No. 237460
`
`ksrinivasan@susmangodfrey.com
`SUSMAN GODFREY LLP
`1900 Avenue of the Stars, Suite 1400
`Los Angeles, CA 90067
`
`15
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 20 of 21 PageID #: 933
`
`
`
`Telephone: (310) 789-3100
`Facsimile: (310) 789-3150
`
`Daniel J. Shih
` Washington State Bar No. 37999
`
`dshih@susmangodfrey.com
`SUSMAN GODFREY LLP
`401 Union Street, Suite 3000
`Seattle, WA 98101
`Telephone: (206) 516-3880
`Facsimile: (206) 516-3883
`
`Shawn D. Blackburn
`
`Texas State Bar No. 24089989
`
`sblackburn@susmangodfrey.com
`Daniel A. Wilson
`
`Texas State Bar No. 24070859
`
`dwilson@susmangodfrey.com
`SUSMAN GODFREY LLP
`1000 Louisiana Street, Suite 5100
`Houston, TX 77002
`Telephone: (713) 651-9366
`Facsimile: (713) 654-6666
`
`Ravi Bhalla
`New York State Bar No. 5478223
`rbhalla@susmangodfrey.com
`Robert Greenfeld
`New York State Bar No. 2824811
`rgreenfeld@susmangodfrey.com
`SUSMAN GODFREY LLP
`1301 Avenue of the Americas, 32nd Fl.
`New York, NY 10019
`Telephone: (212) 336-8330
`Facsimile: (212) 336-8340
`
`ATTORNEYS FOR PLAINTIFF
`THE CALIFORNIA INSTITUTE OF
`TECHNOLOGY
`
`16
`
`
`
`
`
`
`
`

`

`Case 2:21-cv-00446-JRG Document 62 Filed 08/19/22 Page 21 of 21 PageID #: 934
`
`
`
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on August 17, 2022, all counsel of record who are deemed to have
`
`consented to electronic service are being served with a copy of this document via the Court’s
`
`CM/ECF system.
`
`
`
`
`
`
`
`
`
`Dated: August 17, 2022
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` /s/
`
`
`
`Kalpana Srinivasan
`
`Kalpana Srinivasan
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`17
`
`

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