Content for TS 23.433 Word version: 19.4.0
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.13 SEALDD enabled adaptive data transmission |R19| p. 126
9.13.1 General p. 126
The following clauses specify procedures, information flows and APIs about SEALDD enabled adaptive data transmission.
9.13.2 SEALDD enabled adaptive data transmission p. 126
Figure 9.13.2-1 illustrate the procedure for supporting adaptive data transmission. The SEALDD facilitates to transmit data between the VAL client and VAL server adaptively by using application enablement layer capabilities of the AIML Enablement server defined in TS 23.482. This procedure can be used to support adaptive data transmission for XR services.
Pre-conditions:
- The AIMLE Server is known by the consumer and the SEALDD Server.
- The AI/ML services provided by the AIMLE Server is allowed for exposure to the consumer and the SEALDD Server.
- The consumer decides on the application which requires split image/video processing (distribute image/video processing tasks to multiple split endpoints for processing).
- Up to requirements of high layer application, SEALDD Server triggers interaction with AIMLE Server for assistance information.
Step 1.
The consumer (e.g. VAL server, VAL client via SEALDD client) sends adaptive data transmission request to the SEALDD server (e.g. for supporting XR service to deliver/distribute data to the split AI/ML endpoints (i.e. VAL client(s))). The request message contains message as defined in Table 9.13.3.1-1.
Step 2.
Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server responses to the VAL server. The SEALDD server derives information for the request, for example, based on the message in the request to decide whether assistance from 5GC and/or AIMLE server is needed or not, and determine downstream entities and services needed based on the information derived.
Then the SEALDD server sends request to the AIMLE server for split operation assistance information for the data transmission. For example, for split AI/ML image/video processing, the request contains the information of split AI/ML endpoints (from the request in step 1), data information (e.g. data type, data size, range of data size) to be delivered/distributed to the split AI/ML endpoints, may contain QoS requirements on the data transmission, e.g. desired data transmission time. The information flow for the request reuses the mechanisms specified in TS 23.482.
Step 3.
The SEALDD server may request and receive assistance from 5GC, as described in step 2, e.g. assistance information from NWDAF (or via NEF) about analytics on E2E data volume transfer time. In the request from SEALDD server to NWDAF for E2E data volume transfer time analytics, the split AI/ML endpoints information and a pre-configured data size (or data size range) may be used (the pre-configured data size may be the data size provided in step 1 or be decided by the SEALDD server according to the data size range in step 1 and based on its local policy. The data size range is provided in step 1.). The analytics subscription can be modified when the actual data size changed. The actual data size may be obtained via measurement described in Sdd_TransmissionQuality Management API.
Step 4.
The SEALDD server triggers to establish connection among the consumer, SEALDD server, SEALDD client(s), and with the split AI/ML endpoints (i.e. VAL client(s)) for the data transmission. The split operation assistance information received in steps 2 and 3 can be used by the SEALDD server separately or jointly based on need and local policy.
According to the assistance information, the SEALDD server may adjust the data volume to be transmission to each of the split AI/ML endpoints (if adaptive assign of date volume to the split AI/ML endpoints is allowed), or adjust the time point/time window for data transmission to the split endpoints.
Step 5.
Operations are performed at the consumer, SEALDD server, SEALDD client(s), and VAL client(s) for the data transmission, e.g. image/video/multi-modal data transmission from the consumer to the split AI/ML endpoints.
9.13.3 Information flows p. 128
9.13.3.1 SEALDD adaptive data transmission request p. 128
Table 9.13.3.1-1 describes the information flow from the consumer to the SEALDD server for requesting or updating request for an adaptive data transmission.
| Information element | Status | Description |
|---|---|---|
| Requestor ID | M
(NOTE) | The identifier of the consumer (e.g. VAL server ID, SEALDD client ID, VAL client ID). |
| VAL service ID | O | Identity of the VAL service. |
| VAL UE ID(s) | O | Identifier(s) of the endpoints (i.e. VAL UE(s)). |
| Adaptive data assign Indicator | O | Indicate that the data can be assigned to different endpoints adaptively. |
| Data information | M | The information of the data needs to be delivered or distributed. |
| >Data type | O | The type of data, could be e.g. image, video, multi-model data (e.g. audio, video, positioning, haptic data). |
| >Data size information | M | The maximum/minimum/average size of the data or a range of size for the data (a pair of minimum and maximum data volumes) to be delivered/distributed. |
| >Time duration | M | The time duration (start and end time) expected for sending the volume of data. |
| QoS requirement | O | The QoS requirement, e.g. latency for data transmission. |
| Assistance information | O | The assistance information for deliver/distribute the data, e.g. time point/time window for the data transmission to the split AI/ML endpoints. |
|
NOTE:
This information element shall not be updated.
|
||
9.13.3.2 SEALDD adaptive data transmission response p. 128
Table 9.13.3.2-1 describes the information from the SEALDD server to the consumer for responding to the adaptive data transmission request.
| Information element | Status | Description |
|---|---|---|
| Result | M | The result of the request (positive or negative acknowledgement). |
9.13.4 APIs p. 128
9.13.4.1 General p. 128
Table 9.13.4.1-1 illustrates the APIs exposed by SEALDD server for adaptive data transmission.
| API Name | API Operations | Operation Semantics | Consumer(s) |
|---|---|---|---|
| Sdd_ | Request | Request/Response | VAL server, SEALDD client |
9.13.4.2 Sdd_AdaptiveTransmission Request operation p. 129
API operation name:
Sdd_AdaptiveTransmission Request
Description:
The consumer requests for adaptive data transmission service.
Inputs:
See clause 9.13.3.1.
Outputs:
See clause 9.13.3.2.
See clause 9.13.2 for details of usage of this operation.
