ETSI TS 129 513 V15.6.0 (2020-01)

5G; 5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3 (3GPP TS 29.513 version 15.6.0 Release 15)

RTS/TSGC-0329513vf60

General Information

• Status: Published
• Publication Date: 14-Jan-2020
• Technical Committee: 3GPP CT 3 - Interworking with external networks (formely CN3)
• Current Stage: 12 - Completion
• Completion Date: 15-Jan-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G System;
Policy and Charging Control signalling flows and QoS
parameter mapping;
Stage 3
(3GPP TS 29.513 version 15.6.0 Release 15)

3GPP TS 29.513 version 15.6.0 Release 15 1 ETSI TS 129 513 V15.6.0 (2020-01)

Reference
RTS/TSGC-0329513vf60
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 2 ETSI TS 129 513 V15.6.0 (2020-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 3 ETSI TS 129 513 V15.6.0 (2020-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Reference architecture . 9
5 Signalling Flows for the Policy Framework . 13
5.1 AM Policy Association Management . 13
5.1.1 AM Policy Association Establishment . 13
5.1.2 AM Policy Association Modification . 14
5.1.2.1 AM Policy Association Modification initiated by the AMF . 14
5.1.2.1.1 AM Policy Association Modification initiated by the AMF without AMF relocation . 14
5.1.2.1.2 AM Policy Association Modification with old PCF during AMF relocation . 15
5.1.2.2 AM Policy Association Modification initiated by the PCF . 16
5.1.3 AM Policy Association Termination . 17
5.1.3.1 AM Policy Association Termination initiated by the AMF . 17
5.1.3.2 AM Policy Association Termination initiated by the PCF . 18
5.2 SM Policy Association Management . 20
5.2.1 SM Policy Association Establishment . 20
5.2.2 SM Policy Association Modification . 21
5.2.2.1 General . 21
5.2.2.2 SM Policy Association Modification initiated by the PCF . 21
5.2.2.2.1 Interactions between SMF, PCF and CHF. 21
5.2.2.2.2 Interactions between PCF, AF and UDR . 22
5.2.2.2.2.1 AF Session Establishment . 22
5.2.2.2.2.2 AF Session Modification . 24
5.2.2.2.2.3 AF Session Termination . 25
5.2.2.3 SM Policy Association Modification initiated by the SMF . 26
5.2.3 SM Policy Association Termination . 29
5.2.3.1 SM Policy Association Termination initiated by the SMF. 29
5.2.3.2 SM Policy Association Termination initiated by the PCF . 31
5.3 Spending Limit Procedures . 31
5.3.1 General . 31
5.3.2 Initial Spending Limit Report Request . 31
5.3.3 Intermediate Spending Limit Report Request . 32
5.3.4 Final Spending Limit Report Request . 33
5.3.5 Spending Limit Report. 33
5.3.6 Subscription termination request by CHF . 34
5.4 Network Data Analytics Procedures . 35
5.4.1 General . 35
5.4.2 Network data analytics Subscribe/Unsubscribe . 35
5.4.3 Network data analytics info request . 36
5.5 Service Capability Exposure Procedures . 37
5.5.1 General . 37
5.5.2 Management of Packet Flow Descriptions . 37
5.5.2.1 AF-initiated PFD management procedure . 37
5.5.2.2 PFD management towards SMF . 38
5.5.2.2.1 PFD retrieval . 38
5.5.2.2.2 PFD management . 39
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 4 ETSI TS 129 513 V15.6.0 (2020-01)
5.5.3 Traffic influence procedures . 40
5.5.3.1 General . 40
5.5.3.2 AF requests targeting an individual UE address . 41
5.5.3.3 AF requests targeting PDU Sessions not identified by an UE address . 42
5.5.4 Negotiation for future background data transfer procedure . 45
5.6 UE Policy Association Management . 46
5.6.1 UE Policy Association Establishment . 46
5.6.1.1 General . 46
5.6.1.2 Non-roaming . 47
5.6.1.3 Roaming . 49
5.6.2 UE Policy Association Modification . 51
5.6.2.1 UE Policy Association Modification initiated by the AMF . 51
5.6.2.1.1 General . 51
5.6.2.1.2 Non-roaming . 51
5.6.2.1.3 Roaming . 52
5.6.2.2 UE Policy Association Modification initiated by the PCF . 53
5.6.2.2.1 General . 53
5.6.2.2.2 Non-roaming . 53
5.6.2.2.3 Roaming . 54
5.6.3 UE Policy Association Termination . 55
5.6.3.1 UE Policy Association Termination initiated by the AMF . 55
5.6.3.1.1 General . 55
5.6.3.1.2 Non-roaming . 56
5.6.3.1.3 Roaming . 57
5.6.3.2 UE Policy Association Termination initiated by the PCF . 57
5.6.3.2.1 General . 57
5.6.3.2.2 Non-roaming . 58
5.6.3.2.3 Roaming . 59
6 Binding Mechanism . 60
6.1 Overview . 60
6.2 Session Binding . 60
6.3 PCC rule Authorization . 61
6.4 QoS flow binding . 61
7 QoS Parameters Mapping . 63
7.1 Overview . 63
7.2 QoS parameter mapping Functions at AF . 64
7.2.1 Introduction. 64
7.2.2 AF supporting Rx interface . 65
7.2.3 AF supporting N5 interface . 65
7.3 QoS parameter mapping Functions at PCF . 65
7.3.1 Introduction. 65
7.3.2 PCF Interworking with an AF supporting Rx interface . 65
7.3.3 PCF Interworking with an AF supporting N5 interface . 72
7.4 QoS parameter mapping Functions at SMF . 79
8 PCF addressing . 79
8.1 General . 79
8.2 PCF discovery and selection by the AMF . 79
8.3 PCF discovery and selection by the SMF . 80
8.4 PCF discovery and selection by the AF. 80
8.4.1 General . 80
8.4.2 Binding Support Function (BSF) . 80
8.5 BSF procedures . 81
8.5.1 General . 81
8.5.2 Binding information Creation . 81
8.5.3 Binding information Deletion . 82
8.5.4 Binding information Retrieval . 82
8.5.5 Proxy BSF . 82
8.5.5.1 General . 82
8.5.5.2 Rx Session Establishment . 83
8.5.5.3 Rx Session Modification . 83
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 5 ETSI TS 129 513 V15.6.0 (2020-01)
8.5.5.3.1 AF-initiated . 83
8.5.5.3.2 PCF-initiated . 84
8.5.5.4 Rx Session Termination . 84
8.5.5.4.1 AF-initiated . 84
8.5.5.4.2 PCF-initiated . 85
8.5.6 Redirect BSF . 85
8.5.6.1 General . 85
8.5.6.2 Rx Session Establishment . 86
Annex A (informative): DRA and BSF coexistence . 87
Annex B (informative): Change history . 88
History . 91

ETSI
3GPP TS 29.513 version 15.6.0 Release 15 6 ETSI TS 129 513 V15.6.0 (2020-01)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 7 ETSI TS 129 513 V15.6.0 (2020-01)
1 Scope
The present document specifies detailed call flows of Policy and Charging Control (PCC) over the Npcf, Nsmf, Namf,
Nudr, Nnef, Nchf, Nbsf and Nnwdaf service-based interfaces and their relationship with the flow level signalling in 5G
system.
NOTE: The call flows depicted in this Technical Specification do not cover all traffic cases.
The stage 2 definition and procedures of PCC are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4]. The 5G
System Architecture is defined in 3GPP TS 23.501 [2].
Detailed stage 3 procedures are provided in 3GPP TS 29.507 [7], 3GPP TS 29.508 [8], 3GPP TS 29.512 [9],
3GPP TS 29.514 [10], 3GPP TS 29.520 [11], 3GPP TS 29.519 [12], 3GPP TS 29.521 [22], 3GPP TS 29.594 [23],
3GPP TS 29.522 [24], 3GPP TS 29.551 [25], 3GPP TS 29.525 [31] and 3GPP TS 29.554 [26].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
of the 5G System are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The present specification also describes the PCC reference architectures for non-roaming and roaming scenarios in 5G
system.
The present specification also describes the mapping of QoS parameters at AF, PCF and SMF.
The present specification also describes the session binding at PCF, and the QoS flow binding at SMF.
The present specification also describes the PCF addressing.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[5] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[6] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[7] 3GPP TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3".
[8] 3GPP TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".
[9] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[10] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[11] 3GPP TS 29.520: "5G System; Network Data Analytics Services; Stage 3".
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 8 ETSI TS 129 513 V15.6.0 (2020-01)
[12] 3GPP TS 29.519: "5G System; Usage of the Unified Data Repository Service for Policy Data,
Application Data and Structured Data for Exposure; Stage 3".
[13] 3GPP TS 23.203: "Policies and Charging control architecture; Stage 2".
[14] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and
interaction".
[15] 3GPP TS 29.201: "Representational State Transfer (REST) reference point between Application
Function (AF) and Protocol Converter (PC)".
[16] IETF RFC 4566: "SDP: Session Description Protocol".
[17] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS) Progressive
Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[18] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".
[19] 3GPP TS 26.234: "End-to-end transparent streaming service; Protocols and codecs".
[20] 3GPP2 C.S0046-0 v1.0: "3G Multimedia Streaming Services".
[21] 3GPP2 C.S0055-A v1.0: "Packet Switched Video Telephony Services (PSVT/MCS)".
[22] 3GPP TS 29.521: "5G System; Binding Support Management Service; Stage 3".
[23] 3GPP TS 29.594: "5G System; Spending Limit Control Service; Stage 3".
[24] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[25] 3GPP TS 29.551: "5G System; Packet Flow Description Management Service; Stage 3".
[26] 3GPP TS 29.554: "5G System; Background Data Transfer Policy Control Service; Stage 3".
[27] 3GPP TS 29.504: "5G System; Unified Data Repository Services; Stage 3".
[28] 3GPP TS 32.240: "Charging management; Charging architecture and principles".
[29] IETF RFC 6733: "Diameter Base Protocol".
[30] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS)
parameter mapping".
[31] 3GPP TS 29.525: "UE Policy Control Service; Stage 3".
[32] 3GPP TS 29.518: "Access and Mobility Management Services; Stage 3".
[33] 3GPP TS 24.501: " Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 9 ETSI TS 129 513 V15.6.0 (2020-01)
5GC 5G Core Network
5QI 5G QoS Identifier
AF Application Function
AMBR Aggregate Maximum Bit Rate
AMF Access and Mobility Management Function
ARP Allocation and Retention Priority
AW Average Window
BSF Binding Support Function
CHF Charging Function
LBO Local Breakout
MBR Maximum Bitrate
MPD Media Presentation Description
MPS Multimedia Priority Service
NEF Network Exposure Function
NRF Network Repository Function
NWDAF Network Data Analytics Function
PCC Policy and Charging Control
PCF Policy Control Function
PDB Packet Delay Budget
PER Packet Error Rate
PFD Packet Flow Description
PFDF Packet Flow Description Function
PL Priority Level
QNC QoS Notification Control
QoS Quality of Service
SDP Session Description Protocol
SEPP Security Edge Protection Proxy
SMF Session Management Function
S-NSSAI Single Network Slice Selection Assistance Information
UDR Unified Data Repository
UPF User Plane Function
UPSI UE policy section identifier
4 Reference architecture
The policy framework functionality in 5G is comprised by the functions of the Policy Control Function (PCF), the
policy and charging enforcement functionality supported by SMF and UPF, the access and mobility policy enforcement
functionality supported by the AMF, the Network Data Analytics Function (NWDAF), the Network Exposure Function
(NEF), the Charing Function (CHF), the Unified Data Repository (UDR) and the Application Function (AF). For the
roaming scenario, the Security Edge Protection Proxy (SEPP) is deployed between the V-PCF and H-PCF.
3GPP TS 23.503 [4] specifies the 5G policy framework stage 2 functionality.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 10 ETSI TS 129 513 V15.6.0 (2020-01)
NEF UDR PCF AF NWDAF CHF
Nchf
Nnef Nudr Naf Nnwdaf
Npcf
Namf Nsmf
AMF
SMF
N4
UPF
Figure 4.1-1a: Overall non-roaming 5G Policy framework architecture (service based representation)

