Content for TS 23.482 Word version: 19.3.0
8.9 AIMLE client selection
8.9.1 General
8.9.2 Procedure
8.9.3 Information flows
8.10 AIMLE client participation
8.10.1 General
8.10.2 Procedure
8.10.3 Information flows
...
...
8.9 AIMLE client selection p. 56
8.9.1 General p. 56
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.
8.9.2 Procedure p. 56
8.9.2.1 AIMLE client selection p. 56
Pre-conditions:
- 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.
- The AIMLE server can access a ML repository to obtain AIMLE client profiles and supported services associated with the AIMLE clients.
Step 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.
Step 2.
The AIMLE server performs authentication and authorization checks to determine if the requestor is able to select AIMLE clients.
Step 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 TS 23.288) 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 clause 9.3.9 of TS 23.434, or clause 9.3.10 of TS 23.434) or 3GPP 5G Core Network Services (such as GMLC as in TS 23.273 and NEF as in TS 23.273 or TS 23.502) 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.
Step 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.
Step 5.
The AIMLE server sends an AIMLE client selection response that includes information in Table 8.9.3.2-1.
8.9.3 Information flows p. 57
8.9.3.1 AIMLE client selection request p. 57
Table 8.9.3.1-1 shows the request sent by a VAL server to an AIMLE server for the AIMLE client selection procedure.
| 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.
|
||
8.9.3.2 AIMLE client selection response p. 58
Table 8.9.3.2-1 shows the response sent by the AIMLE server to the VAL server for the AIMLE client selection procedure.
| 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.
|
||
8.10 AIMLE client participation p. 58
8.10.1 General p. 58
The following clauses specify procedures, information flows, and APIs for AIMLE client participation.
8.10.2 Procedure p. 58
8.10.2.1 AIMLE client participation p. 58
Step 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.
Step 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.2-1.
8.10.3 Information flows p. 59
8.10.3.1 AIMLE client participation request p. 59
Table 8.10.3.1-1 shows the request sent by the AIMLE server to each AIMLE client selected for AIMLE client participation procedure.
| 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). |
8.10.3.2 AIMLE client participation response p. 59
Table 8.10.3.2-1 shows the response sent by the AIMLE clients to the AIMLE server for the AIMLE client participation procedure.
| 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. |
