EXHIBIT 3

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 1 of 52 PageID #:

5623
Page 1 of 51

U.S. Patent No. 7,519,814 vs. HPE

Accused Instrumentalities: HPE products and services using secure containerized applications, including without limitation HPE’s Ezmeral Runtime 

Enterprise and HPE GreenLake, and all versions and variations thereof since the issuance of the asserted patent.

Each Accused Instrumentality infringes the claims in substantially the same way, and the evidence shown in this chart is similarly applicable to each 

Accused Instrumentality. Each claim limitation is literally infringed by each Accused Instrumentality. However, to the extent any claim limitation is 

not met literally, it is nonetheless met under the doctrine of equivalents because the differences between the claim limitation and each Accused 

Instrumentality would be insubstantial, and each Accused Instrumentality performs substantially the same function, in substantially the same way, to 

achieve the same result as the claimed invention. Notably, Defendant has not yet articulated which, if any, particular claim limitations it believes are 

not met by the Accused Instrumentalities.

Claim 1

Claim 1 Accused Instrumentalities

[1pre] 1. In a system having a plurality of 

servers with operating systems that 

differ, operating in disparate computing 

environments, wherein each server 

includes a processor and an operating 

system including a kernel a set of 

associated local system files compatible 

with the processor, a method of providing 

at least some of the servers in the system 

with secure, executable, applications 

related to a service, wherein the 

applications are executed in a secure 

environment, wherein the applications 

each include an object executable by at 

least some of the different operating 

systems for performing a task related to 

the service, the method comprising:

To the extent the preamble is limiting, HPE and/or its customer practices, through the Accused 

Instrumentalities, in a system having a plurality of servers with operating systems that differ, 

operating in disparate computing environments, wherein each server includes a processor and an 

operating system including a kernel a set of associated local system files compatible with the 

processor, a method of providing at least some of the servers in the system with secure, executable, 

applications related to a service, wherein the applications are executed in a secure environment, 

wherein the applications each include an object executable by at least some of the different operating 

systems for performing a task related to the service, as claimed.

For example, HPE Ezmeral Runtime Enterprise runs on individual servers, including HPE Synergy 

and HPE ProLiant servers, each of which runs an independent operating system, including for 

example RHEL or SLES running either on bare metal, through an on-premises virtualized 

infrastructure, through one or more cloud services, or through any other supported deployment. In an 

exemplary deployment, two or more servers use different operating systems. 

HPE requires that each server includes a processor with one or more cores available to the OS kernel. 

HPE further requires each server to have a supported operating system (SLES or RHEL/CentOS), 

which includes a kernel and associated local system files, including for example libraries such as 

libc/glibc, configuration files, etc. In the infringing system, at least two servers have different 

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 2 of 52 PageID #:

5624
Page 2 of 51

Claim 1 Accused Instrumentalities

operating systems, for example SLES and RHEL/CentOS, or for another example different versions 

of SLES and/or RHEL/CentOS.

In at least some instances, HPE directly owns, operates, controls, and/or benefits from the claimed

system and/or method. In other instances, HPE’s customer makes and uses the system and/or method 

either by following HPE’s direction and control, including HPE’s documentation, or automatically 

through the ordinary and expected operation of HPE’s software, or a combination thereof.

See claim limitations below.

See also, e.g.:

https://www.hpe.com/psnow/doc/a50004264enw.pdf?jumpid=in_pdp-psnow-qs

https://community.hpe.com/t5/hpe-ezmeral-uncut/hpe-ezmeral-container-platform-is-now-hpeezmeral-runtime/ba-p/7151720

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 3 of 52 PageID #:

5625
Page 3 of 51

Claim 1 Accused Instrumentalities

https://www.hpe.com/psnow/doc/a50003599enw

https://www.hpe.com/psnow/doc/a50004264enw.pdf?jumpid=in_pdp-psnow-qs

https://www.hpe.com/psnow/doc/a50004264enw.pdf?jumpid=in_pdp-psnow-qs

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 4 of 52 PageID #:

5626
Page 4 of 51

Claim 1 Accused Instrumentalities

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

6-2761ENW.pdf

https://docs.ezmeral.hpe.com/runtime-enterprise/56/home/about-hpe-ezmeral-containerpl/GEN_End_User_Software_Agreement.html

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 5 of 52 PageID #:

5627
Page 5 of 51

Claim 1 Accused Instrumentalities

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

6-2761ENW.pdf

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

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

https://docs.ezmeral.hpe.com/runtime-enterprise/56/reference/universalconcepts/Controller_Gateway_and_Worker_Hosts.html

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 6 of 52 PageID #:

