hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.2 Procedure | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.2.1 Notification based data storage | Figure 8.10.2.1-1 illustrates the procedure for consumer to request A-ADRF to initiate request for data or analytics to store.
Pre-conditions:
1. Analytics or data consumer requests ADAE server, A-DCCF or data sources to store analytics or data to A-ADRF.
2. ADAE server, A-DCCF or A-ADRF are configured with default operator storage policies.
Figure 8.10.2.1-1: Support for data storage to A-ADRF
1. The consumer (A-DCCF or ADAE server) determines that data and/or analytics needs to be stored to the A-ADRF, or requests the A-ADRF subscribes to Data Producer for receiving notifications. The determination may be made based on configuration or information supplied by the data or analytics. As specified in Table 8.10.3.2-1, the request to the A-ADRF specifies the data and/or analytics to which the A-ADRF will subscribe. The request includes identity of the consumer, security credential(s) for authorization and verification, Storage Handling information (e.g. a lifetime for how long the data or analytics should be stored, indicate that a notification alerting the consumer be sent prior to data deletion from the A-ADRF).
2. The A-ADRF may, based on implementation, determine whether the same data and/or analytics is already stored or being stored, based on the information sent in step 1 by the consumer. Based on Storage Handling information, the A-ADRF determines the Storage Approach (e.g. lifetime for storing data and whether consumer is notified prior to data deletion).
3. If the data and/or analytics is already stored and/or being stored in the A-ADRF, the A-ADRF sends data storage subscription response message to the consumer indicating that data and/or analytics is stored. As specified in Table 8.10.3.3-1, the A-ADRF includes the Storage Approach if determined in step 2.
4. The A-ADRF subscribes to the data producer (e.g. A-DCCF, ADAE server) to receive notifications with data or analytics, providing its notification endpoint address and a notification correlation ID.
5. The data producer sends data or analytics notifications containing the notification correlation ID provided by the A-ADRF to notification endpoint address. The analytics or data notifications shall contain timestamp. The ADRF stores the notifications. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.2.2 Direct data storage | Figure 8.10.2.2-1 illustrates the procedure for the consumer to request A-ADRF for data or analytics storage.
Pre-conditions:
1. ADAE server or A-DCCF has data or analytics need to store to A-ADRF.
2. ADAE server, A-DCCF or A-ADRF are configured with default operator storage policies.
Figure 8.10.2.2-1: Support for data storage to A-ADRF
1. The consumer (e.g. ADAE server, A-DCCF) sends data storage request to the A-ADRF for storing data and/or analytics. The request message includes identity of the consumer, security credential(s) for authorization and verification, collected data with timestamp and/or analytics with timestamp, Storage Handling information (e.g. a lifetime for how long the data or analytics should be stored, indicate that a notification alerting the consumer be sent prior to data deletion from the A-ADRF) , as specified in Table 8.10.3.4-1.
2. Based on Storage Handling information (if available), the A-ADRF determines the Storage Approach (e.g. lifetime for storing data and whether consumer is notified prior to data deletion).
3. The A-ADRF stores the data and/or analytics sent by the consumer. The A-ADRF may, based on implementation, determine whether the same data and/or analytics is already stored or being stored based on the information sent in step 1 by the consumer and, if the data and/or analytics is already stored or being stored in the A-ADRF, the A-ADRF decides to not store again the data and/or analytics sent by the consumer.
4. The ADRF sends data storage response message to the consumer indicating that data and/or analytics is stored, whether the A-ADRF determined at step 3 that data or analytics is already stored and the Storage Approach, as specified in Table 8.10.3.5-1. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.3.1 General | The following information flows are specified for data storage based on 8.10.2. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.3.2 Data storage subscription request | Table 8.10.3.2-1 describes information elements for the data storage subscription request from the consumer (ADAE server, A-DCCF) to the A-ADRF.
Table 8.10.3.2-1: Data storage subscription request
Information element
Status
Description
Consumer ID
M
The identifier of the consumer (ADAE server, A-DCCF).
Data Producer ID
O
The identifier of the data producer (e.g. ADAE server, A-DCCF).
Analytics ID
O
The identifier of the analytics event. This IE shall be provided when Analytics Producer ID is present.
Analytics Type
O
The type of analytics for the event, which include category (e.g. statistics or predictive analytics), may include mode (e.g. offline or online) and indication on ML-enabled analytics. This IE shall be provided when Analytics Producer ID is present.
Target Data Producer Profile Criteria
O
Characteristics of the data producers to be used. This IE shall be provided when Data Producer ID is present.
Area of Interest
O
The geographical or service area for which the subscription request applies.
Time Validity
O
The time validity of the subscription request to the A-ADRF.
Storage Handling information
O
The information for storage handling.
> Lifetime
O
A lifetime for how long the data or analytics should be stored.
> Alert Indicator
O
To indicate that a notification alerting the consumer be sent prior to data deletion from the A-ADRF. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.3.3 Data storage subscription response | Table 8.10.3.3-1 describes information elements for the data storage subscription response from the A-ADRF to the consumer (ADAE server, A-DCCF).
Table 8.10.3.3-1: Data storage subscription response
Information element
Status
Description
Result
M
The result of the data storage subscription request (positive or negative acknowledgement).
Storage Approach
M
Represent the Storage Approach (e.g. lifetime for storing data, and whether consumer is notified prior to data deletion). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.3.4 Data storage request | Table 8.10.3.4-1 describes information elements for the data storage request from the consumer (ADAE server, A-DCCF) to the A-ADRF.
Table 8.10.3.4-1: Data storage request
Information element
Status
Description
Consumer ID
M
The identifier of the consumer (ADAE server, A-DCCF).
Data Type
M
To indicate the data type (e.g. data or analytics).
Content
M
The data or analytics to be stored.
Timestamp
M
The timestamp of the data or analytics.
Analytics ID
O
The identifier of the analytics event. This IE shall be provided if the Storage Type is analytics.
Analytics Type
O
The type of analytics, which include category (e.g. statistics or predictive analytics), may include mode (e.g. offline or online) and indication on ML-enabled analytics. This IE shall be provided if the Data Type is analytics.
Data Source Information
O
Information of the data source. This IE shall be provided if the Data Type is data.
Storage Handling information
O
The information for storage handling.
> Lifetime
O
A lifetime for how long the data or analytics should be stored.
> Alert Indicator
O
To indicate that a notification alerting the consumer be sent prior to data deletion from the A-ADRF. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.10.3.5 Data storage response | Table 8.10.3.5-1 describes information elements for the data storage response from the A-ADRF to the consumer (ADAE server, A-DCCF).
Table 8.10.3.5-1: Data storage response
Information element
Status
Description
Result
M
The result of the data storage request (positive or negative acknowledgement).
Storage Approach
M
Represent the Storage Approach (e.g. lifetime for storing data, and whether consumer is notified prior to data deletion). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11 Procedure for edge computing preparation analytics | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.1 General | This clause describes the procedure for edge computing preparation analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.2 Procedure | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.2.1 Subscribe-notify model | Figure 8.11.2.1-1 illustrates the procedure for edge computing preparation analytics.
Pre-conditions:
1. ADAES is connected to A-ADRF.
2. ADAES has subscribed to OAM for receiving management analytics.
Figure 8.11.2.1-1: ADAES support for edge computing preparation analytics subscribe-notify model
1. The analytics consumer (e.g., VAL server, ECS, EES) of the ADAE server analytics service sends an Edge computing preparation analytics subscription request to the ADAE server.
2. The ADAE server sends an Edge computing preparation analytics response as an ACK to the analytics consumer.
3. The ADAE server utilizes OAM (Network Resource Model) for edge deployment time information for EAS, EES, or ECS. The deployment time information is determined from the Process Monitor that specifies, for instance, NOT_STARTED, RUNNING and start and/or end time for these states as described in 3GPP TS 28.623 [15].
4. The ADAE server requests historical edge deployment time information of EAS, EES, and/or ECS from A-ADRF by sending an Edge computing preparation data request.
5. Based on the request, the ADAE server receives historical edge deployment time information of EAS, EES, and/or ECS by receiving an Edge computing preparation data response from A-ADRF.
6. The ADAE server collects EAS and/or EES instantiation triggering time and their registration time from the corresponding EES/ECS to determine when the instantiation request is sent to OAM and when EAS/EES service is ready.
7. The ADAE server abstracts or correlates the data/analytics from step 3-6. Based on the request in step 1, ADAES may also provide predictions for the edge deployment time.
8. The ADAE server sends an Edge computing preparation analytics notification to the analytics consumer, based on the request and the derived analytics in step 7. Such analytics indicate analytics and/or prediction of the edge deployment time for EAS, EES, and/or ECS. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.2.2 Request-response model | Figure 8.11.2.2-1 illustrates the procedure where the analytics consumer (e.g., VAL server, ECS, EES) requests edge computing preparation analytics using the request/response model.
Pre-conditions:
1. ADAES is connected to A-ADRF.
2. ADAES has subscribed to OAM for receiving management analytics.
Figure 8.11.2.2-1: ADAES support for edge computing preparation analytics request/response model
1. The analytics consumer (e.g., VAL server, ECS, EES) sends an Edge computing preparation analytics retrieval request to the ADAES.
2. Upon receiving the request, the ADAE server authenticates and authorizes the analytics consumer. If the analytics consumer is authorized, the ADAES performs step 3-7 of clause 8.11.2.1.
3. The ADAES sends an Edge computing preparation analytics retrieval response to the analytics consumer. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3.1 General | The following information flows are specified for edge computing preparation analytics based on 8.11.2. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3.2 Edge computing preparation analytics subscription request | Table 8.11.3.2-1 describes information elements for the edge computing preparation analytics subscription request from the analytics consumer (e.g., the VAL server, ECS, EES) to the ADAE server.
Table 8.11.3.2-1: Edge computing preparation analytics subscription request
Information element
Status
Description
Analytics Consumer ID
M
The identifier of the analytics consumer (VAL server, ECS etc.).
Analytics ID
O
The identifier of the analytics event. This ID can be for example "edge computing preparation analytics".
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions.
Reporting requirements
O
Requirements for analytics reporting. The requirements may include for example when the deployment information of the target (EAS, EES, ECS) is set to a specific state (such as "finished") or when the state is changed.
DNN/DNAI
O
DNN or DNAIs information of the EDN for which the subscription applies.
ECS provider ID
O
The identifier of the ECS provider
ECS endpoint
O
By providing the ECS endpoint, the consumer wants to subscribe to the EES instantiation info (EESs that will register in the ECS)
EES provider ID
O
The identifier of the EES provider
EES endpoint
O
By providing the EES endpoint, the consumer wants to subscribe to the EAS instantiation info (EASs that will register in the EES)
EAS provider ID
O
The identifier of the EAS provider
EAS ID
O
Identifies an EAS service.
EAS/EES/ECS resource requirements
O
The resources (i.e. available compute, graphical compute, memory, storage) needed for EAS/EES/ECS as described in Table 8.2.5-1 in 3GPP TS 23.558 [14].
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
Area of Interest
O
The geographical or service area for which the requirement request applies.
Time validity
O
The time validity of the subscription request. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3.3 Edge computing preparation analytics subscription response | Table 8.11.3.3-1 describes information elements for the edge computing analytics preparation analytics subscription response from the ADAE server to the analytics consumer.
Table 8.11.3.3-1: Edge computing preparation analytics subscription response
Information element
Status
Description
Result
M
The result of the analytics subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3.4 Edge computing preparation analytics notification | Table 8.11.3.4-1 describes information elements for the edge computing preparation analytics notification from the ADAE server to the analytics consumer.
Table 8.11.3.4-1: Edge computing preparation analytics notification
Information element
Status
Description
Analytics ID
O
The identifier of the analytics event.
Analytics Output
M
Represents the analytics output including prediction or statistics for the EAS/EES/ECS deployment time.
Confidence level
O
For predictive analytics, the achieved confidence level can be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3.5 Edge computing preparation data request | Table 8.11.3.5-1 describes information elements for the edge computing preparation data request from the ADAE server to the A-ADRF/EES/ECS.
Table 8.11.3.5-1: Edge computing preparation data request
Information element
Status
Description
ADAE server ID
M
The identifier of the ADAE server.
Analytics ID
M
The identifier of the analytics event.
Target ECS information
O (NOTE)
This identifier shows the target ECS information
Target EES information
O (NOTE)
This identifier shows the target EES information
Target EAS information
O (NOTE)
This identifier shows the target EAS information
Time validity
O
The time validity of the request.
NOTE: At least one of these shall be present for A-ADRF as receiver. Target ECS information is included for collecting EES instantiation triggering time and EES registration time. Target EES information is included for collecting EAS instantiation triggering time and EAS registration time. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3.6 Edge computing preparation data response | Table 8.11.3.6-1 describes information elements for the edge computing preparation data response from the A-ADRF/EES/ECS to the ADAE server.
Table 8.11.3.6-1: Edge computing preparation data response
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event.
Data Type
M
The 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).
Data Output
M
The reported data, which can be in form of measurements or offline/historical data on the requested parameter based on the request. The reported data includes historical ECS/EES/EAS deployment time information, EES/EAS registration data etc. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3.7 Edge computing preparation analytics retrieval request | Table 8.11.3.7-1 describes information elements for the Edge computing preparation analytics retrieval request from the analytics consumer to the ADAE server.
Table 8.11.3.7-1: Edge computing preparation analytics retrieval request
Information element
Status
Description
Analytics Consumer ID
M
The identifier of the analytics consumer (VAL server, ECS etc.).
Analytics ID
O
The identifier of the analytics event. This ID can be for example “edge computing preparation analytics”.
Analytics type
M
Whether analytics event is about prediction or statistics.
DNN/DNAI
O
DNN or DNAIs information of the EDN for which the subscription applies.
ECS provider ID
O
The identifier of the ECS provider
ECS endpoint
O
By providing the ECS endpoint, the consumer wants to subscribe to the EES instantiation info (EESs that will register in the ECS)
EES provider ID
O
The identifier of the EES provider
EES endpoint
O
By providing the EES endpoint, the consumer wants to subscribe to the EAS instantiation info (EASs that will register in the EES)
EAS provider ID
O
The identifier of the EAS provider
EAS ID
O
Identifies an EAS service.
EAS/EES/ECS resource requirements
O
The resources (i.e. available compute, graphical compute, memory, storage) needed for EAS/EES/ECS as described in Table 8.2.5-1 in 3GPP TS 23.558 [14].
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
Area of Interest
O
The geographical or service area for which the requirement request applies.
Time duration
O
Time duration since when analytics data is required. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.11.3.8 Edge computing preparation analytics retrieval response | Table 8.11.3.8-1 describes information elements for the Edge computing preparation analytics retrieval response from the ADAE server to the analytics consumer.
Table 8.11.3.8-1: Edge computing preparation analytics retrieval response
Information element
Status
Description
Results
M
The result of the analytics data request (positive or negative acknowledgement).
Analytics ID
O
The identifier of the analytics event.
Analytics Output
M
Represents the analytics output including prediction or statistics for the EAS/EES/ECS deployment time.
Confidence level
O
For predictive analytics, the achieved confidence level can be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12 Procedure for supporting data collection to A-DCCF | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.1 General | This clause describes two procedures (covering both subscribe-notify and request-response models in 8.12.2.1 and 8.12.2.2 respectively) for supporting data collection at A-DCCF. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.2 Procedure | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.2.1 Subscribe-notify model | Figure 8.12.2.1-1 illustrates the procedure for consumer to request A-DCCF to initiate subscription for data or analytics collection. The procedure may be utilized by the consumer to update the subscription for data or analytics collection.
Pre-conditions:
1. Consumer (ADAE server) collects data or analytics via A-DCCF from data producer.
Figure 8.12.2.1-1: Support for data collection over A-DCCF
1. The consumer (ADAE server) sends a data collection subscription request to A-DCCF for collecting data/analytics. As specified in Table 8.12.3.2-1, the request message includes identifier of the consumer (ADAE server ID), Data Collection Event ID, and Data Collection Requirements. The request message may include the identifier of Data Producer, Analytics ID, target data producer profile criteria, process requirements, Area of Interest, Time validity, storage requirements, and notification endpoints. The consumer decides to go via A-DCCF based on internal configuration.
2. If the data producer is not identified by the consumer, the A-DCCF determines the data procedure that can provide data/analytics. If the consumer requested storage of data/analytics in an A-ADRF but the A-ADRF ID is not provided by the consumer, or the collected data/analytics is to be stored in an A-ADRF according to configuration on the A-DCCF, the A-DCCF selects an A-ADRF to store the collected data/analytics.
3. The A-DCCF determines whether the data/analytics requested in step 1 are already being collected. If the requested data/analytics are already being collected by a consumer, the A-DCCF adds the new consumer to the list of consumers that are subscribed for these data/analytics.
4. If the data/analytics subscribed in step 1 is not being collected by the A-DCCF, the A-DCCF subscribes to the data producer for data/analytics.
If the data/analytics subscribed in step 1 partially matches the data/analytics that is already being collected by the A-DCCF, a modification of this subscription to the data producer would satisfy both the existing data/analytics subscriptions as well as the newly requested data/analytics, the A-DCCF requests an update of the previous subscription to the data producer. The A-DCCF adds the consumer to the list of consumers that are subscribed for these data/analytics.
5. Upon received the data/analytics subscription request from the A-DCCF, the data producer determines whether the required data/analytics can be provided and sends data/analytics subscription response to the A-DCCF.
6. The A-DCCF sends data/analytics subscription response to the consumer.
7. When the required data/analytics are available, the data producer notifies the data/analytics to the A-DCCF.
8. The A-DCCF notifies the data/analytics to all notification endpoints indicated in step 1. Data/analytics sent to notification endpoints may be processed by the DCCF upon to the request in step 1. The DCCF may store the data/analytics in the A-ADRF if requested by the consumer or if required by A-DCCF configuration. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.2.2 Request-response model | Figure 8.12.2.2-1 illustrates the procedure for the consumer to request A-DCCF for data or analytics collection.
Figure 8.12.2.2-1: Support for Get data/analytics over A-DCCF
1. The consumer (ADAE server) sends a Get data/analytics request to A-DCCF for data/analytics collection. As specified in Table 8.12.3.5-1, the request message includes identifier of the consumer (ADAE server ID), and Data/Analytics Requirements. The request message may include the identifier of Data Producer, Analytics ID, target data producer profile criteria, process requirements, storage requirements, and notification endpoints. The consumer decides to go via A-DCCF based on internal configuration.
2. The A-DCCF determines whether the data/analytics requested in step 1 are already being collected. If the requested data/analytics are already being collected by a consumer, the A-DCCF adds the new consumer to the list of consumers that are subscribed for these data/analytics.
3. If the data/analytics requested in step 1 is not being collected by the A-DCCF, and the data producer is not identified by the consumer, the A-DCCF determines the data procedure that can provide data/analytics. If the consumer requested storage of data/analytics in an A-ADRF but the A-ADRF ID is not provided by the consumer, or the collected data/analytics is to be stored in an A-ADRF according to configuration on the A-DCCF, the A-DCCF selects an A-ADRF to store the collected data/analytics.
4. The A-DCCF sends Get data/analytics request to the data producer for data/analytics.
5. Upon received the data/analytics request from the A-DCCF, the data producer determines whether the required data/analytics can be provided and sends data/analytics response to the A-DCCF. The required data/analytics may be contained in the response if they are available at the data producer.
6. The A-DCCF sends data/analytics response to the consumer. The required data/analytics may be contained in the response if get from the data producer. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.3.1 General | The following information flows are specified for data collection based on clause 8.12.2. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.3.2 Data collection subscription request | Table 8.12.3.2-1 describes information elements for the data collection subscription request from the consumer (ADAE server) to the A-DCCF.
Table 8.12.3.2-1: Data collection subscription request
Information element
Status
Description
Consumer ID
M
The identifier of the consumer (ADAE server ID).
Data Collection Event ID
M
The identifier of the data collection event.
Data Collection requirements
M
The requirements for data collection, including the format of data, frequency of reporting, level of abstraction of data, level of accuracy of data.
Analytics ID
O
The identifier of the analytics event, for which the data collection is needed.
List of Data Producer IDs
O
The list of Data Producer IDs.
Target data producer profile criteria
O
Characteristics of the data producers to be used.
Area of Interest
O
The geographical or service area for which the requirement request applies
Time validity
O
The time validity of the request
Process requirements
O
Requirements on processing the collected data/analytics.
Storage requirements
O
Requirements on storage of the collected data/analytics.
> A-ADRF ID
O
The identifier of A-ADRF for store the collected data/analytics.
Notification endpoints ID or address
O
The identifier or address of the notification endpoints. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.3.3 Data collection subscription response | Table 8.12.3.3-1 describes information elements for the data collection subscription response from the A-DCCF to the consumer (ADAE server).
Table 8.12.3.3-1: Data collection subscription response
Information element
Status
Description
Result
M
The result of the data collection subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.3.4 Data collection notification | Table 8.12.3.4-1 describes information elements for the data collection notification from the A-DCCF to the consumer (ADAE server).
Table 8.12.3.4-1: Data collection notification
Information element
Status
Description
Data Collection Event ID
M
The identifier of the data collection event.
Analytics ID
O
The identifier of the analytics event.
Analytics Type
O
The type of reported analytics, which can be statistics, prediction, etc.
Data Type
O
The type of reported data samples, which can be UE data, network data, application data, edge data, or different granularities/abstraction of data (e.g. real time, non-real time).
Data Output
M
The reported data/analytics, which can be inform of measurements or offline/historical data/analytics based on subscription.
Process information
O
Information of the processing of the collected data/analytics.
Storage information
O
Information of the storage of the collected data/analytics.
> A-ADRF ID
O
The identifier of A-ADRF for store the collected data/analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.3.5 Get Data/Analytics request | Table 8.12.3.5-1 describes information elements for the Get data/analytics request from the consumer (ADAE server) to the A-DCCF.
Table 8.12.3.5-1: Get Data/Analytics request
Information element
Status
Description
Consumer ID
M
The identifier of the consumer (ADAE server ID).
Data/Analytics requirements
M
The requirements for data/analytics collection, including the format of data, level of abstraction of data, level of accuracy of data.
Analytics ID
O
The identifier of the analytics event for the required analytics.
List of Data Producer IDs
O
The list of Data Producer IDs.
Target data producer profile criteria
O
Characteristics of the data producers to be used.
Area of Interest
O
The geographical or service area for which the requirement request applies
Time validity
O
The time validity of the request
Process requirements
O
Requirements on processing the collected data/analytics.
Storage requirements
O
Requirements on storage of the collected data/analytics.
> A-ADRF ID
O
The identifier of A-ADRF for store the collected data/analytics.
Notification endpoints ID or address
O
The identifier or address of the notification endpoints. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.3.6 Data collection response | Table 8.12.3.6-1 describes information elements for the data collection response from the A-DCCF to the consumer (ADAE server).
Table 8.12.3.6-1: Data collection response
Information element
Status
Description
Result
M
The result of the analytics data request (positive or negative acknowledgement).
Analytics ID
O
The identifier of the analytics event.
Analytics Type
O
The type of reported analytics, which can be statistics, prediction, etc.
Data Type
O
The type of reported data samples, which can be UE data, network data, application data, edge data, or different granularities/abstraction of data (e.g. real time, non-real time).
Data Output
M
The reported data/analytics, which can be inform of measurements or offline/historical data/analytics based on subscription.
Process information
O
Information of the processing of the collected data/analytics.
Storage information
O
Information of the storage of the collected data/analytics.
> A-ADRF ID
O
The identifier of A-ADRF for store the collected data/analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.12.3.7 Data producer profile | The data producer profile IE includes information about the data generation/production capability of the data producer to support data collection for data analytics service and the availability/accessibility of the generated/produced data, as defined in Table 8.12.3.7-1.
Table 8.12.3.7-1: Data producer profile
Information element
Status
Description
Data Producer ID
M
ID of the data producer.
Data producer type (NOTE)
M
Specifies the type of the data producer, e.g., ADAEC, A-DCCF, A-ADRF, VAL server, SEAL server, SEAL client, EES, EAS.
Data type (NOTE)
M
Type of information that can be provided by the data producer, e.g., performance indicators, reproducer usage data, server load data, application performance, edge load.
Data producer role (NOTE)
O
Role of the data producer, e.g., generating entity, original producer, repository.
Original producer ID (NOTE)
O
If the data producer role is not “original producer” or “generating entity”, specifies the Producer ID of the original data producer for the data provided by this data producer.
If the data producer type is A-DCCF, this is a list of Data Producer IDs.
Data freshness (NOTE)
O
If the data producer role is not “original producer” or “generating entity”, length of time elapsed after the data is generated until is available at the data producer. Alternatively, the data collection rate supported by the producer is provided.
Data producer capability (NOTE)
O
Indicates data producer capabilities for this data type, e.g. how long the data can be stored, support for anonymization, data generation rate and schedule.
NOTE: When the Data producer profile IE is used for Target data producer profile criteria (e.g. Table 8.12.3.2-1 and Table 8.12.3.5-1), this IE may be a list of values. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13 Procedure on support for server-to-server performance analytics | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.1 General | This clause describes the procedure for server-to-server performance analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.2 Procedure | Figure 8.13.2.1-1 illustrates the procedure for server-to-server performance analytics.
Pre-conditions:
1. ADAES is connected to A-ADRF and the target server (server#1).
Figure 8.13.2.1-1: ADAES support for server-to-server performance analytics
1. The analytics consumer (e.g., VAL server, EES) of the ADAE server analytics service sends a server-to-server analytics subscription request to the ADAE server. Such request can include whether the analytics notification shall be periodic or based on an expected application QoS change (in that case also the thresholds can be provided at the request)
2. The ADAE server sends a server-to-server analytics subscription response as an ACK to the analytics consumer.
3. The ADAE server identifies server#1 where the session performance analytics need to be performed. The ADAES server sends an Inter-server data request to server #1. Such request includes QoS attributes to be analysed (latency, bitrate, jitter, application layer PER) based on the request in step 1.
4. Bases on the request, measurement may be started between the server#1 and server#2. Such data can be about the latency, throughput, jitter, QoE measurements, PQI load, etc.
NOTE: How the measurement is collected is out of 3GPP scope. The measurement data can be already available in server#1 or server#2.
5. Server#1 sends the analytics to the ADAE server in an Inter-server data response message.
6. The ADAE server requests historical inter-server performance analytics from A-ADRF by sending a Server-to-server analytics request.
7. Based on the request, the ADAE server receives historical inter-server performance analytics by receiving a Server-to-server analytics response from A-ADRF.
8. The ADAE server abstracts or correlates the data/analytics from step 5-7. Based on the request in step 1, ADAES may also provide predictions for performance change.
9. The ADAE server sends a server-to-server analytics notification to the analytics consumer. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3.1 General | The following information flows are specified for server-to-server performance analytics based on 8.13.2. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3.2 Server-to-server performance analytics subscription request | Table 8.13.3.2-1 describes information elements for the server-to-server performance analytics subscription request from the analytics consumer (e.g., the VAL server, EES) to the ADAE server.
Table 8.13.3.2-1: Server-to-server performance analytics subscription request
Information element
Status
Description
Analytics Consumer ID
M
The identifier of the analytics consumer (VAL server, EES etc.).
Analytics ID
O
The identifier of the analytics event. This ID can be for example “server-to-server performance analytics”.
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions.
List of server identifiers and addresses
M
Identifier of the servers, e.g. SEAL server ID, EASID, EESID, and IP address(es) for which the analytics subscription applies.
VAL service ID
O
The VAL service for which the subscription applies.
Reporting requirements
O
Requirements for analytics reporting. The requirements may include for example the type and frequency of reporting (periodic or event triggered), the reporting periodicity in case of periodic, and reporting thresholds.
Area of Interest
O
The geographical or service area for which the subscription request applies.
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
Time validity
O
The time validity of the subscription request. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3.3 Server-to-server performance analytics subscription response | Table 8.13.3.3-1 describes information elements for the server-to-server performance analytics subscription response from the ADAE server to the analytics consumer.
Table 8.13.3.3-1: Server-to-server performance analytics subscription response
Information element
Status
Description
Result
M
The result of the analytics subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3.4 Server-to-server performance analytics notification | Table 8.13.3.4-1 describes information elements for the server-to-server performance analytics notification from the ADAE server to the analytics consumer.
Table 8.13.3.4-1: Server-to-server performance analytics notification
Information element
Status
Description
Analytics ID
O
The identifier of the analytics event. This ID can be for example “server-to-server performance analytics”.
Analytics Output
M
The predictive or statistical parameter, which can be:
- A server-to-server session predicted or expected performance change
- A server-to-server session performance sustainability over a given time horizon/area
- QoS measurements from the session (e.g. latency)
Confidence level
O
For predictive analytics, the achieved confidence level can be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3.5 Inter-server session data request | Table 8.13.3.5-1 describes information elements for the Inter-server session data request from the target server to the ADAE server.
Table 8.13.3.5-1: Inter-server session data request
Information element
Status
Description
ADAE server ID
M
The identifier of the ADAE server.
Analytics ID
O
The identifier of the analytics event. This ID can be for example “Server-to-server performance analytics”.
Analytics type
M
Whether analytics event is about prediction or statistics.
List of server identifiers and addresses
M
Identifier of the servers, e.g. SEAL server ID, EASID, EESID, and IP address(es) for which the analytics subscription applies.
QoS attributes
M
The QoS attributes (latency, bitrate, jitter, application layer PER) to be collected.
Data collection requirements
O
The requirements for data collection, including the format of data, level of abstraction of data, level of accuracy of data, if the measurements should be from real-time measurements or offline data.
Time validity
O
The time validity of the request. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3.6 Inter-server session data response | Table 8.13.3.6-1 describes information elements for the Inter-server session data response from the ADAE server to the target server.
Table 8.13.3.6-1: Inter-server session data response
Information element
Status
Description
Results
M
The result of the analytics data request (positive or negative acknowledgement).
Analytics ID
O
The identifier of the analytics event.
List of server identifiers and addresses
O
Identifier of the servers, e.g. SEAL server ID, EASID, EESID, and IP address(es) for which the analytics subscription applies.
Data Output
O
The reported data for the server-to server sessions, which can be in form of offline stats/historical data or real-time measurements on the requested QoS parameters.. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3.7 Server-to-server analytics request | Table 8.13.3.7-1 describes information elements for the server-to-server analytics request from the ADAE server to the A-ADRF.
Table 8.13.3.7-1: Server-to-server analytics request
Information element
Status
Description
ADAE server ID
M
The identifier of the ADAE server.
Analytics ID
M
The identifier of the analytics event.
List of server identifiers and addresses
M
Identifier of the servers, e.g. SEAL server ID, EASID, EESID, for which the analytics subscription applies.
QoS attributes
M
The QoS attributes (latency, bitrate, jitter, application layer PER) to be collected.
Time validity
O
The time validity of the request. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.13.3.8 Server-to-server analytics response | Table 8.13.3.8-1 describes information elements for the server-to-server analytics response from the A-ADRF to the ADAE server.
Table 8.13.3.8-1: Server-to-server analytics response
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event.
List of server identifiers and addresses
M
Identifier of the servers, e.g. SEAL server ID, EASID, EESID, for which the analytics subscription applies.
Data Output
M
The reported data, which can be in form of measurements or offline/historical data on the requested QoS attributes. The reported data includes historical inter-server performance analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14 Procedure for Collision Detection Analytics | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.1 General | This clause describes two procedures (covering both subscribe-notify and request-response models in 8.14.2.1 and 8.14.2.2 respectively) for supporting collision detection analytics, where the collision detection analytics are performed based on data collected from the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server) and A-ADRF. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.2 Procedure | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.2.1 Subscribe-notify model | Pre-conditions:
- Information about environment, e.g. static devices, are available from the 3rd party LM server.
- The location information about the UEs is available at SEAL LM server and/or LM client.
- The Ranging/Sidelink Positioning information exposure of the UEs is allowed at 5GC.
Figure 8.14.2.1-1: ADAES support for collision detection analytics
1. The analytics consumer (e.g. VAL Server, LM server, UAE server, UAS application specific server) sends collision detection analytics subscription request to ADAE server. The Analytics ID in the request message is set to "Collision detection analytics for target UE(s)" or "Collision detection analytics for any UEs". For analytics subscription request, the request contains message as defined in table 8.14.3.2-1.
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.
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.
4. The ADAE server sends data collection subscription request to the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server) and a data collection request to the Data Producer (e.g. A-ADRF for historical data) with the respective Data Collection Event ID and the requirement for collection of ranging and/or sidelink positioning related data or analytics of UEs, and location information of UEs. Data collection at the UE(s) reuses mechanism defined in 3GPP TS 26.531 [3].
5. The Data Producer sends data collection subscription response as a positive or negative acknowledgement to the ADAE server.
6. The ADAE server based on data collection subscription receive ranging and/or sidelink positioning related data/analytics of UEs and location information of UEs from the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server).
NOTE: The procedures for UE related data collection need to take user consent into account.
7. The ADAE server based on data collection request receive ranging and/or sidelink positioning related historical data of UEs from Data Producer (e.g. A-ADRF).
8. The ADAE server performs analytics relevant operations to generate the analytics for the collision detection between any target VAL UEs, collision detection between any UEs and target VAL UEs, or collision detection between any UE within the Area of Interest and based on the request provided in step 1 and the data/analytics received from the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server, A-ADRF for historical data).
9. The ADAE server sends collision detection analytics notifications to the consumer with the required collision detection analytics. The notification contains message as defined in table 8.14.3.4-1. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.2.2 Request-response model | Pre-conditions:
- ADAE Server already have the analytics data derived from steps 3-6 in the procedure introduced in clause 8.14.2.1.
Figure 8.14.2.2-1: ADAES support for collision detection analytics
1. The analytics consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) sends a get collision detection analytics request message to the ADAE server to receive analytics data for collision detection analytics with Analytics ID in the request message setting to "Collision detection analytics for target UE(s)" or "Collision detection analytics for any UEs". The request contains message as defined in table 8.14.3.8-1.
2. Upon receiving the request, the ADAE server authenticates and authorizes the analytics consumer.
3. If the analytics consumer is authorized, the ADAE server may get the analytics by performing steps 3 to 8 of clause 8.14.2.1.
4. If the analytics consumer is authorized, the ADAE server sends a get collision detection analytics response message including the analytics data (statistical and/or predictive) of the collision detection analytics as defined in table 8.14.3.9-1. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.1 General | The following information flows are specified for collision detection analytics based on clause 8.14.2. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.2 Collision detection analytics subscription request | Table 8.14.3.2-1 describes the information flow from the consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) as a request or update request for the collision detection analytics.
Table 8.14.3.2-1: Collision detection analytics subscription request
Information element
Status
Description
Requestor ID
M
(NOTE 1)
The identifier of the consumer.
Analytics ID
O
(NOTE 1)
The identifier of the analytics event. This ID can be for example "Collision Detection analytics for target UE(s)", "Collision Detection analytics for any UEs".
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions,
Analytics filter information
M
Filter information for the analytics event.
> Filter for Collision between interested UE(s) and target UE(s)
O
(NOTE 2)
The filter information for the Collision Detection analytics for target UE(s).
>>Target VAL UE ID(s)
M
The identifier(s) of VAL UE(s) for which the analytics subscription applies.
>> Interested VAL UE ID(s)
O
(see NOTE 3)
The identifier(s) of a list of the interested UE(s) collision with that shall be analysed.
>>Target VAL server ID
O
If consumer is different from the VAL server, this identifier shows the target VAL server for which the analytics subscription applies.
>>Area of Interest
O
(see NOTE 3)
The geographical or service area for which the subscription request applies.
> Filter for Collision detection between any UE(s)
O
(NOTE 2)
The filter information for the Collision Detection analytics for any UE(s) in an area.
>>Target VAL server ID
O
If consumer is different from the VAL server, this identifier shows the target VAL server for which the analytics subscription applies.
>>Area of Interest
M
The geographical or service area for which the subscription request applies.
Collision detection criteria
O
The parameters for collision detection analytics apply.
>Distance
O
The allowed minimum distance between UEs. The collision is detected if the distance between the UEs is less than the provided value.
Reporting requirements
O
It 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 in case of event triggered.
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
Time validity
O
The time validity of the subscription request.
NOTE 1: This information element shall not be updated.
NOTE 2: One of the elements shall be provided.
NOTE 3: If the IE "Filter for Collision between the interested UE(s) and target UE(s)" is present, at least one of the elements shall be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.3 Collision detection analytics subscription response | Table 8.14.3.3-1 describes the information elements for the collision detection analytics subscription response from the ADAE server to the consumer.
Table 8.14.3.3-1: Collision detection analytics subscription response
Information element
Status
Description
Result
M
The result of the analytics subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.4 Collision detection analytics notification | Table 8.14.3.4-1 describes the information flow from the ADAES to the consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) as a response for the collision detection analytics.
Table 8.14.3.4-1: Collision detection analytics notification
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event. This ID can be for example "Collision Detection analytics for target UE(s)", "Collision Detection analytics for any UEs".
Outputs for Collision between any UE(s) and target UE(s)
O
(see NOTE)
The analytics (predictive or statistical parameter) for Collision Detection analytics for target UE(s).
> List of target VAL UE(s)
M
The analytics outputs of the list of target VAL UE(s).
>>Target VAL UE ID
M
The identifier of target VAL UE for which the analytics outputs apply.
>>Potential collision VAL UE ID(s)
M
The identifier(s) of the potential collision VAL UE(s) for which the analytics outputs apply.
>>Time of potential collisions
M
Time of the potential collisions between the target UE and the UEs.
>>Location of potential collisions
M
Location of the potential collisions between the target UE and the UEs.
>>Direction of moving
O
Direction of the target UE and the UEs moving.
>>Velocity of moving
O
Velocity of the target UE and the UEs moving.
>>Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
Outputs for Collision between any UE(s)
O
(NOTE)
The analytics (predictive or statistical parameter) for Collision Detection analytics for any UEs.
>Potential collision VAL UE ID(s)
M
The identifier(s) of the potential collision VAL UE(s) for which the analytics outputs apply.
>Time of potential collisions
M
Time of the potential collisions between the UEs.
>Location of potential collisions
M
Location of the potential collisions between the UEs.
>Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
NOTE: One of the elements shall be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.5 Ranging/SL positioning data and location information collection subscription request | Table 8.14.3.5-1 describes information elements for the Ranging/SL positioning data and location information collection subscription request from the ADAE server to the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server, A-ADRF for historical data.
Table 8.14.3.5-1: Data collection subscription request
Information element
Status
Description
Requestor ID
M
The identifier of the consumer.
Data Collection Event ID
M
The identifier of the data collection event
Data Collection requirements
M
The requirements for data collection, including the format of data, frequency of reporting, level of abstraction of data, level of accuracy of data.
Analytics ID
O
The identifier of the analytics event, for which the data collection is needed.
List of Data Producer IDs
O
In case when this request is performed via A-DCCF, then the list of Data Producer IDs is needed.
>Target data producer profile criteria
O
Characteristics of the data producers to be used.
>VAL UE IDs
O
The VAL UE(s) identifiers for which the data/analytics apply.
Area of Interest
O
The geographical or service area for which the requirement request applies.
Time validity
O
The time validity of the request. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.6 Ranging/SL positioning data and location information collection subscription response | Table 8.14.3.6-1 describes information elements for the Data collection subscription response from the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server, A-ADRF for historical data.
Table 8.14.3.6-1: Data collection subscription response
Information element
Status
Description
Result
M
The result of the Ranging/SL positioning data and location information collection subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.7 Data Notification | Table 8.14.3.7-1 describes information elements for the Data Notification from the Data Producer to the ADAE server.
Table 8.14.3.7-1: Data notification
Information element
Status
Description
Data Collection Event ID
M
The identifier of the data collection event.
Data Producer ID
M
The identity of Data Producer.
Analytics ID
O
The identifier of the analytics event.
Data Type
M
The 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 Output
M
The reported data, which can be inform of measurements or offline/historical data on the requested parameter based on subscription. Such data can be ranging/sidelink positioning information of UEs, location information of UEs (moving devices like UAS devices, V2X devices, robots, and/or people with UE), and the location information about environment (static devices like infrastructures) for a given time and area of interest, Relative Proximity analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.8 Get analytics data request | Table 8.14.3.8-1 describes information elements for the collision detection analytics request from the analytics consumer to the ADAE server.
Table 8.14.3.8-1: Get analytics data request
Information element
Status
Description
Requestor ID
M
The identifier of the consumer.
Analytics ID
O
The identifier of the analytics event. This ID can be for example "Collision Detection analytics for target UE(s)" , "Collision Detection analytics for any UEs".
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions.
Analytics filter information
M
Filter information for the analytics event
> Filter for Collision between interested UE(s) and target UE(s)
O
(see NOTE 1)
The filter information for the Collision Detection analytics for target UE(s).
>>Target VAL UE ID(s)
M
The identifier(s) of VAL UE(s) for which the request applies
>> Interested VAL UE ID(s)
O
(see NOTE 2)
The identifier(s) of a list of the interested UE(s) collision with that shall be analysed.
>Target VAL server ID
O
If consumer is different from the VAL server, this identifier shows the target VAL server for which the request applies.
>Area of Interest
O
(see NOTE 2)
The geographical or service area for which the subscription request applies
> Filter for Collision detection between any UE(s)
O
(see NOTE 1)
The filter information for the Collision Detection analytics for any UE(s) in an area.
>>Target VAL server ID
O
If consumer is different from the VAL server, this identifier shows the target VAL server for which the request applies.
>>Area of Interest
M
The geographical or service area for which the request applies.
Collision detection criteria
O
The parameters for collision detection analytics apply.
>Distance
O
The allowed minimum distance between UEs.
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
Time duration
O
Time duration since when analytics data is required.
NOTE 1: One of the elements shall be provided.
NOTE 2: If the IE "Filter for Collision between any UE(s) and target UE(s)" is present, at least one of the elements shall be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.14.3.9 Get analytics data response | Table 8.14.3.9-1 describes information elements for the Get collision detection analytics response from the ADAE server to the consumer.
Table 8.14.3.9-1: Get analytics response
Information element
Status
Description
Analytics ID
O
The identifier of the analytics event. This ID can be for example "Collision Detection analytics for target UE(s)", "Collision Detection analytics for any UEs"".
Outputs for Collision between any UE(s) and target UE(s)
O
(see NOTE)
The analytics (predictive or statistical parameter) for Collision Detection analytics for target UE(s).
> List of target VAL UE(s)
M
The analytics outputs of the list of target VAL UE(s).
>>Target VAL UE ID
M
The identifier of target VAL UE for which the analytics outputs apply.
>>Potential collision VAL UE ID(s)
M
The identifier(s) of the potential collision VAL UE(s) for which the analytics outputs apply.
>>Time of potential collisions
M
Time of the potential collisions between the UEs.
>>Location of potential collisions
M
Location of the potential collisions between the UEs.
>>Direction of moving
O
Direction of the UEs moving.
>>Velocity of moving
O
Velocity of the UEs moving.
>>Timestamp
O
Time stamp of the collected analytics data.
>>Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
Outputs for Collision between any UE(s)
O
(see NOTE)
The analytics (predictive or statistical parameter) for Collision Detection analytics for any UEs.
>Potential collision VAL UE ID(s)
M
The identifier(s) of the potential collision VAL UE(s) for which the analytics outputs apply.
>Time of potential collisions
M
Time of the potential collisions between the UEs.
>Location of potential collisions
M
Location of the potential collisions between the UEs.
>Timestamp
O
Time stamp of the collected analytics data.
>Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
NOTE: One of the elements shall be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15 Procedure for Location-related UE Group Analytics | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.1 General | This clause describes two procedures (covering both subscribe-notify and request-response models in 8.15.2.1 and 8.15.2.2 respectively) for supporting location-related UE group analytics, where the location-related UE group analytics are performed based on data collected from the Data Producer (e.g. 5GC NFs (e.g. GMLC (via NEF), NWDAF), ADAE Client, LM server) and A-ADRF. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.2 Procedure | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.2.1 Subscribe-notify model | Pre-conditions:
- The location information about the UEs is available at SEAL LM server.
- The location information of the UEs exposure is allowed at 5GC.
Figure 8.15.2.1-1: ADAES support for location-related UE group analytics
1. The analytics consumer (i.e. LMS) sends location-related UE group analytics subscription request to ADAE server. The Analytics ID in the request message is set to "UE group route analytics" or "UE group member deviation". For analytics subscription request, the request contains message as defined in table 8.15.3.2-1.
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.
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.
4. The ADAE server sends a data collection subscription request to the Data Producer (e.g. 5GC NFs (e.g. GMLC (via NEF), NWDAF), ADAE Client, LM server) and a data collection request to the Data Producer (e.g. A-ADRF for historical data) with the respective Data Collection Event ID and the requirement for collection location related data/analytics of UEs. Data collection at the UE(s) reuses the mechanism defined in 3GPP TS 26.531 [3].
5. The Data Producer sends data collection subscription response as a positive or negative acknowledgement to the ADAE server.
6. The ADAE server based on data collection subscription receive location related data/analytics of UEs from the Data Producer (e.g. 5GC NFs (e.g. GMLC (via NEF), NWDAF), ADAE Client, LM server).
7. The ADAE server based on data collection request receive location related historial data of UEs from the Data Producer (e.g. A-ADRF).
NOTE: The procedures for UE location information collection need to take user consent into account.
8. The ADAE server performs analytics relevant operations to generate the analytics based on the data received from the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, A-ADRF for historical data). In detail, the ADAE server may generate analytics in the following ways.
- For UE group route analytics: Inputs include the location information of UE(s) from LM server (e.g. UE's location in clause 9.3.7 of 3GPP TS 23.434 [2]), the analytics from NWDAF (e.g. UE mobility analytics, Movement behaviour analytics, UE communication analytics, and/or Dispersion analytics in 3GPP TS 23.288 [4]). For example, UE's location service from LMS allows ADAES to obtain the UE location, UE mobility analytics provides potential moving direction of the UE(s), Dispersion analytics gives ADAES information on UE data volume dispersion predictions, etc., by combining all the information collected, predictions on UE group route can be generated.
- For UE group member deviation analytics: Inputs include the Ranging/Sidelink Positioning location information of the UE group member from GMLC (via NEF) (e.g. Ranging/Sidelink Positioning location results in clause 6.20 of 3GPP TS 23.273 [18]), location information of the UE group member from LM server (e.g. UE's location in clause 9.3.7 of 3GPP TS 23.434 [2]), and the analytics from NWDAF (e.g. UE mobility analytics, Movement behaviour analytics, Relative Proximity analytics, and/or Abnormal behaviour analytics in 3GPP TS 23.288 [4]) of this UE group member. The ADAE server can aggregate the collected information (e.g. distance between UEs from the Ranging/Sidelink Positioning location information service, predictions on distance between UEs from the Relative Proximity analytics, etc.) and derive which UE group member is deviating (or will deviate) from other group member(s) or target group member (e.g. UE's ranging information with any other UE(s) in a group is larger than a threshold, and such trend shows longer and longer ranging within a time period, or the UE moving direction is different from any other UE(s) in a group or target group member).
9. The ADAE server sends location-related UE group analytics notifications to the consumer with the required location-related UE group analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.2.2 Request-response model | Pre-conditions:
- ADAE Server already has the analytics data derived from steps 3-6 in the procedure introduced in clause 8.15.2.1.
Figure 8.15.2.2-1: ADAES support for location-related UE group analytics
1. The analytics consumer (i.e. LMS) sends a get location-related UE group analytics request message to the ADAE server to receive analytics data for location-related UE group analytics with Analytics ID in the request message setting to "UE group route analytics" or "UE group member deviation". The request contains message as defined in table 8.15.3.8-1.
2. Upon receiving the request, the ADAE server authenticates and authorizes the analytics consumer.
3. If the analytics consumer is authorized, the ADAE server may get the analytics by performing steps 3 to 8 of clause 8.15.2.1.
4. If the analytics consumer is authorized, the ADAE server sends a get location-related UE group analytics response message including the analytics data (statistical and/or predictive) of the location-related UE group analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.1 General | The following information flows are specified for location-related UE group analytics based on clause 8.15.2. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.2 Location-related UE group analytics subscription request | Table 8.15.3.2-1 describes the information flow from the consumer (LMS) as a request or update request for the location-related UE group analytics.
Table 8.15.3.2-1: Location-related UE group analytics subscription request
Information element
Status
Description
Requestor ID
M
(NOTE 1)
The identifier of the consumer.
Analytics ID
O
(NOTE 1)
The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics".
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions,
Analytics filter information
M
Filter information for the analytics event.
>Application Group ID
O
(NOTE 2)
Application group identifier for which the analytics subscription applies.
>Target VAL UE ID(s)
O
(NOTE 2)
The identifier(s) of the VAL UE(s) for which the analytics subscription applies.
>Area of Interest
O
The geographical or service area for which the subscription request applies.
>Application Group profile(s)
O
Information about the Application Group(s) with common EAS (as defined in 3GPP TS 23.558 [14] Table 8.15.11-1).
>Deviation
O
Deviation information, e.g. different moving direction or moving speed, distance with the target group member UE larger than an threshold.
>>Target Group member UE ID
O
The identifier of the target group member UE.
>>Deviation criteria
O
The criteria used for detecting deviation of group member UE, e.g. distance, moving direction, moving speed.
Reporting requirements
O
It 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.
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
Time validity
O
The time validity of the subscription request.
NOTE 1: This information element shall not be updated.
NOTE 2: One of the elements shall be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.3 Location-related UE group analytics subscription response | Table 8.15.3.3-1 describes the information elements for the location-related UE group analytics subscription response from the ADAE server to the consumer.
Table 8.15.3.3-1: Location-related UE group analytics subscription response
Information element
Status
Description
Result
M
The result of the analytics subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.4 Location-related UE group analytics notification | Table 8.15.3.4-1 describes the information flow from the ADAES to the consumer (LM Server) as a response for the location-related UE group analytics.
Table 8.15.3.4-1: Location-related UE group analytics notification
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics".
Outputs for UE group route
O
(NOTE 1)
The reported analytics for UE group route analytics apply.
>List of EAS ID(s)
M
List of identifiers of EAS.
>>EAS ID(s)
O
Identifier(s) of EAS(s).
>>Route ID
M
The identifier of the common route for the UE(s) to EAS(s).
>>VAL UE ID(s)
M
The identifiers of the VAL UE(s) which with the common route to the EAS(s).
Outputs for UE group member deviation
O
(NOTE 1, NOTE 2)
The reported analytics for group member deviation analytics apply.
>Application Group ID
M
Application group identifier.
>>Target Group member UE ID
O
The identifier of the target group member UE.
>List of VAL UE ID(s)
M
The VAL UE(s) which with different behaviour with the majority group members or the target group member.
>>VAL UE ID
O
Identifier of the VAL UE.
>>Deviation
O
Detail information of deviation for the VAL UE, e.g., different moving direction or moving speed, distance with the target group member.
>>Time duration
O
The time duration of this UE deviation.
Validity Time
O
The valid time duration of the analytics.
Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
NOTE 1: One of these shall be present based on the analytics event.
NOTE 2: Statistics on UE deviation including e.g. minimum, maximum, and average UEs moving into area, moving out of area, moving speed, and distance from target group member. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.5 Location information collection subscription request | Table 8.15.3.5-1 describes information elements for the Ranging/SL positioning data and location information collection subscription request from the ADAE server to the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, A-ADRF for historical data.
Table 8.15.3.5-1: Data collection subscription request
Information element
Status
Description
Requestor ID
M
The identifier of the consumer.
Data Collection Event ID
M
The identifier of the data collection event
Data Collection requirements
M
The requirements for data collection, including the format of data, frequency of reporting, level of abstraction of data, level of accuracy of data.
Analytics ID
O
The identifier of the analytics event, for which the data collection is needed. This ID can be for example "UE group route analytics" or "UE group member deviation analytics".
List of Data Producer IDs
O
In case when this request is performed via A-DCCF, then the list of Data Producer IDs is needed.
>Target data producer profile criteria
O
Characteristics of the data producers to be used.
>VAL UE IDs
O
The VAL UE(s) identifiers for which the data/analytics apply.
Area of Interest
O
The geographical or service area for which the requirement request applies.
Time validity
O
The time validity of the request. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.6 Location information collection subscription response | Table 8.15.3.6-1 describes information elements for the Data collection subscription response from the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, A-ADRF for historical data.
Table 8.15.3.6-1: Data collection subscription response
Information element
Status
Description
Result
M
The result of the location information collection subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.7 Data Notification | Table 8.15.3.7-1 describes information elements for the Data Notification from the Data Producer to the ADAE server.
Table 8.15.3.7-1: Data notification
Information element
Status
Description
Data Collection Event ID
M
The identifier of the data collection event.
Data Producer ID
M
The identity of Data Producer.
Analytics ID
O
The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics".
Data Type
M
The 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 Output
M
The reported data, which can be inform of measurements or offline/historical data on the requested parameter based on subscription. Such data can be location information of UEs (moving devices like UAS devices, V2X devices, robots, and/or people with UE, static devices like infrastructures) for a given time and area of interest, measurement of UE(s) moving in or moving out of the area of interest, UE mobility analytics, Ranging/Sidelink Positioning location information of UEs, Movement behaviour analytics, UE communication analytics, Dispersion analytics, Relative Proximity analytics, and/or Abnormal behaviour analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.8 Get analytics data request | Table 8.15.3.8-1 describes information elements for the location-related UE group analytics request from the analytics consumer to the ADAE server.
Table 8.15.3.8-1: Get analytics data request
Information element
Status
Description
Requestor ID
M
The identifier of the consumer.
Analytics ID
M
The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics".
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions,
Analytics filter information
M
Filter information for the analytics event.
>Application Group ID
O
(NOTE)
Application group identifier for which the analytics subscription applies.
>Target VAL UE ID(s)
O
(NOTE)
The identifier(s) of the VAL UE(s) for which the analytics subscription applies.
>Area of Interest
O
The geographical or service area for which the subscription request applies.
>Application Group profile(s)
O
Information about the Application Group(s) with common EAS (as defined in 3GPP TS 23.558 [14] Table 8.15.11-1).
>Deviation
O
Deviation information, e.g. different moving direction or moving speed, distance with the target group member UE larger than a threshold.
>>Target Group member UE ID
O
The identifier of the target group member UE.
>>Deviation criteria
O
The criteria used for detecting deviation of group member UE, e.g. distance, moving direction, moving speed.
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
NOTE: One of elements shall be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.15.3.9 Get analytics data response | Table 8.15.3.9-1 describes information elements for the Get location-related UE group analytics response from the ADAE server to the consumer.
Table 8.15.3.9-1: Get analytics response
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics".
Outputs for UE group route
O
(NOTE 1)
The reported analytics for UE group route analytics apply.
>List of EAS ID(s)
M
List of identifiers of EAS.
>>EAS ID(s)
O
Identifier(s) of EAS(s).
>>Route ID
M
The identifier of the common route for the UE(s) to EAS(s).
>>VAL UE ID(s)
M
The identifiers of the VAL UE(s) which with the common route to the EAS(s).
>Timestamp
O
Time stamp of the collected analytics data.
Outputs for UE group member deviation
O
(NOTE 1, NOTE 2)
The reported analytics for group member deviation analytics apply.
>Application Group ID
M
Application group identifier.
>>Target Group member UE ID
O
The identifier of the target group member UE.
>List of VAL UE ID(s)
M
The VAL UE(s) which with different behaviour with the majority group members or the target group member.
>>VAL UE ID
O
Identifier of the VAL UE.
>>Deviation
O
Detail information of deviation for the VAL UE, e.g., different moving direction or moving speed, distance with the target group member.
>>Time duration
O
The time duration of this UE deviation.
>Timestamp
O
Time stamp of the collected analytics data.
Validity Time
O
The valid time duration of the analytics.
Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
NOTE 1: One of these shall be present based on the analytics event.
NOTE 2: Statistics on UE deviation including e.g. minimum, maximum, and average UEs moving into area, moving out of area, moving speed, and distance from target group member. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16 Procedure for Application Layer AI/ML Member Capability Analytics | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.1 General | This clause describes two procedures (covering both subscribe-notify and request-response models in 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. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.2 Procedure | 8.16.2.1 Subscribe-notify model
Figure 8.16.2.1-1: ADAES support for application layer AI/ML Member capability analytics
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.
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.
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.
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 3GPP TS 26.531 [3].
5. The Data Producers (ADAE client) send data collection subscription response as a positive or negative acknowledgement to the ADAE server.
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.
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.
NOTE 1: The procedures for data collection for application layer AI/ML Member capability analytics need to take user consent into account.
8. The ADAES performs analytics relevant operations to generate the analytics based on the data/analytics received from the ADAEC.
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.
NOTE 2: The format for the application layer AI/ML Member capability attributes will be standardized in stage 3. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.2.2 Request-response model | Pre-conditions:
- ADAE server already have the analytics data derived from steps 3-8 in the procedure introduced in clause 8.16.2.1.
Figure 8.16.2.2-1: ADAES support for application layer AI/ML Member capability analytics
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.
2. Upon receiving the request, the ADAE server authenticates and authorizes the analytics consumer.
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.
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. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.1 General | The following information flows are specified for application layer AI/ML Member capability analytics based on clause 8.16.2. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.2 Application Layer AI/ML Member capability analytics subscription request | 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.
Table 8.16.3.2-1: Application Layer AI/ML Member capability analytics subscription request
Information element
Status
Description
Requestor ID
M
(NOTE)
The identifier of the consumer.
Analytics ID
M
(NOTE)
The identifier of the analytics event. This ID can be for example "Application layer AI/ML Member capability analytics".
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions.
List of VAL users or AI/ML Member IDs
M
The VAL users or AI/ML Member (s) identifiers for which the data/analytics apply.
VAL service ID
O
The identifier of the VAL service which is associated with application layer AI/ML Member capability.
Application layer AI/ML Member capability attributes
M
The 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 requirements
O
It 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 Interest
O
The geographical or service area for which the subscription request applies.
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
Time validity
O
The time validity of the subscription request.
NOTE: This information element shall not be updated.
Editor's Note: Whether and what more details about member capability need to be added is FFS. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.3 Application Layer AI/ML Member capability analytics subscription response | 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.
Table 8.16.3.3-1: Application layer AI/ML Member capability analytics subscription response
Information element
Status
Description
Result
M
The result of the analytics subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.4 Application layer AI/ML Member capability analytics notification | 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.
Table 8.16.3.4-1: Application layer AI/ML Member capability analytics notification
Information element
Status
Description
Analytics ID
M
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 IDs
M
The VAL users or AI/ML Member(s) identifiers for which the data/analytics apply.
>VAL user or AI/ML Member ID in the list
M
The VAL user or AI/ML Member identifier for which the data/analytics apply.
>>Analytics Output
M
The analytics outputs for the application layer AI/ML Member capability, which can be the predictive or statistical parameter.
>>>Applicable time period
O
The time period that the analytics applies to.
>>>AI/ML member availability
M
Statistics or predictions of the availability of the AI/ML member, e.g. if the AI/ML member will be up or down during the applicable time period.
>>>AI/ML member capability
M
Statistics or predictions of the capability of the AI/ML member, e.g. maximum/minimum number of supported active connections.
>>Confidence level
O
For predictive analytics, the achieved confidence level can be provided. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.5 Application Layer AI/ML Member capability data collection subscription request | 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.
Table 8.16.3.5-1: Data collection subscription request
Information element
Status
Description
Requestor ID
M
The identifier of the consumer.
Data Collection Event ID
M
The identifier of the data collection event
Data collection requirements
O
The requirements for data collection, including the format of data, frequency of reporting, level of abstraction of data, level of accuracy of data.
Analytics ID
O
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 IDs
O
In case when this request is performed via A-DCCF, then the list of Data Producer IDs is needed.
Target data producer profile criteria
O
Characteristics of the data producers to be used.
List of VAL users or AI/ML Member IDs
M
The VAL users or AI/ML Member (s) identifiers for which the data/analytics apply.
VAL service ID list
O
The identifier(s) of the VAL service(s) which is associated with application layer AI/ML Member capability.
Application layer AI/ML Member capability attributes
M
The application layer AI/ML Member capability attributes to be analyzed at the ADAE client.
Area of Interest
O
The geographical or service area for which the requirement request applies.
Time validity
O
The time validity of the request. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.6 Application Layer AI/ML Member capability data collection subscription response | 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.
Table 8.16.3.6-1: Data collection subscription response
Information element
Status
Description
Result
M
The result of the application layer AI/ML Member capability data collection subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.7 Data Notification | Table 8.16.3.7-1 describes information elements for the Data Notification from the Data Producer to the ADAE server.
Table 8.16.3.7-1: Data notification
Information element
Status
Description
Data Collection Event ID
M
The identifier of the data collection event.
Data Producer ID
M
The identity of Data Producer.
Analytics ID
O
The identifier of the analytics event. This ID can be for example "Application layer AI/ML Member capability analytics".
Data Type
M
The 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 Output
M
The reported data, which can be inform of measurements or offline/historical data on the requested parameter based on subscription. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.8 Get analytics data request | 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.
Table 8.16.3.8-1: Get analytics data request
Information element
Status
Description
Requestor ID
M
The identifier of the consumer.
Analytics ID
M
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 type
M
The type of analytics, e.g. statistics or predictions.
List of VAL users or AI/ML Member IDs
M
The VAL users or AI/ML Member (s) identifiers for which the data/analytics apply.
VAL service ID
O
The identifier of the VAL service which is associated with application layer AI/ML Member capability.
Application layer AI/ML Member capability attributes
M
The 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 level
O
The level of accuracy for the analytics service (in case of prediction).
Time window
O
The start and end time requirements on the generation of the analytics data to be collected.
Time validity
O
The time validity of the request.
Editor's Note: Whether and what more details about member capability need to be added is FFS. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.16.3.9 Get analytics data response | 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.
Table 8.16.3.9-1: Get analytics response
Information element
Status
Description
Result
M
The result of the analytics data request (positive or negative acknowledgement).
Analytics ID
O
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 IDs
M
The VAL users or AI/ML Member(s) identifiers for which the data/analytics apply.
>VAL user or AI/ML Member ID in the list
M
The VAL user or AI/ML Member identifier for which the data/analytics apply.
>>Analytics Output
M
The analytics outputs, which can be predictive or statistical parameter.
>>>AI/ML member availability
M
Statistics or predictions of the availability of the AI/ML member, e.g. if the AI/ML member will be up or down during the applicable time period.
>>>AI/ML member capability
M
Statistics or predictions of the capability of the AI/ML member, e.g. maximum/minimum number of supported active connections.
>>Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
>>Timestamp
O
Timestamp of the analytics output. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.17 Procedure VAL performance analytics for tethered UEs | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.17.1 General | The clause provides a mechanism for analyzing the delay for application layer segments withinan end-to-end XR application service segment, and in particular the link between the VAL Client (e.g., SEALDD client) at the Tethered Device, and the 3GPP VAL UE. Based on this analysis, the mechanism includes the derivation of application layer statistics or predictions for the segment of interest towards the consumer. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.17.2 Procedure | The procedure associated with the ADAE analytics for tethered UE and application connectivity performance is described below as depicted in Figure 8.17.2-1.
Pre-conditions:
1. A connection between an ADAEC and ADAES is established.
2. A connection between tethered VAL UE and host VAL UE is established.
Figure 8.17.2-1: Tethered VAL connectivity performance analytics procedure
1. The consumer of the ADAES analytics service, e.g., the SEALDD server or VAL server, sends a subscription request to ADAES and provides the analytics event ID e.g., "tethered VAL connectivity performance".
2. The ADAES sends a subscription response as an ACK to the consumer.
3. The ADAES maps the analytics ID (i.e., tethered VAL UE connectivity performance) to a list of data collection event identifiers, and optionally a list of data producer IDs. Such mapping may be preconfigured by the ADAES itself based on ASP preferred event types, or VAL type, or alternatively may be preconfigured by an MNO by means of the OAM.
4. The ADAES sends a tethered VAL UE connectivity performance data request to the determined tethered ADAEC with the analytics event ID and the configuration of the reporting required (e.g., periodic, based on maximum delay threshold etc.). Such request also includes additional application QoS attributes to be analyzed additionally based on other metrics (tethered link delay, E2E delay, 5GS PER, 5GS PDB/PSDB etc.). This step reuses the data collection subscription request and data collection subscription response flows as in clauses 8.2.4.4 and 8.2.4.5 respectively.
An application session then starts between the tethered VAL UE and the VAL server.
The next steps may happen asynchronously and in parallel given the 5GC reporting of events for the configured data collection.
5a. The ADAEC starts collecting data from the tethered VAL UE based on the request. The collection and reporting can be similar to ADAE procedure on VAL session performance analytics (as in step 8 of clause 8.2.3 in 3GPP TS 23.436). As enhancement of existing data collection, ADAEC may collect various events related to tethered link delay, e.g., TetheredLinkDelayExperience. This data can thus be about the delay measurements, throughput (e.g., max WiFi capacity), QoE measurements, etc.
5b. The ADAEC detects/predicts an application QoS change. Such a change can be for example a change in the QoS attributes requirements by means of detecting an event where the maximum latency threshold (e.g., over the tethered link or end to end) accepted by the ASP is exceeded, whereas the detection mechanism is performed over a given time horizon based on the analytics subscription request.
6. The ADAES sends a tethered VAL UE connectivity performance data response to the ADAES, including the detected/predicted application QoS change. This step reuses the Data Notification message as in clause 8.2.4.6.
7a. The ADAES may optionally further collect data about the DN performance analytics by means of NWDAF events consumption including service experience analytics etc. This type of analytics will provide statistics/predictions on the user plane performance over a specific application server instance and can be used to predict possible service experience downgrade/deviation that could be used as input to step 7b to predict an application QoS change.
7b. The ADAES predicts an application QoS change. Such a change can be for example a change in the QoS attributes requirements by means of predicting (based on collected metrics and detection in step 5b) an event where the maximum latency threshold (e.g., over the tethered link, over the DN link, or over the E2E connectivity) accepted by the ASP is likely to be exceeded over a given time horizon based on the analytics subscription request.
NOTE: How the DN performance analytics together with the ADAEC measurements are used together to trigger an event related to application QoS change is up to implementation.
8. The ADAES sends the derived analytics notification to the consumer (e.g., VAL server or any other authorized AF consumer). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.17.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.17.3.1 General | The following information flows are specified for tethered VAL connectivity performance analytics based on 8.17.2. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.17.3.2 Tethered VAL connectivity performance analytics subscription request | Table 8.17.3.2-1 describes information elements for the tethered VAL connectivity performance analytics subscription request from the VAL server / Consumer to the ADAE server.
Table 8.17.3.2-1: Tethered VAL connectivity performance analytics subscription request
Information element
Status
Description
Consumer ID
M
The identifier of the analytics consumer
Analytics ID
M
The identifier of the analytics event. This ID can be for example “tethered VAL connectivity performance analytics”.
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions.
VAL service ID
M
The identifier of the VAL service for which analytics subscription apply.
Target tethered VAL UE ID(s)
O
The tethered VAL UE(s) for which the analytics subscription applies.
Target VAL server ID
O
If consumer is different from the VAL server, this identifier shows the target VAL server for which the analytics subscription applies.
Target data producer profile criteria
O
Characteristics of the data producers to be used.
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction.
Area of Interest
O
The geographical or service area for which the subscription request applies.
Time validity
O
The time validity of the subscription request
Reporting requirements
O
It 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. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.17.3.3 Tethered VAL connectivity performance analytics subscription response | Table 8.17.3.3-1 describes information elements for the Tethered VAL connectivity performance analytics subscription response from the ADAE server to the consumer/VAL server.
Table 8.17.3.3-1: VAL performance analytics subscription response
Information element
Status
Description
Result
M
The result of the analytics subscription request (positive or negative acknowledgement). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 8.18 Procedure for supporting DN Energy Efficiency analytics |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.