throbber
IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`§§
`

`§ Case No. 2:19-CV-00414-JRG

`
`BRIGHT DATA LTD.
`
` Plaintiff,
`
` v.
`
`§§
`

`
`TEFINCOM S.A. D/B/A NORDVPN
`
` Defendants.
`
`JOINT STATUS REPORT REGARDING MEDIATION
`
`Pursuant to the Court’s March 16, 2022 mediation orders (“Mediation Order”)1 entered in
`
`each of the Bright Data Ltd. v. Teso LT, UAB et. al., Case No. 2:19-CV-00395 (“Teso Action”),
`
`Bright Data Ltd. v. Code200, UAB et. al., Case No. 2:19-CV-00396 (“Code200 Action”) and
`
`Bright Data Ltd. v. Tefincom S.A., Case No. 2:19-CV-00396 (“Tefincom Action”) (collectively,
`
`“Related Actions”) and subsequent orders regarding the same, the Parties held an in-person medi-
`
`ation on August 24, 2022 before Judge Folsom regarding the Related Actions. Pursuant to the
`
`Court’s Mediation Order in the Teso Action, Plaintiff Bright Data Ltd. (“Bright Data”) and De-
`
`fendants Teso LT, UAB, Metacluster LT, UAB and Oxysales, UAB (collectively, “Defendants”)
`
`respectfully file this Joint Status Report. As stated in Judge Folsom’s August 25, 2022 Mediation
`
`Report, “The mediation session ended in an impasse. No further follow up is anticipated.” Teso
`
`Action, Dkt. 586 at 1; Code200 Action, Dkt. 277 at 1; Tefincom Action, Dkt. 214 at 1.
`
`Remaining Disputes in Tefincom Action: The Parties have the following remaining dis-
`
`putes and other motions:
`
`
`1 A similar Mediation Order was entered in each of the Teso Action (Dkt. 580), Code200 Action
`(Dkt. 270), and Tefincom Action (Dkt. 205).
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`1 of 11
`
`

`

` Defendants’ response and subsequent briefing to Bright Data’s pending Motion to
`
`Exclude Dr. Aviel Rubin (“Motion to Exclude Dr. Aviel Rubin,” November 18,
`
`2021, Dkt. 179);
`
` The Parties’ Joint Stipulation and Motion for Entry of Order Addressing Claims
`
`and Parties to address Tefincom’s post-litigation reorganization (See e.g. Dkt. 183);
`
` Bright Data’s Second Amended Complaint (See e.g. Dkt. 183);
`
` Tefincom’s Answer to Second Amended Complaint (See e.g. Dkt. 183);
`
` The Parties exchange of Updated Exhibit Lists, Witness Lists and Deposition Des-
`
`ignations;
`
` The Filing of the Joint Pretrial Order, Proposed Jury Instructions, and Joint Pro-
`
`posed Verdict Form; and
`
` Bright Data’s Motions in Limine (Dkt. 167)(Briefing is incomplete as Defendant
`
`has not filed its response to the motions);
`
` Defendants’ Motions in Limine (Dkt. 166)(Briefing is incomplete as Defendant has
`
`not filed its reply in support of the motions);
`
` Defendant’s motion for Summary Judgment of Noninfringement of the ‘319, ‘510,
`
`and ‘614 Patents (Dkt. 93);
`
` Bright Data’s Motion for Partial Summary Judgment on Certain Invalidity Grounds
`
`(Dkt. 92);
`
` Defendant’s Motion for Partial Summary Judgment of Noninfringement or in the
`
`Alternative Invalidity for the ’511 Patent (Dkt. 91);
`
` Defendant’s motion to Exclude Opinions and Testimony of Dr. Vernon Thomas
`
`Rhyne, III (Dkt. 90);
`
`- 2 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`2 of 11
`
`