NWDAF NEF CHF
UDR AF
N28 N40
N36 N5 N23 N30 N29
PCF
N15 N7
AMF SMF
N4
UPF
Figure 4.1-1b: Overall non-roaming 5G Policy framework architecture (reference point representation)
NOTE 1: The N4 interface is not part of the Policy Framework architecture but shown in the figures for
completeness.
The Nchf service for online and offline charging consumed by the SMF is defined in 3GPP TS 32.240 [28].
The Nchf service for Spending Limit Control consumed by the PCF is defined in 3GPP TS 29.594 [23].
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 11 ETSI TS 129 513 V15.6.0 (2020-01)

VPLMN HPLMN
NEF NWDAF AF V-PCF H-PCF UDR
Nudr
Nnwdaf Naf Npcf Npcf
Nnef
N32
vSEPP hSEPP
Namf
Nsmf
AMF
SMF
N4
UPF
Figure 4.1-2a: Overall roaming policy framework architecture - LBO (service based representation)

VPLMN HPLMN
NEF AF NWDAF UDR
N30
N5 N23 N36
N24
H-PCF
V-PCF
N15 N7
AMF SMF
N4
UPF
Figure 4.1-2b: Overall roaming policy framework architecture - LBO (reference point representation)
NOTE 2: In the LBO scenario, the PCF in the VPLMN may interact with the AF in order to generate PCC rules for
services delivered via the VPLMN. The PCF in the VPLMN uses locally configured policies according to
the roaming agreement with the HPLMN operator as input for PCC rule generation. The PCF in VPLMN
has no access to subscriber policy information from the HPLMN to retrieve input for PCC Rule
generation. The interactions between the PCF in the VPLMN and the PCF in the HPLMN through the
Npcf service based interface enables the PCF in the HPLMN to provision UE policies to the PCF in the
VPLMN, as described in 3GPP TS 23.503 [4] subclause 5.2.5.
NOTE 3: In the LBO scenario, AF requests targeting a DNN (and slice) and / or a group of UEs are stored in the
UDR by the NEF. The PCF in the VPLMN subscribes to and get notification from the UDR in the
VPLMN for those AF requests. Details are defined in subclause 5.6.7 of 3GPP TS 23.501 [2].
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 12 ETSI TS 129 513 V15.6.0 (2020-01)
NOTE 4: For the sake of clarity, SEPPs are not depicted in the roaming reference point architecture figures.
NOTE 5: N4 and N32 are not service based interfaces.

