throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`SAMSUNG ELECTRONICS CO., LTD. AND
`
`SAMSUNG ELECTRONICS AIVIERICA, INC.,
`
`Petitioner,
`
`V.
`
`SEVEN NETWORKS, LLC,
`Patent Owner.
`
`Case IPR2018-01108
`
`Patent 9,516,127
`
`Samsung Brief Addressing Real Party in Interest and Privity Issues
`
`

`

`lPR2018-01 108
`Proceeding N0.:
`Attorney Docket: 39843-0046IP2
`
`EXHIBIT LIST
`
`US. Patent No. 9,516,127 to Nirantar, et al. (“the ’ 127 patent”)
`
`US. Provisional Application No. 61/805,070
`
`Exhibit 1011 Murphy, The Busy COder ’s Guide to Android Development,
`
`CommonsWare, LLC (Sept. 2012)
`
` Exhibit 1010
`
`Exhibit 1012-
`
`1029
`
`Exhibit 1030
`
`Declaration of Joseph Shear
`
`Exhibit1031
`
`l
`
`I
`
`

`

`Proceeding N0.: IPR2018-01 108
`Attorney Docket: 39843-0046IP2
`
`I
`I
`
`I
`
`I
`
`I
`
`i
`
`Exhibit1032
`Exhibit1033
`
`Exhibit 1034
`
`l
`l
`
`I
`
`Exhibit 1035
`
`Declaration of Seung-Jae Oh
`
`Exhibit 1 03 6-
`
`1046
`
`Exhibit 1048
`
`Exhibit 1049-
`
`1050
`
`Exhibit 1051
`
`|
`
`I
`
`I
`
`I i
`
`Exhibit1047
`
`

`

`lPR2018-01 108
`Proceeding No.:
`Attorney Docket: 39843-0046IP2
`
`I.
`
`INTRODUCTION
`
`SEVEN Networks, LLC (“SEVEN”) alleges that Google LLC (“Google”)
`
`“is in privity with Petitioner, and is also a real party-in—interest (‘RPI’).” IPR2018-
`
`01108, Paper 11 (POPR), p. 1. These allegations are unsupported by and contrary
`
`to the evidence, which unequivocally demonstrates that Google is not an RPl to
`
`this proceeding or in privity with Samsung.
`
`11.
`
`APPROPRIATE LEGAL FRAMEWORK
`
`While alleging that Google is an RPI to this proceeding and that Google is in
`
`privity with Samsung, SEVEN does not set forth separate proofs for privity and
`
`RPI, but instead subsumes its analysis of RPI within a broader analysis of privity
`
`and focuses on the general business relationship between the parties throughout.
`
`See POPR at 9. Thus, the law of privity is addressed, followed by the law of RPI.
`
`The Federal Circuit specifically addressed the “legal standard for privity” in
`
`WesternGeco LLC v. ION Geophysical Corp, 889 F. 3d 1308, 1316-1319 (Fed.
`
`Cir. 2018).1 Based on its analysis of Taylor v. Sturgell, 553 US. 880 (2008), with
`
`respect to lPRs, the Federal Circuit cautioned against an over-application of privity
`
`1 Neither of the Federal Circuit’s subsequent decisions in Applications In Internet
`
`Time, LLC v. RPX Corp. (“AIT”), 897 F.3d 1336, 1360 (Fed. Cir. 2018) or Worlds
`
`Inc. v. Bungie, Inc. (“Worlds”),
`
`
`
`F.3d
`
`
`
`,2018WL4262564 (Fed. Cir. Sept. 7,
`
`2018) invalidate this precedent.
`
`