`

` Bright Data’s Motion to Strike Certain Invalidity Opinions of Dr. Michael J. Freed-
`
`man (Dkt. 89);
`
` Defendant’s motion to Exclude Opinions and Testimony of Dr. Stephen Becker
`
`(Dkt. 88);
`
` Defendant’s Motion for Summary Judgment of Invalidity of the ‘’319, ‘’510, and
`
`’511 Patents (Dkt. 87);
`
` Bright Data’s Motion to Strike Certain Non-Infringement Opinions of Dr. Kevin
`
`Almeroth (Dkt. 86);
`
` Bright Data’s Daubert Motion to Exclude Expert Testimony of Keith R. Ugone
`
`(Dkt. 85);
`
` Bright Data’s Motion for Leave to File Second Amended Infringement Contentions
`
`(Dkt. 75); and
`
` Bright Data requests the production of updated financials from Tefincom and an-
`
`ticipates filing a Motion for Updated Financials to the extent there is any dispute.
`
`Bright Data further anticipates updating its damages expert’s calculations regarding
`
`the same.
`
`Bright Data’s Scheduling Proposal and Position in Tefincom Action: The Court’s No-
`
`vember 11, 2021 Order found “that a continuance is appropriate in light of the Jury Verdict in the
`
`Teso case and the parties’ ongoing mediation efforts.” ECF 181 at 1. Bright Data engaged in
`
`mediation in good faith, but the mediation concluded without any resolution with the mediator
`
`reporting “The mediation session ended in an impasse. No further follow up is anticipated.” Tefin-
`
`com Action, Dkt. 214 at 1. Consequently, Bright Data requests that the stay be lifted and the Court
`
`grant Bright Data’s proposed schedule to proceed with resolution of the above disputes and trial.
`
`- 3 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`3 of 11
`
`

`

`Tefincom Action, Dkt. 205. Understanding that both the Tefincom and Code200 Actions are in
`
`the pretrial phase, Bright Data proposes that the Court schedule the Tefincom trial first, because
`
`the Tefincom Action involves significantly higher damages and resolution of that case may reduce
`
`issues in the Code200 Action.
`
`Bright Data’s
`
`Event
`
`Proposed Dates
`
`September 8, 2022 Parties file the Joint Stipulation and Motion for Entry of Order Address-
`
`ing Claims and Parties;
`
`Defendant files its Opposition to Bright Data’s Motions in Limine; and
`
`Defendant files its Reply in Support of Defendants’ Motions in Limine.
`
`September 15,
`
`Parties Exchange Updated Exhibit Lists, Witness Lists and Deposition
`
`2022
`
`Designations;
`
`Bright Data files it Reply in Support of its Motion to Exclude Dr. Aviel
`
`Rubin;
`
`Bright Data files it Reply in Support of Its Motions in Limine;
`
`Bright Data files its Second Amended Complaint; and
`
`Defendant produces updated financials.
`
`September 22,
`
`Parties File Joint Pretrial Order, Joint Proposed Jury Instructions, and
`
`2022
`
`Joint Proposed Verdict Form;
`
`Parties file Surreplies to Motions in Limine; and
`
`Defendant files its Surreply to the Motion to Exclude Dr. Aviel Rubin;
`
`Bright Data files its Motion for Updated Financials
`
`- 4 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`4 of 11
`
`

`

`September 29,
`
`Tefincom Files Answer to Second Amended Complaint
`
`2022
`
`October 2022
`
`Pretrial Conference
`
`November 2022 –
`
`Jury Selection and Trial
`
`December 2022
`
`Having reached an impasse in the mediation, Defendant has no basis to request a continued
`
`stay based on a speculative appeal of the Teso Action or post-grant proceedings before the PTAB.
`
`The November 5, 2021 jury verdict upheld the validity of all asserted claims of the ’319, ’510, and
`
`’614 Patents. Despite the nine month delay since the jury verdict, defendants in the Teso Action
`
`have filed no motions challenging the jury finding of validity and Tefincom has no basis for as-
`
`serting that this Court or the Federal Circuit will simplify any issues by overturning the jury ver-
`
`dict. Further, Defendant’s requested administrative closure of the matter would clearly prejudice
`
`Bright Data as it would stay the case indefinitely. In addition, such an indefinite stay is unwar-
`
`ranted given the late stage of the litigation as both parties were preparing for the November 29,
`
`2021 pretrial conference when the conference and trial were continued to accommodate mediation.
`
`The IPRs and EPRs also do not warrant a stay under the factors described in NFC Techs.
`
`LLC v. HTC Am., Inc., Case No. 2:13-cv-1058-WCB, 2015 U.S. Dist. LEXIS 29573, at *5 (E.D.
`
`Tex. Mar. 11, 2015) (Bryson, J.): (1) Bright Data will be prejudiced, (2) the litigation is in the
`
`advanced pre-trial phase, and (3) a stay will not likely simplify issues for the Court. None of the
`
`IPRs against the any Bright Data patents have resulted in a final written decision invalidating any
`
`of the patent claims or addressing any of the claim construction issues, and the earliest final written
`
`decision would not be expected before May 2023. Furthermore, the reexaminations (EPRs) of the
`
`- 5 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`5 of 11
`
`

`

