EXHIBIT 1 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 1 of 83 PageID #
Page 1 of 82

Exhibit C - U.S. Patent No. 9,615,192 (“’192 Patent”)

Accused Devices: Samsung’s push messaging servers (e.g., Samsung’s Knox and Tizen servers), and all versions and variations thereof since the 

issuance of the asserted patent.

Claim 1

Issued Claim(s) Public Documentation

[1pre]. A message link server 

comprising: 

Samsung’s push messaging servers are each “message link server[s].” See, e.g.,

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 2 of 83 PageID #: 2251
Page 2 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 3 of 83 PageID #: 2252
Page 3 of 82

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

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 4 of 83 PageID #: 2253
Page 4 of 82

https://docs.samsungknox.com/admin/knox-manage/km-features.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” 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 5 of 83 PageID #: 2254
Page 5 of 82

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 79-1 Filed 03/19/24 Page 6 of 83 PageID #: 2255
Page 6 of 82

[1a] a transport services stack to maintain 

a respective secure message link through 

an Internet network between the message 

link server and a respective device link 

agent on each of a plurality of wireless 

end-user devices, each of the wireless 

end-user devices comprising multiple 

software components authorized to 

receive and process data from secure 

message link messages received via a 

device link agent on that device; 

Samsung’s push messaging servers comprise “a transport services stack to maintain a respective 

secure message link through an Internet network between the message link server and a 

respective device link agent on each of a plurality of wireless end-user devices, each of the 

wireless end-user devices comprising multiple software components authorized to receive and 

process data from secure message link messages received via a device link agent on that 

device.” 

For example, Samsung’s push messaging server maintains a secure message link between the 

Tizen Push Server and a device link agent (e.g., Tizen App and/or Push Service) on a plurality 

of devices which comprise multiple software components and receive/process data from 

messages sent over the secure message link. See, e.g.,

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 7 of 83 PageID #: 2256
Page 7 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 8 of 83 PageID #: 2257
Page 8 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 9 of 83 PageID #: 2258
Page 9 of 82

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 and the 

Samsung Knox servers managing those phones and devices, maintains a secure message link 

between the server and a device link agent on a plurality of devices which comprise multiple 

software components and receive/process data from messages sent over the secure message link.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 10 of 83 PageID #:

2259
Page 10 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 11 of 83 PageID #:

2260
Page 11 of 82

https://docs.samsungknox.com/admin/knox-manage/km-features.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” 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 12 of 83 PageID #:

2261
Page 12 of 82

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 79-1 Filed 03/19/24 Page 13 of 83 PageID #:

2262
Page 13 of 82

[1b] an interface to a network to receive 

network element messages from a 

plurality of network elements, the 

received network element messages 

comprising respective message content 

and requests for delivery of the 

respective message content to respective 

wireless end-user devices, the respective 

message content including data for, and 

an identification of, a respective one of 

the authorized software components; and

Samsung’s push messaging servers comprise “an interface to a network to receive network 

element messages from a plurality of network elements, the received network element messages 

comprising respective message content and requests for delivery of the respective message 

content to respective wireless end-user devices, the respective message content including data 

for, and an identification of, a respective one of the authorized software components.” 

For example, Samsung’s push messaging servers receive messages from a plurality of network 

elements (e.g., App Servers) which comprise content and delivery requests to devices and 

software components. See, e.g.,

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 14 of 83 PageID #:

2263
Page 14 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 15 of 83 PageID #:

2264
Page 15 of 82

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

https://docs.tizen.org/application/native/guides/messaging/push-server/; 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 16 of 83 PageID #:

2265
Page 16 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 17 of 83 PageID #:

2266
Page 17 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 18 of 83 PageID #:

2267
Page 18 of 82

As another example, Samsung’s receive messages from a plurality of network elements (e.g.,

App Servers) which comprise content and delivery requests to devices and software components 

in the Knox ecosystem.

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 19 of 83 PageID #:

2268
Page 19 of 82

https://docs.samsungknox.com/admin/knox-manage/km-features.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” 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 20 of 83 PageID #:

2269
Page 20 of 82

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 79-1 Filed 03/19/24 Page 21 of 83 PageID #:

2270
Page 21 of 82

[1c] a message buffer system including a 

memory and logic,

The Accused Devices include “a message buffer system including a memory and logic.”

For example, Samsung’s push messaging servers include memory to store messages and logic.

