`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`Bright Data Ltd.,
`
`Plaintiff,
`
`v.
`
`Teso LT, UAB, Oxysales, UAB and
`Metacluster LT, UAB,
`
`Defendants.
`
`Civil Action No.
`2:19-cv-00395-JRG
`
`REVISED JOINT PRETRIAL ORDER
`
`Plaintiff Bright Data Networks Ltd. (“Bright Data”), and Defendants Teso LT, UAB
`
`(“Teso”), Oxysales, UAB (“Oxysales”) and Metacluster LT, UAB (“Metacluster”) (Defendants
`
`collectively, “Oxylabs” or “Defendants”) (Bright Data and Defendants, collectively, the “Parties”)
`
`hereby submit this Amended Joint Pretrial Order pursuant to the Court’s First Amended Docket
`
`Control Order (ECF No. 379) and the Court’s Order on Pretrial Motions (ECF No. 476).
`
`A. COUNSEL FOR THE PARTIES
`
`1. ATTORNEYS FOR BRIGHT DATA
`
`S. Calvin Capshaw
`State Bar No. 03783900
`Elizabeth L. DeRieux
`State Bar No. 05770585
`Capshaw DeRieux, LLP
`114 E. Commerce Ave.
`Gladewater, TX 75647
`Telephone: 903-845-5770
`ccapshaw@capshawlaw.com
`ederieux@capshawlaw.com
`
`Korula T. Cherian
`CA Bar No.: 133967
`(Admitted to practice in E.D. Texas)
`Robert Harkins
`CA Bar No.: 179525
`(Admitted to practice in E.D. Texas)
`RuyakCherian LLP
`1936 University Ave, Ste. 350
`Berkeley, CA 94702
`Telephone: (510) 944-0190
`sunnyc@ruyakcherian.com
`
`1
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 1 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 2 of 32 PageID #: 25365
`
`
`
`
`
`
`
`
`James Mark Mann
`State Bar No. 12926150
`Gregory Blake Thompson
`State Bar No. 24042033
`Mann Tindel & Thompson
`201 E. Howard Street
`Henderson, TX 75654
`Telephone: 903-657-8540
`Mark@TheMannFirm.com
`Blake@TheMannFirm.com
`
`
`bobh@ruyakcherian.com
`
`Amadou Kilkenny Diaw
`DC Bar No.: 1006908
`(Admitted to practice in E.D. Texas)
`Ronald Wielkopolski
`DC Bar No.: 1013586
`(Admitted to practice in E.D. Texas)
`Thomas M. Dunham
`DC Bar No.: 448407
`(Admitted to practice in E.D. Texas)
`Colby Davis
`CA Bar No.: 307292
`(Admitted to practice in E.D. Texas)
`RuyakCherian LLP
`1901 L Street NW, Suite 700
`Washington, DC 20036
`Telephone: (202) 838-1560
`amadoukd@ruyakcherian.com
`ronw@ruyakcherian.com
`tomd@ruyakcherian.com
`colbyd@ruyakcherian.com
`
`2. ATTORNEYS FOR DEFENDANTS/COUNTERCLAIM-PLAINTIFFS
`
`MICHAEL C. SMITH
` Texas State Bar No. 18650410
` michael.smith@solidcounsel.com
`SIEBMAN, FORREST,
`BURG & SMITH LLP
`113 East Austin Street
`Marshall, Texas 75671
`Telephone: (903) 938-8900
`Telecopier: (972) 767-4620
`
`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
`
`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
`
`2
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 2 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 3 of 32 PageID #: 25366
`
`
`
`
`
` 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
`
`
`
`
`B. STATEMENT OF JURISDICTION
`
`
`
`This Court has subject matter jurisdiction over the action brought by Bright Data pursuant to
`
`28 U.S.C. §§ 1331 and 1338(a), because this action arises under the patent laws of the United
`
`States, including 35 U.S.C. § 1 et seq. The parties do not dispute that, with respect to Bright Data’s
`
`claims, the Court has personal jurisdiction over Bright Data, Teso, Oxysales, and Metacluster and
`
`that venue is proper in this judicial district.
`
`
`
`Oxylabs further asserts that, with respect to Oxylabs’ counterclaims, personal jurisdiction
`
`exists over Bright Data, the Court has subject-matter jurisdiction, and venue is proper.
`
`C. NATURE OF ACTION
`
`1. Bright Data’s Statement:
`
`This is a patent infringement case related to Internet Protocol (“IP”) proxy technology, and
`
`
`
`specifically residential proxy services (“Residential Proxy Services”) that use client devices as
`
`proxies in Internet communication. Plaintiff Bright Data alleges that Defendants’ Residential
`
`Proxy and Real-Time Crawler services (“Accused Instrumentalities”) infringe claims 1 and 26 of
`
`U.S. Patent No. 10,257,319 (the “’319 Patent”), claims 1 and 22 of U.S. Patent No. 10,484,510
`
`(the “’510 Patent”) and 1, 6, 11, 16, 20 and 26 of U.S. Patent No. 10,469,614 (the “’614 Patent”),
`
`collectively “Asserted Patents” and “Asserted Patent Claims” respectively). Bright Data asserts
`
`that Defendants directly or indirectly infringe the Asserted Patent Claims under 25 U.S.C. § 271(a)
`
`and/or (b) as Defendants have and continue to use, provide, sell, and offer to sell the Accused
`
`
`
`3
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 3 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 4 of 32 PageID #: 25367
`
`
`
`Instrumentalities using residential proxies (client device) located in the United States, induce their
`
`customers to infringe the same Asserted Patent Claims through the use of the Accused Instrumen-
`
`talities, induce their partners and residential proxy suppliers to infringe the Asserted Patent Claims
`
`through their support of the Accused Instrumentalities, and import into the United States software
`
`development kits (“SDKs”) used to cause client devices in the United States to serve as residential
`
`proxies in support of the Accused Instrumentalities.
`
`
`
`Defendants assert counterclaims of invalidity and non-infringement regarding the Asserted
`
`patent Claims, as well as a counterclaim of unenforceability of the ’614 Patent based on Defend-
`
`ants’ allegations of inequitable conduct. Bright Data denies these counterclaims and Defendants
`
`defenses.
`
`2. Defendants’ Statement:
`
`Bright Data accuses Oxylabs of infringing Claims 1, 6, 11, 16, 20 and 26 of the ’614 Patent;
`
`
`
`Claims 1 and 26 of the ’319 Patent; and Claims 1 and 22 of the ’510 Patent (collectively, the
`
`“Asserted Claims” and the ’614 Patent, the ’319 Patent, and the ’510 Patent, collectively, the “Pa-
`
`tents-in-Suit”).
`
`
`
`The accused products are Teso’s residential proxy service and Metacluster’s real-time
`
`crawler service when operated over Teso’s residential proxy service (collectively, the “Accused
`
`Products”). Oxylabs denies that it infringes (whether directly or indirectly, willfully or otherwise)
`
`the Patents-in-Suit and further contends that Patents-in-Suit are invalid and not patent eligible un-
`
`der 35 U.S.C. § 101. Oxylabs further asserts that the ’614 Patent is unenforceable due to inequita-
`
`ble conduct. Oxylabs further asserts that Bright Data’s claims for relief are limited by 35 U.S.C.
`
`§§ 286-287 and/or 28 U.S.C. § 1498, prosecution-history estoppel, extraterritoriality principles,
`
`and/or the disclosure-dedication doctrine.
`
`
`
`4
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 4 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 5 of 32 PageID #: 25368
`
`
`
`
`
`Oxylabs asserts declaratory judgment claims against Bright Data under the Declaratory Judg-
`
`ment Act, 28 U.S.C. §§ 2201(a) and 2202. Oxylabs seeks a declaratory judgment that the Patents-
`
`in-Suit are not infringed and invalid, and that the ’614 Patent is unenforceable due to inequitable
`
`conduct.
`
`D.
`
`CONTENTIONS OF THE PARTIES
`
`1. Plaintiff Bright Data’s contentions
`
`Infringement claims and damages:
`
`1. Bright Data contends that Defendants directly infringe the Asserted Patent Claims, literally
`
`and/or under the doctrine of equivalents, in violation of 35 U.S.C. § 271 including at least §
`
`271(a) because Defendants have used, uses, offered for sale, offers for sale, imported, imports,
`
`sells and/or has sold the Accused Instrumentalities in the United States; and § 271(b) because
`
`Defendants have and continues to actively induced their customers and residential proxy sup-
`
`pliers to infringe the Asserted Patent Claims.
`
`2. Bright Data contends that it has been damaged by the offers for sale and sales of the Accused
`
`Instrumentalities and is entitled to past damages equal to at least its lost profits and not less
`
`than a reasonable royalty under 35 U.S.C. § 284 for the time beginning on April 9, 2019 when
`
`Defendants first infringed the ’319 Patent, beginning on November 5, 2019 when Defendants
`
`first infringed the ’614 Patent, and beginning November 19, 2019 when Defendants first in-
`
`fringed the ’510 Patent.
`
`3. Bright Data further contends that it is and has been being irreparably harmed by the offers for
`
`sale and sales of the Accused Instrumentalities and that no remedy at law would suffice to
`
`compensate Bright Data for the ongoing harm to its business.
`
`
`
`5
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 5 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 6 of 32 PageID #: 25369
`
`
`
`4. Bright Data contends that Defendants’ infringement has been and continues to be willful at
`
`least since the filing of the Complaint and Bright Data is entitled to enhanced damages up to
`
`three times under 35 U.S.C. § 284.
`
`5. Bright Data further contends that Defendants’ actions related to the case including but not
`
`limited to the willful infringement warrants a finding of exceptional case under 35 U.S.C. §
`
`285 and an award of attorneys’ fees and costs and any other applicable award as a result of that
`
`finding.
`
`6. Bright Data further contends that damages are an inadequate remedy to compensate Bright
`
`Data for the ongoing harm caused by the continued offers for sale and sale of the Accused
`
`Instrumentalities, and consequently Bright Data is entitled to a permanent injunction prohibit-
`
`ing the sale of the Accused Instrumentalities.
`
`Responses to Defendants’ affirmative defenses and counterclaims:
`
`7. Bright Data contends that the Asserted Patent Claims are not invalid for any reason, including
`
`under sections 101, 102, 103, and 112 of the Patent Act and any other argument for invalidity
`
`raised by Defendants. In addition to other grounds, Bright Data contends that the Asserted
`
`Patents are not invalid under section 101 for at least the reasons found in the Court’s February
`
`16, 2021 Order (Dkt. 303) denying Oxylabs’ Rule 12(c) motion for judgment on the pleadings
`
`and those reasons stated in Bright Data’s response to Defendants’ motion for summary judg-
`
`ment of invalidity on the basis of 35 U.S.C. § 101.
`
`8. Bright Data contends that its damages are not limited by operation by any provision of law or
`
`equity asserted by Defendants.
`
`9. Bright Data contends that the Asserted Patents Claims are not unenforceable or barred for any
`
`reason, including for prosecution history estoppel, license and/ or exhaustion, or any other
`
`
`
`6
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 6 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 7 of 32 PageID #: 25370
`
`
`
`equitable or legal theory asserted by Defendants.
`
`10. Bright Data contends that it has not dedicated to the public systems, methods, and/or products
`
`in the Patents-in-Suit.
`
`11. Bright Data contends that it has not engaged in any inequitable conduct whatsoever and did
`
`not omit information material to patentability during prosecution, including as Bright Data
`
`specifically contends that the ’319 Patent application which serves as the basis for Defendants’
`
`inequitable conduct claim is duplicative of the disclosed U.S. Patent No. 8,560,604 (“’604
`
`Patent”). Further, to the extent that Defendants assert that claim 1 of the ’319 Patent is coex-
`
`tensive with dependent claim 29 of the ’433 Application, which issued as claim 1 of the ‘’614
`
`Patent, Bright Data contends that this is incorrect and that Defendants make such contention
`
`by excluding the limitations of independent claim 1 of the ’433 Application that are incorpo-
`
`rated in dependent claim 29 of the ’433 Application.
`
`12. Bright Data contends that its claims are not limited or barred by any provision of law or equity
`
`asserted by Defendants.
`
`13. Bright Data contends that Defendants are not entitled to a finding in its favor that this case is
`
`exceptional under Section 285 or to any other damages, attorneys’ fees, or costs under the
`
`Patent Act or any other law or basis in equity.
`
`14. Bright Data contends that, upon a finding of Defendants’ liability, it is entitled to a court order
`
`imposing a permanent injunction preventing Defendants’ further infringement of the Asserted
`
`Patent Claims.
`
`15. Bright Data contends that Defendants are not entitled to any relief from Bright Data.
`
`16. Bright Data contends that the Court should declare that Defendants are not entitled to any
`
`relief, whether in law or equity or otherwise, from its counterclaims against Bright Data.
`
`
`
`7
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 7 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 8 of 32 PageID #: 25371
`
`
`
`17. Bright Data contends that the Court should declare that Defendants infringe the Asserted Patent
`
`Claims.
`
`18. Bright Data contends that the Court should declare that the claims of the Asserted Patent
`
`Claims are not invalid.
`
`19. Bright Data contends that the Court should declare that the claims of the ’614 patent are not
`
`unenforceable.
`
`20. Bright Data contends that Defendants cannot establish that this an “exceptional case” in De-
`
`fendants’ favor.
`
`21. Bright Data contends that Defendants are not entitled to recover their attorney’s fees.
`
`22. Bright Data contends that Defendants are not entitled to recover their costs.
`
`23. Bright Data contends that the Court should award pre-judgment and post-judgment interest on
`
`the damages awarded to Bright Data at the highest rate allowed by law.
`
`2. Defendants’ contentions
`
`
`1. Oxylabs contends that it has not infringed, whether directly or indirectly, literally or under the
`
`doctrine of equivalent, willfully or otherwise, the Patents-in-Suit. For example, Oxylabs con-
`
`tends that it does not infringe the Patents-in-Suit or Asserted Claims under any section of the
`
`Patent Act, including without limitation 35 U.S.C. §§ 271(a) and (b). Oxylabs has not in any
`
`manner, whether directly or indirectly, literally or under the doctrine of equivalents, infringed
`
`or induced the infringement of any valid and enforceable claim of the Patents-in-Suit, and is
`
`not liable for infringement thereof. Oxylabs has also not imported into the United States or
`
`offered to sell, sold, or used within the United States a product which is made by a process
`
`patented in the United States. Oxylabs has filed a Motion for Summary Judgment of Non-
`
`Infringement. See ECF No. 276.
`
`
`
`8
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 8 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 9 of 32 PageID #: 25372
`
`
`
`2. Oxylabs contends that the Patents-in-Suit are invalid and/or void for failure to meet the condi-
`
`tions for patentability specified by 35 U.S.C. §§ 101 et seq., including but not limited to 35
`
`U.S.C. §§ 101, 102, 103, 112 and/or 282 and/or the Rules and Regulations of the United States
`
`Patent & Trademark Office. Oxylabs has filed a Motion for Summary Judgment of Invalidity.
`
`See ECF No. 277. For example:
`
`a. Oxylabs specifically contends that the Patents-in-Suit are invalid as anticipated:
`
`i. Oxylabs asserts that the ’319 and ’510 Patents are anticipated by Crowds,1
`
`MorphMix,2 and/or Border.3
`
`ii. Oxylabs asserts that the ’614 Patent is anticipated by Mithyantha4 and/or
`
`MorphMix.
`
`b. Oxylabs specifically contends that the Patents-in-Suit are invalid as obvious:
`
`i. Oxylabs asserts that the ’319 and ’510 Patents, to the extent not anticipated
`
`by Crowds, are rendered obvious based on Crowds itself and/or a combina-
`
`tion of Crowds with the general knowledge of a POSA and the RFC 2616
`
`HTTP protocol specification (which specification also further evidences the
`
`general knowledge of a POSA) and/or with the disclosure of Border and/or
`
`with the disclosure of the TCP/IP specifications (RFC 793 and RFC 1180)
`
`
`1 Crowds: Anonymity for Web Transactions (“Crowds”), Michael K. Reiter of Bell Laboratories
`and Aviel D. Rubin of AT&T Labs, ACM Transactions on Information and System Security, Vol.
`1, No. 1, November 1998, Pages 66-92.
`2 MorphMix – A Peer-to-Peer-based System for Anonymous Internet Access (“MorphMix”), Doc-
`toral Thesis authored by Marc Rennhard, of the Swiss Federal Institute of Technology (ETH Zur-
`ich), Computer Engineering and Networks Laboratory; Zurich, Switzerland (2004).
`3 United States Patent 6,795,848 (“Border”) issued to Border et al. on Sep. 21, 2004. Border issued
`from United States Patent Application 09/708,134, filed on Nov. 8, 2000.
`4 United States Patent 8,972,602 (“Mithyantha”) issued to Mithyantha on March 3, 2015. Mith-
`yantha issued from U.S. Patent Application 13/524,799, which was filed June 15, 2012.
`
`
`
`9
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 9 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 10 of 32 PageID #: 25373
`
`
`
`
`
`and/or for the reasons explained in Appendices A and E to Dr. Freedman’s
`
`December 18, 2020 Expert Report Regarding Invalidity.
`
`ii. Oxylabs asserts that the ’319 and ’510 Patents, to the extent not anticipated
`
`by MorphMix, are rendered obvious based on MorphMix itself and/or a
`
`combination of MorphMix with the general knowledge of a POSA and the
`
`RFC 2616 HTTP protocol specification (which specification also further
`
`evidences the general knowledge of a POSA) and/or with the disclosure of
`
`Border and/or with the disclosure of the TCP/IP specifications (RFC 793
`
`and RFC 1180) and/or for the reasons explained in Appendices B and F to
`
`Dr. Freedman’s December 18, 2020 Expert Report Regarding Invalidity.
`
`iii. Oxylabs asserts that the ’319 and ’510 Patents, to the extent not anticipated
`
`by Border, are rendered obvious based on Border itself and/or a combina-
`
`tion of Border with the general knowledge of a POSA and the RFC 2616
`
`HTTP protocol specification (which specification also further evidences the
`
`general knowledge of a POSA) and/or with the disclosure of Crowds and/or
`
`with the disclosure of MorphMix and/or with the disclosure of the TCP/IP
`
`specifications (RFC 793 and RFC 1180) and/or for the reasons explained in
`
`Appendices C and G to Dr. Freedman’s December 18, 2020 Expert Report
`
`Regarding Invalidity.
`
`iv. Oxylabs asserts that the ’614 Patent, to the extent not anticipated by Mith-
`
`yantha, is rendered obvious based on Mithyantha itself and/or a combina-
`
`tion of Mithyantha with the general knowledge of a POSA and the RFC
`
`2616 HTTP protocol specification (which specification also further
`
`10
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 10 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 11 of 32 PageID #: 25374
`
`
`
`evidences the general knowledge of a POSA) and/or with the disclosure of
`
`the TCP/IP specifications (RFC 793 and RFC 1180) and/or with the disclo-
`
`sure and/or with a POSA’s understanding regarding resource utilization on
`
`general computers and/or with the general knowledge concerning standard
`
`process and resource monitoring tools, including Windows Task Manager
`
`and Windows Resource Monitor5 and/or for the reasons explained in Ap-
`
`pendix I to Dr. Freedman’s December 18, 2020 Expert Report Regarding
`
`Invalidity.
`
`v. Oxylabs asserts that the ’614 Patent, to the extent not anticipated by
`
`MorphMix, is rendered obvious based on MorphMix itself and/or a combi-
`
`nation of MorphMix with the general knowledge of a POSA and the RFC
`
`2616 HTTP protocol specification (which specification also further evi-
`
`dences the general knowledge of a POSA) and/or with the disclosure of the
`
`TCP/IP specifications (RFC 793 and RFC 1180) and/or with the disclosure
`
`and/or with a POSA’s understanding regarding resource utilization on gen-
`
`eral computers, and/or with the general knowledge concerning standard pro-
`
`cess and resource monitoring tools, including Windows Task Manager and
`
`Windows Resource Monitor, and/or with the disclosure of Border, and/or
`
`with the disclosure of Mithyantha and/or with the disclosure of RFC 2547
`
`
`5 “Windows Task Manager” and “Windows Resource Manager” refer herein to Windows Task
`Manager or Resource Manager functionality known to a POSA including through the inclusion of
`the functionality in Microsoft Windows Vista operating system (Microsoft Corp., available Janu-
`ary 2007); Microsoft Windows 8 operating system (Microsoft Corp., available October 2012);
`and/or Microsoft Windows Server 2008 R2 operating system (Microsoft Corp., available Oct.
`2009) and including through the description of such functionality in William R. Stanek, Introduc-
`ing Microsoft Windows Vista (2006).
`
`
`
`11
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 11 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 12 of 32 PageID #: 25375
`
`
`
`and/or RFC 4026 and/or for the reasons explained in Appendix J to Dr.
`
`Freedman’s December 18, 2020 Expert Report Regarding Invalidity.
`
`c. Oxylabs specifically contends that the Patents-in-Suit are invalid for claiming un-
`
`patentable subject matter under 35 U.S.C. § 101.6 Oxylabs asserts that the Patents-
`
`in-Suit are ineligible for patent protection under 35 U.S.C. 101 for the reasons ex-
`
`plained in Oxylabs’ briefing associated with its Rule 12(c) motion for judgment on
`
`the pleadings and its motion for summary judgment of invalidity relating to 35
`
`U.S.C. § 101. Bright Data’s Asserted Claims fail step one of the test set forth in
`
`Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208 (2014) because they are di-
`
`rected to abstract idea of obtaining information through an intermediary, and no
`
`fact exists that would allow any factfinder to find that the claims do so in any man-
`
`ner other than through the use of standard computers and servers in the most routine
`
`and conventional way possible to exchange data or content from standard and rou-
`
`tine Internet communications. Bright Data’s Asserted Claims fail step two of the
`
`Alice test because there is nothing in the claims to convert the abstract idea to an
`
`inventive concept. The recitation of a standard computer device acting in a standard
`
`role of a “client” or “server,” or the recitation of the determination of a proxy de-
`
`vice’s resource utilization, cannot convert an abstract idea to an inventive concept
`
`under Alice step two. Oxylabs refers to the discussion and caselaw in its briefing
`
`associated with its Rule 12(c) motion for judgment on the pleadings and its motion
`
`for summary judgment of invalidity.
`
`
`6 Bright Data objects to Defendants’ contentions regarding abstractness as the Court has already
`rejected Defendants’ arguments in the Court’s February 16, 2021 Order denying Defendants’ Mo-
`tion for Judgment on the Pleadings (ECF 303).
`
`
`
`12
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 12 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 13 of 32 PageID #: 25376
`
`
`
`
`
`d. Oxylabs specifically contends that the Patents-in-Suit are invalid for lack of written
`
`description, including for the reasons set forth in the December 18, 2020 Expert
`
`Report of Dr. Michael Freedman Regarding Invalidity. The disclosure of the spec-
`
`ification does not “reasonably convey[] to those skilled in the art that the [patentees]
`
`had possession of the claimed subject matter as of” October 8, 2009. Ariad Pharm.,
`
`Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010). The specification does
`
`not contain a disclosure of the purported server – client device – web server archi-
`
`tecture or the claimed methods. Additionally, the specification specifically teaches
`
`away from the use of prior art proxy servers and peer-to-peer file sharing systems.
`
`Further, the following claim terms lack sufficient written description for at least the
`
`following reasons:
`
`i. If “first client device” is construed, interpreted, or applied to refer to a spe-
`
`cific type of device or hardware other than a standard computer as described
`
`in the ’319 and ’510 Patents (despite the Court’s Claim Construction Order),
`
`Claim 1 of the ’319 and ’510 patents is invalid for lack of sufficient written
`
`description.
`
`ii. If “second server” is construed, interpreted, or applied to refer to a specific
`
`type of device or hardware other than a standard computer as described in
`
`the ’319 and ’510 Patents (despite the Court’s Claim Construction Order),
`
`Claim 1 of the ’319 and ’510 patents is invalid for lack of sufficient written
`
`description.
`
`iii. If Claim 26 of the ’319 Patent or Claim 22 of the ’510 Patent are construed,
`
`interpreted, or applied to cover any details relating to a computer operating
`
`13
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 13 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 14 of 32 PageID #: 25377
`
`
`
`
`
`system beyond what would have been well-known to POSAs, those claims
`
`would be invalid because it would lack a sufficient written description re-
`
`lating to such claim scope.
`
`iv. If Claim 11 of the ’614 Patent is construed, interpreted, or applied to cover
`
`any details relating to a computer operating system beyond what would have
`
`been well-known to POSAs, those claims would be invalid because they
`
`would lack a sufficient written description relating to such claim scope.
`
`e. Oxylabs specifically contends that the ’614 Patent is unenforceable as a result of
`
`Bright Data’s inequitable conduct. Oxylabs asserts that the ’614 Patent is unen-
`
`forceable for at least the reasons explained in Oxylabs’ briefing with respect to
`
`Bright Data’s Motion to Dismiss Oxylabs’ Third Amended Complaint and Bright
`
`Data’s Motion for Summary Judgment of No Inequitable Conduct. Bright Data
`
`committed inequitable conduct by withholding—with specific intent to defraud the
`
`Patent Office—the ’319 Patent from the Examiner of the ’433 Application that is-
`
`sued as the ’614 Patent. Claim 1 of the ’433 Application was rejected as obvious in
`
`view of the prior art. Claim 29 was allowed if rewritten in independent form. Claim
`
`29 was coextensive in scope to claim 1 of the ’319 Patent, and Bright Data there-
`
`fore, unbeknownst to the Examiner of the ’433 Application, previously represented
`
`that it invented the subject matter of claim 1 of the ’319 Patent four years before
`
`the alleged priority date of the ’433 Application. Rather than traverse the Exam-
`
`iner’s rejections, Bright Data amended claim 1 to include the limitations of Claim
`
`29. Because Bright Data intentionally withheld the ’319 Patent from the Examiner,
`
`he allowed Claim 1 of the ’433 Application, as amended, to issue.
`
`14
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 14 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 15 of 32 PageID #: 25378
`
`
`
`f. Oxylabs specifically contends that certain claims of the Patents-in-Suit are invalid
`
`for indefiniteness.7 Oxylabs asserts that the following claim terms are indefinite for
`
`the reasons explained in Oxylabs’ claim construction briefing, arguments and
`
`presentations made at the Claim construction Hearing, and its Objections to the
`
`Claim Construction Order:
`
`i. Claim 1 of the ’510 Patent: “in response to the receiving of the first content
`
`identifier.”
`
`3. Oxylabs contends that it is entitled to a declaratory judgment of non-infringement of the Pa-
`
`tents-in-Suit.
`
`4. Oxylabs contends that it is entitled to a declaratory judgment of invalidity of the Patents-in-
`
`Suit.
`
`5. Oxylabs contends that it is entitled to a declaratory judgment that the ’614 Patent is unenforce-
`
`able due to inequitable conduct.
`
`6. Oxylabs contends that Bright Data’s claims for relief are limited by 35 U.S.C. §§ 286-287
`
`and/or 28 U.S.C. § 1498.
`
`7. Oxylabs contends that Bright Data’s patent claims for relief are barred by prosecution-history
`
`estoppel, extraterritoriality principles, and/or the disclosure-dedication doctrine.
`
`8. Oxylabs contends that the Court should declare that Bright Data is not entitled to any relief,
`
`whether in law or equity or otherwise, from its suit against Oxylabs.
`
`9. Oxylabs contends that the Court should declare that Oxylabs does not infringe and has not
`
`infringed the Patents-in-Suit.
`
`
`7 Bright Data objects to Defendants’ contentions of indefiniteness as the Court has already ruled
`Defendants’ indefiniteness arguments in the Court’s Claim Construction Order (ECF 191).
`15
`
`
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 15 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 16 of 32 PageID #: 25379
`
`
`
`10. Oxylabs contends that the Court should declare that the claims of the Patents-in-Suit are inva-
`
`lid.
`
`11. Oxylabs contends that the Court should declare that the claims of the ’614 patent are unen-
`
`forceable.
`
`12. Oxylabs contends that the Court should permanently enjoin Bright Data, its successors and
`
`assigns, and anyone acting in concert therewith or on its behalf, from attempting to enforce the
`
`Patents-in-Suit against Oxylabs or any parents, affiliates, or subsidiaries of Oxylabs or any of
`
`their respective officers, agents, employees, successors, and assigns.
`
`13. Oxylabs contends that the Court should declare that this is an exceptional case in Oxylabs’
`
`favor pursuant to 35 U.S.C. § 285.
`
`14. Oxylabs contends that the Court should award Oxylabs its costs, expenses, and reasonable
`
`attorney’s fees, whether pursuant to 35 U.S.C. § 285 or otherwise.
`
`15. Oxylabs contends that the Court should dismiss Bright Data’s Complaint in its entirety, with
`
`prejudice.
`
`16. Oxylabs contends that the Court should enter an Order that Oxylabs shall have and recover
`
`from Bright Data any and all such other and further relief, general and special, at law or in
`
`equity, to which Oxylabs may be justly entitled.
`
`17. Oxylabs contends that Bright Data has not suffered any damages on account of its claims
`
`against Oxylabs.
`
`18. Oxylabs contends that Bright Data is not entitled to lost profits or a reasonable royalty, as
`
`Bright Data cannot establish its entitlement to such relief.
`
`19. Oxylabs contends that Bright Data is not entitled to enhanced damages.
`
`
`
`16
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1078
`Page 16 of 32
`
`
`
`Case 2:19-cv-00395-JRG Document 490 Filed 09/17/21 Page 17 of 32 PageID #: 25380
`
`
`
`20. Oxylabs contends that Bright Data cannot establish that this an “exceptional case” in Bright
`
`Data’s favor.
`
`21. Oxylabs contends that Bright Data is not entitled to recover its attorney’s fees.
`
`22. Oxylabs contends that Bright Data is not entitled to recover its costs.
`
`23. Oxylabs contends that Bright Data has not suffered an irreparable injury.
`
`24. Oxylabs contends that, if Bright Data has suffered any injury, Bright Data has an adequate
`
`remedy at law.
`
`25. Oxylabs contends that Bright Data is not entitled to injunctive relief.
`
`26. Oxylabs contends that its declaratory judgment counterclaims are properly brought before this
`
`Court, including but not limited to because the Court has personal jurisdiction over Bright
`
`Data, and that subject-matter jurisdiction and venue are appropriate.
`
`E. STIPULATIONS AND UNCONTESTED FACTS
`
`1. Stipulations
`
`1. Subject-matter jurisdiction is proper in this Court for Bright Data’s claims and Oxylabs’ de-
`
`claratory judgment counterclaims.
`
`2. Defendants and Bright Data do not contest that the Court has personal jurisdiction over the
`
`parties solely for the limited purpose of this action only.
`
`3. Defendants and Bright Data do not contest that venue is proper for this action in the United
`
`States District Court for the Eastern District of Texas, Marshall Division.