`

`Proceeding N0.: IPR2018-Ol lO8
`Attorney Docket: 39843-0046IP2
`
`and its preclusive effect. See WesternGeco, 889 F.3d at 1319 (“Because nonparty
`
`preclusion risks binding those who have not had a full and fair opportunity to
`
`litigate, the Supreme Court has cautioned that there is a general rule against
`
`nonparty preclusion, subject to certain exceptions.” (emphasis added)).
`
`The Supreme Court
`
`in Taylor
`
`identified a non-exhaustive list of six
`
`considerations where nonparty preclusion would be justified. Taylor, 553 US. at
`
`894-95. “Privity is essentially a shorthand statement that collateral estoppel is to
`
`be applied in a given case.”
`
`Id. at 1318-19 (citing 77 Fed. Reg. at 48,759)
`
`(emphasis added). In other words, the Taylor factors are considered with regard to
`
`“a given case,” such that parties may be in privity in one case but not in another.
`
`In applying the Taylor factors to the facts in WesternGeco, the Federal
`
`Circuit found that the relevant parties were n_ot in privity, despite the existence of
`
`(l) a “contractual and fairly standard customer-manufacturer relationship regarding
`
`the accused product” between the parties, and (2) a purchase agreement with
`
`potential indemnity obligations. See WesternGeco, 889 F.3d at 1321. The Federal
`
`Circuit held similarly in Wi-Fz' One, LLC v. Broadcom Corp, where “evidence
`
`showed that Broadcom’s interests as to the issue of infringement were generally
`
`aligned with those of its customers, and that Broadcom had indemnity agreements
`
`with at least two of the D—Link defendants,” yet “the evidence did not show that
`
`Broadcom had the right to control that litigation or otherwise participated in that
`
`

`

`lPR2018-01 108
`Proceeding No.:
`Attorney Docket: 39843-0046IP2
`
`litigation to the extent that it should be bound by the results.” Wi-Fi One, LLC v.
`
`Broadcom Corp, 887 F. 3d 1329, 1341 (Fed. Cir. 2018).
`
`The Federal Circuit has also identified the Taylor factors as “relevant” to
`
`determining whether a party is an RPl. See AIT, 897 F.3d at 1342. However, with
`
`regard to RPl, the Federal Circuit focuses more specifically on the relationship of
`
`an unnamed party to the lPR proceeding. See id. at 1351 (“whether a petition has
`
`been filed at a nonparty’s ‘behest’” is “at the heart” of “[d]etermining whether a
`
`non-party is a :real party in interest”).
`
`III.
`
`APPLICATION OF APPROPRIATE LEGAL FRAMEWORK
`
`SEVEN has not presented sufficient evidence to “reasonably bring[] into
`
`question the accuracy of a petitioner’s identification of the real parties in interest.”
`
`Worlds, 2018 WL 4262564 at *5, n. 8. The evidence provided by SEVEN in its
`
`POPRS is not sufficiently tied to the products and agreements between Samsung
`
`and Google relevant
`
`to these lPRs and the co-pending litigation.
`
`The old
`
`agreements and indemnification obligations cited by SEVEN are directed to old
`
`Android operating system products not shown to be associated with any of the
`
`particular Android products alleged to be infringing SEVEN’S patents. POPR, p.
`
`1-3, 6. SEVEN’s other evidence is at best evidence of a customer-manufacturer
`
`relationship or a joint defense relationship, both of which the Federal Circuit has
`
`deemed insufficient evidence of an RPl or a privity relationship. See POPR, p. 5-
`
`

`

`15', see also WesternGeco, 889 F.3d at 1321', 77 Fed. Reg. at 48,760; Wi-Fi One,
`
`Proceeding N0.: 1PR2018-01 108
`Attorney Docket: 39843-00461P2
`
`887 F.3d at 1336.
`
`Assuming, arguendo, that the evidence advanced by SEVEN reasonably
`
`brought into question the accuracy of a petitioner’s identification, a preponderance
`
`of the evidence demonstrates that Google is not an RPI to this proceeding or in
`
`privity with Samsung.
`
`Properly applying the Taylor
`
`factors to this case
`
`demonstrates that the interactions between Samsung and Google do not result in a
`
`“sufficiently close” relationship to justify a finding of privity or RPI.
`
`See
`
`WesternGeco, 889 F. 3d at 1318-19. The relevant time period for considering each
`
`Taylor factor is at the time the Petitions were filed. See Synopsys, Inc. v. Mentor
`
`Graphics Corp, IPR2012-00042, Paper 16 at 16-17 (PTAB Feb. 22, 2013).
`
`Factor 1: “An agreement to be bound”
`
`Samsung and Google have not agreed to be legally bound together,
`
`explicitly or implicitly. The only relevant agreements between Samsung and
`
`Google are:
`
`

