Content for  TS 23.288  Word version:  18.4.0

This clause specifies the procedure on how NWDAF can provide NWDAF-assisted PFD Determination analytics, in the form of statistics. To assist determination of PFDs 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 or updated PFDs, e.g. IP 3-tuple list in PFD is new or updated, to an analytics consumer in the 5GC. The NEF(PFDF) as the consumer may forward new or updated PFD information provided by the NWDAF to the UPF via the SMF to detect a known application, as defined in TS 23.502. The service consumer may be a NEF(PFDF). The consumer of these analytics shall indicate in the request or subscription:

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

The NWDAF collects information on user data traffic from NF(s) for a specific S-NSSAI, DNN, Application ID and retrieves the existing PFDs from the NEF(PFDF). The detailed input 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 may be used to provision new or updated PFDs information for known applications. The NWDAF may assign a confidence to the PFD Determination statistics based on the input data provided by UPF.

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