5628
Page 6 of 51

Claim 1 Accused Instrumentalities

https://docs.ezmeral.hpe.com/runtimeenterprise/56/reference/kubernetes/Kubernetes_Physical_Architecture.html#v52_k8s-kubernetesphysical-architecture__k8s-cluster-architecture

[1a] storing in memory accessible to at 

least some of the servers a plurality of 

secure containers of application software, 

each container comprising one or more of 

the executable applications and a set of 

associated system files required to 

execute the one or more applications, for 

use with a local kernel residing 

permanently on one of the servers; 

The method practiced by HPE and/or its customer through the Accused Instrumentalities includes a 

step of storing in memory accessible to at least some of the servers a plurality of secure containers of 

application software, each container comprising one or more of the executable applications and a set 

of associated system files required to execute the one or more applications, for use with a local kernel 

residing permanently on one of the servers.

For example, HPE Ezmeral Runtime Enterprise stores application containers, sometimes called 

Docker containers, container images, Kubernetes containers, or Kubernetes pods, in persistent storage 

available to each node running the application. The container might be in a format defined by the 

Open Container Initiative. This storage may be physically attached to the server or connected through 

any supported interconnect, including over a network. Each container includes the application 

software as well as a Linux user space required to execute the application, for example libc/glibc and 

other shared libraries, configuration files, etc. necessary for the application. For example, the 

container includes a base OS image, provided by HPE or by a third party, such as a CentOS, RHEL, 

or Ubuntu base image. The container is compatible with the host kernel, for example because the 

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 7 of 52 PageID #:

5629
Page 7 of 51

Claim 1 Accused Instrumentalities

container libraries are linked against the Linux kernel, and the supported host operating systems also 

use the Linux kernel, which has a stable binary interface.

See, e.g.:

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

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 8 of 52 PageID #:

5630
Page 8 of 51

Claim 1 Accused Instrumentalities

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

6-2761ENW.pdf

https://www.hpe.com/psnow/doc/a50002075enw

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 9 of 52 PageID #:

5631
Page 9 of 51

Claim 1 Accused Instrumentalities

https://www.hpe.com/psnow/doc/a50002075enw

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

https://developer.hpe.com/blog/kubernetes-application-containers-managing-containers-and-clusterresour/

https://developer.hpe.com/blog/kubernetes-application-containers-managing-containers-and-clusterresour/

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

https://www.docker.com/blog/the-10-most-common-questions-it-admins-ask-about-docker/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 10 of 52 PageID #:

5632
Page 10 of 51

Claim 1 Accused Instrumentalities

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

=reference/universal-concepts/Namespaces.html

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 11 of 52 PageID #:

5633
Page 11 of 51

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 12 of 52 PageID #:

5634
Page 12 of 51

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 13 of 52 PageID #:

5635
Page 13 of 51

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 14 of 52 PageID #:

5636
Page 14 of 51

Claim 1 Accused Instrumentalities

https://kubernetes.io/docs/concepts/storage/volumes/

https://kubernetes.io/docs/concepts/containers/container-environment/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 15 of 52 PageID #:

5637
Page 15 of 51

Claim 1 Accused Instrumentalities

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

https://kubernetes.io/docs/concepts/storage/volumes/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 16 of 52 PageID #:

5638
Page 16 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/spec.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 17 of 52 PageID #:

5639
Page 17 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/spec.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 18 of 52 PageID #:

5640
Page 18 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/config.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 19 of 52 PageID #:

5641
Page 19 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/config.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 20 of 52 PageID #:

5642
Page 20 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/config.md

[1b] wherein the set of associated system 

files are compatible with a local kernel of 

at least some of the plurality of different 

operating systems, 

In the method practiced by HPE and/or its customer through the Accused Instrumentalities, the set of 

associated system files are compatible with a local kernel of at least some of the plurality of different 

operating systems.

The system files in the container are compatible with the host kernel, for example because they are 

linked against the Linux kernel and the supported host operating systems also use the Linux kernel, 

which has a stable binary interface.

See discussion in element [1a] above. 

See, e.g.:

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 21 of 52 PageID #:

5643
Page 21 of 51

Claim 1 Accused Instrumentalities

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

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

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

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

6-2761ENW.pdf

[1c] the containers of application 

software excluding a kernel, 

In the method practiced by HPE and/or its customer through the Accused Instrumentalities, the 

containers of application software exclude a kernel.

See, e.g.:

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

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 22 of 52 PageID #:

5644
Page 22 of 51

Claim 1 Accused Instrumentalities