`

`lPR2018-Ol 108
`Proceeding N0.:
`Attorney Docket: 39843-0046IP2
`
`— Accordingly,
`
`at the time of filing of these petitions and to date,
`
`there exists no agreement
`
`between the parties subjugating Samsung to Google in either the litigation or the
`
`lPRs.
`
`Likewise,
`
`— Samsung and Google are parties to separate co-
`
`pending litigations, which have been consolidated for pre-trial proceedings. As
`
`such, they may be bound by certain decisions of the consolidated proceedings
`
`(e.g.,, case schedule, claim construction). Even still, Samsung and Google are
`
`named in separate and distinct cases: each party has retained its own counsel and
`
`maintains the exclusive right to control the litigation of its own case (including
`
`settlement), and each case will be tried separately.—
`
`

`

`Proceeding N0.: IPR201 8-01 108
`Attorney Docket: 39843-0046IP2
`
`Factor 2: “pre-existing substantive legal relationships between the person to
`
`be bound and a party to the judgment”
`
`Federal Circuit precedent confirms that the business relationship between
`
`Samsung and Google does not rise to the level of RPI or privity. For instance, they
`
`are
`
`“distinct
`
`and unrelated corporate
`
`entities,” just as
`
`in WesternGeco.
`
`WesternGeco, 889 F.3d at 1320. Additionally, no AIT-like relationship exists
`
`between Samsung and Google.
`
`Indeed, Samsung is unlike the Petitioner in AIT
`
`(11a, RPX Corp), which held itself as “an extension of in—house counsel” for the
`
`unnamed party and who received funding from the unnamed party. See AIT, 897
`
`F.3d at 1340, 1342, 1364. Samsung and Google are separate and distinct parties in
`
`co-pending litigations, each represented by its own counsel.
`
`

`

`lPRZOl 8-01 108
`Proceeding N0.:
`Attorney Docket: 39843-0046IP2
`
`Factor 3: “adequate representation by someone with the same interests who
`
`was a party”
`
`As noted above,—
`
`I As a result, Google could settle out of the co-pending litigation and/or dismiss
`
`its IPRs, and Samsung’s position would be unchanged — it would still be defending
`
`its co-pending litigation, and it still would pursue its lPRs. Google does not and
`
`cannot represent Samsung in any of these proceedings; Samsung has and continues
`
`to represent and defend its own interests, without reliance on Google or any other
`
`party. Accordingly, Samsung has no assurance of adequate representation by
`
`Google or anyone else with the same interests who was a party.
`
`Factor 4: “assumption of control over the litigation in which the judgment
`was rendered”
`
`— As a result, Samsung
`
`maintains full, exclusive control over its defense. See Ex. 1035, W 3-5.
`
`Indeed,
`
`Google and Samsung have retained separate legal counsel in the two co-pending
`
`litigations and the lPRs, each individually directing its own defenses and
`
`controlling its own counsel.— This contrasts with previous
`
`cases involving Google and Samsung highlighted in SEVEN’S own evidence. For
`
`example, Exhibit 2041 describes a previous, unrelated litigation, in which Google
`
`

`

`specifically acknowledged its obligation to indemnify Samsung. Ex. 2041, pp. 1-3.
`
`lPR2018-01 108
`Proceeding N0.:
`Attorney Docket: 39843-0046IP2
`
`Without any evidence, SEVEN has asserted that Samsung and Google have
`
`“mounted a coordinated IPR campaign, wherein Google and Samsung have
`
`collectively filed 26 petitions, 21 of which challenge the 7 patents asserted in
`
`3
`common against the two companies.” POPR, p. 6. To the contrary, Samsung
`
`unequivocally states it alone has controlled and funded its IPRs. See EX. 1035, W
`
`3-5 (“Google in no way instructed, either directly or indirectly, Samsung to file
`
`these IPR petitions against SEVEN’S patents”). Google has made similar
`
`statements, establishing the independence of its IPR efforts. EX. 1030, W 19-21.
`
`In sum, the evidence demonstrates that the
`
`

`