See e.g.,

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 22 of 83 PageID #:

2271
Page 22 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 23 of 83 PageID #:

2272
Page 23 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 24 of 83 PageID #:

2273
Page 24 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 25 of 83 PageID #:

2274
Page 25 of 82

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

As another example, Samsung’s Knox servers include memory to store messages and logic.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 26 of 83 PageID #:

2275
Page 26 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 27 of 83 PageID #:

2276
Page 27 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 28 of 83 PageID #:

2277
Page 28 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 29 of 83 PageID #:

2278
Page 29 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 30 of 83 PageID #:

2279
Page 30 of 82

https://docs.samsungknox.com/admin/knox-manage/set-the-profile-update-schedule.htm. 

[1d] the memory to buffer content from 

the received network element messages 

for which delivery is requested to a given 

one of the wireless end-user devices,

The Accused Devices include “the memory to buffer content from the received network element 

messages for which delivery is requested to a given one of the wireless end-user devices.”

For example, Samsung’s push messaging servers include memory to store content from received 

messages for delivery to a device. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 31 of 83 PageID #:

2280
Page 31 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 32 of 83 PageID #:

2281
Page 32 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 33 of 83 PageID #:

2282
Page 33 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 34 of 83 PageID #:

2283
Page 34 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 35 of 83 PageID #:

2284
Page 35 of 82

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

As another example, Samsung’s Knox servers include memory to store content from received 

messages for delivery to a device.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 36 of 83 PageID #:

2285
Page 36 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 37 of 83 PageID #:

2286
Page 37 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 38 of 83 PageID #:

2287
Page 38 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 39 of 83 PageID #:

2288
Page 39 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 40 of 83 PageID #:

2289
Page 40 of 82

https://docs.samsungknox.com/admin/knox-manage/set-the-profile-update-schedule.htm. 

[1e] the logic to determine when one of a 

plurality of message delivery triggers for 

the given one of the wireless end-user 

devices has occurred, wherein for at least 

some of the received network element 

messages, the receipt of such a message 

by the message buffer system is not a 

The Accused Devices include “the logic to determine when one of a plurality of message 

delivery triggers for the given one of the wireless end-user devices has occurred, wherein for at 

least some of the received network element messages, the receipt of such a message by the 

message buffer system is not a message delivery trigger, and for at least one of the message 

delivery triggers, the trigger is an occurrence of an asynchronous event with time-critical 

messaging needs.”

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 41 of 83 PageID #:

2290
Page 41 of 82

message delivery trigger, and for at least 

one of the message delivery triggers, the 

trigger is an occurrence of an 

asynchronous event with time-critical 

messaging needs, and

For example, Samsung’s push messaging servers include logic to determine whether a delivery 

trigger that is not based on the receipt of the message has occurred. See e.g.,

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 42 of 83 PageID #:

2291
Page 42 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 43 of 83 PageID #:

2292
Page 43 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 44 of 83 PageID #:

2293
Page 44 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 45 of 83 PageID #:

2294
Page 45 of 82

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

As another example, Samsung’s Knox servers include logic to determine whether a delivery 

trigger that is not based on the receipt of the message has occurred.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 46 of 83 PageID #:

2295
Page 46 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 47 of 83 PageID #:

2296
Page 47 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 48 of 83 PageID #:

2297
Page 48 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 49 of 83 PageID #:

2298
Page 49 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 50 of 83 PageID #:

2299
Page 50 of 82

https://docs.samsungknox.com/admin/knox-manage/set-the-profile-update-schedule.htm. 

[1f] upon determining that one of the 

message delivery triggers has occurred, 

the logic further to supply one or more 

messages comprising the buffered 

content to the transport services stack for 

delivery on the secure message link 

maintained between the transport 

The Accused Devices include “upon determining that one of the message delivery triggers has 

occurred, the logic further to supply one or more messages comprising the buffered content to 

the transport services stack for delivery on the secure message link maintained between the 

transport services stack and a device link agent on the given one of the wireless end-user 

devices.”

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 51 of 83 PageID #:

2300
Page 51 of 82

services stack and a device link agent on 

the given one of the wireless end-user 

devices.

For example, Samsung’s push messaging servers comprise logic which supplies buffered 

content for delivery. See e.g.,

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 52 of 83 PageID #:

2301
Page 52 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 53 of 83 PageID #:

2302
Page 53 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 54 of 83 PageID #:

