Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.3   6.1.4…   6.1.4.4…   6.1.5…   6.1A…   6.1B…   6.1B.2.3…   6.1C   6.2…   6.2.3…   6.2.6…   6.2.6.2   6.2.6.3…   6.2.6.3.3   6.2.6.3.4   6.2.6.3.5   6.2.6.3.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. 261

6.16.1  Generalp. 261

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 this, 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 PFD determination statistics, e.g. new or updated IP 3-tuple list, to an analytics consumer in the 5GC. The NEF(PFDF) as the consumer uses the suggested PFD information of the PFD determination statistics provided by the NWDAF as defined in clause 4.18.2.2 of TS 23.502 and in TS 23.503.
The service consumer is a NEF(PFDF).
The consumer of these analytics shall indicate in the subscription:
  • Analytics ID = " PFD Determination";
  • Target of Analytics Reporting: "any UE";
  • Application identifier;
  • Analytics Filter Information optionally containing:
    • S-NSSAI(s);
    • DNN(s);
  • An Analytics target period indicates the time period over which the statistics are requested;
  • Analytics Reporting Parameters indicating either periodic reporting (together with the parameter periodicity) or reporting when threshold is reached (together with the parameter Reporting type (as defined in clause 4.15.1 of TS 23.502) to indicate that the report shall only occur when the information differs from the previous report);
  • Optionally, the preferred level of accuracy on the PFD determination statistics;
  • Optionally, maximum number of objects. This refers to the analytic output (i.e. maximum number of new or updated suggested PFD information in the PFD determination statistics);
  • In a subscription, the Notification Correlation Id and the Notification Target Address are included.
Up

6.16.2  Input Datap. 261

The NWDAF collects information on user data traffic from the UPF for a known Application ID optionally together with a combination of certain S-NSSAI(s) and/or DNN(s) 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 for detection of suggested PFD information (NOTE 1)UPFIdentifies the application detection algorithm used for the detection of suggested PFD information.
Application Traffic Flow Information (1..max)UPFPer Application Traffic flow related information for the application and optionally, for a DNN, S-NSSAI combination.
 > 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 6.1.2.3.2 of TS 23.503.
> Application IDNEF(PFDF)Identification of the application that refers to one or more application detection filters.
> PFD(s) (1..max)NEF(PFDF)
 >> PFD IDNEF(PFDF)
 >> 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).
 >> Source NF type (NOTE 2)NEF(PFDF)Indicates the source NF type which generated the PFD (i.e. AF or NWDAF).
NOTE 1:
In the UPF, the "Application ID for detection of suggested PFD information" can refer to a detection algorithm that has a wider scope than the detection algorithm the Application ID provided by the consumer refers to.
NOTE 2:
In order to enable retrieval of input data from the UPF as listed in Table 6.16.2-1, if UPF supports exposure, then SMF is expected to provide DNN and S-NSSAI to UPF at PDU Session establishment.
Up

6.16.3  Output Analyticsp. 262

The output analytics of PFD Determination 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 analytics of input data provided by UPF and NEF(PFDF).
Information Description
Application IDIdentifies the application for which the PFD information applies.
List of suggested PFD information (1..max)Suggested PFD information derived by the analytics for the application.
> PFD IDIdentifier of the PFD (i.e. new PFD ID assigned by NWDAF or existing PFD ID retrieved from UDR).
> IP 3-tuple listIncluding protocol, server side IP address and port number.
> URL listThe significant parts of the URL to be matched, e.g. host name.
> Domain Name listA Domain Name matching criteria and information about applicable protocol(s).
> ConfidenceConfidence on the provided suggested PFD information for the Application ID.
Up

6.16.4  Proceduresp. 263

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
Up
Step 1.
The Consumer NF (NEF(PFDF)) 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 subscribes to PFD notifications for the Application ID provided in step 1 by sending Nnef_PFDManagement_Subscribe message to the NEF (PFDF) in order to be informed about the stored PFD information in use from UDR via NEF(PFDF). The NEF(PFDF) sends the PFD(s) that are currently stored for the Application ID in the Nnef_PFD_Management_Notify message. The NEF(PFDF) will send further Nnef_PFD_Management_Notify messages whenever the PFD(s) for this Application ID change.
Step 3.
The NWDAF collects information from the UPF (event "User Data Usage Measures") as listed in Table 6.16.2-1 via SMF as defined in clause 5.8.2.17 of TS 23.501. NWDAF discovers the SMF through NRF as defined in clause 4.15.4.5.3 of TS 23.502. The event "User Data Usage Measures" is defined in clause 5.2.26.2 of TS 23.502, the subscription to the event includes an "Application ID for detection of suggested PFD information" which 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 suggested PFD information for the existing Application ID. For providing new suggested PFD information, the NWDAF shall assign a new PFD ID that is not yet used for this Application ID. For updating PFD information, the NWDAF shall use the existing PFD ID when indicating the updated suggested PFD information. For deleting PFD information, the NWDAF shall only indicate the existing PFD ID. The NWDAF can only update or delete suggested PFD information previously generated by the NWDAF, i.e. that contains "NWDAF" as source NF type. When the consumer provides the preferred level of accuracy, the NWDAF provides PFD Determination Analytics that reaches or exceeds this level to the consumer.
Step 6.
The NWDAF notifies PFD Determination analytics (shown in Table 6.16.3-1) to the consumer NF (i.e. NEF(PFDF)) with suggested PFD Information according to the reporting mode indicated by the Consumer NF (i.e. NEF(PFDF)) during the subscription in step 1.
Up

Up   Top   ToC