VPLMN HPLMN
V-PCF
AF NEF H-PCF UDR CHF NWDAF
Naf Npcf Nudr
Npcf
Nnef Nnwdaf
Nchf
N32
vSEPP hSEPP
Nsmf
Namf
SMF
AMF
N4
UPF
Figure 4.1-3a: Overall roaming policy framework architecture - home routed scenario (service based
representation)
VPLMN HPLMN
NWDAF UDR AF NEF CHF
N5 N30 N29 N28 N40
N36
N23
N24
V-PCF
H-PCF
N15 N7
AMF
SMF
N4
UPF
Figure 4.1-3b: Overall roaming policy framework architecture - home routed scenario (reference point
representation)
NOTE 6: For the sake of clarity, SEPPs are not depicted in the roaming reference point architecture figures.
NOTE 7: N4 and N32 are not service based interfaces.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 13 ETSI TS 129 513 V15.6.0 (2020-01)
To allow the 5G system to interwork with AFs related to existing services, e.g. IMS based services, Mission Critical
Push To Talk services, the PCF shall support the corresponding Rx procedures and requirements defined in
3GPP TS 29.214 [18]. This facilitates the migration from EPC to 5GC without requiring these AFs to upgrade to
support the N5 interface.
Rx
PCF AF
Figure 4.1-4: Interworking between 5G Policy framework and AFs supporting Rx interface
5 Signalling Flows for the Policy Framework
5.1 AM Policy Association Management
5.1.1 AM Policy Association Establishment
This procedure concerns the following scenarios:
1. UE initial registration with the network.
2. The AMF re-allocation with PCF change in handover procedure and registration procedure.
3. UE registers with 5GS during the UE moving from EPS to 5GS when there is no existing AM Policy
Association.
AMF (V-)PCF UDR
1. Npcf_AMPolicyControl_Create request

