Exhibit 4

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 1 of 14 PageID #: 245
Page 1 of 13

U.S. Patent No. 7,784,058 vs. HPE

Accused Instrumentalities: HPE’s Ezmeral Runtime Enterprise, and all versions and variations thereof since the issuance of the asserted patent.

Claim 1

Claim 1 Accused Instrumentalities

[1pre] 1. A computing system for 

executing a plurality of software 

applications comprising:

To the extent the preamble is limiting, each Accused Instrumentality comprises or constitutes a

computing system for executing a plurality of software applications as claimed.

See claim limitations below.

See also, e.g.:

https://support.hpe.com/hpesc/public/docDisplay?docId=a00ecp54hen_us&page=home/about-hpeezmeral-container-pl/Welcome.html

https://support.hpe.com/hpesc/public/docDisplay?docId=a00097165en_us&docLocale=en_US&page

=GUID-6B6676DB-AF5F-4555-B6AB-D2C11A89F320.html

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 2 of 14 PageID #: 246
Page 2 of 13

Claim 1 Accused Instrumentalities

https://h50146.www5.hpe.com/products/software/oe/linux/mainstream/support/whitepaper/pdfs/4AA

6-2761ENW.pdf

[1a] a) a processor; Each Accused Instrumentality comprises a processor.

See, e.g.:

https://support.hpe.com/hpesc/public/docDisplay?docId=a00ecp54hen_us&docLocale=en_US&page

=home/about-hpe-ezmeral-container-pl/GEN_End_User_Software_Agreement.html

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 3 of 14 PageID #: 247
Page 3 of 13

Claim 1 Accused Instrumentalities

[1b] b) an operating system having an 

operating system kernel having OS 

critical system elements (OSCSEs) for 

running in kernel mode using said 

processor; and,

Each Accused Instrumentality comprises an operating system having an operating system kernel 

having OS critical system elements (OSCSEs) for running in kernel mode using said processor.

See, e.g.:

https://support.hpe.com/hpesc/public/docDisplay?docId=a00097165en_us&docLocale=en_US&page

=GUID-6B6676DB-AF5F-4555-B6AB-D2C11A89F320.html

https://support.hpe.com/hpesc/public/docDisplay?docId=a00ecp54hen_us&docLocale=en_US&page

=home/about-hpe-ezmeral-container-pl/GEN_End_User_Software_Agreement.html

https://support.hpe.com/hpesc/public/docDisplay?docId=a00ecp54hen_us&page=home/about-hpeezmeral-container-pl/GEN_OS_Support.html

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 4 of 14 PageID #: 248
Page 4 of 13

Claim 1 Accused Instrumentalities

https://h50146.www5.hpe.com/products/software/oe/linux/mainstream/support/whitepaper/pdfs/4AA

6-2761ENW.pdf

https://www.techtarget.com/searchdatacenter/definition/kernel

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 5 of 14 PageID #: 249
Page 5 of 13

Claim 1 Accused Instrumentalities

[1c] c) a shared library having shared 

library critical system elements 

(SLCSEs) stored therein for use by the 

plurality of software applications in user 

mode and

Each Accused Instrumentality comprises a shared library having shared library critical system 

elements (SLCSEs) stored therein for use by the plurality of software applications in user mode.

See, e.g.:

https://support.hpe.com/hpesc/public/docDisplay?docId=a00097165en_us&docLocale=en_US&page

=GUID-6B6676DB-AF5F-4555-B6AB-D2C11A89F320.html

https://www.hpe.com/us/en/what-is/container-platform.html

https://kubernetes.io/docs/concepts/containers/

https://community.hpe.com/t5/hpe-blog-uk-ireland-middle-east/containerization-the-next-generationof-virtualization/ba-p/7154442

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 6 of 14 PageID #: 250
Page 6 of 13

Claim 1 Accused Instrumentalities

https://www.techtarget.com/searchitoperations/definition/container-containerization-or-containerbased-virtualization

https://docs.docker.com/storage/storagedriver/

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 7 of 14 PageID #: 251
Page 7 of 13

Claim 1 Accused Instrumentalities

https://h50146.www5.hpe.com/products/software/oe/linux/mainstream/support/whitepaper/pdfs/4AA

6-2761ENW.pdf

[1d] i) wherein some of the SLCSEs 

stored in the shared library are functional 

replicas of OSCSEs and are accessible to 

some of the plurality of software 

applications and when one of the 

SLCSEs is accessed by one or more of 

the plurality of software applications it 

forms a part of the one or more of the 

plurality of software applications,

In each Accused Instrumentality, some of the SLCSEs stored in the shared library are functional 

replicas of OSCSEs and are accessible to some of the plurality of software applications and when one 

of the SLCSEs is accessed by one or more of the plurality of software applications it forms a part of 

the one or more of the plurality of software applications.

For example, a Docker base image serves as a self-contained unit that encompasses all the necessary 

components for an application to run, including the application code, runtime environment, system 

tools, and dependencies (i.e., SLCSEs). The images are based on existing Linux distributions, such as 