2303
Page 54 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 55 of 83 PageID #:

2304
Page 55 of 82

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

As another example, Samsung’s Knox servers comprise logic which supplies buffered content 

for delivery.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 56 of 83 PageID #:

2305
Page 56 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 57 of 83 PageID #:

2306
Page 57 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 58 of 83 PageID #:

2307
Page 58 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 59 of 83 PageID #:

2308
Page 59 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 60 of 83 PageID #:

2309
Page 60 of 82

https://docs.samsungknox.com/admin/knox-manage/set-the-profile-update-schedule.htm. 

Claim 2

2. The message link server of claim 1, 

further comprising an encrypt function to 

encrypt the one or more messages 

supplied to the transport services stack 

The Accused Devices comprise the “message link server of claim 1, further comprising an 

encrypt function to encrypt the one or more messages supplied to the transport services stack for 

delivery on the secure message link maintained between the message link server and the device 

link agent on the given one of the wireless end-user devices.”

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 61 of 83 PageID #:

2310
Page 61 of 82

for delivery on the secure message link 

maintained between the message link 

server and the device link agent on the 

given one of the wireless end-user 

devices.

For example, the message link servers of the accused instrumentalities use encryption protocols 

to secure communications between the device and the network system. See e.g.,

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 62 of 83 PageID #:

2311
Page 62 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 63 of 83 PageID #:

2312
Page 63 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 64 of 83 PageID #:

2313
Page 64 of 82

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

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 65 of 83 PageID #:

2314
Page 65 of 82

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 66 of 83 PageID #:

2315
Page 66 of 82

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

The messages passed between servers of the accused instrumentalities and end user devices are 

also secured. As another example, the Tizen Push Server receives encrypted information from 

app servers and transmits such encrypted information on to device messaging agents residing on 

user devices, which in turn decrypt received messages. 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 67 of 83 PageID #:

2316
Page 67 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 68 of 83 PageID #:

2317
Page 68 of 82

https://docs.tizen.org/application/native/guides/messaging/push/#managing-security

As another example, the Firebase framework encrypts messages in transit. See: 

https://firebase.google.com/docs/cloud-messaging/concept-options (“Encryption for data 

messages The Android Transport Layer (see FCM architecture) uses point-to-point 

encryption.”).

Likewise, messages sent with Knox Manage instrumentalities are also encrypted. See 

https://docs.samsungknox.com/admin/fundamentals/whitepaper/core-platform-security/knoxvault/; https://docs.samsungknox.com/admin/fundamentals/whitepaper/network-security/virtualprivate-networks/.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 69 of 83 PageID #:

2318
Page 69 of 82

Claim 3

3. The message link server of claim 2, 

wherein the encrypted one or more 

messages are transported to the device 

link agent on the given one of the 

wireless end-user devices using one or 

more of encryption on the transport 

services stack, IP (Internet Protocol) 

layer encryption, and tunneling.

The accused instrumentalities comprise the “message link server of claim 2, wherein the 

encrypted one or more messages are transported to the device link agent on the given one of the 

wireless end-user devices using one or more of encryption on the transport services stack, IP 

(Internet Protocol) layer encryption, and tunneling.”

See supra claims 1 and 2.

Claim 4

4. The message link server of claim 1, 

wherein the device link agent executes in 

a secure execution environment on at 

least one of the devices, and at least one 

of the software components executes 

outside of the secure execution 

environment on that device.

The accused instrumentalities comprise the “message link server of claim 1, wherein the device 

link agent executes in a secure execution environment on at least one of the devices, and at least 

one of the software components executes outside of the secure execution environment on that 

device.”

See supra claim 1. As just one example, with Knox-managed devices, the Knox agent software 

residing on the user device executes from a specially protected partition of local memory. This 

specially protected partition is sometimes referred to as the Knox Secure Folder. Applications 

stored in the Secure Folder partition are managed separately with respect to push notifications. 

Other applications on the user device may be run from outside of the Knox Secure Folder 

partition.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 70 of 83 PageID #:

2319
Page 70 of 82

https://www.samsung.com/uk/support/mobile-devices/what-is-the-secure-folder-and-how-do-iuse-it/

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 71 of 83 PageID #:

2320
Page 71 of 82

https://www.samsung.com/us/support/answer/ANS00081123/

Claim 5

5. The message link server of claim 1, 

wherein the transport services stack is 

further to receive, over each of the 

respective secure message links, upload 

