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:  19.3.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…   A…   C   D… 
9.3.3 Information flows  9.3.3.1 SEALDD URLLC transmission request  9.3.3.2 SEALDD URLLC transmission response  9.3.3.3 SEALDD URLLC transmission connection establishment request  9.3.3.4 SEALDD URLLC transmission connection establishment response  9.3.3.5 SEALDD URLLC transmission connection update request  9.3.3.6 SEALDD URLLC transmission connection update response  9.3.3.7 SEALDD URLLC transmission connection release request  9.3.3.8 SEALDD URLLC transmission connection release response 
...

 

9.3.3  Information flows  p. 48

9.3.3.1  SEALDD URLLC transmission request  p. 48

See clause 9.2.3.1 for the details of information flow with the following clarification:
  • The bandwidth related IEs are not applicable.

9.3.3.2  SEALDD URLLC transmission response  p. 48

See clause 9.2.3.2 for the details of information flow.

9.3.3.3  SEALDD URLLC transmission connection establishment request  p. 48

Table 9.3.3.3-1 describes the information flow from the SEALDD client to the SEALDD server or from the SEALDD server to the SEALDD client for requesting the URLLC transmission connection establishment.
Information element Status Description
SEALDD client IDMIdentity of the SEALDD client.
IdentityOThe VAL user ID of the VAL user or VAL UE ID
SEALDD-UU flow IDsM
(See NOTE 1)		Identity of the SEALDD-UU flows.
VAL server IDO
(See NOTE 1)		Identity of the VAL server.
VAL service IDO
(See NOTE 1)		Identity of the VAL service.
SEALDD traffic descriptorsOA pair of SEALDD traffic descriptors (e.g. address, port, transport layer protocol) of the SEALDD client side (for client side initiated request) or the SEALDD server side (for server side initiated request) used to establish redundant SEALDD connection.
Capability for BAT and periodicity adaptationO
(See NOTE 2)		Indicates BAT and periodicity adaptation capability for SEALDD client in client side initiated request.
Transmission assistance infoO
(See NOTE 2)		Indicates transmission assistance information for uplink SEALDD traffic in client side initiated request.
It includes BAT, BAT window, periodicity, and periodicity range.
For URLLC transmission, it includes assistance information per SEALDD traffic descriptor.
NOTE 1:
The SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to identify different application traffic, and it is mapped from the VAL service ID.
NOTE 2:
If provided, only one of these IEs shall be present in the message.
Up

9.3.3.4  SEALDD URLLC transmission connection establishment response  p. 48

Table 9.3.3.4-1 describes the information flow from the SEALDD server to the SEALDD client or from the SEALDD client to the SEALDD server for responding to the URLLC transmission connection establishment.
Information element Status Description
ResultMIndicates the success or failure of establishing the SEALDD connection.
SEALDD traffic descriptorsOA pair of SEALDD traffic descriptors (e.g. address, port, transport layer protocol) of the SEALDD server side (for client side initiated request) or the SEALDD client side (for server side initiated request) used to establish redundant SEALDD connection.
CauseO
(See NOTE 1)		Indicates the reason for the failure, e.g. SEALDD policy mismatch.
Capability for BAT and periodicity adaptationO
(See NOTE 2)		Indicates BAT and periodicity adaptation capability for SEALDD client in server side initiated request.
Transmission assistance infoO
(See NOTE 2)		Indicates transmission assistance information for uplink SEALDD traffic in server side initiated request.
It includes BAT, BAT window, periodicity, and periodicity range.
For URLLC transmission, it includes assistance information per SEALDD traffic descriptor.
NOTE 1:
The IE is only present if the Result is failure.
NOTE 2:
If provided, only one of these IEs shall be present in the message.
Up

9.3.3.5  SEALDD URLLC transmission connection update request  p. 49

Table 9.3.3.5-1 describes the information flow from the SEALDD client to the SEALDD server for requesting the URLLC transmission connection update.
Information element Status Description
SEALDD client IDMIdentity of the SEALDD client.
SEALDD-UU flow IDsM
(See NOTE)		Identity of the SEALDD-UU flows.
VAL server IDO
(See NOTE)		Identity of the VAL server.
VAL service IDO
(See NOTE)		Identity of the VAL service.
SEALDD traffic descriptorsOA pair of SEALDD traffic descriptors (e.g. address, port, transport layer protocol) of the SEALDD client side used to establish redundant SEALDD connection.
NOTE:
The SEALDD-UU flow IDs is used by the SEALDD client and SEALDD server to identify different application traffic, and it is mapped from the VAL service ID.
Up

9.3.3.6  SEALDD URLLC transmission connection update response  p. 49

Table 9.3.3.6-1 describes the information flow from the SEALDD server to the SEALDD client for responding to the redundant transmission connection update.
Information element Status Description
ResultMIndicates the success or failure of updating the SEALDD connection.
CauseO
See NOTE		Indicates the reason for the failure, e.g. SEALDD policy mismatch.
NOTE:
The IE is only present if the Result is failure.
Up

9.3.3.7  SEALDD URLLC transmission connection release request  p. 50

See clause 9.2.3.5 for the details of information flow.

9.3.3.8  SEALDD URLLC transmission connection release response  p. 50

See clause 9.2.3.6 for the details of information flow.

Up   Top   ToC