2. Nudr_DataRepository_Query request

3. Nudr_DataRepository_Query response

4. Nudr_DataRepository_Subscribe request

5. Nudr_DataRepository_Subscribe response

6. Policy Decision
7. Npcf_AMPolicyControl_Create response
8. Deploy Access and
Mobility control policy
Figure 5.1.1-1: AM Policy Association Establishment procedure
This procedure concerns both roaming and non-roaming scenarios.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 14 ETSI TS 129 513 V15.6.0 (2020-01)
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 2 - step 5 are not executed in the roaming case.
1. The AMF receives the registration request from the AN. Based on local policy, the AMF selects to contact the
(V-) PCF to create the policy association with the (V-) PCF and to retrieve Access and Mobility control policy.
The AMF selects the PCF as described in subclause 8.2 and invokes the Npcf_AMPolicyControl_Create service
operation by sending the HTTP POST request to the "AM Policy Associations" resource. The request operation
provides the SUPI, and if received from the UDM, the Service Area Restrictions, RFSP index, and GPSI, and
may provide the access type, the PEI if received in the AMF, the User Location Information if available, the UE
Time Zone if available, Serving Network, RAT type. The request includes a Notification URI to indicate to the
PCF where to send a notification when the policy is updated.
2. If the PCF does not have the subscription data, it invokes the Nudr_DataRepository_Query service operation to
the UDR by sending an HTTP GET request to the "AccessAndMobilityPolicyData " resource as specified in
TS 29.519 [12]
3. The UDR sends an HTTP "200 OK" response to the PCF with the subscription data.
4. The PCF may request notifications from the UDR on changes in the subscription information by invoking
Nudr_DataRepository_Subscribe service operation by sending an HTTP POST request to the
"PolicyDataSubscriptions" resource as specified in 3GPP TS 29.519 [12].
5. The UDR sends an HTTP "201 Created" response to acknowledge the subscription from the PCF.
6. The (V-)PCF makes the requested policy decision including Access and Mobility control policy information, and
may determine applicable Policy Control Request Trigger(s).
7. The (V)PCF sends an HTTP "201 Created" response to the AMF with the determined policies as described in
subclause 4.2.2 of 3GPP TS 29.507 [7]:
- Access and Mobility control Policy including Service Area Restrictions, and/or a RAT Frequency Selection
Priority (RFSP) Index; and/or
- Policy Control Request Trigger parameters;
NOTE: The PCF can reject the AM Policy Association establishment, e.g. the PCF cannot obtain the
subscription-related information from the UDR and the PCF cannot make the policy decisions, as
described in 3GPP TS 29.512 [9]. In this case, the remaining steps in this procedure are not followed.
8. The AMF deploys the Access and Mobility control policy information if received which includes storing the
Service Area Restrictions, provisioning the Service Area Restrictions to the UE and/ or provisioning the RFSP
index and Service Area Restrictions to the NG-RAN.
5.1.2 AM Policy Association Modification
5.1.2.1 AM Policy Association Modification initiated by the AMF
5.1.2.1.1 AM Policy Association Modification initiated by the AMF without AMF relocation
This procedure is performed when a Policy Control Request Trigger condition is met.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 15 ETSI TS 129 513 V15.6.0 (2020-01)

