6.14 DN Performance Analytics

23.2883GPPArchitecture enhancements for 5G System (5GS) to support network data analytics servicesRelease 18TS

6.14.1 General

This clause specifies how an NWDAF can provide DN Performance Analytics which provides analytics for user plane performance (i.e. average/maximum traffic rate, average/maximum packet delay, average packet loss rate) in the form of statistics or predictions to a service consumer.

The DN Performance Analytics may provide one or a combination of the following information:

– User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific serving anchor UPF.

– User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific DNAI.

– User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific Edge Application Server Instance.

The service consumer may be an NF (e.g. SMF) or an AF.

The consumer of these analytics shall indicate in the request or subscription:

– Analytics ID = "DN Performance";

– Target of Analytics Reporting: one or more SUPI(s) or Internal Group Identifier(s), or "any UE";

– Analytics Filter Information as defined in table 6.14.1-1; and

– optionally, a preferred level of accuracy of the analytics;

– optionally, preferred level of accuracy per analytics subset (see clause 6.14.3);

– optionally, preferred order of results for the list of Network Performance information:

– ordering criterion: one of the analytics subset (see clause 6.14.3);

– order: ascending or descending;

– optionally, Reporting Thresholds, which apply only for subscriptions and indicate conditions on the level to be reached for respective analytics subsets (see clause 6.14.3) in order to be notified by the NWDAF;

– optionally, maximum number of objects and maximum number of SUPIs;

– An Analytics target period indicates the time period over which the statistics or predictions are requested.

Table 6.14.1-1: Analytics Filter Information related to DN Performance Analytics

Information

Description

Application ID (0..max)

The identification of the application(s) for which the analytics information is subscribed or requested.

S-NSSAI

Identifies the Network Slice for which analytics information is subscribed or requested.

NSI ID(s)

Identifies the Network Slice instance(s) for which analytics information is subscribed or requested.

Area of Interest

Identifies the Area (i.e. set of TAIs), as defined in TS 23.501 [2] for which the analytics information is subscribed or requested.

Anchor UPF info

Identifies the UPF where a UE has an associated PDU session.

DNN

DNN to access the application.

DNAI

The UPF ID/address/FQDN information identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501 [2].

Application Server Address(es)

List of IP address(s)/FQDN(s) of the Application Server(s) that a UE, group of UEs, or ‘any UE’ has a communication session with for which DN Performance Analytic information is requested.

List of analytics subsets

List of analytics subsets that are requested among those specified in clause 6.14.3.

NOTE: All parameters are optional.

6.14.2 Input Data

The data collected from the AF are defined in table 6.14.2-1

Table 6.14.2-1: Performance Data from AF

Information

Source

Description

UE identifier

AF

IP address of the UE at the time the measurements was made.

UE location

AF

The location of the UE when the performance measurement was made.

Application ID

AF

To identify the service and support analytics per type of service (the desired level of service).

IP filter information

AF

Identify a service flow of the UE for the application.

Locations of Application

AF/NEF

Locations of application represented by a list of DNAI(s). The NEF may map the AF-Service-Identifier information to a list of DNAI(s) when the DNAI(s) being used by the application are statically defined.

Application Server Instance address

AF/NEF

The IP address/FQDN of the Application Server that the UE had a communication session when the measurement was made.

UL/DL Performance Data

AF

The performance associated with the communication session of the UE with an Application Server that includes: Average/Maximum Packet Delay, Average/Maximum Loss Rate and Average/Minimum/Maximum Throughput.

Timestamp

AF

A time stamp associated to the Performance Data provided by the AF.

The data collected by the SMF are described in table 6.4.2-2.

The NWDAF subscribes to network data as defined in clause 6.4.2.

Data may be collected from OAM as described in table 6.4.2-3 by using the services provided by OAM as described in clause 6.2.3.

The Event Filters for the service data collection from SMF, AMF and AF are defined in TS 23.502 [3].

The timestamps are provided by each NF to allow correlation of QoS and traffic KPIs. The clock reference is able to know the accuracy of the time and correlate the time series of the data retrieved from each NF.

6.14.3 Output Analytics

The DN performance analytics is shown in table 6.14.3-1 and table 6.14.3-2.

Table 6.14.3-1: DN service performance statistics

Information

Description

Application ID

Identifies the application for which analytics information is provided.

S-NSSAI

Identifies the Network Slice for which analytics information is provided. See note 1.

DNN

Identifies the data network name (e.g. "internet") for which analytics information is provided. See NOTE 1.

DN performance (0-x)

List of DN performances for the application.

> Application Server Instance Address

Identifies the Application Server Instance (IP address/FQDN of the Application Server).

> Serving anchor UPF info

The UPF ID/address/FQDN information for the involved anchor UPF. See NOTE 1.

> DNAI

Identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501 [2].

> Performance

Performance indicators.

>> Average Traffic rate (NOTE 2)

Average traffic rate observed for UEs communicating with the application.

>> Maximum Traffic rate (NOTE 2)

