Content for  TS 23.436  Word version:  19.3.0

The ADAE client determines the service experience information based on information received from the VAL client. The service experience information includes application specific performance measurements like end-to-end response time, connection bandwidth, request rate, server availability time, etc. On request from VAL client or any other trigger conditions, the ADAE client sends the service experience report about a VAL server to the ADAE server. The ADAE client may use the direct reporting mechanism as defined in clause 5.5 of TS 26.531. The indirect reporting procedure (between ADAE client and ADAE server over ADAE-UU interface) may be used when a Direct Data Collection Client is not available in the UE or when the ADAE server (having Indirect Data Collection Client) needs to modify the collected UE data to satisfy the requirements of its data collection and reporting configuration. The information elements as defined in clause 8.9.3.1 are used by ADAE client to send the request and clause 8.9.3.2 are used by ADAE server to send the response. For direct reporting, if data reporting session is not available, the ADAE client creates data reporting session as specified in clause 5.4 of TS 26.531. Once data reporting session is available, the ADAE client (acting as a UE client) sends reports to ADAE server using direct reporting method as specified in clause 5.5 of TS 26.531. For indirect reporting, Figure 8.9.2.1-1 illustrates the procedure where the ADAE client pushes the service experience information to the ADAE server.

Once UE data is collected (either using direct reporting or indirect reporting), the ADAE server may take further actions based on the analysis of the report as shared by the ADAE client. A service experience information from certain UEs, can trigger the ADAE server to fetch further service experience information from other UEs. The ADAE server can use the service experience information report from other UEs to determine/predict analytics.

• If most of the UE side entities report similar service experience, then it could be the application server problem across globally.
• If only some UEs report a bad service experience, the problem could be localized among a group of UEs.
• If the bad service experience from only one UE, the problem is localized to the UE.

The procedure can be initiated by the ADAE server upon receiving a service experience from an ADAE client, to fetch service experience information from other ADAE clients or upon receiving VAL server performance analytics request from application service provider (application server) or any other event that requires the ADAE server to determine the service experience data.

The ADAE server configures triggers to the ADAE client to send the service experience report using the mechanism defined in clause 5.4 of TS 26.531. The procedure can be initiated by the ADAE server upon receiving VAL server performance analytics request from application service provider (application server). The information elements as defined in clause 8.9.3.5 are used by ADAE server to send the request and clause 8.9.3.6 are used by ADAE client to send the response.

Table 8.9.3.1-1 describes information elements for the Push service experience information request from the ADAE client to the ADAE server.

Table 8.9.3.2-1 describes information elements for the Push service experience information response from the ADAE server to the ADAE client.

Table 8.9.3.3-1 describes information elements for the Pull service experience information request from the ADAE server to the ADAE client.

Table 8.9.3.4-1 describes information elements for the Pull service experience information response from the ADAE client to the ADAE server.

Table 8.9.3.5-1 describes information elements for the Configure service experience report trigger request from the ADAE server to the ADAE client.

Table 8.9.3.6-1 describes information elements for the Configure service experience report trigger response from the ADAE client to the ADAE server.