throbber
Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 1 of 11 PageID #: 7160
`
`UNITED STATES DISTRICT COURT
`EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`CIVIL ACTION NO. 2:18-cv-00546
`
`JURY TRIAL DEMANDED
`
`§§§§§§§§§§
`
`CANON, INC.
`
`Plaintiff,
`
`v.
`
`TCL ELECTRONICS HOLDINGS
`LTD., et al.,
`
`Defendants.
`
`PLAINTIFF CANON, INC.’S SUPPLEMENTAL CLAIM CONSTRUCTION BRIEF
`REGARDING
`
`After the Markman hearing, and only in response to this Court’s pointed questioning,
`
`Defendants finally admitted that Roku
`
`Roku is
`
`. Defendants also admitted that
`
`. In short, Roku is
`
` both before this Court and the
`
`PTAB — a fact Defendants omitted from their Initial Disclosures.1 Yet, Defendants contend
`
`Roku’s conflicting arguments before the PTAB are irrelevant to claim construction in this
`
`litigation because Roku is a different entity than Defendants.2
`
`That position is untenable. Roku is not an unrelated party;
`
`. As this Court noted, this relationship “goes to the binding nature of
`
`1 Defendants and Roku are both represented by the same counsel at Ropes & Gray.
`2 Dkt. No. 116 at 16:12-17:6. (“The main issue, though, that I need to correct from counsel's
`statement is the IPRs were filed -- filed by Roku. …. Now, Roku does supply the operating
`system to TCL, but the IPRs were signed by Roku, not by TCL.”).
`
`-1-
`
`CANON EXHIBIT 2015
`Roku, Inc. v. Canon Kabushiki Kaisha
`IPR2020-00343
`
`Page 1 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 2 of 11 PageID #: 7161
`
`
`
`
`the impact of that IPR proceeding here.” Dkt. No. 116 (Markman Tr.) at 16:6-11. Privity is the
`
`legal concept that captures instances when a person who is not a party to a litigation nevertheless
`
`appears in that litigation through the persona of another, its privy. Accordingly, the common law
`
`prohibits a litigant from taking a second bite at the apple by relitigating the same case—or the
`
`same issues—through its privy, particularly when the privy
`
`Specifically, by virtue of collateral and judicial estoppel, any decision in Roku’s IPRs would
`
`bind not only Roku itself, but also Defendants—
`
`.
`
`
`
`. The Court therefore should not ignore Roku’s arguments before the PTAB
`
`that manifestly contradict its privies’ positions here, and further demonstrate the correctness of
`
`Canon’s proposed claim constructions.
`
`BACKGROUND
`
`Canon has repeatedly requested
`
` and information since
`
`November 11, 2019. Ex. 1 at 15, RFP No. 60 (Nov. 11, 2019 Letter from Ozawa to Radsch
`
`providing RFPs); Ex. 2 at 29-30, RFP Nos. 18, 20 (Dec. 20, 2019 Roku Subpoena). On
`
`December 27, 2019, Roku filed IPR petitions on each of the asserted patents, listing Defendants
`
`as statutory privies for purposes of 35 U.S.C. §§ 315(b) and 315(e), but leaving unclear the exact
`
`relationship between the parties and if they were also privies in this litigation.3 See, e.g., Dkt.
`
`No. 91-14 (Ex. K, IPR2020-00357, Petition) at 9-10 (“Petitioner identifies the following
`
`companies as privies….”). Thereafter, Defendants (through its counsel, Ropes & Gray) spurned
`
`Canon’s
`
` on the basis of privilege, Ex. 3 (Jan. 13, 2020, Roku
`
`
`3 Defendants represented at the Markman hearing that Roku “identified privies because that’s
`what’s customary to do. And if you don’t, then there could be consequences at the
`PTAB.” Many IPR petitioners list potential privies out of caution. Dkt. No. 116 at 16:18-17:6.
`
`-2-
`
`Page 2 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 3 of 11 PageID #: 7162
`
`
`
`
`Response to Subpoena), but, on January 15, 2020, produced
`
`
`
`
`
`
`
`
`
`
`
`Through multiple meet-and-confers, Canon pressed Defendants and Roku as to whether
`
`they were, in fact,
`
`, but was told the information was
`
`privileged. Then, on February 20, 2020, Defendants served amended initial disclosures that
`
`failed to mention even the possibility
`
`, despite this Court’s Discovery Order
`
`requiring the parties to list any
`
` and to list all persons having knowledge of
`
`relevant facts with a description of their connection to the case. Dkt. No. 78, Sections 1(d)-(e).
`
`This caused Canon additional uncertainty as to whether
`
`
`
`. Unable to get a yes-or-no answer,
`
`Canon thus served an additional interrogatory and requests for admission to help clarify if Roku
`
`and Defendants were privies in this litigation. See Ex. 5 (Canon’s Second Set of Common
`
`Interrogatories); Ex. 6 (Canon’s First Set of Requests for Admission). Only after repeated
`
`pressing by this Court at the Markman hearing, did Defendants admit that Roku is
`
`. Dkt. No. 116 at 15:4-16:11; Ex. 7 (Defendants’
`
`March 19, 2020 Responses to Canon’s Second Set of Common Interrogatories).
`
`
`4 TCL Multimedia Technology Holdings Ltd. is a named Defendant in this action.
`, TTE Corporation is a subsidiary of TCL Multimedia Technology
`5
`Holdings Ltd.
`6
`
`
`
`
`
`
`
`
`
`
`
`-3-
`
`Page 3 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 4 of 11 PageID #: 7163
`
`
`Specifically, Defendants admitted that
`
`
`
`
`
`
`
`
`
`
` Under the TCL/Roku license agreement,
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`7 Dkt. No. 116 at 16:18 (“Now, Roku does supply the operating system to TCL . . . .”).
`8 Proceeding to list the exceptions noted in FN 6.
`
`-4-
`
`Page 4 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 5 of 11 PageID #: 7164
`
`
`
`
`
`
`
` Roku is also
`
`
`
`
`
`ARGUMENT
`
`
`
`
`
`
`
`
`
`Roku is
`
`, while
`
`simultaneously controlling and funding the IPR proceedings of the patents in suit. Thus, in
`
`effect, Roku (and Ropes & Gray, its common counsel with Defendants since at least November,
`
`6, 2019) are advancing claim constructions before the PTAB
`
`
`
`. Ex. 9 at 11-12 (November 6, 2019 Initial Disclosures listing “Roku, Inc.” and Roku
`
`employees as “contact only through outside counsel of record for Defendants”). While Roku’s
`
`role,
`
` and the IPR proceedings, ordinarily would not be an issue if it
`
`were maintaining consistent positions between both proceedings, that did not occur here.
`
`As is detailed in Ex. 10, Roku repeatedly advanced positions in the IPRs that are at direct
`
`odds with those advanced in this action. For example, regarding the ’413 Patent claim term
`
`“attribute of a remote control device,” Roku argued before the PTAB that the term should be
`
`construed as “remote control identification information or operation device information and, for
`
`the purposes of this Petition, include ‘code sequences transmitted from a remote control device,”
`
`but, on the other hand,
`
` before this Court that the term does
`
`not include transmitted code sequences. Dkt. No. 91-14 (Ex. K, IPR2020-00357, Petition) at 22.
`
`-5-
`
`Page 5 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 6 of 11 PageID #: 7165
`
`
`
`
`Defendants (or more aptly Roku), should not be allowed have their cake and eat it too,
`
`particularly after delaying disclosure of
`
`.
`
`This is not a situation where Defendants
`
` are making permissible arguments in
`
`the alternative. See e.g., Advanced Micro Devices, Inc. v. Aquila Innovations, Inc., IPR2019-
`
`01525, Paper No. 12, 21-23 (P.T.A.B. Mar. 6, 2020) (discussing how petitioner pursues grounds
`
`under its own construction/interpretation and alternatively under a different construction
`
`proffered by an opposing party). Rather,
`
`
`
` (without consequence before this Court) by taking contradictory positions
`
`before the PTAB and this Court. This is unequitable. Music Choice v. Stingray Dig. Grp., No.
`
`2:16-cv-00586-JRG-RSP, 2019 U.S. Dist. LEXIS 228326, at *15-16 (E.D. Tex. Nov. 19, 2019)
`
`(“This contradicts the current construction proposed by Stingray, and allowing Stingray to argue
`
`under one position during PTAB proceedings for issues of invalidity and then argue a
`
`contradictory position in this Court for issues of infringement would be unfair to Music
`
`Choice.”); see also inMusic Brands, Inc. v. Roland Corp., No. 17-00010-JJM, 2019 U.S. Dist.
`
`LEXIS 129622, at *6-7 (D.R.I. June 12, 2019) (holding that a defendant did not meet its burden
`
`of establishing indefiniteness of the term “minimize” where the defendant argued to the PTAB
`
`that claims including the term were previously known); Rovi Guides, Inc. v. Comcast Corp., 410
`
`F. Supp. 3d 628, 643 (S.D.N.Y. 2019) (“Furthermore, Rovi's current position seems to contradict
`
`the views it expressed before the PTAB when opposing Comcast's petition for IPR.”);
`
`Intellectual Ventures II LLC v. Kemper Corp., No. 6:16-cv-81-JRG-KNM, 2019 U.S. Dist.
`
`LEXIS 15753, at *14-16 (E.D. Tex. Jan. 31, 2019) (“Defendants also correctly point out that
`
`Plaintiff's plain and ordinary meaning construction contradicts the position Plaintiff took in front
`
`of the PTAB.”).
`
`-6-
`
`Page 6 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 7 of 11 PageID #: 7166
`
`
`Roku’s
`
`
`
`
` in this action establishes a
`
`
`
` under the common law that binds one to the positions taken by the other. See
`
`Wallace v. JP Morgan Chase Bank, N.A., No. 13-13862, 2014 U.S. Dist. LEXIS 133987, at *10
`
`(E.D. Mich. Sep. 24, 2014), aff'd as modified sub nom. Wallace v. JPMorgan Chase Bank, N.A.
`
`(6th Cir. 2015) 628 F. App’x 940 (“A privy includes a person so identified in interest with
`
`another that he represents the same legal right, such as a principal to an agent, a master to a
`
`servant, or an indemnitor to an indemnitee.”). “Privity is a ‘legal conclusion that the relationship
`
`between the one who is a party on the record and the non-party is sufficiently close to afford
`
`application of the principle of preclusion.’” Vines v. University of Louisiana at Monroe, 398
`
`F.3d 700, 706 (5th Cir. 2005). Privity, particularly with
`
`, is a
`
`prerequisite to showing that one party’s positions in one case binds another party in a different
`
`case under collateral and judicial estoppel. Id. at 705. Defendants’ belated discovery responses
`
`establish that
`
`.
`
` allowed to argue
`
`claim constructions in this action that are inconsistent with those being proposed by Roku at the
`
`PTAB.
`
`In the Fifth Circuit, “[i]ssue preclusion or collateral estoppel is appropriate when: (1) the
`
`identical issue was previously adjudicated; (2) the issue was actually litigated; and (3) the
`
`previous determination was necessary to the decision.” Pace v. Bogalusa City School Bd., 403
`
`F.3d 272, 290 (5th Cir. 2005); see also Duffy & McGovern Accommodation Servs. v. QCI
`
`Marine Offshore, Inc., 448 F.3d 825, 829 (5th Cir. 2006) (collateral estoppel applies to both
`
`issues of law and issues of fact). Administrative decisions by an administrative agency can
`
`ground collateral estoppel or issue preclusion. B & B Hardware, Inc. v. Hargis Indus., Inc., 575
`
`U.S. 138, 135 S.Ct. 1293, 1302-10, 191 L.Ed.2d 222 (2015) (finding that Trademark Trial and
`
`-7-
`
`Page 7 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 8 of 11 PageID #: 7167
`
`
`
`
`Appeal Board decisions can ground issue preclusion in district courts). Collateral estoppel also
`
`applies to issues of claim construction. e.Digital Corp. v. Futurewei Techs., Inc., 772 F.3d 723,
`
`726 (Fed. Cir. 2014) (finding collateral estoppel applied where a reexamined claim “present[ed]
`
`the identical claim construction inquiry” decided in a prior litigation).
`
`Similarly, judicial estoppel prevents parties from taking inconsistent positions when “‘(1)
`
`the party against whom judicial estoppel is sought has asserted a legal position which is plainly
`
`inconsistent with a prior position; (2) a court accepted the prior position; and (3) the party did not
`
`act inadvertently.’” Conversant Intelectual Prop. Mgmt. Inc. v. Xilinx, Inc., No. 6:12-CV-847,
`
`2015 WL 138157, at *3 (E.D. Tex. Jan. 9, 2015) (quoting Love v. Tyson Foods, Inc., 677 F.3d
`
`258, 261 (5th Cir. 2012)). Like equitable estoppel, judicial estoppel also applies to privies. Cf.
`
`Paltalk Holdings, Inc. v. Microsoft Corp., No. CIV.A. 2:06CV367-DF, 2008 WL 4830571, at *5
`
`(E.D. Tex. July 29, 2008); see also Austin v. McNamara, No. 6:05-CV-247, 2007 WL 5787498,
`
`at *3 (E.D. Tex. Mar. 30, 2007) (“[O]ther circuits have held that privity, though often present in
`
`judicial estoppel cases, is not required.”); Feuerbacher v. Wells Fargo Bank, No. 4:15-CV-59,
`
`2016 WL 3669744, at *3 (E.D. Tex. July 11, 2016) (“Defendants assert, and Plaintiffs do not
`
`deny, that the position they are currently taking is inconsistent with the position Billie took
`
`during the bankruptcy proceedings, that Billie’s position was accepted by the bankruptcy court,
`
`and that Billie’s failure to disclose was not inadvertent. Plaintiffs also do not dispute that privity
`
`exists between Plaintiffs, and thus, even though Alan was not a debtor in Billie’s bankruptcy
`
`proceedings, the doctrine of judicial estoppel applies to them both because of their
`
`relationship.”).
`
`The disputed claim constructions in this action are identical to those before the PTAB as
`
`the same patents, same claim terms, and same Phillips legal standard are at issue in both
`
`-8-
`
`Page 8 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 9 of 11 PageID #: 7168
`
`
`
`
`tribunals. The claim constructions are necessary for final decisions both in this Court and at the
`
`PTAB. Markman v. Westview Instruments, Inc., 52 F.3d 967, 997 n.7, (Fed. Cir. 1995) (en banc)
`
`(Mayer, J., concurring), aff'd, 517 U.S. 370 (1996) (“A claim must be construed before
`
`determining its validity just as it is first construed before deciding infringement.”).
`
`Because Roku is
`
`
`
`, the two parties have a sufficiently close relationship to be considered close privies, if
`
`not more. See Wallace, 2014 U.S. Dist. LEXIS 133987, at *10 (“A privy includes a person so
`
`identified in interest with another that he represents the same legal right, such as a principal to an
`
`agent, a master to a servant, or an indemnitor to an indemnitee.”). Thus, collateral and judicial
`
`estoppel will apply upon a final determination by this Court or the PTAB, and Roku’s positions
`
`in either tribunal are germane to issues in the other.
`
`Therefore, as Defendants
`
`, Canon respectfully requests
`
`that the Court consider Roku’s contradictory arguments before the PTAB when construing the
`
`disputed claim terms in this action.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`-9-
`
`Page 9 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 10 of 11 PageID #: 7169
`
`
`DATED: March 30, 2020
`
`
`
`
`
`Respectfully submitted,
`
`PAUL HASTINGS LLP
`
`By: /s/ Yar R. Chaikovsky
`Yar R. Chaikovsky
`yarchaikovsky@paulhastings.com
`Hiroyuki Hagiwara
`hiroyukihagiwara@paulhastings.com
`Jeffrey A. Pade
`jeffpade@paulhastings.com
`David Okano
`davidokano@paulhastings.com
`Bruce S. Yen
`bruceyen@paulhastings.com
`Kyotaro Ozawa
`kyotaroozawa@paulhastings.com
`1117 S. California Avenue
`Palo Alto, California 94304-1106
`Telephone: (650) 320-1800
`Facsimile: (650) 320-1900
`
`Harry L. Gillam, Jr.
`TX Bar No. 07921800
`GILLAM & SMITH LLP
`303 S. Washington Ave.
`Marshall, Texas 75670
`Telephone: (903) 934-8450
`Facsimile: (903) 934-9257
`gil@gillamsmithlaw.com
`
`Attorneys for Plaintiff
`
`
`
`
`
`
`-10-
`
`Page 10 of 11
`
`

`

`Case 2:18-cv-00546-JRG Document 121 Filed 04/02/20 Page 11 of 11 PageID #: 7170
`
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that all counsel of record who have consented to electronic
`
`service are being notified of the filing of this document via the Court’s CM/ECF system per
`
`Local Rule CV-5(a). I also hereby certify that all counsel of record are being served with a copy
`
`of the foregoing document by electronic mail on this 30th day of March 2020.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Harry L. Gillam, Jr.
`Harry L. Gillam, Jr.
`
`
`
`
`
`
`
`
`
`
`
`-11-
`
`Page 11 of 11
`
`

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