SM PCF Jul2020

3GPP TS 29.512 V16.5.
0 (2020-06)
Technical Specification
3rd Generation Partnership Project;

Technical Specification Group Core Network and Terminals;
5G System; Session Management Policy Control Service;
Stage 3
(Release 16)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP..
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 16 2 3GPP TS 29.512 V16.5.0 (2020-06)
Keywords
3GPP
Postal address
3GPP support office address

650 Route des Lucioles – Sophia Antipolis
Valbonne – FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.
© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
3GPP
Release 16 3 3GPP TS 29.512 V16.5.0 (2020-06)
Contents
Foreword........................................................................................................................................................... 10
1 Scope ...................................................................................................................................................... 11
2 References .............................................................................................................................................. 11
3 Definitions, symbols and abbreviations ................................................................................................. 13
3.1 Definitions ....................................................................................................................................................... 13
3.2 Abbreviations................................................................................................................................................... 13
4 Npcf_SMPolicyControl Service ............................................................................................................. 14
4.1 Service Description .......................................................................................................................................... 14
4.1.1 Overview .................................................................................................................................................... 14
4.1.2 Service Architecture ................................................................................................................................... 14
4.1.3 Network Functions ..................................................................................................................................... 15
4.1.3.1 Policy Control Function (PCF) ............................................................................................................. 15
4.1.3.2 NF Service Consumers ......................................................................................................................... 16
4.1.4 Rules........................................................................................................................................................... 16
4.1.4.1 General ................................................................................................................................................. 16
4.1.4.2 PCC rules .............................................................................................................................................. 16
4.1.4.2.1 PCC rules definition ........................................................................................................................ 16
4.1.4.2.2 PCC rules operation ........................................................................................................................ 20
4.1.4.3 Session rule ........................................................................................................................................... 20
4.1.4.3.1 Session rules definition ................................................................................................................... 20
4.1.4.3.2 Session rules operation ................................................................................................................... 20
4.1.4.4 Policy Decision types ........................................................................................................................... 21
4.1.4.4.1 General ............................................................................................................................................ 21
4.1.4.4.2 Traffic control data definition ......................................................................................................... 21
4.1.4.4.3 QoS data definition ......................................................................................................................... 21
4.1.4.4.4 Charging data definition ................................................................................................................. 22
4.1.4.4.5 UsageMonitoring data definition .................................................................................................... 22
4.1.4.4.6 QoS Monitoring data definition ...................................................................................................... 23
4.1.5 Policy control request trigger ..................................................................................................................... 23
4.1.6 Requested rule data .................................................................................................................................... 24
4.1.7 Requested usage data ................................................................................................................................. 24
4.1.8 Condition data ............................................................................................................................................ 24
4.2 Service Operations ........................................................................................................................................... 24
4.2.1 Introduction ................................................................................................................................................ 24
4.2.2 Npcf_SMPolicyControl_Create Service Operation.................................................................................... 25
4.2.2.1 General ................................................................................................................................................. 25
4.2.2.2 SM Policy Association establishment .................................................................................................. 26
4.2.2.3 Provisioning of charging related information for PDU session ............................................................ 29
4.2.2.3.1 Provisioning of Charging Addresses ............................................................................................... 29
4.2.2.3.2 Provisioning of Default Charging Method ...................................................................................... 29
4.2.2.4 Provisioning of revalidation time ......................................................................................................... 29
4.2.2.5 Policy provisioning and enforcement of authorized AMBR per PDU session ..................................... 30
4.2.2.6 Policy provisioning and enforcement of authorized default QoS ......................................................... 30
4.2.2.7 Provisioning of PCC rule for Application Detection and Control ........................................................ 30
4.2.2.8 3GPP PS Data Off Support ................................................................................................................... 30
4.2.2.9 IMS Emergency Session Support ......................................................................................................... 31
4.2.2.10 Request Usage Monitoring Control ...................................................................................................... 31
4.2.2.11 Access Network Charging Identifier report .......................................................................................... 31
4.2.2.12 Request for the successful resource allocation notification .................................................................. 32
4.2.2.13 Request of Presence Reporting Area Change Report ........................................................................... 32
4.2.2.14 Provisioning of IP Index Information ................................................................................................... 32
4.2.2.15 Negotiation of the QoS flow for IMS signalling .................................................................................. 32
4.2.2.16 PCF resource cleanup ........................................................................................................................... 32
4.2.2.17 Access traffic steering, switching and splitting support ....................................................................... 32
4.2.2.18 DNN Selection Mode Support .............................................................................................................. 33
3GPP
Release 16 4 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.2.19 Detection of TSN related SM Policy Association ................................................................................ 33

4.2.3 Npcf_SMPolicyControl_UpdateNotify Service Operation ........................................................................ 34
4.2.3.1 General ................................................................................................................................................. 34
4.2.3.2 SM Policy Association Update request ................................................................................................ 35
4.2.3.3 SM Policy Association termination request.......................................................................................... 36
4.2.3.4 Provisioning of revalidation time ......................................................................................................... 36
4.2.3.7 Provisioning of PCC rule for Application Detection and Control ........................................................ 37
4.2.3.9 IMS Emergency Session Support ......................................................................................................... 38
4.2.3.9.1 Provisioning of PCC rule ................................................................................................................ 38
4.2.3.9.2 Removal of PCC Rules for Emergency Services ............................................................................ 38
4.2.3.10 Request of Access Network Information .............................................................................................. 38
4.2.3.11 Request Usage Monitoring Control ...................................................................................................... 38
4.2.3.12 Ipv6 Multi-homing support .................................................................................................................. 38
4.2.3.13 Request for the result of PCC rule removal .......................................................................................... 39
4.2.3.14 Access Network Charging Identifier request ........................................................................................ 39
4.2.3.15 Request for the successful resource allocation notification .................................................................. 39
4.2.3.16 PCC Rule Error Report ......................................................................................................................... 39
4.2.3.17 IMS Restoration Support ...................................................................................................................... 39
4.2.3.18 P-CSCF Restoration Enhancement Support ......................................................................................... 40
4.2.3.19 Request of Presence Reporting Area Change Report ........................................................................... 40
4.2.3.20 Session Rule Error Report .................................................................................................................... 40
4.2.3.22 Policy provisioning and enforcement of the AF session with required QoS ........................................ 41
4.2.3.23 Forwarding of TSN information received from the AF ........................................................................ 41
4.2.3.24 Provisioning of TSCAI input information and TSC QoS related data .................................................. 42
4.2.3.25 Policy provisioning of QoS Monitoring to Assist URLLC Service ...................................................... 42
4.2.3.26 Policy decision and condition data error handling ................................................................................ 43
4.2.4 Npcf_SMPolicyControl_Update Service Operation .................................................................................. 43
4.2.4.1 General ................................................................................................................................................. 43
4.2.4.2 Requesting the update of the Session Management related policies..................................................... 44
4.2.4.3 Request the policy based on revalidation time ..................................................................................... 46
4.2.4.6 Application detection information reporting ........................................................................................ 47
4.2.4.7 Indication of QoS Flow Termination Implications ............................................................................... 47
4.2.4.9 Request and Report of Access Network Information ........................................................................... 49
4.2.4.10 Request Usage Monitoring Control and Reporting Accumulated Usage ............................................. 49
4.2.4.11 Ipv6 Multi-homing support .................................................................................................................. 50
4.2.4.12 Request and report for the result of PCC rule removal ......................................................................... 51
4.2.4.13 Access Network Charging Identifier request and report....................................................................... 51
4.2.4.14 Request and report for the successful resource allocation notification ................................................. 51
4.2.4.15 PCC Rule Error Report ......................................................................................................................... 51
4.2.4.16 Presence Reporting Area Information Report ...................................................................................... 52
4.2.4.17 UE initiates a resource modification support ........................................................................................ 53
4.2.4.18 Trace Control ........................................................................................................................................ 54
4.2.4.19 Negotiation of the QoS flow for IMS signalling .................................................................................. 54
4.2.4.20 Notification about Service Data Flow QoS target enforcement ........................................................... 54
4.2.4.21 Session Rule Error Report .................................................................................................................... 55
4.2.4.22 Request the termination of SM Policy association ............................................................................... 56
4.2.4.23 Reporting of TSN information.............................................................................................................. 56
4.2.4.24 Notification about Service Data Flow QoS Monitoring ....................................................................... 56
4.2.4.26 Policy decision and condition data error handling ................................................................................ 57
4.2.4.27 Policy Control for DDN Failure Events ............................................................................................... 57
4.2.5 Npcf_SMPolicyControl_Delete Service Operation.................................................................................... 57
4.2.5.1 General ................................................................................................................................................. 57
4.2.5.2 SM Policy Association termination ...................................................................................................... 58
4.2.5.3 Report Accumulated Usage .................................................................................................................. 58
3GPP
Release 16 5 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.5.4 Report Access Network Information .................................................................................................... 58

4.2.6 Provisioning and Enforcement of Policy Decisions ................................................................................... 59
4.2.6.1 General ................................................................................................................................................. 59
4.2.6.2 PCC Rules ............................................................................................................................................ 60
4.2.6.2.1 Overview......................................................................................................................................... 60
4.2.6.2.2 Gate function................................................................................................................................... 62
4.2.6.2.3 Policy enforcement for authorized QoS per PCC Rule ................................................................... 62
4.2.6.2.4 Redirect function............................................................................................................................. 62
4.2.6.2.5 Usage Monitoring Control .............................................................................................................. 63
4.2.6.2.6 Traffic Steering Control support ..................................................................................................... 63
4.2.6.2.6.1 Steering the traffic in the N6-LAN ............................................................................................ 63
4.2.6.2.6.2 Steering the traffic to a local access of the data network........................................................... 63
4.2.6.2.7 Conditioned PCC rule ..................................................................................................................... 65
4.2.6.2.8 PCC rule for resource sharing ......................................................................................................... 66
4.2.6.2.9 Resource reservation for services sharing priority .......................................................................... 67
4.2.6.2.10 PCC rule bound to the default QoS flow ........................................................................................ 68
4.2.6.2.11 PCC rule for Application Detection and Control ............................................................................ 69
4.2.6.2.12 Provisioning of PCC Rules for Multimedia Priority Services......................................................... 69
4.2.6.2.12.1 General ...................................................................................................................................... 69
4.2.6.2.12.2 Invocation/Revocation of Priority PDU connectivity services .................................................. 70
4.2.6.2.12.3 Invocation/Revocation of IMS Multimedia Priority Services ................................................... 70
4.2.6.2.13 Sponsored Data Connectivity.......................................................................................................... 71
4.2.6.2.14 Support for PCC rule versioning ..................................................................................................... 71
4.2.6.2.15 Background data transfer support ................................................................................................... 72
4.2.6.2.16 Number of supported packet filter for signalled QoS rule limitation support ................................. 72
4.2.6.2.17 Access traffic steering, switching and splitting support .................................................................. 72
4.2.6.2.18 Void ................................................................................................................................................ 75
4.2.6.2.19 Provisioning of PCC Rules for Mission Critical Services .............................................................. 75
4.2.6.2.19.1 General ...................................................................................................................................... 75
4.2.6.2.19.2 Invocation/Revocation of Priority PDU connectivity services .................................................. 76
4.2.6.2.19.3 Invocation/Revocation of IMS Mission Critical Services ......................................................... 76
4.2.6.3 Session Rules ........................................................................................................................................ 77
4.2.6.3.1 Overview ......................................................................................................................................... 77
4.2.6.3.2 Conditioned Session rule ................................................................................................................ 78
4.2.6.3.2.1 General ...................................................................................................................................... 78
4.2.6.3.2.2 Time conditioned authorized session AMBR ............................................................................ 79
4.2.6.3.2.3 Time conditioned authorized default QoS ................................................................................. 79
4.2.6.3.2.4 Access type conditioned authorized session AMBR ................................................................. 79
4.2.6.3.3 Provisioning of authorized default QoS .......................................................................................... 79
4.2.6.3.4 Access traffic steering, switching and splitting support .................................................................. 80
4.2.6.4 Policy control request triggers .............................................................................................................. 80
4.2.6.5 Encoding of the request of information reporting................................................................................. 80
4.2.6.5.1 Request of Access Network Charging Identifier ............................................................................. 80
4.2.6.5.2 RAN NAS Cause Support ............................................................................................................... 81
4.2.6.5.3 Provisioning of the Usage Monitoring Control Policy .................................................................... 81
4.2.6.5.4 Request for Access Network Information ....................................................................................... 82
4.2.6.5.5 Request for the successful resource allocation notification ............................................................ 82
4.2.6.5.6 Provisioning of Presence Reporting Area Information ................................................................... 83
4.2.6.5.7 Policy provisioning and enforcement of reflective QoS ................................................................. 83
4.2.6.6 Authorized QoS .................................................................................................................................... 84
4.2.6.6.1 General ............................................................................................................................................ 84
4.2.6.6.2 Policy provisioning and enforcement of authorized QoS per service data flow ............................. 85
4.2.6.6.3 Policy provisioning and enforcement of authorized explicitly signalled QoS Characteristics ....... 86
4.2.7 Detection and handling of late arriving requests ........................................................................................ 86
4.2.7.1 Handling of requests which collide with an existing SM Policy Association ...................................... 86
5 Npcf_SMPolicyControl Service API ..................................................................................................... 87
5.1 Introduction...................................................................................................................................................... 87
5.2 Usage of HTTP ................................................................................................................................................ 87
5.2.1 General ....................................................................................................................................................... 87
5.2.2 HTTP standard headers .............................................................................................................................. 87
5.2.2.1 General ................................................................................................................................................. 87
3GPP
Release 16 6 3GPP TS 29.512 V16.5.0 (2020-06)
5.2.2.2 Content type.......................................................................................................................................... 87

5.2.3 HTTP custom headers ................................................................................................................................ 88
5.2.3.1 General ................................................................................................................................................. 88
5.2.3.2 3gpp-Sbi-Origination-Timestamp......................................................................................................... 88
5.3 Resources ......................................................................................................................................................... 88
5.3.1 Resource Structure ..................................................................................................................................... 88
5.3.2 Resource: SM Policies ............................................................................................................................... 89
5.3.2.1 Description ........................................................................................................................................... 89
5.3.2.2 Resource definition ............................................................................................................................... 89
5.3.2.3 Resource Standard Methods ................................................................................................................. 89
5.3.2.3.1 POST............................................................................................................................................... 89
5.3.2.4 Resource Custom Operations ............................................................................................................... 90
5.3.3 Resource: Individual SM Policy................................................................................................................. 90
5.3.3.1 Description ........................................................................................................................................... 90
5.3.3.2 Resource definition ............................................................................................................................... 90
5.3.3.3 Resource Standard Methods ................................................................................................................. 90
5.3.3.3.1 GET................................................................................................................................................. 90
5.3.3.4 Resource Custom Operations ............................................................................................................... 91
5.3.3.4.1 Overview ......................................................................................................................................... 91
5.3.3.4.2 Operation: delete ............................................................................................................................. 91
5.3.3.4.2.1 Description ................................................................................................................................ 91
5.3.3.4.2.2 Operation Definition ................................................................................................................. 91
5.3.3.4.3 Operation: update ............................................................................................................................ 91
5.3.3.4.3.1 Description ................................................................................................................................ 91
5.3.3.4.3.2 Operation Definition ................................................................................................................. 91
5.4 Custom Operations without associated resources ............................................................................................ 92
5.5 Notifications .................................................................................................................................................... 92
5.5.1 General ....................................................................................................................................................... 92
5.5.2 Policy Update Notification ......................................................................................................................... 92
5.5.2.1 Description ........................................................................................................................................... 92
5.5.2.2 Operation Definition ............................................................................................................................. 92
5.5.3 Request for termination of the policy association ...................................................................................... 93
5.5.3.1 Description ........................................................................................................................................... 93
5.5.3.2 Operation Definition ............................................................................................................................. 93
5.6 Data Model ...................................................................................................................................................... 93
5.6.1 General ....................................................................................................................................................... 93
5.6.2 Structured data types .................................................................................................................................. 99
5.6.2.1 Introduction .......................................................................................................................................... 99
5.6.2.2 Type SmPolicyControl ......................................................................................................................... 99
5.6.2.3 Type SmPolicyContextData ............................................................................................................... 100
5.6.2.4 Type SmPolicyDecision ..................................................................................................................... 102
5.6.2.5 Type SmPolicyNotification ................................................................................................................ 104
5.6.2.6 Type PccRule...................................................................................................................................... 105
5.6.2.7 Type SessionRule ............................................................................................................................... 107
5.6.2.8 Type QosData ..................................................................................................................................... 108
5.6.2.9 Type ConditionData ........................................................................................................................... 109
5.6.2.10 Type TrafficControlData .................................................................................................................... 110
5.6.2.11 Type ChargingData ............................................................................................................................ 111
5.6.2.12 Type UsageMonitoringData ............................................................................................................... 112
5.6.2.13 Type RedirectInformation .................................................................................................................. 113
5.6.2.14 Type FlowInformation ........................................................................................................................ 114
5.6.2.15 Type SmPolicyDeleteData ................................................................................................................. 115
5.6.2.16 Type QosCharacteristics ..................................................................................................................... 115
5.6.2.17 Type ChargingInformation ................................................................................................................. 116
5.6.2.18 Type AccuUsageReport ...................................................................................................................... 116
5.6.2.19 Type SmPolicyUpdateContextData .................................................................................................... 117
5.6.2.20 Type UpPathChgEvent ....................................................................................................................... 119
5.6.2.21 Type TerminationNotification ............................................................................................................ 119
5.6.2.22 Type AppDetectionInfo ...................................................................................................................... 119
5.6.2.23 Type AccNetChId ............................................................................................................................... 119
5.6.2.24 Type RequestedRuleData ................................................................................................................... 120
5.6.2.25 Type RequestedUsageData ................................................................................................................. 120
3GPP
Release 16 7 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.26 Type UeCampingRep ......................................................................................................................... 120

5.6.2.27 Type RuleReport ................................................................................................................................ 121
5.6.2.28 Type RanNasRelCause ....................................................................................................................... 121
5.6.2.29 Type UeInitiatedResourceRequest ..................................................................................................... 121
5.6.2.30 Type PacketFilterInfo ......................................................................................................................... 122
5.6.2.31 Type RequestedQos ............................................................................................................................ 122
5.6.2.32 Type QosNotificationControlInfo ...................................................................................................... 123
5.6.2.33 Type PartialSuccessReport ................................................................................................................. 123
5.6.2.34 Type AuthorizedDefaultQos............................................................................................................... 124
5.6.2.35 Type AccNetChargingAddress ........................................................................................................... 124
5.6.2.36 Type ErrorReport................................................................................................................................ 125
5.6.2.37 Type SessionRuleReport .................................................................................................................... 125
5.6.2.38 Type ServingNfIdentity ...................................................................................................................... 125
5.6.2.39 Type SteeringMode ............................................................................................................................ 126
5.6.2.40 Type QosMonitoringData ................................................................................................................... 127
5.6.2.41 Type TsnBridgeInfo ........................................................................................................................... 128
5.6.2.42 Type QosMonitoringReport ............................................................................................................... 128
5.6.2.43 Type AdditionalAccessInfo ................................................................................................................ 128
5.6.2.44 Void .................................................................................................................................................... 128
5.6.2.45 Type PortManagementContainer ........................................................................................................ 129
5.6.2.46 Type IpMulticastAddressInfo ............................................................................................................. 129
5.6.2.47 Type BridgeManagementContainer.................................................................................................... 129
5.6.3 Simple data types and enumerations ........................................................................................................ 129
5.6.3.1 Introduction ........................................................................................................................................ 129
5.6.3.2 Simple data types ................................................................................................................................ 129
5.6.3.3 Enumeration: FlowDirection .............................................................................................................. 130
5.6.3.4 Enumeration: ReportingLevel ............................................................................................................ 130
5.6.3.5 Enumeration: MeteringMethod .......................................................................................................... 131
5.6.3.6 Enumeration: PolicyControlRequestTrigger ...................................................................................... 132
5.6.3.7 Enumeration: RequestedRuleDataType .............................................................................................. 136
5.6.3.8 Enumeration: RuleStatus .................................................................................................................... 136
5.6.3.9 Enumeration: FailureCode .................................................................................................................. 137
5.6.3.10 Enumeration: AfSigProtocol .............................................................................................................. 138
5.6.3.11 Enumeration: RuleOperation .............................................................................................................. 138
5.6.3.12 Enumeration: RedirectAddressType ................................................................................................... 138
5.6.3.13 Enumeration: QosFlowUsage ............................................................................................................. 139
5.6.3.14 Enumeration: FailureCause ................................................................................................................ 139
5.6.3.15 Enumeration: FlowDirectionRm ........................................................................................................ 139
5.6.3.16 Enumeration: CreditManagementStatus ............................................................................................. 139
5.6.3.17 Enumeration: SessionRuleFailureCode .............................................................................................. 140
5.6.3.18 Enumeration: SteeringFunctionality ................................................................................................... 140
5.6.3.19 Enumeration: SteerModeValue .......................................................................................................... 140
5.6.3.20 Enumeration: MulticastAccessControl ............................................................................................... 140
5.6.3.21 Enumeration RequestedQosMonitoringParameter ............................................................................. 141
5.6.3.22 Enumeration: ReportingFrequency ..................................................................................................... 141
5.6.3.23 Enumeration: SmPolicyAssociationReleaseCause ............................................................................. 141
5.6.3.24 Enumeration: PduSessionRelCause .................................................................................................... 141
5.6.3.25 Enumeration: MaPduIndication .......................................................................................................... 142
5.6.3.26 Enumeration: AtsssCapability ............................................................................................................ 142
5.6.3.27 Enumeration: NetLocAccessSupport .................................................................................................. 142
5.6.3.28 Enumeration: PolicyDecisionFailureCode ......................................................................................... 143
5.7 Error handling ................................................................................................................................................ 143
5.7.1 General ..................................................................................................................................................... 143
5.7.2 Protocol Errors ......................................................................................................................................... 143
5.7.3 Application Errors .................................................................................................................................... 143
5.8 Feature negotiation ........................................................................................................................................ 145
5.9 Security .......................................................................................................................................................... 147
3GPP
Release 16 8 3GPP TS 29.512 V16.5.0 (2020-06)
Annex A (normative): OpenAPI specification ................................................................................. 148

A.1 General ................................................................................................................................................. 148
A.2 Npcf_SMPolicyControl API ................................................................................................................ 148
Annex B (normative): 5GC and EPC interworking scenario support .......................................... 176
B.1 Scope .................................................................................................................................................... 176
B.2 Npcf_SMPolicyControl Service ........................................................................................................... 177
B.2.1 Service Description ........................................................................................................................................ 177
B.2.1.1 Overview .................................................................................................................................................. 177
B.2.1.2 Service Architecture ................................................................................................................................. 177
B.3 Service Operation ................................................................................................................................. 178
B.3.1 Introduction.................................................................................................................................................... 178
B.3.2 Npcf_SMPolicyControl_Create Service Operation ....................................................................................... 178
B.3.2.0 General ..................................................................................................................................................... 178
B.3.2.1 UE Location related information .............................................................................................................. 179
B.3.2.2 Access Type related information .............................................................................................................. 179
B.3.3 Npcf_SMPolicyControl_UpdateNotify Service Operation............................................................................ 179
B.3.3.0 General ..................................................................................................................................................... 179
B.3.3.1 Policy Update When UE suspends ........................................................................................................... 179
B.3.3.2 Request report of EPS Fallback................................................................................................................ 180
B.3.4 Npcf_SMPolicyControl_Update Service Operation ...................................................................................... 180
B.3.4.0 General ..................................................................................................................................................... 180
B.3.4.1 Number of Supported Packet Filters Report ............................................................................................ 181
B.3.4.2 Policy Update When UE suspends ........................................................................................................... 181
B.3.4.2.1 Policy Update Error Report ................................................................................................................ 181
B.3.4.2.2 UE State Change Report ..................................................................................................................... 181
B.3.4.3 UE Location related information .............................................................................................................. 181
B.3.4.4 Presence Reporting Area Information Report .......................................................................................... 182
B.3.4.5 Access Type related information .............................................................................................................. 182
B.3.4.6 Report of EPS Fallback ............................................................................................................................ 182
B.3.4.7 MA PDU Session ..................................................................................................................................... 183
B.3.5 Npcf_SMPolicyControl_Delete Service Operation ....................................................................................... 183
B.3.5.1 General ..................................................................................................................................................... 183
B.3.6 Provisioning and Enforcement of Policy Decisions ....................................................................................... 183
B.3.6.1 QoS mapping perfomed by the SMF+PGW-C ......................................................................................... 183
B.3.6.2 Provisioning of Presence Reporting Area Information ............................................................................ 183
B.3.6.3 Request and Report of Access Network information ............................................................................... 184
Annex C (normative): Wireless and wireline convergence access support ................................... 184
C.1 Scope .................................................................................................................................................... 184
C.2 Npcf_SMPolicyControl Service ........................................................................................................... 184
C.2.1 Service Description ........................................................................................................................................ 184
C.2.1.1 Overview .................................................................................................................................................. 184
C.2.1.2 Service Architecture ................................................................................................................................. 185
C.2.1.3 Network Functions ................................................................................................................................... 185
C.2.1.3.1 Policy Control Function (PCF) ........................................................................................................... 185
C.2.1.3.2 NF Service Consumers ....................................................................................................................... 185
C.2.1.4 Rules......................................................................................................................................................... 185
C.2.1.4.1 PCC Rules .......................................................................................................................................... 185
C.2.1.5 Policy control request trigger ................................................................................................................... 185
C.3 Service Operation ................................................................................................................................. 186
C.3.1 Introduction.................................................................................................................................................... 186
C.3.2 Npcf_SMPolicyControl_Create Service Operation ....................................................................................... 186
C.3.2.1 General ..................................................................................................................................................... 186
C.3.2.2 IPTV service support................................................................................................................................ 186
C.3.3 Npcf_SMPolicyControl_UpdateNotify Service Operation ............................................................................ 187
C.3.3.1 General ..................................................................................................................................................... 187
3GPP
Release 16 9 3GPP TS 29.512 V16.5.0 (2020-06)

C.3.4 Npcf_SMPolicyControl_Update Service Operation ...................................................................................... 187
C.3.4.1 General ..................................................................................................................................................... 187
C.3.5 Npcf_SMPolicyControl_Delete Service Operation ....................................................................................... 188
C.3.5.1 General ..................................................................................................................................................... 188
C.3.6 Provisioning and Enforcement of Policy Decisions ....................................................................................... 188
C.3.6.2 Hybrid Access support ............................................................................................................................. 189
C.3.6.2.1 General ............................................................................................................................................... 189
C.3.6.2.2 Hybrid Access with single PDU session............................................................................................. 189
C.3.6.2.3 Hybrid Access with MA PDU session connectivity over NG-RAN and wireline .............................. 189
C.3.6.2.4 Hybrid Access with MA PDU session connectivity over EPC/E-UTRAN and wireline using EPC
interworking scenarios........................................................................................................................ 189
Annex D(informative): Change history ............................................................................................. 191
3GPP
Release 16 10 3GPP TS 29.512 V16.5.0 (2020-06)
Foreword
This Technical Specification has been produced by the 3 rd 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.
3GPP
Release 16 11 3GPP TS 29.512 V16.5.0 (2020-06)
1 Scope
The present document provides the stage 3 specification of the Session Management Policy Control Service of 5G
system. The stage 2 definition and related procedures of the Session Management Policy Control Service are contained
in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [6]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
Stage 3 call flows are provided in 3GPP TS 29.513 [7].
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 [4] and 3GPP TS 29.501 [5].
The Policy Control Function with session related policies provides the Session Management Policy Control Service to
the NF consumers (i.e. Session Management Function).
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 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[7] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter
mapping; Stage 3".
[8] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[9] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[10] OpenAPI: "OpenAPI 3.0.0 Specification", https://github.com/OAI/OpenAPI-

Specification/blob/master/versions/3.0.0.md.
[11] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[12] 3GPP TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".
[13] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes".
[14] Void.
[15] 3GPP TS 29.519: "5G System; Usage of the Unified Data Repository service for Policy Control
Data, Application Data and Structured Data for Exposure; Stage 3".
[16] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2".
3GPP
Release 16 12 3GPP TS 29.512 V16.5.0 (2020-06)
[17] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[18] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point 5".
[19] 3GPP TS 32.291: "5G System; Charging service; Stage 3".
[20] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[21] 3GPP TS 23.380: "IMS Restoration Procedures".
[22] 3GPP TS 29.502: "5G System; Session Management Services; Stage 3".
[23] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
[24] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace
control and configuration management".
[25] 3GPP TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3".
[26] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[27] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[28] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[29] 3GPP TS 29.510: "Network Function Repository Services; Stage 3".
[30] 3GPP TS 32.290: "5G system; Services, operations and procedures of charging using Service
Based Interface (SBI)".
[31] IETF RFC 7807: "Problem Details for HTTP APIs".
[32] 3GPP TS 29.122: "T8 reference point for Northbound APIs".
[33] 3GPP TS 23.527: "5G System; Restoration Procedures".
[34] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
[35] 3GPP TS 32.255: "Charging management; 5G data connectivity domain charging; stage 2".
[36] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[37] 3GPP TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service
(GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[38] 3GPP TR 21.900: "Technical Specification Group working methods".
[39] 3GPP TS 29.521: "5G System; Binding Support Management Service; Stage 3".
[40] 3GPP TS 29.524: "Cause codes mapping between 5GC interfaces; Stage 3".
[41] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification".
[42] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[43] 3GPP TS 24.193: "Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3".
[44] 3GPP TS 24.519: "Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side
TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3".
[45] IEEE 802.1Q: "Virtual Bridged Local Area Networks".
3GPP
Release 16 13 3GPP TS 29.512 V16.5.0 (2020-06)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP
TR 21.905 [1].
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [2],
subclause 3.1 apply:
5G QoS Identifier
Access Traffic Steering
Access Traffic Switching
Access Traffic Splitting
MA PDU Session
PCC rule
PDU Session
Service Data Flow
Service Data Flow Filter
Service Data Flow Template
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP 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
3GPP TR 21.905 [1].
5G-RG 5G Residential Gateway

AF Application Function
AMF Access and Mobility Management Function
API Application Programming Interface
ATSSS Access Traffic Steering, Switching, Splitting
ATSSS-LL ATSSS Low-Layer
BBF Broadband Forum
BMIC Bridge Management Information Container
CHEM Coverage and Handoff Enhancements using Multimedia error robustness feature
CHF Charging Function
DN-AAA Data Network Authentication, Authorization and Accounting
DNN Data Network Name
DS-TT Device-side TSN translator
ePDG evolved Packet Data Gateway
FN-RG Fixed Network Residential Gateway
GFBR Guaranteed Flow Bit Rate
GUAMI Globally Unique AMF Identifier
HFC Hybrid Fiber Coax
HTTP Hypertext Transfer Protocol
MA Multi-Access
MPTCP Multi-Path TCP Protocol
NAS Non-Access-Stratum
NEF Network Exposure Function
NF Network Function
3GPP
Release 16 14 3GPP TS 29.512 V16.5.0 (2020-06)
NID Network Identifier

NRF Network Repository Function
NW-TT Network-side TSN translator
PCC Policy and Charging Control
PCF Policy Control Function
PMIC Port Management Information Container
PSAP Public Safety Answering Point
QoS Quality of Service
RTT Round-Trip Time
SDF Service Data Flow
SMF Session Management Function
SNPN Stand-alone Non-Public Network
S-NSSAI Single Network Slice Selection Assistance Information
TSC Time Sensitive Communication
TSCAI Time Sensitive Communication Assistance Information
TSN Time Sensitive Networking
TSN GM TSN Grand Master
UDM Unified Data Management
UDR Unified Data Repository
UE User Equipment
URLLC Ultra Reliable Low Latency Communication
W-5GAN Wireline 5G Access Network
W-5GBAN Wireline BBF Access Network
W-5GCAN Wireline 5G Cable Access Network
W-AGF Wireline Access Gateway Function
4 Npcf_SMPolicyControl Service
4.1 Service Description

4.1.1 Overview
The Session Management Policy Control Service performs provisioning, update and removal of session related policies
and PCC rules by the Policy Control Function (PCF) to the NF service consumer (i.e. SMF). The Session Management
Policy Control Service can be used for charging control, policy control, application detection and control and/or access
traffic steering, switching and splitting within a MA PDU Session. Session Management Policy Control Service applies
to the cases where the SMF interacts with the PCF in the non-roaming scenario, the V-SMF interacts with the V-PCF in
the local breakout roaming scenario and the H-SMF interacts with the H-PCF in the home-routed scenario.
4.1.2 Service Architecture

The Session Management Policy Control Service is provided by the PCF to the consumer and shown in the SBI
representation model in figure 4.1.2-1 and in the reference point representation model in figure 4.1.2-2. The overall
Policy and Charging Control related 5G architecture is depicted in 3GPP TS 29.513 [7].
The only known NF Service Consumer is the SMF.
3GPP
Release 16 15 3GPP TS 29.512 V16.5.0 (2020-06)
PCF
Npcf
Npcf_SMPolicyControl
SMF
Figure 4.1.2-1: Reference Architecture for the Npcf_SMPolicyControl Service; SBI representation
PCF SMF
N7
Figure 4.1.2-2: Reference Architecture for the Npcf_SMPolicyControl Service; reference point
representation
NOTE: The SMF represents the V-SMF and the PCF represents the V-PCF in the local breakout scenario. The
SMF represents the H-SMF and the PCF represents the H-PCF in the home routed scenario.
4.1.3 Network Functions
4.1.3.1 Policy Control Function (PCF)

The PCF is responsible for policy control decisions and flow based charging control functionalities. The PCF provides
the following:
- policies for application and service data flow detection, gating, QoS, flow based charging, traffic steering
control, usage monitoring control, access traffic steering, switching and steering within a MA PDU Session,
access network information report, TSN BMIC, TSN port management information container and TSN TSCAI
input container and RAN support information to the SMF.
The policy decisions made by the PCF may be based on one or more of the following:
- Information obtained from the AF, e.g. the session, media and subscriber related information;
- Information obtained from the UDR;
- Information obtained from the AMF, e.g. UE related and access related information;
- Information obtained from the SMF;
- Information obtained from the NWDAF;
- Information obtained from the NEF;
- information from CHF; and
- PCF pre-configured policy context.
3GPP
Release 16 16 3GPP TS 29.512 V16.5.0 (2020-06)
4.1.3.2 NF Service Consumers

The SMF is responsible for the enforcement of session management related policy decisions from the PCF, related to
service flow detection, QoS, charging, gating, traffic usage reporting, traffic steering and access traffic steering,
switching and splitting within a MA PDU Session.
The SMF shall support:
- sending the PDU session related attributes to the PCF;
- requesting and receiving the PCC rule(s) from the PCF;
- binding of service data flows to QoS flow as defined in 3GPP TS 29.513 [7];
- deriving rule(s) from the PCC rule(s) and then providing those rules to the user plane function or remove the
rule(s) from the user plane as defined in 3GPP TS 29.244 [13];
- deriving the QoS rules towards the UE;
- deriving the QoS profile towards the access network;
- deriving the ATSSS rules towards the UE if applicable;
- handling the policy control request trigger; and
- handling the PDU session related policy information.
NOTE: SMF functionality related to event exposure is defined in 3GPP TS 29.508 [12].
4.1.4 Rules
4.1.4.1 General
A rule is a set of policy information elements associated with a PDU session, or with service data flows (i.e., with a
PCC rule).
Two types of rules are defined:
- Session rule; and
- PCC rule.
Both Session rules and PCC rules are composed of embedded information elements as well as information elements that
are part of the referenced objects (e.g. condition data, or usage monitoring policy data type) by the rule.
PCC rule is defined in subclause 4.1.4.2. Session rule is defined in subclause 4.1.4.3.
4.1.4.2 PCC rules
4.1.4.2.1 PCC rules definition

A PCC rule is a set of information elements enabling the detection of a service data flow and providing parameters for
policy control and/or charging control. There are two different types of PCC rules as defined in 3GPP TS 23.503 [6]:
- Dynamic PCC rules. PCC rules that are dynamically provisioned by the PCF to the SMF. These PCC rules may
be either predefined or dynamically generated in the PCF. Dynamic PCC rules can be installed, modified and
removed at any time.
- Predefined PCC rules. PCC rules that are preconfigured in the SMF. Predefined PCC rules can be activated or
deactivated by the PCF at any time. Predefined PCC rules within the PCF may be grouped allowing the PCF to
dynamically activate a set of PCC rules.
3GPP
Release 16 17 3GPP TS 29.512 V16.5.0 (2020-06)
Additionally, predefined PCC rules may be grouped within the SMF as predefined PCC rule bases which allow the PCF
to dynamically activate these sets of rules. In this case, the PCC rule identifier is used to hold the predefined PCC rule
base identifier.
NOTE: The operator can define a predefined PCC rule, to be activated by the SMF. Such a predefined rule is not
explicitly known in the PCF.
A PCC rule consists of:
3GPP
Release 16 18 3GPP TS 29.512 V16.5.0 (2020-06)
Table 4.1.4.2.1-1: PCC rule information elements
Information name Description Category

Rule identifier Uniquely identifies the PCC rule, within a PDU Session. Mandatory
It is used between PCF and SMF for referencing PCC rules.
Service data flow detection
Precedence Determines the order, in which the service data flow templates are Mandatory
applied at service data flow detection, enforcement and charging.
Service Data Flow Template For IP PDU traffic: Either a list of service data flow filters or an Mandatory
application identifier that references the corresponding application
detection filter for the detection of the service data flow.
For Ethernet PDU traffic: Combination of traffic patterns of the
Ethernet PDU traffic.
Mute for notification Defines whether application's start or stop notification is to be Optional
muted.
Charging
Charging key The charging system (CHF) uses the charging key to determine Optional
the tariff to apply to the service data flow.
Service identifier The identity of the service or service component the service data Optional
flow in a rule relates to.
Sponsor Identifier An identifier, provided from the AF, which identifies the Sponsor, Optional
used for sponsored flows to correlate measurements from
different users for accounting purposes.
Application Service Provider An identifier, provided from the AF, which identifies the Application Optional
Identifier Service Provider, used for sponsored flows to correlate
measurements from different users for accounting purposes.
Charging method Indicates the required charging method for the PCC rule. Optional
Values: online or offline or none.
Service Data flow handling while Indicates whether the service data flow is allowed to start while Optional
requesting credit the SMF is waiting for the response to the credit request.
Only applicable for charging method online.
Measurement method Indicates whether the service data flow data volume, duration, Optional
combined volume/duration or event shall be measured.
This is applicable to reporting, if the charging method is online or
offline.
Note: Event based charging is only applicable to predefined PCC
rules and PCC rules used for application detection filter (i.e. with
an application identifier).
Application Function Record An identifier, provided from the AF, correlating the measurement Optional
Information for the Charging key/Service identifier values in this PCC rule with
application level reports.
Service identifier level reporting Indicates that separate usage reports shall be generated for this Optional
Service identifier.
Values: mandated or not required.
Policy control
5QI Identifier for the authorized QoS parameters for the service data Mandatory
flow.
ARP The Allocation and Retention Priority for the service data flow Mandatory
consisting of the priority level, the pre-emption capability and the
pre-emption vulnerability.
Gate status The gate status indicates whether the service data flow, detected Optional
by the service data flow template, may pass (Gate is open) or
shall be discarded (Gate is closed).
QoS Notification Control (QNC) Indicates whether notifications are requested from 3GPP NG-RAN Optional
when the GFBR can no longer (or again) be guaranteed for a QoS
Flow during the lifetime of the QoS Flow.
Reflective QoS Control Indicates to apply reflective QoS for the SDF. Optional
MBR (UL/DL) The uplink/downlink maximum bitrate authorized for the service Optional
data flow.
GBR (UL/DL) The uplink/downlink guaranteed bitrate authorized for the service Optional
data flow.
UL sharing indication Indicates resource sharing in uplink direction with service data Optional
flows having the same value in their PCC rule.
DL sharing indication Indicates resource sharing in downlink direction with service data Optional
flows having the same value in their PCC rule.
Redirect Redirect state of the service data flow (enabled/disabled). Optional
3GPP
Release 16 19 3GPP TS 29.512 V16.5.0 (2020-06)
Redirect Destination Controlled Address to which the service data flow is redirected Optional
when redirect is enabled.
Bind to default QoS Flow Indicates that the dynamic PCC rule shall always have its binding Optional
with the default QoS Flow.
Priority Level Indicates a priority in scheduling resources among QoS Flows. Optional
Averaging Window Represents the duration over which the guaranteed and maximum Optional
bitrate shall be calculated.
Maximum Data Burst Volume Denotes the largest amount of data that is required to be Optional
transferred within a period of 5G-AN PDB.
Access Network Information Reporting
User Location Required The serving cell of the UE is to be reported. When the Optional
corresponding QoS flow is deactivated, and if available,
information on when the UE was last known to be in that location
is also to be reported.
UE Timezone Required The time zone of the UE is to be reported. Optional
Usage Monitoring Control
Monitoring key The PCF uses the monitoring key to group services that share a Optional
common allowed usage.
Indication of exclusion from Indicates that the service data flow shall be excluded from PDU Optional
session level monitoring Session usage monitoring.
N6-LAN Traffic Steering Enforcement Control
Traffic steering policy identifier(s) Reference to a pre-configured traffic steering policy at the SMF. Optional
AF influenced Traffic Steering Enforcement Control
Data Network Access Identifier Identifier of the target Data Network Access. Optional
Per DNAI: Traffic steering policy Reference to a pre-configured traffic steering policy at the SMF. Optional
identifier
Per DNAI: N6 traffic routing Describes the information necessary for traffic steering to the Optional
information DNAI.
Information on AF subscription to Indicates whether a notification in case of UP path change is Optional
UP path changes events requested, as well as the destination(s) for where to provide the
notification.
Indication of traffic correlation Indicates that the target PDU Sessions should be correlated via a Optional
common DNAI in the user plane.
RAN support information
UL Maximum Packet Loss Rate The maximum rate for lost packets that can be tolerated in the Optional
uplink direction for the service data flow.
DL Maximum Packet Loss Rate The maximum rate for lost packets that can be tolerated in the Optional
downlink direction for the service data flow.
MA PDU Session Control
Application descriptors Identifies the application traffic to apply the Steering functionality Optional
and the Steering mode.
Steering Functionality Indicates the applicable traffic steering functionality. Optional
Steering mode (UL/DL) Indicates the UL and/or DL traffic distribution rules between the Optional
3GPP and Non-3GPP accesses together with associated
parameters (when applicable) for the traffic matching the service
data flow.
Charging for Non-3GPP access Indicates parameters used for charging packets carried via Non- Optional
3GPP access for a MA PDU Session. The same set of parameters
as for the Charging information above applies. If a parameter is
not included here, the value provided in the Charging information
above applies.
Usage Monitoring for Non-3GPP Indicates parameters used to monitor usage of the packets carried Optional
access via Non-3GPP access for a MA PDU Session. The same set of
parameters as for the Usage Monitoring information above
applies. If a parameter is not included here, the value provided in
the Usage Monitoring information above applies.
IPTV (NOTE 1)
IP Multicast traffic control Indicates whether the service data flow, corresponding to the Optional
information service data flow template, is allowed or not allowed.
QoS Monitoring for URLLC
QoS parameter(s) to be UL packet delay, DL packet delay or round trip packet delay. Optional
measured
Reporting frequency Defines the frequency for the reporting, such as event triggered, Optional
periodic, or when the PDU Session is released.
Target of reporting Defines the target of the QoS Monitoring reports, it can be either Optional
the PCF or the AF, decided by the PCF.
Alternative QoS Parameter Sets (NOTE 2)
3GPP
Release 16 20 3GPP TS 29.512 V16.5.0 (2020-06)
5QI The 5QI in this Alternative QoS Parameter Set. Optional

MBR (UL/DL) The uplink/downlink maximum bitrate authorized for the service Optional
data flow in this Alternative QoS Parameter Set.
GBR (UL/DL) The uplink/downlink guaranteed bitrate authorized for the service Optional
data flow in this Alternative QoS Parameter Set.
TSN TSCAI Input container
Burst Arrival Time Indicates the burst arrival time in reference to TSN GM and Optional
ingress port.
Periodicity The time period (in reference to TSN GM) between start of two Optional
bursts.
Flow Direction Direction of the flow. Optional
NOTE 1: Only applicable to the 5G-RG connecting to the 5GC via NG-RAN as defined in Annex C.
NOTE 2: Only applicable for GBR service data flow with QoS Notification Control enabled.
The above information is organized into a set of decision data objects as defined in subclause 4.1.4.4. The exact
encoding of PCC rules is defined in subclause 5.6.2.6.
4.1.4.2.2 PCC rules operation

For dynamic PCC rules, the following applies:
- Installation: to provision the PCC rules.
- Modification: to modify the PCC rules.
- Removal: to remove the PCC rules.
For predefined PCC rules, the following operations are available:
- Activation: to activate the PCC rules.
- Deactivation: to deactivate the PCC rules.
4.1.4.3 Session rule
4.1.4.3.1 Session rules definition

A session rule consists of policy information elements associated with PDU session. The encoding of the SessionRule
data type is defined in subclause 5.6.2.7.
A session rule may include:
- Session Rule ID;
- Authorized Session AMBR;
- Authorized Default QoS;
- Reference to Usage Monitoring Data;
- Reference to Usage Monitoring Data for Non-3GPP access of MA PDU session; and
- Reference to Condition Data.
4.1.4.3.2 Session rules operation

For Session rules, the following applies:
- Installation: to provision the session rules.
- Modification: to modify the session rules.
- Removal: to remove the session rules.
3GPP
Release 16 21 3GPP TS 29.512 V16.5.0 (2020-06)
4.1.4.4 Policy Decision types
4.1.4.4.1 General
A policy decision is a grouping of cohesive information elements describing a specific type of decision, e.g. QoS,
Charging data, etc. A policy decision can be linked to one or more PCC rules or one or more Session rules. A PCC rule
or session rule can at most refer to one instance of the policy decision for each type.
The following types of policy decision are defined:
- Traffic control data;
- QoS data;
- Charging data;
- Usage Monitoring data; and
- QoS Monitoring data.
4.1.4.4.2 Traffic control data definition

Traffic control data defines how traffic data flows associated with a rule are treated (e.g. blocked, redirected). The
traffic control data encoding table is defined in subclause 5.6.2.10.
Traffic control data shall include:
- Traffic Control Data ID.
Traffic control data may include:
- Flow status;
- Redirect Information;
- Mute Notification;
- Traffic Steering Policy ID UL;
- Traffic Steering Policy ID DL;
- Routing requirements;
- UP path change event subscription from the AF;
- Indication of traffic correlation;
- Access Traffic Steering Functionality;
- Access Traffic Steering Mode DL;
- Access Traffic Steering Mode UL; and
- Multicast Access Control.
4.1.4.4.3 QoS data definition

QoS data defines QoS parameters (e.g. bitrates) associated with a rule. The QoS data encoding table is defined in
subclause 5.6.2.8.
QoS data shall include:
- QoS Data ID;
QoS data may include:
3GPP
Release 16 22 3GPP TS 29.512 V16.5.0 (2020-06)
- 5QI;
- ARP;
- QNC;
- Maximum Packet Loss Rate UL;
- Maximum Packet Loss Rate DL;
- Maximum Bit Rate UL;
- Maximum Bit Rate DL;
- Guaranteed Bit Rate UL;
- Guaranteed Bit Rate DL;
- 5QI Priority Level;
- Averaging window;
- Maximum Data Burst Volume;
- Bound to default QoS flow indication;
- Resource Sharing Key UL;
- Resource Sharing Key DL; and
- Reflective QoS attribute.
NOTE: Either 5QI and ARP combination or Bound to default QoS flow indication is provided.
4.1.4.4.4 Charging data definition

Charging data defines charging related parameters (e.g. rating group) associated with a rule. The charging data encoding
table is defined in subclause 5.6.2.11.
Charging data shall include:
- Charging Data ID;
- Rating Group.
Charging data may include:
- Metering Method;
- Charging Method;
- Service Data flow handling while requesting credit;
- Reporting Level;
- Service ID;
- Sponsor ID;
- Application Service Provider ID; and
- AF Charging ID.
4.1.4.4.5 UsageMonitoring data definition

UsageMonitoring data defines usage monitoring information associated with a rule. The UsageMonitoring data
encoding table is defined in subclause 5.6.2.12.
3GPP
Release 16 23 3GPP TS 29.512 V16.5.0 (2020-06)
Usage Monitoring Data shall include:
- Usage Monitoring ID.
Usage Monitoring Data may include:
- Volume Threshold;
- Volume Threshold UL;
- Volume Threshold DL;
- Time Threshold;
- Monitoring Time;
- Next Volume Threshold;
- Next Volume Threshold UL;
- Next Volume Threshold DL;
- Next Time Threshold;
- Inactivity Time; and
- PCC rule identifier(s) corresponding to the service data flow(s) which needs to be excluded from PDU session
level usage monitoring.
4.1.4.4.6 QoS Monitoring data definition

QoS Monitoring data defines QoS Monitoring related parameters (e.g. request QoS monitoring parameter to be
measured) associated with a rule. The QoS Monitoring data encoding table is defined in subclause 5.6.2.40.
QoS Monitoring data shall include:
- QoS Monitoring Data ID;
- requested QoS monitoring parameters to be measured;
- reporting frequency.
QoS monitoring data may include:
- reporting thresholds;
- wait time;
- reporting period; and/or
- target of reporting.
4.1.5 Policy control request trigger

Policy control request trigger is a condition when the SMF shall interact again with PCF for further policy decision of a
PDU session.
The policy control request trigger is designed as an Enumeration type defined in the subclause 5.6.3.6.
The PCF can provide an array of policy control request triggers in policy decision to subscribe the triggers in SMF.
When SMF interacts with PCF due to the triggering of the policy control request triggers, the SMF shall send the related
attributes that have changed together with the corresponding triggers.
3GPP
Release 16 24 3GPP TS 29.512 V16.5.0 (2020-06)
4.1.6 Requested rule data

Requested rule data consists of requested information by the PCF associated with one or more PCC rules.
The requested rule data is designed as a subresource of the policy decision within an attribute called "lastReqRuleData".
The PCF only records the last requested rule data.
When requesting rule data, the PCF shall include the types of data requested for the rules within the "reqData" array of
the "lastReqRuleData" and shall also provide the corresponding policy control request triggers if the triggers are not yet
set.
The encoding of the requested rule data is further specified in subclause 5.6.2.24.
When the SMF receives the requested rule data, the SMF shall report the corresponding information to the PCF for the
associated PCC rule(s).
4.1.7 Requested usage data

Requested Usage data consists of requested usage reports by the PCF for one or more instances of Usage Monitoring
data decision.
The requested usage data is designed as a sub resource of the policy decision within an attribute called
"lastReqUsageCtlData". The PCF only records the last requested usage data.
The encoding of the requested usage data is further specified in subclause 5.6.2.25.
When the SMF receives the requested usage data, the SMF shall report the corresponding accumulated usage to the PCF
for the corresponding Usage Monitoring data decision(s). The requested usage data shall not be valid for the Usage
Monitoring data decision(s) after the reporting.
4.1.8 Condition data

Condition data defines the condition(s) where the PCC rules or session rules are applicable and/or not applicable. The
condition data encoding is defined in subclause 5.6.2.9.
Condition data shall include:
- Condition Data ID.
Condition data may include:
- Activation Time;
- Deactivation Time;
- Access Type; and
- RAT Type
NOTE: Access type and RAT type are only applicable to the session rule.
4.2 Service Operations

4.2.1 Introduction
The service operations defined for Npcf_SMPolicyControl are shown in table 4.2.1-1.
3GPP
Release 16 25 3GPP TS 29.512 V16.5.0 (2020-06)
Table 4.2.1-1: Npcf_SMPolicyControl Operations
Service Operation Name Description Initiated by

Npcf_SMPolicyControl_Create Request to create an SM Policy Association with NF consumer (SMF)
the PCF to receive the policy for a PDU session.
Npcf_SMPolicyControl_Update Request to update the SM Policy association with NF consumer (SMF)
the PCF to receive the updated policy when Policy
Control Request Trigger condition is met.
Npcf_SMPolicyControl_UpdateNotify Update and/or delete the PCC rule(s) PDU session PCF
related policy context at the SMF and Policy
Control Request Trigger information.
Npcf_SMPolicyControl_Delete Request to delete the SM Policy Association and NF consumer (SMF)
the associated resources.
4.2.2 Npcf_SMPolicyControl_Create Service Operation
4.2.2.1 General
The Npcf_SMPolicyControl_Create service operation provides means for the SMF to request the creation of a
corresponding SM Policy Association with PCF.
The Session Management procedures of the SMF and related to policies are defined in 3GPP TS 23.501 [2],
3GPP TS 23.502 [3] and 3GPP TS 23.503 [6].
The following procedures using the Npcf_SMPolicyControl_Create service operation are supported:
- Request of creation of a corresponding SM Policy Association with PCF.
- Provisioning of PCC rules.
- Provisioning of policy control request triggers.
- Provisioning of charging related information for PDU session.
- Provisioning of revalidation time.
- Policy provisioning and enforcement of authorized AMBR per PDU session.
- Policy provisioning and enforcement of authorized default QoS.
- Provisioning of PCC rule for Application Detection and Control.
- 3GPP PS Data Off Support.
- IMS Emergency Session Support.
- Request Usage Monitoring Control.
- Access Network Charging Identifier report.
- Request for the successful resource allocation notification.
- Provisioning of IP Index Information.
- Negotiation of the QoS flow for IMS signalling.
- PCF resource cleanup.
- Access traffic steering, switching and splitting support.
- DNN Selection Mode Support.
- Detection of TSN related SM Policy Association.
3GPP
Release 16 26 3GPP TS 29.512 V16.5.0 (2020-06)
When the EMDBV feature defined in subclause 5.8 is supported by both the PCF and the SMF, the PCF shall use the
extMaxDataBurstVol attribute instead of the maxDataBurstVol attribute to signal maximum data burst volume values
higher than 4095 Bytes.
When the EMDBV feature is supported by the PCF but not supported by SMF and the PCF needs to signal maximum
data burst volume values higher than 4095 Bytes, the PCF shall use the maxDataBurstVol attribute set to 4095 Bytes.
For values lower than or equal to 4095 Bytes, the PCF shall use the maxDataBurstVol attribute.
NOTE: Maximum data burst volume values are sent by the PCF in responses to the SMF or in an SM Policy
Association Update request i.e. after feature negotiation, so the PCF knows whether the SMF supports the
EMDBV feature.
4.2.2.2 SM Policy Association establishment
SMF PCF
1. POST .../sm-policies
2. 201 Created
Figure 4.2.2.2-1: SM Policy Association establishment
When the SMF receives the Nsmf_PDUSession_CreateSMContext Request as defined in subclause 5.2.2.2 of
3GPP TS 29.502 [22], if the SMF was requested not to interact with the PCF, the SMF shall not interact with the PCF;
otherwise, the SMF shall send the POST method as step 1of the figure 4.2.2.2-1 to request to create an "Individual SM
Policy".
NOTE 1: The decision to not interact with PCF applies for the life time of the PDU session.
NOTE 2: The indicator to not interact with PCF is configured in the UDM. It is delivered by the UDM to the SMF
within the Charging Characteristics using the Session Management Subscription Data Retrieval service
operation as described in 3GPP TS 29.503 [34]. The indicator is operator specific, therefore it can only be
used in non-roaming and home routed roaming cases.
The SMF shall include SmPolicyContextData data structure in the payload body of the HTTP POST to request a
creation of representation of the "Individual SM Policy" resource. The "Individual SM Policy" resource is created as
described below.
The SMF shall include (if available) in SmPolicyContextData data structure:
- SUPI of the user within the "supi" attribute;
- PDU Session Id within the "pduSessionId" attribute;
- DNN within the "dnn" attribute;
- DNN selection mode within the "dnnSelMode" attribute if the "DNNSelectionMode" feature is supported;
- URL identifying the recipient of SM policies update notification within the "notificationUri" attribute;
- PDU Session Type within the "pduSessionType" attribute;
- PEI within the "pei" attribute;
- Internal Group Id(s) within the "interGrpIds" attribute;
- type of access within the "accessType" attribute;
- type of the radio access technology within the "ratType" attribute;
3GPP
Release 16 27 3GPP TS 29.512 V16.5.0 (2020-06)
- the combination of additional access type and RAT type within the "addAccessInfo" attribute if the ATSSS
feature is supported;
- the UE Ipv4 address within the "ipv4Address" attribute and/or the UE Ipv6 prefix within the
"ipv6AddressPrefix" attribute;
- the UE time zone information within "ueTimeZone" attribute;
- the UDM subscribed Session-AMBR or, if the "DN-Authorization" feature is supported, the DN-AAA
authorized Session-AMBR within "subsSessAmbr" attribute;
NOTE 3: When both, the UDM subscribed Session-AMBR and the DN-AAA authorized Session-AMBR are
available in the SMF, the SMF includes the DN-AAA authorized Session-AMBR.
- if the "DN-Authorization" feature is supported, the DN-AAA authorization profile index within the
"authProfIndex" attribute;
- subscribed Default QoS Information within "subsDefQos" attribute;
- the number of supported packet filters for signalled QoS rules within the "numOfPackFilter";
- the online charging status within "online" attribute;
- the offline charging status within "offline" attribute;
- the charging characteristics within "chargingCharacteristics" attribute;
- access network charging identifier within the "accNetChId" attribute;
- the address of the network entity performing charging within the "chargEntityAddr" attribute;
- 3GPP PS data off status within the "3gppPsDataOffStatus" attribute;
- indication of UE supporting reflective QoS within the "refQosIndication" attribute;
- user location information within the "userLocationInfo" attribute;
- the S-NSSAI corresponding to the network slice the PDU session is allocated within the "sliceInfo" attribute;
- the QoS flow usage required of the default QoS flow within the "qosFlowUsage" attribute;
- the MA PDU session indication within the "maPduInd" attribute if the "ATSSS" feature is supported;
- the ATSSS capability within the "atsssCapab" attribute if the "ATSSS" feature is supported;
- identifier of the serving network, for SNPN also including the NID, within the "servingNetwork" attribute;
- one or more framed routes within the "ipv4FrameRouteList" attribute for IPv4 and/or one or more framed routes
within the "ipv6FrameRouteList" attribute.
NOTE 4: When both, the UDM subscribed framed routes and the DN-AAA authorized framed routes are available
in the SMF, the SMF includes the DN-AAA authorized framed routes. If the UDM or DN-AAA updates
the framed routes during the lifetime of the PDU Session, the SMF releases the PDU Session as defined
in subclause 4.2.2.3.
- serving network function identifier within the "servNfId" attribute; and
- trace control and configuration parameters information encoded as "traceReq" attribute.
The SMF may include in "SmPolicyContextData" data structure the IPv4 address domain identity within the
"ipDomain" attribute.
3GPP
Release 16 28 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE 4: The "ipDomain" attribute is helpful when within a network slice instance, there are several separate IP
address domains, with SMF/UPF(s) that allocate Ipv4 IP addresses out of the same private address range
to UE PDU Sessions. The same IP address can thus be allocated to UE PDU sessions served by
SMF/UPFs in different IPv4 address domains. If one PCF controls several SMF/UPFs in different IP
address domains, the UE IP address is thus not sufficient for the AF session binding procedure, as
described in 3GPP TS 29.514 [17]. The SMF assists the PCF in the session binding supplying an
"ipDomain" attribute denoting the IPv4 address domain identity of the allocated UE IPv4 address.
When the PCF receives the HTTP POST request from the SMF, the PCF shall make an authorization based on the
information received from the SMF and, if available, AMF, CHF, AF, UDR, NWDAF and operator policy pre-
configured at the PCF. If the authorization is successful, the PCF shall create a new resource, which represents
"Individual SM Policy", addressed by a URI as defined in subclause 5.3.3.2 and contains a PCF created resource
identifier. The PCF shall respond to the SMF with a 201 Created message, including:
- Location header field containing the URI for the created resource; and
- a response body providing session management related policies, e.g. provisioning of PCC rules as defined in
subclause 4.2.6.2, provisioning of policy control request triggers as defined in subclause 4.2.6.4.
The SMF shall use the URI received in the Location header in subsequent requests to the PCF to refer to the "Individual
SM Policy".
It the PCF received a "traceReq" attribute, it shall perform trace procedures as defined in 3GPP TS 32.422 [24].
If errors occur when processing the HTTP POST request, the PCF shall apply error handling procedures as specified in
subclause 5.7.
If the user information received within the "supi" attribute is unknown, the PCF shall reject the request and include in
an HTTP "400 Bad Request" response message the "cause" attribute of the ProblemDetails data structure set to
"USER_UNKNOWN".
If the PCF is, due to incomplete, erroneous or missing information (e.g. QoS, RAT type, subscriber information) not
able to provision a policy decision as response to the request for PCC rules by the SMF, the PCF may reject the request
and include in an HTTP "400 Bad Request" response message the "cause" attribute of the ProblemDetails data structure
set to "ERROR_INITIAL_PARAMETERS".
If the PCF, based on local configuration and/or operator policies, denies the creation of the Individual SM Policy
resource, the PCF may reject the request and include in an HTTP "403 Forbidden" response message the "cause"
attribute of the ProblemDetails data structure set to "POLICY_CONTEXT_DENIED". Based on configured failure
action, the SMF at reception of this error code may reject the PDU session establishment or allow the PDU session
establishment applying local policies.
If the SMF receives HTTP response with these codes, the SMF shall reject the PDU session establishment that initiated
the HTTP POST Request.
If the "SamePcf" feature as defined in subclause 5.8 is supported, when the PCF determines that the same PCF shall be
selected for the SM Policy associations to the same UE ID, S-NSSAI and DNN combination in the non-roaming or
home-routed scenario, the PCF shall request the BSF to check if there is an existing PCF binding information for the
same UE ID, S-NSSAI and DNN combination as defined in subclause 4.2.2.2 of 3GPP TS 29.521 [39]. If the PCF
receives the "403 Forbidden" status code with the "cause" attribute of the ProblemDetails data structure set to
"EXISTING_BINDING_INFO_FOUND" and the FQDN or the description of IP endpoints hosting
Npcf_SMPolicyControl service of the existing PCF binding information from the BSF within the "pcfSmFqdn" attribute
or "pcfSmIpEndPoints" attribute of BindingResp data structure respectively as defined in subclause 4.2.2.2 of 3GPP
TS 29.251 [39], the PCF shall reply with an HTTP "308 Permanent Redirect" error response and the Location header
containing the URI with the FQDN or IP endpoint as {apiRoot} defined in subclause 5.3.2.2 to the SMF. Upon
reception of the response, the SMF shall initiate a new HTTP POST request to the returned URI.
The forwarding of the Origination Time Stamp parameter shall apply as described hereafter, if the SMF supports the
detection and handling of late arriving requests as specified in subclause 5.2.3.3 of 3GPP TS 29.502 [22] and the
procedure is enabled by the operator. If the SMF receives a request to create an SM Context or a PDU session context,
which includes the 3gpp-Sbi-Origination-Timestamp header as defined in subclause 5.2.3.2, the SMF shall forward this
header to the PCF as HTTP custom header. See also subclause 4.2.7 for the handling at the PCF, when the PCF receives
the 3gpp-Sbi-Origination-Timestamp header.
3GPP
Release 16 29 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.2.3 Provisioning of charging related information for PDU session
4.2.2.3.1 Provisioning of Charging Addresses

The PCF may provide the CHF address(es), CHF instance ID(s) and CHF set ID(s) as charging information to the SMF
during the initial interaction with the SMF defining the charging function respectively based on the operator policy. In
this case, the PCF may retrieve the CHF address(es) as follows and possible associated CHF instance ID(s) and CHF set
ID(s):
- receives it from the UDR as part of the Policy Data Subscription information as defined in subclause 5.2.10 of
3GPP TS 29.519 [15].
- locally configured in the PCF based on operator policies.
- discovers using NRF as described in subclause 6.1 of 3GPP TS 32.290 [30].
In order to provision the CHF information to the SMF, the PCF shall include the "chargingInfo" attribute containing the
charging information within the SmPolicyDecision data structure. Within the ChargingInformation data structure, both
primary CHF address within a "primaryChfAddress" attribute and secondary CHF address within a
"secondaryChfAddress" attribute shall be provided simultaneously. Primary and secondary CHF addresses may be
complemented by associated CHF instance ID(s) within the "primaryChfInstanceId" and "secondaryChfInstanceId"
attribute. Primary and secondary CHF addresses may be complemented by associated CHF set ID(s) within the
"primaryChfSetId" and "secondaryChfSetId". These shall overwrite any predefined addresses and associated CHF
instance ID(s) and CHF set ID(s) at the SMF. Provisioning charging information without PCC rules for charged service
data flows shall not be considered as an error since such PCC rules may be provided later. If the PCF has provided the
CHF address, it shall not modify the charging information in subsequent interactions.
If no charging information is provisioned by the PCF, the SMF shall use the charging information obtained via one of
the following procedures with this precedence (highest to lowest) order (see 3GPP TS 32.255 [35], subclause 5.1.8):
1. UDM provided charging characteristics.
2. NRF based discovery.
3. SMF locally configured charging characteristics.
4.2.2.3.2 Provisioning of Default Charging Method

The default charging method indicates what charging method shall be used for every PCC rule where the charging
method is omitted within the PCC rule. The SMF may have a pre-configured default charging method.
Upon the initial interaction with the PCF, the SMF shall provide the pre-configured default charging method, if
available, within the "offline" attribute and/or "online" attribute embedded directly within the SmPolicyContextData
data structure of HTTP POST message to the PCF.
The PCF may provide the default charging method which applies to the PDU session. In order to do so, if offline
charging applies, the PCF shall include the "offline" attribute set to "true" within the SmPolicyDecision data structure,
or if online charging applies, the PCF shall include the "online" attribute set to "true" within the SmPolicyDecision data
structure in the response of HTTP POST message. The default charging method provided by the PCF shall overwrite
any predefined default charging method at the SMF. If the PCF has provided the default charging method, it shall not
modify the default charging method in subsequent interactions.
NOTE: It is possible that there is no default charging method applied to a PDU session.
4.2.2.4 Provisioning of revalidation time

The PCF may within the SmPolicyDecision data structure provide the revalidation time within the "revalidationTime"
attribute and the RE_TIMEOUT policy control request trigger within the "policyCtrlReqTriggers" attribute to instruct
the SMF to trigger a PCF interaction to request PCC rule from the PCF.
The SMF shall start the timer based on the revalidation time and shall send the PCC rule request before the indicated
revalidation time.
3GPP
Release 16 30 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.2.5 Policy provisioning and enforcement of authorized AMBR per PDU session
The SMF may include either the UDM subscribed AMBR or, if the "DN-Authorization" feature is supported, the DN-
AAA authorized AMBR per PDU session with the "subsSessAmbr" attribute within the SmPolicyContextData data
structure as defined in subclause 4.2.2.2. When both, the UDM subscribed Session-AMBR and the DN-AAA authorized
Session-AMBR are available in the SMF, the DN-AAA authorized Session-AMBR shall take precedence over the
UDM subscribed Session-AMBR.
The PCF shall authorize the session AMBR based on the operator's policy and provision the authorized session AMBR
to the SMF in the response of the message as defined in subclauses 4.2.6.3.1 and 4.2.6.3.2.
Upon receiving the authorized session AMBR from the PCF, the SMF shall apply the corresponding procedures
towards the access network, the UE and the UPF for the enforcement of the AMBR per PDU session.
4.2.2.6 Policy provisioning and enforcement of authorized default QoS

During the PDU session establishment as defined in subclause 4.2.2.2, the SMF may include the subscribed default QoS
with the "subsDefQos" attribute. The PCF shall provision the authorized default QoS to the SMF in the response of the
message as defined in subclauses 4.2.6.3.1 and 4.2.6.3.2.
Upon receiving the authorized default QoS, the SMF enforces it which may lead to the change of the subscribed default
QoS. The SMF shall apply the corresponding procedures towards the access network, the UE and the UPF for the
enforcement of the authorized default QoS.
NOTE 1: If dynamic PCC is not deployed, the SMF can have a DNN based configuration to enable the
establishment of a GBR resource type default QoS flow. This configuration contains a standardized GBR
5QI as well as GFBR and MFBR for UL and DL.
NOTE 2: GBR resource type is not applicable to the default QoS flow of the PDU session which is interworking
with EPS.
4.2.2.7 Provisioning of PCC rule for Application Detection and Control

If the ADC feature is supported, and the user subscription indicates that the application detection and control is
required, the PCF may provision PCC rule for application detection and control as defined in subclause 4.2.6.2.11 in the
response message.
If the SMF receives the PCC rule for application detection and control, the SMF shall instruct the UPF as defined in
3GPP TS 29.244 [13] to detect the application traffic.
4.2.2.8 3GPP PS Data Off Support

When the 3GPP-PS-Data-Off feature as defined in subclause 5.8 is supported, and if the SMF is informed that the 3GPP
PS Data Off status of the UE is set to active during the establishment of a PDU session over 3GPP access and/or non-
3GPP access, it shall include the "3gppPsDataOffStatus" attribute set to true within the SmPolicyContextData data
structure in the HTTP POST message as defined in subclause 4.2.2.2.
If the PCF receives that HTTP POST message with a "3gppPsDataOffStatus" set to true as above and the access type of
the PDU session indicated as "3GPP_ACCESS", the PCF shall configure the SMF to block any downlink and
optionally uplink IP flows not relating to a service within the list of 3GPP PS Data Off Exempt Services, for instance by
not installing any related dynamic PCC rule(s) or by not activating related predefined PCC rule(s) such as PCC rule(s)
with wild-carded service data flow filters. The PCF may also, subject to its normal policies, provide the PCC rule for
service(s) from the list of 3GPP PS Data Off Exempt Service as defined in subclause 4.2.6.2.1.
The PCF shall subscribe to "AC_TY_CH" policy control request trigger with the SMF as defined in subclause 4.2.6.4 to
support this feature if the PCF determines the UE is allowed to access the non-3GPP access.
NOTE 1: The PCF can be configured with a list of 3GPP PS Data Off Exempt Services per DNN and S-NSSAI.
The list of 3GPP PS Data Off Exempt Services for an DNN and S-NSSAI can also be empty, or can allow
for any service within that DNN and S-NSSAI, according to operator policy.
3GPP
Release 16 31 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE 2: For the PDU session used for IMS services, the 3GPP Data Off Exempt Services are enforced in the IMS
domain as specified 3GPP TS 23.228 [16]. Policies configured in the PCF need to ensure that IMS
services are allowed when the 3GPP Data Off status of the UE is set to activated, e.g. by treating any
service within a well-known IMS DNN as 3GPP PS Data Off Exempt Services.
NOTE 2: The packets transferred over the non-3GPP access are unaffected by the 3GPP PS Data Off functionality.
If the "ATSSS" feature as defined in subclause 5.8 is supported, and the PCF receives in the SmPolicyContextData data
structure the "maPduInd" attribute, the "3gppPsDataOffStatus" attribute set to true and "accessType" attribute or the
"addAccInfo" attribute is set to "3GPP_ACCESS", the PCF shall configure the SMF in such a way that:
- packets for services belonging to the 3GPP PS Data Off Exempt services are forwarded over 3GPP access and
non-3GPP access as indicated by the policy for ATSSS Control, as as specified in subclause 4.2.6.2.17.
- for downlink and optionally uplink flows not related to a service within the list of 3GPP PS Data Off Exempt
services, the PCF may configure the SMF to handle the traffic only in the non-3GPP access, if available, by
providing the corresponding ATSSS policy within the PCC rule as specified in subclause 4.2.6.2.17.
4.2.2.9 IMS Emergency Session Support

A SMF that requests PCC Rules at PDU Session Establishment shall send an HTTP POST message as defined in
subclause 4.2.2.2 and the "dnn" attribute including the Emergency DNN. The SMF may include the SUPI within the
"supi" attribute and if the SUPI is not available, the SMF shall include the PEI within the "pei". The SMF may include
the rest of the attributes described in subclause 4.2.2.2. The SMF may also include the GPSI if available within the
"gpsi" attribute.
The PCF shall detect that a PDU session is restricted to IMS Emergency services when the HTTP POST message is
received and the "dnn" attribute includes a data network identifier that matches one of the Emergency DNs from the
configurable list. The PCF:
- shall provision PCC Rules restricting the access to Emergency Services (e.g. P-CSCF(s), DHCP(s) and DNS (s)
and SUPL(s) addresses) as required by local operator policies in a response message according to the procedures
described in subclause 4.2.6.
- may provision the authorized QoS that applies to the default QoS flow within the "authDefQos" attribute of a
session rule according to the procedures described in subclause 4.2.3.6 except for obtaining the authorized QoS
upon interaction with the UDR. The value for the "priorityLevel" attribute shall be assigned as required by local
operator policies (e.g. if an IMS Emergency session is prioritized the "priorityLevel" attribute may contain a
value that is reserved for an operator domain use of IMS Emergency sessions). If the "accessType" attribute is
assigned to "3GPP_ACCESS" the values for "preemptCap" attribute and the "preemptVuln" attribute shall be
assigned as required by local operator policies.
- may provision the authorized session AMBR in the response message according to the procedures described in
subclause 4.2.3.5.
When the SMF detects that the provisioning of PCC Rules failed, the PCC rule error handling procedure shall be
performed.
4.2.2.10 Request Usage Monitoring Control

If the UMC as defined in subclause 5.8 is support, the PCF may provision the usage monitoring control policy to the
SMF as defined in subclause 4.2.6.5.3.
4.2.2.11 Access Network Charging Identifier report

During the PDU session establishment, the SMF may provide the access network charging identifier information within
the "accNetChId" attribute. Within the AccNetChId data structure, the SMF shall include the "accNetChaIdValue"
containing the Access Network Charging Identifier for the default QoS flow and the "sessionChScope" attribute set to
true if the Access Network Charging Identifier is applied to the whole PDU session. The SMF may provide the address
of the network entity performing charging within the "chargEntityAddr" attribute.
3GPP
Release 16 32 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE: During the PDU Session Establishment no "refPccRuleIds" attribute is provided regardless if the charging
identifier applies to the entire PDU session or to the default QoS flow since the PCC Rules are not yet
authorized at this stage.
4.2.2.12 Request for the successful resource allocation notification

The PCF may request the SMF to confirm that the resources associated to a PCC rule are successfully allocated as
defined in subclause 4.2.6.5.5.
4.2.2.13 Request of Presence Reporting Area Change Report

If the PRA feature as defined in subclause 5.8 is supported, the PCF may provision the Presence Reporting Area
Information to the SMF as defined in subclause 4.2.6.5.6.
4.2.2.14 Provisioning of IP Index Information

If the PDU session type received within the "pduSessiontype" attribute is "IPv4" or "IPv6" or "IPv4v6", and no
corresponding IP address/prefix is received, the PCF may within the SmPolicyDecision data structure include the IP
index information within the "ipv4Index" attribute for IPv4 address allocation and/or "ipv6Index" attribute for IPv6
address allocation.
The SMF may use this to assist in selecting how the IP address is to be allocated when multiple allocation methods, or
multiple instances of the same method are supported.
4.2.2.15 Negotiation of the QoS flow for IMS signalling

If the SMF includes the "qosFlowUsage" attribute required for the default QoS flow within the SmPolicyContextData
data structure during the PDU session establishment procedure, the PCF shall provide the "qosFlowUsage" attribute
back in the response with the authorized usage.
If during PDU session establishment procedure, the SMF includes the “IMS_SIG" value within the "qosFlowUsage"
attribute and the PCF accepts that default QoS flow is dedicated to IMS signalling, the PCF shall within the
SmPolicyDecision data structure include the "IMS_SIG" value within the "qosFlowUsage" attribute. In this case, the
PCF shall restrict the QoS flow to only be used for IMS signalling as specified in 3GPP TS 23.228 [16] by applying the
applicable 5QI for IMS signalling.
If the SMF include the "IMS_SIG" value within the "qosFlowUsage" attribute of the SmPolicyContextData data
structure, but the PCF does not include the "IMS_SIG" within the "qosFlowUsage" attribute of SmPolicyDecision data
structure, the PCC Rules provided by the PCF shall have a 5QI value different from the 5QI value for the IMS
signalling.
4.2.2.16 PCF resource cleanup

In the Npcf_SMPolicyControl_Create service operation, the SMF as NF service consumer may provide SMF Id in
"smfId" attribute and recovery timestamp in "recoveryTime" attribute. The PCF may use the "smfId" attribute to
supervise the status of the SMF as described in subclause 5.2 of 3GPP TS 29.510 [29] and perform necessary cleanup
upon status change of the SMF later, and/or both the "smfId" attribute and the "recoveryTime" attribute in cleanup
procedure as described in subclause 6.4 of 3GPP TS 23.527 [33].
4.2.2.17 Access traffic steering, switching and splitting support

If the SMF supports the "ATSSS" feature defined in subclause 5.8, the SMF shall within the SmPolicyContextData data
structure include the ATSSS capability within the "atsssCapab" attribute and the MA PDU session Indication within the
"maPduInd" attribute as defined in subclause 4.2.2.2.
The SMF determines the ATSSS capability supported for the MA PDU Session based on the ATSSS capabilities
provided by the UE and per DNN configuration on SMF, as follows:
- If the SMF receives the UE’s ATSSS capabilities "MPTCP functionality with any steering mode and ATSSS-LL
functionality with only Active-Standby steering mode" and;
3GPP
Release 16 33 3GPP TS 29.512 V16.5.0 (2020-06)
- if the DNN configuration allows both MPTCP and ATSSS-LL with any steering mode, including RTT
measurement without using PMF protocol, the SMF shall set the "atsssCapab" attribute to the value
"MPTCP_ATSSS_LL_WITH_ASMODE_UL", or;
- if the DNN configuration allows both MPTCP and ATSSS-LL with any steering mode, including RTT
measurement without using PMF protocol, but the UPF does not support the RTT measurement without
using PMF protocol, the SMF shall set the "atsssCapab" attribute to the value
"MPTCP_ATSSS_LL_WITH_EXSDMODE_DL_ASMODE_UL".
- if the DNN configuration allows MPTCP with any steering mode and ATSSS-LL with only Active-Standby
steering mode, the SMF shall set the "atsssCapab" attribute to the value
"MPTCP_ATSSS_LL_WITH_ASMODE_DLUL".
- If the SMF receives the UE’s ATSSS capabilities "ATSSS-LL functionality with any steering mode" and the
DNN configuration allows ATSSS-LL with any steering mode, the SMF shall set the "atsssCapab" attribute to
the value "ATSSS_LL".
- If the SMF receives the UE’s ATSSS capabilities "MPTCP functionality with any steering mode and ATSSS-LL
functionality with any steering mode", and the DNN configuration allows both MPTCP and ATSSS-LL with any
steering mode, the SMF shall set the "atsssCapab" attribute to the value "MPTCP_ATSSS_LL".
If the SMF receives the MA PDU Request Indication from the UE and the SMF determines that the MA PDU session is
allowed based on the Session Management subscription data retrieved from the UDM and the operator policy, the SMF
shall include the "MA_PDU_REQUEST" within the "maPduInd" attribute; otherwise if the SMF receives the MA PDU
Network-Upgrade Allowed indication from the UE and the SMF determines that the MA PDU session is allowed based
on the Session Management subscription data retrieved from the UDM and the operator policy, the SMF shall include
the "MA_PDU_ NETWORK_UPGRADE ALLOWED" within the "maPduInd" attribute.
If the PCF supports the "ATSSS" feature, the PCF may provide PCC rules and/or session rules of ATSSS policy for the
MA PDU session as defined in subclause 4.2.6.2.17 and subclause 4.2.6.3.4; otherwise the PCF shall not provide any
PCC rules and/or session rules of ATSSS policy.
4.2.2.18 DNN Selection Mode Support

If the SMF supports the "DNNSelectionMode" feature defined in subclause 5.8, when the SMF receives from the AMF
the DNN selection mode, the SMF shall send an HTTP POST message as defined in subclause 4.2.2.2 and shall include
the received information in the "dnnSelMode" attribute.
The "dnnSelMode" attribute indicates whether the DNN suplied in the "dnn" attribute is an explicitly subscribed DNN
and thus verified by the network against UDM subscription (regardless of it was originally provided by the UE or
replaced by the network), or if it is a non-subscribed DNN (and provided by the UE, or replaced by the network).
If the PCF supports the "DNNSelectionMode" feature, when the "dnnSelMode" attribute indicates:
- the DNN is not explicitly subscribed, the PCF may provision PCC rules and Session rules according to the PCF
local configuration for the UE provided and/or network provided non-subscribed DNN;
- the DNN is explicitly subscribed and verified by the network against UDM subscription, the PCF proceeds
according to existing specified procedures.
4.2.2.19 Detection of TSN related SM Policy Association

When the feature "TimeSensitiveNetworking" is supported, the PCF detects if the Npcf_SMPolicyControl_Create
request relates to TSC traffic based on the received DNN and S-NSSAI. The PCF then may provide within the
SmPolicyDecision data structure the "TSN_BRIDGE_INFO" policy control request trigger within the
"policyCtrlReqTriggers" attribute to instruct the SMF to trigger a PCF interaction when the trigger is met; i.e., new 5GS
Bridge information is available.
3GPP
Release 16 34 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.3 Npcf_SMPolicyControl_UpdateNotify Service Operation
4.2.3.1 General
The UpdateNotify service operation provides updated Session Management related policies to the NF service consumer
(SMF) or triggers the deletion of the context of SM related policies. The POST method is used for both, update and
delete operations.
The following procedures using the Npcf_SMPolicyControl_UpdateNotify service operation are supported:
- PCF initiated update of the policies associated with the PDU session.
- PCF initiated deletion of SM Policy Association of a PDU session.
- Provisioning of revalidation time.
- Provisioning of PCC rule for Application Detection and Control.
- IMS Emergency Session Support.
- Request Access Network Information.
- Request Usage Monitoring Control.
- Request for the result of PCC rule removal.
- Access Network Charging Identifier request.
- Request for the successful resource allocation notification.
- IMS Restoration Support.
- P-CSCF Restoration Enhancement Support.
- Access traffic steering, switching and splitting support.
- Policy provisioning and enforcement of the AF session with required QoS.
- Forwarding of TSN information received from AF.
- Provisioning of TSCAI input information and TSC QoS related data.
- Policy provisioning and enforcement of the AF session with required QoS.
- Policy provisioning of QoS Monitoring to assist URLLC Service.
- Policy decision and condition data error handling.
3GPP
Release 16 35 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.3.2 SM Policy Association Update request
SMF PCF
1. POST {notificationUri}/update
2a. 200 OK
2b. 204 No Content
Figure 4.2.3.2-1: SM Policy Association Update request
The PCF may decide to provision policies without obtaining a request from the SMF, e.g. in response to information
provided to the PCF via the Rx or N5 reference point, or in response to an internal trigger within the PCF. The PCF
shall send a POST request to the NF Service Consumer (SMF) (../{notificationUri}/update). The payload body of the
message shall contain an SmPolicyNotification data structure that contains the representation of the updated policies
within the "smPolicyDecision" attribute and the resource URI of individual SM Policy related to the notification within
the "resourceUri" attribute. Detailed procedures related to the provisioning and enforcement of the policy decisions
within the SmPolicyDecision data structure are contained in subclause 4.2.6.
In case of a successful update of SM policies:
- if the PCF provisioned the policy control request triggers related to access type change, RAT change or location
change, a "200 OK" response code and a response body with the corresponding available information in the
"UeCampingRep" data structure shall be returned in the response;
- otherwise, a "204 No Content" response code shall be returned in the response.
If errors occur when processing the HTTP POST request, the SMF shall apply error handling procedures as specified in
subclause 5.7.
If the SMF received one or more PCC rules from the PCF but the validation of all the PCC Rules were unsuccessful, the
SMF shall reject the request and include in an HTTP "400 Bad Request" response message the ErrorReport data
structure. Within the ErrorReport data structure, SMF shall include the "error" attribute containing the "cause" attribute
of the ProblemDetails data structure set to "PCC_RULE_EVENT" or "PCC_QOS_FLOW_EVENT" and the
"ruleReports" attribute to report the PCC rule status of affected PCC rules as defined in subclause 4.2.3.16.
If the "SessionRuleErrorHandling" feature is supported and if the SMF received one or more PCC rules and/or session
rules from the PCF but the validation of all the PCC Rules and/or session rule were unsuccessful, the SMF shall reject
the request and include in an HTTP "400 Bad Request" response message the ErrorReport data structure. Within the
ErrorReport data structure, SMF shall include the "error" attribute containing the "cause" attribute of the
ProblemDetails data structure set to "RULE_PERMANENT_ERROR" or "RULE_TEMPORARY_ERROR" and the
"ruleReports" attribute to report the PCC rule status of affected PCC rules as defined in subclause 4.2.3.16 and/or the
"sessRuleReports" attribute to report the session rule status of affected session rules as defined in subclause 4.2.3.20.
If the SMF received one or more PCC rules from the PCF but the validation of some of them were unsuccessful, the
SMF shall include an HTTP "200 OK" status code together with one or more RuleReport data structure(s) to report the
PCC rule status of affected PCC rules as defined in subclause 4.2.3.16 in the "PartialSuccessReport" data structure
included in the response message. The "failureCause" attribute of the "PartialSuccessReport" shall be set to
"PCC_RULE_EVENT" or "PCC_QOS_FLOW_EVENT".
If the "SessionRuleErrorHandling" feature is supported and if the SMF received one or more PCC rule and/or session
rules from the PCF but the validation of some of them were unsuccessful, the SMF shall include an HTTP "200 OK"
status code together with the "ruleReports" attribute to report the PCC rule status of affected PCC rules as defined in
subclause 4.2.3.16 and/or the "sessRuleReports" attribute to report the session rule status of affected session rules as
defined in subclause 4.2.3.20 in the "PartialSuccessReport" data structure included in the response message. The
"failureCause" attribute of the "PartialSuccessReport" shall be set to "RULE_PERMANENT_ERROR" or
"RULE_TEMPORARY_ERROR".
3GPP
Release 16 36 3GPP TS 29.512 V16.5.0 (2020-06)
If the PCF provisioned policy control request triggers, the SMF may include in the "PartialSuccessReport" data
structure the "ueCampingRep" attribute with the corresponding available information. When it is required to report
multiple instances of the "PartialSuccessReport" data structure due to different "failureCause" values, the SMF shall
use only one instance of the "PartialSuccessReport" data structure to include the ueCampingRep" attribute with the
corresponding available information.
4.2.3.3 SM Policy Association termination request
SMF PCF
1. POST {notificationUri}/terminate
2. 204 No Content
Figure 4.2.3.3-1: SM Policy Association termination request
The PCF may request the PDU session termination in the following instances:
- If the PCF decides to terminate a PDU session due to an internal trigger or trigger from the UDR.
- The PCF may also decide to terminate an PDU session upon receiving POST message from the SMF (e.g. when
usage quota reached).
The PCF shall send a POST request to the NF Service Consumer (SMF) (../{notificationUri}/terminate) and include the
TerminationNotification data structure in the body of the HTTP POST request. Within the TerminationNotification data
structure, the PCF shall include the resource URI of the individual SM policy related to the notification within the
"resourceUri" attribute and the cause why the PCF requests the termination of the policy association encoded as "cause"
attribute.
If the SMF accepted received POST request the SMF shall send "204 No Content" response.
After the successful processing of the HTTP POST request, the SMF shall invoke the Npcf_SMPolicyControl_Delete
Service Operation defined in subclause 4.2.5 to terminate the policy association and initiate the procedure to terminate
the PDU session as defined in 3GPP TS 29.502 [22].
If errors occur when processing the HTTP POST request, the SMF shall apply error handling procedures as specified in
subclause 5.7.
4.2.3.4 Provisioning of revalidation time

During the lifetime of the PDU session, within the SmPolicyDecision data structure, the PCF may provide the
revalidation time within the "revalidationTime" attribute and the RE_TIMEOUT policy control request trigger within
the "policyCtrlReqTriggers" attribute to instruct the SMF to trigger a PCF interaction to request PCC rule from the PCF
if not provided yet. The PCF may also update the revalidation time by including the new value within the
"revalidationTime" attribute. The PCF may disable the revalidation function by removing RE_TIMEOUT policy control
request trigger if it has been provided.
If the SMF receives revalidation time or new revalidation time, the SMF shall store the received value and start the
timer based on it. Then the SMF shall send the PCC rule request before the indicated revalidation time.
If the RE_TIMEOUT policy control request trigger is removed, SMF shall stop the timer for revalidation.
The PCF may modify the authorized session AMBR at any time during the lifetime of the PDU session and provision it
to the SMF by invoking the procedure as defined in subclause 4.2.3.2. The PCF shall provision the new authorized
session AMBR to the SMF in the response of the message as defined in subclauses 4.2.6.2.1 and 4.2.6.2.2.
3GPP
Release 16 37 3GPP TS 29.512 V16.5.0 (2020-06)
Upon receiving the authorized session AMBR, the SMF shall apply the corresponding procedures towards the access
network, the UE and the UPF for the enforcement of the AMBR per PDU session.
For UL Classifier or Multi-homing PDU Session, the SMF will provision the policies of session-AMBR for downlink
and uplink direction to the UL Classifier/Branching Point functionality and in addition provision the policies of session-
AMBR in the downlink direction to all the PDU session anchors as defined in subclause 5.4.4 of 3GPP TS 29.244 [13].

The PCF may modify the authorized default QoS during the lifetime of the PDU session and provision it to the SMF by
invoking the procedure as defined in subclause 4.2.3.2. The PCF shall provision the authorized default QoS to the SMF
in the response of the message as defined in subclauses 4.2.6.3.1 and 4.2.6.3.2.
4.2.3.7 Provisioning of PCC rule for Application Detection and Control

If the ADC feature is supported, and the user subscription indicates that the application detection and control is
required, the PCF may provision PCC rule for application detection and control as defined in subclause 4.2.6.2.11 in the
HTTP POST request.
If the SMF receives the PCC rule for application detection and control, the SMF shall instruct the UPF as defined in
3GPP TS 29.244 [13] to detect the application traffic.

When the PCF receives service information from the AF while the 3GPP PS Data Off handling functionality is active as
described in subclause 4.2.2.8 or 4.2.4.8, the PCF shall check:
- for a non-MA PDU session, whether the corresponding service is a 3GPP PS Data Off Exempt Service and
permissible according to the user´s subscription and the policies of the PCF;
- for a MA PDU session:
a. whether the corresponding service is a 3GPP Data Off Exempt Service and permissible according to the
user’s subscription and the policies of the PCF; or
b. the corresponding service does not belong to the 3GPP PS Data Off Exempt services but:
- the non-3GPP access is available; and
- the PCF policies allow all the traffic of the service is forwarded using the non-3GPP access.
If so, the PCF shall install, modify or delete corresponding PCC rules. For a MA PDU session and when service does
not belong to the 3GPP PS Data Off Exempt services, the policy for ATSSS Control included in the PCC rule, as
specified in subclause 4.2.6.2.17, shall enable all the traffic is forwarded using only the non-3GPP access.
Otherwise, the PCF shall reject the service information from the AF.
If the PCF determines that the 3GPP PS Data Off handling functionality becomes inactive, the PCF shall perform policy
control decision and provision the PCC rules to make sure that services are allowed according to the user's subscription
and operator policy (irrespective of whether they belong to the list of 3GPP PS Data Off Exempt Services).
NOTE: The PCF can then open gates via the "flowStatus" attribute for active PCC associated to services not
within the list 3GPP PS Data Off Exempt Services. The PCF can also install PCC rules or activate
predefined PCC rules for some services not belonging to the list 3GPP PS Data Off Exempt Services. If
the PCF activates or installs a PCC rule with wildcarded filters, it can remove or de-activate PCC rules for
3GPP PS Data Off Exempt Services that are made redundant by this PCC rule.
3GPP
Release 16 38 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.3.9 IMS Emergency Session Support
4.2.3.9.1 Provisioning of PCC rule

When the PCF receives IMS service information from the AF for an Emergency service and derives authorized PCC
Rules from the service information, the "priorityLevel" attribute, the "preemptCap" attribute and the "preemptVuln"
attribute in the ARP within the QoS data decision which the PCC Rule refers to shall be assigned a priority and pre-
emption as required by local operator policies (e.g. if an IMS Emergency session is prioritized the "priorityLevel"
attribute may contain a value that is reserved for an operator domain use of IMS Emergency session).
The PCF shall immediately initiate the procedure as described in subclause 4.2.6.2.1 to provision PCC Rules and the
procedures described in subclause 4.2.6.2.3 to provision the authorized QoS per service data flow.
The provisioning of PCC Rules at the SMF that require the establishment of a dedicated QoS flow for emergency
services shall cancel the inactivity timer in the SMF, if it started running as defined in the subclause 4.2.3.9.2.
Any SMF-initiated request for PCC Rules for an IMS Emergency service with the "repPolicyCtrlReqTriggers" attribute
containing the "RES_MO_RE" value (i.e. UE-initiated resource reservation) shall be rejected by the PCF with an
appropriate status code.
The SMF shall execute the procedures to ensure that a new QoS flow is established for the Emergency service.
When the SMF detects that the provisioning of PCC Rules failed, the PCC rule error handling procedure shall be
performed.
4.2.3.9.2 Removal of PCC Rules for Emergency Services

The reception of a request to terminate an AF session for an IMS Emergency service by the PCF triggers the removal of
PCC Rules assigned to the terminated IMS Emergency Service from the SMF by using the procedure as defined in
subclause 4.2.6.2.1 to removed PCC Rules.
At reception of an HTTP POST message that removes one or several PCC Rules from an PDU Session restricted to
emergency services the SMF shall:
- when all PCC Rules bound to a QoS flow are removed, initiate a QoS flow termination procedure.
- when not all PCC Rule bound to a QoS flow are removed, initiate an QoS flow modification procedure.
In addition, the SMF shall initiate an inactivity timer if all PCC Rules with a 5QI other than the 5QI of the default QoS
flow or the 5QI used for IMS signalling were removed from the PDU session restricted to Emergency Services (e.g., to
enable PSAP Callback session). When the inactivity timer expires, the SMF shall initiate a PDU session termination
procedure as defined in subclause 4.2.3.3.
4.2.3.10 Request of Access Network Information

If the NetLoc as defined in subclause 5.8 is supported, the PCF may request the SMF to report the access network
information as defined in subclause 4.2.6.5.4.
4.2.3.11 Request Usage Monitoring Control

If the UMC as defined in subclause 5.8 is supported, the PCF may provision the usage monitoring control policy to the
SMF as defined in subclause 4.2.6.5.3 to request the usage monitoring control.
4.2.3.12 Ipv6 Multi-homing support

During the lifetime of the Multi-homing PDU session, the PCF shall provision the PCC rules and session rules to SMF.
The SMF shall derive the appropriate policies based on the policies provisioned by the PCF and provision them to the
appropriate UPF if applicable, access network, if applicable, and UE if applicable.
3GPP
Release 16 39 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.3.13 Request for the result of PCC rule removal

If the RAN-NAS-Cause feature is supported, the PCF may request the SMF to inform it of the result of the PCC rule
removal when the PCF removes the PCC rule as defined in subclause 4.2.6.5.2.
When the SMF receives the request, the SMF shall maintain locally the removed PCC rules until it receives of the
resource release outcome from the network.
4.2.3.14 Access Network Charging Identifier request

The PCF may request the SMF to provide the Access Network Charging Identifier associated to the dynamic PCC rules
as defined in subclause 4.2.6.5.1.
4.2.3.15 Request for the successful resource allocation notification

4.2.3.16 PCC Rule Error Report

If the SMF receives one or more PCC rules as defined in subclause 4.2.3.1 but the validation of all the PCC Rule was
unsuccessful, the SMF shall reject the request and include an HTTP "400 Bad Request" status code and the
"ruleReports" attribute for the affected PCC rules to report the failure within the ErrorReport data structure; otherwise if
the validation of some of PCC rules was unsuccessful, the SMF shall include an HTTP "200 OK" status code and one or
more RuleReport data structure(s) for the affected PCC rules to report the failure within the PartialSuccessReport data
structure in the response message. Within each RuleReport instance, the SMF shall identify the failed PCC rule(s) by
including the affected PCC rules within the "pccRuleIds" attribute(s), identify the failed reason code by including a
"failureCode" attribute, and shall include rule status within the "ruleStatus" attribute with the value as described below.
If the installation/activation of one or more new PCC rules (i.e. rules which were not previously successfully installed)
fails, the SMF shall set the "ruleStatus" to INACTIVE.
If the modification of a currently active PCC rule fails, the SMF shall retain the existing PCC rule as active without any
modification unless the reason for the failure has an impact also on the existing PCC rule.
The removal of a PCC rule shall not fail, even if the PDU session procedures with the UE fail. The SMF shall retain
information on the removal and conduct the necessary PDU session procedures with the UE when it is possible.
Depending on the value of the "failureCode" attribute, the PCF may decide whether retaining of the old PCC rule, re-
installation, modification, removal of the PCC rule or any other action applies.
If the "RuleVersioning" feature is supported and the PCF included the "contVer" attribute for a specific PCC rule
instance in the "pccRules" attribute, then if the resource allocation for the corresponding PCC rule was unsuccessful, the
SMF shall include the "contVers" attribute for the corresponding RuleReport instance included in the "ruleReports"
attribute. Depending on the value of the "failureCode" attribute, and when applicable, depending also on the value of
the "contVer" attribute, the PCF may decide whether retaining of the old PCC rule, re-installation, modification,
removal of the PCC rule or any other action applies.
4.2.3.17 IMS Restoration Support

In order to support IMS Restoration procedures (refer to 3GPP TS 23.380 [21]), PCF needs to convey the AF address to
the SMF. In order to do so, in case AF provisions information about the AF signalling flows between the UE and the
AF, as defined in 3GPP TS 29.214 [18] subclause 4.4.5a, or in 3GPP TS 29.514 [17] subclause 4.2.2.16 and 4.2.3.17,
the PCF shall install the corresponding dynamic PCC rules (if not installed before) as defined in subclause 4.2.6.2.1.
The PCF shall within the PccRule instance include the signalling flows between UE and the AF within the "flowInfos"
attribute and the "afSigProtocol" attribute set to the value corresponding to the signalling protocol used between the UE
and the AF.
The SMF shall respond with "204 no content" to the PCF and initiate the corresponding QoS flow procedure if required.
The SMF shall extract the AF address from the PCC rules and use it for the monitoring procedure as defined for the
different access types.
3GPP
Release 16 40 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE 1: The SMF can use the extracted AF address from the PCC rule to check if, the monitoring procedure has
to be started for the corresponding AF.
In case AF de-provisions information about the AF signalling flows between the UE and the AF, as defined in
3GPP TS 29.214 [18] subclause 4.4.5a, or in 3GPP TS 29.514 [17] subclause 4.2.2.16 and 4.2.3.17, the PCF shall
remove the corresponding dynamic PCC rules by triggering an HTTP POST message. The PCF shall apply the
procedure as defined in subclause 4.2.6.2.1.
The SMF shall send a HTTP response message to the PCF.
NOTE 2: The SMF can use the AF address associated with the removed rule to check if it can stop monitoring the
corresponding AF.
4.2.3.18 P-CSCF Restoration Enhancement Support

This subclause is applicable when the PCF-based P-CSCF Restoration Enhancement, as defined in
3GPP TS 23.380 [21], represented by the supported feature "PCSCF-Restoration-Enhancement" is supported by both
PCF and SMF.
If the PCF receives a request for P-CSCF restoration from the P-CSCF as defined in subclause 4.4.7 of
3GPP TS 29.214 [18] or in subclause 4.2.2.27 of 3GPP TS 29.514 [17], the PCF shall send an HTTP POST message
including the "pcscfRestIndication" attribute set to true to the SMF for the corresponding PDU session.
The SMF shall acknowledge to the PCF and shall initiate the corresponding QoS flow procedure for the IMS PDU
connection as defined in 3GPP TS 23.380 [21].
4.2.3.19 Request of Presence Reporting Area Change Report

If the PRA feature as defined in subclause 5.8 is supported, the PCF may provision the Presence Reporting Area
Information to the SMF as defined in subclause 4.2.6.5.6.
4.2.3.20 Session Rule Error Report

If the "SessionRuleErrorHandling" feature is supported and if the SMF receives one or more session rules as defined in
subclause 4.2.6.3.1 but the validation of all the session Rule was unsuccessful, the SMF shall reject the request and
include an HTTP "400 Bad Request" status code and the "sessRuleReports" attribute for the affected session rules to
report the failure within the ErrorReport data structure; otherwise if the validation of some of session rules was
unsuccessful, the SMF shall include an HTTP "200 OK" status code and one or more SessionRuleReport data
structure(s) for the affected session rules to report the failure within the PartialSuccessReport data structure in the
response message. Within each SessionRuleReport instance, the SMF shall identify the failed session rule(s) by
including the affected session rules within the "ruleIds" attribute(s), identify the failed reason code by including a
"sessRuleFailureCode" attribute, and shall include rule status within the "ruleStatus" attribute with the value as
described below.
If the installation/activation of one or more new session rules (i.e. rules which were not previously successfully
installed) fails, the SMF shall set the "ruleStatus" to INACTIVE.
If the modification of a currently active session rule fails, the SMF shall retain the existing session rule as active without
any modification unless the reason for the failure has an impact also on the existing session rule.
The removal of a session rule shall not fail, even if the PDU session procedures with the UE fail. The SMF shall retain
Depending on the value of the "sessRuleFailureCode" attribute, the PCF may decide whether retaining of the old
session rule, re-installation, modification, removal of the session rule or any other action applies.

If the PCF supports the "ATSSS" feature, the PCF may provide PCC rules and/or session rules for the MA PDU session
as defined in subclause 4.2.6.2.17 and subclause 4.2.6.3.4.
3GPP
Release 16 41 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.3.22 Policy provisioning and enforcement of the AF session with required QoS
If the PCF receives a QoS reference parameter during the initial provisioning of service information as defined in
subclause 4.2.2.32 of 3GPP TS 29.514 [17] and if the PCF and the SMF support the "AuthorizationWithRequiredQoS"
feature as defined in subclause 5.8, the PCF shall authorizes the service information from the AF and derive the QoS
parameters of the PCC rule based on the service information and the indicated QoS reference parameter.
NOTE: A SLA has to be in place between the operator and the ASP defining the possible QoS levels and their
charging rates. For each of the possible pre-defined QoS information sets, the PCF needs to be configured
with the corresponding QoS parameters and their values as well as the appropriate Charging key (or
receive this information from the UDR).
If the PCF receives a different QoS reference parameter during the modification of service information as defined in
subclause 4.2.3.32 of 3GPP TS 29.514 [17], the PCF shall update the related QoS parameters corresponding to the new
QoS reference parameter in the PCC rule accordingly.
If the AF subscribes to Service Data Flow QoS notification control, the PCF may additionally receive the Alternative
Service Requirements during the initial provisioning of service information as defined in subclause 4.2.2.32 of
3GPP TS 29.514 [17]. In this case, when the PCF authorizes service information based on the indicated QoS reference
parameter, the PCF shall additionally derive alternative QoS parameter sets for this PCC rule based on the QoS
reference parameters in the Alternative Service Requirements. In order to do so, the PCF shall include one or more
references to the QosData data structure within the "refAltQosParams" attribute of the PCC rule and a "qosDecs"
attribute containing these one or more QoS data decision(s) within the SmPolicyDecision data structure. In each QoS
data decision instance, the PCF shall include alternative QoS parameter set Id within the "qosId" attribute, the
alternative 5QI with the "5qi" attribute, the alternative maximum bandwidth in unlink within the "maxbrUl" attribute,
the alternative maximum bandwidth in downlink within the "maxbrDl" attribute, the alternative guaranteed bandwidth
in uplink within the "gbrUl" attribute, and the alternative guaranteed bandwidth in downlink within the "gbrDl"
attribute. The "refAltQosParams" attribute is an ordered list of alternative QoS parameter sets, where the lower the
index of the array for a given entry, the higher the priority.
If the AF changes the Alternative Service Requirements during the modification of service information as defined in
subclause 4.2.3.30 of 3GPP TS 29.514 [17], the PCF shall update the Alternative QoS parameter sets in the PCC rule
accordingly.
The PCF shall provision the PCC rule with alternative QoS parameter set(s) and enable QoS Notification Control if it
has not been enabled yet as defined in subclause 4.2.3.30.
When the SMF receives the PCC rule with alternative QoS parameter sets, the SMF shall enforce the PCC rule with the
addition that the SMF shall derive the alternative QoS profile(s) towards the access network based on the alternative
QoS parameter set(s).
4.2.3.23 Forwarding of TSN information received from the AF

During the lifetime of a PDU session related to a TSN communication the PCF may receive a BMIC and/or one or more
PMIC(s) from the AF within the service information as defined in 3GPP TS 29.514 [17]. A BMIC carries TSN bridge
management information. A PMIC carries TSN port management information for a TSN port located in DS-TT and/or
NW-TT.
If the feature "TimeSensitiveNetworking" is supported the PCF initiates the Npcf_SMPolicyControl_UpdateNotify

request and sends possibly updated policy information about the PDU Session and/or the BMIC and/or the PMIC(s) to
the SMF via the SmPolicyDecision structure, in which the BMIC is encoded in the "tsnBridgeManCont" attribute, the
DS-TT PMIC is encoded in the "tsnPortManContDstt" attribute and the one or more NW-TT PMIC(s) are encoded in
the "tsnPortManContNwtts" attribute.
The PMIC(s) are encoded in the "PortManagementContainer" data type, that includes the port management information
in the "portManCont" attribute and the related TSN port number in the "portNum" attribute. If the TSN port is on DS-
TT the SMF forwards the PMIC(s) to the DS-TT port. If the TSN port is on NW-TT the SMF forwards the PMIC(s) to
the NW-TT port.
The BMIC is encoded in the "BridgeManagementContainer" data type, that includes the bridge management
information in the "bridgeManCont" attribute. The SMF always forwards the BMIC to the Bridge functionality of the
UPF/NW-TT.
3GPP
Release 16 42 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.3.24 Provisioning of TSCAI input information and TSC QoS related data
The PCF may receive the TSCAI input information and TSC traffic QoS related information from the AF.
If the feature "TimeSensitiveNetworking" is supported by both the SMF and PCF as described in subclause 5.8, the PCF
shall provide for the derived PCC rule(s):
- the 5G QoS parameters and the optional 5G QoS characteristics corresponding to a 5QI for a delay-critical GBR
derived from the TSC traffic QoS information received from the TSN AF encoded within a QosData type
referred in the "refQosData" of the PCC rule; and
- the TSCAI input information container as received from the TSN AF encoded in the "tscaiInputUl" attribute
and/or "tscaiInputDl" attribute of the PCC rule.
The values of MDBV and PDB applied to the derived 5QI shall follow principles defined in subclause 5.27.3 of
3GPP TS 23.501 [2].
The value of the MBR, if applicable, and the GBR are derived using the Maximum Bit Rate provided by the TSN AF,
and the ARP is assigned a value preconfigured for TSN services.
The SMF shall convert the received TSCAI input information from the TSN GM into the 5G GM based on the time
offset and cumulative rateRatio between TSN time and 5GS time as measured and reported by the UPF and, forward the
derived TSCAI parameters per QoS Flow basis to the AN-RAN as follows:
- for the traffic in downlink direction, correct the value of the "burstArrivalTime" attribute of the "tscaiInputDl"
attribute based on the latest received time offset measurement from the UPF and set the downlink TSCAI Burst
Arrival Time as the sum of the correct value and the CN PDB as described in subclause 5.7.3.4 of
3GPP TS 23.501 [2].
- for the traffic in uplink direction, correct the value of "burstArrivalTime" attribute of the "tscaiInputUl" attribute
based on the latest received time offset measurement from the UPF and set the uplink TSCAI Burst Arrival Time
as the sum of correct value and the UE-DS-TT Residence Time.
- correct the value of "periodicity" attribute of the "tscaiInputUl" and/or "tscaiInputDl" based on the latest received
cumulative rateRatio measurement from the UPF and set the TSCAI Periodicity as the corrected value.
The provisioning of TSCAI input information and TSC traffic QoS configuration per PCC Rule shall be performed
using the PCC rule provisioning procedure as defined in subclause 4.2.6.2.1.
4.2.3.25 Policy provisioning of QoS Monitoring to Assist URLLC Service

The QoS Monitoring for URLLC refers to the real time packet delay measurement between the UE and the UPF for a
QoS flow corresponding to an URLLC service.
If the "QosMonitoring" feature is supported, the PCF may generate the authorized QoS Monitoring data decision for the
service data flow based on the QoS Monitoring request if received from the AF. The PCF shall include within the
SmPolicyDecision data structure one or more QosMonitoringData instances within the "qosMonDecs" attribute and
"QOS_MONITORING" within the "PolicyCtrlReqTriggers" attribute if the PCF determines the QoS monitoring report
shall be sent to the PCF from the SMF and if it has not been provisioned yet.
NOTE: The QoS monitoring report can be sent to the PCF as described in subclause 4.2.4.24 or to the AF directly
as described in 3GPP TS 29.508 [12] based on the PCF decision.
For each QosMonitoringData instance, PCF shall include:
- the requested QoS monitoring parameter(s) to be measured (i.e. DL, UL and/or round trip packet delay) within
the "reqQosMonParams" attribute;
- the frequency(s) of reporting (e.g. event triggered, periodic, or when the PDU Session is released, and/or any
combination) within the "repFreqs" attribute;
- for the case the "repFreqs" attribute includes the value "EVENT_TRIGGERED":
- the delay threshold for downlink with the "repThreshDl" attribute if "reqQosMonParams" attribute includes
DOWNLINK;
3GPP
Release 16 43 3GPP TS 29.512 V16.5.0 (2020-06)
- the delay threshold for uplink with the "repThreshUl" attribute if "reqQosMonParams" attribute includes
UPLINK; and/or
- the delay threshold for round trip with the "repThreshRp" attribute if "reqQosMonParams" attribute includes
ROUND_TRIP;
- the minimum waiting time between subsequent reports within the "waitTime" attribute;
- for the case the "repFreqs" attribute includes "PERIODIC", the reporting period within the "repPeriod" attribute;
- the notification URI within the "notifUri" attribute and the notification correlation id within the "notifCorreId"
attribute if the PCF determines that the notification shall be sent to the AF directly from the SMF.
The PCF shall include the value of QoS Monitoring Data ID of QosMonitoringData instance within the "refQosMon"
attribute of the corresponding PCC rule and provide the QoS monitoring data decision together with the PCC rule if it
has not been provisioned to the SMF. When the SMF receives the PCC rule, the SMF shall send a QoS Monitoring
request to the PSA UPF via N4 as defined in 3GPP TS 29.244 [13] and NG-RAN via N2 signalling to request the QoS
monitoring between PSA UPF and NG-RAN as defined in 3GPP TS 29.503 [34]
If the PCF receives the request to disable the QoS monitoring from the AF, the PCF shall update the PCC rule with the
"refQosMon" attribute set to NULL. The PCF may also remove the corresponding QoS Monitoring Data if no PCC rule
is referring to it.
4.2.3.26 Policy decision and condition data error handling

If the "PolicyDecisionErrorHandling" feature is supported and if the SMF receives one or more policy decisions and/or
condition datas which are not referred by any PCC rules or session rules as defined in subclause 4.2.3.1 but the storage
of the policy decisions and/or condition datas was unsuccessful (e.g. the policy decision could not be successfully stored
due to a limitation of resources at the SMF), the SMF shall behave as follows:
- include an HTTP "200 OK" status code and one or more PolicyDecisionFailureCode data types to indicate the
type(s) of the failed policy decisions and/or condition data in the response message if the SMF does not need to
report any other information (e.g. the failure report of the PCC rule or session rule which are provisioned in the
same message are not needed).
- include an HTTP "200 OK" status code and the "policyDecFailureReports" attribute to indicate the type(s) of the
failed policy decisions and/or condition data within the PartialSuccessReport data structure in the response
message if the SMF needs to report partial success (e.g. some of the PCC rules and/or session rules provisioned
by the PCF in the same message are not installed/activated successfully).
- include an HTTP "400 Bad Request" status code and the "policyDecFailureReports" attribute to indicate the
type(s) of the failed policy decisions and/or condition data within the ErrorReport data structure in the response
message if the SMF needs to reject the request (e.g. all the PCC rules and/or session rules provisioned by the
PCF in the same message are not installed/activated successfully).
When the PCF receives the above reports, the PCF shall consider all the instances of the policy decsions and/or
condition data which are provisioned in the request message and indicated by the PolicyDecisionFailureCode data type
are removed from the SMF. When the PCF receives the response with HTTP "400 Bad Request" status code but the
"policyDecFailureReports" attribute is not included, the PCF shall consider all the provisioned instances of the policy
decsions and/or condition data in the request message are removed from the SMF.
4.2.4 Npcf_SMPolicyControl_Update Service Operation
4.2.4.1 General
The Npcf_SMPolicyControl_Update service operation provides means for the NF service consumer to inform the PCF
that a policy control request trigger condition has been met and for the PCF to inform the NF service consumer of any
resulting update of the Session Management related policies.
The following procedures using the Npcf_SMPolicyControl_Update service operation are supported:
3GPP
Release 16 44 3GPP TS 29.512 V16.5.0 (2020-06)
- Request the policy based on revalidation time.
- Application detection information reporting.
- Indication of QoS Flow Termination Implications.
- Request and report Access Network Information.
- Request Usage Monitoring Control and report Accumulated Usage.
- Ipv6 Multi-homing support.
- Request and report the result of PCC rule removal.
- Access Network Charging Identifier Request and report.
- Request and report the successful resource allocation notification.
- Negotiation of the QoS flow for IMS signalling.
- Notification about Service Data Flow QoS target enforcement.
- Request the termination of SM Policy association.
- Reporting of TSN information.
- QoS Monitoring Report.
- Policy decision and condition data error handling.
- Request the policy after DDN failure events.
4.2.4.2 Requesting the update of the Session Management related policies
SMF PCF
1. POST …/sm-policies/{smPolicyId}/update
2. 200 OK
Figure 4.2.4.2-1: Requesting the update of the Session Management related policies
When the SMF detects that one or more policy control request triggers are met, the SMF shall send a POST request to
the PCF to update an Individual SM Policy resource. The {smPolicyId} in the URI identifies the Individual SM Policy
resource to be updated. The SMF include SmPolicyUpdateContextData data structure in the payload body of the HTTP
POST to request a update of representation of the "Individual SM Policy" resource. The SMF shall include the met
policy control request trigger(s) within the "repPolicyCtrlReqTriggers" attribute and applicable updated value(s) in the
corresponding attribute(s).
The SMF shall include (if the corresponding policy control request trigger is met and the applicable information is
available) in SmPolicyUpdateContextData data structure:
3GPP
Release 16 45 3GPP TS 29.512 V16.5.0 (2020-06)
- type of access within the "accessType" attribute;
- type of the radio access technology within the "ratType" attribute;
- the new allocated UE Ipv4 address within the "ipv4Address" attribute and/or the UE Ipv6 prefix within the
"ipv6AddressPrefix" attribute;
- multiple new allocated UE Ipv6 prefixes within the "addIpv6AddrPrefixes" attribute, if the
"MultiIpv6AddrPrefix" feature is supported;
- the released UE Ipv4 address within the "ipv4Address" attribute and/or the UE Ipv6 prefix within the
"relIpv6AddressPrefix" attribute;
- multiple released UE Ipv6 prefixes within the "addRelIpv6AddrPrefixes" attribute, if the "MultiIpv6AddrPrefix
feature" is supported;
- the UE MAC address within the "ueMac" attribute;
- the released UE MAC address within the "relUeMac" attribute;
- the indication of UE supporting reflective QoS within the "refQosIndication" attribute;
- access network charging identifier within the "accNetChIds" attribute;
- 3GPP PS data off status within the "3gppPsDataOffStatus" attribute;
- the UE time zone information within the "ueTimeZone" attribute;
- the UDM subscribed Session-AMBR or, if the "DN-Authorization" feature is supported, the DN-AAA
authorized Session-AMBR within the "subsSessAmbr" attribute;
NOTE 1: When both, the UDM subscribed Session-AMBR and the DN-AAA authorized Session-AMBR are
available in the SMF, the SMF includes the DN-AAA authorized Session-AMBR.
- if the "DN-Authorization" feature is supported, the DN-AAA authorization profile index within the
"authProfIndex" attribute;
- subscribed Default QoS Information within the "subsDefQos" attribute;
- detected application information within the "appDetectionInfos" attribute;
- accumulated usage reports within the "accuUsageReports" attribute;
- reported presence reporting area information within the "praInfos" attribute;
- the QoS flow usage required of the default QoS flow within the "qosFlowUsage" attribute;
- indication whether the QoS targets of one or more SDFs are not guaranteed or guaranteed again within the
"qncReports" attribute;
- serving network function identifier within the "servNfId" attribute; and
- identifier of the serving network within the "servingNetwork" attribute.
The SMF may include in "SmPolicyUpdateContextData" data structure the IPv4 address domain identity within the
"ipDomain" attribute.
In case of a successful update, "200 OK" response shall be returned. The PCF shall include in the "200 OK" response
the representation of the updated policies within the SmPolicyDecision data structure. Detailed procedures related to the
provisioning and enforcement of the policy decisions within the SmPolicyDecision data structure are contained in
subclause 4.2.6.
NOTE 2: An empty SmPolicyDecision data structure is included in the "200 OK" response when the PCF decides
not to update policies.
3GPP
Release 16 46 3GPP TS 29.512 V16.5.0 (2020-06)
If errors occur when processing the HTTP POST request, the PCF shall apply error handling procedures as specified in
subclause 5.7.
If the PCF is, due to incomplete, erroneous or missing information (e.g. QoS, RAT type, subscriber information) not
able to provision a policy decision as response to the request for PCC rules by the SMF, the PCF may reject the request
and include in an HTTP "400 Bad Request " response message the "cause" attribute of the ProblemDetails data structure
set to "ERROR_INITIAL_PARAMETERS".
If the PCF receives the set of session information which is sent in the message originated due to a trigger being met is
incoherent with the previous set of session information for the same session (E.g. trigger met was RAT changed, and
the RAT notified is the same as before), the PCF may reject the request and include in an HTTP "400 Bad Request"
response message the "cause" attribute of the ProblemDetails data structure set to "ERROR_TRIGGER_EVENT".
If the PCF detects that the packet filters in the request for new PCC rules received from the SMF is covered by the
packet filters of outstanding PCC rules that the PCF is provisioning to the SMF, the PCF may reject the request and
include in an HTTP "403 Forbidden" response message the "cause" attribute of the ProblemDetails data structure set to
"ERROR_CONFLICTING_REQUEST".
If the PCF does not accept one or more of the traffic mapping filters provided by the SMF in an HTTP POST request
(e.g. because the PCF does not allow the UE to request enhanced QoS for services not known to the PCF), the PCF shall
reject the request and include in an HTTP "403 Forbidden" response message the "cause" attribute of the
ProblemDetails data structure set to "ERROR_TRAFFIC_MAPPING_INFO_REJECTED".
If the SMF receives HTTP response with these codes, the SMF shall reject the PDU session modification that initiated
the HTTP Request.
The PCF shall not combine a rejection with provisioning of PCC rule operations in the same HTTP response message.
4.2.4.3 Request the policy based on revalidation time

If the timer for the policy revalidation is started, the SMF shall send the PCC rule request before the indicated
revalidation time. The SMF shall within the SmPolicyUpdateContextData data structure include RE_TIMEOUT within
the "repPolicyCtrlReqTriggers" attribute. The SMF shall stop the timer once the SMF sends the request.
NOTE 1: The PCF is expected to be prepared to provide a new policy, as desired for the revalidation time, during a
preconfigured period before the revalidation time. The preconfigured periods in the SMF and PCF need to
be aligned.
The PCF may provide a new value of revalidation time by including "revalidationTime" attribute within the
SmPolicyDecision in the response. The PCF may disable the revalidation function by removing the RE_TIMEOUT
policy control request trigger in the response.
When the SMF receives the response message, the SMF shall start the timer for revalidation based on the new value or
existing value of revalidation time if the revalidation function is not disabled; otherwise, the SMF shall not start the
timer for revalidation.
NOTE 2: By removing the RE_TIMEOUT the revalidation time value previously provided to the SMF is not
applicable anymore.
When the SMF detects that the session AMBR changes, the SMF shall notify of the change to the PCF by invoking the
procedure defined in subclause 4.2.4.2, and shall include the new session AMBR within the "subsSessAmbr" attribute
and the "SE_AMBR_CH" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute.
If the "DN-Authorization" feature is supported, when both, the UDM subscribed Session-AMBR and the DN-AAA
authorized Session-AMBR are available in the SMF, the DN-AAA authorized/re-authorized Session-AMBR shall take
precedence over the changes on UDM subscribed Session-AMBR.
Upon receiving the change of session AMBR, the PCF shall provision the new authorized session AMBR to the SMF in
the response as defined in subclauses 4.2.6.2.1 and 4.2.6.2.2.
Upon receiving the authorized session AMBR from the PCF, the SMF shall apply the corresponding procedures
towards the access network, the UE and the UPF for the enforcement of the AMBR per PDU session.
3GPP
Release 16 47 3GPP TS 29.512 V16.5.0 (2020-06)
For UL Classifier or Multi-homing PDU Session, the SMF will provision the policies of session-AMBR for downlink
and uplink direction to the UL Classifier/Branching Point functionality and in addition provision the policies of session-
AMBR in the downlink direction to all the PDU session anchors as defined in subclause 5.4.4 of 3GPP TS 29.244 [13].

When the SMF detects that the subscribed default QoS change, the SMF shall notify of the PCF by invoking the
procedure as defined in subclause 4.2.4.2, include the new subscribed default QoS within the "subsDefQos" attribute
and "repPolicyCtrlReqTriggers" set to DEF_QOS_CH. Upon receiving the change of default QoS, the PCF shall
provision the authorized default QoS to the SMF in the response of the message The PCF shall provision the authorized
default QoS to the SMF in the response of the message as defined in subclauses 4.2.6.3.1 and 4.2.6.3.2.
4.2.4.6 Application detection information reporting

If the ADC feature is supported and if the SMF receives the PCC rule for application detection and control, the SMF
shall instruct the UPF as defined in 3GPP TS 29.244 [13] to detect the application traffic. When the start of the
application`s traffic, identified by an application identifier, is received from the UPF, if PCF has previously provisioned
the APP_STA/APP_STO policy control request trigger, unless a request to mute such a notification (i.e. the
"muteNotif" attribute set to true within the Traffic Control Data decision which the PCC rule refers to), the SMF shall
report the start of the application to the PCF. In order to do so, the SMF shall perform the procedure as defined in
subclause 4.2.4.2 by including the information regarding the detected application`s traffic within the
"appDetectionInfos" attribute and the "APP_STA" within the "repPolicyCtrlReqTriggers" attribute even if the
application traffic is discarded due to enforcement actions of the PCC rule. In this case, within the each
AppDetectionInfo instance, the SMF shall include the corresponding application identifier within the "appId" attribute,
may include the detected service data flow description within the "sdfDescriptions" attribute and application instance
identifier within the "instanceId" if deducible. The "sdfDescriptions" attribute, if present, shall contain the
"flowDescription" attribute and "flowDirection" attribute. The application instance identifier, which is dynamically
assigned by the SMF in order to allow correlation of APP_STA and APP_STO policy control request trigger to the
specific service data flow descriptions.
When the stop of the application's traffic, identified by an application identifier is received from the UPF and the SMF
has reported the start of the application to the PCF, the SMF shall report the stop of the application to the PCF. In order
to do so, the SMF shall perform the procedure as defined in subclause 4.2.4.2 by including the information regarding
the detected application`s traffic within the "appDetectionInfos" attribute and the "APP_STO" within the
"repPolicyConReqTriggers" attribute. For each AppDetectionInfo instance, the SMF shall include the corresponding
application identifier within the "appId" attribute and application instance identifier within the "instanceId" if it is
provided along with the APP_STA.
The PCF then may make policy decisions based on the information received and send the corresponding updated PCC
rules to the SMF.
4.2.4.7 Indication of QoS Flow Termination Implications

When the SMF detects that a dedicated QoS flow could not be activated or has been terminated it shall remove the
affected PCC rules and send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure,
including the "ruleReports" attribute containing the RuleReport data instance which specifies the affected PCC rules
within the "pccRuleIds" attribute(s), "INACTIVE" as the value within the "ruleStatus" attribute and the
"RES_ALLO_FAIL" as the value of the "failureCode" attribute.
If the RAN-NAS-Cause feature is supported, the SMF shall provide the available access network information within the
"userLocationInfo" attribute (if available), "userLocationInfoTime" attribute (if available) and "ueTimezone" attribute
(if available). Additionally, if the SMF receives from the access network the RAN cause and/or the NAS cause due to
QoS flow termination the SMF shall provide the received cause(s) in the "ranNasRelCauses" attribute included in
RuleReport data instance.
If the NetLoc feature is supported, and if the identifier of the affected PCC rule was included within the "refPccRuleIds"
attribute of the RequestedRuleData data structure when the affected PCC rule was installed or modified, the SMF shall
provide the access network information to the PCF by including the user location information within the
3GPP
Release 16 48 3GPP TS 29.512 V16.5.0 (2020-06)
"userLocationInfo" attribute (if requested by the PCF and if provided to the SMF), the information on when the UE was
last known to be in that location within "userLocationInfoTime" attribute (if user location information was requested by
the PCF and if the corresponding information was provided to the SMF), the PLMN identifier and for SNPN also the
NID within the "servingNetwork" attribute (if the user location information was requested by the PCF but it is not
provided to the SMF) and the timezone information within the "ueTimeZone" attribute (if requested by the PCF and
available).
This shall be done whenever one of these conditions applies:
- The SMF is requested by the RAN to initiate the deactivation of a QoS flow.
- PCC rule(s) are removed/deactivated by the SMF without PCF request (e.g. due to unsuccessful reservation of
resources to satisfy the QoS flow binding).
NOTE: The SMF will not initiate the deactivation of the QoS flow upon reception of the UE-initiated resource
modification procedure indicating packet filter deletion. If all the PCC rules associated to a QoS flow
have been deleted as a consequence of the PCF interaction, the SMF will initiate the QoS flow
termination procedure towards the RAN.
Signalling flows for the QoS flow termination and details of the binding mechanism are presented in
3GPP TS 29.513 [7].

If the SMF is informed that the 3GPP PS Data Off status of the UE changes, the SMF shall provide the PS_DA_OFF
value within the "repPolicyCtrlReqTriggers" attribute and the "3gppPsDataOffStatus" attribute set to the value indicated
by the UE within "SmPolicyUpdateContextData" and send the HTTP POST message as defined in subclause 4.2.4.2 to
the PCF.
Upon receipt of an HTTP POST message with the "repPolicyCtrlReqTriggers" attribute with the value PS_DA_OFF or
the AC_TY_CH the PCF shall determine whether the 3GPP PS Data Off handling functionality (as described below)
becomes active or inactive. The 3GPP PS Data Off handling functionality is active if, and only if,
- the latest received "3gppPsDataOffStatus" attribute is set to true, and
NOTE 1: If the PS_DA_OFF policy control request trigger is received, the latest received value is the one received
in the HTTP POST message. Otherwise, it corresponds to the stored value.
- the UE uses the 3GPP access, i.e.:
- for a non MA PDU session, the "accessType" attribute is set to "3GPP_ACCESS"; and
- for a MA PDU session either the "accessType" attribute or the "addAccessInfo"attribute indicate
"3GPP_ACCESS", and the "relAccessInfo" attribute either is not available or does not indicate
"3GPP_ACCESS".
If the PCF determines that the 3GPP PS Data Off handling functionality becomes active, the PCF shall configure the
SMF in such a way that:
- only packets for services belonging to the list of 3GPP PS Data Off Exempt Services are forwarded over the
3GPP access; and
- all other downlink packets and optionally uplink packets are:
- for a non-MA PDU session or a MA PDU session where the non-3GPP access is not available, discarded by
modifying or removing any related dynamic PCC rule(s) or by deactivating any related predefined PCC
rule(s);
- for a MA PDU session where the non-3GPP access is available, forwarded only in the non-3GPP access, if it
is ensured by the policy for ATSSS Control as specified in subclause 4.2.6.2.17.
3GPP
Release 16 49 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE 2: In order for the UPF to prevent the services that do not belong to the list of 3GPP PS Data Off Exempted
Services, if such services are controlled by dynamic PCC rules, PCF can either close gates for the
downlink and optionally the uplink direction via the "flowStatus" attribute in related dynamic PCC rules
or remove those dynamic PCC rules. If the services are controlled by predefined PCC rules, PCF needs to
deactivate those PCC rules. PCC rule(s) with wild-carded service data flow filters can be among the PCC
rules that are modified, removed or disabled in that manner. It can then be necessary that the PCF at the
same time installs or activates PCC rules for data-off exempt services. The network configuration can
ensure that at least one PCC rule is bound to the default QoS flow when Data Off is activated in order to
avoid a deletion of an existing PDU session or in order to not fail a PDU session establishment.
If the PCF determines that the 3GPP PS Data Off handling functionality becomes inactive, the PCF shall perform policy
control decision and perform PCC rule operations to make sure that services are allowed according to the user’s
subscription and operator policy (irrespective of whether they belong to the list of 3GPP PS Data Off Exempt Services).
NOTE 3: The PCF can then open gates via the "flowStatus" attribute for active PCC rules associated to services not
within the list 3GPP PS Data Off Exempt Services. The PCF can also install PCC rules or activate
predefined PCC rules for some services not belonging to the list 3GPP PS Data Off Exempt Services. If
the PCF activates or installs a PCC rule with wildcarded filters, it can remove or de-activate PCC rules for
3GPP PS Data Off Exempt Services that are made redundant by this PCC rule.
4.2.4.9 Request and Report of Access Network Information

If the NetLoc as defined in subclause 5.8 is supported, the PCF may request the SMF to report the access network
information as defined in subclause 4.2.6.5.4.
If the AN_INFO policy control request trigger is set, upon receiving the "lastReqRuleData" attribute with the "reqData"
attribute with the value(s) MS_TIME_ZONE and/or USER_LOC_INFO and the "refPccRuleIds" attribute containing
the PCC rule identifier(s) corresponding to the PCC rule(s) which is being installed, modified or removed together, the
SMF shall apply the Namf_EventExposure service with One-Time Report type as defined in subclause 5.3.1 of
3GPP TS 29.518 [36] if the related information is not available to obtain this information. When the SMF then receives
access network information from the AMF, the SMF shall provide the required access network information to the PCF
by as defined in subclause 4.2.4.1 and set the corresponding attributes as follows:
- If the user location information was requested by the PCF and was provided to the SMF, the SMF shall provide
the user location information within the "userLocationInfo" attribute and the time when it was last known within
"userLocationInfoTime" attribute (if available).
- If the user location information was requested by the PCF and was not provided to the SMF, the SMF shall
provide the serving PLMN identifier and for SNPN also the NID within the "servingNetwork" attribute.
- If the time zone was requested by the PCF, the SMF shall provide it within the "ueTimeZone" attribute.
In addition, the SMF shall provide the AN_INFO policy control request trigger within the "repPolicyCtrlReqTriggers"
attribute.
The SMF shall not report any subsequent access network information updates received from the RAN without any
further provisioning or removal of related PCC rules requesting the access network information unless the associated
QoS flow or PDU session has been released.
4.2.4.10 Request Usage Monitoring Control and Reporting Accumulated Usage

If the UMC as defined in subclause 5.8 is supported, the PCF may provision the usage monitoring control policy to the
SMF as defined in subclause 4.2.6.5.3 to request the usage monitoring control.
When the SMF receives the accumulated usage report from the UPF as defined in subclauses 7.5.5.2, 7.5.7.2 or 7.5.8.3
of 3GPP TS 29.244 [13], the SMF shall send an HTTP POST message as defined in subclause 4.2.4.2 by including one
or more accumulate usage reports within the "accuUsageReports" attribute(s). Each AccuUsageReport data structure
shall contain the accumulated usage within one or two Usage Report information element(s) corresponding to one usage
monitoring control instance as requested by the PCF.
If the monitoring time is provided by the PCF for a usage monitoring control instance and:
3GPP
Release 16 50 3GPP TS 29.512 V16.5.0 (2020-06)
- if the SMF receives only one Usage Report information elements corresponding to the usage monitoring control
instance from the UPF, within the AccuUsageReport data structure, the SMF shall include the accumulated
usage before the monitoring time within the "timeUsage" attribute, "volUsage" attribute, "volUsageUplink"
attribute and/or "volUsageDownlink" attribute if applicable; otherwise,
- if the SMF receives two Usage Report information elements corresponding to the usage monitoring control
instance from the UPF, within the AccuUsageReport data structure, the SMF include the accumulated usage
before the monitoring time within the "timeUsage" attribute, "volUsage" attribute, "volUsageUplink" attribute
and/or "volUsageDownlink" attribute if applicable and the accumulated usage after the monitoring time within
the "nextTimeUsage" attribute, "nextVolUsage" attribute, "nextVolUsageUplink" attribute and/or
"nextVolUsageDownlink" attribute if applicable.
When the PCF receives the accumulated usage in the HTTP POST message, the PCF shall indicate to the SMF if usage
monitoring shall continue for usage monitoring control instance as follows:
- if the PCF wishes to continue monitoring for the usage monitoring control instance and:
- if monitoring shall continue for specific level(s), the PCF shall provide the new thresholds for the level(s) in
the response of HTTP POST message using the same attribute as before (i.e. "volumeThreshold" attribute,
"volumeThresholdUplink" attribute, "volumeThresholdDownlink" attribute and/or "timeThreshold" attribute;
"nextVolThreshold" attribute, "nextVolThresholdUplink" attribute, "nextVolThresholdDownlink" attribute,
and/or "nextTimeThreshold" attribute if the "monitoringTime" attribute is provided within an entry of the
"umDecs" attribute); or
- if the PCF wishes to stop monitoring for specific level(s) the PCF shall not include an updated threshold in
the response of HTTP POST message for the stopped level(s) i.e. the corresponding "volumeThreshold"
attribute, "volumeThresholdUplink" attribute, "volumeThresholdDownlink" attribute, "timeThreshold"
attribute, "nextVolThreshold" attribute, "nextVolThresholdUplink" attribute, "nextVolThresholdDownlink"
attribute, and/or "nextTimeThreshold" attribute shall not be included within an entry of the "umDecs"
attribute.
- otherwise, if the PCF wishes to stop monitoring for the usage monitoring control instance, the PCF shall not
include any thresholds of the usage monitoring control instance in the response of HTTP POST message or
remove the reference of the usage monitoring control instance from the PCC rule or session rule.
If both volume and time thresholds were provided and the threshold for one of the measurements is reached, the SMF
shall report this event to the PCF and the accumulated usage since last report shall be reported for both measurements.
The PCF shall process the usage reports and shall perform the actions as appropriate for each report.
4.2.4.11 Ipv6 Multi-homing support

The SMF may insert an additional PDU Session Anchor to an existing PDU session by using Ipv6 multi-homing
mechanism. In this case, the SMF shall inform the PCF when one or more new Ipv6 prefix is allocated to the new PDU
Session Anchor as defined in subclause 4.2.4.2. The SMF shall, within the SmPolicyUpdateContextData data structure,
include the "UE_IP_CH" within the "repPolicyCtrlReqTrigger" attribute and include the new Ipv6 prefix within the
"ipv6AddressPrefix" attribute or multiple new Ipv6 prefixes within the "addIpv6AddrPrefixes" attribute, if the
"MultiIpv6AddrPrefix" feature is supported.
When the PCF receives the request from the SMF indicating the addition of one or more new Ipv6 prefixes, the PCF
shall determine the impacted PCC rules and/or session rules associated with each new Ipv6 prefix and provision them to
the SMF as defined in subclauses 5.6.2.6 and 5.6.2.7. The SMF shall derive the appropriate policies based on the
policies provisioned by the PCF and provision them to the appropriate UPF, if applicable, access network, if applicable,
and UE, if applicable. The PCF shall additionally consider the new Ipv6 prefix, or the multiple new Ipv6 prefixes if the
"MultiIpv6AddrPrefix" feature is supported, during subsequent PCC rules and/or session rules updates.
When the SMF removes a PDU Session anchor from the Multi-homing PDU session, the SMF shall inform the PCF of
the released Ipv6 prefix related to the PDU Session anchor as defined in subclause 4.2.5.2. The SMF shall, within the
SmPolicyUpdateContextData data structure, include the "UE_IP_CH" within the "repPolicyConReqTrigger" attribute
and include the released Ipv6 prefix within the "relIpv6AddressPrefix" attribute or multiple released UE Ipv6 prefixes
within the "addRelIpv6AddrPrefixes" attribute, if the "MultiIpv6AddrPrefix feature" is supported.
When the PCF receives the request from the SMF indicating the release of one or more Ipv6 prefixes, the PCF shall
determine the previously provisioned PCC rules and/or session rules associated with each released Ipv6 prefix and shall
3GPP
Release 16 51 3GPP TS 29.512 V16.5.0 (2020-06)
remove and/or update them from the SMF as applicable. The PCF shall remove the released Ipv6 prefix, or the multiple
released Ipv6 prefixes if the "MultiIpv6AddrPrefix" is supported.
4.2.4.12 Request and report for the result of PCC rule removal
If the RAN-NAS-Cause feature is supported, the PCF may request the SMF to inform it of the result of the PCC rule
removal when the PCF removes the PCC rule as defined in subclause 4.2.6.5.2.
When the SMF receives the request, the SMF shall maintain locally the removed PCC rules until it receives of the
resource release outcome from the network.
The SMF shall notify the PCF by include the "RES_RELEASE" within the "repPolicyCtrlReqTrigger" attribute and the
affected rules indicated within one instance of the "ruleReports" attribute with the "ruleStatus" attribute set to the value
INACTIVE.
If the QoS flow is terminated as a consequence of the removal of one or more PCC rules, the SMF shall inform the PCF
about the completion of the QoS flow procedure related to the removal of PCC rules that indicated resource release
notification by including the RequestedRuleData instance containing the "reqData" attribute with the RES_RELEASE
referring to the PCC rule. If the SMF received from the access network some RAN/NAS release cause(s), the SMF shall
also provide the received cause(s) in the "ruleReports" attribute. The SMF shall also provide the available access
network information within the "userLocationInfo" attribute (if available), "userLocationInfoTime" attribute (if
available) and "ueTimezone" attribute (if available).
4.2.4.13 Access Network Charging Identifier request and report

If the "PolicyCtrlReqTriggers" attribute with the value "AN_CH_COR" has been provided to the SMF, the SMF shall
notify of the PCF the Access Network Charging Identifier(s) that the SMF has assigned for the dynamic PCC Rules
which referred from the RequestedRuleData data structure containing the CH_ID within the "reqData" attribute by
including an "accNetChIds" attribute within the SmPolicyUpdateContextData data structure in the HTTP POST
message. If the SMF assigns a Access Network Charging Identifier to the whole PDU session, the SMF shall include
one AccNetChId instance within the "accNetChIds" attribute and include the Access Network Charging Identifier
within the "accNetChaIdValue" attribute and the "sessionChScope" attribute set to true; otherwise, within each
AccNetChId instance, the PCF shall include Access Network Charging Identifier within the "accNetChaIdValue"
attribute and all the PCC rule identifier(s) associated to the provided Access Network Charging Identifier within the
"refPccRuleIds" attribute.
The PCF may request the SMF to provide the Access Network Charging Identifier associated to the new dynamic PCC
rules as defined in subclause 4.2.6.5.1 in the response message.
4.2.4.14 Request and report for the successful resource allocation notification
If the "PolicyCtrlReqTriggers" attribute with the value "SUCC_RES_ALLO" has been provided to the SMF, the SMF
shall notify of the PCF the resources associated to the PCC rules which referred from the RequestedRuleData data
structure containing the "SUCC_RES_ALLO" within the "reqData" attribute are successfully allocated. When the SMF
received successful resource allocation response from the access network, the SMF shall within the
SmPolicyUpdateContextData data structure include the "SUCC_RES_ALLO" within the "repPolicyCtrlReqTriggers"
attribute and "ruleReports" attribute. Within the RuleReport instance, the SMF shall include the corresponding PCC rule
identifier(s) within the "pccRuleIds" attribute and the "ruleStatus" attribute set to value "ACTIVE".
instance, and the resource allocation was successful for this PCC rule, the SMF shall include the rule content version
within the "contVers" attribute in the corresponding RuleReport instance.
4.2.4.15 PCC Rule Error Report

If the installation/activation of one or more PCC rules fails using the procedure as defined in subclause 4.2.2.1 or
4.2.4.1 or the PCF installed, activated or modified one or more PCC rules as defined in subclause 4.2.3.1 but resource
allocation for the PCC Rule was unsuccessful, the SMF shall include the "ruleReports" attribute for the affected PCC
rules to report the failure within the SmPolicyUpdateContextData data structure. Within each RuleReport instance, the
3GPP
Release 16 52 3GPP TS 29.512 V16.5.0 (2020-06)
SMF shall identify the failed PCC rule(s) by including the affected PCC rules within the "pccRuleIds" attribute(s),
identify the failed reason code by including a "failureCode" attribute, and shall include rule status within the
"ruleStatus" attribute with the value as described below.
If the installation/activation of one or more new PCC rules (i.e., rules which were not previously successfully installed)
fails, the SMF shall set the "ruleStatus" to INACTIVE.
The removal of a PCC rule shall not fail, even if the PDU session procedures with the UE fail. The SMF shall retain
If the modification of a currently active PCC rule, the SMF shall retain the existing PCC rule as active without any
modification unless the reason for the failure has an impact also on the existing PCC rule. The SMF shall report the
modification failure to the PCF.
If a PCC rule was successfully installed/activated, but can no longer be enforced by the SMF, the SMF shall set the
"ruleStatus" attribute to INACTIVE.
NOTE: When the PCF receives "ruleStatus" set to INACTIVE, the PCF does not need request the SMF to remove
the inactive PCC rule.
Depending on the value of the "failureCode" attribute, the PCF may decide whether retaining of the old PCC rule, re-
installation, modification, removal of the PCC rule or any other action applies.
If the RAN-NAS-Cause feature is supported and as part of any of the procedures described in this subclause the SMF
receives from the access network some RAN/NAS release cause(s) or untrusted WLAN release cause(s), the SMF shall
also provide the received cause(s) in the RuleReport instance. If RAN-NAS-Cause feature is supported the SMF shall
provide the available access network information within the "userLocationInfo" attribute (if available),
"userLocationInfoTime" attribute (if available) and "ueTimezone" attribute (if available).
instance, and the resource allocation was unsuccessful as for any of the procedures described in this subclause the SMF
shall include the rule content version within the "contVers" attribute for the corresponding RuleReport instance.
4.2.4.16 Presence Reporting Area Information Report

If the PRA feature as defined in subclause 5.8 is support and when the SMF receives the presence reporting area
information from the serving node as defined in 3GPP TS 29.518 [36] indicating that the UE is inside or outside of one
or more presence reporting areas or any of the presence reporting areas is set to inactive, the SMF shall check if the
reported presence reported area identifier corresponds to a presence reporting area that is relevant for the PCF. In that
case, the SMF shall within the SmPolicyUpdateContextData data structure include the "PRA_CH" within the
"repPolicyCtrlReqTriggers" attribute and one or more Presence Reporting Area Information Report within the
"repPraInfos" attribute. For each PresenceInfo data structure, the SMF shall also include the presence reporting area
status within the "presenceState" attribute and the presence reporting area identifier within the "praId" attribute for each
of the presence reporting areas reported by the serving node.
If the SMF receives additional presence reporting area information together with the PRA Identifier as described in
3GPP TS 29.502 [22], the SMF shall only provide the PCF with the presence reporting area information corresponding
to the additional PRA information.
NOTE 1: The SMF will receive additional presence reporting area information when the UE enters or leaves one or
more presence reporting areas related to a PRA set. In that case, the additional presence reporting area
information corresponds to the actual individual presence reporting area. The received presence reporting
area identifier corresponds to the PRA set id and is used to identify the requester (PCF or CHF) of the
notification information.
NOTE 2: The PCF can acquire the necessary data for presence reporting from the UDR.
NOTE 3: Homogeneous support of Presence Area reporting in a network is assumed.
NOTE 4: The serving node can activate the reporting for the PRAs which are inactive as described in the
3GPP TS 23.501 [2].
3GPP
Release 16 53 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.4.17 UE initiates a resource modification support

In the case that the UE initiates a resource modification procedure as defined in subclause 6.4.2.2 of
3GPP 3GPP TS 24.501 [20], the SMF shall within the SmPolicyUpdateContextData data structure include the
"RES_MO_RE" within the "repPolicyCtrlReqTriggers" attribute and shall include the UE request of specific QoS
handling for selected SDF within the "ueInitResReq" attribute. Within the UeInitiatedResourceRequest data structure,
the SMF shall include the "ruleOp" attribute, "packetFiltInfo" attribute and "reqQos" attribute if applicable as follows:
- When the UE requests to "Create new QoS rule", the SMF shall include the "ruleOp" attribute set to
"CREATE_PCC_RULE", the "packFiltInfo" attribute and "reqQos" attribute containing the requested QoS for
the new PCC rule. Each PacketFilterInfo instance shall contain one packet filters requested for creating the new
QoS rule. If the PCF authorizes the request, the PCF shall create a new PCC rule by including the new packet
filters within the service data flow template of the PCC rule. When the SMF received the PCC rule, the SMF
shall derive the QoS rule based on the PCC rule, assign a new QoS rule identifier within the PDU session for the
QoS rule. The SMF shall keep the mapping between the PCC rule identifier and the QoS rule identifier.
- When the UE requests to "Modify existing QoS rule and add packet filters" for the QoS rule created as a result of
the UE-initiated resource modification, SMF shall include the "ruleOp" attribute set to
"MODIFY_PCC_RULE_AND_ADD_PACKET_FILTERS", the "pccRuleId" attribute including the PCC rule
identifier corresponding the QoS rule identifier and the "packFiltInfo" attribute. Each PacketFilterInfo instance
shall contain one packet filters requested for addition to this QoS Rule. If the UE request includes the modified
QoS information the SMF shall also include the "reqQos" attribute to indicate the updated QoS for the affected
PCC rule(s). If the PCF authorizes the request, the PCF shall update the PCC rule by adding the new packet
filters to the service data flow template of the PCC rule.
- When the UE requests to "Modify existing QoS rule and replace all packet filters" for the QoS rule created as a
result of the UE-initiated resource modification, SMF shall include the "ruleOp" attribute set to
"MODIFY_PCC_RULE_AND_REPLACE_PACKET_FILTERS", the "pccRuleId" attribute including the PCC
rule identifier corresponding the QoS rule identifier and the "packFiltInfo" attribute. Each PacketFilterInfo
instance shall contain one packet filters requested for addition to this QoS Rule. If the UE request includes the
modified QoS information the SMF shall also include the "reqQos" attribute to indicate the updated QoS for the
affected PCC rule. If the PCF authorizes the request, the PCF shall update PCC rule by replacing the all existing
packet filters within the service data flow template of the PCC rule with the new packet filter(s).
- When the UE requests to "Modify existing QoS rule and delete packet filters" for the QoS rule created as a result
of the UE-initiated resource modification, SMF shall include the "ruleOp" attribute set to
"MODIFY_PCC_RULE_AND_DELETE_PACKET_FILTERS", the "pccRuleId" attribute including the PCC
rule identifier corresponding the QoS rule identifier and the "packFiltInfo" attribute. Each PacketFilterInfo
instance shall within the "packFiltId" attribute include the removed packet filter identifier assigned by the PCF
corresponding to the packet filter identifier received from the UE. If the UE request includes modified QoS
information the SMF shall also include the "reqQos" attribute to indicate the updated QoS for the affected PCC
rule(s). If the PCF authorizes the request, the PCF shall update PCC rule by removing the corresponding packet
filters from the service data flow template of the PCC rule.
- When the UE requests to "Modify existing QoS rule without modifying packet filters" for the QoS rule created
as a result of the UE-initiated resource modification, SMF shall include the "ruleOp" attribute set to
"MODIFY_PCC_RULE_WITHOUT_MODIFY_PACKET_FILTERS", the "pccRuleId" attribute including the
PCC rule identifier corresponding the QoS rule identifier, the "packFiltInfo" attribute and the modified QoS
information within the "reqQos" attribute. The "packFiltInfo" attribute shall include one PacketFilterInfo
instance which includes any packet filter identifier assigned by the PCF for the PCC rule within the "packFiltId"
attribute.
- When the UE requests to "Delete existing QoS rule" the SMF shall include the "ruleOp" attribute set to
"DELETION_PCC_RULE" for the QoS rule created as a result of the UE-initiated resource modification, the
"pccRuleId" attribute including the PCC rule identifier corresponding the QoS rule identifier and the
"packFiltInfo" attribute. The "packFiltInfo" attribute shall include one PacketFilterInfo instance which includes
any packet filter identifier assigned by the PCF for the PCC rule within the "packFiltId" attribute. The PCF shall
remove the PCC rule when the PCF receives the request according to the PCC rule identifier.
The SMF shall calculate the requested GBR, for a GBR 5QI, as the sum of the previously authorized GBR for the
affected PCC rule, corresponding to the QoS rule, adjusted with the difference between the requested GBR for the QoS
flow and previously negotiated GBR for the QoS flow. For the UE request to create a new QoS Rule, the GBR as
requested by the UE for the QoS rule shall be used.
3GPP
Release 16 54 3GPP TS 29.512 V16.5.0 (2020-06)
If the request covers all the PCC rules with a QoS flow binding to the same QoS flow, then the SMF may request a
change to the 5QI for existing PCC rules.
For the purpose of creating or modifying a QoS rule with adding, replacing and modifying packet filter, within the
UeInitiatedResourceRequest instance, the SMF shall include the precedence information of the QoS rule within the
"precedence" attribute, and within each PacketFilterInfo instance, the SMF shall include the "packFiltCont" attribute,
"tosTrafficClass" attribute, "spi" attribute, "flowLabel" attribute and "flowDirection" attribute set to the value(s)
describing the packet filter provided by the UE.
NOTE: The UE signalling with the network is governed by the applicable NAS signalling TS. The NAS
3GPP TS for a specific access may restrict the UE possibilities to make requests compared to what is
stated above.
If the PCF authorizes the request from the UE, the PCF shall construct a PCC rule(s) based on the
UeInitiatedResourceRequest data structure. For the request to add the filter(s), the PCF shall within the
FlowInformation data structure include the assigned packet filter identifier within the "packFiltId" attribute. When the
SMF derives the QoS based on the PCC rule, the SMF shall assign a new packet filter identifier for each added packet
filter within the QoS rule and keep the mapping between the packet filter identifier for the packet filter within the PCC
rule and QoS rule.
The PCF shall perform the QoS authorization for the new created or modified PCC rules if requested by the UE as
If the PCF detects that the packet filters in the request for new PCC rules received from the SMF is covered by the
packet filters of outstanding PCC rules that the PCF is provisioning to the SMF, the PCF may reject the request and
indicate the cause for the rejection including the "cause" attribute of the ProblemDetails data structure set to
"ERROR_CONFLICTING_REQUEST" in an HTTP "403 Forbidden" response message. If the SMF receives a
response message with this code, the SMF shall reject the PDU session modification that initiated the HTTP request.
If the PCF does not accept one or more of the traffic mapping filters provided by the SMF in an HTTP Request (e.g.
because the PCF does not allow the UE to request enhanced QoS for services not known to the PCF), the PCF shall
reject the request and indicate the cause for the rejection including the "cause" attribute of the ProblemDetails data
structure set to "ERROR_TRAFFIC_MAPPING_INFO_REJECTED" in an HTTP "403 Forbidden" response message.
If the SMF receives an HTTP response with this code, the SMF shall reject the PDU session modification that initiated
the HTTP request.
The PCF shall not combine a rejection with provisioning of PCC rule operations in the same HTTP response.
4.2.4.18 Trace Control

When there is the requirement to activate tracing the SMF may provide trace control parameters to the PCF via the
Npcf_SMPolicyControl_Update service operation. The update service operation may also indicate the deactivation of
the trace session to the PCF.
4.2.4.19 Negotiation of the QoS flow for IMS signalling

When UE initiates a resource modification request, if the SMF includes the "qosFlowUsage" attribute containing
"IMS_SIG" within SmPolicyUpdateContextData data structure and the PCF accepts that a QoS flow dedicated to IMS
signalling shall be used, the PCF shall return the "qosFlowUsage" containing "IMS_SIG" value within the
SmPolicyDecision data structure. The provided PCC rules shall have the 5QI applicable for IMS signalling.
4.2.4.20 Notification about Service Data Flow QoS target enforcement

When the SMF gets the knowledge that for one or more QoS Flows:
- the GBR QoS targets cannot be guaranteed; or
- the GBR QoS targets can be guaranteed again;
the SMF shall inform the PCF that the GBR QoS targets cannot be guaranteed or can be guaranteed again for the PCC
rules bound to the QoS flows.
3GPP
Release 16 55 3GPP TS 29.512 V16.5.0 (2020-06)
The SMF gets the knowledge that the GBR QoS targets cannot be guaranteed or can be guaranteed again for the QoS
flow(s) as follows:
- upon receiving a notification from the NG-RAN that the GFBR can no longer be guaranteed or can be
guaranteed again as defined subclause 5.2.2.3.1 of 3GPP TS 29.502 [22]; or
- during a handover, a QoS Flow which is listed as transferred QoS Flow received from the AMF as defined
subclause 5.2.2.3.1 of 3GPP TS 29.502 [22] can be interpreted as a notification that GFBR can be guaranteed
again if the SMF has received a notification from the source NG-RAN that the GFBR can no longer be
guaranteed but does not receive an explicit notification that the GFBR can no longer be guaranteed for that QoS
Flow from the Target NG-RAN within a configured time as previous bullet.
The SMF shall send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including
the "QOS_NOTIF" within "repPolicyCtrlReqTriggers" attribute and the "qncReports" attribute. In each
QosNotificationControlInfo data structure, the SMF shall include the indication that the GBR QoS targets cannot be
guaranteed or the GBR QoS targets can be guaranteed again within the "notifType" attribute and affected PCC rule
identifiers within the "refPccRuleIds" attribute. If the "AuthorizationWithRequiredQoS" feature as defined in
subclause 5.8 is supported and if the SMF additionally receives the reference to the matching Alternative QoS Profile
which the NG-RAN can guarantee when the NG-RAN indicates the GBR QoS targets cannot be guaranteed, the SMF
shall include the reference to the QosData data structure for the Alternative QoS parameter set corresponding to the
reference to the matching alternative QoS profile within the "altQosParamId" attribute.
If the affected PCC rule was provisioned with a content version, the SMF shall include the "contVers" attribute defined
in the QosNotificationControlInfo data structure for those corresponding PCC rules. The SMF may include more than
one content version in the "contVers" attribute for the same PCC rule within the corresponding
QosNotificationControlInfo instance included in the "qncReports" attribute (e.g. the SMF has combined multiple PCC
rule versions enforcement into one QoS flow operation).
When the PCF receives the HTTP POST request, it shall acknowledge the request by sending a "200 OK" response to
the SMF and then notify the AF as defined in 3GPP TS 29.514 [17], subclause 4.2.5.4.
4.2.4.21 Session Rule Error Report

If the "SessionRuleErrorHandling" feature is supported and if the installation/activation of one or more session rules
fails using the procedure as defined in subclauses 4.2.2.1 or 4.2.4.1 or the PCF installed, activated or modified one or
more session rules as defined in subclause 4.2.3.1 but enforcement of the session Rule was unsuccessful (e.g. session-
AMBR is rejected by the AMF in the roaming scenario, the SMF shall include the "sessRuleReports" attribute for the
affected session rules to report the failure within the SmPolicyUpdateContextData data structure. Within each
SessionRuleReport instance, the SMF shall identify the failed session rule(s) by including the affected session rules
within the "ruleIds" attribute(s), identify the failed reason code by including a "sessRuleFailureCode" attribute, and
shall include rule status within the "ruleStatus" attribute with the value as described below.
If the installation/activation of one or more new session rules (i.e., rules which were not previously successfully
installed) fails, the SMF shall set the "ruleStatus" to INACTIVE.
The removal of a session rule shall not fail, even if the PDU session procedures with the UE fail. The SMF shall retain
If the modification of a currently active session rule, the SMF shall retain the existing session rule as active without any
modification unless the reason for the failure has an impact also on the existing session rule. The SMF shall report the
modification failure to the PCF.
If a session rule was successfully installed/activated, but can no longer be enforced by the SMF, the SMF shall set the
"ruleStatus" attribute to INACTIVE.
NOTE: When the PCF receives "ruleStatus" set to INACTIVE, the PCF does not need request the SMF to remove
the inactive session rule.
Depending on the value of the "sessRuleFailureCode" attribute, the PCF may decide whether retaining of the old
session rule, re-installation, modification, removal of the session rule or any other action applies.
3GPP
Release 16 56 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.4.22 Request the termination of SM Policy association

If "RespBasedSessionRel" feature is supported, PCF may request the PDU session termination upon receiving a POST
message from the SMF (e.g. when usage quota reached). In this case, the PCF shall include the "relCause" attribute
within the SmPolicyDecision data structure of the response to the POST message.
After the receipt of a successful HTTP POST response from the PCF containing the "relCause" attribute within the
SmPolicyDecision data structure, the SMF shall invoke the Npcf_SMPolicyControl_Delete Service Operation defined
in subclause 4.2.5 to terminate the policy association and initiate the procedure to terminate the PDU session as defined
in 3GPP TS 29.502 [22].
4.2.4.23 Reporting of TSN information

If the feature "TimeSensitiveNetworking" is supported and the "TSN_BRIDGE_INFO" policy control request trigger is
provisioned in the SMF, when new 5GS Bridge information is available the SMF requests to update the SM Policy
Association and provides to the PCF information on the conditions that have been met.
The Policy Control Request Trigger condition "TSN_BRIDGE_INFO" is met when:
a. the SMF detects new 5GS Bridge ports which supports exchange of Ethernet Port Management Information
Containers. The SMF shall send to the PCF, if changed, and if available:
- the one or more NW-TT port numbers allocated by the UPF encoded within the "nwttPortNums" attribute;
- the DS-TT port number encoded in the "dsttPortNum" attribute allocated by the UPF;
- the bridge ID received from the UPF encoded in the "bridgeId" attribute;
- the MAC address of the DS-TT received from the UE encoded in the "dsttAddr" attribute; and
- the UE-DS-TT residence time if received from the UE encoded in the "dsttResidTime" attribute,
within the SmPolicyUpdateContextData structure encoded in the "tsnBridgeInfo" attribute of the TsnBridgeInfo
data type; and/or
b. when the SMF receives a BMIC from the Bridge functionality of the UPF/NW-TT and/or a PMIC from the DS-
TT port and/or one or more PMIC(s) in the corresponding one or more NW-TT ports. The SMF shall
transparently forward to the PCF the BMIC encoded within the "tsnBridgeManCont" attribute and/or the DS-TT
PMIC encoded within the "tsnPortManContDstt" attribute and/or the one or more NW-TT PMIC(s) encoded
within the "tsnPortManContNwtts" attribute within the SmPolicyUpdateContextData structure.
4.2.4.24 Notification about Service Data Flow QoS Monitoring

When the SMF gets the information about any one of the following items for one or more SDFs from the UPF:
- uplink packet delay(s); or
- downlink packet delay(s); or
- round trip delay(s);
then SMF shall inform the PCF for the impacted PCC rules.
The SMF shall send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including
the "QOS_MONITORING" within "repPolicyCtrlReqTriggers" attribute and the "qosMonReports" attribute. In each
QosMonitoringReport data structure, the PCF shall include:
- one or two uplink packet delays within the "ulDelays" attribute; or
- one or two downlink packet delays within the "dlDelays" attribute; or
- one or two round trip packet delays within the "rtDelays" attribute; and
- affected PCC rule identifiers within the "refPccRuleIds" attribute.
3GPP
Release 16 57 3GPP TS 29.512 V16.5.0 (2020-06)

If "ATSSS" feature defined in subclause 5.8 is supported and the PCF has previously provisioned the AC_TY_CH
policy control request trigger, when the UE requests to:
- add an access to an already established MA PDU session (i.e. registers to another acess), the SMF shall, within
the SmPolicyUpdateContextData data structure, include the "AC_TY_CH" within the
"repPolicyCtrlReqTrigger" attribute and include the additional Access type and the additional RAT type if
available within the "addAccessInfo" attribute.
- release an access from an already established MA PDU session (i.e. deregisters from one access but remains
registered on the other access), the SMF shall, within the SmPolicyUpdateContextData data structure, include
the "AC_TY_CH" within the "repPolicyCtrlReqTrigger" attribute and include the released access type and the
released RAT type if available within the "relAccessInfo" attribute.
When the PCF receives the request from the SMF indicating the addition of Access Type or removal of Access Type,
the PCF may provide PCC rules and/or session rules for the MA PDU session as defined in subclause 4.2.6.2.17 and
subclause 4.2.6.3.4.
4.2.4.26 Policy decision and condition data error handling

If the "PolicyDecisionErrorHandling" feature is supported and one or more policy decisions and/or condition datas
which are not referred by any PCC rules or session rule is provisioned using the procedure as defined in
subclauses 4.2.2.1, 4.2.3.1 or 4.2.4.1 but the storage was unsuccessful (e.g. the policy decision could not be successfully
stored due to a limitation of resources at the SMF), the SMF shall include the "policyDecFailureReports" attribute to
indicate the type(s) of the failed policy decisions and/or condition data within the SmPolicyUpdateContextData data
structure.When the PCF receives the above reports, the PCF shall consider all the instances of the policy decsions
and/or condition data which are not referred by any PCC rule and/or session stored at the SMF and indicated by the
PolicyDecisionFailureCode data type are removed from the SMF.
4.2.4.27 Policy Control for DDN Failure Events

If the feature "DDNEventPolicyControl" is supported, and if the PCF has previously provisioned "DDN_FAILURE"
policy control request trigger, the SMF shall send the PCC rule request when it receives an event subscription for DDN
Failure event including the traffic descriptors. The SMF shall send an HTTP POST request to the PCF with an
SmPolicyUpdateContextData data structure, including the "DDN_FAILURE" within "repPolicyCtrlReqTriggers"
attribute and include the traffic descriptor in the "trafficDescriptor" attribute within the SmPolicyUpdateContextData
structure for policy evaluation.
If the feature "DDNEventPolicyControl" is supported, and if the PCF has previously provisioned
"DDN_DELIVERY_STATUS" policy control request trigger, the SMF shall send the PCC rule request when it receives
an event subscription for DDN Delievery Status event including the traffic descriptors. The SMF shall send an HTTP
POST request to the PCF with an SmPolicyUpdateContextData data structure, including the
"DDN_DELIVERY_STATUS" within "repPolicyCtrlReqTriggers" attribute and include the traffic descriptor in the
"trafficDescriptor" attribute within the SmPolicyUpdateContextData structure for policy evaluation.
For both of the above cases, upon reception of the HTTP POST message, the PCF shall apply policies related to the
traffic descriptors included in the HTTP POST message to derive the priority of the PCC rules.
4.2.5 Npcf_SMPolicyControl_Delete Service Operation
4.2.5.1 General
The delete service operation provides means for the NF service consumer to delete the context of PDU Session related
information.
The following procedures using the Npcf_SMPolicyControl_Delete service operation are supported:
- Deletion of the policy context associated with a PDU session.
- Report Accumulated Usage.
3GPP
Release 16 58 3GPP TS 29.512 V16.5.0 (2020-06)
- Report Access Network Information.
4.2.5.2 SM Policy Association termination
SMF PCF
1. POST .../sm-policies/{smPolicyId}/delete
2. 204 No Content
Figure 4.2.5.2-1: SM Policy Association termination
When an individual resource of the SM Policy Association shall be deleted the SMF shall invoke the
Npcf_SMPolicyControl_DELETE service operation to the PCF using an HTTP POST request, as shown in
figure 4.2.5.2-1, step 1.
The SMF shall set the request URI to "{apiRoot}/npcf-smpolicycontrol/v1/sm-policies/{smPolicyId}/delete". The

{smPolicyId} in the URI identifies the "Individual SM Policy" to be deleted.
The SMF delete request shall (if available) contain SM Policy Association related information within the
SmPolicyDeleteData data structure in the body:
- accumulated usage within the "accuUsageReport" attribute as defined in subclause 4.2.5.3;
- the user location information within the "userLocationInfo" attribute, the information on when the UE was last
known to be in that location within the "userLocationInfoTime" attribute, the PLMN identifier and for SNPN
also the NID within the "servingNetwork" attribute, the timezone information within the "ueTimeZone" attribute
and RAN cause and/or the NAS cause within the "ranNasRelCauses" attribute as defined in subclause 4.2.5.4;
- the "PS_TO_CS_HO" value within the "pduSessRelCause" attribute, if the PDU session is released due to PS to
CS handover and the "PDUSessionRelCause" feature defined in subclause 5.8 is supported.
When the PCF receives the HTTP POST request from the SMF, the PCF shall acknowledge the request by sending an
HTTP response message with the corresponding status code. The PCF acknowledged the delete request by sending a
"204 No Content" response to the SMF, as shown in figure 4.2.5.2-1, step 2. Further, the PCF shall remove the
individual resources linked to the delete request.
4.2.5.3 Report Accumulated Usage

If the UMC feature is supported, when the SMF receives the accumulated usage report from the UPF as defined in
subclause 7.5.7.2 of 3GPP TS 29.244 [13], within the SmPolicyDeleteData data structure the SMF shall include one or
more accumulated usage reports within the "accuUsageReports" attribute.
If all PDU sessions of a user to the same DNN are terminated, the PCF may store the remaining allowed usage, i.e. the
information about the remaining overall amount of resources, in the UDR as defined in 3GPP TS 29.519 [15].
4.2.5.4 Report Access Network Information

If the RAN-NAS-Cause feature is supported or the NetLoc feature is supported, within the SmPolicyDeleteData data
structure the SMF shall provide the available access network information within the "userLocationInfo" attribute (if
available), the information on when the UE was last known to be in that location within "userLocationInfoTime"
attribute (if available), "ueTimezone" attribute (if available). Additional, for NetLoc feature, if the user location
information is not available, the SMF shall include the PLMN identifier and for SNPN also the NID within the
"servingNetwork" attribute; for RAN-NAS-Cause feature, if the SMF received from the access network the RAN cause
and/or the NAS cause due to PDU session termination, the SMF shall provide the received cause(s) in the
"ranNasRelCauses" attribute.
3GPP
Release 16 59 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.6 Provisioning and Enforcement of Policy Decisions
4.2.6.1 General
Policy Decisions are provided from the PCF to the NF service consumer (SMF) as part of the following service
operations:
- the Npcf_SMPolicyControl_Create Service Operation described in subclause 4.2.2;
- the SM Policy Association Notification request as part of the Npcf_SMPolicyControl_UpdateNotify Service

Operation as described in subclause 4.2.3.2; and
- the Npcf_SMPolicyControl_Update service operation as described in subclause 4.2.4
Policy decisions shall be encoded within the SmPolicyDecision data structure defined in subclause 5.6.2.4
Policy decisions may include:
- Session Rules as described in subclause 4.1.4.3 encoded within the "sessRules" attribute;
- PCC Rules as described in subclause 4.1.4.2 encoded within the "pccRules" attribute;
- QoS decisions as described in subclause 4.1.4.4.3 that can be referenced from PCC rules and session rules
encoded within the "qosDecs" attribute;
- charging decisions as described in subclause 4.1.4.4.4 that can be referenced from PCC rules encoded within the
"chgDecs" attribute;
- Traffic control decisions as described in subclause 4.1.4.4.2 that can be referenced from PCC rules encoded
within the "traffContDecs" attribute;
- Usage monitoring control decisions as described in subclause 4.1.4.4.5 that can be referenced from PCC rules
and session rules encoded within the "umDecs" attribute;
- Conditions that can be referenced from PCC rules and session rules encoded within the "conds" attribute;
- A reflective QoS timer;
- Policy control request triggers and applicable additional information, e.g., Revalidation Time, PRA information;
- Last requested rule data;
- Last requested usage data;
- Default charging method of the PDU session;
- Charging information;
- P-CSCF Restoration Support Indication;
- IP index information;
- Usage of QoS flow.
For the Npcf_SMPolicyControl_Create Service Operation, the SmPolicyDecision data structure shall contain a full
description of all of policies decisions provided by the PCF for the policy association.
For the Npcf_SMPolicyControl_UpdateNotify service operation for the SM Policy Association Notification request and
for the Npcf_SMPolicyControl_Update service operation, the SmPolicyDecision data structure shall contain a
description of changes of the policies decisions with respect to the last provided previous policy decision for the
corresponding policy association. The default charging method of the PDU session, charging information, Reflective
QoS Timer, P-CSCF Restoration Support Indication and IP index information shall not been updated by the PCF.
If no other rules are defined for specific data types within the SmPolicyDecision data structure, the encoding of changes
of the policies decisions in the SmPolicyDecision data structure shall follow the following principles:
3GPP
Release 16 60 3GPP TS 29.512 V16.5.0 (2020-06)
1) To modify an attribute with a value of type map (e.g. the "sessRules" attribute, the "pccRules" attribute, the
"qosDecs" attribute, the "traffContDecs" attribute, the "umDecs" attribute, and the "conds" attribute) the attribute
shall be provided with a value containing a map with entries according to the following principles:
- A new entry shall be added by supplying a new identifier (e.g. rule / decision identifier) as key and the
corresponding structured data type instance (e.g. PCC rule) with complete contents as value as an entry
within the map.
- An existing entry shall be modified by supplying the existing identifier as key and the corresponding
structured data type instance with the same existing identifier (e.g. set the "qosId" to the same existing QoS
data decision identifier), which shall describe the modifications following bullets 1 to 6, as value as an entry
within the map.
- An existing entry shall be deleted by supplying the existing identifier as key and "NULL" as value as an entry
within the map.
- For an unmodified entry, no entry needs to be provided within the map.
2) To modify an attribute with a structured data type instance as value, the attribute shall be provided with a value
containing a structured data type instance with entries according to bullets 1 to 6.
3) To modify an attribute with another type than map or structured data type as value, the attribute shall be
provided with a complete representation of its value that shall replace the previous value.
4) To create an attribute of any type, the attribute shall be provided with a complete representation of its value.
5) To delete an attribute of any type, the attribute shall be provided with NULL as value.
NOTE 1: Attributes that are allowed to be deleted need to be marked as "nullable" within the OpenAPI file in
Annex A.
6) Attributes that are not added, modified, or deleted do not need to be provided.
NOTE 2: In related data structures no attribute can be marked as mandatory except the attribute for the identifier
(e.g. rule / decision identifier).
The PCF shall not remove a provisioned policy decision data or condition data from the SMF when the reference(s)
from the PCC rule(s) or session rule(s) are still valid. The PCF may keep a policy decision data or condition data valid
when the PCF removes all the PCC(s) or session rule(s) referring to the policy decision data or condition data.
If the installation/activation of one or more new PCC rule(s) or session rule(s) (i.e. rules which were not previously
successfully installed) fails, although the failed PCC rule(s) or session rule(s) is removed, the policy decision data or
condition data which is referred by the failed PCC rule(s) or session rule(s) remains applicable in the SMF until the PCF
removes it.
4.2.6.2 PCC Rules
4.2.6.2.1 Overview
The PCF may perform an operation on a single PCC rule or a group of PCC rules. The impacted rules shall be included
in the "pccRules" map attribute within the SMPolicyDecision data structure with the "pccRuleId" as a key. For
activating the pre-defined PCC rule, or installing or modifying a dynamic PCF-provisioned PCC rule, the corresponding
PccRule data instance shall be provided as the map entry value. For deactivating or removing a PCC rule, the map entry
value shall be set to NULL.
NOTE 1: When deactivating a predefined PCC rule that is activated in more than one QoS flow, the predefined
PCC rule is deactivated simultaneously in all the QoS flow where it was previously activated.
In order to activate a pre-defined PCC rule, the PCF shall within the PccRule instance include the pre-defined PCC rule
identifier within the "pccRuleId" attribute and the "refCondData" attribute if applicable, i.e. the PccRule instance is
empty except for the "pccRuleId" attribute and the "refCondData" if applicable. If the "refCondData" attribute is
applicable, a "conds" attributes containing the corresponding Condition Data referred by the PCC rule shall be included
in the SmPolicyDecision data structure if it has not been provided.
3GPP
Release 16 61 3GPP TS 29.512 V16.5.0 (2020-06)
In order to install a new dynamic PCF-provisioned PCC rule, the PCF shall further set other attributes within the
PccRule data structure as follows:
- it may include the precedence within the "precedence" attribute. Within a PDU session, the PCF shall authorize
different precedence values for the PCC rules whose packet filters contained within the "flowDescription"
attribute or the "ethFlowDescription" attribute include the "packetFilterUsage" attribute set to true;
NOTE 2: The SMF sets the precedence value of the QoS rule to the precedence value of the PCC rule for which the
QoS rule is generated. The UE considers an error when two or more QoS rules associated with a PDU
session have identical precedence values.
- it shall include either the flow information within the "flowInfos" attribute(s) or the application identifier within
the "appId" attribute;
- it shall include one reference to the QoSData data structure within the "refQosData" attribute. In this case, a
"qosDecs" attributes containing the corresponding QoS data policy decisions shall be included in the
SmPolicyDecision data structure if it has not been provided;
- it may include reference(s) to the QoSData structure within the "refAltQosParams" attribute to refer to the
Alternative QoS parameter sets of the service data flow. In this case, a "qosDecs" attributes containing the
corresponding alternative QoS data policy decision(s) shall be included in the SmPolicyDecision data structure if
it has not been provided;
- it shall include one reference to the TrafficControlData data structure within the "refTcData" attribute. In this
case, a "traffContDecs" attribute containing the corresponding Traffic Control data policy decision shall be
included in the SmPolicyDecision data structure if it has not been provided;
- it may include one reference to the ChargingData data structure within the "refChgData" attribute. In this case, a
"chgDecs" attribute containing the corresponding Charging Data policy decisions shall be included in
- it may include one reference to the UsageMonitoringData data structure within the "refUmData" attribute. In this
case, a "umDecs" attribute containing the corresponding Usage Monitoring data policy decision shall be included
in the SmPolicyDecision data structure if it has not been provided;
- it may include one reference to the QosMonitoringData data structure within the "refQoSMon" attribute. In this
case, a "qosMonDecs" attribute containing the corresponding QoS Monitoring data policy decision shall be
included in the SmPolicyDecision data structure if it has not been provided; and
- it may include one reference to the ConditionData data type within the "refCondData" attribute. In this case, a
"conds" attributes containing the corresponding Condition Data shall be included in the SmPolicyDecision data
structure if it has not been provided;
In order to modify an existing dynamic PCF-provisioned PCC rule, the PCF shall further set other attributes within the
PccRule data structure as follows:
- If the PCF needs to modify the attribute(s) within a PCC rule, the PCF shall include the modified attributes(s)
with the new value(s) within the PccRule data instance. Previously supplied attributes not supplied in the
modified PCC rule instance shall remain valid.
- If the PCF only needs to modify the content of referenced policy decision data (e.g. QoSData, ChargingData,
etc.) and/or condition data for one or more PCC rules, the PCF shall, within the SmPolicyDecision data structure,
include the corresponding policy decision data and/or condition data within the corresponding map attributes
(e.g. include the QoS data decision within the "qosDecs" attribute).
In order to modify the content of referenced condition data for one or more existing pre-defined PCC rules, the PCF
shall, within the SmPolicyDecision data structure, include the corresponding condition data within the "conds" attribute.
The PCF may combine multiple of the above PCC rule operations in a single message.
The SMF shall ensure that at least one PCC Rule bound to the default QoS flow is activated for the PDU Session. If the
PCF did not provision any PCC rule, the SMF shall activate at least one pre-defined PCC rule which is not known by
the PCF and bound to the default QoS flow.
3GPP
Release 16 62 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.6.2.2 Gate function

The Gate Function represents a user plane function enabling or disabling the forwarding of data packets belonging to a
service data flow. A gate is described within a PCC rule. If the PCC rule contains the "flowInfos" attribute(s) applicable
for uplink service data flows, it shall describe a gate for the corresponding uplink service data flows. If the PCC rule
contains the "flowInfos" attribute(s) applicable for downlink service data flows, it shall describe a gate for the
corresponding downlink service data flows. If the PCC rule contains the "appId" attribute, it shall describe a gate for the
corresponding detected application traffic. The "flowStatus" attribute within a TrafficControlData data structure which
the PCC rule refers to shall describe if the possible uplink and possible downlink gate is opened or closed.
The commands to open or close the gate shall lead to the enabling or disabling of the passage for corresponding data
packets. If the gate is closed all packets of the related service data flows shall be dropped. If the gate is opened the
packets of the related service data flows are allowed to be forwarded.
4.2.6.2.3 Policy enforcement for authorized QoS per PCC Rule

The PCF can provide the authorized QoS for a PCC rule to the SMF. The Provisioning of authorized QoS per PCC Rule
shall be performed using the PCC rule provisioning procedure as defined in subclause 4.2.6.2.1. For a PCF-provided
PCC rule, the authorized QoS shall be encoded using a QosData data structure. The PCF shall include the reference to
the QosData data structure within the "refQosData" attribute of the PCC rule and a "qosDecs" attribute containing this
QoS data decision within the SmPolicyDecision data structure.
If the authorized QoS is provided for a PCC rule, the SMF shall derive the QoS profile towards the access network if
applicable, the QoS rule towards the UE if applicable, and the QoS information with the PDR(s) towards the UPF.
4.2.6.2.4 Redirect function

The PCF may provide the redirect instruction for one or several dynamic PCC rule to the SMF. The Provisioning shall
be performed using the policy provisioning procedure as defined in subclause 4.2.6.1.
The "traffContDecs" attribute within the SmPolicyDecision is used to provide traffic control decisions. The redirect
instruction shall be encoded using a "redirectInfo" attribute within the corresponding TrafficControlData data structure.
That attribute provides a RedirectInformation data structure with the following components:
- The "redirectEnabled" attribute indicates whether redirect is enabled. It shall be included and set to true when the
redirect instruction is initially provisioned and may be included in subsequent updates of the
RedirectInformation to enable or disable the redirect instruction.
- The redirect address may be provided using the "redirectAddressType" and "redirectServerAddress" attributes or
may be preconfigured in the SMF/UPF. A redirect destination provided within the "redirectServerAddress"
attribute for a dynamic PCC Rule shall override the redirect destination preconfigured in the SMF/UPF.
NOTE: The SMF/UPF uses the preconfigured redirection address only if it can be applied to the application
traffic being detected, e.g. the redirection destination address could be preconfigured on a per application
identifier basis.
If redirect needs to be applied to a dynamic PCC rule, that PCC rule shall reference a traffic control decision with such
redirect instructions. If a dynamic PCC rule includes flow information for UE IPv4 address and IPv6 prefix address(es)
related to the same application identifier and ADCmultiRedirection feature is supported, addRedirectInfo attribute
including more than one RedirectInformation data may be provided simultaneously as the redirect instruction.
If "redirectInfo" attribute is provided for a dynamic PCC rule, the SMF shall instruct the UPF to perform the redirection
as defined in 3GPP TS 29.244 [13].
To disable the redirect function for one or more already installed PCC Rule, the PCF shall:
- update the PCC rule to modify the reference to a new Traffic Control Data decision which does not have the
"redirectInfo"; or
- update the Traffic Control Data decision which the PCC rule refers to with the "redirectEnabled" attribute set to
false if the PCF disables the redirect function for all the PCC rules which refer to this Traffic Control Data
decision.
3GPP
Release 16 63 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.6.2.5 Usage Monitoring Control

Usage monitoring may be performed for service data flows associated with one or more PCC rules.
The provisioning of usage monitoring control per PCC rule shall be performed using the PCC rule provisioning
procedure as defined in subclause 4.2.6.2.1. For a dynamic PCC rule, the reference to the UsageMonitoringData data
structure of the usage monitoring control instance, which is related with the PCC rule, shall be included within the
"refUmData" attribute of the PccRule data structure of the PCC rule(s). For a predefined PCC rule, the reference to a
usage monitoring control instance shall be included in the rule definition at the SMF. Usage monitoring shall be
activated for both service data flows associated with predefined PCC rules and dynamic PCC rules, including rules with
deferred activation and/or deactivation times while those rules are active.
4.2.6.2.6 Traffic Steering Control support

If the TSC feature is supported, the PCF may instruct the SMF to apply a traffic steering control for the purpose of
steering the subscriber's traffic to appropriate operator or 3rd party service functions (e.g. NAT, antimalware, parental
control, DdoS protection) in the N6-LAN or enabling the routing of the user traffic to a local Data Network identified
by the DNAI per AF request.
4.2.6.2.6.1 Steering the traffic in the N6-LAN
This procedure is only applicable in non-roaming and home-routed scenarios.
For the purpose of steering the subscriber's traffic to appropriate operator or 3rd party service functions in the N6-LAN,
the PCF shall include the reference to a Traffic Control Data decision within the PccRule data instance and set other
attribute as follows:
- either include the application to be detected identified by the "appId" attribute or the service data flow to be
detected identified by the "flowInfos" attribute(s) within the PccRule data structure; and
- include a "traffContDecs" attribute containing the corresponding Traffic Control Data decision within the
SmPolicyDecision if it has not been provided yet. In this case, the PCF shall include a traffic steering policy
identifier for downlink identified by the "trafficSteeringPolIdDl" attribute and/or a traffic steering policy
identifier for uplink identified by the "trafficSteeringPolIdUl" attribute directly within the Traffic Control Data
decision.
The PCF may also provision the traffic steering control information by activating the pre-defined PCC rule(s) in the
SMF.
4.2.6.2.6.2 Steering the traffic to a local access of the data network
This procedure is only applicable in non-roaming and visited access scenarios.
The PCF shall determine if the ongoing PDU Session is impacted by the routing of traffic to a local access to a data
network as follows:
- If the AF request includes the individual IP address/ prefix allocated to an UE or the UE MAC address, the PCF
shall store the received traffic routing information and shall perform the session binding as defined in
subclause 6.2 of 3GPP TS 29.513 [7] to determine the impacted PDU session.
- Otherwise, the PCF fetches the traffic routing data information from the UDR as defined in
3GPP TS 29.519 [15] applicable for a UE, any UE or Internal Group Id if received in the SMF request.
Then the PCF authorizes the request for influencing SMF routing decisions. For the impacted PDU Session that
corresponds to the AF request, the PCF shall take into account, if available, the local routing indication stored in the
policy data subscription information in UDR as defined in 3GPP TS 29.519 [15] to determine whether it is allowed to
generate PCC rules with traffic routing information. When allowed, the PCC rules are generated based on the AF
request as follows:
- When the request is for influencing SMF routing decisions, based on the traffic routing information, operator's
policy, etc. and determines the traffic steering policy. The traffic steering policy indicates for each DNAI, a
traffic steering policy identifier configured in SMF and/or if the N6 routing information associated to the
application is explicitly provided by the AF, the N6 routing information (as provided by the AF). The traffic
steering policy identifier is related to the mechanism enabling traffic steering to the DN, the PCF derives it from
3GPP
Release 16 64 3GPP TS 29.512 V16.5.0 (2020-06)
the routing profile Id provided by the AF. The PCF shall within each PccRule data instance include the
information to identify the traffic within the "flowInfos" attribute or "appId" attribute, and within the
TrafficControlData data type which the PCC rule refers to include a list of locations which the traffic shall be
routed to in the "routeToLocs" attribute. Within each RouteToLocation instance, the PCF shall include a DNAI
in the "dnai" attribute to indicate the location of the application towards which the traffic routing is applied, and
a traffic steering policy identifier in the "routeProfId" attribute or the explicit routing information in the
"routeInfo" attribute. If the AF provides both a traffic steering policy identifier and the N6 routing information
for a DNAI, the PCF shall include two RouteToLocation instances with same DNAI within the "dnai" attribute
and include the traffic steering policy identifier within the "routeProfId" attribute in one instance and include the
explicit routing information within the "routeInfo" attribute in the other instance.
NOTE 1: The N6 traffic routing requirements are related to the mechanism enabling traffic steering in the local
access to the DN. The routing profile ID refers to a pre-agreed policy between the AF and the 5GC. This
policy may refer to different steering policy identifier(s) sent to SMF and e.g. based on time of the day
etc.
NOTE 2: Per DNAI, a Traffic steering policy identifier and/or N6 traffic routing information can be provided. If the
pre-configured traffic steering policy (that is referenced by the traffic steering policy identifier) contains
information that is overlapping with the N6 traffic routing information, the N6 traffic routing information
shall take precedence.
NOTE 3: In this release of the specification, either a traffic steering policy identifier for UL or a traffic steering
policy identifier for the DL can be defined per DNAI.
- When the request is for subscribing the UP path change event of the PDU session, the PCF shall include the
information on AF subscription to UP path change event within the PCC rule(s) to request the notification from
the SMF for the AF. In order to do so, the PCF shall within the PccRule data instance(s) include the information
to identify the traffic either within the "flowInfos" attribute or "appId" attribute, and/or within the Traffic Control
Data data decision which the PCC rule refers to include the information on AF subscription to the events within
the "upPathChgEvent" attribute. Within the "upPathChgEvent" attribute, the PCF shall include the
"dnaiChgType" attribute to indicate the type of notification (i.e. early notification, late notification or both), the
notification address within the "notificationUri" attribute, the notification correlation Id within the "notifCorreId"
attribute and if the URLLC feature is supported, may include an indication of AF acknowledgement to be
expected within the "afAckInd" attribute. In order to enable the AF to identify the AF request which the
notification corresponds to when the AF receives the notification from the SMF as defined in subclause 4.2.2.2
of 3GPP TS 29.508 [12], the PCF shall set the values of "notificationUri" attribute and "notifCorreId" attribute
respectively as follows:
- If the PCF fetches the traffic routing data information from the UDR, the PCF shall set the value of
"notificationUri" to the value of the "upPathChgNotifUri" attribute of the TrafficInfluData data structure and
set the value of "notifCorreId" attribute to value of "upPathChgNotifiCorreId" attribute of the
TrafficInfluData data structure as defined in 3GPP TS 29.519 [15].
- If the PCF receives the traffic routing data information from the AF via N5 interface, the PCF shall set the
values of "notificationUri" attribute and "notifCorreId" attribute according to the "upPathChgSub" attribute
within the AfRoutingRequirement data structure as defined in 3GPP TS 29.514 [17].
- If the AF request includes an indication indicating that application relocation is not possible, the PCF shall
within the PccRule data instance(s) include the information to identify the traffic either within the "flowInfos"
attribute or "appId" attribute and the "appReloc" attribute set to true. In this case, the SMF shall ensure that for
the traffic related with an application, no DNAI change takes place once selected for this application;
- If the URLLC feature is supported and the AF request includes an indication indicating that the UE IP address
preservation should be considered, the PCF shall within the PccRule data instance(s) include the indication of
UE IP address preservation within the "addrPreserInd" attribute; and
- If the AF request includes an indication indicating that the PDU session should be correlated by a common
DNAI for a given traffic, the PCF shall within the TrafficControlData data instance provisioned for one or more
PCC rules, include the indication of traffic correlation within the "traffCorreInd" attribute.
The PCF shall provide the PCC rule(s) as defined in subclause 4.2.6.2.1.
If the temporal validity condition is received, the PCF shall evaluate the temporal validity condition of the AF request
and informs the SMF to install or remove the corresponding PCC rules according to the evaluation result. When policies
3GPP
Release 16 65 3GPP TS 29.512 V16.5.0 (2020-06)
specific to the PDU Session and policies general to multiple PDU Sessions exist, the PCF gives precedence to the PDU
Session specific policies over the general policies.
If the spatial validity condition is received, the PCF considers the latest known UE location to determine the PCC rules
provided to the SMF. In order to do that, the PCF shall request the SMF to report the notifications about change of UE
location in an area of interest (i.e. Presence Reporting Area) as defined in subclauses 4.2.2.13 or 4.2.3.19. The
subscribed area of interest may be the same as spatial validity condition, or may be a subset of the spatial validity
condition (e.g. a list of TAs) based on the latest known UE location. When the SMF detects that UE entered the area of
interest subscribed by the PCF, the SMF notifies the PCF and the PCF provides to the SMF the PCC rules described
above. When the SMF becomes aware that the UE left the area subscribed by the PCF, the SMF notifies the PCF and
the PCF may remove or provide updated PCC rules to the SMF.
When the PCC rules are installed, the SMF may, based on local policies, take the information in the PCC rules into
account to:
- if the PDU Session is of IP type and if the indication of UE IP address preservation is included in the PCC rules,
the SMF should preserve the UE IP address and, if necessary, not reselect the related PSA UPF for the traffic
identified in the PCC rule once the PSA UPF is selected; otherwise, the SMF (re)selects UPF(s) as it might be
required for PDU Sessions.
- activate mechanisms for traffic multi-homing or enforcement of an UL Classifier (UL CL).
- inform the AF of the (re)selection of the UP path (change of DNAI).
- if the indication of traffic correlation is included within the "traffCorreInd" attribute in the TrafficControlData
data type referenced by a set of PCC rules, based on SMF implementation and local configuration, the SMF
should select a common DNAI from the list of DNAI included in the "routeToLocs" attribute for the identified
traffic of the PDU session.
4.2.6.2.7 Conditioned PCC rule

The PCF may control at what time the status of a PCC rule changes. In order to provision a PCC rule with conditional
data, the PCF shall provision a PCC rule as defined in subclause 4.2.6.2.1and include within its "refCondData" attribute
the corresponding ConditionData's "condId" attribute value. The PCF shall also ensure that the referenced
ConditionData instance is included in the "conds" map within the SmPolicyDecision data structure following the
procedures defined in subclause 4.2.6.1.
Within the ConditionData instance, the PCF shall include the activation time within the "activationTime" attribute
and/or deactivation time within the "deactivationTime" attribute.
When the SMF receives the PCC rule, the SMF shall act as follows:
1) If "activationTime" attribute is specified only and the time specified in "activationTime" attribute is in the future,
then the SMF shall set the PCC rule inactive and make it active at that time. If time specified in the
"activationTime" attribute is in the past, then the SMF shall immediately set the PCC rule active.
2) If "deactivationTime" attribute is specified only and the time specified in "deactivationTime" attribute is in the
future, then the SMF shall set the PCC rule active and make it inactive at that time. If the time specified in the
"deactivationTime" is in the past, then the SMF shall immediately set the PCC rule inactive.
3) If both "activationTime" attribute and "deactivationTime" attribute are specified, and the time specified in the
"activationTime" occurs before the time specified in the "deactivationTime" attribute, and also when the PCC
rule is provided before or at the time specified in the "deactivationTime", the SMF shall handle the rule as
defined in 1) and then as defined in 2).
4) If both "activationTime" attribute and "deactivationTime" attribute are specified, and the time specified in the
"deactivationTime" attribute occurs before the time specified in the "activationTime", and also when the PCC
rule is provided before or at the time specified in the "activationTime" attribute, the SMF shall handle the rule as
defined in 2) and then as defined in 1).
5) If both the "activationTime" attribute and the "deactivationTime" attribute are specified but time has already
occurred for both, and the time specified in the "activationTime" occurs before the time specified in the
"deactivationTime" attribute, then the SMF shall immediately set the PCC rule inactive.
3GPP
Release 16 66 3GPP TS 29.512 V16.5.0 (2020-06)
6) If both the "activationTime" attribute and the "deactivationTime" attribute are specified but time has passed for
both, and the time specified in "deactivationTime" attribute occurs before the "activationTime" attribute, then the
SMF shall immediately set the PCC rule active.
The PCF may modify a currently installed/activated PCC rule, including setting, modifying or deleting its deferred
activation and/or deactivation time as follows:
1) When modifying a PCC rule by setting the deferred activation time and/or deactivation time, the PCF shall
update the PCC rule by including the corresponding ConditionData's "condId" attribute value within the
"refCondData" attribute and within the SmPolicyDecision data structure include the ConditionData instance
within the "conds" attribute if not provisioned yet.
2) When modifying a PCC rule by modifying the deferred activation time and/or deactivation time:
- the PCF may update the PCC rule by replacing the existing ConditionData instance's "condId" attribute value
within the "refCondData" attribute with a new one and within the SmPolicyDecision data structure include
the new ConditionData instance within the "conds" attribute if not provisioned yet; or
- the PCF may update the condition data decision which the PCC rule refers to by updating the corresponding
ConditionData instance as defined in subclause 4.2.6.1. The PCF may add an activation time or an
deactivation time, update the values of the existing activation time and/or the existing deactivation time, or
delete either the existing activation time or the existing deactivation time.
3) When modifying a PCC rule by deleting the deferred activation time and deactivation time:
- the PCF shall delete the reference to the ConditionData instance within the PCC rule by updating PCC rule
with the "refCondData" attribute set to NULL; and
- the PCF may delete the condition data decision which the PCC rule refers to as defined in subclause 4.2.6.1 if
no other PCC rules are referring to the condition data decision.
To delete a conditioned PCC rule, the PCF shall perform the deletion of PCC rule as defined in subclause 4.2.6.2.1.
The UE timezone information, if available, may be used by the PCF to derive the values of "activationTime" attribute
and/or the "deactivationTime" attribute.
The PCC rule(s) including the reference to the Condition Data decision which includes the "activationTime" attribute
and/or "deactivationTime" attribute shall be bound to a QoS flow associated with a default QoS rule that allows all UL
packets. If such PCC(s) is not bound to a QoS flow associated with a default QoS rule, the SMF shall report the failure
to the PCF by including the "ruleReports" attribute with the "failureCode" attribute set the value
"NO_QOS_FLOW_BOUND" for the affected PCC rule(s). Changes of the QoS profile or QoS rule which will initiate
the signalling towards the access network and/or UE in such PCC rule(s) shall also not be applied.
NOTE: This limitation prevents dependencies on the signalling of changed traffic mapping information towards
the UE.
4.2.6.2.8 PCC rule for resource sharing

If the ResShare feature is supported by both the SMF and PCF as described in subclause 5.8, the PCF may indicate that
the SMF should commonly reserve resources for a set of PCC rules. The SMF shall then, for PCC rules bound to the
same QoS flow and the same sharing key value , use the highest GBR value among those PCC rules as input for
calculating the common GBR value when reserving QoS flow resources. The GBR value for each direction shall be
considered separately, so that the uplink and downlink GBR values may originate from different PCC rules.
The SMF may, based on internal logic, use the highest MBR value among the provided PCC rules indicated to share
resources, when determining the MBR for the QoS flow. Each individual PCC rule is still subject to data rate policing
based on its own MBR values.
The PCF shall provide the "sharingKeyDl" attribute and/or "sharingKeyUl" attribute within the QosData data structure
which the PCC rules refers to in order to indicate that the related PCC rule may share resources with other PCC rules
bound to the same QoS flow.
The SMF shall apply resource sharing if at least two PCC rules bound to the same QoS flow share the same value in the
"sharingKeyDl" attribute and/or "sharingKeyUl" attribute.
3GPP
Release 16 67 3GPP TS 29.512 V16.5.0 (2020-06)
When modifying the value of "sharingKeyDl" attribute and/or "sharingKeyUl" attribute of the QosData data structure,
which a PCC rule refers to for the PCC rule that is subject to resource sharing the SMF may adjust the resource sharing
of the remaining PCC rules.
NOTE 1: A PCC rule that is deleted is also removed from the resource sharing, while the remaining PCC rules
continue their sharing relationship.
NOTE 2: The state of resource sharing ends when less than two of the PCC rules in the set remains.
4.2.6.2.9 Resource reservation for services sharing priority

When the PCF derives PCC Rules corresponding to a service related to an AF that has indicated that priority sharing is
allowed for that service over Rx interface or within the Npcf_PolicyAuthorization service, it derives the corresponding
PCC Rules according to current procedures as described in 3GPP TS 29.513 [7], subclause 7.3. The PCF may
additionally take the suggested pre-emption capability and vulnerability values into account if the AF provided them
when the PCF determines the ARP pre-emption capability and vulnerability. The ARP derived at this point and the
priority sharing indicator provided over Rx reference point (see 3GPP TS 29.214 [18] for further information) or over
the Npcf_PolicyAuthorization service (see 3GPP TS 29.514 [17] for further information) related to these derived PCC
Rules are stored for later use.
For PCC Rules related to the same PDU session with the same assigned 5QI and with the priority sharing indicator
enabled (see 3GPP TS 29.214 [18], subclause 4.4.8, or 3GPP TS 29.514 [17], subclauses 4.2.2.21, 4.2.3.21 and 4.2.4.9),
the PCF shall rederive the ARP into a shared ARP for these PCC Rules as follows:
- The Priority Level shall be set to the lowest value (i.e. highest priority) among the Priority Level values derived
for the PCC rules that include the priority sharing indicator.
- The Pre-emption Capability shall be set to true if any of the original derived PCC Rules have the Pre-emption-
Capability value set to true.
- The Pre-emption Vulnerability shall be set to true if all the original derived PCC Rules have the Pre-emption
Vulnerability value set to true.
NOTE 1: Having the same setting for the ARP parameter in the PCC Rules with the priority sharing indicator set
enables the usage of the same QoS flow. Furthermore, a combined modification of the ARP parameter in
the PCC rules ensures that a QoS flow modification is triggered when a media flow with higher service
priority starts.
If the 5QI and/or ARP related to any of the PCC Rules that share priority is changed (e.g. based on local policies), the
PCF shall rederive the ARP for the impacted PCC Rules following the same procedure as defined in this subclause.
The PCF shall provision the PCC Rules according to the rederived ARP information as described in subclause 4.2.6.2.1.
If the PCF receives a report that a PCC rule provisioning or modification failed due to the resource reservation failure as
defined in subclauses 4.2.3.1.6 and 4.2.4.15 (PCC Rule Error Report) and if the PCF supports the MCPTT-Preemption
feature as defined in subclause 5.4.1 of 3GPP TS 29.214 [18] or in subclause 5.8 of 3GPP TS 29.514 [17], the PCF shall
check if pre-emption control based on the pre-emption control information provided by the AF as defined in
subclauses 4.4.1 or 4.4.2 of 3GPP TS 29.214 [18] or in subclauses 4.2.2.21, 4.2.3.21 or 4.2.4.9 of 3GPP TS 29.514 [17]
applies.
NOTE 2: The PCF determines that pre-emption control applies based on the presence of the Pre-emption-Control-
Info AVP received over Rx reference point as defined in 3GPP TS 29.214 [18] or "preemptControlInfo"
attribute received over N5 reference point as defined in 3GPP TS 29.514 [17] and operator policies.
If pre-emption control applies, the PCF shall check the corresponding derived PCC Rules (before applying priority
sharing procedures). If the Pre-emption Capability of the derived PCC Rule is disabled the PCF shall notify that
resource allocation has failed for this PCC rule to the AF as defined in subclauses 4.4.1 or 4.4.2 of
3GPP TS 29.214 [18] or in subclauses 4.2.2.21, 4.2.3.21 or 4.2.4.9 of 3GPP TS 29.514 [17]. Otherwise, if the Pre-
emption Capability of the derived PCC Rule is enabled, the PCF shall perform the pre-emption control as follows:
- For all the active PCC rule(s) that applied priority sharing mechanism, the PCF shall identify the PCC Rules that
have the Pre-emption Vulnerability enabled. For those selected PCC Rule(s), the PCF shall check the Priority
Level value.
3GPP
Release 16 68 3GPP TS 29.512 V16.5.0 (2020-06)
- If there is only one PCC Rule with the Priority Level value higher (i.e. lower priority) than the derived Priority
Level value of new or modified PCC Rule, the PCF shall remove this PCC rule. The PCF shall retry the PCC
rule provisioning or modification procedure for the PCC rule that failed.
- Otherwise, if there are more than one PCC Rule with the Priority Level value higher (i.e. lower priority) than the
derived Priority Level value of new or modified PCC Rule, the PCF shall remove the PCC Rule with the highest
Priority Level from the SMF. The PCF shall retry the PCC rule provisioning or modification procedure for the
PCC rule that failed; If more than one PCC Rule have the same highest Priority Level, the PCF shall check the
Pre-Emption-Control-Info AVP received over Rx interface as defined in 3GPP TS 29.214 [18], or the
"preemptControlInfo" attribute received over N5 interface as defined in 3GPP TS 29.514 [17] and remove the
PCC Rule that matches the condition.
- Otherwise, if there is at least one PCC Rule with the same Priority Level value than the derived Priority Level
value of new or modified PCC Rule, the PCF shall check the Pre-emption-Control-Info AVP received over Rx
interface as defined in 3GPP TS 29.214 [18] or the "preemptControlInfo" attribute received over N5 interface as
defined in 3GPP TS 29.514 [17] for these PCC Rules and remove the PCC Rule that matches the condition.
- Otherwise, the PCF shall notify that resource allocation has failed for this PCC rule to the AF as defined in
subclauses 4.4.1 or 4.4.2 of 3GPP TS 29.214 [18] or in subclauses 4.2.2.21 or 4.2.3.21 of 3GPP TS 29.514 [17].
If there is no active PCC Rule with the Pre-emption Vulnerability enabled, the PCF shall notify that resource allocation
has failed for this PCC rule to the AF as defined in subclauses 4.4.1 or 4.4.2 of 3GPP TS 29.214 [18].
NOTE 3: If the PCF receives a report that a PCC rule provisioning or modification failed due to the resource
reservation failure and the PCF does not support the MCPTT-Preemption feature as defined in
subclause 5.4.1 of 3GPP TS 29.214 [18] or subclause 5.8 of 3GPP TS 29.514 [17], the PCF can apply
pre-emption and remove active PCC rules from the SMF and then retry the PCC rule provisioning or
modification procedure. Otherwise, the PCF will notify it to the AF as defined in subclauses 4.4.1 or 4.4.2
of 3GPP TS 29.214 [18] or in subclauses 4.2.2.21 or 4.2.3.21 of 3GPP TS 29.514 [17]. How the PCF
applies the pre-emption depends on the implementation.
4.2.6.2.10 PCC rule bound to the default QoS flow

The PCF may indicate to the SMF that a PCC rule shall be bound to the default QoS flow and shall remain on the
default QoS flow. The SMF shall then, for the indicated PCC rule bind it to the default QoS flow until the PCC rule is
removed or until the PCF modifies the PCC rule to set the "defQosFlowIndication" attribute to false. The SMF this
second case shall evaluate the full QoS information within the QosData data structure which the PCC rule refers and
follow normal policy enforcement procedures for authorized QoS per service data flow as described in
subclause 4.2.8.2.
NOTE: 5QI, ARP, QNC (if available), Priority Level (if available), Averaging Window (if available) and
Maximum Data Burst Volume (if available) within QoS Data decision referred by the PCC rule are only
used by the SMF for QoS flow binding purposes when the "defQoSFlowIndication" attribute is not
included in "qoSData" attribute or it is set to false.
The PCF shall provide the "defQoSFlowIndication" attribute set to true in order to indicate that the related PCC rule
shall be bound to the default QoS flow.
If the "defQoSFlowIndication" attribute set to true within the QosData data structure which the PCC rule refers to is
received in the SMF, the SMF shall bind the related PCC rule to the default QoS flow. This remains valid until the PCC
rule is removed or if the PCF indicates to the SMF that the binding to the default QoS flow no longer applies.
The SMF shall ignore other values including 5QI, ARP, QNC (if available), Priority Level (if available), Averaging
Window (if available) and Maximum Data Burst Volume (if available) within the QosData data structure if the
"defQoSFlowIndication" attribute set to true. If the PCF has previously indicated to the SMF that a PCC rule shall be
bound to the default QoS flow, to indicate that the binding to the default QoS flow no longer applies the PCF shall
update the PCC rule by including the "defQosFlowIndication" attribute set to false. The SMF in this case shall evaluate
the full QoS information within the QosData data structure which the PCC rule refers to and follow normal policy
enforcement procedures for authorized QoS per service data flow.
If the PCF has not previously indicated to the SMF that a PCC rule shall be bound to the default QoS flow (i.e. it may
be bound to another QoS flow) in order to indicate that the binding to the default QoS flow applies, the PCF shall
update the PCC rule by including the "defQoSFlowIndication" set to true. The SMF in this case shall follow the
procedures described in this subclause.
3GPP
Release 16 69 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.6.2.11 PCC rule for Application Detection and Control

If the ADC feature is supported and the user subscription indicates that the application detection and control is required,
the PCF may instruct the SMF to detect application (s) by installing or activating a PCC rule. Within the PCC rule, the
PCF shall provide an "appId" attribute set to the value of an application identifier. If the PCF requires to be reported
about when the application start/stop is detected, it shall also provide the APP_STA and APP_STO policy control
request trigger to the SMF as defined in subclause 4.2.6.4. The PCF may also mute such a notification about a specific
detected application by including a "traffContDecs" attribute to contain a Traffic Control Data decision which includes
the "muteNotif" attribute set to true and including a "refTcData" attribute referring to the Traffic Control Data decision
within the PCC rule.
4.2.6.2.12 Provisioning of PCC Rules for Multimedia Priority Services
4.2.6.2.12.1 General
The provision of PCC Rules corresponding to both MPS and non-MPS service shall be performed as described in
subclause 4.2.6.2.1 "Provisioning of PCC rules".
When the PCF derives PCC Rules corresponding to MPS service, the ARP and 5QI shall be set as appropriate for the
prioritized service, e.g. an IMS Multimedia Priority Service. The PCF may authorize a standardized 5QI or a
standardized 5QI with a specific 5QI priority level as defined in subclause 4.2.6.6.2. The PCF may also authorize a non-
standardized 5QI with explicitly signalled QoS characteristics as defined in subclause 4.2.6.6.3.
When the PCF derives PCC Rules corresponding to non-MPS service, the PCF shall generate the PCC Rules as per
normal procedures. At the time the Priority PDU connectivity services is invoked (i.e. Indication for support of priority
PDU connectivity service and MPS Priority Level are set), the PCF shall upgrade the ARP and/or change 5QI for the
PCC Rules to appropriate values as needed for MPS. The PCF shall change the ARP and/or 5QI (also associated QoS
characteristics if applicable) modified for the priority PDU connectivity service to an appropriate value according to
PCF decision.
When the PCF receives an HTTP POST message as defined in subclause 4.2.2.1, the PCF shall check whether any of
these parameters is stored in the UDR: indication for support of priority PDU connectivity service, MPS Priority Level
and/or indication of IMS priority service support. The PCF shall derive the applicable PCC rules and default QoS flow
QoS based on that information. If the indication of IMS priority service support is set and the "dnn" attribute
corresponds to a DNN dedicated for IMS, the PCF shall assign an ARP corresponding to MPS for the default QoS flow
and for the PCC Rules corresponding to the IMS signalling QoS flow. If the "dnn" does not correspond to a DNN
dedicated for IMS, the ARP shall be derived without considering IMS Signalling Priority.
NOTE 1: Subscription data for MPS is provided to PCF through the Nudr service.
Once the PCF receives a notification of a change in Priority PDU connectivity services support, MPS Priority Level
and/or IMS priority service support from the UDR, the PCF shall make the corresponding policy decisions (i.e. ARP
and/or 5QI (also associated QoS characteristics if applicable) change) and, if applicable, shall initiate an HTTP POST
message as defined in subclause 4.2.3.2 to provision the modified data.
NOTE 2: The details associated with the UDR service are specified in 3GPP TS 29.519 [15].
NOTE 3: The MPS Priority Level is one among other input data such as operator policy for the PCF to set the ARP.
Whenever one or more AF sessions of an MPS service are active within the same PDU session, the PCF shall ensure
that the ARP priority level of the default QoS flow is at least as high as the highest ARP priority level used by any
authorized PCC rules belonging to an MPS service. If the ARP pre-emption capability is enabled for any of the
authorized PCC rules belonging to an MPS service, the PCF shall also enable the ARP pre-emption capability for the
default QoS Flow.
NOTE 4: This ensures that services using dedicated QoS flows are not terminated because of a default QoS flow
with a lower ARP priority level or disabled ARP pre-emption capability being dropped during mobility
events.
NOTE 5: This PCF capability does not cover interactions with services other than MPS services.
3GPP
Release 16 70 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.6.2.12.2 Invocation/Revocation of Priority PDU connectivity services
When a Priority PDU connectivity services is invoked, the PCF shall:
- Derive the corresponding PCC Rules with the ARP and 5QI (also associated QoS characteristics if applicable)
set as appropriate for a prioritized service.
- Set the ARP of the default QoS flow as appropriate for a Priority PDU connectivity services under consideration
of the requirement described in subclause 4.2.6.2.12.1.
- Set the 5QI (also associated QoS characteristics if applicable) of the default QoS flow as appropriate for the
Priority PDU connectivity services.
- Set the ARP of PCC Rules installed before the activation of the Priority PDU connectivity services to the ARP as
appropriate for the Priority PDU connectivity services under the consideration of the requirements described in
subclause 4.2.6.2.12.1.
- Set the 5QI of the PCC Rules installed before the activation of the Priority PDU connectivity services to the 5QI
(also associated QoS characteristics if applicable) as appropriate for the Priority PDU connectivity services if
modification of the 5QI of the PCC Rules is required.
When a Priority PDU connectivity services is revoked, the PCF shall:
- Delete the PCC Rules corresponding to the Priority PDU connectivity services if they were previously provided.
- Set the ARP of the default QoS flow to the normal ARP under the consideration of the requirements described in
subclause 4.2.6.2.12.1.
- Set the 5QI of the default QoS flow as appropriate for PCF decision.
- Set the ARP of all active PCC Rules as appropriate for the PCF under the consideration of the requirements
described in subclause 4.2.6.2.12.1.
- Set the 5QI to an appropriate value according to PCF decision if modification of the 5QI of PCC Rules is
required.
NOTE: Priority PDU connectivity services can be explicitly invoked/revoked via UDR MPS user profile
(Indication of Priority PDU connectivity services, MPS Priority Level). An AF for MPS Priority Service
can also be used to provide Priority PDU connectivity services using network-initiated resource allocation
procedures (via interaction with PCC) for originating accesses.
The PCF shall provision the SMF with the applicable PCC Rules upon Priority PDU connectivity services activation
and deactivation as described above. The provision of the QoS information applicable for the PCC Rules shall be
performed as described in subclause 4.5.6.2. The provision of QoS information for the default QoS flow shall be
performed as described in subclause 4.2.6.3.
4.2.6.2.12.3 Invocation/Revocation of IMS Multimedia Priority Services
If the PCF receives service information including an MPS session indication and the service priority level from the P-
CSCF or at reception of the indication that IMS priority service is active for the PDU session, the PCF shall under
consideration of the requirements described in subclause 4.2.6.2.12.1:
- if required, set the ARP and 5QI (also associated QoS characteristics if applicable) of the default QoS flow as
appropriate for the prioritized service;
- if required, set the ARP and 5QI (also associated QoS characteristics if applicable) of all PCC rules assigned to
the IMS signalling QoS flow as appropriate for IMS Multimedia Priority Services;
- derive the PCC Rules corresponding to the IMS Multimedia Priority Service and set the ARP and 5QI (also
associated QoS characteristics if applicable) of these PCC Rules based on the information received over N5/Rx.
If the PCF detects that the P-CSCF released all the MPS session and the IMS priority service has been deactivated for
the PDU session the PCF shall under consideration of the requirements described in subclause 4.2.6.2.12.1:
- delete the PCC Rules corresponding to the IMS Multimedia Priority Service;
3GPP
Release 16 71 3GPP TS 29.512 V16.5.0 (2020-06)
- if required, set the ARP and 5QI of the default QoS flow as appropriate for the IMS Multimedia Priority set to
inactive;
- replace the ARP and 5QI of all PCC Rules assigned to the IMS signalling QoS flow as appropriate when the
IMS Multimedia Priority is inactive.
4.2.6.2.13 Sponsored Data Connectivity

Sponsored data connectivity may be performed for service data flows associated with one or more PCC rules if the
information about the sponsor, the application service provider and optionally the threshold values are provided by the
AF and if the AF has not indicated to disable/not enable sponsored data connectivity as described in
3GPP TS 29.214 [18] subclauses 4.4.1 and 4.4.2 or 3GPP TS 29.514 [17] subclauses 4.2.2.5 and 4.2.3.5.
The provisioning of sponsored data connectivity per PCC rule shall be performed using the PCC rule provisioning
procedure as defined in subclause 4.2.6.2.1. The sponsor identity shall be set using the "sponsorId" attribute within the
ChargingData data type which the PCC rule refers to. The application service provider identity shall be set using the
"appSvcProvId" attribute within the ChargingData data type which the PCC rule refers to. The "sponsorId" attribute and
"appSvcProvId" shall be set if the "reportingLevel" attribute within the ChargingData data type which the PCC rule
refers to is set to the value "SPON_CON_LEVEL".
When receiving the usage thresholds from the AF, the PCF shall use the sponsor identity to generate a value of "umId"
attribute of the UsageMonitoringData data type which the PCC rule refers to and request usage monitoring control for
the sponsored data connectivity by following the procedures specified in subclauses 4.2.6.2.5.
When the AF disables sponsoring a service (See 3GPP TS 29.214 [18] subclause 4.4.2 or 3GPP TS 29.514 [17]
subclause 4.2.3.5), the PCF
- may modify the PCC rules in order to set the "reportingLevel" attribute to "SER_ID_LEVEL" or
"RAT_GR_LEVEL" within the ChargingData data type which the PCC rule refers to and not include the
"sponsorId" attribute and "appSvcProvId" attribute if they were included previously.
- may modify the PCC rules to update the charging key by setting the new value of the "ratingGroup" attribute
within the ChargingData data type which the PCC rule refers to.
NOTE: A specific charging key can be applied to the sponsored data connectivity for online charging.
- shall disable the usage monitoring for the sponsored data connectivity according to subclause 4.2.6.2.5 if it was
enabled previously. As a result, PCF gets the accumulated usage of the sponsored data connectivity.
4.2.6.2.14 Support for PCC rule versioning

The support of PCC rule versioning is optional. When the "RuleVersioning" feature is supported, the SMF and the PCF
shall comply with the procedures specified in this subclause.
If required by operator policies, the PCF shall assign a content version for each generated PCC rule and shall include
the assigned version in the "contVer" attribute included within the PccRule data structure. Upon each PCC rule
modification, if the content version was previously assigned to a PCC rule, the PCF shall assign a new content version.
In this case, all the content related to that PCC rule shall be included. If the PCF needs to modify the attribute(s) within
the PCC rule, the PCF shall include the new content version within the "contVer" attribute together with all modified
and unmodified applicable attributes(s) within the PccRule data structure. If the PCF only needs to modify the content
of referenced policy decision data and/or condition data for one or more PCC rules, the PCF shall additionally provide
the PCC rule(s) which is referring to the modified policy decision data and/or condition data. Within each PCC rule
instance, the PCF shall include all unmodified applicable attributes(s) and the new assigned version in the "contVer"
attribute. The content version is unique for the lifetime of the PCC rule.
NOTE 1: The PCF will include all the content of the PCC rule in each modification of the PCC rule in order to
ensure that the rule is installed with the proper information regardless of the outcome of the QoS flow
procedure related to previous rule provisioning versions that are not reported yet.
NOTE 2: The operation policies can take into account whether the AF provides the related content version
information over Rx reference point (see subclause 4.4.9 in 3GPP TS 29.214 [18]), or over
Npcf_PolicyAuthorization service (see subclauses 4.2.2.13 and 4.2.3.13 in 3GPP TS 29.514 [17]).
3GPP
Release 16 72 3GPP TS 29.512 V16.5.0 (2020-06)
Whenever the SMF provides a PCC rule report for rules that were provisioned with a content version, the SMF shall
include the "contVers" attribute defined in the RuleReport data structure for those corresponding PCC rules. In case it is
required to report the content version of multiple PCC rules, the SMF shall use one instance of RuleReport data
structure per PCC rule, and shall include in the "pccRuleIds" attribute only the identifier of the corresponding PCC rule.
The SMF may include more than one content version in the "contVers" attribute for the same PCC rule within the
corresponding RuleReport instance included in the "ruleReports" attribute (e.g. the SMF has combined multiple PCC
rule versions enforcement into one QoS flow operation). In this case, the "ruleStatus" attribute shall indicate the final
status of the PCC rule.
NOTE 3: The PCF will use the content version to identify the PCC rule version that failed or succeeded when
multiple provisions of the same PCC rule occur in a short period of time. If required by the AF, the PCF
will inform the AF according to 3GPP TS 29.214 [18], subclause 4.4.9, or according to
3GPP TS 29.514 [17], subclause 4.2.5.8 about the failure or success for the media component version
associated to the PCC rule version.
4.2.6.2.15 Background data transfer support

If the PCF receives Reference Id within the service information from the AF as defined in 3GPP TS 29.514 [17] or
3GPP TS 29.214 [18] or if "EnhancedBackgroundDataTransfer" feature as defined in subclause 5.8 is supported and the
PCF receives the Reference Id(s) within the PDU session related subscription information from the UDR as defined in
3GPP TS 29.519 [15], the PCF shall retrieve the corresponding transfer policy from the UDR based on the Reference
Id(s) as defined in 3GPP TS 29.519 [15]. The PCF shall use the retrieved transfer policy as input for policy decisions
(e.g. setting the charging key equal to the charging key of the transfer policy, rule activation/deactivation time
according to the time window).
During PDU session establishment, if "EnhancedBackgroundDataTransfer" feature as defined in subclause 5.8 is

supported and if validation conditions (i.e. Time Window and/or Location Criteria) of the transfer policy are not
satisfied then the PCF may reject corresponding SM Policy Association as defined in subclause 4.2.2.2 and include in
an HTTP "403 Forbidden" response message the "cause" attribute of the ProblemDetails data structure set to
"VALIDATION_CONDITION_NOT_MET". And based on this feedback, the SMF shall reject the PDU session setup.
After successful PDU session establishment, if "EnhancedBackgroundDataTransfer" feature as defined in subclause 5.8
is supported, PCF may request the PDU session termination if the validation conditions become not satisfied as defined
in subclause 4.2.3.3. Within the TerminationNotification, the PCF shall include the "cause" attribute set to
"VALIDATION_CONDITION_NOT_MET".
4.2.6.2.16 Number of supported packet filter for signalled QoS rule limitation support
If the PCF includes the flow information within the "flowInfos" attribute(s) and if the number of supported packet filter
for signalled QoS rules within the "numOfPackFilter" attribute is received from the SMF during the PDU session
establishment, the PCF shall ensure that for all the dynamic PCC rules of a PDU session, the number of packet filters
contained within the "flowDescription" attribute or the "ethFlowDescripiont" attribute with the "packetFilterUsage" set
to true does not exceed the value of the "numOfPackFilter" attribute.
4.2.6.2.17 Access traffic steering, switching and splitting support

If both the SMF and the PCF support the "ATSSS" feature as defined in subclause 5.8, the PCF may enable the control
of traffic steering, switching and splitting for a detected service data flow by including MA PDU Session control
information within the PCC rule. In order to do so, within the PccRule data structure the PCF:
- may include one reference to the ChargingData data structure within the "refChgN3gData" attribute if the PCF
determines that the specific charging parameters used for packets carried via Non-3GPP access. In this case, a
"chgDecs" attribute containing the corresponding Charging Data policy decisions shall be included in the
- may include one reference to the UsageMonitoringData data structure within the "refChgN3gData" attribute if
the PCF determines that the specific usage monitoring parameters used for packets carried via Non-3GPP access.
In this case, a "umDecs" attribute containing the corresponding Usage Monitoring Data policy decisions shall be
included in the SmPolicyDecision data structure if it has not been provided;
- may include the ATSSS rule application descriptor(s) within "appDescriptors" attribute if the SDF template
included in the PCC rule contains an Application Identifier in the "appId" attribute (see subclause 4.2.6.2.1). The
3GPP
Release 16 73 3GPP TS 29.512 V16.5.0 (2020-06)
PCF may retrieve the OS Id(s) from the "UEPolicySet" resource in the UDR as described in
3GPP TS 29.519 [15] to determine, by internal configuration, the OS Application Identifier supported by the OS
Id that corresponds to the application identifier included in the SDF template. If no OS Id is available in the
UDR, the PCF may use the PEI to determine the OS Id supported by the UE;
NOTE 1: If the PCF does not take into account the received PEI and/or the retrieved OSid(s) to derive the
application descriptor, then the PCF can include in the PCC rule multiple application descriptors
associated to multiple operating systes.
NOTE 2: If only one UE OSid is stored in the UDR and the PCF takes it into account to derive the application
descriptor, then the PCF can omit the OS Id in the application descriptor included in the Pcc rule.
- may include the ATSSS policies within the Traffic Control Data decision which the PCC rule refers to. Within
the TrafficControlData data structure, based on the ATSSS capability supported for the MA PDU Session, the
PCF shall include:
- the applicable access traffic steering method, "ATSSS_LL" or "MPTCP", for the UL and DL traffic, encoded
in the "steerFun" attribute; and
- the steering rule for access traffic distribution across the 3GPP and Non-3GPP accesses encoded in a
"SteeringMode" data structure within the "steerModeDl" attribute for the DL traffic and within the
"steerModeUl" attribute for the UL traffic.
The "SteeringMode" data structure shall include:
- the steering mode value determined by the PCF within the "steerModeValue" attribute as follows:
a. "ACTIVE_STANDBY" indicates the traffic of a SDF is steered on one access (the Active access), when this
access is available, and switched to the other access (the Standby access), when Active access becomes
unavailable. When the Active access becomes available again, the SDF is switched back to this access. If the
Standby access is not defined, then the SDF is only allowed on the Active access and cannot be transferred
on another access.
b. "LOAD_BALANCING" indicates that the traffic of an SDF is split percentually between the 3GPP and Non-
3GPP accesses.
c. "SMALLEST_DELAY" indicates that the traffic of an SDF is steered and/or switched to the access that has
the smallest delay (e.g. smallest RTT).
d. "PRIORITY_BASED" indicates that the traffic of an SDF is steered to the high priority access until the
access is determined to be congested. In this case, the traffic of the SDF is also sent to the low priority access,
i.e. the SDF traffic is split over the two accesses. When the high priority access becomes unavailable, all SDF
traffic is switched to the low priority access. How UE and UPF determine when a congestion occurs on an
access is implementation dependent.
- When the access traffic steering mode in the "steerModeValue" attribute is "ACTIVE_STANDBY", the active
access encoded within the "active" attribute, and the standby access, if defined, in the "standby" attribute; or
- When the access traffic steering mode in the "steerModeValue" attribute is "LOAD_BALANCING", the traffic
load distributed across 3GPP and Non-3GPP accesses encoded within the "3gLoad" attribute as the 3GPP access
traffic weight percentage. The sum of the Non-3GPP access traffic weight percentage and the 3GPP access
traffic weight percentage must be 100; or
- When the access traffic steering mode in the "steerModeValue" attribute is "PRIORITY_BASED", the high
priority access type encoded within the "prioAcc" attribute.
If the value of "atsssCapab" attribute received from the SMF is

"MPTCP_ATSSS_LL_WITH_EXSDMODE_DL_ASMODE_UL", the PCF shall provide a PCC Rule for non-MPTCP
traffic. To enable non-MPTCP traffic, the PCF shall include a "match all" packet filter within the "flowInfos" attribute,
the highest value within the "precedence" attribute of the PCC rule, and within the TrafficControlData data structure
referred by the PCC rule, set the "steerFun" attribute to the "ATSSS_LL", the "steerModeValue"attribute of the
"steerModeUl" attribute to "ACTIVE_STANDBY", and the "steerModeValue"attribute of the "steerModeDl" attribute
to any supported steering mode except the "SMALLEST_DELAY" steering mode.
3GPP
Release 16 74 3GPP TS 29.512 V16.5.0 (2020-06)
If the value of "atsssCapab" received from the SMF is "MPTCP_ATSSS_LL_WITH_ASMODE_UL", the PCF shall
provide a PCC rule for non-MPTCP traffic. To enable non-MPTCP traffic, the PCF shall include a "match all" packet
filter within the "flowInfos" attribute, the highest value within the "precedence" attribute of the PCC rule, and within the
TrafficControlData data structure referred by the PCC rule, set the "steerFun" attribute to the "ATSSS_LL", the
"steerModeValue"attribute of the "steerModeUl" attribute to "ACTIVE_STANDBY", and the
"steerModeValue"attribute of the "steerModeDl" attribute to any supported steering mode.
If the value of "atsssCapab" received from the SMF is "MPTCP_ATSSS_LL_WITH_ASMODE_DLUL", the PCF shall
provide a PCC rule for non-MPTCP traffic. To enable non-MPTCP traffic, the PCF shall include a "match all" packet
filter within the "flowInfos" attribute, the highest value within the "precedence" attribute of the PCC rule, and within the
"steerModeValue"attribute of the "steerModeUl" attribute and the "steerModeDl" attribute to "ACTIVE_STANDBY.
If the value of "atsssCapab" received from the SMF is "MPTCP_ATSSS_LL", the PCF shall provide a PCC rule for
non-MPTCP traffic. To enable non-MPTCP traffic, the PCF may include a "match all" packet filter within the
"flowInfos" attribute, the highest value within the "precedence" attribute of the PCC rule, and within the
"steerModeValue"attribute of the "steerModeUl" attribute and the "steerModeDl" attribute to any supported steering
mode.
Upon receipt of the PCC with the MA PDU Session control information, the SMF shall:
- derive the ATSSS rules to deliver to the UE for UL traffic steering as defined in 3GPP TS 29.502 [22];
NOTE 3: The Traffic Descriptor in the ATSSS rule is genereated by the SMF from the SDF template of the PCC
rule. If the PccRule data structure contains the "flowInfos" attribute, the SMF uses the UL SDF filters for
the generation of the IP descriptors or Non-IP descriptors. If the PccRule data structure contains the
"appId" attribute, the SMF includes the application descriptors received from the PCF in the
"appDescriptor" attribute of the PCC rule.
- derive the QoS profile and provide it to the access network(s) as follows:
- for a Non-GBR QoS flow,
a) the SMF shall provide the QoS profile to both access networks if the UE is registered over both accesses
during MA PDU Session Establishment procedure;
b) the SMF shall provide the QoS profile to the access networks over which the user plane resources are
activated during MA PDU Session Modification procedure.
- for a GBR QoS flow,
a) if the Multi Access policies of the PCC rule indicate the GBR SDF is handled only in one access (i.e. , the
SMF shall provide the QoS profile to the access network indicated by the PCC rule;
b) if the Multi Access policies of the PCC rule indicate the GBR SDF is handled in both accesses, the SMF
shall decide to which access network to provide the QoS profile for the GBR SDF based on its local
policy (e.g. the local policy is configured the access where the traffic is ongoing according to the Multi
Access policies of the PCC rule).
c) for a GBR QoS flow, traffic splitting is not supported because the QoS profile is provided to a single
access network at a given time, and the traffic can be steered or switched as indicated by the
“ACTIVE_STANDBY” steering mode. If the SMF receives the report that the current active access is not
available from the UPF, the SMF shall perform as follows:
- if the corresponding PCC rule allows the GBR QoS flow only on this access or if the corresponding
PCC rule allows the GBR QoS flow on both accesses but the other access is not available, the SMF
shall release the resources for the GBR QoS flow and report to the PCF about the removal of the PCC
rule as defined in subclause 4.2.4.15.
- if the corresponding PCC rule allows the GBR QoS flow on both accesses and the other access is
available, the SMF shall try to move the GBR QoS flow to the other access. The SMF may trigger a
PDU session modification procedure to provide the QoS profile to the other access and release the
resources for the GBR QoS flow in the current access.
3GPP
Release 16 75 3GPP TS 29.512 V16.5.0 (2020-06)
- if the QoS notification control is not enabled for the corresponding PCC rule and the other access
does not accept the QoS profile, the SMF shall release the resources for the GBR QoS flow and
report to the PCF about the removal of the PCC rule as defined in subclause 4.2.4.15.
- if the QoS notification control is enabled for the corresponding PCC rule, the SMF shall notify the
PCF within the "qncReports" attribute that the QoS targets of the SDFs are not guaranteed. After
the other access accepts the QoS profile, the SMF shall notify the PCF within the "qncReports"
attribute that the QoS targets of the SDFs are guaranteed again. If the other access does not accept
the QoS profile, the SMF shall delete the GBR QoS flow and report to the PCF about the removal
of the PCC rule as defined in subclause 4.2.4.15.
- instruct the UPF for DL access traffic steering as defined in 3GPP TS 29.244 [13];
- apply charging information depending on the used access type if indicated in the PCC rule; and
- apply usage monitoring control depending on the used access type if indicated in the PCC rule.
The PCF may update the steering rule for access traffic distribution across the 3GPP and Non-3GPP accesses for a PCC
rule. In order to do so, the PCF may:
- within the corresponding PccRule data structure, include a new reference of a Traffic Control Data decision and
provide the Traffic Control Data decision if not provided yet.
- update the Traffic Control Data decision by including the appropriate attribute value(s) within the "steerFun"
attribute, "steerModeDl" attribute and/or "steerModeUl" attribute.
4.2.6.2.18 Void
4.2.6.2.19 Provisioning of PCC Rules for Mission Critical Services
4.2.6.2.19.1 General
The provision of PCC Rules corresponding to both MCS and non-MCS service shall be performed as described in
subclause 4.2.6.2.1 "Provisioning of PCC rules".
When the PCF derives PCC Rules corresponding to MCS service, the ARP and 5QI shall be set as appropriate for the
prioritized service, e.g. an IMS Mission Critical Service. The PCF may authorize a standardized 5QI or a standardized
5QI with a specific 5QI priority level as defined in subclause 4.2.6.6.2. The PCF may also authorize a non-standardized
5QI with explicitly signalled QoS characteristics as defined in subclause 4.2.6.6.3.
At the time the Priority PDU connectivity services is invoked (i.e. Indication for support of priority PDU connectivity
service and MCS Priority Level are set), the PCF shall upgrade the ARP and/or change 5QI for the PCC Rules to
appropriate values as needed for MCS. The PCF shall change the ARP and/or 5QI (also associated QoS characteristics
if applicable) modified for the priority PDU connectivity service to an appropriate value according to PCF decision.
When the PCF receives an HTTP POST message as defined in subclause 4.2.2.1, the PCF shall check whether any of
these parameters is stored in the UDR: indication for support of priority PDU connectivity service, indication for
support of MCS Priority Level. The PCF shall derive the applicable PCC rules and default QoS flow QoS based on that
information. If the indication of IMS priority service support is set and the "dnn" attribute corresponds to a DNN
dedicated for IMS, the PCF shall assign an ARP corresponding to MCS for the default QoS flow and for the PCC Rules
corresponding to the IMS signalling QoS flow. If the "dnn" does not correspond to a DNN dedicated for IMS, the ARP
shall be derived without considering IMS Signalling Priority.
NOTE 1: Subscription data for MCS is provided to the PCF through the Nudr service.
Once the PCF receives a notification of a change in Priority PDU connectivity services support, MCS Priority Level
and/or IMS priority service support from the UDR, the PCF shall make the corresponding policy decisions (i.e. ARP
and/or 5QI (also associated QoS characteristics if applicable) change) and, if applicable, shall initiate an HTTP POST
message as defined in subclause 4.2.3.2 to provision the modified data.
NOTE 2: The details associated with the UDR service are specified in 3GPP TS 29.519 [15].
NOTE 3: The MCS Priority Level is one among other input data such as operator policy for the PCF to set the
ARP.
3GPP
Release 16 76 3GPP TS 29.512 V16.5.0 (2020-06)
Whenever one or more AF sessions of an MCS service are active within the same PDU session, the PCF shall ensure
that the ARP priority level of the default QoS flow is at least as high as the highest ARP priority level used by any
authorized PCC rules belonging to an MCS service. If the ARP pre-emption capability is enabled for any of the
authorized PCC rules belonging to an MCS service, the PCF shall also enable the ARP pre-emption capability for the
default QoS Flow.
NOTE 4: This ensures that services using dedicated QoS flows are not terminated because of a default QoS flow
with a lower ARP priority level or disabled ARP pre-emption capability being dropped during mobility
events.
NOTE 5: This PCF capability does not cover interactions with services other than MCS services.
4.2.6.2.19.2 Invocation/Revocation of Priority PDU connectivity services
When a Priority PDU connectivity services is invoked, the PCF shall:
- Derive the corresponding PCC Rules with the ARP and 5QI (also associated QoS characteristics if applicable)
set as appropriate for a prioritized service.
- Set the ARP of the default QoS flow as appropriate for a Priority PDU connectivity services under consideration
of the requirement described in subclause 4.2.6.2.19.1.
- Set the 5QI (also associated QoS characteristics if applicable) of the default QoS flow as appropriate for the
Priority PDU connectivity services.
- Set the ARP of PCC Rules installed before the activation of the Priority PDU connectivity services to the ARP as
appropriate for the Priority PDU connectivity services under the consideration of the requirements described in
subclause 4.2.6.2.19.1.
- Set the 5QI of the PCC Rules installed before the activation of the Priority PDU connectivity services to the 5QI
(also associated QoS characteristics if applicable) as appropriate for the Priority PDU connectivity services if
modification of the 5QI of the PCC Rules is required.
When a Priority PDU connectivity services is revoked, the PCF shall:
- Delete the PCC Rules corresponding to the Priority PDU connectivity services if they were previously provided.
- Set the ARP of the default QoS flow to the normal ARP under the consideration of the requirements described in
subclause 4.2.6.2.19.1.
- Set the 5QI of the default QoS flow as appropriate for PCF decision.
- Set the ARP of all active PCC Rules as appropriate for the PCF under the consideration of the requirements
described in subclause 4.2.6.2.19.1.
- Set the 5QI to an appropriate value according to PCF decision if modification of the 5QI of PCC Rules is
required.
NOTE: Priority PDU connectivity services can be explicitly invoked/revoked via UDR MCS user profile
(Indication of Priority PDU connectivity services, MCS Priority Level). An AF for MCS Priority Service
can also be used to provide Priority PDU connectivity services using network-initiated resource allocation
procedures (via interaction with PCC) for originating accesses.
The PCF shall provision the SMF with the applicable PCC Rules upon Priority PDU connectivity services activation
and deactivation as described above. The provision of the QoS information applicable for the PCC Rules shall be
performed as described in subclause 4.5.6.2. The provision of QoS information for the default QoS flow shall be
performed as described in subclause 4.2.6.3.
4.2.6.2.19.3 Invocation/Revocation of IMS Mission Critical Services
If the PCF receives service information including an MCS session indication and the service priority level from the P-
CSCF or at reception of the indication that IMS priority service is active for the PDU session, the PCF shall under
consideration of the requirements described in subclause 4.2.6.2.19.1:
3GPP
Release 16 77 3GPP TS 29.512 V16.5.0 (2020-06)
- if required, set the ARP and 5QI (also associated QoS characteristics if applicable) of the default QoS flow as
appropriate for the prioritized service;
- if required, set the ARP and 5QI (also associated QoS characteristics if applicable) of all PCC rules assigned to
the IMS signalling QoS flow as appropriate for IMS Mission Critical Services;
- derive the PCC Rules corresponding to the IMS Mission Critical Service and set the ARP and 5QI (also
associated QoS characteristics if applicable) of these PCC Rules based on the information received over N5/Rx.
If the PCF detects that the P-CSCF released all the MCS session and the IMS priority service has been deactivated for
the PDU session the PCF shall under consideration of the requirements described in subclause 4.2.6.2.19.1:
- delete the PCC Rules corresponding to the IMS Mission Critical Service;
- if required, set the ARP and 5QI of the default QoS flow as appropriate for the IMS Mission Critical set to
inactive;
- replace the ARP and 5QI of all PCC Rules assigned to the IMS signalling QoS flow as appropriate when the
IMS Mission Critical Service is inactive.
4.2.6.3 Session Rules
4.2.6.3.1 Overview
The PCF may perform operations on session rules. The impacted rules shall be included in the "SessRules" map
attribute within the SMPolicyDecision data structure with the "sessRuleId" as a key. For installing or modifying a
session rule, the corresponding SessionRule data instance shall be provided as the map entry value. For removing a
session rule, the map entry value shall be set to NULL.
In order to install a new session rule, the PCF shall further set other attributes within the SessionRule data structure as
follows:
- it may include the authorized session AMBR within the "authSessAmbr" attribute;
- it may include the authorized default QoS within the "authDefQoS" attribute using the procedure as defined in
subclause 4.2.6.3.3;
- it may include one reference to the UsageMonitoringData data structure within the "refUmData" attribute. In this
case, a "umDecs" attribute containing the corresponding Usage Monitoring data policy decisions shall be
included in SmPolicyDecision data structure if it has not been previously provided;
- if the "ATSSS" feature is supported, it may include one reference to the UsageMonitoringData data structure to
apply for the Non-3GPP access within the "refUmN3gData" attribute. In this case, a "umDecs" attribute
containing the corresponding Usage Monitoring data policy decisions shall be included in SmPolicyDecision
data structure if it has not been previously provided; and
- it may include one reference to the ConditionData data structure within the "refCondData" attribute. In this case,
a "conds" attribute containing the corresponding Condition Data decision shall be included in SmPolicyDecision
data structure if it has not been previously provided.
In order to modify an existing session rule, the PCF shall further set other attributes within the SessionRule data
structure as follows:
- If the PCF needs to modify the attribute(s) within a session rule, the PCF shall include the modified attributes(s)
with the new value(s) within the SessionRule data instance. Previously supplied attributes not supplied in the
modified PCC rule instance shall remain valid.
- If the PCF only needs to modify the content of referenced policy decision data (e.g. UsageMonitoringData, etc.)
and/or condition data for one or more session rules, the PCF shall, within the SmPolicyDecision data structure,
include the corresponding policy decision data and/or condition data within the corresponding map attributes
(e.g. include the usage monitoring data decision within the "umDecs" attribute).
The PCF may combine multiple of the above session rule operations in a single message, but the PCF shall make sure
that these is only one session rule active.
3GPP
Release 16 78 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.6.3.2 Conditioned Session rule
4.2.6.3.2.1 General
Up to four conditioned session rules (i.e. authorized session AMBR and/or authorized default QoS) may be provisioned
by the PCF. In order to provision a session rule with conditional data, the PCF shall provision a session rule as defined
in subclause 4.2.6.3.1 and include within its "refCondData" attribute the corresponding ConditionData's "condId"
attribute value. The PCF shall also ensure that the referenced ConditionData instance is included in the "conds" map
within the SmPolicyDecision data structure following the procedures defined in subclause 4.2.6.1.
Within the ConditionData instance, the PCF may include the activation time within the "activationTime" attribute for
the time conditioned authorized Session AMBR and/or authorized default QoS. If the "AccessTypeCondition" feature
as defined in subclause 5.8 is supported, the PCF may also include the access type within the "accessType" attribute and
RAT type within the "ratType" attribute if applicable for the access type conditioned authorized session AMBR.
NOTE 1: The same instance of session rule can convey information related to the authorized session-AMBR and
authorized default QoS when the same time condition applies to both.
NOTE 2: The SMF retains remaining time conditioned authorized QoS that have an execution time in the future.
NOTE 3: Time condition and access type condition can both apply to one authorized session AMBR.
If the SMF receives the conditioned session rule, when the condition indicated in the related attribute(s) within the
Condition Data decision (e.g. at the time indicated in the "activationTime" attribute) is met, the SMF shall perform the
conditional policy without interaction with the PCF. If the Condition Data decision includes more than one type of
conditions and all the types of conditions are met, the SMF shall perform the conditional policy.
If time conditioned session rule(s) to change the non-conditioned session rule are received by the SMF and the earliest
Activation Time is in the past, then the SMF shall immediately enforce the most recent time conditioned instance that is
not in the future.
The PCF may modify a currently installed session rule, including setting, modifying or deleting its condition(s) as
follows:
1) When modifying a session rule by setting the condition(s), the PCF shall update the session rule by including the
corresponding ConditionData's "condId" attribute value within the "refCondData" attribute and within the
SmPolicyDecision data structure include the ConditionData instance within the "conds" attribute if not
provisioned yet.
2) When modifying a session rule by modifying the condition(s):
- the PCF may update the session rule by replacing the existing ConditionData instance's "condId" attribute
value within the "refCondData" attribute with a new one and within the SmPolicyDecision data structure
include the new ConditionData instance within the "conds" attribute if not provisioned yet; or
- the PCF may update the condition data decision which the session rule refers to by updating the
corresponding ConditionData instance as defined in subclause 4.2.6.1. The PCF may update the value of the
condition within the related attribute (e.g. the value of the existing deferred activation time within the
"activationTime" attribute).
3) When modifying a session rule by deleting the condition(s):
- the PCF shall delete the reference to the ConditionData instance within the session rule by updating session
rule with the "refCondData" attribute set to NULL; and
- the PCF may delete the condition data decision which the session rule refers to as defined in
subclause 4.2.6.1 if no other session rules are referring to the condition data decision.
To delete a conditioned session rule, the PCF shall perform the deletion of session rule as defined in subclause 4.2.6.3.1.
The "ueTimeZone" attribute, if available, may be used by the PCF to derive the value for the "activationTime" attribute.
3GPP
Release 16 79 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE 4: Conditioned session AMBR and default QoS change helps reducing the signalling load over N7.
However, the session AMBR and default QoS change needs to be communicated to the UE. Consequently
a simultaneous change of the session AMBR and default QoS for many UE(s) may introduce a signalling
storm in the 5GC (e.g. over N1/N2/N4/N11). The PCF can avoid this simultaneous change of the session
AMBR and default QoS (e.g. spread the time conditioned change over time for many UEs).
4.2.6.3.2.2 Time conditioned authorized session AMBR
The procedures in subclause 4.2.6.3.2.1 apply with clarifications in the present subclause.
Each instance of the session rule shall include authorized session AMBR within the "authSessAmbr" attribute.
The SMF shall, after applying a time conditioned instruction to change the authorized AMBR, apply the corresponding
procedures towards to the access network, the UE and the UPF for the enforcement of the AMBR per PDU session.
4.2.6.3.2.3 Time conditioned authorized default QoS
The procedures in subclause 4.2.6.3.2.1 apply with clarifications in the present subclause.
Each instance of the session rule shall include authorized default QoS within the "authDefQos" attribute.
The SMF shall, after applying a time conditioned instruction to change the authorized default QoS, apply the
corresponding procedures towards to the access network, the UE and the UPF for the enforcement of the authorized
default QoS. All PCC rule(s) with the "defQosFlowIndication" attribute set to true shall remain bound to the default
QoS flow. For any other PCC rule previously bound to the default QoS flow, SMF shall then perform the QoS flow
binding according to subclause 6.4 in 3GPP TS 29.513 [7].
4.2.6.3.2.4 Access type conditioned authorized session AMBR
The SMF shall enforce the session AMBR values corresponding to the "accessType" attribute and "ratType" attribute
matching the current access type and RAT type of the UE for the given PDU session.
If there is an authorized session AMBR without any access type condition provided or if it has been previously
provisioned and there is also an access type conditioned authorized session AMBR provided, then the access type
conditioned authorized session AMBR where the conditions specified within the Condition Data decision are met shall
be enforced. Otherwise, the authorized session AMBR without any access type condition shall be enforced.
If conditions from multiple access type conditioned authorized session AMBR are met at the same time then the session
AMBR related to the most strict matching condition is enforced, e.g. Policy1 specifies access type only and Policy2
specifies access type (with the value same as in Policy1) and an RAT Type, both, then the Policy2 shall be enforced
when the UE's current access type and RAT type matches with the condition specified by Policy2.
If conditions from multiple access type conditioned authorized session AMBR are met at the same time and all of these
policies are equally applicable, e.g. Policy1 specifies access type only and Policy2 specifies RAT type only and if the
UE's current access type matches with Policy1 and the UE's current RAT type matches with Policy2, then the SMF
should apply the session AMBR with Policy2.
4.2.6.3.3 Provisioning of authorized default QoS

The PCF can provide the authorized default QoS for a session rule to the SMF. The provisioning of authorized default
QoS for a session rule shall be performed using the session rule provisioning procedure as defined in
subclause 4.2.6.3.1. The authorized default QoS shall be encoded using a AuthorizedDefaultQos data structure.
In order to provision authorized default QoS for a new session rule, the PCF shall include the assigned 5QI value within
the "5qi" attribute and the assigned ARP value within the "arp" attribute in the AuthorizedDefaultQos data structure.
The PCF may include "priorityLevel", "averWindow" and/or "maxDataBurstVol" or "extMaxDataBurstVol" (if
supported, see subclause 4.2.2.1) attributes in the AuthorizedDefaultQos data structure to authorize particular QoS
characteristics that override the default values for a standardized or pre-configured 5QI. The PCF may include a
"QosCharacteristics" entry in the "qosChars" attribute map to provide explicitly signalled QoS characteristics associated
with a 5QI that is neither standardized nor pre-configured. When the authorized default QoS applies to explicitly
signalled QoS Characteristics, it shall be provisioned as defined in subclause 4.2.6.6.3. For 5QI of GBR type or delay
critical GBR type, the PCF shall include max bandwidth in uplink within the "maxbrUl" attribute and/or max bandwidth
in downlink within the "maxbrDl" attribute, the guaranteed bandwidth in uplink within the "gbrUl" attribute and/or the
3GPP
Release 16 80 3GPP TS 29.512 V16.5.0 (2020-06)
guaranteed bandwidth in downlink within the "gbrDl" attribute and may request a notification when authorized GBR or
delay critical GBR cannot be guaranteed or can be guaranteed again by including the "qnc" attribute set to true.
In order to modify authorized default QoS for an existing session rule, the PCF shall include the modified attributes(s)
with the new value(s) within the AuthorizedDefaultQos data structure and provision a new QoS Characteristics if
applicable. Previously supplied attributes not supplied in the AuthorizedDefaultQos data structure shall remain valid.
4.2.6.3.4 Access traffic steering, switching and splitting support

If both the SMF and the PCF support the "ATSSS" feature, the PCF may enable the control of the PDU session level
Usage Monitoring information depending on what access type is used to carry service data flows.
When the PCF determines that at PDU session level different usage monitoring data shall be defined for the 3GPP and
the Non-3GPP access, the PCF shall include within the SessionRule data structure one reference to the
UsageMonitoringData policy decision to apply for the Non-3GPP access within the "refUmN3gData" attribute, and a
"umDecs" attribute containing the corresponding Usage Monitoring Data policy decisions if it has not been previously
provided. When the "refUmN3gData" is omitted, the attribute "refUmData" contains the reference to the
UsageMonitoringData policy decision to apply for both, 3GPP and Non-3GPP, accesses.
NOTE: To ensure that the traffic of a set of service data flows is excluded for both, the 3GPP access and Non-
3GPP access, from the PDU session level usage monitoring, the "exUsagePccRuleIds" attribute is set to
the same value within the Usage Monitoring Control decision referred by the "refUmN3gData" attribute
and within the Usage Monitoring Control decision referred by the "refUmData" attribute.
4.2.6.4 Policy control request triggers

The PCF may provide one or several policy control request trigger(s) to the SMF. In order to do so, the PCF shall
include one or several policy control request trigger(s) within the "policyCtrlReqTriggers" attribute(s) within the
SmPolicyDecision data structure.
During the lifetime of the PDU session, the PCF may update or remove the policy control request triggers. In order to
update the policy control request trigger, the PCF shall provide the new complete list of applicable policy control
request triggers by including one or several policy control request trigger(s) within the "policyCtrlReqTriggers"
attribute within the SmPolicyDecision data structure.
The PCF may remove all previously provided policy control request triggers by providing a "policyCtrlReqTriggers"
attribute set to the value NULL. Upon reception of a policy control request trigger with this value, the SMF shall not
inform PCF of any trigger except for those triggers that are always reported and do not require provisioning from the
PCF.
Whenever the PCF provisions one or several policy control request trigger(s) by using an HTTP POST message as
defined in subclause 4.2.3.2, unless otherwise specified in a policy control request trigger's value definition, the SMF
shall send the corresponding currently applicable values (e.g. access type, RAT type, user location information, etc.) to
the PCF within the UeCampingRep data structure in the response of the HTTP POST message, and in this case, the
"repPolicyCtrlReqTriggers" attribute shall not be included.
4.2.6.5 Encoding of the request of information reporting
4.2.6.5.1 Request of Access Network Charging Identifier

When the Access Network Charging Identifier is unknown for an AF session to the PCF, the PCF may request the SMF
to provide the Access Network Charging Identifier associated to the dynamic PCC rules. To do so, the PCF shall within
SmPolicyDecision data structure provide the "policyCtrlReqTriggers" attribute with the value "AN_CH_COR" if the
policy control request trigger is not previously set and the "lastReqRuleData" attribute. For the RequestedRuleData
instance, the PCF shall include the CH_ID within the "reqData" attribute and reference of the PCC rule within the
"refPccRuleIds" attribute.
The PCF shall interpret that the Access Network Charging Identifier is known when the PCF receives an "accNetChId"
attribute with the "sessionChScope" attribute included and set to true.
3GPP
Release 16 81 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.6.5.2 RAN NAS Cause Support

When RAN-NAS-Cause feature is supported, the PCF may request the SMF to inform it of the result of the PCC rule
removal when the PCF removes the PCC rule. In order to do so, the PCF shall additionally include the
"policyCtrlReqTriggers" attribute with RES_RELEASE if the policy control request trigger is not previously set and the
"lastReqRuleData" attribute. For the RequestedRuleData instance, the PCF shall include the RES_RELEASE within the
"reqData" attribute and reference of the removed PCC rule within the "refPccRuleIds" attribute.
NOTE: This is done to allow the PCF to notify the AF when there is an abnormal termination of the QoS flow.
The PCF does not have to retry the removal of these PCC Rules.
4.2.6.5.3 Provisioning of the Usage Monitoring Control Policy

The PCF may indicate the need to apply monitoring control for the accumulated usage of network resources on a PDU
session basis. Usage is defined as volume or time of user plane traffic. Monitoring for traffic volume and traffic time
can be performed in parallel. The data collection for usage monitoring control shall be performed per monitoring key,
which may apply for a single service data flow, a set of service data flows or for all the traffic in a PDU session. If the
usage monitoring of a PDU session level is enabled, the PCF may request the SMF to exclude a single service data flow
or a set of service data flows from the usage monitoring of PDU session level.
During the PDU session establishment, the PCF may receive information about total allowed usage per DNN and S-
NSSAI combination and UE from the UDR, i.e. the overall amount of allowed traffic volume and/or time of usage that
are to be monitored per DNN and S-NSSAI combination and UE and/or total allowed usage for Monitoring key(s) per
DNN and S-NSSAI combination and UE.
NOTE: It depends on the implementation of UDR to provide the total allowed usage per DNN and UE to
different PCFs if the different PCFs are serving the PDU sessions with same value of DNN and UE.
If the SMF supports the UMC feature, the PCF may request usage monitoring control for the PDU session. If at this
time, the PCF has not provided "US_RE" policy control request trigger to the SMF, the PCF shall include the
"policyCtrlReqTriggers" attribute with the value "US_RE" and provide it to the SMF as defined in subclause 4.2.6.4.
The PCF shall not remove the "US_RE" policy control request trigger while usage monitoring is still active in the SMF.
At PDU session establishment and modification, the PCF may provide the applicable thresholds, volume threshold, time
threshold or both volume threshold and time threshold, for each usage monitoring control instance to the SMF. To
provide the initial threshold for each usage monitoring control instance, the PCF shall include the threshold(s) within
the "umDecs" attribute within the SmPolicyDecision data structure.
The PCF may provide a monitoring time to the SMF for the usage monitoring control instance (s) and optionally specify
a subsequent threshold value for the usage after the monitoring time.
Threshold levels, monitoring time if applicable and inactive time if applicable for each usage monitoring control
instance may be provisioned within an entry of the "umDecs" attribute as follows:
- the total volume threshold within the "volumeThreshold" attribute if applicable;
- the uplink volume threshold within the "volumeThresholdUplink" attribute if applicable;
- the downlink volume threshold within the "volumeThresholdDownlink" attribute if applicable;
- the time threshold within the "timeThreshold" attribute if applicable;
. the total volume threshold after the monitoring time within the "nextVolThreshold" attribute if applicable;
- the uplink volume threshold after the monitoring time within the "nextVolThresholdUplink" attribute if
applicable;
- the downlink volume threshold after the monitoring time within the "nextVolThresholdDownlink" attribute if
applicable;
- the time threshold after the monitoring time within the "nextTimeThreshold" attribute if applicable;
- the monitoring time within the "monitoringTime" attribute if applicable;
- the inactive time within the "inactivityTime" attribute if applicable.
3GPP
Release 16 82 3GPP TS 29.512 V16.5.0 (2020-06)
If the usage monitoring control instance applies to the PDU session level, the PCF shall include the reference to the
Usage Monitoring Data decision within the "refUmData" attribute of a session rule.
If the usage monitoring control instance applies to a service data flow or a group of service data flows, the PCF shall
include the reference to the Usage Monitoring Data decision within the "refUmData" attribute of one or more PCC rule.
The PCF may provide one usage monitoring control instance applicable at PDU session level and one or more usage
monitoring instances applicable at PCC Rule level.
If the PDU session level usage monitoring is enabled and if the service data flow(s) need to be excluded from PDU
session level usage monitoring, the PCF shall include the corresponding PCC rule identifier(s) within the
"exUsagePccRuleIds" attribute of the UsageMonitoringData instance of PDU session level usage monitoring. If the
exclusion is enabled, the PCF may disable the exclusion again for the service data flow(s) by removing the
corresponding PCC rule identifier from "exUsagePccRuleIds" attribute.
If the PCF wishes to remove the threshold level for one or more monitoring keys, the PCF shall provide the
corresponding attribute with NULL value to the corresponding usage monitoring control instance.
When the SMF receives the usage monitoring control request above from the PCF, the SMF shall initiate the PFCP
Session Establishment Request as defined in subclause 7.5.2 or PFCP Session Modification Request as defined in
subclause 7.5.4 of 3GPP TS 29.244 [13] to request the UPF to perform the usage monitoring control.
When usage monitoring is enabled, the PCF may request the SMF to report accumulated usage for one or more enabled
usage monitoring control instance regardless if a usage threshold has been reached. In order do so, the PCF shall
include the "lastReqUsageData" attribute to contain one more reference(s) to usage monitoring data decision(s) within
the "refUmIds" attribute or contain the "allUmIds" set to true. The PCF shall only require SMF to report accumulated
usage for one or more enabled usage monitoring control instance(s) in a response of HTTP POST initiated by the SMF
when the SMF has not provided accumulated usage in the HTTP POST for the same usage monitoring control
instance(s).
Upon receiving the reported usage from the SMF, the PCF shall deduct the value of the usage report from the total
allowed usage for that PDU session, usage monitoring key, or both as applicable, and the PCF may also derive the PCC
rules based on the remaining allowed usage or reported usage and provision them to the SMF.
4.2.6.5.4 Request for Access Network Information

When the NetLoc feature is supported, if the AF requests the PCF to report the access network information as described
in subclauses 4.2.2, 4.2.3 or 4.2.4 of 3GPP TS 29.514 [17] or in subclauses 4.1 and 4.2 of 3GPP TS 29.214 [18], the
PCF shall perform the PCC rule provisioning procedure as defined in subclause 4.2.6.2.1 and additionally provide the
requested access network information indication (e.g. user location and/or user timezone information) to the SMF as
follows:
- it shall include the "lastReqRuleData" attribute to contain the "reqData" attribute with the value(s)
MS_TIME_ZONE and/or USER_LOC_INFO and the "refPccRuleIds" attribute to contain the related
installed/modified/removed PCC rule identifier(s).
- it shall provide the AN_INFO policy control request rigger within the "policyCtrlReqTriggers" attribute (if not
yet set).
For those PCC Rule(s) based on preliminary service information as described in 3GPP TS 29.514 [17] or in
3GPP TS 29.214 [18], the PCF may assign the 5QI and ARP of the default QoS flow to avoid signalling to the UE.
These PCC Rules shall not include the "packetFilterUsage" attribute set to true within the "flowInfos" attribute.
4.2.6.5.5 Request for the successful resource allocation notification

The PCF may request the SMF to confirm that the resources associated to a PCC rule are successfully allocated. To do
so the PCF shall within the SmPolicyDecision data structure provide the "policyCtrlReqTriggers" attribute with the
value "SUCC_RES_ALLO " if the policy control request trigger is not previously set and the "lastReqRuleData"
attribute. For the RequestedRuleData instance, the PCF shall include the "SUCC_RES_ALLO" within the "reqData"
attribute and the reference of the PCC rule within the "refPccRuleIds" attribute.
3GPP
Release 16 83 3GPP TS 29.512 V16.5.0 (2020-06)
4.2.6.5.6 Provisioning of Presence Reporting Area Information

When PRA feature is supported, the PCF may determine during the lifetime of the IP-CAN session whether reports for
change of UE presence in Presence Reporting Area(s) are desired for the PDU session based on the subscriber's profile
configuration. If the reporting is desired for the PDU session, the PCF shall provide the "praInfos" attribute within the
SmPolicyDecision data structure. Within each PresenceInfo data structure, the PCF shall include the Presence
Reporting Area Identifier within the "praId" attribute, and, for a UE-dedicated Presence Reporting Area, the list of
elements composing the presence reporting area within the "trackingAreaList" attribute, "ecgiList" attribute, "ncgiList"
attribute, and/or "globalRanNodeIdList" attribute. If PCF is configured with a Presence Reporting Area identifier
referring to the list of Presence Reporting Area Identifier(s) within a Set of Core Network predefined Presence
Reporting Areas as defined in 3GPP TS 23.501 [2], the PCF shall include the identifier of the Presence Reporting Area
set within the "praId" attribute. The PCF shall activate the reporting changes of UE presence in Presence Reporting
Area(s) by provisioning the "PRA_CH" policy control request trigger to the SMF.
NOTE 1: If this feature is not supported, the PCF can instead activate location change reporting that reports actual
location. Due to the potential increase in signalling load, careful consideration of the network load is
necessary for such reporting, e.g. limiting the number of subscribers' subject to such reporting.
NOTE 2: The Presence Reporting Area Identifier can correspond to a list of Presence Reporting Area Identifier(s)
within a set of Core Network predefined Presence Reporting Areas (PRA set identifier) as defined in
3GPP TS 23.501 [2].
The PCF may modify the list of PRA Identifier(s) by providing the new Presence Reporting Area or by removing
existing Presence Reporting Area(s) or modify the list(s) of Presence Reporting Area elements by providing the
updated Presence Reporting Area. In order to do that, the PCF shall follow the general procedure as defined in
subclause 4.2.6.1 and supply the Presence Reporting Area identifier(s) as the key(s) of the map.
The PCF may remove the policy control request trigger of change of UE presence in Presence Reporting Area as
defined in subclause 4.2.6.4, if previously activated.
If the "PRA_CH" policy control request trigger is provisioned, when the PCF provides a list of presence reporting areas
as described above, the PCF shall ensure that the maximum number of provisioned Presence Reporting Area Identifiers
is not exceeded. The maximum number of PRAs may be configured in the PCF. The PCF may have independent
configuration of the maximum number for Core Network pre-configured PRAs and UE-dedicated PRAs.
NOTE 3: For all the Presence Reporting Area(s) provided by the PCF, the SMF can store the Presence Reporting
Area Identifier(s) together with an indication that states that it relates to PCF requested PRA status
changes.
NOTE 4: This information is needed so that if both PCF and CHF request the reports of PRA status changes, the
SMF is able to differentiate whether the reported PRA changes are relevant to PCF or CHF.
The SMF shall invoke the Namf_EventExposure service in the AMF to handle the subscription to the presence state of a
UE in an area of interest as specified in 3GPP TS 29.518 [36].
The PCF may be notified during the lifetime of an PDU session that the UE is located in an access network where local
configuration indicates that the reporting change of UE presence in Presence Reporting Area is not supported. The PCF
may remove the policy control request trigger of the change of UE presence in Presence Reporting Area, if previously
activated. In this case, the PCF shall also remove the provisioned presence reporting areas by including the "praInfos"
attribute set to NULL within the SmPolicyDecision data structure.
The SMF shall de-activate the relevant PDU session specific procedure for reporting Change of UE presence in
Presence Reporting Area, when the PCF and CHF remove the request trigger of change of UE presence in Presence
Reporting Area.
4.2.6.5.7 Policy provisioning and enforcement of reflective QoS

If the PCF receives the "refQosIndication" attribute set to true as defined in subclauses 4.2.2.2 or 4.2.4.2, and if the PCF
determines that Reflective QoS Control will be enabled for the PDU session based on the operator's policy and user
subscriptions, the PCF may provision the Reflective QoS Timer by including the "reflectiveQoSTimer" attribute within
the SmPolicyDecision data structure in the response message.
The provisioning of reflective QoS may be performed for service data flows associated with one or more PCC rules,
and shall be performed using the PCC rule provisioning procedure. The PCF may within a QoS data decision which a
3GPP
Release 16 84 3GPP TS 29.512 V16.5.0 (2020-06)
PCC rule refer to include the "reflectiveQos" attribute set to true to enable the Reflective QoS control to a non-GBR
downlink service data flow when the PCF authorizes the QoS for the service data flow as defined in subclause 4.2.6.6.2.
The PCF shall ensure that both, uplink and downlink traffic for such non-GBR service data flow are allowed.
NOTE 1: The PCF can allow both uplink and downlink traffic for the non-GBR service data flow in several ways,
e.g. by installing a PCC rule with uplink and downlink flow information, or by installing separate PCC
rules for the uplink flows and downlink flows, or by installing a PCC rule with only the application
identifier.
The PCF shall activate the reporting changes of reflective QoS indication by provisioning the "REF_QOS_IND_CH"
policy control request trigger to the SMF.
NOTE 2: While the UE applies a standardized value for the precedence of all UE derived QoS rules, PCC rules
precedence values can vary and PCF configuration has to ensure that there is a large enough value range
for the precedence of PCC rules corresponding to UE derived QoS rules. To avoid that the precedence of
network provided QoS rules need to be changed when Reflective QoS is activated and filters are
overlapping, the PCF will take the standardized value for the precedence of UE derived QoS rules into
account and will setting the precedence value of PCC rules subject to Reflective QoS to a value in the
range from 70 to 99 (decimal), as specified in 3GPP TS 24.501 [20], subclause 6.2.5.1.1.3.
The SMF shall apply reflective QoS control for the downlink traffic of the service data flows of the PCC rules that
reference a QosData decision that includes "reflectiveQos" attribute set to true.
The PCF shall not include the "reflectiveQos" attribute set to true within the QoS data decision which the PCC rule with
match-all SDF template refers to. If a PCC rule with match-all SDF template has been provisioned to the SMF, the PCF
shall not include the "reflectiveQos" attribute within the QoS data decision which contains the "defQosFlowIndication"
attribute, either.
If the PCF receives the "refQosIndication" attribute set to false as defined in subclause 4.2.4.2, the PCF shall disable the
reflective QoS Control for the PDU session. In order to do so, the PCF shall within the QoS data decision which
affected PCC rule refer to include the "reflectiveQos" attribute set to false and may update other QoS parameters within
the QoS data decision and/or update the flow information of PCC rule by including the "packetFilterUsage" attribute set
to true.
4.2.6.6 Authorized QoS
4.2.6.6.1 General
The PCF shall provision the authorized QoS. The authorized QoS may apply to a PCC rule or to a PDU session.
- When the authorized QoS applies to a PCC rule, it shall be provisioned within the corresponding PCC rule as
- When the authorized QoS for a PCC rule with a GBR QCI is candidate for resource sharing an instruction on the
allowed sharing may be provisioned as defined in subclause 4.2.6.2.8.
- When the authorized QoS applies to a PDU session, it shall be provisioned as defined in subclause 4.2.6.3.1.
- When the authorized QoS applies to the default QoS flow, it shall be provisioned as defined in
- When the authorized QoS applies to an explicitly signalled QoS Characteristics, it shall be provisioned as
- When the authorized QoS applies to the Reflective QoS, it shall be provisioned as defined in subclause 4.2.6.5.7.
The authorized QoS provides appropriate values for the resources to be enforced. The authorized QoS for a PCC rule is
a request for allocating the corresponding resources. The Provisioning of authorized QoS per PCC rule is a part of PCC
rule provisioning procedure.
If the SMF cannot allocate any of the resources as authorized by the PCF, the SMF informs the PCF and acts as
described in subclauses 4.2.3.16 and 4.2.4.15.
3GPP
Release 16 85 3GPP TS 29.512 V16.5.0 (2020-06)
The SMF shall interact with the (R)AN, UPF and UE for enforcing the policy based authorization.
QoS authorization information may be dynamically provisioned by the PCF or it may be a pre-defined PCC rule in the
SMF. Moreover, all the parameters of the authorized QoS may be changed.
NOTE 1: A change of 5QIs cannot be described as an upgrade or downgrade and also no 5QI can be referred to as
the higher or lower. Whether the 5QI is permitted to be changed or not is subject to both operator policies
and normal restrictions on changing from a non-GBR 5QI value to GBR 5QI value on an IP flow.
NOTE 2: All attributes of the ARP QoS parameter can be changed but only the ARP priority level represents an
ordered range of values. The ARP priority level attribute represents the actual priority for the service/user
with the value 1 as the highest and can thus be upgraded and downgraded.
If the PCF is unable to make a decision for the response to the HTTP POST message by the SMF, the PCF may reject
the request as described in subclause 5.7.
4.2.6.6.2 Policy provisioning and enforcement of authorized QoS per service data flow
The Provisioning of authorized QoS per service data flow is a part of PCC rule provisioning procedure, as described in
The authorized QoS per service data flow shall be provisioned within a QosData data structure. The PCF shall include a
"qosDecs" attribute containing the corresponding QoS data decision within the SmPolicyDecision data structure and
include the reference to this QoS data decision within the "refQosData" attribute of the PccRule data instance.
Within the QoS data decision, for 5QI of GBR type or delay critical GBR type, the PCF shall include the authorized
GBR 5QI or delay critical GBR 5QI respectively within the "5qi" attribute, the ARP within the "arp" attribute, and max
bandwidth in uplink within the "maxbrUl" attribute and/or max bandwidth in downlink within the "maxbrDl" attribute,
the guaranteed bandwidth in uplink within the "gbrUl" attribute and/or the guaranteed bandwidth in downlink within the
"gbrDl" attribute. If the PCF determines that the application traffic can be adapted to the change in the QoS based on the
configuration (e.g. if the AF is capable to trigger rate adaptation), the PCF may request a notification when authorized
GBR or delay critical GBR cannot be guaranteed or can be guaranteed again by including the "qnc" attribute set to true.
Within the QoS data decision, for 5QI of non-GBR type, the PCF shall include the authorized non-GBR 5QI within the
"5qi" attribute and the ARP within the "arp" attribute. The PCF may authorize the max bandwidth in uplink within the
"maxbrUl" attribute and/or max bandwidth in downlink within the "maxbrDl" attribute.
When the PCF authorizes a standardized 5QI but a Priority Level, an Averaging Window and/or a Maximum Data Burst
Volume which are different from the standardized value in the table 5.7.4-1 of 3GPP TS 23.501 [2] are required, the
PCF shall include the Priority Level within the "priorityLevel" attribute, the Averaging Window within the
"averWindow" attribute and/or the Maximum Data Burst Volume within the "maxDataBurstVol" attribute or the
"extMaxDataBurstVol" attribute (if supported, see subclause 4.2.2.1).
NOTE 1: For the non-standardized or non-configured 5QI, the PCF needs to authorize explicitly signalled QoS
Characteristics associated with the 5QI if the PCF has not provisioned it.
If the configured policy allows at reception of the service information from the AF and the application of the rules of
the QoS mapping procedures defined in 3GPP TS 29.513 [7] subclause 7.3.2 for the received service information result
in a 5QI of 1 associated with the corresponding flows, and the RAN-Support-Info feature as defined subclause 5.8 is
supported, the PCF shall determine the Maximum Packet Loss Rate for UL and DL for those flows associated within
5QI of 1. In this case, the PCF shall include the value of Maximum Packet Loss Rate for UL within the
"maxPacketLossRateUl" attribute and/or the value of Maximum Packet Loss Rate for DL within the
"maxPacketLossRateDl" attribute.
NOTE 2: If CHEM feature is supported, then PCF as described in subclause 7.2.3 of 3GPP TS 29.513 [7] or based
on local configuration, the PCF sets the downlink and uplink maximum packet loss rates corresponding to
either the most robust codec mode or the least robust codec mode of the negotiated set in each direction.
If the PCF wants to ensure that a PCC Rule is always bound to the default QoS flow, the policy provisioning for the
related authorized QoS shall be done as described in subclause 4.2.6.2.10.
The SMF shall perform a QoS flow binding based on the QoS information within the Qos data decision as defined in
subclause 6.4 of 3GPP TS 29.513 [7] after the SMF installs or activates the PCC rules.
3GPP
Release 16 86 3GPP TS 29.512 V16.5.0 (2020-06)
The SMF shall reserve the resources necessary for the guaranteed bitrate for the PCC rule upon receipt of a PCC rule
provisioning including QoS information. For GBR QoS flows the SMF should set the QoS flow's GBR to the sum of
the GBRs of all PCC rules that are active/installed and bound to that GBR QoS flow. For GBR QoS flow the SMF
should set the QoS flow's MBR to the sum of the MBRs of all PCC rules that are active/installed and bound to that
GBR QoS flow.
NOTE 3: Since the PCF controls the GBR value in the PCC rule, the PCF can prevent that uplink GBR resources
are reserved by providing an uplink GBR value of zero for that PCC rule This may be useful e.g. for a
PCC rule with application identifier as the uplink traffic can be received in other QoS flow than the one
the PCC rule is bound to.
The SMF shall assign a QFI if a new QoS flow needs to be established and shall derive, if applicable, the QoS profile
required towards the Access Network, the QoS rule required towards the UE and the QoS information with PDRs
towards to the UPF. If multiple PCC rules with the Maximum Packet Loss Rate for UL and DL are bound to the same
QoS flow, the SMF shall choose the lowest value per direction related to the PCC rules within the QoS profile towards
to the access network.
If one or more of the 5QI, ARP, QNC, Priority level, Averaging Window and Maximum Data Burst Volume attributes
of a PCC rule are modified to the same updated values for all the PCC rules bound to the same QoS flow, then the SMF
should modify the corresponding attributes for that impacted QoS flow.
Upon deactivation or removal of a PCC rule, the SMF shall free the resources reserved for that PCC rule, and initiate
the corresponding procedure with access network, UE and UPF to remove the resources.
4.2.6.6.3 Policy provisioning and enforcement of authorized explicitly signalled QoS

Characteristics
The PCF may provision a dynamically assigned 5QI value (from the non-standardized and non-preconfigured value
range) and the associated 5G QoS characteristics to the SMF. In order to do so, the PCF shall within the
SmPolicyDecision data structure include the "qosChars" attribute to contain one more authorized signalled
QosCharacteristics instances. For each QosCharacteristics instance, the PCF shall include assigned 5QI value within the
"5qi" attribute, resource type value within the "resourceType" attribute, the 5QI Priority Level value within the
"priorityLevel" attribute, the Packet Delay Budget value within the "packetDelayBudget" attribute, Packet Error Rate
value within the "packetErrorRate" attribute, the Averaging Window value within the "averagingWindow" attribute if
applicable and the Maximum Data Burst Volume value within the "maxDataBurstVol" attribute or the
"extMaxDataBurstVol" attribute (if supported, see subclause 4.2.2.1) if applicable. If the PCF has provisioned an
authorized signalled QosCharacteristics instance to the SMF, the PCF shall not update nor remove it during the lifetime
of the policy association.
Upon receiving the authorized explicitly signalled QoS characteristics, the SMF shall derive the QoS profile towards the
access network and provide it to the access network by invoking corresponding procedure.
4.2.7 Detection and handling of late arriving requests
4.2.7.1 Handling of requests which collide with an existing SM Policy Association

The PCF may receive an Originating Time Stamp parameter within the 3gpp-Sbi-Origination-Timestamp header, which
is set by the AMF, by the Npcf_SMPolicyControl_Create service request.
NOTE 1: The SMF forwards the Origination Time Stamp to the PCF, when received from the AMF to allow the
handling of colliding requests at the PCF based on network conditions.
Upon receipt of a Npcf_SMPolicyControl_Create service request which collides with an existing SM Policy
Association for the same UE (i.e. same values of "supi" attribute) and the same PDU session Id (i.e. same values of
"pduSessionId" attribute), the PCF shall accept the new request only if it contains a more recent timestamp within the
3gpp-Sbi-Origination-Timestamp header than the origination timestamp stored for the existing SM Policy Association.
An incoming Npcf_SMPolicyControl_Create service request shall be considered as more recent than an existing SM
Policy Association and be accepted if no 3gpp-Sbi-Origination-Timestamp header was provided for at least one of the
two SM Policy Associations. The PCF shall reject an incoming request whose timestamp is less recent than the
timestamp of the existing SM Policy Association with the HTTP status code "403 Forbidden" and the application error
"LATE_OVERLAPPING_REQUEST".
3GPP
Release 16 87 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE 2: When the PCF accepts the new request that contains a more recent timestamp within the 3gpp-Sbi-
Origination-Timestamp header than the timestamp stored for the SM Policy Association, the PCF
performs implementation specific, e.g. locally deletes the existing Individual SM Policy Association.
5 Npcf_SMPolicyControl Service API
5.1 Introduction
The Npcf_SMPolicyControl Service shall use the Npcf_SMPolicyControl API.
The API URI of the Npcf_SMPolicyControl API shall be:
{apiRoot}/<apiName>/<apiVersion>/
The request URIs used in HTTP request from the NF service consumer towards the PCF shall have the Resource URI
structure defined in subclause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>
with the following components:
- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
- The <apiName> shall be "npcf-smpolicycontrol".
- The <apiVersion> shall be "v1".
- The <{apiSpecificResourceUriPart> shall be set as described in subclause 5.3.
5.2 Usage of HTTP

5.2.1 General
HTTP/2, IETF RFC 7540 [8], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2, shall be transported as specified in subclause 5.3 of 3GPP TS 29.500 [4].
An OpenAPI [10] specification of HTTP messages and content bodies for the Npcf_SMPolicyControl is contained in
Annex A.
5.2.2 HTTP standard headers
5.2.2.1 General
See subclause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
5.2.2.2 Content type

JSON, IETF RFC 8259 [9], shall be used as content type of the HTTP bodies specified in the present specification as
specified in subclause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type
"application/json".
"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and
shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [31].
3GPP
Release 16 88 3GPP TS 29.512 V16.5.0 (2020-06)
5.2.3 HTTP custom headers
5.2.3.1 General
The mandatory HTTP custom header fields specified in subclause 5.2.3.2 of 3GPP TS 29.500 [4] shall be applicable.
5.2.3.2 3gpp-Sbi-Origination-Timestamp
The header contains the date and time (with a millisecond granularity) when the originating entity initiated the request
as specified in subclause 6.1.2.3.2 of 3GPP TS 29.502 [22].
5.3 Resources
5.3.1 Resource Structure
{apiRoot}/npcf-smpolicycontrol/v1
/sm-policies
/{smPolicyId}
/update
/delete
Figure 5.3.1-1: Resource URI structure of the Npcf_SMPolicyControl API
Table 5.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 5.3.1-1: Resources and methods overview
HTTP method or
Resource name Resource URI Description
custom operation
POST Create a new Individual SM Policies
{apiRoot}/
resource for an SUPI or for a PEI and
SM Policies npcf-smpolicycontrol/
PDU Session ID and PDU Session ID
v1/sm-policies
supplied by the SMF.
{apiRoot}/ GET Read the Individual SM Policies
npcf-smpolicycontrol/ resource.
v1/sm-policies/{smPolicyId}
{apiRoot}/ delete Delete the Individual SM Policies
npcf-smpolicycontrol/v1/ (POST) resource.
Individual SM Policy
sm-policies/{smPolicyId}/delete
update Update the Individual SM Policies
{apiRoot}/
(POST) resource when a policy control
npcf-smpolicycontrol/v1/
request event is met or an error of
sm-policies/{smPolicyId}/update
policy enforcement occurs.
3GPP
Release 16 89 3GPP TS 29.512 V16.5.0 (2020-06)
5.3.2 Resource: SM Policies
5.3.2.1 Description
This resource represents the collection of the individual SM Policies created in the PCF.
5.3.2.2 Resource definition

Resource URI: {apiRoot}/npcf-smpolicycontrol/v1/sm-policies
This resource shall support the resource URI variables defined in table 5.3.2.2-1.
Table 5.3.2.2-1: Resource URI variables for this resource
Name Data type Definition

apiRoot string See subclause 5.1
5.3.2.3 Resource Standard Methods
5.3.2.3.1 POST
This method shall support the URI query parameters specified in table 5.3.2.3.1-1.
Table 5.3.2.3.1-1: URI query parameters supported by the POST method on this resource
Name Data type P Cardinality Description

n/a
This method shall support the request data structures specified in table 5.3.2.3.1-2 and the response data structures and
response codes specified in table 5.3.2.3.1-3.
Table 5.3.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type P Cardinality Description

SmPolicyContextData M 1 Parameters to create an individual SM policies resources.
Table 5.3.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type P Cardinality Response Description

codes
SMPolicyDecision M 1 201 Created An individual SM Policy resources for the SUPI and PDU
session id are created successfully.
ProblemDetails O 0..1 400 Bad Request (NOTE 2)
ProblemDetails O 0..1 403 Forbidden (NOTE 2)
n/a 308 Permanent The URI of the PCF within the existing PCF binding
Redirect information stored in the BSF for the indicated combination
is returned in the non-roaming or home-routed scenario.
(NOTE 3)
NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of
3GPP TS 29.500 [4] shall also apply.
NOTE 2: Failure cases are described in subclause 5.7.
NOTE 3：Only applicable to the "SamePcf" feature as defined in subclause 5.8.
3GPP
Release 16 90 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.3.2.3.1-4: Headers supported by the 201 Response Code on this resource

Location string M 1 Contains the URI of the newly created resource, according to
the structure: {apiRoot}/npcf-smpolicycontrol/v1/sm-
policies/{smPolicyId}
Table 5.3.2.3.1-5: Headers supported by the 308 Response Code on this resource

Location string M 1 Contains the URI of the PCF within the existing PCF binding
information stored in the BSF for the indicated combination.
5.3.2.4 Resource Custom Operations

None.
5.3.3 Resource: Individual SM Policy
5.3.3.1 Description
The individual SM Policy resource represents an individual SM Policy created in the PCF and associated with the SUPI
and PDU session ID.
5.3.3.2 Resource definition

Resource URI: {apiRoot}/npcf-smpolicycontrol/v1/sm-policies/{smPolicyId}
This resource shall support the resource URI variables defined in table 5.3.3.2-1.
Table 5.3.3.2-1: Resource URI variables for this resource
Name Data type Definition

apiRoot string See subclause 5.1
smPolicyId string Unique identifier of the individual SM Policy resource.
5.3.3.3 Resource Standard Methods
5.3.3.3.1 GET
This method shall support the URI query parameters specified in table 5.3.3.3.1-1.
Table 5.3.3.3.1-1: URI query parameters supported by the GET method on this resource

n/a
This method shall support the request data structures specified in table 5.3.3.3.1-2 and the response data structures and
response codes specified in table 5.3.3.3.1-3.
Table 5.3.3.3.1-2: Data structures supported by the GET Request Body on this resource

n/a
3GPP
Release 16 91 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.3.3.3.1-3: Data structures supported by the GET Response Body on this resource
Data type P CardinalityResponse codes Description

SmPolicyControl M 1 200 OK An individual SM Policy resources for the SUPI and
PDU session id are returned successfully.
NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4]
shall also apply.
5.3.3.4 Resource Custom Operations
5.3.3.4.1 Overview
Table 5.3.3.4.1-1: Custom operations
Operation Name Custom operation URI Mapped HTTP method Description

delete {apiRoot}/ POST Delete an individual SM Policy resource.
npcf-smpolicycontrol/
v1/sm-
policies/{smPolicyId}/delete
update {apiRoot}/ POST Update an individual SM Policy
npcf-smpolicycontrol/ resource.
v1/sm-
policies/{smPolicyId}/update
5.3.3.4.2 Operation: delete
5.3.3.4.2.1 Description
5.3.3.4.2.2 Operation Definition
This custom operation deletes an individual SM Policy resource in the PCF.
This operation shall support the request data structures specified in table 5.3.3.4.2.2-1 and the response data structure
and response codes specified in table 5.3.3.4.2.2-2.
Table 5.3.3.4.2.2-1: Data structures supported by the POST Request Body on this resource

SmPolicyDeleteData O 0..1 Parameters to be sent by the SMF when the individual SM policy is
deleted.
Table 5.3.3.4.2.2-2: Data structures supported by the POST Response Body on this resource
Data type P Cardinality Response codes Description

n/a 204 No Content This case represents a successful deletion of the
individual SM policy resource.
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of
5.3.3.4.3 Operation: update
5.3.3.4.3.1 Description
5.3.3.4.3.2 Operation Definition
This custom operation updates an individual SM Policy resource in the PCF.
3GPP
Release 16 92 3GPP TS 29.512 V16.5.0 (2020-06)
This operation shall support the request data structures specified in table 5.3.3.4.3.2-1 and the response data structure
and response codes specified in table 5.3.3.4.3.2-2.
Table 5.3.3.4.3.2-1: Data structures supported by the POST Request Body on this resource

SmPolicyUpdateContextData M 1 Parameters to be sent by the SMF when the individual SM policy
is updated. It indicates the occurred changes.
Table 5.3.3.4.3.2-2: Data structures supported by the POST Response Body on this resource

SmPolicyDecision M 1 200 OK An individual SM Policy resources is updated
successfully. Response body includes the policy
decision changes.
ProblemDetails O 0..1 400 Bad Request (NOTE 2)
ProblemDetails O 0..1 403 Forbidden (NOTE 2)
NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4]
shall also apply.
5.4 Custom Operations without associated resources

None.
5.5 Notifications
5.5.1 General
Table 5.5.1-1: Notifications
Notification Custom operation URI Mapped HTTP method Description

Policy Update {notificationUri}/update POST Policy Update Notification.
Notification
Request for {notificationUri}/terminate POST Request for termination of the policy
termination of the association.
policy association
5.5.2 Policy Update Notification
5.5.2.1 Description
This notification is used by the PCF to update the policy.
5.5.2.2 Operation Definition

This operation shall support the request data structures specified in table 5.5.2.2-1 and the response data structure and
response codes specified in table 5.5.2.2-2.
Table 5.5.2.2-1: Data structures supported by the POST Request Body on this resource

SmPolicyNotification M 1 Update the SM policies provided by the PCF
3GPP
Release 16 93 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.5.2.2-2: Data structures supported by the POST Response Body on this resource

n/a 204 No Content The SM policies are updated successfully.
UeCampingRep O 0..1 200 OK The current applicable values corresponding to
the policy control request trigger is reported.
array(PartialSuccessRepo O 1..N 200 OK Some of the PCC rules and/or session rule
rt) provisioned by the PCF are not installed/activated
successfully.
ErrorReport M 1 400 Bad Request The SM policies including all the PCC rules and
session rules provisioned by the PCF are not
installed/activated successfully.
array(PolicyDecisionFailur O 1..N 200 OK Provisioning of some of the policy decision and/
eCode) condition data which are not referred by any PCC
rules or session rule are failure.
NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of
5.5.3 Request for termination of the policy association
5.5.3.1 Description
This notification is used by the PCF to request the termination of a policy association.
5.5.3.2 Operation Definition

This operation shall support the request data structures specified in table 5.5.3.2-1 and the response data structure and
response codes specified in table 5.5.3.2-2.
Table 5.5.3.2-1: Data structures supported by the POST Request Body on this resource

TerminationNotification M 1 Request to terminate the policy association.
Table 5.5.3.2-2: Data structures supported by the POST Response Body on this resource

n/a 204 No Content The request for policy association termination was
received.
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of
5.6 Data Model

5.6.1 General
This subclause specifies the application data model supported by the API.
The Npcf_SMPolicyControl API allows the SMF to retrieve the session management related policy from the PCF as
defined in 3GPP TS 23.503 [6].
Table 5.6.1-1 specifies the data types defined for the Npcf_SMPolicyControl service based interface protocol.
3GPP
Release 16 94 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.6.1-1: Npcf_SMPolicyControl specific Data Types
Data type Section defined Description Applicability

5GSmCause 5.6.3.2 Indicates the 5GSM cause code value. RAN-NAS-
Cause
AdditionalAccessInfo 5.6.2.43 Indicates the combination of additional Access ATSSS
Type and RAT Type for MA PDU session
AccNetChargingAddress 5.6.2.35 Identifies the address of the network node
performing charging and used for charging
applications.
AccNetChId 5.6.2.23 Contains the access network charging identifier
for the PCC rule(s) or whole PDU session.
AccuUsageReport 5.6.2.18 Contains the accumulated usage report UMC
information.
AfSigProtocol 5.6.3.10 Indicates the protocol used for signalling between ProvAFsignalFl
the UE and the AF. ow
AppDetectionInfo 5.6.2.22 Contains the detected application's traffic ADC
information.
ApplicationDescriptor 5.6.3.2 Defines the Application Descriptor for an ATSSS ATSSS
rule.
AtsssCapability 5.6.3.26 Contains the ATSSS capability supported for the ATSSS
MA PDU Session.
AuthorizedDefaultQos 5.6.2.34 Authorized Default QoS.
BridgeManagementContainer 5.6.2.47 Contains the TSN BMIC. TimeSensitive
Networking
ChargingData 5.6.2.11 Contains charging related parameters.
ChargingInformation 5.6.2.17 Contains the addresses of the charging functions.
ConditionData 5.6.2.9 Contains conditions for applicability of a rule.
CreditManagementStatus 5.6.3.16 Indicates the reason of the credit management
session failure.
ErrorReport 5.6.2.36 Contains the rule reports.
FailureCause 5.6.3.14 Indicates the cause of the failure in a Partial
Success Report.
FailureCode 5.6.3.9 Indicates the reason of the PCC rule failure.
FlowDescription 5.6.3.2 Defines a packet filter for an IP flow.
FlowDirection 5.6.3.3 Indicates the direction of the service data flow.
FlowDirectionRm 5.6.3.15 This data type is defined in the same way as the
"FlowDirection" data type, but allows null value.
FlowInformation 5.6.2.14 Contains the flow information.
IpMulticastAddressInfo 5.6.2.46 Contains the IP multicast addressing information WWC
MaPduIndication 5.6.3.25 Contains the MA PDU session indication, i.e., MA ATSSS
PDU Request or MA PDU Network-Upgrade
Allowed.
MeteringMethod 5.6.3.5 Indicates the metering method.
MulticastAccessControl 5.6.3.20 Indicates whether the service data flow, WWC
corresponding to the service data flow template, is
allowed or not allowed.
NetLocAccessSupport 5.6.3.27 Indicates the access network support of the report NetLoc
of the requested access network information.
PacketFilterContent 5.6.3.2 Defines a packet filter for an IP flow.
PacketFilterInfo 5.6.2.30 Contains the information from a single packet filter
sent from the SMF to the PCF.
PartialSuccessReport 5.6.2.33 Includes the information reported by the SMF
when some of the PCC rules and/or session rules
are not successfully installed/activated.
PccRule 5.6.2.6 Contains the PCC rule information.
PduSessionRelCause 5.6.3.24 Contains the SMF PDU Session release cause. PDUSessionR
elCause
PolicyControlRequestTrigger 5.6.3.6 Contains the policy control request trigger(s).
PolicyDecisionFailureCode 5.6.3.28 Indicates the type of the failed policy decision PolicyDecision
and/or condition data. ErrorHandling
PortManagementContainer 5.6.2.45 Contains the TSN port management information TimeSensitive
container for a TSN port. Networking
QosCharacteristics 5.6.2.16 Contains QoS characteristics for a non-
standardized or non-configured 5QI.
QosData 5.6.2.8 Contains the QoS parameters.
QosFlowUsage 5.6.3.13 Indicates a QoS flow usage information.
3GPP
Release 16 95 3GPP TS 29.512 V16.5.0 (2020-06)
QosMonitoringData 5.6.2.40 Contains QoS monitoring related control QosMonitoring

information.
QosMonitoringReport 5.6.2.42 Contains QoS monitoring reporting information. QosMonitoring
QosNotificationControlInfo 5.6.2.32 Contains the QoS Notification Control Information.
RanNasRelCause 5.6.2.28 Contains the RAN/NAS release cause. RAN-NAS-
Cause
RedirectAddressType 5.6.3.12 Indicates the redirect address type.
RedirectInformation 5.6.2.13 Contains the redirect information.
ReportingFrequency 5.6.3.22 Indicates the frequency for the reporting QosMonitoring
ReportingLevel 5.6.3.4 Indicates the reporting level.
RequestedQos 5.6.2.31 Contains the QoS information requested by the
UE.
RequestedQosMonitoringPar 5.6.3.21 Indicates the requested QoS monitoring QosMonitoring
ameter parameters to be measured.
RequestedRuleData 5.6.2.24 Contains rule data requested by the PCF to
receive information associated with PCC rules.
RequestedRuleDataType 5.6.3.7 Contains the type of rule data requested by the
PCF.
RequestedUsageData 5.6.2.25 Contains usage data requested by the PCF
requesting usage reports for the corresponding
usage monitoring data instances.
RuleOperation 5.6.3.11 Indicates a UE initiated resource operation that
causes a request for PCC rules.
RuleReport 5.6.2.27 Reports the status of PCC.
RuleStatus 5.6.3.8 Indicates the status of PCC or session rule.
ServingNfIdenty 5.6.2.38 Contains the serving Network Function identity.
SessionRule 5.6.2.7 Contains session level policy information.
SessionRuleFailureCode 5.6.3.17 Indicates the reason of the session rule failure.
SessionRuleReport 5.6.2.37 Reports the status of session rule.
SmPolicyAssociationRelease 5.6.3.23 Represents the cause why the PCF requests the
Cause termination of the SM policy association.
SmPolicyControl 5.6.2.2 Contains the parameters to request the SM
policies and the SM policies authorized by the
PCF.
SmPolicyContextData 5.6.2.3 Contains the parameters to create individual SM
policy resource.
SmPolicyDecision 5.6.2.4 Contains the SM policies authorized by the PCF.
SmPolicyNotification 5.6.2.5 Contains the update of the SM policies.
SmPolicyDeleteData 5.6.2.15 Contains the parameters to be sent to the PCF
when the individual SM policy is deleted.
SmPolicyUpdateContextData 5.6.2.19 Contains the met policy control request trigger(s)
and corresponding new value(s) or the error
report of the policy enforcement.
SteeringFunctionality 5.6.3.18 Indicates functionality to support traffic steering, ATSSS
switching and splitting determined by the PCF.
SteeringMode 5.6.2.39 Contains the steering mode value and parameters ATSSS
determined by the PCF.
SteeringModeValue 5.6.3.19 Indicates the steering mode value determined by ATSSS
the PCF.
TerminationNotification 5.6.2.21 Termination Notification.
TrafficControlData 5.6.2.10 Contains parameters determining how flows
associated with a PCCRule are treated (blocked,
redirected, etc).
TsnBridgeInfo 5.6.2.41 Contains parameters that describe and identify TimeSensitive
the TSN bridge. Networking
TsnPortNumber 5.6.3.2 Contains a TSN port number. TimeSensitive
Networking
UeCampingRep 5.6.2.26 Contains the current applicable values
corresponding to the policy control request
triggers.
UeInitiatedResourceRequest 5.6.2.29 Indicates a UE requests specific QoS handling for
selected SDF.
UpPathChgEvent 5.6.2.20 Contains the UP path change event subscription TSC
from the AF.
UsageMonitoringData 5.6.2.12 Contains usage monitoring related control UMC
information.
3GPP
Release 16 96 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.6.1-2 specifies data types re-used by the Npcf_SMPolicyControl service based interface protocol from other
specifications, including a reference to their respective specifications and when needed, a short description of their use
within the Npcf_SMPolicyControl service based interface.
3GPP
Release 16 97 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.6.1-2: Npcf_SMPolicyControl re-used Data Types
Data type Reference Comments Applicability

5GMmCause 3GPP TS 29.571 [11] Contains the cause value of 5GMM protocol. RAN-NAS-
Cause
5Qi 3GPP TS 29.571 [11] Unsigned integer representing a 5G QoS Identifier
(see subclause 5.7.2.1 of 3GPP TS 23.501 [2]),
within the range 0 to 255.
5QiPriorityLevel 3GPP TS 29.571 [11] Unsigned integer indicating the 5QI Priority Level
(see subclauses 5.7.3.3 and 5.7.4 of
3GPP TS 23.501 [2]), within the range 1 to 127.
Values are ordered in decreasing order of priority,
i.e. with 1 as the highest priority and 127 as the
lowest priority.
5QiPriorityLevelRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"5QiPriorityLevel" data type, but with the OpenAPI
"nullable: true" property.
AccessType 3GPP TS 29.571 [11] The identification of the type of access network.
AccessTypeRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"AccessType" data type, but with the OpenAPI
Ambr 3GPP TS 29.571 [11] Session AMBR.
AnGwAddress 3GPP TS 29.514 [17] Carries the control plane address of the access
network gateway. (NOTE 1)
ApplicationChargingId 3GPP TS 29.571 [11] Application provided charging identifier allowing AF_Charging_
correlation of charging information. Identifier
Arp 3GPP TS 29.571 [11] ARP.
AverWindow 3GPP TS 29.571 [11] Averaging Window.
AverWindowRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"AverWindow" data type, but with the OpenAPI
Bytes 3GPP TS 29.571 [11] String with format "byte". TimeSensitive
Networking
BitRate 3GPP TS 29.571 [11] String representing a bit rate that shall be
formatted as follows:
pattern: "^\d+(\.\d+)?
(bps|Kbps|Mbps|Gbps|Tbps)$"
Examples:
"125 Mbps", "0.125 Gbps", "125000 Kbps".
BitRateRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"BitRate" data type, but with the OpenAPI
ChargingId 3GPP TS 29.571 [11] Charging identifier allowing correlation of charging
information.
ContentVersion 3GPP TS 29.514 [17] Indicates the content version of a PCC rule. It RuleVersionin
uniquely identifies a version of the PCC rule as g
DateTime 3GPP TS 29.571 [11] String with format "date-time" as defined in
OpenAPI Specification [10].
DateTimeRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"DateTime" data type, but with the OpenAPI
DddTrafficDescriptor 3GPP TS 29.571 [11] Traffic Descriptor DDNEventPoli
cyControl
DnaiChangeType 3GPP TS 29.571 [11] Describes the types of DNAI change.
Dnn 3GPP TS 29.571 [11] The DNN the user is connected to.
DnnSelectionMode 3GPP TS 29.502 [22] DNN selection mode. DNNSelection
Mode
DurationSec 3GPP TS 29.571 [11] Identifies a period of time in units of seconds.
DurationSecRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"DurationSec" data type, but with the OpenAPI
EthFlowDescription 3GPP TS 29.514 [17] Defines a packet filter for an Ethernet flow.
(NOTE 2)
ExtMaxDataBurstVol 3GPP TS 29.571 [11] Maximum Data Burst Volume. EMDBV
3GPP
Release 16 98 3GPP TS 29.512 V16.5.0 (2020-06)
ExtMaxDataBurstVolRm 3GPP TS 29.571 [11] This data type is defined in the same way as the EMDBV
"ExtMaxDataBurstVol" data type, but with the
OpenAPI "nullable: true" property.
FinalUnitAction 3GPP TS 32.291 [19] Indicates the action to be taken when the user's
account cannot cover the service cost.
FlowStatus 3GPP TS 29.514 [17] Describes whether the IP flow(s) are enabled or
disabled. The value "REMOVED" is not applicable
to Npcf_SMPolicyControl service.
Gpsi 3GPP TS 29.571 [11] Identifies a GPSI.
GroupId 3GPP TS 29.571 [11] Identifies a group of internal globally unique ID.
Guami 3GPP TS 29.571 [11] Globally Unique AMF Identifier.
IpIndex 3GPP TS 29.519 [15] Information that identifies which IP pool or external
server is used to allocate the IP address.
Ipv4Addr 3GPP TS 29.571 [11] Identifies an Ipv4 address.
Ipv4AddrMask 3GPP TS 29.571 [11] String identifying an IPv4 address mask.
Ipv6Addr 3GPP TS 29.571 [11] Identifies an IPv6 address.
Ipv6Prefix 3GPP TS 29.571 [11] The Ipv6 prefix allocated for the user.
MacAddr48 3GPP TS 29.571 [11] MAC Address.
MaxDataBurstVol 3GPP TS 29.571 [11] Maximum Data Burst Volume.
MaxDataBurstVolRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"MaxDataBurstVol" data type, but with the
OpenAPI "nullable: true" property.
NfInstanceId 3GPP TS 29.571 [11] The NF instance identifier.
NfSetId 3GPP TS 29.571 [11] The NF set identifier.
NgApCause 3GPP TS 29.571 [11] Contains the cause value of NgAP protocol. RAN-NAS-
Cause
NullValue 3GPP TS 29.571 [11] JSON's null value, used as an explicit value of an
enumeration.
PacketDelBudget 3GPP TS 29.571 [11] Packet Delay Budget.
PacketErrRate 3GPP TS 29.571 [11] Packet Error Rate.
PacketLossRateRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"PacketLossRate" data type, but with the OpenAPI
PduSessionId 3GPP TS 29.571 [11] The identification of the PDU session.
PduSessionType 3GPP TS 29.571 [11] Indicate the type of a PDU session.
Pei 3GPP TS 29.571 [11] The Identification of a Permanent Equipment.
PlmnIdNid 3GPP TS 29.571 [11] The identification of the Network. PLMN Identity,
and for SNPN NID.
PresenceInfo 3GPP TS 29.571 [11] Contains the information which describes a PRA
Presence Reporting Area.
PresenceInfoRm 3GPP TS 29.571 [11] This data type is defined in the same way as the
"PresenceInfo" data type, but with the OpenAPI
ProblemDetails 3GPP TS 29.571 [11] Contains a detailed information about an error.
QosNotifType 3GPP TS 29.514 [17] Indicates whether the GBR targets for the
indicated SDFs are "NOT_GUARANTEED" or
"GUARANTEED" again.
QosResourceType 3GPP TS 29.571 [11] Indicates whether the resource type is GBR, delay
critical GBR, or non-GBR.
RatingGroup 3GPP TS 29.571 [11] Identifier of a rating group.
RatType 3GPP TS 29.571 [11] The identification of the RAT type.
RouteToLocation 3GPP TS 29.571 [11] A traffic routes to applications location. TSC
ServiceId 3GPP TS 29.571 [11] Identifier of a service.
Snssai 3GPP TS 29.571 [11] Identifies the S-NSSAI.
SubscribedDefaultQos 3GPP TS 29.571 [11] Subscribed Default QoS.
Supi 3GPP TS 29.571 [11] The identification of the user (i.e. IMSI, NAI).
SupportedFeatures 3GPP TS 29.571 [11] Used to negotiate the applicability of the optional
features defined in table 5.8-1.
TraceData 3GPP TS 29.571 [11]
TimeZone 3GPP TS 29.571 [11] Contains the user time zone information.
TscaiInputContainer 3GPP TS 29.514 [17] TSCAI Input information. TimeSensitive
Networking
Uinteger 3GPP TS 29.571 [11] Unsigned Integer. TimeSensitive
Networking
3GPP
Release 16 99 3GPP TS 29.512 V16.5.0 (2020-06)
Uint64 3GPP TS 29.571 [11] Unsigned 64-bit integers. TimeSensitive

Networking
Uri 3GPP TS 29.571 [11] URI.
UserLocation 3GPP TS 29.571 [11] Contains the user location.
Volume 3GPP TS 29.122 [32] Unsigned integer identifying a volume in units of
bytes.
VolumeRm 3GPP TS 29.122 [32] This data type is defined in the same way as the
"VolumeRm" data type, but with the OpenAPI
NOTE 1: "AnGwAddr" data structure is only applicable to the 5GS and EPC/E-UTRAN interworking scenario as
defined in Annex B.
NOTE 2: In order to support a set of MAC addresses with a specific range in the traffic filter, feature
MacAddressRange as specified in subclause 5.8 shall be supported.
5.6.2 Structured data types
5.6.2.1 Introduction
This subclause defines the structures to be used in resource representations.
5.6.2.2 Type SmPolicyControl

Table 5.6.2.2-1: Definition of type SmPolicyControl
Attribute name Data type P Cardinality Description Applicability

context SmPolicyContextData M 1 Includes the parameters to request the
SM policies by the SMF.
policy SmPolicyDecision M 1 Includes the SM policies authorized by
the PCF.
3GPP
Release 16 100 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.3 Type SmPolicyContextData

Table 5.6.2.3-1: Definition of type SmPolicyContextData

accNetChId AccNetChId O 0..1 Indicates the access network charging
identifier for default QoS flow or whole
PDU session.
chargEntityAddr AccNetChargingAddr O 0..1 Address of the network entity
ess performing charging.
gpsi Gpsi O 0..1 Gpsi shall contain either an External
Id or an MSISDN.
supi Supi C 0..1 Subscription Permanent Identifier. It
can be omitted for the emergency
session.
pduSessionId PduSessionId M 1 PDU session Id.
dnn Dnn M 1 The DNN of the PDU session, a full
DNN with both the Network Identifier
and Operator Identifier, or a DNN with
the Network Identifier only.
dnnSelMode DnnSelectionMode O 0..1 Indicates whether the requested DNN DNNSelection
corresponds to an explicitly Mode
subscribed DNN.
interGrpIds array(GroupId) O 1..N The internal Group Id(s).
notificationUri Uri M 1 Identifies the recipient of SM policies
update notifications sent by the PCF.
pduSessionType PduSessionType M 1 Indicates the type of a PDU session.
accessType AccessType O 0..1 The Access Type where the served
UE is camping.
ratType RatType O 0..1 The RAT Type where the served UE
is camping.
addAccessInfo AdditionalAccessInfo O 0..1 Indicates the combination of additional
Access Type and RAT Type for MA
PDU session.
servingNetwork PlmnIdNid O 0..1 The serving network where the served
UE is camping. For an SNPN the NID
together with the PLMN ID identifies
the SNPN.
userLocationInfo UserLocation O 0..1 The location of the served UE is
camping.
ueTimeZone TimeZone O 0..1 The time zone where the served UE is
camping.
pei Pei O 0..1 The Permanent Equipment Identifier
of the served UE.
ipv4Address Ipv4Addr O 0..1 The IPv4 Address of the served UE.
ipv6AddressPrefix Ipv6Prefix O 0..1 The Ipv6 Address Prefix of the served
UE.
ipDomain string O 0..1 IPv4 address domain identifier.
(NOTE)
subsSessAmbr Ambr O 0..1 UDM subscribed or DN-AAA
authorized Session-AMBR.
authProfIndex string O 0..1 DN-AAA authorization profile index. DN-
Authorization
subsDefQos SubscribedDefaultQ O 0..1 Subscribed Default QoS Information.
os
numOfPackFilter integer O 0..1 Contains the number of supported
packet filter for signalled QoS rules.
online boolean O 0..1 If it is included and set to true, the
online charging is applied to the PDU
session.
offline boolean O 0..1 If it is included and set to true, the
offline charging is applied to the PDU
session.
3GPP
Release 16 101 3GPP TS 29.512 V16.5.0 (2020-06)
chargingCharacteri string O 0..1 Contains the Charging Characteristics

stics applied to the PDU session.
Functional requirements for the
Charging Characteristics are defined
in 3GPP TS 32.255 [35] Annex A.
The charging characteristics are
encoded as specified in
3GPP TS 29.503 [34].
3gppPsDataOffStat boolean O 0..1 If it is included and set to true, the
us 3GPP PS Data Off is activated by the
UE.
refQosIndication boolean O 0..1 If it is included and set to true, the
reflective QoS is supported by the UE.
sliceInfo Snssai M 1 Identifies the S-NSSAI.
qosFlowUsage QosFlowUsage O 0..1 Indicates the required usage for
default QoS flow.
servNfId ServingNfIdentity O 0..1 Contains the serving network function
identity.
suppFeat SupportedFeatures C 0..1 Indicates the list of Supported
features used as described in
subclause 5.8.
This parameter shall be supplied by
the NF service consumer in the POST
request that requested the creation of
an individual SM policy resource.
traceReq TraceData O 0..1 Trace control and configuration
parameters information defined in
3GPP TS 32.422 [24].
smfId NfInstanceId O 0..1 SMF instance identifier.
recoveryTime DateTime O 0..1 It includes the recovery time of the
SMF.
maPduInd MaPduIndication O 0..1 Contains the MA PDU session ATSSS
indication, i.e., MA PDU Request or
MA PDU Network-Upgrade Allowed.
atsssCapab AtsssCapability O 0..1 Contains the ATSSS capability ATSSS
supported for the MA PDU Session.
Ipv4FrameRouteLis array(Ipv4AddrMask) O 1..N List of Framed Route information of
t IPv4.
ipv6FrameRouteLis array(Ipv6Prefix) O 1..N List of Framed Route information of
t IPv6.
NOTE: The value provided in this attribute is implementation specific. The only constraint is that the SMF shall
supply a different identifier for each overlapping address domain (e.g. the SMF NF instance identifier).
3GPP
Release 16 102 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.4 Type SmPolicyDecision

Table 5.6.2.4-1: Definition of type SmPolicyDecision

sessRules map(SessionRule) O 1..N A map of Sessionrules with the
content being the SessionRule as
described in subclause 5.6.2.7. The
key used in this map for each entry is
the sessRuleId attribute of the
corresponding SessionRule. (NOTE 2)
pccRules map(PccRule) O 1..N A map of PCC rules with the content
being the PCCRule as described in
subclause 5.6.2.6. The key used in
this map for each entry is the
pccRuleId attribute of the
corresponding PccRule.
qosDecs map(QoSData) O 1..N Map of QoS data policy decisions. The
key used in this map for each entry is
the qosId attribute of the
corresponding QoSData. (NOTE 2)
chgDecs map(ChargingData) O 1..N Map of Charging data policy
decisions. The key used in this map
for each entry is the chgId attribute of
the corresponding ChargingData.
chargingInfo ChargingInformation C 1 Contains the CHF addresses and
possible associated CHF instance Ids
and CHF set IDs of the PDU session.
(NOTE 3)
traffContDecs map(TrafficControlDa O 1..N Map of Traffic Control data policy
ta) decisions. The key used in this map
for each entry is the tcId attribute of
the corresponding TrafficControlData.
(NOTE 2)
umDecs map(UsageMonitorin O 1..N Map of Usage Monitoring data policy
gData) decisions. The key used in this map
for each entry is the umId attribute of
the corresponding
UsageMonitoringData.
qosChars map(QosCharacterist O 1..N Map of QoS characteristics for non-
ics) standard 5QIs and non-preconfigured
5QIs. This map uses the 5QI values
as keys. (NOTE 2)
qosMonDecs map(QosMonitoringD O 1..N Map of QoS Monitoring data policy QoSMonitoring
ata) decision. The key used in this map for
each entry is the qmId attribute of the
corresponding QosMonitoringData.
reflectiveQoSTimer DurationSec O 0..1 Defines the lifetime of a UE derived
QoS rule belonging to the PDU
Session for reflective QoS. (NOTE 2)
offline boolean O 0..1 Indicates the offline charging is
applicable to the PDU session when it
is included and set to true. (NOTE 3)
(NOTE 4)
online boolean O 0..1 Indicates the online charging is
applicable to the PDU session when it
is included and set to true. (NOTE 3)
(NOTE 4)
conds map(ConditionData) O 1..N A map of condition data with the
content being as described in
subclause 5.6.2.9. The key used in
this map for each entry is the condId
attribute of the corresponding
ConditionData.
revalidationTime DateTime O 0..1 Defines the time before which the
SMF shall have to re-request PCC
rules.
3GPP
Release 16 103 3GPP TS 29.512 V16.5.0 (2020-06)
pcscfRestIndication boolean O 0..1 If this attribute is included and set to PCSCF-

true, it indicates that the P-CSCF Restoration-
Restoration is requested. The default Enhancement
value "FALSE" applies, if the attribute
is not present and has not been
supplied previously.
policyCtrlReqTrigg array(PolicyControlR O 1..N Defines the policy control request
ers equestTrigger) triggers subscribed by the PCF.
lastReqRuleData array(RequestedRule O 1..N Defines the last list of rule control data
Data) requested by the PCF.
lastReqUsageData RequestedUsageDat O 0..1 Defines the last requested usage data
a by the PCF.
praInfos map(PresenceInfoR O 1..N Defines the PRA information PRA
m) provisioned by the PCF. The "praId"
attribute within the PresenceInfo data
type shall also be the key of the map.
The "presenceState" attribute within
the PresenceInfo data type shall not
be supplied.
ipv4Index IpIndex C 0..1 Information that identifies the IP
address allocation method for IPv4
address allocation. (NOTE 3)
ipv6Index IpIndex C 0..1 Information that identifies the IP
address allocation method for IPv6
address allocation. (NOTE 3)
default QoS flow.
relCause SmPolicyAssociation O 0..1 The cause for which the PCF requests RespBasedSe
ReleaseCause the termination of the policy ssionRel
association.
suppFeat SupportedFeatures C 0..1 Indicates the list of negotiated
supported features.
This parameter shall be supplied by
the PCF in the response to the POST
request that requested the creation of
an individual SM policy resource.
tsnBridgeManCont BridgeManagementC O 0..1 Transports TSN bridge management TimeSensitive
ontainer information Networking
tsnPortManContDs PortManagementCon O 0..1 Transports TSN port management TimeSensitive
tt tainer information for the DS-TT port. Networking
tsnPortManContNw array(PortManageme O 1..N Transports TSN port management TimeSensitive
tts ntContainer) information for one or more NW-TT Networking
ports.
NOTE 1: For IPv4v6 PDU session, both the "ipv4Index" attribute and "ipv6Index" attribute may be provisioned by the
PCF.
NOTE 2: This attribute shall not be removed if it was provisioned.
NOTE 3: This attribute may only be supplied by the PCF in the response to the POST request that requested the
creation of an individual SM policy resource.
NOTE 4: If both the "offline" attribute and the "online" attribute is omitted by the PCF, the default charging method pre-
configured at the SMF if available shall be applied to the PDU session. If both offline and online charging
methods are pre-configured at the SMF, the SMF shall determine either of them to be applied to the PDU
session based on local policy. The “offline” attribute and the “online” attribute shall not be simultaneously
present with the same value, i.e., both set to true or both set to false.
NOTE 5: If the "chargingInfo" attribute is not supplied by the PCF, the charging information configured at the SMF shall
be applied to the PDU session.
3GPP
Release 16 104 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.5 Type SmPolicyNotification

Table 5.6.2.5-1: Definition of type SmPolicyNotification

resourceUri Uri M 1 The resource URI of the individual SM
policy related to the notification.
smPolicyDecision SmPolicyDecision M 1 Session management policy (see
subclause 5.6.2.4).
3GPP
Release 16 105 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.6 Type PccRule

Table 5.6.2.6-1: Definition of type PccRule
Attribute name Data type P Cardinalit Description Applicability

y
flowInfos array(FlowInformation) C 1..N An array of IP flow packet filter
information. (NOTE 3)
appId string C 0..1 A reference to the application ADC
detection filter configured at the UPF.
(NOTE 3)
appDescriptor ApplicationDescriptor C 0..1 ATSSS rule application descriptor. It ATSSS
shall be present when the PDU
session is a MA PDU session and the
SDF template contains an Application
Identifier (i.e. when the "appId"
attribute is present).
contVer ContentVersion O 0..1 Indicates the content version of the RuleVersioning
PCC rule.
pccRuleId string M 1 Univocally identifies the PCC rule
within a PDU session.
precedence Uinteger O 0..1 Determines the order in which this
PCC rule is applied relative to other
PCC rules within the same PDU
session. It shall be included if the
"flowInfos" attribute is included or
may be included if the "appId"
attribute is included when the PCF
initially provisions the PCC rule.
(NOTE 2) (NOTE 4)
afSigProtocol AfSigProtocol O 0..1 Indicates the protocol used for ProvAFsignalFlo
signalling between the UE and the w
AF. The default value
"NO_INFORMATION" shall apply, if
the attribute is not present and has
not been supplied previously.
appReloc boolean O 0..1 It indicates that the application TSC
cannot be relocated once a location
of the application is selected by the
5GC when it is included and set to
"true". Indication of application
relocation possibility. The default
value "false" shall apply, if the
attribute is not present and has not
been supplied previously.
addrPreserInd boolean O 0..1 Indicates whether UE IP address URLLC
should be preserved.
This attribute shall set to "true" if
preserved, otherwise, set to "false".
The default value "false" shall apply,
if the attribute is not present and has
refQosData array(string) O 1..N A reference to the QoSData policy
type decision type. It is the qosId
described in subclause 5.6.2.8.
(NOTE 1)
3GPP
Release 16 106 3GPP TS 29.512 V16.5.0 (2020-06)
refAltQosParam array(string) O 1..N A Reference to the QoS Data policy AuthorizationWit

s decision type for the Alternative QoS hRequiredQoS
parameter sets of the service data
flow. Only the "qosId" attribute, "5qi"
attribute, "maxbrUl" attribute,
"maxbrDl" attribute, "gbrUl" attribute
and "gbrDl" attribute are applicable
within the QosData data type. This
data type represents an ordered list,
where the lower the index of the
array for a given entry, the higher the
priority.
refTcData array(string) O 1..N A reference to the TrafficControlData
policy decision type. It is the tcId
(NOTE 1)
refChgData array(string) O 1..N A reference to the ChargingData
policy decision type. It is the chgId
(NOTE 1)
refChgN3gData array(string) O 1..N A reference to the ChargingData ATSSS
policy decision type only applicable to
Non-3GPP access. It is the chgId
(NOTE 1) (NOTE 5)
refUmData array(string) O 1..N A reference to UsageMonitoringData
policy decision type. It is the umId
(NOTE 1)
refUmN3gData array(string) O 1..N A reference to UsageMonitoringData ATSSS
policy decision type only applicable to
Non-3GPP access. It is the umId
(NOTE 1) (NOTE 6)
refCondData string O 0..1 A reference to the condition data. It is
the condId described in
subclause 5.6.2.9.
refQoSMon array(string) O 1..N A reference to QoSMonitoringData QosMonitoring
policy decision type. It is the qmId
(NOTE 1)
tscaiInputUl TscaiInputContainer O 0..1 Transports TSCAI input parameters TimeSensitiveN
for TSC traffic at the ingress interface etworking
of the DS-TT/UE (uplink flow
direction).
tscaiInputDl TscaiInputContainer O 0..1 Transports TSCAI input parameters TimeSensitiveN
for TSC traffic at the ingress of the etworking
NW-TT (downlink flow direction).
3GPP
Release 16 107 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE 1: Arrays are only introduced for future compatibility. In this release of the specification the maximum number
of elements in the array is 1.
NOTE 2: For a PCC rule with the "appId" attribute, the precedence can be preconfigured in SMF or provided in the
PCC rule from PCF. The precedence provided by the PCF shall take precedence.
NOTE 3: Either the "flowInfos" attribute or "appId" attribute shall be supplied by the PCF when the PCC rule is initially
provisioned. If the "appId" attribute is supplied, the PCF shall not modify the application identifier supplied
within the "appId" attribute later.
NOTE 4: The "precedence" attribute is used to specify the precedence of the PCC rule among all PCC rules
associated with the PDU session. It includes an integer value in the range from 0 to 255 (decimal). The
higher the value of the "precedence" attribute, the lower the precedence of that PCC rule is. The precedence
value range from 70 to 99 (decimal) shall be used for the PCC rules subject to Reflective QoS.
NOTE 5: For a MA PDU Session, Charging Data decision referred by the "refChgData" attribute applies to both
accesses if there is no "refChgN3gData" attribute included. If there is a "refChgN3gData" attribute included,
the Charging Data decision referred by the "refChgN3gData" attribute applies to non-3GPP access and the
Charging Data decision referred by the "refChgData" attribute applies to 3GPP access. The value(s) of
attribute(s) within the Charging Data decision except the “chgId" attribute referred by the "refChgN3gData"
attribute shall be the same as the one(s) within the Charging Data decision referred by the "refChgData"
attribute.
NOTE 6: For a MA PDU Session, Usage Monitoring Data decision referred by the "refUmData" attribute applies to
both accesses if there is no "refUmN3gData" attribute included. If there is a "refUmN3gData" attribute
included, the Usage Monitoring Data decision referred by the "refUmN3gData" attribute applies to non-3GPP
access and the Usage Monitoring Data decision referred by the "refUmData" attribute applies to 3GPP
access.
5.6.2.7 Type SessionRule

Table 5.6.2.7-1: Definition of type SessionRule

authSessAmbr Ambr O 0..1 Authorized Session-AMBR.
authDefQos AuthorizedDefaultQos O 0..1 Authorized default QoS information.
sessRuleId string M 1 Univocally identifies the session rule
within a PDU session.
refUmData string O 0..1 A reference to UsageMonitoringData
policy decision type. It is the umId
(NOTE)
refCondData string O 0..1 A reference to the condition data. It is
the condId described in
subclause 5.6.2.9.
refUmN3gData string O 0..1 A reference to UsageMonitoringData ATSSS
policy decision type to apply for Non-
3GPP access. It is the umId described
(NOTE)
NOTE: For a MA PDU session, if the "refUmN3gData" is omitted, the attribute "refUmData" contains the reference to
the UsageMonitoringData policy decision to apply for both, 3GPP and Non-3GPP, accesses.
3GPP
Release 16 108 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.8 Type QosData

Table 5.6.2.8-1: Definition of type QosData

qosId string M 1 Univocally identifies the QoS control
policy data within a PDU session.
5qi 5Qi C 0..1 Identifier for the authorized QoS
parameters for the service data flow. It
shall be included when the QoS data
decision is initially provisioned and
"defQosFlowIndication" is not included
or is included and set to false.
maxbrUl BitRateRm O 0..1 Indicates the max bandwidth in uplink.
maxbrDl BitRateRm O 0..1 Indicates the max bandwidth in
downlink.
gbrUl BitRateRm O 0..1 Indicates the guaranteed bandwidth in
uplink.
gbrDl BitRateRm O 0..1 Indicates the guaranteed bandwidth in
downlink.
arp Arp C 1 Indicates the allocation and retention
priority. It shall be included when the
QoS data decision is initially
provisioned and "defQosFlowIndication"
is not included or is included and set to
false.
qnc boolean O 0..1 Indicates whether notifications are
requested from 3GPP NG-RAN when
the GFBR can no longer (or again) be
guaranteed for a QoS Flow during the
lifetime of the QoS Flow. Default value
"FALSE" is used, if not present and has
reflectiveQos boolean O 0..1 Indicates whether the QoS information
is reflective for the corresponding non-
GBR service data flow. Default value
sharingKeyDl string O 0..1 Indicates, by containing the same ResShare
value, what PCC rules may share
resource in downlink direction.
sharingKeyUl string O 0..1 Indicates, by containing the same ResShare
value, what PCC rules may share
resource in uplink direction.
priorityLevel 5QiPriorityLevelRm O 0..1 Indicates a priority in scheduling
resources among QoS Flows.
(NOTE 1)
averWindow AverWindowRm O 0..1 Represents the duration over which the
guaranteed and maximum bitrate shall
be calculated. (NOTE 1)
maxDataBurstVol MaxDataBurstVolR O 0..1 Denotes the largest amount of data that
m is required to be transferred within a
period of 5G-AN PDB. (NOTE 1,
NOTE 2)
maxPacketLossR PacketLossRateRm O 0..1 Indicates the downlink maximum rate RAN-Support-
ateDl for lost packets that can be tolerated for Info
the service data flow.
maxPacketLossR PacketLossRateRm O 0..1 Indicates the uplink maximum rate for RAN-Support-
ateUl lost packets that can be tolerated for Info
the service data flow.
defQosFlowIndic boolean O 0..1 Indicates that the dynamic PCC rule
ation shall always have its binding with the
QoS Flow associated with the default
QoS rule. Default value "FALSE" is
used, if not present and has not been
3GPP
Release 16 109 3GPP TS 29.512 V16.5.0 (2020-06)
extMaxDataBurst ExtMaxDataBurstVo O 0..1 Denotes the largest amount of data that EMDBV
Vol lRm is required to be transferred within a
period of 5G-AN PDB. (NOTE 1,
NOTE 2)
NOTE 1: Applicable only when a value different from the standardized value for this 5QI in table 5.7.4-1
3GPP TS 23.501 [2] is required.
NOTE 2: Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present. If the maximum data burst
volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurst Vol IE is used. If the
EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit
maximum data burst volume values higher than 4095 Bytes (see subclause 4.2.2.1).
5.6.2.9 Type ConditionData

Table 5.6.2.9-1: Definition of type ConditionData

condId string M 1 Uniquely identifies the condition data within
a PDU session.
activationTime DateTimeRm O 0..1 The time when the decision data shall be
activated.
deactivationTime DateTimeRm O 0..1 The time when the decision data shall be
deactivated.
accessType AccessType O 0..1 The condition of access type of the UE AccessTypeCo
when the session AMBR shall be enforced. ndition
ratType RatType O 0..1 The condition of RAT type of the UE when AccessTypeCo
the session AMBR shall be enforced. ndition
3GPP
Release 16 110 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.10 Type TrafficControlData

Table 5.6.2.10-1: Definition of type TrafficControlData

tcId string M 1 Univocally identifies the traffic control
flowStatus FlowStatus O 0..1 Enum determining what action to
perform on traffic. Possible values
are: [enable, disable, enable_uplink,
enable_downlink]. The default value
"ENABLED" shall apply, if the attribute
is not present and has not been
redirectInfo RedirectInformation O 0..1 It indicates whether the detected ADC
application traffic should be redirected
to another controlled address.
addRedirectInfo array(RedirectInform O 1..N Additional redirection information. ADCmultiRedir
ation) Each element indicates whether the ection
detected application traffic should be
redirected to another controlled
address.
muteNotif boolean O 0..1 Indicates whether application's start or ADC
stop notification is to be muted. The
default value "FALSE" shall apply, if
the attribute is not present and has
trafficSteeringPolIdDl string O 0..1 Reference to a pre-configured traffic TSC
(NOTE) steering policy for downlink traffic at
the SMF.
trafficSteeringPolIdUl string O 0..1 Reference to a pre-configured traffic TSC
(NOTE) steering policy for uplink traffic at the
SMF.
routeToLocs array(RouteToLocati O 1..N A list of location which the traffic shall TSC
(NOTE) on) be routed to for the AF request.
traffCorreInd boolean O 0..1 Indication of traffic correlation.
upPathChgEvent UpPathChgEvent O 0..1 Contains the information about the AF TSC
subscriptions of the UP path change.
steerFun SteeringFunctionalit O 0..1 Indicates the applicable traffic steering ATSSS
y functionality.
steerModeDl SteeringMode O 0..1 Determines the traffic distribution rule ATSSS
across 3GPP and Non-3GPP
accesses to apply for downlink traffic.
steerModeUl SteeringMode O 0..1 Determines the traffic distribution rule ATSSS
across 3GPP and Non-3GPP
accesses to apply for uplink traffic.
mulAccCtrl MulticastAccessCon O 0..1 Indicates whether the service data WWC
trol flow, corresponding to the service
data flow template, is allowed or not
allowed. The default value
"NOT_ALLOWED" applies, if the
attribute is not present and has not
been supplied previously.
NOTE: Traffic steering policy identifier(s) (i.e. "trafficSteeringPolIdDl" attribute and/or "trafficSteeringPolIdUl”
attribute) and N6 traffic routing requirements (i.e. "routeToLocs" attribute) are mutually exclusive.
3GPP
Release 16 111 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.11 Type ChargingData

Table 5.6.2.11-1: Definition of type ChargingData
Attribute name Data type P Cardinalit Description Applicability

y
chgId string M 1 Univocally identifies the charging
control policy data within a PDU
session.
meteringMethod MeteringMethod O 0..1 Defines what parameters shall be
metered for offline charging. If the
attribute is not present but it has been
supplied previously, the previous
information remains valid. If the attribute
is not present and it has not been
supplied previously or the attribute has
been supplied previously but the
attribute is set to NULL, the metering
method pre-configured at the SMF is
applicable as default metering method.
offline boolean O 0..1 Indicates the offline charging is
applicable to the PCC rule when it is
included and set ot true. (NOTE 1)
online boolean O 0..1 Indicates the online charging is
applicable to the PCC rule when it is
included and set ot true. (NOTE 1)
sdfHandl boolean O 0..1 Indicates whether the service data flow
is allowed to start while the SMF is
waiting for the response to the credit
request. The default value "FALSE"
(blocking) shall apply, if the attribute is
not present. (NOTE 2)
ratingGroup RatingGroup O 0..1 The charging key for the PCC rule used
for rating purposes.
reportingLevel ReportingLevel O 0..1 Defines on what level the SMF reports
the usage for the related PCC rule. If
the attribute is not present but it has
been supplied previously, the previous
information remains valid. If the attribute
is not present and it has not been
supplied previously or the attribute has
been supplied previously but it is set to
NULL, the reporting level pre-configured
at the SMF is applicable as default
reporting level.
serviceId ServiceId O 0..1 Indicates the identifier of the service or
service component the service data flow
in a PCC rule relates to.
sponsorId string O 0..1 Indicates the sponsor identity. Sponsored-
Connectivity
appSvcProvId string O 0..1 Indicates the application service Sponsored-
provider identity. Connectivity
afChargingIdentifie ChargingId O 0..1 An identifier, provided from the AF,
r correlating the measurement for the
Charging key/Service identifier values in
this PCC rule with application level
reports.
(NOTE 4)
afChargId ApplicationCharging O 0..1 A character string identifier, provided AF_Charging_
Id from the AF, correlating the Identifier
measurement for the Charging
key/Service identifier values in this PCC
rule with application level reports.
(NOTE 3)
3GPP
Release 16 112 3GPP TS 29.512 V16.5.0 (2020-06)
NOTE 1: The absence of both the "offline" attribute and "online" attribute or only one attribute is present and set to
false within a Charging Data decision instance indicates that the default charging method of the PDU session
is applicable to the PCC rule referring to the Charging Data decision. Either "offline" attribute or "online"
attribute set to true shall be provisioned initially if there is no default charging method applied to the PDU
session. The “offline” attribute and the “online” attribute shall not be simultaneously present with the same
value, i.e., both set to true or both set to false.
NOTE 2: The "sdfHandl" attribute shall not be present when the online charging method does not apply for the PCC
rule referring to the Charging Data decision (i.e., when the "online" attribute is present and set to false, or is
absent and the online default charging method does not apply for the PDU session, or is absent and there is
no online default charging method defined).
NOTE 3: The "afChargId" attribute shall be used instead of the "afChargingIdentifier" attribute when the
"AF_Charging_Identifier" feature is supported.
NOTE 4: The "afChargingIdentifier" attribute shall not be present when the "IMS_Charging_Identifier" feature is
supported. When the "AF_Charging_Identifier" feature is not supported it is out of the scope of the
specification what the behaviour of the PCF is when the AF provides charging identifier values that are out of
ChargingId data type value range.
5.6.2.12 Type UsageMonitoringData

Table 5.6.2.12-1: Definition of type UsageMonitoringData

umId string M 1 Univocally identifies the usage
monitoring policy data within a PDU
session.
volumeThreshold VolumeRm O 0..1 Indicates the total volume threshold.
volumeThresholdUp VolumeRm O 0..1 Indicates a volume threshold in uplink.
link
volumeThresholdDo VolumeRm O 0..1 Indicates a volume threshold in
wnlink downlink.
timeThreshold DurationSecRm O 0..1 Indicates a time threshold.
monitoringTime DateTimeRm O 0..1 Indicates the time at which the UP
function is expected to reapply the next
thresholds (e.g. nextVolThreshold).
nextVolThreshold VolumeRm C 0..1 Indicates a volume threshold after the
Monitoring Time.
nextVolThresholdU VolumeRm O 0..1 Indicates a volume threshold in uplink
plink after the Monitoring Time.
nextVolThresholdD VolumeRm O 0..1 Indicates al volume threshold in
ownlink downlink after the Monitoring Time.
nextTimeThreshold DurationSecRm C 0..1 Indicates a time threshold after the
Monitoring.
inactivityTime DurationSecRm O 0..1 Defines the period of time after which
the time measurement shall stop, if no
packets are received.
exUsagePccRuleIds array(string) C 1..N Contains the PCC rule identifier(s)
which corresponding service data
flow(s) shall be excluded from PDU
Session usage monitoring. It is only
included in the UsageMonitoringData
instance for session level usage
monitoring.
3GPP
Release 16 113 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.13 Type RedirectInformation

Table 5.6.2.13-1: Definition of type RedirectInformation

redirectEnabled boolean C 0..1 This attribute indicates whether the
redirect instruction is enable. It
shall be included and set to true
when the redirect instruction is
provisioned initially and may be
included subsequently to disable or
re-enable the redirect instruction. If
the attribute omitted, the previous
value shall apply.
redirectAddressType RedirectAddressTy O 0..1 Indicates the type of redirect
pe address.
redirectServerAddress string O 0..1 Indicates the address of the
redirect server.
3GPP
Release 16 114 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.14 Type FlowInformation

Table 5.6.2.14-1: Definition of type FlowInformation

flowDescription FlowDescription O 0..1 Contains the packet filters of the IP
flow(s).
ethFlowDescription EthFlowDescription O 0..1 Defines a packet filter for an Ethernet
flow. If the "fDir" attribute is included, it
shall be set to "DOWNLINK". If the
"fDir" attribute is never provided, the
address information within the
"ethFlowDescription" attribute shall be
encoded in downlink direction.
packFiltId string O 0..1 An identifier of packet filter.
packetFilterUsage boolean O 0..1 The packet shall be sent to the UE.
The default value "FALSE" shall apply,
if the attribute is not present and has
tosTrafficClass string O 0..1 2-octet string. The first octet contains
the Ipv4 Type-of-Service or the Ipv6
Traffic-Class field and the second octet
contains the ToS/Traffic mask field in
hexadecimal representation. Each
character in the string shall take a
value of "0" to "9" or "A" to "F" and
shall represent 4 bits. One example is
that of a TFT packet filter as defined in
3GPP TS 24.008 [41].
spi string O 0..1 4 octet string, representing the security
parameter index of the IPSec packet in
shall represent 4 bits. One example is
that of a TFT packet filter as defined in
3GPP TS 24.008 [41].
flowLabel string O 0..1 3-octet string, representing the Ipv6
flow label header field in hexadecimal
representation. Each character in the
string shall take a value of "0" to "9" or
"A" to "F" and shall represent 4 bits.
One example is that of a TFT packet
filter as defined in
3GPP TS 24.008 [41].
flowDirection FlowDirectionRm O 0..1 Indicates the direction/directions that a
filter is applicable, downlink only,
uplink only or both down- and uplink
(bidirectional).
3GPP
Release 16 115 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.15 Type SmPolicyDeleteData

Table 5.6.2.15-1: Definition of type SmPolicyDeleteData

userLocationInfo UserLocation O 0..1 The location of the served UE is RAN-NAS-
camping. Cause, NetLoc
ueTimeZone TimeZone O 0..1 The time zone where the served UE RAN-NAS-
is camping. Cause, NetLoc
userLocationInfoTime DateTime O 0..1 Contains the NTP time at which the RAN-NAS-
UE was last known to be in the Cause, NetLoc
location.
servingNetwork PlmnIdNid O 0..1 The serving network where the RAN-NAS-
served UE is camping. For an SNPN Cause, NetLoc
the NID together with the PLMN ID
identifies the SNPN.
ranNasRelCauses array(RanNasRel O 1..N indicates the RAN or NAS release RAN-NAS-
Cause) cause code information. Cause
accuUsageReports array(AccuUsage O 1..N Contains the usage report. UMC
Report)
pduSessRelCause PduSessionRelCa O 0..1 Indicates PDU session release PDUSessionRel
use cause. Cause
5.6.2.16 Type QosCharacteristics

Table 5.6.2.16-1: Definition of type QosCharacteristics

5qi 5Qi M 1 Identifier for the authorized QoS
parameters for the service data
flow. Applies to PCC rule and PDU
session level.
resourceType QosResourceType M 1 Indicates whether the resource
type is GBR, delay critical GBR, or
non-GBR.
priorityLevel 5QiPriorityLevel M 1 Unsigned integer indicating the 5QI
Priority Level, within a range of 1 to
127.
packetDelayBudget PacketDelBudget M 1 Unsigned integer indicates the
packet delay budget. Packet Delay
Budget expressed in milliseconds.
packetErrorRate PacketErrRate M 1 String indicating the packet error
rate.
Examples:
Packer Error Rate 4x10-6 shall be
encoded as "4E-6".
Packer Error Rate 10-2 shall be
encoded as"1E-2".
averagingWindow AverWindow C 0..1 Indicates the averaging window.
This IE shall be present only for a
GBR QoS flow or a Delay Critical
GBR QoS flow.
maxDataBurstVol MaxDataBurstVol C 0..1 Unsigned Integer. Indicates the
maximum data burst volume.
(NOTE)
extMaxDataBurstVol ExtMaxDataBurstV C 0..1 Unsigned Integer. Indicates the EMDBV
ol maximum data burst volume.
(NOTE)
NOTE: Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present for a Delay Critical GBR QoS
flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the
maxDataBurst Vol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the
extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes (see
subclause 4.2.2.1).
3GPP
Release 16 116 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.17 Type ChargingInformation

Table 5.6.2.17-1: Definition of type ChargingInformation
Attribute name Data type P

Cardinality Description Applicability
primaryChfAddress Uri M 1 URI, which corresponds to the {apiRoot}
in the form of an FQDN, of the primary
CHF instance.
secondaryChfAddress Uri M 1 URI, which corresponds to the {apiRoot}
in the form of an FQDN, of the
secondary CHF instance.
primaryChfSetId NfSetId C 0..1 The CHF set Id of the primary CHF
instance may complement the primary
CHF address and shall be present, if
available.
primaryChfInstanceId NfInstanceId C 0..1 The CHF instance Id of the primary
CHF instance may complement the
primary CHF address and shall be
present, if available.
secondaryChfSetId NfSetId C 0..1 The CHF set Id of the secondary CHF
instance may complement the
secondary CHF address and shall be
secondaryChfInstance NfInstanceId C 0..1 The CHF instance Id of the secondary
Id CHF instance may complement the
secondary CHF address and shall be
NOTE: Based on the {apiRoot} of the CHF instance, the consumer can derive the Nfinstance via NRF lookup. It is up
to the consumer to determine which service to invoke from the CHF. The {apiRoot} shall apply to all CHF
services.
5.6.2.18 Type AccuUsageReport

Table 5.6.2.18-1: Definition of type AccuUsageReport

refUmIds string M 1 An id referencing UsageMonitoringData
objects associated with this usage report.
volUsage Volume O 0..1 Indicates a total accumulated volume
usage.
volUsageUplink Volume O 0..1 Indicates an accumulated volume usage
in uplink.
volUsageDownlink Volume O 0..1 Indicates an accumulated volume usage
in downlink.
timeUsage DurationSec O 0..1 Indicates an accumulated time usage.
nextVolUsage Volume C 0..1 Indicates an accumulated volume usage
after the Monitoring Time.
nextVolUsageUplink Volume O 0..1 Indicates an accumulated volume usage
in uplink after the Monitoring Time.
nextVolUsageDownli Volume O 0..1 Indicates an accumulated volume usage
nk in downlink after the Monitoring Time.
nextTimeUsage DurationSec C 0..1 Indicates an accumulated time usage after
the Monitoring.
3GPP
Release 16 117 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.19 Type SmPolicyUpdateContextData

Table 5.6.2.19-1: Definition of type SmPolicyUpdateContextData

repPolicyCtrlReqTrig array(PolicyContr C 1..N The policy control request triggers
gers olRequestTrigger) which are met. It is omitted if no
triggers are met such as in
subclauses 4.2.4.7 and 4.2.4.15.
accNetChIds array(AccNetChId O 1..N Indicates the access network
) charging identifier for the PCC rule(s)
or whole PDU session.
accessType AccessType O 0..1 The Access Type where the served
UE is camping.
ratType RatType O 0..1 The RAT Type where the served UE
is camping.
addAccessInfo AdditionalAccessI O 0..1 Indicates the combination of added ATSSS
nfo Access Type and RAT Type for MA
PDU session.
relAccessInfo AdditionalAccessI O 0..1 Indicates the combination of released ATSSS
nfo Access Type and RAT Type for MA
PDU session.
servingNetwork PlmnIdNid O 0..1 The serving network where the
served UE is camping. For an SNPN
the NID together with the PLMN ID
identifies the SNPN.
camping.
ueTimeZone TimeZone O 0..1 The time zone where the served UE
is camping.
ipv4Address Ipv4Addr O 0..1 The IPv4 Address of the served UE.
ipDomain string O 0..1 IPv4 address domain identifier.
(NOTE 2)
relIpv4Address Ipv4Addr O 0..1 Indicates the released IPv4 Address
of the served UE.
ipv6AddressPrefix Ipv6Prefix O 0..1 The Ipv6 Address Prefix of the served
UE.
relIpv6AddressPrefix Ipv6Prefix O 0..1 Indicates the released IPv6 Address
Prefix of the served UE in multi-
homing case.
relUeMac MacAddr48 O 0..1 Indicates the released MAC Address
of the served UE.
ueMac MacAddr48 O 0..1 The MAC Address of the served UE.
subsSessAmbr Ambr O 0..1 UDM subscribed or DN-AAA
authorized Session-AMBR.
authProfIndex string O 0..1 DN-AAA authorization profile index. DN-
Authorization
subsDefQos SubscribedDefault O 0..1 Subscribed Default QoS Information.
Qos
numOfPackFilter integer O 0..1 Contains the number of supported
packet filter for signalled QoS rules.
(NOTE 1)
accuUsageReports array(AccuUsage O 1..N Accumulate usage report.
Report)
3gppPsDataOffStatus boolean O 0..1 If it is included and set to true, the
3GPP PS Data Off is activated by the
UE.
appDetectionInfos array(AppDetectio O 1..N Reports the start/stop of the ADC
nInfo) application traffic and detected SDF
descriptions if applicable.
ruleReports array(RuleReport) O 1..N Used to report the PCC rule failure.
sessRuleReports array(SessionRul O 1..N Used to report the session rule failure. SessionRuleEr
eReport) rorHandling
qncReports array(QosNotificat O 1..N QoS Notification Control information.
ionControlInfo)
qosMonReports array(QosMonitori O 1..N QoS Monitoring reporting information. QosMonitoring
ngReport)
3GPP
Release 16 118 3GPP TS 29.512 V16.5.0 (2020-06)
userLocationInfoTime DateTime O 0..1 Contains the NTP time at which the

UE was last known to be in the
location.
repPraInfos map(PresenceInfo O 1..N Reports the changes of presence PRA
) reporting area. The "praId" attribute
within the PresenceInfo data type
shall also be the key of the map. The
"presenceState" attribute within the
PresenceInfo data type shall be
supplied.
ueInitResReq UeInitiatedResour O 0..1 Indicates a UE requests specific QoS
ceRequest handling for selected SDF.
refQosIndication boolean O 0..1 If it is included and set to true, the
reflective QoS is supported by the
UE. If it is included and set to false,
the reflective QoS is revoked by the
UE.
default QoS flow.
creditManageStatus CreditManageme O 0..1 Indicates the reason of the credit
ntStatus management session failure.
identity.
traceReq TraceData C 0..1 It shall be included if trace is required
to be activated, modified or
deactivated (see
3GPP TS 32.422 [24]). For trace
modification, it shall contain a
complete replacement of trace data.
For trace deactivation, it shall contain
the Null value.
addIpv6AddrPrefixes array(Ipv6Prefix) O 1..N The Ipv6 Address Prefixes of the MultiIpv6AddrP
served UE. refix
addRelIpv6AddrPrefi array(Ipv6Prefix) O 1..N Indicates the released IPv6 Address MultiIpv6AddrP
xes Prefixes of the served UE in multi- refix
homing case.
tsnBridgeInfo TsnBridgeInfo O 0..1 Transports TSN bridge information. TimeSensitive
Networking
tsnBridgeManCont BridgeManageme O 0..1 Transports TSN bridge management TimeSensitive
ntContainer information. Networking
tsnPortManContDstt PortManagement O 0..1 Transports TSN port management TimeSensitive
Container information for the DS-TT port. Networking
tsnPortManContNwtt array(PortManage O 1..N Transports TSN port management TimeSensitive
s mentContainer) information for one or more NW-TT Networking
ports.
maPduInd MaPduIndication O 0..1 Contains the MA PDU session ATSSS
indication, i.e., MA PDU Request or
MA PDU Network-Upgrade Allowed.
(NOTE 1)
atsssCapab AtsssCapability O 0..1 Contains the ATSSS capability ATSSS
supported for the MA PDU session.
(NOTE 1)
mulAddrInfos array(IpMulticastA O 1..N Contains the IP multicast address WWC
ddressInfo) information.
policyDecFailureRep array(PolicyDecisi O 1..N Indicates the type(s) of the failed PolicyDecision
orts onFailureCode) policy decision and/or condition data. ErrorHandling
trafficDescriptor DddTrafficDescrip O 0..1 Contains the traffic descriptor DDNEventPoli
tor cyControl
NOTE 1: This attribute is only applicable to the 5GS and EPC/E-UTRAN interworking scenario as defined in Annex B.
NOTE 2: The value provided in this attribute is implementation specific. The only constraint is that the SMF shall
supply a different identifier for each overlapping address domain (e.g. the SMF NF instance identifier).
3GPP
Release 16 119 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.20 Type UpPathChgEvent

Table 5.6.2.20-1: Definition of type UpPathChgEvent

notificationUri Uri M 1 Notification address of AF receiving the TSC
event notification.
notifCorreId string M 1 It is used to set the value of Notification TSC
Correlation ID in the notification sent by
the SMF.
dnaiChgType DnaiChangeType M 1 Indicates the type of DNAI change. TSC
afAckInd boolean O 0..1 Identifies whether the AF URLLC
acknowledgement of UP path event
notification is expected.
Set to "true" if the AF acknowledge is
expected; otherwise set to "false".
Default value is "false" if omitted.
5.6.2.21 Type TerminationNotification

Table 5.6.2.21-1: Definition of type TerminationNotification

resourceUri Uri M 1 The resource URI of the individual SM
policy related to the notification.
cause SmPolicyAssociati M 1 The cause why the PCF requests the
onReleaseCause termination of the policy association.
5.6.2.22 Type AppDetectionInfo

Table 5.6.2.22-1: Definition of type AppDetectionInfo

appId string M 1 A reference to the application
detection filter configured at the UPF.
instanceId string O 1 Identifier dynamically assigned by the
SMF in order to allow correlation of
application Start and Stop events to
the specific service data flow
description, if service data flow
descriptions are deducible.
sdfDescriptions array(FlowInformation O 1..N Contains the detected service data
) flow descriptions if they are deducible.
5.6.2.23 Type AccNetChId

Table 5.6.2.23-1: Definition of type AccNetChId

accNetChaIdValue ChargingId M 1 Contains a charging identifier.
refPccRuleIds array(string) O 1..N Contains the identifier of the PCC
rule(s) associated to the provided
Access Network Charging Identifier.
sessionChScope boolean O 0..1 When it is included and set to true,
indicates the Access Network
Charging Identifier applies to the
whole PDU Session.
3GPP
Release 16 120 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.24 Type RequestedRuleData

Table 5.6.2.24-1: Definition of type RequestedRuleData

refPccRuleIds array(string) M 1..N An array of PCC rule id references to
the PCC rules associated with the
control data.
reqData array(Requested M 1..N Array of requested rule data type
RuleDataType) elements indicating what type of rule
data is requested for the
corresponding referenced PCC rules.
5.6.2.25 Type RequestedUsageData

Table 5.6.2.25-1: Definition of type RequestedUsageData

refUmIds array(string) C 1..N An array of usage monitoring data id
references to the usage monitoring data
instances for which the PCF is requesting
a usage report. This attribute shall only
be provided when allUmIds is not set to
true.
allUmIds boolean C 0..1 This boolean indicates whether requested
usage data applies to all usage
monitoring data instances. When it's not
included, it means requested usage data
shall only apply to the usage monitoring
data instances referenced by the
refUmIds attribute.
5.6.2.26 Type UeCampingRep

Table 5.6.2.26-1: Definition of type UeCampingRep

accessType AccessType O 0..1 The Access Type where the served UE
is camping.
ratType RatType O 0..1 The RAT Type where the served UE is
camping.
identity.
servingNetwork PlmnIdNid O 0..1 The serving network where the served
UE is camping. For an SNPN the NID
together with the PLMN ID identifies the
SNPN.
camping.
ueTimeZone TimeZone O 0..1 The time zone where the served UE is
camping.
netLocAccSupp NetLocAccessSu O 0..1 Indicates the access network does not NetLoc
pport support the report of the requested
access network information.
policyDecFailureR array(PolicyDecis O 1..N Used to report the failure of the policy PolicyDecisionE
eports ionFailureCode) decision and/or condition data. rrorHandling
3GPP
Release 16 121 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.27 Type RuleReport

Table 5.6.2.27-1: Definition of type RuleReport

pccRuleIds array(string) M 1..N Contains the identifier of the affected
PCC rule(s).
ruleStatus RuleStatus M 1 Indicates the status of the PCC rule(s).
contVers array(ContentVers C 1..N Indicates the version of the PCC rule. If RuleVersioning
ion) rule versioning feature is supported, the
content version shall be included if it
was included when the corresponding
PCC rule was installed or modified.
failureCode FailureCode C 0..1 Indicates the reason that the PCC Rule
is being reported. It shall be included
when the SMF reports the enforcement
failure of the PCC rule(s).
finUnitAct FinalUnitAction O 0..1 Contains the related filter parameters
and redirect address parameters (if
available), when the user's account
cannot cover the service cost.
ranNasRelCauses array(RanNasRel O 1..N Indicates the RAN or NAS release RAN-NAS-
Cause) cause code information. Cause
5.6.2.28 Type RanNasRelCause

Table 5.6.2.28-1: Definition of type RanNasRelCause

ngApCause NgApCause O 0..1 Indicates the cause value of NGAP RAN-NAS-
protocol. Cause
5gMmCause 5GMmCause O 0..1 Indicates the cause value of 5GMM RAN-NAS-
protocol. Cause
5gSmCause 5GSmCause O 0..1 Indicates the cause value of 5GSM RAN-NAS-
protocol. Cause
5.6.2.29 Type UeInitiatedResourceRequest

Table 5.6.2.29-1: Definition of type UeInitiatedResourceRequest

pccRuleId string C 1 Indicates a PCC rule corresponding
to a QoS rule which is requested to
be modified or deleted by the UE.
ruleOp RuleOperation M 1 Indicates an operation for the PCC
rule.
packFiltInfo array(PacketFilterInfo) M 1..N Contains the information from a
single packet filter sent from the
SMF to the PCF.
precedence integer O 0..1 The requested order for the PCC
rule generated from the QoS rule
requested by the UE.
reqQos RequestedQos O 0..1 Contains the QoS information
3GPP
Release 16 122 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.30 Type PacketFilterInfo

Table 5.6.2.30-1: Definition of type PacketFilterInfo

packFiltId string O 0..1 An identifier of packet filter. For PCC
rules created as a result of UE-
initiated resource modification, the
packet filter identifier is assigned by
the PCF and is unique per UE and
PCF instance.
packFiltCont PacketFilterContent O 0..1 Contains the content of the packet
filter as requested by the UE and
required by the PCF to create the
PCC rules.
tosTrafficClass string O 0..1 2-octet string. The first octet contains
the Ipv4 Type-of-Service or the Ipv6
Traffic-Class field and the second
octet contains the ToS/Traffic mask
field in hexadecimal representation.
Each character in the string shall
take a value of "0" to "9" or "A" to "F"
and shall represent 4 bits. One
example is that of a TFT packet filter
as defined in 3GPP TS 24.008 [41].
spi string O 0..1 4 octet string, representing the
security parameter index of the
IPSec packet in hexadecimal
representation. Each character in the
string shall take a value of "0" to "9"
or "A" to "F" and shall represent 4
bits. One example is that of a TFT
packet filter as defined in
3GPP TS 24.008 [41].
flowLabel string O 0..1 3-octet string, representing the Ipv6
flow label header field in
shall represent 4 bits. One example
is that of a TFT packet filter as
defined in 3GPP TS 24.008 [41].
flowDirection FlowDirection O 0..1 Indicates the direction/directions that
a filter is applicable, downlink only,
uplink only or both down- and uplink
(bidirectional).
5.6.2.31 Type RequestedQos

Table 5.6.2.31-1: Definition of type RequestedQos

5qi 5Qi M 1 Identifier for the authorized QoS
parameters for the service data flow.
gbrUl BitRate O 0..1 Indicates the guaranteed bandwidth in
uplink requested by the UE.
gbrDl BitRate O 0..1 Indicates the max guaranteed in
downlink requested by the UE.
3GPP
Release 16 123 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.32 Type QosNotificationControlInfo

Table 5.6.2.32-1: Definition of type QosNotificationControlInfo

refPccRuleIds array(string) M 1..N An array of PCC rule id references to the
PCC rules associated with the
QosNotificationControlInfo.
notifType QosNotifType M 1 Indicates whether the GBR targets for
the indicated SDFs are
"NOT_GUARANTEED" or
"GUARANTEED" again.
contVers array(ContentV C 1..N Indicates the version of the PCC rule. If RuleVersioning
ersion) rule versioning feature is supported, the
content version shall be included if it was
included when the corresponding PCC
rule was installed or modified.
altQosParamId string O 0..1 Indicates the alternative QoS parameter AuthorizationWit
set the NG-RAN can guarantee. hRequiredQoS
5.6.2.33 Type PartialSuccessReport

Table 5.6.2.33-1: Definition of type PartialSuccessReport

failureCause FailureCause M 1 Application error cause specific to this
report.
ruleReports array(RuleReport) C 1..N Information about the PCC rules
provisioned by the PCF not successfully
installed/activated.
sessRuleReports array(SessionRule O 1..N Information about the session rules SessionRuleEr
Report) provisioned by the PCF not successfully rorHandling
installed.
ueCampingRep UeCampingRep O 0..1 Includes the current applicable values
corresponding to the provisioned policy
control request triggers.
policyDecFailure array(PolicyDecisio O 1..N Used to report the failure of the policy PolicyDecision
Reports nFailureCode) decision and/or condition data. ErrorHandling
NOTE: The "ruleReports" shall be included if the SessionRuleErrorHandling feature is not supported.
3GPP
Release 16 124 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.34 Type AuthorizedDefaultQos

Table 5.6.2.34-1: Definition of type AuthorizedDefaultQos

5qi 5Qi C 0..1 5G QoS Identifier. It shall be included
when the Authorized Default QoS is
initially provisioned.
arp Arp C 0..1 Indicates the allocation and retention
priority. It shall be included when the
Authorized Default QoS is initially
provisioned.
priorityLevel 5QiPriorityLevel O 0..1 Unsigned integer indicating the 5QI
Rm Priority Level, within a range of 1 to 127.
averWindow AverWindowRm O 0..1 Indicates the averaging window.
This IE can be present only for GBR QoS
flow or a Delay Critical GBR QoS flow.
maxDataBurstVol MaxDataBurstV O 0..1 Unsigned integer indicating the maximum
olRm data burst volume. (NOTE 2)
gbrUl BitRateRm O 0..1 Indicates the guaranteed bandwidth in
uplink. (NOTE 1)
gbrDl BitRateRm O 0..1 Indicates the guaranteed bandwidth in
downlink. (NOTE 1)
maxbrUl BitRateRm O 0..1 Indicates the max bandwidth in uplink.
(NOTE 1)
maxbrDl BitRateRm O 0..1 Indicates the max bandwidth in downlink.
(NOTE 1)
qnc boolean O 0..1 Indicates whether notifications are
requested from 3GPP NG-RAN when the
GFBR can no longer (or again) be
guaranteed for a QoS Flow during the
lifetime of the QoS Flow. Default value
not been supplied previously. (NOTE 1)
extMaxDataBurstVol ExtMaxDataBur O 0..1 Unsigned integer indicating the maximum EMDBV
stVolRm data burst volume. (NOTE 2)
NOTE 1: This attribute is only applicable to GBR type or delay critical GBR type 5QI.
NOTE 2: Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present for a Delay Critical GBR QoS
flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the
maxDataBurst Vol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the
extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes (see
subclause 4.2.2.1).
5.6.2.35 Type AccNetChargingAddress

Table 5.6.2.35-1: Definition of type AccNetChargingAddress

anChargIpv4Addr Ipv4Addr O 0..1 Includes the IPv4 address of network
entity within the access network
performing charging.
anChargIpv6Addr Ipv6Addr O 0..1 Includes the IPv6 address of network
entity within the access network
performing charging.
NOTE: At least one address of the access network entity (the IPv4 address or the IPv6 address or both if both
addresses are available) shall be included.
3GPP
Release 16 125 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.36 Type ErrorReport

Table 5.6.2.36-1: Definition of type ErrorReport

error ProblemDetails M 1 More information on the error shall be
provided in the "cause" attribute of the
"ProblemDetails" structure.
ruleReports array(RuleReport) O 1..N Used to report the PCC rule failure.
sessRuleReports array(SessionRule O 1..N Used to report the session rule failure. SessionRuleEr
Report) rorHandling
5.6.2.37 Type SessionRuleReport

Table 5.6.2.37-1: Definition of type SessionRuleReport

ruleIds array(string) M 1..N Contains the identifier of the affected
session rule(s).
ruleStatus RuleStatus M 1 Indicates the status of the session
rule(s).
sessRuleFailureCode SessionRuleFailu C 0..1 Indicates the reason that the session
reCode rule(s) is being reported. It shall be
included when the SMF reports the
enforcement failure of the session
rule(s).
5.6.2.38 Type ServingNfIdentity

Table 5.6.2.38-1: Definition of type ServingNfIdentity

servNfInstId NfInstanceId O 0..1 Network Function Instance Identifier of
the 5G serving CN node. It represents
the AMF.
guami Guami O 0..1 Globally Unique AMF Identifier.
anGwAddr AnGwAddress O 0..1 Contains the access network control
gateway address. It represents the S-
GW or ePDG address. (NOTE 2)
NOTE 1: At least one of the "servNfInstId", "guami", or "anGwAddr" attributes shall be present.
NOTE 2: "anGwAddr" attribute is only applicable to the 5GS and EPC (E-UTRAN and non-3GPP access) interworking
scenario as defined in Annex B.
3GPP
Release 16 126 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.39 Type SteeringMode

Table 5.6.2.39-1: Definition of type SteeringMode

steerModeValue SteerModeValue M 1 Indicates the value of the steering ATSSS
mode.
active AccessType C 0..1 Indicates the Active access. It shall be ATSSS
included when the "steerModeValue"
attribute is set to "ACTIVE_STANDBY".
standby AccessTypeRm O 0..1 Indicates the Standby access. It may be ATSSS
included when the "steerModeValue"
attribute is set to "ACTIVE_STANDBY".
3gLoad Uinteger C 0..1 Indicates the traffic load to steer to the ATSSS
3GPP Access expressed in one
percent.
It shall be set to 0, 10, 20, 30, 40, 50,
60, 70, 80, 90 or 100.
It shall be included when the
"steerModeValue" attribute is set to
"LOAD_BALANCING".
prioAcc AccessType C 0..1 Indicates the high priority access. ATSSS
It shall be included when the
"steerModeValue" attribute is set to
"PRIORITY_BASED".
3GPP
Release 16 127 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.40 Type QosMonitoringData

Table 5.6.2.40-1: Definition of type QosMonitoringData

qmId string M 1 Univocally identifies the QoS monitoring
reqQosMonParams array(Requeste M 1..N Indicates the UL packet delay, DL packet
dQosMonitoring delay and/or round trip packet delay
Parameter) between the UE and the UPF is to be
monitored when the QoS Monitoring for
URLLC is enabled for the service data
flow. (NOTE)
repFreqs array(Reporting M 1..N indicates the frequency for the reporting,
Frequency) such as event triggered, periodic, when
the PDU Session is released, and/or any
combination.
repThreshDl integer O 0..1 Unsigned integer identifying a threshold in
units of milliseconds for DL packet delay.
Only applicable when the
"reqQosMonParams" attribute includes the
"DOWNLINK" value and the "repFreqs"
attribute includes the value
"EVENT_TRIGGERED".
repThreshUl integer O 0..1 Unsigned integer identifying a threshold in
units of milliseconds for UL packet delay.
Only applicable when the
"UPLINK" value and the "repFreqs"
"EVENT_TRIGGERED".
repThreshRp integer O 0..1 Unsigned integer identifying a threshold in
units of milliseconds for round trip packet
delay. Only applicable when the
"ROUND_TRIP" value and the "repFreqs"
"EVENT_TRIGGERED".
waitTime DurationSecRm O 0..1 Indicates the minimum waiting time
between subsequent reports. Only
applicable when the "repFreqs" attribute
includes the value
"EVENT_TRIGGERED".
repPeriod DurationSecRm O 0..1 Indicates the reporting period. Only
applicable when the "repFreqs" attribute
includes the value "PERIODIC".
notifUri Uri O 0..1 Notification address of AF receiving the
event notification. It shall be included if the
PCF determines that the notification shall
be sent to the AF directly from the SMF.
notifCorreId string O 0..1 It is used to set the value of Notification
Correlation ID in the notification sent by
the SMF. It may be included if the PCF
determines that the notification shall be
sent to the AF directly from the SMF.
NOTE: In this release of the specification the maximum number of elements in the array is 3.
3GPP
Release 16 128 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.41 Type TsnBridgeInfo

Table 5.6.2.41-1: Definition of type TsnBridgeInfo

bridgeId Uint64 O 0..1 Contains the bridge Id defined in
IEEE 802.1Q [45] clause 14.2.5.
dsttAddr MacAddr48 O 0..1 Contain the MAC address of DS-TT.
nwttPortNums array(TsnPort O 1..N NW-TT ports available for a PDU session.
Number)
dsttPortNum TsnPortNumb O 0..1 DS-TT port allocated to a PDU session.
er
dsttResidTime Uinteger O 0..1 The time taken within the UE and DS-TT to
forward a packet between the UE/DS-TT port
encoded as specified in subclause 9.11.4.26
of 3GPP TS 24.501 [20] starting with octet 2.
5.6.2.42 Type QosMonitoringReport

Table 5.6.2.42-1: Definition of type QosMonitoringReport

refPccRuleIds array(string) M 1..N An array of PCC rule id references to
the PCC rules associated with the QoS
Monitoring report.
ulDelays array(integer) O 1..N Uplink packet delay in units of
milliseconds. (NOTE)
dlDelays array(integer) O 1..N Downlink packet delay in units of
rtDelays array(integer) O 1..N Round trip delay in units of
NOTE: In this release of the specification the maximum number of elements in the array is 2. If more than one value
is received at one given point of time for UL packet delay, DL packet delay or round trip packet delay
respectively, the SMF reports the minimum and maximum packet delays to the PCF.
5.6.2.43 Type AdditionalAccessInfo

Table 5.6.2.43-1: Definition of type AdditionalAccessInfo

accessType AccessType M 0..1 The Access Type where the served UE is ATSSS
camping.
ratType RatType O 0..1 The RAT Type where the served UE is ATSSS
camping.
5.6.2.44 Void
3GPP
Release 16 129 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.2.45 Type PortManagementContainer

Table 5.6.2.45-1: Definition of type PortManagementContainer

portManCont Bytes M 1 Transports TSN port management
information for a DS-TT port or a NW-
TT port encoded as specified in
subclause 9.11.4.27 of
3GPP TS 24.501 [20] starting with
octet 4.
portNum TsnPortNumber M 1 Provides port number for a DS-TT port
or a NW-TT port.
5.6.2.46 Type IpMulticastAddressInfo

Table 5.6.2.46-1: IpMulticastAddressInfo

srcIpv4Addr Ipv4Addr C 0..1 Indicates the source IPv4 address of
the DL multicast flow. Maybe included
if the "ipv4MulAddr" attribute is
included.
ipv4MulAddr Ipv4Addr O 0..1 Indicates the destination IPv4
multicast address of the DL multicast
flow.
srcIpv6Addr Ipv6Addr C 0..1 Indicates the source IPv6 address of
the DL multicast flow. Maybe included
if the "ipv6MulAddr" attribute is
included.
ipv6MulAddr Ipv6Addr O 0..1 Indicates the destination IPv6
multicast address of the DL multicast
flow.
NOTE: Either "ipv4MulAddr" attribute or "ipv6MulAddr" attribute shall be included.
5.6.2.47 Type BridgeManagementContainer

Table 5.6.2.47-1: Definition of type BridgeManagementContainer

bridgeManCont Bytes M 1 Transports a Bridge management
service message encoded as
specified in subclause 8.7 of
3GPP TS 24.519 [44].
5.6.3 Simple data types and enumerations
5.6.3.1 Introduction
This subclause defines simple data types and enumerations that can be referenced from data structures defined in the
previous subclauses.
5.6.3.2 Simple data types

The simple data types defined in table 5.6.3.2-1 shall be supported. For additional simple data types see
3GPP TS 29.571 [11].
3GPP
Release 16 130 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.6.3.2-1: Simple data types
Type Name Type Definition Description Applicability

5GSmCause Uinteger Indicates the 5GSM cause code value as defined in RAN-NAS-Cause
subclause 9.10.4.2 of 3GPP TS 24.501 [20].
FlowDescription string Defines a packet filter for an IP flow.
Refer to subclause 5.4.2 of 3GPP TS 29.212 [23] for
encoding.
PacketFilterContent string Defines a packet filter for an IP flow.
Refer to subclause 5.3.54 of 3GPP TS 29.212 [23] for
encoding.
TsnPortNumber Uinteger Port number of a DS-TT or NW-TT port. TimeSensitiveNetwo
rking
ApplicationDescript Bytes Defines the OS Id and the OS application identifier for ATSSS
or an ATSSS rule, where the OS Id is optional.
It is a sequence of octets representing the traffic
descriptor(s) of the ATSS rule as Os Id, if applicable,
and Os App Id as defined in table 6.1.3.2-1 of
3GPP TS 24.193 [43].
5.6.3.3 Enumeration: FlowDirection

Table 5.6.3.3-1: Enumeration FlowDirection
Enumeration value Description Applicability

DOWNLINK The corresponding filter applies for traffic to the UE.
UPLINK The corresponding filter applies for traffic from the UE.
BIDIRECTIONAL The corresponding filter applies for traffic both to and from the UE.
UNSPECIFIED The corresponding filter applies for traffic to the UE (downlink), but
has no specific direction declared. The service data flow detection
shall apply the filter for uplink traffic as if the filter was bidirectional.
The PCF shall not use the value UNSPECIFIED in filters created by
the network in NW-initiated procedures. The PCF shall only include
the value UNSPECIFIED in filters in UE-initiated procedures if the
same value is received from the SMF.
5.6.3.4 Enumeration: ReportingLevel

Table 5.6.3.4-1: Enumeration ReportingLevel

SER_ID_LEVEL Indicates that the usage shall be reported on service id
and rating group combination level.
RAT_GR_LEVEL Indicates that the usage shall be reported on rating group
level.
SPON_CON_LEVEL Indicates that the usage shall be reported on sponsor
identity and rating group combination level.
3GPP
Release 16 131 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.3.5 Enumeration: MeteringMethod

Table 5.6.3.5-1: Enumeration MeteringMethod

DURATION Indicates that the duration of the service data flow traffic shall be
metered.
VOLUME Indicates that volume of the service data flow traffic shall be
metered.
DURATION_VOLUME Indicates that the duration and the volume of the service data
flow traffic shall be metered.
EVENT Indicates that events of the service data flow traffic shall be
metered.
3GPP
Release 16 132 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.3.6 Enumeration: PolicyControlRequestTrigger

Table 5.6.3.6-1: Enumeration PolicyControlRequestTrigger

PLMN_CH PLMN Change.
RES_MO_RE A request for resource modification has been received by the
SMF. (NOTE)
AC_TY_CH Access Type Change. It also indicates the addition or removal of
Access Type for MA PDU session.
UE_IP_CH UE IP address change. (NOTE)
UE_MAC_CH A new UE MAC address is detected or a used UE MAC address
is inactive for a specific period.
AN_CH_COR Access Network Charging Correlation Information.
US_RE The PDU Session or the Monitoring key specific resources UMC
consumed by a UE either reached the threshold or needs to be
reported for other reasons.
APP_STA The start of application traffic has been detected. ADC
APP_STO The stop of application traffic has been detected. ADC
AN_INFO Access Network Information report. NetLoc
CM_SES_FAIL Credit management session failure.
PS_DA_OFF The SMF reports when the 3GPP PS Data Off status changes. 3GPP-PS-Data-Off
(NOTE)
DEF_QOS_CH Default QoS Change. (NOTE)
SE_AMBR_CH Session AMBR Change. (NOTE)
QOS_NOTIF The SMF notify the PCF when receiving notification from RAN
that QoS targets of the QoS Flow cannot be guaranteed or can
be guaranteed.
NO_CREDIT Out of credit.
REALLO_OF_CREDIT Reallocation of credit ReallocationOfCred
it
PRA_CH Change of UE presence in Presence Reporting Area. PRA
SAREA_CH Location Change with respect to the Serving Area.
SCNN_CH Location Change with respect to the Serving CN node.
RE_TIMEOUT Indicates the SMF generated the request because there has
been a PCC revalidation timeout (i.e. Enforced PCC rule request
defined in table 6.1.3.5.-1 of 3GPP TS 29.503 [6]).
RES_RELEASE Indicates that the SMF can inform the PCF of the outcome of the RAN-NAS-Cause
release of resources for those rules that require so.
SUCC_RES_ALLO Indicates that the SMF shall inform the PCF of the successful
resource allocation for those rules that requires so.
RAT_TY_CH RAT type change.
REF_QOS_IND_CH Reflective QoS indication Change.
NUM_OF_PACKET_FILTE Indicates that the SMF shall report the number of supported
R packet filter for signalled QoS rules. (NOTE) Only applicable to
the interworking scenario as defined in Annex B.
UE_STATUS_RESUME Indicates that the UE’s status is resumed. Only applicable to the PolicyUpdateWhen
interworking scenario as defined in Annex B. UESuspends
UE_TZ_CH UE Time Zone Change.
AUTH_PROF_CH Indicates that the DN-AAA authorization profile index has DN-Authorization
changed. (NOTE)
TSN_BRIDGE_INFO Indicates the SMF has detected new 5GS Bridge information. TimeSensitiveNetw
orking
QOS_MONITORING Indicate that the SMF notifies the PCF of the QoS Monitoring QosMonitoring
information.
SCELL_CH Location Change with respect to the Serving Cell. Only
applicable to the interworking scenario as defined in Annex B.
EPS_FALLBACK EPS Fallback report is enabled in the SMF. Only applicable to EPSFallbackReport
the interworking scenario as defined is Annex B.
MA_PDU Indicates that the SMF notifies the PCF of the MA PDU session ATSSS
request. Only applicable to the interworking scenario as defined
in Annex B. (NOTE)
5G_RG_JOIN The 5G-RG has joined to an IP Multicast Group. WWC
5G_RG_LEAVE The 5G-RG has left an IP Multicast Group. WWC
3GPP
Release 16 133 3GPP TS 29.512 V16.5.0 (2020-06)
DDN_FAILURE Indicates that the SMF requests policies from PCF if it received DDNEventPolicyCo
an event subscription for DDN Failure event. ntrol
DDN_DELIVERY_STATUS Indicates that the SMF requests policies from PCF if it received DDNEventPolicyCo
an event subscription for DDN Delievery Status event. ntrol
NOTE: The SMF always reports to the PCF.
The PCF may provision the values of policy control request trigger which are not always reported by the SMF as
defined in subclause 4.2.6.4.
When the SMF detects the corresponding policy control request trigger(s), the SMF shall report the detected trigger(s)
to the PCF as defined in subclause 4.2.4.1 with the additional information for different independent policy control
request triggers as follows:
If the "PLMN_CH" is provisioned, when the SMF detects a change of PLMN, the SMF shall include the "PLMN_CH"
within the "repPolicyCtrlReqTriggers" attribute and the current identifier of the serving network within the
"servingNetwork" attribute.
When the SMF receives the resource modification request from the UE, the SMF shall include the "RES_MO_RE"
within the "repPolicyCtrlReqTriggers" attribute and the information for requesting the PCC rule as defined in
subclause 4.2.4.17.
If the "AC_TY_CH" is provisioned, when the SMF detects a change of access type, the SMF shall include the
"AC_TY_CH" within the "repPolicyCtrlReqTriggers" attribute and the current access type within the "accessType"
attribute. The RAT type encoded in the "ratType" attribute shall also be provided when applicable to the specific access
type. Specific attributes for the EPC interworking case are described in Annex B. If the ATSSS feature is supported,
when the SMF detects an access is added or released for MA PDU session, the SMF shall include the added Access
Type or released Access type encoded as "accessType" attribute within the AdditionalAccessInfo data structure. The
RAT type encoded in the "ratType" attribute shall also be provided within the AdditionalAccessInfo data structure when
applicable to the added access type or released access type.
When the SMF detects an IPv4 address and/or an IPv6 prefix is allocated or released, the SMF shall include the
"UE_IP_CH" within the "repPolicyCtrlReqTriggers" attribute and new allocated UE Ipv4 address within the
"ipv4Address" attribute and/or the UE Ipv6 prefix within the "ipv6AddressPrefix" attribute or the released UE Ipv4
address within the "relIpv4Address" attribute and/or the UE Ipv6 prefix within the "relIpv6AddressPrefix" attribute. If
the "MultiIpv6AddrPrefix" feature is supported ,and if multiple allocated or released IPv6 prefixes are detected, the
SMF shall include the new allocated UE Ipv6 prefixes within the "addIpv6AddrPrefixes" attribute and the released UE
Ipv6 prefixes within the "addRelIpv6AddrPrefixes" attribute.
When the SMF detects a new UE MAC address or a used UE MAC address is not used any more, the SMF shall include
the "UE_MAC_CH" within the "repPolicyCtrlReqTriggers" attribute and new detected UE MAC address within the
"ueMac" attribute or the not used UE MAC address within the "relUeMac" attribute.
If the "AN_CH_COR" is provisioned, when the SMF is provisioned with the PCC rule as defined in subclause 4.2.6.5.1,
the SMF shall notify the PCF of access network charging identifier associated with the PCC rules as defined in
subclause 4.2.4.13.
If the "US_RE" is provisioned, when the SMF receives the usage report from the UPF, the SMF shall notify the PCF of
the accumulated usage as defined in subclause 4.2.4.10. Applicable to functionality introduced with the UMC feature as
described in subclause 5.8.
If the "APP_STA" is provisioned, when the SMF receives the application start report from the UPF, the SMF shall
notify the PCF of the application start report as defined in subclause 4.2.4.6. Applicable to functionality introduced with
the ADC feature as described in subclause 5.8.
If the "APP_STO" is provisioned, when the SMF receives the application stop report from the UPF, the SMF shall
notify the PCF of the application stop report as defined in subclause 4.2.4.6. Applicable to functionality introduced with
the ADC feature as described in subclause 5.8.
If the "AN_INFO" is provisioned, when the SMF receives the reported access network information from the access
network, the SMF shall notify the PCF of the access network information as defined in subclause 4.2.4.9. Applicable to
functionality introduced with the NetLoc feature as described in subclause 5.8.
If the "CM_SES_FAIL" is provisioned, when the SMF receives a detected transient/permanent failure from the CHF,
the SMF shall include the "CM_SES_FAIL" within the "repPolicyCtrlReqTriggers" attribute. If the failure does not
3GPP
Release 16 134 3GPP TS 29.512 V16.5.0 (2020-06)
apply to all PCC Rules, the affected PCC Rules are indicated within the "ruleReports" attribute, with the "ruleStatus"
attribute set to value ACTIVE and the "failureCode" attribute set to the corresponding value as reported by the CHF;
otherwise if the failure applies to the session, the "creditManageStatus" shall be set to the corresponding value as
reported by the CHF.
If the "PS_DA_OFF" is provisioned, when the SMF receives a change of 3GPP PS Data Off status from the UE, the
SMF shall notify the PCF as defined in subclause 4.2.4.8. Applicable to functionality introduced with the 3GPP-PS-
Data-Off feature as described in subclause 5.8.
When the SMF detects a change of subscribed default QoS, the SMF shall include the "DEF_QOS_CH" within the
"repPolicyCtrlReqTriggers" attribute and the new subscribed default QoS within the "subsDefQos" attribute.
When the SMF detects a change of Session-AMBR, the SMF shall include the "SE_AMBR_CH" within the
"repPolicyCtrlReqTriggers" attribute and the new Session-AMBR within the "subsSessAmbr" attribute.
If the "QOS_NOTIF" is provisioned, when the SMF receives a notification from access network that QoS targets of the
QoS Flow cannot be guaranteed or can be guaranteed again, the SMF shall send the notification as defined in
subclause 4.2.4.20.
When the "ReallocationOfCredit" feature is supported, if the "NO_CREDIT" is provisioned, when the SMF detects the
credit for the PCC rule(s) is no longer available, the SMF shall include the "NO_CREDIT" within the
"repPolicyCtrlReqTriggers" attribute, the termination action the SMF applies to the PCC rules as instructed by the CHF
within the "finUnitAct" attribute and the affected PCC rules within the "ruleReports" attribute.
If the "REALLO_OF_CREDIT" is provisioned, when the SMF detects the credit for the PCC rule(s) is reallocated, the
SMF shall include the "REALLO_OF_CREDIT" within the "repPolicyCtrlReqTriggers" attribute and include the
affected PCC rules for which credit has been reallocated after credit was no longer available and the "ruleStatus"
attribute set to value ACTIVE within the "ruleReports" attribute.
If the "PRA_CH" is provisioned, the SMF is provisioned the presence reporting area information as defined in
subclause 4.2.6.5.6. When the SMF receives the presence reporting area information from the serving node, the SMF
shall notify the PCF of the reported presence area information as defined in subclause 4.2.4.16. Applicable to
functionality introduced with the PRA feature as described in subclause 5.8.
If the "SAREA_CH" is provisioned, when the SMF detects a change of serving area (i.e. tracking area), the SMF shall
include the "SAREA_CH" within the "repPolicyCtrlReqTriggers" attribute and the current TAI within the
"userLocationInfo" attribute in either the "eutraLocation" or "nrLocation", as applicable. Non-3GPP access user
location is reported in the "n3gaLocation" attribute when applicable. The attributes used in case of EPC interworking
are described in Annex B.
If the "SCNN_CH" is provisioned, when the SMF detects a change of serving Network Function (i.e. the AMF, ePDG
or S-GW), the SMF shall include the "SCNN_CH" within the "repPolicyCtrlReqTriggers" attribute and the current
serving Network Function in the "servNfId" attribute if available. When the serving Network Function is an AMF, the
SMF shall include the AMF Network Function Instance Identifier within the "servNfInstId" attribute and the Globally
Unique AMF Identifier within the "guami" attribute. The attributes included in case of EPC interworking are described
in Annex B.
NOTE 1: In the home-routed roaming case, if the AMF change is unknown to the H-SMF, then the AMF change is
not reported.
If the "RE_TIMEOUT" is provisioned, the SMF is provisioned the revalidation time by the PCF. The SMF shall request
the policy before the indicated the revalidation time as defined in subclause 4.2.4.13.
If the "RES_RELEASE" is provisioned, when the SMF receives the request of PCC rule removal as defined in
subclause 4.2.6.5.2, the SMF shall report the outcome of resource release as defined in subclause 4.2.4.12. Applicable
to functionality introduced with the RAN-NAS-Cause feature as described in subclause 5.8.
When "SUCC_RES_ALLO" is provisioned and PCC rules are provisioned according to subclause 4.2.6.5.5, the SMF
shall inform the PCF of the successful resource allocation as defined in subclause 4.2.4.14.
If the "RAT_TY_CH" is provisioned, when the SMF detects a change of the RAT type, the SMF shall include the
"RAT_TY_CH" within the "repPolicyCtrlReqTriggers" attribute and the current RAT type within the "ratType"
attribute. For MA PDU session, the SMF shall include the current RAT type at the SmPolicyUpdateContextData data
type level or AdditionalAccessInfo data type level. If the RAT type is provided at the SmPolicyUpdateContextData data
type level, the SMF shall also provide the associated access type within the SmPolicyUpdateContextData data structure.
3GPP
Release 16 135 3GPP TS 29.512 V16.5.0 (2020-06)
If the "REF_QOS_IND_CH" is provisioned, when the SMF receives a change of reflective QoS indication from the UE,
the SMF shall include the "REF_QOS_IND_CH" within the "repPolicyCtrlReqTriggers" attribute and the indication
within the "refQosIndication" attribute.
When the SMF receives the number of supported packet filter for signalled QoS rules for the PDU session from the UE
during the PDU Session Modification procedure after the first inter-system change from EPS to 5GS for a PDU Session
established in EPS and transferred from EPS with N26 interface, the SMF shall include the
"NUM_OF_PACKET_FILTER" within the "repPolicyCtrlReqTriggers" attribute and the number of supported packet
filter for signalled QoS rules within the "numOfPackFilter" attribute. Only applicable to the interworking scenario as
defined in Annex B.
If the "UE_STATUS_RESUME" is provisioned, when the SMF detected the UE’s status is resumed from suspend state,
the SMF shall inform the PCF of the UE status including the "UE_STATUS_RESUME" within
"repPolicyCtrlReqTriggers" attribute. The PCF shall after this update the SMF with PCC Rules or session rules if
necessary. Applicable to functionality introduced with the PolicyUpdateWhenUESuspends feature as described in
subclause 5.8.
If the "UE_TZ_CH" is provisioned, when the SMF detects a change of the UE Time Zone, the SMF shall include the
"UE_TZ_CH" within the "repPolicyCtrlReqTriggers" attribute and the current UE Time Zone within the "ueTimeZone"
attribute.
If the "DN-Authorization" feature is supported, when the SMF detects a change of DN-AAA authorization profile
index, the SMF shall include the "AUTH_PROF_CH" within the "repPolicyCtrlReqTriggers" attribute and the new DN-
AAA authorization profile index within the "authProfIndex" attribute.
If the "TimeSensitiveNetworking" feature is supported and "TSN_BRIDGE_INFO" is provisioned, when the SMF
detects:
- there is new or updated 5G Bridge information, e.g. a new manageable Ethernet port, the SMF shall include the
"TSN_BRIDGE_INFO" within the "repPolicyCtrlReqTriggers" attribute and the updated TSN bridge
information within the "tsnBridgeInfo" attribute; and/or
- the SMF detects a Bridge Management or Port Management Container, the SMF shall include the
"TSN_BRIDGE_INFO" within the "repPolicyCtrlReqTriggers" attribute and the Bridge Management Container,
if available, within the "tsnBridgeManCont" attribute, and/or the Port Management Container(s), if available,
within the "tsnPortManContDstt" and the "tsnPortManContNwtt" attributes.
NOTE 2: When the SMF detects that a new NW-TT port is added or an existing NW-TT port is deleted, the SMF
includes all the available NW-TT ports within the "nwttPorts" attribute of the "tsnBridgeInfo" attribute.
When the SMF detects updated Port Management Information of the NW-TT ports, the SMF includes the
Port Management Information within the "tsnPortManContNwtts" attribute of
SmPolicyUpdateContextData data type.
If the "QOS_MONITORING" is provisioned, upon receiving the QoS Monitoring report from the UPF, the SMF shall
send the QoS monitoring report to the PCF as defined in subclause 4.2.4.24.
If the "SCELL_CH" is provisioned, when the SMF detects a change of serving cell, the SMF shall include the
"SCELL_CH" within the "repPolicyCtrlReqTriggers" attribute and the current cell Id within the "userLocationInfo"
attribute in the "eutraLocation" attribute, as applicable. The attributes used in case of EPC interworking are described in
Annex B.
If the "EPSFallbackReport" feature is supported and the "EPS_FALLBACK" is provisioned and there is a PCC rule
installed that required the reporting, when the SMF receives a PDU session modification response indicating the
rejection of the establishment of the QoS flow with 5QI=1, the SMF shall notify the PCF of EPS fallback as defined in
subclause B.3.4.6.
When the SMF receives the MA PDU Request Indication or MA PDU Network-Upgrade Allowed Indication and
ATSSS Capability from the UE during the PDU Session Modification procedure after the first inter-system change from
EPS to 5GS for a PDU Session established in EPS and transferred from EPS with N26 interface, the SMF shall include
the "MA_PDU" within the "repPolicyCtrlReqTriggers" attribute, the MA PDU session Indication in the "maPduInd"
attribute, the ATSSS capability of the MA PDU session within the "atsssCapab" attribute. Only applicable to the
interworking scenario as defined in Annex B.
3GPP
Release 16 136 3GPP TS 29.512 V16.5.0 (2020-06)
If the "WWC" feature is supported and "5G_RG_JOIN" is provisioned and when the SMF detects a 5G-RG has joined
to an IP Multicast Group, the SMF shall include the "5G_RG_JOIN" within the "repPolicyCtrlReqTriggers" attribute
and the IP multicast addressing information within the "mulAddrInfos" attribute.
If the "WWC" feature is supported and "5G_RG_LEAVE" is provisioned and when the SMF detects a 5G-RG has left
an IP Multicast Group, the SMF shall include the "5G_RG_LEAVE" within the "repPolicyCtrlReqTriggers" attribute
and the IP multicast addressing information within the "mulAddrInfos" attribute.
If "DDNEventPolicyControl" feature is supported, and if "DDN_FAILURE" is provisioned, when the SMF receives an
event subscription for DDN Failure event including the traffic descriptors, the SMF shall include the "DDN_FAILURE"
within the "repPolicyCtrlReqTriggers" attribute and traffic descriptor within the "trafficDescriptor" attribute.
If "DDNEventPolicyControl" feature is supported, and if "DDN_DELIVERY_STATUS" is provisioned, when the SMF

receives an event subscription for DDN Delievery Status event including the traffic descriptors, the SMF shall include
the "DDN_DELIVERY_STATUS" within the "repPolicyCtrlReqTriggers" attribute and traffic descriptor within the
"trafficDescriptor" attribute.
5.6.3.7 Enumeration: RequestedRuleDataType

Table 5.6.3.7-1: Enumeration RequestedRuleDataType

CH_ID Indicates that the requested rule data is the
charging identifier.
MS_TIME_ZONE Indicates that the requested access network info
type is the UE's timezone. (NOTE)
USER_LOC_INFO Indicates that the requested access network info
type is the UE's location. (NOTE)
RES_RELEASE Indicates that the requested rule data is the result of
the release of resource.
SUCC_RES_ALLO Indicates that the requested rule data is the
successful resource allocation.
EPS_FALLBACK Indicates that the requested rule data is the report of EPSFallbackReport
QoS flow rejection due to EPS fallback.
NOTE: The requested rule data shall also be reported at QoS flow termination and PDU session termination.
5.6.3.8 Enumeration: RuleStatus

Table 5.6.3.8-1: Enumeration RuleStatus

ACTIVE Indicates that the PCC rule(s) are successfully installed (for
those provisioned from PCF) or activated (for those pre-defined
in SMF), or the session rule(s) are successfully installed.
INACTIVE Indicates that the PCC rule(s) are removed (for those
provisioned from PCF) or inactive (for those pre-defined in SMF)
or the session rule(s) are removed.
3GPP
Release 16 137 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.3.9 Enumeration: FailureCode

Table 5.6.3.9-1: Enumeration FailureCode

UNK_RULE_ID Indicates that the pre-provisioned PCC rule could not be
successfully activated because the PCC rule identifier is unknown
to the SMF.
RA_GR_ERR Indicates that the PCC rule could not be successfully installed or
enforced because the Rating Group specified within the Charging
Data policy decision which the PCC rule refers to is unknown or,
invalid.
SER_ID_ERR Indicates that the PCC rule could not be successfully installed or
enforced because the Service Identifier specified within the
Charging Data policy decision which the PCC rule refers to is
invalid, unknown, or not applicable to the service being charged.
NF_MAL Indicates that the PCC rule could not be successfully installed (for
those provisioned from the PCF) or activated (for those pre-
defined in SMF) or enforced (for those already successfully
installed) due to SMF/UPF malfunction.
RES_LIM Indicates that the PCC rule could not be successfully installed (for
those provisioned from PCF) or activated (for those pre-defined in
SMF) or enforced (for those already successfully installed) due to
a limitation of resources at the SMF/UPF.
MAX_NR_QoS_FLOW Indicates that the PCC rule could not be successfully installed (for
those provisioned from PCF) or activated (for those pre-defined in
SMF) or enforced (for those already successfully installed) due to
the fact that the maximum number of QoS flows has been
reached for the PDU session.
MISS_FLOW_INFO Indicates that the PCC rule could not be successfully installed or
enforced because neither the "flowInfos" attribute nor "appId"
attribute is specified within the "pccRule" attribute by the PCF
during the first install request of the PCC rule.
RES_ALLO_FAIL Indicates that the PCC rule could not be successfully installed or
maintained since the QoS flow establishment/modification failed,
or the QoS flow was released.
UNSUCC_QOS_VAL This value is used to:
- indicate that the QoS validation has failed or,
- Indicate when Guaranteed Bandwidth > Max-Requested-
Bandwidth.
INCOR_FLOW_INFO Indicates that the PCC rule could not be successfully installed or
modified at the SMF because the provided flow information is not
supported by the network (e.g. the provided IP address(es) or
Ipv6 prefix(es) do not correspond to an IP version applicable for
the PDU session).
PS_TO_CS_HAN Indicates that the PCC rule could not be maintained because of
PS to CS handover.
APP_ID_ERR Indicates that the PCC rule could not be successfully installed or
enforced because the Application Identifier is invalid, unknown, or
not applicable to the application required for detection.
NO_QOS_FLOW_BOUND Indicates that there is no QoS flow which the SMF can bind the
PCC rule(s) to.
FILTER_RES Indicates that the Flow Information within the "flowinfos" attribute
cannot be handled by the SMF because any of the restrictions
defined in subclause 5.4.2 of 3GPP TS 29.212 [23] was not met.
MISS_REDI_SER_ADDR Indicates that the PCC rule could not be successfully installed or
enforced at the SMF because there is no valid Redirect Server
Address within the Traffic Control Data policy decision which the
PCC rule refers to, provided by the PCF, and no preconfigured
redirection address for this PCC rule at the SMF.
CM_END_USER_SER_D Indicates that the charging system denied the service request due
ENIED to service restrictions (e.g. terminate rating group) or limitations
related to the end-user, for example the end-user's account could
not cover the requested service.
3GPP
Release 16 138 3GPP TS 29.512 V16.5.0 (2020-06)
CM_CREDIT_CON_NOT_ Indicates that the charging system determined that the service
APP can be granted to the end user but no further credit control is
needed for the service (e.g. service is free of charge or is treated
for offline charging).
CM_AUTH_REJ Indicates that the charging system denied the service request in
order to terminate the service for which credit is requested.
CM_USER_UNK Indicates that the specified end user could not be found in the
charging system.
CM_RAT_FAILED Indicates that the charging system cannot rate the service request
due to insufficient rating input, incorrect AVP combination or due
to an attribute or an attribute value that is not recognized or
supported in the rating.
UE_STA_SUSP Indicates that the UE is in suspend state. Only applicable to the PolicyUpdateWhen
5.6.3.10 Enumeration: AfSigProtocol

Table 5.6.3.10-1: Enumeration AfSigProtocol

NO_INFORMATION Indicate that no information about the AF signalling ProvAFsignalFlow
protocol is being provided. This is the default value.
SIP Indicate that the signalling protocol is Session Initiation ProvAFsignalFlow
Protocol.
5.6.3.11 Enumeration: RuleOperation

Table 5.6.3.11-1: Enumeration RuleOperation

CREATE_PCC_RULE Indicates to create a new PCC rule to reserve
the resource requested by the UE.
DELETE_PCC_RULE Indicates to delete a PCC rule corresponding
to reserve the resource requested by the UE.
MODIFY_PCC_RULE_AND_ADD_PACKET Indicates to modify the PCC rule by adding
_FILTERS new packet filter(s).
MODIFY_PCC_RULE_AND_REPLACE_PA Indicates to modify the PCC rule by replacing
CKET_FILTERS the existing packet filter(s).
MODIFY_PCC_RULE_AND_DELETE_PAC Indicates to modify the PCC rule by deleting
KET_FILTERS the existing packet filter(s).
MODIFY_PCC_RULE_WITHOUT_MODIFY Indicates to modify the PCC rule by modifying
_PACKET_FILTERS the QoS of the PCC rule.
5.6.3.12 Enumeration: RedirectAddressType

Table 5.6.3.12-1: Enumeration RedirectAddressType

IPV4_ADDR Indicates that the address type is in the form of "dotted-
decimal" IPv4 address.
IPV6_ADDR Indicates that the address type is in the form of IPv6
address.
URL Indicates that the address type is in the form of Uniform
Resource Locator.
SIP_URI Indicates that the address type is in the form of SIP
Uniform Resource Identifier.
3GPP
Release 16 139 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.3.13 Enumeration: QosFlowUsage

Table 5.6.3.13-1: Enumeration QosFlowUsage

GENERAL Indicates no specific QoS flow usage information is available.
IMS_SIG Indicates that the QoS flow is used for IMS signalling only.
5.6.3.14 Enumeration: FailureCause

Table 5.6.3.14-1: Enumeration FailureCause

PCC_RULE_EVENT Some of the PCC rules provisioned by the PCF in the request
cannot be installed/activated. It is used to inform the PCF that the
request failed and should not be attempted again.
PCC_QOS_FLOW_EVENT For some reason some of the PCC rules provisioned by the PCF in
the request cannot be enforced or modified successfully in a
network initiated procedure. It is used to inform the PCF that the
request could not be satisfied at the time it was received, but may
be able to satisfy the request in the future.
RULE_PERMANENT_ERR The HTTP request is rejected because some of the PCC and/or SessionRuleError
OR session rules provisioned by the PCF in the request cannot be Handling
installed/activated. It is used to inform the PCF that the request
failed, and should not be attempted again.
RULE_TEMPORARY_ERR The HTTP request is rejected because for some reason some of SessionRuleError
OR the PCC and/or session rules provisioned by the PCF in the Handling
request cannot be enforced or modified successfully in a network
initiated procedure. It is used to inform the PCF that the request
could not be satisfied at the time it was received, but may be able
to satisfy the request in the future.
5.6.3.15 Enumeration: FlowDirectionRm

This data type is defined in the same way as the "FlowDirection" data type, but also allows null value (specified as
"NullValue" data type).
5.6.3.16 Enumeration: CreditManagementStatus

Table 5.6.3.16-1: Enumeration CreditManagementStatus

END_USER_SER_DENIED Indicates that the charging system denied the service request due
to service restrictions (e.g. terminate rating group) or limitations
related to the end-user, for example the end-user's account could
not cover the requested service.
CREDIT_CTRL_NOT_APP Indicates that the charging system determined that the service can
be granted to the end user but no further credit control is needed
for the service (e.g. service is free of charge or is treated for offline
charging).
AUTH_REJECTED Indicates that the charging system denied the service request in
order to terminate the service for which credit is requested.
USER_UNKNOWN Indicates that the specified end user could not be found in the
charging system.
RATING_FAILED Indicates that the charging system cannot rate the service request
due to insufficient rating input, incorrect attribute combination or
an attribute value that is not recognized or supported in rating.
3GPP
Release 16 140 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.3.17 Enumeration: SessionRuleFailureCode

Table 5.6.3.17-1: Enumeration SessionRuleFailureCode

NF_MAL Indicates that the session rule could not be successfully installed)
or enforced (for those already successfully installed) due to
SMF/UPF malfunction.
RES_LIM Indicates that the session rule could not be successfully installed
or enforced (for those already successfully installed) due to a
limitation of resources at the SMF/UPF.
UNSUCC_QOS_VAL Indicate that the QoS validation has failed.
UE_STA_SUSP Indicates that the UE is in suspend state. Only applicable to the PolicyUpdateWhen
5.6.3.18 Enumeration: SteeringFunctionality

Table 5.6.3.18-1: Enumeration SteeringFunctionality

MPTCP Indicates that PCF authorizes the MPTCP functionality to ATSSS
support traffic steering, switching and splitting.
ATSSS_LL Indicates that PCF authorizes the ATSSS-LL functionality ATSSS
to support traffic steering, switching and splitting.
5.6.3.19 Enumeration: SteerModeValue

Table 5.6.3.19-1: Enumeration SteerModeValue

ACTIVE_STANDBY Indicates the steering mode is Active-Standy. It is used to ATSSS
steer a SDF on one access (the Active access), when this
access is available, and to switch the SDF to the other
access (the Standby access), when Active access
becomes unavailable.
LOAD_BALANCING Indicates the traffic of an SDF is split percentually across ATSSS
accesses.
SMALLEST_DELAY Indicates the traffic of a SDF is steered and/or switch to the ATSSS
access with the smallest delay.
PRIORITY_BASED Indicates all the traffic of an SDF is steered to the high ATSSS
priority access, until this access is determined to be
congested.
5.6.3.20 Enumeration: MulticastAccessControl

Table 5.6.3.20-1: Enumeration MulticastAccessControl

ALLOWED Indicates the service data flow, corresponding to the WWC
service data flow template, is allowed.
NOT_ALLOWED Indicates the service data flow, corresponding to the WWC
service data flow template, is not allowed. This is default
value.
3GPP
Release 16 141 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.3.21 Enumeration RequestedQosMonitoringParameter

Table 5.6.3.21-1: Enumeration RequestedQosMonitoringParameter

DOWNLINK Indicates the DL packet delay between the UE and the
UPF is to be monitored.
UPLINK Indicates the UL packet delay between the UE and the
UPF is to be monitored.
ROUND_TRIP Indicates the round trip packet delay between the UE and
the UPF is to be monitored.
5.6.3.22 Enumeration: ReportingFrequency

Table 5.6.3.22-1: Enumeration ReportingFrequency

EVENT_TRIGGERED Indicates the delay is reported when the delay
exceeds the threshold.
PERIODIC Indicates the delay is reported periodically.
SESSION_RELEASE Indicates the delay is reported when the PDU
session is released.
5.6.3.23 Enumeration: SmPolicyAssociationReleaseCause

The enumeration SmPolicyAssociationReleaseCause represents the cause why the PCF requests the termination of the
policy association. It shall comply with the provisions defined in table 5.6.3.23-1.
Table 5.6.3.23-1: Enumeration SmPolicyAssociationReleaseCause

UNSPECIFIED This value is used for unspecified reasons.
UE_SUBSCRIPTION This value is used to indicate that the policy association needs
to be terminated because the subscription of UE has changed
(e.g. was removed).
INSUFFICIENT_RES This value is used to indicate that the server is overloaded and
needs to abort the policy association.
VALIDATION_CONDITION_ This value is used to indicate that the policy association needs
NOT_MET to be terminated because the validation condition of
background data transfer policy is not met.
5.6.3.24 Enumeration: PduSessionRelCause

Table 5.6.3.24-1: Enumeration PduSessionRelCause

PS_TO_CS_HO Indicates that the PDU session is terminated due to PS
to CS handover.
3GPP
Release 16 142 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.3.25 Enumeration: MaPduIndication

Table 5.6.3.25-1: Enumeration MaPduIndication

MA_PDU_REQUEST UE requested MA PDU session and the request is authorized
by subscription.
MA_PDU_ UE requested single access PDU session with indication of
NETWORK_UPGRADE network upgrade to MA PDU session supported and the
ALLOWED upgrade is authorized by subscription.
5.6.3.26 Enumeration: AtsssCapability

Table 5.6.3.26-1: Enumeration AtsssCapability

ATSSS_LL Indicates that the MA PDU Session supports the
ATSSS-LL capability with any steering mode in the
uplink and in the downlink.
MPTCP_ATSSS_LL Indicates that the MA PDU Session supports both the
MPTCP and ATSSS-LL capability with any steering
mode in the uplink and in the downlink.
MPTCP_ATSSS_LL_WITH_ASMODE_U Indicates that the MA PDU Session supports the
L MPTCP capability with any steering mode in uplink
and downlink, and ATSSS-LL capability with any
steering mode in the downlink and Active-Standby
mode in the uplink.
MPTCP_ATSSS_LL_WITH_EXSDMODE Indicates that the MA PDU Session supports the
_DL_ASMODE_UL MPTCP capability with any steering mode in uplink
and downlink, and ATSSS-LL capability with any
steering mode except Smallest Delay mode in the
downlink and Active-Standby mode in the uplink.
MPTCP_ATSSS_LL_WITH_ASMODE_D Indicates that the MA PDU Session supports the
LUL MPTCP capability with any steering mode and
ATSSS-LL capability with Active-Standby mode in
uplink and downlink.
5.6.3.27 Enumeration: NetLocAccessSupport

Table 5.6.3.27-1: Enumeration NetLocAccessSupport

ANR_NOT_SUPPORTED Indicates that the access network does not support the report of
access network information.
TZR_NOT_SUPPORTED Indicates that the access network does not support the report of UE
time zone.
(NOTE)
LOC_NOT_SUPPORTED Indicates that the access network does not support the report of UE
Location.
(NOTE 2)
NOTE 1: The UE time zone is not available in EPC untrusted WLAN.
NOTE 2: The SMF+PGW determines the UE Location is not available as described in subclause B.3.6.3.
3GPP
Release 16 143 3GPP TS 29.512 V16.5.0 (2020-06)
5.6.3.28 Enumeration: PolicyDecisionFailureCode

Table 5.6.3.28-1: PolicyDecisionFailureCode

TRA_CTRL_DECS_ER Indicates the traffic control decision is failure.
R
QOS DECS_ERR Indicates the QoS decision is failure.
CHG DECS_ERR Indicates the charing decision is failure.
USA_MON_DECS_ERR Indicates the usage monitoring decision is failure.
QOS_MON_DECS_ERR Indicates the QoS monitoring decision is failure.
CON_DATA_ERR Indicates the condition data is failure.
5.7 Error handling

5.7.1 General
HTTP error handling shall be supported as specified in subclause 5.2.4 of 3GPP TS 29.500 [4].
For the Npcf_SMPolicyControl API, HTTP error responses shall be supported as specified in subclause 4.8 of
3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be
supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP
method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. In addition, the requirements in the following subclauses shall apply.
5.7.2 Protocol Errors

In this Release of the specification, there are no additional protocol errors applicable for the Npcf_SMPolicyControl
API.
5.7.3 Application Errors

The application errors defined for the Npcf_SMPolicyControl API are listed in table 5.7.3-1 and 5.7.3-2. The PCF shall
include in the HTTP status code a "ProblemDetails" data structure with the "cause" attribute indicating the application
error as listed in table 5.7.3-1 when PCF acts as a server. The SMF shall include in the HTTP status code a
"ProblemDetails" data structure with the "cause" attribute indicating the application error as listed in table 5.7.3-2 when
SMF acts as a server.
3GPP
Release 16 144 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.7.3-1: Application errors when PCF acts as a server
Application Error HTTP status code Description

USER_UNKNOWN 400 Bad Request The HTTP request is rejected because the end
user specified in the request is unknown to the
PCF. (NOTE 1) (NOTE 3)
ERROR_INITIAL_PARAMETERS 400 Bad Request The HTTP request is rejected because the set of
session or subscriber information needed by the
PCF for rule selection is incomplete or erroneous
or not available for the decision to be made. (E.g.
QoS, , RAT type, subscriber information)
(NOTE 1) (NOTE 2) (NOTE 3)
ERROR_TRIGGER_EVENT 400 Bad Request The HTTP request is rejected because the set of
session information sent the message originated
due to a trigger been met is incoherent with the
previous set of session information for the same
session. (E.g. trigger met was RAT changed, and
the RAT notified is the same as before)
(NOTE 2) (NOTE 3)
ERROR_TRAFFIC_MAPPING_INFO_ 403 Forbidden The HTTP request is rejected because the PCF
REJECTED does not accept one or more of the traffic
mapping filters provided by the SMF in a PCC
Request. (NOTE 2) (NOTE 3)
ERROR_CONFLICTING_REQUEST 403 Forbidden The HTTP request is rejected because the PCF
cannot accept the UE-initiated resource request
as a network-initiated resource allocation is
already in progress that has packet filters that
cover the packet filters in the received UE-
initiated resource request. The SMF shall reject
the attempt for UE-initiated resource request.
(NOTE 2) (NOTE 3)
LATE_OVERLAPPING_REQUEST 403 Forbidden The request is rejected because it collides with
and exiting Policy Association with a more recent
originating timestamp. (NOTE 1)
POLICY_CONTEXT_DENIED 403 Forbidden The HTTP request is rejected because the PCF
does not accept the SMF request due to operator
policies and/or local configuration. (NOTE 1)
(NOTE 3)
VALIDATION_CONDITION_NOT_MET 403 Forbidden The HTTP request is rejected because the PCF
does not accept the SMF request because the
validation condition of background data transfer
policy is not met. (NOTE 1) (NOTE 3)
PENDING_TRANSACTION 400 Bad Request This error shall be used when the
PendingTransaction feature is supported and the
PCF receives an incoming request on a policy
association while it has an ongoing transaction
on the same policy association and cannot
handle the request as described in subclause 9.2
of 3GPP TS 29.513 [7]. (NOTE 2)
NOTE 1: These application errors are used by the create service operation (see subclause 4.2.2.2) and included in
the responses to the POST request.
NOTE 2: These application errors are used by the update service operation (see subclause 4.2.4.2) and included in
the responses to the POST request.
NOTE 3: The Cause codes mapping performed by SMF between this Application Error and the 5GSM related value
is specified in subclause 5.2.2.2 of 3GPP TS 29.524 [40].
3GPP
Release 16 145 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.7.3-2: Application errors when SMF acts as a server to receive a notification
Application Error HTTP status code Description

PCC_RULE_EVENT 400 Bad Request The HTTP request is rejected because all the
PCC rules provisioned by the PCF in the
request cannot be installed/activated. It is used
to inform the PCF that the request failed, and
should not be attempted again. (NOTE)
PCC_QOS_FLOW_EVENT 400 Bad Request The HTTP request is rejected because for some
reason all the PCC rules provisioned by the
PCF in the request cannot be enforced or
modified successfully in a network initiated
procedure. It is used to inform the PCF that the
request could not be satisfied at the time it was
received, but may be able to satisfy the request
in the future. (NOTE)
UE_STATUS_SUSPEND 400 Bad Request The HTTP request is rejected because the UE’s
status is suspended and the policy decisions
received from the PCF cannot be enforced by
the SMF. Applicable only to functionality
introduced with the
PolicyUpdateWhenUESuspends feature as
described in subclause 5.8. (NOTE)
RULE_PERMANENT_ERROR 400 Bad Request The HTTP request is rejected because all the
PCC rules and/or session rules provisioned by
the PCF in the request cannot be
installed/activated. It is used to inform the PCF
that the request failed, and should not be
attempted again. Applicable only to functionality
introduced with the SessionRuleErrorHandling
feature as described in subclause 5.8. (NOTE)
RULE_TEMPORARY_ERROR 400 Bad Request The HTTP request is rejected because for some
reason all the PCC rules and/or session rules
provisioned by the PCF in the request cannot be
enforced or modified successfully in a network
initiated procedure. It is used to inform the PCF
that the request could not be satisfied at the
time it was received, but may be able to satisfy
the request in the future. Applicable only to
functionality introduced with the
SessionRuleErrorHandling feature as described
in subclause 5.8. (NOTE)
PENDING_TRANSACTION 400 Bad Request This error shall be used when the
PendingTransaction feature is supported and
the SMF receives an incoming request on a
policy association while it has an ongoing
transaction on the same policy association and
cannot handle the request as described in
subclause 9.2 of 3GPP TS 29.513 [7]. (NOTE)
NOTE: These application errors are used by the UpdateNotify service operation (see subclause 4.2.3.2) and
included in the responses to the POST request.
5.8 Feature negotiation

The optional features in table 5.8-1 are defined for the Npcf_SMPolicyControl API. They shall be negotiated using the
extensibility mechanism defined in subclause 6.6 of 3GPP TS 29.500 [4].
3GPP
Release 16 146 3GPP TS 29.512 V16.5.0 (2020-06)
Table 5.8-1: Supported Features
Feature number Feature Name Description

1 TSC This feature indicates support for traffic steering control in
the (S)Gi-LAN or routing of the user traffic to a local Data
Network identified by the DNAI per AF request. If the SMF
supports this feature, the PCF shall behave as described in
2 ResShare This feature indicates the support of service data flows that
share resources. If the SMF supports this feature, the PCF
shall behave as described in subclause 4.2.6.2.8.
3 3GPP-PS-Data-Off This feature indicates the support of 3GPP PS Data off
status change reporting.
4 ADC This feature indicates the support of application detection
and control.
5 UMC Indicates that the usage monitoring control is supported.
6 NetLoc This feature indicates the support of the Access Network
Information Reporting for 5GS.
7 RAN-NAS-Cause This feature indicates the support for the detailed release
cause code information from the access network.
8 ProvAFsignalFlow This feature indicates support for the feature of IMS
Restoration as described in subclause 4.2.3.17. If SMF
supports this feature the PCF may provision AF signalling IP
flow information.
9 PCSCF-Restoration-Enhancement This feature indicates support of P-CSCF Restoration
Enhancement. It is used for the SMF to indicate if it
supports P-CSCF Restoration Enhancement.
10 PRA This feature indicates the support of presence reporting
area change reporting.
11 RuleVersioning This feature indicates the support of PCC rule versioning as
defined in subclause 4.2.6.7.
12 SponsoredConnectivity This feature indicates support for sponsored data
connectivity feature. If the SMF supports this feature, the
PCF may authorize sponsored data connectivity to the
subscriber.
13 RAN-Support-Info This feature indicates the support of maximum packet loss
rate value(s) for uplink and/or downlink voice service data
flow(s).
14 PolicyUpdateWhenUESuspends This feature indicates the support of report when the UE is
suspended and then resumed from suspend state. Only
applicable to the interworking scenario as defined in
Annex B.
15 AccessTypeCondition This feature indicates the support of access type
conditioned authorized session AMBR as defined in
subclause 4.2.6.3.2.4.
16 MultiIpv6AddrPrefix This feature indicates the support of multiple Ipv6 address
prefixes reporting.
17 SessionRuleErrorHandling This feature indicates the support of session rule error
handling.
18 DN-Authorization This feature indicates the support of DN-AAA authorization
data for policy control.
19 ATSSS This feature indicates the support of the access traffic
switching, steering and splitting functionality as defined in
subclauses 4.2.6.2.17 and 4.2.6.3.4.
20 PendingTransaction This feature indicates support for the race condition
handling as defined in 3GPP TS 29.513 [7].
21 URLLC This feature indicates support of Ultra-Reliable Low-Latency
Communication (URLLC) requirements, i.e. AF application
relocation acknowledgement requirement and UE
address(es) preservation. The TSC feature shall be
supported in order to support this feature.
22 MacAddressRange Indicates the support of a set of MAC addresses with a
specific range in the traffic filter.
23 WWC Indicates support of wireless and wireline convergence
access as defined in annex C.
24 QosMonitoring Indicates support of QoS monitoring as defined in
subclause 4.2.3.25 and 4.2.4.24.
3GPP
Release 16 147 3GPP TS 29.512 V16.5.0 (2020-06)
25 AuthorizationWithRequiredQoS Indicates support of policy authorization for the AF session

with required QoS as defined in subclause 4.2.3.22.
26 EnhancedBackgroundDataTransfer Indicates the support of applying the Background Data
Transfer Policy to a future PDU session.
27 AF_Charging_Identifier Indicates the support of long character strings as charging
identifiers.
28 PDUSessionRelCause Indicates the support of PDU session release cause.
29 SamePcf This feature indicates the support of same PCF selection for
the parameter's combination.
30 ADCmultiRedirection This feature indicates support for multiple redirection
information in application detection and control. It requires
the support of ADC feature.
31 RespBasedSessionRel Indicates support of handling PDU session termination
functionality as defined in subclause 4.2.4.22.
32 TimeSensitiveNetworking Indicates that the 5G System is integrated within the
external network as a TSN bridge.
33 EMDBV This feature indicates the support of the
ExtMaxDataBurstVol data type defined in
3GPP TS 29.571 [11]. The use of this data type is specified
34 DNNSelectionMode This feature indicates the support of DNN selection mode.
35 EPSFallbackReport This feature indicates the support of the report of EPS
Fallback as defined in subclauses B.3.3.2 and B.3.4.6.
36 PolicyDecisionErrorHandling This feature indicates the support of the error report of the
policy decision and/or condition data which is not referred
by any PCC rule or session rule as defined in
subclause 4.2.3.26 and 4.2.4.26.
37 DDNEventPolicyControl This feature indicates the support for policy control in the
case of DDN Failure and Delivery Status events as defined
38 ReallocationOfCredit This feature indicates the support of notifications of
reallocation of credit.
5.9 Security
As indicated in 3GPP TS 33.501 [27], the access to the Npcf_SMPolicyControl API shall be authorized by means of the
OAuth2 protocol (see IETF RFC 6749 [28]), using the "Client Credentials" authorization grant, where the NRF (see
3GPP TS 29.510 [29]) plays the role of the authorization server.
An NF Service Consumer, prior to consuming services offered by the Npcf_SMPolicyControl API, shall obtain a
"token" from the authorization server, by invoking the Access Token Request service, as described in
3GPP TS 29.510 [29], subclause 5.4.2.2.
NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF
that the NF Service Consumer used for discovering the Npcf_SMPolicyControl service.
The Npcf_SMPolicyControl API defines a single scope "npcf-smpolicycontrol" for OAuth2 authorization (as specified
in 3GPP TS 33.501 [27]) for the entire API, and it does not define any additional scopes at resource or operation level.
3GPP
Release 16 148 3GPP TS 29.512 V16.5.0 (2020-06)
Annex A (normative):
OpenAPI specification
A.1 General
The present Annex contains an OpenAPI [10] specification of HTTP messages and content bodies used by the
Npcf_SMPolicyControl API.
This Annex shall take precedence when being discrepant to other parts of the specification with respect to the encoding
of information elements and methods within the API.
NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations
of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the
specification also apply.
Informative copies of the OpenAPI specification file contained in this 3GPP Technical Specification are available on a
Git-based repository hosted in ETSI Forge, that uses the GitLab software version control system (see clause 5B of the
3GPP TR 21.900 [38] and subclause 5.3.1 of the 3GPP TS 29.501 [5] for further information).
A.2 Npcf_SMPolicyControl API

openapi: 3.0.0
info:
title: Npcf_SMPolicyControl API
version: 1.1.1
description: |
Session Management Policy Control Service
© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
externalDocs:
description: 3GPP TS 29.512 V16.5.0; 5G System; Session Management Policy Control Service.
url: 'http://www.3gpp.org/ftp/Specs/archive/29_series/29.512/'
security:
- {}
- oAuth2Clientcredentials:
- npcf-smpolicycontrol
servers:
- url: '{apiRoot}/npcf-smpolicycontrol/v1'
variables:
apiRoot:
default: https://example.com
description: apiRoot as defined in subclause 4.4 of 3GPP TS 29.501
paths:
/sm-policies:
post:
summary: Create a new Individual SM Policy
operationId: CreateSMPolicy
tags:
- SM Policies (Collection)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SmPolicyContextData'
responses:
'201':
description: Created
content:
application/json:
schema:
$ref: '#/components/schemas/SmPolicyDecision'
headers:
Location:
description: 'Contains the URI of the newly created resource'
required: true
3GPP
Release 16 149 3GPP TS 29.512 V16.5.0 (2020-06)
schema:
type: string
'308':
description: Permanent Redirect
headers:
Location:
description: 'Contains the URI of the PCF within the existing PCF binding information
stored in the BSF for the same UE ID, S-NSSAI and DNN combination '
required: true
schema:
type: string
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
'403':
'404':
description: Not Found
'411':
'413':
'415':
'429':
'500':
'503':
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
callbacks:
SmPolicyUpdateNotification:
'{$request.body#/notificationUri}/update':
post:
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SmPolicyNotification'
responses:
'200':
description: OK. The current applicable values corresponding to the policy control
request trigger is reported
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/UeCampingRep'
- type: array
items:
$ref: '#/components/schemas/PartialSuccessReport'
minItems: 1
- type: array
items:
$ref: '#/components/schemas/PolicyDecisionFailureCode'
minItems: 1
'204':
description: No Content, Notification was succesfull
'400':
description: Bad Request.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorReport'
'401':
'403':
'404':
'411':
'413':
3GPP
Release 16 150 3GPP TS 29.512 V16.5.0 (2020-06)
'415':
'429':
'500':
'503':
default:
SmPolicyControlTerminationRequestNotification:
'{$request.body#/notificationUri}/terminate':
post:
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/TerminationNotification'
responses:
'204':
description: No Content, Notification was succesful
'400':
'401':
'403':
'404':
'411':
'413':
'415':
'429':
'500':
'503':
default:
/sm-policies/{smPolicyId}:
get:
summary: Read an Individual SM Policy
operationId: GetSMPolicy
tags:
- Individual SM Policy (Document)
parameters:
- name: smPolicyId
in: path
description: Identifier of a policy association
required: true
schema:
type: string
responses:
'200':
description: OK. Resource representation is returned
content:
application/json:
schema:
$ref: '#/components/schemas/SmPolicyControl'
'400':
'401':
'403':
'404':
'406':
'429':
'500':
3GPP
Release 16 151 3GPP TS 29.512 V16.5.0 (2020-06)
'503':
default:
/sm-policies/{smPolicyId}/update:
post:
summary: Update an existing Individual SM Policy
operationId: UpdateSMPolicy
tags:
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SmPolicyUpdateContextData'
parameters:
- name: smPolicyId
in: path
required: true
schema:
type: string
responses:
'200':
description: OK. Updated policies are returned
content:
application/json:
schema:
'400':
'401':
'403':
'404':
'411':
'413':
'415':
'429':
'500':
'503':
default:
/sm-policies/{smPolicyId}/delete:
post:
summary: Delete an existing Individual SM Policy
operationId: DeleteSMPolicy
tags:
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SmPolicyDeleteData'
parameters:
- name: smPolicyId
in: path
required: true
schema:
type: string
responses:
'204':
description: No content
'400':
'401':
3GPP
Release 16 152 3GPP TS 29.512 V16.5.0 (2020-06)
'403':
'404':
'411':
'413':
'415':
'429':
'500':
'503':
default:
components:
securitySchemes:
oAuth2Clientcredentials:
type: oauth2
flows:
clientCredentials:
tokenUrl: '{nrfApiRoot}/oauth2/token'
scopes:
npcf-smpolicycontrol: Access to the Npcf_SMPolicyControl API
schemas:
SmPolicyControl:
type: object
properties:
context:
$ref: '#/components/schemas/SmPolicyContextData'
policy:
required:
- context
- policy
SmPolicyContextData:
type: object
properties:
accNetChId:
$ref: '#/components/schemas/AccNetChId'
chargEntityAddr:
$ref: '#/components/schemas/AccNetChargingAddress'
gpsi:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
supi:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
interGrpIds:
type: array
items:
$ref: 'TS29571_CommonData.yaml#/components/schemas/GroupId'
minItems: 1
pduSessionId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionId'
pduSessionType:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionType'
chargingcharacteristics:
type: string
dnn:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'
dnnSelMode:
$ref: 'TS29502_Nsmf_PDUSession.yaml#/components/schemas/DnnSelectionMode'
notificationUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
accessType:
$ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType'
ratType:
$ref: 'TS29571_CommonData.yaml#/components/schemas/RatType'
addAccessInfo:
$ref: '#/components/schemas/AdditionalAccessInfo'
servingNetwork:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid'
userLocationInfo:
$ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation'
ueTimeZone:
$ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone'
3GPP
Release 16 153 3GPP TS 29.512 V16.5.0 (2020-06)
pei:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Pei'
ipv4Address:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr'
ipv6AddressPrefix:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix'
ipDomain:
type: string
description: Indicates the IPv4 address domain
subsSessAmbr:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr'
authProfIndex:
type: string
description: Indicates the DN-AAA authorization profile index
subsDefQos:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SubscribedDefaultQos'
numOfPackFilter:
type: integer
description: Contains the number of supported packet filter for signalled QoS rules.
online:
type: boolean
description: If it is included and set to true, the online charging is applied to the PDU
session.
offline:
type: boolean
description: If it is included and set to true, the offline charging is applied to the PDU
session.
3gppPsDataOffStatus:
type: boolean
description: If it is included and set to true, the 3GPP PS Data Off is activated by the
UE.
refQosIndication:
type: boolean
description: If it is included and set to true, the reflective QoS is supported by the UE.
traceReq:
$ref: 'TS29571_CommonData.yaml#/components/schemas/TraceData'
sliceInfo:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai'
qosFlowUsage:
$ref: '#/components/schemas/QosFlowUsage'
servNfId:
$ref: '#/components/schemas/ServingNfIdentity'
suppFeat:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
smfId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId'
recoveryTime:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
maPduInd:
$ref: '#/components/schemas/MaPduIndication'
atsssCapab:
$ref: '#/components/schemas/AtsssCapability'
ipv4FrameRouteList:
type: array
items:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4AddrMask'
minItems: 1
ipv6FrameRouteList:
type: array
items:
minItems: 1
required:
- supi
- pduSessionId
- pduSessionType
- dnn
- notificationUri
- sliceInfo
SmPolicyDecision:
type: object
properties:
sessRules:
type: object
additionalProperties:
$ref: '#/components/schemas/SessionRule'
minProperties: 1
3GPP
Release 16 154 3GPP TS 29.512 V16.5.0 (2020-06)
description: A map of Sessionrules with the content being the SessionRule as described in
subclause 5.6.2.7.
pccRules:
type: object
$ref: '#/components/schemas/PccRule'
minProperties: 1
description: A map of PCC rules with the content being the PCCRule as described in
subclause 5.6.2.6.
nullable: true
pcscfRestIndication:
type: boolean
description: If it is included and set to true, it indicates the P-CSCF Restoration is
requested.
qosDecs:
type: object
$ref: '#/components/schemas/QosData'
minProperties: 1
description: Map of QoS data policy decisions.
chgDecs:
type: object
$ref: '#/components/schemas/ChargingData'
minProperties: 1
description: Map of Charging data policy decisions.
nullable: true
chargingInfo:
$ref: '#/components/schemas/ChargingInformation'
traffContDecs:
type: object
$ref: '#/components/schemas/TrafficControlData'
minProperties: 1
description: Map of Traffic Control data policy decisions.
umDecs:
type: object
$ref: '#/components/schemas/UsageMonitoringData'
minProperties: 1
description: Map of Usage Monitoring data policy decisions.
nullable: true
qosChars:
type: object
$ref: '#/components/schemas/QosCharacteristics'
minProperties: 1
description: Map of QoS characteristics for non standard 5QIs. This map uses the 5QI
values as keys.
qosMonDecs:
type: object
$ref: '#/components/schemas/QosMonitoringData'
minProperties: 1
description: Map of QoS Monitoring data policy decisions.
nullable: true
reflectiveQoSTimer:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'
conds:
type: object
$ref: '#/components/schemas/ConditionData'
minProperties: 1
description: A map of condition data with the content being as described in subclause
5.6.2.9.
nullable: true
revalidationTime:
offline:
type: boolean
description: Indicates the offline charging is applicable to the PDU session when it is
included and set to true.
online:
type: boolean
description: Indicates the online charging is applicable to the PDU session when it is
policyCtrlReqTriggers:
type: array
3GPP
Release 16 155 3GPP TS 29.512 V16.5.0 (2020-06)
items:
$ref: '#/components/schemas/PolicyControlRequestTrigger'
minItems: 1
description: Defines the policy control request triggers subscribed by the PCF.
nullable: true
lastReqRuleData:
type: array
items:
$ref: '#/components/schemas/RequestedRuleData'
minItems: 1
description: Defines the last list of rule control data requested by the PCF.
lastReqUsageData:
$ref: '#/components/schemas/RequestedUsageData'
praInfos:
type: object
$ref: 'TS29571_CommonData.yaml#/components/schemas/PresenceInfoRm'
minProperties: 1
description: Map of PRA information.
nullable: true
ipv4Index:
$ref: 'TS29519_Policy_Data.yaml#/components/schemas/IpIndex'
ipv6Index:
$ref: 'TS29519_Policy_Data.yaml#/components/schemas/IpIndex'
qosFlowUsage:
relCause:
$ref: '#/components/schemas/SmPolicyAssociationReleaseCause'
suppFeat:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
tsnBridgeManCont:
$ref: '#/components/schemas/BridgeManagementContainer'
tsnPortManContDstt:
$ref: '#/components/schemas/PortManagementContainer'
tsnPortManContNwtts:
type: array
items:
minItems: 1
SmPolicyNotification:
type: object
properties:
resourceUri:
smPolicyDecision:
PccRule:
type: object
properties:
flowInfos:
type: array
items:
$ref: '#/components/schemas/FlowInformation'
minItems: 1
description: An array of IP flow packet filter information.
appId:
type: string
description: A reference to the application detection filter configured at the UPF.
appDescriptor:
$ref: '#/components/schemas/ApplicationDescriptor'
contVer:
$ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ContentVersion'
pccRuleId:
type: string
description: Univocally identifies the PCC rule within a PDU session.
precedence:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger'
afSigProtocol:
$ref: '#/components/schemas/AfSigProtocol'
appReloc:
type: boolean
description: Indication of application relocation possibility.
refQosData:
type: array
items:
type: string
minItems: 1
maxItems: 1
3GPP
Release 16 156 3GPP TS 29.512 V16.5.0 (2020-06)
description: A reference to the QoSData policy type decision type. It is the qosId
refAltQosParams:
type: array
items:
type: string
minItems: 1
description: A Reference to the QoS Data policy decision type for the Alternative QoS
parameter sets of the service data flow.
refTcData:
type: array
items:
type: string
minItems: 1
maxItems: 1
description: A reference to the TrafficControlData policy decision type. It is the tcId
refChgData:
type: array
items:
type: string
minItems: 1
maxItems: 1
description: A reference to the ChargingData policy decision type. It is the chgId
nullable: true
refChgN3gData:
type: array
items:
type: string
minItems: 1
maxItems: 1
description: A reference to the ChargingData policy decision type only applicable to Non-
3GPP access if "ATSSS" feature is supported. It is the chgId described in subclause 5.6.2.11.
nullable: true
refUmData:
type: array
items:
type: string
minItems: 1
maxItems: 1
description: A reference to UsageMonitoringData policy decision type. It is the umId
nullable: true
refUmN3gData:
type: array
items:
type: string
minItems: 1
maxItems: 1
description: A reference to UsageMonitoringData policy decision type only applicable to
Non-3GPP access if "ATSSS" feature is supported. It is the umId described in subclause 5.6.2.12.
nullable: true
refCondData:
type: string
description: A reference to the condition data. It is the condId described in subclause
5.6.2.9.
nullable: true
refQosMon:
type: array
items:
type: string
minItems: 1
maxItems: 1
description: A reference to the QosMonitoringData policy type decision type. It is the
qmId described in subclause 5.6.2.40.
nullable: true
addrPreserInd:
type: boolean
nullable: true
tscaiInputDl:
$ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer'
tscaiInputUl:
$ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer'
required:
- pccRuleId
nullable: true
SessionRule:
3GPP
Release 16 157 3GPP TS 29.512 V16.5.0 (2020-06)
type: object
properties:
authSessAmbr:
authDefQos:
$ref: '#/components/schemas/AuthorizedDefaultQos'
sessRuleId:
type: string
description: Univocally identifies the session rule within a PDU session.
refUmData:
type: string
description: A reference to UsageMonitoringData policy decision type. It is the umId
nullable: true
refUmN3gData:
type: string
description: A reference to UsageMonitoringData policy decision type to apply for Non-3GPP
access. It is the umId described in subclause 5.6.2.12.
nullable: true
refCondData:
type: string
description: A reference to the condition data. It is the condId described in subclause
5.6.2.9.
nullable: true
required:
- sessRuleId
nullable: true
QosData:
type: object
properties:
qosId:
type: string
description: Univocally identifies the QoS control policy data within a PDU session.
5qi:
$ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi'
maxbrUl:
$ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm'
maxbrDl:
gbrUl:
gbrDl:
arp:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Arp'
qnc:
type: boolean
description: Indicates whether notifications are requested from 3GPP NG-RAN when the GFBR
can no longer (or again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow.
priorityLevel:
$ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevelRm'
averWindow:
$ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindowRm'
maxDataBurstVol:
$ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVolRm'
reflectiveQos:
type: boolean
description: Indicates whether the QoS information is reflective for the corresponding
service data flow.
sharingKeyDl:
type: string
description: Indicates, by containing the same value, what PCC rules may share resource in
downlink direction.
sharingKeyUl:
type: string
description: Indicates, by containing the same value, what PCC rules may share resource in
uplink direction.
maxPacketLossRateDl:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PacketLossRateRm'
maxPacketLossRateUl:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PacketLossRateRm'
defQosFlowIndication:
type: boolean
description: Indicates that the dynamic PCC rule shall always have its binding with the
QoS Flow associated with the default QoS rule
extMaxDataBurstVol:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVolRm'
required:
3GPP
Release 16 158 3GPP TS 29.512 V16.5.0 (2020-06)
- qosId
nullable: true
ConditionData:
type: object
properties:
condId:
type: string
description: Uniquely identifies the condition data within a PDU session.
activationTime:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DateTimeRm'
deactivationTime:
accessType:
ratType:
required:
- condId
nullable: true
TrafficControlData:
type: object
properties:
tcId:
type: string
description: Univocally identifies the traffic control policy data within a PDU session.
flowStatus:
$ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/FlowStatus'
redirectInfo:
$ref: '#/components/schemas/RedirectInformation'
addRedirectInfo:
type: array
items:
$ref: '#/components/schemas/RedirectInformation'
minItems: 1
muteNotif:
type: boolean
description: Indicates whether applicat'on's start or stop notification is to be muted.
trafficSteeringPolIdDl:
type: string
description: Reference to a pre-configured traffic steering policy for downlink traffic at
the SMF.
nullable: true
trafficSteeringPolIdUl:
type: string
description: Reference to a pre-configured traffic steering policy for uplink traffic at
the SMF.
nullable: true
routeToLocs:
type: array
items:
$ref: 'TS29571_CommonData.yaml#/components/schemas/RouteToLocation'
minItems: 1
description: A list of location which the traffic shall be routed to for the AF request
traffCorreInd:
type: boolean
upPathChgEvent:
$ref: '#/components/schemas/UpPathChgEvent'
steerFun:
$ref: '#/components/schemas/SteeringFunctionality'
steerModeDl:
$ref: '#/components/schemas/SteeringMode'
steerModeUl:
$ref: '#/components/schemas/SteeringMode'
mulAccCtrl:
$ref: '#/components/schemas/MulticastAccessControl'
required:
- tcId
nullable: true
ChargingData:
type: object
properties:
chgId:
type: string
description: Univocally identifies the charging control policy data within a PDU session.
meteringMethod:
$ref: '#/components/schemas/MeteringMethod'
offline:
type: boolean
3GPP
Release 16 159 3GPP TS 29.512 V16.5.0 (2020-06)
description: Indicates the offline charging is applicable to the PCC rule when it is
online:
type: boolean
description: Indicates the online charging is applicable to the PCC rule when it is
sdfHandl:
type: boolean
description: Indicates whether the service data flow is allowed to start while the SMF is
waiting for the response to the credit request.
ratingGroup:
$ref: 'TS29571_CommonData.yaml#/components/schemas/RatingGroup'
reportingLevel:
$ref: '#/components/schemas/ReportingLevel'
serviceId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ServiceId'
sponsorId:
type: string
description: Indicates the sponsor identity.
appSvcProvId:
type: string
description: Indicates the application service provider identity.
afChargingIdentifier:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ChargingId'
afChargId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ApplicationChargingId'
required:
- chgId
nullable: true
UsageMonitoringData:
type: object
properties:
umId:
type: string
description: Univocally identifies the usage monitoring policy data within a PDU session.
volumeThreshold:
$ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm'
volumeThresholdUplink:
volumeThresholdDownlink:
timeThreshold:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm'
monitoringTime:
nextVolThreshold:
nextVolThresholdUplink:
nextVolThresholdDownlink:
nextTimeThreshold:
inactivityTime:
exUsagePccRuleIds:
type: array
items:
type: string
minItems: 1
description: Contains the PCC rule identifier(s) which corresponding service data flow(s)
shall be excluded from PDU Session usage monitoring. It is only included in the UsageMonitoringData
instance for session level usage monitoring.
nullable: true
required:
- umId
nullable: true
RedirectInformation:
type: object
properties:
redirectEnabled:
type: boolean
description: Indicates the redirect is enable.
redirectAddressType:
$ref: '#/components/schemas/RedirectAddressType'
redirectServerAddress:
type: string
description: Indicates the address of the redirect server.
3GPP
Release 16 160 3GPP TS 29.512 V16.5.0 (2020-06)
FlowInformation:
type: object
properties:
flowDescription:
$ref: '#/components/schemas/FlowDescription'
ethFlowDescription:
$ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription'
packFiltId:
type: string
description: An identifier of packet filter.
packetFilterUsage:
type: boolean
description: The packet shall be sent to the UE.
tosTrafficClass:
type: string
description: Contains the Ipv4 Type-of-Service and mask field or the Ipv6 Traffic-Class
field and mask field.
nullable: true
spi:
type: string
description: the security parameter index of the IPSec packet.
nullable: true
flowLabel:
type: string
description: the Ipv6 flow label header field.
nullable: true
flowDirection:
$ref: '#/components/schemas/FlowDirectionRm'
SmPolicyDeleteData:
type: object
properties:
userLocationInfo:
ueTimeZone:
servingNetwork:
userLocationInfoTime:
ranNasRelCauses:
type: array
items:
$ref: '#/components/schemas/RanNasRelCause'
minItems: 1
description: Contains the RAN and/or NAS release cause.
accuUsageReports:
type: array
items:
$ref: '#/components/schemas/AccuUsageReport'
minItems: 1
description: Contains the usage report
pduSessRelCause:
$ref: '#/components/schemas/PduSessionRelCause'
QosCharacteristics:
type: object
properties:
5qi:
resourceType:
$ref: 'TS29571_CommonData.yaml#/components/schemas/QosResourceType'
priorityLevel:
$ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevel'
packetDelayBudget:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PacketDelBudget'
packetErrorRate:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PacketErrRate'
averagingWindow:
$ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindow'
maxDataBurstVol:
$ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVol'
extMaxDataBurstVol:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVol'
required:
- 5qi
- resourceType
- priorityLevel
- packetDelayBudget
- packetErrorRate
3GPP
Release 16 161 3GPP TS 29.512 V16.5.0 (2020-06)
ChargingInformation:
type: object
properties:
primaryChfAddress:
secondaryChfAddress:
primaryChfSetId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/NfSetId'
primaryChfInstanceId:
secondaryChfSetId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/NfSetId'
secondaryChfInstanceId:
required:
- primaryChfAddress
- secondaryChfAddress
AccuUsageReport:
type: object
properties:
refUmIds:
type: string
description: An id referencing UsageMonitoringData objects associated with this usage
report.
volUsage:
$ref: 'TS29122_CommonData.yaml#/components/schemas/Volume'
volUsageUplink:
volUsageDownlink:
timeUsage:
nextVolUsage:
nextVolUsageUplink:
nextVolUsageDownlink:
nextTimeUsage:
required:
- refUmIds
SmPolicyUpdateContextData:
type: object
properties:
repPolicyCtrlReqTriggers:
type: array
items:
$ref: '#/components/schemas/PolicyControlRequestTrigger'
minItems: 1
description: The policy control reqeust trigges which are met.
accNetChIds:
type: array
items:
$ref: '#/components/schemas/AccNetChId'
minItems: 1
description: Indicates the access network charging identifier for the PCC rule(s) or whole
PDU session.
accessType:
ratType:
addAccessInfo:
relAccessInfo:
servingNetwork:
userLocationInfo:
ueTimeZone:
relIpv4Address:
ipv4Address:
ipDomain:
3GPP
Release 16 162 3GPP TS 29.512 V16.5.0 (2020-06)
type: string
description: Indicates the IPv4 address domain
ipv6AddressPrefix:
relIpv6AddressPrefix:
addIpv6AddrPrefixes:
addRelIpv6AddrPrefixes:
relUeMac:
$ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48'
ueMac:
subsSessAmbr:
authProfIndex:
type: string
description: Indicates the DN-AAA authorization profile index
subsDefQos:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SubscribedDefaultQos'
numOfPackFilter:
type: integer
description: Contains the number of supported packet filter for signalled QoS rules.
accuUsageReports:
type: array
items:
$ref: '#/components/schemas/AccuUsageReport'
minItems: 1
description: Contains the usage report
3gppPsDataOffStatus:
type: boolean
description: If it is included and set to true, the 3GPP PS Data Off is activated by the
UE.
appDetectionInfos:
type: array
items:
$ref: '#/components/schemas/AppDetectionInfo'
minItems: 1
description: Report the start/stop of the application traffic and detected SDF
descriptions if applicable.
ruleReports:
type: array
items:
$ref: '#/components/schemas/RuleReport'
minItems: 1
description: Used to report the PCC rule failure.
sessRuleReports:
type: array
items:
$ref: '#/components/schemas/SessionRuleReport'
minItems: 1
description: Used to report the session rule failure.
qncReports:
type: array
items:
$ref: '#/components/schemas/QosNotificationControlInfo'
minItems: 1
description: QoS Notification Control information.
qosMonReports:
type: array
items:
$ref: '#/components/schemas/QosMonitoringReport'
minItems: 1
userLocationInfoTime:
repPraInfos:
type: object
$ref: 'TS29571_CommonData.yaml#/components/schemas/PresenceInfo'
minProperties: 1
description: Reports the changes of presence reporting area.
ueInitResReq:
$ref: '#/components/schemas/UeInitiatedResourceRequest'
refQosIndication:
type: boolean
description: If it is included and set to true, the reflective QoS is supported by the UE.
If it is included and set to false, the reflective QoS is revoked by the UE.
3GPP
Release 16 163 3GPP TS 29.512 V16.5.0 (2020-06)
qosFlowUsage:
creditManageStatus:
$ref: '#/components/schemas/CreditManagementStatus'
servNfId:
traceReq:
$ref: 'TS29571_CommonData.yaml#/components/schemas/TraceData'
maPduInd:
$ref: '#/components/schemas/MaPduIndication'
atsssCapab:
$ref: '#/components/schemas/AtsssCapability'
tsnBridgeInfo:
$ref: '#/components/schemas/TsnBridgeInfo'
tsnBridgeManCont:
$ref: '#/components/schemas/BridgeManagementContainer'
tsnPortManContDstt:
tsnPortManContNwtts:
type: array
items:
minItems: 1
mulAddrInfos:
type: array
items:
$ref: '#/components/schemas/IpMulticastAddressInfo'
minItems: 1
policyDecFailureReports:
type: array
items:
minItems: 1
description: Contains the type(s) of failed policy decision and/or condition data.
trafficDescriptor:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DddTrafficDescriptor'
UpPathChgEvent:
type: object
properties:
notificationUri:
notifCorreId:
type: string
description: It is used to set the value of Notification Correlation ID in the
notification sent by the SMF.
dnaiChgType:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DnaiChangeType'
afAckInd:
type: boolean
required:
- notificationUri
- notifCorreId
- dnaiChgType
nullable: true
TerminationNotification:
type: object
properties:
resourceUri:
cause:
$ref: '#/components/schemas/SmPolicyAssociationReleaseCause'
required:
- resourceUri
- cause
AppDetectionInfo:
type: object
properties:
appId:
type: string
description: A reference to the application detection filter configured at the UPF
instanceId:
type: string
description: Identifier sent by the SMF in order to allow correlation of application Start
and Stop events to the specific service data flow description, if service data flow descriptions are
deducible.
sdfDescriptions:
type: array
items:
3GPP
Release 16 164 3GPP TS 29.512 V16.5.0 (2020-06)
$ref: '#/components/schemas/FlowInformation'
minItems: 1
description: Contains the detected service data flow descriptions if they are deducible.
required:
- appId
AccNetChId:
type: object
properties:
accNetChaIdValue:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ChargingId'
refPccRuleIds:
type: array
items:
type: string
minItems: 1
description: Contains the identifier of the PCC rule(s) associated to the provided Access
Network Charging Identifier.
sessionChScope:
type: boolean
description: When it is included and set to true, indicates the Access Network Charging
Identifier applies to the whole PDU Session
required:
- accNetChaIdValue
AccNetChargingAddress:
description: Describes the network entity within the access network performing charging
type: object
anyOf:
- required: [anChargIpv4Addr]
- required: [anChargIpv6Addr]
properties:
anChargIpv4Addr:
anChargIpv6Addr:
RequestedRuleData:
type: object
properties:
refPccRuleIds:
type: array
items:
type: string
minItems: 1
description: An array of PCC rule id references to the PCC rules associated with the
control data.
reqData:
type: array
items:
$ref: '#/components/schemas/RequestedRuleDataType'
minItems: 1
description: Array of requested rule data type elements indicating what type of rule data
is requested for the corresponding referenced PCC rules.
required:
- refPccRuleIds
- reqData
RequestedUsageData:
type: object
properties:
refUmIds:
type: array
items:
type: string
minItems: 1
description: An array of usage monitoring data id references to the usage monitoring data
instances for which the PCF is requesting a usage report. This attribute shall only be provided when
allUmIds is not set to true.
allUmIds:
type: boolean
description: Th ooleanean indicates whether requested usage data applies to all usage
monitoring data instances. When it's not included, it means requested usage data shall only apply to
the usage monitoring data instances referenced by the refUmIds attribute.
UeCampingRep:
type: object
properties:
accessType:
ratType:
servNfId:
3GPP
Release 16 165 3GPP TS 29.512 V16.5.0 (2020-06)
servingNetwork:
userLocationInfo:
ueTimeZone:
netLocAccSupp:
$ref: '#/components/schemas/NetLocAccessSupport'
RuleReport:
type: object
properties:
pccRuleIds:
type: array
items:
type: string
minItems: 1
description: Contains the identifier of the affected PCC rule(s).
ruleStatus:
$ref: '#/components/schemas/RuleStatus'
contVers:
type: array
items:
minItems: 1
description: Indicates the version of a PCC rule.
failureCode:
$ref: '#/components/schemas/FailureCode'
finUnitAct:
$ref: 'TS32291_Nchf_ConvergedCharging.yaml#/components/schemas/FinalUnitAction'
ranNasRelCauses:
type: array
items:
$ref: '#/components/schemas/RanNasRelCause'
minItems: 1
description: indicates the RAN or NAS release cause code information.
required:
- pccRuleIds
- ruleStatus
RanNasRelCause:
type: object
properties:
ngApCause:
$ref: 'TS29571_CommonData.yaml#/components/schemas/NgApCause'
5gMmCause:
$ref: 'TS29571_CommonData.yaml#/components/schemas/5GMmCause'
5gSmCause:
$ref: '#/components/schemas/5GSmCause'
UeInitiatedResourceRequest:
type: object
properties:
pccRuleId:
type: string
ruleOp:
$ref: '#/components/schemas/RuleOperation'
precedence:
type: integer
packFiltInfo:
type: array
items:
$ref: '#/components/schemas/PacketFilterInfo'
minItems: 1
reqQos:
$ref: '#/components/schemas/RequestedQos'
required:
- ruleOp
- packFiltInfo
PacketFilterInfo:
type: object
properties:
packFiltId:
type: string
description: An identifier of packet filter.
packFiltCont:
$ref: '#/components/schemas/PacketFilterContent'
tosTrafficClass:
type: string
3GPP
Release 16 166 3GPP TS 29.512 V16.5.0 (2020-06)
description: Contains the Ipv4 Type-of-Service and mask field or the Ipv6 Traffic-Class
field and mask field.
spi:
type: string
description: The security parameter index of the IPSec packet.
flowLabel:
type: string
description: The Ipv6 flow label header field.
flowDirection:
$ref: '#/components/schemas/FlowDirection'
RequestedQos:
type: object
properties:
5qi:
gbrUl:
$ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate'
gbrDl:
$ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate'
required:
- 5qi
QosNotificationControlInfo:
type: object
properties:
refPccRuleIds:
type: array
items:
type: string
minItems: 1
description: An array of PCC rule id references to the PCC rules associated with the QoS
notification control info.
notifType:
$ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/QosNotifType'
contVer:
altQosParamId:
type: string
required:
- refPccRuleIds
- notifType
PartialSuccessReport:
type: object
properties:
failureCause:
$ref: '#/components/schemas/FailureCause'
ruleReports:
type: array
items:
minItems: 1
description: Information about the PCC rules provisioned by the PCF not successfully
installed/activated.
sessRuleReports:
type: array
items:
minItems: 1
description: Information about the session rules provisioned by the PCF not successfully
installed.
ueCampingRep:
$ref: '#/components/schemas/UeCampingRep'
type: array
items:
minItems: 1
required:
- failureCause
AuthorizedDefaultQos:
type: object
properties:
5qi:
arp:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Arp'
priorityLevel:
$ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevelRm'
3GPP
Release 16 167 3GPP TS 29.512 V16.5.0 (2020-06)
averWindow:
$ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindowRm'
maxDataBurstVol:
$ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVolRm'
maxbrUl:
maxbrDl:
gbrUl:
gbrDl:
qnc:
type: boolean
description: Indicates whether notifications are requested from 3GPP NG-RAN when the GFBR
can no longer (or again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow.
extMaxDataBurstVol:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVolRm'
ErrorReport:
type: object
properties:
error:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ProblemDetails'
ruleReports:
type: array
items:
minItems: 1
description: Used to report the PCC rule failure.
sessRuleReports:
type: array
items:
minItems: 1
description: Used to report the session rule failure.
SessionRuleReport:
type: object
properties:
ruleIds:
type: array
items:
type: string
minItems: 1
description: Contains the identifier of the affected session rule(s).
ruleStatus:
$ref: '#/components/schemas/RuleStatus'
sessRuleFailureCode:
$ref: '#/components/schemas/SessionRuleFailureCode'
type: array
items:
minItems: 1
required:
- ruleIds
- ruleStatus
ServingNfIdentity:
type: object
properties:
servNfInstId:
guami:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Guami'
anGwAddr:
$ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AnGwAddress'
SteeringMode:
type: object
properties:
steerModeValue:
$ref: '#/components/schemas/SteerModeValue'
active:
standby:
$ref: 'TS29571_CommonData.yaml#/components/schemas/AccessTypeRm'
3gLoad:
prioAcc:
3GPP
Release 16 168 3GPP TS 29.512 V16.5.0 (2020-06)
required:
- steerModeValue
AdditionalAccessInfo:
type: object
properties:
accessType:
ratType:
required:
- accessType
QosMonitoringData:
type: object
properties:
qmId:
type: string
description: Univocally identifies the QoS monitoring policy data within a PDU session.
reqQosMonParams:
type: array
items:
$ref: '#/components/schemas/RequestedQosMonitoringParameter'
minItems: 1
description: indicates the UL packet delay, DL packet delay and/or round trip packet delay
between the UE and the UPF is to be monitored when the QoS Monitoring for URLLC is enabled for the
service data flow.
repFreqs:
type: array
items:
$ref: '#/components/schemas/ReportingFrequency'
minItems: 1
repThreshDl:
type: integer
description: Unsigned integer identifying a period of time in units of miliiseconds for DL
packet delay.
nullable: true
repThreshUl:
type: integer
description: Unsigned integer identifying a period of time in units of miliiseconds for UL
packet delay.
nullable: true
repThreshRp:
type: integer
description: Unsigned integer identifying a period of time in units of miliiseconds for
round trip packet delay.
nullable: true
waitTime:
repPeriod:
notifyUri:
notifyCorreId:
type: string
required:
- qmId
- reqQosMonParams
- repFreqs
nullable: true
QosMonitoringReport:
type: object
properties:
refPccRuleIds:
type: array
items:
type: string
minItems: 1
description: An array of PCC rule id references to the PCC rules associated with the QoS
monitoring report.
ulDelays:
type: array
items:
type: integer
minItems: 1
dlDelays:
type: array
items:
type: integer
3GPP
Release 16 169 3GPP TS 29.512 V16.5.0 (2020-06)
minItems: 1
rtDelays:
type: array
items:
type: integer
minItems: 1
required:
- refPccRuleIds
#
TsnBridgeInfo:
type: object
properties:
bridgeId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uint64'
dsttAddr:
nwttPortNums:
type: array
items:
$ref: '#/components/schemas/TsnPortNumber'
minItems: 1
description: NW-TT port numbers available for a PDU session.
dsttPortNum:
dsttResidTime:
#
PortManagementContainer:
type: object
properties:
portManCont:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Bytes'
portNum:
required:
- portManCont
- portNum
BridgeManagementContainer:
type: object
properties:
bridgeManCont:
required:
- bridgeManCont
IpMulticastAddressInfo:
type: object
properties:
srcIpv4Addr:
ipv4MulAddr:
srcIpv6Addr:
ipv6MulAddr:
5GSmCause:
PacketFilterContent:
type: string
description: Defines a packet filter for an IP flow. Refer to subclause 5.3.54 of 3GPP TS
29.212 for encoding.
FlowDescription:
type: string
description: Defines a packet filter for an IP flow. Refer to subclause 5.4.2 of 3GPP TS
29.212 for encoding.
TsnPortNumber:
ApplicationDescriptor:
FlowDirection:
anyOf:
- type: string
enum:
- DOWNLINK
- UPLINK
- BIDIRECTIONAL
- UNSPECIFIED
- type: string
3GPP
Release 16 170 3GPP TS 29.512 V16.5.0 (2020-06)
description: >
This string provides forward-compatibility with future
extensions to the enumeration but is not used to encode
content defined in the present version of this API.
description: >
Possible values are
- DOWNLINK: The corresponding filter applies for traffic to the UE.
- UPLINK: The corresponding filter applies for traffic from the UE.
- BIDIRECTIONAL: The corresponding filter applies for traffic both to and from the UE.
- UNSPECIFIED: The corresponding filter applies for traffic to the UE (downlink), but has no
specific direction declared. The service data flow detection shall apply the filter for uplink
traffic as if the filter was bidirectional. The PCF shall not use the value UNSPECIFIED in filters
created by the network in NW-initiated procedures. The PCF shall only include the value UNSPECIFIED
in filters in UE-initiated procedures if the same value is received from the SMF.
FlowDirectionRm:
anyOf:
- $ref: '#/components/schemas/FlowDirection'
- $ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue'
ReportingLevel:
anyOf:
- type: string
enum:
- SER_ID_LEVEL
- RAT_GR_LEVEL
- SPON_CON_LEVEL
- type: string
description: >
description: >
Possible values are
- SER_ID_LEVEL: Indicates that the usage shall be reported on service id and rating group
combination level.
- RAT_GR_LEVEL: Indicates that the usage shall be reported on rating group level.
- SPON_CON_LEVEL: Indicates that the usage shall be reported on sponsor identity and rating
group combination level.
MeteringMethod:
anyOf:
- type: string
enum:
- DURATION
- VOLUME
- DURATION_VOLUME
- EVENT
- type: string
description: >
description: >
Possible values are
- DURATION: Indicates that the duration of the service data flow traffic shall be metered.
- VOLUME: Indicates that volume of the service data flow traffic shall be metered.
- DURATION_VOLUME: Indicates that the duration and the volume of the service data flow
traffic shall be metered.
- EVENT: Indicates that events of the service data flow traffic shall be metered.
PolicyControlRequestTrigger:
anyOf:
- type: string
enum:
- PLMN_CH
- RES_MO_RE
- AC_TY_CH
- UE_IP_CH
- UE_MAC_CH
- AN_CH_COR
- US_RE
- APP_STA
- APP_STO
- AN_INFO
- CM_SES_FAIL
- PS_DA_OFF
- DEF_QOS_CH
- SE_AMBR_CH
- QOS_NOTIF
3GPP
Release 16 171 3GPP TS 29.512 V16.5.0 (2020-06)
- NO_CREDIT
- REALLO_OF_CREDIT
- PRA_CH
- SAREA_CH
- SCNN_CH
- RE_TIMEOUT
- RES_RELEASE
- SUCC_RES_ALLO
- RAT_TY_CH
- REF_QOS_IND_CH
- NUM_OF_PACKET_FILTER
- UE_STATUS_RESUME
- UE_TZ_CH
- AUTH_PROF_CH
- QOS_MONITORING
- SCELL_CH
- EPS_FALLBACK
- MA_PDU
- TSN_BRIDGE_INFO
- 5G_RG_JOIN
- 5G_RG_LEAVE
- DDN_FAILURE
- DDN_DELIVERY_STATUS
- type: string
description: >
description: >
Possible values are
- PLMN_CH: PLMN Change
- RES_MO_RE: A request for resource modification has been received by the SMF. The SMF
always reports to the PCF.
- AC_TY_CH: Access Type Change
- UE_IP_CH: UE IP address change. The SMF always reports to the PCF.
- UE_MAC_CH: A new UE MAC address is detected or a used UE MAC address is inactive for a
specific period
- AN_CH_COR: Access Network Charging Correlation Information
- US_RE: The PDU Session or the Monitoring key specific resources consumed by a UE either
reached the threshold or needs to be reported for other reasons.
- APP_STA: The start of application traffic has been detected.
- APP_STO: The stop of application traffic has been detected.
- AN_INFO: Access Network Information report
- CM_SES_FAIL: Credit management session failure
- PS_DA_OFF: The SMF reports when the 3GPP PS Data Off status changes. The SMF always
reports to the PCF.
- DEF_QOS_CH: Default QoS Change. The SMF always reports to the PCF.
- SE_AMBR_CH: Session AMBR Change. The SMF always reports to the PCF.
- QOS_NOTIF: The SMF notify the PCF when receiving notification from RAN that QoS targets of
the QoS Flow cannot be guranteed or gurateed again.
- NO_CREDIT: Out of credit
- REALLO_OF_CREDIT: Reallocation of credit
- PRA_CH: Change of UE presence in Presence Reporting Area
- SAREA_CH: Location Change with respect to the Serving Area
- SCNN_CH: Location Change with respect to the Serving CN node
- RE_TIMEOUT: Indicates the SMF generated the request because there has been a PCC
revalidation timeout
- RES_RELEASE: Indicate that the SMF can inform the PCF of the outcome of the release of
resources for those rules that require so.
- SUCC_RES_ALLO: Indicates that the requested rule data is the successful resource
allocation.
- RAT_TY_CH: RAT Type Change.
- REF_QOS_IND_CH: Reflective QoS indication Change
- NUM_OF_PACKET_FILTER: Indicates that the SMF shall report the number of supported packet
filter for signalled QoS rules
- UE_STATUS_RESUME: Indicates that the UE’s status is resumed.
- UE_TZ_CH: UE Time Zone Change
- AUTH_PROF_CH: The DN-AAA authorization profile index has changed
- QOS_MONITORING: Indicate that the SMF notifies the PCF of the QoS Monitoring information.
- SCELL_CH: Location Change with respect to the Serving Cell. Only applicable to the
interworking scenario as defined in Annex B.
- EPS_FALLBACK: EPS Fallback report is enabled in the SMF.
- MA_PDU: UE Indicates that the SMF notifies the PCF of the MA PDU session request
- TSN_BRIDGE_INFO: 5GS Bridge information available
- 5G_RG_JOIN: The 5G-RG has joined to an IP Multicast Group.
- 5G_RG_LEAVE: The 5G-RG has left an IP Multicast Group.
- DDN_FAILURE: Event subscription for DDN Failure event received.
- DDN_DELIVERY_STATUS: Event subscription for DDN Delivery Status received.
3GPP
Release 16 172 3GPP TS 29.512 V16.5.0 (2020-06)
RequestedRuleDataType:
anyOf:
- type: string
enum:
- CH_ID
- MS_TIME_ZONE
- USER_LOC_INFO
- RES_RELEASE
- SUCC_RES_ALLO
- EPS_FALLBACK
- type: string
description: >
description: >
Possible values are
- CH_ID: Indicates that the requested rule data is the charging identifier.
- MS_TIME_ZONE: Indicates that the requested access network info type is the UE's timezone.
- USER_LOC_INFO: Indicates that the requested access network info type is the UE's location.
- RES_RELEASE: Indicates that the requested rule data is the result of the release of
resource.
- SUCC_RES_ALLO: Indicates that the requested rule data is the successful resource
allocation.
- EPS_FALLBACK: Indicates that the requested rule data is the report of QoS flow rejection
due to EPS fallback.
RuleStatus:
anyOf:
- type: string
enum:
- ACTIVE
- INACTIVE
- type: string
description: >
description: >
Possible values are
- ACTIVE: Indicates that the PCC rule(s) are successfully installed (for those provisioned
from PCF) or activated (for those pre-defined in SMF), or the session rule(s) are successfully
installed
- INACTIVE: Indicates that the PCC rule(s) are removed (for those provisioned from PCF) or
inactive (for those pre-defined in SMF) or the session rule(s) are removed.
FailureCode:
anyOf:
- type: string
enum:
- UNK_RULE_ID
- RA_GR_ERR
- SER_ID_ERR
- NF_MAL
- RES_LIM
- MAX_NR_QoS_FLOW
- MISS_FLOW_INFO
- RES_ALLO_FAIL
- UNSUCC_QOS_VAL
- INCOR_FLOW_INFO
- PS_TO_CS_HAN
- APP_ID_ERR
- NO_QOS_FLOW_BOUND
- FILTER_RES
- MISS_REDI_SER_ADDR
- CM_END_USER_SER_DENIED
- CM_CREDIT_CON_NOT_APP
- CM_AUTH_REJ
- CM_USER_UNK
- CM_RAT_FAILED
- UE_STA_SUSP
- type: string
description: >
description: >
Possible values are
- UNK_RULE_ID: Indicates that the pre-provisioned PCC rule could not be successfully
activated because the PCC rule identifier is unknown to the SMF.
3GPP
Release 16 173 3GPP TS 29.512 V16.5.0 (2020-06)
- RA_GR_ERR: Indicate that the PCC rule could not be successfully installed or enforced
because the Rating Group specified within the Charging Data policy decision which the PCC rule
refers to is unknown or, invalid.
- SER_ID_ERR: Indicate that the PCC rule could not be successfully installed or enforced
because the Service Identifier specified within the Charging Data policy decision which the PCC rule
refers to is invalid, unknown, or not applicable to the service being charged.
- NF_MAL: Indicate that the PCC rule could not be successfully installed (for those
provisioned from the PCF) or activated (for those pre-defined in SMF) or enforced (for those already
successfully installed) due to SMF/UPF malfunction.
- RES_LIM: Indicate that the PCC rule could not be successfully installed (for those
provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those already
successfully installed) due to a limitation of resources at the SMF/UPF.
- MAX_NR_QoS_FLOW: Indicate that the PCC rule could not be successfully installed (for
those provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those
already successfully installed) due to the fact that the maximum number of QoS flows has been
reached for the PDU session.
- MISS_FLOW_INFO: Indicate that the PCC rule could not be successfully installed or
enforced because neither the "flowInfos" attribute nor the "appId" attribute is specified within the
PccRule data structure by the PCF during the first install request of the PCC rule.
- RES_ALLO_FAIL: Indicate that the PCC rule could not be successfully installed or
maintained since the QoS flow establishment/modification failed, or the QoS flow was released.
- UNSUCC_QOS_VAL: indicate that the QoS validation has failed or when Guaranteed Bandwidth
> Max-Requested-Bandwidth.
- INCOR_FLOW_INFO: Indicate that the PCC rule could not be successfully installed or
modified at the SMF because the provided flow information is not supported by the network (e.g. the
provided IP address(es) or Ipv6 prefix(es) do not correspond to an IP version applicable for the PDU
session).
- PS_TO_CS_HAN: Indicate that the PCC rule could not be maintained because of PS to CS
handover.
- APP_ID_ERR: Indicate that the rule could not be successfully installed or enforced
because the Application Identifier is invalid, unknown, or not applicable to the application
required for detection.
- NO_QOS_FLOW_BOUND: Indicate that there is no QoS flow which the SMF can bind the PCC
rule(s) to.
- FILTER_RES: Indicate that the Flow Information within the "flowInfos" attribute cannot
be handled by the SMF because any of the restrictions defined in subclause 5.4.2 of 3GPP TS 29.212
was not met.
- MISS_REDI_SER_ADDR: Indicate that the PCC rule could not be successfully installed or
enforced at the SMF because there is no valid Redirect Server Address within the Traffic Control
Data policy decision which the PCC rule refers to provided by the PCF and no preconfigured
redirection address for this PCC rule at the SMF.
- CM_END_USER_SER_DENIED: Indicate that the charging system denied the service request due
to service restrictions (e.g. terminate rating group) or limitations related to the end-user, for
example the end-user's account could not cover the requested service.
- CM_CREDIT_CON_NOT_APP: Indicate that the charging system determined that the service can
be granted to the end user but no further credit control is needed for the service (e.g. service is
free of charge or is treated for offline charging).
- CM_AUTH_REJ: Indicate that the charging system denied the service request in order to
terminate the service for which credit is requested.
- CM_USER_UNK: Indicate that the specified end user could not be found in the charging
system.
- CM_RAT_FAILED: Indicate that the charging system cannot rate the service request due to
insufficient rating input, incorrect AVP combination or due to an attribute or an attribute value
that is not recognized or supported in the rating.
- UE_STA_SUSP: Indicates that the UE is in suspend state.
AfSigProtocol:
anyOf:
- type: string
enum:
- NO_INFORMATION
- SIP
- type: string
description: >
description: >
Possible values are
- NO_INFORMATION: Indicate that no information about the AF signalling protocol is being
provided.
- SIP: Indicate that the signalling protocol is Session Initiation Protocol.
RuleOperation:
anyOf:
- type: string
enum:
- CREATE_PCC_RULE
- DELETE_PCC_RULE
3GPP
Release 16 174 3GPP TS 29.512 V16.5.0 (2020-06)
- MODIFY_PCC_RULE_AND_ADD_PACKET_FILTERS
- MODIFY_ PCC_RULE_AND_REPLACE_PACKET_FILTERS
- MODIFY_ PCC_RULE_AND_DELETE_PACKET_FILTERS
- MODIFY_PCC_RULE_WITHOUT_MODIFY_PACKET_FILTERS
- type: string
description: >
description: >
Possible values are
- CREATE_PCC_RULE: Indicates to create a new PCC rule to reserve the resource requested by
the UE.
- DELETE_PCC_RULE: Indicates to delete a PCC rule corresponding to reserve the resource
- MODIFY_PCC_RULE_AND_ADD_PACKET_FILTERS: Indicates to modify the PCC rule by adding new
packet filter(s).
- MODIFY_ PCC_RULE_AND_REPLACE_PACKET_FILTERS: Indicates to modify the PCC rule by replacing
the existing packet filter(s).
- MODIFY_ PCC_RULE_AND_DELETE_PACKET_FILTERS: Indicates to modify the PCC rule by deleting
the existing packet filter(s).
- MODIFY_PCC_RULE_WITHOUT_MODIFY_PACKET_FILTERS: Indicates to modify the PCC rule by
modifying the QoS of the PCC rule.
RedirectAddressType:
anyOf:
- type: string
enum:
- IPV4_ADDR
- IPV6_ADDR
- URL
- SIP_URI
- type: string
description: >
description: >
Possible values are
- IPV4_ADDR: Indicates that the address type is in the form of "dotted-decimal" IPv4
address.
- IPV6_ADDR: Indicates that the address type is in the form of IPv6 address.
- URL: Indicates that the address type is in the form of Uniform Resource Locator.
- SIP_URI: Indicates that the address type is in the form of SIP Uniform Resource
Identifier.
QosFlowUsage:
anyOf:
- type: string
enum:
- GENERAL
- IMS_SIG
- type: string
description: >
description: >
Possible values are
- GENERAL: Indicate no specific QoS flow usage information is available.
- IMS_SIG: Indicate that the QoS flow is used for IMS signalling only.
FailureCause:
anyOf:
- type: string
enum:
- PCC_RULE_EVENT
- PCC_QOS_FLOW_EVENT
- RULE_PERMANENT_ERROR
- RULE_TEMPORARY_ERROR
- type: string
CreditManagementStatus:
anyOf:
- type: string
enum:
- END_USER_SER_DENIED
- CREDIT_CTRL_NOT_APP
- AUTH_REJECTED
- USER_UNKNOWN
- RATING_FAILED
- type: string
3GPP
Release 16 175 3GPP TS 29.512 V16.5.0 (2020-06)
SessionRuleFailureCode:
anyOf:
- type: string
enum:
- NF_MAL
- RES_LIM
- UNSUCC_QOS_VAL
- UE_STA_SUSP
- type: string
description: >
description: >
Possible values are
- NF_MAL: Indicate that the PCC rule could not be successfully installed (for those
provisioned from the PCF) or activated (for those pre-defined in SMF) or enforced (for those already
successfully installed) due to SMF/UPF malfunction.
- RES_LIM: Indicate that the PCC rule could not be successfully installed (for those
provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those already
successfully installed) due to a limitation of resources at the SMF/UPF.
- UNSUCC_QOS_VAL: indicate that the QoS validation has failed.
- UE_STA_SUSP: Indicates that the UE is in suspend state.
SteeringFunctionality:
anyOf:
- type: string
enum:
- MPTCP
- ATSSS_LL
- type: string
description: >
description: >
Possible values are
- MPTCP: Indicates that PCF authorizes the MPTCP functionality to support traffic steering,
switching and splitting.
- ATSSS_LL: Indicates that PCF authorizes the ATSSS-LL functionality to support traffic
steering, switching and splitting.
SteerModeValue:
anyOf:
- type: string
enum:
- ACTIVE_STANDBY
- LOAD_BALANCING
- SMALLEST_DELAY
- PRIORITY_BASED
- type: string
MulticastAccessControl:
anyOf:
- type: string
enum:
- ALLOWED
- NOT_ALLOWED
- type: string
RequestedQosMonitoringParameter:
anyOf:
- type: string
enum:
- DOWNLINK
- UPLINK
- ROUND_TRIP
- type: string
ReportingFrequency:
anyOf:
- type: string
enum:
- EVENT_TRIGGERED
- PERIODIC
- SESSION_RELEASE
- type: string
SmPolicyAssociationReleaseCause:
anyOf:
- type: string
enum:
- UNSPECIFIED
- UE_SUBSCRIPTION
3GPP
Release 16 176 3GPP TS 29.512 V16.5.0 (2020-06)
- INSUFFICIENT_RES
- VALIDATION_CONDITION_NOT_MET
- type: string
PduSessionRelCause:
anyOf:
- type: string
enum:
- PS_TO_CS_HO
- type: string
MaPduIndication:
anyOf:
- type: string
enum:
- MA_PDU_REQUEST
- MA_PDU_ NETWORK_UPGRADE ALLOWED
- type: string
AtsssCapability:
anyOf:
- type: string
enum:
- MPTCP_ATSSS_LL_WITH_ASMODE_UL
- MPTCP_ATSSS_LL_WITH_EXSDMODE_DL_ASMODE_UL
- MPTCP_ATSSS_LL_WITH_ASMODE_DLUL
- ATSSS_LL
- MPTCP_ATSSS_LL
- type: string
#
NetLocAccessSupport:
anyOf:
- type: string
enum:
- ANR_NOT_SUPPORTED
- TZR_NOT_SUPPORTED
- LOC_NOT_SUPPORTED
- type: string
description: >
description: >
Possible values are
- ANR_NOT_SUPPORTED: Indicates that the access network does not support the report of access
network information.
- TZR_NOT_SUPPORTED: Indicates that the access network does not support the report of UE
time zone.
- LOC_NOT_SUPPORTED: Indicates that the access network does not support the report of UE
Location (or PLMN Id).
PolicyDecisionFailureCode:
anyOf:
- type: string
enum:
- TRA_CTRL_DECS_ERR
- QOS DECS_ERR
- CHG DECS_ERR
- USA_MON_DECS_ERR
- QOS_MON_DECS_ERR
- CON_DATA_ERR
- type: string
#
Annex B (normative):
5GC and EPC interworking scenario support
B.1 Scope
This annex defines procedures for 5GC and EPC interworking, which contains the following scenarios:
- EPS and 5GS interworking (i.e. 3GPP access connected to EPC and 3GPP access connected to 5GC).
- EPC/ePDG and 5GS interworking (i.e. ePDG connected to EPC and 3GPP access connected to 5GC).
3GPP
Release 16 177 3GPP TS 29.512 V16.5.0 (2020-06)
- EPS and 5GC/N3IWF interworking (i.e. 3GPP access connected to EPC and N3IWF connected to 5GC).
B.2 Npcf_SMPolicyControl Service
B.2.1 Service Description

B.2.1.1 Overview
Session Management Policy Control Service applies to the cases where the SMF+PGW-C interacts with the PCF in the
non-roaming scenario, the V-SMF+V-PGW-C interacts with the V-PCF in the local breakout roaming scenario and the
H-SMF+H-PGW-C interacts with the H-PCF in the home-routed scenario.
B.2.1.2 Service Architecture

The Session Management Policy Control Service is provided by the PCF as shown in the SBI representation model in
figure B.2.1.2-1 and in the reference point representation model in figure B.2.1.2.2.
In this scenario the NF Service Consumer is a combined SMF and PGW-C.
PCF
Npcf
Npcf_SMPolicyControl
SMF+PGW-C
Figure B.2.1.2-1: Reference Architecture for the Npcf_SMPolicyControl Service for 5GC and
EPC interworking scenario; SBI representation
PCF SMF+PGW-C
N7
Figure B.2.1.2-2: Reference Architecture for the Npcf_SMPolicyControl Service or 5GC and
EPC interworking scenario; reference point representation
NOTE: The SMF+PGW-C represents the V-SMF+V-PGW-C and the PCF represents the V-PCF in the local
breakout scenario. The SMF+PGW-C represents the H-SMF+H-PGW-C and the PCF represents the H-
PCF in the home routed scenario.
3GPP
Release 16 178 3GPP TS 29.512 V16.5.0 (2020-06)
B.3 Service Operation
B.3.1 Introduction
This subclause defines the specific service operations for the 5GC and EPC interworking scenario. In addition, the
service operations defined in subclause 4.2 shall be applicable.
NOTE: For brevity reason, the combined SMF and PGW-C is denoted as SMF in what follows.
B.3.2 Npcf_SMPolicyControl_Create Service Operation

B.3.2.0 General
When the UE establishes the PDN connection through the EPC network and the SMF+PGW-C receives the Create
Session Request message as defined in 3GPP TS 29.274 [37], the SMF+PGW-C shall behave as defined in
subclause 4.2.2.2 with the differences that the SMF+PGW-C shall include (if available) in SmPolicyContextData data
structure:
- the IMSI of the user within the "supi" attribute;
- the MSISDN of the user within the "gpsi" attribute;
- APN within the "dnn" attribute;
- PDU Session Id determined by the SMF+PGW-C within "pduSessionId" attribute for a UE that has an EPS
subscription that allows 5GC interworking but does not support 5GC NAS.
NOTE 1: For a PDN connection established via the MME or ePDG, the PDU Session ID value is assigned from a
reserved range as specified in Table 5.4.2-1 of TS 29.571 [11];
- PDN Type within the "pduSessionType" attribute;
- IMEI-SV within the "pei" attribute;
- IP-CAN type within the "accessType" attribute;
- RAT type within the "ratType" attribute;
NOTE 2: See Annex B.3.2.2 for further information.
- subscribed APN-AMBR within "subsSessAmbr" attribute;
- subscribed Default EPS bearer QoS within "subsDefQos" attribute;
NOTE 3: Subscribed APN-AMBR and the QCI within the subscribed default EPS bearer QoS are mapped to
subscribed Session-AMBR and 5QI as defined in Annex B.3.6.1 respectively.
- the S-NSSAI determined by the SMF+PGW-C within the "sliceInfo" attribute; and
- the bearer usage required of the default bearer within the "qosFlowUsage" attribute.
- the UE time zone information within "ueTimeZone" attribute, if available;
NOTE 5: The UE time zone is not available in EPC untrusted WLAN.
3GPP
Release 16 179 3GPP TS 29.512 V16.5.0 (2020-06)
B.3.2.1 UE Location related information

When the UE establishes the PDU session through the EPC/E-UTRAN network, the SMF+PGW-C shall include, if
available, the following user location information:
- user location information within the "eutraLocationInfo" attribute included in the "userLocationInfo" attribute;
and
- S-GW address, if available, within the "anGwAddr" attribute included in the "servNfId" attribute.
When the UE establishes the PDU session through the EPC/ePDG network, the SMF+PGW-C shall include, if available,
the following user location information:
- user location information within the "n3gaLocation" attribute included in the "userLocationInfo" attribute; and
- ePDG identification within the "anGwAddr" attribute included in the "servNfId" attribute.
NOTE: The "n3gaLocation" attribute does not include the "n3gppTai" and "n3IwfId" attributes in EPC
interworking scenarios.
B.3.2.2 Access Type related information

When the UE establishes the PDU session through the EPC/E-UTRAN network, the SMF+PGW shall include, if
available, the following access type information:
- the "3GPP_ACCESS" value within the "accessType" attribute; and
- the "EUTRA" value within the "ratType" attribute.
When the UE establishes the PDU session through the EPC/ePDG network, the SMF+PGW shall include, if available,
the following access type information:
- the "NON_3GPP_ACCESS" value within the "accessType" attribute;
- the "WLAN" or "VIRTUAL" value within the "ratType" attribute, as applicable; and
- the ePDG address in the "servNfId" attribute within the "anGwAddr" attribute.
B.3.3 Npcf_SMPolicyControl_UpdateNotify Service Operation

B.3.3.0 General
When the UE has an established PDN connection through the EPC/E-UTRAN network and the PCF provisions the
policy to the SMF+PGW-C as defined in subclause 4.2.3. The SMF+ PGW-C shall behave as defined in subclause 4.2.3
with the differences that the SMF+PGW-C shall map the QoS information within the PCC rule and/or session rule into
EPS QoS information as defined in Annex B.3.6.1.
B.3.3.1 Policy Update When UE suspends

If the PolicyUpdateWhenUESuspends feature as defined in subclause 5.8 is supported, and when the SMF receives the
policy decision from the PCF as defined in subclause 4.2.3.1 for a PDN connection maintained when the UE’s status is
suspend state, the SMF shall reject the request and include an HTTP "400 Bad Request" status code together with an
ErrorReport structure. Within the ErrorReport data structure, the SMF shall include the "error" attribute containing the
"cause" attribute of the ProblemDetails data structure set to "UE_STATUS_SUSPEND" which indicates the failure to
enforce the corresponding policy decision, except if the policy decision is for the PCC rule removal only and/or session
rule removal only, and further include the information as follows:
- If the policy decision includes the installation of one or more PCC rules, the SMF shall invoke the procedure as
defined in subclause 4.2.3.16 with the "failureCode" attribute set to "UE_STA_SUSP" and "ruleStatus" attribute
set to INACTIVE to indicate the failure to enforce those PCC rules.
3GPP
Release 16 180 3GPP TS 29.512 V16.5.0 (2020-06)
- If the policy decision includes the modification of one or more PCC rules, the SMF shall invoke the procedure as
set to ACTIVE to indicate the failure to enforce those PCC rules.
- If the policy decision includes the modification of one or more session rules, the SMF shall within an RuleReport
data structure include the "sessRuleReports" attribute. Within each SessionRuleReport data structure, the SMF
shall include the affected session rules within the "ruleIds" attribute(s), the "sessRuleFailureCode" attribute set to
"UE_STA_SUSP" and "ruleStatus" attribute set to ACTIVE to indicate the failure to enforce those session rules.
Upon reception of the "failureCode" attribute and/or "sessRuleFailureCode" attribute set to "UE_STA_SUSP" or the
ProblemDetails data structure set to "UE_STATUS_SUSPEND", the PCF shall not initiate any PDU Session
Modification procedure, except if it is initiated for the PCC rule removal only or the session rule removal only, for the
given PDU session over N7 until the UE’s status is resumed. When the SMF detected the UE’s status is resumed from
suspend state, the SMF shall inform the PCF of the UE status as defined in Annex B.3.4.2.
B.3.3.2 Request report of EPS Fallback

When the "EPSFallbackReport" feature is supported, if the AF requests the PCF to report the EPS fallback for voice
media type as described in subclauses 4.2.2.30 or 4.2.3.29 of 3GPP TS 29.514 [17] or in subclause E.3 of
3GPP TS 29.214 [18], the PCF shall perform the PCC rule provisioning procedure as defined in subclause 4.2.6.2.1 and
additionally provide the request of EPS fallback report to the SMF as follows:
- it shall include the "lastReqRuleData" attribute to contain the "reqData" attribute with the value
"EPS_FALLBACK" and the "refPccRuleIds" attribute to contain the related installed/modified PCC rule
identifier(s) with 5QI=1.
- it shall provide the "EPS_FALLBACK" policy control request rigger within the "policyCtrlReqTriggers"
attribute, if not provided before.
B.3.4 Npcf_SMPolicyControl_Update Service Operation

B.3.4.0 General
When the established PDN connection through the EPC/E-UTRAN network is modified and SMF+PGW-C receives
Modify Bearer Request, Modify Bearer or Delete Bearer Command message and if the SMF detects the policy control
request trigger(s) is met or the error(s) needs to be reported or when the UE handed over from the 5GS to the EPS and
the SMF detects the policy control request trigger(s) is met, the SMF+PGW-C shall behave as defined in
subclause 4.2.4.2 with the differences that the SMF+PGW-C shall include (if available) in the
SmPolicyUpdateContextData data structure:
- IP-CAN type within the "accessType" attribute;
- RAT type within the "ratType" attribute;
- subscribed APN-AMBR within the "subsSessAmbr" attribute;
- subscribed Default EPS bearer QoS Information within the "subsDefQos" attribute;
NOTE 2: Subscribed APN-AMBR and the QCI within the subscribed default EPS bearer QoS are mapped to
subscribed Session-AMBR and 5QI as defined in Annex B.3.6.1 respectively.
- the bearer usage required of the default bearer within the "qosFlowUsage" attribute; and
- user location information of EPC within the "userLocationInfo" attribute.
3GPP
Release 16 181 3GPP TS 29.512 V16.5.0 (2020-06)
B.3.4.1 Number of Supported Packet Filters Report

When the UE handed over from the EPC/E-UTRAN to the 5GS and the number of supported packet filters for signalled
QoS rules is received from the UE, the SMF shall include the "NUM_OF_PACKET_FILTER" within the
"repPolicyCtrlReqTriggers" attribute and the number of supported packet filters for signalled QoS rules within the
"numOfPackFilter". In this case, the PCF shall behave as defined in subclause 4.2.6.2.16.
B.3.4.2 Policy Update When UE suspends
B.3.4.2.1 Policy Update Error Report

If the PolicyUpdateWhenUESuspends feature as defined in subclause 5.8 is supported, and when the SMF receives the
policy decision from the PCF as defined in subclause 4.2.4.1 for a PDN connection maintained when the UE’s status is
suspend state, the SMF shall include the "ruleReports" attribute for the affected PCC rules and/or session rules to report
the failure within the SmPolicyUpdateContextData data structure. Within the ErrorReport data structure, the SMF shall
include the "error" attribute containing the "cause" attribute of the ProblemDetails data structure set to
"UE_STATUS_SUSPEND" which indicates the failure to enforce the corresponding policy decision, except if the
policy decision is for the PCC rule removal only and/or session rule removal only, and further include the information
as follows:
- if the policy decision includes the modification of one or more session rules, within an RuleReport instance, the
SMF shall include the "sessRuleReports" attribute. Within each SessionRuleReport data structure, the SMF shall
include the affected session rules within the "ruleIds" attribute(s), the "sessRuleFailureCode" attribute set to
"UE_STA_SUSP" and the "ruleStatus" attribute set to ACTIVE to indicate the failure to enforce those session
rules.
- if the policy decision includes the installation of one or more PCC rules, the SMF shall invoke the procedure as
set to INACTIVE to indicate the failure to enforce those PCC rules.
- if the policy decision includes the modification of one or more PCC rules, the SMF shall invoke the procedure
as defined in subclause 4.2.4.15 with the "failureCode" attribute set to "UE_STA_SUSP" and "ruleStatus"
attribute set to ACTIVE to indicate the failure to enforce those PCC rules.
Upon reception of the "failureCode" attribute and/or "sessRuleFailureCode" attribute set to "UE_STA_SUSP", the PCF
shall not initiate any PDU Session Modification procedure, except if it is initiated for the PCC rule removal only and/or
session rule removal only, for the given PDU session over N7 until the UE’s status is resumed.
B.3.4.2.2 UE State Change Report

If the SMF detected the UE’s status is resumed from suspend state, the SMF shall inform the PCF of the UE status
including the "UE_STATUS_RESUME" within "repPolicyCtrlReqTriggers" attribute. The PCF shall after this update
the SMF with PCC Rules or session rules if necessary.
B.3.4.3 UE Location related information

When the UE handed over from the 5GS to EPC/E-UTRAN the SMF+PGW-C shall include, together with the policy
control request triggers met, the following user location information:
- If the "SAREA_CH" or "SCELL_CH" policy control request trigger is provisioned and met, the user location
information within the "eutraLocationInfo" attribute included in the "userLocationInfo" attribute.
- If the "SCNN_CH" policy control request trigger is provisioned and met, the "servNfId" attribute including the
S-GW identification within the "anGwAddr" attribute.
When the UE handed over from the 5GS to EPC non-3GPP access, the SMF+PGW-C shall include, together with the
applicable provisioned policy control request triggers, the following user location information:
- If the "SAREA_CH" policy control request trigger is provisioned and met, the user location information within
the "n3gaLocation" attribute included in the "userLocationInfo" attribute; and
3GPP
Release 16 182 3GPP TS 29.512 V16.5.0 (2020-06)
- if the "SCNN_CH" policy control request trigger is provisioned and met, the ePDG identification within the
"anGwAddr" attribute included in the "servNfId" attribute.
NOTE: The "n3gaLocation" attribute does not include the "n3gppTai" and "n3IwfId" attributes in EPC
interworking scenarios.
B.3.4.4 Presence Reporting Area Information Report

When the UE is connected through the EPC/E-UTRAN network, the SMF+PGW-C receives the presence reporting area
information as defined in 3GPP TS 29.274 [37].
B.3.4.5 Access Type related information

The SMF+PGW shall include, when the policy control request trigger "AC_TY_CH" is met, the following access type
information:
- If after handover the new access type is EPC/E-UTRAN:
a) the "3GPP_ACCESS" value within the "accessType" attribute; and
b) the "EUTRA" value within the "ratType" attribute.
- If after handover the new access type is EPC/ePDG:
a) the "NON_3GPP_ACCESS" value within the "accessType" attribute;
b) the "WLAN" or "VIRTUAL" value within the "ratType" attribute, as applicable; and
c) the ePDG address in the "servNfId" attribute within the "anGwAddr" attribute.
NOTE 1: In the interworking scenario, "AC_TY_CH" is met when the UE handed over from the 5GC/N3IWF to
the EPC/E-UTRAN, or when the UE handed over from the 5GS to the EPC/ePDG.
The SMF+PGW shall include, when the policy control request trigger "RAT_TY_CH " is met, the following RAT type
information:
- If after handover the new RAT type is the E-UTRA, the "EUTRA" value within the "ratType" attribute.
- If after handover the new RAT type is the WLAN, the "WLAN" or "VIRTUAL" value within the "ratType"
attribute, as applicable.
NOTE 2: In the interworking scenario, "RAT_TY_CH" is met when the UE handed over from the NR to the E-
UTRA or when the UE handed over from the NR to the WLAN and from E-UTRA to WLAN.
B.3.4.6 Report of EPS Fallback

When the "EPSFallbackReport" feature is supported, if the "PolicyCtrlReqTriggers" attribute with the value
"EPS_FALLBACK" has been provided to the SMF, the SMF shall notify to the PCF of EPS fallback when a PCC rule
referred from the "lastReqRuleData" attribute required the EPS fallback report within the "reqData" attribute.
When the SMF received a PDU session modification response from the access network indicating the establishment of
the QoS flow with 5QI=1 is rejected due to EPS fallback, the SMF shall within the SmPolicyUpdateContextData data
structure include:
- the "EPS_FALLBACK" value within the "repPolicyCtrlReqTriggers" attribute; and
- the affected PCC rules within the "pccRuleIds" attribute included in the "ruleReports" attribute, where the
"ruleStatus" attribute is set to ACTIVE.
The PCF shall identify the AF session that requested the voice media type that triggered the EPS fallback and shall
notify the AF as described in subclauses 4.2.5.15 of 3GPP TS 29.514 [17] or in subclause E.3 of 3GPP TS 29.214 [18].
3GPP
Release 16 183 3GPP TS 29.512 V16.5.0 (2020-06)
B.3.4.7 MA PDU Session

If the "ATSSS" feature defined in subclause 5.8 is supported, when the UE handed over from the EPC/E-UTRAN to the
5GS and the MA PDU Request Indication or MA PDU Network-Upgrade Allowed Indication and ATSSS Capability
are received from the UE, the SMF shall include the "MA_PDU" within the "repPolicyCtrlReqTriggers" attribute, and,
as defined in subclause 4.2.2.17, the SMF shall include the MA PDU session Indication within the "maPduInd" attribute
and the ATSSS capability of the MA PDU session within the "atsssCapab" attribute. In this case, the PCF shall behave
as defined in subclause 4.2.2.17.
B.3.5 Npcf_SMPolicyControl_Delete Service Operation

B.3.5.1 General
When the UE deletes the PDN connection through the EPC network and the SMF+PGW-C shall behave as defined in
subclause 4.2.5.2 with the difference that the SMF+PGW-C shall include the information elements contained in the
Delete Session Request message within the SmPolicyDeleteData data structure.
NOTE: See Annex B.3.2.1 for location information.
B.3.6 Provisioning and Enforcement of Policy Decisions

B.3.6.1 QoS mapping perfomed by the SMF+PGW-C
When the UE is served by the 5GC, during PDU Session establishment and GBR QoS flow establishment, SMF+
PGW-C performs EPS QoS mappings, from the 5G QoS parameters obtained from the PCF, and allocates TFT with the
PCC rules obtained from the PCF. If a TFT is to be allocated for a downlink unidirectional EPS bearer mapped from a
downlink only QoS Flow, the SMF+ PGW-C shall allocate a TFT packet filter that effectively disallows any useful
uplink packet as described in subclause 15.3.3.4 of 3GPP TS 23.060 [26]. The SMF+PGW-C sends the mapped QoS
parameters and TFT to the UE via PCO.
When the UE is served by the EPC, during PDN Connection establishment and dedicated bearer
establishment/modification, SMF+ PGW-C performs EPS QoS mappings, from the 5G QoS parameters obtained from
the PCF, and allocates TFT with the PCC rules obtained from the PCF. Other 5G QoS parameters corresponding to the
PDN connection, e.g. Session AMBR, and QoS rules and QoS Flow level QoS parameters if needed for the QoS
Flow(s) associated with the QoS rule(s), are sent to UE in PCO.
The SMF+PGW-C shall perform EPS QoS mappings as defined in subclause 4.11.1.1 and Annex C in
3GPP TS 23.502 [3] as follows:
- ignore the QNC and reflective QoS indication if received;
- for standardized 5QIs, the authorized 5QI is one to one mapped to the QCI;
NOTE: The delay critical 5QI mapping to QCI is unspecified in the present specification.
- for non-standardized 5QI,derive the authorized QCI based on the authorized 5QI and operator policy;
- one to one map the subscribed default QCI to the subscribed default 5QI;
- set the subscribed Session-AMBR according to operator policy (e.g. taking the value of subscribed APN-AMBR
into account); and
- set the authorized APN-AMBR according to operator policy (e.g. taking the value of authorized Session-AMBR
into account).
B.3.6.2 Provisioning of Presence Reporting Area Information

When the UE is connected through the EPC/E-UTRAN network, the SMF+PGW-C initiates the appropriate PDU
session specific procedures specified in 3GPP TS 29.274 [37] to obtain the presence state of a UE in a presence
reporting area.
3GPP
Release 16 184 3GPP TS 29.512 V16.5.0 (2020-06)
B.3.6.3 Request and Report of Access Network information

If the NetLoc feature as defined in subclause 5.8 is supported, the PCF may request the SMF+PGW-C to report the
access network information as defined in subclause 4.2.6.5.4.
If the AN_INFO policy control request trigger is set, upon receiving the "lastReqRuleData" attribute with the "reqData"
attribute with the value(s) MS_TIME_ZONE and/or USER_LOC_INFO and the "refPccRuleIds" attribute containing
the PCC rule identifier(s) corresponding to the PCC rule(s) being installed, modified or removed:
- If the "reqData" attribute indicates MS_TIME_ZONE and USER_LOC_INFO and the SMF+PGW-C determines
that the access network does not support the access network information reporting, the SMF+PGW-C shall
immediately inform the PCF by including the "netLocAccSupp" attribute set to "ANR_NOT_SUPPORTED”
value in the "UeCampingRep" data structure returned in the "200 OK" response to the policy update notification
request.
- If the "reqData" attribute only includes the MS_TIME_ZONE value and the SMF+PGW-C determines that the
access network does not support the report of the UE time zone, the SMF+PGW-C shall immediately inform the
PCF by including the "netLocAccSupp" attribute set to "TZR_NOT_SUPPORTED” value in the
"UeCampingRep" data structure returned in the "200 OK" response to the policy update notification request.
- If the "reqData" attribute only includes the USER_LOC_INFO value and the SMF+PGW-C determines that the
access network does not support the report of the UE location, the SMF+PGW-C shall immediately inform the
PCF by including the "netLocAccSupp" attribute set to "LOC_NOT_SUPPORTED” value in the
"UeCampingRep" data structure returned in the "200 OK" response to the policy update notification request.
- If the "reqData" attribute includes the USER_LOC_INFO value and/or the MS_TIME_ZONE value, and the
SMF+PGW-C determines the access network supports the report of UE time zone, the SMF+PGW-C shall apply
appropriate procedures to the EPC access network to obtain the requested access network information and shall
behave as specified in subclause 4.2.4.9.
NOTE: The SMF+PGW determines whether the access network supports access network information reporting
based on access type, RAT type and trusted/untrusted type of the access network.
Annex C (normative):
Wireless and wireline convergence access support
C.1 Scope
This annex defines procedures for wireless and wireline convergence access support for 5GS. The specific stage 2
definition and related procedures are contained in 3GPP TS 23.316 [42]. The System Architecture for wireless and
wireline convergence access is defined in 3GPP TS 23.501 [2].
C.2 Npcf_SMPolicyControl Service
C.2.1 Service Description

C.2.1.1 Overview
Subclause 4.1.1 applies with the exception that the UE is replaced by the 5G-RG and the W-AGF, which is acting as a
UE towards the 5GC on behalf of the FN-RG.
3GPP
Release 16 185 3GPP TS 29.512 V16.5.0 (2020-06)
C.2.1.2 Service Architecture

Subclause 4.1.2 applies with the exception that roaming functionality does not apply for session policy control in this
Release of the specification for 5G-RG users connecting to the 5GC via W-5GAN and FN-RG users. Roaming
architecture is only applicable to a 5G-RG connecting to the 5GC via NG RAN.
The 5G-RG may support LTE access connected to EPC and EPC interworking as defined in Annex B.
C.2.1.3 Network Functions
C.2.1.3.1 Policy Control Function (PCF)

The PCF functionality defined in subclause 4.1.3.1 shall apply with the exceptions described in this Annex.
C.2.1.3.2 NF Service Consumers

The functionality defined in subclause 4.1.3.2 shall apply.
The enforcement of the policy decisions applies for a single access PDU session over wireline access and multiaccess
PDU sessions over wireline access and 3GPP with the exceptions described in this Annex.
C.2.1.4 Rules
C.2.1.4.1 PCC Rules

Functionality as described in subclause 4.1.4.2 applies with the following exceptions for the traffic of a PDU session
over wireline access:
- UL/DL Maximum Packet Loss Rate information does not apply.
- QoS Notification Control Information does not apply.
C.2.1.5 Policy control request trigger

The Policy Control Request Triggers defined in subclause 5.6.3.6 and related procedures are supported for a 5G-RG
connecting to the 5GC via NG-RAN.
The Policy Control Request Triggers defined in subclause 5.6.3.6 are supported for a 5G-RG or FN-RG connecting to
the 5GC via W-5GAN with the following not supporting ones:
- PLMN_CH
- SAREA_CH
- SCNN_CH
- PRA_CH
- PS_DA_OFF
- QOS_NOTIF
- RES_RELEASE
- UE_STATUS_RESUME
- TSN_ETHER_PORT
- TSN_CONTAINER
Consequently, the procedures related to above policy control request triggers are not supported in the corresponding
service operations.
3GPP
Release 16 186 3GPP TS 29.512 V16.5.0 (2020-06)
C.3 Service Operation
C.3.1 Introduction
Subclause 4.2.1 applies.
C.3.2 Npcf_SMPolicyControl_Create Service Operation

C.3.2.1 General
Subclause 4.2.2.2 is applied with the following differences:
- The allocated /128 IPv6 address or IPv6 /64 prefix or IPv6 prefix shorter than /64 is included within the
"ipv6AddressPrefix" attribute.
- Request of Presence Reporting Area Change Report is not applicable when the 5G-RG or FN-RG connects to the
5GC via W-5GAN.
- Global Line ID including the line Id and either PLMN Id or operator Id is encoded within the "gli" attribute of
the "n3gaLocation" attribute included in the "userLoc" attribute within the PolicyAssociationRequest data
structure when the 5G-RG or FN-RG registers via W-5GBAN.
- The HFC Node Identifier is encoded in the "hfcNodeId" attribute of the "n3gaLocation" attribute included in the
"userLocationInfo" attribute within the SmPolicyContextData data structure when the 5G-CRG or FN-CRG
connects to the 5GC via W-5GCAN.
- The PEI that may be included within the "pei" attribute shall have one of the following representations:
i. When the UE supports only wireline access, the PEI shall be a MAC address.
NOTE: When the PEI includes an indication that the MAC address cannot be used as Equipment identifier, the
PEI cannot be trusted for regulatory purposes and cannot be used for equipment based policy evaluation.
ii. When the UE supports at least one 3GPP access technology, the PEI shall be the allocated IMEI or IMEISV.
- To support of Hybrid Access for a 5G-RG with a single PDU session as described in subclause C.3.6.2.2, EPC
interworking specific attributes and procedures apply as described in subclause B.3.2;
- Access Traffic Steering, Switching and Splitting as defined in subclause 4.2.2.17 is only applicable to the case
that the 5G-RG establishes:
a) Hybrid Access with a multi-access PDU Session connectivity via NG-RAN and W-5GAN, as described in
subclause C.3.6.2.3; or
b) Hybrid Access with a multi-access PDU Session connectivity via EPC/E-UTRAN and W-5GAN, as
described in subclause C.3.6.2.4.
- The access network transmission technology for the wireline access may be encoded:
i. within the "ratType" attribute of the SmPolicyContextData type; or
ii. when Access Traffic Steering, Switching and Splitting is supported, within the "ratType" attribute of the
SmPolicyContextData type, or within the "ratType" attribute of the AdditionalAccessInfo type.
C.3.2.2 IPTV service support

If the PCF fetches the Multicast Access Control information from the UDR as defined in 3GPP TS 29.519 [15], the PCF
shall authorize a PCC rule as defined in Annex C.3.6.1 and provision it to the SMF in the HTTP response message.
3GPP
Release 16 187 3GPP TS 29.512 V16.5.0 (2020-06)
C.3.3 Npcf_SMPolicyControl_UpdateNotify Service Operation

C.3.3.1 General
The descriptions in subclause 4.2.3.1 are applied with the following differences:
- To support Hybrid Access for a 5G-RG with a single PDU session as described in subclause C.3.6.2.2, EPC
interworking specific attributes and procedures apply as described in B.3.3;
- Access traffic steering, switching and splitting support as described in subclause 4.2.3.21 is only applicable to
the case that 5G-RG establishes:
- Request for the result of PCC rule removal is not applicable when the 5G-RG or FN-RG connects to the 5GC via
W-5GAN.

If the PCF fetches the Multicast Access Control information from the UDR as defined in 3GPP TS 29.519 [15], for each
impacted PDU session, the PCF shall authorize a PCC rule as defined in Annex C.3.6.1 and provision it to the SMF in
the HTTP POST message.
C.3.4 Npcf_SMPolicyControl_Update Service Operation

C.3.4.1 General
Subclause 4.2.4.2 is applied with the following differences:
- The released /128 IPv6 address or IPv6 /64 prefix or IPv6 prefix shorter than /64 is included within the
"relIpv6AddressPrefix" attribute.
- RAN cause and/or the NAS cause information is not applicable when the 5G-RG or FN-RG connects the 5GC
via W-5GAN.
- To support Hybrid Access for a 5G-RG with a single PDU session as described in subclause C.3.6.2.2, EPC
interworking specific attributes and procedures apply as described in B.3.4;
- Access traffic steering, switching and splitting support as described in subclause 4.2.4.25 is only applicable to
the case that 5G-RG establishes:
- The access network transmission technology for the wireline access may be encoded:
i. within the "ratType" attribute of the SmPolicyUpdateContextData type; or
ii. when Access Traffic Steering, Switching and Splitting is supported, within the "ratType" attribute of the
SmPolicyContextUpdateData type, or within the "ratType" attribute of the AdditionalAccessInfo type.
3GPP
Release 16 188 3GPP TS 29.512 V16.5.0 (2020-06)

If the "WWC" feature is supported and "5G_RG_JOIN" and/or "5G_RG_LEAVE" are provisioned and when the SMF
detects a 5G-RG has joined or left to an IP Multicast Group, the SMF shall send an HTTP POST message as defined in
subclause 4.2.4.2 and include the "5G_RG_JOIN" or "5G_RG_LEAVE" within the "repPolicyCtrlReqTriggers"
attribute respectively and the received one or more IP multicast addressing information within the "mulAddrInfos"
attribute. Within each IpMulticastAddressInfo data structure, the SMF shall include the destination IPv4 multicast
address of the DL multicast flow within the "ipv4MulAddr" attribute and the source IPv4 address of the DL multicast
flow within the "srcIpv4Addr" attribute if available or the destination IPv6 multicast address of the DL multicast flow
within the "ipv6MulAddr" attribute and the source IPv6 address of the DL multicast flow within the "srcIpv6Addr"
attribute if available.
NOTE: The corresponding notification can be used by the PCF to manage Preview Rights related with an IP
multicast flow corresponding to an IPTV channel by provisioning the corresponding PCC rule. In this
case the PCF is responsible to remove the provisioned PCC rule when the preview duration has elapsed.
C.3.5 Npcf_SMPolicyControl_Delete Service Operation

C.3.5.1 General
Subclause 4.2.5.1 is applied with the following differences and limitations:
- Global Line ID including the line Id and either PLMN Id or operator Id is encoded within the "gli" attribute of
the "n3gaLocation" attribute included in the "userLocationInfo" attribute within the SmPolicyDeleteData data
structure when the 5G-RG or FN-RG connects the 5GC via W-5GBAN.
- The HFC Node Identifier is encoded in the "hfcNodeId" attribute of the "n3gaLocation" attribute included in the
"userLocationInfo" attribute within the SmPolicyDeleteData data structure when the 5G-CRG or FN-CRG
connects to the 5GC via W-5GCAN.
- RAN cause and/or the NAS cause information is not applicable when the 5G-RG or FN-RG connects the 5GC
via W-5GAN.
C.3.6 Provisioning and Enforcement of Policy Decisions

Subclause 4.2.6 applies with the following exceptions for the traffic of a PDU session over wireline access:
- Policy provisioning and enforcement of authorized QoS per service data flow as described in subclause 4.2.6.6.2
applies with the following differences:
a) Determination of Maximum Packet Loss Rate for UL/DL does not apply.
b) PCF does not request a notification when authorized GBR or delay critical GBR cannot be guaranteed or can
be guaranteed again, i.e. "qnc" attribute does not apply.
- Provisioning of PCC Rules for Multimedia Priority Services is not supported. Subclause 4.2.6.2.12 does not
apply.
- Provisioning of PCC Rules for Mission Critical Services is not supported. Subclause 4.2.6.2.19 does not apply.

If the "WWC" feature is supported by the SMF and PCF as defined in subclause 5.8, when the PCF fetches the
Multicast Access Control information from the UDR as defined in 3GPP TS 29.519 [15] applicable for a SUPI or
Internal Group Id, the PCF authorizes the request. For impacted PDU Session that corresponds to the request, the PCF
shall determine the PCC rules that are generated based on the request as follows:
- The PCF include the multicast address within the "flowInfos" attribute of the PCC rule;
- The PCF shall include the "mulAccCtrl" attribute set to "ALLOWED" within a Traffic Control Data instance
which the PCC rule refers to indicate that the multicast channel is allowed.
3GPP
Release 16 189 3GPP TS 29.512 V16.5.0 (2020-06)
- The PCF shall include the "mulAccCtrl" attribute set to "NOT_ALLOWED" within a Traffic Control Data
instance which the PCC rule refers to indicate that the multicast channel is not allowed.
NOTE: The "flowStatus" attribute is not included in this Traffic Control Data instance.
C.3.6.2 Hybrid Access support
C.3.6.2.1 General
This clause specifies the support of policy control for Hybrid Access considering both, the support of single access PDU
sessions and MA PDU sessions.
Hybrid Access applies to a 5G-RG capable of connecting to:
- both, NG-RAN and wireline access; and/or
- both, wireline access and EPC/E-UTRAN using EPC interworking as described in Annex B.
Hybrid Access does not apply to FN-RG.
C.3.6.2.2 Hybrid Access with single PDU session

Hybrid Access scenarios with single PDU sessions shall only use one of the two accesses, but the PDU session can be
handover over between the two accesses.
When the "WWC" feature is supported by the SMF and the PCF as defined in subclause 5.8:
- for a 5G-RG capable of connecting to the NG-RAN and the wireline access, the procedures specified in the main
body of this specification apply, except:
i. the UE is replaced by the 5G-RG; and
ii. the non-3GPP access is replaced by the wireline access, as specified in this annex;
- for a 5G-RG capable of connecting to the wireline access and the EPC/E-UTRAN access, the procedures
specified in the Annex B of this specification apply, except:
i. the UE is replaced by the 5G-RG; and
ii. the non-3GPP access N3IWF is replaced by the wireline access.
C.3.6.2.3 Hybrid Access with MA PDU session connectivity over NG-RAN and wireline
If the "WWC" and the "ATSSS" features are supported by the SMF and the PCF as defined in subclause 5.8, this
scenario uses the Access Traffic Steering, Switching and Splitting functionality as described in subclauses 4.2.2.17,
4.2.3.21, and 4.2.4.25.8 with the following differences:
- UE is replaced by 5G-RG.
- Non-3GPP access(es) is replaced by wireline access.
C.3.6.2.4 Hybrid Access with MA PDU session connectivity over EPC/E-UTRAN and
wireline using EPC interworking scenarios
If the "WWC" and the "ATSSS" features are supported by the SMF and the PCF as defined in subclause 5.8, this
scenario uses the Access Traffic Steering, Switching and Splitting functionality as described in subclauses 4.2.2.17,
4.2.3.21, and 4.2.4.2 with the following specifics:
- UE is replaced by 5G-RG.
- Non-3GPP access(es) is replaced by wireline access.
3GPP
Release 16 190 3GPP TS 29.512 V16.5.0 (2020-06)
- Multi access connectivity is provided using ATSSS using both, EPC (as 3GPP access) and wireline access/5GC
system (as non-3GPP access), where:
i. the ATSSS rules are derived from PCC rules and provided from the PGW-C+SMF to the 5G-RG over
wireline access/5GC system;
ii. when the 5G-RG requests a PDN connection in EPC indicating the association with a MA PDU session, the
PDN connection may be handed over to 3GPP access in 5GC without affecting the ATSSS control.
3GPP
Release 16 191 3GPP TS 29.512 V16.5.0 (2020-06)
Annex D(informative):
Change history
Date Meeting TDoc CR Rev Cat Subject/Comment New
version
2017-10 TS skeleton of Session Management Policy Control Services 0.0.0
specification
2017-10 CT3#92 Inclusion of C3-175237, C3-175353 and editorial changes 0.1.0
from Rapporteur
2017-12 CT3#93 Inclusion of C3-176145, C3-176248, C3-176252, C3-176254, 0.2.0
C3-176255, C3-176256, C3-176257, C3-176319, C3-
176320, C3-176321, C3-176322, C3-176323 and editorial
changes from Rapporteur
C3-180303, C3-180343, C3-180202, C3-180305, C3-
180307, C3- 180308, C3-180306, C3-180309, C3-180310,
C3-1801311, C3-180312
C3-181226, C3-181227
2018-04 CT3#96 C3-182515 Inclusion of C3-182056, C3-182318, C3-182322, C3-182463, 0.5.0
C3-182325, C3-182327, C3-182330, C3-182331, C3-
182132, C3-182332, C3-182324, C3-182482.
2018-05 CT3#97 C3-183868 Inclusion of C3-183811, C3-183889, C3-183748, C3-183749, 0.6.0
C3-183845, C3-183461, C3-183846, C3-183847, C3-
183884, C3-183850, C3-183851, C3-183852, C3-183853,
C3-183470, C3-183855, C3-183854, C3-183760, C3-
183885, C3-183736, C3-183848, C3-183857, C3-183858,
C3-183765, C3-183766, C3-183486, C3-183886, C3-
183859, C3-183887, C3-183488, C3-183489, C3-183888,
C3-183815, C3-183769, C3-183793, C3-183816, C3-
183763, C3-183509, C3-183865, C3-183866, C3-183771,
C3-183867, C3-183772, C3-183818, C3-183255, C3-
183868, C3-183284
2018-06 CT#80 CP-181036 TS sent to plenary for approval 1.0.0
2018-06 CT#80 CP-181036 TS approved by plenary 15.0.0
2018-09 CT#81 CP-182015 0001 5 F Updates for TS 29.512 structure 15.1.0
2018-09 CT#81 CP-182015 0002 4 F Update of Npcf_SMPolicyControl_Create Service Operation 15.1.0
2018-09 CT#81 CP-182015 0003 5 F Update of Npcf_SMPolicyControl_UpdateNotify Service 15.1.0
Operation
2018-09 CT#81 CP-182015 0004 3 F Update of Npcf_SMPolicyControl_Update Service Operation 15.1.0
2018-09 CT#81 CP-182015 0005 4 F Update of Npcf_SMPolicyControl_Delete Service Operation 15.1.0
2018-09 CT#81 CP-182015 0006 5 F Multi-homing support 15.1.0
2018-09 CT#81 CP-182015 0007 2 F Access Network Charging Identifier request and report 15.1.0
2018-09 CT#81 CP-182015 0008 3 F Request result of PCC rule removal 15.1.0
2018-09 CT#81 CP-182015 0009 3 F Request the successful resource allocation notification 15.1.0
2018-09 CT#81 CP-182168 0010 6 F HTTP error handling procedure 15.1.0
2018-09 CT#81 CP-182169 0011 7 F PCC Rule Error Handling 15.1.0
2018-09 CT#81 CP-182015 0012 2 F Failure cases of Npcf_SMPolicyControl_Create Service 15.1.0
Operation
2018-09 CT#81 CP-182015 0013 5 F Failure cases of Npcf_SMPolicyControl_UpdateNotify 15.1.0
Service Operation
2018-09 CT#81 CP-182015 0014 2 F Failure cases of Npcf_SMPolicyControl_Update Service 15.1.0
Operation
2018-09 CT#81 CP-182015 0015 1 F Update of PCF and SMF function descriptions 15.1.0
2018-09 CT#81 CP-182015 0016 3 F Rules, Session rules, PCC rules definition updates 15.1.0
2018-09 CT#81 CP-182015 0017 2 F Policy Decision types Updates 15.1.0
2018-09 CT#81 CP-182015 0018 4 F Policy control request trigger definition update 15.1.0
2018-09 CT#81 CP-182015 0019 2 F Conditioned PCC rule update 15.1.0
2018-09 CT#81 CP-182015 0020 2 F Conditioned session rule update 15.1.0
2018-09 CT#81 CP-182015 0021 2 F IMS restoration support 15.1.0
2018-09 CT#81 CP-182015 0022 9 F PRA support 15.1.0
2018-09 CT#81 CP-182015 0023 5 F Update of steering the traffic to a local access of the data 15.1.0
network
2018-09 CT#81 CP-182015 0024 2 F Support for Ethernet PDU type 15.1.0
2018-09 CT#81 CP-182015 0025 6 F Update of Provisioning of charging related information for 15.1.0
PDU session
2018-09 CT#81 CP-182015 0026 4 F UE requests specific QoS handling for selected SDF 15.1.0
2018-09 CT#81 CP-182015 0027 6 F Provisioning of IP index information 15.1.0
2018-09 CT#81 CP-182015 0028 1 F Update of Multimedia Priority Services 15.1.0
2018-09 CT#81 CP-182015 0029 3 F Exclude the traffic from the session level usage monitoring 15.1.0
3GPP
Release 16 192 3GPP TS 29.512 V16.5.0 (2020-06)
2018-09 CT#81 CP-182015 0030 3 F Provisioning of specific QoS parameters together with 5QI 15.1.0
2018-09 CT#81 CP-182015 0031 1 F Add Unspecified value to the FlowDirection data type 15.1.0
2018-09 CT#81 CP-182015 0032 2 F Completion of definitions of UsageMonitoringData and 15.1.0
AccuUsageReport
2018-09 CT#81 CP-182015 0033 4 F Definition of FlowStatus data type 15.1.0
2018-09 CT#81 CP-182015 0034 1 F Definition of RedirectAddressType data type 15.1.0
2018-09 CT#81 CP-182015 0035 1 F Mandate the TrafficControlData decision 15.1.0
2018-09 CT#81 CP-182015 0036 2 F Reflective QoS support 15.1.0
2018-09 CT#81 CP-182015 0037 1 F Remove the DELETE method 15.1.0
2018-09 CT#81 CP-182015 0038 1 F Remove the Packet Loss Rate from the QoS characteristics 15.1.0
2018-09 CT#81 CP-182015 0039 1 F Re-use the ARP data type from 29.571 15.1.0
2018-09 CT#81 CP-182015 0043 1 F Definition of DNAI 15.1.0
2018-09 CT#81 CP-182015 0044 1 F Completion of ConditionData 15.1.0
2018-09 CT#81 CP-182015 0045 1 F Completion of TrafficControlData data type 15.1.0
2018-09 CT#81 CP-182023 0046 1 B Trace activation 15.1.0
2018-09 CT#81 CP-182015 0047 2 F Corrections on the notification URIs defined for the 15.1.0
UpdateNotify
2018-09 CT#81 CP-182015 0048 4 F Corrections on attributes and data types 15.1.0
2018-09 CT#81 CP-182015 0049 - F Corrections on Supported Features 15.1.0
2018-09 CT#81 CP-182015 0050 1 F Update custom operation for Npcf_SMPolicyControl_Update 15.1.0
2018-09 CT#81 CP-182015 0051 - F Missing Slice Information 15.1.0
2018-09 CT#81 CP-182015 0052 1 F Solution to IPv4 overlapping 15.1.0
2018-09 CT#81 CP-182015 0053 1 F Description of Structured data types 15.1.0
2018-09 CT#81 CP-182104 0054 1 B Support of PCC rule versioning 15.1.0
2018-09 CT#81 CP-182015 0055 1 F Update of Sponsored data connectivity support 15.1.0
2018-09 CT#81 CP-182015 0056 1 F Update of resource structure 15.1.0
2018-09 CT#81 CP-182015 0057 1 F Correction on cardinality of array and map 15.1.0
2018-09 CT#81 CP-182015 0058 - F Update of PccRule data type 15.1.0
2018-09 CT#81 CP-182015 0059 1 F Open issues on Reused data types 15.1.0
2018-09 CT#81 CP-182015 0060 - F DNAI report 15.1.0
2018-09 CT#81 CP-182015 0061 - F Definition of maxPacketLossRate 15.1.0
2018-12 CT#82 CP-183205 0063 6 F Correction to the AF influence traffic steering control 15.2.0
2018-12 CT#82 CP-183205 0064 2 F Some corrections to the OpenAPI file 15.2.0
2018-12 CT#82 CP-183205 0065 3 F Backgroud data transfer support 15.2.0
2018-12 CT#82 CP-183205 0066 4 F Clarification of default QoS 15.2.0
2018-12 CT#82 CP-183205 0067 3 F Clarification of Maximum Packet Loss Rate authorization 15.2.0
2018-12 CT#82 CP-183205 0068 1 F Clarification of PCC rule enforcement 15.2.0
2018-12 CT#82 CP-183205 0069 - F Clarification of service data flow template 15.2.0
2018-12 CT#82 CP-183205 0070 - F Correction to name of maximumDataBurstVolume attribute 15.2.0
2018-12 CT#82 CP-183205 0071 1 F Correction to the QoS notification control authorization 15.2.0
2018-12 CT#82 CP-183205 0072 3 F IMS dedicated signalling QoS flow 15.2.0
2018-12 CT#82 CP-183205 0073 2 F Internal Group Id during the PDU session establishment 15.2.0
2018-12 CT#82 CP-183205 0074 3 F Number of packet filters sent to the UE 15.2.0
2018-12 CT#82 CP-183205 0075 2 F Packet filter identifier 15.2.0
Remove two values of policy control request triggers in 15.2.0
2018-12 CT#82 CP-183205 0076 1 F
OpenAPI
2018-12 CT#82 CP-183205 0077 1 F SM policy association termination 15.2.0
2018-12 CT#82 CP-183205 0078 3 F The procedure of QoS notification control 15.2.0
2018-12 CT#82 CP-183205 0079 4 F Architecture of 5GS and EPS interworking scenario support 15.2.0
2018-12 CT#82 CP-183205 0083 2 F QoS mapping in 5GS and EPS interworking scenario 15.2.0
2018-12 CT#82 CP-183205 0084 - F PCC Rules for MPS 15.2.0
2018-12 CT#82 CP-183205 0086 2 F ExternalDocs field 15.2.0
2018-12 CT#82 CP-183205 0089 1 F Correction of SMPolicyControl resource URI structure 15.2.0
2018-12 CT#82 CP-183205 0089 2 F Correction of SMPolicyControl resource URI structure 15.2.0
2018-12 CT#82 CP-183205 0090 1 F Definition on map keys in SmPolicyDecision 15.2.0
2018-12 CT#82 CP-183205 0091 1 F Security field 15.2.0
2018-12 CT#82 CP-183205 0092 1 F Correction of datatypes related to QoS 15.2.0
2018-12 CT#82 CP-183205 0093 1 F Correction of 404 error information 15.2.0
2018-12 CT#82 CP-183205 0094 - F Correction of API name 15.2.0
2018-12 CT#82 CP-183205 0095 1 F Corrections of external references in OpenAPI 15.2.0
2018-12 CT#82 CP-183205 0096 4 F Corrections on IP index provisioning 15.2.0
Corrections misused data types, attributes and error 15.2.0
2018-12 CT#82 CP-183205 0097 1 F
definitions
2018-12 CT#82 CP-183205 0098 2 F Application Error POLICY_CONTEXT_DENIED 15.2.0
2018-12 CT#82 CP-183205 0099 2 F Corrections on RAN-NAS-Cause feature 15.2.0
2018-12 CT#82 CP-183205 0100 1 F Missing Policy Control Request trigger for RAT Type Change 15.2.0
2018-12 CT#82 CP-183205 0101 2 F Corrections on rule versioning 15.2.0
Corrections for Npcf_SMPolicyControl_UpdateNotify service 15.2.0
2018-12 CT#82 CP-183205 0102 1 F
operation.
2018-12 CT#82 CP-183205 0103 - F Default value for apiRoot 15.2.0
2018-12 CT#82 CP-183205 0104 1 F Correction to RAN-NAS-Cause feature 15.2.0
2018-12 CT#82 CP-183205 0105 1 F a new PolicyControlRequestTrigger for refQosIndication 15.2.0
3GPP
Release 16 193 3GPP TS 29.512 V16.5.0 (2020-06)
2018-12 CT#82 CP-183205 0106 1 F PCC rule error report triggerconvention 15.2.0
2018-12 CT#82 CP-183205 0108 1 F Missing SponsoredConnectivity feature 15.2.0
2018-12 CT#82 CP-183205 0109 2 F Correct DNAI change type in OpenAPI 15.2.0
2018-12 CT#82 CP-183205 0110 3 F Selection of Predefined PCC Rule Base 15.2.0
Correction to treatment of subscribed default QoS and 15.2.0
2018-12 CT#82 CP-183205
0111 3 F authorized default QoS
2018-12 CT#82 CP-183123 0113 1 F Address attribute for the network entity performing charging 15.2.0
2018-12 CT#82 CP-183205 0115 1 F Status code update for Npcf_SMPolicyControl API 15.2.0
2018-12 CT#82 CP-183205 0116 1 F CHF discovery and selection 15.2.0
2018-12 CT#82 CP-183205 0117 1 F Condition Data 15.2.0
2018-12 CT#82 CP-183205 0119 - F Correction to authDefaultQos attribute 15.2.0
2018-12 CT#82 CP-183205 0120 1 F Correction to error handling 15.2.0
2018-12 CT#82 CP-183205 0121 - F Correction to Partial Success handling 15.2.0
2018-12 CT#82 CP-183205 0122 2 F Correction to precedence of the PCC rule 15.2.0
2018-12 CT#82 CP-183205 0123 2 F Correction to pre-defined PCC rule activation 15.2.0
2018-12 CT#82 CP-183205 0124 - F Correction to the terminology of QoS notification control 15.2.0
Correction to the general descriptions of Provisioning and 15.2.0
2018-12 CT#82 CP-183205 0125 1 F
Enforcement of Policy Decisions
2018-12 CT#82 CP-183205 0126 3 F Correction to the PCC rule defintion 15.2.0
2018-12 CT#82 CP-183205 0128 1 F Correction to the policy decision data definition 15.2.0
2018-12 CT#82 CP-183205 0129 1 F Correction to the resource URI 15.2.0
2018-12 CT#82 CP-183205 0130 - F Correction to the RuleReport data type 15.2.0
2018-12 CT#82 CP-183205 0131 1 F Delay critical GBR resrouce type 15.2.0
2018-12 CT#82 CP-183205 0132 1 F Correction to the specific data type table 15.2.0
2018-12 CT#82 CP-183205 0133 1 F HTTP custom headers 15.2.0
2018-12 CT#82 CP-183205 0134 1 F Inactivity timer for emergency session 15.2.0
2018-12 CT#82 CP-183205 0135 1 F Provisioning and deletion of the policy decision data 15.2.0
2018-12 CT#82 CP-183205 0136 1 F QoS authorization for the emergency service 15.2.0
2018-12 CT#82 CP-183205 0137 1 F Reference number alignment 15.2.0
2018-12 CT#82 CP-183205 0138 - F Supported content types 15.2.0
2018-12 CT#82 CP-183205 0140 2 F Adding "nullable" property to data types 15.2.0
2018-12 CT#82 CP-183205 0141 2 F VolumeRm data type 15.2.0
2018-12 CT#82 CP-183205 0142 - F Re-use PresenceInfoRm data type 15.2.0
2018-12 CT#82 CP-183205 0143 1 F Re-use PacketLossRateRm data type 15.2.0
2018-12 CT#82 CP-183205 0144 1 F Re-use MaxDataBurstVolRm data type 15.2.0
2018-12 CT#82 CP-183205 0145 - F Re-use DurationSecRm data type 15.2.0
2018-12 CT#82 CP-183205 0146 - F Re-use DateTimeRm data type 15.2.0
2018-12 CT#82 CP-183205 0147 - F Re-use BitRateRm data type 15.2.0
2018-12 CT#82 CP-183205 0148 - F Re-use AverWindowRm data type 15.2.0
2018-12 CT#82 CP-183205 0150 - F Re-use 5QiPriorityLevelRm data type 15.2.0
2018-12 CT#82 CP-183205 0151 - F FlowDirectionRm data type 15.2.0
2018-12 CT#82 CP-183205 0152 1 F Correction to TrafficControlData data type 15.2.0
2018-12 CT#82 CP-183205 0153 1 F Correction to the redirect function 15.2.0
Correction to the modification of an attribute with a value of 15.2.0
2018-12 CT#82 CP-183205 0154 - F
type map
2018-12 CT#82 CP-183205 0155 3 F Correction to SmPolicyDection data type 15.2.0
2018-12 CT#82 CP-183205 0157 1 F Correction to request rule data and requuest usage data 15.2.0
2018-12 CT#82 CP-183205 0158 1 F Correction to QosData data structure 15.2.0
2018-12 CT#82 CP-183205 0159 2 F Correction to Qos Characteristics 15.2.0
2018-12 CT#82 CP-183205 0160 1 F Correction to PccRule data type 15.2.0
2018-12 CT#82 CP-183205 0161 - F Correction to FlowInformation data type 15.2.0
2018-12 CT#82 CP-183205 0162 1 F Correction to ChargingData data type 15.2.0
2018-12 CT#82 CP-183205 0163 - F Correct the minProperties of the attributes 15.2.0
2018-12 CT#82 CP-183205 0164 1 F Correct the minItems of the attributes 15.2.0
2018-12 CT#82 CP-183205 0166 1 F delete UsageMonitoring in pccRule 15.2.0
2018-12 CT#82 CP-183205 0167 - F rename the heading 15.2.0
2018-12 CT#82 CP-183205 0168 - F incorrect description of online and offline 15.2.0
2018-12 CT#82 CP-183205 0169 - F Location header 15.2.0
2018-12 CT#82 CP-183205 0170 1 F API Version Update 15.2.0
2018-12 CT#82 CP-183205 0172 - F Corrections to OpenAPI file 15.2.0
2018-12 CT#82 CP-183205 0173 1 F Corrections of user location and session AMBR attributes 15.2.0
2018-12 CT#82 CP-183205 0174 1 F Common data types 15.2.0
2018-12 CT#82 CP-183205 0176 2 F Presence Info removal 15.2.0
2018-12 CT#82 CP-183205 0177 2 F Correction of SmPolicyUpdateContext data type in OpenAPI 15.2.0
The SMF may allow traffic to start before quota management 15.3.0
2019-03 CT#83 CP-190111 0178 1 F
for online charging
2019-03 CT#83 CP-190111 0179 1 F Correction of application error codes 15.3.0
2019-03 CT#83 CP-190111 0180 - F Corrections to qosDecs attribute 15.3.0
2019-03 CT#83 CP-190111 0182 - F PCF resource cleanup 15.3.0
2019-03 CT#83 CP-190135 0183 1 F Corrections on Traffic Steering Control 15.3.0
2019-03 CT#83 CP-190111 0184 2 F Control of QoS parameters for default QoS Flow 15.3.0
2019-03 CT#83 CP-190157 0185 1 F Correction to UE initiates a resource modification support 15.3.0
3GPP
Release 16 194 3GPP TS 29.512 V16.5.0 (2020-06)
2019-03 CT#83 CP-190136 0186 1 F Completion of the QoS control notification 15.3.0
2019-03 CT#83 CP-190111 0187 1 F Correction to credit management session failure 15.3.0
2019-03 CT#83 CP-190111 0188 1 F Correction to OpenAPI file 15.3.0
2019-03 CT#83 CP-190111 0189 1 F Correction to Provisioning of Default Charging Method 15.3.0
2019-03 CT#83 CP-190111 0191 1 F Correction to the access network information reporting 15.3.0
2019-03 CT#83 CP-190111 0192 - F Correction to the ARP 15.3.0
2019-03 CT#83 CP-190111 0193 1 F Correction to the QoS data decision 15.3.0
Correction to the QoS mapping perfomed by the SMF+PGW- 15.3.0
2019-03 CT#83 CP-190111 0194 2 F
C
2019-03 CT#83 CP-190111 0195 2 F Correction to the SmPolicyDecision data type 15.3.0
Correction to number of supported Packet Filters for 15.3.0
2019-03 CT#83 CP-190111 0197 2 F
signalled QoS rules
2019-03 CT#83 CP-190111 0198 1 F PCC rule enforcement 15.3.0
2019-03 CT#83 CP-190111 0199 2 F Policy Update When UE suspends 15.3.0
2019-03 CT#83 CP-190111 0200 1 F Correction to the QoS characteristics 15.3.0
2019-03 CT#83 CP-190111 0201 1 F Remove two values of failure codes 15.3.0
2019-03 CT#83 CP-190111 0205 1 F Alignment of attributes 15.3.0
2019-03 CT#83 CP-190111 0206 2 F HTTP response code 204 for QoS Notification 15.3.0
2019-03 CT#83 CP-190111 0208 1 F Corrections on Charging Characteristics 15.3.0
2019-03 CT#83 CP-190111 0209 - F Correction on Provisioning of Charging Address 15.3.0
Corrections for Location Change Policy Control Request 15.3.0
2019-03 CT#83 CP-190111 0210 1 F
Triggers
2019-03 CT#83 CP-190111 0211 1 F AC_TY_CH related information 15.3.0
2019-03 CT#83 CP-190111 0212 - F Time Zone Change Policy Control Request Trigger 15.3.0
2019-03 CT#83 CP-190111 0213 - F Corrections on Reflective QoS 15.3.0
2019-03 CT#83 CP-190167 0216 - F OpenAPI version number update 15.3.0
2019-03 CT#83 CP-190121 0203 2 B Access Type conditioned Session-AMBR 16.0.0
Multiple IPV6 prefixes allocated or released in PolicyUpdate 16.0.0
2019-03 CT#83 CP-190121 0207 1 B
request
2019-03 CT#83 CP-190121 0215 - F OpenAPI version number update 16.0.0
2019-06 CT#84 CP-191072 0218 2 A Correction of PCC rule base activation 16.1.0
2019-06 CT#84 CP-191072 0220 1 A Corrections in main body of the specification 16.1.0
2019-06 CT#84 CP-191089 0222 2 B DN Authorization for Policy Control 16.1.0
General description for the support for traffic switching,
2019-06 CT#84 CP-191087 0223 1 B 16.1.0
steering and splitting
Session Rule support for traffic switching, steering and
2019-06 CT#84 CP-191087 0225 1 B 16.1.0
splitting
2019-06 CT#84 CP-191071 0227 3 A Correction to 5GS-EPS interworking support 16.1.0
2019-06 CT#84 CP-191072 0229 1 A Correction to FlowInformation and rule versioning support 16.1.0
2019-06 CT#84 CP-191072 0231 2 A Correction to PacketErrRate data type 16.1.0
2019-06 CT#84 CP-191072 0233 - A Correction to PartialSuccessReport 16.1.0
2019-06 CT#84 CP-191072 0237 2 A Correction to the PCC bound to the default QoS flow 16.1.0
2019-06 CT#84 CP-191072 0241 1 A MBR of Non-GBR type 5QI 16.1.0
2019-06 CT#84 CP-191072 0243 3 A Precedence of PCC rule 16.1.0
2019-06 CT#84 CP-191071 0245 4 A Session Rule error handling 16.1.0
2019-06 CT#84 CP-191072 0247 2 A Usage limitiaion of the time-conditioned PCC rule 16.1.0
2019-06 CT#84 CP-191089 0248 2 B Multiple IPv6 prefixes report for Multi-homing support 16.1.0
2019-06 CT#84 CP-191087 0249 4 B PCC support for traffic switching, steering and splitting 16.1.0
2019-06 CT#84 CP-191072 0254 1 A Miscellaneous corrections 16.1.0
Correction to Npcf_SMPolicyControl_UpdateNotify service
2019-06 CT#84 CP-191072 0256 3 A 16.1.0
operation
Update the redirection server address to support dual stack
2019-06 CT#84 CP-191089 0257 1 F 16.1.0
UE
2019-06 CT#84 CP-191072 0262 - A Precedence of OpenAPI file 16.1.0
2019-06 CT#84 CP-191072 0263 1 A Deprecating API version 16.1.0
2019-06 CT#84 CP-191071 0264 2 B AF acknowledgement to be expected 16.1.0
2019-06 CT#84 CP-191071 0265 2 B UE IP address preservation indication 16.1.0
2019-06 CT#84 CP-191072 0269 1 A Corrections to conditioned PCC rule 16.1.0
2019-06 CT#84 CP-191089 0273 2 F Correction to IPv6 Multihoming support 16.1.0
2019-06 CT#84 CP-191072 0275 - A Correction of RuleReport type 16.1.0
2019-06 CT#84 CP-191072 0283 1 A Correction to access network information report 16.1.0
2019-06 CT#84 CP-191072 0285 1 A Correction to FailureCode data type 16.1.0
2019-06 CT#84 CP-191072 0291 1 A Correction to UE_STATUS_RESUME 16.1.0
2019-06 CT#84 CP-191089 0293 1 B Race condition handling 16.1.0
2019-06 CT#84 CP-191085 0294 1 B Npcf_SMPolicyControl service extention of 5WWC 16.1.0
2019-06 CT#84 CP-191072 0296 1 F Copyright Note in YAML file 16.1.0
2019-06 CT#84 CP-191101 0298 1 F API version update 16.1.0
2019-09 CT#85 CP-192167 0302 1 B Handling of requests colliding with an existing context 16.2.0
2019-09 CT#85 CP-192178 0303 1 B Adding NID as input for policy decisions 16.2.0
2019-09 CT#85 CP-192156 0304 1 B Support a set of MAC addresses in traffic filter 16.2.0
2019-09 CT#85 CP-192155 0305 1 B Support of IMS restoration 16.2.0
2019-09 CT#85 CP-192155 0306 1 B Support of Npcf_PolicyAuthorization invocation of priority 16.2.0
3GPP
Release 16 195 3GPP TS 29.512 V16.5.0 (2020-06)
sharing
2019-09 CT#85 CP-192142 0308 2 A Correction to Resource Sharing 16.2.0
2019-09 CT#85 CP-192176 0311 1 B Support of wireline and wireless access convergence, NFs 16.2.0
2019-09 CT#85 CP-192142 0313 - A Correction to appReloc attribute 16.2.0
2019-09 CT#85 CP-192142 0315 1 A Correction to GBR type default QoS flow 16.2.0
2019-09 CT#85 CP-192142 0317 1 A Correction to interworking between the 5GC and EPC 16.2.0
2019-09 CT#85 CP-192142 0319 2 A Correction to serving node change 16.2.0
2019-09 CT#85 CP-192142 0323 1 A Correction to UE requested resource modification 16.2.0
Include ipDomain within SmPolicyUpdateContextData data
2019-09 CT#85 CP-192142 0325 - A type 16.2.0
2019-09 CT#85 CP-192142 0327 1 A Correction to Usage Monitoring Control 16.2.0
2019-09 CT#85 CP-192142 0329 1 A Packet filters for reflective QoS 16.2.0
2019-09 CT#85 CP-192153 0330 - B PCC rule attribute correction for ATSSS 16.2.0
2019-09 CT#85 CP-192156 0331 - B Correction to time conditioned PCC rule 16.2.0
Npcf_SMPolicyControl_Create Service Operation Update of
2019-09 CT#85 CP-192152 0333 1 B 5WWCCorrection to time conditioned PCC rule 16.2.0
Npcf_SMPolicyControl_UpdateNotify Service Operation
2019-09 CT#85 CP-192152 0334 1 B Update of 5WWC 16.2.0
Npcf_SMPolicyControl_Update Service Operation Update of
2019-09 CT#85 CP-192152 0335 1 B 5WWC 16.2.0
Npcf_SMPolicyControl_Delete Service Operation Update of
2019-09 CT#85 CP-192152 0336 1 B 5WWC 16.2.0
2019-09 CT#85 CP-192152 0337 2 B IPTV support 16.2.0
2019-09 CT#85 CP-192175 0338 2 B QoS Monitoring support for URLLC 16.2.0
2019-09 CT#85 CP-192171 0339 2 B PCC rule decision enhancement for supporting xBDT 16.2.0
2019-09 CT#85 CP-192173 0341 - B OpenAPI version update TS 29.512 R-16 16.2.0
2019-12 CT#86 CP-193213 0345 2 F Increasing the maximum MDBV value 16.3.0
2019-12 CT#86 CP-193181 0346 1 B Open issue for AddrPreservation feature 16.3.0
2019-12 CT#86 CP-193184 0349 1 A Correction to the usage monitoring control 16.3.0
2019-12 CT#86 CP-193184 0351 2 A Correction to the traffic steering control 16.3.0
2019-12 CT#86 CP-193193 0352 2 B Usage Monitoring Control for ATSSS 16.3.0
Correction to handling of requests colliding with an existing
2019-12 CT#86 CP-193210 0353 1 B context 16.3.0
2019-12 CT#86 CP-193223 0354 1 B Multiple BDT Policies 16.3.0
2019-12 CT#86 CP-193223 0355 5 B New cause value of association termination for xBDT 16.3.0
2019-12 CT#86 CP-193202 0356 6 B QoS Handling for V2X Communication 16.3.0
2019-12 CT#86 CP-193197 0358 4 B Serving 4G only UEs by SMF+PGW-C 16.3.0
2019-12 CT#86 CP-193196 0359 - B Add reference of 29.514 16.3.0
2019-12 CT#86 CP-193181 0360 1 B Report frequency of QoS monitoring 16.3.0
2019-12 CT#86 CP-193236 0361 2 B Line Identifier 16.3.0
2019-12 CT#86 CP-193193 0364 2 B remove EN related to SteeringFunctionality datatype 16.3.0
2019-12 CT#86 CP-193197 0366 - F Correct the Cardinality of redirectInfo 16.3.0
2019-12 CT#86 CP-193223 0367 1 D Background data transfer support editorials 16.3.0
Transport of TSN information and containers between SMF
2019-12 CT#86 CP-193222 0368 2 B and PCF 16.3.0
Transport of TSC assistance information between SMF and
2019-12 CT#86 CP-193222 0369 2 B PCF 16.3.0
2019-12 CT#86 CP-193184 0371 - A CHF addresses as apiRoot in the form of an FQDN 16.3.0
Indication of PS to CS Handover for 5G SRVCC from SMF to
2019-12 CT#86 CP-193259 0372 4 B PCF 16.3.0
2019-12 CT#86 CP-193215 0373 2 B Coverage and Handover Enhancements for Media (CHEM) 16.3.0
2019-12 CT#86 CP-193197 0374 1 B MCS Priority Level 16.3.0
2019-12 CT#86 CP-193197 0375 1 F Removal of non-breaking spaces, TABs and $ref descriptions 16.3.0
Request of SM Policy Association Termination during the
2019-12 CT#86 CP-193197 0377 2 B Update procedur 16.3.0
2019-12 CT#86 CP-193184 0379 - A Correction to delete a PCC rule requested by the UE 16.3.0
2019-12 CT#86 CP-193184 0381 - A Termination action 16.3.0
2019-12 CT#86 CP-193233 0382 1 B AMF change in the HR scenario 16.3.0
Same PCF selection for the same UE ID, S-NSSAI and DNN
2019-12 CT#86 CP-193197 0383 2 B combination 16.3.0
2019-12 CT#86 CP-193238 0384 2 B Correction to the QoS monitoring Control 16.3.0
2019-12 CT#86 CP-193212 0385 - F Update of API version and TS version in OpenAPI file 16.3.0
Correct the redirection server address to support dual stack
2019-12 CT#86 CP-193197 0386 - F UE 16.3.0
2019-12 CT#86 CP-193184 0388 1 A Correction of AF Charging Identifier data type 16.3.0
2019-12 CT#86 CP-193191 0389 2 B Clarification of PEI format, TS 29.512 16.3.0
2019-12 CT#86 CP-193230 0390 2 B HFC node Id in Location information, TS 29.512 16.3.0
2019-12 CT#86 CP-193197 0393 1 B Add reference to TS 29.524 16.3.0
2020-03 CT#87e CP-200207 0402 1 B Update of the same PCF selection 16.4.0
2020-03 CT#87e CP-200207 0403 - B DNN Clarification 16.4.0
2020-03 CT#87e CP-200207 0404 1 B Cell change trigger 16.4.0
2020-03 CT#87e CP-200207 0405 1 B Correction to the policy decision data and condition 16.4.0
3GPP
Release 16 196 3GPP TS 29.512 V16.5.0 (2020-06)
data
2020-03 CT#87e CP-200207 0406 1 B Reallocation of credit 16.4.0
2020-03 CT#87e CP-200207 0407 1 B UE initiated resource modification correction 16.4.0
2020-03 CT#87e CP-200204 0408 2 B Complete the PCC procedure for ATSSS 16.4.0
2020-03 CT#87e CP-200203 0410 1 B Complete the IPTV support 16.4.0
2020-03 CT#87e CP-200203 0411 1 B Policy Control Request Triggers for wireline access 16.4.0
2020-03 CT#87e CP-200203 0412 1 B The data type of GlobalLineId 16.4.0
2020-03 CT#87e CP-200212 0414 1 B Complete the PCC procedure for V2XARC 16.4.0
2020-03 CT#87e CP-200202 0415 1 B Complete the QoS Monitoring 16.4.0
2020-03 CT#87e CP-200218 0416 1 B Indication of traffic correlation 16.4.0
2020-03 CT#87e CP-200207 0417 1 B DNN selection mode 16.4.0
2020-03 CT#87e CP-200204 0419 2 B interwoking with EPS for ATSSS 16.4.0
2020-03 CT#87e CP-200285 0420 3 B Additional Access Type for ATSSS 16.4.0
2020-03 CT#87e CP-200231 0423 1 B Report of EPS Fallback 16.4.0
2020-03 CT#87e CP-200226 0424 1 B Clarification of DS-TT and NW-TT ports identification 16.4.0
Clarification of DS-TT and NW-TT ports management
2020-03 CT#87e CP-200226 0425 1 B information 16.4.0
PCF provisioning of TSN related Policy Control Request
2020-03 CT#87e CP-200218 0426 - B triggers 16.4.0
2020-03 CT#87e CP-200218 0427 1 B TSCAI input container and TSN QoS container 16.4.0
2020-03 CT#87e CP-200214 0428 - F OpenAPI: usage of the "tags" keyword 16.4.0
2020-03 CT#87e CP-200214 0429 - F Enumerations and "nullable" keyword 16.4.0
2020-03 CT#87e CP-200215 0430 - F Referencing enumerations in clause 5.6.1 16.4.0
2020-03 CT#87e CP-200200 0431 - B CHF set and instance Id in charging information 16.4.0
29.512 Rel-16 Update of OpenAPI version and TS version in
2020-03 CT#87e CP-200216 0435 - F externalDocs field 16.4.0
2020-06 CT#88e CP-201217 0437 1 A Correction to attributes interGrpIds and appDetectionInfos 16.5.0
2020-06 CT#88e CP-201238 0438 - F Correction to V2XARC 16.5.0
2020-06 CT#88e CP-201217 0440 - A String format of flow information 16.5.0
2020-06 CT#88e CP-201217 0444 1 A Notification URI 16.5.0
2020-06 CT#88e CP-201233 0445 1 B Cause Mapping of VALIDATION_CONDITION_NOT_MET 16.5.0
2020-06 CT#88e CP-201229 0446 - B ATSSS rule derivation 16.5.0
2020-06 CT#88e CP-201229 0447 3 B QoS support for ATSSS 16.5.0
2020-06 CT#88e CP-201229 0448 1 B Enable removing the policy decision 16.5.0
2020-06 CT#88e CP-201252 0449 2 F Correction to bridge Information report 16.5.0
Correction to Port Management Information Container
2020-06 CT#88e CP-201252 0450 2 F exchange 16.5.0
Correction to Provisioning of TSCAI input information and
2020-06 CT#88e CP-201271 0451 2 F TSC QoS related data 16.5.0
2020-06 CT#88e CP-201252 0452 1 B PCC rule information update for vertical 16.5.0
2020-06 CT#88e CP-201252 0453 1 B PCF functionality update for TSN 16.5.0
2020-06 CT#88e CP-201228 0454 - B General update of Annex C 16.5.0
2020-06 CT#88e CP-201262 0455 3 B Support of full Frame Routing feature 16.5.0
2020-06 CT#88e CP-201228 0456 1 B The data type of GlobalLineId 16.5.0
2020-06 CT#88e CP-201338 0457 3 B Procedure of policy provisioning of QoS monitoring control 16.5.0
2020-06 CT#88e CP-201213 0458 1 F QoS Monitoring Control Data correction 16.5.0
2020-06 CT#88e CP-201217 0463 1 A timeUsage in Accumulated Usage Report 16.5.0
2020-06 CT#88e CP-201229 0464 - F Support the update of SteeringFunctionality 16.5.0
2020-06 CT#88e CP-201228 0465 - B Not to support Mission Critical Services 16.5.0
2020-06 CT#88e CP-201228 0468 - F Removal of MAC address 16.5.0
2020-06 CT#88e CP-201244 0470 - F Removal of unbreakable space and TAB 16.5.0
2020-06 CT#88e CP-201213 0471 1 B Solving Editor’s note on UL CL 16.5.0
2020-06 CT#88e CP-201228 0472 1 B Hybrid Access Support 16.5.0
2020-06 CT#88e CP-201228 0473 1 B Untrusted PEI 16.5.0
2020-06 CT#88e CP-201228 0474 1 B RAT type for WWC 16.5.0
2020-06 CT#88e CP-201229 0475 1 B PS Data Off for a MA PDU session 16.5.0
2020-06 CT#88e CP-201233 0476 1 F Correction to Reallocation of Credit 16.5.0
2020-06 CT#88e CP-201233 0477 1 B Local traffic routing policy 16.5.0
2020-06 CT#88e CP-201238 0478 1 F Referencing alternative QoS in clause 4.2.6.2.1 16.5.0
2020-06 CT#88e CP-201252 0479 1 B QoS information for Time Sensitive Networking 16.5.0
2020-06 CT#88e CP-201252 0480 1 B Update of TSN related PCRTs 16.5.0
2020-06 CT#88e CP-201252 0481 1 B Completion of traffic correlation 16.5.0
2020-06 CT#88e CP-201217 0482 1 A Correction to NetLoc feature 16.5.0
2020-06 CT#88e CP-201217 0484 1 A Correction to PS Data Off 16.5.0
2020-06 CT#88e CP-201213 0486 1 F Correct data type used in QoS monitoring 16.5.0
2020-06 CT#88e CP-201244 0487 1 F Storage of YAML files in ETSI Forge 16.5.0
2020-06 CT#88e CP-201257 0489 1 B DDN Failure and Delivery Policy Control Request triggers 16.5.0
2020-06 CT#88e CP-201272 0490 1 B Introduction of Bridge management information 16.5.0
Clarification of PCF behaviour to honor UE provided
2020-06 CT#88e CP-201267 0491 1 B maximum packet filter support 16.5.0
2020-06 CT#88e CP-201233 0492 1 B Policy decision and condition data status report 16.5.0
3GPP
Release 16 197 3GPP TS 29.512 V16.5.0 (2020-06)
2020-06 CT#88e CP-201263 0494 1 B New value of the ATSSS capability 16.5.0
2020-06 CT#88e CP-201264 0495 1 B PCC rule for Non-MPTCP traffic 16.5.0
2020-06 CT#88e CP-201265 0496 1 B Steering modes for GBR traffic 16.5.0
2020-06 CT#88e CP-201252 0499 1 B Correct the reference of the port management info container 16.5.0
2020-06 CT#88e CP-201256 0501 1 F URI of the Npcf_SMPolicyControl service 16.5.0
2020-06 CT#88e CP-201233 0503 1 F Correction to the usage of appReloc attribute 16.5.0
2020-06 CT#88e CP-201217 0505 1 A Correction to session rule error report 16.5.0
2020-06 CT#88e CP-201297 0506 2 B Clarification on the target of QoS Monitoring report 16.5.0
2020-06 CT#88e CP-201213 0507 1 F Correction to attributes related to QosMonitoring 16.5.0
2020-06 CT#88e CP-201229 0508 - F Clarification on the value of 3gLoad attribute 16.5.0
2020-06 CT#88e CP-201266 0511 1 B Application Id in a PCC rule for ATSSS 16.5.0
2020-06 CT#88e CP-201273 0513 1 B QoS parameter mapping 16.5.0
2020-06 CT#88e CP-201217 0517 1 A Not supporting simultaneous online and offline charging 16.5.0
2020-06 CT#88e CP-201244 0518 - F Optionality of ProblemDetails 16.5.0
2020-06 CT#88e CP-201232 0519 - F "PCSCF-Restoration-Enhancement" feature corrections 16.5.0
Supported headers, Resource Data type, Operation Name
2020-06 CT#88e CP-201244 0520 1 F and yaml mapping 16.5.0
2020-06 CT#88e CP-201247 0522 - F Reallocation of credit reporting to the PCF 16.5.0
Update of OpenAPI version and TS version in externalDocs
2020-06 CT#88e CP-201255 0524 - F field 16.5.0
2020-06 CT#88e CP-201282 0525 - F Correcting feature numbers 16.5.0
3GPP

SM PCF Jul2020

Uploaded by

Copyright:

Available Formats

SM PCF Jul2020

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SM PCF Jul2020

Uploaded by

Copyright:

Available Formats

3GPP TS 29.512 V16.5.

3rd Generation Partnership Project;

3GPP support office address

No part may be reproduced except as authorized by written permission.

4.2.2.19 Detection of TSN related SM Policy Association ................................................................................ 33

4.2.5.4 Report Access Network Information .................................................................................................... 58

5.2.2.2 Content type.......................................................................................................................................... 87

5.6.2.26 Type UeCampingRep ......................................................................................................................... 120

Annex A (normative): OpenAPI specification ................................................................................. 148

C.3.3.2 IPTV service support................................................................................................................................ 187

Annex D(informative): Change history ............................................................................................. 191

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.

Stage 3 call flows are provided in 3GPP TS 29.513 [7].

- For a specific reference, subsequent revisions do not apply.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".

[8] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".

[10] OpenAPI: "OpenAPI 3.0.0 Specification", https://github.com/OAI/OpenAPI-

[16] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2".

[19] 3GPP TS 32.291: "5G System; Charging service; Stage 3".

[21] 3GPP TS 23.380: "IMS Restoration Procedures".

[27] 3GPP TS 33.501: "Security architecture and procedures for 5G system".

[28] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".

[29] 3GPP TS 29.510: "Network Function Repository Services; Stage 3".

[31] IETF RFC 7807: "Problem Details for HTTP APIs".

[32] 3GPP TS 29.122: "T8 reference point for Northbound APIs".

[33] 3GPP TS 23.527: "5G System; Restoration Procedures".

[38] 3GPP TR 21.900: "Technical Specification Group working methods".

[41] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification".

[45] IEEE 802.1Q: "Virtual Bridged Local Area Networks".

3 Definitions, symbols and abbreviations

Access Traffic Steering

Access Traffic Switching

Access Traffic Splitting

Service Data Flow

Service Data Flow Filter

Service Data Flow Template

5G-RG 5G Residential Gateway

NID Network Identifier

4.1 Service Description

4.1.2 Service Architecture

The only known NF Service Consumer is the SMF.

4.1.3 Network Functions

4.1.3.1 Policy Control Function (PCF)

- Information obtained from the UDR;

- Information obtained from the SMF;

- Information obtained from the NWDAF;

- Information obtained from the NEF;

- information from CHF; and

- PCF pre-configured policy context.

4.1.3.2 NF Service Consumers

The SMF shall support:

- sending the PDU session related attributes to the PCF;

- requesting and receiving the PCC rule(s) from the PCF;

- deriving the QoS rules towards the UE;

- deriving the QoS profile towards the access network;