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.3 Procedure on support for slice-specific application performance analytics 8.3.1 General 8.3.2 Procedure 8.3.3 Information flows 8.3.3.1 General 8.3.3.2 Slice-specific performance analytics subscription request 8.3.3.3 Slice-specific performance analytics subscription response 8.3.3.4 Slice-specific performance analytics notification
...

8.3 Procedure on support for slice-specific application performance analytics p. 31

8.3.1 General p. 31

This clause describes the procedure for supporting slice-specific application performance analytics. The ADAES service consumer can subscribe and receive notifications about slice specific application performance analytics events. In case that the ADAES consumer needs information about historical data, the procedure in clause 8.7.3 can be used for retrieving of slice-specific application performance metrics data about a specific area and time window in the past.

8.3.2 Procedure p. 31

Figure 8.3.2-1 illustrates the procedure where the VAL server performance analytics are performed based on data collected from the ongoing VAL sessions as well as data from the DN (VAL server, DN database or networking stack at DN) for a specific slice.

Pre-conditions:

ADAEC is connected to ADAES.

Reproduction of 3GPP TS 23.436, Fig. 8.3.2-1: ADAES support for slice-related performance analytics

Figure 8.3.2-1: ADAES support for slice-related 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. "slice perf prediction", the target S-NSSAI, DNN, NSI ID, the time validity of the request, the required confidence level, whether offline and/or online analytics are needed, area and time horizon, etc.

Step 2.

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

Step 3.

The ADAES subscribes to the Data Sources with the respective Data Collection Event ID and the requirement for data collection related to the request slice(s). Such requests may be towards:

OAM for providing PM data related to the requested slice / NSI. Alternatively, if the interaction to OAM happens via NSCE layer (see TS 23.435), such subscription can be performed to NSCE (where ADAES is acting as VAL server).
NWDAF for providing slice related analytics for the given area and time horizon (indicated in step 1). Such analytics can be the slice load level related network data analytics, or the service experience related network data analytics for a given slice

Step 4.

The ADAES based on subscription, receives PM data notification from OAM or from NSCE server (via OAM APIs or NSCE-S APIs)

Step 5.

The ADAES based on subscription, receives the requested NWDAF analytics outputs. Such analytics can be:

network slice or NSI statistics or predictions (clause 6.3.3A of TS 23.288)
per slice instance service experience stats or predictions (clause 6.4.3 of TS 23.288)

Step 6.

The ADAES can also provide analytics on the VAL session performance (based on the procedure of clause 8.2.2 step 11 or clause 8.2.3 step 12) and filters the analytics only for the sessions which are connected to that requested slice for the area of interest.

Step 7.

The ADAES abstracts or correlates the data/analytics from steps 4-6 and provides analytics on the slice or NSI performance for the target VAL application/server. For example, such analytics can be about the min/average/max predicted RTT / end to end latency for the VAL application/server if this server uses a given slice/NSI (or for a list of given slices) within an area of interest.

Step 8.

The ADAES sends the analytics to the consumer, as a slice-specific performance analytics notification message.

8.3.3 Information flows p. 33

8.3.3.1 General p. 33

The following information flows are specified for slice-specific application performance analytics based on clause 8.3.2.

8.3.3.2 Slice-specific performance analytics subscription request p. 33

Table 8.3.3.2-1 describes information elements for the slice-specific performance analytics subscription request from the consumer (VAL server / NSCE server) to the ADAE server.

Table 8.3.3.2-1: Slice-specific performance analytics subscription request

Information element	Status	Description
Consumer ID	M	The identifier of the analytics consumer.
Analytics ID	O	The identifier of the analytics event. This ID can be for example "slice-specific application performance analytics".
Analytics type	M	The type of analytics for the event, e.g. statistics or predictions.
Slice identifier	M	The identifier of the target slice or slice instance, i.e. S-NSSAI, NSI ID or ENSI.
DNN	O	The target DNN for which the request applies.
Target VAL UE ID(s)	O	The 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 (for procedure in clause 8.2.2).
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.
Time horizon	O	The time horizon for predictive analytics.
> Start time	O	The start time point of predictive validity. If omitted, the default value is the current time.
> End time	M	The end time point of predictive validity.
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.3.3.3 Slice-specific performance analytics subscription response p. 33

Table 8.3.3.3-1 describes information elements for the slice-specific performance analytics subscription response from the ADAE server to the consumer (VAL/NSCE server).

Table 8.3.3.3-1: Slice-specific performance analytics subscription response

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

8.3.3.4 Slice-specific performance analytics notification p. 34

Table 8.3.3.4-1 describes information elements for the slice-specific performance analytics notification from the ADAE server to the Consumer.

Table 8.3.3.4-1: Slice-specific performance analytics notification

Information element	Status	Description
Analytics ID	O	The identifier of the analytics event. This ID can be for example "slice-specific application performance analytics".
Analytics Output	M	The predictive or statistical parameter, which can be for a target slice or slice instance the: A VAL server predicted or expected performance change or sustainability A VAL session predicted or expected performance change of sustainability
Confidence level	O (NOTE)	For predictive analytics, the achieved confidence level.
Time horizon	O (NOTE)	The time horizon for predictive analytics.
> Start time	O	The start time point of predictive validity. If omitted, the default value is the current time.
> End time	M	The end time point of predictive validity.
NOTE: These information elements shall be provided for the predictive analytics.