`only communications between the parties were with regard to the “jointly-filed
`
`papers and coordination in district court .
`
`.
`
`.—
`
`Proceeding N0.: IPR2018-01 108
`Attorney Docket: 39843-00461P2
`
`” EX. 1030, fi 19.
`
`When considered in light of the broader relationship between Samsung and
`
`Google (as addressed in the other Taylor
`
`factors),
`
`the complete lack of
`
`communication, control, and funding with respect to the IPRs is more than enough
`
`evidence to prove that neither this nor the other IPRs filed by Samsung against
`
`SEVEN’S patents were at Google’s “behest,” which is the “heart” of the RPI
`
`inquiry. See AIT, 897 F.3d at 1351.
`
`It is notable that no judgments have yet been rendered, as contemplated in
`
`this factor.
`
`“In the AIA context, the privity provision of § 315(b) ‘prevent[s]
`
`successive challenges to a patent by those who previously have had the
`
`opportunity to make such challenges in prior litigation.” AIT, 897 F.3d at 1360
`
`(Renya concurring) (citing WesternGeco, 889 F.3d at 1319) (emphasis added).
`
`Here, there are no successive challenges, as Samsung’s IPRS were filed within
`
`several business days of Google’s lPRs, and there were no prior challenges before
`
`the PTAB. Further, there is no “prior litigation,” as both parties are involved in co-
`
`pending litigations in which no judgments had been entered at the time the
`
`petitions were filed.
`
`

`

`Proceeding No.: 1PR2018-01 108
`Attorney Docket: 39843-0046IP2
`
`Factor 5: “Where the nonparty to an earlier litigation acts as a proxy for the
`
`named party to relitigate the same issues”
`
`Again, there is no “earlier litigation,” and there is no relitigation of the
`
`“same issues.” Samsung’s IPRs were prepared, controlled, and financed entirely
`
`independent of Google, through the work of Samsung’s own counsel. Further, the
`
`timing of Samsung’s and Google’s petitions make it clear that the parties” IPR
`
`work was conducted in parallel, not serially.
`
`Samsung’s IPR work clearly
`
`proceeded on a separate but parallel
`
`track to Google’s IPR work, as the two
`
`parties” petitions were filed substantially contemporaneously. See EX. 1035, 1111 3-
`
`5', EX. 1030,
`
`1111 19-21. Moreover, both parties are involved in co-pending
`
`litigations that remain ongoing. At any time, one party could settle, and the
`
`position of the remaining party would be unchanged — it would still need to defend
`
`itself. Neither party is acting as a proxy for the other.
`
`Factor 6: “a special statutory scheme expressly foreclosing successive
`
`litigation by nonlitigants”
`
`No such special statutory scheme exists with regard to lPRs, nor has one
`
`been alleged by SEVEN. See A114 General [LC 12. UUSI ILC, 1PR2016-01049,
`
`Paper No 42, p. 10 (PTAB Nov. 1, 2017).
`
`IV.
`
`CONCLUSION
`
`For the foregoing reasons, Samsung and Google are neither RPls nor in
`
`privity, and the Supreme Court’s “general rule against nonparty preclusion” should
`
`be applied.
`
`10
`
`

`

`
`Date: October 12 2018
`
`/W. Karl Renner/
`
`lPR2018-01 108
`Proceeding N0.:
`Attorney Docket: 39843-00461P2
`
`W. Karl Renner, Reg. No. 41,265
`Jeremy Monaldo, Reg. No. 58,680
`Roberto DeVoto, Reg. No. 55,108
`Kim Leung, Reg. No. 64,399
`Fish & Richardson PC.
`
`3200 RBC Plaza, 60 South Sixth Street
`
`Minneapolis, MN 55402
`T: 202-783-5070
`
`F: 877-769-7945
`
`Attorneys for Petitioner
`
`ll
`
`

`

`Proceeding No.: IPR2018-01 108
`Attorney Docket: 39843-0046IP2
`
`CERTIFICATE OF SERVICE
`
`Pursuant to 37 CFR §§ 42.6(e)(1) and 42.6(e)(4)(iii), the undersigned
`
`certifies that on October 12, 2018, a complete and entire copy of this Samsung
`
`Brief Addressing Real Party in Interest and Privity Issues was provided Via email
`
`to the Patent Owner by serving the email correspondence addresses of record as
`
`follows:
`
`Kenneth J. Weatherwax
`
`Nathan Lowenstein
`
`Edward Hsieh
`
`Parham Hendifar
`
`Patrick Maloney
`
`LOWENSTEIN & WEATHERWAX LLP
`
`1880 Century Park East, Suite 815
`
`Los Angeles, CA 90067
`
`Email: weatherwax@10wensteinweatherwax.com
`
`SEVEN IPRs
`
`lowensteinweatherwaxcom
`
`lDiana Bradley/
`
`Diana Bradley
`Fish & Richardson PC.
`
`3200 RBC Plaza
`
`60 South Sixth Street
`
`Minneapolis, MN 55402
`(858) 678-5667
`
`

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