Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 1 of 160
`Case 5:18—md-02834-BLF Document 448-3 Filed 06/11/19 Page 1 of 160
`
`EXHIBIT 2
`
`EXHIBIT 2
`
`

`

`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 2 of 160
`
`Michael A. Sherman (SBN 94783)
`masherman@stubbsalderton.com
`Jeffrey F. Gersh (SBN 87124)
`jgersh@stubbsalderton.com
`Sandeep Seth (SBN 195914)
`sseth@stubbsalderton.com
`Wesley W. Monroe (SBN 149211)
`wmonroe@stubbsalderton.com
`Stanley H. Thompson, Jr. (SBN 198825)
`sthompson@stubbsalderton.com
`Viviana Boero Hedrick (SBN 239359)
`vhedrick@stubbsalderton.com
`STUBBS, ALDERTON & MARKILES, LLP
`15260 Ventura Blvd., 20th Floor
`Sherman Oaks, CA 91403
`Telephone:
`(818) 444-4500
`Facsimile:
`(818) 444-4520
`
`Attorneys for PersonalWeb Technologies, LLC
`and Level 3 Communications, LLC
`[Additional Attorneys listed below]
`
`UNITED STATES DISTRICT COURT
`NORTHERN DISTRICT OF CALIFORNIA
`SAN JOSE DIVISION
`CASE NO.: 5:18-md-02834-BLF
`IN RE PERSONALWEB TECHNOLOGIES,
`
`LLC, ET AL., PATENT LITIGATION
`
`
`
`PERSONALWEB TECHNOLOGIES, LLC, a
`Texas limited liability company, and
`LEVEL 3 COMMUNICATIONS, LLC, a
`Delaware limited liability company
`
`Plaintiffs,
`v.
`TWITCH INTERACTIVE, INC., a Delaware
`corporation,
`
`Defendants.
`
`
`PERSONALWEB’S FIRST AMENDED
`DISCLOSURES PURSUANT TO PATENT
`LOCAL RULES 3-1 AND 3-2
`
`
`Case No.: 5:18-cv-05619-BLF
`
`
`
`
`
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 3 of 160
`
`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`Pursuant to Patent Local Rules 3-1 and 3-2, Plaintiff PersonalWeb Technologies, LLC
`(“Plaintiff” or “PersonalWeb”) hereby makes the following Disclosure of Asserted Claims and
`Infringement Contentions to Defendant Twitch Interactive, Inc. (“Twitch” or “Defendant”). These
`discloses are preliminary and subject to change based upon discovery and the Court’s claim
`construction rulings:
`I.
`PRELIMINARY STATEMENT
`In making these contentions, Plaintiff has not yet received any discovery from Defendant
`regarding their infringing methods and systems and has not had access to the source code of the
`accused methods and systems. Plaintiff has, however researched available information, including (1)
`Defendant website(s), (2) publicly available information published by Defendants’ about their accused
`products and services, and (3) publicly available statements and information describing Defendants’
`accused products and services. PersonalWeb therefore reserves the right to amend its Infringement
`Contentions under Patent L.R. 3-6(c).
`Defendants engage in the allegedly infringing conduct through computer systems operating
`proprietary software. Defendants do not publicly disclose the precise operation of their computer
`systems and do not publicly disclose their source code. Because Defendants have not publicly
`disclosed the specific operation of their accused products and services and do not publicly disclose
`their source code for those products and services, PersonalWeb is inherently limited in the degree of
`specificity it can provide in the preliminary infringement contentions. Under these circumstances, the
`Northern District of California recognizes that the plaintiff will not be able to provide highly specified
`infringement contentions and should be permitted further discovery to supplement initial contentions
`with additional information. SpeedTrack, Inc. v. Amazon.com, Inc., No. 4:09-cv-04479-JSW (KAW),
`2018 U.S. Dist. LEXIS 112885, at *16 (N.D. Cal. July 6, 2018). Similarly, Patent Local Rule 3-1
`“does not require [the patent owner] to produce evidence of infringement”, but rather requires that the
`patent owner merely provide the accused infringer “with notice of infringement beyond that which is
`provided by the mere language of the patents themselves.” Network Caching Technology, LLC v.
`Novell, Inc., 2003 U.S. Dist. LEXIS 9881, 2003 WL 21699799, *4 (N.D. Cal. 2003).
`
`
`
`1
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 4 of 160
`
`Accordingly, PersonalWeb reserves the right to amend its disclosures, including the identity
`of the claims being asserted, upon receiving discovery from Defendant.
`II.
`DISCLOSURES UNDER PATENT LOCAL 3-1
`3-1(a): Asserted Claims
`The following claims of each patent in suit are allegedly infringed by the Amazon Parties, the
`applicable statutory subsections of 35 U.S.C. §271 asserted.
`
`(a)
`
`Asserted Patent
`
`Asserted Claims
`
`Statutory Provision
`
`‘310
`
`‘420
`
`‘442
`
`‘544
`
`
`
`20, 69
`
`25, 26, 27, 29, 30, 32, 34, 35,
`36, 166
`
`35 U.S.C. § 271(a)
`
`35 U.S.C. § 271(a)
`
`10, 11
`
`35 U.S.C. § 271(a)
`
`46, 48, 52, 55
`
`35 U.S.C. § 271(a)
`
`(b)
`
`3-1(b): Accused Instrumentality
`The accused method operates in a system that includes Twitch’s website file host servers
`operating with Twitch’s website development system (“Twitch’s web server system”) when used by
`Twitch to control the distribution of Twitch’s webpage file content to other computers connected
`thereto via the Internet, such as intermediate cache servers and computers running web browsers.
`The accused method operates in a system that includes content delivery networks used by
`Twitch to control the distribution of its webpage file content to other computers connected thereto and
`each other via the Internet, such as intermediate cache servers and computers running web browsers.
`The accused systems and methods include certain accused functionalities when combined in
`the manner specified by the asserted claims. Inclusion in the list below does not imply that the
`functionality is an element of any particular patent claim. These functionalities include, but are not
`necessarily limited to:
`
`
`2
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 5 of 160
`
`(a) Cache busting Twitch’s webpage base files1 with content-based ETag values generated and
`
`served from Twitch’s web server system used in conjunction with conditional HTTP GET
`
`requests with IF-NONE-MATCH headers (Category 1);
`
`(b) Cache busting Twitch’s webpage asset files with content-based ETag values generated and
`
`served with the asset file content from Twitch’s web server system, including to CDNs for
`
`re-service, used in conjunction with conditional HTTP GET requests with IF-NONE-
`
`MATCH headers (Category 2);
`
`(c) Cache busting Twitch’s webpage asset files with content-based ETag values generated and
`
`served with the asset file content from Amazon
`
`(d) Web Services (“AWS”) Simple Storage Service (“S3”) (“S3 website file host servers”),
`
`used in conjunction with conditional HTTP GET requests with IF-NONE-MATCH headers
`
`(Category 3).
`
`(e) Cache busting Twitch’s webpage asset files using content-based fingerprints generated and
`
`inserted into the filenames and URI’s of Twitch’s asset files by Twitch’s web server
`
`system, and serving such asset files with fingerprinted URIs from CDNs for re-service,
`
`(Category 4);
`
`(f) Cache busting Twitch’s webpage asset files using fingerprinted URIs in conjunction with
`
`conditional HTTP GET requests, including conditional HTTP GET requests with IF-
`
`NONE-MATCH headers and content-based ETags for Twitch’s webpage base files (‘544
`
`infringement).
`
`
`1 “Webpage base file” refers to the initial file served by a web server in response to a request
`for a webpage. Usually, but not always, this is an HTML file. A webpage base file is sometimes
`referred to as an “index file,” but this term is underinclusive of what is typically contained in a
`webpage base file.
`
`
`3
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 6 of 160
`
`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`The accused instrumentality for categories 1-2 includes software instructions executing in
`Twitch’s web server system, which cannot at this stage be identified by name. Upon information and
`belief, content-based ETag for a webpage base file/webpage asset file values are calculated by such
`software instructions controlling processors to apply the MD5 message digest algorithm to the content
`of the file/object, wherein any two versions of a file/object having identical content will have identical
`associated E-Tag values.
`Before being received in conditional HTTP GET requests, such content-based ETag values
`were previously sent to the other computer in an ETag header field of an HTTP 200 message in
`response to an HTTP GET request for that object.
`The HTTP 304 response message indicates to the other computer that the computer that sent
`the conditional GET request that it is permitted to access the cached copy of the content of the
`file/object referenced in the request for the purposes of that request, such as to re-serve it or use it in
`rendering the Twitch webpage. The HTTP 200 response message, in contrast, indicates to the
`requesting computer that it is not authorized to access the cached copy of the content of the file/object
`referenced in the request, for the purposes of the request, and should instead access the new content
`contained in the HTTP 200 response message for the purposes of the request, such as to re-serve it or
`use it in rendering the webpage of the website operator.
`The accused instrumentality for category 4 includes software instructions executing in
`Twitch’s web server system, which cannot at this stage be identified by name. Upon information and
`belief, content-based fingerprint values are calculated by such software instructions controlling
`processors to apply the MD5 message digest algorithm to the content of the webpage asset file
`file/object plus a seed value, wherein any two versions of a file/object having identical content will
`have identical associated E-Tag values when the same seed value is used. The fingerprint is inserted
`into the filename/URI for the webpage asset file and used for cache-busting in a couple of different
`ways. In one way (‘544 infringement), the browser rendering a Twitch webpage initially receives a
`Twitch webpage base file which references one or more URIs with fingerprints for Twitch asset files
`needed to render the webpage. The browser obtains the referenced webpage asset files and caches the
`
`
`
`4
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 7 of 160
`
`content of those files indexed to their URI that include their fingerprints. When called to again render
`the webpage, the browser sends up a conditional GET request for the webpage base file, which will
`return an HTTP 304 message if the content of any webpage base file (and hence its fingerprint) has
`not changed and therefore the content-based ETag value of. The HTTP 304 message indicates to the
`browser that it is re-permitted to use the cached webpage base file. Because all the webpage asset files
`referenced in the cached file have the same fingerprint value as they did when they were cached, the
`browser will be able to render the webpage using the cached webpage asset files and will not have to
`retrieve them again. If, however, the content of an asset file has changed since the time it was cached,
`its fingerprint would have changed, thereby changing the content of the webpage base file (that will
`now reference the new fingerprint value), thereby changing its ETag value. Therefore, the conditional
`HTTP GET request for the webpage base file will return an HTTP 200 message with, inter alia, the
`new ETag value for the webpage base file and the new content. The Browser will read the new
`webpage base file, and for any webpage base file whose fingerprint has changed, will retrieve that file
`because its URI is not contained in its cache index. In this manner, Twitch can precisely control which
`asset file the browser reuses because it still has the latest authorized content and which asset file
`containing the current authorized content it must obtain to use in rendering the webpage. This method
`may also be practiced with no conditional GET request, in which the browser is always instructed to
`get a new webpage base file which will prevent the cache from using any cached webpage asset file
`that no longer comprises the latest authorized content as just described.
`(c)
`3-1(c): Claim Charts
`Attached as Exhibits A to D hereto are claim charts for each patent-in-suit identifying
`specifically where and how each limitation of each asserted claim is found within each Accused
`Instrumentality. PersonalWeb does not contend that any claim limitation should be interpreted under
`35 U.S.C. § 112(6). While not required by the Patent Local Rules, as a courtesy, Exhibits A and D, in
`turn, refer to Annexure A, which includes more specifics about alleged infringing acts.
`
`
`
`5
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 8 of 160
`
`(d)
`
`3-1(d): Indirect Infringement
`Subject to change with discovery, on the present record, PersonalWeb asserts that Twitch
`directly infringes and that the direct infringement is met by their actions or actions for which they have
`vicarious directly liability. Discovery may show that Twitch is also contributing to or inducing other’s
`infringement.
`(e)
`3-1(e): Doctrine of Equivalents
`Subject to change with discovery and the Court’s claim construction order, PersonalWeb
`alleges that each limitation of each asserted claim is literally present. PersonalWeb also
`believes that any claim element not found to be literally present in the Accused Instrumentality would
`be present under the doctrine of equivalents.
`In Twitch’s Responsive Claim Construction Brief (Dkt. 412), it appears to contend that its
`proposed construction, “an identifier used to locate and access a data item that is generated by
`processing the sequence of bits [of the data item / of the particular data item] of the claim term,” for
`“content-dependent name” (‘310: claims 20 and 69, ‘420: claim 25), and specifically that an identifier
`be “created from the data in the data item,” and that this somehow includes a requirement that the
`identifier is generated only from the data in the data items. Dkt 412 at 12-13.
`In Twitch’s Responsive Claim Construction Brief (Dkt. 412), it contends that its proposed
`construction, “being based on a computation where the input is all of the data in the specific part” for
`“being based on a first function of the contents of the specific part” (‘544: claim 46) and “a value
`created by a computation on the sequence of bits that makes up the part,” for “part value” (‘544: claims
`46 and 52) includes a requirement that the part value be based on a computation that only uses the
`contents of a specific part. Dkt. 412 at 18-20.
`In Twitch’s Responsive Claim Construction Brief (Dkt. 412), it also contends that its proposed
`construction, “computation where the input is the one or more part values,” for “function of the one
`or more of part values” (‘544: claim 46) includes a requirement that the input to the computation is
`only the data in a part value. Dkt. 214 at 18-20.
`
`
`
`6
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 9 of 160
`
`(g)
`
`While PersonalWeb does not understand how Twitch’s proposed constructions for these claim
`terms include a requirement of using only the content of a data item, to the extent that the Court adopts
`Twitch’s proposed claim construction and includes a requirement of using only the content of a data
`item and to the extent that Twitch uses a computation based on more than the content of a data item,
`PersonalWeb contends that the claims are infringed under the doctrine of equivalents.
`To the extent that Twitch has not raised this “only” issue in construing other asserted
`independent claims (e.g., ‘442, claim 10, ‘420, claim 166), but will assert in the future that terms in
`these claims incorporate constructions of construed terms in other patents, PersonalWeb contends that
`these claims are infringed under the doctrine of equivalents as well.
`(f)
`3-1(f): Priority Date
`The priority date of the ‘310, ‘420, ‘442 and ‘544 patents is April 11, 1995.
`3-1(g): Self-Practice
`PersonalWeb does not rely upon its manufacture and use of any product that practices the
`asserted claims.
`(h)
`3-1(h): Damages Period
`The time of the first infringement is presently unknown. The start of claimed damages is
`September 13, 2012, six years prior to PersonalWeb’s filing of the Twitch action. The end of claimed
`damages period is December 26, 2016, the expiration date of the last asserted patent to expire.
`(i)
`3-1(i) Willful Infringement
`Twitch has insufficient information to decide whether it will allege willful infringement but
`reserves the right to make such allegation if facts obtained during discovery so warrant.
`III.
`3-2. Document Production Accompanying Disclosure
`With the “Disclosure of Asserted Claims and Infringement Contentions,” the party claiming
`patent infringement shall produce to each opposing party or make available for inspection and
`copying:
`
`(a) PersonalWeb has no such documents in its possession, custody or control.
`
`
`
`7
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 10 of 160
`
`(b) Any such documents in PersonalWeb’s possession, custody or control have been
`
`previously provided as bates numbers PERSONALWEB000001 to
`
`PERSONALWEB003133, subject to all applicable provisions of the Court’s
`
`protective order.
`
`(c) Any such documents in PersonalWeb’s possession, custody or control have been
`
`previously provided as bates numbers PERSONALWEB003134 to
`
`PERSONALWEB006628, subject to all applicable provisions of the Court’s
`
`protective order.
`
`(d) Any such documents in PersonalWeb’s possession, custody or control have been
`
`provided herewith as bates numbers PERSONALWEB006629 to
`
`PERSONALWEB006634, subject to all applicable provisions of the Court’s
`
`protective order.
`
`(e) N/A
`
`(f) Any such documents in PersonalWeb’s possession, custody or control have been
`
`provided as bates numbers PERSONALWEB006635 to PERSONALWEB006999,
`
`subject to all applicable provisions of the Court’s protective order.
`
`(g) See PERSONALWEB006629 to PERSONALWEB007034.
`
`(h) See PERSONALWEB006629 to PERSONALWEB007034.
`
`(i) N/A
`
`(j) N/A
`
`PersonalWeb has used its best efforts to identify responsive P.R. 3-2 documents and only those
`documents. However, given the volume of documents, some documents may have been inadvertently
`
`
`
`8
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`
`
`
`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 11 of 160
`
`listed or inadvertently omitted. To the extent such deficiencies are identified, PersonalWeb will
`supplement its production accordingly.
`
`Dated: May 8, 2019
`
`Respectfully submitted,
`STUBBS, ALDERTON & MARKILES, LLP
`
`Dated: May 8, 2019
`
`Dated: April 18, 2019
`
`
`
`By: /s/ Michael A. Sherman
`Michael A. Sherman
`Jeffrey F. Gersh
`Sandeep Seth
`Wesley W. Monroe
`Stanley H. Thompson, Jr.
`Viviana Boero Hedrick
`Attorneys for PersonalWeb Technologies, LLC,
`and Level 3 Communications, LLC
`
`MACEIKO IP
`
`
`
`By: /s/ Theodore S. Maceiko
`Theodore S. Maceiko (SBN 150211)
`ted@maceikoip.com
`MACEIKO IP
`420 2nd Street
`Manhattan Beach, California 90266
`Telephone:
`(310) 545-3311
`Facsimile:
`(310) 545-3344
`Attorneys for Defendant/Counterclaimant
`PERSONALWEB TECHNOLOGIES, LLC,
`
`DAVID D. WIER
`
`
`
`By: /s/ David D. Wier
`David D. Wier
`david.wier@level3.com
`Vice President and Assistant General Counsel
`Level 3 Communications, LLC
`1025 Eldorado Boulevard
`Broomfield, CO 80021
`Telephone: (720) 888-3539
`Attorneys for Defendant/Counterclaimant
`LEVEL 3 COMMUNICATIONS, LLC
`
`
`
`9
`
`1ST AMENDED PATENT L.R. 3-1/3-2 DISCLOSURES
`
`
`4833-3791-3476, V. 1
`
`CASE NO: 5:18-md-02834-BLF
`CASE NO: 5:18-cv-05619-BLF
`
`

`

`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 12 of 160
`
`
`Case 5:18—md-02834-BLF Document 448-3 Filed 06/11/19 Page 12 of 160
`
`
`
`
`EXHIBIT A
`TWITCH INTERACTIVE
`EXHIBIT A
`U.S. PATENT NO. 7,802,310
`TWITCH INTERACTIVE
`
`
`U.S. PATENT NO. 7,802,310
`
`
`
`
`
`
`
`

`

`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 13 of 160
`U.S. PATENT NO. 7,802,310 – Claims: 20 and 69
`Accused Instrumentality: TWITCH—WEB HOSTING AND SERVING OF WEBPAGE BASE FILES
`WITH CONTENT-BASED ETAGS [CATEGORY 1] 
`
`
`
`20-1
`
`20-2
`
`U.S. PATENT NO. 7,802,310
`CLAIM 20
`
`20. A computer-implemented
`method operable in a system
`which includes a plurality of
`computers, the method
`comprising:
`
`ELEMENTS IN ACCUSED INSTRUMENTALITY
`
`Twitch implemented the claimed method in a system that includes web host servers
`operated by or on behalf of Twitch (“Twitch web servers”) and a plurality of computers
`directly or indirectly [A1] connected to Twitch web servers and each other via the
`Internet. Upon information and belief, the Twitch web servers are running nginx.
`The connected computers communicate via messages in accordance with the HTTP
`1.1 protocol, RFC 2616, including but not limited to its sections regarding GET
`requests ("HTTP GET requests) (e.g., Sec. 9.3), conditional GET requests ("HTTP
`conditional GET requests") with If None-Match Headers (e.g., Sec. 14.9.4), ETags
`(e.g., Sec. 14.19), 304 messages ("HTTP 304 messages") (e.g., Sec. 10.3.5), 200
`messages ("HTTP 200 messages") (e.g., Sec. 10.2.1), and cache control directives
`(e.g., Secs. 13.1, 13.2, 13.3.2-4, 14.9, 14.21, 14.26) to implement the cache control
`described herein.
`
`controlling distribution of content
`from a first computer to at least
`one other computer, in response
`to a request obtained by a first
`device in the system from a
`second device in the system,
`
`Twitch controls the distribution of its hosted webpage base file content (content) to
`other computers such as outside intermediate cache servers and computers running
`web browsers (“browsers,” “browser computers”) (collectively, other computers) with
`a Twitch web server (a first computer) [A1]. This is done in response to a conditional
`HTTP GET request for Twitch webpage base file content (a request), the request
`obtained by a Twitch web server (a first device in the system from another computer
`(a second device in the system), such as an outside intermediate cache server or a
`computer running a browser [A3, A6, A8-A10, A16-A17].
`
`First Amended Infringement Contentions
`
`1
`
`EXHIBIT A—U.S. Patent No. 7,802,310
`
`

`

`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 14 of 160
`U.S. PATENT NO. 7,802,310 – Claims: 20 and 69
`Accused Instrumentality: TWITCH—WEB HOSTING AND SERVING OF WEBPAGE BASE FILES
`WITH CONTENT-BASED ETAGS [CATEGORY 1] 
`
`
`
`20-3
`
`20-4
`
`U.S. PATENT NO. 7,802,310
`CLAIM 20
`
`the first device comprising
`hardware including at least
`one processor,
`
`the request including at least a
`content-dependent name of a
`particular data item, the
`content-dependent name being
`based at least in part on a
`function of at least some of the
`data comprising the particular
`data item, wherein the
`function comprises a message
`digest function or a hash
`function, and wherein two
`identical data items will have
`the same content-dependent
`name,
`
`ELEMENTS IN ACCUSED INSTRUMENTALITY
`
`A server comprises hardware including at least one processor.
`
`The conditional HTTP GET request has an If-None-Match header containing an ETag
`value (a content-dependent name) of the content of a webpage base file (a particular
`data item) referenced in the request [A6, A8]. That ETag value is calculated by
`applying the MD5 message digest algorithm (a function) to the content of the requested
`webpage base file at the time of the ETag’s calculation. That ETag value is therefore
`based at least in part on a function of at least some of the content of that particular
`webpage base file wherein any two versions of a webpage base file having identical
`content will have identical associated E-Tag values. The MD5 message-digest
`algorithm is both a hash algorithm and a message digest function [A5, A6, A8, A18].
`The ETag value in the request was previously sent to the computer making the
`conditional HTTP GET request, such as a computer running a browser or an
`intermediate cache server, in an ETag header field of an HTTP 200 message when the
`webpage base file referenced in the conditional HTTP GET request was previously
`sent to that computer in response to an HTTP GET request for that webpage base file
`[A6, A8]. The ETag value was generated by the Twitch web server as described above
`before the webpage base file was previously sent in the HTTP 200 response.
`
`First Amended Infringement Contentions
`
`2
`
`EXHIBIT A—U.S. Patent No. 7,802,310
`
`

`

`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 15 of 160
`U.S. PATENT NO. 7,802,310 – Claims: 20 and 69
`Accused Instrumentality: TWITCH—WEB HOSTING AND SERVING OF WEBPAGE BASE FILES
`WITH CONTENT-BASED ETAGS [CATEGORY 1] 
`
`
`
`20-5
`
`U.S. PATENT NO. 7,802,310
`CLAIM 20
`
`based at least in part on said
`content-dependent name of
`said particular data item, the
`first device (A) permitting the
`content to be provided to or
`accessed by the at least one
`other computer if it is not
`determined that the content is
`unauthorized or unlicensed,
`otherwise, (B) if it is
`determined that the content is
`unauthorized or unlicensed,
`not permitting the content to
`be provided to or accessed by
`the at least one other
`computer.
`
`ELEMENTS IN ACCUSED INSTRUMENTALITY
`
`The Twitch web server (first device) compares the ETag value in the obtained request
`with stored ETag values to determine whether the received ETag value matches the
`current ETag value for the content of a webpage base file referenced in the request
`[A8, A9]. If there was a matching ETag for the content of a webpage base file
`referenced in the request, the Twitch web server did does not determine that the content
`of a webpage base file referenced in the request stored on the other computer is
`unauthorized for the purposes of the request and serves an HTTP 304 response
`message to the other computer [A9]. Similarly, to the extent that the content is subject
`to a license, such as Terms of Service or an End User License, or the like, if there is a
`matching ETag for the content of an object referenced in the request, the Twitch web
`server, does not determine that the content of an object referenced in the request stored
`on the other computer is unlicensed for the purposes of the request and serves an HTTP
`304 response message to the other computer.
`If there was not a matching ETag for the content of a webpage base file referenced in
`the request, the Twitch web server did does determine that the content of a webpage
`base file referenced in the request stored on the other computer is unauthorized for the
`purposes of the request and serves an HTTP 200 response message to the other
`computer [A10]. Similarly, to the extent that the content is subject to a license, such
`as Terms of Service or an End User License, or the like, if there is not a matching ETag
`for the content of an object referenced in the request, the S3 website host server or
`CloudFront PoP server, respectively, does determine that the content of an object
`referenced in the request stored on the other computer is unlicensed for the purposes
`of the request and serves an HTTP 200 response message to the other computer. The
`
`First Amended Infringement Contentions
`
`3
`
`EXHIBIT A—U.S. Patent No. 7,802,310
`
`

`

`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 16 of 160
`U.S. PATENT NO. 7,802,310 – Claims: 20 and 69
`Accused Instrumentality: TWITCH—WEB HOSTING AND SERVING OF WEBPAGE BASE FILES
`WITH CONTENT-BASED ETAGS [CATEGORY 1] 
`
`
`
`U.S. PATENT NO. 7,802,310
`CLAIM 20
`
`ELEMENTS IN ACCUSED INSTRUMENTALITY
`
`HTTP 200 response includes the content of a webpage base file referenced in the
`request as then stored on the Twitch web server [A10].
`The HTTP 304 response message indicates to the other computer that the other
`computer is permitted to access the content of a webpage base file referenced in the
`request, stored at the other computer, for the purpose of the request, such as to re-serve
`it or use it in rendering a Twitch webpage [A9]. The HTTP 200 response message, in
`contrast, indicates to the other computer that the other computer is not permitted to
`access the copy of the content of a webpage base file referenced in the request stored
`at the other computer and that the other computer must instead access the new content
`of the webpage base file contained in the HTTP 200 response message for the purposes
`of the request, such as to re-serve it or use it in rendering the Twitch webpage.
`
`
`
`First Amended Infringement Contentions
`
`4
`
`EXHIBIT A—U.S. Patent No. 7,802,310
`
`

`

`Case 5:18-md-02834-BLF Document 448-3 Filed 06/11/19 Page 17 of 160
`U.S. PATENT NO. 7,802,310 – Claims: 20 and 69
`Accused Instrumentality: TWITCH—WEB HOSTING AND SERVING OF WEBPAGE BASE FILES
`WITH CONTENT-BASED ETAGS [CATEGORY 1] 
`
`
`
`U.S. PATENT NO. 7,802,310
`CLAIM 69
`
`69-1 69. A system operable in a
`network of computers, the system
`comprising hardware including at
`least a processor, and software, in
`combination with said hardware:
`
`ELEMENTS IN ACCUSED INSTRUMENTALITY
`
`Twitch’s system, operable in the Internet, includes web host servers operated by or on
`behalf of Twitch (collectively, “Twitch web servers”) for hosting webpage base files and
`a plurality of computers directly or indirectly connected to each other via the Internet.
`Upon information and belief, the content servers are running nginx.
`The connected computers communicate via messages in accordance with the HTTP 1.1
`protocol, RFC 2616, including but not limited to its sections regarding GET requests
`("HTTP GET requests) (e.g., Sec. 9.3), conditional GET requests ("HTTP conditional
`GET requests") with If None-Match Headers (e.g., Sec. 14.9.4), ETags (e.g., Sec. 14.19),
`304 messages ("HTTP 304 messages") (e.g., Sec. 10.3.5), 200 messages ("HTTP 200
`messages") (e.g., Sec. 10.2.1), and cache control directives (e.g., Secs. 13.1, 13.2, 13.3.2-
`4, 14.9, 14.21, 14.26) to implement the cache control described herein [A1, A3, A6, A8-
`A10, A16-A17, A18, A19-21].
`
`69-2
`
`(a) to receive at a first computer,
`from a second computer, a request
`regarding a data item,
`
`A Twitch web server (a first computer) receives a conditional HTTP GET request (a
`request) from another computer (a second computer), such as an outside intermediate
`cache server or a browser [A6].
`
`First Amended Inf