hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.3.2 AIMLE client
| The AIMLE client functional entity acts as the application client supporting AIMLE services. It interacts with the AIMLE server.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.3.3 AIMLE server
| The AIMLE server functional entity provides AIMLE services supported within the vertical application layer. It interacts with the AIMLE client, the 3GPP network, other SEAL services, and VAL server.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.3.4 ML repository
| The ML repository is a logical entity that serves both as a registry for ML/FL members and as a repository for application layer ML model related information. It can be accessed by the AIMLE server.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.4 Reference Points Description
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.4.1 General
| The reference points for the functional model related to AIMLE are described in the following subclauses.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.4.2 AIML-UU
| The interactions related to AIML enablement functions between the AIMLE client and AIMLE server are supported by AIML-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [7] and 3GPP TS 23.501 [6].
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.4.3 AIML-S
| The interactions related to AIML enablement functions between the VAL server(s) and the AIMLE server are supported by AIML-S reference point.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.4.4 AIML-C
| The interactions related to AIML enablement functions between the VAL client(s) and the AIMLE client within a VAL UE are supported by AIML-C reference point.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.4.5 AIML-R
| The interactions related to AIML enablement functions between the AIMLE server, and the ML repository are supported by AIML-R reference point.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.4.6 AIML-E
| The interactions related to AIML enablement functions between AIMLE servers (e.g., central and edge AIMLE servers).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.4.7 AIML-PC5
| The interactions related to AIML enablement functions between AIMLE clients in off-network deployments.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6 AIMLE Functional Description
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.1 Support for ML model retrieval
| This functionality covers the retrieval of ML models by an AIMLE client or a VAL server via the AIMLE server. The AIMLE server provides the functionality required to retrieve ML models stored in a ML repository based on a filtering criteria. The functionality is provided to the ML model consumer via an API following a request/response model or a subscribe/notify model.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.2 Support for ML model training
| This functionality enables the AIMLE server to support ML model training based on requests from a VAL server. The AIMLE server provides the functionality to train a specific ML model or assist the ML model training at VAL server/client(s).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.3 Support for FL member registration
| This functionality covers the registration, registration update and de-registration of the candidate FL member to the ML repository which is keeping the FL member registrations. Such candidate member can be a VAL server functionality or an enabler layer functionality (e.g. AIMLE server) which is registering to the ML repository/registry to act as FL member for a given application event (analytics event or event triggered by a VAL layer application server).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.4 Support for FL events subscription and notification
| This functionality enables a consumer (who can be the AIMLE server or a VAL server e.g. acting as FL server) to subscribe for FL related events and getting notified on changes on the availability of the FL members which are to be used for the FL-related task (e.g., training). This capability at the ML repository acting as an AIML service registry supports the subscription for events related to FL members and the notification to the consumer in case of changes. This feature assumes that such FL members (AIMLE or VAL server or AIMLE clients) have previously registered to this registry their availability and capabilities.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.5 Support AI/ML task transfer
| This functionality covers the AIMLE support for ML task transfer, which is applicable to scenarios where an AI/ML member cannot finish the assigned AI/ML task during the performing process. In this scenario, the AIMLE server assists the source AI/ML member by support transferring 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 | 6.6 Support for AIMLE client registration
| This functionality allows an AIMLE client (e.g., AI/ML capable UEs) to register with an AIMLE server. The AIMLE server stores the client information for future interactions. This functionality is crucial for enabling the AIMLE client to participate in AI/ML operations.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.7 Support for AIMLE client discovery
| This functionality enables the VAL server to discover available AIMLE clients for AI/ML operations, such as training or inference. The AIMLE server provides the functionality to select suitable AIMLE clients that fulfill the discovery criteria.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.8 Support for AIMLE client selection
| This functionality enables the selection of AIMLE clients to participate in AI/ML operations. There are two modes for client selection: VAL server selection and AIMLE server selection. In VAL server selection, the functionality is provided by the AIMLE Server selecting candidate AIMLE clients from the client list provided by the VAL Server. In AIMLE server selection, the functionality is provided by the AIMLE Server selecting candidate AIMLE clients based on the client selection criteria provided by the VAL Server from the AIMLE clients in the ML repository.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.9 Support for AIMLE client participation
| This functionality enables the AIMLE server to verify and manage the participation of AIMLE clients in AI/ML operations. The AIMLE client responds with its willingness to perform AI/ML operations based on the information provided by the AIMLE server.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.10 Support for ML model management
| This functionality enables the AIMLE server to manage ML models through interaction with the ML repository. The AIMLE server provides the storage and discovery functionality for ML model information. The storage functionality allows the AIMLE server to store ML model information in the repository. The discovery functionality enables the AIMLE server to retrieve information about available ML models via an API following a request/response model.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.11 Support HFL training
| This functionality provides the AIMLE server support for horizontal federated learning. This support is applicable to the case where multiple AIMLE clients are expected to locally train the ML model, and the AIMLE server is required to select, configure and coordinate the HFL clients.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.12 Support AIMLE client selection subscription and notification
| This functionality is related to the AIMLE client selection subscription request and notification to enable VAL Servers to subscribe for monitoring AIML members who meet criteria for performing an AIMLE service, selecting AIMLE clients and receiving notification when there is an update on the selected and re-selected AIML client’s status when re-selection is performed according to AIML member selection criteria.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.13 Support for Split AI/ML Operation
| Split AI/ML operation is a type of AI/ML operation that allows distributed processing related to ML models into multiple stages on different processing nodes. The intention is to offload the computation-intensive and energy-intensive AI/ML stages to network endpoints, whereas leave the privacy-sensitive and delay-sensitive stage at the end device as described in 3GPP TS 22.261 [10].
The following functionality is provided to support split AI/ML operation:
- An application consuming services from the AI/ML application enablement layer can discover or manage (e.g., create, update, delete) a split operation profile with the AIMLE server for the purpose of consuming results from corresponding instance of a split AI/ML operation pipeline.
- A VAL server can register with the AIMLE server to indicate its capabilities for acting as a processing node of an instance of a split AI/ML operation pipeline.- An application consuming services from the AI/ML application enablement layer can subscribe with the AIMLE server to receive event notifications related to an instance of a split AI/ML operation pipeline.
NOTE: How to split a ML model is out of scope of this release and the ML model used in a stage needs to be available in the ML repository.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.14 Support data management assistance
| This functionality covers the AIMLE assistance in data management related operations in the ML model lifecycle. AIMLE data management assistance is the process of the AIMLE server assisting AIMLE service consumers with managing data operations (data preparation and processing) performed by VAL clients.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.15 Support for Transfer Learning enablement
| This functionality covers the support for discovering and selecting pre-trained models transfer learning operations in application enablement layer, where the support is based on the request for either an ML task from VAL layer or for an analytics task from ADAES. Transfer Learning enablement allows the consumer to discover the similar ML models to be used as base models for the TL, as well as to support the selection of the best model to be used as pre-trained model.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.16 Support for FL member grouping
| This functionality covers the AIMLE capability to enable the group management of the entities serving as FL clients at the application enablement layer. Such group management is about the creation, monitoring and update of the FL member groups based on the AI/ML operations, which are based on 1) the analytics event/service by ADAES or 2) the VAL requirement for FL support services.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.17 Support vertical federated learning
| This functionality is related to the AIMLE support for vertical FL (VFL) among AIMLE clients serving as VFL members. This capability involves the determination of employing VFL based on the ML model training request, the feature alignment and the decision on the AIMLE clients serving as VFL clients, based on the training capability evaluation functionality.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.18 Support for ML model training capability evaluation
| This functionality enables AIMLE server to request AIMLE client for ML model training capability evaluation to support FL training (e.g. HFL, VFL). AIMLE client evaluates its capability and availability to join the FL training process and responds to the AIMLE server with the evaluation result (e.g. join the FL training process with test result, or not join with fail reason). The ML model training capability evaluation result can be used by the AIMLE server to select FL members for FL training process (e.g. HFL, VFL).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.19 Support AIML service operations control and management
| This functionality enables the VAL server (as AIMLE service consumer) to control the operation mode of an AIMLE service for a given AI/ML operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.20 Support for ML model update
| This functionality enables the AIMLE server to update trained and deployed ML models by detecting model performance degradation, and triggering ML model re-training and update to fix the observed degradation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.21 Support for ML model performance monitoring
| This functionality covers a capability of AIMLE server for monitoring detecting a degradation relation to an ML operation / analytics operation and translating to an ML model degradation (expected or predicted) and performing an action to alleviate this issue (new model training or re-training).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.22 Support for AIMLE assisted ML model selection
| This functionality enables an AIMLE service consumer to request assistance with ML model selection from an AIMLE server. The AIMLE server returns a list of ML models with corresponding model performance.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.23 Support for AIMLE context transfer in edge data networks
| This functionality provides support for AIMLE operations performed by AIMLE clients spread across multiple edge service areas in edge data networks. The functionality allows the context transfer between edge AIMLE servers when an AIMLE client moves to a different edge service area.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 6.24 Support for Assisting Hierarchical Computing
| This functionality provides support for assisting hierarchical computing by AIMLE servers. The functionality allows the consumer to request hierarchical computing assistance information to support its operations.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7 Identities and commonly used values
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.1 General
| The common identities for SEAL and ADAES refer to 3GPP TS 23.434 [5] and 3GPP TS 23.436 [4] respectively. The following clauses list the additional identities and commonly used values for AIMLE Service.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.2 AIMLE server ID
| The AIMLE server ID uniquely identifies the AIML enablement server.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.3 AIMLE client ID
| The AIMLE client ID uniquely identifies the AIML enablement client.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.4 ML repository ID
| The ML repository ID uniquely identifies the ML-related repository function, which is used for storing the ML models and ML related information, as well as for serving as registry for the ML / FL members.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.5 ML model ID
| The ML model ID uniquely identifies the application-layer ML model.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.6 FL member ID
| The FL member ID uniquely identifies the participant entity in a Federated Learning process which is supported by AIMLE service, e.g., AIMLE server ID, VAL server ID or EAS ID.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.7 AIMLE service area
| The AIMLE service area is the area where the AIML Enablement server owner provides its AIML support services. The AIMLE service area can be expressed as a Topological Service Area (e.g., a list of TA), a Geographical Service Area (e.g., geographical coordinates) or both.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.8 ML model profile ID
| The ML model profile ID uniquely identifies a ML model profile that is created by the ML repository as a result of a successful ML model storage request by a AIMLE server.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 7.9 AIMLE client set ID
| The AIMLE client set ID is a unique identifier assigned by an AIMLE server that is associated with the set of AIMLE clients that have been selected and have agreed to participate in performing AI/ML related operations, e.g., ML model training.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8 Procedures and information flows
| The security aspects for the AIMLE services are specified in 3GPP TS 33.434 [14].
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.1 General
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2 ML model retrieval
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.1 General
| ML model retrieval enable applications consuming services from the AI/ML application enablement layer to retrieve ML models available with the enablement layer.
ML model retrieval enables an AIMLE client or VAL server to obtain ML models of interest. The retrieval of ML models is based on matching ML model retrieval filters provided in the request.
ML model retrieval subscription enables an AIMLE client or VAL server to receive notifications about ML models of interest. The subscription is based on matching ML model retrieval filters provided in the subscription request.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2 Procedure
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2.1 General
| Following procedures are supported for ML model retrieval:
- ML model retrieval request-response procedure;
- ML model subscribe-notify procedures for retrieval of ML models, comprising:
- Subscription procedure;
- Subscription update procedure; and
- Unsubscribe procedure;
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2.2 ML model retrieval
| Figure 8.2.2.2-1 illustrates the procedure for an AIMLE client or VAL server to discover and obtain ML models from the AIMLE server.
Pre-conditions:
1. The AIMLE client or VAL server has received information (e.g., URI, IP address) related to the AIMLE Server.
2. The AIMLE client or VAL server has received security credentials authorizing it to communicate with the AIMLE server.
Figure 8.2.2.2-1: ML model retrieval
1. The requestor (e.g., AIMLE client or VAL server) sends a ML model retrieval request to the AIMLE server. The request includes the requestor identifier along with security credentials and may include ML model retrieval filters.
2. Upon receiving the request from the requestor, the AIMLE server validates if the requestor is authorized for the request.
If the requestor is authorized, the AIMLE server may determine if the requested ML model is available with the AIMLE server based on ML model retrieval filters. If the ML model is not available with the AIMLE server, the AIMLE server performs the ML model information discovery procedure with the ML repository as described in clause 8.11.3.
If the request is received from an AIMLE client that has registered with the AIMLE server, the AIMLE server determines the ML model based on the AIMLE client profile (Table 8.7.3.2-2), e.g. supported AI/ML model types, application layer AIMLE client capabilities.
3. The AIMLE server sends a ML model retrieval response to the requestor. If the AIMLE server has determined ML models (e.g., locally, or from the ML repository), the response includes an indication of success and may include the ML models. Otherwise, the response includes an indication of failure and may include a reason for failure.
Upon receiving a response including ML models, the requestor can store the ML models and may provide the ML model to the VAL client(s) if the requestor is the AIMLE client.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2.3 ML model retrieval subscription
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2.3.1 General
| Clause 8.2.2.3.2 and clause 8.2.2.3.3 together illustrate the ML model retrieval subscribe-notify ML model.
Clause 8.2.2.3.4 illustrates the ML model retrieval subscription update procedure.
Clause 8.2.2.3.5 illustrates the ML model retrieval unsubscribe procedure.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2.3.2 Subscribe
| Figure 8.2.2.3.2-1 illustrates the procedure for an AIMLE client or VAL server to subscribe with the AIMLE server to be notified of retrieval of ML models.
Pre-conditions:
1. The AIMLE client or VAL server has received information (e.g. URI, IP address) related to the AIMLE Server.
2. The AIMLE client or VAL server has received security credentials authorizing it to communicate with the AIMLE server.
Figure 8.2.2.3.2-1: ML model retrieval subscription
1. The requestor (e.g., AIMLE client or VAL server) sends a ML model retrieval subscribe request to the AIMLE server. The request includes the requestor identifier, security credentials and may include ML model retrieval filters and expiration time.
2. Upon receiving the request from the requestor, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server creates the subscription and stores the subscription information.
3. The AIMLE server sends a ML model retrieval subscribe response to the requestor. If the AIMLE server has created the subscription, the response includes an indication of success, the subscription identity and may include an expiration time; to maintain the subscription, the requestor shall send a subscription update request before the expiration time, otherwise the ML model retrieval subscription expires. If the AIMLE server has not created the subscription, the response includes an indication of failure and may include a reason for failure.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2.3.3 Notify
| Figure 8.2.2.3.3-1 illustrates the ML model retrieval notify operation between the AIMLE server and an AIMLE client or VAL server.
Pre-conditions:
1. The AIMLE client or VAL server has subscribed for ML model retrieval with the AIMLE Server.
Figure 8.2.2.3.3-1: ML model retrieval notification
1. An event occurs at the AIMLE server that satisfies trigger conditions for notifying a subscriber (e.g., AIMLE client or VAL server). The event may be the detection of availability of new ML model(s) (e.g., new ML model or new revision of a ML model) that satisfies the ML model retrieval filters of the subscription, or changes in the AIMLE client profile. For example, the AIMLE server receives an updated AIMLE client profile with updated “supported AI/ML model type” which indicates the existing model is no longer supported and a new model needs to be retrieved. The detection of availability of new ML models by the AIMLE server is based on ML model storage in the ML repository as described in clause 8.11.2.
2. The AIMLE server sends a ML model retrieval notification to the requestor indicating newly available ML models. The notification includes a subscription identity and newly available ML model(s).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2.3.4 Subscription update
| Figure 8.2.2.3.4-1 illustrates the procedure for an AIMLE client or VAL server to update a subscription with the AIMLE server.
Pre-conditions:
1. The AIMLE client or VAL server has subscribed for ML model retrieval with the AIMLE Server.
Figure 8.2.2.3.4-1: ML model retrieval subscription update
1. The requestor (e.g., AIMLE client or VAL server) sends a ML model retrieval update request to the AIMLE server. The request includes the requestor identifier, security credentials and the subscription identifier and may include ML model retrieval filters and expiration time.
2. Upon receiving the request from the requestor, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server updates the subscription information.
3. The AIMLE server sends a ML model retrieval subscription update response to the requestor. If the AIMLE server has updated the subscription, the response includes an indication of success and may include an expiration time. To maintain the subscription, the requestor shall send a subscription update request before the expiration time, otherwise the ML model retrieval subscription expires. If the AIMLE server has not updated the subscription, the response includes an indication of failure and may include a reason for failure.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.2.3.5 Unsubscribe
| Figure 8.2.2.3.5-1 illustrates the procedure for an AIMLE client or VAL server to unsubscribe with the AIMLE server.
Pre-conditions:
1. The AIMLE client or VAL server has subscribed for ML model retrieval with the AIMLE Server.
Figure 8.2.2.3.5-1: ML model retrieval unsubscribe
1. The requestor (e.g., AIMLE client or VAL server) sends a ML model retrieval unsubscribe request to the AIMLE server. The request includes the requestor identifier, security credentials and the subscription identifier.
2. Upon receiving the request from the requestor, the AIMLE server validates if the requestor is authorized for the request. If the requestor is authorized, the AIMLE server cancels the subscription.
3. The AIMLE server sends a ML model retrieval unsubscribe response to the requestor. If the AIMLE server has canceled the subscription, the response includes an indication of success. If the AIMLE server has not canceled the subscription, the response includes an indication of failure and may include a reason for failure.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.3.1 ML model retrieval request
| Table 8.2.3.1-1 describes information elements for the ML model retrieval request from the AIMLE client or VAL server to the AIMLE server.
Table 8.2.3.1-1: ML model retrieval request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., AIMLE client or VAL server).
Security credentials
M
The security credentials of the requestor.
Filtering criteria
O
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.2.3.2 ML model retrieval response
| Table 8.2.3.2-1 describes information elements for the ML model retrieval response from the AIMLE server.
Table 8.2.3.2-1: ML model retrieval response
Information element
Status
Description
Successful response
O
(NOTE 2)
Indicates that the ML model retrieval request was successful.
>List of ML models
M
List of retrieved ML models; the nested information elements are provided for each ML model in the list.
>> ML model identifier
M
The ML model identifier.
>> ML model retrieval endpoint (NOTE 1)
O
The endpoint (e.g., URL, URI, IP address) where the ML model file can be retrieved.
>> ML model (NOTE 1)
O
The ML model containing a retrieved ML model.
Failure response
O
(NOTE 2)
Indicates that the request has failed.
> Cause
O
The cause for the request failure.
NOTE 1: At least one of these information elements is needed.
NOTE 2: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.3.3 ML model retrieval subscribe request
| Table 8.2.3.3-1 describes information elements for the ML model retrieval subscription request from the AIMLE client or VAL server to the AIMLE server.
Table 8.2.3.3-1: ML model retrieval subscription request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., AIMLE client or VAL server).
Security credentials
M
The security credentials of the requestor.
Notification Target Address
M
Notification target address (e.g. URL) where the notifications should be sent.
Proposed expiration time
O
Proposed expiration time for the subscription.
Filtering criteria
O
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.2.3.4 ML model retrieval subscription response
| Table 8.2.3.4-1 describes information elements for the ML model retrieval subscription response from the AIMLE server.
Table 8.2.3.4-1: ML model retrieval subscription response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the ML model retrieval request was successful.
> Subscription ID
M
Subscription identifier corresponding to the subscription.
> Expiration time
O
Indicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time.
Failure response
O
(NOTE)
Indicates that the request has failed.
> Cause
O
The cause for the request failure.
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.3.5 ML model retrieval notification
| Table 8.2.3.5-1 describes information elements for the ML model retrieval subscription response from the AIMLE server.
Table 8.2.3.5-1: ML model retrieval notification
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
List of ML models
O
List of retrieved ML models; the nested information elements are provided for each ML model in the list.
> ML model identifier
O
The ML model identifier.
> ML model retrieval endpoint (NOTE)
O
The endpoint (e.g., URL, URI, IP address) where the ML model file can be retrieved.
> ML model (NOTE)
O
The ML model containing a retrieved ML model.
NOTE: At least one of these elements is needed.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.3.6 ML model retrieval subscription update request
| Table 8.2.3.6-1 describes information elements for the ML model retrieval subscription update request from the AIMLE client or VAL server to the AIMLE server.
Table 8.2.3.6-1: ML model retrieval subscription update request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., AIMLE client or VAL server).
Security credentials
M
The security credentials of the requestor.
Subscription ID
M
Subscription identifier corresponding to the subscription to be updated.
Notification Target Address
O
Notification target address (e.g. URL, URI, IP address) where the notifications should be sent.
Proposed expiration time
O
Proposed expiration time for the subscription.
Filtering criteria
O
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.2.3.7 ML model retrieval subscription update response
| Table 8.2.3.7-1 describes information elements for the ML model retrieval subscription update response from the AIMLE server.
Table 8.2.3.7-1: ML model retrieval subscription update response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the ML model retrieval subscription update request was successful.
> Expiration time
O
Indicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time.
Failure response
O
(NOTE)
Indicates that the request has failed.
> Cause
O
The cause for the request failure.
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.3.8 ML model retrieval unsubscribe request
| Table 8.2.3.8-1 describes information elements for the ML model retrieval unsubscribe request from the AIMLE client or VAL server to the AIMLE server.
Table 8.2.3.8-1: ML model retrieval unsubscribe request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., AIMLE client or VAL server).
Security credentials
M
The security credentials of the requestor.
Subscription ID
M
Subscription identifier corresponding to the subscription to be unsubscribed.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.2.3.9 ML model retrieval unsubscribe response
| Table 8.2.3.9-1 describes information elements for the ML model retrieval unsubscribe response from the AIMLE server.
Table 8.2.3.9-1: ML model retrieval unsubscribe response
Information element
Status
Description
Successful response
O
(NOTE)
Indicates that the ML model retrieval unsubscribe request was successful.
Failure response
O
(NOTE)
Indicates that the request has failed.
> Cause
O
The cause for the request failure.
NOTE: One of the IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.3 ML model training
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.3.1 General
| This clause describes the procedure for supporting the ML model training by the AIMLE server. The VAL server requests the AIMLE server for the ML model training. VAL server requests the AIMLE server to train a ML model by specifying the type of learning, details about the ML model to be trained or requirements to select a ML model for training and criteria for selecting the members who can participate in the ML model training.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.3.2 Procedure for ML model training
| Figure 8.3.2-1 illustrates the procedure for AIMLE server to support ML model training based on the request from the VAL server.
Figure 8.3.2-1: ML model training
1. The VAL server sends an ML model training request to AIMLE server, requesting to assist in its ML model training. This request consists of ML model information or ML model requirement information, etc.
2. The AIMLE server checks whether the VAL server is authorized to perform the ML model training request. If no model information is provided but only the model requirement information is provided in step 1, the AIMLE server identifies and selects the appropriate ML model for training based on the ML model requirement information using the procedure as specified in clause 8.11.3.
3. If the VAL server is authorized, AIMLE server returns the success response, otherwise a failure response indication the reason for failure.
4. The AIMLE server notifies the VAL server to update the list FL/ML clients selected or de-selected for the ML model training or to share the training output or any errors during the training process.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.3.3 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.3.3.1 ML model training request
| Table 8.3.3.1-1 describes the information flow from the VAL server to the AIMLE server for requesting the ML model training.
Table 8.3.3.1-1: ML model training request
Information element
Status
Description
Requestor identity
M
Identity of the VAL server performing the request.
Training type
M
Identifies whether the VFL or HFL training to be performed.
List of member clients
O
(NOTE 1)
List of member clients or AIMLE client set identifier to be utilized for training the ML model.
Member selection criteria
O
(NOTE 1)
Identifies the criteria that needs to be continuously monitored for selecting the member clients (e.g., AIMLE clients in a particular location, member availability duration, new member clients registering with the required capabilities).
Number of required AIML clients
O
Indicates the requested number of AIML clients to be selected based on member selection criteria.
ML model information
O
(NOTE 2)
Identifies the ML model that has to be distributed to the selected member clients for training. This information consists of the model identifier, address (e.g., a URL or an FQDN) of the ML model file or address of the model repository where the ML model resides
ML model requirement information
O
(NOTE 2)
Identifies the requirement for selecting a model to be trained and this information contains the filtering criteria for selecting the model as specified in Table 8.11.4.1-2.
Dataset identifiers
M
Identifier of dataset used to HFL or VFL training. For VFL training, multiple dataset identifiers is specified for different data domains.
Number of data samples
O
The number of data samples required for a round of HFL or VFL training.
Operational schedule
O
A schedule for when training is to occur.
VFL specific parameters
O
(NOTE 3)
Parameters specific to VFL training
> Dataset common features
O
(NOTE 3)
A list of one or more common features is specify for VFL training. Common features can be UE identifiers, AIMLE client identifiers, group identifier, VAL service identifier, area of interest, and VAL service area.
> Data domain feature ID lists
O
(NOTE 3)
List of features for each data domain(s) of the datasets at the UE for VFL training.
> Feature alignment information
O
Information provided to align features from dataset of different domains for VFL training. Alignment information is also provided for data domain features with ground truth data.
> Data labels
O
Ground truth data provided for VFL training.
Training objective
O
Identifies the termination condition for the ML model training. Table 8.3.3.1-2 describes the information related to training objective.
Members update notification
O
Indicates whether requestor needs to be notified whenever there is update related to new member clients selected or de-selected.
Notification Target Address
O
Notification target address (e.g. URL) where the notifications should be sent.
NOTE 1: At least one of these IE shall be present.
NOTE 2: At least one of these IE shall be present.
NOTE 3: These IE shall be present for VFL training.
Table 8.3.3.1-2: ML model training objective
Information element
Status
Description
Objective Type
M
Identifies the metric to be optimized by the ML model (e.g. accuracy.)
Target Value
O
Identifies the threshold to be reached for the objective type.
Early stopping Criteria
O
Identifies the metric to be used for early stopping.
Maximum number of Epochs
O
Identifies the maximum number of training epochs
Acceptable training errors
O
Maximum error acceptable with training.
Inference Latency
O
Inference latency requirements for the trained model.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.3.3.2 ML model training response
| Table 8.3.3.2-1 describes the information flow of ML model training response from the AIMLE server to the VAL server.
Table 8.3.3.2-1: ML model training response
Information element
Status
Description
Success response
O
(NOTE)
Indicates that the ML model training request was successful.
> ML model training identifier
M
An identifier for the ML model training request.
> ML model identifier
O
Identifies the ML model selected by AIMLE server for training.
Failure response
O
(NOTE)
Indicates that the ML model training request was failure.
> Cause
M
Reason for the failure.
NOTE: Only one of these information elements shall be present
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.3.3.3 ML model training notification
| Table 8.3.3.3-1 describes the information flow of ML model training notification from the AIMLE server to the VAL server.
Table 8.3.3.3-1: ML model training notification
Information element
Status
Description
ML model training identifier
M
An identifier for the ML model training request the notification is for.
List of AIMLE clients
O
(NOTE)
Indicates the list of AIMLE clients selected or de-selected for the ML model training.
Training output
O
(NOTE)
Output of training, e.g., ML model parameters for the training.
Percentage completion
O
Indicates a completion percentage for the training.
Errors list
O
(NOTE)
A list of errors, if any, encountered during training process.
NOTE: At least one of these IEs shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4 Support for FL member registration
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.1 General
| This clause provides the procedures for the registration, registration update, and deregistration of candidate FL members in the ML repository which serves as service registry for the FL members undertaking a task related to the ML model lifecycle, such as ML model local training. Candidate FL members can be application layer entities at the server side (e.g., VAL server, AIMLE server), which can potentially be selected as FL clients or FL server for a particular ASP /vertical requirement, or at the client side (e.g., AIMLE client), which can potentially be selected as FL clients. If VAL server or the AIMLE client is the candidate FL member, it registers indirectly via AIMLE server to the ML repository.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.2 Procedure on FL member registration information storage
| Figure 8.4.2-1 illustrates the procedure where the registration of a candidate FL member happens via the ML repository, serving as AIML service registry.
Figure 8.4.2-1: Procedure for registration on FL member registration information storage
0. The candidate FL member sends an FL member registration request to AIMLE server and gets authorization checking.
The procedure for AIMLE client to register to AIMLE server as FL member is introduced in clause 8.7.2.2.
1. AIMLE server sends an FL member registration information storage request to the ML repository which acts as the AIML service information registry.
2. The ML repository validates the received request and generates the identity and other security related information for all the FL members listed in the request.
3. The ML repository sends the generated information in the FL member registration information storage response message to the AIMLE server.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.3 Procedure on FL member registration information storage update
| Figure 8.4.3-1 illustrates the procedure where the registration update of a candidate FL member happens via the ML repository.
Figure 8.4.3-1: Procedure for registration information update
0. The candidate FL member (e.g., VAL server or AIMLE client, or another AIMLE server) sends an FL member registration update request to AIMLE server and gets authorization.
The procedure for AIMLE client to update registration to AIMLE server as FL member is introduced in clause 8.7.2.3.
1. The candidate FL member (VAL server via AIMLE server or AIMLE Server) sends an FL member registration update request to the ML repository acting as AIML service registry for updating the registration of the FL member.
2. The ML repository validates the received update request and generates the identity and other security related information for the FL member.
3. The ML repository sends the generated information in the FL member registration update response message to the candidate FL member.
The procedure for AIMLE client to update its registration to ML repository as FL member is introduced in clause 8.7.2.3.
8.4.3a Procedure on registration information storage update for FL member deregistration
Figure 8.4.3a-1 illustrates the procedure registration information storage update where the deregistration of a candidate registered FL member happens.
The deregistration may be triggered by the VAL server or AIMLE server in case of an expected or predicted unavailability of the candidate FL member e.g. due to load / energy, access limitation in different VAL service area based on the vertical/ASP requirement.
Such deregistration is provided by the AIMLE server e.g. after offboarding of the VAL server from the SEAL platform, or upon termination of the AIMLE/VAL service (FL task), and then registration information stored at ML repository should be updated accordingly.
Figure 8.4.3a-1: Procedure for due to deregistration information storage update for FL member
0. The candidate FL member (e.g., VAL server or AIMLE client, or another AIMLE server) sends an FL member de-registration request to AIMLE server and gets authorization.
The procedure for AIMLE client to deregister to AIMLE server as FL member is introduced in clause 8.7.2.4.
1. The candidate registered FL member (e.g., VAL server via AIMLE server or AIMLE server) sends an FL member deregistration request to the ML repository for registering to the ML repository which acts as the AIML service registry.
2. The ML repository validates the received request for all the registered FL members listed in the deregistration request.
3. The ML repository sends the generated information in the FL member deregistration response message to the candidate registered FL member.
The procedure for AIMLE client to deregister to ML repository as FL member is introduced in clause 8.7.2.4.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.4 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.4.1 General
| The following information flows are specified for supporting the FL member registration information storage and registration information update based on clause 8.4.2 and clause 8.4.3.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.4.2 FL member registration information storage request
| Table 8.4.4.2-1 describes information elements for the FL member registration information storage request AIMLE server to the ML repository/registry.
Table 8.4.4.2-1: FL member registration information storage request
Information element
Status
Description
Security information
M
Information for ML repository to validate the registration information storage request.
FL member list
M
The information of registered FL members, which are authorized as candidate FL member
>FL member ID
M
(NOTE)
The identifier of the candidate FL member. This can be the VAL server ID, the EAS ID, the AIMLE server ID, AIMLE client ID based on which entity is the candidate FL member.
>FL member supported AI/ML role
M
(NOTE)
The supported AI/ML role of FL member which can be used as FL server or FL client.
>FL member capabilities
O
(NOTE)
FL member capability information (e.g., ML application type, allowed resource usage level).
>FL member velocity
O
Indicates the FL member velocity (e.g., mobile or static).
>FL member Location information
O
Indicates the location information of the UE (e.g., Cell Identity, Tracking Area Identity, GPS Coordinates or civic addresses).
>FL member Availability schedule
O
(NOTE)
Availability schedule of the FL member for a certain FL member.
>Supported ML model ID list
O
The list of ML model IDs for which the FL member can be used.
>Area of Interest
O
The area of interest (i.e., location co-ordinates) for which the registration applies.
>Time validity
O
The time validity for the registration of the FL member.
NOTE: At least one of these shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.4.3 FL member registration information storage response
| Table 8.4.4.3-1 describes information elements for the FL member registration information storage response to AIMLE server from the ML repository/registry.
Table 8.4.4.3-1: FL member registration response
Information element
Status
Description
Result
M
The result of the registration request (positive or negative acknowledgement).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.4.4 FL member registration information storage update request
| Table 8.4.4.4-1 describes information elements for the FL member registration information update request from AIMLE server to the ML repository/registry.
Table 8.4.4.4-1: FL member registration information update request
Information element
Status
Description
Security information
M
Information for ML repository to validate the registration information update request
FL member list to be updated
M
The information FL member to be deleted due to deregistration or to be added due to registration update
>FL member ID
M
The identifier of the candidate FL member for which the update applies. This can be the VAL server ID, the EAS ID, the AIMLE server ID based on which entity is the candidate FL member.
>Updated registration parameters
O
The updates of the registration parameters if registration information is updated.
>> FL member supported AI/ML role
O
(see NOTE)
The updated supported AI/ML role of FL member which can be FL server, FL client.
>> FL member Availability schedule
O
(see NOTE)
Updated Availability schedule of the FL member.
>> supported ML model ID list
O
(see NOTE)
The updated list of ML model IDs for which the FL member can be used
>> area of interest
O
(see NOTE)
The updated area of interest for the registration update.
>> time validity
O
(see NOTE)
The update time validity for the FL member registration update.
>de-registration parameter
O
The indication of FL member ID being deregistered.
NOTE: At least one of these information elements shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.4.5 FL member registration update response
| Table 8.4.4.5-1 describes information elements for the FL member registration information update response to AIMLE server from the ML repository/registry.
Table 8.4.4.5-1: FL member registration update response
Information element
Status
Description
Result
M
The result of the registration update request (positive or negative acknowledgement).
Registration ID
O
The generated ID for the new registration based on the update (if needed).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.4.6 FL member deregistration request
| Table 8.4.4.6-1 describes information elements for the FL member deregistration request from the candidate FL member (VAL server, AIMLE server) to the ML repository/registry.
Table 8.4.4.6-1: FL member deregistration request
Information element
Status
Description
Registration ID
M
The identity of the registered FL member
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.4.4.7 FL member deregistration response
| Table 8.4.4.7-1 describes information elements for the FL member deregistration response to the candidate registered FL member (VAL server, AIMLE server) from the ML repository/registry.
Table 8.4.4.7-1: FL member deregistration response
Information element
Status
Description
Result
M
The result of the deregistration request (positive or negative acknowledgement).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5 Support for FL events subscription and notification
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.1 General
| This clause consists of the following procedures 1) the subscription for the FL related events in clause 8.5.2 and 2) the event notification procedure in clause 8.5.3.
This capability targets the enhancements to a global ML repository acting as AIML service registry which monitors the status and changes to the availability and capabilities of the FL members. The subscriber can be the AIMLE server or VAL server which requires to get notified on the FL member availability, since this information is vital for enabling the subscriber to perform the FL-related AIML operations (e.g. AIMLE server selecting FL members for a certain FL task). If VAL server is the subscriber, it registers indirectly via AIMLE server for FL-related events.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.2 Procedure on subscription for FL related events
| This procedure, as illustrated in Figure 8.5.2-1, describes the subscription for events related to FL member availability.
Pre-conditions:
1. The AIMLE server has the authorization to subscribe for the FL-related events (events described in clause 8.5.4).
Figure 8.5.2-1: Procedure for FL-related event subscription
1. The subscriber (AIMLE server or VAL server (via AIMLE server)) sends an FL-related event subscription request to the ML repository to receive notification of FL related events and in particular the availability of FL member for a target area and time.
2. Upon receiving the event subscription request from the AIMLE server, the ML repository checks for the relevant authorization for the event subscription. If the authorization is successful, the ML repository stores the subscription information.
3. The ML repository sends an FL-related event subscription response to the subscriber indicating successful operation.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.3 Procedure on FL related event notification
| This procedure describes the event notification procedure for the FL member availability. This can be triggered based on a change at the availability or capabilities of the candidate or selected FL members.
Pre-conditions:
1. The subscription procedure in clause 8.5.2 was performed by the AIMLE server or VAL server (via AIMLE server).
2. The FL member has registered its capabilities or availability to the ML repository based on the support for FL registration capability.
Figure 8.5.3-1: Procedure for FL-related event notifications
1. The ML repository detects a change related to the availability of an FL member and generates events to be consumed by the AIMLE server, based on the notification, or based on a received updated registration from FL member, who has already registered at the ML repository.
2. For the generated event, the ML repository retrieves the list of corresponding subscriptions.
3. The ML repository sends FL-related event notification to all entities (e.g., AIMLE servers) that have subscribed for the FL-related event matching the criteria. If a notification reception information is available as part of the FL-related event subscription, then the notification reception information is used by the ML repository to send event notifications to the corresponding AIMLE servers.
4. The notified subscriber (s) sends an event notification acknowledgement to the ML repository.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.4 Definition of FL-related Events
| The definition of the FL related events is provided in Table 8.5.4-1.
Table 8.5.4-1: Definition of FL related events
Events
Events Description
Availability changes of FL member
The event type relates to the availability change of a FL member. Such availability change can be an indication of availability or unavailability for a given service area, or for a given ML model ID/profile.
FL model information
Information such as accuracy, time schedule and latency for the FL training. Latency is considering the target latency, i.e., when the FL model training shall be completed.
FL member load information
The event type relates to the monitoring of the computational load for the requested FL member. Such load can be the estimated (based on measurements) or expected/predicted based on the tasks that the FL member undertakes. This event may be triggered on-demand or can be monitored periodically.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.5 Information flows
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.5.1 General
| The following information flows are specified for supporting the FL events subscription and events notification based on clause 8.5.2 and clause 8.5.3.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.5.2 FL-related event subscription request
| Table 8.5.5.2-1 describes information elements for FL-related event subscription request from the subscriber (AIMLE server, or VAL server (via AIMLE server)) to the ML repository.
Table 8.5.5.2-1: FL-related event subscription request
Information element
Status
Description
Requestor Identifier
M
The identifier to determine the identity of the requestor entity. This can be either the AIMLE server ID, or AIMLE server ID and VAL server ID.
Security Credentials
M
The security credentials of the requestor.
Time of validity
M
The time validity for the subscription.
ML model information
M
Information of the ML model for, specified in Table 8.11.4.1-2, which the subscription is needed.
FL member information
M
Information on the FL member (candidate or selected).
>FL member type
O
(NOTE)
The type of FL member which can be an FL server or FL client.
>FL member ID
O
(NOTE)
The ID of the entity serving as FL member. This can be used for events where the FL member is known and possibly selected, and the availability needs to be checked.
Event Information
M
Information on the FL-related event.
> Event ID
O
The identity of the FL-related event (if known by the requestor).
> Event type
M
The event type requested, based on the Definition of FL related events (shown in Table 8.5.4-1).
Notification endpoint
M
The information of the endpoint for receiving the notifications for the event.
NOTE: At least one of these shall be present.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.5.3 FL-related event subscription response
| Table 8.5.5.3-1 describes information elements for the FL-related event subscription response to the subscriber (e.g. AIMLE server or VAL server (via AIMLE server)) from the ML repository.
Table 8.5.5.3-1: FL-related event subscription response
Information element
Status
Description
Result
M
Indicates the success or failure of the event subscription operation.
Subscription Identifier
M
The unique identifier for the event subscription.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.5.4 FL related event notification
| Table 8.5.5.4-1 describes information elements for the FL-related event notification from the ML repository to the requestor (e.g., AIMLE server).
Table 8.5.5.4-1: FL-related event notification
Information element
Status
Description
Subscription identifier
M
The unique identifier of the event subscription.
Event identifier
M
The unique identifier for the event. For the definition of events, refer to the Table 8.5.4-1 with the list of FL related events.
Event related information
M
The event related information (e.g., time at which the event originated or is planned to be executed, location of event).
Event content
M
The content of the event information.
> List of FL member ID /address
O
The list of the FL members and their addresses.
>> FL member enter / leave
O
The indication of an FL member entering or leaving the available list.
>> FL member updated capability
O
The update of capabilities for the FL members.
>> Time availability of FL member
O
The time period for which the FL member is available.
>> Area of interest
O
The area of interest or exact or predicted location for which the event applies.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.5.5.5 FL-related event notification acknowledgement
| Table 8.5.5.5-1 describes information elements for the FL-related event notification acknowledgement from the AIMLE server to the ML repository.
Table 8.5.5.5-1: FL-related event notification acknowledgement
Information element
Status
Description
Result
M
The positive or negative acknowledgement of the notification reception.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 8.6 Support AI/ML Task Transfer
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.