6.16 PFD Determination Analytics

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

6.16.1 General

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 [3].

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.

6.16.2 Input Data

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.

Table 6.16.2-1: Input data to detect known application from NFs

Information	Source	Description
SUPI	SMF, UPF	UE ID for the UE that uses the application
S-NSSAI	SMF, UPF	Identifies the Network Slice for which analytics information is provided.
DNN	SMF, UPF	Identifies the data network name (e.g. internet) for which analytics information is provided.
Application ID	UPF	Identifies the application
IP Flow Information (1..max)	UPF	Per IP flow related information for the application
> IP 5-tuple	UPF	Identifies a service flow of the UE that uses the application.
> Start time	UPF	Start time of traffic detection for the flow.
> End time	UPF	End time of traffic detection for the flow.
> UL Data volume	UPF	Measured UL data traffic volume for the flow.
> DL Data volume	UPF	Measured DL data traffic volume for the flow.
> UL Data Rate	UPF	Measured UL data rate for the flow.
> DL Data Rate	UPF	Measured DL data rate for the flow.
> URL list	UPF	List of URLs extracted from the inspected user plane packets in the flow.
> Domain Name list	UPF	List of domain names extracted from the inspected user plane packets in the flow.
PFD Information	NEF(PFDF)	PFD Information stored in the UDR (as Application Data) and retrieved by NEF, as defined in clause 6.1.2.3.2 of TS 23.503 [4].
> Application ID	NEF(PFDF)	Identification of the application that refers to one or more application detection filters.
> IP 3-tuple list	NEF(PFDF)	Including protocol, server side IP address and port number.
> URL list	NEF(PFDF)	The significant parts of the URL to be matched, e.g. host name.
> Domain Name list	NEF(PFDF)	A Domain name matching criteria and information about applicable protocol(s).

NOTE: Extensive reporting of all traffic flows may conflict with the requirement to avoid extra UPF load. An NWDAF may subscribe only for reporting for some UEs to limit the load.

6.16.3 Output Analytics

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.

Table 6.16.3-1: PFD Determination statistics

Information	Description
Application ID	Application ID of the application that refers to the application detection filter (Flow descriptor, URL or Domain name information) stored in the UDR.
List of application description analytics
> S-NSSAI	Identifies the Network Slice for which analytics information is provided.
> DNN	Identifies the data network name (e.g. internet) for which analytics information is provided.
> Flow descriptor	Flow descriptor containing 3-tuple, server side (destination address, port, and protocol).
> URL	the significant parts of the URL to be matched, e.g. host name defined in.
> Domain name information	A Domain name matching criteria and information about applicable protocol(s).

6.16.4 Procedures

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

Figure 6.16.4-1: A procedure for NWDAF-assisted PFD Determination

1. The Consumer NF (NEF(PFDF)) requests or subscribes to the NWDAF to request PFD determination analytics. The Target of Analytics Reporting is set to Any UE. A single App-ID or a list of App-IDs are also provided as input.

This subscription may be triggered by local configuration or OAM. The Analytics Filter Information may optionally include the S-NSSAI and/or DNN.

2. The NWDAF fetches currently stored PFD information in use from UDR via NEF(PFDF).

3. The NWDAF collects session related information from the UPF about URL, Domain name part, and IP 3-tuples of packets corresponding to Application ID from the SDF not matching installed PDRs.

Editor’s note: UPEAS WI is specifying UPF event exposure for NWDAF data collection. It is FFS whether clause 4.15 of TS 23.502 [3] and the other UPEAS normative work address the needs of this new analytic.

4. The NWDAF derives PFD determination analytics, e.g., new/updated PFD information for the existing Application ID.

5. The NWDAF notifies PFD determination analytics to the Consumer NF (NEF(PFDF)) with PFD Information.