throbber
Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 1 of 12 PageID #: 32406
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`
`
`Civil Action No.
`2:19-cv-00395-JRG
`
`
`
`
`
`
`
`Bright Data Ltd.,
`
` Plaintiff,
`
` v.
`
`Teso LT, UAB, Oxysales, UAB, and
`Metacluster LT, UAB,
`
` Defendants.
`
`
`
`JOINT MOTION FOR ENTRY OF
`POST-VERDICT SCHEDULING ORDER
`
`Plaintiff Bright Data Ltd. (“Plaintiff”) and Defendants Teso LT, UAB, Oxysales, UAB,
`
`and Metacluster LT, UAB (collectively, “Defendants”) hereby move the Court for entry of a pro-
`
`posed post-verdict Scheduling Order.
`
`I.
`
`INTRODUCTION
`
`Pursuant to the Court’s September 21, 2022 Order (ECF No. 601), the parties met and
`
`conferred regarding the post-verdict schedule and jointly submit this motion for a proposed post-
`
`verdict scheduling order.
`
`
`
`
`
`
`
`
`
`
`
`
`
`1
`
`Data Co Exhibit 1105
`Data Co v. Bright Data
`IPR2022-00135
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 2 of 12 PageID #: 32407
`
`Date Provided
`by the Court
`
`Plaintiff’s
`Proposed Date
`
`Defendants’ Pro-
`posed Date
`
`Event
`
`N/A; if the Court enter-
`tains the motion, 30
`days for response, 14
`days for reply and 14
`days for sur-reply
`
`Bright Data files Motion
`for Compensation for On-
`going Infringement
`
`N/A (Defendants re-
`spectfully suggest that
`the Court deny this
`motion)
`
`28 days after any entry
`of Judgment as pro-
`vided for in Federal
`Rules. See Fed. R. Civ.
`P 50(b); Fed. R. Civ. P.
`59(b).
`
`N/A; the Court will en-
`ter any judgment on
`the Court’s own sched-
`ule, not Bright Data’s
`schedule
`
`Subject to Court Ruling on
`Pending Motion for Post-
`Verdict Discovery (ECF
`No. 607), Defendants pro-
`duce updated financials
`
`Parties file Rule 50(b) and
`59 Motion for New Trial,
`with responses, replies and
`surreplies due according to
`Local Rules
`
`Entry of Judgment
`
`Defendants file Response
`to Motion for Updated Fi-
`nancials (ECF No. 607)
`
`Defendants file Response
`to Bright Data’s Motion for
`Enhanced Damages and
`Exceptional Case (ECF No.
`541), with replies and sur-
`replies due according to
`Local Rules
`
`TBD
`
`TBD
`
`14 Days After Ser-
`vice of Requested
`Financials per Dis-
`covery Motion (ECF
`607), including ex-
`pert
`declaration,
`with response, re-
`plies, and surreplies
`due according to Lo-
`cal Rules
`
`14 Days after Court
`Order
`addressing
`Bright Data Post-
`Verdict Discovery
`Motion (ECF 607)
`
`TBD
`
`October 21, 2022
`
`TBD
`
`October 19, 2022
`
`TBD
`
`October 10, 2022
`
`October 10, 2022
`
`September 28,
`2022
`
`Already set by Court Already set by Court
`
`2
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 3 of 12 PageID #: 32408
`
`TBD
`
`
`
`N/A; there is no ba-
`sis
`for any such
`deadline limiting the
`potential
`enforce-
`ment of any judg-
`ment
`
`30 days after the final
`disposition of all post-
`trial motions in this
`Court
`
`Any potential enforcement
`of any judgment
`
`II.
`
`THE PARTIES’ POSITIONS ON DISPUTED ISSUES
`
`The parties’ positions regarding their proposals on disputed issues are set forth as follows:
`
`A. Bright Data’s Position:
`
`Bright Data requests an expedited schedule to bring this action to a judgment, and if nec-
`
`essary, any appeal. Within days of the November 5, 2021 jury verdict, Defendants announced on
`
`their website that “Oxylabs is legally entitled to continue providing the accused services” and
`
`“Oxylabs continues to offer its services in an uninterrupted manner.” ECF 541-26 at 5 (https://ox-
`
`ylabs.io/legal-timeline). Despite openly continuing their willful infringement, Defendants have
`
`refused to produce updated and supplemental financials to allow Bright Data to calculate compen-
`
`sation for Defendants’ ongoing infringement, including supplemental damages following the jury
`
`verdict. By forcing Bright Data to file a motion to compel narrowly tailored post-verdict discovery
`
`(ECF 607), Defendants seek to further hinder and delay the filing of Bright Data’s anticipated
`
`motion for compensation for ongoing infringement in the hopes of further delaying the entry of
`
`judgment and any subsequent appeal.
`
`Disregarding the jury verdict that found willful infringement and awarded Bright Data its
`
`lost profits, Defendants have taken the position that they can freely infringe Bright Data’s patents
`
`without any compensation for their ongoing infringement. Such position is meritless. 35 U.S.C.
`
`§ 284 provides that “upon finding for the claimant the court shall award the claimant damages
`
`adequate to compensate for the infringement, but in no event less than a reasonable royalty for the
`
`3
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 4 of 12 PageID #: 32409
`
`use made by the infringer…” and “[w]hen the damages are not found by a jury, the court shall
`
`assess them.”
`
`As briefed in Bright Data’s motion for discovery (ECF 607) and Defendants are already
`
`aware, Promega and Whitserve are inapposite. That case was about past damages – not compen-
`
`sation for post-trial ongoing infringement. Promega Corp. v. Life Techs. Corp, 875 F.3d 651, *666
`
`(Fed. Cir. 2017). The Federal Circuit held that Promega was not entitled to any past damages,
`
`because Promega expressly waived any reasonable royalty and “there was no evidence to support
`
`a lost profits damages calculation under the narrow damages theory Promega crafted over the
`
`course of litigation.” Id. at *664; see also 660 and 662. In contrast, Bright Data is seeking com-
`
`pensation for Defendants’ continuing post-trial infringement, which is equitable relief not subject
`
`to a jury trial. Similarly, Defendants imply that the Federal Circuit case of Whitserve, LLC v.
`
`Computer Packages, Inc. supports waiver of an ongoing royalty, but this is not true. As explained
`
`in Erfindergemeinschaft, the Federal Circuit in Whitserve “held that the district court abused its
`
`discretion by denying the request for prospective relief (i.e., an injunction or an ongoing royalty),
`
`and forcing the plaintiff to ‘resort to serial litigation’ to obtain compensation for the post-verdict
`
`period.” Erfindergemeinschaft UroPep GbR v. Eli Lilly & Co., No. 2:15-CV-1202-WCB, 2017
`
`U.S. Dist. LEXIS 111425, at *8 (E.D. Tex. July 18, 2017). Any delay in calculating compensation
`
`for Defendants’ ongoing infringement has been caused solely by Defendants’ own obstruction and
`
`refusal to produce updated financials (documents which it previously produced in discovery). De-
`
`fendants have no basis for asking the Court to allow Defendants to continue their infringement
`
`indefinitely without compensation to Bright Data.
`
`4
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 5 of 12 PageID #: 32410
`
`As addressed in the August 31, 2022 Joint Status Report (ECF 594), Defendants have no
`
`basis to further delay briefing. The jury reached a verdict eleven months ago.1 Instead of focusing
`
`on settlement, Defendants have used the subsequent eleven months to (1) file 9 IPR/PGR petitions
`
`against Bright Data patents, including 4 against the ’319 and ’510 Patents found not invalid in the
`
`November 5, 2021 jury verdict, and (2) file a new patent infringement complaint against Bright
`
`Data entitled Metacluster LT, UAB v. Bright Data Ltd., Case No. 2:22-cv-11.2 Defendants have
`
`had eleven months to prepare their much anticipated and much touted JMOL and new trial mo-
`
`tions, but request that they not be due until 28 days after entry of Judgment. Defendants do not
`
`need to wait for entry of the judgment to file their Rule 50(b) and 59 Motions and have had almost
`
`a year to prepare.
`
`Accordingly, Bright Data respectfully requests expedited resolution of Bright Data’s pend-
`
`ing discovery motion (ECF No. 607) and entry of judgment in this matter along with the other
`
`deadlines proposed above. With regard Defendants’ request that any potential enforcement of the
`
`judgment be filed within 30 days of final resolution, Bright Data is aware of no basis for such a
`
`requirement. Defendants cannot dictate how long a Court’s judgment may be enforced and such
`
`request should be denied.
`
`B. Defendants’ Position:
`
`
`
`1 Defendants originally moved for the stay on December 1, 2021 arguing that “Bright Data
`will not suffer any prejudice by a brief stay of several weeks, as the mediation will occur early in
`the New Year and briefing can continue on Bright Data’s motions in the New Year if the mediation
`is not successful.” Teso Action, ECF No. 534 at 2.
`
`2 Oxylabs widely publicized its new complaint including through a press release and its own
`webpage
`touting
`its
`litigation against Bright Data. See, e.g., https://markets.busi-
`nessinsider.com/news/stocks/oxylabs-sues-bright-data-in-patent-infringement-case-1031088447,
`https://www.yahoo.com/now/oxylabs-sues-bright-data-patent-144400197.html and https://ox-
`ylabs.io/legal-timeline.
`
`5
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 6 of 12 PageID #: 32411
`
`(cid:120) “Motion for Compensation for Ongoing Infringement”: The Court should not allow
`
`Bright Data to file such motion. Defendants will set forth their position in more detail
`
`in Defendants’ Response to Bright Data’s “Motion for Updated Financials,” which De-
`
`fendants will file on October 10, 2022. Among other things, BD waived its right to seek
`
`such “compensation” by failing to present a reasonable-royalty damages theory at trial
`
`and having JMOL granted against it (without any opposition from BD) by the Court on
`
`reasonable-royalty damages (Trial Tr. Vol. 4, 287:18-288:5). See, e.g., Promega Corp.
`
`v. Life Techs. Corp., 875 F.3d 651, 660, 662, 663, 665, 666 (Fed. Cir. 2017) (finding
`
`waiver of reasonable-royalty damages where plaintiff only sought damages in the form
`
`of lost profits—“a district court does not abuse its discretion by declining to give that
`
`plaintiff multiple chances to correct deficiencies in its arguments or the record”; “a
`
`patent owner may waive its right to a damages award when it deliberately abandons
`
`valid theories of recovery . . .”). The Court should not be burdened with Bright Data’s
`
`attempt to redo its unreliable reasonable-royalty theory for the third time. Additionally,
`
`the Court need not award any such compensation under relevant case law and, further,
`
`the Court need not take this issue up now pending rulings on Defendants’ JMOL/new
`
`trial motions or any appeal (or severance) of the case. See, e.g., Whitserve, LLC v.
`
`Computer Packages, Inc., 694 F.3d 10, 35 (Fed. Cir. 2012) (noting that, with respect
`
`to “ongoing infringement,” the court “can exercise its discretion to conclude that no
`
`forward-looking relief is appropriate in the circumstances”); Cave Consulting Group,
`
`LLC v. Optuminsight, Inc., 11-CV-00469, 2016 WL 4658979, at *24 (N.D. Cal. Sept.
`
`7, 2016) (“Given the number and complexity of the issues in this case that remain un-
`
`6
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 7 of 12 PageID #: 32412
`
`resolved, the Court finds that it would be appropriate to delay the consideration of ev-
`
`idence and calculating the ongoing royalty rate until after the completion of the appeals
`
`in this case.”); Golden Hour Data Sys., Inc. v. emsCharts, Inc., 06-CV-381, 2014 WL
`
`8708239, at *14 (E.D. Tex. Mar. 31, 2014) (“While the Court recognizes the efficiency
`
`of determining post-verdict damages in the originally-filed case, without the showing
`
`of an appropriate royalty base supported by competent evidence, any damages award
`
`would be speculative. As such, the Court deems it proper and prudent to sever the de-
`
`termination of the royalty base for post-verdict damages into a new cause to facilitate
`
`the entry of judgment in this case.”) (Gilstrap, C.J.). But, if the Court allows Bright
`
`Data to file this motion, it should allow 30 days for Defendants to respond to the motion
`
`(as Bright Data will presumably have disclosed a brand-new reasonable royalty theory
`
`from its expert Dr. Becker, which Defendants will need time to analyze and rebut with
`
`their own expert (it is also unclear whether the Court would allow expert depositions)),
`
`with 14 days for the parties to file replies and surreplies.
`
`(cid:120) “Defendants produce updated financials”: As will be explained in Defendants’ Re-
`
`sponse to Bright Data’s “Motion for Updated Financials,” which will be filed on Octo-
`
`ber 10, 2022, the Court should not require Defendants to produce “updated financials.”
`
`(cid:120) “Entry of Judgment”: Bright Data seeks to require the Court to enter judgment on
`
`October 19, 2022. Defendants defer to the Court on this issue—i.e., Defendants’ posi-
`
`tion is that the Court enters judgment if and when it believes judgment is appropriate.
`
`For example, the Court may wish to resolve Bright Data’s pending Motion for En-
`
`hanced Damages and Exceptional Case (ECF No. 541) prior to entering any judgment.
`
`That motion will not be fully briefed until October 12, 2022 (see ECF No. 601, Order
`
`7
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 8 of 12 PageID #: 32413
`
`Lifting Stay (setting briefing schedule on motion)). Further, Defendants respectfully
`
`request that the Court stay any potential enforcement of any judgment until thirty days
`
`after the final disposition of all post-trial motions in this Court. See L.R. 62(a) (allowing
`
`Court to stay execution of judgment).
`
`(cid:120) “Rule 50(b) and 59 Motion for New Trial”: Bright Data proposes that these motions
`
`be due two days after the Court enters judgment under Bright Data’s proposal (i.e.,
`
`Bright Data proposes that the Court enter judgment on October 19, 2022 and that Rule
`
`50(b)/Rule 59 motions be due on October 21, 2022). Two days for such motions is
`
`unreasonable. Instead, Defendants respectfully submit that the briefing on Rule
`
`50(b)/Rule 59 motions follow the briefing schedule set forth in the Federal Rules—i.e.,
`
`that these motions be due 28 days after entry of any Judgment. See Fed. R. Civ. P 50(b);
`
`Fed. R. Civ. P. 59(b).3
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`3 BD suggests that Defendants did not “focus[] on settlement[.]” See p. 3-4. This suggestion
`is meritless. Defendants have previously detailed their settlement efforts and offered to submit
`their own and the parties’ settlement communications and offers to the Court on the Court’s request
`or if BD consents. ECF No. 594; Metacluster v. Bright Data, Case 2:22-cv-00011-JRG-RSP (E.D.
`Tex.), ECF No. 49 at 12-13. BD refuses to consent, which speaks volumes about the lack of merit
`of its allegation. Metacluster, ECF No. 57 at 5 n.7.
`
`8
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 9 of 12 PageID #: 32414
`
`
`
`Dated: October 5, 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 94702
`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
` Texas State Bar No. 03783900
` ccapshaw@capshawlaw.com
`ELIZABETH L. DERIEUX
`
`9
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 10 of 12 PageID #: 32415
`
` 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.
`
`
`
`
`
`
`
`10
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 11 of 12 PageID #: 32416
`
`Dated: October 5, 2022
`
`
`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
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`/s/ Steven Callahan .
`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 Teso LT, UAB,
`Oxysales, UAB, and Metacluster LT, UAB
`
`
`
`
`
`11
`
`
`

`

`Case 2:19-cv-00395-JRG Document 613 Filed 10/05/22 Page 12 of 12 PageID #: 32417
`
`CERTIFICATE OF SERVICE
`
`
`
`I hereby certify that all counsel of record who are deemed to have consented to electronic
`
`service are being served this 5th day of October 2022, with a copy of this document via CM/ECF.
`
`
`
`
`
`/s/ Ronald Wielkopolski
`
`
`
`
`
`CERTIFICATE OF CONFERENCE
`
`The undersigned hereby certifies that the counsels for the parties have complied with Local
`
`Rule CV-7(h). A telephonic meet and confer was held on October 5, 2022 with counsel partici-
`
`pating including Ron Wielkopolski on behalf of Plaintiff; Steven Callahan on behalf of Defend-
`
`ants. The parties partially dispute this motion.
`
`
`
`/s/ Ronald Wielkopolski
`
`
`
`
`
`12
`
`
`

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