AMF (V-)PCF
1. A policy control
request trigger is
triggered
2. Npcf_AMPolicyControl_Update request
3. Policy Decision
4. Npcf_AMPolicyControl_Update response
5. Deploy Access and
Mobility control policy
Figure 5.1.2.1.1-1: AMF-initiated AM Policy Association Modification without AMF relocation
procedure
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.
1. The AMF detects a Policy Control Request Trigger condition is met.
2. The AMF invokes the Npcf_AMPolicyControl_Update service operation to the (V-) PCF by sending the HTTP
POST request to the "Individual AM Policy Association" resource with information on the conditions that have
changed.
3. The (V)PCF stores the information received in step 2 and makes the policy decision.
4. The (V)PCF sends an HTTP "200 OK" response to the AMF with the updated Access and Mobility control
policy information and/ or the updated Policy Control Request Trigger parameters.
5. The AMF deploys the Access and Mobility control policy if received, which includes storing the Service Area
Restrictions, provisioning the Service Area Restrictions to the NG-RAN and UE, and/or provisioning the RFSP
index to the NG-RAN.
5.1.2.1.2 AM Policy Association Modification with old PCF during AMF relocation
This procedure is performed when AMF relocation is performed and the old PCF is selected by the target AMF.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 16 ETSI TS 129 513 V15.6.0 (2020-01)

