Content for TS 23.482 Word version: 19.3.0
8.7 AIMLE client registration
8.7.1 General
8.7.2 Procedures
8.7.2.1 General
8.7.2.2 AIMLE client registration
8.7.2.3 AIMLE client registration update
8.7.2.4 AIMLE client de-registration
8.7.3 Information flows
8.8 AIMLE client discovery
8.8.1 General
8.8.2 Procedure
8.8.3 Information flows
...
...
8.7 AIMLE client registration p. 48
8.7.1 General p. 48
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.
8.7.2 Procedures p. 48
8.7.2.1 General p. 48
The following are supported for AIMLE client registration:
- AIMLE client registration procedure;
- AIMLE client registration update procedure; and
- AIMLE client de-registration procedure
8.7.2.2 AIMLE client registration p. 48
Pre-conditions:
- The AIMLE client has been pre-configured or has discovered the address (e.g., URI) of the AIMLE server.
- The AIMLE client has been pre-configured with an AIMLE client profile.
Step 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.
Step 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.
Step 3.
The AIMLE server returns an AIMLE client registration response to the AIMLE client with the status of the request.
8.7.2.3 AIMLE client registration update p. 49
Pre-conditions:
- The AIMLE client has already registered with the AIMLE Server.
Step 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.
Step 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.
Step 3.
The AIMLE server returns an AIMLE client registration update response to the AIMLE client with the status of the update.
8.7.2.4 AIMLE client de-registration p. 50
Pre-conditions:
- The AIMLE client has already registered with the AIMLE Server.
Step 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.
Step 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.
Step 3.
The AIMLE server returns an AIMLE client de-registration response to the AIMLE client with the status of the request.
8.7.3 Information flows p. 50
8.7.3.1 General p. 50
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
8.7.3.2 AIMLE client registration request p. 50
Table 8.7.3.2-1 shows the request sent by an AIMLE client to an AIMLE server for the 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). |
| 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.
|
|||||||||
8.7.3.3 AIMLE client registration response p. 51
Table 8.7.3.3-1 shows the AIMLE client registration response sent by the AIMLE server to the AIMLE client.
| 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.
|
||
8.7.3.4 AIMLE client registration update request p. 52
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.
| 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). |
8.7.3.5 AIMLE client registration update response p. 52
Table 8.7.3.5-1 shows the AIMLE client de-registration update response sent by the AIMLE server to the AIMLE client.
| 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.
|
||
8.7.3.6 AIMLE client de-registration request p. 53
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.
| Information element | Status | Description |
|---|---|---|
| Registration ID | M | Identifier of the existing registration for which the update request applies. |
8.7.3.7 AIMLE client de-registration response p. 53
Table 8.7.3.7-1 shows the AIMLE client de-registration response sent by the AIMLE server to the AIMLE client.
| 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.
|
||
8.8 AIMLE client discovery p. 53
8.8.1 General p. 53
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.
8.8.2 Procedure p. 54
8.8.2.1 AIMLE client discovery p. 54
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 AIMLE clients.
Step 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.
Step 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 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.
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.
Step 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.
8.8.3 Information flows p. 55
8.8.3.1 AIMLE client discovery request p. 55
Table 8.8.3.1-1 shows the request sent by a VAL server to an AIMLE server for the AIMLE client discovery procedure.
| 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. |
| 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. |
8.8.3.2 AIMLE client discovery response p. 55
Table 8.8.3.2-1 shows the response sent by the AIMLE server to the VAL server for the AIMLE client discovery procedure.
| 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. |
