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  Procedures and flows for Policy FrameworkWord-p. 320
4.16.1  AM Policy Association Establishment
4.16.1.1  General
There are three cases considered for AM Policy Association Establishment:
  1. UE initial registration with the network.
  2. The AMF re-allocation with PCF change in handover procedure and registration procedure.
  3. EPS to 5GS mobility when there is no existing AM Policy Association between AMF and PCF for this UE.
4.16.1.2  AM Policy Association Establishment with new Selected PCF
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF.
Step 1.
Based on local policies, the AMF decides to establish AM Policy Association with the (V-)PCF then steps 2 to 3 are performed under the conditions described below.
Step 2.
[Conditional] If the AMF has not yet obtained Access and Mobility policy for the UE or if the Access and Mobility policy in the AMF are no longer valid, the AMF requests the PCF to apply operator policies for the UE from the PCF. The AMF sends Npcf_AMPolicyControl_Create to the (V-)PCF to establish an AM policy control association with the (V-)PCF. The request includes the following information: SUPI, Internal Group (see clause 5.9.7 of TS 23.501), subscription notification indication and, if available, Service Area Restrictions, RFSP index, Subscribed UE-AMBR, the Allowed NSSAI, GPSI which are retrieved from the UDM during the update location procedure, and may include Access Type and RAT Type, PEI, ULI, UE time zone, and Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501).
Step 3.
The (V)-PCF responds to the Npcf_AMPolicyControl_Create service operation. The (V)-PCF provides Access and mobility related policy information (e.g. Service Area Restrictions) as defined in clause 6.5 of TS 23.503. In addition, (V)-PCF can provide Policy Control Request Trigger of AM Policy Association to AMF.
The AMF is implicitly subscribed in the (V-)PCF to be notified of changes in the policies.
Step 4.
[Conditional] The AMF deploys the Access and mobility related policy information which includes storing the Service Area Restrictions and Policy Control Request Trigger of AM Policy Association, provisioning Service Area Restrictions to the UE and provisioning the RFSP index, the UE-AMBR and Service Area Restrictions to the NG-RAN as defined in TS 23.501.
Up
4.16.1.3Void
4.16.2  AM Policy Association ModificationWord-p. 321
4.16.2.0  General
There are three cases considered for AM Policy Association Modification:
  • Case A: A Policy Control Request Trigger condition is met: the procedure is initiated by the AMF.
  • Case B: PCF local decision or trigger from other peers of the PCF (i.e. UDR): the procedure is initiated by the PCF.
  • Case C: AM Policy Association Modification with the old PCF during AMF relocation: the procedure is initiated by the AMF.
4.16.2.1  AM Policy Association Modification initiated by the AMF
4.16.2.1.1  AM Policy Association Modification initiated by the AMF without AMF relocation
This procedure is applicable to Case A.
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF.
Step 1.
When a Policy Control Request Trigger condition is met the AMF updates AM Policy Association and provides information on the conditions that have changed to the PCF by invoking Npcf_AMPolicyControl_Update.
Step 2.
The (V-)PCF stores the information received in step 1 and makes the policy decision.
Step 3.
The (V-)PCF responds to the AMF of the updated Access and Mobility related policy control information as defined in clause 6.5 of TS 23.503 and the updated Policy Control Request Trigger parameters.
Step 4.
The AMF deploys the access and mobility control policy, which includes storing the Service Area Restrictions and Policy Control Request Trigger of AM Policy Association, provisioning the Service Area Restrictions to the UE and provisioning the RFSP index, UE-AMBR and Service Area Restrictions to the NG-RAN as defined in TS 23.501.
Up
4.16.2.1.2  AM Policy Association Modification with old PCF during AMF relocationWord-p. 322
This procedure is applicable to Case C. In this case, AMF relocation is performed without PCF change in handover procedure and registration procedure.
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF.:
Step 1.
[Conditional] When the old AMF and the new AMF belong to the same PLMN, the old AMF transfers to the new AMF about the AM Policy Association information including policy control request trigger(s) and the PCF ID. For the roaming case, the new AMF receives V-PCF ID.
Step 2.
Based on local policies, the new AMF decides to establish UE Context with the (V-)PCF and contacts the (V-)PCF identified by the PCF ID received in step 1.
Step 3.
The new AMF sends Npcf_AMPolicyControl_Update to the (V-)PCF to update the AM policy association with the (V-)PCF. The request may include the following information: policy control request trigger which has been met, Subscribed Service Area Restrictions (if updated), subscribed RFSP index (if updated) which are retrieved from the UDM during the update location procedure, and may include access type and RAT, PEI, ULI, UE time zone, service network. The (V-)PCF updates the stored information provided by the old AMF with the information provided by the new AMF.
Step 4.
The (V-)PCF may update the policy decision based on the information provided by the new AMF.
Step 5.
The AMF deploys the access and mobility control policy, which includes storing the Service Area Restrictions, provisioning Service Area Restrictions to the UE and provisioning the RFSP index, UE-AMBR and Service Area Restrictions to the NG-RAN.
Up
4.16.2.2  AM Policy Association Modification initiated by the PCFWord-p. 323
This procedure is applicable to AM Policy Association modification due to Case B.
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF.
NOTE:
The V-PCF stores the access and mobility control policy information provided to the AMF.
Step 1.
[Conditional] PCF determines locally that the new status of the UE context requires new policies.
Step 2.
The (V-)PCF makes a policy decision.
Step 3.
The (V-)PCF sends Npcf_UpdateNotify including AM Policy Association ID associated with the SUPI defined in TS 29.507, Service Area Restrictions, UE-AMBR or RFSP index.
Step 4.
The AMF deploys the Access and mobility related policy information, which includes storing the Service Area Restrictions and Policy Control Request Trigger of AM Policy Association, provisioning of the Service Area Restrictions to the UE and provisioning the RFSP index, UE-AMBR and Service Area Restrictions to the NG-RAN.
Up
4.16.3  AM Policy Association Termination
4.16.3.1  General
The following case is considered for AM 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.
4.16.3.2  AMF-initiated AM Policy Association TerminationWord-p. 324
Up
This procedure concerns both roaming and non-roaming scenarios.
In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF.
Step 1.
The AMF decides to terminate the AM Policy Association during Deregistration procedure or due to mobility with change of AMF and (V-)PCF in the registration procedure or handover procedure, then if a AM Policy Association was established with the (V-)PCF steps 2 to 3 are performed.
Step 2.
The AMF sends the Npcf_AMPolicyControl_Delete service operation including AM 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.
Step 4.
The AMF removes the AM Policy Association for this UE, including the Access and Mobility Control Policy related to the UE. The AMF deletes the subscription to AMF detected events requested for that Policy Association.
Up
4.16.3.3Void

Up   Top   ToC