Maximum traffic rate observed for UEs communicating with the application.

>> Minimum Traffic rate (NOTE 3)

Minimum traffic rate observed for UEs communicating with the application.

>> Average Packet Delay (NOTE 2)

Average packet delay observed for UEs communicating with the application.

>> Maximum Packet Delay (NOTE 2)

Maximum packet delay for observed for UEs communicating with the application.

>> Average Packet Loss Rate (NOTE 2)

Average packet loss observed for UEs communicating with the application.

>> Maximum Packet Loss Rate (NOTE 2)

Maximum packet loss observed for UEs communicating with the application.

> Spatial Validity Condition

Area where the DN performance analytics applies.

> Temporal Validity Condition

Validity period for the DN performance analytics.

NOTE 1: The item "Serving anchor UPF info" shall not be included if the consumer NF is an AF.

NOTE 2: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds".

NOTE 3: Minimum traffic rate measurements are only derived from active traffic.

Table 6.14.3-2: DN service performance predictions

Information

Description

Application ID

Identifies the application for which analytics information is provided.

S-NSSAI

Identifies the Network Slice for which analytics information is provided. See NOTE 1.

DNN

Identifies the data network name (e.g. internet) for which analytics information is provided. See NOTE 1.

DN performance (0-x)

List of DN performance for the application.

> Application Server Instance Address

Identifies the Application Server Instance (IP address/FQDN of the Application Server).

> Serving anchor UPF info

The UPF ID/address/FQDN information for the involved anchor UPF. See NOTE 1.

> DNAI

Identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501 [2].

> Performance

Performance indicators

>> Average Traffic rate (NOTE 2)

Average traffic rate predicted for UEs communicating with the application.

>> Maximum Traffic rate (NOTE 2)

Maximum traffic rate predicted for UEs communicating with the application.

>> Minimum Traffic rate (NOTE 3)

Minimum traffic rate predicted for UEs communicating with the application.

>> Average Packet Delay (NOTE 2)

Average packet delay predicted for UEs communicating with the application.

>> Maximum Packet Delay (NOTE 2)

Maximum packet delay for predicted for UEs communicating with the application.

>> Average Packet Loss Rate (NOTE 2)

Average packet loss predicted for UEs communicating with the application.

>> Maximum Packet Loss Rate (NOTE 2)

Maximum packet loss predicted for UEs communicating with the application.

> Spatial Validity Condition

Area where the DN performance analytics applies.

> Temporal Validity Condition

Validity period for the DN performance analytics.

> Confidence

Confidence of this prediction.

NOTE 1: The item "Serving anchor UPF info" shall not be included if the consumer is an AF.

NOTE 2: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds".

NOTE 3: Minimum traffic rate measurements are only derived from active traffic.

6.14.4 Procedures to request DN Performance Analytics for an Application

Figure 6.14.4-1: Procedure for NWDAF providing DN Performance analytics for an Application

The procedure illustrated in figure 6.14.4-1 allows an analytics consumer to request Analytics ID "DN Performance" for a particular Application. The analytics consumer includes the Application ID for which DN Performance is requested. The consumer indicates the Target of Analytics Reporting (e.g. "any UE") and may include as Analytic Filter Information the UPF anchor ID, DNAI, or Application Server instance that DN performance analytics are requested.

1. Analytics consumer sends an Analytics request/subscribe (Analytics ID = DN Performance Target of Analytics Reporting, Analytics Filter Information = (Application ID, S-NSSAI, DNN, Area of Interest, UPF anchor ID, DNAI, Application Server Address(es)), Analytics Reporting Information = Analytics target period) to NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request or a Nnwdaf_AnalyticsSubscription_Subscribe service.

2a. NWDAF subscribes to the performance data from AF defined in table 6.14.2-1 by invoking Nnef_EventExposure_Subscribe or Naf_EventExposure_Subscribe service (Event ID = Performance Data, Application ID, Event Filter information), Target of Event Reporting = Any UE) as defined in TS 23.502 [3].

NOTE 1: In the case of trusted AF, NWDAF provides the Area of Interest as a list of TAIs to AF. In the case of untrusted AF, NEF translates the requested Area of Interest provided as event filter by NWDAF into geographic zone identifier(s) that act as event filter for AF.

2b. NWDAF subscribes to the network data from 5GC NF(s) defined in table 6.4.2-2 by invoking Nnf_EventExposure_Subscribe service.

2c. With the collected data, the NWDAF estimates the DN Performance for the application.

3. NWDAF provides the data analytics, to the analytics consumer by means of either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.

NOTE 2: For simplicity, the call flow only shows a request-response model for the interaction of NWDAF and analytics consumer instead of both request-response model and subscription-notification model.

If the analytics consumer is an SMF, the SMF may use the analytics to determine the UPF and DNAI that offers the best user plane performance.

If the analytics consumer is an AF, the AF may use the analytics to determine the DNAI that has the best user plane performance if Application Server relocation is required.