`’511 and ’614 Patents referenced by Defendant below are each subject to a pending petition to stay
`
`based on the copending IPRs handling the same claim construction issues.
`
` With regard to scheduling, Defendant has had more than nine months to prepare its re-
`
`sponses to the Bright Data’s Motions in Limine and its own Replies to Bright Data’s Oppositions
`
`to Tefincom’s Motions in Limine, which Bright Data filed back in November 2021. With regard
`
`to updated financials, Defendant also has an obligation to update its own financials which are
`
`particularly dated given the nine month delay. Bright Data’s damages expert identified the Tefin-
`
`com financials that he relied upon and there should be no issue for Tefincom to produce the current
`
`data.
`
`Defendant’s Scheduling Proposal and Position in Tefincom Action: Defendant pro-
`
`poses that the Court administratively close this matter pending the resolution of the Teso case by
`
`the Court and, should either party appeal, the Federal Circuit. The Tefincom matter involves the
`
`same three patents as Teso, as well as one patent from Code200. Not only do the patents overlap,
`
`the parties jointly moved, and the Court accepted the parties’ request “[t]o find that the ultimate
`
`claim constructions adopted by the Court in Teso and Code200 shall apply as if ordered by the
`
`Court in this case” because of the similarity in positions. ECF Nos. 62, 63. Thus, resolution of
`
`the Teso litigation will provide further guidance in this matter. The efficiencies gained by waiting
`
`for resolution of the Teso matter would conserve judicial resources because substantial work re-
`
`mains for both the Court and the parties to prepare for trial. Five Daubert motions, four motions
`
`for summary judgment, and numerous motions in limine and evidentiary objections remain pend-
`
`ing. The parties also have not completed briefing on motions in limine or submitted the pretrial
`
`order.
`
`- 6 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`6 of 11
`
`

`

`Further, the PTAB has issued four institution decisions granting institution of two separate
`
`IPRs challenging all asserted claims of the asserted ’319 Patent and another two separate IPRs
`
`challenging all asserted claims of the asserted ’510 Patent. In each decision, the PTAB rejected
`
`Bright Data’s assertion that the Court’s constructions of “client device” and “server” are wrong
`
`and, instead, held: “We credit the district court’s interpretation of the claim terms” “client device”
`
`and “first/second server.” See, e.g., IPR2021-01493, Paper 11 at 22. Additionally, all asserted
`
`claims of the asserted ’511 and ’614 Patents stand rejected in final office actions in ex parte reex-
`
`aminations, where the examiner has likewise rejected Plaintiff’s arguments that the Court’s claim
`
`constructions of “client device” and “server are wrong.” See, e.g., Final Office Action in Reex-
`
`amination No. 90/014,624 at 70 (holding, contrary to Plaintiff’s arguments and as the Court held,
`
`a “computer can be both a client and a server depending on what role it is playing at a particular
`
`time”). Continued progress of these patent office proceedings may further resolve or simplify this
`
`matter. Accordingly, administratively closing this matter would conserve judicial resources.
`
`Should the Court decline to administratively close this matter, Bright Data’s scheduling
`
`proposal is inappropriate. First, Bright Data has no justification for proposing trial in Tefincom
`
`proceed before trial in Code200 despite the fact that Code200 has a lower case number. Second,
`
`Bright Data’s proposal that Defendant be required in four business days to make multiple substan-
`
`tive filings addressing issues that have been dormant for almost a year is not necessary. Third,
`
`Bright Data’s proposal that “Defendant produces updated financials” in two weeks is not practical.
`
`Defendant will, of course, work on good faith to update discovery as necessary. But Bright Data
`
`has yet to even identify what updated information it requests. Defendant cannot be expected to
`
`estimate the time to collect, let alone produce, information that has yet to be identified. The com-
`
`- 7 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`7 of 11
`
`

`