https://www.docker.com/blog/the-10-most-common-questions-it-admins-ask-about-docker/

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

[1d] wherein some or all of the associated 

system files within a container stored in 

memory are utilized in place of the 

associated local system files that remain 

resident on the server, 

In the method practiced by HPE and/or its customer through the Accused Instrumentalities, some or 

all of the associated system files within a container stored in memory are utilized in place of the 

associated local system files that remain resident on the server.

For example, each container will utilize its own local system files, including libraries such as 

libc/glibc and configuration files, not the corresponding libraries and configuration files of the host 

OS.

See, e.g.:

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

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

https://developer.hpe.com/blog/kubernetes-application-containers-managing-containers-and-clusterresour/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 23 of 52 PageID #:

5645
Page 23 of 51

Claim 1 Accused Instrumentalities

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

[1e] wherein said associated system files 

utilized in place of the associated local 

system files are copies or modified 

copies of the associated local system files 

that remain resident on the server, 

In the method practiced by HPE and/or its customer through the Accused Instrumentalities, said 

associated system files utilized in place of the associated local system files are copies or modified 

copies of the associated local system files that remain resident on the server.

For example, in some cases the host OS and container will use one or more identical system files, for 

example when both the host and the container incorporate the same Linux distribution version, or 

when both host and container use the same version of libc. In other cases modified copies are used 

instead, for example when different versions of the same library, or configuration files with different 

parameters, are used by the host and container.

See, e.g.:

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

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

https://medium.com/@swalperen3008/what-is-dockerize-and-dockerize-your-project-a-step-by-stepguide-899c48a34df6

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 24 of 52 PageID #:

5646
Page 24 of 51

Claim 1 Accused Instrumentalities

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

[1f] and wherein the application software 

cannot be shared between the plurality of 

secure containers of application software,

In the method practiced by HPE and/or its customer through the Accused Instrumentalities, the 

application software cannot be shared between the plurality of secure containers of application 

software.

For example, each container has an isolated runtime environment that cannot be accessed by other 

containers, for example including a per-container writeable layer or other ephemeral per-container 

storage. For another example, when the plurality of secure containers each corresponds to a different 

container image, each container cannot access another container’s image and therefore application 

software.

See, e.g.:

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

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

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

=reference/universal-concepts/Namespaces.html

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 25 of 52 PageID #:

5647
Page 25 of 51

Claim 1 Accused Instrumentalities

https://developer.hpe.com/blog/kubernetes-application-containers-managing-containers-and-clusterresour/

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 26 of 52 PageID #:

5648
Page 26 of 51

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 27 of 52 PageID #:

5649
Page 27 of 51

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 28 of 52 PageID #:

5650
Page 28 of 51

Claim 1 Accused Instrumentalities

[1g] and wherein each of the containers 

has a unique root file system that is 

different from an operating system's root 

file system.

In the method practiced by HPE and/or its customer through the Accused Instrumentalities, each of 

the containers has a unique root file system that is different from an operating system's root file 

system.

For example, the container’s root file system comprises the image layer(s), an ephemeral writeable 

layer (e.g., in Docker terminology the container layer), and optionally one or more volumes. This root 

file system is distinct and isolated from the host operating system’s root file system.

See, e.g.:

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

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

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 29 of 52 PageID #:

5651
Page 29 of 51

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 30 of 52 PageID #:

5652
Page 30 of 51

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 31 of 52 PageID #:

5653
Page 31 of 51

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 32 of 52 PageID #:

5654
Page 32 of 51

Claim 1 Accused Instrumentalities

https://kubernetes.io/docs/concepts/storage/volumes/

https://kubernetes.io/docs/concepts/containers/container-environment/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 33 of 52 PageID #:

5655
Page 33 of 51

Claim 1 Accused Instrumentalities

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

https://kubernetes.io/docs/concepts/storage/volumes/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 34 of 52 PageID #:

5656
Page 34 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/spec.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 35 of 52 PageID #:

5657
Page 35 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/spec.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 36 of 52 PageID #:

5658
Page 36 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/config.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 37 of 52 PageID #:

5659
Page 37 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/config.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 38 of 52 PageID #:

5660
Page 38 of 51

Claim 1 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/config.md

Claim 2

Claim 2 Accused Instrumentalities

2. A method as defined in claim 1, 

wherein each container has an execution 

file associated therewith for starting the 

one or more applications.

HPE and/or its customer practices, through the Accused Instrumentalities, a method as defined in 

claim 1, wherein each container has an execution file associated therewith for starting the one or more 

applications.

