throbber
Case 2:19-cv-00395-JRG Document 516 Filed 11/05/21 Page 1 of 8 PageID #: 26262
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`§ §§§§
`
`§§§
`
`BRIGHT DATA LTD.,
`
`Plaintiff,
`
`v.
`
`TESO LT, UAB, METACLUSTER LT,
`UAB, OXYSALES, UAB,
`
`Defendants.
`
` CIVIL ACTION NO. 2:19-CV-00395-JRG
`
`JURY VERDICT FORM
`
`In answering the following questions and completing this Verdict Form, you
`
`are to follow all the instructions I have given you in the Court s Final July
`
`Instructions. Your answers to each question must be unanimous. Some of the
`
`questions contain legal terms that are defined and explained in detail in the Final
`
`Juiy Instructions. You should refer to and consider the Final Jury Instructions as you
`
`answer the questions in this Verdict Form.
`
`Code200, UAB, et al. v. Bright Data Ltd.
`Code200's Exhibit 1023
`Page 1 of 8
`
`

`

`Case 2:19-cv-00395-JRG Document 516 Filed 11/05/21 Page 2 of 8 PageID #: 26263
`
`As used herein, the following terms have the following meanings:
`
`• Bright Data refers to Plaintiff Bright Data, Ltd. (formerly known as
`
`Luminati Networks Ltd.)
`
`• Oxylabs refers collectively to Defendants Teso LT, UAB, Oxysales,
`
`UAB, and Metacluster LT, UAB.
`
`® The “ 319 Patent” refers to U.S. Patent No. 10,257,319.
`
`• The “ 510 Patent refers to U.S. Patent No. 10,484,510.
`
`• The “’614 Patent refers to U.S. Patent No. 10,469,614.
`
`• “Asserted Patents refers collectively to the ’319 Patent, the ’510
`
`Patent, and the ’614 Patent.
`
`• The Asserted Claims refers collectively to:
`
`o Claims 1 and 26 of the ’319 Patent;
`
`o Claims 1 and 22 of the ’510 Patent; and
`
`o Claims 1, 11, 16, and 20 of the ’614 Patent.
`
`2
`
`Code200, UAB, et al. v. Bright Data Ltd.
`Code200's Exhibit 1023
`Page 2 of 8
`
`

`

`Case 2:19-cv-00395-JRG Document 516 Filed 11/05/21 Page 3 of 8 PageID #: 26264
`
`IT IS VERY IMPORTANT THAT YOU FOLLOW THE
`INSTRUCTIONS PROVIDED IN THIS VERDICT FORM.
`
`READ THEM CAREFULLY AND
`ENSURE YOUR VERDICT COMPLIES WITH THEM.
`
`3
`
`Code200, UAB, et al. v. Bright Data Ltd.
`Code200's Exhibit 1023
`Page 3 of 8
`
`

`

`Case 2:19-cv-00395-JRG Document 516 Filed 11/05/21 Page 4 of 8 PageID #: 26265
`
`QUESTION NO. 1
`
`Did Bright Data prove by a preponderance of the evidence that Oxylabs infringed
`
`ANY of the Asserted Claims?
`
`Yes: No:
`
`4
`
`Code200, UAB, et al. v. Bright Data Ltd.
`Code200's Exhibit 1023
`Page 4 of 8
`
`

`

`Case 2:19-cv-00395-JRG Document 516 Filed 11/05/21 Page 5 of 8 PageID #: 26266
`
`QUESTION NO. 2
`
`Did Oxylabs prove by clear and convincing evidence that any of the following
`
`Asserted Claims are invalid?
`
`Claim 1 of the 319 Patent Yes: No: V
`
`Claim 26 of the 319 Patent Yes: No:
`
`Claim 1 of the 510 Patent Yes: No: \/
`
`Claim 22 of the ’510 Patent Yes: No: \/
`
`Claim 1 of the ’614 Patent Yes: No: \/
`
`Claim 11 of the ’614 Patent Yes: No:
`
`Claim 16 of the ’614 Patent Yes: No: i
`
`Claim 20 of the ’614 Patent Yes: No:
`
`5
`
`Code200, UAB, et al. v. Bright Data Ltd.
`Code200's Exhibit 1023
`Page 5 of 8
`
`

`

`Case 2:19-cv-00395-JRG Document 516 Filed 11/05/21 Page 6 of 8 PageID #: 26267
`
`If you answered No to Question No. 1, OR YES to ALL Asserted Claims in
`Question No. 2, then DO NOT answer Question No. 3.
`
`Answer Question No. 3 ONLY as to any Asserted Claim that you have found
`BOTH to be infringed AND not invalid.
`
`QUESTION NO. 3
`
`Did Bright Data prove by a preponderance of the evidence that Oxylabs willfully
`
`infringed ANY of the Asserted Claims that you found were infringed?
`
`Yes: No:
`
`6
`
`Code200, UAB, et al. v. Bright Data Ltd.
`Code200's Exhibit 1023
`Page 6 of 8
`
`

`

`Case 2:19-cv-00395-JRG Document 516 Filed 11/05/21 Page 7 of 8 PageID #: 26268
`
`If you answered No to Question No. 1, OR YES to ALL Asserted Claims in
`Question No. 2, then DO NOT answer Question No. 4.
`
`Answer Question No. 4 ONLY as to an Asserted Claim that you have found
`BOTH to be infringed AND not invalid.
`
`QUESTION NO. 4
`
`What sum of money, if any, has Bright Data proven by a preponderance of the
`
`evidence that it is entitled to receive from Oxylabs as lost profits?
`
`Answer in United States Dollars and Cents, if any:
`
`7
`
`Code200, UAB, et al. v. Bright Data Ltd.
`Code200's Exhibit 1023
`Page 7 of 8
`
`

`

`Case 2:19-cv-00395-JRG Document 516 Filed 11/05/21 Page 8 of 8 PageID #: 26269
`
`FINAL PAGE OF JURY VERDICT FORM
`
`
`
`
`
`You have now reached the end of the Verdict Form and should review it to
`
`
`
`
`
`
`
`ensure it accurately reflects your unanimous determinations. The Jury Foreperson
`
`
`
`
`
`
`
`
`
`should then sign and date the Verdict From in the space below. Once this is done,
`
`
`
`
`
`notify the Court Security Officer that you have reached a verdict. The Jury
`
`
`
`
`
`
`
`
`
`Foreperson should keep the Verdict Form and bring it when the jury is brought back
`
`
`
`
`
`
`
`into the courtroom.
`
`
`
`
`
`Signed this 511). day of November, 2021.
`
`________________________
`Jury Foreperson
`
`8
`
`Code200, UAB, et al. v. Bright Data Ltd.
`Code200's Exhibit 1023
`Page 8 of 8
`
`

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