Content for TS 23.436 Word version: 19.2.0

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

8.4 Procedure on support for UE-to-UE application performance analytics 8.4.1 General 8.4.2 Procedure 8.4.3 Information flows 8.4.3.1 General 8.4.3.2 UE-to-UE session performance analytics subscription request 8.4.3.3 UE-to-UE session performance analytics subscription response 8.4.3.4 UE-to-UE analytics request 8.4.3.5 UE-to-UE analytics response 8.4.3.6 ADAE Analytics Notification
...

8.4 Procedure on support for UE-to-UE application performance analytics p. 34

8.4.1 General p. 34

This clause describes the procedure for supporting UE-to-UE application performance analytics.

8.4.2 Procedure p. 34

Figure 8.4.2-1 illustrates the procedure where the VAL session performance analytics are performed based on data collected from the ongoing VAL UE-to-UE sessions.

Pre-conditions:

ADAECs are connected to ADAES.

Reproduction of 3GPP TS 23.436, Fig. 8.4.2-1: ADAES support for UE-to-UE application performance analytics

Figure 8.4.2-1: ADAES support for UE-to-UE application performance analytics

Step 1.

The consumer of the ADAES analytics service sends a subscription request to ADAES and provides the analytics event ID e.g. "VAL UE to UE session prediction", the target VAL UE ID or group of UE IDs, the VAL session / service ID, the time validity and area of the request, the required confidence level, exposure level for providing UE to UE analytics. Such request can also 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)

Step 2.

The ADAES sends a subscription response as an ACK to the consumer.

Step 3.

The ADAES selects the corresponding ADAEC #1 of the VAL UE 1 where the session performance analytics need to be performed. Such UE can be for example a capable and authorized UE from the involved VAL UEs within the service or group, e.g. a group lead.

Step 4.

The ADAES sends a UE to UE analytics request to the ADAEC #1 with the analytics event ID and the configuration of the reporting required (e.g., periodic, based on threshold(s) or event). Such request also includes the application QoS attributes to be analyzed (latency, bitrate, jitter, application layer PER)A session starts between the VAL UE #1 and a VAL UE #2 (or more VAL UEs).

Step 5.

The ADAEC #1 starts collecting data from the corresponding VAL UE(s) based on the request. Such data can be about the latency, throughput, jitter, QoE measurements, PQI load, etc. The data can be collected by ADAEC #1 from other ADAECs via ADAE-C interface, or from the VAL clients (VAL client to VAL client interaction is out of scope).

Step 6.

The ADAEC either detects or predicts an application QoS change (depending on the authorization of ADAEC to perform analytics). Such change can be for example an application QoS downgrade related to the UE-to-UE session latency, or the application layer PER/channel losses higher than a predefined threshold, for a given time horizon with a certain confidence level.

Step 7.

The ADAEC sends the analytics to the ADAES in a UE-to-UE analytics response message.

Step 8.

The ADAES based on the received response, confirms/verifies the analytics received or provides analytics (in case that data were reported) for the UE-to-UE session. Such analytics can be about predicting the application QoS change for the UE-to-UE session.

Step 9.

The ADAES sends the derived analytics notification to the consumer.

8.4.3 Information flows p. 36

8.4.3.1 General p. 36

The following information flows are specified for UE-to-UE session performance analytics based on clause 8.4.2.

8.4.3.2 UE-to-UE session performance analytics subscription request p. 36

Table 8.4.3.2-1 describes information elements for the UE-to-UE session performance analytics subscription request from the consumer (VAL server) to the ADAE server.

Table 8.4.3.2-1: UE-to-UE session performance analytics subscription request

Information element	Status	Description
VAL server ID	M	The identifier of the analytics consumer (VAL server).
Analytics ID	O	The identifier of the analytics event. This ID can be equivalent to "UE-to-UE session performance analytics".
Analytics type	M	The type of analytics for the event, e.g. statistics or predictions.
List of VAL UE IDs and addresses	M	The VAL UEs for which the analytics subscription applies.
VAL service ID	O	The VAL service for which the subscription applies.
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.
Exposure level requirement	O	The level of exposure requirement (e.g. condition on providing the analytics like threshold is reached) for the analytics to be exposed.
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.

8.4.3.3 UE-to-UE session performance analytics subscription response p. 37

Table 8.4.3.3-1 describes information elements for the UE-to-UE session performance analytics subscription response from the ADAE server to the VAL server.

Table 8.4.3.3-1: UE-to-UE session performance analytics subscription response

Information element	Status	Description
Result	M	The result of the analytics subscription request (positive or negative acknowledgement).

8.4.3.4 UE-to-UE analytics request p. 37

Table 8.4.3.4-1 describes information elements for the UE-to-UE Analytics request from the ADAE server to the ADAE client.

Table 8.4.3.4-1: UE-to-UE analytics request

Information element	Status	Description
ADAE server ID	M	The identifier of the ADAE server.
Analytics ID	O	The identifier of the analytics event (Analytics ID='UE to UE session analytics').
List of VAL UE IDs and addresses	M	The VAL UE(s) identifiers and IP address(es) for which the data/analytics apply.
Application QoS attributes	M	The QoS attributes (latency, bitrate, jitter, application layer PER) to be analyzed at the ADAE client.
Reporting configuration	O	The configuration for analytics reporting. This requirement may include e.g. the frequency of reporting (periodic), the reporting periodicity in case of periodic, and reporting thresholds, whether data abstraction is needed or not.
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.
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.

8.4.3.5 UE-to-UE analytics response p. 37

Table 8.4.3.5-1 describes information elements for the UE-to-UE analytics response from the ADAE client to the ADAE server.

Table 8.4.3.5-1: UE-to-UE analytics response

Information element	Status	Description
Analytics ID	M	The identifier of the analytics event.
List of VAL UE IDs and addresses	M	The VAL UE(s) identifiers and IP address(es) for which the analytics apply.
Analytics Output	M	The reported analytics for the UE to UE sessions, which can be in form of offline stats/historical data or predictions on the requested QoS parameter based on the analytics event.

8.4.3.6 ADAE Analytics Notification p. 37

Table 8.4.3.6-1 describes information elements for the ADAE Analytics Notification from the ADAE server to the consumer (VAL server).

Table 8.4.3.6-1: ADAE Analytics notification

Information element	Status	Description
Analytics ID	O	The identifier of the analytics event. This ID can be "UE to UE session performance analytics".
Analytics Output	M	The predictive or statistical parameter, which can be: A VAL UE to UE session predicted or expected performance change A VAL UE to UE session performance sustainability over a given time horizon/area
Confidence level	O	For predictive analytics, the achieved confidence level can be provided.