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.4.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… 
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.3.5 SEALDD-UUc Connection Request  9.12.3.6 SEALDD-UUc Connection Connection Response  9.12.3.7 Inform XR transmission request  9.12.3.8 Inform XR transmission response  9.12.3.9 Trigger XR transmission request  9.12.3.10 Trigger XR transmission 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.4.4 Sdd_SEALDD-UUcConnectionEstablish operation  9.12.4.5 Sdd_XRTransmissionConnection_Trigger operation  9.12.4.6 Sdd_XRTransmissionConnection_Inform operation 
...

 

9.12.3  Information flows  p. 122

9.12.3.1  SEALDD enabled XR transmission request  p. 122

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

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

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

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.
Multi-modal SEALDD flow IDMIdentity of the Multi-modal SEALDD-UU flow associated with the multi-modal XR 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.3.5  SEALDD-UUc Connection Request  p. 124

Table 9.12.3.5-1 describes the information flow from the SEALDD client on 3GPP UE to SEALDD client on tethered UE for SEALDD-UUc Connection Request.
Information element Status Description
Requestor's ID or PIN IDMIdentity of the requestor SEALDD client on 3GPP UE, or the PIN ID of the requestor.
SEALDD-UUc Data transmission connection informationMSEALDD-UUc Data transmission connection information (e.g., address/port allocated).
Up

9.12.3.6  SEALDD-UUc Connection Connection Response  p. 124

Table 9.12.3.6-1 describes the information flow from the SEALDD client on 3GPP UE to SEALDD client on tethered UE for SEALDD-UUc Connection Connection Response.
Information element Status Description
ResultMSuccess or failure.
SEALDD-UUc Data transmission connection informationOSEALDD-UUc Data transmission connection information (e.g., address/port allocated).
Up

9.12.3.7  Inform XR transmission request  p. 124

Table 9.12.3.7-1 describes the information flow from the SEALDD client to the SEALDD server to inform XR transmission connection status between two UEs.
Information element Status Description
Requestor IDMIdentity of the requestor (i.e. SEALDD client).
VAL service IDOIdentity of the VAL service.
IdentitiesMIdentifier of UEs or VAL users involved in the UE-to-UE direct communication.
StatusMIdentifies the UE-to-UE direct communication status (e.g. establishment, release).
Up

9.12.3.8  Inform XR transmission response  p. 124

Table 9.12.3.8-1 describes the information flow from the SEALDD server to the SEALDD client to acknowledge XR transmission connection status between two UEs.
Information element Status Description
ResultMResult of the operation.
Up

9.12.3.9  Trigger XR transmission request  p. 124

Table 9.12.3.9-1 describes the information flow from the SEALDD server to the SEALDD client to trigger XR transmission connection operation between two UEs.
Information element Status Description
Requestor IDMIdentity of the requestor (i.e. SEALDD server).
VAL service IDOIdentity of the VAL service.
IdentitiesMIdentifier of UEs or VAL users involved in the UE-to-UE direct communication.
OperationMIdentifies the action for UE-to-UE direct communication (e.g. establishment, release).
Up

9.12.3.10  Trigger XR transmission response  p. 125

Table 9.12.3.10-1 describes the information flow from the SEALDD client to the SEALDD server to acknowledge XR transmission connection operation between two UEs.
Information element Status Description
ResultMResult of the operation.
Up

9.12.4  APIs  p. 125

9.12.4.1  General  p. 125

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
Trigger (NOTE)Request/ResponseSEALDD server
InformRequest/ResponseSEALDD client
Sdd_SEALDD-UUcConnectionEstablishRequest/ResponseSEALDD client
NOTE:
The Sdd_XRTransmissionConnection_Trigger API operation is exposed by the SEALDD client.
Up

9.12.4.2  Sdd_XRTransmission Request operation  p. 125

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

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.

9.12.4.4  Sdd_SEALDD-UUcConnectionEstablish operation  p. 126

API operation name:
Sdd_SEALDD-UUcConnectionEstablish
Description:
The consumer requests for SEALDD-UUc connection establishment between the SEALDD client on 3GPP UE and tethered device.
Inputs:
See clause 9.12.3.5.
Outputs:
See clause 9.12.3.6.
See clause 9.12.2.3.4 for details of usage of this operation.

9.12.4.5  Sdd_XRTransmissionConnection_Trigger operation  p. 126

API operation name:
Sdd_XRTransmissionConnection_Trigger
Description:
The consumer requests to trigger direct multi-modal transmission connection establishment between two UEs.
Inputs:
See clause 9.12.3.7.
Outputs:
See clause 9.12.3.8.
See clause 9.12.2.4 for details of usage of this operation.

9.12.4.6  Sdd_XRTransmissionConnection_Inform operation  p. 126

API operation name:
Sdd_XRTransmissionConnection_Inform
Description:
The consumer informs direct multi-modal transmission connection establishment between two UEs.
Inputs:
See clause 9.12.3.9.
Outputs:
See clause 9.12.3.10.
See clause 9.12.2.4 for details of usage of this operation.

Up   Top   ToC