Exhibit 4

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 1 of 53 PageID #:

5869
Page 1 of 52

U.S. Patent No. 7,784,058 (“’058 Patent”)

Accused Instrumentalities: IBM products and services using user mode critical system elements as shared libraries, including without 

limitation IBM Cloud Kubernetes Service (IKS), IBM Cloud Private (ICP), and IBM Hybrid Cloud mesh,, 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. 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://www.ibm.com/products/kubernetes-service

https://www.ibm.com/products/kubernetes-service

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 2 of 53 PageID #:

5870
Page 2 of 52

Claim 1 Accused Instrumentalities

https://developer.ibm.com/articles/true-benefits-of-moving-to-containers-1/

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

See, e.g.:

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 3 of 53 PageID #:

5871
Page 3 of 52

Claim 1 Accused Instrumentalities

https://www.ibm.com/topics/containers

https://www.ibm.com/blog/containers-vs-vms/

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 4 of 53 PageID #:

5872
Page 4 of 52

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://www.ibm.com/topics/containerization

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 5 of 53 PageID #:

5873
Page 5 of 52

Claim 1 Accused Instrumentalities

https://en.wikipedia.org/wiki/Glibc

[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://cloud.ibm.com/docs/containers?topic=containers-images

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 6 of 53 PageID #:

5874
Page 6 of 52

Claim 1 Accused Instrumentalities

https://cloud.ibm.com/docs/Registry?topic=Registry-va_index&interface=ui

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 7 of 53 PageID #:

5875
Page 7 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 8 of 53 PageID #:

5876
Page 8 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 9 of 53 PageID #:

5877
Page 9 of 52

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 10 of 53 PageID #:

5878
Page 10 of 52

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 111-4 Filed 12/05/24 Page 11 of 53 PageID #:

5879
Page 11 of 52

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 111-4 Filed 12/05/24 Page 12 of 53 PageID #:

5880
Page 12 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 13 of 53 PageID #:

5881
Page 13 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 14 of 53 PageID #:

5882
Page 14 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 15 of 53 PageID #:

5883
Page 15 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 16 of 53 PageID #:

5884
Page 16 of 52

Claim 1 Accused Instrumentalities

https://www.ibm.com/topics/docker

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 17 of 53 PageID #:

5885
Page 17 of 52

Claim 1 Accused Instrumentalities

https://ibm.github.io/kube101/

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 18 of 53 PageID #:

5886
Page 18 of 52

Claim 1 Accused Instrumentalities

https://en.wikipedia.org/wiki/Glibc

[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 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.

See, e.g.:

https://cloud.ibm.com/docs/containers?topic=containers-images

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 19 of 53 PageID #:

5887
Page 19 of 52

Claim 1 Accused Instrumentalities

https://www.ibm.com/topics/docker

https://www.ibm.com/docs/en/product-master/12.0.0?topic=deployment-installing-product-by-usingdocker-images

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 20 of 53 PageID #:

5888
Page 20 of 52

Claim 1 Accused Instrumentalities

https://hub.docker.com/search?image_filter=official&type=image&q=

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 21 of 53 PageID #:

5889
Page 21 of 52

Claim 1 Accused Instrumentalities

https://docs.docker.com/engine/install/

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

https://www.ibm.com/topics/docker

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 22 of 53 PageID #:

5890
Page 22 of 52

Claim 1 Accused Instrumentalities

https://docs.docker.com/glossary/#image

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 23 of 53 PageID #:

5891
Page 23 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 24 of 53 PageID #:

5892
Page 24 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 25 of 53 PageID #:

5893
Page 25 of 52

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 26 of 53 PageID #:

5894
Page 26 of 52

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 111-4 Filed 12/05/24 Page 27 of 53 PageID #:

5895
Page 27 of 52

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 111-4 Filed 12/05/24 Page 28 of 53 PageID #:

5896
Page 28 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 29 of 53 PageID #:

5897
Page 29 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 30 of 53 PageID #:

5898
Page 30 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 31 of 53 PageID #:

5899
Page 31 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 32 of 53 PageID #:

5900
Page 32 of 52

Claim 1 Accused Instrumentalities

[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 running 

under the operating system 

have use of a unique instance 

of a corresponding critical 

system element for performing 

same function, and

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 or Kubernetes 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 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 image includes essential system files, 

libraries, and dependencies required to run the software application within the container. The 

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 or Kubernetes 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.:

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 33 of 53 PageID #:

5901
Page 33 of 52

Claim 1 Accused Instrumentalities

https://www.ibm.com/topics/docker

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 34 of 53 PageID #:

5902
Page 34 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 35 of 53 PageID #:

5903
Page 35 of 52

Claim 1 Accused Instrumentalities

https://www.ibm.com/topics/docker

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 36 of 53 PageID #:

5904
Page 36 of 52

Claim 1 Accused Instrumentalities

https://ibm.github.io/kube101/

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 37 of 53 PageID #:

5905
Page 37 of 52

Claim 1 Accused Instrumentalities

[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 or Kubernetes containers, each container operates independently, and a 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 an image is used to create a container in the 

Accused Instrumentality, an instance of 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

https://www.ibm.com/topics/docker

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 38 of 53 PageID #:

5906
Page 38 of 52

Claim 1 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 39 of 53 PageID #:

5907
Page 39 of 52

Claim 1 Accused Instrumentalities

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

Claim 2

Claim 2 Accused Instrumentalities

2. A computing system as 

defined in claim 1, wherein in 

operation, multiple instances of 

an SLCSE stored in the shared 

library run simultaneously 

within the operating system.

Each Accused Instrumentality comprises or constitutes a computing system as defined in claim 1, 

wherein in operation, multiple instances of an SLCSE stored in the shared library run 

simultaneously within the operating system.

For example, an individual host/node runs multiple containers and/or pods simultaneously, each of 

which has an instance of an SLCSE.

See, e.g.:

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 40 of 53 PageID #:

5908
Page 40 of 52

Claim 2 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 41 of 53 PageID #:

5909
Page 41 of 52

Claim 2 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 42 of 53 PageID #:

5910
Page 42 of 52

Claim 2 Accused Instrumentalities

https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 43 of 53 PageID #:

5911
Page 43 of 52

Claim 2 Accused Instrumentalities

https://docs.docker.com/engine/reference/run/

Claim 3

Claim 3 Accused Instrumentalities

3. A computing system 

according to claim 1 wherein 

OSCSEs corresponding to and 

capable of performing the same 

function as SLCSEs remain in 

the operating system kernel.

Each Accused Instrumentality comprises or constitutes a computing system according to claim 1 

wherein OSCSEs corresponding to and capable of performing the same function as SLCSEs remain in 

the operating system kernel.

For example, both Docker and Kubernetes systems preserve the host kernel substantially unchanged; 

therefore the OSCSEs corresponding to the SLCSEs remain in the operating system kernel.

See, e.g.:

https://cloud.ibm.com/docs/containers?topic=containers-images

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 44 of 53 PageID #:

5912
Page 44 of 52

Claim 3 Accused Instrumentalities

https://cloud.ibm.com/docs/Registry?topic=Registry-va_index&interface=ui

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 45 of 53 PageID #:

5913
Page 45 of 52

Claim 3 Accused Instrumentalities

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

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 46 of 53 PageID #:

5914
Page 46 of 52

Claim 3 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 47 of 53 PageID #:

5915
Page 47 of 52

Claim 3 Accused Instrumentalities

https://ibm.github.io/kube101/

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 48 of 53 PageID #:

5916
Page 48 of 52

Claim 4

Claim 4 Accused Instrumentalities

4. A computing system 

according to claim 1 wherein 

the one or more SLCSEs 

provided to one of the plurality 

of software applications having 

exclusive use thereof, use 

system calls to access services 

in the operating system kernel.

Each Accused Instrumentality comprises or constitutes a computing system according to claim 1 

wherein the one or more SLCSEs provided to one of the plurality of software applications having 

exclusive use thereof, use system calls to access services in the operating system kernel.

For example, the SLCSEs in a container use system calls to access services in the operating system 

kernel. For example, the glibc library (or other similar library) in the container uses system calls to 

interface with the host Linux kernel. In general, system calls can be observed using a tool such as 

strace.

See, e.g.:

https://en.wikipedia.org/wiki/Glibc

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 49 of 53 PageID #:

5917
Page 49 of 52

https://www.berops.com/blog/a-different-method-to-debug-kubernetes-pods

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 50 of 53 PageID #:

5918
Page 50 of 52

Claim 18

Claim 18 Accused Instrumentalities

18. A computer system as 

defined in claim 2 wherein 

SLCSEs are not copies of 

OSCSEs.

Each Accused Instrumentality comprises or constitutes a computer system as defined in claim 2 

wherein SLCSEs are not copies of OSCSEs.

For example, in a typical case the SLCSEs come from a Linux distribution independent of the host 

operating system, and thus are not identical to the OSCSEs. For another example, the SLCSEs are 

provided to the computer system through a separate process than the process by which the OSCSEs 

are provided to the computer system, and thus are not copied from the OSCSEs.

See, e.g.:

https://www.ibm.com/topics/containers

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 51 of 53 PageID #:

5919
Page 51 of 52

Claim 18 Accused Instrumentalities

https://www.ibm.com/blog/containers-vs-vms/

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

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 52 of 53 PageID #:

5920
Page 52 of 52

Claim 18 Accused Instrumentalities

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

Case 2:24-cv-00093-JRG Document 111-4 Filed 12/05/24 Page 53 of 53 PageID #:

5921