`pressed timing of Bright Data’s proposal demonstrates that, even if the Court agreed that the Tefin-
`
`com case should move forward now, Bright Data’s October pretrial conference request is not prac-
`
`tical.
`
`
`
`
`
`
`
`Dated: August 31, 2022
`
`Respectfully submitted,
`
`/s/ Ronald Wielkopolski
`J. MARK MANN
` Texas State Bar No. 12926150
`mark@themannfirm.com
`G. BLAKE THOMPSON
` Texas State Bar No. 24042033
`blake@themannfirm.com
`MANN | TINDEL | THOMPSON
`300 West Main Street
`Henderson, Texas 75652
`Telephone: (903) 657-8540
`Telecopier: (903) 657-6003
`
`KORULA T. CHERIAN
` sunnyc@cherianllp.com
`ROBERT HARKINS
`bobh@cherianllp.com
`CHERIAN LLP
`1936 University Avenue, Suite 350
`Berkeley, California 94704
`Telephone: (510) 944-0192
`
`THOMAS DUNHAM
` tomd@cherianllp.com
`RONALD WIELKOPOLSKI
` ronw@cherianllp.com
`CHERIAN LLP
`1901 L Street, NW, Suite 700
`Washington, DC 20036
`Telephone: (202) 838-1560
`
`S. CALVIN CAPSHAW
`
`- 8 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`8 of 11
`
`

`

` Texas State Bar No. 03783900
`ccapshaw@capshawlaw.com
`ELIZABETH L. DERIEUX
` Texas State Bar No. 05770585
`ederieux@capshawlaw.com
`CAPSHAW DERIEUX, LLP
`114 E. Commerce Avenue
`Gladewater, Texas 75647
`Telephone: (903) 845-5770
`
`Counsel for Bright Data Ltd.
`
`
`
`- 9 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`9 of 11
`
`

`

`Dated: August 31, 2022
`
`Respectfully submitted,
`
`BRETT C. GOVETT
` Texas State Bar No. 08235900
` brett.govett@nortonrosefulbright.com
`NORTON ROSE FULBRIGHT US LLP
`2200 Ross Avenue, Suite 3600
`Dallas, Texas 75201
`Telephone: (214) 855-8000
`Telecopier: (214) 855-8200
`
`DANIEL S. LEVENTHAL
` Texas State Bar No. 24050923
` daniel.leventhal@nortonrosefulbright.com
`NORTON ROSE FULBRIGHT US LLP
`1301 McKinney, Suite 5100
`Houston, Texas 77010-3095
`Telephone: (713) 651-5151
`Telecopier: (713) 651-5246
`
`/s/ Brett C. Govett
`MICHAEL C. SMITH
` Texas State Bar No. 18650410
` michael.smith@solidcounsel.com
`SCHEEF & STONE, LLP
`113 East Austin Street
`Marshall, Texas 75670
`Telephone: (903) 938-8900
`Telecopier: (972) 767-4620
`
`STEVEN CALLAHAN
` Texas State Bar No. 24053122
` scallahan@ccrglaw.com
`CRAIG TOLLIVER
` Texas State Bar No. 24028049
` ctolliver@ccrglaw.com
`GEORGE T. “JORDE” SCOTT
` Texas State Bar No. 24061276
` jscott@ccrglaw.com
`MITCHELL SIBLEY
` Texas State Bar No. 24073097
` msibley@ccrglaw.com
`JOHN HEUTON
` Admitted Pro Hac Vice
` jheuton@ccrglaw.com
`CHARHON CALLAHAN
`ROBSON & GARZA, PLLC
`3333 Lee Parkway, Suite 460
`Dallas, Texas 75219
`Telephone: (214) 521-6400
`Telecopier: (214) 764-8392
`
`Counsel for Defendants Tefincom, S.A.
`
`
`
`
`
`- 10 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`10 of 11
`
`

`

`CERTIFICATE OF SERVICE
`
`I hereby certify that all counsel of record who are deemed to have consented to electronic
`
`service are being served this 31st day of August, 2022, with a copy of this document via electronic
`
`mail.
`
`/s/ Ronald Wielkopolski
`
`
`
`- 11 -
`
`Major Data, UAB v. Bright Data Ltd.
`IPR2022-00915, EX. 2028
`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