Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.436  Word version:  19.2.0

Top   Top   Up   Prev   Next
0…   5…   6…   8…   8.3…   8.4…   8.5…   8.6…   8.7…   8.8…   8.9…   8.10…   8.11…   8.12…   8.13…   8.14…   8.15…   8.16…   9…   9.3…   9.4…   A…

 

8.16  Procedure for Application Layer AI/ML Member Capability Analytics |R19|p. 93

8.16.1  Generalp. 93

This clause describes two procedures (covering both subscribe-notify and request-response models in clause 8.16.2.1 and 8.16.2.2 respectively) for supporting application layer AI/ML member capability analytics, where the application layer AI/ML member capability analytics are performed based on data collected from the Data Producer (e.g. ADAE client) and A-ADRF.
Up

8.16.2  Procedurep. 94

8.16.2.1  Subscribe-notify modelp. 94

Reproduction of 3GPP TS 23.436, Fig. 8.16.2.1-1: ADAES support for application layer AI/ML Member capability analytics
Up
Step 1.
The analytics consumer (e.g. VAL Server, AIMLE Server) sends application layer AI/ML member capability analytics subscription request to ADAE server. For analytics subscription request, the request contains message as defined in Table 8.16.3.2-1.
Step 2.
Upon receiving the event subscription request from the consumer, the ADAE server checks for the relevant authorization for the event subscription. If the authorization is successful, the ADAE server stores the request information. The ADAE server sends a service API event subscription response indicating successful subscription.
Step 3.
The ADAES maps the analytics event ID to a list of data collection event identifiers, and a list of data producer IDs. Such mapping may be preconfigured by OAM or may be determined by ADAES based on the analytics event type/vertical type and/or data producer profile.
Step 4.
The ADAE server sends a data collection subscription request to the Data Producers (ADAE client) or a data collection request to the Data Producers (A-ADRF) with the respective Data Collection Event ID and the requirement for data collection. Data collection at the UE(s) reuses the mechanism defined in TS 26.531.
Step 5.
The Data Producers (ADAE client) send data collection subscription response as a positive or negative acknowledgement to the ADAE server.
Step 6.
The ADAE server based on data collection subscription receive data on the application layer AI/ML Member capability based on the data collection event ID from ADAE client.
Step 7.
The ADAE server based on data collection request receive data/analytics on the application layer AI/ML Member capability based on the data/analytics collection event ID from A-ADRF.
Step 8.
The ADAES performs analytics relevant operations to generate the analytics based on the data/analytics received from the ADAEC.
Step 9.
The ADAES sends application layer AI/ML member capability analytics notifications to the consumer with the required application layer AI/ML Member capability analytics.
Up

8.16.2.2  Request-response modelp. 95

Pre-conditions:
  • ADAE server already have the analytics data derived from steps 3-8 in the procedure introduced in clause 8.16.2.1.
Reproduction of 3GPP TS 23.436, Fig. 8.16.2.2-1: ADAES support for application layer AI/ML Member capability analytics
Up
Step 1.
The analytics consumer (e.g. VAL Server, AIMLE Server) sends a get application layer AI/ML member capability analytics request message to the ADAE server to receive analytics data for application layer AI/ML Member capability. The request contains message as defined in Table 8.16.3.8-1.
Step 2.
Upon receiving the request, the ADAE server authenticates and authorizes the analytics consumer.
Step 3.
If the analytics consumer is authorized, the ADAE server may get the analytics by performing step 3 to 8 of clause 8.16.2.1.
Step 4.
The ADAE server sends a get application layer AI/ML member capability analytics response message including the analytics data (statistical and/or predictive) of the application layer AI/ML Member capability.
Up

8.16.3  Information flowsp. 95

8.16.3.1  Generalp. 95

The following information flows are specified for application layer AI/ML Member capability analytics based on clause 8.16.2.

8.16.3.2  Application Layer AI/ML Member capability analytics subscription requestp. 96

Table 8.16.3.2-1 describes the information flow from the consumer (e.g. VAL server, AIMLE server) as a request or update request for the application layer AI/ML Member capability analytics.
Information element Status Description
Requestor IDM
(NOTE)
The identifier of the consumer.
Analytics IDM
(NOTE)
The identifier of the analytics event. This ID can be for example "Application layer AI/ML Member capability analytics".
Analytics typeMThe type of analytics for the event, e.g. statistics or predictions.
List of VAL users or AI/ML Member IDsMThe VAL users or AI/ML Member (s) identifiers for which the data/analytics apply.
VAL service IDOThe identifier of the VAL service which is associated with application layer AI/ML Member capability.
Application layer AI/ML Member capability attributesMThe application layer AI/ML Member capability attributes to be analyzed at the ADAE client, e.g. communication capability (e.g. maximum/minimum number of supported active connections).
Reporting requirementsOIt describes the requirements for analytics reporting. This requirement may include e.g. the type and frequency of reporting (periodic or event triggered), the reporting periodicity in case of periodic, and reporting thresholds.
Area of InterestOThe geographical or service area for which the subscription request applies.
Preferred confidence levelOThe level of accuracy for the analytics service (in case of prediction).
Time validityOThe time validity of the subscription request.
NOTE:
This information element shall not be updated.
Up

8.16.3.3  Application Layer AI/ML Member capability analytics subscription responsep. 96

Table 8.16.3.3-1 describes the information elements for the application layer AI/ML Member capability analytics subscription response from the ADAE server to the consumer.
Information element Status Description
ResultMThe result of the analytics subscription request (positive or negative acknowledgement).
Up

