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.12 SEALDD enabled transmission for XR application  9.12.1 General  9.12.2 Procedures  9.12.2.1 SEALDD enabled XR data transmission service for XR application  9.12.2.2 SEALDD enabled multi-modal flow synchronization  9.12.3 Information flows  9.12.3.1 SEALDD enabled XR transmission request  9.12.3.2 SEALDD enabled XR transmission request  9.12.3.3 SEALDD XR transmission connection establishment request  9.12.3.4 SEALDD XR transmission connection establishment response  9.12.4 APIs  9.12.4.1 General  9.12.4.2 Sdd_XRTransmission Request operation  9.12.4.3 Sdd_XRTransmissionConnection_Establish operation 
...

 

9.12  SEALDD enabled transmission for XR application |R19|  p. 102

9.12.1  General  p. 102

This clause provides the services to support the transmission for XR application based on SEALDD capabilities.

9.12.2  Procedures  p. 102

9.12.2.1  SEALDD enabled XR data transmission service for XR application  p. 102

9.12.2.1.1  General  p. 102
The following clauses specify procedures, information flows and APIs about SEALDD enabled data transmission for XR application, including the SEALDD facilate PDU set handling.
9.12.2.1.2  SEALDD enabled XR data transmission establishment  p. 102
Figure 9.12.2.1.2-1 illustrate the procedure for establishing XR data transmission connection, and the SEALDD facilitates the XR application to transmit its data between the VAL client and VAL server with RTP packetilization and PDU set inclusion.
Pre-condition:
  • The VAL server can discover and select the SEALDD server by CAPIF functions.
Reproduction of 3GPP TS 23.433, Fig. 9.12.2.1.2-1: SEALDD enabled XR data transmission connection establishment procedure
Figure 9.12.2.1.2-1: SEALDD enabled XR data transmission connection establishment procedure
Up
Step 1.
The VAL server decides to use SEALDD service for XR traffic transfer and allocates address/port as SEALDD-S Data transmission connection information for receiving the data packets from SEALDD server. The VAL server sends Sdd_XRTransmission request to the SEALDD server discovered by CAPIF. The service request includes UE ID/address, VAL server ID, VAL service ID, SEALDD-S Data transmission connection information of the VAL server side, and optionally, the protocol description, the QoS information for the application traffic, e.g. QoS requirements.
Step 2.
Same as step 2 of clause 9.2.2.2. For application multi-modal service, the SEALDD server derives PDU Set related assistance information based on received VAL service ID and/or VAL server ID, and protocol description for interacting with NEF/PCF.
Step 3-5.
Same as step 3-5 of clause 9.2.2.2.
Step 6.
The SEALDD client establishes XR transmission connection with the SEALDD server. The SEALDD server sends the SEALDD traffic descriptors for multiple flows from SEALDD server side (e.g. address/port for multiple SEALDD-UU flow) to the SEALDD client, and may send the protocol description (UL related info) received from the VAL server to the SEALDD client in the XR transmission connection response.
Step 7-8.
Same as step 8-9 of clause 9.2.2.2.
The XR application traffic is exchanged between VAL client and VAL server via SEALDD layer as described in clause 9.2.2.2. If packetization indication indicates that SEALDD layer needs to perform packetization, the SEALDD server performs packetization and sends streaming data (e.g. RTP packet) via SEALDD-UU user plane (e.g. SEALDD/UDP/IP) to the SEALDD client for downlink application traffic. Similarly, the SEALDD client performs packetization and sends streaming data (e.g. RTP packet) via SEALDD-UU user plane (e.g. SEALDD/UDP/IP) to the SEALDD server for uplink application traffic. The SEALDD server and client also perform PDU Set inclusion (e.g. in RTP extension as defined in TS 26.522), and if needed, stream session and transport management (e.g. RTCP, RTSP).
Up

9.12.2.2  SEALDD enabled multi-modal flow synchronization  p. 103

9.12.2.2.1  General  p. 103
The following clauses specify procedures, information flows and APIs about SEALDD enabled data transmission for XR application, including SEALDD enabled multi-modal flow synchronization.
9.12.2.2.2  SEALDD enabled multi-modal flow synchronization  p. 104
Figure 9.12.2.2.2-1 illustrate the procedure for SEALDD enabled multi-modal flow synchoronization, the SEALDD server determines/updates the required QoS information for multi-modal flow(s), and further interacts with 5G network.
Pre-condition:
  • The VAL server can discover and select the SEALDD server by CAPIF functions.
  • The SEALDD server has been provisioned to multi-modal XR policy including the synchronization threshold, as specified in clause 9.10.3.1.
