Content for TS 23.482 Word version: 19.3.0
8.14 Support for Split AI/ML Operation
8.14.1 General
8.14.2 Procedure
8.14.2.1 General
8.14.2.2 Split operation pipeline discovery
8.14.2.3 Split operation pipeline creation
8.14.2.4 Split operation node registration
8.14.2.5 Split operation event subscription
8.14.2.6 Split operation pipeline update
8.14.2.7 Split operation pipeline delete
8.14.3 Information flows
...
...
8.14 Support for Split AI/ML Operation p. 74
8.14.1 General p. 74
Split AI/ML operation (e.g., split operation) procedures enable applications consuming services from the AI/ML application enablement layer to discover and create instance(s) of split operation pipeline and addresses aspects related to consumption of split operation results.
Split operation pipeline discovery enables an AIMLE client to obtain information about available instances of split operation pipeline or processing nodes of interest. The discovery of split operation or processing node instances is based on matching split operation discovery filters provided in the request.
Split operation pipeline creation enables an AIMLE client to create an instance of a split operation pipeline. The creation of an instance of a split operation pipeline is based on discovery of available ML models and processing nodes.
Split operation pipeline update and delete enable an AIMLE client to manage an instance of a split operation pipeline.
Split operation node registration enables a VAL server to register with the AIMLE server to indicate split operation capabilities. Registered VAL servers can be notified by the AIMLE server for participating in an instance of a split operation pipeline.
Split operation event subscription enables an AIMLE client or VAL server to receive notifications about split operation events. The subscription is based on matching split operation events filters provided in the request.
8.14.2 Procedure p. 75
8.14.2.1 General p. 75
Following procedures are supported for split AI/ML operation:
- Split operation pipeline discovery request-response procedure;
- Split operation pipeline creation, update and delete request-response procedures;
- Split operation node registration, registration update and de-registration request-response procedures;
-
Split operation event subscribe-notify procedures for information, comprising:
- Subscription procedure;
- Subscription update procedure; and
- Unsubscribe procedure;
8.14.2.2 Split operation pipeline discovery p. 75
Figure 8.14.2.2-1 illustrates the procedure for an AIMLE client to discover instance(s) of split AI/ML operation pipeline or processing nodes from the AIMLE server.
Pre-conditions:
- The AIMLE client has received information (e.g. URI, IP address) related to the AIMLE Server;
- The AIMLE client has received security credentials authorizing it to communicate with the AIMLE server;
Step 1.
Upon receiving a response including split operation profile(s), the AIMLE client stores the discovered split operation profile(s). The AIMLE client provides split operation profile information (e.g. endpoints, usage, etc.) to VAL client(s). The VAL client may use the provided information to access the split operation pipeline.
If the VAL client is a data provider, the VAL client may use the endpoint information to send data (e.g., intermediate inference data) towards the split operation pipeline instance's head endpoint.
If the VAL client is a data consumer, the VAL client may use the endpoint information to request results or subscribe to results from the split operation pipeline instance's tail endpoint.
The AIMLE client sends split operation pipeline discovery request to the AIMLE server; the request may be based on a VAL client requirement(s) and the split operation request includes information defined in Table 8.14.3.2-1.
Step 2.
Upon receiving the request from the AIMLE client, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server may determine if existing instance(s) of a split operation pipeline satisfy the request parameters. If the AIMLE server determines existing instance(s) of split operation pipeline, the AIMLE server may proceed to step 3.
If no instance of a split operation pipeline satisfies the request parameters, the AIMLE server determines if an instance of a split operation pipeline can be created. The determination for split operation pipeline creation is based on availability of ML models and determination of available processing nodes (e.g., VAL server(s), NWDAF(s), etc.) to execute operations for such ML models (e.g., inference). VAL server nodes register with the AIMLE server to indicate their availability and capabilities as described in clause 8.14.2.4. If the AIMLE server determines that an instance of a split operation pipeline can be created, the AIMLE server creates a split operation profile accordingly as defined in Table 8.14.3.3-2.
Step 3.
The AIMLE server sends a split operation pipeline discovery response to the requestor. If the AIMLE server has determined instance(s) of split operation pipeline (e.g., existing, or new), the response includes an indication of success and includes the corresponding split operation profile(s). Otherwise, the response includes an indication of failure and may include a reason for failure.
8.14.2.3 Split operation pipeline creation p. 76
Figure 8.14.2.3-1 illustrates the procedure for an AIMLE client to create an instance of a split operation pipeline at the AIMLE server. If the required number of nodes are not discovered in using the discovery procedure (i.e., the number of nodes in the discovery response message are less than the required minimum number of nodes), then the AIML enablement client can discover the remaining required processing nodes from other AIMLE server(s).
Pre-conditions:
- The AIMLE client has received information (e.g. URI, IP address) related to the AIMLE Server;
- The AIMLE client has received security credentials authorizing it to communicate with the AIMLE server;
- The AIMLE client has discovered information about processing nodes available with the AIMLE server;
- The VAL client (along with the AIMLE client) selects the nodes, which can take part in the split operation and decides the order in which nodes should perform the split operation inference.
Step 1.
Upon receiving a response including a split operation profile, the AIMLE client can store the split operation profile. The AIMLE client provides split operation profile information to VAL client(s). Split operation profile information can be used to access the split operation as described in clause 8.14.2.2.
The AIMLE client sends a split operation pipeline create request to the AIMLE server. The request includes information defined in Table 8.14.3.4-1.
Step 2.
Upon receiving the request from the AIMLE client, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server validates if the requested split operation pipeline can be created based on the information included in the request.
If the requestor is authorized and the AIMLE server has determined that an instance of a split operation pipeline can be created, the AIMLE server creates a split operation profile along with its identifier and notifies the appropriate processing nodes indicated in the request about their inclusion in the split operation pipeline as described in clause 8.14.2.5.
Step 3.
The AIMLE server sends a split operation pipeline create response message to the AIMLE client. If the AIMLE server has created an instance of a split operation pipeline, the response includes an indication of success, and the corresponding split operation profile. Otherwise, the response includes an indication of failure and may include a reason for failure.
8.14.2.4 Split operation node registration p. 77
8.14.2.4.1 General p. 77
Clause 8.14.2.4.2 illustrates the split operation node registration procedure.
Clause 8.14.2.4.3 illustrates the split operation node registration update procedure.
Clause 8.14.2.4.4 illustrates the split operation node de-registration procedure.
8.14.2.4.2 Split operation node registration p. 77
Figure 8.14.2.4.2-1 illustrates the procedure for VAL server to register with the AIMLE server to indicate split operation capabilities.
Pre-conditions:
- The VAL server has received information (e.g. URI, IP address) related to the AIMLE Server;
- The VAL server has received security credentials authorizing it to communicate with the AIMLE server;
Step 1.
The VAL server sends a split operation node register request to the AIMLE server to indicate the split operation capabilities of the VAL server. The request includes information defined in Table 8.14.3.6-1.
Step 2.
Upon receiving the request from the VAL server, the AIMLE server validates if the requestor is authorized for the request, the AIMLE server stores the registration information.
Step 3.
The AIMLE server sends a split operation node register response to the requestor. If the AIMLE server has registered the requestor, the response includes an indication of success and may include an updated expiration time. The requestor shall send a registration update request before the expiration time to maintain the registration; otherwise, the split operation node registration expires. If the requestor was not registered, the response includes an indication of failure and may include a reason for failure.
8.14.2.4.3 Split operation node registration update p. 78
Figure 8.14.2.4.3-1 illustrates the procedure for VAL server to update a split operation node registration with the AIMLE server.
Pre-conditions:
- The VAL server has registered with the AIMLE Server.
Step 1.
The VAL server sends a split operation node registration update request to the AIMLE server to update an existing split operation registration. The request includes information defined in Table 8.14.3.8-1.
Step 2.
Upon receiving the request from the VAL server, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server updates the registration information.
Step 3.
The AIMLE server sends a split operation node registration update response to the requestor. If the AIMLE server has successfully updated the registration, the response includes an indication of success and may include an updated expiration time. The requestor shall send a registration update request before the expiration time to maintain the registration; otherwise, the split operation registration expires. If the registration was not updated, the response includes an indication of failure and may include a reason for failure.
8.14.2.4.4 Split operation node de-registration p. 78
Figure 8.14.2.4.4-1 illustrates the procedure for VAL server to de-register for split operation with the AIMLE server.
Pre-conditions:
- The VAL server has registered with the AIMLE Server.
Step 1.
The VAL server sends a split operation node de-register request to the AIMLE server. The request includes information defined in Table 8.14.3.10-1.
Step 2.
Upon receiving the request from the VAL server, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server terminates the registration for split operation.
Step 3.
The AIMLE server sends a split operation node de-register response to the requestor. If the AIMLE server has successfully terminated the registration for split operation node, the response includes an indication of success. If the registration for split operation was not terminated, the response includes an indication of failure and may include a reason for failure.
8.14.2.5 Split operation event subscription p. 79
8.14.2.5.1 General p. 79
Clause 8.14.2.5.2 and clause 8.14.2.5.3 together illustrate the split operation subscribe/notify model.
Clause 8.14.2.5.4 illustrates the split operation subscription update procedure.
Clause 8.14.2.5.5 illustrates the split operation unsubscribe procedure.
8.14.2.5.2 Subscribe p. 79
Figure 8.14.2.5.2-1 illustrates the procedure for an AIMLE client or VAL server to subscribe with the AIMLE server to be notified of events related to split AI/ML operation.
Pre-conditions:
- The AIMLE client or VAL server has received information (e.g. URI, IP address) related to the AIMLE Server;
- The AIMLE client or VAL server has received security credentials authorizing it to communicate with the AIMLE server;
Step 1.
The requestor (e.g., AIMLE client or VAL server) sends a split operation subscribe request to the AIMLE server. The request includes information defined in Table 8.14.3.12-1.
Step 2.
- The requestor (e.g., AIMLE client or VAL server) may include the "split operation pipeline information" event to indicate the AIMLE server to notify the requestor when a split operation profile is created or an existing pipeline is updated (e.g., node is added or removed, stage order or ML models are modified, etc.) or deleted and satisfy the discovery filters of the subscription request.
- The requestor (e.g., AIMLE client or VAL server) may include the " split operation assistance information" event to indicate the AIMLE server to notify the requestor when the AIMLE server determines assistance information related to the split operation usage.
Upon receiving the request from the requestor, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server creates the subscription and stores the subscription information.
Step 3.
The AIMLE server sends a split operation subscribe response to the requestor. If the AIMLE server has created the subscription, the response includes an indication of success, the subscription identity and may include an expiration time; to maintain the subscription, the requestor shall send a subscription update request before the expiration time, otherwise the split operation subscription expires. If the AIMLE server has not created the subscription, the response includes an indication of failure and may include a reason for failure.
If the subscription is for "assistance information", the AIMLE Server considers the assistance information included in the subscription request and can perform the following:
The AIMLE Server aggregates the collected assistance information from NEF, NWDAF, and/or ADAES to generate assistance information, e.g. Time (time point(s) or time window(s)) to deliver the task or data for the split operation. Or the AIMLE server performs inference using ML model to generate assistance information, e.g. achievable QoS with current configuration for task or data delivery, or suggestion of QoS for task or data delivery.
- For assistance information from NEF, the AIMLE Server, acting as AF, sends a request to NEF for assistance information (e.g. PDTQ on recommended time windows for AI/ML operations with QoS, QoS monitoring) as described in clause 4.16.15 of TS 23.502. The request may include the information of the AI/ML task/ML model/data (e.g. size of the task or ML model, or data volume), information of the receiving nodes, requirement on the delivery/distribution (e.g. time budget, time critical or not, QoS), maximum time for complete the distribution/delivery.
- For assistance information from NWDAF, the AIMLE Server can send a request or subscription request to NWDAF for analytics (e.g. E2E data volume transfer time, DN performance, Network performance, UE mobility). The details parameters in the requests to NWDAF for analytics are given in TS 23.288.
- For assistance information from ADAES, the AIMLE Server can send a request or subscription request to ADAES for analytics (e.g. slice-specific application performance analytics, UE-to-UE application performance analytics). The details parameters in the requests to ADAES for analytics are given in TS 23.436.
8.14.2.5.3 Notify p. 80
Figure 8.14.2.5.3-1 illustrates the split operation notify operation between the AIMLE server and an AIMLE client or VAL server.
Pre-conditions:
- The AIMLE client or VAL server has subscribed for split operation with the AIMLE Server;
Step 1.
The AIMLE server detects event(s) that satisfies trigger conditions for notifying a subscriber (e.g., AIMLE client or VAL server) according to subscribed events.
Step 2.
- If the subscribed event is for "split operation pipeline information" and the AIMLE server detects that a new split operation profile is created or an existing pipeline is updated (e.g., node is added or removed, stage order or ML models are modified, etc.) or deleted and satisfy the discovery filters of the subscription, the AIMLE server notifies the subscriber (e.g., AIMLE client or VAL server) accordingly;
- If the subscribed event is for "split operation assistance information" and the AIMLE server has determined assistance information related to split operation usage, the AIMLE server notifies the subscribers (e.g., AIMLE client or VAL server) accordingly.
The AIMLE server sends a split operation notification to the requestor indicating the event. The notification includes a subscription identity and may include a split operation profile(s), split operation node information, or split operation assistance information dependent on the associated event.
8.14.2.5.4 Subscription update p. 81
Figure 8.14.2.5.4-1 illustrates the procedure for an AIMLE client or VAL server to update a subscription with the AIMLE server.
Pre-conditions:
- The AIMLE client or VAL server has subscribed for split operation with the AIMLE Server;
Step 1.
The requestor (e.g., AIMLE client or VAL server) sends a split operation subscription update request to the AIMLE server. The request includes information defined in Table 8.14.3.15-1.
Step 2.
Upon receiving the request from the requestor, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server updates the subscription information.
Step 3.
The AIMLE server sends a split operation subscription update response to the requestor. If the AIMLE server has updated the subscription, the response includes an indication of success and may include an expiration time. To maintain the subscription, the requestor shall send a subscription update request before the expiration time, otherwise the split operation subscription expires. If the AIMLE server has not updated the subscription, the response includes an indication of failure and may include a reason for failure.
8.14.2.5.5 Unsubscribe p. 81
Figure 8.14.2.5.5-1 illustrates the procedure for an AIMLE client or VAL server to unsubscribe with the AIMLE server.
Pre-conditions:
- The AIMLE client or VAL server has subscribed for split operation with the AIMLE Server;
Step 1.
The requestor (e.g., AIMLE client or VAL server) sends a split operation unsubscribe request to the AIMLE server. The request includes information defined in Table 8.14.3.17-1.
Step 2.
Upon receiving the request from the requestor, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server cancels the subscription associated with the subscription identifier.
Step 3.
The AIMLE server sends a split operation unsubscribe response to the requestor. If the AIMLE server has canceled the subscription, the response includes an indication of success. If the AIMLE server has not canceled the subscription, the response includes an indication of failure and may include a reason for failure.
8.14.2.6 Split operation pipeline update p. 82
Figure 8.14.2.6-1 illustrates the procedure for an AIMLE client to update an instance of a split operation pipeline at the AIMLE server. The AIMLE client or VAL client can determine that some of the nodes in the split operation pipeline may not be able to perform the required operation and decides to modify the pipeline either to add or remove the nodes.
Pre-conditions:
- The AIMLE client has received information related to split operation pipeline profile as specified in clause 8.14.2.3.
Step 1.
The AIMLE client sends a split operation pipeline update request to the AIMLE server. The request includes information defined in Table 8.14.3.19-1.
Step 2.
Upon receiving the request from the AIMLE client, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server validates if the requested split operation pipeline can be updated based on the split operation pipeline identifier included in the request.
If the requestor is authorized and a split operation pipeline profile is determined, the AIMLE server updates the split operation pipeline profile and notifies the appropriate processing nodes indicated in the request about their inclusion or exclusion in the split operation pipeline as described in clause 8.14.2.5. The AIMLE server also notifies the already existing nodes about modification of the existing pipeline as described in clause 8.14.2.5.
Step 3.
The AIMLE server sends a split operation pipeline update response message to the AIMLE client. If the AIMLE server has updated an instance of a split operation pipeline profile, the response includes an indication of success, and the corresponding split operation profile. Otherwise, the response includes an indication of failure and may include a reason for failure.
8.14.2.7 Split operation pipeline delete p. 82
Figure 8.14.2.7-1 illustrates the procedure for an AIMLE client to delete an instance of a split operation pipeline at the AIMLE server. The AIMLE client or VAL client can determine to delete a split operation pipeline when it is no longer needed.
Pre-conditions:
- The AIMLE client has received information related to split operation pipeline profile as specified in clause 8.14.2.3.
Step 1.
The AIMLE client sends a split operation pipeline delete request to the AIMLE server. The request includes information defined in Table 8.14.3.21-1.
Step 2.
Upon receiving the request from the AIMLE client, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server validates if the requested split operation pipeline can be deleted based on the split operation pipeline identifier included in the request.
If the requestor is authorized and a split operation pipeline is determined, the AIMLE server deletes the split operation pipeline profile and notifies the appropriate processing nodes about deletion of the split operation pipeline as described in clause 8.14.2.5.
Step 3.
The AIMLE server sends a split operation pipeline delete response message to the AIMLE client. If the AIMLE server has deleted a split operation profile, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
8.14.3 Information flows p. 83
8.14.3.1 General p. 83
The following information flows are specified for operation splitting.
8.14.3.2 Split operation pipeline discovery request p. 83
Table 8.14.3.2-1 shows the request sent by a AIMLE client to the AIMLE server for split operation pipeline discovery request.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identity of the requestor (e.g., VAL client ID, AIMLE client ID, UE identifier). |
| Security credentials | M | The security credentials of the requestor. |
| Split operation discovery filters | M | Split operation discovery filters. |
| > stage information | M | Information about the split operation stages (e.g., number, order, etc.). |
| > model information | M | Information about the ML models to be used in each stage (e.g., identifiers, versions, etc.). |
| > usage information | O | Information about the planned usage of the split operation (e.g., inputs frequency/size, output frequency/size, etc.). |
| > number of nodes | O | Minimum number of nodes required to support AIML operation splitting. |
8.14.3.3 Split operation pipeline discovery response p. 84
Table 8.14.3.3-1 shows the response sent by sent by the AIMLE server after processing of split operation pipeline discovery request.
| Information element | Status | Description |
|---|---|---|
| Successful response | O
(NOTE 2) | Indicates that the request was successful. |
| > List of nodes (NOTE 1) | O | The list of discovered nodes. |
| > List of split operation profiles (NOTE 1) | O | The list of split operation profiles as specified in Table 8.14.3.3-2. |
| Failure response | O
(NOTE 2) | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE 1:
Only one of the IE shall be present for successful response.
NOTE 2:
One of the IEs shall be present.
|
||
| Information element | Status | Description |
|---|---|---|
| Split operation pipeline identifier | M | The identifier of the split operation pipeline. |
| Head endpoint | M | The endpoint information of the head node for providing intermediate data. |
| Tail endpoint | M | The endpoint information of the tail node for obtaining results. |
| Usage information | O | The usage information of the AI/ML split operation (e.g., inputs frequency/size, output frequency/size, etc.). |
| Stage information | M | The list of stage(s) of the AI/ML split operation, the nested information is provided for each stage. |
| > Stage identifier | M | The identifier of the stage. |
| > number of nodes | O | Number of nodes included in the stage. |
| > head node | M | Endpoint of the head node - for providing initial the inference data. |
| > tail node | M | Endpoint of the head node - for obtaining inference results. |
| > order of the nodes | M | The order of the nodes in the AI/ML split operation (including head node, tail node). |
| >> list of nodes | M | List of all discovered node in the order in which they process the data. |
| >> notification target | O | Endpoint information where the inference result of the split operation is sent by the nodes. |
| > Model information | M | The ML model information used in the stage (e.g., identifiers, versions, etc.). |
8.14.3.4 Split operation pipeline create request p. 84
Table 8.14.3.4-1 shows the request sent by a AIMLE client to the AIMLE server for split operation pipeline create request.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identity of the requestor (e.g., VAL client ID, AIMLE client ID, UE identifier). |
| Security credentials | M | The security credentials of the requestor. |
| Split operation requirements | M | Split operation requirements. |
| > model information | M | Information about the ML models to be used in each stage (e.g., identifiers, versions, etc.). |
| > usage information | O | Information about the planned usage of the split operation (e.g., inputs frequency/size, output frequency/size, etc.). |
| > notification target | O | Endpoint information where the result of the split operation is sent by the tail node. |
| > stage information | M | Information about the split operation stages (e.g., number, order, etc.). |
| >> head node | M | Endpoint of the head node - for providing initial the inference data. |
| >> tail node | M | Endpoint of the head node - for obtaining inference results. |
| >> node information | M | List of Information about the nodes in order of the stage (e.g., identifier, endpoint, etc.). |
8.14.3.5 Split operation pipeline create response p. 85
Table 8.14.3.5-1 shows the response sent by a AIMLE server after processing of split operation pipeline create request.
| Information element | Status | Description |
|---|---|---|
| Successful response | O
(NOTE) | Indicates that the request was successful. |
| > Split operation profile | O | The split operation profile as specified in Table 8.14.3.3-2. |
| Failure response | O
(NOTE) | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of the IEs shall be present.
|
||
8.14.3.6 Split operation node register request p. 85
Table 8.14.3.6-1 shows the request sent by a VAL server to the AIMLE server for split operation node register request.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identity of the requestor (e.g., VAL server ID). |
| Security credentials | M | The security credentials of the requestor. |
| Node information | M | Information about the VAL server node (e.g., identifier, endpoints, etc.). |
| Split operation capabilities | M | Split operation capabilities of the VAL server. |
| > Model information | M | Information about ML model capabilities of the VAL server for split operation (e.g., identifiers, versions, etc.). |
| > Usage information | O | Information about usage capabilities of the VAL server for split operation (e.g., inputs frequency/size, output frequency/size, etc.). |
| Expiration time | O | The proposed expiration time of the registration. |
8.14.3.7 Split operation node register response p. 86
Table 8.14.3.7-1 shows the response sent by an AIMLE server after processing of split operation node register request.
| Information element | Status | Description |
|---|---|---|
| Successful response | O
(NOTE) | Indicates that the request was successful. |
| > Registration identifier | M | The identifier of the registration. |
| > Expiration time | O | The expiration time of the registration. To maintain an active registration, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the registration never expires. |
| Failure response | O
(NOTE) | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of the IEs shall be present.
|
||
8.14.3.8 Split operation node registration update request p. 86
Table 8.14.3.8-1 shows the request sent by a VAL server to the AIMLE server for split operation node registration update request.
| Information element | Status | Description |
|---|---|---|
| Registration identifier | M | The identifier of the registration. |
| Security credentials | M | The security credentials of the requestor. |
| Node information | O | Information about the VAL server node (e.g., identifier, endpoints, etc.). |
| Split operation capabilities | O | Split operation capabilities of the VAL server. |
| > Model information | O | Information about ML model capabilities of the VAL server for split operation (e.g., identifiers, versions, etc.). |
| > Usage information | O | Information about usage capabilities of the VAL server for split operation (e.g., inputs frequency/size, output frequency/size, etc.). |
| Expiration time | O | The proposed expiration time of the registration. |
8.14.3.9 Split operation node registration update response p. 86
Table 8.14.3.9-1 shows the response sent by an AIMLE server after processing of split operation node registration update request.
| Information element | Status | Description |
|---|---|---|
| Successful response | O
(NOTE) | Indicates that the request was successful. |
| > Expiration time | O | The expiration time of the registration. To maintain an active registration, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the registration never expires. |
| Failure response | O
(NOTE) | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of the IEs shall be present.
|
||
8.14.3.10 Split operation node de-register request p. 87
Table 8.14.3.10-1 shows the request sent by a VAL server to the AIMLE server for split operation de-register request.
| Information element | Status | Description |
|---|---|---|
| Registration identifier | M | The identifier of the registration. |
| Security credentials | M | The security credentials of the requestor. |
8.14.3.11 Split operation node de-register response p. 87
Table 8.14.3.11-1 shows the response sent by an AIMLE server after processing of split operation de-register request.
| Information element | Status | Description |
|---|---|---|
| Successful response | O
(NOTE) | Indicates that the request was successful. |
| Failure response | O
(NOTE) | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of the IEs shall be present.
|
||
8.14.3.12 Split operation subscribe request p. 87
Table 8.14.3.12-1 shows the request sent by an AIMLE client or a VAL server to the AIMLE server for split operation subscribe request.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identity of the requestor (e.g., VAL server ID). |
| Security credentials | M | The security credentials of the requestor. |
| Split operation pipeline identifier | M | Identifier of the split operation pipeline for which the requestor is subscribing. |
| Notification endpoint | M | The notification endpoint (e.g. URL/URI/IP address) where the notifications should be sent to. |
| Event identifier | M |
The event identifier for the subscription:
|
| Discovery filters | O | The set of characteristics to determine matching split operation profiles or nodes (as detailed in Table 8.14.3.2-1). Applicable for "Split operation pipeline information". |
| Assistance information | O |
The assistance information for the subscription:
|
| Expiration time | O | The proposed expiration time of the subscription. |
8.14.3.13 Split operation subscription response p. 87
Table 8.14.3.13-1 shows the response sent by an AIMLE server after processing of split operation subscription request.
| Information element | Status | Description |
|---|---|---|
| Successful response | O
(NOTE) | Indicates that the request was successful. |
| > Subscription identifier | M | The identifier of the subscription. |
| > Expiration time | O | The expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time. If the Expiration time IE is not included, it indicates that the subscription never expires. |
| Failure response | O
(NOTE) | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of the IEs shall be present.
|
||
8.14.3.14 Split operation notification p. 88
Table 8.14.3.14-1 shows the request sent by an AIMLE server to notify a subscriber of detected split operation events.
| Information element | Status | Description |
|---|---|---|
| Subscription identifier | M | The identifier of the subscription. |
| Event identifier | M |
The identifier for the detected event, either:
|
| Availability information | O | The split operation availability information. Applicable for "Split operation availability" event. |
| > List of split operation profiles | O | The list of newly available split operation profiles as specified in Table 8.14.3.3-2. |
| > List of nodes | O | The list of newly available nodes. |
| Split operation pipeline information | O | The split operation pipeline information. Applicable for "Split operation pipeline information" event. |
| > Sub-event | O |
Indicates the possible sub-event.
|
| > Split operation profile | O | The split operation profile that the VAL server participates to as specified in Table 8.14.3.3-2. |
| Assistance information | O | The split operation assistance information. Applicable for "Split operation assistance information" event. |
| > Delivery time | O | Time (time point(s) or time window(s)) to deliver the task or data for the split operation. |
| > Achievable QoS | O | The achievable QoS with current configuration for task or data delivery. |
| > Suggestion of QoS | O | The suggestion of QoS for task or data delivery. |
8.14.3.15 Split operation subscribe update request p. 88
Table 8.14.3.15-1 shows the request sent by an AIMLE client or a VAL server to the AIMLE server for split operation subscription update request.
| Information element | Status | Description |
|---|---|---|
| Subscription identifier | M | The identifier of the subscription. |
| Security credentials | M | The security credentials of the requestor. |
| Notification endpoint | O | The notification endpoint (e.g. URL/URI/IP address) where the notifications should be sent to. |
| Event identifier | O |
The event identifier for the subscription:
|
| Split operation discovery filters | O | |
| O | The set of characteristics to determine matching split operation profiles or nodes (as detailed in Table 8.14.3.2-1). Applicable for "Split operation availability" event. | |
| Expiration time | O | The proposed expiration time of the subscription. |
8.14.3.16 Split operation subscribe update response p. 89
Table 8.14.3.16-1 shows the request sent by an AIMLE server after processing of split operation subscription update request.
| Information element | Status | Description |
|---|---|---|
| Successful response | O
(NOTE) | Indicates that the request was successful. |
| > Expiration time | O | The expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time. If the Expiration time IE is not included, it indicates that the subscription never expires. |
| Failure response | O
(NOTE) | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of the IEs shall be present.
|
||
8.14.3.17 Split operation unsubscribe request p. 89
Table 8.14.3.17-1 shows the request sent by an AIMLE client or a VAL server to the AIMLE server for split operation unsubscribe request.
| Information element | Status | Description |
|---|---|---|
| Subscription identifier | M | The identifier of the subscription. |
| Security credentials | M | The security credentials of the requestor. |
8.14.3.18 Split operation unsubscribe response p. 89
Table 8.14.3.18-1 shows the response sent by an AIMLE server after processing of split operation unsubscribe request.
| Information element | Status | Description |
|---|---|---|
| Successful response | O
(NOTE) | Indicates that the request was successful. |
| Failure response | O
(NOTE) | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of the IEs shall be present.
|
||
8.14.3.19 Split operation pipeline update request p. 90
Table 8.14.3.19-1 shows the request sent by an AIMLE client to the AIMLE server for split operation pipeline update request.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identity of the requestor (e.g., VAL client ID, AIMLE client ID, UE identifier). |
| Security credentials | M | The security credentials of the requestor. |
| Split operation pipeline identifier | M | The identifier of the AI/ML split operation pipeline. |
| Split operation pipeline information | M | Split operation pipeline information to be updated; this may include information elements defined in the split operation profile in Table 8.14.3.3-2. |
8.14.3.20 Split operation pipeline update response p. 90
Table 8.14.3.20-1 shows the response sent by an AIMLE server after processing of split operation pipeline update request.
| Information element | Status | Description |
|---|---|---|
| Successful response (NOTE) | O | Indicates that the request was successful. |
| > Split operation profile | O | The split operation profile as specified in Table 8.14.3.3-2. |
| Failure response (NOTE) | O | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of these IE is included.
|
||
8.14.3.21 Split operation pipeline delete request p. 90
Table 8.14.3.21-1 shows the request sent by an AIMLE client to the AIMLE server for split operation pipeline delete request.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identity of the requestor (e.g., VAL client ID, AIMLE client ID, UE identifier). |
| Security credentials | M | The security credentials of the requestor. |
| Split operation pipeline identifier | M | The identifier of the AI/ML split operation pipeline. |
8.14.3.22 Split operation pipeline delete response p. 90
Table 8.14.3.22-1 shows the response sent by an AIMLE server after processing of split operation pipeline delete request.
| Information element | Status | Description |
|---|---|---|
| Successful response (NOTE) | O | Indicates that the request was successful. |
| Failure response (NOTE) | O | Indicates that the request failed. |
| > Failure cause | O | Indicates the failure cause. |
|
NOTE:
One of these IE is included.
|
||
