Exhibit 8

 

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 1 of 10 PageID #: 180
1 

Exhibit 8 to Complaint 

Intellectual Ventures I LLC and Intellectual Ventures II 

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 2 of 10 PageID #: 181
2 

Example Chase Count I Systems and Services 

U.S. Patent No. 8,332,844 (“the ’844 Patent”) 

The Accused Instrumentalities include, without limitation, Chase’s systems that utilize Docker; all past, current, and future 

systems and services that operate in the same or substantially similar manner as the specifically identified systems and services; and all 

past, current, and future Chase’s systems and services that have the same or substantially similar features as the specifically identified 

systems and services (“Example Chase Count I Systems and Services”). 

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 3 of 10 PageID #: 182
3 

U.S. Patent No. 8,332,844 

Example Claim 7 Example Chase Count I Systems and Services 

7. A method for 

providing data to a 

plurality of compute 

nodes, comprising: 

Upon information and belief, Chase’s systems provide “a method for providing data to a plurality of compute 

nodes, including Docker.” Docker provides docker images to a compute node in a cluster. 

See https://careers.jpmorgan.com/global/en/students/programs/techconnect?search=&tags=location__Americas__UnitedStatesofAmerica (last accessed on November 10, 

2023); see also

https://jpmc.fa.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1002/job/210434368/?keyword=

kubernetes&mode=location (last accessed November 13, 20203) 

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 4 of 10 PageID #: 183
4 

storing blocks of a 

root image of said 

compute nodes on a 

first storage unit; 

Upon information and belief, Chase’s systems perform “storing blocks of a root image of said compute nodes 

on a first storage unit.” Docker stores blocks of a root image (via the collection of read-only layers in a 

Docker image) in the Docker registry. 

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 5 of 10 PageID #: 184
5 

See https://docs.docker.com/storage/storagedriver/ (last accessed on November 10, 2023). 

See https://distribution.github.io/distribution/ (last accessed on November 11, 2023). 

storing leaf images 

for respective 

compute nodes on 

respective second 

storage units, 

Upon information and belief, Chase’s systems perform “storing leaf images for respective compute nodes on 

respective second storage units.” Docker stores leaf images (thin R/W layer in a runnable container) for 

respective compute nodes on respective second storage units (Docker’s local storage area). 

See https://docs.docker.com/develop/develop-images/dockerfile_best-practices/ (last accessed on November 

10, 2023).

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 6 of 10 PageID #: 185
6 

See https://docs.docker.com/storage/storagedriver/ (last accessed on November 10, 2023). 

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 7 of 10 PageID #: 186
7 

See https://docs.docker.com/storage/storagedriver/ (last accessed on November 10, 2023). 

said leaf images 

including only 

additional data blocks 

not previously 

contained in said root 

image and changes 

made by respective 

compute nodes to the 

blocks of the root 

image, 

Upon information and belief, Chase’s systems also have “leaf images including only additional data blocks 

not previously contained in said root image and changes made by respective compute nodes to the blocks of 

the root image.” Docker includes a writable per runnable container layer for new data such as new files and 

including a copy on write strategy for changes made to the blocks of the root image. 

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 8 of 10 PageID #: 187
8 

See https://docs.docker.com/develop/develop-images/dockerfile_best-practices/ (last accessed on November 

10, 2023). 

See https://docs.docker.com/storage/storagedriver/ (last accessed on November 10, 2023). 

wherein said leaf 

images of respective 

compute nodes do not 

include blocks of said 

root image that are 

unchanged by 

respective compute 

nodes; and 

Upon information and belief, Chase’s systems include “wherein said leaf images of respective compute nodes 

do not include blocks of said root image that are unchanged by respective compute nodes.” Docker contains 

a writable layer using copy on write, leaving unchanged image data in their original image layers. 

See https://docs.docker.com/storage/storagedriver/ (last accessed on November 10, 2023).

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 9 of 10 PageID #: 188
9 

caching blocks of 

said root image that 

have been accessed 

by at least one of said 

compute nodes in a 

cache memory. 

Upon information and belief, Chase’s systems perform “caching blocks of said root image that have been 

accessed by at least one of said compute nodes in a cache memory.” Docker caches unchanged image layers 

from previous RUN commands. 

See https://collabnix.com/how-to-clear-docker-cache/ (last accessed on November 10, 2023). 

See https://thenewstack.io/understanding-the-docker-cache-for-faster-builds/ (last accessed on November 

10, 2023).

Case 2:23-cv-00523-JRG Document 1-9 Filed 11/15/23 Page 10 of 10 PageID #: 189