Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.502  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.2.11…   4.2.11.5…   4.3…   4.3.2.2.2   4.3.2.2.3…   4.3.3…   4.3.3.3   4.3.4…   4.3.4.3   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1…   4.11.1.2.2   4.11.1.2.3   4.11.1.3…   4.11.1.3.3…   4.11.1.4…   4.11.1.5…   4.11.2…   4.11.3…   4.12…   4.12.6…   4.12a…   4.12b…   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.3.2.5…   4.15.4…   4.15.6…   4.15.6.7…   4.15.6.13…   4.15.6.14…   4.15.9…   4.15.9.4…   4.15.13…   4.15.13.4…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.16.14…   4.16.15…   4.17…   4.17.9…   4.18…   4.19…   4.22…   4.23…   4.23.7…   4.23.7.3.3   4.23.7.3.4…   4.23.9…   4.23.9.4…   4.23.11…   4.24…   4.25…   4.25.6…   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   5.2.18…   A…   E…   F…   G   H… 
4.18 Procedures for Management of PFDs  4.18.1 General  4.18.2 PFD management via NEF (PFDF)  4.18.2.1 PFD management triggered by AF  4.18.2.2 PFD management based on PFD Determination analytics  4.18.3 PFD management in the SMF  4.18.3.1 PFD Retrieval by the SMF  4.18.3.2 Management of PFDs in the SMF 
...

 

4.18  Procedures for Management of PFDs  p. 572

4.18.1  General  p. 572

4.18.2  PFD management via NEF (PFDF)  p. 573

4.18.2.1  PFD management triggered by AF |R18|  p. 573

Reproduction of 3GPP TS 23.502, Fig. 4.18.2.1-1: Procedure for PFD management via NEF (PFDF) triggered by AF
Figure 4.18.2.1-1: Procedure for PFD management via NEF (PFDF) triggered by AF
Up
Step 1.
The AF invokes the Nnef_PFDManagement_Create/Update/Delete service. The Allowed Delay is an optional parameter. If the Allowed Delay is included, it indicates that the list of PFDs in this request should be provisioned within the time interval indicated by the Allowed Delay to the SMF(s) that have subscribed to the PFD management service using Nnef_PFDManagement_Subscribe service operation.
Step 2.
NEF (PFDF) checks whether the AF is authorized to perform this request and if the AF is authorised to provision this PFD data based on the operator policies. The NEF (PFDF) may in addition subscribe to the NWDAF to receive PFD Determination analytics (defined in clause 6.16.3 of TS 23.288) for this Application Identifier.
Step 3.
The NEF (PFDF) invokes the corresponding Nudr_DM_Create/Update/Delete (Data Key = Packet Flow Descriptions, Application Identifier, one or more PFDs, Allowed Delay) to the UDR.
Step 4.
The UDR creates/updates/deletes the list of PFDs for the Application Identifier.
Step 5.
The UDR sends a Nudr_DM_Create/Update/Delete Response to the NEF (PFDF).
Step 6.
The NEF (PFDF) sends Nnef_PFDManagement_Create/Update/Delete Response to the Application Function.
Up

4.18.2.2  PFD management based on PFD Determination analytics |R18|  p. 573