Reproduction of 3GPP TS 23.433, Fig. 9.12.2.2.2-1: SEALDD enabled multi-flow synchronization procedure
Figure 9.12.2.2.2-1: SEALDD enabled multi-flow synchronization procedure
Up
Step 1.
An on-going multi-modal data transmission connection is established according to the steps 1-8 of clause 9.12.2.1.2.
Step 2.
The SEALDD server performs data transmission quality measurement in SEALDD-UU interface based on the mapping information for multiple flow association information between SEALDD-S interface and SEALDD-UU interface. Upon receiving the packets from multiple associated flows in SEALDD-S interface, the SEALDD server performs the packet encapsulation with sending timestamp information in the corresponding SEALDD-UU interface, and can calculate the transmission delay measurement result of multiple associated flows after obtaining the receiving timestamp from the SEALDD client.
Step 3.
Based on the calculated transmission delay for multiple associated flow over SEALDD-UU interface in step 2, and the synchronization threshold for multi-modal application as described in pre-condition, the SEALDD server can determine the service flow(s) (i.e. address/port for SEALDD-UU flow) that needs to be adjusted among the multiple associated flows in SEALDD-UU interface, and the corresponding required QoS information (i.e. transmission delay).
Step 4.
The SEALDD server sends the AF request to 5GC via N33/N5 with the SEALDD traffic descriptor of the adjusted flow(s) (i.e. address/port for the adjusted SEALDD-UU flow) and the corresponding required QoS information determined in step 3, by utilizing the AF session with required QoS procedure in clause 4.15.6.6 of TS 23.502. The SEALDD traffic descriptor of the adjusted flow(s) contains the address or port in SEALDD server side, and/or SEALDD client side.
After requesting the transmission quality optimization on 5G network with the required QoS for the adjusted flow(s), the multi-flow synchronization of multi-modal application can be satisfied.
Up

9.12.3  Information flows  p. 105

9.12.3.1  SEALDD enabled XR transmission request  p. 105

Table 9.12.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting XR transmission service.
Information element Status Description
VAL server IDMIdentity of the VAL server.
VAL service IDOIdentity of the VAL service.
IdentityOIdentifier of specific UE or VAL user.
SEALDD-S Data transmission connection information for multi-modal XRMAddress(s)/port(s) and/or URL(s) of the VAL server to receive the multi-flow packets from the SEALDD server (e.g. audio flow, tactile flow).
Protocol descriptionOThe protocol description of VAL traffic. It includes header extension information (e.g. RTP extension with PDU set), packetization indication, payload type and format (e.g. H.264/RTP, H.265/RTP, H.264, H.265).
Header extension information is only applicable when payload indicates RTP.
Up

9.12.3.2  SEALDD enabled XR transmission request  p. 105

Table 9.12.3.2-1 describes the information flow from the SEALDD server to the VAL server for responding to the XR transmission request.
Information element Status Description
ResultMSuccess or failure.
SEALDD-S information Data transmission connection information for multi-modal XROAddress(s)/port(s) and/or URL(s) of the SEALDD server to receive the multi-flow packets from the VAL server for application traffic transfer (e.g. audio flow, tactile flow).
CauseO
(See NOTE)		Indicates the reason for the failure.
NOTE:
The IE is only present if the Result is failure.
Up

9.12.3.3  SEALDD XR transmission connection establishment request  p. 105

Table 9.12.3.3-1 describes the information flow from the SEALDD client to the SEALDD server for requesting the XR 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 IDsMIdentity of the SEALDD-UU flows.
VAL server IDOIdentity of the VAL server.
VAL service IDOIdentity of the VAL service.
SEALDD traffic descriptorsOSEALDD traffic descriptors for multiple flows (e.g. address(s), port(s), transport layer protocol) of the SEALDD client side used to establish SEALDD multi-modal XR connection.
Up

9.12.3.4  SEALDD XR transmission connection establishment response  p. 106

Table 9.12.3.4-1 describes the information flow from the SEALDD server to the SEALDD client for responding to the XR transmission connection establishment.
Information element Status Description
ResultMIndicates the success or failure of establishing the SEALDD connection.
SEALDD traffic descriptorsOSEALDD traffic descriptors for multiple flows (e.g. address(s), port(s), transport layer protocol) of the SEALDD server side used to establish SEALDD multi-modal connection.
Protocol descriptionOThe protocol description of VAL traffic. It includes header extension information (e.g. RTP extension with PDU set), packetization indication, payload type and format (e.g. H.264/RTP, H.265/RTP, H.264, H.265).
Header extension information is only applicable when payload indicates RTP.
CauseO
(See NOTE)		Indicates the reason for the failure.
NOTE:
The IE is only present if the Result is failure.
Up

9.12.4  APIs  p. 106

9.12.4.1  General  p. 106

Table 9.12.4.1-1 illustrates the APIs exposed by SEALDD server for XR transmission.
API Name API Operations Operation Semantics Consumer(s)
Sdd_XRTransmissionRequestRequest/ResponseVAL server
Sdd_XRTransmissionConnnectionEstablishRequest/ResponseSEALDD client
Up

9.12.4.2  Sdd_XRTransmission Request operation  p. 106

API operation name:
Sdd_XRTransmission Request
Description:
The consumer requests for one time for multi-modal XR transmission service.
Inputs:
See clause 9.12.3.1.
Outputs:
See clause 9.12.3.2
See clause 9.12.2.1.2 and 9.12.2.2.2 for details of usage of this operation.

9.12.4.3  Sdd_XRTransmissionConnection_Establish operation  p. 107

API operation name:
Sdd_XRTransmissionConnection_Establish
Description:
The consumer requests for multi-modal transmission connection establishment.
Inputs:
See clause 9.12.3.3.
Outputs:
See clause 9.12.3.4.
See clause 9.12.2.1.2 and 9.12.2.2.2 for details of usage of this operation.

Up   Top   ToC