For example, a container image has an associated image configuration comprising information for 

starting the one or more applications. This can be an Open Containers Initiative image configuration. 

See, e.g.:

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 39 of 52 PageID #:

5661
Page 39 of 51

Claim 2 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/spec.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 40 of 52 PageID #:

5662
Page 40 of 51

Claim 2 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/spec.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 41 of 52 PageID #:

5663
Page 41 of 51

Claim 2 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/config.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 42 of 52 PageID #:

5664
Page 42 of 51

Claim 2 Accused Instrumentalities

https://github.com/opencontainers/imagespec/blob/a6af2b480dcfc001ba975f44de53001c873cb0ef/config.md

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 43 of 52 PageID #:

5665
Page 43 of 51

Claim 6

Claim 6 Accused Instrumentalities

6. A method as defined in claim 2, 

comprising the step of assigning a unique 

associated identity to each of a plurality 

of the containers, wherein the identity 

includes at least one of IP address, host 

name, and MAC address.

HPE and/or its customer practices, through the Accused Instrumentalities, a method as defined in 

claim 2, comprising the step of assigning a unique associated identity to each of a plurality of the 

containers, wherein the identity includes at least one of IP address, host name, and MAC address.

For example, Kubernetes containers have an associated hostname, which in the case of a singlecontainer Pod is the unique identity of that container. For another example, Kubernetes pods have an 

associated hostname, which is unique. For another example, a networked Kubernetes pod has an 

assigned IPv4 and/or IPv6 address. For another example, a Docker container has an IP address and a 

hostname.

See, e.g.:

https://kubernetes.io/docs/concepts/containers/container-environment/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 44 of 52 PageID #:

5666
Page 44 of 51

Claim 6 Accused Instrumentalities

https://docs.docker.com/network/

Claim 9

Claim 9 Accused Instrumentalities

9. A method as defined in claim 2, 

wherein server information related to 

hardware resource usage including at 

least one of CPU memory, network 

bandwidth, and disk allocation is 

associated with at least some of the 

containers prior to the applications within 

the containers being executed.

HPE and/or its customer practices, through the Accused Instrumentalities, a method as defined in 

claim 2, wherein server information related to hardware resource usage including at least one of CPU 

memory, network bandwidth, and disk allocation is associated with at least some of the containers 

prior to the applications within the containers being executed.

For example, Kubernetes tracks and limits resource usage, including CPU and memory resources. For 

another example, Docker tracks and limits resource usage, including CPU and memory resources.

See, e.g.:

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 45 of 52 PageID #:

5667
Page 45 of 51

Resource Management for Pods and Containers

When you specify a Pod, you can optionally specify how much of each resource 

a container needs. The most common resources to specify are CPU and memory 

(RAM); there are others.

When you specify the resource request for containers in a Pod, the kubescheduler uses this information to decide which node to place the Pod on. When 

you specify a resource limit for a container, the kubelet enforces those limits so 

that the running container is not allowed to use more of that resource than the 

limit you set. The kubelet also reserves at least the request amount of that system 

resource specifically for that container to use.

Requests and limits

If the node where a Pod is running has enough of a resource available, it's 

possible (and allowed) for a container to use more resource than its request for 

that resource specifies. However, a container is not allowed to use more than its 

resource limit.

For example, if you set a memory request of 256 MiB for a container, and that 

container is in a Pod scheduled to a Node with 8GiB of memory and no other 

Pods, then the container can try to use more RAM.

If you set a memory limit of 4GiB for that container, the kubelet (and container 

runtime) enforce the limit. The runtime prevents the container from using more 

than the configured resource limit. For example: when a process in the container 

tries to consume more than the allowed amount of memory, the system kernel 

terminates the process that attempted the allocation, with an out of memory 

(OOM) error.

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 46 of 52 PageID #:

5668
Page 46 of 51

Claim 9 Accused Instrumentalities

Limits can be implemented either reactively (the system intervenes once it sees a 

violation) or by enforcement (the system prevents the container from ever 

exceeding the limit). Different runtimes can have different ways to implement the 

same restrictions.

https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

Runtime options with Memory, CPUs, and GPUs

By default, a container has no resource constraints and can use as much of a given 

resource as the host's kernel scheduler allows. Docker provides ways to control how 

much memory, or CPU a container can use, setting runtime configuration flags of 

the docker run command. This section provides details on when you should set such 

limits and the possible implications of setting them.

Limit a container's access to memory

Docker can enforce hard or soft memory limits.

• Hard limits lets the container use no more than a fixed amount of memory.

• Soft limits lets the container use as much memory as it needs unless certain 

