Content for  TS 23.436  Word version:  19.3.0

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".

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

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.

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.

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 of 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.

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.

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.

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.

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.

The ADAES sends the derived analytics notification to the consumer (e.g., VAL server or any other authorized AF consumer).