Content for  TS 23.288  Word version:  18.0.0

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.

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

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

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

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

This clause specifies the procedure on how NWDAF can provide NWDAF-assisted PFD Determination analytics, in the form of statistics, to analytics To assist on PFD determination for known application identifiers, if the related Service Level Agreement does not preclude, an NWDAF may perform data analytics on existing PFD information and user plane traffic and provide analytics results in the form of new/updated PFDs to analytic consumer in the 5GC. The NEF(PFDF) as the consumer may forward new/updated PFD information provided by the NWDAF to UPF via SMF to detect a known application defined as TS 23.502. The service consumer may be a NEF(PFDF). The consumer of these analytics may indicate in the request:

• Analytics ID = " PFD Determination";
• Target of Analytics Reporting: "any UE";
• Application ID list;
• Analytics Filter Information optionally containing:
  • Area of Interest;
  • S-NSSAI;
  • DNN;
• An Analytics target period indicates the time period over which the statistics or predictions are requested;
• Optionally, maximum number of objects. This refers to the analytic output (i.e. maximum number of new/updated PFDs);
• In a subscription, the Notification Correlation Id and the Notification Target Address are included.

NWDAF collects QoS flow related data from NF(s) for a specific S-NSSAI, DNN, and UE(s). The detailed data are described in Table 6.16.2-1.

The output analytics of NWDAF is defined in Table 6.16.3-1. The output analysis can be used to provision new/updated PFDs for known applications.

The procedure depicted in Figure 6.16.4-1 shows the procedure that the NWDAF can provide PFD Detection analytics to a NEF (PFDF).