messages forwarded by the respective 

device link agents from at least a subset 

of the device software components, each 

of the upload messages identifying a 

corresponding one of the network 

elements to which the device respective 

software component has requested 

delivery, the network server system using 

the interface to a network to deliver 

content from the upload messages to the 

respective identified network elements.

The accused instrumentalities comprise the “message link server of claim 1, wherein the 

transport services stack is further to receive, over each of the respective secure message links, 

upload messages forwarded by the respective device link agents from at least a subset of the 

device software components, each of the upload messages identifying a corresponding one of 

the network elements to which the device respective software component has requested delivery, 

the network server system using the interface to a network to deliver content from the upload 

messages to the respective identified network elements.”

See supra claim 1.

For example, the end user devices of the accused instrumentalities cause their respective device 

link agents of a subset of the software components on the device to send messages to servers 

such as the App Servers (e.g., from Tizen devices), Knox Manage servers (from Knox managed 

devices), and push messaging servers (e.g., from Samsung’s Android devices). These messages 

include those for sending authentication and verification information to servers.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 72 of 83 PageID #:

2321
Page 72 of 82

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 73 of 83 PageID #:

2322
Page 73 of 82

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

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

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 74 of 83 PageID #:

2323
Page 74 of 82

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

Claim 6

6. The message link server of claim 1, 

wherein at least one of the one or more 

messages for delivery by the transport 

The accused instrumentalities comprise a “message link server of claim 1, wherein at least one 

of the one or more messages for delivery by the transport services stack comprises multiple 

identifier/data pairs.”

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 75 of 83 PageID #:

2324
Page 75 of 82

services stack comprises multiple 

identifier/data pairs. See supra claim 1. See, for example, https://firebase.google.com/docs/cloud-messaging/conceptoptions (“Data messages, by contrast, contain only your user-defined custom key-value pairs. 

Notification messages can contain an optional data payload. Maximum payload for both 

message types is 4000 bytes, except when sending messages from the Firebase console, which 

enforces a 1000 character limit.”); 

https://docs.tizen.org/application/native/guides/messaging/push/ (“The message field contains 

not only the message to show in the quick panel on the device, but also the behaviors that the 

device must take when receiving the notification. The message field is a string that consists of 

key-value pairs. The available pair options are given in the following table.”). On information 

and belief, messages transmitted to and from Knox servers also comprise multiple identifier/data 

pairs.

Claim 7

7. The message link server of claim 1, the 

device messaging agent on at least one of 

the wireless end-user devices further to 

initiate the respective secure Internet data 

message link to the transport services 

stack.

The accused instrumentalities comprise a “message link server of claim 1, the device messaging 

agent on at least one of the wireless end-user devices further to initiate the respective secure 

Internet data message link to the transport services stack.”

See supra claim 1, 5. As explained above, the device messaging agents on the devices may 

initiate secure connections to both app servers and the push messaging servers and Knox 

Manage servers to, inter alia, request push messages and other information and initiate 

authentication procedures. 

Claim 8

8. The message link server of claim 1, 

further comprising a secure server to 

provide secure authorization signatures to 

the given one of the wireless end-user 

devices, the secure authorization 

signatures indicating the authorized 

software components that are allowed to 

The accused instrumentalities comprise the “message link server of claim 1, further comprising 

a secure server to provide secure authorization signatures to the given one of the wireless enduser devices, the secure authorization signatures indicating the authorized software components 

that are allowed to receive data from secure message link messages via the message link server.”

See supra claim 1, 5. As explained above, the device messaging agents on the devices may 

initiate secure connections to both app servers and the push messaging servers and Knox 

Manage servers to, inter alia, request push messages and other information and initiate 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 76 of 83 PageID #:

2325
Page 76 of 82

receive data from secure message link 

messages via the message link server.

authentication procedures. Among these communications are transmissions from apps in the 

user devices to push messaging servers to register said applications as being permitted to receive 

messages and data from the servers. Likewise, Knox Manage software components on the user 

device communicate with Knox servers to authenticate the software on the user device to, 

among other things, allow the device to access Knox-related functionality over the network.

Claim 9

9. The message link server of claim 1, 

wherein one of the message delivery 

triggers is the expiration of a periodic 

timer.

The accused instrumentalities comprise the “message link server of claim 1, wherein one of the 

message delivery triggers is the expiration of a periodic timer.”

