hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
8.18.1 General
|
This clause describes the procedure for DN energy consumption/efficiency analytics, where the analytics are performed based on data collected from one or more DNs and A-ADRF.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
8.18.2 Procedure
|
Figure 8.18.2-1 illustrates the procedure for DN energy efficiency analytics enablement solution.
Pre-conditions:
1. Data producers (e.g. A-ADRF, EAS, EES) may be pre-configured with data producer profiles (as in Table 8.2.4.8-1) for the data they can provide. ADAES has discovered available data producers and their data producer profiles.
Figure 8.8.2.1-1: ADAES support for DN energy analytics
1. The VAL server sends a DN energy analytics request to ADAES to perform analytics on the DN Energy Consumption/Efficiency for one or more DNs/EDNs, Event ID= “DN energy analytics”, for a given DN service area (or subarea) and a given time window.
2. The ADAES authorizes the VAL request.
3. The ADAES requests and receives from the EAS /VAL servers hosted at the serving and target DNs (within the VAL service area), expected application service load and traffic schedules for the ongoing or future sessions within the area. Such data include traffic schedule report for the VAL Server, and this step re-uses the step 3 to 10 of clause 8.8.2.1.
4. The ADAES calculates the expected energy consumption or efficiency based on the received traffic and load data for the given DNN/DNAI based on the request.
NOTE: How the collected data are used to calculate energy efficiency metric is up to implementation.
5. The ADAES obtains the corresponding trained ML model based on procedure in 3GPP TS 23.482 clause 8.3.2 and performs analytics to derive the predicted energy consumption at the target area and time horizon. The analytics outputs can be the predicted energy consumption / efficiency for the given DNN/DNAI.
6. The ADAES sends a DN energy analytics response with the energy consumption/efficiency analytics output data to the VAL server.
Based on 6, the VAL server can use these analytics as input to trigger pro-actively:
- an application server migration to a different edge cloud or to a centralized cloud as a way of reducing the energy consumption for the edge (if consumption is expected to be very high (e.g. higher than a pre-configured threshold)).
- an application server offboarding and the instantiation of a new server at the target edge/centralized cloud to minimize energy consumption of the edge platform (taking into account the system wide energy efficiency).
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
8.18.3 Information flows
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
8.18.3.1 General
|
The following information flows are specified for DN energy analytics based on clause 8.18.2.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
8.18.3.2 DN energy analytics request
|
Table 8.18.3.2-1 describes information elements for the DN energy analytics request from the VAL server to the ADAE server.
Table 8.8.3.2-1: DN energy analytics request
Information element
Status
Description
Analytics Consumer ID
M
The identifier of the analytics consumer (VAL server, EAS).
Analytics ID
M
The identifier of the analytics event. This ID can be for example “edge performance analytics”.
Analytics type
M
The type of analytics for the event, e.g. statistics or predictions.
DNN/DNAI
M
DNN or DNAIs information for which the subscription applies.
Energy Efficiency/Consumption metrics
O
The formula and necessary metrics for calculating the EE based on load and traffic information per DN.
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 the energy 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.18.3.3 DN energy analytics response
|
Table 8.18.3.3-1 describes information elements for the DN energy analytics request from the VAL server to the ADAE server.
Table 8.18.3.3-1: DN energy analytics response
Information element
Status
Description
Result
M
The result of the analytics request (positive or negative acknowledgement).
Analytics ID
O
The identifier of the analytics event.
Analytics Output
O
The predictive or statistical parameter, which can be stats or prediction related to the energy consumption or efficiency for the edge platform for a given area/time and based on the event type.
> DNN
M
Identifies the data network name for which analytics information is provided.
> DNAI
M
Identifier of a user plane access to one or more DN(s) of the DN.
> Energy metrics
O
The predicted energy metrics.
>> Energy Consumption (NOTE)
O
The predicted energy consumption per DNAI based on network and edge resource usage
>> Energy Efficiency (NOTE)
O
The energy efficiency per DNAI based on network and edge resource usage (given a certain optimal energy consumption metric, which can be pre-configured).
>> DN Data Volume (NOTE)
O
The predicted data volume per DNAI.
> Area of Interest
O
The area (topological or geographical or edge area) where the analytics apply.
> Applicable time period
O
The time period that the analytics applies to.
>Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
NOTE: At least one of these shall be present.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
8.19 Procedure for ML Model Performance Degradation Detection
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
8.19.1 General
|
This clause describes a procedure for ML model performance degradation detection for supporting application layer AI/ML operations.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
8.19.2 Procedure
|
Pre-conditions:
- An ADAE Server, acting as an AIMLE consumer, receives a trained ML model (or ML model information) from the AIMLE Server.
Figure 8.19.2-1: ADAES supports for ML model performance degradation detection
1. The ADAE Server receives a request from the consumer for analytics, generates analytics by using the ML model provided by AIMLE Server, and responds/notifies to the consumer with the required analytics.
2. The ADAE Server requests the consumer to provide feedback on the usage of the analytics.
3. The consumer uses the analytics for its operations and collects operation results. Performance degradation may be found from the operation results. The performance degradation may be caused by e.g., insufficient analytics accuracy, or the current analytics cannot fulfill the changed conditions at the consumer.
4. The consumer provides feedback on the result of usage of the analytics to the ADAE Server.
5. The ADAE Server updates the analytics accuracy based on feedback information from the consumer, and checks the performance of the ML model, which is used to generate the analytics, e.g., performance degradation of the ML model.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9 ADAE layer APIs
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.1 General
|
The following ADAE capabilities are offered as APIs:
- ADAE server APIs;
- A-ADRF APIs;
The following SEAL service APIs are specified in 3GPP TS 23.434 [2] (and TS 23.435 [6] for NSCE):
- Group management server APIs;
- Location management server APIs;
- Configuration management server APIs;
- Identity management server APIs;
- Key management server APIs; and
- Network slice capability enablement APIs.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2 ADAE server APIs
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.1 General
|
This clause provides the APIs provided by ADAES.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.2 ADAE server APIs
|
Table 9.2.2-1 illustrates the ADAE server APIs.
Table 9.2.2-1: List of ADAE server APIs
API Name
API Operations
Known Consumer(s)
Communication Type
SS_ADAE_VAL_performance_analytics
Subscribe
VAL server
Subscribe/Notify
Notify
SS_ADAE_slice_performance_analytics
Subscribe
VAL server
Subscribe/Notify
Notify
SS_ADAE_UE-to-UE_performance_analytics
Subscribe
VAL server
Subscribe/Notify
Notify
SS_ADAE_server-to-server_performance_analytics
Subscribe
VAL server / EES
Subscribe/Notify
Notify
SS_ADAE_location_accuracy_analytics
Subscribe
VAL server
Subscribe/Notify
Notify
SS_ADAE_service_API_analytics
Subscribe
VAL server / Subscriber/ API invoker
Subscribe/Notify
Notify
SS_ADAE_slice_usage_pattern_analytics
Subscribe
VAL server / SEAL server
Subscribe/Notify
Notify
SS_ADAE_edge_analytics
Subscribe
VAL server / EAS / EES
Subscribe/Notify
Notify
Get
VAL server / EAS / EES
Request / Response
SS_ADAES_slice_usage_stats
Get
VAL server
Request / Response
SS_ADAES_edge_preparation_analytics
Subscribe
VAL server / ECS / EES
Subscribe/Notify
Notify
Get
VAL server / ECS / EES
Request / Response
SS_ADAE_collision_detection_analytics
Subscribe
VAL server / LM server / UAE server, UAS application specific server
Subscribe/Notify
Notify
Get
VAL server / LM server / UAE server, UAS application specific server
Request / Response
SS_ADAE_location-related_UE_group_analytics
Subscribe
LM server
Subscribe/Notify
Notify
Get
LM server
Request / Response
SS_ ADAE_AIML_member_capability_analytics
Subscribe
VAL server / AIMLE server
Subscribe/Notify
Notify
Get
VAL server / AIMLE server
Request / Response
SS_ ADAE_ServiceExp
Request
ADAE client
Request / Response
SS_ADAE_DN_energy_analytics
Get
VAL server / EAS / EES
Request / Response
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.3 SS_ ADAE_VAL_performance_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.3.1 General
|
API description: This API enables the VAL server to communicate with the ADAE server for subscribing for VAL performance analytics and for getting notified on the result.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.3.2 Subscribe
|
API operation name: VAL_performance_analytics_subscribe
Description: The consumer subscribes for VAL performance analytics.
Inputs: See clause 8.2.4.2.
Outputs: See clause 8.2.4.3.
See clause 8.2.2 and 8.2.3 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.3.3 Notify
|
API operation name: VAL_performance_analytics_notify
Description: The consumer is notified by ADAES on the VAL performance analytics.
Inputs: -
Outputs: See clause 8.2.4.7.
See clause 8.2.2 and 8.2.3 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.4 SS_ ADAE_slice_performance_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.4.1 General
|
API description: This API enables the VAL server to communicate with the ADAE server for subscribing for slice specific application performance analytics and for getting notified when analytics are derived.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.4.2 Subscribe
|
API operation name: slice_performance_analytics_subscribe
Description: The consumer subscribes for slice specific performance analytics.
Inputs: See clause 8.3.3.2.
Outputs: See clause 8.3.3.3.
See clause 8.3.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.4.3 Notify
|
API operation name: slice_performance_analytics_notify
Description: The consumer is notified by ADAES on the slice specific performance analytics.
Inputs: -
Outputs: See clause 8.3.3.4.
See clause 8.3.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.5 SS_ ADAE_UE-to-UE_performance_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.5.1 General
|
API description: This API enables the VAL server to communicate with the ADAE server for subscribing for UE-to-UE session performance analytics and for getting notified when analytics are derived.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.5.2 Subscribe
|
API operation name: UE-to-UE performance_analytics_subscribe
Description: The consumer subscribes for UE-to-UE performance analytics.
Inputs: See clause 8.4.3.2.
Outputs: See clause 8.4.3.3.
See clause 8.4.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.5.3 Notify
|
API operation name: UE-to-UE performance_analytics_notify
Description: The consumer is notified by ADAES on the slice specific performance analytics.
Inputs: -
Outputs: See clause 8.4.3.6.
See clause 8.4.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.6 SS_ ADAE_location_accuracy_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.6.1 General
|
API description: This API enables the VAL server to communicate with the ADAE server for subscribing for location accuracy analytics and for getting notified when analytics are derived.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.6.2 Subscribe
|
API operation name: Location_accuracy_analytics_subscribe
Description: The consumer subscribes for location accuracy analytics.
Inputs: See clause 8.5.3.2.
Outputs: See clause 8.5.3.3.
See clause 8.5.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.6.3 Notify
|
API operation name: Location_accuracy_analytics_notify
Description: The consumer is notified by ADAES on the location accuracy analytics.
Inputs: -
Outputs: See clause 8.5.3.6.
See clause 8.5.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.7 SS_ ADAE_service_API_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.7.1 General
|
API description: This API enables the VAL server to communicate with the ADAE server for subscribing for service API analytics and for getting notified when analytics are derived.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.7.2 Subscribe
|
API operation name: Service_API_analytics_subscribe
Description: The consumer subscribes for service API analytics.
Inputs: See clause 8.6.3.2.
Outputs: See clause 8.6.3.3.
See clause 8.6.2 for details of usage of this operation.
9.2.6.3 Notify
API operation name: Service_API_analytics_notify
Description: The consumer is notified by ADAES on the location accuracy analytics.
Inputs: -
Outputs: See clause 8.6.3.6.
See clause 8.6.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.8 SS_ADAE_slice_usage_pattern_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.8.1 General
|
API description: This API enables the VAL server to communicate with the ADAE server for subscribing for slice usage pattern analytics and for getting notified when analytics are derived.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.8.2 Subscribe
|
API operation name: slice_usage_pattern_analytics_subscribe
Description: The consumer subscribes for slice usage pattern analytics.
Inputs: See clause 8.7.3.2.
Outputs: See clause 8.7.3.3.
See clause 8.7.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.8.3 Notify
|
API operation name: slice_usage_pattern_analytics_notify
Description: The consumer is notified by ADAES on the slice usage pattern analytics.
Inputs: -
Outputs: See clause 8.7.3.4.
See clause 8.7.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.9 SS_ ADAE_edge_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.9.1 General
|
API description: This API enables the VAL server to communicate with the ADAE server for subscribing for edge load analytics and for getting notified when analytics are derived.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.9.2 Subscribe
|
API operation name: edge_analytics_subscribe
Description: The consumer subscribes for edge load analytics.
Inputs: See clause 8.8.3.2.
Outputs: See clause 8.8.3.3.
See clause 8.8.2 for details of usage of this operation.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.