6.3.7.1 PCF discovery and selection for a UE or a PDU Session

PCF discovery and selection functionality is implemented in AMF, SMF, SCP and PCF for the PDU Session and follows the principles in clause 6.3.1.

When the NF service consumer performs PCF discovery and selection for a UE, the following applies:

• The AMF may utilize the NRF to discover the candidate PCF instance(s) for a UE. In addition, PCF information may also be locally configured in the AMF. The AMF selects a PCF instance based on the available PCF instances obtained from the NRF or locally configured information in the AMF, depending on operator's policies.

In the non roaming case, the AMF selects a PCF instance for AM Policy Association and selects the same PCF instance for UE Policy Association. In the roaming case, the AMF selects a V-PCF instance for AM Policy Association and selects the same V-PCF instance for UE Policy Association.

The PCF for the PDU Session selects a (V-)PCF instance for UE Policy Association.

The following factors may be considered at PCF discovery and selection for Access and Mobility policies and UE policies:

• SUPI; the AMF selects a PCF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for PCF discovery.
• S-NSSAI(s). In the roaming case, the AMF selects the V-PCF instance based on the S-NSSAI(s) of the VPLMN and selects the H-PCF instance based on the S-NSSAI(s) of the HPLMN.
• PCF Set ID.
• PCF Group ID of the UE's SUPI.

NOTE 1: The AMF can infer the PCF Group ID the UE's SUPI belongs to, based on the results of PCF discovery procedures with NRF. The AMF provides the PCF Group ID the SUPI belongs to to other PCF NF consumers as described in TS 23.502 [3].

• DNN replacement capability of the PCF.
• Slice replacement capability of the PCF.
• PCF Selection Assistance Info and PCF ID(s) serving the established PDU Sessions/PDN Connections received from UDM. In case PCF Selection Assistance Info and PCF ID(s) are received from the UDM, the AMF selects the same PCF instance serving the combination of DNN and S-NSSAI as indicated by the PCF Selection Assistance Info, if multiple DNN, S-NSSAI combinations are provided, the AMF selects the DNN,S-NSSAI using local configuration. In case PCF ID(s) are not received, e.g. EPS interworking is not supported, the AMF selects the PCF instance by considering other above factors.
• URSP delivery in EPS capability of the PCF.

When the NF service consumer performs PCF discovery and selection for a PDU Session, the following applies:

• The SMF may utilize the NRF to discover the candidate PCF instance(s) for a PDU Session. In addition, PCF information may also be locally configured in the SMF. The SMF selects a PCF instance based on the available PCF instances obtained from the NRF or locally configured information in the SMF, depending on operator's policies.

The following factors may be considered at PCF discovery and selection for a PDU Session:

• Local operator policies.
• Selected Data Network Name (DNN).
• S-NSSAI of the PDU Session. In the LBO roaming case, the SMF selects the PCF instance based on the S-NSSAI of the VPLMN. In the home routed roaming case, the H-SMF selects the H-PCF instance based on the S-NSSAI of the HPLMN.
• SUPI; the SMF selects a PCF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for PCF discovery.
• PCF selected by the AMF for the UE.
• MA PDU Session capability of the PCF, for an MA PDU Session.
• The PCF Group ID provided by the AMF to the SMF.
• PCF Set ID.
• Same PCF Selection Indication.
• URSP delivery in EPS capability of the PCF.

In the case of delegated discovery and selection in SCP, the SMF includes the factors b) - h), j), if available, in the first request.

The selected PCF instance for serving the UE and the selected PCF instance for serving a PDU Session of this UE may be the same or may be different.

In the following scenarios, information about the PCF instance that has been selected (i.e. the PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available)) may be forwarded to another NF. If the NF service consumer performs discovery and selection, this NF may use this PCF instance. If the NF service consumer performs delegated discovery and selection, this NF may include PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) in the request and the SCP may use this information to select the PCF instance (discovery may still be needed depending on what level of information is sent by the AMF, e.g. the endpoint address of the PCF instance may not be present):

When NF service consumer performs PCF discovery and selection, the following applies:

• During AMF relocation, the target AMF may receive a PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) from the source AMF to enable the usage of the same PCF by the target AMF and the target AMF may decide based on operator policy either to use the same PCF or select a new PCF.
• The AMF may, based on operator policies, forward the selected PCF to SMF instance(s) during the PDU Session Establishment procedure(s) to enable the usage of the same PCF for the AMF and the SMF instance(s). The SMF may decide based on operator policy either to use the same PCF or select a new PCF. If combination of the DNN and S-NSSAI of the PDU Session matches one of the combination of the DNN and S-NSSAI included in the PCF Selection Assistance info received from UDM, the AMF shall forward Same PCF Selection Indication together with the selected PCF to SMF instance during the PDU Session Establishment procedure. In case that the Same PCF Selection Indication is received together with the PCF ID, the SMF shall select the same PCF instance for SM Policy Control.
• In the roaming case, the AMF may, based on operator policies, e.g. roaming agreement, select the H-PCF in addition to the V-PCF for a UE by performing the PCF discovery and selection as described above. The AMF may send the ID and/or endpoint address (e.g. URI) of the selected H-PCF instance to the V-PCF during the UE Policy Association establishment procedure.

When the SMF receives a redirection indication with PCF ID from the PCF for the PDU Session, the SMF shall terminate the current SM Policy Association and reselects a PCF based on the received PCF ID. The SMF shall then establish an SM Policy Association with the reselected PCF.

In the case of delegated discovery and selection in the SCP, the following applies:

• The selected PCF instance may include the PCF Id, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) in the response to the AMF.

NOTE 2: The selected (V-)PCF instance can include the binding indication, including the (V-)PCF ID and possibly PCF Set ID in the response to the AMF as described in clause 6.3.1.0.

• The AMF first establishes an AM Policy Association; when forwarding the related request message the SCP discovers and selects a PCF instance. Unless binding information is provided in the response to that request the SCP adds the NF function producer ID it selected, i.e. PCF ID, into the response and the AMF uses the received PCF ID and available binding information as discovery and selection parameters for the request to establish the UE Policy Association towards the SCP. The SCP selects the (V-)PCF instance for UE Policy Association based on the received discovery and selection parameters.
• During AMF relocation, the AMF may receive a PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) from the source AMF to enable the usage of the same PCF instance by the AMF. The AMF may decide based on operator policy either to use the old PCF instance or select another PCF instance. If the AMF decides to use the old PCF, the AMF includes the PCF ID PCF Set Id and if PCF Set Id is not available, the PCF Group ID (if available) as received from the source AMF in the AM Policy Association update request to the SCP.
• The AMF may, based on operator policies, forward the selected PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) to the SMF during the PDU Session Establishment procedure to enable the usage of the same PCF for the AMF and the SMF. The SMF may include that information in the request in discovery and selection parameters to the SCP. The SCP may decide based on operator policy either to use the indicated PCF instance or select another PCF instance.
• In the roaming case, the AMF performs discovery and selection of the H-PCF from NRF as described in this clause. The AMF may indicate the maximum number of H-PCF instances to be returned from NRF, i.e. H-PCF selection at NRF. The AMF uses the received V-PCF ID and endpoint address (e.g. URI) and available binding information received during the AM Policy Association procedure to send the UE Policy Association establishment request, which may also include the H-PCF ID and/or endpoint address (e.g. URI), to the SCP. The SCP discovers and selects the V-PCF. The V-PCF sends an UE Policy Association establishment request towards the HPLMN, which may include the H-PCF ID and/or endpoint address (e.g. URI) as a discovery and selection parameter to SCP.