conditions are met, such as when the kernel detects low memory or contention on 

the host machine.

https://docs.docker.com/config/containers/resource_constraints/

Claim 10

Claim 10 Accused Instrumentalities

10. A method as defined in claim 2, 

wherein in operation when an application 

residing within a container is executed, 

said application has no access to system 

files or applications in other containers or 

HPE and/or its customer practices, through the Accused Instrumentalities, a method as defined in 

claim 2, wherein in operation when an application residing within a container is executed, said 

application has no access to system files or applications in other containers or to system files within 

the operating system during execution thereof.

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 47 of 52 PageID #:

5669
Page 47 of 51

Claim 10 Accused Instrumentalities

to system files within the operating 

system during execution thereof.

See, e.g.:

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

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

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

=reference/universal-concepts/Namespaces.html

https://developer.hpe.com/blog/kubernetes-application-containers-managing-containers-and-clusterresour/

Claim 31

Claim 31 Accused Instrumentalities

[31pre] A computing system for 

performing a plurality of tasks each 

comprising a plurality of processes 

comprising:

To the extent the preamble is construed as a limitation, each Accused Instrumentality is or comprises 

a computing system for performing a plurality of tasks each comprising a plurality of processes.

See claim limitations below. See also analysis and evidence for [1pre] above.

[31a] a system having a plurality of 

secure containers of associated files 

accessible to, and for execution on, one 

or more servers, each container being 

mutually exclusive of the other, such that 

read/write files within a container cannot 

Each Accused Instrumentality comprises a system having a plurality of secure containers of 

associated files accessible to, and for execution on, one or more servers, each container being 

mutually exclusive of the other, such that read/write files within a container cannot be shared with 

other containers, each container of files is said to have its own unique identity associated therewith, 

said identity comprising at least one of an IP address, a host name, and a Mac_address.

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 48 of 52 PageID #:

5670
Page 48 of 51

Claim 31 Accused Instrumentalities

be shared with other containers, each 

container of files is said to have its own 

unique identity associated therewith, said 

identity comprising at least one of an IP 

address, a host name, and a Mac_address

See analysis and evidence for [1pre], limitations [1a] and [1f], and claim 6 above.

[31b] wherein, the plurality of files 

within each of the plurality of containers 

comprise one or more application 

programs including one or more 

processes, and associated system files for 

use in executing the one or more 

processes wherein the associated system 

files are files that are copies of files or 

modified copies of files that remain as 

part of the operating system, each 

container having its own execution file 

associated therewith for starting one or 

more applications, in operation, each 

container utilizing a kernel resident on 

the server and wherein each container 

exclusively uses a kernel in an underlying 

operation system in which it is running 

and is absent its own kernel; and,

Each Accused Instrumentality comprises a system wherein the plurality of files within each of the 

plurality of containers comprise one or more application programs including one or more processes, 

and associated system files for use in executing the one or more processes wherein the associated 

system files are files that are copies of files or modified copies of files that remain as part of the 

operating system, each container having its own execution file associated therewith for starting one or 

more applications, in operation, each container utilizing a kernel resident on the server and wherein 

each container exclusively uses a kernel in an underlying operation system in which it is running and 

is absent its own kernel.

See analysis and evidence for [1pre], limitations [1a], [1c], [1d], [1e], and [1f], and claim 2 above.

[31c] a run time module for monitoring 

system calls from applications associated 

with one or more containers and for 

providing control of the one or more 

applications.

Each Accused Instrumentality comprises a run time module for monitoring system calls from 

applications associated with one or more containers and for providing control of the one or more 

applications.

For example, HPE Ezmeral Runtime Enterprise includes either the Docker or containerd runtime 

module. For another example, Kubernetes uses the Linux kernel’s seccomp mode to monitor and 

control system calls made from a container.

See, e.g.:

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 49 of 52 PageID #:

5671
Page 49 of 51

Claim 31 Accused Instrumentalities

https://docs.ezmeral.hpe.com/runtimeenterprise/56/reference/kubernetes/hewlett_packard_enterprise_distributions_of_kubernetes.html

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 50 of 52 PageID #:

5672
Page 50 of 51

Claim 31 Accused Instrumentalities

https://kubernetes.io/docs/setup/production-environment/container-runtimes/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 51 of 52 PageID #:

5673
Page 51 of 51

Claim 31 Accused Instrumentalities

https://kubernetes.io/docs/tutorials/security/seccomp/

Case 2:24-cv-00093-JRG Document 106-3 Filed 11/22/24 Page 52 of 52 PageID #:

5674