New AMF (V-)PCF
Old AMF
1.UE Context retrieval from old AMF
2.Decision to establish
Policy Association
3. Npcf_AMPolicyControl_Update Request
4. Policy decision
5. Npcf_AMPolicyControl_Update Response
6. Deploy access and
mobility control policy
Figure 5.1.2.1.2-1: AMF-initiated AM Policy Association Modification with old PCF during AMF
relocation procedure
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.
1. 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 resource URI (i.e.
{apiRoot}/npcf-am-policy-control/v1/policies/{polAssoId}) of AM Policy Association at the (V-)PCF).
2. Based on local policies, the new AMF decides to contact with (V-)PCF and update the resource identified by the
resource URI received in step 1.
3. The new AMF invokes the Npcf_AMPolicyControl_Update service operation to the (V-) PCF by sending the
HTTP POST request to the "Individual AM Policy Association" resource with the Notification URI of the new
AMF. The request may also include the met policy control request trigger(s) and corresponding information.
4. The (V-)PCF updates the stored information provided by the old AMF with the information provided by the new
AMF and make the policy decision.
5. The PCF sends an HTTP "200 OK" response to the AMF with the updated Access and Mobility control policy
information and/or the updated Policy Control Request Trigger parameters.
6. The AMF deploys the Access and Mobility control policy if received, which includes storing the Service Area
Restrictions, provisioning the Service Area Restrictions to the NG-RAN and UE, and/or provisioning the RFSP
index to the NG-RAN.
5.1.2.2 AM Policy Association Modification initiated by the PCF
This procedure is performed when the Access and Mobility control policies are changed.
ETSI
3GPP TS 29.513 version 15.6.0 Release 15 17 ETSI TS 129 513 V15.6.0 (2020-01)

AMF
(V-)PCF
1.trigger
2. Policy Decision
3. Npcf_AMPolicyControl_UpdateNotify request

4. Npcf_AMPolicyControl_U
...