Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.433  Word version:  20.0.0

Top   Top   Up   Prev   Next
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.9.3…   9.10…   9.10.3…   9.11…   9.11.3…   9.12…   9.12.3…   9.13   10…   A…   C   D… 
8 Identities and commonly used values  8.1 General  8.2 SEALDD server ID  8.3 SEALDD client ID  8.4 SEALDD-UU flow ID  8.5 Multi-modal SEALDD flow ID  8.6 Multi-modal service ID  9 Procedures and information flows  9.1 General 
...

 

8  Identities and commonly used values  p. 28

8.1  General  p. 28

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

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

8.3  SEALDD client ID  p. 28

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

8.4  SEALDD-UU flow ID  p. 28

The SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to identify different VAL application traffic, which has the same attributes, e.g. the same 5-tuple, media type, QoS requirements. The SEALDD-UU flow ID should be uniquely identified with the SEALDD-UU connection.

8.5  Multi-modal SEALDD flow ID |R19|  p. 28

The multi-modal SEALDD flow ID is used by the SEALDD client and SEALDD server to uniquely identify associated multi-modal VAL application traffic flows per VAL service.

8.6  Multi-modal service ID |R19|  p. 28

The Multi-modal Service ID is an identifier of the multi-modal service as defined in clause 6.1.3.27.3 of TS 23.503. Data flows belonging to the same multi-modal service share the same Multi-modal Service ID.

9  Procedures and information flows  p. 29

9.1  General  p. 29

The VAL application data/content is stored in the VAL server, or the SEALDD server, or other cloud platform. For the downlink traffic transmission, the SEALDD server retrieves the data/content of VAL application, by using one of the following modes:
  • Downlink pull mode: the SEALDD server pulls the data/content of VAL application from the address provided by the VAL server (i.e. pull from the data/content address in VAL server over SEALDD-S interface, or in other cloud platform).
  • Downlink push mode: the VAL server pushes the data/content of VAL application to the SEALDD server over SEALDD-S interface.
For the uplink traffic transmission, the SEALDD server 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 pulls the data/content of VAL application from the SEALDD server over SEALDD-S interface.
  • Uplink push mode: the SEALDD server pushes the data/content of VAL application to the address provided by the VAL server (i.e. push to the data/content address in VAL server over SEALDD-S interface, or in other cloud platform).
Up

Up   Top   ToC