throbber
Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 1 of 21 PageID #: 5338
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`BRIGHT DATA LTD.,
`Plaintiff,
`
`v.
`
`TEFINCOM S.A. D/B/A NORDVPN,
`Defendant.
`







`
`Civil Action No. 2:19-CV-00414-JRG
`
`DEFENDANT’S MOTION FOR SUMMARY JUDGMENT OF
`INVALIDITY OF THE ’319, ’510, AND ’511 PATENTS
`
`103104467.1
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 1 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 2 of 21 PageID #: 5339
`TABLE OF CONTENTS
`
`I.
`INTRODUCTION .................................................................................................................. 1
`II. STATEMENT OF ISSUE TO BE DECIDED........................................................................ 2
`III.
`STATEMENT OF UNDISPUTED MATERIAL FACTS .................................................. 2
`A.
`The Court’s “Server” Claim Scope Orders ...................................................................... 2
`B.
`Undisputed Criteria for “Operating in the Role of a Server” ........................................... 4
`C.
`Crowds and Dr. Freedman’s Mapping of the Second/First Server .................................. 5
`D.
`It is Undisputed that Jondo “4” Meets Both Prongs of the Court’s Clarified “Second
`Server” and “First Server” Constructions ................................................................................... 7
`Dr. Rhyne’s Rebuttals are Irrelevant to the Court’s Clarified Constructions or Dr.
`E.
`Freedman’s Mappings Presented in This Motion ....................................................................... 8
`IV. CROWDS ANTICIPATES THE ASSERTED CLAIMS OF THE ’319, ’510 AND ’511
`PATENTS ....................................................................................................................................... 9
`A.
`Plaintiff Does Not Dispute Much of the Anticipation Mappings..................................... 9
`B.
`There is No Fact Dispute That Jondo “4” Meets Both Prongs of the Court’s Clarified
`“Second Server” (’319, ’510 Patents) and “First Server” (’511 Patent) Constructions ............ 10
`Plaintiff Cannot Avoid Summary Judgment by Raising Arguments Contrary to the
`C.
`Court’s Clarified Claim Constructions ..................................................................................... 12
`Plaintiff’s Criticisms of Dr. Freedman’s Prior Art Mapping of Dependent Claims are
`D.
`Contradicted by Plaintiff’s Infringement Mapping ................................................................... 13
`1.
`’319 Patent Claim 2 and ’510 Patent Claim 2 ............................................................ 13
`2.
`’319 Patent Claim 17 and ’510 Patent Claims 8-9 ..................................................... 14
`3.
`’511 Patent Claim 28 .................................................................................................. 15
`V. CONCLUSION ..................................................................................................................... 15
`
`
`103104467.1
`
`ii
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 2 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 3 of 21 PageID #: 5340
`TABLE OF EXHIBITS
`
`
`
`Exhibit
`A
`
`B
`
`C
`
`D
`
`E
`
`F
`
`G
`H
`I
`J
`
`K
`
`L
`
`M
`
`N
`
`O
`
`P
`
`Shorthand
`Tefincom CC
`Order
`O2 Micro
`Request
`
`Supplemental
`CC Order
`Rhyne Daubert
`Order
`Crowds
`
`ACM Dec.
`
`’319 Patent
`’510 Patent
`’511 Patent
`Freedman Rep.
`
`Freedman Rep.
`App’x A
`Freedman Rep.
`App’x E
`Freedman Rep.
`App’x M
`Rhyne Rebuttal
`Rep.
`Rhyne Tr.
`
`RFC 2616
`
`Description
`Order that claim construction orders from related cases shall
`apply in this case (ECF 63)
`Defendant’s Motion for Hearing Regarding O2 Micro Issue
`(ECF 444 in Bright Data Ltd. v. Teso lt, UAB et al., Case
`No. 2:19-cv-395 (“Teso”))
`Supplemental Claim Construction Order (ECF 453 in Teso)
`
`Excerpt of Order on Pretrial Motions and Motions in Limine
`in Teso (ECF 476 in Teso)
`Reiter and Rubin, Crowds: Anonymity for Web
`Transactions, ACM Transactions on Information and
`System Security, Vol. 1, No. 1, November 1998
`(NORDPA0002553)
`June 4, 2020 Declaration of Scott Delman of Association
`for Computing Machinery (ACM) regarding publication
`status of Crowds (NORDPA0002552)
`U.S. Patent No. 10,257,319
`U.S. Patent No. 10,484,510
`U.S. Patent No. 10,484,511
`Excerpts of August 19, 2021 Expert Report of Dr. Michael
`J. Freedman on behalf of Defendant
`Excerpts of Appendix A of the August 19, 2021 Expert
`Report of Dr. Michael J. Freedman on behalf of Defendant
`Excerpts of Appendix E of the August 19, 2021 Expert
`Report of Dr. Michael J. Freedman on behalf of Defendant
`Excerpts of Appendix M of the August 19, 2021 Expert
`Report of Dr. Michael J. Freedman on behalf of Defendant
`Excerpts of September 12, 2021 Rebuttal Expert Report of
`Dr. V. Thomas Rhyne on behalf of Plaintiff
`Excerpts of rough draft of September 20, 2021 Deposition
`of Dr. V. Thomas Rhyne
`Excerpts of RFC 2616 Hypertext Transfer Protocol --
`HTTP/1.1
`
`103104467.1
`
`iii
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 3 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 4 of 21 PageID #: 5341
`
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`Cases
`Little v. Liquid Air Corp.,
`37 F.3d, 1069, 1075 (5th Cir. 1994) ........................................................................................10
`
`103104467.1
`
`iv
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 4 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 5 of 21 PageID #: 5342
`
`
`I.
`
`INTRODUCTION
`
`Dr. Rhyne, Plaintiff’s rebuttal expert, disputes one—and only one—aspect of Defendant’s
`
`expert, Dr. Freedman’s, mappings of the sole independent claim of each of the ’319, ’510 and ’511
`
`Patents to the prior art reference, Crowds. Ex. N (Rhyne Rebuttal Rep.) at ¶¶ 173-185, 576-588.
`
`Dr. Rhyne asserts only that jondo “4” cannot be a “server.” Id. As discussed in the concurrently-
`
`filed Motion to Strike Dr. Rhyne, the Court’s prior claim construction orders have addressed and
`
`rejected the bases for Dr. Rhyne’s contention—that “a server cannot be a client device” and a user
`
`computer cannot be “interchangeable” with a server. Setting those arguments aside, summary
`
`judgment of invalidity follows directly.
`
`There is no fact issue that Crowds’ jondo “4” is “operating in the role of a server,” which
`
`the Court held is the “correct” criteria for determining if a device is a server. Ex. C (Supplemental
`
`CC Order) at 7-11. Dr. Rhyne’s report does not dispute Dr. Freedman’s analysis on this point.
`
`And Dr. Rhyne provided matching testimony as to: (1) his view on what functionality is
`
`“sufficient” to be a server and (2) the functionality of jondo “4” that he agrees Crowds discloses:
`
`
`
`Functionality of jondo “4” that Dr. Rhyne
`
`
`
`agrees Crowds discloses
`
`
`
`
`
` Ex. O (Rhyne Tr.) at 117:4-17,
`
`152:12-153:19.1
`
`
`
`
`
`
`
`
`
` Id. at 152:12-
`
`153:19.
`
`
`1 All emphasis added unless otherwise indicated.
`
`103104467.1
`
`- 1 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 5 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 6 of 21 PageID #: 5343
`
`Further, Dr. Rhyne raises only a handful of challenges to the mapping of any dependent
`
`claims, and those are nothing more than inaccurate assertions that Defendant’s expert, Dr.
`
`Freedman, did not address an issue. Accordingly, the Court should grant summary judgment of
`
`invalidity.
`
`II.
`
`STATEMENT OF ISSUE TO BE DECIDED
`
`Whether the prior art Crowds reference anticipates the asserted claims of the ’319, ’510
`
`and ’511 Patents.
`
`III.
`
`STATEMENT OF UNDISPUTED MATERIAL FACTS
`
`A.
`
`1.
`
`The Court’s “Server” Claim Scope Orders
`
`Claim construction in this matter is governed by the Orders and final constructions
`
`entered in Bright Data Ltd. v. Teso lt, UAB et al., Case No. 2:19-cv-395 (“Teso”) and Bright Data
`
`Ltd. v. Code200, UAB et al., Case No. 2:19-cv-396 (“Code200”). Ex. A (Tefincom CC Order).
`
`2.
`
`Defendants in the Teso and Code200 cases filed a Motion for Rehearing Regarding
`
`O2 Micro Issue in which Defendants stated: “Oxylabs respectfully requests clarification that: (i)
`
`as already recited in the existing constructions, the claimed “server” is not the separately recited
`
`[first / requesting] client device, but can otherwise be a client device, and (ii) as the Court already
`
`ruled for another term (i.e., “client device”), the claimed “server” is a device operating in the role
`
`of a server and does not require any specific hardware.” Ex. B (O2 Micro Request) at 1 (emphasis
`
`in original).
`
`3.
`
`Oxylabs proposed the following clarifications shown in underline to the Court’s
`
`existing claim constructions:
`
`(cid:120)
`
`’319/’510 Patents (Teso): “second server” means “a device that is operating
`in the role of a server and that is not the first client device.”
`
`…
`
`103104467.1
`
`- 2 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 6 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 7 of 21 PageID #: 5344
`
`(cid:120)
`
`’511 Patent (Code200): “first server” means “a device that is operating in
`the role of a server and that is not the first client device or the web server.”
`
`Id. (emphasis in original).
`
`4.
`
`In response, the Court issued a Supplemental Claim Construction Order
`
`summarizing the Court’s prior holdings in the Teso and Code200 claim construction Orders and
`
`concluding:
`
`The Court finds that the clarifications Defendants seek are not inconsistent with
`the Court’s previous findings about the nature of the client device, web server, first
`server and second server. Said previous findings have already been stated with
`respect to the constructions as they stand. Accordingly, the Court clarifies that
`Defendants’ understanding of the scope of the constructions, as represented by
`the requested clarifications in Defendants’ Motion for Hearing, is correct. The
`Court is not changing the construction of “first server” and “second server,” as this
`understanding is already embedded in those terms’ construction. Further, the Court
`is not now changing the scope of the terms in any way, but merely providing a
`clarification of the scope of the terms as they stand.
`
`Ex. C (Supplemental CC Order) at 7-11.
`
`5.
`
`The Court largely reached this conclusion by summarizing the prior Orders, and
`
`also addressed Bright Data’s argument regarding interchangeability:
`
`Plaintiff’s argument that Defendant seeks to treat client devices and servers
`interchangeably, citing to the Court’s statement that “[Defendants] deny that they
`will claim client devices and servers are interchangeable general user computers”
`is an oversimplification of the issue. It is not that Defendants seek to “reduc[e] the
`recited server ↔ client device ↔ web server architecture . . . and the recited client
`device ↔ server ↔ web server architecture . . . as an indistinguishable computer
`↔ computer ↔ computer architecture” as Plaintiffs argue. See Dkt. No. 242 at 4.
`Rather, a component can be configured to operate in different roles—so long as it
`does not “simultaneously serve as more than one of: the client device, the first
`server/second server, and the web server.” See Dkt. No. 97 at 13.
`
`Id. at 10.
`
`6.
`
`Finally, in a Daubert Order based on briefing submitted prior to the Court’s
`
`Supplemental Claim Construction Order, the Court “instructed that Dr. Rhyne was not to testify
`
`before the jury that a client device cannot be a server.” Ex. D (Rhyne Daubert Order) at 4.
`
`103104467.1
`
`- 3 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 7 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 8 of 21 PageID #: 5345
`
`7.
`
`Thus, applying the Court’s constructions and clarifications, “second server” as used
`
`in the ’319, ’510 Patents has two prongs: (1) “a device that is operating in the role of a server” and
`
`(2) “is not the first client device.” Ex. C (Supplemental CC Order) at 7-11. Likewise, “first server”
`
`as used in the ’511 Patent has two prongs: (1) “a device that is operating in the role of a server”
`
`and (2) “is not the first client device or the first web server.” Id.
`
`B.
`
`8.
`
`Undisputed Criteria for “Operating in the Role of a Server”
`
`Under Defendants’ requested clarifications, which the Court held “are correct,” a
`
`device is a “server” when it is “operating in the role of a server.” Ex. C (Supplemental CC Order)
`
`at 7-11. Arguments that any other properties are required for a device to either be a server or
`
`disqualify a device from being a server are contrary to the Court’s Order.
`
`9.
`
`There is no material dispute as to what “operating in the role of a server” entails to
`
`a POSITA as Dr. Freedman and Dr. Rhyne employed similar descriptions, all equally applicable
`
`to the art. All descriptions are similar to the definition of “server” provided by RFC 2616, the
`
`HTTP 1.1 specification cited by the asserted patents, of “[a]n application program that accepts
`
`connections in order to service requests by sending back responses.” Ex. J (Freedman Rep.) at
`
`¶ 136; Ex. P (RFC 2616) at § 1.3. Citing RFC 2616, Dr. Freedman concluded a device “fulfill(s)
`
`the typical role of a server” because it “receives web requests from” other devices “and provides
`
`information to other network devices.” Ex. J (Freedman Rep.) at ¶ 122. Dr. Freedman also
`
`elsewhere tracked the RFC 2616 language even more closely, concluding that a device is operating
`
`in the role of a server because it “accepted a connection” from a requesting device “in order to
`
`send back a response.” Ex. K (Freedman Rep. App’x A) at 11.
`
`10.
`
`103104467.1
`
`- 4 -
`
`
`
`
`
`
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 8 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 9 of 21 PageID #: 5346
`
`Ex. O (Rhyne Tr.) at 26:7-25.
`
`
`
`
`
`
`
` Id. at 117:4-17.
`
`C.
`
`11.
`
`Crowds and Dr. Freedman’s Mapping of the Second/First Server
`
`Crowds: Anonymity for Web Transactions (“Crowds”) is an article published in
`
`1998, making it 102(b) prior art to each asserted patent. Ex. E (Crowds); see also Ex. F (ACM
`
`Dec) (ACM declaration confirming that Crowds was published in the November 1998 journal);
`
`Ex. J (Freedman Rep.) at ¶ 113. Crowds was not before the Patent Office during prosecution of
`
`the patents. Ex. G (’319 Patent) at Cover; Ex. H (’510 Patent) at Cover; Ex. I (’511 Patent) at
`
`Cover.
`
`12.
`
`The relevant disclosure of Crowds is not disputed. “‘Crowds’ describes a system
`
`comprised of groups (‘crowds’) of user computers that can interact with one or more web servers.”
`
`Ex. N (Rhyne Rebuttal Rep.) at ¶ 166. “[A] user installs software on his/her computer to initiate
`
`a process called a ‘jondo.’” Id. In Crowds, when a user’s browser makes a web request, the jondo
`
`software on that device will intercept the request and route the request through a path of jondos
`
`(software running on the computer of other users of the system). Crowds discloses an embodiment
`
`in which messages travel over the path “5→4→6→server;” that is, jondo “5” → jondo “4” →
`
`jondo “6” → web server “5.” See Ex. E (Crowds) at 73; Fig. 2. Dr. Freedman annotated this path
`
`in green:
`
`103104467.1
`
`- 5 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 9 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 10 of 21 PageID #: 5347
`
`
`
`Ex. K (Freedman Rep. App’x A) at 11.
`
`13.
`
`Dr. Freedman explained that in this embodiment “the initiator would be jondo ‘5,’
`
`which would forward the web request to jondo ‘4’ on another user’s computer, which would
`
`forward the request to jondo ‘6,’ which would make the request to the target web server.” Ex. K
`
`(Freedman Rep. App’x A) at 7. “As Crowds notes, ‘server replies traverse the same path as the
`
`requests, only in reverse.’” Id. at 11.
`
`
`
`
`
`
`
` Ex. O (Rhyne Tr.) at 152:12-153:19.
`
`14.
`
`Dr. Freedman mapped the “5→4→6→server” embodiment of Crowds to the
`
`asserted claims of each of the ’319, ’510 and ’511 Patents. Ex. K (Freedman Rep. App’x A); Ex.
`
`L (Freedman Rep. App’x E); Ex. M (Freedman Rep. App’x M). For Claim 1 of each patent, Dr.
`
`Rhyne disputed one—and only one—aspect of Dr. Freedman’s mapping. Ex. N (Rhyne Rebuttal
`
`Rep.) at ¶¶ 173-185, 576-588. Dr. Rhyne disputed only that jondo “4” can be a “server” and, in
`
`particular, that it can be the claimed “second server” of the ’319 and ’510 Patents or the claimed
`
`“first server” of the ’511 Patent. Id.
`
`103104467.1
`
`- 6 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 10 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 11 of 21 PageID #: 5348
`
`D.
`
`It is Undisputed that Jondo “4” Meets Both Prongs of the Court’s Clarified
`“Second Server” and “First Server” Constructions
`
`15.
`
`Addressing the first prong of the Court’s clarified constructions, whether jondo “4”
`
`is operating in the role of a server, Dr. Freedman opined that jondo “4” operates in the role of a
`
`server because “jondo 4 receives web requests from preceding jondo 5 in the jondo path, and
`
`provides information to other network devices, fulfilling the typical role of a server.” Ex. M
`
`(Freedman Rep. App’x M) at 5; see also Ex. K (Freedman Rep. App’x A) at 8 (“Crowds teaches
`
`that a jondo provides information to other jondos in response to the other jondos issuing requests
`
`to it, thereby fulfilling the typical role of a server”); Ex. L (Freedman Rep. App’x E) at 11 (same).
`
`16.
`
`Dr. Freedman provided further analysis, opining “that jondo ‘4’ in the above
`
`example is indeed a ‘server’ in the commonly understood sense of the word because jondo ‘4’
`
`accepted a connection from jondo ‘5’ in order to send back a response. As Crowds notes, ‘server
`
`replies traverse the same path as the requests, only in reverse.’” Ex. K (Freedman Rep. App’x A)
`
`at 11; Ex. L (Freedman Rep. App’x E) at 8 (same).
`
`17.
`
`Dr. Rhyne provided no rebuttal to this analysis. Dr. Rhyne argued without analysis:
`
`“Nor does Dr. Freedman provide any analysis as to whether Crowds discloses configuring jondo
`
`‘4’ to operate in the role of a server.” Ex. N (Rhyne Rebuttal Rep.) at ¶ 177; id. at ¶ 584 (same).
`
`Dr. Rhyne is incorrect.
`
`18.
`
`Dr. Rhyne’s deposition testimony is in accord with Dr. Freedman’s analysis. Dr.
`
`Rhyne testified that
`
`Ex. O (Rhyne Tr.) at 117:4-17.
`
`103104467.1
`
`- 7 -
`
`
`
`
`
`
`
`
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 11 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 12 of 21 PageID #: 5349
`
`
`
` Id. at 152:12-153:19.
`
`19.
`
`Addressing the second prong of the Court’s clarified constructions, for the ’319 and
`
`’510 Patents, Dr. Freedman mapped jondo “6” to the claimed “first client device” and jondo “4”
`
`to the claimed “second server.” Ex. K (Freedman Rep. App’x A) at 7; Ex. L (Freedman Rep.
`
`App’x E) at 8. Thus, jondo “4” is not the first client device. Id. For the ’511 Patent, Dr. Freedman
`
`mapped jondo “5” to the claimed “first client device,” jondo “4” to the claimed “first server,” and
`
`web server “5” to the claimed “first web server.” Ex. M (Freedman Rep. App’x M) at 3. Thus,
`
`jondo “4” is not the first client device or the first web server. Id. Dr. Rhyne did not assert
`
`otherwise.
`
`the first client
`device
`
`the first web server
`
`the first client device
`
`Not the first client device
`
`Not the first client device or the first web server
`
`
`
`
`
`’319 and ’510 Patents
`
`’511 Patent
`
`
`
`E.
`
`Dr. Rhyne’s Rebuttals are Irrelevant to the Court’s Clarified Constructions
`or Dr. Freedman’s Mappings Presented in This Motion
`
`20. While disputing Dr. Freedman’s conclusion, no portion of Dr. Rhyne’s analysis of
`
`Dr. Freedman’s mapping of the independent claims of the ’319, ’510 and ’511 Patents to Crowds
`
`rebuts any portion of Dr. Freedman’s analysis. For the ’319 and ’510 Patent, the first portion of
`
`103104467.1
`
`- 8 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 12 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 13 of 21 PageID #: 5350
`
`Dr. Rhyne’s rebuttal asserted that “Crowds does not disclose the second server” for reasons not
`
`relevant and contrary to the Court’s construction. Ex. N (Rhyne Rebuttal Rep.) at ¶¶ 173-78
`
`(arguing that “a server cannot be a client device” and “user computers” are not “interchangeable”
`
`with servers). And, the latter portion addressed Dr. Freedman’s alternative mappings (obviousness
`
`and disclosure of “specialized hardware” ultimately not required by the Court’s construction) not
`
`at issue in this Motion. Id. at ¶¶ 178-85.
`
`21.
`
`Likewise, for the ’511 Patent, the first portion of Dr. Rhyne’s rebuttal asserted
`
`“Crowds does not disclose a first server” for reasons not relevant and contrary to the Court’s
`
`construction. Ex. N (Rhyne Rebuttal Rep.) at ¶¶ 577-81 (arguing that “user computers” are not
`
`“servers” and “user computers” are not “interchangeable” with servers). And, the latter portion
`
`addressed Dr. Freedman’s alternative mappings (obviousness and disclosure of “specialized
`
`equipment” ultimately not required by the Court’s construction) not at issue in this Motion. Id. at
`
`¶¶ 582-88.
`
`IV. CROWDS ANTICIPATES THE ASSERTED CLAIMS OF THE ’319, ’510 AND
`’511 PATENTS
`
`A.
`
`Plaintiff Does Not Dispute Much of the Anticipation Mappings
`
`It is undisputed that Crowds was published in 1998, over a decade before the earliest
`
`priority date of the ’319, ’510 and ’511 Patents in 2009, and is therefore 102(b) prior art. Ex. E
`
`(Crowds); Ex. F (ACM Dec); Ex. J (Freedman Rep.) at ¶ 113. Dr. Freedman has presented
`
`summary judgment evidence demonstrating how Crowds discloses each element of each asserted
`
`claim of the ’319, ’510 and ’511 Patents. Ex. J (Freedman Rep.) at ¶ 112-43; Ex. K (Freedman
`
`Rep. App’x A); Ex. L (Freedman Rep. App’x E); Ex. M (Freedman Rep. App’x M). Dr. Rhyne’s
`
`challenges to Dr. Freedman’s analysis are limited:
`
`103104467.1
`
`- 9 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 13 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 14 of 21 PageID #: 5351
`
`(cid:120) Dr. Rhyne does not challenge any aspect of Dr. Freedman’s mappings of Claim 1
`
`of each patent except disputing that jondo “4” can be the claimed “second server”
`
`of the ’319 and ’510 Patents or the claimed “first server” of the ’511 Patent. Ex. N
`
`(Rhyne Rebuttal Rep.) at ¶¶ 173-185, 576-588.
`
`(cid:120) Dr. Rhyne does not raise any challenge to Dr. Freedman’s mapping of dependent
`
`claims 14, 15, 18, 21, 22, 24, 25, 26, or 27 of the ’319 Patent, dependent claims 10,
`
`11, 13, 15, 16, 18, 19, 22, or 23 of the ’510 Patent, or dependent claims 14, 20, 21,
`
`22, 23, 25, 27, 29, or 30 of the ’511 Patent other than a missing “second” / “first”
`
`“server.” Id. at ¶¶ 186-97, 210-23, 589-99.
`
`B.
`
`There is No Fact Dispute That Jondo “4” Meets Both Prongs of the Court’s
`Clarified “Second Server” (’319, ’510 Patents) and “First Server” (’511
`Patent) Constructions
`
`As discussed in Section III.A, above, the Court’s clarified construction of “second server”
`
`as used in the ’319, ’510 Patents has two prongs: (1) “a device that is operating in the role of a
`
`server” and (2) “is not the first client device.” Ex. C (Supplemental CC Order) at 7-11. Likewise,
`
`“first server” as used in the ’511 Patent has two prongs: (1) “a device that is operating in the role
`
`of a server” and (2) “is not the first client device or the first web server.” Id.
`
`Addressing the first prong of “a device that is operating in the role of a server,” Dr. Rhyne
`
`asserted only: “Nor does Dr. Freedman provide any analysis as to whether Crowds discloses
`
`configuring jondo ‘4’ to operate in the role of a server.” Ex. N (Rhyne Rebuttal Rep.) at ¶ 177; id.
`
`at ¶ 584 (same). This statement is incorrect and insufficient to overcome summary judgment. See
`
`Little v. Liquid Air Corp., 37 F.3d, 1069, 1075 (5th Cir. 1994). As discussed in Section III.D,
`
`above, Dr. Freedman provides such analysis, explaining “jondo 4 receives web requests from
`
`preceding jondo 5 in the jondo path, and provides information to other network devices, fulfilling
`
`103104467.1
`
`- 10 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 14 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 15 of 21 PageID #: 5352
`
`the typical role of a server.” Ex. M (Freedman Rep. App’x M) at 5; see also Ex. K (Freedman
`
`Rep. App’x A) at 8 (“Crowds teaches that a jondo provides information to other jondos in response
`
`to the other jondos issuing requests to it, thereby fulfilling the typical role of a server”); Ex. L
`
`(Freedman Rep. App’x E) at 11 (same).
`
`Not only does Dr. Rhyne’s report raise no rebuttal, his deposition makes clear he does not
`
`dispute Dr. Freedman’s position. First, as discussed in Section III.B, above,
`
`
`
`
`
`
`
`at 117:4-17. Second,
`
` Ex. O (Rhyne Tr.)
`
`
`
` Dr. Rhyne agrees that jondo “4”
`
`“forwards the traffic onto [jondo] 6 to the web server,” thereby requesting on behalf of a client
`
`content from a target website and “and provide[s] that content to [jondo] 5,” thereby returning the
`
`content back to the requesting client, jondo “5.” Id. at 152:12-153:19.
`
`
`
`
`
` Id. at 101:5-18, 98:18-99:2. Thus,
`
`both under the Court’s construction and Dr. Rhyne’s view, the undisputed functionality of jondo
`
`“4” operating in the role of a server makes jondo “4” conclusively a server.
`
`Plaintiff does not dispute that the second prong is met. As illustrated graphically below,
`
`jondo “4” “is not the first client device” in Dr. Freedman’s mapping of the ’319 and ’510 Patents
`
`because Dr. Freedman maps jondo “6,” a distinct device, to the claimed “first client device. Ex.
`
`K (Freedman Rep. App’x A) at 7; Ex. L (Freedman Rep. App’x E) at 8. Likewise, jondo “4” “is
`
`103104467.1
`
`- 11 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 15 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 16 of 21 PageID #: 5353
`
`not the first client device or the first web server” in Dr. Freedman’s mapping of the ’511 Patent
`
`because Dr. Freedman maps jondo “5,” a distinct device, to the claimed “first client device” and
`
`web server “5” to the claimed “first web server.” Ex. M (Freedman Rep. App’x M) at 3.
`
`the first client
`device
`
`the first web server
`
`the first client device
`
`Not the first client device
`
`Not the first client device or the first web server
`
`
`
`
`
`’319 and ’510 Patents
`
`’511 Patent
`
`
`
`C.
`
`Plaintiff Cannot Avoid Summary Judgment by Raising Arguments Contrary
`to the Court’s Clarified Claim Constructions
`
`When an expert’s opinion “is clearly foreclosed by the district court’s claim construction”
`
`“the district court is not obligated to credit an expert’s testimony” and such opinion is not sufficient
`
`to avoid summary judgment. See Duncan Parking Techs., Inc. v. IPS Group, Inc., 914 F.3d 1347,
`
`1363 (Fed. Cir. 2019) (affirming the district court’s grant of summary judgment). Such is the case
`
`here as explained in Defendant’s Motion to Strike Dr. Rhyne’s “server” opinions. Dr. Rhyne
`
`argues that jondo “4” cannot be a “server” because: (1) “a server cannot be a client device” and
`
`(2) “user computers” are not “interchangeable” with servers and Crowds discloses an
`
`“indistinguishable computer ↔ computer ↔ computer architecture.” Ex. N (Rhyne Rebuttal Rep.)
`
`at ¶¶ 173-78, 577-81. Both arguments are “clearly foreclosed by the district court’s claim
`
`construction.”
`
`103104467.1
`
`- 12 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 16 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 17 of 21 PageID #: 5354
`
`As an initial matter, these arguments are contrary to the Court’s claim construction because
`
`they seek to add limitations not found in the construction. Moreover, here the Court has
`
`specifically rejected the limitations Dr. Rhyne seeks to add. Dr. Rhyne conceded in deposition
`
`that the statement “a server cannot be a client device” is not “consistent with the Court’s rulings.”
`
`Ex. O (Rhyne Tr.) at 95:4-96:18. And the Court specifically addressed and rejected Dr. Rhyne’s
`
`“interchangeable” argument, holding “Plaintiff’s argument that Defendant seeks to treat client
`
`devices and servers interchangeably as “an oversimplification of the issue,” quoting and rejecting
`
`the same “indistinguishable computer ↔ computer ↔ computer architecture” language Dr. Rhyne
`
`uses. Ex. C (Supp. CC Order) at 10.
`
`D.
`
`Plaintiff’s Criticisms of Dr. Freedman’s Prior Art Mapping of Dependent
`Claims are Contradicted by Plaintiff’s Infringement Mapping
`
`As discussed above, Dr. Rhyne does not raise any challenge to Dr. Freedman’s mapping
`
`of dependent Claims 14, 15, 18, 21, 22, 24, 25, 26, or 27 of the ’319 Patent, dependent Claims 10,
`
`11, 13, 15, 16, 18, 19, 22, or 23 of the ’510 Patent, or dependent Claims 14, 20, 21, 22, 23, 25, 27,
`
`29, or 30 of the ’511 Patent other than a missing “second” / “first” “server.” Ex. N (Rhyne Rebuttal
`
`Rep.) at ¶¶ 186-97, 210-23, 589-99. Thus, the Court should grant summary judgment of invalidity
`
`on those claims.
`
`For ’319 Patent Claims 2 and 12, ’510 Patent Claim 2 and 8-9, and ’511 Patent Claim 27,
`
`Dr. Rhyne offers only conclusory rebuttals that fail to acknowledge Dr. Freedman’s analysis.
`
`1.
`
`’319 Patent Claim 2 and ’510 Patent Claim 2
`
`’319 Patent Claim 2 and ’510 Patent Claim 2 each recite a step of “sending, by the first
`
`client device, during, as part of, or in response to, a start-up of the first client device, a first message
`
`to the second server, and wherein the first messages comprises the first IP address, the MAC
`
`address, or the hostname.” Ex. G (’319 Patent) at Claim 2; Ex. H (’510 Patent) at Claim 2. Dr.
`
`103104467.1
`
`- 13 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1076
`Page 17 of 21
`
`