As explained in claim 1 supra, various triggers cause transmissions to occur between devices 

and push messaging servers and Knox servers. The transmission trigger may be a time period of 

inactivity or the expiration of a periodic timer.

See, e.g., https://docs.tizen.org/application/web/guides/messaging/push/: 

• “Store the notification at the push service database and request it later when the 

application is launched.

This happens when the action is set to ALERT or SILENT in the message field when 

sending the notification from the application server. When such a notification arrives 

at the device, the push service keeps the notification in the database and waits for 

the request from the application.

For more information, see the Retrieving Missed Push Messages use case.

The difference between the ALERT and SILENT actions is that the former shows an 

alert message in the quick panel and changes the badge count, while the latter does 

not. If the user clicks the alert message in the quick panel, the push service forcibly 

launches the application and delivers the notification.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 77 of 83 PageID #:

2326
Page 77 of 82

Store the notification at the push service database and request it later when the application 

is launched.

You need to set the action to ALERT or SILENT in the message field when sending the 

notification from the application server. When such a notification arrives at the device, the 

push service keeps the notification in the database and waits for the request from the 

application.

You can request for unread notifications from the push service. The request can be 

performed after connecting to the push server when the application is launched.

• Request the unread notifications asynchronously. If there is such a notification, it 

can be received through the _noti_cb() function after 

the _on_state_registered() function returns. Once the request for unread 

notifications is successfully delivered, PUSH_SERVICE_ERROR_NONE is returned.”

Claim 11

11. The message link server of claim 1, 

wherein one of the message delivery 

triggers is the receipt of a transmission on 

the respective secure message link from 

the device link agent of the given one of 

the wireless end-user devices, or a 

response generated to a transmission 

received from that device link agent.

The accused instrumentalities comprise the “message link server of claim 1, wherein one of the 

message delivery triggers is the receipt of a transmission on the respective secure message link 

from the device link agent of the given one of the wireless end-user devices, or a response 

generated to a transmission received from that device link agent.”

As explained in claim 1 supra, various triggers cause transmissions to occur between devices 

and push messaging servers and Knox servers. The transmission trigger may be the receipt by 

the messaging server of a notification from a user device that is has started up and/or is 

requesting push messages.

See, e.g., https://docs.tizen.org/application/web/guides/messaging/push/: 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 78 of 83 PageID #:

2327
Page 78 of 82

• “Store the notification at the push service database and request it later when the 

application is launched.

This happens when the action is set to ALERT or SILENT in the message field when 

sending the notification from the application server. When such a notification arrives 

at the device, the push service keeps the notification in the database and waits for 

the request from the application.

For more information, see the Retrieving Missed Push Messages use case.

The difference between the ALERT and SILENT actions is that the former shows an 

alert message in the quick panel and changes the badge count, while the latter does 

not. If the user clicks the alert message in the quick panel, the push service forcibly 

launches the application and delivers the notification.

Store the notification at the push service database and request it later when the application 

is launched.

You need to set the action to ALERT or SILENT in the message field when sending the 

notification from the application server. When such a notification arrives at the device, the 

push service keeps the notification in the database and waits for the request from the 

application.

You can request for unread notifications from the push service. The request can be 

performed after connecting to the push server when the application is launched.

• Request the unread notifications asynchronously. If there is such a notification, it 

can be received through the _noti_cb() function after 

the _on_state_registered() function returns. Once the request for unread 

notifications is successfully delivered, PUSH_SERVICE_ERROR_NONE is returned.”

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 79 of 83 PageID #:

2328
Page 79 of 82

Claim 12

12. The message link server of claim 11, 

wherein the transmission is a heartbeat 

message generated by the given device 

link agent, or a request received from the 

given device link agent.

The accused instrumentalities comprise the “message link server of claim 11, wherein the 

transmission is a heartbeat message generated by the given device link agent, or a request 

received from the given device link agent.”

As explained in claim 1 supra, various triggers cause transmissions to occur between devices 

and push messaging servers and Knox servers. The transmission trigger may be the receipt by 

the messaging server of a notification from a user device that is has started up and/or is 

requesting push messages.

See, e.g., https://docs.tizen.org/application/web/guides/messaging/push/: 

• “Store the notification at the push service database and request it later when the 

application is launched.

This happens when the action is set to ALERT or SILENT in the message field when 

sending the notification from the application server. When such a notification arrives 

at the device, the push service keeps the notification in the database and waits for 

