Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.433  Word version:  19.6.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 flowsp. 127

9.12.3.1  SEALDD enabled multi-modal transmission requestp. 127

Table 9.12.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting multi-modal 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.
List of requested flowsMList of the requested multi-modal flows.
> 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).
> QoS informationOQoS information provided by VAL server.
> 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 multi-modal transmission responsep. 128

Table 9.12.3.2-1 describes the information flow from the SEALDD server to the VAL server for responding to the multi-modal transmission response.
Information element Status Description
ResultMSuccess or failure.
SEALDD-S information Data transmission connection information for multi-modal serviceOAddress(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 multi-modal transmission connection establishment requestp. 128

Table 9.12.3.3-1 describes the information flow from the SEALDD client to the SEALDD server for requesting the multi-modal 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 flows infoMInformation of the list of SEALDD-UU flows.
> SEALDD-UU flow IDMIdentity of the SEALDD-UU flow.
> SEALDD traffic descriptorMSEALDD traffic descriptor for the flow of the SEALDD client side used to establish SEALDD multi-modal XR connection.
>> Addressing infoMIndicates the addressing information (e.g. address, port, URL).
>> Transport layer protocolMIndicates the transport layer protocol.
VAL server IDOIdentity of the VAL server.
VAL service IDOIdentity of the VAL service.
Up

9.12.3.4  SEALDD multi-modal transmission connection establishment responsep. 129

Table 9.12.3.4-1 describes the information flow from the SEALDD server to the SEALDD client for responding to the multi-modal transmission connection establishment.
Information element Status Description
ResultMIndicates the success or failure of establishing the SEALDD connection.
Multi-modal SEALDD flow infoMInformation of the Multi-modal SEALDD-UU flow associated with the multi-modal XR connection.
> Multi-modal SEALDD flow IDMIdentity of the Multi-modal SEALDD-UU flow associated with the multi-modal service connection.
> SEALDD-UU flows listMIndicates the list of SEALDD-UU flows.
>> SEALDD-UU flow IDMIdentity of the SEALDD-UU flow.
>> SEALDD traffic descriptorsMSEALDD traffic descriptors for the flows of the SEALDD server side used to establish SEALDD multi-modal connection.
>>> Addressing infoMIndicates the addressing information (e.g. address, port, URL).
>>> Transport layer protocolMIndicates the transport layer protocol.
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 requestp. 129

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 responsep. 129

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 requestp. 130

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 responsep. 130

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 requestp. 130

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 responsep. 130

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  APIsp. 130

9.12.4.1  Generalp. 130

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_multi-modalTransmissionRequestRequest/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_multi-modalTransmission Request operationp. 131

API operation name:
Sdd_multi-modalTransmission Request
Description:
The consumer requests for one time for multi-modal transmission service.
Inputs:
Outputs:
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 operationp. 131

API operation name:
Sdd_XRTransmissionConnection_Establish
Description:
The consumer requests for multi-modal transmission connection establishment.
Inputs:
Outputs:
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 operationp. 131

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:
Outputs:
See clause 9.12.2.3.4 for details of usage of this operation.

9.12.4.5  Sdd_XRTransmissionConnection_Trigger operationp. 131

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

9.12.4.6  Sdd_XRTransmissionConnection_Inform operationp. 132

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

Up   Top   ToC