hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.1 General
| The following clauses specify procedures to support AI/ML task transfer.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.2 Procedures for AI/ML task transfer
| Due to various reasons (e.g., changes of available resource, changes of available time), an AI/ML member (e.g., AIMLE Client, VAL Client) finds itself cannot finish the assigned AI/ML task during the performing process. Here AI/ML member means the participant of an AI/ML task. To save resource and time, the AI/ML member (source AI/ML member) decides to transfer the intermediate AI/ML information (e.g., the intermediate AI/ML operation status and results) to another AI/ML member (target AI/ML member) for further operations to complete the AI/ML task.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.2.1 Request AIMLE Server to assist AI/ML task transfer
| Pre-conditions:
1. The information of target AI/ML member (e.g., another AIMLE Client or VAL Client different from the source AI/ML member) is unknown at the source AI/ML member. The source AI/ML member decides that assistance from the AIMLE Server is needed.
2. The source determines which AI/ML tasks to transfer. For example, if the AI/ML task is model training, AI/ML model are obtained by source AI/ML member performing AI/ML model training. Then the source AI/ML member determines the remaining AI/ML model training requirement based on the intermediate AI/ML operation status and results and AI/ML model training requirement.
Figure 8.6.2.1-1: Procedure for requesting AIMLE Server assist AI/ML task transfer
Figure 8.6.2.1-1 illustrates the procedure for requesting AIMLE Server to assist the AI/ML task transfer. The detailed corresponding procedure is detailed as follows:
1. The source AI/ML member (e.g., an AIMLE Client) sends an AI/ML task transfer assist request to AIMLE Server for assisting the AI/ML task transfer. The request message contains the information as specified in Table 8.6.3.2-1.
2. The AIMLE Server discovers other AI/ML members (e.g., other AIMLE Clients) directly or via ML repository, and selects one or more target AI/ML member(s) based on the request from the source AI/ML member. The AIMLE Server sends request to the selected target AI/ML member(s) for the AI/ML task transfer, as defined in clause 8.6.2.2. Then, the AIMLE Server determines the transfer mode, i.e., transfer with server-controlled or transfer directly from the source AI/ML member to the target AI/ML member. For example, if the task is model training, the AI/MLE server determines the target AI/ML member(s) based on AI/ML member(s)’s capability in the AIMLE client profile and task's AI/ML model training requirement. The task’s AI/ML model training requirement indicates the AI/ML Information.
If target AI/ML member(s) is discovered, the AIMLE Server generates assistance information for the AI/ML task transfer from the source AI/ML member to the target AI/ML member(s) (e.g., time window for the transfer).
3. The AIMLE Server sends an AI/ML task transfer assist response to the source AI/ML member with the information of the target AI/ML member(s), and assistance information generated in step 2. The response message contains the information as specified in Table 8.6.3.3-1.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.2.2 Request target AI/ML member for AI/ML task transfer
|
Figure 8.6.2.2-1: Procedure for requesting target AI/ML member for AI/ML task transfer
Figure 8.6.2.2-1 illustrates the procedure for requesting target AI/ML member for AI/ML task transfer. The corresponding procedure in detail is as follows:
1. The AIMLE Server sends an AI/ML task transfer request to the selected target AI/ML member(s) for AI/ML task transfer. The request message contains the information as specified in Table 8.6.3.4-1.
2. The target AI/ML member(s) authenticates and authorizes the request from the AIMLE Server. If the request is authorized, the target AI/ML member(s) performs step 3.
3. The target AI/ML member(s) sends an AI/ML task transfer response to the AIMLE Server with information as specified in Table 8.6.3.5-1.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.2.3 Direct AI/ML task transfer
| Pre-conditions:
1. The information of target AI/ML member (e.g., another AIMLE Client or VAL Client different from the source AI/ML member) is assumed to be known at the source AI/ML member, or the source AI/ML member may get the target AI/ML member information via ML repository. The source AI/ML member decides to transfer the AI/ML task to the target AI/ML member.
Figure 8.6.2.3-1: Procedure for direct AI/ML task transfer
Figure 8.6.2.3-1 illustrates the procedure for direct AI/ML task transfer. The corresponding procedure in detail is as follows:
1. The source AI/ML member (e.g. an AIMLE Client) sends a direct AI/ML task transfer request to the target AI/ML member for direct AI/ML task transfer. The request message contains the information as specified in Table 8.6.3.6-1.
2. The target AI/ML member authenticates and authorizes the request from the source AI/ML member. If the request is authorized, the target AI/ML member checks its availability for continue the AI/ML operations (e.g., available resource and time).
3. The target AI/ML member sends a direct AI/ML task transfer response to the source AI/ML member with information as specified in Table 8.6.3.7-1.
4. The source AI/ML member interacts with the target AI/ML member to perform AI/ML task transfer to the target AI/ML member.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.2.4 AIMLE server-controlled AI/ML task transfer
| Pre-conditions:
1. The information of target AI/ML member (e.g. another AIMLE Client or VAL Client different from the source AI/ML member) is unknown at the source AI/ML member. The source AI/ML member decides that AIMLE server-controlled AI/ML task transfer is needed.
Figure 8.6.2.4-1: Procedure for AIMLE server-controlled AI/ML task transfer
Figure 8.6.2.4-1 illustrates the procedure for AIMLE server-controlled AI/ML task transfer. The corresponding procedure in detail is as follows:
1. The source AI/ML member (e.g., an AIMLE Client) may send an AIMLE server-controlled AI/ML task transfer request to AIMLE Server. The request message contains the information as specified in Table 8.6.3.8-1. Or, AIMLE server-controlled AI/ML task transfer may be decided by the AIMLE server as described in step 2 of clause 8.6.2.1.
2. If received the request for AIMLE server-controlled AI/ML task transfer from the source AI/ML member, the AIMLE sever authenticates and authorizes the request from the source AI/ML member. If the request is authorized, the AIMLE server checks the availability of the target AI/ML member(s) for AI/ML task transfer as defined in clause 8.6.2.2. The AIMLE server generates assistance information for the transfer of AI/ML task the source AI/ML member to the target AI/ML member(s) via AIMLE server (e.g. time window for the transfer).
3. The AIMLE server sends response to the source AI/ML member.
4. The source AI/ML member performs AI/ML task transfer to the target AI/ML member(s) via the AIMLE server based on the information received from the AIMLE server in step 3 if AIMLE server-controlled AI/ML task transfer is requested by the source AI/ML member, or based on the assistance information generated in step 2 of clause 8.6.2.1 if AIMLE server-controlled AI/ML task transfer is decided by the AIMLE server.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.1 General
| The following information flows are specified for supporting AI/ML task transfer. In the following clauses 8.6.3.2 to 8.6.3.9, the source AI/ML member and the target AI/ML member could be e.g., VAL UE, AIMLE Client.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.2 AI/ML task transfer assist request
| Table 8.6.3.2-1 describes information elements for the AI/ML task transfer assist request from the source AI/ML member to the AIMLE Server.
Table 8.6.3.2-1: AI/ML task transfer assist request
Information element
Status
Description
Requestor identity
M
The identifier of the source AI/ML member (e.g. identifier of the source AIMLE client or the VAL UE).
VAL service ID
O
The identifier of the VAL service for which the assistance information is requested.
AI/ML Task Type
M
The type of the AI/ML operation (e.g. ML model training).
AI/ML Information Type
M
The type of the AI/ML information in the AI/ML task need be transferred (e.g. intermediate AI/ML operation status, intermediate AI/ML operation results).
> AI/ML model remaining training requirement (NOTE)
O
Indicate the requirement for AI/ML model training including, required remaining training resource, required remaining training number of iterations,
> AI/ML intermediate information (NOTE)
O
Indicate the AI/ML intermediate information for intermediate AI/ML operation and result (e.g. ML model training), including AI/ML intermediate model, AI/ML intermediate model used training time, used training resource, used training number of iterations.
Time validity
O
The time validity of the request.
NOTE: The IE only present when AI/ML Task Type is ML model training.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.3 AI/ML task transfer assist response
| Table 8.6.3.3-1 describes information elements for the AI/ML task transfer assist response from the AIMLE Server to the source AI/ML member.
Table 8.6.3.3-1: AI/ML task transfer assist response
Information element
Status
Description
Transfer Mode
O
Indication the transfer mode (e.g. direct transfer).
Target AI/ML member(s)
M
The identifier of the target AI/ML member (e.g. identifier of the target AIMLE client or the VAL UE).
Assistance Information
M
Assistance information for the AI/ML task transfer (e.g. time window for the transfer).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.4 AI/ML task transfer request
| Table 8.6.3.4-1 describes information elements for the AI/ML task transfer request from the AIMLE Server to the target AI/ML member.
Table 8.6.3.4-1: AI/ML task transfer request
Information element
Status
Description
Requestor identity
M
The identifier of the AIMLE server.
Source AI/ML member
M
The identifier of the source AI/ML member (e.g. identifier of the source AIMLE client or the VAL UE).
AI/ML Task Type
M
The type of the AI/ML operation (e.g. ML model training).
AI/ML Information Type
M
The type of the AI/ML information in the AI/ML task need be transferred (e.g. intermediate AI/ML operation status, intermediate AI/ML operation results).
AI/ML Task Transfer Time
O
Information on time or time window for the AI/ML task transfer.
Time validity
O
The time validity of the request.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.5 AI/ML task transfer response
| Table 8.6.3.5-1 describes information elements for the AI/ML task transfer response from the target AI/ML member to the AIMLE Server.
Table 8.6.3.5-1: AI/ML task transfer response
Information element
Status
Description
Status
M
The status for the request: success or fail.
AI/ML Task Transfer Time
O
Information on time or time window for the AI/ML task transfer.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.6 Direct AI/ML task transfer request
| Table 8.6.3.6-1 describes information elements for the direct AI/ML task transfer request from the source AI/ML member to the target AI/ML member.
Table 8.6.3.6-1: Direct AI/ML task transfer request
Information element
Status
Description
Requestor identity
M
The identifier of the source AI/ML member (e.g. identifier of the source AIMLE client or the VAL UE).
AI/ML Task Type
M
The type of the AI/ML operation (e.g. ML model training).
AI/ML Information Type
M
The type of the AI/ML information in the AI/ML task need be transferred (e.g. intermediate AI/ML operation status, intermediate AI/ML operation results).
AI/ML Task Transfer Time
O
Information on time or time window for the AI/ML task transfer.
Time validity
O
The time validity of the request.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.7 Direct AI/ML task transfer Response
| Table 8.6.3.7-1 describes information elements for the direct AI/ML task transfer response from the target AI/ML member to the source AI/ML member.
Table 8.6.3.7-1: Direct AI/ML task transfer response
Information element
Status
Description
Status
M
The status for the request: success or fail.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.8 AIMLE server-controlled AI/ML task transfer request
| Table 8.6.3.8-1 describes information elements for the AIMLE server-controlled AI/ML task transfer request from the source AI/ML member to the AIMLE server.
Table 8.6.3.8-1: AIMLE server-controlled AI/ML task transfer request
Information element
Status
Description
Requestor identity
M
The identifier of the source AI/ML member (e.g. identifier of the source AIMLE client or the VAL UE).
AI/ML Task Type
M
The type of the AI/ML operation (e.g. ML model training).
AI/ML Information Type
M
The type of the AI/ML information in the AI/ML task need be transferred (e.g. intermediate AI/ML operation status, intermediate AI/ML operation results).
AI/ML Task Transfer Time
O
Information on time or time window for the AI/ML task transfer.
Time validity
O
The time validity of the request.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6.3.9 AIMLE server-controlled AI/ML task transfer Response
| Table 8.6.3.9-1 describes information elements for the AIMLE server-controlled AI/ML task transfer response from the AIMLE server to the source AI/ML member.
Table 8.6.3.9-1: AIMLE server-controlled AI/ML task transfer response
Information element
Status
Description
Status
M
The status for the request: success or fail.
Assistance Information
M
Assistance information for the AI/ML task transfer (e.g. time window for the transfer).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7 AIMLE client registration
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.1 General
| Prior to participation in AI/ML operations, AI/ML capable UEs register to an AIMLE server and provide an AIMLE client profile and optionally a list of supported services. The AIMLE server uses information provided by the AIMLE client to discover and select suitable AIMLE clients for requested AI/ML operations.
The following clauses specify procedures, information flows, and APIs for AIMLE client registration.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.2 Procedures
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.2.1 General
| The following are supported for AIMLE client registration:
- AIMLE client registration procedure;
- AIMLE client registration update procedure; and
- AIMLE client de-registration procedure
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.2.2 AIMLE client registration
| Pre-conditions:
1. The AIMLE client has been pre-configured or has discovered the address (e.g., URI) of the AIMLE server.
2. The AIMLE client has been pre-configured with an AIMLE client profile.
Figure 8.7.2.2-1: AIMLE client registration
1. The AIMLE client sends an AIMLE client registration request to the AIMLE server, the registration request includes information as described in Table 8.7.3.2-1. The AIMLE client indicates in the registration request its AI/ML capabilities such as supported ML model types and supported AI/ML operations, supported AIMLE client task capabilities with compute and task performance capabilities to assist with performing AIMLE client discovery and AIMLE client selection.
2. The AIMLE server validates the registration request and performs an authentication and authorization check to determine if the AIMLE client is permitted to register to the AIMLE server and participate in AI/ML operations. Upon successful authorization, the AIMLE server saves the context of the AIMLE client registration in the ML repository as defined in clause 8.4.2.
3. The AIMLE server returns an AIMLE client registration response to the AIMLE client with the status of the request.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.2.3 AIMLE client registration update
| Pre-conditions:
1. The AIMLE client has already registered with the AIMLE Server.
Figure 8.7.2.3-1: AIMLE client registration update
1. The AIMLE client sends an AIMLE client registration update request to the AIMLE server, the registration update shall include registration identifier, updated list of supported services and updated AIMLE client profile as described in Table 8.7.3.4-1. The AIML client removes services from the list of services identified by Service ID(s) when it ceases to provide a service and adds to the service when it starts to provide a service.
2. The AIMLE server validates the registration update and performs an authentication and authorization check. Upon successful authorization, the AIMLE server updates the context of the AIMLE client registration in the ML repository as defined in clause 8.4.3.
3. The AIMLE server returns an AIMLE client registration update response to the AIMLE client with the status of the update.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.2.4 AIMLE client de-registration
| Pre-conditions:
1. The AIMLE client has already registered with the AIMLE Server.
Figure 8.7.2.4-1: AIMLE client de-registration
1. The AIMLE client sends an AIMLE client de-registration request to the AIMLE server. The request shall include registration identifier as described in Table 8.7.3.6-1.
2. The AIMLE server validates the deregistration request and performs an authentication and authorization check to determine whether the AIMLE client can deregister from AI/ML operations. Upon successful authorization, the AIMLE server removes the context of the AIMLE client registration from the ML repository as defined in clause 8.4.2.
3. The AIMLE server returns an AIMLE client de-registration response to the AIMLE client with the status of the request.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.3.1 General
| The following information flows are specified for AIMLE client registration:
- AIMLE client registration request and response;
- AIMLE client registration update request and response; and
- AIMLE client de-registration request and response
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.3.2 AIMLE client registration request
| Table 8.7.3.2-1 shows the request sent by an AIMLE client to an AIMLE server for the AIMLE client registration request.
Table 8.7.3.2-1: AIMLE client registration request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
List of supported profiles
M
Supported AIML client profile(s). For each client profile provided in the list, the supported service information is provided.
> AIMLE client profile
M
Information about the capability of the AIMLE client to support AI/ML operations for the VAL service ID as detailed in Table 8.7.3.2-2.
> List of supported services
M
List of VAL service IDs with corresponding permissions.
> VAL service ID
M
The identifier of the VAL service.
> Service permission level
O
Service permission level (e.g., premium resource usage, standard resource usage, limited resource usage).
Table 8.7.3.2-2: AIMLE client profile
Information element
Status
Description
Supported AI/ML model types
O
AI/ML model types supported by the AIMLE client (e.g., decision trees, linear regression, neural networks).
Supported AI/ML operations
M
AI/ML operations supported by the AIMLE client such as ML model training, model transfer, model inference, model offload, model split, continue perform intermediate AI/ML operation/task).
AIMLE client time schedule configurations
O
Indicates the availability schedule of the AIMLE client for the AIML service, e.g., the AIMLE client is (not) available to participate in the AIML operations (e.g., ML model training) in the given time slot(s) and/or day(s) of the week.
AIMLE client location configurations
O
Indicates the location-based configurations of the AIMLE client for the AIML service, e.g., the AI/ML member is (not) available to participate in the AI/ML operations in the given locations represented by coordinates, civic addresses, network areas, or VAL service area ID.
AIMLE client capabilities
M
AIMLE client capability information (e.g., ML application type, allowed resource usage level).
Dataset availability
O
Dataset availability such as dataset size, age, list of dataset features, and dataset identifiers.
Data capabilities
O
A list of data capabilities such as the type of data that can be collected (e.g., raw data), supported data processing capabilities (e.g., processed data), and supported exploratory data analysis functions.
AIMLE client task capability
O
See NOTE
Indicates the AIML task performing capabilities. It includes compute capabilities (e.g., high, low), task performance preference capabilities (e.g., green task, energy-efficient, low costs)
NOTE: The Green and Energy-efficient task performance may not be applicable to a UE.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.3.3 AIMLE client registration response
| Table 8.7.3.3-1 shows the AIMLE client registration response sent by the AIMLE server to the AIMLE client.
Table 8.7.3.3-1: AIMLE client registration response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the registration was successful.
> Registration ID
M
The identifier of the registration.
> Expiration time
O
Indicates the expiration time of the updated registration. To maintain an active registration status, a registration update is required before the expiration time.
If the Expiration time IE is not included, it indicates that the updated registration never expires.
Failure response
O
(NOTE)
Indicates that the registration request failed.
> Cause
O
Indicates the cause of registration request failure
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.3.4 AIMLE client registration update request
| Table 8.7.3.4-1 shows the request sent by an AIMLE client to an AIMLE server for the AIMLE client registration update request.
Table 8.7.3.4-1: AIMLE client registration update request
Information element
Status
Description
Registration identifier
M
Identifier of the existing registration for which the update request applies.
AIMLE client profile
O
Update information about the capability of the AIMLE client to support AI/ML operations as detailed in Table 8.7.3.2-2.
List of supported services
O
Update to supported service information. Services identified by their VAL Service ID are either removed from the list when the AIMLE client ceases to provide a service and added when the AIMLE client starts to provide a service.
> VAL service ID
M
The identifier of the VAL service.
> Service permission level
O
Service permission level (e.g., premium resource usage, standard resource usage, limited resource usage).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.3.5 AIMLE client registration update response
| Table 8.7.3.5-1 shows the AIMLE client de-registration update response sent by the AIMLE server to the AIMLE client.
Table 8.7.3.5-1: AIMLE client registration update response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the registration update request was successful.
> Expiration time
O
Indicates the expiration time of the updated registration. To maintain an active registration status, a registration update is required before the expiration time.
If the Expiration time IE is not included, it indicates that the updated registration never expires.
Failure response
O
(NOTE)
Indicates that the registration update request failed.
> Cause
O
Indicates the cause of registration update request failure
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.3.6 AIMLE client de-registration request
| Table 8.7.3.6-1 shows the request sent by an AIMLE client to an AIMLE server for the AIMLE client de-registration request.
Table 8.7.3.6-1: AIMLE client de-registration request
Information element
Status
Description
Registration ID
M
Identifier of the existing registration for which the update request applies.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.7.3.7 AIMLE client de-registration response
| Table 8.7.3.7-1 shows the AIMLE client de-registration response sent by the AIMLE server to the AIMLE client.
Table 8.7.3.7-1: AIMLE client de-registration response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the de-registration request was successful.
Failure response
O
(NOTE)
Indicates that the de-registration request failed.
> Cause
O
Indicates the cause of de-registration request failure
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.8 AIMLE client discovery
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.8.1 General
| Discovery of AIMLE clients is an important step in the AI/ML process for distributed, federated, split AI/ML, and transfer learning. Due to the nature of such learning, VAL servers need to discover suitable AIMLE clients to fulfil the requirements for the AI/ML application. The VAL server can then use the discovered AIMLE clients to select a set of AIMLE clients to perform AI/ML operations.
The following clauses specify procedures, information flows, and APIs for AIMLE client discovery.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.8.2 Procedure
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.8.2.1 AIMLE client discovery
| Pre-conditions:
1. AIMLE clients that support AI/ML operations have registered with the AIMLE server and included their AIMLE client profiles and optionally a list of supported services.
2. The AIMLE server can access a ML repository to obtain AIMLE client profiles and supported services associated with AIMLE clients.
Figure 8.8.2.1-1: AIMLE client discovery
1. A VAL server sends an AIMLE client discovery request to an AIMLE server to discover a list of AIMLE clients that are available to participate in AI/ML operations (e.g., is available and have required data to train an ML model). The request may also include AIML client task capability requirements to discover clients who can perform the AIML tasks like AIML model training/offload/split with compute requirements and task performance preference like green task performance. The AIMLE client discovery request includes information as described in Table 8.8.3.1-1.
2. The AIMLE server performs authentication and authorization checks to determine if the requestor is able to discover AIMLE clients. If the requestor is authorized, the AIMLE server performs the following to discover AIMLE clients fulfilling the provided AIMLE client discovery criteria.
The AIMLE server also obtains candidate UEs from the ML repository.
From the list of candidate UEs, the AIMLE server discovers a list of UEs (i.e., AIMLE clients) that fulfils the discovery criteria based on supported services and AIMLE client profiles.
The AIMLE server determines whether the discovered UEs fulfil the location information in the discovery criteria by using their identifiers to determine their location and includes in the discovery response only those UEs that meet the requirements. The AIMLE server may use SEAL-LMS (as in 3GPP TS 23.434 [5] clause 9.3.9, or 3GPP TS 23.434 [5] clause 9.3.10) or 3GPP 5G Core Network Services (such as GMLC as in 3GPP TS 23.273 [13] and NEF as in 3GPP TS 23.273 [13] or 3GPP TS 23.502 [9]) to determine the UEs which fulfil the location requirement.
If the available AIMLE clients (as determined by the AIMLE server) that fulfil discovery criteria are less than the required minimum number of AIMLE clients for AI/ML operation (e.g., split AI/ML), then the AIMLE server may discover the remaining required AIMLE clients from other AIMLE servers over AIML-E reference point and include them in the response message.
3. The AIMLE server sends an AIMLE client discovery response that includes information in Table 8.8.3.2-1.
If the required number of AIMLE clients are not included in the response message from the AIMLE server (i.e., the AIMLE clients in the response message are less than the required minimum number of AIMLE clients), then the AIML service consumer may discover the remaining required AIMLE clients from other AIML enablement server indicating the required number of AIMLE clients. The response may also include information related to supported tasks with guaranteed task KPIs, available AIML tasks service duration, AIML task expected KPI like latency.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.8.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.8.3.1 AIMLE client discovery request
| Table 8.8.3.1-1 shows the request sent by a VAL server to an AIMLE server for the AIMLE client discovery procedure.
Table 8.8.3.1-1: AIMLE client discovery request
Information element
Status
Description
Requestor identity
M
The identifier of the requestor (e.g., VAL server).
AIMLE client discovery criteria
M
Discovery criteria for finding suitable AIMLE clients for AI/ML operations as detailed in Table 8.8.3.1-2.
Number of required AIMLE clients
O
Indicates the requested number of AIMLE clients to be discovered based on the discovery criteria.
Table 8.8.3.1-2: AIMLE client discovery criteria
Information element
Status
Description
Service requirement
M
Information about the required service
> VAL Service ID
M
VAL Service ID that the client is required to support. This identifies the service associated with the requester.
> Service permission level
O
Required corresponding service permission level (e.g., premium resource usage standard resource usage, limited resource usage).
Requested ML model types
O
Requested ML model types (decision trees, linear regression, neural networks).
Requested AIML operations
M
Requested role for AI/ML operations such as model training, model transfer, model inference, model offload, model split.
Application layer AIMLE client capabilities
M
Application layer AIMLE client capability information (e.g., ML application type like FL/TL/SL, client availability to support AIML operations at the UE, AIMLE drop off rate).
Dataset requirements
O
Information about dataset.
> Dataset availability
O
Dataset availability, including dataset identifiers, dataset size, age, list of dataset features.
> Data capabilities
O
A list of data capabilities such as the type of data that can be collected (e.g., raw data), supported data processing capabilities (e.g., processed data) and supported exploratory data analysis functions.
AIML client task capability requirements
O
Indicates the AIML task requirements to discover the AIML clients for performing AIML tasks.
It includes compute capabilities (e.g., high, low), task performance preference capabilities (e.g. Green task, Energy-efficient, low costs)
AIMLE client velocity
O
Indicates the AIMLE client velocity. It includes mobile (e.g., high, low), static.
Location information
O
Indicates the location information (e.g., Cell Identity, Tracking Area Identity, GPS Coordinates or civic addresses, VAL service area ID) to discover the AIMLE clients.
AIMLE client QoS requirements
O
Indicates the AIMLE client QoS information (like PLR, bandwidth, latency jitter) with the corresponding threshold(s) and threshold matching direction(s) (e.g., above or below) to discover the AIMLE clients.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.8.3.2 AIMLE client discovery response
| Table 8.8.3.2-1 shows the response sent by the AIMLE server to the VAL server for the AIMLE client discovery procedure.
Table 8.8.3.2-1: AIMLE client discovery response
Information element
Status
Description
Status
M
The status for the request: success or fail.
List of AIMLE client IDs
M
A list of AIMLE client IDs that matches the AIML discovery criteria.
AIML supported tasks
O
Indicates the discovered AIML task providers fulfilling the AIML task and AIML task requirements. It includes expected AIML task KPIs like latency, available AIML tasks service duration, list of AIML task providers like IDs or URI, and supported tasks.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.9 AIMLE client selection
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.9.1 General
| The AIMLE client selection procedure has two modes of operation: VAL server selection and AIMLE server selection. In VAL server selection, a List of AIMLE client IDs is provided to form an AIMLE client set, which can be used for AI/ML operations (e.g., training). In AIMLE server selection, a VAL server provides AIMLE client selection criteria and number of the required AIMLE clients for the AIMLE server to select the AIMLE client set.
The following clauses specify procedures, information flows, and APIs for AIMLE client selection.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.9.2 Procedure
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.9.2.1 AIMLE client selection
| Pre-conditions:
1. AIMLE clients that support AI/ML operations have registered with the AIMLE server and included their AIMLE client profiles and optionally a list of supported services.
2. The AIMLE server can access a ML repository to obtain AIMLE client profiles and supported services associated with the AIMLE clients.
Figure 8.9.2.1-1: AIMLE client selection
1. A VAL server sends an AIMLE client selection request to an AIMLE server to select AIMLE clients available for participation in AI/ML operations (e.g., is available and have required data to train an ML model). The AIMLE client selection request includes information as described in Table 8.9.3.1-1.
2. The AIMLE server performs authentication and authorization checks to determine if the requestor is able to select AIMLE clients.
3. If the requestor is authorized, the AIMLE server performs AIMLE client selection based on the provided inputs as described below.
For VAL server selection, the AIMLE server receives a list of AIMLE client IDs in the request and selects the AIMLE clients in the list as candidate AIMLE clients.
For AIMLE server selection, the AIMLE server retrieves a list of clients with AI/ML capabilities from the ML repository. From the list of clients, the AIMLE server selects a list of candidate AIMLE clients, whose client profiles fulfil the AIMLE client selection criteria. The AIMLE server may use SEAL (LM service), NEF (e.g. MonitoringEvent API), and NWDAF (e.g. UE mobility analytics as defined in clause 6.7.2 of 3GPP TS 23.288 [2]) capabilities to assist the AIMLE client selection.
The AIMLE server determines UEs by using their identifiers to determine their location and then selects only those that fulfil the location requirements specified in the AIMLE client selection criteria. The AIMLE server may use SEAL-LMS (as in 3GPP TS 23.434 [5] clause 9.3.9, or 3GPP TS 23.434 [5] clause 9.3.10) or 3GPP 5G Core Network Services (such as GMLC as in 3GPP TS 23.273 [13] and NEF as in 3GPP TS 23.273 [13] or 3GPP TS 23.502 [9]) to determine the UEs which fulfil the location requirement.
The AIMLE server may then determine the QoS parameters for the AIML traffic session between the requestor and the candidate AIMLE client(s) and configure the AI/ML traffic session(s) via SEALDD (Sdd_RegularTransmission API) or NEF services (AfSessionWithQoS API). The AIMLE server determines the application QoS parameters based on the VAL Service ID.
NOTE 1: To determine the application QoS parameters based on the VAL service ID, the AIMLE server can use the VAL service ID associated AIMLE client QoS requirements in the AIMLE client selection criteria provided in step 1.
NOTE 2: If the available AIMLE clients (as determined by the AIMLE server) that fulfil discovery criteria are less than the required number of AIMLE clients for AI/ML operation (e.g., split AI/ML), then the AIMLE server can discover the remaining required AIMLE clients from other AIMLE servers over AIML-E reference point and include them in the AIMLE client selection response message.
NOTE 3: The AIMLE server can reuse SEAL group management for any necessary group management.
4. The AIMLE server performs AIMLE client participation procedure with each candidate AIMLE client as described in clause 8.10.
For all candidate AIMLE clients that agreed to participate in AI/ML operations, the AIMLE server selects the AIMLE clients and assigns an AIMLE client set identifier for the selected clients. The AIMLE client set may then be used for training a ML model.
NOTE 4: If a required minimum number of AIMLE clients for AI/ML operation is provided in the AIMLE client selection request and the number of AIMLE clients that agreed to participate in AI/ML operations is less than this number, an AIMLE client set identifier will not be assigned and the status will be set to fail in the AIMLE client selection response in step 5.
5. The AIMLE server sends an AIMLE client selection response that includes information in Table 8.9.3.2-1.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.9.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.9.3.1 AIMLE client selection request
| Table 8.9.3.1-1 shows the request sent by a VAL server to an AIMLE server for the AIMLE client selection procedure.
Table 8.9.3.1-1: AIMLE client selection request
Information element
Status
Description
Requestor identity
M
The identifier of the requestor (e.g., VAL server).
VAL service identifier
O
An identifier for the VAL service associated with the requestor.
List of AIMLE client IDs
O
(NOTE 1)
(NOTE 3)
A list of AIMLE client IDs that was previously discovered for inclusion into an AIMLE client set.
AIMLE client selection criteria
O
(NOTE 2)
Selection criteria for finding suitable AIMLE clients for AI/ML operations as detailed in Table 8.8.3.1-2.
Number of required AIMLE clients
O
(NOTE 2)
(NOTE 3)
Indicates the requested number of AIMLE clients to be selected based on selection criteria.
Minimum number of required AIMLE clients
O
Indicates the minimum acceptable number of AIMLE clients to be selected.
NOTE 1: This information element is only present for VAL server selection.
NOTE 2: These information elements are only present for AIMLE server selection.
NOTE 3: At least one of the information elements are present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.9.3.2 AIMLE client selection response
| Table 8.9.3.2-1 shows the response sent by the AIMLE server to the VAL server for the AIMLE client selection procedure.
Table 8.9.3.2-1: AIMLE client selection response
Information element
Status
Description
Status
M
The status for the request: success or fail.
AIMLE client set identifier
O
(NOTE 1)
An identifier to associate with the set of AIMLE clients that the VAL server has provided in the request. The AIMLE client set can be updated by using this identifier.
List of AIMLE client IDs
O
(NOTE 1)
(NOTE2)
A list of AIMLE client IDs that matches the AIML selection criteria.
NOTE 1: This is present if the response status is success.
NOTE 2: This information element is present for dynamic selection.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.10 AIMLE client participation
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.10.1 General
| The following clauses specify procedures, information flows, and APIs for AIMLE client participation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.10.2 Procedure
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.10.2.1 AIMLE client participation
|
Figure 8.10.2.1-1: AIMLE client participation
1. An AIMLE server sends an AIMLE client participation request to an AIMLE client to verify participation in AI/ML operation(s). The request includes information as described in Table 8.10.3.1-1.
2. The AIMLE client acknowledge its willingness to be part of (or removed from) the AIMLE client set in an AIMLE client participation response sent to the AIMLE server. The response includes information as described in Table 8.10.3.1-2.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.10.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.10.3.1 AIMLE client participation request
| Table 8.10.3.1-1 shows the request sent by the AIMLE server to each AIMLE client selected for AIMLE client participation procedure.
Table 8.10.3.1-1: AIMLE client participation request
Information element
Status
Description
Requestor identity
M
The identifier of the requestor.
AIMLE client set identifier
M
An identifier for the AIMLE client set.
Add/remove indicator
M
Indicator for adding/removing the AIMLE client to/from the AIMLE client set.
ML model ID
M
The ML model ID to use for the AI/ML operation.
AI/ML operations
M
A list of AI/ML operations (e.g., training) required to be performed.
Operational schedule
O
Schedule for the AI/ML operations.
Dataset requirement
M
Dataset requirements for the AI/ML operations. Requirements includes dataset identifier, dataset size and age, and/or dataset features.
Service requirement
M
Information about the required Service including its VAL service ID and its service permission level (e.g., premium resource usage standard resource usage, limited resource usage)
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.10.3.2 AIMLE client participation response
| Table 8.10.3.2-1 shows the response sent by the AIMLE clients to the AIMLE server for the AIMLE client participation procedure.
Table 8.10.3.2-1: AIMLE client participation response
Information element
Status
Description
Requestor identity
M
The identifier of the requestor.
Status
M
The status for the request: success or failure.
Cause
O
The cause for the request failure.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11 ML model management
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.1 General
| In this functionality, two prodedures are described in more detail in clause 8.11.2 and clause 8.11.3 accordingly:
- Clause 8.11.2 for ML model information storage;
- Clause 8.11.3 for ML model information discovery.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.2 ML model information storage
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.2.1 AIMLE server-initiated ML model information storage
| Figure 8.11.2.1-1 illustrates the procedure of the AIMLE server-initiated ML model information storage.
Pre-condition:
1. The AIMLE server has either received application specific model details from AIML consumer or produced analytics model.
Figure 8.11.2.1-1: AIMLE server-initiated ML model information storage
1. The AIMLE server sends a ML model information storage request to the ML repository to store an ML model. The ML model included in the request is one trained by the ML repository consumer or its information is provisioned to the ML repository consumer. The request contains information elements as described in Table 8.11.4.1-1. The request message may contain Indication of continuous training and continuous training model parameter.
NOTE: The security requirements within the ML model storage requirements are out of scope.
2. Upon receiving the ML model information storage request, the ML repository verifies if the AIMLE server is authorized to store the ML model identified by ADAE Analytics ID and/or list of the allowed vendors provided within the ML model information attribute. If the AIMLE server is authorized, the ML repository processes the request and records information of the ML model (e.g., by creating a ML model profile). The ML repository sends an ML model information storage response to the AIMLE server with an identifier of the created ML model profile.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.2.2 AIMLE consumer-initiated ML model information storage
| Figure 8.11.2.2-1 illustrates the procedure of AIMLE consumer-initiated ML model information storage.
Pre-condition:
1. AIMLE consumer such as AIMLE client or VAL server has ML model or address to ML model.
Figure 8.11.2.2-1: AIMLE consumer-initiated ML model information storage
1. An AIMLE client or a VAL server sends an ML model information storage request to an AIMLE server to store an ML model in the ML repository. The request includes the information elements as described in Table 8.11.4.1-1.
2. The AIMLE server sends an ML model information storage request as described in clause 8.11.2.1 to store the ML model in the ML repository.
3. The AIMLE server sends an ML model information storage response to the AIMLE client or VAL server with the information elements as described in Table 8.11.4.2-1.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.3 ML model information discovery
| Figure 8.11.3-1 illustrates the procedure of ML model information discovery.
Pre-condition:
1. Either AIMLE consumer has requested to discover ML model or AIMLE server decides to discover model for training.
Figure 8.11.3-1: ML model information discovery
1. The AIMLE server sends an ML model information discovery request to the ML repository. The request contains information elements as described in Table 8.11.4.3-1.
2. Upon receiving the ML model information discovery request, the ML repository verifies if the requestor is authorized to discover the ML model(s) identified by the ML model ID. Further, it verifies whether the requestor is present in the list of allowed vendors or not. If the ML repository consumer is authorized, the ML repository processes the request and discovers the model based on ML model ID, ADAE Analytics ID, Base Model ID, and/or ML model interoperability information.
If the discovery request is for transfer of learning, the ML repository identifies all candidate models matching the domain and required accuracy level.
The ML repository sends the response message to the ML repository consumer. The response includes information of the discovered ML model.
NOTE: When the ML model is within training or re-training phase, the ML model is not available for discovery. The details are indicated within the Result IE in Table 8.11.4.4-1. The training and re-training phase is used during federated learning so that AIML enablement consumer can rely on model repository to get the model details.
After the AIMLE server receives the response from the ML repository, the AIMLE server determines whether the received ML model satisfy the ML model requirement of the AIMLE server. If not, the AIMLE server needs to continuously train the model to satisfy the ML model requirement based on the AIMLE server capability of supporting continuous training and ML model profile (Indication of continuous model training, continuous training model parameter).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.4 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.4.1 ML model information storage request
| Table 8.11.4.1-1 describes the information flow from the AIMLE server to the ML repository or from the AIMLE client/VAL server to the AIMLE server as a request for the ML model information storage.
Table 8.11.4.1-1: ML model information storage request
Information element
Status
Description
Requestor Identity
M
The identity of the requestor performing the request.
Security Credentials
O
(NOTE 1)
Security credentials of the requestor performing the request.
ML model
O
(NOTE 2)
The ML model to be stored in the ML repository.
ML model address
O
(NOTE 2)
The address (e.g., a URL or an FQDN) of the ML model file.
ML model information
M
Provides information of the ML model, as described in Table 8.11.4.1-2.
NOTE 1: This information is needed if the requestor is at the VAL service provider domain.
NOTE 2: At least one of these information elements shall be provided.
Table 8.11.4.1-2: ML model information
Information element
Status
Description
ML model identifier
M
An identifier for the ML model
ADAE Analytics ID
O
Represents ADAE analytics ID for which the model can be used.
ML model size
O
Indicates the size of the ML model.
ML model source identifier
O
The identifier of ML model source (e.g., VAL server ID, VAL client ID) that stored the model in the ML repository.
VAL service ID(s)
O
Identify the VAL service ID(s).
Domain
O
Specifies domain for which the model can be used (e.g., for speech recognition, image recognition, video processing, location prediction, etc.).
List of allowed vendors
O
(NOTE 1)
Indicates which vendors that are allowed to use the ML model and thereby also are interoperable to the model.
ML model interoperability information
O
(NOTE 1)
Represents the vendor-specific information that conveys, e.g., requested model file format, model execution environment, input/output parameters of the ML model, etc. The encoding, format, and value of ML Model Interoperable Information is not specified since it is vendor specific information, and is agreed between vendors, if necessary for sharing purposes.
ML Model phase
O
(NOTE 1)
Represents the ML model phase, e.g., in training, trained, re-training, deployed.
> Observed performance
O
(NOTE 2)
Provides information on the performance of the model e.g. accuracy, or application-specific performance metrics (if ML model is in trained or deployment phase).
> Training information
O
(NOTE 2)
If the ML model is in trained or deployed phase: Information on the data that has been used to train the model (e.g. data sources, volume, freshness), and the base model ID in case of Transfer Learning.
> Indication of continuous model training
O
Indicates whether the model can be continuously trained or not.
> Continuous model training parameter
O
Parameters required for continuous model training.
ML model storage and discovery requirements
O
(NOTE 1)
Represents the requirements for the ML repository for the ML model storage and discovery.
> Storage duration
O
Represents the ML model storage duration time. When the storage duration time is expired, the stored ML model and the related information shall be deleted.
> Security and access requirements
O
Represents the information on security requirements for storing the ML model information and the ML model access requirements (e.g., publicly available, private use only, or available for the list of VAL server IDs or VAL client IDs, time period and location access). If the access requirement is private use only, then the model is not discoverable by other consumers.
ML model usage requirements
O
Represents the requirements for using the ML model (e.g. for inference or for training). The requirements are used by the AIMLE server to determine whether an AIMLE client is capable of using the model based on comparing the requirements with information in the AIMLE client profile in Table 8.7.3.1-2.
NOTE 1: At least one of these information elements shall be provided.
NOTE 2: This IE is included only if trained ML model is available.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.4.2 ML model information storage response
| Table 8.11.4.2-1 describes the information flow from the ML repository to the AIMLE server or from the AIMLE server to the AIMLE client/VAL server as a response for the ML model information storage request.
Table 8.11.4.2-1: ML model information storage response
Information element
Status
Description
Result
M
Indicates success or failure of the request.
ML model profile identifier
O
The identifier of the ML model profile created as a result of a successful ML model storage request.
Table 8.11.4.2-2: ML model profile
Information element
Status
Description
ML model profile identifier
M
The identifier of the ML model profile.
AIMLE server identifier
M
The identifier of the AIMLE server that stored the ML model.
ML repository identifier
M
The identifier of the ML repository where the ML model is stored.
ML model information
M
The information about the ML model, as described in Table 8.11.4.1-2.
ML model retrieval endpoint
O
Represents the ML model retrieval endpoint (e.g., URL, URI, IP address and Port) that can be used to download the ML model.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.4.3 ML model information discovery request
| Table 8.11.4.3-1 describes the information flow from the AIMLE server to the ML repository as a request for the ML model information discovery.
Table 8.11.4.3-1: ML model information discovery request
Information element
Status
Description
Requester Identity
M
The identity of the ML repository consumer performing the request.
Filtering criteria
M
Represents the filtering criteria, which can be any of the ML model information as in Table 8.11.4.1-2.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.11.4.4 ML model information discovery response
| Table 8.11.4.4-1 describes the information flow from the model repository to the AIMLE server as a response for the ML model information discovery request.
Table 8.11.4.4-1: ML model information discovery response
Information element
Status
Description
Successful response
O
(NOTE 1)
Indicates that the request was successful.
> ML model profile list
O
(NOTE 2)
Represents the ML model profile(s) of the discovered list of ML models, as described in Table 8.11.4.2-2.
>> ML model profile ID
M
Represents the ML model profile ID of the ML model profile.
> ML model list
O
(NOTE 2)
Represents the ML model(s) of the discovered list of ML models.
>> ML model ID
M
Represents the ML model ID of the ML model.
> Indication of continuous model training
O
Indicate whether the model needs to be continuously trained or not.
Failure response
O
(NOTE 1)
Indicates that the request failed.
> Cause
O
Indicates the failure cause.
NOTE 1: Only one of these information elements shall be provided.
NOTE 2: Only one of these information elements shall be provided.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12 HFL training
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.1 General
| AI/ML training is a highly iterative process and is performed over many training rounds. In the case of federated and distributed learning, the training is performed with many AIMLE clients. Due to the repetitive nature of AI/ML training, the AIMLE server can be configured to manage the training process over multiple training rounds for VAL servers. Note that the HFL training procedure supports horizontal federated learning, distributed learning, transfer learning, and split AI/ML.
The following clauses specify procedures, information flows, and APIs to support HFL training. The procedure for the HFL training is supported for AIMLE server:
- subscription and notification;
- subscription update; and
- unsubscription.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.2 Procedure
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.2.1 HFL training subscription and notification
| Pre-conditions:
1. AIMLE client discovery and selection have been performed.
2. Datasets are available and prepared for AI/ML training at the AIMLE clients. The datasets are assigned identifiers for use in HFL training.
Figure 8.12.2-1: HFL training subscription and notification
1. An AIMLE server receives an ML model training request from a VAL server as described in clause 8.3.2. If the AIMLE server determines to use HFL training, the procedure continues to step 2.
2. The AIMLE server retrieves the indicated ML model using the ML model retrieval procedure as described in clause 8.1.
3. For the HFL training, the AIMLE server performs AIMLE client selection using the AIMLE client selection criteria or a list of AIMLE clients provided in step 1. If AIMLE client selection criteria are provided in step 1, then the AIMLE server continuously monitors and selects AIMLE clients for the HFL training. If a list of AIMLE clients is provided in step 1, the AIMLE server selects the provided AIMLE clients for the HFL training.
4. Based on the AIMLE client set determined in step 3, the AIMLE server checks with the selected AIMLE clients for their capability and participation in the HFL training as described in the clause 8.10.
5. The AIMLE server configures training schedule for each of the AIMLE client and sends a HFL training subscription request with information as described in Table 8.12.3.1-1.
6. Each AIMLE client sends a HFL training subscription response with information as described in Table 8.12.3.2-2. If the AIMLE client is not able to grant the subscription (e.g., is not able to perform the training), the AIMLE client sends a response with a failure status and the procedure skips to step 8.
7. Each AIMLE client performs local training using the configured AI/ML model, model parameters, and the prepared local data associated with the dataset identifier for the specified number of samples according to the operational schedule.
8. Upon completion or due to errors in the training, each AIMLE client sends a HFL training notification to the AIMLE server. The notification includes information as described in Table 8.12.3.1-3. The AIMLE client provides an VAL service ID for the HFL training operation.
9. If errors were encountered, the procedure skips to step 10.
If training was successful, the AIMLE server aggregates (e.g. averages) the model parameters received from the AIMLE clients.
If the training schedule is not complete (e.g., there are remaining training rounds), the AIMLE server configures the next set of training schedules and steps 3 to 8 are repeated for the next training round.
When the training schedule has been exhausted (e.g. there are no remaining training round) and if configured, the AIMLE server makes a ML model information storage request as described in clause 8.11.2 to store the AI/ML model in the ML repository.
10. The AIMLE server sends a ML model training notification to the VAL server as described in clause 8.3.2.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.2.2 HFL training subscription update
| Pre-conditions:
- The AIMLE server has subscribed for the HFL training with the AIMLE client.
Figure 8.12.2-2: HFL training subscription update
1. The AIMLE server sends the HFL training subscription update request containing the subscription identifier and new information as described in Table 8.12.3.1-4 to the AIMLE Client.
2. Upon receiving the request from the AIMLE server, the AIMLE client validates if the AIMLE server is authorized for the request. If the AIMLE server is authorized, the AIMLE client updates the HFL training subscription.
3. The AIMLE client sends the HFL training subscription update response to the AIMLE server. If the AIMLE client has updated the HFL training subscription, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.2.3 HFL training unsubscription
| Pre-conditions:
- The AIMLE server has subscribed for the HFL training with the AIMLE client.
Figure 8.12.2-3: HFL training unsubscription
1. The AIMLE server sends the HFL training unsubscription request containing the subscription identifier to the AIMLE Client.
2. Upon receiving the request from the AIMLE server, the AIMLE client validates if the AIMLE server is authorized for the request. If the AIMLE server is authorized, the AIMLE client unsubscribe the HFL training subscription.
3. The AIMLE client sends the HFL training unsubscription response to the AIMLE server. If the AIMLE client has unsubscribed the HFL training subscription, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.3.1 HFL training subscription request
| Table 8.12.3.1-1 shows the request sent by the AIMLE server to AIMLE clients for the HFL training subscription and HLF training subscription update procedure.
Table 8.12.3.1-1: HFL training subscription request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
AI/ML model and model parameters
M
(NOTE)
Information about the AI/ML model and model parameters for use in HFL training.
Dataset identifier
M
(NOTE)
The dataset identifier associated with the dataset used for HFL training.
Number of data samples
M
(NOTE)
The number of data samples required for a round of HFL training.
Operational schedule
O
A schedule for when training is to occur.
Notification settings
O
Settings for how often to send notifications providing status of HFL training. For example, periodic, event- triggered (e.g. based on percentage completion), upon completion of each training round.
NOTE: These IEs are optional in HFL training subscription update procedure.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.3.2 HFL training subscription response
| Table 8.12.3.2-1 shows the response sent by AIMLE clients to the AIMLE server for the HFL training subscription procedure.
Table 8.12.3.2-1: HFL training subscription response
Information element
Status
Description
Status
M
The status for the subscription request: success, fail.
Subscription ID
O
An identifier for the subscription only if the status is success.
VAL service ID
M
The VAL service identifier for the AIMLE HFL training operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.12.3.3 HFL training subscription notification
| Table 8.12.3.3-1 shows the notification sent by AIMLE clients to the AIMLE server for the HFL training subscription procedure.
Table 8.12.3.3-1: HFL training subscription notification
Information element
Status
Description
Status
M
Status for the request: success, fail.
VAL service ID
M
The VAL service identifier for the AIMLE HFL training operation.
HFL training output
M
ML model parameters from HFL training.
Errors list
O
A list of errors encountered during a HFL training round.
Timestamp
O
A timestamp for the notification.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13 AIMLE client selection subscription and notification
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.1 General
| AIMLE client selection subscription request and notification enable VAL Servers to subscribe for monitoring and selection of AIMLE clients and receive notification when there is an update on the selected and re-selected AIMLE client’s status when re-selection is performed according to AIML member selection criteria.
The AIMLE server interacts with the NEF and/or SEAL services to monitor AIML members who meet the selection criteria and obtain their identifiers and configuring the AIML traffic session(s) between the VAL Server and the selected AIMLE Client(s) who meet the criteria. When the AIMLE clients no more meet the criteria, the QoS adjustment is reversed.
The subscription may also be updated when the VAL Server's requirements change, ensuring that it remains relevant and accurate. The VAL server may also unsubscribe when the subscription is no longer needed so that the AIMLE Server terminates monitoring of AIMLE clients and reverses QoS adjustments.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.2 Procedures
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.2.1 General
| The following are supported for AIMLE client selection subscription and notification :
- AIMLE client selection subscription and notification;
- AIMLE client selection subscription update; and
- AIMLE client selection unsubscribe
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.2.2 AIMLE client selection subscription and notification
|
Figure 8.13.2.2-1: AIMLE client selection subscription and notification
1. A VAL server sends an AIMLE client selection subscription request to the AIMLE Server. The AIMLE client selection subscription request includes information as described in Table 8.13.3-1 which includes selection criteria.
2. The AIMLE server validates the AIMLE client selection subscription request. The AIMLE server further performs authentication and authorization checks to determine if the requestor is able to subscribe to the selected AIMLE client selection subscription request.
3. The AIMLE server sends the AIMLE client selection subscription response to the VAL server.
4. The AIMLE server monitors AIMLE clients whether they fulfil the selection criteria as provided in step 1. The AIMLE server interacts with the NEF and/or SEAL services (including SEALDD) to establish monitoring. The AIMLE server utilizes SEAL-LMS (as in 3GPP TS 23.434 [5] clause 9.3.11, or 3GPP TS 23.434 [5] clause 9.3.12) or 3GPP 5G Core Network Services (such as GMLC as in 3GPP TS 23.273 [13] and NEF as in 3GPP TS 23.273 [13] or 3GPP TS 23.502 [9]) to establish monitoring of UEs entering or present in the target location provided in the location information in the selection criteria.
5. The AIMLE Server obtains the identifiers of the AIMLE clients from the monitoring and selects the clients that fulfil the selection criteria and remove the AIMLE clients which do not fulfil the selection criteria. The AIMLE server uses the location monitoring for selecting UEs that fulfil the location criteria and removing UEs which cease to fulfil the location criteria as provided in the location information in the AIMLE client selection criteria. The AIMLE Server may determine the application QoS parameters (e.g. bandwidth, latency, jitter) for the AIML traffic session between the VAL server and the selected AIMLE client and configure the AIML traffic session(s) via SEALDD (Sdd_RegularTransmission API) or NEF services (AfSessionWithQoS API). When the AIMLE clients no more meet the criteria, the QoS adjustment is reversed.
The AIMLE server may determine the application QoS parameters based on the VAL Service ID.
If a desired service in the selection criteria is ceased to be provided by the client or its profile change so that it no longer meets the selection criteria, the AIMLE server removes the AIMLE clients which ceases to fulfil the criteria and selects other clients that fulfil selection criteria.
NOTE 1: To determine the application QoS parameters based on the VAL service ID, the AIMLE server can use the VAL service ID associated AIMLE client QoS requirements in the AIMLE client selection criteria provided in step 1.
NOTE 2: In case of AIMLE server determining the application QoS parameters based on the VAL service ID, how it does this is up to implementation.
6. The AIMLE Server notifies the VAL server about the selected and re-selected AIMLE clients e.g., the AIMLE Client A is re-selected and replaced by AIMLE Client B.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.2.3 AIMLE client selection subscription update
| Figure 8.13.2.3-1 illustrates the procedure for an VAL server to update a subscription with the AIMLE server.
Pre-conditions:
1. The AIMLE client or VAL server has subscribed for AIMLE client selection with the AIMLE Server.
Figure 8.13.2.3-1: AIMLE client selection subscription update
1. A VAL server sends a AIMLE client selection subscription update request to the AIMLE server. The AIMLE client selection subscription update request includes the subscription identifier and may include information as described in Table 8.13.3.w-1 for updated subscription.
2. Upon receiving the request from the VAL server, the AIMLE server validates if the VAL server is authorized for the request. If the VAL server is authorized, the AIMLE server updates the subscription.
3. The AIMLE server sends a AIMLE client selection subscription update response to the VAL server. If the AIMLE server has updated the subscription, the response includes an indication of success. If the AIMLE server has not updated the subscription, the response includes an indication of failure and may include a reason for failure.
If the subscription update request in step 1 include updated information as in Table 8.13.3.w-1, the AIMLE server also adjusts step 4 and 5 as in clause 8.13.2.2 based on the updated information in the subscription update.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.2.4 AIMLE client selection unsubscribe
| Figure 8.13.2.4-1 illustrates the procedure for a VAL server to unsubscribe with the AIMLE server.
Pre-conditions:
1. The VAL server has subscribed for AIMLE client selection with the AIMLE Server.
Figure 8.13.2.4-1: AIMLE client selection unsubscribe
1. A VAL server sends a AIMLE client selection unsubscribe request to the AIMLE server. The request includes the subscription identifier.
2. Upon receiving the request from the requestor, the AIMLE server validates if the VAL server is authorized for the request. If the VAL is authorized, the AIMLE server unsubscribes the subscription.
3. The AIMLE server sends a AIMLE client selection unsubscribe response to the VAL server. If the AIMLE server has unsubscribed the subscription, the response includes an indication of success. If the AIMLE server has not unsubscribed the subscription, the response includes an indication of failure and may include a reason for failure.
If the AIMLE server has successfully unsubscribed the subscription, it also cancels its corresponding subscriptions with the NEF and/or SEAL services (including SEALDD) associated with the subscription. Additionally, the AIMLE server reverses the QoS adjustments performed as described in step 5 of clause 8.13.2.2.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3.1 General
| The following information flows are specified for AIMLE client registration:
- AIMLE client selection subscription and notification request and response;
- AIMLE client selection subscription update request and response; and
- AIMLE client selection unsubscribe request and response
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3.2 AIMLE client selection subscription request
| Table 8.13.3.2-1 shows the request sent by a VAL server to an AIMLE server for the Selected AIMLE Client selection subscription.
Table 8.13.3.2-1: AILME client selection subscription request
Information element
Status
Description
Requestor identity
M
The identifier of the requestor.
AIMLE client selection criteria
M
Selection criteria for finding suitable AIMLE clients for AIML operations as detailed in per clause 8.8.3.1-2.
Number of the required AIML clients
O
Indicates the requested number of AIML clients to be selected based on member selection policies.
Notification endpoint for the selected AIMLE Client’s
M
Represents the endpoint at the VAL server for receiving the notifications on the selected AIMLE Client’s status update.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3.3 AIMLE client selection subscription response
| Table 8.13.3.3-1 shows the response sent by the AIMLE server to the VAL server for the selected AIMLE client selection subscription response.
Table 8.13.3.3-1: AIMLE client selection subscription response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the subscription was successful.
> Subscription ID
M
The identifier of the subscription.
> Expiration time
O
Indicates the expiration time of the updated subscription. To maintain an active subscription status, a subscription update is required before the expiration time.
If the Expiration time IE is not included, it indicates that the updated subscription never expires.
Failure response
O
(NOTE)
Indicates that the subscription request failed.
> Cause
O
Indicates the cause of subscription request failure
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3.4 AIMLE client selection update notification
| Table 8.13.3.4-1 shows the notification sent by the AIMLE Server to the VAL server for the AIMLE client selection update notification.
Table 8.13.3.4-1: AIMLE client selection update notification
Information element
Status
Description
Requestor ID
M
The identifier of the requestor.
List of the selected AIMLE Client status update events
M
Represents the list of selected AIMLE Client status update events, e.g., the AIMLE Client A is re-selected and replaced by AIMLE Client B.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3.5 AIMLE client subscription update request
| Table 8.13.3.5-1 shows the request sent by a VAL server to an AIMLE server for the AIMLE client selection subscription update request.
Table 8.13.3.5-1: AIMLE client selection subscription update request
Information element
Status
Description
Subscription ID
M
Identifier of the existing subscription for which the update request applies.
AIMLE client selection criteria
O
Selection criteria for finding suitable AIMLE clients for AIML operations as detailed in per clause 8.8.3.1-2.
Number of the required AIML clients
O
Indicates the requested number of AIML clients to be selected based on member selection policies.
Notification endpoint for the selected AIMLE Client’s
O
Represents the endpoint at the VAL server for receiving the notifications on the selected AIMLE Client’s status update.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3.6 AIMLE client selection subscription update response
| Table 8.13.3.6-1 shows the AIMLE client selection subscription update response sent by the AIMLE server to the VAL server.
Table 8.13.3.6-1: AIMLE client selection subscription update response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the subscription update request was successful.
> Expiration time
O
Indicates the expiration time of the updated subscription. To maintain an active subscription status, a subscription update is required before the expiration time.
If the Expiration time IE is not included, it indicates that the updated subscription never expires.
Failure response
O
(NOTE)
Indicates that the subscription update request failed.
> Cause
O
Indicates the cause of subscription update request failure.
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3.7 AIMLE client selection unsubscribe request
| Table 8.13.3.7-1 shows the request sent by a VAL server to an AIMLE server for the AIMLE client selection unsubscribe request.
Table 8.13.3.7-1: AIMLE client selection unsubscribe request
Information element
Status
Description
Subscription ID
M
Identifier of the existing subscription for which the unsubscribe request applies.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.13.3.8 AIMLE client selection unsubscribe response
| Table 8.13.3.8-1 shows the AIMLE client selection unsubscribe response sent by the AIMLE server to the VAL server.
Table 8.13.3.8-1: AIMLE client selection unsubscribe response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the unsubscribe request was successful.
Failure response
O
(NOTE)
Indicates that the unsubscribe request failed.
> Cause
O
Indicates the cause of unsubscribe request failure.
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14 Support for Split AI/ML Operation
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.1 General
| 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.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2 Procedure
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2.1 General
| 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;
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2.2 Split operation pipeline discovery
| 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:
1. The AIMLE client has received information (e.g. URI, IP address) related to the AIMLE Server;
2. The AIMLE client has received security credentials authorizing it to communicate with the AIMLE server;
Figure 8.14.2.2-1: Split operation pipeline discovery
1. 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.
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.
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.
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.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2.3 Split operation pipeline creation
| 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:
1. The AIMLE client has received information (e.g. URI, IP address) related to the AIMLE Server;
2. The AIMLE client has received security credentials authorizing it to communicate with the AIMLE server;
3. The AIMLE client has discovered information about processing nodes available with the AIMLE server;
4. 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.
Figure 8.14.2.3-1: Split operation pipeline creation
1. 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.
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.
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.
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.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2.4 Split operation node registration
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2.4.1 General
| 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.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2.4.2 Split operation node registration
| 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:
1. The VAL server has received information (e.g. URI, IP address) related to the AIMLE Server;
2. The VAL server has received security credentials authorizing it to communicate with the AIMLE server;
Figure 8.14.2.4.2-1: Split operation node registration
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.
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.
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.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2.4.3 Split operation node registration update
| Figure 8.14.2.5-1 illustrates the procedure for VAL server to update a split operation node registration with the AIMLE server.
Pre-conditions:
1. The VAL server has registered with the AIMLE Server.
Figure 8.14.2.4.3-1: Split operation node registration update
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.
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.
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.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.14.2.4.4 Split operation node de-registration
| 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:
1. The VAL server has registered with the AIMLE Server.
Figure 8.14.2.4.4-1: Split operation node de-registration
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.
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.
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.