Content for TS 23.433 Word version: 19.0.0

0… 4… 7… 8… 9.2… 9.2.2.3… 9.2.3… 9.2.4… 9.3… 9.3.2.2… 9.3.3… 9.3.4… 9.4… 9.5… 9.5.3… 9.5.4… 9.6… 9.7… 9.7.3… 9.7.4… 9.8… 9.9… 9.10… A… C…

8.1 General 8.2 SEALDD server ID 8.3 SEALDD client ID 8.4 SEALDD flow ID 9.1 General
...

8 Identities and commonly used values p. 21

8.1 General p. 21

The common identities for SEAL refer to TS 23.434. The following clauses list the additional identities and commonly used values for SEALDD.

8.2 SEALDD server ID p. 21

The SEALDD server ID uniquely identifies the SEAL data delivery server.

8.3 SEALDD client ID p. 21

The SEALDD client ID is a globally unique value that identifies the SEAL data delivery client.

8.4 SEALDD flow ID p. 22

The SEALDD flow ID is used by the SEALDD client and SEALDD server to identify different VAL application traffic.

9 Procedures and information flows p. 22

The VAL application data/content can be stored in the VAL server, or the SEALDD server, or other cloud platform. For the downlink traffic transmission, the SEALDD server can retrieve the data/content of VAL application, by using one of the following modes:

Downlink pull mode: the SEALDD server can pull the data/content of VAL application from the address provided by the VAL server (i.e. data/content address in VAL server, or in other cloud platform).
Downlink push mode: the VAL server can push the data/content of VAL application to the SEALDD server.

For the uplink traffic transmission, the SEALDD server can sends the data/content of VAL application to the address provided by the VAL server, by using one of the following modes:

Uplink pull mode: the VAL server can pull the data/content of VAL application from the SEALDD server.
Uplink push mode: the SEALDD server can push the data/content of VAL application to the address provided by the VAL server (i.e. data/content address in VAL server, or in other cloud platform).