EXHIBIT D

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 1 of 75 PageID #: 4688
Page 1 of 108

U.S. Patent No. 8,406,733 (“’733 Patent”)

Accused Devices: Samsung’s mobile electronic devices (e.g., Galaxy phones and tablets, as well as Samsung devices which include Samsung Knox 

functionality), and Samsung Tizen devices (e.g., TVs and wearables), and all versions and variations thereof since the issuance of the asserted patent.

Claim 1

Issued Claim(s) Public Documentation

1[pre] An end-user device comprising: Samsung Galaxy phones and tablets and Samsung Tizen based devices are each “an end-user 

device.” For example, the Galaxy S22 is a mobile device. See e.g., 

https://www.samsung.com/us/smartphones/galaxy-s22/;

As another example, Samsung’s Tizen based devices are user devices. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 2 of 75 PageID #: 4689
Page 2 of 108

https://www.samsung.com/us/televisions-home-theater/tvs/the-frame/55-class-the-frame-qled4k-smart-tv-2022-qn55ls03bafxza/. 

1[a] a modem for enabling 

communication with a network system 

over a service control link provided by 

the network system over a wireless 

access network, the service control link 

secured by an encryption protocol and 

configured to support control-plane 

communications between the network 

system and a service control device link 

agent on the end-user device;

Samsung Galaxy phones and tablets and Samsung’s Tizen based devices comprise “a modem 

for enabling communication with a network system over a service control link provided by the 

network system over a wireless access network, the service control link secured by an 

encryption protocol and configured to support control-plane communications between the 

network system and a service control device link agent on the end-user device.”

For example, the Galaxy S22 includes a plurality of wireless modems for communicating with a 

network system over a wi-fi network and/or a cellular network (a “wireless access network”).

See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 3 of 75 PageID #: 4690
Page 3 of 108

https://www.samsung.com/us/smartphones/galaxy-s22/models/.

Samsung Galaxy phones and tablets use encryption protocols, e.g., using encryption keys, 

signatures, secure buses, etc., to secure communications between the device and the network 

system. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 4 of 75 PageID #: 4691
Page 4 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 5 of 75 PageID #: 4692
Page 5 of 108

https://www.samsung.com/us/security/;

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 6 of 75 PageID #: 4693
Page 6 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 7 of 75 PageID #: 4694
Page 7 of 108

https://firebase.google.com/docs/cloud-messaging/fcm-architecture; 

https://firebase.google.com/docs/cloud-messaging/conceptoptions#encryption_for_data_messages. 

As another example, Samsung’s Tizen based devices include wireless modems for 

communicating with a network system over a wi-fi network (a “wireless access network”). See 

e.g., 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 8 of 75 PageID #: 4695
Page 8 of 108

https://www.samsung.com/us/televisions-home-theater/tvs/the-frame/55-class-the-frame-qled4k-smart-tv-2022-qn55ls03bafxza/#specs;

https://downloadcenter.samsung.com/content/UM/202203/20220303092001587/OSNATSCB3.2.0_EM_Oscar_Pontus_Nike_Kant-SU2e_USA_ENG_220216.0.pdf. 

Further, Samsung’s Tizen based devices use encryption protocols, e.g., using encryption keys, 

signatures, secure buses, etc., to secure communications between the device and the network 

system. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 9 of 75 PageID #: 4696
Page 9 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 10 of 75 PageID #:

4697
Page 10 of 108

https://docs.tizen.org/application/native/guides/messaging/push/#connect; 

https://docs.tizen.org/application/native/guides/security/overview/. 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 11 of 75 PageID #:

4698
Page 11 of 108

As another example, Samsung’s devices operating in the Samsung Knox ecosystem, for example 

mobile phones and other devices enrolled in the Samsung Knox MDM platform, include 

modems for communicating with a network system over a service control link secured by 

encryption protocols, e.g., using encryption keys, signatures, secure buses, etc., programmed 

into the Samsung Knox MDM platform and e.g., Samsung Knox end-user device software for 

