Content for  TS 23.288  Word version:  18.4.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.3   6.1.4……   6.1.5…   6.1A…   6.1B…   6.1B.2.3…   6.1C   6.2…   6.2.3…   6.2.6………   6.2.7…   6.2.8…   6.2.9…   6.2.13…   6.2A…   6.2B…   6.2B.3   6.2B.4…   6.2C…   6.2D…   6.2E…   6.2F…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   6.16…   6.17…   6.18…   6.19…   6.20…   6.21…   7…   7.4…   7.7…   7.9…   8…   9…   10…


6.16  PFD Determination Analytics |R18|p. 252

6.16.1  Generalp. 252

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.

6.16.2  Input Datap. 252

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.
Information Source Description
Application ID (NOTE 1)UPFIdentifies the application
IP Flow Information (1..max)UPFPer IP flow related information for the application
 > IP 5-tupleUPFIdentifies a service flow of the UE that uses the application.
 > Start timeUPFStart time of traffic detection for the flow.
 > End timeUPFEnd time of traffic detection for the flow.
 > UL Data volumeUPFMeasured UL data traffic volume for the flow.
 > DL Data volumeUPFMeasured DL data traffic volume for the flow.
 > UL Data RateUPFMeasured UL data rate for the flow.
 > DL Data RateUPFMeasured DL data rate for the flow.
 > URL listUPFList of URLs extracted from the inspected user plane packets in the flow.
 > Domain Name listUPFList of domain names extracted from the inspected user plane packets in the flow.
PFD InformationNEF(PFDF)PFD Information stored in the UDR (as Application Data) and retrieved by NEF (PFDF), as defined in clause of TS 23.503.
> Application IDNEF(PFDF)Identification of the application that refers to one or more application detection filters.
> IP 3-tuple listNEF(PFDF)Including protocol, server side IP address and port number.
> URL listNEF(PFDF)The significant parts of the URL to be matched, e.g. host name.
> Domain Name listNEF(PFDF)A Domain Name matching criteria and information about applicable protocol(s).
The Application ID maps in the UPF to a detection algorithm that has a wider scope than the Application ID provided by the consumer.

6.16.3  Output Analyticsp. 253

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.
Information Description
Application IDApplication 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 traffic description
> Flow descriptorFlow descriptor containing 3-tuple server side IP address, server port number and protocol of uplink/downlink application traffic as described in TS 23.503).
> URLthe significant parts of the URL to be matched, e.g. host name defined in.
> Domain name informationA Domain name matching criteria and information about applicable protocol(s).
ConfidenceConfidence on the provided application traffic description for the Application ID.

6.16.4  Proceduresp. 254

The procedure depicted in Figure 6.16.4-1 shows the procedure that the NWDAF can provide PFD Detection analytics to a NEF (PFDF).
Reproduction of 3GPP TS 23.288, Fig. 6.16.4-1: A procedure for NWDAF-assisted PFD Determination
Step 1.
The Consumer NF (NEF(PFDF)) requests or subscribes to the NWDAF to request PFD Determination analytics for a known application identifier. The Target of Analytics Reporting is set to Any UE.
The Analytics Filter Information may optionally include the S-NSSAI and/or DNN.
Step 2.
The NWDAF fetches currently stored PFD information in use from UDR via NEF(PFDF) for the Application ID provided in step 1, as listed in Table 6.16.2-1.
Step 3.
The NWDAF collects information from the UPF (event "UserDataUsageMeasures") as listed in Table 6.16.2-1 either via SMF (Option 1) or directly from UPF (Option 2) as defined in clause of TS 23.501. NWDAF discovers the SMF (Option 1) or UPF (Option 2) through NRF as defined in clause of TS 23.502. The event "UserDataUsageMeasures" is defined in clause of TS 23.502, the subscription to the event may include an Application ID set to a value that allows the NWDAF to retrieve input information to derive PFD Determination Analytics for the Application ID that is provided by the consumer.
Step 4.
UPF reports the data directly to NWDAF.
Step 5.
The NWDAF derives PFD Determination analytics, e.g. new or updated PFD information for the existing Application ID. When the consumer provides the preferred level of accuracy, the NWDAF provides PFD Determination Analytics that reaches this level to the consumer.
Step 6.
In the case that PFD information for the existing Application ID is new or to be updated, the NWDAF notifies PFD Determination analytics to the consumer NF (i.e. NEF(PFDF)) with PFD Information.

Up   Top   ToC