Figure 4.18.2.2-1 shows the procedure that NEF (PFDF) determines the PFD information for the known Application Identifier(s), based on the PFD Determination analytics information notified/responded from the subscribed/requested NWDAF. The procedure enables the NEF (PFDF) to determine whether to create/update/delete PFD information corresponding to the known Application Identifier(s).
Reproduction of 3GPP TS 23.502, Fig. 4.18.2.2-1: Procedure for PFD management based on PFD Determination analytics
Figure 4.18.2.2-1: Procedure for PFD management based on PFD Determination analytics
Up
Step 1.
The NWDAF notifies/responds to PFD Determination analytics to the NEF (PFDF) as Consumer NF with PFD Information defined in clause 6.16.3 of TS 23.288.
Step 2.
The NEF (PFDF) fetches the PFD information currently in use from UDR if not available in NEF (PFDF) as described from step 2 to step 3 of clause 4.18.3.1.
Step 3.
The NEF (PFDF) compares the PFD information from UDR with PFD information from the NWDAF to determine whether to create/update/delete PFD information corresponding to the Application Identifier.
Step 4.
If the NEF (PFDF) has determined in step 3 to create/update/delete PFD information corresponding to the Application Identifier, the NEF (PFDF) invokes the Nudr_DM_Create/Update/Delete (Application Identifier, one or more sets of PFDs) to the UDR to create/update/delete PFD information corresponding to the Application Identifier, i.e. from step 3 to step 5 of clause 4.18.2.1 are executed. The NEF (PFDF) may forward new/updated PFD information to UPF via SMF to detect a known application, as defined in clause 6.1.2.3.1 of TS 23.503.
Up

4.18.3  PFD management in the SMF  p. 574

4.18.3.1  PFD Retrieval by the SMF  p. 574

This procedure enables the SMF to retrieve PFDs for an Application Identifier from the NEF (PFDF) when a PCC rule with this Application Identifier is provided/activated and PFDs provided by the NEF (PFDF) are not available at the SMF.
In addition, this procedure enables the SMF to retrieve PFDs from the NEF (PFDF)when the caching timer for an Application Identifier elapses and a PCC Rule for this Application Identifier is still active.
The NEF (PFDF) retrieves the PFDs from UDR unless already available in NEF (PFDF).
The SMF may retrieve PFDs for one or more Application Identifiers in the same Request. All PFDs related to an Application Identifier are provided in the response from the UDR to NEF (PFDF).
Reproduction of 3GPP TS 23.502, Fig. 4.18.3.1-1: PFD Retrieval by the SMF
Figure 4.18.3.1-1: PFD Retrieval by the SMF
Up
Step 1.
SMF invokes the Nnef_PFDManagement_Fetch (Application Identifier (s)) to the NEF (PFDF).
Step 2.
NEF (PFDF) checks if the PFDs for the Application Identifier (s) are available in the NEF (PFDF), if available, the NEF (PFDF) skips to step 4. If not, the NEF (PFDF) invokes Nudr_DM_Query (Application Identifier (s)) to retrieve the PFD(s) from UDR.
Step 3.
The UDR provides a Nudr_DM_Query response (Application Identifier(s), PFD(s)) to the NEF (PFDF).
Step 4.
The NEF (PFDF) replies to the SMF with Nnef_PFDManagement_Fetch (Application Identifier(s), PFD(s)).
Up

4.18.3.2  Management of PFDs in the SMF  p. 575

This procedure enables the provisioning, modification or removal of PFDs associated with an application identifier in the SMF. Either the complete list of all PFDs of all application identifiers, the complete list of all PFDs of one or more application identifiers or a subset of PFDs for individual application identifiers may be managed.
Each PFD of an application identifier is associated with a PFD id if a subset of the PFD(s) associated with an application identifier can be provisioned, updated or removed. If always the full set of PFD(s) for an application identifier is managed in each transaction, PFD ids do not need to be provided.
Reproduction of 3GPP TS 23.502, Fig. 4.18.3.2-1: Management of PFDs in the SMF
Figure 4.18.3.2-1: Management of PFDs in the SMF
Up
Step 1.
As pre-requisite condition to receiving push notifications, the SMF subscribes to PFD notifications from the NEF (PFDF) by sending Nnef_PFDManagement_Subscribe message.
Step 2.
The NEF (PFDF) invokes Nnef_PFD_Management_Notify (Application Identifier, PFDs, PFDs operation) to the SMF(s) to which the PFD(s) shall be provided. The NEF (PFDF) may decide to delay the distribution of PFDs to the SMF(s) for some time to optimize the signalling load. If the NEF (PFDF) received an Allowed Delay for a PFD, the NEF (PFDF) shall distribute this PFD within the indicated time interval.
Up

Up   Top   ToC