Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.502  Word version:   16.4.0

Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3…   4.3.2.2…   4.3.2.2.2   4.3.2.2.3…   4.3.3   4.3.4   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.2.2…   4.11.1.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.4…   4.16…   4.16.4…   4.16.8…   4.17…   4.17.9…   4.18…   4.19…   4.23…   4.23.7…   4.23.9…   4.23.11…   4.24   4.25   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   A…   E…   F…

 

4.16.8  Procedures on interaction between PCF and CHFWord-p. 334
4.16.8.1  General
The PCF may interact with the CHF to make PCC decisions based on spending limits. In Home Routed roaming and Non-roaming case, the H-PCF will interact with the CHF in HPLMN.
4.16.8.2  Initial Spending Limit Retrieval
This clause describes the signalling flow for the PCF to retrieve the status of the policy counters available at the CHF, and to subscribe to spending limit reporting (i.e. to notifications of policy counter status changes) by the CHF. If the PCF provides the list of policy counter identifier(s), the CHF returns the policy counter status per policy counter identifier provided by the PCF. If the PCF does not provide the list of policy counter identifier(s), the CHF returns the policy counter status of all policy counter(s), which are available for this subscriber.
The Initial Spending Limit Report Retrieval includes all subscriber Identifiers associated with the UE available at the PCF.
NOTE:
If the CHF returns the status of all available policy counters some of these might not be relevant for a policy decision (e.g. those used in a policy decision only when roaming).
Up
Step 1.
The PCF retrieves subscription information that indicates that policy decisions depend on the status of policy counter(s) held at the CHF and optionally the list of policy counter identifier(s).
Step 2.
The PCF sends Nchf_SpendingLimitControl_Subscribe if this is the first time policy counter status information is requested for the user identified by a SUPI. It includes: the subscriber ID (e.g. SUPI), the EventId "policy counter status change" and, optionally, the list of policy counter identifier(s) as Event Filter, the Notification Target Address, Event Reporting Information (continuous reporting).
The CHF responds to the Nchf_SpendingLimitControl_Subscribe service operation including the Subscription Correlation Id) and as Event Information provides a policy counter status, and optionally pending policy counter statuses and their activation times, per required policy counter identifier and stores the PCF's subscription to spending limit reports for these policy counters. If no policy counter identifier(s) was provided the CHF returns the list of the policy counter status, optionally including pending policy counter statuses and their activation times, for all policy counter(s), which are available for this subscriber and stores the PCF's subscription to spending limit reports of all policy counters provided to the PCF.
Up
4.16.8.3  Intermediate Spending Limit Report RetrievalWord-p. 335
This clause describes the signalling flow for the PCF to retrieve the status of additional policy counters available at the CHF or to unsubscribe from spending limit reporting. If the PCF provides the list of policy counter identifier(s), the CHF returns the policy counter status per policy counter identifier provided by the PCF.
NOTE:
If the CHF returns the status of all available policy counters some of these might not be relevant for a policy decision, (e.g. those used in a policy decision only when roaming).
Up
Step 1.
The PCF determines that policy decisions depend on the status of additional policy counter(s) held at the CHF or that notifications of policy counter status changes for some policy counters are no longer required.
Step 2.
The PCF sends Nchf_SpendingLimitControl_Subscribe to the CHF, including the Subscription Correlation Id, the EventId "policy counter status change" and an updated list of policy counter identifier(s) as EventFilters, that overrides the previously stored list of policy counter identifier(s).
The CHF responds to the Nchf_SpendingLimitControl_Subscribe service operation and provides as Event Information the policy counter status, and optionally pending policy counter statuses and their activation times, per required policy counter identifier, and stores or removes the PCF's subscription to spending limit reporting by comparing the updated list with the existing PCF subscriptions. If no policy counter identifier(s) was provided, the CHF returns the policy counter status, optionally including pending policy counter statuses and their activation times, for all policy counter(s), which are available for this subscriber and stores the PCF's subscription to spending limit reports of all policy counters provided to the PCF.
Up
4.16.8.4  Final Spending Limit Report RetrievalWord-p. 336
This clause describes the signalling flow for the PCF to cancel the subscriptions to status changes for the policy counters available at the CHF.
Up
Step 1.
The PCF decides that notifications of policy counter status changes are no longer needed.
Step 2.
The PCF sends Nchf_SpendingLimitControl_Unsubscribe including the SubscriptionCorrelationId to the CHF to cancel the subscription to notifications of policy counter status changes from the CHF.
Step 3.
The CHF removes the PCF's subscription to spending limit reporting and responds to the Nchf_SpendingLimitControl_Unsubscribe service operation to the PCF.
Up
4.16.8.5  Spending Limit Report
This clause describes the signalling flow for the CHF to notify the change of the status of the subscribed policy counters available at the CHF for that subscriber. Alternatively, the signalling flow can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied.
Up
Step 1.
The CHF detects that the status of a policy counter(s) has changed and the PCF subscribed to notifications of changes in the status of this policy counter. Alternatively, the CHF may detect that a policy counter status will change at a future point in time, and decides to instruct the PCF to apply one or more pending statuses for a requested policy counter.
Step 2.
The CHF sends Nchf_SpendingLimitControl_Notify with the SUPI, Notification Target Address, and in the Event Information the policy counter status, and optionally pending policy counter statuses and their activation times, for each policy counter that has changed and for which the PCF subscribed to spending limit reporting. Alternatively, the CHF sends one or more pending statuses for any of the subscribed policy counters together with the time they have to be applied.
Step 3.
The PCF acknowledges sending Nchf_SpendingLimitControl_Notify response and takes that information into account as input for a policy decision.
Up
4.16.8.6  CHF report the removal of the subscriberWord-p. 337
This clause describes the signalling flow for the CHF to report the removal of the subscriber.
Up
Step 1.
The CHF decides that a subscriber is removed.
Step 2.
The CHF sends the Nchf_SpendingLimitControl_Notify Request to H-PCF to notify the removal of the subscriber. The H-PCF removes the subscription to notification of policy counter status from CHF.
NOTE:
Notification on the removing of a subscriber causes the H-PCF to make the applicable policy decision and act accordingly.
Step 3.
The H-PCF responds to CHF using Nchf_SpendingLimitControl_Notify to acknowledge the receiving of the notification.
Up
4.16.9  Update of the subscription information in the PCFWord-p. 338
Up
NOTE:
The V-PCF is not used for session management related policy decisions in this procedure.
Step 0.
The PCF performs the subscription to notification to the profile modified in the UDR by invoking Nudr_DM_Subscribe (Policy Data, SUPI, Notification Target Address (+ Notification Correlation Id), Event Reporting Information (continuous reporting), one or several of the following: "PDU Session Policy Control data", "Remaining allowed Usage data" or "UE context Policy Control data") service.
Step 1.
The UDR detects that the related subscription profile has been changed.
Step 2.
If subscribed by the PCF, the UDR notifies the PCF on the changed profile by invoking Nudr_DM_Notify (Notification Correlation Id, Policy Data, SUPI, updated data and one or several of the following data subtypes "PDU Session Policy Control Data" or "Remaining allowed Usage data" or "UE Context Policy Control data") service.
Step 3.
The PCF stores the updated profile.
Step 4.
If the updated subscriber profile requires the status of new policy counters available at the CHF then an Initial/Intermediate Spending Limit Report Retrieval is initiated by the PCF as defined in clauses 4.16.8,2 and 4.16.8.3. If the updated subscriber profile implies that no policy counter status is needed an Intermediate Spending Limit Report Request Retrieval is initiated by the PCF to unsubscribe or, if this is the last policy counter status, a Final Spending Limit Report Retrieval is initiated by the PCF as specified in clause 4.16.8.4.
Step 5.
PCF makes an authorization and policy decision.
Step 6.
The PCF provides new session management related policy decisions to the SMF, using the Policy related interaction in PDU Session Modification procedure in clause 4.16.6, new access and mobility related policy information or new UE access selection and PDU Session selection related policy information to the AMF using the UE Context Modification procedure in clause 4.16.2.
Up
4.16.10Void
4.16.11  UE Policy Association EstablishmentWord-p. 339
This procedure concerns the following scenarios:
  1. UE initial registration with the network.
  2. The AMF relocation with PCF change in handover procedure and registration procedure.
  3. UE registration with 5GS when the UE moves from EPS to 5GS and there is no existing UE Policy Association between AMF and PCF for this UE.
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF and the H-PCF interacts with the V-PCF:
Step 1.
The AMF establishes UE Policy Association with the (V-)PCF when a UE Policy Container is received from the UE. If a UE Policy Container is not received from the UE, the AMF may establish UE Policy Association with the (V-)PCF based on AMF local configuration.
NOTE 1:
In roaming scenario, the AMF local configuration can indicate whether UE Policy delivery is needed based on the roaming agreement with home PLMN of the UE.
Step 2.
The AMF sends a Npcf_UEPolicyControl Create Request with the following information: SUPI, may include Access Type and RAT, PEI, ULI, UE time zone, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501), the Internal-Group-ID-list and UE Policy Container (the list of stored PSIs, operating system identifier, Indication of UE support for ANDSP). In roaming scenario, based on operator policies, the AMF may provide to the V-PCF the PCF ID of the selected H-PCF. The V-PCF contacts the H-PCF. In roaming case, steps 3 and 4 are executed, otherwise step 5 follows.
Step 3.
The V-PCF forwards the information received from AMF in step 2 to the H-PCF. When a UE Policy Container is received at initial registration, the H-PCF may store the PEI, the OSId or the indication of UE support for ANDSP in the UDR using Nudr_DM_Create including DataSet "Policy Data" and Data Subset "UE context policy control data".
Step 4.
The H-PCF sends a Npcf_UEPolicyControl Create Response to the V-PCF. The H-PCF may provide the Policy Control Request Trigger parameters in the Npcf_UEPolicyControl Create Response.
Step 5.
The (V-) PCF sends a Npcf_UEPolicyControl Create Response to the AMF. The (V-)PCF relays the Policy Control Request Trigger parameters in the Npcf_UEPolicyControl Create Response.
The (V-)PCF also subscribes to notification of N1 message delivery of policy information to the UE.
Step 6.
The (H-)PCF gets policy subscription related information and the latest list of PSIs from the UDR using Nudr_DM_Query service operation (SUPI, Policy Data, UE context policy control data, Policy Set Entry) if either or both are not available and makes a policy decision. The (H-)PCF may get the PEI, the OSId or the indication of UE support for ANDSP in the UDR using Nudr_DM_Query including DataSet "Policy Data" and Data Subset "UE context policy control data" if the AMF relocates and the PCF changes. The (H-)PCF may get the 5G VN group data for each Internal-Group-ID received from the AMF using Nudr_DM_Query (Internal-Group-Id, Subscription Data, Group Data). The (H-)PCF may store the 5G VN group data for later use for other SUPIs that belong to the same Internal-Group-ID. The (H-)PCF may request notifications from the UDR on changes in the subscription information by invoking Nudr_DM_Subscribe (Policy Data, SUPI, DNN, S-NSSAI, Notification Target Address (+ Notification Correlation Id), Event Reporting Information (continuous reporting), UE context policy control data) service. The (H-)PCF may request notifications from the UDR on changes in the 5G VN group data associated to each of the Internal-Group-Id provided to the PCF associated with 5G VN group data by invoking Nudr_DM_Subscribe (Subscription Data, 5G VN group data, Internal Group ID, Notification Target Address (+ Notification Correlation Id), Event Reporting Information (continuous reporting)) service. The (H-)PCF creates the UE policy container including UE access selection and PDU Session selection related policy information as defined in clause 6.6 of TS 23.503 and in the case of of roaming H-PCF provides the UE policy container in the Npcf_UEPolicyControl UpdateNotify Request.
Step 7.
The V-PCF sends a response to H-PCF using Npcf_UEPolicyControl UpdateNotify Response.
NOTE 2:
Step 6 (and step 7) can be omitted. Then the (H-)PCF creates the UE policy container including UE access selection and PDU Session selection polices in step 2 (in the case of non-roaming) or step 3 (in the case of roaming). This means that the potential interactions with UDR as in step 6 will have to be executed in step 2 (non-roaming) or step 3 (roaming).
Step 8.
The (V-)PCF triggers UE Configuration Update Procedure in clause 4.2.4.3 to sends the UE policy container including UE access selection and PDU Session selection related policy information to the UE. The (V-)PCF checks the size limit as described in TS 23.503, clause 6.1.2.2.2.
Step 9.
If the V-PCF received notification of the reception of the UE Policy container then the V-PCF forwards the notification response of the UE to the H-PCF using Npcf_UEPolicyControl_Update Request.
Step 10.
The H-PCF sends a response to the V-PCF.
Up
4.16.12  UE Policy Association ModificationWord-p. 340
4.16.12.1  UE Policy Association Modification initiated by the AMF
4.16.12.1.1  UE Policy Association Modification initiated by the AMF without AMF relocation
This procedure addresses the scenario where a Policy Control Request Trigger condition is met.
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case the V-PCF is not involved. In the roaming case, the AMF interacts with the V-PCF and the H-PCF interacts with the V-PCF.
Step 1.
When a Policy Control Request Trigger condition is met the AMF updates UE Policy Control Association and provides information on the conditions that have changed to the PCF. The AMF sends a Npcf_UEPolicyControl Update Request with the following information: UE Policy Association ID associated with the SUPI defined in TS 29.525 and the Policy Control Request Trigger met. In roaming scenario, based on operator policies, the AMF may provide to the V-PCF the PCF ID of the selected H-PCF. The V-PCF contacts the H-PCF.
In the roaming case, steps 2 and 3 are executed, otherwise step 4 follows.
Step 2.
The V-PCF forwards the information received from AMF in step 1 to the (H-)PCF.
Step 3.
The H-PCF replies to the V-PCF.
Step 4.
The (V-) PCF sends a Npcf_UEPolicyControl Update Response to the AMF.
Step 5.
The (H-)PCF may create the UE policy container including UE access selection and PDU Session selection related policy information as defined in clause 6.6 of TS 23.503. In the case of roaming the H-PCF may include the UE policy container in the Npcf_UEPolicyControl UpdateNotify Request.
Step 6.
The (V-)PCF sends a response to H-PCF using Npcf_UEPolicyControl UpdateNotify Response.
Steps 7, 8 and 9 are the same as steps 8, 9 and 10 of procedure UE Policy Assocaition Establishment in clause 4.16.11.
Up
4.16.12.1.2  UE Policy Association Modification with old PCF during AMF relocationWord-p. 342
This procedure addresses the scenario where a UE Policy Association Modification with the old PCF during AMF relocation.
Up
This procedure addresses both roaming and non-roaming scenarios.
In the non-roaming case the V-PCF is not involved. In the roaming case, the AMF interacts with the V-PCF and the V-PCF interacts with the H-PCF.
Step 1.
[Conditional] When the old AMF and the new AMF belong to the same PLMN, the old AMF transfers to the new AMF the UE Policy Association information including policy control request trigger(s) and the PCF ID(s). For the roaming case, the new AMF receives both V-PCF ID and H-PCF ID.
Step 2.
Based on local policies, the new AMF decides to re-use the UE policy association for the UE Context with the (V-)PCF and contacts the (V)-PCF identified by the PCF ID received in step 1.
NOTE:
The scenario that only the H-PCF is reused by the new AMF but the V-PCF is not reused is not considered in this Release.
Step 3.
The new AMF sends Npcf_UEPolicyControl_Update to the (V-)PCF to update the UE policy association with the (V-)PCF. If a Policy Control Request Trigger condition is met, the information matching the trigger condition may also be provided by the new AMF.
In the roaming case, step 4 and 5 are executed, otherwise step 6 follows.
Step 4.
The V-PCF forwards the information received from new AMF in step 3 to the (H-)PCF.
Step 5.
The H-PCF replies to the V-PCF.
Step 6.
The (V-)PCF updates the stored information provided by the old AMF with the information provided by the new AMF. The (V-)PCF sends a Npcf_UEPolicyControl Update Response to the AMF.
Step 7.
The (H-)PCF may create the UE policy containter including UE access selection and PDU Session selection related policy information as defined in clause 6.6 of TS 23.503. In the case of roaming the H-PCF may include the UE policy container in the Npcf_UEPolicyControl UpdateNotify Request.
Step 8.
The V-PCF sends a response to H-PCF using Npcf_UEPolicyControl UpdateNotify Response.
Steps 9, 10 and 11 are the same as steps 8, 9 and 10 of procedure UE Policy Assocaition Establishment in clause 4.16.11.
Up
4.16.12.2  UE Policy Association Modification initiated by the PCFWord-p. 343
This procedure is used to update UE policy and/or UE policy triggers.
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case the V-PCF is not involved and the role of the H-PCF is performed by the PCF. In the roaming case, the H-PCF provides UE access selection and PDU Session selection policy decision, and provides the policy to the AMF via V-PCF.
Step 1a and 1b.
If (H-)PCF subscribed to notification of subscriber's policy data change or 5G VN group data change and a change is detected, the UDR notifies that the subscriber's policy data of a UE or 5G VN group data has been changed.
The UDR notifies the (H-)PCF of the updated policy control subscription information profile via Nudr_DM_Notify (Notification correlation Id, Policy Data, either UE context policy control data or Policy Set Entry data or both, SUPI), or
The UDR notifies the (H-)PCF of the updated 5G VN group data via Nudr_DM_Notify (Notification correlation Id, Group data, Internal-Group-Identifier), or
The (V-)UDR notifies the (V-)PCF of the updated policy control subscription information profile via Nudr_DM_Notify (Notification correlation Id, Policy Data, PolicySetEntry Data. PLMN ID).
Step 1c and 1d.
PCF determines locally that UE Access selection and PDU session selection policy information needs to be sent to the UE.
Step 2a and 2b.
The PCF makes the policy decision. If the group data is updated, the (H-) PCF checks the UE Policy Associations for those SUPIs within the Internal-Group-Id and may need to perform step 3 to step 9 for each UE Policy Association that needs to be updated with new UE Policies sent to each UE.
Step 3.
The (H-)PCF may create the UE policy container including UE access selection and PDU Session selection related policy information as defined in clause 6.1.2.2.2 of TS 23.503. In the case of roaming, the H-PCF may send the UE policy container in the Npcf_UEPolicyControl UpdateNotify Request. The H-PCF may provide updated policy control triggers for the UE policy association.
Step 4.
The V-PCF sends a response to H-PCF using Npcf_UEPolicyControl UpdateNotify Response.
Step 5.
The (V-)PCF provides the Policy Control Request Trigger parameters in the Npcf_UEPolicyControl UpdateNotify Request to the AMF. In the case of roaming, the V-PCF may also provide UE Acccess selection and PDU session selection related policy information to the UE. The V-PCF may also provide updated policy control triggers for the UE policy association to the AMF.
Step 6.
The AMF sends a response to (V-)PCF.
Steps 7, 8 and 9 are the same as steps 8, 9 and 10 of procedure UE Policy Association Establishment in clause 4.16.11.
Up
4.16.13  UE Policy Association TerminationWord-p. 344
4.16.13.1  AMF-initiated UE Policy Association Termination
The following case is considered for UE Policy Association Termination:
  1. UE Deregistration from the network.
  2. The mobility with change of AMF (e.g. new AMF is in different PLMN or new AMF in the same PLMN).
  3. [Optional] 5GS to EPS mobility with N26 if the UE is not connected to the 5GC over a non-3GPP access in the same PLMN.
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the V PCF interacts with the AMF. The V PCF contacts the H-PCF to request removing UE Policy Association.
Step 1.
The AMF decides to terminate the UE Policy Association.
Step 2.
The AMF sends the Npcf_UEPolicyControl_Delete service operation including UE Policy Association ID to the (V-)PCF.
Step 3.
The (V-)PCF removes the policy context for the UE and replies to the AMF with an Acknowledgement including success or failure. The V-PCF may interact with the H-PCF. The (V-)PCF may unsubscribe to subscriber policy data changes with UDR by Nudr_DM_Unsubscribe (Subscription Correlation Id). The AMF removes the UE Policy Context.
Step 4 and Step 5 apply only to the roaming case.
Step 4.
The V-PCF sends the Npcf_UEPolicyControl_Delete service operation including UE Policy Association ID to the H-PCF.
Step 5.
The H-PCF removes the policy context for the UE and replies to the V-PCF with an Acknowledgement including success or failure. The H-PCF may unsubscribe to subscriber policy data changes with UDR by Nudr_DM_Unsubscribe (Subscription Correlation Id) for subscriber policy changes.
Up
4.16.13.2  PCF-initiated UE Policy Association TerminationWord-p. 346
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the H-PCF interacts with the V-PCF to request removing Policy Association.
The PCF is subscribed to notification of changes in Data Set "Policy Data" for a UE Policy Association ID.
Step 1.
The Policy data is removed, either the Data Set "Policy Data" or the Data Subset "UE context policy control".
Step 2.
The UDR sends the Nudr_DM_Notify_Request (Notification correlation Id, Policy Data, SUPI, UE Context Policy Control data, updated data) including the SUPI, the Data Set Identifier, the Data Subset Identifier and the Updated Data including empty "Policy Data" or empty "UE context policy control".
Step 3.
The PCF sends the Nudr_DM_Notify_Response to confirm reception and the result to UDR.
Step 4.
The PCF may notify the AMF of the removal of the UE Policy Association via Npcf_UEPolicyControl_UpdateNotify service operation. Alternatively, the PCF may decide to maintain the Policy Association if a default profile is applied, in this case steps 4, 5 and 6 are not executed.
Step 5.
The AMF acknowledges the operation.
Step 6.
Steps 2-5 in clause 4.16.13.1 AMF-initiated UE Policy Association Termination are performed to remove the UE Policy Association for this UE and the subscription to Policy Control Request Triggers for that UE Policy Association.
Up

Up   Top   ToC