hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.3.12 SEALDD enabled data transmission quality measurement unsubscribe response
|
Table 9.7.3.12-1 describes the information flow from the SEALDD server to the VAL server for responding to the transmission quality measurement unsubscribe request.
Table 9.7.3.12-1: SEALDD transmission quality measurement unsubscribe response
Information element
Status
Description
Result
M
Success or failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.4.1 General
|
Table 9.7.4.1-1 illustrates the APIs exposed by SEALDD server for data transmission quality measurement.
Table 9.7.4.1-1: List of SEALDD server APIs for transmission quality measurement
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_TransmissionQualityMeasurement
Subscribe
Subscribe/Notify
VAL server, SEALDD server
Update
Subscribe/Notify
VAL server, SEALDD server
Unsubscribe
Subscribe/Notify
VAL server, SEALDD server
Notify
Subscribe/notify
VAL server, SEALDD server
Query
Request/Response
VAL server, SEALDD server, NSCE server, ADAE server
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.4.2 Sdd_TransmissionQualityMeasurement_Subscribe operation
|
API operation name: Sdd_TransmissionQualityMeasurement_subscription Request
Description: The consumer requests for subscribing transmission quality measurement service.
Inputs: See clause 9.7.3.1.
Outputs: See clause 9.7.3.2
See clause 9.7.2.1 and clause 9.7.2.3 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.4.3 Sdd_TransmissionQualityMeasurement_Notify operation
|
API operation name: Sdd_TransmissionQualityMeasurement_notify
Description: The consumer is notified with the transmission quality measurement reports.
Inputs: See clause 9.7.3.3.
Outputs: None.
See clause 9.7.2.1 and clause 9.7.2.3 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.4.4 Sdd_TransmissionQualityMeasurement_Query operation
|
API operation name: Sdd_TransmissionQualityMeasurement_Query Request
Description: The consumer requests for one time for transmission quality query.
Inputs: See clause 9.7.3.4.
Outputs: See clause 9.7.3.5.
See clause 9.7.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.4.5 Sdd_TransmissionQualityMeasurement_Update operation
|
API operation name: Sdd_TransmissionQualityMeasurement_Update
Description: The consumer requests for updating transmission quality measurement service.
Inputs: See clause 9.7.3.9.
Outputs: See clause 9.7.3.10
See clause 9.7.2.1 and clause 9.7.2.3 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.7.4.6 Sdd_TransmissionQualityMeasurement_Unsubscribe operation
|
API operation name: Sdd_TransmissionQualityMeasurement_Unsubscribe
Description: The consumer requests for unsubscribing transmission quality measurement service.
Inputs: See clause 9.7.3.11.
Outputs: See clause 9.7.3.12.
See clause 9.7.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.8 SEALDD enabled rate control for VAL applications
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.8.1 General
|
The following clauses specify procedures, information flows and APIs for SEALDD enabled rate control transmission.
NOTE: In clause 9.8, the terms bandwidth control and data transmission rate control are interchangeable.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.8.2 Procedures
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.8.2.1 SEALDD enabled bandwidth control for different VAL users
|
The SEALDD layer provides the differentiated data delivery service with different bandwidth experience for VAL users, where the VAL server provides the bandwidth limit (i.e., minimum bandwidth requirement and maximum bandwidth limit) for VAL users. Figure 9.8.2.1-1 illustrates the procedure for bandwidth control for different VAL users.
Pre-conditions:
1. The VAL server has discovered and selected the SEALDD server by CAPIF functions as specified in clause 9.4.2.
2. The SEALDD server has subscribed to 5GC for QoS monitoring of the specific UE related to the VAL user, as defined in clause 5.2.6.9 in 3GPP TS 23.502 [6].
3. The SEALDD policy (i.e, the bandwidth control policy) has been configured in SEALDD server, as described in clause 9.10.
Figure 9.8.2.1-1: SEALDD enabled bandwidth control transmission procedure
1. The VAL server sends a Sdd_regularTransmission request to the SEALDD server. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), the VAL server’s total bandwidth limit and the bandwidth limits (i.e. minimum bandwidth requirement and maximum bandwidth limit) for VAL users.
2. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server sends a response to the VAL server.
3. The VAL client sends a SEALDD service request to SEALDD client.
4. The VAL/SEALDD client discover and select the proper SEALDD server for the VAL application. After this step, the VAL server is discovered and selected along with the associated SEALDD server, the SEALDD client gets the SEALDD server's address.
5. The SEALDD client sends Sdd_RegularTransmissionConnection_Establish request to SEALDD server with the SEALDD client ID, the VAL user or UE identity, XR application device capability information as per Table 9.2.3.3-1. The SEALDD client retrieves the capability information as per the 3GPP TS 26.118 [20] clause 9.2.3 and clause 9.2.6.
6. The SEALDD server performs bandwidth limit check according to the VAL user’s bandwidth limit, the current SEALDD traffic delivery status, the VAL server’s total bandwidth limit and/or the related UE’s current network status (i.e. via QoS monitoring report from the 5GC). If the available bandwidth (i.e. the remaining bandwidth that is used for the VAL user without exceeding the VAL server’s total bandwidth limit) fails to meet the VAL user’s minimum bandwidth requirement, the SEALDD server will reject the SEALDD client’s connection establishment request.
7. When the available bandwidth meets the VAL user’s requirement, the SEALDD client establishes the SEALDD connection with the SEALDD server. The SEALDD server calculates the suggested traffic transmission bandwidth to the SEALDD client according to the VAL user’s bandwidth limit and the related UE’s current network status (i.e. via QoS monitoring report or ECN marking for L4S report from the 5GC) and XR application device capability information (e.g., codec).
8. If the bandwidth limit check is failed (i.e., the available bandwidth fails to meet the VAL user’s minimum bandwidth requirement) in step 6, the SEALDD server sends Sdd_RegularTransmissionConnection_Establish response with the failed result (i.e., reject the connection establishment) and the pending timer to trigger the re-connection from SEALDD client. If the bandwidth limit check is successful (i.e., the available bandwidth meets the VAL user’s requirement) in step 6, the SEALDD server sends Sdd_RegularTransmissionConnection_Establish response with the successful result and/or the suggested traffic transmission bandwidth.
NOTE: The SEALDD server can re-allocate the available bandwidth resource to different VAL users according to the configured bandwidth control policy, as described in clause 9.10.
If the connection establishment is rejected, the SEALDD client re-establishes SEALDD connection by performing steps 5-8, when the pending timer is expired.
For the uplink application traffic, the SEALDD client buffers or drops some packets when the uplink traffic from VAL client exceeds the suggested traffic transmission bandwidth. Similarly, for the downlink application traffic, the SEALDD server buffers or drops some packets when the downlink traffic from VAL server exceeds the suggested traffic transmission bandwidth.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.8.2.2 SEALDD enabled congestion control for VAL applications
|
Based on the congestion information exposed by 5GS (i.e., by using ECN marking for L4S), the SEALDD server performs the differentiated congestion control for multiple VAL applications, after receiving the L4S feedback from the SEALDD client. Figure 9.8.2.2-1 illustrates the procedure for SEALDD enabled congestion control for VAL applications.
Pre-conditions:
1. The VAL server has discovered and selected the SEALDD server by CAPIF functions as specified in clause 9.4.2.
Figure 9.8.2.2-1: SEALDD enabled congestion control procedure
1-6. Same as clause 9.2.2.2 step 1 to step 7 with difference that in step 5 the SEALDD client includes also L4S feedback capability in Sdd_RegularTransmissionConnection_Establish request.
7. If the L4S feedback capability is received in step 5, the SEALDD server requests 5GC to perform the ECN marking for L4S for the required VAL applications by utilizing the AF session with required QoS procedure in clause 4.15.6.6 of 3GPP TS 23.502 [6].
8. Same as step 9 of clause 9.2.2.2.
9. For downlink traffic, if ECN marking is identified, the L4S feedback is performed in transport layer.
10. After receiving the L4S feedback in step 9, the SEALDD server may perform the congestion mitigation for downlink traffics from multiple VAL applications. For the same UE, the SEALDD server determines differentiated congestion control/rate control with the calculated congestion level or the calculated transmission rate for multiple VAL applications based on internal policy considering the received QoS requirements of different VAL applications identified by VAL service ID in step 1.
11. [Optional] The SEALDD server sends Sdd_connection status notification to VAL server with the calculated congestion level for the VAL service.
NOTE 1: According to the congestion level provided by SEALDD server, the VAL server supporting media can perform congestion control, e.g. by adjusting the encoding scheme, and rendering scheme, etc.
NOTE 2: Step 11 is performed if the SEALDD server cannot perform transmission rate adaptation to mitigate the congestion by itself.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.8.3 Information flows
|
See clause 9.2.3 for the details of information flow.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.8.4 APIs
|
See clause 9.2.4 for the details of API.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9 SEALDD enabled data transmission quality guarantee
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.1 General
|
The following clauses specify procedures, information flows and APIs for SEALDD enabled data transmission quality guarantee.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.2 Procedures
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.2.1 SEALDD enabled data transmission quality guarantee by switching SEALDD server
|
Figure 9.9.2.1-1 illustrate the procedure for data transmission quality guarantee based on transmission quality report from SEALDD server and QoS monitoring from 5GS. The procedure is applicable to the scenario where there is a single path between UE and SEALDD server.
Pre-conditions:
1. The VAL server discovers and selects the SEALDD server by CAPIF functions.
2. The VAL server has requested the transmission quality measurement to the SEALDD server by invoking the Sdd_TransmissionQualityMeasurement_subscription API in clause 9.7.4.2.
3. A SEALDD service policy (i.e., the necessary SEALDD layer actions for meeting the service policy requirements) has been configured in SEALDD server and shared with the SEALDD client.
Figure 9.9.2.1-1: SEALDD enabled data transmission quality guarantee procedure by switching SEALDD server
1. The VAL server sends a Sdd_RegularTransmission request to the SEALDD server, as specified in clause 9.2.2.2. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), and optionally, the QoS information for the application traffic, e.g. QoS requirements.
2. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server sends a response to the VAL server. The QoS information may be allocated by SEALDD server according to VAL service ID for different service type of application traffic if the QoS information is not provided by VAL server.
3. The regular data transmission connection is established according to clause 9.2.2.2.
4. The S-SEALDD server (i.e., SEALDD server#1) generates the transmission quality measurement report according to the SEALDD enabled transmission quality measurement procedure in clause 9.7.2.1, and detects whether the current transmission quality satisfies the QoS requirements of VAL application.
5. The S-SEALDD server subscribes to 5GC for QoS monitoring of the specific UE related to the VAL user, as defined in clause 5.2.6.9 in 3GPP TS 23.502 6]. If the S-SEALDD server diagnoses that QoS deterioration is caused by N6/SEALDD overload (i.e., based on QoS monitoring between UE and UPF, and the E2E transmission quality measurement). The S-SEALDD server determines to trigger the data transmission quality guarantee procedure (i.e., switching the connected SEALDD server according to SEALDD service policy) based on the QoS monitoring and E2E transmission quality measurement.
NOTE 1: The QoS monitoring subscription request may be triggered after step 4 when the current transmission quality cannot satisfy the QoS requirements of VAL application.
NOTE 2: This procedure cannot solve the QoS deterioration issue caused by NG-RAN (e.g. RAN congestion).
6. The S-SEALDD server performs target SEALDD server discovery procedure by using EEL, as specified in clause 9.4.
7. The S-SEALDD server selects the T-SEALDD server (i.e., SEALDD server #2) based on N6 traffic and/or SEALDD server load from performance of the available target SEALDD servers in step 6.
8. The SEALDD relocation procedure is performed for the switched SEALDD servers and the switched VAL servers, as specified in clause 9.6.2.2.
After the SEALDD relocation procedure, the SEALDD client connects to the selected T-SEALDD server to obtain the data transmission quality guarantee service (i.e. the QoS requirements of VAL application is satisfied).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.2.2 SEALDD enabled data transmission quality guarantee with redundant transport
|
Figure 9.9.2.2-1 illustrates the procedure of using redundant transmission as the action to meet connection reliability requirements specified by a SEALDD service policy.
Pre-conditions:
1. A SEALDD service policy, which includes data transmission quality guarantees, is available to SEALDD server. The policy is used to configure measurements and determine the necessary SEALDD layer actions for meeting the service policy requirements.
2. The SEALDD Client is authorized to request redundant transport services on behalf of the VAL client.
Figure 9.9.2.2-1: SEALDD data transmission quality guarantee with redundant transmission
1. A VAL client and server establish a SEALDD connection to transport the application data. As part of the connection establishment, the SEALDD service policy in precondition 1 is shared so that it is available to both the SEALDD client and the SEALDD Server. The SEALDD Server may use the data transmission quality requirements of this policy in conjunction with other local policies pre-provisioned at the SEALDD server. The SEALDD server determines whether to start data transmission quality measurement by itself or by the SEALDD client. As a result, SEALDD measurements (e.g. packet loss rate, latency) are configured either at the SEALDD client as described in clause 9.7.2.3 or at the SEALDD server as described in clause 9.7.2.1 and started accordingly. Then either the SEALDD client or server receives measurement reports.
2. Based on measurement reports and the SEALDD service policy, depending on the which entity started the measurement, either the SEALDD client or server determines to perform an action so that the data transmission quality requirements of the policy are met.
3. Specifically, if the measurement was started by the SEALDD client, the SEALDD client triggers the establishment of redundant transmission services. If the measurement was started by the SEALDD server, the SEALDD server triggers the establishment of redundant transmission services by sending a Transmission quality management request to the SEALDD client requesting to establish redundant transmission path.
NOTE: The request can be sent to SEALDD client via Application Triggering (specified in clause 4.13.2 of 3GPP TS 23.502 [6]) with payload indicating a trigger of a redundant connection setup for SEALDD packet transmission.
4. The SEALDD client uses steps 6 to 9 of the procedure in clause 9.3.2.1 to request the use of redundant transmission service from the SEALDD server. As part of this step, the UE may end the initial PDU session and establish redundant PDU sessions.
5. The SEALDD client updates the SEALDD connection with the redundant transmission information, i.e., the UE addresses and ports for the redundant PDU sessions, the SEALDD-UU flow identifier, and the application traffic descriptors. The SEALDD client or server also configures the parameters for enabling any necessary SEALDD measurements for the new SEALDD-UU flow.
6. The SEALDD server may subscribe to receive notifications from the 5G network for user plane measurements (e.g., the network latency requirements specified in 3GPP TS 28.541 [12]), network analytics (as specified in 3GPP TS 28.104 [11], etc.).
7. The SEALDD client and server handle data duplication and elimination of application traffic on the redundant SEALDD-UU flows and the necessary measurements are collected by the SEALDD client or server.
When the SEALDD measurement results indicating that the SEALDD data transmission has good performance according to policy guarantee threshold, if the measurement was started by the SEALDD client, the SEALDD client may release one transmission path and return back to single SEALDD connection mode, otherwise the SEALDD server may send a Transmission quality management request to the SEALDD client requesting to use single transmission, then the SEALDD client releases one transmission path and returns to single SEALDD connection mode.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.2.3 SEALDD enabled data transmission quality guarantee with BAT and periodicity adaptation
|
Figure 9.9.2.3-1 illustrates the procedure of using 3GPP CN (5GS) capability for BAT and periodicity report and application layer adjustment in SEALDD layer for data transmission.
Precondition:
- SEALDD layer connection needs to be established as described in clause 9.2 and clause 9.3.
- In policy driven SEALDD connection management, the VAL server has indicated quality optimization policy during SEALDD policy configuration procedure as described in clause 9.10.
Figure 9.9.2.3-1: SEALDD data transmission quality guarantee with BAT and periodicity adaptation
1. A VAL client and server establish a SEALDD regular or redundant connection to transport the application data as described in clause 9.2 or clause 9.3. The connection establishment may be triggered by either SEALDD server or SEALDD client. During the connection establishment, the SEALDD client includes an indication for data transmission adjustment request as part of the connection establishment over SEALDD-UU reference point.
In SEALDD-UU connection establishment, the SEALDD client also includes its capability for BAT and periodicity adaptation, or transmission assistance info to the SEALDD server in the connection establishment request (SEALDD client triggered establishment) or response (SEALDD server triggered establishment).
2. The SEALDD server, based on received data transmission adjustment request from VAL server or SEALDD client, its own capability and/or received capability from SEALDD client for BAT and periodicity adaptation, and its own DL transmission assistance info and/or received transmission assistance info from SEALDD client, subscribes to 5GS AF session with QoS service with capability for BAT adaptation or transmission assistance info as described in clause 4.15.6.6 and 4.16.6.4 of 3GPP TS 23.502 [6].
3. The SEALDD server receives BAT offset and optionally a proposed periodicity (which was adjusted in 5GS) in AF session with QoS notification from 5GS.
4. If the SEALDD client indicated its BAT and periodicity adaptation capability in step 1 during SEALDD connection establishment, the SEALDD server sends UL periodicity and BAT window to the SEALDD client in Transmission quality management request with transmission parameter adjustment action.
5. The SEALDD client applies UL periodicity and BAT offset for uplink SEALDD data.
6. The SEALDD server locally applies DL periodicity and BAT offset for downlink SEALDD data.
NOTE: Step 6 can happen before step 5, and step 3 to 6 can be repeated.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.2.4 SEALDD enabled data transmission quality guarantee using Non-3GPP access
|
Figure 9.9.2.4-1 illustrates the procedure of using non-3gpp access for SEALDD enabled data transmission quality guarantee.
Pre-conditions:
1. The SEALDD Client is authorized to use non-3GPP access on behalf of the VAL client.
Figure 9.9.2.4-1: SEALDD enabled data transmission quality guarantee using Non-3GPP access
1. A regular data transmission connection is established according to clause 9.2.2.2 or via clause 9.3.2.3 and SEALDD data transmission measurement reporting as per clause 9.7.2.1 or clause 9.7.2.2 to get the data transmission quality.
2. If Non-3GPP access measurement policy is available in the SEALDD server, the SEALDD server requests the SEALDD client to report the latest Non-3GPP access measurements(like RSSI for the WLAN SSIDs) as per steps 3-4 of the procedure defined in clause 9.2.2.6.
If Non-3GPP access measurement policy is not available, the SEALDD server fetches the UE location using the SEAL location service defined in 3GPP TS 23.434 [4] clause 9.3.12 and requests the SEALDD client to report the latest Non-3GPP access measurements of the nearby WLAN SSIDs. The SEALDD server uses the steps 3-4 of the procedure defined in clause 9.2.2.6 to get the report from the SEALDD client.
If the Non-3GPP access measurement values in the data transmission quality report or SEALDD connection status report defined in clause 9.2.2.6 are above the Signal strength thresholds mentioned in SEALDD Non-3GPP access measurement policy then the SEALDD server offloads the SEALDD-UU connection from 3GPP access to Non-3GPP access(WLAN) using steps 5-6.
3. The SEALDD server subscribes to NWDAF analytics service for subscription to network performance analytics with Analytics ID as Network Performance using the procedure described in clause 6.6.4 3GPP TS 23.288 [19]. It also subscribes to PDU Session traffic analytics service using the procedure defined in clause 6.20 3GPP TS 23.288 [19].
The SEALDD server subscribes to WLAN performance analytics using the procedure defined in clause 6.11 3GPP TS 23.288 [19]. The SEALDD server uses the SEALDD Non-3GPP access measurement policy information or information received in step 2 for subscription to WLAN performance analytics.
4. Based on SEALDD client Non-3GPP access measurement reports, NWDAF analytics measurement reports(including predicted values), and data transmission quality measurement reports, the SEALDD server detects the 3GPP RAN congestion and determines to use non-3GPP access to meet the data transmission quality requirements.
5. The SEALDD server requests 5GS to create or update URSP rules using clause 4.15.6.10 of 3GPP TS 23.502 [6] to establish a PDU session connection over Non-3GPP access. The SEALDD server creates a URSP rule with Access Type Route selection descriptors as non-3GPP to establish PDU session. The request may include the UE ID and application traffic descriptor containing the addresses or ports allocated by SEALDD server.
6. The UE receives the new or updated URSP rules from the 5G core network. Based on the URSP rules, the UE establishes a PDU session connectivity over non-3GPP access with the 5GS.
7. On the successful establishment of PDU session connection over Non-3GPP access, the SEALDD client updates the SEALDD data transmission connection with the updated SEALDD client IP address as per steps 7-8 mentioned in clause 9.3.2.2.
Based on continuous monitoring and measurement reports, the SEALDD server decides to switch back to 3GPP access and use the SEALDD-UU connection over 3GPP access for data transmission.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.2.5 SEALDD enabled data transmission quality guarantee to support the user group level QoS
|
Figure 9.9.2.5-1 illustrates the procedure to support the user group level QoS guarantee. The user group level QoS guarantee provides different QoS for different users in single service(e.g., XR service).
Pre-conditions:
1. The SEALDD server acts as NSaaS provider, and is authorized to get network slice related information and capabilities in Network Slice ServiceProfile (3GPP TS 28.541 [12]) from NSCE server as defined in 3GPP TS 23.435 [21].
2. The SEALDD policy for a group of users has been configured, by providing the VAL UE group ID (as defined in clause 7.5 of 3GPP TS 23.434 [4]), VAL UE identity list, or slice identifier in the SEALDD policy configuration request.
Figure 9.9.2.5-1: procedure of supporting the user group level QoS guarantee
1. The regular data transmission connection is established according to clause 9.2.2.2.
2a. Based on the configured SEALDD policy and network slice related information received from NSCE, the SEALDD server determines whether the slice related communication service lifecycle management is needed, based on Network slice information, e.g., Slice Coverage Area, Latency, and, Data volume, which specify the Network Slice characteristics, as specified in clause of ServiceProfile in 3GPP TS 28.541 [12]. If the performance of network slice identified by the provided Slice identifier is not satisfying, the SEALDD server could trigger slice related communication service Reconfiguration.
If the network slice related information of network slice identified by the provided Slice identifier is not received from NSCE before, the SEALDD server obtains the Network slice information by invoking the Network Slice Information delivery as defined in 3GPP TS 23.435 [21], clause 9.17.
Before triggering the network slice management service, to determine the target UE of network slice(s), the SEALDD server acting as AF, may receive a UE location report or a monitoring event report from 5GC (assuming that SEALDD server has subscribed to consume 5GC services like LCS or NEF monitoring events related to UE actual location, or UE mobility analytics from NWDAF) or Location service from SEAL.
2b. Based on the configured SEALDD policy, the SEALDD server initiates AF session with required QoS as defined in 3GPP TS 23.502 [6], clause 4.15.6.6a, or Multi-member AF session with required QoS as defined in 3GPP TS 23.502 [6], clause 4.16.5.3, or QoS/resource management capability provided by SEAL NRM as defined in 3GPP TS 23.434 [4], clause 14.3.5.2.
2c. Based on the configured SEALDD policy, the SEALDD server determines whether the SEALDD enabled bandwidth control is needed. If needed(e.g., multiple user groups have different bandwidth requirements), the SEALDD server may initiate the SEALDD enabled bandwidth control for different VAL users as defined in 3GPP TS23.433, clause 9.8.2.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.3.1 Transmission quality management request
|
Table 9.9.3.1-1 describes the information flow from the SEALDD server to the SEALDD client for requesting data transmission quality management.
Table 9.9.3.1-1: Transmission quality management request
Information element
Status
Description
SEALDD-UU flow ID
M
Identifier of the SEALDD-UU flow.
Transmission quality management action
M
Indicates the data transmission quality guarantee action (e.g. redundant transmission path, re-establish transmission path, switch to backup transmission path) or optimization action (back to single transmission path, transmission parameter adjustment) that triggering by event (e.g. measurement threshold).
UL periodicity (NOTE)
O
Uplink periodicity.
BAT offset for UL (NOTE)
O
BAT offset for Uplink data.
NOTE: The IE is applicable for transmission parameter adjustment.
NOTE: The triggering event (e.g. measurement threshold) is changeable with the transmission quality guarantee event.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.3.2 Transmission quality management response
|
Table 9.9.3.2-1 describes the information flow from the SEALDD client to the SEALDD server for responding to the transmission quality management request.
Table 9.9.3.2-1: Transmission quality management response
Information element
Status
Description
Result
M
Success or failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.4.1 General
|
Table 9.9.4.1-1 illustrates the APIs exposed by SEALDD client for data transmission quality management.
Table 9.9.4.1-1: API list for transmission quality management
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_TransmissionQuality Management
Request
Request/Response
SEALDD server
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.9.4.2 Sdd_TransmissionQualityManagement Request operation
|
API operation name: Sdd_TransmissionQualityManagement Request
Description: The consumer requests for one time for transmission quality management.
Inputs: See clause 9.9.3.1.
Outputs: See clause 9.9.3.2
See clause 9.9.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10 SEALDD policy configuration
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.1 General
|
The following clauses specify procedures, information flow for SEALDD policy configuration. In clause 9.10, the VAL server is a specific server for configurating SEALDD policy, and is different from the VAL server used for VAL application processing in other clauses.
Depending on the configuration, a SEALDD policy may apply to individual SEALDD flows or to multi-modal SEALDD flows.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.2 Procedures
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.2.1 SEALDD policy configuration
|
Figure 9.10.2.1-1 illustrates the procedure for SEALDD policy configuration from the VAL server used for SEALDD policy configuration to the SEALDD server.
Figure 9.10.2.1-1: SEALDD policy configuration
1. The VAL server sends the SEALDD policy configuration request to the SEALDD server. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), VAL UE identify, and the SEALDD policy.
2. The SEALDD server performs authorization check to verify whether the VAL server is accepted/authorized to configure the SEALDD policy.
3. Upon successful authorization, the SEALDD server stores the SEALDD policy for later use (e.g. for bandwidth control, transmission quality guarantee) and replies to the VAL server with the SEALDD policy configuration response.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.2.2 SEALDD policy configuration update
|
Figure 9.10.2.2-1 illustrates the procedure for SEALDD policy configuration update from the VAL server used for SEALDD policy configuration to the SEALDD server.
Figure 9.10.2.2-1: SEALDD policy configuration update
1. The VAL server used for SEALDD policy configuration determines that the existing SEALDD policy needs to be updated, the VAL server sends the SEALDD policy configuration update request to the SEALDD server.
2. The SEALDD server performs authorization check to verify whether the VAL server is accepted/authorized to update the SEALDD policy configuration.
3. Upon successful authorization, the SEALDD server updates the SEALDD policy configuration and replies to the VAL server with the SEALDD policy configuration update response.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.2.3 SEALDD policy configuration delete
|
Figure 9.10.2.3-1 illustrates the procedure for SEALDD policy configuration delete from the VAL server used for SEALDD policy configuration to the SEALDD server.
Figure 9.10.2.3-1: SEALDD policy configuration delete
1. The VAL server used for SEALDD policy configuration determines that the existing SEALDD policy needs to be deleted, the VAL server sends the SEALDD policy configuration delete request to the SEALDD server.
2. The SEALDD server performs authorization check to verify whether the VAL server is accepted/authorized to delete the SEALDD policy configuration.
3. Upon successful authorization, the SEALDD server deletes the SEALDD policy configuration and replies to the VAL server with the SEALDD policy configuration update response.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.2.4 SEALDD client policy configuration request
|
Figure 9.10.2.4-1 illustrates the procedure for SEALDD client policy configuration request from the SEALDD server to the SEALDD client.
Pre-condition:
1. The SEALDD connectivity has been established between the SEALDD client and SEALDD server.
Figure 9.10.2.4-1: SEALDD client policy configuration request
1. Based on policy received from the VAL server(e.g., Multi-modal flows alignment policy), or SEALDD server determines that the policy needs to be configured to the SEALDD client, the SEALDD server sends the SEALDD client policy configuration request to the SEALDD client.
2. The SEALDD client performs authorization check to verify whether the SEALDD server is authorized to configure the SEALDD client policy.
3. Upon successful authorization, the SEALDD server stores the SEALDD client policy for later use (e.g. for multi-modal flows alignment) and replies to the SEALDD server with the SEALDD client policy configuration response.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.2.5 SEALDD client policy configuration update request
|
Figure 9.10.2.5-1 illustrates the procedure for SEALDD client policy configuration update request from the SEALDD server to the SEALDD client.
Pre-condition:
1. The SEALDD connectivity has been established between the SEALDD client and SEALDD server.
Figure 9.10.2.5-1: SEALDD client policy configuration update request
1. Based on policy received from the VAL server, or SEALDD server determines that the policy needs to be updated to the SEALDD client, the SEALDD server sends the SEALDD client policy configuration update request to the SEALDD client.
2. The SEALDD client performs authorization check to verify whether the SEALDD server can be authorized to update the SEALDD client policy.
3. Upon successful authorization, the SEALDD client updates the SEALDD client policy and replies to the SEALDD server with the SEALDD client policy configuration update response.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.2.6 SEALDD client policy configuration delete request
|
Figure 9.10.2.6-1 illustrates the procedure for SEALDD client policy configuration delete request from the SEALDD server to the SEALDD client.
Pre-condition:
1. The SEALDD connectivity has been established between the SEALDD client and SEALDD server.
Figure 9.10.2.6-1: SEALDD client policy configuration delete request
1. Based on request received from the VAL server, or SEALDD server determines that the policy needs to be deleted, the SEALDD server sends the SEALDD client policy configuration delete request to the SEALDD client.
2. The SEALDD client performs authorization check to verify whether the SEALDD server can be authorized to delete the SEALDD client policy.
3. Upon successful authorization, the SEALDD client deletes the SEALDD client policy and replies to the SEALDD server with the SEALDD client policy configuration delete response.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.1 SEALDD policy configuration request
|
Table 9.10.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the SEALDD policy configuration.
Table 9.10.3.1-1: SEALDD policy configuration request
Information element
Status
Description
Application traffic identifiers
M
Identify of the application traffic (e.g. VAL server ID, VAL service ID).
Identities
O
Identifier of the VAL UEs or VAL users, or VAL UE group ID(as defined in clause 7.5 of 3GPP TS 23.434 [4]), or VAL UE identity list for which SEALDD policy applies
Slice identifier
O
The slice identifier (S-NSSAI) for which SEALDD policy applies.
SEALDD policy
O
(See NOTE 4)
The SEALDD policy associated with application traffic identifiers, VAL UE identity.
> Quality guarantee policy
O
(See NOTE 1)
Indicates the event (e.g. measurement threshold) to be measured for the quality guarantee
> Quality optimization policy
O
(See NOTE 1)
Indicates the data transmission adjustment policy (e.g., adjustment need) to be performed in SEALDD layer.
> Bandwidth control policy
O
(See NOTE 2)
Indicate the bandwidth control preference, e.g. re-allocating the bandwidth limit between different VAL users, including UL/DL
> Geofence policy
O
(See NOTE 3)
Indicates the geofence policy per VAL service.
>> Geofence location
O
(See NOTE 3)
Indicates the geofence location information for the mentioned VAL service
>>Geofence policy action
O
(See NOTE 3)
Indicates the policy action like allowed or blocked.
> temporal policy
O
(See NOTE 3)
Indicates the time period for which the sealdd traffic is allowed
> policy expiration time
O
Indicates the validity of the policy.
> Non-3GPP access measurement policy
O
Indicates the non-3GPP access (like WLAN) measurement policy (e.g. WLAN SSIDs/BSSID, signal strength thresholds(high/low), time-based threshold for offload to WLAN).
Multi-modal SEALDD policy
O
(See NOTE 4)
Multi-modal SEALDD policy associated with set of individual SEALDD flows.
> Synchronization policy
O
Indicates the synchronization threshold for multi-modal application, as specified in 3GPP TS 22.261 [2].
> Multi-modal flows alignment policy
O
Indicates the information to do the multi-modal flows alignment, e.g., Multi-modal Service ID, maximum acceptable duration for traffic flow alignment.
> Policy expiration time
O
Indicates the validity period of the policy.
> UE-to-UE policy
O
Specifies UE-to-UE direct communication policy including proximity threshold, QoS threshold (e.g. bitrate, latency and jitter, PLR, PER) or QoE threshold (e.g. MOS as specified in ITU-T P.1203.3 [18]) for entering direct communication mode, and proximity threshold, QoS threshold or QoE threshold for leaving direct communication mode.
NOTE 1: This IE is used for the SEALDD enabled transmission quality guarantee, as specified in clause 9.9.
NOTE 2: This IE is used for the SEALDD enabled bandwidth control, as specified in clause 9.8.
NOTE 3: This IE is used for the SEALDD connection establishment and data delivery, as specified in clause 9.2
NOTE 4: At least one of these IEs shall be present.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.2 SEALDD policy configuration response
|
Table 9.10.3.2-1 describes the information flow from the SEALDD server to the VAL server for responding to the SEALDD policy configuration.
Table 9.10.3.2-1: SEALDD policy configuration response
Information element
Status
Description
Result
M
Success or failure.
> Configuration ID
O
(See NOTE)
Identifier of the SEALDD policy configuration.
> Expiration time
O
(See NOTE)
Indicates the expiration time of the configured SEALDD policy
NOTE: These IEs are used for the successful case for SEALDD policy configuration request.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.3 SEALDD policy configuration update request
|
Table 9.10.3.3-1 describes the information flow from the VAL server to the SEALDD server for requesting the SEALDD policy configuration update.
Table 9.10.3.3-1: SEALDD policy configuration update request
Information element
Status
Description
Configuration ID
M
Identifier of the SEALDD policy configuration.
Updated SEALDD policy
O
The updated SEALDD policy as described in Table 9.10.3.1-1.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.4 SEALDD policy configuration update response
|
Table 9.10.3.4-1 describes the information flow from the SEALDD server to the VAL server for responding to the SEALDD policy configuration update.
Table 9.10.3.4-1: SEALDD policy configuration update response
Information element
Status
Description
Result
M
Success or failure.
> Expiration time
O
(See NOTE)
Indicates the expiration time of the configured SEALDD policy
NOTE: This IEs is used for the successful case for SEALDD policy configuration update request.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.5 SEALDD policy configuration delete request
|
Table 9.10.3.5-1 describes the information flow from the VAL server to the SEALDD server for requesting the SEALDD policy configuration delete.
Table 9.10.3.5-1: SEALDD policy configuration delete request
Information element
Status
Description
Configuration ID
M
Identifier of the SEALDD policy configuration.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.6 SEALDD policy configuration delete response
|
Table 9.10.3.6-1 describes the information flow from the SEALDD server to the VAL server for responding to the SEALDD policy configuration delete.
Table 9.10.3.6-1: SEALDD policy configuration delete response
Information element
Status
Description
Result
M
Success or failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.7 SEALDD client policy configuration request
|
Table 9.10.3.7-1 describes the information flow from the SEALDD server to the SEALDD client for requesting SEALDD client policy configuration.
Table 9.10.3.7-1: SEALDD client policy configuration request
Information element
Status
Description
Requestor ID
M
Identity of the requestor
SEALDD flow ID
O
(NOTE)
Identity of the SEALDD flow
Multi-modal SEALDD flow ID
O
(NOTE)
Identity of the multi-modal SEALDD flows associated with the SEALDD multi-modal connection
VAL service ID
M
Identity of the VAL service
UE ID
O
Identifier of specific UE or VAL user
>Configuration ID
M
Identifier of the SEALDD policy configuration.
Multi-modal flows alignment policy
O
Multi-modal flows alignment Policy
>Multi-modal Service ID
O
Identifier of Multi-modal Service
>Flows transmission requirement
O
Flows transmission requirement including the delay requirement, maximum acceptable duration for traffic flow alignment. Maximum acceptable time duration for traffic flow alignment is used to limit the maximum waiting time. for the associated flow
SEALDD UE-to-UE policy
O
Specifies UE-to-UE direct communication policy including, QoS threshold (e.g. bitrate, latency and jitter, PLR, PER) for entering direct communication mode, and QoS threshold for leaving direct communication mode.
NOTE: At least one of these IEs shall be present in the message.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.8 SEALDD client policy configuration response
|
Table 9.10.3.8-1 describes the information flow from the SEALDD server to the VAL server for response SEALDD client policy configuration.
Table 9.10.3.8-1: SEALDD client policy configuration response
Information element
Status
Description
Result
M
Success or failure of the request.
Configuration ID
M
Identifier of the SEALDD client policy.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.9 SEALDD client policy configuration update request
|
Table 9.10.3.9-1 describes the information flow from the SEALDD server to the SEALDD client for requesting SEALDD client policy configuration update.
Table 9.10.3.9-1: SEALDD client policy configuration update request
Information element
Status
Description
Configuration ID
M
Identifier of the SEALDD client policy.
Updated SEALDD client policy
O
The updated SEALDD client policy.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.10 SEALDD client policy configuration update response
|
Table 9.10.3.10-1 describes the information flow from the SEALDD server to the VAL server for response SEALDD client configuration policy update.
Table 9.10.3.10-1: SEALDD client policy configuration update response
Information element
Status
Description
Result
M
Success or failure of the request.
Configuration ID
M
Identifier of the SEALDD client policy.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.11 SEALDD client policy configuration delete request
|
Table 9.10.3.11-1 describes the information flow from the SEALDD server to the SEALDD client for requesting SEALDD client policy configuration delete.
Table 9.10.3.11-1: SEALDD client policy configuration delete request
Information element
Status
Description
Configuration ID
M
Identity of the SEALDD client policy.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.3.12 SEALDD client policy configuration delete response
|
Table 9.10.3.12-1 describes the information flow from the SEALDD server to the VAL server for response SEALDD client policy Configuration delete.
Table 9.10.3.12-1: SEALDD client policy configuration delete response
Information element
Status
Description
Result
M
Success or failure of the request.
Configuration ID
M
Identifier of the SEALDD client policy.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.4.1 General
|
Table 9.10.4.1-1 illustrates the APIs exposed by SEALDD server for SEALDD policy configuration.
Table 9.10.4.1-1: List of SEALDD server APIs for policy configuration
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_PolicyConfiguration
Request
Request/Response
VAL server
Update
Delete
Sdd_ClientPolicyConfiguration
Request
Request/Response
SEALDD server
Update
Delete
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.4.2 Sdd_PolicyConfiguration operation
|
API operation name: Sdd_PolicyConfiguration_Request
Description: The consumer requests for one time for SEALDD policy configuration.
Inputs: See clause 9.10.3.1.
Outputs: See clause 9.10.3.2.
See clause 9.10.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.4.3 Sdd_PolicyConfiguration update operation
|
API operation name: Sdd_PolicyConfiguration_Update
Description: The consumer requests for one time for SEALDD policy configuration update.
Inputs: See clause 9.10.3.3.
Outputs: See clause 9.10.3.4.
See clause 9.10.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.4.4 Sdd_PolicyConfiguration delete operation
|
API operation name: Sdd_PolicyConfiguration_Delete
Description: The consumer requests for one time for SEALDD policy configuration deletion.
Inputs: See clause 9.10.3.5.
Outputs: See clause 9.10.3.6.
See clause 9.10.2.3 for details of the usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.4.5 Sdd_ClientPolicyConfiguration operation
|
API operation name: Sdd_ClientPolicyConfiguration_Request
Description: The consumer requests for one time for SEALDD Client policy configuration.
Inputs: See clause 9.10.3.7.
Outputs: See clause 9.10.3.8.
See clause 9.10.2.4 for details of the usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.4.6 Sdd_ClientPolicyConfiguration_Update operation
|
API operation name: Sdd_ClientPolicyConfiguration_Update
Description: The consumer requests for SEALDD Client policy configuration update.
Inputs: See clause 9.10.3.9.
Outputs: See clause 9.10.3.10.
See clause 9.10.2.5 for details of the usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.10.4.7 Sdd_ClientPolicyConfiguration_Delete operation
|
API operation name: Sdd_ClientPolicyConfiguration_Delete
Description: The consumer requests for SEALDD Client policy configuration delete.
Inputs: See clause 9.10.3.11.
Outputs: See clause 9.10.3.12.
See clause 9.10.2.6 for details of the usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11 SEALDD Background data transfer
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.1 General
|
The following clauses specify procedures and information flow for SEALDD Background data transfer (BDT). The SEALDD supports BDT in downlink (DL) centric direction, e.g., streaming a video clip to the VAL client, and in uplink (UL) centric direction, e.g., uploading drone captured data to the VAL server.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.2 Procedures
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.2.1 SEALDD background data transfer subscription
|
Figure 9.11.2.1-1 illustrates the procedure for SEALDD background data transfer subscription.
Figure 9.11.2.1-1: SEALDD background data transfer
1. The VAL server sends a SEALDD background data transfer subscription request to the SEALDD server. The request includes the VAL service ID, a list of VAL UE IDs or VAL group ID, the data volume per UE and may also include the desired time window, the desired area information (e.g., when a UE enters a geographical area), Policy Selection Guidance.
2. The SEALDD server authorizes the request from the VAL server.
3. The SEALDD server starts the BDT configuration negotiation with the SEAL NRM server as described in clause 14.3.13 of 3GPP TS 23.434 [4].
NOTE: If the NRM server is an external control plane functionality for the SEALDD server, then the SEALDD server uses step 3, otherwise SEALDD server can use procedure defined in 3GPP TS 23.502 [6] clause 4.16.7.2.
4. The SEALDD server sends the SEALDD background data transfer subscription response, containing the result of the operation which includes the result and may include the BDT subscription identifier.
5. If the SEALDD server determines that the negotiated BDT policy applies to ongoing sessions, the SEALDD server performs Network resource adaptation negotiation with the SEAL NRM server as described in clause 14.3.3.3 of 3GPP TS 23.434 [4]. Policies are set for the BDT data transfer using the previously negotiated BDT Reference ID. This step may be performed simultaneously with step 7.
6. If the SEALDD server determines that the negotiated BDT policy applies to future sessions, the SEALDD server performs the Set BDT policy for future sessions as specified in clause 4.15.6.8 of 3GPP TS 23.502 [6].
7. The VAL server uses clause 9.5.2 procedure to send the BDT data to the SEALDD server for DL centric direction. During the negotiated transmission time window, the SEALDD server sends the BDT data to SEALDD client(s) and monitors the quality, e.g., latency, jitter, bitrate, packet loss rate, of the transmission. The SEALDD client forwards the BDT data received to the VAL client.
Equivalently, for UL centric direction, during the negotiated transmission window, the SEALDD client(s) sends the BDT data to the SEALDD server. The SEALDD server forwards the BDT data received to the VAL server.
8. The SEALDD server may notify the VAL server about:
i. the delivery result, by sending the SEALDD background data transfer notification including the BDT subscription identifier and optionally the list of VAL UEs which received/sent the BDT data, the executed time window and quality of the BDT data transmission based on the measurements in step 5; or.
ii. the renogiated granted time window or the removal of BDT policy, if there is any change in the network impacting the current BDT policy and the SEAL NRM server performs BDT policy re-selection as described in clause 14.3.13.3 of 3GPP TS 23.434 [4].
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.2.2 SEALDD background data transfer subscription update
|
Figure 9.11.2.2-1 illustrates the procedure for SEALDD background data transfer subscription update from VAL server to the SEALDD server.
Pre-condition:
- The SEALDD background data transfer subscription procedure has been performed.
Figure 9.11.2.2-1: SEALDD background data transfer subscription update
1. The VAL server initiates a BDT update by sending a SEALDD background data transfer subscription update request. The request contains BDT subscription identifier and may contain e.g. updated desired time window, desired area information, Policy Selection Guidance, updated data volume per UE.
2. The SEALDD server starts a new BDT configuration negotiation with the SEAL NRM server as described in clause 14.3.13.5 of 3GPP TS 23.434 [4].
NOTE: If the NRM server is an external control plane functionality for the SEALDD server, then the SEALDD server uses step 3 otherwise SEALDD server can directly use procedure defined in 3GPP TS 23.502 [6] clause 4.16.7.2
3. The SEALDD server sends the SEALDD background data transfer subscription update response to the VAL server, containing result and the BDT subscription identifier, and, if updated, the granted time window.
4. If the SEALDD server determines that the negotiated BDT policy applies to ongoing sessions, the SEALDD may perform Network resource adaptation negotiation with the SEAL NRM server as described in clause 14.3.3.3 of 3GPP TS 23.434 [4] for the updated BDT subscription. This step may occur simultaneously with the delivery of the BDT data.
5. If the SEALDD server determines that the negotiated BDT policy applies to future sessions, the SEALDD server may perform the Set BDT policy for future sessions as specified in clause 4.15.6.8 of 3GPP TS 23.502 [6].
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.2.3 SEALDD background data transfer unsubscribe
|
Figure 9.11.2.3-1 illustrates the procedure for SEALDD background data transfer unsubscription from the VAL server to the SEALDD server.
Pre-condition:
- The SEALDD background data transfer subscription procedure has been performed.
Figure 9.11.2.3-1: SEALDD background data transfer unsubscribe
1. The VAL server may trigger a BDT deletion by sending a SEALDD background data transfer unsubscribe request to the SEALDD server. The request contains the BDT subscription identifier.
2. The SEALDD server requests the deletion of the BDT configuration to the SEAL NRM server as described in clause 14.3.13.6 of TS 23.434 [4] and deletes any stored application data related to the BDT subscription identifier.
3. The SEALDD server sends the SEALDD background data transfer unsubscribe response to the VAL server, containing result of the operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.3.1 SEALDD background data transfer subscription request
|
Table 9.11.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the SEALDD background data transfer request.
Table 9.11.3.1-1: SEALDD background data transfer subscription request
Information element
Status
Description
VAL service ID
M
Identity of the VAL service for which the background data transfer is requested.
List of VAL UE IDs
O
(See NOTE)
List of VAL UE IDs for which the transfer policy applies.
VAL group ID
O
(See NOTE)
VAL group ID for which the transfer policy applies.
Desired time window
O
Desired time window for the background data transfer.
Data volume per UE
M
Expected data volume for the background data transfer.
Desired area information
O
Desired geographical area for the background data transfer.
Policy Selection Guidance
O
List that includes guidance in selecting from multiple transfer policies provided by underlying network. Possible values include: ”lowest cost”, “highest throughput given maximum cost of X”, etc.
If not included, local and ASP-provided policies decide one among multiple transfer policies.
NOTE: One of these IEs shall be present in the message.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.3.2 SEALDD background data transfer subscription response
|
Table 9.11.3.2-1 describes the information flow from the SEALDD server to the VAL server.
Table 9.11.3.2-1: SEALDD background data transfer subscription response
Information element
Status
Description
Result
M
The result indicates success or failure.
subscription identifier
O
Indicates the background data transfer subscription identifier.
Applicable for successful result.
Granted time window
O
Granted time window for the background data transfer.
Applicable for successful result.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.3.3 SEALDD background data transfer notification
|
Table 9.11.3.2-1 describes the information flow from the SEALDD server to the VAL server.
Table 9.11.3.3-1: SEALDD background data transfer notification
Information element
Status
Description
subscription identifier
M
Indicates the background data transfer subscription identifier
List of VAL UE IDs
O
List of VAL UE IDs or VAL group ID.
Executed time window
O
The actual time window the BDT data was transferred.
Granted time window
O
If BDT renegotiation takes place, and the previously provided granted time window changed, the current granted time window for the background data transfer.
BDT transmission quality
O
Indicates the transmission quality (e.g., QoE) when transferring the BDT data between SEALDD client and SEALDD server.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.3.4 SEALDD background data transfer update subscription request
|
Table 9.11.3.4-1 describes the information flow from the VAL server to the SEALDD server for sending the SEALDD background data transfer update subscription request.
Table 9.11.3.4-1: SEALDD background data transfer update subscription request
Information element
Status
Description
subscription identifier
M
Indicates the background data transfer subscription identifier.
Desired time window
O
(See NOTE)
Desired time window for the background data transfer.
Desired area information
O
(See NOTE)
Desired geographical area for the background data transfer.
Policy Selection Guidance
O
(See NOTE)
List that includes guidance in selecting from multiple transfer policies provided by underlying network. Possible values include: ”lowest cost”, “highest throughput given maximum cost of X”, etc.
Data volume per UE
O
(See NOTE)
Updated expected data volume for the background data transfer.
NOTE: At least one of these IEs shall be present in the message.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.3.5 SEALDD background data transfer update subscription response
|
Table 9.11.3.5-1 describes the information flow from the SEALDD server to the VAL server for responding to the SEALDD background data transfer update subscription request.
Table 9.11.3.5-1: SEALDD background data transfer update subscription response
Information element
Status
Description
Result
M
The result indicates success or failure.
Subscription identifier
O
Indicates the background data transfer subscription identifier.
Applicable for successful result.
Granted time window
O
Granted time window for the background data transfer.
Applicable for successful result.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.3.6 SEALDD background data transfer unsubscribe request
|
Table 9.11.3.6-1 describes the information flow from the VAL server to the SEALDD server for requesting the SEALDD background data transfer unsubscribe request.
Table 9.11.3.6-1: SEALDD background data transfer unsubscribe request
Information element
Status
Description
subscription identifier
M
Indicates the background data transfer subscription identifier.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.3.7 SEALDD background data transfer unsubscribe response
|
Table 9.11.3.7-1 describes the information flow from the SEALDD server to the VAL server for responding to the SEALDD background data transfer unsubscribe response.
Table 9.11.3.7-1: SEALDD background data transfer unsubscribe response
Information element
Status
Description
Result
M
The result indicates success or failure of the BDT unsubscribe operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.4.1 General
|
Table 9.11.4.1-1 illustrates the APIs exposed by SEALDD server for background data transfer.
Table 9.11.4.1-1: List of SEALDD server APIs for background data transfer
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_BDT
Subscribe
Subscribe/Notify
VAL server
Notify
Subscribe/Notify
VAL server
Update
Subscribe/Notify
VAL server
Unsubscribe
Subscribe/Notify
VAL server
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.4.2 Sdd_BDT_Subscribe operation
|
API operation name: Sdd_BDT_Subscribe
Description: The consumer requests for a background data transfer service.
Inputs: See clause 9.11.3.1.
Outputs: See clause 9.11.3.2.
See clause 9.11.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.4.3 Sdd_BDT_Notify operation
|
API operation name: Sdd_BDT_Notify
Description: The consumer is notified with background data transfer result.
Inputs: See clause 9.11.3.3.
Outputs: None.
See clause 9.11.2.1 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.4.4 Sdd_BDT_Update operation
|
API operation name: Sdd_BDT_Update
Description: The consumer requests to update the SEALDD background data transfer service.
Inputs: See clause 9.11.3.4.
Outputs: See clause 9.11.3.5.
See clause 9.11.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.11.4.5 Sdd_BDT_Unsubscribe operation
|
API operation name: Sdd_BDT_Unsubscribe
Description: The consumer requests to unsubscribe the SEALDD background data transfer service.
Inputs: See clause 9.11.3.6.
Outputs: See clause 9.11.3.7.
See clause 9.11.2.3 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12 SEALDD enabled transmission for XR application
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.1 General
|
This clause provides the services to support the transmission for XR application based on SEALDD capabilities.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2 Procedures
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.1 SEALDD enabled XR data transmission service for XR application
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.1.1 General
|
The following clauses specify procedures, information flows and APIs about SEALDD enabled data transmission for XR application, including the SEALDD facilate PDU set handling.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.1.2 SEALDD enabled XR data transmission establishment
|
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 has discovered and selected the SEALDD server by CAPIF functions.
Figure 9.12.2.1.2-1: SEALDD enabled XR data transmission connection establishment procedure
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, list of requested flows, including 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. As one of key parameters for XR application, Crossflow measurement can be measured as procedure in clause 9.7.2.2 step 1.
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. The SEALDD server may send the AF request to provide the required QoS information to 5GC via N33/N5 for each requested flow provided in step 1. The AF request may also include the Multi-modal Service ID, which could be determined by the SEALDD server according to VAL service ID and/or VAL server ID.
3-5. Same as step 3-5 of clause 9.2.2.2.
6. The SEALDD client establishes XR transmission connection with the SEALDD server. The request includes the SEALDD client ID, VAL user/UE ID, VAL server ID, VAL service ID, SEALDD-UU flow IDs, and traffic descriptors for the multiple flows from the SEALDD client side. 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. The response also includes a multi-modal SEALDD-UU flow ID which the SEALDD server allocates.
7-8. Same as step 8-9 of clause 9.2.2.2.
NOTE : If multiple requested flows are provided in step 1, the SEALDD client repeats steps 6-8 for each requested flow provided in step 1.
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 3GPP TS 26.522 [TS26522]), and if needed, stream session and transport management (e.g. RTCP, RTSP).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.2 SEALDD enabled multi-modal flow synchronization
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.2.1 General
|
The following clauses specify procedures, information flows and APIs about SEALDD enabled data transmission for XR application, including SEALDD enabled multi-modal flow synchronization.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.2.2 SEALDD enabled multi-modal flow synchronization
|
Figure 9.12.2.2.2-1 illustrate the procedure for SEALDD enabled multi-modal flow synchronization, 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 has discovered and selected the SEALDD server by CAPIF functions.
- The SEALDD server has been provisioned with a multi-modal XR policy including the synchronization threshold, as specified in clause 9.10.3.1.
- The SEALDD client has been provisioned with a multi-modal SEALDD policy, as specified in clause 9.10.2.4.
Figure 9.12.2.2.2-1: SEALDD enabled multi-flow synchronization procedure
1. An on-going multi-modal data transmission connection is established according to the steps 1-8 of clause 9.12.2.1.2.
2. Upon the multi-modal flows alignment policy triggered, the SEALDD server may help to provide the flows alignment assistance information (e.g. timestamp in the RTP header, RTCP) to the SEALDD client. If the maximum acceptable duration for traffic flow alignment is not provided, then the SEALDD server may determine the maximum acceptable duration for traffic flow alignment based on VAL service ID, flows transmission requirement, transmission quality, and the synchronization threshold. The server may translate the traffic descriptor into multi-modal SEALDD flow ID.
The SEALDD server may communicate with the 5GS to get the analytics and prediction for the RAN congestion as per clause 6.6, clause 6.7, and clause 6.8 3GPP TS 23.288 [19]. Based on the RAN congestion analytics and prediction information, synchronization threshold and/or multi-modal flow alignment policy, the SEALDD server derives the delay introduced by the RAN and adjusts the flow alignment assistance information like DL/UL transmission timing advance or delay period. In case flow alignment is required, the flow alignment assistance information may contain UL/DL transmission timing advance period, UL/DL transmission timing delay period and the associated flow IDs in the multi-modal flows.
The UL flow alignment assistance information may be sent to the SEALDD client in the Transmission quality management request specified in clause 9.9.3.1.NOTE 1: The flow alignment assistance information can be obtained by SEALDD server based on SEALDD policy.
NOTE 2: The SEALDD client performs the caching and transmission to align multi-modal flows based on the flow alignments assistance information and maximum acceptable time duration.
NOTE 3: The NTP timestamp and RTP timestamp in RTCP sender report (SR) can be used to identify the associated packets among muti-modal flow, and further be used to perform alignment in SEALDD client.
NOTE 4: The option to rely on UE congestion analytics and RAN congestion analytics, as exposed by the 5GC via NWDAF has a margin of error, as with any predictions. To handle the real-time/near real-time constraint of these predictions, these UE congestion analytics can be requested ahead of time from the 5GC/NWDAF, e.g., once the XR session is started by the UE.
3. Upon the multi-modal flows alignment policy triggered, the SEALDD client initiates the multi-modal flows alignment based on the policy. The flows need to be aligned are identified by the VAL service ID, multi-modal SEALDD flow ID, and flow alignment assistance information.
If the flow alignment assistance information is provided, the SEALDD client identifies the associated packets (e.g., those with the same RTP timestamp) in the multi-modal flows. After all associated packets in the multi-modal flows have arrived, the SEALDD client sends the associated packets to the application client. If the maximum acceptable time duration is provided, once this maximum acceptable time is reached, the SEALDD client will no longer wait for the associated packets in multi-modal flows, even if they have not arrived yet.
For the UL synchronization, the SEALDD client sends the UL packets as per the flow alignment assistance information. The UL transmission timing advance period indicates SEALDD client to advance the UL packet transmission by advance period. The UL transmission timing delay period correction mode indicates SEALDD client to delay the transmission of the UL packet by UL delay period units. After all associated packets in the multi-modal flow have arrived at the SEALDD server, then the SEALDD server sends the associated UL packets to the VAL server. 4. The SEALDD server performs data transmission quality measurement, as defined in clause 9.7.2.1 or clause 9.7.2.3, 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 calculates the transmission delay measurement result of multiple associated flows after obtaining the receiving timestamp from the SEALDD client. As one of key parameters for XR application, delay difference can be measured as procedure in clause 9.7.2.3 step 10.
5. Based on the data transmission quality measurement results obtained for multiple associated flow over SEALDD-UU interface in step 4, and the synchronization threshold for multi-modal application as described in pre-condition, the SEALDD server determines 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). E.g., the SEALDD server evaluates whether the difference of the packet delay measurements for the flows that need to be in synchrony is above the synchronization threshold, and if it is so, the SEALDD server takes the corresponding corrective actions. The SEALDD server may advance or delay the transmission of the DL packets according to the flow assistance information to maintain the synchronization of DL flows. The DL transmission timing advance period correction mode indicates SEALDD server to advance the DL packet transmission by advance period. The DL transmission timing delay period correction mode indicates SEALDD server to delay the transmission of the DL packet by DL delay period units.
The SEALDD server may further update the flow alignment assistance information like DL/UL transmission timing advance or delay period to fine-tune as per the data transmission quality measurement results.
6. 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 5, by utilizing the AF session with required QoS procedure in clause 4.15.6.6 of TS 23.502 [6]. The SEALDD traffic descriptor of the adjusted flow(s) contains the address or port in SEALDD server side, and/or SEALDD client side.
NOTE: This procedure is applicable for both downlink and uplink synchronization of multi-modal flow. For downlink and/or uplink, the step 5 is determined according to the measured downlink and/or uplink data transmission quality measurements in step 4. For uplink synchronization, the SEALDD server performs the caching and transmission to align multi-modal flows based on the flow alignment assistance information before sending the associated packets to the VAL server.
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 is satisfied.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.3 Tethering link measurement and provisioning
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.3.1 General
|
The following clauses specify procedures, information flows and APIs about SEALDD enabled Tethering link measurement and provisioning for XR application.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.3.2 SEALDD and VAL coordination measurement based on PIN
|
Figure 9.12.2.3.2-1 illustrates the procedure of SEALDD and VAL coordination Tethering link measurement based on PIN.
Pre-conditions:
1. The UE or PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The UE or PINE has already been registered in PIN server;
3. The PEMC on the 3GPP device has already obtained the tethered device information from PIN server;
4. There is business agreement between the VAL provider and the SEALDD provider, which requests the VAL client to respond to ICMP Ping packet.
Figure 9.12.2.3.2-1: SEALDD and VAL coordination measurement based on PIN procedure
1. The PIN is successfully created and in use. The 3GPP UE acts as PEGC and PEMC, and the Tethered XR devices acts as a PINE. During the PIN creation, the detailed information of the tethered device has been provided to PEMC on 3GPP UE from PINAPP server as defined in clause 8.5.2, 3GPP TS 23.542 [23].
2. The regular data transmission connection is established, with the information received in step1.
The connection between the SEALDD server and 3GPP UE is established as defined in clause 9.2.2.2.
3. The VAL server sends a SEALDD transmission quality measurement subscription request to the SEALDD server as defined in clause 9.7. If authorization is successful, the SEALDD server sends a response to the VAL server with the subscription ID, expiration time.
4. The SEALDD server starts the transmission quality measurement as defined in clause 9.7.2.3. The SEALDD server sends a SEALDD transmission quality measurement subscription request to the SEALDD client and the SEALDD client responds to the SEALDD server.
5. The SEALDD client, acting as a PINE, gets the information of the tethered device from the PEMC over PIN-1, as defined in the clause 8.5.8 of 3GPP TS 23.542 [23], to identify the tethering link.
6. The SEALDD client on the 3GPP UE interacts with XR client on the tethered UE to do the measurement based on ICMP ping protocol.
7. The SEALDD client sends the report to the SEALDD server using the transmission quality measurement notification.
8. The SEALDD server reports the data transmission quality measurement results to the VAL server via the notification message.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.3.3 SEALDD measurement based on PIN
|
Figure 9.12.2.3.3-1 illustrates the procedures of SEALDD measurement based on PIN.
Pre-conditions:
1. The UE or PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The UE or PINE has already been registered in PIN server;
3. The PEMC on the 3GPP device has already obtained the tethered device information from PIN server;
Figure 9.12.2.3.3-1: SEALDD measurement based on PIN procedure
1. The PIN is successfully created and in use. The 3GPP UE acts as PEGC and PEMC, and the Tethered XR devices act as a PINE. During the PIN creation, the detailed information of the tethered device has been provided to PEMC on 3GPP UE from PINAPP server as defined in clause 8.5.2, 3GPP TS 23.542 [23].
2. The regular data transmission connection is established, with the information received in step1.
The connection between the SEALDD server and 3GPP UE is established as defined in clause 9.2.2.2.
Optionally, the SEALDD client gets the tethered device information form PEMC(e.g., the MAC address, PINE Address, Port number.) and sends the direct data transmission connection request to the tethered UE using the information form PEMC to establish a SEALDD-UUc connection between the 3GPP UE and tethered device as defined in clause 9.12.2.3.4.
3. The VAL server sends a SEALDD transmission quality measurement subscription request to the SEALDD server as defined in clause 9.7. If authorization is successful, the SEALDD server sends a response to the VAL server with the subscription ID, expiration time.
4. The SEALDD transmission quality measurement is defined in clause 9.7.2.3. The SEALDD server sends a SEALDD transmission quality measurement subscription request to the SEALDD client and the SEALDD client responds to the SEALDD server.
5. The SEALDD client gets the information of the tethered device from the PEMC over PIN-1, as defined in the clause 8.5.8 of 3GPP TS 23.542 [23], to identify the tethering link.
6. The SEALDD client on the 3GPP UE interacts with SEALDD client on the tethered UE to do the measurement based on ICMP ping protocol, or uses monitoring packet in established tethering link SEALDD connection.
7. The SEALDD client sends the report to the SEALDD server using the transmission quality measurement notification.
8. The SEALDD server sends the data transmission quality measurement results (e.g. latency, jitter, bitrate, packet loss rate) to the VAL server via the SEALDD enabled data transmission quality measurement notification as defined in clause 9.7.3.3.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.3.4 SEALDD-UUc connection establishment between the SEALDD client on 3GPP UE and tethered device
|
Depicted in figure 9.12.2.3.4-1 is the procedure for establishment of SEALDD-UUc connection between the SEALDD client on 3GPP UE and tethered device.
Figure 9.12.2.3.4-1: Establishment of SEALDD-UUc connection between the SEALDD client on 3GPP UE and tethered device
1. SEALDD client on 3GPP UE sends a SEALDD-UUc connection request to SEALDD client on tethered UE. This message includes the UE identity, SEALDD-UUc data transmission connection information(e.g., address/port allocated).
2. SEALDD client on Tethered UE initiates the procedure for mutual authentication. The successful completion of the authentication procedure completes the establishment of the SEALDD-UUc connection.
3. SEALDD client on tethered UE sends a SEALDD-UUc connection response to SEALDD client on 3GPP UE.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.4 SEALDD enabled UE-to-UE communication based on policy
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.4.1 General
|
When two VAL UEs need to communicate with each other for exchanging gaming/interactive data in XR service, they use servers in the DN as data relay or communicate with each other directly.
NOTE 1: This solution is only applicable for the XR transmission scenario without involvement of VAL server. As an example, XR gaming application client can support LAN-type of multi-player game mode without involvement of XR gaming server to process run-time game data.
In order to improve service experience (esp. for reducing service latency), SEALDD server monitors distance of UEs involved in the XR communication. When SEALDD server finds that the two UEs are within direct communication range, the SEALDD server instructs the SEALDD clients to switch to direct communication mode. Such mode switch decision needs to take E2E communication performance into consideration.
If the UE-to-UE application performance analytics result from ADAE shows the quality in off-network mode will be degraded and the quality in on-network mode is estimated to be good, or vice versa, the mode switch is done in SEALDD layer.
NOTE 2: For the same XR application service, all XR traffic flows are transmitted via either off-network or on-network between UEs.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.2.4.2 SEALDD enabled UE-to-UE communication
|
The SEALDD servers has Data Delivery (DD) policy being provisioned for UE-to-UE communication. The DD policy is enforced by the SEALDD server to switch the SEALDD connection for UE-to-UE communication (either direct or indirect).
Pre-conditions:
1. The SEALDD server has DD policies available.
2. The SEALDD clients in UE1 and UE2 has discovered the same SEALDD server.
3. The SEALDD clients in UE1 and UE2 have the ProSe application capabilities.
4. SEALDD UE-to-UE policy has been provided to SEALDD client.
Figure 9.12.2.4.2-1: Policy enforced by SEALDD server for connectivity between two UEs
1a. The UE-to-UE communication is established between UE 1 and UE 2 via SEALDD client as specified in clause 6.4.3.1 3GPP TS 23.304 [17].
1b. The SEALDD client in UE1/2 informs the SEALDD server about the establishment of direct SEALDD communication with Sdd_XRTransmissionConnnection_Inform operation.
2. Based on SEALDD UE-to-UE policy, the SEALDD server requests 3GPP CN (NWDAF/NEF) for UE relative proximity analytics for UE1 and UE2, requests 3GPP CN (GMLC/NEF) for SL/Ranging service exposure about the relative locations or distances and directions related to the UE1 and UE2, and requests ADAES for UE-to-UE application performance analytics as described in 3GPP TS 23.436 [13] clause 8.4, requests NWDAF/NEF for QoS Sustainability Analytics and Service Experience Analytics for UEs and/or requests PCF/NEF for QoS monitoring.
Editor's note: Whether SA2 provided services can support UE-to-UE communication analytics is FFS. Whether ADAES supports off-network communication analytics is FFS.
3a. According to the SEALDD UE-to-UE policy, if relative proximity analytics result shows that both UEs are not in vicinity to each other (distance between UEs > proximity threshold in UE-to-UE policy), and/or the QoS/QoE for UE-to-UE direct communication analytics result is no so good (e.g. PLR in analytics report > PLR threshold in UE-to-UE policy), the SEALDD continues with step 4 for indirect communication preparation; otherwise, the SEALDD keeps monitoring (as described in step 2) for the two UEs.
3b. According to the SEALDD UE-to-UE policy, if the ProSe discovery result shows that both UEs are not in vicinity to each other(e.g., no discovery response received), and/or the UE-to-UE application performance result(collected as defined in 3GPP TS 23.436 [13] clause 8.4 step 5) is not so good(latency in application performance result > latency in UE-to-UE policy), the SEALDD client(s) on either or both of the two UEs decides to perform path switching and continues with step 4 for indirect communication preparation.4. After establishment of SEALDD connections for UE1 and UE2, the SEALDD traffic carrying XR flows are processed in the SEALDD server. The SEALDD server forwards traffic between UE1 and UE2, and may buffer data burst from originating UE and send it to destination UE smoothly.
5. If later on, both UEs are in proximity which is capable of direct communication and the QoS/QoE analytics result from ADAES for UE-to-UE direct communication shows good quality, the SEALDD server helps to establish direct SEALDD communication by informing the SEALDD client of any of the two UEs with Sdd_XRTransmissionConnnection_Trigger operation including the information of its peer SEALDD client (of UE1 or UE2). Then the SEALDD client 1 or 2 establishes SEALDD connection towards the peer SEALDD client via SEALDD-PC5 and the SEALDD traffic carrying XR flows are exchanged directly between UE1 and UE2 via SEALDD-PC5.
Based on the monitoring and analytics result (as requested in step 2), and SEALDD UE-to-UE policy:
- if the current UE1-UE2 communication mode is direct and SEALDD server decides to switch to indirect communication mode, the SEALDD server establishes SEALDD connections with SEALDD client 1 and SEALDD client 2 as described in step 4, then triggers direct SEALDD communication release using Sdd_XRTransmissionConnnection_Trigger operation towards the SEALDD client which received establishment request in step 5 and the SEALDD client further releases the direct SEALDD connection towards its peer SEALDD client via SEALDD-PC5.
- if the current UE1-UE2 communication mode is indirect and SEALDD server decides to switch to direct communication mode, the SEALDD server triggers direct SEALDD communication setup as described in step 5 and releases SEALDD connections towards SEALDD client 1 and SEALDD client 2.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3 Information flows
|
Editor's note: Whether SEALDD enabled XR data transmission establishment service and SEALDD enabled multi-modal flow synchronization service can use the same API is FFS.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.1 SEALDD enabled XR transmission request
|
Table 9.12.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting XR transmission service.
Table 9.12.3.1-1: SEALDD enabled XR transmission request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
Identity
O
Identifier of specific UE or VAL user
List of requested flows
M
List of the requested multi-modal flows
>SEALDD-S Data transmission connection information for multi-modal XR
M
Address(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 information
O
QoS information provided by VAL server
>Protocol description
O
The 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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.2 SEALDD enabled XR transmission request
|
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.
Table 9.12.3.2-1: SEALDD enabled XR transmission response
Information element
Status
Description
Result
M
Success or failure.
SEALDD-S information Data transmission connection information for multi-modal XR
O
Address(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)
Cause
O
(See NOTE)
Indicates the reason for the failure
NOTE: The IE is only present if the Result is failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.3 SEALDD XR transmission connection establishment request
|
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.
Table 9.12.3.3-1: SEALDD XR transmission connection establishment request
Information element
Status
Description
SEALDD client ID
M
Identity of the SEALDD client.
Identity
O
The VAL user ID of the VAL user or VAL UE ID
SEALDD-UU flow IDs
M
Identity of the SEALDD-UU flows.
VAL server ID
O
Identity of the VAL server.
VAL service ID
O
Identity of the VAL service.
SEALDD traffic descriptors
O
SEALDD 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.