Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.436  Word version:  19.2.0

Top   Top   Up   Prev   Next
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.13 Procedure on support for server-to-server performance analytics  8.13.1 General  8.13.2 Procedure  8.13.3 Information flows 
...

 

8.13  Procedure on support for server-to-server performance analytics |R19|  p. 76

8.13.1  General  p. 76

This clause describes the procedure for server-to-server performance analytics.

8.13.2  Procedure  p. 76

Figure 8.13.2.1-1 illustrates the procedure for server-to-server performance analytics.
Pre-conditions:
  1. ADAES is connected to A-ADRF and the target server (server#1).
Reproduction of 3GPP TS 23.436, Fig. 8.13.2.1-1: ADAES support for server-to-server performance analytics
Figure 8.13.2.1-1: ADAES support for server-to-server performance analytics
Up
Step 1.
The analytics consumer (e.g., VAL server, EES) of the ADAE server analytics service sends a server-to-server analytics subscription request to the ADAE server. Such request can include whether the analytics notification shall be periodic or based on an expected application QoS change (in that case also the thresholds can be provided at the request)
Step 2.
The ADAE server sends a server-to-server analytics subscription response as an ACK to the analytics consumer.
Step 3.
The ADAE server identifies server#1 where the session performance analytics need to be performed. The ADAES server sends an Inter-server data request to server #1. Such request includes QoS attributes to be analysed (latency, bitrate, jitter, application layer PER) based on the request in step 1.
Step 4.
Bases on the request, measurement may be started between the server#1 and server#2. Such data can be about the latency, throughput, jitter, QoE measurements, PQI load, etc.
Step 5.
Server#1 sends the analytics to the ADAE server in an Inter-server data response message.
Step 6.
The ADAE server requests historical inter-server performance analytics from A-ADRF by sending a Server-to-server analytics request.
Step 7.
Based on the request, the ADAE server receives historical inter-server performance analytics by receiving a Server-to-server analytics response from A-ADRF.
Step 8.
The ADAE server abstracts or correlates the data/analytics from step 5-7. Based on the request in step 1, ADAES may also provide predictions for performance change.
Step 9.
The ADAE server sends a server-to-server analytics notification to the analytics consumer.
Up

8.13.3  Information flows  p. 77

8.13.3.1  General  p. 77

The following information flows are specified for server-to-server performance analytics based on clause 8.13.2.

8.13.3.2  Server-to-server performance analytics subscription request  p. 77

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.
Information element Status Description
Analytics Consumer IDMThe identifier of the analytics consumer (VAL server, EES etc.).
Analytics IDO The identifier of the analytics event. This ID can be for example "server-to-server performance analytics".
Analytics typeMThe type of analytics for the event, e.g. statistics or predictions.
List of server identifiers and addressesMIdentifier of the servers, e.g. SEAL server ID, EASID, EESID, and IP address(es) for which the analytics subscription applies.
VAL service IDOThe VAL service for which the subscription applies.
Reporting requirementsORequirements 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 InterestOThe geographical or service area for which the subscription request applies.
Preferred confidence levelOThe level of accuracy for the analytics service (in case of prediction).
Time validityOThe time validity of the subscription request.
Up

8.13.3.3  Server-to-server performance analytics subscription response  p. 77

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.
Information element Status Description
ResultMThe result of the analytics subscription request (positive or negative acknowledgement).
Up

8.13.3.4  Server-to-server performance analytics notification  p. 78

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.
Information element Status Description
Analytics IDO The identifier of the analytics event. This ID can be for example "server-to-server performance analytics".
Analytics OutputMThe 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 levelOFor predictive analytics, the achieved confidence level can be provided.
Up

8.13.3.5  Inter-server session data request  p. 78

Table 8.13.3.5-1 describes information elements for the Inter-server session data request from the target server to the ADAE server.
Information element Status Description
ADAE server IDMThe identifier of the ADAE server.
Analytics IDO The identifier of the analytics event. This ID can be for example "Server-to-server performance analytics".
Analytics typeMWhether analytics event is about prediction or statistics.
List of server identifiers and addressesMIdentifier of the servers, e.g. SEAL server ID, EASID, EESID, and IP address(es) for which the analytics subscription applies.
QoS attributesMThe QoS attributes (latency, bitrate, jitter, application layer PER) to be collected.
Data collection requirementsOThe 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 validityOThe time validity of the request.
Up

8.13.3.6  Inter-server session data response  p. 78

Table 8.13.3.6-1 describes information elements for the Inter-server session data response from the ADAE server to the target server.
Information element Status Description
ResultsMThe result of the analytics data request (positive or negative acknowledgement).
Analytics IDOThe identifier of the analytics event.
List of server identifiers and addressesOIdentifier of the servers, e.g. SEAL server ID, EASID, EESID, and IP address(es) for which the analytics subscription applies.
Data OutputOThe 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.
Up

8.13.3.7  Server-to-server analytics request  p. 79

Table 8.13.3.7-1 describes information elements for the server-to-server analytics request from the ADAE server to the A-ADRF.
Information element Status Description
ADAE server IDMThe identifier of the ADAE server.
Analytics IDMThe identifier of the analytics event.
List of server identifiers and addressesMIdentifier of the servers, e.g. SEAL server ID, EASID, EESID, for which the analytics subscription applies.
QoS attributesMThe QoS attributes (latency, bitrate, jitter, application layer PER) to be collected.
Time validityOThe time validity of the request.
Up

8.13.3.8  Server-to-server analytics response  p. 79

Table 8.13.3.8-1 describes information elements for the server-to-server analytics response from the A-ADRF to the ADAE server.
Information element Status Description
Analytics IDMThe identifier of the analytics event.
List of server identifiers and addressesMIdentifier of the servers, e.g. SEAL server ID, EASID, EESID, for which the analytics subscription applies.
Data OutputMThe 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.
Up

Up   Top   ToC