secure communications with a network system:

https://docs.samsungknox.com/admin/fundamentals/welcome.htm

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 12 of 75 PageID #:

4699
Page 12 of 108

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

As a further example, the communications link Samsung Knox Manage servers or Knox MDM 

platform and devices being managed by such servers or MDM platform, for example including 

the Knox workspace devices, Android devices, iOS devices, Chrome OS devices, and Windows 

devices illustrated above, comprise a “service control link” (e.g., a communication link between 

the server and device) Data and messages transmitted over the secure control link between the 

Samsung Knox Manage servers or Knox MDM platform and managed devices is encrypted, and 

commands and notifications transmitted from such servers to devices are “agent messages.”

These agent messages are received by “service control device link agent[s],” e.g., software on 

the device, such as the Knox Manage (KM) agent on Samsung’s devices.

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 13 of 75 PageID #:

4700
Page 13 of 108

As a further example, the communications link between Samsung’s Tizen servers and Tizen OS 

devices, and Firebase messaging servers and Samsung’s Android devices, comprises a “service 

control link.” Notifications, data, and messages transmitted over these service control links from 

such servers to devices are encrypted, as illustrated above, and are “agent messages.” These 

agent messages are received by “service control device link agent[s],” e.g., software on the 

device, such as Samsung’s Tizen software running on Samsung’s devices.

As a further example, Samsung’s Knox MDM platform, Knox Manage servers and Tizen 

servers are all examples of servers which provide control-plane communications (e.g., links

between the device agents related to various aspects of device based network service policy 

implementation). and which are service control server link elements, including because they 

control, manage, and apply service policies to user devices to which they are connected. 

As a further example, devices managed by Samsung Knox Manage or the Knox MDM platform 

are managed by software including specific end-user device applications and software, such as 