the request from the application.

For more information, see the Retrieving Missed Push Messages use case.

The difference between the ALERT and SILENT actions is that the former shows an 

alert message in the quick panel and changes the badge count, while the latter does 

not. If the user clicks the alert message in the quick panel, the push service forcibly 

launches the application and delivers the notification.

Store the notification at the push service database and request it later when the application 

is launched.

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 80 of 83 PageID #:

2329
Page 80 of 82

You need to set the action to ALERT or SILENT in the message field when sending the 

notification from the application server. When such a notification arrives at the device, the 

push service keeps the notification in the database and waits for the request from the 

application.

You can request for unread notifications from the push service. The request can be 

performed after connecting to the push server when the application is launched.

• Request the unread notifications asynchronously. If there is such a notification, it 

can be received through the _noti_cb() function after 

the _on_state_registered() function returns. Once the request for unread 

notifications is successfully delivered, PUSH_SERVICE_ERROR_NONE is returned.”

Claim 13

13. The message link server of claim 1, 

wherein one of the message delivery 

triggers is the receipt of a particular 

network element message from one of 

the network elements.

The accused instrumentalities comprise the “message link server of claim 1, wherein one of the 

message delivery triggers is the receipt of a particular network element message from one of the 

network elements.”

As explained supra for claim 1, app servers may communicate with push messaging servers to 

cause messages to be sent to user devices.

Claim 15

15. A method of operating a message link 

server, comprising:

See supra claim 1.

maintaining a respective secure message 

link through an Internet network between 

the message link server and a respective 

device link agent on each of a plurality of 

The accused instrumentalities comprise a method including “maintaining a respective secure 

message link through an Internet network between the message link server and a respective 

device link agent on each of a plurality of wireless end-user devices, each of the wireless endCase 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 81 of 83 PageID #:

2330
Page 81 of 82

wireless end-user devices, each of the 

wireless end-user devices comprising 

multiple software components authorized 

to receive and process data from secure 

message link messages received via a 

device link agent on that device;

user devices comprising multiple software components authorized to receive and process data 

from secure message link messages received via a device link agent on that device.”

See supra claim 1[a].

receiving network element messages 

from a plurality of network elements, the 

received network element messages 

comprising respective message content 

and requests for delivery of the 

respective message content to respective 

wireless end-user devices, the respective 

message content including data for, and 

an identification of, a respective one of 

the authorized software components;

The accused instrumentalities comprise a method including “receiving network element 

messages from a plurality of network elements, the received network element messages 

comprising respective message content and requests for delivery of the respective message 

content to respective wireless end-user devices, the respective message content including data 

for, and an identification of, a respective one of the authorized software components.”

See supra claim 1[b].

buffering content from the received 

network element messages for which 

delivery is requested to a given one of the 

wireless end-user devices;

The accused instrumentalities comprise a method including “buffering content from the received 

network element messages for which delivery is requested to a given one of the wireless enduser devices.”

See supra claim 1[c].

determining when one of a plurality of 

message delivery triggers for the given 

one of the wireless end-user devices has 

occurred, wherein for at least some of the 

received network element messages, the 

receipt of such a message is not a 

message delivery trigger, and for at least 

one of the message delivery triggers, the 

trigger is an occurrence of an 

asynchronous event with time-critical 

messaging needs; and

The accused instrumentalities comprise a method including “determining when one of a 

plurality of message delivery triggers for the given one of the wireless end-user devices has 

occurred, wherein for at least some of the received network element messages, the receipt of 

such a message is not a message delivery trigger, and for at least one of the message delivery 

triggers, the trigger is an occurrence of an asynchronous event with time-critical messaging 

needs.”

See supra claim 1[d].

upon determining that one of the message 

delivery triggers has occurred, supplying 

one or more messages comprising the 

The accused instrumentalities comprise a method including “upon determining that one of the 

message delivery triggers has occurred, supplying one or more messages comprising the 

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 82 of 83 PageID #:

2331
Page 82 of 82

buffered content for delivery on the 

secure message link maintained between 

the message link server and a device link 

agent on the given one of the wireless 

end-user devices.

buffered content for delivery on the secure message link maintained between the message link 

server and a device link agent on the given one of the wireless end-user devices.”

See supra claim 1[e].

Case 2:23-cv-00103-JRG-RSP Document 79-1 Filed 03/19/24 Page 83 of 83 PageID #:

2332