8.16.3.4  Application layer AI/ML Member capability analytics notificationp. 96

Table 8.16.3.4-1 describes the information flow from the ADAES to the consumer (e.g. VAL Server, AIMLE Server) as a response for the application layer AI/ML Member capability analytics.
Information element Status Description
Analytics IDM The identifier of the analytics event. This ID can be for example "Application layer AI/ML Member capability analytics".
List of VAL users or AI/ML Member IDsMThe VAL users or AI/ML Member(s) identifiers for which the data/analytics apply.
> VAL user or AI/ML Member ID in the listMThe VAL user or AI/ML Member identifier for which the data/analytics apply.
>> Analytics OutputMThe reported analytics for the application layer AI/ML Member capability. The predictive or statistical parameter on, e.g. communication capability (e.g. maximum/minimum number of supported active connections).
>> Confidence levelOFor predictive analytics, the achieved confidence level can be provided.
Up

8.16.3.5  Application Layer AI/ML Member capability data collection subscription requestp. 97

Table 8.16.3.5-1 describes information elements for the application layer AI/ML Member capability data collection subscription request from the ADAE server to the Data Producer at the ADAE client or the A-ADRF.
Information element Status Description
Requestor IDMThe identifier of the consumer.
Data Collection Event IDMThe identifier of the data collection event.
Data collection requirementsOThe requirements for data collection, including the format of data, frequency of reporting, level of abstraction of data, level of accuracy of data.
Analytics IDO The identifier of the analytics event, for which the data collection is needed. This ID can be for example "Application layer AI/ML Member capability analytics".
List of Data Producer IDsOIn case when this request is performed via A-DCCF, then the list of Data Producer IDs is needed.
Target data producer profile criteriaOCharacteristics of the data producers to be used.
List of VAL users or AI/ML Member IDsMThe VAL users or AI/ML Member (s) identifiers for which the data/analytics apply.
VAL service ID listOThe identifier(s) of the VAL service(s) which is associated with application layer AI/ML Member capability.
Application layer AI/ML Member capability attributesMThe application layer AI/ML Member capability attributes to be analyzed at the ADAE client.
Area of InterestOThe geographical or service area for which the requirement request applies.
Time validityOThe time validity of the request.
Up

8.16.3.6  Application Layer AI/ML Member capability data collection subscription responsep. 97

Table 8.16.3.6-1 describes information elements for the Data collection subscription response from the application layer AI/ML Member capability data Producer at the ADAE client or the A-DCCF to the ADAE server.
Information element Status Description
ResultMThe result of the application layer AI/ML Member capability data collection subscription request (positive or negative acknowledgement).
Up

8.16.3.7  Data Notificationp. 98

Table 8.16.3.7-1 describes information elements for the Data Notification from the Data Producer to the ADAE server.
Information element Status Description
Data Collection Event IDMThe identifier of the data collection event.
Data Producer IDMThe identity of Data Producer.
Analytics IDO The identifier of the analytics event. This ID can be for example "Application layer AI/ML Member capability analytics".
Data TypeMThe type of reported data samples which can be network data, application data, edge data, or different granularities / abstraction of data (e.g. real time, non-real time). This also indicates whether data are offline (from A-ADRF or not).
Data OutputMThe reported data, which can be inform of measurements or offline/historical data on the requested parameter based on subscription.
Up

8.16.3.8  Get analytics data requestp. 98

Table 8.16.3.8-1 describes information elements for the Get application layer AI/ML Member capability analytics request from the analytics consumer to the ADAE server.
Information element Status Description
Requestor IDMThe identifier of the consumer.
Analytics IDM The identifier of the analytics event. The identifier of the analytics event. This ID can be for example "Application layer AI/ML Member capability analytics".
Analytics typeMThe type of analytics, e.g. statistics or predictions.
List of VAL users or AI/ML Member IDsMThe VAL users or AI/ML Member (s) identifiers for which the data/analytics apply.
VAL service IDOThe identifier of the VAL service which is associated with application layer AI/ML Member capability.
Application layer AI/ML Member capability attributesMThe application layer AI/ML Member capability attributes to be analyzed at the ADAE client, e.g. communication capability (e.g. maximum/minimum number of supported active connections).
Preferred confidence levelOThe level of accuracy for the analytics service (in case of prediction).
Time windowOThe start and end time requirements on the generation of the analytics data to be collected.
Time validityOThe time validity of the request.
Up

8.16.3.9  Get analytics data responsep. 99

Table 8.16.3.9-1 describes information elements for the Get application layer AI/ML Member capability analytics response from the ADAE server to the consumer.
Information element Status Description
ResultMThe result of the analytics data request (positive or negative acknowledgement).
Analytics IDO The identifier of the analytics event. This ID can be for example "Application layer AI/ML Member capability analytics".
List of VAL users or AI/ML Member IDsMThe VAL users or AI/ML Member(s) identifiers for which the data/analytics apply.
> VAL user or AI/ML Member ID in the listMThe VAL user or AI/ML Member identifier for which the data/analytics apply.
>> Analytics OutputMThe predictive or statistical parameter on, e.g. communication capability (e.g. maximum/minimum number of supported active connections).
>> Confidence levelOFor predictive analytics, the achieved confidence level can be provided.
>> TimestampOTimestamp of the collected analytics data.
Up

Up   Top   ToC