the Knox Manage (KM) agent on such devices (see, e.g., 

https://docs.samsungknox.com/admin/knox-manage/enroll-a-single-device.htm).

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 14 of 75 PageID #:

4701
Page 14 of 108

1[b] a plurality of device agents 

communicatively coupled to the service 

control device link agent through an 

agent communication bus, each of the 

plurality of device agents identifiable by 

an associated device agent identifier; and

Samsung Galaxy phones and tablets and Samsung’s Tizen based devices comprise “a plurality 

of device agents communicatively coupled to the service control device link agent through an 

agent communication bus, each of the plurality of device agents identifiable by an associated 

device agent identifier.”

For example, Samsung Galaxy phones and tablets comprise multiple device agents (e.g., 

operating system software and/or applications) which have an identifier. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 15 of 75 PageID #:

4702
Page 15 of 108

https://firebase.google.com/docs/cloud-messaging/android/client; 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 16 of 75 PageID #:

4703
Page 16 of 108

https://firebase.google.com/docs/cloud-messaging/android/receive;

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 17 of 75 PageID #:

4704
Page 17 of 108

https://developers.google.com/instance-id. 

For further example, Samsung’s Tizen based devices comprise multiple device agents (e.g., 

operating system software and/or applications) which have an identifier. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 18 of 75 PageID #:

4705
Page 18 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 19 of 75 PageID #:

4706
Page 19 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 20 of 75 PageID #:

4707
Page 20 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 21 of 75 PageID #:

4708
Page 21 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 22 of 75 PageID #:

4709
Page 22 of 108

https://docs.tizen.org/application/web/guides/messaging/push/;

https://www.samsung.com/hk_en/support/apps-services/how-do-i-enable-push-notificationsfrom-galaxy-store/. 

As another example, Samsung’s devices operating in the Samsung Knox ecosystem, for example 

mobile phones and other devices enrolled in the Samsung Knox MDM platform, comprise 

multiple device agents which have an identifier.

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 23 of 75 PageID #:

4710
Page 23 of 108

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 24 of 75 PageID #:

4711
Page 24 of 108

https://docs.samsungknox.com/admin/knox-configure/updating-an-existing-device-profile.htm

As a further illustration, the service control device link agents on Samsung’s devices are coupled 

to various other device agents within the device by way of the Android operating system 

through an agent communication bus (e.g., communication path for various agents and functions 

to communicate over). That communication structure allows for intercommunication between 

agents in the device, and enables the service control device link agents to send messages to (and 

control) behavior of other components within the system. The communications bus connecting 

device agents to the service control device link agents need not be internal to the device, and the 

communications channel between Samsung Knox and MDM servers and managed devices is an 

example of such a communications bus. 

1[c] memory configured to store an 

encryption key, the encryption key 

shared between the service control device 

link agent and a service control server 

link element of the network system;

Samsung Galaxy phones and tablets and Samsung’s Tizen based devices comprise “memory 

configured to store an encryption key, the encryption key shared between the service control 

device link agent and a service control server link element of the network system.”

For example, Samsung Galaxy phones and tablets include memory that stores an encryption key 

(e.g. keys, tokens, or signatures used by device and server to encrypt communications, such as 

public/private keys, shared keys, partially shared keys, symmetric and/or asymmetric 

encryption, etc., such as those used in transport layer encryption, end-to-end encryption, pointto-point encryption, etc.) that is shared between the agent and the network system. See, e.g., 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 25 of 75 PageID #:

4712
Page 25 of 108

https://www.samsung.com/us/smartphones/galaxy-s22/models/; 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 26 of 75 PageID #:

4713
Page 26 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 27 of 75 PageID #:

4714
Page 27 of 108

https://www.samsung.com/us/security/;

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 28 of 75 PageID #:

4715
Page 28 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 29 of 75 PageID #:

4716
Page 29 of 108

https://firebase.google.com/docs/cloud-messaging/fcm-architecture; 

https://firebase.google.com/docs/cloud-messaging/conceptoptions#encryption_for_data_messages. 

As another example, Samsung’s Tizen based devices include memory that stores an encryption 

key (e.g. keys, tokens, or signatures used by device and server to encrypt communications, such 

as public/private keys, shared keys, partially shared keys, symmetric and/or asymmetric 

encryption, etc., such as those used in transport layer encryption, end-to-end encryption, pointto-point encryption, etc.) that is shared between the agent and the network system. See e.g.:

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 30 of 75 PageID #:

4717
Page 30 of 108

https://www.samsung.com/us/televisions-home-theater/tvs/the-frame/55-class-the-frame-qled4k-smart-tv-2022-qn55ls03bafxza/#specs;

https://downloadcenter.samsung.com/content/UM/202203/20220303092001587/OSNATSCB3.2.0_EM_Oscar_Pontus_Nike_Kant-SU2e_USA_ENG_220216.0.pdf;

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 31 of 75 PageID #:

4718
Page 31 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 32 of 75 PageID #:

4719
Page 32 of 108

https://docs.tizen.org/application/native/guides/messaging/push/#connect; 

https://docs.tizen.org/application/native/guides/security/overview/.

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 33 of 75 PageID #:

4720
Page 33 of 108

As another example, Samsung’s devices operating in the Samsung Knox ecosystem, for example 

mobile phones and other devices enrolled in the Samsung Knox MDM platform, include 

memory that stores an encryption key (e.g. keys, tokens, or signatures used by device and server 

to encrypt communications, such as public/private keys, shared keys, partially shared keys, 

symmetric and/or asymmetric encryption, etc., such as those used in transport layer encryption, 

end-to-end encryption, point-to-point encryption, etc.) that is shared between the agent and the 

network system.

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 34 of 75 PageID #:

4721
Page 34 of 108

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

On information and belief, Samsung owns and operates its own push messaging servers, 

including servers for communicating with the Samsung Push Service software on its end user 

devices. See, e.g., 

https://play.google.com/store/apps/details?id=com.sec.spp.push&hl=en_US&gl=US&pli=1; 

https://www.lifewire.com/samsung-push-service-4165507. On information and belief, Samsung 

includes applications in its user devices, such as the “Shop Samsung” and “Galaxy Store” 

applications, which cause notifications (including marketing notifications) to be sent to user 

devices via Samsung’s push messaging servers. See, e.g.:

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 35 of 75 PageID #:

4722
Page 35 of 108

Upon information and belief, the information needed for encryption/decryption of messages 

between nodes and devices in the architecture of the systems used with Samsung’s Accused 

Products are all stored in memory, which is a standard and conventional practice for how 

information needed to, for example, decrypt incoming communications or messages or to 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 36 of 75 PageID #:

4723
Page 36 of 108

authenticate that a given message received from an external source (such as another part of the 

network of devices) is to be trusted.

1[d] wherein the service control device 

link agent is configured to: receive, over 

the service control link, an encrypted 

agent message from the service control 

server link element,

Samsung Galaxy phones and tablets and Samsung’s Tizen based devices comprise a “service 

control device link agent [which] is configured to: receive, over the service control link, an 

encrypted agent message from the service control server link element.”

For example, Samsung Galaxy phones and tablets receive encrypted messages (e.g., messages 

and/or payloads) from a server using software on the device, such as the operating system or 

applications on the device, to receive messages, notifications, payloads, etc. The server and See 

e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 37 of 75 PageID #:

4724
Page 37 of 108

https://firebase.google.com/docs/cloud-messaging/android/client; 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 38 of 75 PageID #:

4725
Page 38 of 108

https://firebase.google.com/docs/cloud-messaging/android/receive;

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 39 of 75 PageID #:

4726
Page 39 of 108

https://developers.google.com/instance-id. 

For further example, Samsung’s Tizen based devices receive encrypted messages from a server. 

See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 40 of 75 PageID #:

4727
Page 40 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 41 of 75 PageID #:

4728
Page 41 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 42 of 75 PageID #:

4729
Page 42 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 43 of 75 PageID #:

4730
Page 43 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 44 of 75 PageID #:

4731
Page 44 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 45 of 75 PageID #:

4732
Page 45 of 108

https://docs.tizen.org/application/web/guides/messaging/push/.

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 46 of 75 PageID #:

4733
Page 46 of 108

As another example, Samsung’s devices operating in the Samsung Knox ecosystem, for example 

mobile phones and other devices enrolled in the Samsung Knox MDM platform, receive 

encrypted messages from a server.

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 47 of 75 PageID #:

4734
Page 47 of 108

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

On information and belief, Samsung owns and operates its own push messaging servers, 

including servers for communicating with the Samsung Push Service software on its end user 

devices. See, e.g., 

https://play.google.com/store/apps/details?id=com.sec.spp.push&hl=en_US&gl=US&pli=1; 

https://www.lifewire.com/samsung-push-service-4165507. On information and belief, Samsung 

includes applications in its user devices, such as the “Shop Samsung” and “Galaxy Store” 

applications, which cause notifications (including marketing notifications) to be sent to user 

devices via Samsung’s push messaging servers. See, e.g.:

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 48 of 75 PageID #:

4735
Page 48 of 108

For avoidance of doubt, service control server link element

1[e] using the encryption key, obtain a 

decrypted agent message, the decrypted 

Samsung Galaxy phones and tablets and Samsung’s Tizen based devices “us[e] the encryption 

key, obtain a decrypted agent message, the decrypted agent message comprising a particular 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 49 of 75 PageID #:

4736
Page 49 of 108

agent message comprising a particular 

agent identifier and message content for 

delivery to a particular device agent of 

the plurality of device agents, the 

particular agent identifier identifying the 

particular device agent, the message 

content from a particular server of a 

plurality of servers communicatively 

coupled to the service control server link 

element, and

agent identifier and message content for delivery to a particular device agent of the plurality of 

device agents, the particular agent identifier identifying the particular device agent, the message 

content from a particular server of a plurality of servers communicatively coupled to the service 

control server link element.”

For example, Samsung Galaxy phones and tablets decrypt messages from a plurality of servers 

which have identifiers and content for delivery to particular device agents. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 50 of 75 PageID #:

4737
Page 50 of 108

https://firebase.google.com/docs/cloud-messaging/android/client; 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 51 of 75 PageID #:

4738
Page 51 of 108

https://firebase.google.com/docs/cloud-messaging/android/receive;

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 52 of 75 PageID #:

4739
Page 52 of 108

https://developers.google.com/instance-id. 

For further example, Samsung’s Tizen based devices receive encrypted messages from a server. 

See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 53 of 75 PageID #:

4740
Page 53 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 54 of 75 PageID #:

4741
Page 54 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 55 of 75 PageID #:

4742
Page 55 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 56 of 75 PageID #:

4743
Page 56 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 57 of 75 PageID #:

4744
Page 57 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 58 of 75 PageID #:

4745
Page 58 of 108

https://docs.tizen.org/application/web/guides/messaging/push/.

As another example, Samsung’s devices operating in the Samsung Knox ecosystem, for example 

mobile phones and other devices enrolled in the Samsung Knox MDM platform, decrypt 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 59 of 75 PageID #:

4746
Page 59 of 108

messages from a plurality of servers which have identifiers and content for delivery to particular 

device agents. 

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 60 of 75 PageID #:

4747
Page 60 of 108

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

1[f] based on the particular agent 

identifier, deliver the message content to 

the particular device agent over the agent 

communication bus.

Samsung Galaxy phones and tablets and Samsung’s Tizen based devices “based on the 

particular agent identifier, deliver the message content to the particular device agent over the 

agent communication bus.”

For example, Samsung Galaxy phones and tablets deliver message content to particular device 

agents based on identifier. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 61 of 75 PageID #:

4748
Page 61 of 108

https://firebase.google.com/docs/cloud-messaging/android/client; 

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 62 of 75 PageID #:

4749
Page 62 of 108

https://firebase.google.com/docs/cloud-messaging/android/receive;

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 63 of 75 PageID #:

4750
Page 63 of 108

https://developers.google.com/instance-id. 

For further example, Samsung’s Tizen based devices deliver message content to particular 

device agents based on identifier. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 64 of 75 PageID #:

4751
Page 64 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 65 of 75 PageID #:

4752
Page 65 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 66 of 75 PageID #:

4753
Page 66 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 67 of 75 PageID #:

4754
Page 67 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 68 of 75 PageID #:

4755
Page 68 of 108

decrypt messages from a plurality of servers which have identifiers and content for delivery to 

particular device agents.

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 69 of 75 PageID #:

4756
Page 69 of 108

https://docs.tizen.org/application/web/guides/messaging/push/.

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 70 of 75 PageID #:

4757
Page 70 of 108

As another example, Samsung’s devices operating in the Samsung Knox ecosystem, for example 

mobile phones and other devices enrolled in the Samsung Knox MDM platform, deliver 

message content to particular device agents based on identifier.

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 71 of 75 PageID #:

4758
Page 71 of 108

https://docs.samsungknox.com/admin/knox-manage/welcome.htm

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 72 of 75 PageID #:

4759
Page 72 of 108

https://docs.samsungknox.com/admin/knox-configure-wearables/update-existing-profile.htm

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 73 of 75 PageID #:

4760
Page 73 of 108

On information and belief, Samsung owns and operates its own push messaging servers, 

including servers for communicating with the Samsung Push Service software on its end user 

devices. See, e.g., 

https://play.google.com/store/apps/details?id=com.sec.spp.push&hl=en_US&gl=US&pli=1; 

https://www.lifewire.com/samsung-push-service-4165507. On information and belief, Samsung 

includes applications in its user devices, such as the “Shop Samsung” and “Galaxy Store” 

applications, which cause notifications (including marketing notifications) to be sent to user 

devices via Samsung’s push messaging servers. See, e.g.:

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 74 of 75 PageID #:

4761
Page 74 of 108

Case 2:23-cv-00103-JRG-RSP Document 96-5 Filed 06/13/24 Page 75 of 75 PageID #:

4762