Debian and Ubuntu, including essential system elements (i.e., functional replicas of OSCSEs). Each 

container image is based on a specific base image, which contains the application code, and 

dependencies, including system libraries or shared library critical system elements (SLCSEs). When 

the container runs the image, it creates a runtime instance of that container image.

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 8 of 14 PageID #: 252
Page 8 of 13

Claim 1 Accused Instrumentalities

See, e.g.:

https://docs.ezmeral.hpe.com/runtime-enterprise/55/app-workbench-5-1/custom-baseimages/AWB51_About_Custom_Base_Images.html

https://community.hpe.com/t5/hpe-blog-uk-ireland-middle-east/containerization-the-next-generationof-virtualization/ba-p/7154442

https://kubernetes.io/docs/concepts/containers/

ttps://www.techtarget.com/searchitoperations/definition/Docker-image

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 9 of 14 PageID #: 253
Page 9 of 13

Claim 1 Accused Instrumentalities

https://docs.docker.com/storage/storagedriver/

https://www.hpe.com/us/en/what-is/docker.html

[1e] ii) wherein an instance of a SLCSE 

provided to at least a first of the plurality 

of software applications from the shared 

library is run in a context of said at least 

first of the plurality of software 

applications without being shared with 

other of the plurality of software 

applications and where at least a second 

of the plurality of software applications 

In each Accused Instrumentality, an instance of a SLCSE provided to at least a first of the plurality of 

software applications from the shared library is run in a context of said at least first of the plurality of 

software applications without being shared with other of the plurality of software applications and 

where at least a second of the plurality of software applications running under the operating system 

have use of a unique instance of a corresponding critical system element for performing same 

function.

When a Docker image is used to create a container, it creates a separate and isolated instance of a 

runtime environment which is independent of other containers running on the same host. Each 

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 10 of 14 PageID #: 254
Page 10 of 13

Claim 1 Accused Instrumentalities

running under the operating system have 

use of a unique instance of a 

corresponding critical system element for 

performing same function, and

container has its own instance of base images and its own data. The containers run in isolation, 

ensuring that the SLCSEs stored in the shared library are accessible to the software applications 

running in their respective containers. The docker image includes essential system files, libraries, and 

dependencies required to run the software application within the container. The Docker containers 

can share common dependencies and components using layered images. This means that multiple 

containers utilize the same base image to create an instance. When an instance of SLCSE is provided 

from the base image (i.e., from the shared library) to an individual container including application 

software, it operates in isolation and runs its own instance of the software application without sharing 

resources or critical system elements with other containers. This ensures that each container has its 

own isolated context. Docker containers can share common dependencies and components using 

layered images. This means that multiple containers can utilize the same base image. Therefore, each 

container, containing the application software running under the operating system, utilizes a unique 

instance of the corresponding critical system element to execute the respective application software 

for performing a same or a different function.

See, e.g.:

https://support.hpe.com/hpesc/public/docDisplay?docId=a00097165en_us&docLocale=en_US&page

=GUID-6B6676DB-AF5F-4555-B6AB-D2C11A89F320.html

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 11 of 14 PageID #: 255
Page 11 of 13

Claim 1 Accused Instrumentalities

https://h50146.www5.hpe.com/products/software/oe/linux/mainstream/support/whitepaper/pdfs/4AA

6-2761ENW.pdf

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 12 of 14 PageID #: 256
Page 12 of 13

Claim 1 Accused Instrumentalities

https://docs.docker.com/storage/storagedriver/

https://www.techtarget.com/searchitoperations/definition/Docker-image

[1f] iii) wherein a SLCSE related to a 

predetermined function is provided to the 

first of the plurality of software 

applications for running a first instance 

of the SLCSE, and wherein a SLCSE for 

performing a same function is provided 

to the second of the plurality of software 

applications for running a second 

instance of the SLCSE simultaneously.

In each Accused Instrumentality, a SLCSE related to a predetermined function is provided to the first 

of the plurality of software applications for running a first instance of the SLCSE, and wherein a 

SLCSE for performing a same function is provided to the second of the plurality of software 

applications for running a second instance of the SLCSE simultaneously.

For example, In Docker, each container operates independently, and a Docker base image includes 

essential system files, libraries, and dependencies (i.e., SLCSEs) required to run the software 

application within the container. Based on information and belief, each element, such as system files, 

libraries, and dependencies (i.e., SLCSE) is associated with an execution of a predetermined function 

related to the application. When a Docker image is used to create a container in ECS, an instance of 

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 13 of 14 PageID #: 257
Page 13 of 13

Claim 1 Accused Instrumentalities

the SLCSE is provided to a software application. Therefore, different instances of the SLCSE are 

provided to different applications for performing either a same or a different function, simultaneously.

See, e.g.:

https://www.techtarget.com/searchitoperations/definition/Docker-image, Last accessed on June 14, 

2023 

https://docs.docker.com/get-started/overview/

https://docs.docker.com/storage/storagedriver/

Case 2:24-cv-00093-JRG Document 39-4 Filed 05/13/24 Page 14 of 14 PageID #: 258