`

`Case 2:19-cv-00414-JRG Document 99 Filed 09/29/21 Page 18 of 21 PageID #: 5355
`
`Rhyne challenged Dr. Freedman’s mapping, asserting in a single sentence without elaboration:
`
`“Dr. Freedman identifies no disclosure from Crowds of the user computer sending its first IP
`
`address, the MAC address, or the hostname ‘during, as part of, or in response to, a start-up or
`
`power-up of the user computer.’” Ex. N (Rhyne Rebuttal Rep.) at ¶¶ 187, 211. The alleged basis
`
`for Dr. Rhyne’s opinion, that “Dr. Freedman identifies no disclosure from Crowds,” is inaccurate.
`
`Dr. Freedman identified disclosure in Crowds that “‘jondos will establish shared keys using Diffie-
`
`Hellman key exchange’” where a “POSA would understand that Diffie-Hellman is a cryptographic
`
`key-exchange protocol” such that “[t]he messages sent as part of that key exchange would include
`
`the IP address of both sender and recipient, and thus the other jondo would receive a message from
`
`the first jondo, during the first jondo’s initialization period, that includes the first jondo’s IP
`
`address and port number.” Ex. K (Freedman Rep. App’x A) at 24-25; Ex. L (Freedman Rep.
`
`App’x E) at 20-21. Dr. Rhyne provided no rebuttal of Dr. Freedman’s analysis. Ex. N (Rhyne
`
`Rebuttal Rep.) at ¶¶ 187, 211.
`
`2.
`
`’319 Patent Claim 17 and ’510 Patent Claims 8-9
`
`’319 Patent Claim 17 and ’510 Patent Claim 8 each recite “periodically communicating
`
`[over the TCP connection] between the second server and the first client device.” Ex. G (’319
`
`Patent) at Claim 17; Ex. H (’510 Patent) at Claim 8. Dr. Rhyne challenged Dr. Freedman’s
`
`mapping, asserting in a single sentence without elaboration: “Dr. Freedman identifies no
`
`disclosure from Crowds showing ‘periodically communicating’ between user computers.” Ex. N
`
`(Rhyne Rebuttal Rep.) at ¶¶ 190, 212. The alleged basis for Dr. Rhyne’s opinion, that “Dr.
`
`Freedman identifies no disclosure from Crowds,” is inaccurate. Dr. Freedman identifies disclosure
`
`in Crowds that jondos “communicate via the HTTP protocol for the purpose of sending web
`
`requests” and “the process of ‘periodically communicating’ was a standard and well-known feature
`
`of devices communicating via HTTP.” Ex. K (Freedman Rep. App’x A) at 29-30; Ex. L (Freedman
`
`103104467.1
`
`- 14 -
`
`Code200, UAB v. Bright Data Ltd.
`Code 200's Exhibit 1

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