3rd Generation Partnership Project;

Technical Specification Group Services and System Aspects;

3GPP TS 32.299
TelecommunicationV15.4.0 (2018-09)
management;
Charging management;
Technical Specification

Diameter charging applications

(Release 15)

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 15 2 3GPP TS 32.299 V15.4.0 (2018-09)

Keywords
charging, management, protocol, Diameter

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.

© 2018, 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 15 3 3GPP TS 32.299 V15.4.0 (2018-09)

Contents
Foreword........................................................................................................................................................13
1 Scope....................................................................................................................................................14
2 References............................................................................................................................................15
3 Definitions, symbols and abbreviations................................................................................................17
3.1 Definitions.........................................................................................................................................................17
3.2 Symbols.............................................................................................................................................................18
3.3 Abbreviations.....................................................................................................................................................18
4 Architecture considerations..................................................................................................................20
4.1 High level architecture.......................................................................................................................................20
4.1.0 General.........................................................................................................................................................20
4.1.1 Charging related transfer requirements........................................................................................................21
5 3GPP charging applications requirements............................................................................................22
5.1 Offline charging scenarios.................................................................................................................................22
5.1.1 Basic principles............................................................................................................................................22
5.1.1.0 Introduction............................................................................................................................................22
5.1.1.1 Event based charging..............................................................................................................................23
5.1.1.2 Session based charging...........................................................................................................................24
5.1.2 Basic operation.............................................................................................................................................26
5.2 Online charging scenarios..................................................................................................................................27
5.2.0 Introduction..................................................................................................................................................27
5.2.1 Basic principles............................................................................................................................................27
5.2.2 Charging scenarios.......................................................................................................................................28
5.2.2.0 Introduction............................................................................................................................................28
5.2.2.1 Immediate Event Charging (IEC)...........................................................................................................29
5.2.2.1.1 Decentralized Unit Determination and Centralized Rating..............................................................29
5.2.2.1.2 Centralized Unit Determination and Centralized Rating..................................................................31
5.2.2.1.3 Decentralized Unit Determination and Decentralized Rating..........................................................33
5.2.2.1.4 Further options..................................................................................................................................34
5.2.2.2 Event Charging with Unit Reservation (ECUR)....................................................................................35
5.2.2.2.1 Decentralized Unit Determination and Centralized Rating..............................................................35
5.2.2.2.2 Centralized Unit Determination and Centralized Rating..................................................................37
5.2.2.2.3 Decentralized Unit Determination and Decentralized Rating..........................................................39
5.2.2.3 Session charging with Reservation.........................................................................................................41
5.2.2.3.1 Decentralized Unit Determination and Centralized Rating..............................................................41
5.2.2.3.2 Centralized Unit Determination and Centralized Rating..................................................................43
5.2.2.3.3 Decentralized Unit Determination and Decentralized Rating..........................................................45
5.2.3 Basic operations...........................................................................................................................................47
5.3 Other requirements............................................................................................................................................50
5.3.1 Re-authorization...........................................................................................................................................50
5.3.2 Threshold based re-authorization triggers....................................................................................................50
5.3.3 Termination action.......................................................................................................................................50
5.3.4 Account expiration.......................................................................................................................................50
6 3GPP charging applications – Protocol aspects....................................................................................51
6.1 Basic principles for Diameter offline charging..................................................................................................51
6.1.0 Introduction..................................................................................................................................................51
6.1.1 Event based charging...................................................................................................................................52
6.1.2 Session based charging................................................................................................................................53
6.1.3 Offline charging error cases - Diameter procedures....................................................................................55
6.1.3.1 CDF connection failure..........................................................................................................................55
6.1.3.2 No reply from CDF................................................................................................................................55
6.1.3.3 Duplicate detection.................................................................................................................................55
6.1.3.4 CDF detected failure..............................................................................................................................55
6.2 Message contents for offline charging...............................................................................................................56

3GPP
Release 15 4 3GPP TS 32.299 V15.4.0 (2018-09)

6.2.1 Summary of offline charging message formats...........................................................................................56

6.2.1.1 General...................................................................................................................................................56
6.2.1.2 Structure for the Accounting message formats......................................................................................56
6.2.2 Accounting-Request message......................................................................................................................57
6.2.3 Accounting-Answer (ACA) message..........................................................................................................59
6.3 Basic principles for Diameter online charging..................................................................................................61
6.3.1 Online Specific Credit-Control application requirements...........................................................................61
6.3.2 Diameter description on the Ro reference point..........................................................................................61
6.3.2.1 Basic principles......................................................................................................................................61
6.3.3 Immediate Event Charging (IEC)................................................................................................................62
6.3.4 Event Charging with Unit Reservation (ECUR)..........................................................................................64
6.3.5 Session Charging with Unit Reservation (SCUR).......................................................................................66
6.3.6 Error cases and scenarios.............................................................................................................................68
6.3.6.0 Introduction............................................................................................................................................68
6.3.6.1 Duplicate detection.................................................................................................................................68
6.3.6.2 Reserve Units / Debit Units operation failure........................................................................................68
6.3.7 Support of tariff changes during an active user session...............................................................................68
6.3.7.1 Support of tariff changes using the tariff switch mechanism.................................................................68
6.3.7.2 Support of tariff changes using Validity-Time AVP...............................................................................68
6.3.8 Support of re-authorization..........................................................................................................................69
6.3.9 Support of failure handling..........................................................................................................................69
6.3.10 Support of failover.......................................................................................................................................69
6.3.11 Credit pooling..............................................................................................................................................69
6.4 Message formats for online charging................................................................................................................70
6.4.1 Summary of online charging message formats............................................................................................70
6.4.1.1 General...................................................................................................................................................70
6.4.1.2 Structure for the Credit-Control message formats.................................................................................70
6.4.2 Credit-Control-Request message.................................................................................................................71
6.4.3 Credit-Control-Answer message..................................................................................................................76
6.4.4 Re-Auth-Request message...........................................................................................................................81
6.4.5 Re-Auth-Answer message...........................................................................................................................82
6.4.6 Capabilities-Exchange-Request message.....................................................................................................82
6.4.7 Capabilities-Exchange-Answer message.....................................................................................................83
6.4.8 Device-Watchdog-Request message............................................................................................................83
6.4.9 Device-Watchdog-Answer message............................................................................................................83
6.4.10 Disconnect-Peer-Request message..............................................................................................................83
6.4.11 Disconnect-Peer-Answer message...............................................................................................................83
6.4.12 Abort-Session-Request message..................................................................................................................83
6.4.13 Abort-Session -Answer message.................................................................................................................83
6.5 Other procedural description of the 3GPP charging applications......................................................................84
6.5.1 Re-Authorization..........................................................................................................................................84
6.5.1.1 Idle timeout............................................................................................................................................84
6.5.1.2 Change of charging conditions...............................................................................................................84
6.5.1.3 Reporting quota usage............................................................................................................................84
6.5.1.4 Quota consumption................................................................................................................................85
6.5.2 Threshold based Re-Authorization triggers.................................................................................................85
6.5.3 Termination action.......................................................................................................................................85
6.5.4 Quota consumption time..............................................................................................................................86
6.5.5 Service termination......................................................................................................................................86
6.5.6 Envelope reporting.......................................................................................................................................86
6.5.6.1 Envelope reporting in Online Charging.................................................................................................86
6.5.6.2 Envelope reporting in Offline Charging.................................................................................................86
6.5.6.3 Envelope reporting - Quota consumption time......................................................................................87
6.5.6.4 Envelope reporting - Combinational quota............................................................................................87
6.5.7 Combinational quota....................................................................................................................................88
6.5.8 Online control of offline charging information............................................................................................88
6.5.9 Support of multiple service..........................................................................................................................88
6.5.10 Supported Features mechanism...................................................................................................................88
6.5.10.1 Introduction............................................................................................................................................88
6.5.10.2 Defining a feature...................................................................................................................................88
6.5.10.3 Supported Feature handling...................................................................................................................89

3GPP
Release 15 5 3GPP TS 32.299 V15.4.0 (2018-09)

6.6 Bindings of the operation to protocol application.............................................................................................90

6.6.0 General.........................................................................................................................................................90
6.6.1 Bindings of Charging Data Transfer to Accounting.....................................................................................90
6.6.2 Bindings of Debit / Reserve Units to Credit-Control...................................................................................91
6.7 Securing Diameter messages.............................................................................................................................91
7 Summary of used Attribute Value Pairs................................................................................................92
7.1 Diameter AVPs...................................................................................................................................................92
7.1.0 General.........................................................................................................................................................92
7.1.1 Accounting-Input-Octets AVP.....................................................................................................................93
7.1.2 Void..............................................................................................................................................................94
7.1.3 Accounting-Output-Octets AVP...................................................................................................................94
7.1.4 Void..............................................................................................................................................................94
7.1.5 Acct-Application-Id AVP.............................................................................................................................94
7.1.6 Auth-Application-Id AVP............................................................................................................................94
7.1.7 Called-Station-Id AVP..................................................................................................................................94
7.1.8 Event-Timestamp AVP.................................................................................................................................94
7.1.8A Experimental-Result AVP............................................................................................................................94
7.1.9 Multiple-Services-Credit-Control AVP........................................................................................................94
7.1.10 Rating-Group AVP.......................................................................................................................................95
7.1.11 Result-Code AVP.........................................................................................................................................95
7.1.12 Service-Context-Id AVP...............................................................................................................................96
7.1.13 Service-Identifier AVP.................................................................................................................................96
7.1.14 Used-Service-Unit AVP...............................................................................................................................96
7.1.15 User-Name AVP...........................................................................................................................................97
7.1.16 Vendor-Id AVP.............................................................................................................................................97
7.1.17 User-Equipment-Info AVP...........................................................................................................................97
7.2 3GPP specific AVPs...........................................................................................................................................98
7.2.0 General.........................................................................................................................................................98
7.2.0A Access-Network-Info-Change AVP...........................................................................................................107
7.2.0aA 3GPP-PS-Data-Off-Status AVP.................................................................................................................107
7.2.1 Access-Network-Information AVP............................................................................................................107
7.2.1A Access-Transfer-Information AVP.............................................................................................................107
7.2.1B Access-Transfer-Type AVP........................................................................................................................108
7.2.2 Account-Expiration AVP............................................................................................................................108
7.2.3 Accumulated-Cost AVP.............................................................................................................................108
7.2.4 Adaptations AVP........................................................................................................................................108
7.2.5 Additional-Content-Information AVP........................................................................................................108
7.2.5A Additional-Exception-Reports AVP...........................................................................................................109
7.2.6 Additional-Type-Information AVP.............................................................................................................109
7.2.7 Address-Data AVP.....................................................................................................................................109
7.2.8 Address-Domain AVP................................................................................................................................109
7.2.9 Address-Type AVP.....................................................................................................................................109
7.2.10 Addressee-Type AVP.................................................................................................................................109
7.2.11 AF-Correlation-Information AVP..............................................................................................................109
7.2.12 Alternate-Charged-Party-Address AVP......................................................................................................110
7.2.12aA Announcement-Identifier AVP...................................................................................................................110
7.2.12aB Announcement-Information AVP...............................................................................................................110
7.2.12aC Announcement-Order AVP........................................................................................................................110
7.2.12aD Announcing-PLMN-ID AVP......................................................................................................................110
7.2.12A Announcing-UE-HPLMN-Identifier AVP.................................................................................................110
7.2.12B Announcing-UE-VPLMN-Identifier AVP..................................................................................................111
7.2.13 AoC-Cost-Information AVP.......................................................................................................................111
7.2.14 AoC-Format AVP.......................................................................................................................................111
7.2.15 AoC-Information AVP................................................................................................................................111
7.2.16 AoC-Request-Type AVP.............................................................................................................................111
7.2.17 AoC-Service AVP.......................................................................................................................................111
7.2.18 AoC-Service-Obligatory-Type AVP...........................................................................................................112
7.2.19 AoC-Service-Type AVP.............................................................................................................................113
7.2.20 AoC-Subscription-Information AVP..........................................................................................................113
7.2.20aA API-Content AVP.......................................................................................................................................113
7.2.20bA API-Direction AVP.....................................................................................................................................113

3GPP
Release 15 6 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.20cA API-Identifier AVP.....................................................................................................................................113

7.2.20dA API-Invocation-Timestamp AVP...............................................................................................................113
7.2.20eA API-Network-Service-Node AVP..............................................................................................................113
7.2.20fA API-Result-Code AVP................................................................................................................................113
7.2.20gA API-Size AVP.............................................................................................................................................113
7.2.20A APN-Rate-Control AVP...........................................................................................................................114
7.2.20B APN-Rate-Control-Downlink AVP..........................................................................................................114
7.2.20C APN-Rate-Control-Uplink AVP...............................................................................................................114
7.2.21 Applic-ID AVP...........................................................................................................................................114
7.2.22 Application-Provided-Called-Party-Address AVP.....................................................................................114
7.2.23 Application-Server AVP.............................................................................................................................115
7.2.24 Application-Server-Information AVP........................................................................................................115
7.2.24A Application-Specific-Data AVP.................................................................................................................115
7.2.25 Associated-Party-Address AVP..................................................................................................................116
7.2.26 Associated-URI AVP..................................................................................................................................116
7.2.27 Authorised-QoS AVP.................................................................................................................................116
7.2.28 Aux-Applic-Info AVP................................................................................................................................116
7.2.29 Base-Time-Interval AVP............................................................................................................................116
7.2.29A Basic-Service-Code AVP...........................................................................................................................116
7.2.29B Bearer-Capability AVP...............................................................................................................................116
7.2.30 Bearer-Service AVP....................................................................................................................................116
7.2.30A BSSID AVP................................................................................................................................................116
7.2.31 Called-Asserted-Identity AVP....................................................................................................................117
7.2.31A Called-Identity AVP...................................................................................................................................117
7.2.31B Called-Identity-Change AVP......................................................................................................................117
7.2.32 Called-Party-Address AVP.........................................................................................................................117
7.2.33 Calling-Party-Address AVP.......................................................................................................................117
7.2.34 Carrier-Select-Routing-Information AVP..................................................................................................118
7.2.35 Cause-Code AVP........................................................................................................................................119
7.2.35A Cellular-Network-Information AVP...........................................................................................................120
7.2.35B Civic-Address-Information AVP................................................................................................................120
7.2.36 CG-Address AVP.......................................................................................................................................120
7.2.37 Change-Condition AVP..............................................................................................................................120
7.2.38 Change-Time AVP.....................................................................................................................................121
7.2.38A Charge-Reason-Code AVP.........................................................................................................................121
7.2.39 Charged-Party AVP....................................................................................................................................122
7.2.39A Charging-Characteristics-Selection-Mode AVP.........................................................................................122
7.2.39B Charging-Per-IP-CAN-Session-Indicator AVP..........................................................................................122
7.2.40 Class-Identifier AVP..................................................................................................................................122
7.2.41 Client-Address AVP...................................................................................................................................122
7.2.41A CN-Operator-Selection-Entity AVP...........................................................................................................122
7.2.42 Content-Class AVP.....................................................................................................................................123
7.2.43 Content-Disposition AVP...........................................................................................................................123
7.2.44 Content-Length AVP..................................................................................................................................123
7.2.45 Content-Size AVP......................................................................................................................................123
7.2.46 Content-Type AVP.....................................................................................................................................123
7.2.46aA Coverage-Status AVP.................................................................................................................................123
7.2.46aaA Coverage-Info AVP....................................................................................................................................123
7.2.46abA CP-CIoT-EPS-Optimisation-Indicator AVP...............................................................................................124
7.2.46acA CPDT-Information AVP.............................................................................................................................124
7.2.46A CSG-Access-Mode AVP............................................................................................................................124
7.2.46B CSG-Membership-Indication AVP............................................................................................................124
7.2.47 Current-Tariff AVP.....................................................................................................................................125
7.2.48 CUG-Information AVP..............................................................................................................................125
7.2.49 Data-Coding-Scheme AVP.........................................................................................................................125
7.2.50 DCD-Information AVP..............................................................................................................................125
7.2.51 Deferred-Location-Event-Type AVP..........................................................................................................125
7.2.52 Delivery-Report-Requested AVP...............................................................................................................125
7.2.53 Destination-Interface AVP.........................................................................................................................125
7.2.54 Diagnostics AVP........................................................................................................................................126
7.2.54A Discoveree-UE-HPLMN-Identifier AVP...................................................................................................126

3GPP
Release 15 7 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.54B Discoveree-UE-VPLMN-Identifier AVP...................................................................................................126

7.2.54C Discoverer-UE-HPLMN-Identifier AVP....................................................................................................126
7.2.54D Discoverer-UE-VPLMN-Identifier AVP....................................................................................................126
7.2.55 Domain-Name AVP....................................................................................................................................126
7.2.56 DRM-Content AVP....................................................................................................................................126
7.2.57 Dynamic-Address-Flag AVP......................................................................................................................126
7.2.57A Dynamic-Address-Flag-Extension AVP....................................................................................................126
7.2.58 Early-Media-Description AVP...................................................................................................................127
7.2.58A Enhanced-Diagnostics AVP.......................................................................................................................127
7.2.59 Envelope AVP............................................................................................................................................127
7.2.60 Envelope-End-Time AVP...........................................................................................................................128
7.2.61 Envelope-Reporting AVP...........................................................................................................................129
7.2.62 Envelope-Start-Time AVP..........................................................................................................................129
7.2.62A EPDG-Address AVP................................................................................................................................129
7.2.63 Event AVP..................................................................................................................................................129
7.2.64 Event-Charging-TimeStamp AVP..............................................................................................................129
7.2.65 Event-Type AVP.........................................................................................................................................129
7.2.66 Expires AVP...............................................................................................................................................129
7.2.66A FE-Identifier-List AVP...............................................................................................................................129
7.2.66aA Exposure-Function-API-Information AVP................................................................................................130
7.2.67 File-Repair-Supported AVP.......................................................................................................................131
7.2.67aA Forwarding-Pending AVP..........................................................................................................................131
7.2.67A From-Address AVP....................................................................................................................................131
7.2.68 GGSN-Address AVP..................................................................................................................................131
7.2.69 IM-Information AVP..................................................................................................................................131
7.2.70 Incremental-Cost AVP................................................................................................................................131
7.2.70A Instance-Id AVP.........................................................................................................................................131
7.2.71 Interface-Id AVP........................................................................................................................................131
7.2.72 Interface-Port AVP.....................................................................................................................................132
7.2.73 Interface-Text AVP.....................................................................................................................................132
7.2.74 Interface-Type AVP....................................................................................................................................132
7.2.74aA Inter-UE-Transfer AVP..............................................................................................................................132
7.2.74A IMS-Application-Reference-Identifier AVP..............................................................................................132
7.2.75 IMS-Charging-Identifier AVP....................................................................................................................132
7.2.76 IMS-Communication-Service-Identifier AVP............................................................................................132
7.2.76A IMS-Emergency-Indicator AVP.................................................................................................................132
7.2.77 IMS-Information AVP................................................................................................................................133
7.2.77A IMS-Visited-Network-Identifier AVP........................................................................................................134
7.2.78 IMSI-Unauthenticated-Flag AVP...............................................................................................................134
7.2.79 Incoming-Trunk-Group-ID AVP................................................................................................................134
7.2.79A Initial-IMS-Charging-Identifier AVP.........................................................................................................134
7.2.80 Inter-Operator-Identifier AVP....................................................................................................................134
7.2.80A IP-Realm-Default-Indication AVP.............................................................................................................134
7.2.80B ISUP-Cause AVP........................................................................................................................................134
7.2.80C ISUP-Cause-Diagnostics AVP...................................................................................................................135
7.2.80D ISUP-Cause-Location AVP........................................................................................................................135
7.2.80E ISUP-Cause-Value AVP.............................................................................................................................135
7.2.80F ISUP-Location-Number AVP.....................................................................................................................135
7.2.80Fa Language AVP............................................................................................................................................135
7.2.80G Layer-2-Group-ID AVP..............................................................................................................................135
7.2.81 LCS-APN AVP...........................................................................................................................................135
7.2.82 LCS-Client-Dialed-By-MS AVP................................................................................................................135
7.2.83 LCS-Client-External-ID AVP....................................................................................................................135
7.2.84 LCS-Client-ID AVP...................................................................................................................................135
7.2.85 LCS-Client-Name AVP..............................................................................................................................137
7.2.86 LCS-Client-Type AVP................................................................................................................................137
7.2.87 LCS-Data-Coding-Scheme AVP................................................................................................................137
7.2.88 LCS-Format-Indicator AVP.......................................................................................................................137
7.2.89 LCS-Information AVP................................................................................................................................137
7.2.90 LCS-Name-String AVP..............................................................................................................................137
7.2.91 LCS-Requestor-ID AVP.............................................................................................................................138

3GPP
Release 15 8 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.92 LCS-Requestor-ID-String AVP..................................................................................................................138

7.2.92A Local-GW-Inserted-Indication AVP...........................................................................................................138
7.2.93 Local-Sequence-Number AVP...................................................................................................................138
7.2.94 Location-Estimate AVP..............................................................................................................................138
7.2.95 Location-Estimate-Type AVP.....................................................................................................................138
7.2.95A Location-Info AVP.....................................................................................................................................138
7.2.96 Location-Type AVP....................................................................................................................................139
7.2.97 Low-Balance-Indication AVP....................................................................................................................139
7.2.97A Low-Priority-Indicator AVP.......................................................................................................................139
7.2.97B MBMS-Charged-Party AVP.......................................................................................................................139
7.2.98 MBMS-GW-Address AVP.........................................................................................................................139
7.2.99 MBMS-Information AVP...........................................................................................................................139
7.2.100 MBMS-User-Service-Type AVP................................................................................................................140
7.2.101 Media-Initiator-Flag AVP...........................................................................................................................141
7.2.102 Media-Initiator-Party AVP.........................................................................................................................141
7.2.103 Message-Body AVP...................................................................................................................................141
7.2.104 Message-Class AVP...................................................................................................................................141
7.2.105 Message-ID AVP........................................................................................................................................141
7.2.106 Message-Size AVP.....................................................................................................................................141
7.2.107 Message-Type AVP....................................................................................................................................142
7.2.108 MM-Content-Type AVP.............................................................................................................................142
7.2.109 MMBox-Storage-Requested AVP..............................................................................................................142
7.2.110 MMS-Information AVP..............................................................................................................................143
7.2.111 MMTel-Information AVP...........................................................................................................................143
7.2.111A MMTel-SService-Type AVP.....................................................................................................................143
7.2.111Aa Monitored-PLMN-Identifier AVP.............................................................................................................144
7.2.111AaA Monitoring-Event-Configuration-Activity AVP........................................................................................144
7.2.111AaB Monitoring-Event-Functionality AVP........................................................................................................144
7.2.111AaC Monitoring-Event-Information AVP..........................................................................................................144
7.2.111AaD Monitoring-Event-Report-Data AVP.........................................................................................................145
7.2.111AaE Monitoring-Event-Report-Number AVP....................................................................................................145
7.2.111Ab Monitoring-UE-HPLMN-Identifier AVP...................................................................................................145
7.2.111Ac Monitoring-UE-Identifier AVP..................................................................................................................145
7.2.111Ad Monitoring-UE-VPLMN-Identifier AVP...................................................................................................145
7.2.111B MSC-Address AVP....................................................................................................................................145
7.2.111C MTC-IWF-Address AVP............................................................................................................................145
7.2.111D Neighbour-Node-Address AVP..................................................................................................................145
7.2.111E Network-Call-Reference-Number AVP.....................................................................................................146
7.2.112 Next-Tariff AVP.........................................................................................................................................146
7.2.112aA NIDD-Submission AVP............................................................................................................................146
7.2.112A NNI-Information AVP................................................................................................................................146
7.2.112B NNI-Type AVP...........................................................................................................................................147
7.2.113 Node-Functionality AVP............................................................................................................................147
7.2.114 Node-Id AVP..............................................................................................................................................147
7.2.115 Number-Of-Diversions AVP......................................................................................................................147
7.2.116 Number-Of-Messages-Sent AVP...............................................................................................................147
7.2.117 Number-Of-Participants AVP.....................................................................................................................147
7.2.118 Number-Of-Received-Talk-Bursts AVP.....................................................................................................148
7.2.119 Number-Of-Talk-Bursts AVP.....................................................................................................................148
7.2.120 Number-Portability-Routing-Information AVP.........................................................................................148
7.2.121 Offline-Charging AVP................................................................................................................................148
7.2.122 Online-Charging-Flag AVP........................................................................................................................148
7.2.123 Originating-IOI AVP..................................................................................................................................149
7.2.124 Originator AVP...........................................................................................................................................149
7.2.125 Originator-Address AVP............................................................................................................................149
7.2.126 Originator-Interface AVP...........................................................................................................................150
7.2.127 Originator-Received-Address AVP............................................................................................................150
7.2.128 Originator-SCCP-Address.........................................................................................................................150
7.2.128A Outgoing-Session-Id AVP..........................................................................................................................150
7.2.129 Outgoing-Trunk-Group-ID AVP................................................................................................................150
7.2.130 Participants-Involved AVP.........................................................................................................................150

3GPP
Release 15 9 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.131 Participant-Group AVP..............................................................................................................................151

7.2.132 Participant-Access-Priority AVP................................................................................................................151
7.2.133 Participant-Action-Type AVP.....................................................................................................................151
7.2.134 Void............................................................................................................................................................151
7.2.135 Void............................................................................................................................................................151
7.2.135A PC3-Control-Protocol-Cause AVP.............................................................................................................151
7.2.135B PC3-EPC-Control-Protocol-Cause AVP....................................................................................................151
7.2.136 PDN-Connection-Charging-ID AVP..........................................................................................................153
7.2.137 PDP-Address AVP......................................................................................................................................153
7.2.137A PDP-Address-Prefix-Length AVP..............................................................................................................153
7.2.138 PDP-Context-Type AVP.............................................................................................................................153
7.2.138A Play-Alternative AVP.................................................................................................................................153
7.2.139 PoC-Change-Condition AVP......................................................................................................................153
7.2.140 PoC-Change-Time AVP.............................................................................................................................153
7.2.141 PoC-Controlling-Address AVP..................................................................................................................154
7.2.142 PoC-Event-Type AVP.................................................................................................................................155
7.2.143 PoC-Group-Name AVP..............................................................................................................................155
7.2.144 PoC-Information AVP................................................................................................................................155
7.2.145 PoC-Server-Role AVP................................................................................................................................155
7.2.146 PoC-Session-Id AVP..................................................................................................................................155
7.2.147 PoC-Session-Initiation-Type AVP..............................................................................................................156
7.2.148 PoC-Session-Type AVP..............................................................................................................................156
7.2.149 PoC-User-Role AVP...................................................................................................................................156
7.2.150 PoC-User-Role-IDs AVP............................................................................................................................156
7.2.151 PoC-User-Role-Info-Units AVP.................................................................................................................156
7.2.152 Positioning-Data AVP................................................................................................................................156
7.2.153 Preferred-AoC-Currency AVP...................................................................................................................156
7.2.154 Priority AVP...............................................................................................................................................157
7.2.154aA Privacy-Indicator AVP...............................................................................................................................157
7.2.154A ProSe-3rd-Party-Application-ID AVP.......................................................................................................157
7.2.154Aa ProSe-Direct-Communication-Reception-Data-Container AVP................................................................157
7.2.154B ProSe-Direct-Communication-Transmission-Data-Container AVP...........................................................157
7.2.154C ProSe-Direct-Discovery-Model AVP.........................................................................................................158
7.2.154D ProSe-Event-Type AVP..............................................................................................................................158
7.2.154E ProSe-Function-IP-Address AVP...............................................................................................................158
7.2.154F ProSe-Function-PLMN-Identifier AVP......................................................................................................158
7.2.154G ProSe-Functionality AVP...........................................................................................................................158
7.2.154H ProSe-Group-IP-Multicast-Address AVP..................................................................................................158
7.2.154I ProSe-Information AVP.............................................................................................................................158
7.2.154J ProSe-Range-Class AVP............................................................................................................................159
7.2.154K ProSe-Reason-For-Cancellation AVP........................................................................................................160
7.2.154L ProSe-Request-Timestamp AVP................................................................................................................160
7.2.154M ProSe-Role-Of-UE AVP............................................................................................................................160
7.2.154N ProSe-Source-IP-Address AVP..................................................................................................................160
7.2.154O ProSe-UE-ID AVP......................................................................................................................................160
7.2.154Oa ProSe-UE-to-Network-Relay-UE-ID AVP................................................................................................160
7.2.154Ob ProSe-Target-Layer-2-ID AVP...................................................................................................................160
7.2.154P Proximity-Alert-Indication AVP................................................................................................................161
7.2.154Q Proximity-Alert-Timestamp AVP...............................................................................................................161
7.2.154R Proximity-Cancellation-Timestamp AVP...................................................................................................161
7.2.155 PS-Append-Free-Format-Data AVP...........................................................................................................161
7.2.156 PS-Free-Format-Data AVP.........................................................................................................................161
7.2.157 PS-Furnish-Charging-Information AVP.....................................................................................................161
7.2.158 PS-Information AVP..................................................................................................................................161
7.2.159 Quota-Consumption-Time AVP.................................................................................................................163
7.2.160 Quota-Holding-Time AVP.........................................................................................................................163
7.2.160aA Quota-Indicator AVP..................................................................................................................................163
7.2.160A Radio-Frequency AVP................................................................................................................................163
7.2.160B Radio-Parameter-Set-Info AVP..................................................................................................................163
7.2.160C Radio-Parameter-Set-Values AVP..............................................................................................................164
7.2.160D Radio-Resources-Indicator AVP................................................................................................................164

3GPP
Release 15 10 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.160Da RAN-End-Timestamp AVP........................................................................................................................164

7.2.160Db RAN-Secondary-RAT-Usage-Report AVP.................................................................................................164
7.2.160Dc RAN-Start-Timestamp AVP.......................................................................................................................164
7.2.160E Rate-Control-Max-Message-Size AVP....................................................................................................164
7.2.160F Rate-Control-Max-Rate AVP...................................................................................................................164
7.2.160G Rate-Control-Time-Unit AVP....................................................................................................................165
7.2.161 Rate-Element AVP.....................................................................................................................................165
7.2.162 Read-Reply-Report-Requested AVP..........................................................................................................165
7.2.163 Void............................................................................................................................................................165
7.2.164 Real-Time-Tariff-Information AVP............................................................................................................166
7.2.164A Reason-Header AVP...................................................................................................................................166
7.2.165 Received-Talk-Burst-Time AVP................................................................................................................166
7.2.166 Received-Talk-Burst-Volume AVP............................................................................................................166
7.2.167 Recipient-Address AVP..............................................................................................................................166
7.2.168 Recipient-Info AVP....................................................................................................................................167
7.2.169 Recipient-Received-Address AVP.............................................................................................................167
7.2.170 Recipient-SCCP-Address...........................................................................................................................167
7.2.171 Refund-Information AVP...........................................................................................................................167
7.2.171A Relationship-Mode AVP............................................................................................................................167
7.2.171Aa Related-Change-Condition-Information AVP............................................................................................168
7.2.171Ab Related-Trigger AVP..................................................................................................................................168
7.2.171B Related-IMS-Charging-Identifier AVP......................................................................................................168
7.2.171C Related-IMS-Charging-Identifier-Node AVP............................................................................................168
7.2.171D Relay-IP-address AVP................................................................................................................................168
7.2.172 Remaining-Balance AVP............................................................................................................................168
7.2.173 Reply-Applic-ID AVP................................................................................................................................169
7.2.174 Reply-Path-Requested AVP.......................................................................................................................169
7.2.175 Reporting-Reason AVP..............................................................................................................................170
7.2.176 Requested-Party-Address AVP..................................................................................................................171
7.2.176A Requested-PLMN-Identifier AVP..............................................................................................................171
7.2.176B Requestor-PLMN-Identifier AVP...............................................................................................................171
7.2.177 Role-Of-Node AVP....................................................................................................................................171
7.2.177aA Role-Of-ProSe-Function AVP....................................................................................................................171
7.2.177A Route-Header-Received AVP.....................................................................................................................171
7.2.177B Route-Header-Transmitted AVP................................................................................................................171
7.2.178 Scale-Factor AVP.......................................................................................................................................172
7.2.178aA SCEF-Address AVP...................................................................................................................................172
7.2.178A SCS-Address AVP......................................................................................................................................172
7.2.178B SCS-AS-Address AVP...............................................................................................................................172
7.2.178C SCS-Realm AVP........................................................................................................................................172
7.2.179 SDP-Answer-Timestamp AVP...................................................................................................................172
7.2.180 SDP-Media-Component AVP....................................................................................................................172
7.2.181 SDP-Media-Description AVP....................................................................................................................173
7.2.182 SDP-Media-Name AVP..............................................................................................................................173
7.2.183 SDP-Offer-Timestamp AVP.......................................................................................................................173
7.2.184 SDP-Session-Description AVP..................................................................................................................173
7.2.185 SDP-TimeStamps AVP...............................................................................................................................173
7.2.186 SDP-Type AVP...........................................................................................................................................173
7.2.186A Session-Direction AVP...............................................................................................................................173
7.2.187 Served-Party-IP-Address AVP...................................................................................................................174
7.2.188 Void............................................................................................................................................................174
7.2.188A Secondary-RAT-Type AVP.........................................................................................................................174
7.2.189 Service-Data-Container AVP.....................................................................................................................174
7.2.190 Service-ID AVP..........................................................................................................................................175
7.2.191 Service-Generic-Information AVP.............................................................................................................175
7.2.192 Service-Information AVP...........................................................................................................................175
7.2.193 Service-Mode AVP.....................................................................................................................................176
7.2.194 Service-Specific-Data AVP........................................................................................................................176
7.2.195 Service-Specific-Info AVP.........................................................................................................................176
7.2.196 Service-Specific-Type AVP........................................................................................................................176
7.2.197 Void............................................................................................................................................................176

3GPP
Release 15 11 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.197a Serving-Node-Identity...............................................................................................................................176
7.2.198 Serving-Node-Type AVP............................................................................................................................177
7.2.198A SGi-PtP-Tunnelling-Method AVP..............................................................................................................177
7.2.199 SGSN-Address AVP...................................................................................................................................177
7.2.199A SGW-Address AVP....................................................................................................................................177
7.2.200 SGW-Change AVP.....................................................................................................................................177
7.2.201 SIP-Method AVP........................................................................................................................................177
7.2.202 SIP-Request-Timestamp AVP....................................................................................................................177
7.2.203 SIP-Request-Timestamp-Fraction AVP.....................................................................................................177
7.2.204 SIP-Response-Timestamp AVP..................................................................................................................178
7.2.205 SIP-Response-Timestamp-Fraction AVP...................................................................................................178
7.2.205A SM-Device-Trigger-Indicator AVP............................................................................................................178
7.2.205B SM-Device-Trigger-Information AVP.......................................................................................................178
7.2.206 SM-Discharge-Time AVP..........................................................................................................................178
7.2.207 SM-Message-Type AVP.............................................................................................................................178
7.2.208 SM-Protocol-Id AVP..................................................................................................................................179
7.2.208A SM-Sequence-Number AVP......................................................................................................................179
7.2.209 SM-Status AVP..........................................................................................................................................179
7.2.210 SM-User-Data-Header AVP.......................................................................................................................179
7.2.211 SMS-Information AVP...............................................................................................................................179
7.2.212 SMS-Node AVP.........................................................................................................................................180
7.2.212A SMS-Result AVP........................................................................................................................................180
7.2.213 SM-Service-Type AVP...............................................................................................................................181
7.2.214 SMSC-Address AVP..................................................................................................................................181
7.2.214A Start-of-Charging AVP...............................................................................................................................181
7.2.215 Start-Time AVP..........................................................................................................................................181
7.2.215A Status-AS-Code AVP.................................................................................................................................181
7.2.216 Stop-Time AVP..........................................................................................................................................181
7.2.217 Submission-Time AVP...............................................................................................................................182
7.2.218 Subscriber-Role AVP.................................................................................................................................182
7.2.219 Supplementary-Service AVP......................................................................................................................182
7.2.219A TAD-Identifier AVP...................................................................................................................................182
7.2.220 Talk-Burst-Exchange AVP.........................................................................................................................182
7.2.221 Talk-Burst-Time AVP.................................................................................................................................183
7.2.222 Talk-Burst-Volume AVP.............................................................................................................................183
7.2.222A Target-IP-Address AVP..............................................................................................................................183
7.2.223 Tariff-Information AVP..............................................................................................................................183
7.2.224 Tariff-XML AVP........................................................................................................................................183
7.2.224A Teleservice AVP.........................................................................................................................................183
7.2.225 Terminating-IOI AVP.................................................................................................................................183
7.2.225A Time-First-Reception AVP.........................................................................................................................184
7.2.225B Time-First-Transmission AVP....................................................................................................................184
7.2.226 Time-First-Usage AVP...............................................................................................................................184
7.2.226A Time-Indicator AVP...................................................................................................................................184
7.2.227 Time-Last-Usage AVP...............................................................................................................................184
7.2.228 Time-Quota-Mechanism............................................................................................................................184
7.2.229 Time-Quota-Threshold AVP......................................................................................................................185
7.2.230 Time-Quota-Type AVP...............................................................................................................................185
7.2.231 Time-Stamps AVP......................................................................................................................................185
7.2.232 Time-Usage AVP.......................................................................................................................................185
7.2.232A TLTRI AVP................................................................................................................................................185
7.2.233 Traffic-Data-Volumes AVP........................................................................................................................185
7.2.233A Transcoder-Inserted-Indication AVP..........................................................................................................186
7.2.233B Transit-IOI-List AVP..................................................................................................................................186
7.2.233C Transmitter-Info AVP.................................................................................................................................186
7.2.234 Token-Text AVP.........................................................................................................................................186
7.2.235 Trigger AVP...............................................................................................................................................186
7.2.236 Trigger-Type AVP......................................................................................................................................187
7.2.237 Trunk-Group-ID AVP.................................................................................................................................190
7.2.237aA TTRI AVP.................................................................................................................................................190
7.2.237A Void............................................................................................................................................................190

3GPP
Release 15 12 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.237B Void............................................................................................................................................................190
7.2.237Ba TWAG-Address AVP.................................................................................................................................190
7.2.237C TWAN-User-Location-Info AVP...............................................................................................................191
7.2.238 Type-Number AVP.....................................................................................................................................191
7.2.238A UNI-PDU-CP-Only-Flag AVP...................................................................................................................191
7.2.239 Unit-Cost AVP............................................................................................................................................191
7.2.240 Unit-Quota-Threshold AVP........................................................................................................................191
7.2.240a Unused-Quota-Timer AVP.........................................................................................................................192
7.2.240A User-CSG-Information AVP......................................................................................................................192
7.2.240B Usage-Information-Report-Sequence-Number AVP..................................................................................192
7.2.241 User-Participating-Type AVP.....................................................................................................................192
7.2.242 User-Session-Id AVP..................................................................................................................................192
7.2.242aaA UWAN-User-Location-Info AVP...............................................................................................................192
7.2.242aA Variable-Part AVP......................................................................................................................................193
7.2.242aB Variable-Part-Order AVP............................................................................................................................193
7.2.242aC Variable-Part-Type AVP.............................................................................................................................193
7.2.242aD Variable-Part-Value AVP............................................................................................................................193
7.2.242A VCS-Information AVP...............................................................................................................................193
7.2.242B VLR-Number AVP.....................................................................................................................................194
7.2.243 Volume-Quota-Threshold AVP..................................................................................................................194
7.2.244 Void............................................................................................................................................................194
7.2.245 Void............................................................................................................................................................194
7.2.246 Void............................................................................................................................................................194
7.2.247 Void............................................................................................................................................................194
7.2.248 Void............................................................................................................................................................194
7.2.249 Void............................................................................................................................................................194
7.2.250 Void............................................................................................................................................................195
7.2.251 WLAN-Operator-Id AVP...........................................................................................................................195
7.2.252 WLAN-Operator-Name AVP.....................................................................................................................195
7.2.253 WLAN-PLMN-Id AVP..............................................................................................................................195
7.3 3GPP2 specific AVPs.......................................................................................................................................196
7.4 ETSI specific AVPs..........................................................................................................................................196
7.5 oneM2M specific AVPs...................................................................................................................................196

Annex A (informative): Bibliography................................................................................................197

Annex B (normative): 3GPP Charging Diameter Overload Control............................................198
B.1 DOIC (Diameter Overload Indication Conveyance)...........................................................................198
B.1.0 General.............................................................................................................................................................198
B.1.1 Reporting node................................................................................................................................................198
B.1.2 Reacting node..................................................................................................................................................198
B.2 Diameter overload AVPs.....................................................................................................................198
B.2.0 General.............................................................................................................................................................198
B.2.1 3GPP-OC-Rating-Group AVP.........................................................................................................................199
B.2.2 3GPP-OC-Request-Type AVP.........................................................................................................................199
B.2.3 3GPP-OC-Specific-Reduction AVP.................................................................................................................199
B.2.4 OC-OLR AVP..................................................................................................................................................199

Annex C (informative): Change history..............................................................................................200

3GPP
Release 15 13 3GPP TS 32.299 V15.4.0 (2018-09)

Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

3GPP
Release 15 14 3GPP TS 32.299 V15.4.0 (2018-09)

1 Scope
The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and
charging management in GSM/UMTS networks. The GSM/UMTS core network-charging architecture and principles
are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify.

- The content of the CDRs' per domain and subsystem (offline charging);

- The content of real-time charging messages per domain / subsystem (online charging);

- The functionality of online and offline charging for those domains and subsystems;

- The interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or
charging events).

The complete document structure for these TSs is defined in TS 32.240 [1].

The present document specifies in detail the Diameter based offline and online charging applications for 3GPP
networks. It includes all charging parameters, scenarios and message flows..

All terms, definitions and, abbreviations used in the present document, that are common across 3GPP TSs, are defined
in TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains, services or
subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document
for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present
document.

Furthermore, requirements that govern the charging work are specified in TS 22.115 [101].

3GPP
Release 15 15 3GPP TS 32.299 V15.4.0 (2018-09)

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 TS 32.240: "Telecommunication management; Charging management; Charging

architecture and principles ".

[2] - [10] Void.

[11] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched

(PS) domain charging".

[12] Void.

[13] 3GPP TS 32.253: "Telecommunication management; Charging management; Control Plane (CP)
data transfer domain charging".

[14] - [99] Void.

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

[101] 3GPP TS 22.115: "Service aspects; Charging and billing".

[102] - [199] Void.

[200] 3GPP TS 23.207: "End to end quality of service concept and architecture".

[201] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".

[202] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3".

[203] 3GPP TS 29.207: "Policy control over Go interface".

[204] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; Protocol Details".

[205] Void.

[206] 3GPP TS 29.230: "3GPP specific codes and identifiers".

[207] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
packet based services and Packet Data Networks (PDN)".

[208] 3GPP TS 23.140: " Multimedia Messaging Service (MMS); Functional description; Stage 2".

[209] OMA "Multimedia Messaging Service; Encapsulation Protocol".

[210] OMNA WSP Content Type Numbers

http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx

[211] OMA-CP-POC: "OMA PoC Control Plane".

[212] Void.

[213] 3GPP TS 29.140: "MM10 interface based on Diameter protocol; Stage 3".

3GPP
Release 15 16 3GPP TS 32.299 V15.4.0 (2018-09)

[214] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point; Stage 3".

[215] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".

[216] 3GPP TS 23.040: "Technical realization of Short Message Service (SMS)".

[217] 3GPP TS 22.142: "Value Added Services (VAS) for Short Message Service (SMS) requirements".

[218] 3GPP TS 23.203: "Policy and Charging control architecture".

[219] 3GPP TS 29.272: " Mobility Management Entity (MME) and Serving GPRS Support Node
(SGSN) related interfaces based on Diameter protocol".

[220] 3GPP TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem;
Protocol specification".

[221] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol;Protocol details".

[222] 3GPP TS 29.658: "SIP Transfer of IP Multimedia Service Tariff Information".

[223] OMA-DDS-Charging_Data: "Charging Data".

[224] 3GPP TS 23.003: "Numbering, Addressing and Identification".

[225] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP)
across the Gn and Gp interface".

[226] 3GPP TS 29.274: "Evolved GPRS Tunnelling Protocol for Control Plane (GTPv2-C); Stage 3".

[227] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".

[228] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".

[229] 3GPP TS 29.173: "Location Services (LCS);Diameter-based SLh interface for Control Plane
LCS".

[230] 3GPP TS 29.272: "Evolved Packet System (EPS);Mobility Management Entity (MME) and
Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".

[231] 3GPP TS 29.337: "Diameter-based T4 interface for communications with packet data networks
and applications ".

[232] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".

[233] 3GPP TS 29.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL);
CAMEL Application Part (CAP) specification".

[234] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem
and Circuit Switched (CS) networks".

[235] 3GPP TS 23.303: "Proximity-based services (ProSe)".

[236] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol
aspects".

[237] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA Interfaces".

[238] 3GPP TS 29.343: "Proximity-services (ProSe) function to ProSe application server aspects (PC2)".

[239] 3GPP TS 29.345: "Inter-Proximity-services (ProSe) Function signalling aspects".

[240] Void.

[241] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification".

[242] Void.

3GPP
Release 15 17 3GPP TS 32.299 V15.4.0 (2018-09)

[243] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data
networks and applications".

[244] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node
(SGSN) interfaces for interworking with packet data networks and applications".

[245] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with
packet data networks and applications".

[246] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security ".

[247] - [299] Void.

[300] ETSI TS 283 034 v2.2.0: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based
on the DIAMETER protocol".

[301] oneM2M TS-0004: "Service Layer Core Protocol Specification".

[302] - [400] Void.

[401] IETF RFC 6733 (2012): "Diameter Base Protocol".

[402] IETF RFC 4006 (2005): "Diameter Credit-Control Application".

[403] Void.

[404] IETF RFC 7315 (2014): "Private Extensions to the Session Initiation Protocol (SIP) for the 3rd
Generation Partnership Projects (3GPP)".

[405] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol".

[406] IETF RFC 4566 (2006): "SDP: Session Description Protocol".

[407] IETF RFC 4005 (2005): "Diameter Network Access Server Application".

[408] IETF RFC 3264 (2002): "An Offer/Answer Model with the Session Description Protocol (SDP) ".

[409] IEEE 802.11-2012: "IEEE Standard for Information technology - Telecommunications and
information exchange between systems - Local and metropolitan area networks - Specific
requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".

[410] IETF RFC 3066 (2001): "Tags for the Identification of Languages".

[411] IETF RFC 7683 (2015):"Diameter Overload Indication Conveyance".

3 Definitions, symbols and abbreviations

3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [100] and the following apply.
A term defined in the present document takes precedence over the definition of the same term, if any, in
TR 21.905 [100].

middle tier TS: term used for the 3GPP charging TSs that specify the domain / subsystem / service specific, online and
offline, charging functionality. These are all the TSs in the numbering range from TS 32.250 to TS 32.27x, e.g. TS
32.250 [10] for the CS domain, or TS 32.270 [30] for the MMS service. Currently, there is only one "tier 1" TS in 3GPP,
which is the TS 32.240 that specifies the charging architecture and principles. Finally, there are a number of top tier TSs
in the 32.29x numbering range ([50] ff) that specify common charging aspects such as parameter definitions, encoding
rules, the common billing domain interface or common charging applications.

offline charging: charging mechanism where charging information does not affect, in real-time, the service rendered

3GPP
Release 15 18 3GPP TS 32.299 V15.4.0 (2018-09)

online charging: charging mechanism where charging information can affect, in real-time, the service rendered and
therefore a direct interaction of the charging mechanism with session/service control is required

3.2 Symbols
For the purposes of the present document, the following symbols apply:

Rf Offline Charging Reference Point between a 3G network element and the CDF.
Ro Online Charging Reference Point between a 3G network element and the OCS.

3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:

5GS 5G System
5GC 5G Core
ACA ACcounting-Answer
ACR ACcounting-Request
ADC Application Detection and Control
AoC Advice of Charge
AS Application Server
ASA Abort-Session-Answer
ASR Abort-Session- Request
AVP Attribute Value Pair
CCA Credit-Control-Answer
CCR Credit-Control-Request
CDF Charging Data Function
CDR Charging Data Record
CEA Capabilities-Exchange-Answer
CER Capabilities-Exchange-Request
CGI Cell Global Identification
CI Cost-Information
CIoT Cellular Internet of Things
CP Control Plane
CSG Closed Subscriber Group
CSG ID Closed Subscriber Group Identity
DBPA Diameter Base Protocol Accounting
DCD Dynamic Content Delivery
DPA Disconnect-Peer-Answer
DPR Disconnect-Peer-Request
DRM Digital Rights Management
DWA Device-Watchdog-Answer
DWR Device-Watchdog-Request
ECGI E-UTRAN Cell Global Identifier
ECUR Event Charging with Unit Reservation
FQDN Fully Qualified Domain Name
FUI Final-Unit-Indication
HSGW HRPD Serving GateWay
GSU Granted-Service-Unit
IEC Immediate Event Charging
IM Instant Messaging
IMS IP Multimedia Subsystem
IMS-AGW IMS Access Media Gateway
IWK-SCEF Interworking SCEF
MSCC Multiple Services Credit-Control
NetLoc Network provided Location information
NIDD Non-IP Data Delivery
NNI Network to Network Interface
NR New Radio
OCS Online Charging System
PFDF Packet Flow Description Function

3GPP
Release 15 19 3GPP TS 32.299 V15.4.0 (2018-09)

ProSe Proximity-based Services

RAA Re-Auth-Answer
RAI Routeing Area Identity
RAR Re-Auth-Request
RAVEL Roaming Architecture for VoicE over IMS with Local breakout
SAI Service Area Identifier
SCCP Signalling Connection Control Part
SCEF Service Capability Exposure Function
SCS Services Capability Server
SDP Session Description Protocol
RCAF RAN Congestion Awareness Function
TAI Tracking Area Identity
TDF Traffic Detection Function
TLTRI T8 Long Term Transaction Reference ID
TrGW Transition GateWay
TTRI T8 Transaction Reference ID
TWAG Trusted WLAN Access Gateway
TWAN Trusted WLAN Access Network
UWAN Untrusted Wireless Access Network
VCS Voice Call Service

3GPP
Release 15 20 3GPP TS 32.299 V15.4.0 (2018-09)

4 Architecture considerations

4.1 High level architecture

4.1.0 General
The Rf and the Ro are reference points from the Charging Trigger Function (CTF) to the Charging Data Function (CDF)
and the Online Charging Function (OCF) respectively, and are intended for the transport of charging events. Rf is used
for offline charging whereas Ro is used for online charging.
Figure 4.1.0.1 and figure 4.1.0.2 depict the position of the Rf and Ro reference points within the overall 3GPP online
and offline charging architecture.

CTF: Charging Trigger Function

CDF: Charging Data Function
CGF: Charging Gateway Function
BD: Billing Domain. This may also be a billing mediation device / post-processing system.

Figure 4.1.0.1: Logical ubiquitous offline charging architecture

3GPP
Release 15 21 3GPP TS 32.299 V15.4.0 (2018-09)

CTF: Charging Trigger Function

OCF: Online Charging Function
CGF: Charging Gateway Function
BD: Billing Domain. This may also be a billing mediation device / post-processing system.

Figure 4.1.0.2: Logical ubiquitous online charging architecture

Different mappings of the ubiquitous offline charging functions, CTF, CDF and CGF, onto physical implementations are
possible. Further details of the configuration refer toTS 32.240 [1]. Details of the implementation options per domain /
subsystem / service (usually a subset of the overall possible variants described above) are specified in the respective
middle tier TSs.

4.1.1 Charging related transfer requirements

Each CTF would have CDF and OCF address list to which it can send its charging events and/or charging requests.
The list is organized in address priority order. If the primary charging function is not available (e.g. out of service) then
the CTF shall send the charging information to the secondary charging function and so on.

Within the scope of this release, each Network Element that generates charging information sends the information only
to the charging entities of the same PLMN, and not to charging entities in other PLMNs.
To implement roaming unbundling for EU roaming regulation III, an architectural solution known as the Single IMSI
architecture has been defined. In this architecture a specific Service-NE (known as a Proxy Function) uses the Ro
reference point for sending charging information to an OCF in another network. The details of this architecture are
defined in Annex B of TS 32.240 [1].

To implement PS domain online charging for roaming context, PCEF in the VPLMN uses the Gy reference point, and
TDF in the VPLMN uses the Gyn reference point, both based on Ro interface and specified in TS 32.251[11], for
sending charging information to an OCS in the HPLMN. A simplified profile is provided in Annex E of TS 32.251[11]
for deployment purposes.

Each CDF in the PLMN may know of other CDFs' network addresses (e.g., for redundancy reasons, to be able to
recommend another CDF address with the Redirection Request message). This is achieved by OAM&P configuration
facilities that enables each CDF to have a configurable list of peer CDF addresses.

3GPP
Release 15 22 3GPP TS 32.299 V15.4.0 (2018-09)

5 3GPP charging applications requirements

5.1 Offline charging scenarios

5.1.1 Basic principles

5.1.1.0 Introduction
Offline charging for both events and sessions between CTF and the CDF is performed using the Rf reference point as
defined in TS 32.240 [1].

Two basic scenarios are used:

- Event based charging;

- Session based charging.

3GPP
Release 15 23 3GPP TS 32.299 V15.4.0 (2018-09)

5.1.1.1 Event based charging

In scenario figure 5.1.1.1.1, CTF asks the CDF to store event related charging data.

UE-A CDF CTF

1. Request for resource usage

2. Content/Service Delivery

3. Charging Data
Generation

Event Based Charging

4.Charging Data Request (Event Related Charging Data)

5. Process
Request

6.Charging Data Response

Figure 5.1.1.1.1: Event based charging

1) Request for resource usage: UE-A requests the desired resource from the Network Element.

2) Content/Service Delivery: the Network Element delivers the content/service.

3) Charging Data Generation: the CTF generates charging data related to service delivery.

4) Record Charging Data Request: the CTF requests the CDF to store event related charging data for CDR
generation purposes.

5) Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR
generation configuration.

6) Record Charging Data Response: the CDF informs the CTF that charging data was stored.

3GPP
Release 15 24 3GPP TS 32.299 V15.4.0 (2018-09)

5.1.1.2 Session based charging

In scenario figure 5.1.1.2.1, CTF asks the CDF to store session related charging data.

UE-A CDF CTF

1. Request for resource usage

2. Session Ongoing

3.Charging Data
Generation

Session Based Charging

4.Charging Data Request (Session Related Charging Data)

5. Process
Request
6.Charging Data Response

7.Charging Data
Generation

8.Charging Data Request (Session Related Charging Data)

9. Process
Request
10.Charging Data Response

8. Credit Unit Control (cont.)

11. Session released

12.Charging Data
Generation

13.Charging Data Request (Session Related Charging Data)

14. Process
Request

15.Charging Data Response

Figure 5.1.1.2.1: Session based charging

1) Request for resource usage: UE-A requests the desired session from the Network Element.

2) Session ongoing: the Network Element establish the session.

3) Charging Data Generation: the CTF generates charging data related to session.

4) Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR
generation purposes.

5) Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR
generation configuration.

6) Record Charging Data Response: the CDF informs the CTF that charging data was stored.

3GPP
Release 15 25 3GPP TS 32.299 V15.4.0 (2018-09)

7) Charging Data Generation: the CTF generates charging data related to session due of e.g. intermediate timer
expiry.

8) Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR
generation purposes.

9) Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR
generation configuration.

10)Record Charging Data Response: the CDF informs the CTF that charging data was stored.

11) Session release: the session is released.

12)Charging Data Generation: the CTF generates charging data related to session due of session termination.

13)Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR
generation purposes.

14)Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR
generation configuration.

15)Record Charging Data Response: the CDF informs the CTF that charging data was stored.

3GPP
Release 15 26 3GPP TS 32.299 V15.4.0 (2018-09)

5.1.2 Basic operation

Event and session based Charging are performed by the use of the "Charging Data Transfer" operation:

- "Charging Data Request"; sent from CTF  CDF

After detecting a chargeable event, the CTF sends a Charging Data Request to the CDF.

- "Charging Data Response"; sent from CDF  CTF

The CDF replies with a Charging Data Response, which informs the CTF that charging data was received.

Table 5.1.2.1 and table 5.1.2.2 describe the content of these operations.

Table 5.1.2.1: Charging Data Request content

Information Element Category Description

Session Identifier M This field identifies the operation session.
Originator Host M This field contains the identification of the source point of the
operation and the realm of the operation originator.
Originator Domain M This field contains the realm of the operation originator.
Destination Domain M This field contains the realm of the operation destination.
Operation Type M This field defines the transfer type: event for event based charging
and start, interim, stop for session based charging.
Operation Number M This field contains the sequence number of the transferred
messages.
Operation Identifier OM The field corresponds to the unique operation identification.
User Name OC The field contains the identification of the service user.
Destination Host OC This field contains the identification of the destination point of the
operation.
Operation Interval OC This field contains the proposal for instructions to produce records
continuously during a session.
Origination State OC This field contains the state associated to the source point of the
operation.
Origination Timestamp OC This field contains the time when the operation is requested.
Proxy Information OC This field contains the parameter of the proxy.
Route Information OC This field contains the parameter of the route.
Operation Token OM This field identifies the domain, subsystem or service and release.
Service information OM This parameter holds the individual service specific parameters as
defined in the corresponding 'middle tier' TS.

Table 5.1.2.2: Charging Data Response content

Information Element Category Description

Session Identifier M This field identifies the operation session.
Operation Result M This field identifies the result of the operation.
Originator Host M This field contains the identification of the source point of the
operation and the realm of the operation originator.
Originator Domain M This field contains the realm of the operation originator.
Operation Type M This field defines the transfer type: event for event based charging
and start, interim, stop for session based charging.
Operation Number M This field contains the sequence number of the transferred
messages.
Operation Identifier OM The field corresponds to the unique operation identification.
Operation Interval OC This field contains the instructions to produce records continuously
during a session.
Error Reporting Host OC If proxies exist between the accounting client and the accounting
server this field contains the identity of the proxy that sent a
response other than 2001 (Success).
Origination State OC This field contains the state associated to the source point of the
service.
Origination Timestamp OC This field contains the time when the operation is requested.
Proxy Information OC This field contains the parameter of the proxy.

3GPP
Release 15 27 3GPP TS 32.299 V15.4.0 (2018-09)

5.2 Online charging scenarios

5.2.0 Introduction
Online charging for both events and sessions between CTF and the OCF is performed using the Ro reference point.
The Ro reference point supports integrity protection and authentication for the case that the CTF is outside the operator
domain.

5.2.1 Basic principles

There are two sub-functions for online charging that affect online charging principles and require a more detailed
description: rating and unit determination. Both rating and unit determination can be implemented centralized, i.e. on
the OCF, or decentralized, that is, on the CTF.

Unit determination refers to the calculation of the number of non-monetary units (service units, data volume, time and
events) that shall be assigned prior to starting service delivery.

- With Centralized Unit Determination, the OCF determines the number of non-monetary units that a certain
service user can consume based on a service key received from the CTF.

- With the Decentralized Unit Determination approach, the CTF determines itself how many units are required to
start service delivery, and requests these units from the OCF.

After checking the service user's account balance, the OCF returns the number of granted units to the CTF. The CTF is
then responsible for the supervision of service delivery. Particularly, the CTF shall limit service delivery to the
corresponding number of granted units.

Rating refers to the calculation of a price out of the non-monetary units calculated by the unit determination function.

- With the Centralized Rating approach, the CTF and the OCF exchange information about non-monetary units.
The OCF translates these units into monetary units.

- With the Decentralized Rating approach, the corresponding rating control is performed within the CTF.
Consequently, CTF and OCF exchange information about monetary units.

Three cases for online charging can be distinguished: Immediate Event Charging (IEC), Event Charging with Unit
Reservation (ECUR) and Session Charging with Unit Reservation (SCUR). These cases are further described in
TS 32.240 [1].

3GPP
Release 15 28 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2 Charging scenarios

5.2.2.0 Introduction
In order to perform event charging via Ro, the scenarios between the involved entities UE-A, OCF and CTF need to be
defined. The charging flows shown in this subclause include scenarios with immediate event charging and event
charging with reservation. In particular, the following cases are shown:

1 Immediate Event Charging

a) Decentralized Unit Determination and Centralized Rating

b) Centralized Unit Determination and Centralized Rating

c) Decentralized Unit Determination and Decentralized Rating

2 Event charging with Unit Reservation

a) Decentralized Unit Determination and Centralized Rating

b) Centralized Unit Determination and Centralized Rating

c) Decentralized Unit Determination and Decentralized Rating

3 Session charging with Unit Reservation

a) Decentralized Unit Determination and Centralized Rating

b) Centralized Unit Determination and Centralized Rating

c) Decentralized Unit Determination and Decentralized Rating

The combination of Centralized Unit Determination with Decentralized Rating is not possible.

3GPP
Release 15 29 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.1 Immediate Event Charging (IEC)

5.2.2.1.1 Decentralized Unit Determination and Centralized Rating

In scenario figure 5.2.2.1.1.1, CTF asks the OCF to assign a defined number of units.

Figure 5.2.2.1.1.1: IEC - Centralized Rating and Decentralized Unit Determination

1) Request for resource usage: UE-A requests the desired resource from the Network Element.

2) Units Determination: depending on the requested service the CTF determines the number of units accordingly.

3) Debit Units Request: the CTF requests the OCF to assign the defined number of units.

4) Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represents
the price for the number of units determined in item 2.

5) Account Control: provided that the user's credit balance is sufficient, the OCF triggers the deduction of the
calculated amount from the subscriber's account.

6) Debit Units Response: the OCF informs the CTF of the number of granted units.

7) Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually
chargeable items, corresponding to the number of granted units.

8) Credit Unit Control (cont.): this function block is optional and a replication of items 2 to 6.

3GPP
Release 15 30 3GPP TS 32.299 V15.4.0 (2018-09)

9) Content/Service Delivery (cont.): the continuation of content delivery occurs in correspondence with the
occurrence of item 8.

10)Session released: Session is released.

3GPP
Release 15 31 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.1.2 Centralized Unit Determination and Centralized Rating

In scenario figure 5.2.2.1.2.1, CTF asks the OCF to assign units based on the service key specified by the CTF.

Figure 5.2.2.1.2.1: IEC - Centralized Rating and Centralized Unit Determination

1) Request for resource usage: The UE-A requests the desired resource or content from the Network Element.

2) Debit Units Request: depending on the service requested by the UE-A, the CTF determines the service key and
forwards the Debit Units Request with service key to the OCF.

3) Units Determination: the OCF determines the number of non-monetary units needed for the content/service
delivery, based on the received service key.

4) Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represent the
price for the number of units determined in item 3.

5) Account Control: provided that the user's credit balance is sufficient, the OCF triggers the deduction of the
calculated amount from the subscriber's account.

6) Debit Units Response: the OCF informs the CTF of the number of granted units. This includes the case where
the number of units granted indicates the permission to render the service that was identified by the received
service key.

7) Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually
chargeable items, corresponding to the number of granted units.

8) Credit Service Control (cont.): this function block is optional and a replication of items 2 to 6.

3GPP
Release 15 32 3GPP TS 32.299 V15.4.0 (2018-09)

9) Content/Service Delivery (cont.): the continuation of content delivery occurs in correspondence with the
occurrence of item 8.

10)Session released: the session is released.

3GPP
Release 15 33 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.1.3 Decentralized Unit Determination and Decentralized Rating

In scenario figure 5.2.2.1.3.1, the CTF asks the OCF to assure the deduction of an amount of the specified number of
monetary units from the subscriber's account.

Figure 5.2.2.1.3.1: IEC - Decentralized Rating and Decentralized Unit Determination

1) Request for resource usage: The UE-A requests the desired content from the Network Element.

2) Units Determination: depending on the service requested by the UE-A, the CTF determines the number of units
accordingly.

3) Rating Control: the CTF calculates the number of monetary units that represent the price for the number of
units determined in item 2.

4) Debit Units Request: the CTF requests the OCF to assure the deduction of an amount corresponding to the
calculated number of monetary units from the subscriber's account.

5) Account Control: provided that the user's credit balance is sufficient, the OCF triggers the deduction of the
calculated amount from the subscriber's account.

6) Debit Units Response: the OCF indicates to the CTF the number of deducted monetary units.

7) Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually
chargeable items, corresponding to the number of units as specified in items 2 and 3.

8) Credit Amount Control (cont.): this function block is optional and a replication of items 2 to 6.

3GPP
Release 15 34 3GPP TS 32.299 V15.4.0 (2018-09)

9) Content/Service Delivery (cont.): the continuation of content delivery occurs in correspondence with the
occurrence of item 8.

10)Session released: the session is released.

5.2.2.1.4 Further options

In addition to the flows that are specified in the previous subclauses, the Debit Unit operation may alternatively be
carried out concurrently with service delivery, or after completion of service delivery.

3GPP
Release 15 35 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.2 Event Charging with Unit Reservation (ECUR)

5.2.2.2.1 Decentralized Unit Determination and Centralized Rating

In scenario figure 5.2.2.2.1.1, the CTF requests the reservation of units prior to service delivery.
An account debit operation is carried out following the conclusion of service delivery.

UE-A OCF CTF

1. Request for resource usage

2. Units
Determination

3. Reserve Units Request (Non-monetary Units)

4. Rating
Control

5. Account
Control

6.Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Reserved Units
Supervision

9. Content/Service Delivery

10. Debit Units Request (Non-monetary Units)

11. Rating
Control

12. Account
Control

13. Debit Units Response (Non-monetary Units)

14. Session released

Figure 5.2.2.2.1.1: ECUR - Decentralized Unit Determination and Centralized Rating

1) Request for resource usage: The UE-A requests the desired content/service from the NE.

2) Units Determination: depending on the requested service the CTF determines the number of units accordingly.

3) Reserve Units Request: the CTF requests the OCF to reserve the number of units determined in item 2.

4) Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represents 

the price for the number of units determined in item 2.

5) Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation.

3GPP
Release 15 36 3GPP TS 32.299 V15.4.0 (2018-09)

6) Reservation Control: if the user's account balance is sufficient then the corresponding reservation is made.

7) Reserve Units Response: the OCF informs the CTF of the reserved number of units.

8) Reserved Units Supervision: simultaneously with the service delivery, the CTF monitors the consumption of
the reserved units.

9) Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually
chargeable items, corresponding to the reserved number of units.

10)Debit Units Request: the CTF requests the OCF to assure the deduction of an amount corresponding to the
consumed number of units from the subscriber's account. In the case that no further units are required for this
service, an appropriate indication triggering the release of the remaining reservation is given.

11) Rating Control: assisted by the rating entity the OCF calculates the number of monetary units to deduct from
the subscriber's account.

12)Account Control: the OCF triggers the deduction of the calculated amount from the subscriber's account.

13)Debit Units Response: the OCF informs the CTF of the actually deducted units.

14)Session Release: the session is released.

3GPP
Release 15 37 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.2.2 Centralized Unit Determination and Centralized Rating

In scenario figure 5.2.2.2.2.1, the CTF requests the OCF to reserve units based on the service key specified by the CTF.
An account debit operation is carried out following the conclusion of service delivery.

UEa OCF CTF

1. Request for resource usage

2. Reserve Units Request (Service Key)

3. Units
Determination

4. Rating Control

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Granted Units
Supervision

9. Content/Service Delivery

10. Debit Units Request (Non-monetary Units)

11. Rating
Control

12. Account
Control
13. Debit Units Response (Non-monetary Units)

14. Session released

Figure 5.2.2.2.2.1: ECUR - Centralized Unit Determination and Centralized Rating

1) Request for resource usage: The UE-A requests the desired content from the CTF.

2) Reserve Units Request: depending on the service requested by the UE-A, the CTF determines the service key
and forwards the Reserve Units Request with service key to the OCF.

3) Units Determination: the OCF determines the number of non­monetary units needed for the content/service 

delivery, based on the received service key.

4) Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represent the 

price for the number of units determined in item 3.

5) Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation.

6) Reservation Control: if the user's account balance is sufficient, then the corresponding reservation is made.

3GPP
Release 15 38 3GPP TS 32.299 V15.4.0 (2018-09)

7) Reserve Units Response: the OCF informs the CTF of the reserved number of units. This includes the case
where the number of units reserved indicates the permission to render the service that was identified by the
received service key.

8) Granted Units Supervision: simultaneously with the service delivery, the CTF monitors the consumption of the
reserved units.

9) Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually
chargeable items, corresponding to the reserved number of units.

10)Debit Units Request: the CTF provides according to previous Reserve Units Response the request to deduct the
amount of units corresponding to the consumed number of units.

11) Rating Control: assisted by the rating entity the OCF calculates the number of monetary units to deduct from
the subscriber's account.

12)Account Control: the OCF triggers the deduction of the calculated amount from the subscriber's account.

13)Debit Units Response: the OCF informs the CTF of the actually deducted units.

14)Session Released: the session is released.

3GPP
Release 15 39 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.2.3 Decentralized Unit Determination and Decentralized Rating

In scenario figure 5.2.2.2.3.1, the CTF request the OCF to assure the reservation of an amount of the specified number
of monetary units from the subscriber's account. An account debit operation that triggers the deduction the amount from
the subscriber's account is carried out following the conclusion of service delivery.

UEa OCF CTF

1. Request for resource usage

2. Units
Determination

3. Rating Control

4. Reserve Units Request (Monetary Units)

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Monetary Units)

8. Budget
Control

9. Content/Service Delivery

10. Debit Units Request (Monetary Units)

11. Account
Control

12. Debit Units Response (Monetary Units)

13. Session released

Figure 5.2.2.2.3.1: ECUR - Centralized Unit Determination and Centralized Rating

1) Request for resource usage: The UE-A requests the desired content from the CTF.

2) Units Determination: depending on the service requested by the UE-A, the CTF determines the number of units
accordingly.

3) Rating Control: the CTF calculates the number of monetary units that represent the price for the number of 

units determined in item 2.

4) Reserve Units Request: the CTF requests the OCF to assure the reservation of an amount corresponding to the 

calculated number of monetary units from the subscriber's account.

5) Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation.

6) Reservation Control: if the user's credit balance is sufficient, then the corresponding reservation is made.

7) Reserve Units Response: the OCF informs the CTF of the reserved number of monetary units.

3GPP
Release 15 40 3GPP TS 32.299 V15.4.0 (2018-09)

8) Budget Control: simultaneously with the service delivery, the CTF monitors the consumption of the granted
amount.

9) Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually 

chargeable items, corresponding to the number of units.

10)Debit Units Request: the CTF requests the OCF to assure the deduction of an amount corresponding to the 

consumed number of monetary units from the subscriber's account.

11) Account Control: the OCF triggers the deduction of the consumed amount from the subscriber's account.

12)Debit Units Response: the OCF indicates to the CTF the number of deducted monetary units. 

13)Session Released: the session is released.

3GPP
Release 15 41 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.3 Session charging with Reservation

5.2.2.3.1 Decentralized Unit Determination and Centralized Rating

In scenario figure 5.2.2.3.1.1, the CTF requests the reservation of units prior to session supervision. An account debit
operation is carried out following the conclusion of session termination.

UE-A OCF CTF

1. Request for resource usage

2. Units
Determination

3. Reserve Units Request (Non-monetary Units)

4. Rating
Control

5. Account
Control

6.Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Reserved Units
Supervision

9. Session ongoing

10. Session released

11. Debit Units Request (Non-monetary Units)

12. Rating
Control

13. Account
Control
14. Debit Units Response (Non-monetary Units)

Figure 5.2.2.3.1.1: SCUR - Decentralized Unit Determination and Centralized Rating

1) Request for resource usage: The UE-A requests session establishment from the CTF.

2) Units Determination: depending on the requested type of the session the CTF determines the number of units
accordingly.

3) Reserve Units Request: the CTF requests the OCF to reserve the number of units determined in item 2

4) Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represents 

the price for the number of units determined in item 2.

3GPP
Release 15 42 3GPP TS 32.299 V15.4.0 (2018-09)

5) Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation.

6) Reservation Control: if the user's account balance is sufficient then the corresponding reservation is made.

7) Reserve Units Response: the OCF informs the CTF of the reserved number of units.

8) Reserved Units Supervision: simultaneously with the ongoing session, the CTF monitors the consumption of
the reserved units.

9) Session ongoing: the CTF maintains the session. One or more debit and reserve operations may be performed
when the session is ongoing.

10)Session Release: the session is released

11) Debit Units Request: the CTF requests the OCF to assure the deduction of an amount corresponding to the
consumed number of units from the subscriber's account.

12)Rating Control: assisted by the rating entity the OCF calculates the number of monetary units to deduct from
the subscriber's account.

13)Account Control: the OCF triggers the deduction of the calculated amount from the subscriber's account.

14)Debit Units Response: the OCF informs the CTF of the actually deducted units.

3GPP
Release 15 43 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.3.2 Centralized Unit Determination and Centralized Rating

In scenario figure 5.2.2.3.2.1, the CTF requests the OCF to reserve units based on the service key specified by the CTF.
An account debit operation is carried out following the conclusion of session.

UEa OCF CTF

1. Request for resource usage

2. Reserve Units Request (Service Key)

3. Units
Determination

4. Rating Control

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Granted Units
Supervision

9. Session ongoing

10. Session released

11. Debit Units Request (Non-monetary Units)

12. Rating
Control

13. Account
Control

14. Debit Units Response (Non-monetary Units)

Figure 5.2.2.3.2.1: SCUR - Centralized Unit Determination and Centralized Rating

1) Request for resource usage: The UE-A requests the session establishment from the CTF.

2) Reserve Units Request: depending on the requested type of the session by the UE-A, the CTF determines the
service key identifier and forwards the Reserve Un with service key its Request to the OCF.

3) Units Determination: the OCF determines the number of non­monetary units needed for the content/service 

delivery, based on the received service key.

4) Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represent the 

price for the number of units determined in item 3.

5) Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation.

3GPP
Release 15 44 3GPP TS 32.299 V15.4.0 (2018-09)

6) Reservation Control: if the user's account balance is sufficient, then the corresponding reservation is made.

7) Reserve Units Response: the OCF informs the CTF of the reserved number of units. This includes the case
where the number of units reserved indicates the permission to render the service that was identified by the
received service key.

8) Granted Units Supervision: simultaneously with the ongoing session, the CTF monitors the consumption of the
reserved units.

9) Session ongoing: the CTF maintains the session. One or more debit and reserve operations may be performed
when the session is ongoing.

10)Session Released: the session is released.

11) Debit Units Request: the CTF requests the OCF to assure the deduction of an amount corresponding to the
consumed number of units from the subscriber's account

12)Rating Control: assisted by the rating entity the OCF calculates the number of monetary units to deduct from
the subscriber's account.

13)Account Control: the OCF triggers the deduction of the calculated amount from the subscriber's account.

14)Debit Units Response: the OCF informs the CTF of the actually deducted units.

3GPP
Release 15 45 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.2.3.3 Decentralized Unit Determination and Decentralized Rating

In scenario figure 5.2.2.3.3.1, the CTF request the OCF to assure the reservation of an amount of the specified number
of monetary units from the subscriber's account. An account debit operation that triggers the deduction the amount from
the subscriber's account is carried out following the conclusion of session establishment.

UEa OCF CTF

1. Request for resource usage

2. Units
Determination

3. Rating Control

4. Reserve Units Request (Monetary Units)

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Monetary Units)

8. Budget
Control

9. Session ongoing

10. Session released

11. Debit Units Request (Monetary Units)

12. Account
Control
13. Debit Units Response (Monetary Units)

Figure 5.2.2.3.3.1: SCUR - Decentralized Unit Determination and Decentralized Rating

1) Request for resource usage: The UE-A requests the session establishment from the CTF.

2) Units Determination: depending on the requested type of the session by the UE-A, the CTF determines the
number of units accordingly.

3) Rating Control: the CTF calculates the number of monetary units that represent the price for the number of 

units determined in item 2.

4) Reserve Units Request: the CTF requests the OCF to assure the reservation of an amount corresponding to the 

calculated number of monetary units from the subscriber's account.

5) Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation.

6) Reservation Control: if the user's credit balance is sufficient, then the corresponding reservation is made.

7) Reserve Units Response: the OCF informs the CTF of the reserved number of monetary units.

3GPP
Release 15 46 3GPP TS 32.299 V15.4.0 (2018-09)

8) Budget Control: simultaneously with the ongoing session, the CTF monitors the consumption of the granted
amount.

9) Session ongoing: the CTF maintains the session. One or more debit and reserve operations may be performed
when the session is ongoing.

10)Session Released: the session is released.

11) Debit Units Request: the CTF requests the OCF to assure the deduction of an amount corresponding to the 

consumed number of monetary units from the subscriber's account.

12)Account Control: the OCF triggers the deduction of the consumed amount from the subscriber's account.

13)Debit Units Response: the OCF indicates to the CTF the number of deducted monetary units.

3GPP
Release 15 47 3GPP TS 32.299 V15.4.0 (2018-09)

5.2.3 Basic operations

Online Credit-Control uses two basic logical operations: Debit Units and Reserve Units.

- "Debit Units Request"; sent from CTF  OCF

After receiving a service request from the subscriber, the CTF sends a Debit Units Request to the OCF.
The CTF may either specify a service key (centralised unit determination) or the number of units requested
(decentralised unit determination).
For refund purpose, the CTF sends a Debit Units Request to the OCF as well.

- "Debit Units Response"; sent from OCF  CTF

The OCF replies with a Debit Units Response, which informs the CTF of the number of units granted as a result
of the Debit Units Request. This includes the case where the number of units granted indicates the permission to
render the requested service.
For refund purpose, the OCF replies with a Debit Units Response.

- "Reserve Units Request"; sent from CTF  OCF

Request to reserve a number of units for the service to be provided by an CTF. In case of centralized unit
determination, the CTF specifies a service key in the Reserve Unit Request, and the OCF determines the number
of units requested. In case of decentralised unit determination, the number of units requested is specified by the
CTF.

- "Reserve Units Response"; sent from OCF  CTF

Response from the OCF which informs the CTF of the number of units that were reserved as a result of the
"Reserve Units Request".

IEC uses the Direct Debiting One Time Event procedure specified in RFC 4006 [402] and therefore is performed by the
use of the logical "Debit Units" operation, as specified in clause 6.3.3.

SCUR and ECUR use both the "Debit Units" and "Reserve Units" operations.

SCUR uses the Session Based Credit-Control procedure specified in RFC 4006 [402]. In session charging with unit
reservation, when the "Debit Units" and "Reserve Units" operations are both needed, they shall be combined in one
message, as specified in clause 6.3.5.

For SCUR and ECUR the consumed units are deducted from the subscriber's account after service delivery.
Thus, the reserved and consumed units are not necessarily the same. Using this operation, it is also possible for the CTF
to modify the current reservation, including the return of previously reserved units.

Table 5.2.3.1 and table 5.2.3.2 describe the content of these operations.

3GPP
Release 15 48 3GPP TS 32.299 V15.4.0 (2018-09)

Table 5.2.3.1: Debit / Reserve Units Request content

Information Category Description

Element
Session Identifier M This field identifies the operation session.
Originator Host M This field contains the identification of the source point of the operation.
Originator Domain M This field contains the realm of the operation originator.
Destination Domain M This field contains the realm of the operation destination.
Operation Identifier M This field is a unique operation identifier.
Operation Token M This field contains the service identifier.
Operation Type M This field defines the transfer type: event for event based charging and start, interim,
stop for session based charging.
Operation Number M This field contains the sequence number of the transferred messages.
Destination Host OC This field contains the identification of the destination point of the operation.
User Name OC This field contains the identification of the user.
Origination State OC This field contains the state associated to the source point of the operation.
Origination OC This field contains the time when the operation is requested.
Timestamp
Subscriber Identifier OM This field contains the identification of the mobile subscriber (i.e. MSISDN) or the fixed
user (i.e. fixed device or residential gateway ) that uses the requested service.
Termination Cause OC This field contains the termination reason of the service.
Requested Action OC This field contains the requested action.
AoC Type OC This field denotes if AoC Information is requested and what type of information is
needed.
Multiple Operation OM This field indicate the occurrence of multiple operations.
Multiple Unit OC This field contains the parameter for the quota management.
Operation
Operation OC This field contains information to correlate messages generated for different
Correlation Identifier components of the service.
Subscriber OC This field contains the identification of the mobile device (i.e. IMEI) that uses the
Equipment Number subscriber.
Proxy Information OC This field contains the parameter of the proxy.
Route Information OC This field contains the parameter of the route.
Service Information OM This parameter holds the individual service specific parameters as defined in the
corresponding 'middle tier' TS.

3GPP
Release 15 49 3GPP TS 32.299 V15.4.0 (2018-09)

Table 5.2.3.2: Debit / Reserve Units Response content

Information Element Category Description

Session Identifier M This field identifies the operation session.
Operation Result M This field identifies the result of the operation.
Originator Host M This field contains the identification of the source point of the
operation.
Originator Domain M This field contains the realm of the operation originator.
Operation Identifier M This field is a unique operation identifier.
Operation Type M This field defines the transfer type: event for event based charging
and start, interim, stop for session based charging.
Operation Number M This field contains the sequence number of the transferred
messages.
Operation Failover OC This field contains an indication to the CTF whether or not a failover
handling is to be used when necessary.
Multiple Unit Operation OC This field contains the parameter for the quota management.
Cost Information OC This field contains the cost information of the service.
Low Balance Indication OC This field indicates whether the subscriber account balance went
below a designated threshold set by his account.
Remaining Balance OC This field contains the remaining balance of the subscriber.
Operation Failure Action OC For Credit-Control sessions the content of this field enables the
credit-control client to decide what to do if sending credit-control
messages to the credit-control server has been temporarily
prevented.
Operation Event Failure Action OC For one time event direct debiting the content of this field enables
the credit-control client to decide what to do if sending credit-control
messages to the credit-control server has been temporarily
prevented.
Redirection Host OC This field contains the host the request should be forwarded to.
Redirection Host Usage OC This field identifies the routing entry resulting from the Redirect-Host
is to be used.
Redirection Cache Time OC This field contains the maximum number of seconds the peer and
route table entries, created as a result of the Redirect-Host, will be
cached.
Proxy Information OC This field contains the parameter of the proxy.
Route Information OC This field contains the parameter of the route.
Failed parameter OC This field contains missing and/or unsupported parameter that
caused the failure.
Service Information OC This parameter holds the individual service specific parameters as
defined in the corresponding 'middle tier' TS.

3GPP
Release 15 50 3GPP TS 32.299 V15.4.0 (2018-09)

5.3 Other requirements

5.3.1 Re-authorization
The server may specify an idle timeout associated with a granted quota. Alternatively, the client may have a
configurable default value. The expiry of that timer shall trigger a re-authorization request.

Mid-session service events (re-authorization triggers) may affect the rating of the current service usage.
The server may instruct the Credit-Control client to re-authorize the quota upon a number of different session related
triggers that can affect the rating conditions.

When a re-authorization is trigger, the client shall reports quota usage. The reason for the quota being reported shall be
notified to the server.

5.3.2 Threshold based re-authorization triggers

The server may optionally include an indication to the client of the remaining quota threshold that shall trigger a quota
re-authorization.

5.3.3 Termination action

The server may specify to the client the behaviour on consumption of the final granted units, or zero units granted in the
first place; this is known as termination action.

5.3.4 Account expiration

The server may provide to the client the date and time of account expiration, which the client may use depending on
operator policy.

3GPP
Release 15 51 3GPP TS 32.299 V15.4.0 (2018-09)

6 3GPP charging applications – Protocol aspects

6.1 Basic principles for Diameter offline charging

6.1.0 Introduction
In order to support the offline charging principles described in the present document, the Diameter client and server
shall implement at least the following Diameter options listed in RFC 6733 [401], i.e. the basic functionality of
Diameter accounting, as defined by the Diameter Base Protocol (RFC 6733 [401]) is re-used.

The charging architecture implementing Diameter adheres to the structure where all communications for offline
charging purposes between the CTF (Diameter client) and the CDF (Diameter server) are carried out on the Diameter Rf
reference point, where the CTF reports charging information to the Charging Data Function (CDF). The CDF uses this
information to construct and format CDRs. The above-mentioned reference points are defined in TS 32.240 [1].

A configurable timer is supported in the CDF to supervise the reception of the ACR[Interim] and/or ACR[Stop]. An
instance of the "Timer" is started at the beginning of the accounting session, reset on the receipt of an ACR[Interim] and
stopped at the reception of the ACR[Stop]. Upon expiration of the timer, the CDF stops the accounting session with the
appropriate error indication.

For offline charging, the CTF implements the accounting state machine described in RFC 6733 [401].
The server (CDF) implements the accounting state machine "SERVER, STATELESS ACCOUNTING" as specified in
RFC 6733 [401], i.e. there is no order in which the server expects to receive the accounting information.

The offline charging functionality is based on the Network Elements reporting accounting information upon reception
of various messages which trigger charging generation, as most of the accounting relevant information is contained in
these messages. This reporting is achieved by sending Diameter Accounting Requests (ACR) [Start, Interim, Stop and
Event] from the Network Elements to the CDF.

Following the Diameter base protocol specification, the following "types" of accounting data may be sent with regard to
offline charging:

 START session accounting data.

 INTERIM session accounting data.

 STOP session accounting data.

 EVENT accounting data.

Two cases are currently distinguished for offline charging purposes:

 Event based charging; and

 Session based charging.

ACR types START, INTERIM and STOP are used for accounting data related to successful sessions. In contrast,
EVENT accounting data is unrelated to sessions, and is used e.g. for a simple registration or interrogation and
successful service event triggered by a Network Element. In addition, EVENT accounting data is also used for
unsuccessful session establishment attempts.

The flows and scenarios for the above two described cases are further detailed below.

3GPP
Release 15 52 3GPP TS 32.299 V15.4.0 (2018-09)

6.1.1 Event based charging

In the case of event based charging, the network reports the usage or the service rendered where the service offering is
rendered in a single operation. It is reported using the ACR[Event].

Figure 6.1.1.1 shows the transactions that are required on the Diameter offline interface in order to perform event based
charging. The operation may alternatively be carried out prior to, concurrently with or after service/content delivery.

CTF CDF/
Server

1. Service Delivery

Event Based Charging

2. ACR[EVENT_RECORD]

3. Process Accounting Request

4. ACA[EVENT_RECORD]

Figure 6.1.1.1: Event based offline charging

Step 1:The Network Element receives indication that service has been used/delivered.

Step 2:The Network Element (acting as client) sends Accounting-Request (ACR) with Accounting-Record-Type
AVP set to EVENT_RECORD to indicate service specific information to the CDF (acting as server).

Step 3:The CDF receives the relevant service charging parameters and processes accounting request.

Step 4:The CDF returns Accounting-Answer message with Accounting-Record-Type AVP set to EVENT_RECORD
to the Network Element in order to inform that charging information was received.

3GPP
Release 15 53 3GPP TS 32.299 V15.4.0 (2018-09)

6.1.2 Session based charging

Session based charging is the process of reporting usage reports for a session and uses the START, INTERIM and STOP
accounting data. During a session, a Network Element may transmit multiple ACR Interims' depending on the
proceeding of the session.

Figure 6.1.2.1 shows the transactions that are required on the Diameter offline interface in order to perform session
based charging.

CTF CDF

1. Service Request

Start accounting session

2. ACR[START_RECORD]

3. Open CDR

4. ACA[START_RECORD, AII]

AII timer or
change of
charging
condition Interim interval elapses

5. ACR[INTERIM_RECORD]

6. Update CDR

7. ACA[INTERIM_RECORD]

8. Service Termination

Close accounting session

9. ACR (STOP_RECORD)
Figure 6.1.2.1: Session based offline charging
10. Close CDR
Step 1:The Network Element receives a service request. The service request may be initiated either by the user or
the other Network Element.
11. ACA[STOP_RECORD]
Step 2:In order to start accounting session, the Network Element sends a Accounting-Request (ACR) with
Accounting-Record-Type AVP set to START_RECORD to the CDF.

Step 3:The CDF opens a CDR for current session.

Step 4:The CDF returns Accounting-Answer (ACA) message with Accounting-Record-Type set to
START_RECORD to the Network Element and possibly Acct-Interim-Interval AVP (AII) set to non-zero
value indicating the desired intermediate charging interval.

Step 5:When either AII elapses or charging conditions changes are recognized at Network Element (NE), the NE
sends an Accounting-Request (ACR) with Accounting-Record-Type AVP set to INTERIM_RECORD to the
CDF.

Step 6:The CDF updates the CDR in question.

3GPP
Release 15 54 3GPP TS 32.299 V15.4.0 (2018-09)

Step 7:The CDF returns Accounting-Answer (ACA) message with Accounting-Record-Type set to
INTERIM_RECORD to the Network Element.

Step 8:The service is terminated.

Step 9:The Network Element sends a Accounting-Request (ACR) with Accounting-Record-Type AVP set to
STOP_RECORD to the CDF.

Step 10: The CDF updates the CDR accordingly and closes the CDR.

Step 11: The CDF returns Accounting-Answer (ACA) message with Accounting-Record-Type set to
STOP_RECORD to the Network Element.

3GPP
Release 15 55 3GPP TS 32.299 V15.4.0 (2018-09)

6.1.3 Offline charging error cases - Diameter procedures

6.1.3.1 CDF connection failure

When the connection towards the primary CDF is broken, the process of sending accounting information should
continue towards a secondary CDF (if such a CDF is configured). For further CDF connection failure functionality, see
clause "Transport Failure Detection" in the RFC 6733 [401].

If no CDF is reachable the Network Element may buffer the generated accounting data in non-volatile memory. Once
the CDF connection is working again, all accounting messages stored in the buffer is sent to the CDF, in the order they
were stored in the buffer.

6.1.3.2 No reply from CDF

In case a Network Element does not receive an ACA in response to an ACR, it may retransmit the ACR message. The
waiting time until a retransmission is sent, and the maximum number of repetitions are both configurable by the
operator. When the maximum number of retransmissions is reached and still no ACA reply has been received, the
Network Element executes the CDF connection failure procedure as specified above.

If retransmitted ACRs' are sent, they are marked with the T-flag as described in RFC 6733 [401], in order to allow
duplicate detection in the CDF, as specified in the next clause 6.1.3.3.

6.1.3.3 Duplicate detection

A Diameter client marks possible duplicate request messages (e.g. retransmission due to the link fail over process) with
the T-flag as described in RFC 6733 [401].

If the CDF receives a message that is marked as retransmitted and this message was already received, then it discards
the duplicate message. However, if the original of the re-transmitted message was not yet received, it is the information
in the marked message that is taken into account when generating the CDR. The CDRs are marked if information from
duplicated message(s) is used.

6.1.3.4 CDF detected failure

The CDF closes a CDR when it detects that expected Diameter ACRs for a particular session have not been received for
a period of time. The exact behaviour of the CDF is operator configurable.

3GPP
Release 15 56 3GPP TS 32.299 V15.4.0 (2018-09)

6.2 Message contents for offline charging

6.2.1 Summary of offline charging message formats

6.2.1.1 General
The corresponding Diameter accounting application messages for the Charging Data Transfer operation is Accounting-
Request (ACR) and Accounting-Answer (ACA) as specified in the Diameter Base Protocol Accounting (DBPA)
application in RFC 6733 [401].

Table 6.2.1.1.1 describes the use of these messages which are adapted for 3GPP offline charging.

Table 6.2.1.1.1: Offline charging messages reference table

Command-Name Source Destination Abbreviation

Accounting-Request CTF CDF ACR
Accounting-Answer CDF CTF ACA
Capabilities-Exchange- CTF CDF CER
Request
Capabilities-Exchange-Answer CDF CTF CEA

Additional Diameter messages (i.e. DPR/DPA, DWR/DWA)are used according to the Diameter Base Protocol
Accounting (DBPA) specification in RFC 6733 [401].

6.2.1.2 Structure for the Accounting message formats

The following is the basic structure shared by all offline charging messages. This is based directly on the format of the
messages defined in the Diameter Base Protocol Application specification in RFC 6733 [401].

Those Diameter Accounting AVPs that are used for 3GPP offline charging are marked in table 6.2.2.1 and table 6.2.3.1
with a category as specified in TS 32.240 [1].

An AVP in grey strikethrough in the message format (in grey in the tables) is not used by 3GPP.

The following symbols are used in the message format definition:

- <AVP> indicates a mandatory AVP with a fixed position in the message.

- {AVP} indicates a mandatory AVP in the message.

- [AVP] indicates an optional AVP in the message.

- *AVP indicates that multiple occurrences of an AVP is possible.

3GPP
Release 15 57 3GPP TS 32.299 V15.4.0 (2018-09)

6.2.2 Accounting-Request message

The ACR messages, indicated by the Command-Code field set to 271 is sent by the CTF to the CDF in order to send
charging information for the requested bearer / subsystem /service.

The ACR message format is defined according to the Diameter Base Protocol in RFC 6733 [401] as follows:
<ACR> ::= < Diameter Header: 271, REQ, PXY >

< Session-Id >

{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ User-Name ]
[ Destination-Host ]
[ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Acct-Interim-Interval ]
[ Accounting-Realtime-Required ]
[ Origin-State-Id ]
[ Event-Timestamp ]
* [ Proxy-Info ]
* [ Route-Record ]
[ Service-Context-Id ]
[ Service-Information ]
* [ AVP ]

NOTE: Similar information as in subscription_id should be added as 3GPP parameter, IMEI.

3GPP
Release 15 58 3GPP TS 32.299 V15.4.0 (2018-09)

Table 6.2.2.1 illustrates the basic structure of a 3GPP Diameter Accounting-Request message as used for 3GPP offline
charging.

Table 6.2.2.1: 3GPP Accounting-Request message contents

AVP Category Description

Session-Id M This field identifies the operation session.
Origin-Host M This field contains the identification of the source point of the
operation and the realm of the operation originator.
Origin-Realm M This field contains the realm of the operation originator.
Destination-Realm M This field contains the realm of the operator domain. The realm will
be addressed with the domain address of the corresponding public
URI.
Accounting-Record-Type M This field defines the transfer type: event for event based charging
and start, interim, stop for session based charging.
Accounting-Record-Number M This field contains the sequence number of the transferred
messages.
Acct-Application-Id OM The field corresponds to the application ID of the Diameter
Accounting Application and is defined with the value 3.
Vendor-Specific-Application-Id - Not used in 3GPP.
Vendor-Id - Not used in 3GPP.
Auth-Application-Id - Not used in 3GPP.
Acct-Application-Id - Not used in 3GPP.
User-Name OC Contains the user name determined by the domain: bearer, sub-
system or service as described in middle tier TS.
Destination-Host OC This field contains the destination address of the CDF.
Accounting-Sub-Session-Id - Not used in 3GPP.
Accounting-Session-Id - Not used in 3GPP.
Acct-Multi-Session-Id - Not used in 3GPP.
Acct-Interim-Interval OC This field contains the proposal for instructions to produce records
continuously during a session.
Accounting-Realtime-Required - Not used in 3GPP.
Origin-State-Id OC This field contains the state associated to the CTF.
Event-Timestamp OC This field corresponds to the exact time the accounting is requested.
Proxy-Info OC This field contains information of the host.
Proxy-Host M This field contains the identity of the host that added the Proxy-Info
field.
Proxy-State M This field contains state local information.
Route-Record Oc This field contains an identifier inserted by a relaying or proxying
node to identify the node it received the message from.
OM This field indicates the service and the corresponding 'middle tier'
Service-Context-Id
TS.
Service-Information OM This parameter holds the individual service specific parameters as
defined in the corresponding 'middle tier' TS.
AVP Oc This field contains extended Information.

NOTE: A detailed description of the AVPs is provided in clause 7.

3GPP
Release 15 59 3GPP TS 32.299 V15.4.0 (2018-09)

6.2.3 Accounting-Answer (ACA) message

The ACA messages, indicated by the Command-Code field set to 271 is sent by the CDF to the CTF in order to reply to
the ACR.

The ACA message format is defined according to the Diameter Base Protocol in RFC 6733 [401] as follows:
<ACA> ::= < Diameter Header: 271, PXY >

< Session-Id >

{ Result-Code }
[ Experimental-Result ]
{ Origin-Host }
{ Origin-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ User-Name ]
[ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
[ Acct-Interim-Interval ]
[ Failed-AVP ]
[ Accounting-Realtime-Required ]
[ Origin-State-Id ]
[ Event-Timestamp ]
* [ Proxy-Info ]
* [ AVP ]

3GPP
Release 15 60 3GPP TS 32.299 V15.4.0 (2018-09)

Table 6.2.3.1 illustrates the basic structure of a 3GPP Diameter Accounting-Answer message as used for offline
charging. This message is always used by the CDF as specified below, regardless of the CTF it is received from and the
ACR record type that is being replied to.

Table 6.2.3.1: 3GPP Accounting-Answer (ACA) message content

AVP Category Description

Session-Id M This field identifies the operation session.
Result-Code M This field contains the result of the specific query.
Experimental-Result OC This field contains the Experimental result of the specific query.
Origin-Host M This field contains the identification of the source point of the
operation and the realm of the operation originator.
Origin-Realm M This field contains the realm of the operation originator.
Accounting-Record-Type M This field defines the transfer type: event for event based charging
and start, interim, stop for session based charging.
Accounting-Record-Number M This field contains the sequence number of the transferred
messages.
Acct-Application-Id OM The field corresponds to the application ID of the Diameter
Accounting Application and is defined with the value 3.
Vendor-Specific-Application-Id - Not used in 3GPP
Vendor-Id - Not used in 3GPP
Auth-Application-Id - Not used in 3GPP
Acct-Application-Id - Not used in 3GPP
User-Name OC Contains the user name determined by the domain: bearer, sub-
system or service as described in middle tier TS.
Accounting-Sub-Session-Id - Not used in 3GPP
Accounting-RADIUS-Session-Id - Not used in 3GPP
Acct-Multi-Session-Id - Not used in 3GPP
Error-Message OC This field contains a human readable error message.
Error-Reporting-Host OC This field contains the identity of the Diameter host that sent the
Result-Code AVP to a value other than 2001 (Success) if the host
setting the Result-Code is different from the one encoded in the
Origin-Host AVP.
Acct-Interim-Interval OC This field contains the instructions to produce records continuously
during a session.
Accounting-Realtime-Required - Not used in 3GPP
Failed-AVP OC This field contains the AVP that could not be processed sucessfully.
This field can occur only once.
Origin-State-Id OC This field contains the state associated to the source point of the
operation.
Event-Timestamp OC This field contains the time when the operation is requested.
Proxy-Info OC This field contains information of the host.
Proxy-Host M This field contains the identity of the host that added the Proxy-Info
field.
Proxy-State M This field contains state local information.
AVP OC This field contains extended Information.

3GPP
Release 15 61 3GPP TS 32.299 V15.4.0 (2018-09)

6.3 Basic principles for Diameter online charging

6.3.1 Online Specific Credit-Control application requirements
For online charging, the basic functionality as defined by the IETF Diameter Credit-Control Application is used.
The basic structure follows a mechanism where the online client (CTF) requests resource allocation and reports Credit-
Control information to the Online Charging System (OCS).

The usage and values of Validity-Time AVP and the timer "Tcc" are under the sole control of the Credit-Control server
(OCS) and determined by operator configuration of the OCS.

The online client implements the state machine described in RFC 4006 [402] for "CLIENT, EVENT BASED" and/or
"CLIENT, SESSION BASED". I.e. when the client applies IEC it uses the "CLIENT, EVENT BASED" state machine,
and when the client applies ECUR defined in 3GPP it uses the "CLIENT, SESSION BASED" state machine for the first
and final interrogations.

The OCS implements the state machine described in RFC 4006 [402] for the "SERVER, SESSION AND EVENT
BASED" in order to support Immediate Event Charging and Event Charging with Unit Reservation.

6.3.2 Diameter description on the Ro reference point

6.3.2.1 Basic principles

For online charging the Diameter Credit-Control Application (DCCA) defined in RFC 4006 [402] is used with
additional AVPs defined in the present document.

Three cases for control of user credit for online charging are distinguished:

- Immediate Event Charging IEC; and

- Event Charging with Unit Reservation (ECUR).

- Session Charging with Unit Reservation (SCUR)

In the case of Immediate Event Charging (IEC),the Credit-Control process for events is controlled by the corresponding
CC-Requested-Type EVENT_REQUEST that is sent with Credit-Control-Request (CCR) for a given Credit-Control
event.

In the case of Event Charging with Unit Reservation (ECUR) the CC-Request-Type INITIAL /
TERMINATION_REQUEST are used for charging for a given Credit-Control event, however, where a reservation is
made prior to service delivery and committed on execution of a successful delivery.

Session Charging with Unit Reservation is used for Credit-Control of sessions and uses the CC-Request-Type INITIAL /
UPDATE and TERMINATION_REQUEST.

The Network Element may apply IEC, where CCR Event messages are generated, or ECUR, using CCR Initial and
Termination. The decision whether to apply IEC or ECUR is based on the service and/or operator's policy.

3GPP
Release 15 62 3GPP TS 32.299 V15.4.0 (2018-09)

6.3.3 Immediate Event Charging (IEC)

Figure 6.3.3.1 shows the transactions that are required on the Ro reference point in order to perform event based Direct
Debiting operation. The Direct Debiting operation may alternatively be carried out prior to service/content delivery.
The Network Element shall ensure that the requested service execution is successful, when this scenario is used.

CTF OCS

1. Service Request

Direct Debiting operation

2. CCR[EVENT_REQUEST, RA, RSU]

4. Perform Direct
3. Timer Tx Debiting

5. CCA[EVENT_REQUEST, GSU, [CI], [RI]]

6. Service Delivery

Figure 6.3.3.1: IEC - Direct Debiting operation

Step 1.The Network Element receives a service request.

The Direct Debiting operation is performed as described in RFC 4006 [402].

Step 2.The Network Element performs direct debiting prior to service execution. Network element (acting as DCCA
client) sends CCR with CC-Request-Type AVP set to EVENT_REQUEST to indicate service specific
information to the OCS (acting as DCCA server). The Requested-Action AVP (RA) is set to
DIRECT_DEBITING. If known, the Network Element may include Requested-Service-Unit AVP (RSU)
(monetary or non-monetary units) in the request message.

Step 3.Having transmitted the CCR message the Network Element starts the communication supervision timer 'Tx'
(RFC 4006 [402]). Upon receipt of the Credit-Control- Answer (CCA) message the Network Element shall
stop timer Tx.

Step 4.The OCS determines the relevant service charging parameters.

Step 5.The OCS returns CCA message with CC-Request-Type AVP set to EVENT_REQUEST to the Network
Element in order to authorize the service execution
(Granted-Service-Unit AVP (GSU) and possibly Cost-Information AVP (CI) indicating the cost of the service
and Remaining-Balance AVP are included in the CCA message).
The CCA message has to be checked by the Network Element accordingly and the requested service is
controlled concurrently with service delivery. The Refund-Information AVP may be included in the CCA
message in order to be sent during the REFUND-ACCOUNT mechanism, see below scenario.

Step 6.Service is being delivered.

3GPP
Release 15 63 3GPP TS 32.299 V15.4.0 (2018-09)

NOTE: It is possible to perform also, CHECK_BALANCE and PRICE_ENQUIRY using above described
mechanism RFC 4006 [402].

Figure 6.3.3.2 shows the transactions for refund purpose.

CTF OCS

1. Service unsuccessful

Refund account operation

2. CCR[EVENT_REQUEST, RA, [RI]]

4. Perform
3. Timer Tx Refund

5. CCA[EVENT_REQUEST]

Figure 6.3.3.2: IEC - Direct Debiting operation for refund purpose

The Direct debiting operation is performed, previously, as described in RFC 4006 [402].

Step 1.The service charged previously through Direct Debiting Operation is finally proved to be unsuccessfully
delivered.

Step 2.As a consequence, the Network Element performs direct debiting operation in order to perform the related
refund. Network element (acting as DCCA client) sends CCR with CC-Request-Type AVP set to
EVENT_REQUEST to indicate service specific information to the OCS (acting as DCCA server). The
Requested-Action AVP (RA) is set to REFUND-ACCOUNT.
The Network Element includes Refund-Information AVP if received in the previous IEC CCA.

Step 3.Having transmitted the CCR message the Network Element starts the communication supervision timer 'Tx'
(RFC 4006 [402]). Upon receipt of the Credit-Control- Answer (CCA) message the Network Element shall
stop timer Tx.

Step 4.The OCS reads the AVPs included in the CCR and performs the refund accordingly.

Step 5.The OCS returns CCA message with CC-Request-Type AVP set to EVENT_REQUEST and the related result
code.

3GPP
Release 15 64 3GPP TS 32.299 V15.4.0 (2018-09)

6.3.4 Event Charging with Unit Reservation (ECUR)

Figure 6.3.4.1 shows the transactions that are required on the Ro reference point in order to perform the ECUR. ECUR
is used when event charging needs separate reserve and commit actions.

CTF OCS

1. Service Request

Reserve Units operation

2. CCR[INITIAL_REQUEST, RSU]

3. Perfor m
Charging Control

4. CCA[INITIAL_REQUEST, GSU, [VT]]

5. Service Delivery

Debit Units operation

6. CCR[TERMINATION_REQUEST, USU]

7.. Perform Charging Control

8. CCA[TERMINATION_REQUEST, CI]

Figure 6.3.4.1: ECUR - Session based Credit-Control

Step 1.The Network Element receives a service request. The service request may be initiated either by the user or
the other Network Element.

Step 2.In order to perform Reserve Units operation for a number of units (monetary or non-monetary units), the
Network Element sends a CCR with CC-Request-Type AVP set to INITIAL_REQUEST to the OCS. If
known, the Network Element may include Requested-Service-Unit (RSU) AVP (monetary or non monetary
units) in the request message.

Step 3.If the service cost information is not received by the OCS, the OCS determines the price of the desired
service according to the service specific information received by issuing a rating request to the Rating
Function. If the cost of the service is included in the request, the OCS directly reserves the specified
monetary amount. If the credit balance is sufficient, the OCS reserves the corresponding amount from the
users account.

Step 4.Once the reservation has been made, the OCS returns CCA message with CC-Request-Type set to
INITIAL_REQUEST to the Network Element in order to authorize the service execution (Granted-Service-
Unit and possibly Cost-Information indicating the cost of the service and Remaining-Balance AVP are
included in the CCA message). The OCS may return the Validity-Time (VT) AVP with value field set to a
non-zero value. The OCS may indicate in the Low-Balance-Indication AVP that the subscriber account
balance has fallen below a predefined treshold of this account.

Step 5.Content/service delivery starts and the reserved units are concurrently controlled.

Step 6.When content/service delivery is completed, the Network Element sends CCR with CC-Request-Type AVP
set to TERMINATION_REQUEST to terminate the active Credit-Control session and report the used units.

Step 7.The OCS deducts the amount used from the account. Unused reserved units are released, if applicable.

3GPP
Release 15 65 3GPP TS 32.299 V15.4.0 (2018-09)

Step 8.The OCS acknowledges the reception of the CCR message by sending CCA message with CC-Request-Type
AVP indicating TERMINATION_REQUEST (possibly Cost-Information AVP indicating the cumulative cost
of the service and Remaining-Balance AVP are included in the CCA message).

NOTE: This scenario is supervised by corresponding timers (e.g. validity time timer) that are not shown in the
figure 6.3.4.1.

3GPP
Release 15 66 3GPP TS 32.299 V15.4.0 (2018-09)

6.3.5 Session Charging with Unit Reservation (SCUR)

Figure 6.3.5.1 shows the transactions that are required on the Ro reference point in order to perform the SCUR.

CTF OCS/

1. Session Request

Reserve Units operation

2. CCR[INITIAL_REQUEST, RSU]

3. Perfor m
Charging Control

4. CCA[INITIAL_REQUEST, GSU, [VT]]

5. Session Delivery

Reserve Units and Debit Units operations

6. CCR[UPDATE_REQUEST, RSU, USU]

7. Perform Charging Control

8. CCA[UPDATE_REQUEST, GSU, [FUI]]

9. Session Delivery

10. Session Terminate

Debit Units operation

11. CCR[TERMINATION_REQUEST, USU]

12. Perform Charging Control

13. CCA[TERMINATION_REQUEST, CI]

Figure 6.3.5.1: SCUR - Session based CCredit-Control

Step 1.The Network Element receives a session initiation. The session initiation may be done either by the user or
the other Network Element.

Step 2.In order to perform Reserve Units operation for a number of units (monetary or non-monetary units), the
Network Element sends a CCR with CC-Request-Type AVP set to INITIAL_REQUEST to the OCS. If
known, the Network Element may include Requested-Service-Unit (RSU) AVP (monetary or non monetary
units) in the request message.

Step 3.If the service cost information is not received by the OCS, the OCS determines the price of the desired
service according to the service specific information received by issuing a rating request to the Rating
Function. If the cost of the service is included in the request, the OCS directly reserves the specified
monetary amount. If the credit balance is sufficient, the OCS reserves the corresponding amount from the
users account.

Step 4.Once the reservation has been made, the OCS returns CCA message with CC-Request-Type set to
INITIAL_REQUEST to the Network Element in order to authorize the service execution (Granted-Service-
Unit and possibly Cost-Information indicating the cost of the service and Remaining-Balance AVP are
included in the CCA message). The OCS may return the Validity-Time (VT) AVP with value field set to a
non-zero value. The OCS may indicate in the Low-Balance-Indication AVP that the subscriber account
balance has fallen below a predefined threshold of this account.

3GPP
Release 15 67 3GPP TS 32.299 V15.4.0 (2018-09)

Step 5.Content/service delivery starts and the reserved units are concurrently controlled.

Step 6.During session delivery, in order to perform Debit Units and subsequent Reserve Units operations, the
Network Element sends a CCR with CC-Request-Type AVP set to UPDATE_REQUEST, to report the units
used and request additional units, respectively. The CCR message with CC-Request-Type AVP set to
UPDATE_REQUEST shall be sent by the Network Element between the INITIAL_REQUEST and
TERMINATION_REQUEST either on request of the Credit-Control application within the validity time or if
the validity time is elapsed. If known, the Network Element may include Requested-Service-Unit AVP
(monetary or non monetary units) in the request message. The Used-Service-Unit (USU) AVP is
complemented in the CCR message to deduct units from both the user's account and the reserved units,
respectively.

Step 7.The OCS deducts the amount used from the account. If the service cost information is not received by the
OCS, the OCS determines the price of the desired service according to the service specific information
received by issuing a rating request to the Rating Function. If the cost of the service is included in the
request, the OCS directly reserves the specified monetary amount. If the credit balance is sufficient, the OCS
reserves the corresponding amount from the users account.

Step 8.Once the deduction and reservation have been made, the OCS returns CCA message with CC-Request-Type
set to UPDATE_REQUEST to the Network Element, in order to allow the content/service delivery to
continue (new Granted-Service-Unit (GSU) AVP and possibly Cost-Information (CI) AVP indicating the
cumulative cost of the service and Remaining-Balance AVP are included in the CCA message). The OCS
may include in the CCA message the Final-Unit-Indication (FUI) AVP to indicate the final granted units. The
OCS may indicate in the Low-Balance-Indication AVP that the subscriber account balance has fallen below a
predefined threshold of this account.

Step 9.Session delivery continues and the reserved units are concurrently controlled.

Step 10. The session is terminated at the Network Element.

Step 11. The Network Element sends CCR with CC-Request-Type AVP set to TERMINATION_REQUEST to
terminate the active Credit-Control session and report the used units.

Step 12. The OCS deducts the amount used from the account. Unused reserved units are released, if applicable.

Step 13. The OCS acknowledges the reception of the CCR message by sending CCA message with CC-Request-
Type AVP indicating TERMINATION_REQUEST (possibly Cost-Information AVP indicating the cumulative
cost of the service and Remaining-Balance AVP are included in the CCA message).

NOTE: This scenario is supervised by corresponding timers (e.g. validity time timer) that are not shown in figure
6.3.5.1.

3GPP
Release 15 68 3GPP TS 32.299 V15.4.0 (2018-09)

6.3.6 Error cases and scenarios

6.3.6.0 Introduction
This clause describes various error cases and how these should be handled.

The failure handling behaviour is locally configurable in the Network Element. If the Direct-Debiting-Failure-Handling
or Credit-Control-Failure-Handling AVP is not used, the locally configured values are used instead.

6.3.6.1 Duplicate detection

The detection of duplicate request is needed and shall be enabled. To speed up and simplify as much as possible the
duplicate detection, the all-against-all record checking should be avoided and just those records marked as potential
duplicates need to be checked against other received requests (in real-time ) by the receiver entity.

The Network Element marks the request messages that are retransmitted after a link fail over as possible duplicates with
the T-flag as described in RFC 6733 [401]. For optimized performance, uniqueness checking against other received
requests is only necessary for those records marked with the T-flag received within a reasonable time window. This
focused check is based on the inspection of the Session-Id and CC-Request-Number AVP pairs.

Note that for EBCC the duplicate detection is performed in the Correlation Function that is part of the OCS.
The OCS that receives the possible duplicate request should mark as possible duplicate the corresponding request that is
sent over the 'Rc' reference point. However, this assumption above is for further study and needs to be clarified.

For Credit-Control duplicate detection, please refer to the Diameter Credit-Control.

6.3.6.2 Reserve Units / Debit Units operation failure

In the case of an OCS connection failure, and/or receiving error responses from the OCS, please refer to
RFC 6733 [401] and RFC 4006 [402] for failure handling descriptions.

6.3.7 Support of tariff changes during an active user session

6.3.7.1 Support of tariff changes using the tariff switch mechanism

After a tariff switch has been reached, all the active user sessions shall report their session usage by the end of the
validity period of the current request and receive new quota for resource usage for the new tariff period.

In order to avoid the need for mass simultaneous quota refresh, the traffic usage can be split into resource usage before a
tariff switch and resources used after a tariff switch.

The Tariff-Time-Change AVP is used to determine the tariff switch time as described by RFC 4006 [402].
In addition to the scenarios described in RFC 4006 [402], the Tariff-Time-Change AVP may also be used in the context
of continuously time-based charging.

The Tariff-Change-Usage AVP is used within the Used-Service-Units AVP to distinguish reported usage before and after
the tariff time change.

The Tariff-Change-Usage AVP is not used directly within the Multiple-Services-Credit-Control AVP.

6.3.7.2 Support of tariff changes using Validity-Time AVP

Changes to the tariffs pertaining to the service during active user sessions may also be handled using the Validity Time
AVP.

NOTE: RFC 4006 [402] does not directly describe how tariff changes are handled with validity time.
If validity time is used for tariff time changes it might overload the client and the server.

3GPP
Release 15 69 3GPP TS 32.299 V15.4.0 (2018-09)

6.3.8 Support of re-authorization

Mid Diameter CC session re-authorizations of multiple active resource quotas within a DCC session can be achieved
using a single Diameter Credit-Control- Request/ Credit-Control- Answer message sequence.

The OCS may also re-authorize multiple active resource quotas within a DCC session by using a single Diameter Re-
Auth-Request/Answer message sequence.

New quota allocations received by the Network Element override any remaining held quota resources after accounting
for any resource usage while the re-authorization was in progress.

6.3.9 Support of failure handling

The Credit-Control-Failure-Handling AVP as defined in RFC 4006 [402] determines what to do if the sending of
Diameter credit-control messages to the OCS has been temporarily prevented. The usage of Credit-Control-Failure-
Handling AVP gives flexibility to have different failure handling for credit-control session.

This AVP may be received from the OCS or may be locally configured. The value received from the OCS in the
Diameter CCA message always override any already existing value.

As defined in RFC 4006 [402], the Tx timer is introduced to limit the waiting time in the CTF for an answer to the CCR
sent to the OCS. When the Tx timer elapses the CTF takes an action to the end user according to the value of the Credit-
Control-Failure-Handling AVP.

It is possible that several concurrent CCR messages are triggered for the same online charging session. In this case, each
CCR message shall reset the Tx timer as defined in RFC 4006 [402].

6.3.10 Support of failover

As defined in RFC 4006 [402] if a failure occurs during an ongoing credit-control session, the CTF may move the
Credit-Control message stream to an alternative OCS if the primary OCS indicated FAILOVER_SUPPORTED in the
CC-Session-Failover AVP. In case CC-Session-Failover AVP is set to FAILOVER_NOT SUPPORTED the Credit-
Control message stream is not moved to a backup OCS.

For new Credit-Control sessions, failover to an alternative OCS should be performed if possible. For instance, if an
implementation of the CTF can determine primary OCS unavailability it can establish the new Credit-Control sessions
with a possibly available secondary OCS.

Since the OCS has to maintain session states, moving the credit-control message stream to a backup OCS requires a
complex charging context transfer solution. This charging context transfer mechanism by OCS is out of the scope of
the 3GPP standardization work.

6.3.11 Credit pooling

Credit pooling shall be supported as described in TS 32.240 [1].

NOTE: Credit pooling is not applicable to IEC since there is no quota management between CTF and OCF.

3GPP
Release 15 70 3GPP TS 32.299 V15.4.0 (2018-09)

6.4 Message formats for online charging

6.4.1 Summary of online charging message formats

6.4.1.1 General
The corresponding Diameter Credit-Control application messages for the Debit / Reserve Unit Request operation is
Credit-Control-Request (CCR) and for the Debit / Reserve Unit Response operation is Credit-Control-Answer (CCA) as
specified in RFC 4006 [402].

The Diameter Credit-Control Application (DCCA) specifies an approach based on a series of "interrogations":

1. Initial interrogation.

2. Zero, one or more interim interrogations.

3. Final interrogation.

In addition to a series of interrogations, also a one time event (interrogation) can be used e.g. in the case when service
execution is always successful.

All of these interrogations use CCR and CCA messages. The CCR for the "interim interrogation" and "final
interrogation" reports the actual number of "units" that were used, from what was previously reserved. This determines
the actual amount debited from the subscriber's account.

Table 6.4.1.1.1 describes the use of these Diameter messages which are adapted for 3GPP online charging.

Table 6.4.1.1.1: Online charging messages reference table

Command-Name Source Destination Abbreviation

Credit-Control-Request CTF OCS CCR
Credit-Control-Answer OCS CTF CCA
Capabilities-Exchange-Request CTF OCS CER
Capabilities-Exchange-Answer OCS CTF CEA

Additional Diameter messages (i.e. ASR/ASA, DPR/DPA, DWR/DWA, RAR/RAA) are used according to the Diameter
Base Protocol Accounting (DBPA) specification in RFC 6733 [401] and to the DCCA specification in RFC 4006 [402].

6.4.1.2 Structure for the Credit-Control message formats

The following is the basic structure shared by all online charging messages. This is based directly on the format of the
messages defined in RFC 4006 [402].

Those Diameter accounting AVPs that are used for 3GPP online charging are marked in the table of contents 6.4.2 and
6.4.3 with a category as specified in TS 32.240 [1].

In the definition of the Diameter commands, the AVPs that are specified in the referenced specifications but not used by
the 3GPP charging specifications are marked with strikethrough, e.g. [ Acct-Multi-Session-Id ].

The following symbols are used in the message format definitions:

- <AVP> indicates a mandatory AVP with a fixed position in the message.

- {AVP} indicates a mandatory AVP in the message.
- [AVP] indicates an optional AVP in the message.
- *AVP indicates that multiple occurrences of an AVP is possible.

3GPP
Release 15 71 3GPP TS 32.299 V15.4.0 (2018-09)

6.4.2 Credit-Control-Request message

The CCR messages, indicated by the Command-Code field set to 272 is sent by the CTF to the OCF in order to request
credits for the request bearer / subsystem /service.

The CCR message format is defined according to RFC 4006 [402] as follows:
<CCR> ::= < Diameter Header: 272, REQ, PXY >

< Session-Id >

{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Application-Id }
{ Service-Context-Id }
{ CC-Request-Type }
{ CC-Request-Number }
[ Destination-Host ]
[ User-Name ]
[ CC-Sub-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Origin-State-Id ]
[ Event-Timestamp ]
*[ Subscription-Id ]
[ Service-Identifier ]
[ Termination-Cause ]
[ Requested-Service-Unit ]
[ Requested-Action ]
*[ Used-Service-Unit ]
[ AoC-Request-Type ]
[ Multiple-Services-Indicator ]
*[ Multiple-Services-Credit-Control ]
*[ Service-Parameter-Info ]
[ CC-Correlation-Id ]
[ User-Equipment-Info ]
[ OC-Supported-Features ]
*[ Proxy-Info ]
*[ Route-Record ]
[ Service-Information ]
*[ AVP ]

Table 6.4.2.1 illustrates the basic structure of a 3GPP Diameter CCR message as used for online charging.

3GPP
Release 15 72 3GPP TS 32.299 V15.4.0 (2018-09)

Table 6.4.2.1: 3GPP CCR message content

3GPP
Release 15 73 3GPP TS 32.299 V15.4.0 (2018-09)

AVP Category Description

Session-Id M This field identifies the operation session.
Origin-Host M This field contains the identification of the source point of the operation
and the realm of the operation originator.
Origin-Realm M This field contains the realm of the operation originator.
Destination-Realm M This field contains the realm of the operator domain. The realm will be
addressed with the domain address of the corresponding public URI.
Auth-Application-Id M The field corresponds to the application ID of the Diameter Credit-Control
Application and is defined with the value 4.
Service-Context-Id M This field indicates the supported protocol version.
M This field defines the transfer type: event for event based charging and
CC-Request-Type initial, update, terminate for session based charging.
CC-Request-Number M This field contains the sequence number of the transferred messages.
Destination-Host OC This field contains the destination peer address of the OCS identity.
User-Name OC Contains the user name determined by the domain: bearer, sub-system or
service as described in middle tier TS.
CC-Sub-Session-Id - Not used in 3GPP.
Acct-Multi-Session-Id - Not used in 3GPP.
Origin-State-Id OC This field contains the state associated to the CTF.
Event-Timestamp OC This field corresponds to the exact time the quota is requested.
OM This field contains the identification of the user that is going to access the
Subscription-Id service in order to be identified by the OCS.
M This field determines the type of the identifier, e.g. t value 0 is used for the
Subscription-Id-Type international E.164 format according to ITU-T E.164 numbering plan.
Subscription-Id-Data M This field contains the user data content e.g. the MSISDN.
Service-Identifier - Not used in 3GPP.
Termination-Cause OC This field contains the reason the Credit-Control session was terminated.
Requested-Service-Unit - Not used in 3GPP, see Multiple-Services-Credit-Control.
CC-Time - Not used in 3GPP.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.
CC-Total-Octets - Not used in 3GPP.
CC-Input-Octets - Not used in 3GPP.
CC-Output-Octets - Not used in 3GPP.
CC-Service-Specific-Units - Not used in 3GPP.
AVP - Not used in 3GPP.
Requested-Action OC The field defines the type of action if the CC-Request-Type indicates
EVENT.
AoC-Request-Type Oc This field denotes if AoC Information is requested and what type of
information is needed.
Used-Service-Unit - Not used in 3GPP, see Multiple-Services-Credit-Control.
Tariff-Change-Usage - Not used in 3GPP.
CC-Time - Not used in 3GPP.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.
CC-Total-Octets - Not used in 3GPP.
CC-Input-Octets - Not used in 3GPP.
CC-Output-Octets - Not used in 3GPP.
CC-Service-Specific-Units - Not used in 3GPP.
AVP - Not used in 3GPP.
OM This field indicates whether the CTF is capable of handling multiple
Multiple-Services-Indicator services independently.
OC This field contains all parameters for the CTF quota management and
Multiple-Services-Credit-Control defines the quotas to allow traffic to flow.
Granted-Service-Unit - Not used in CCR.
Tariff-Time-Change - Not used in CCR.
CC-Time - Not used in CCR.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.

3GPP
Release 15 74 3GPP TS 32.299 V15.4.0 (2018-09)

AVP Category Description

CC-Total-Octets - Not used in CCR.
CC-Input-Octets - Not used in CCR.
CC-Output-Octets - Not used in CCR.
CC-Service-Specific-Units - Not used in CCR.
AVP - Not used in 3GPP.
OC This field contains the amount of requested service units for a particular
Requested-Service-Unit category or an indication that units are needed for a particular category,
as defined in DCCA [402].
CC-Time OC This field contains the amount of requested time.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.
OC This field contains the requested amount of octets to be sent and
CC-Total-Octets received.
CC-Input-Octets OC This field contains the requested amount of octets to be received.
CC-Output-Octets OC This field contains the requested amount of octets to be sent.
OC This field contains the requested amount of service specific units, e.g.
CC-Service-Specific-Units number of events.
AVP - Not used in 3GPP.
Used-Service-Unit OC This field contains the amount of used non-monetary service units
measured for a particular category to a particular quota type.
Reporting-Reason OC Used as defined in clause 7.2.
OC This field identifies the reporting period for the used service unit, i.e.
Tariff-Change-Usage before, after or during tariff change.
CC-Time OC This field contains the amount of used time.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.
CC-Total-Octets OC This field contains the amount of sent and received octets.
CC-Input-Octets OC This field contains the amount of received octets.
CC-Output-Octets OC This field contains the amount of sent octets.
CC-Service-Specific-Units OC This field contains the amount of service specific units, e.g. number of
events.
Event-Charging-TimeStamp Oc Used as defined in clause 7.2.
AVP - Not used in 3GPP.
Tariff-Change-Usage - Not used in 3GPP .
OC This field contains identity of the used service. This ID with the Service-
Service-Identifier Context-ID together forms an unique identification of the service.
Rating-Group OC This field contains the identifier of a rating group.
G-S-U-Pool-Reference - Not used in CCR.
G-S-U-Pool-Identifier - Not used in CCR.
CC-Unit-Type - Not used in CCR.
Unit-Value - Not used in CCR.
Value-Digits - Not used in CCR.
Exponent - Not used in CCR.
Validity-Time - Not used in CCR.
Result-Code - Not used in CCR.
Final-Unit-Indication - Not used in CCR.
Final-Unit-Action - Not used in CCR.
Restriction-Filter-Rule - Not used in CCR.
Filter-Id - Not used in CCR.
Redirect-Server - Not used in CCR.
Redirect-Address-Type - Not used in CCR.
Redirect-Server-Address - Not used in CCR.
Time-Quota-Threshold - Not used in CCR.
Volume-Quota-Threshold - Not used in CCR.
Unit-Quota-Threshold - Not used in CCR.
Quota-Holding-Time - Not used in CCR.
Quota-Consumption-Time - Not used in CCR.
Reporting-Reason OC Used as defined in clause 7.2.
Trigger OC Used as defined in clause 7.2.
Trigger-Type OC Used as defined in clause 7.2.

3GPP
Release 15 75 3GPP TS 32.299 V15.4.0 (2018-09)

AVP Category Description

PS-Furnish-Charging-Information - Not used in CCR.
Refund-Information OC Used as defined in clause 7.2.
AF-Correlation-Information OC Used as defined in clause 7.2.
Envelope OC Used as defined in clause 7.2.
Envelope-Start-Time M Used as defined in clause 7.2.
Envelope-End-Time OC Used as defined in clause 7.2.
CC-Total-Octets OC Used as defined in clause 7.2.
CC-Input-Octets OC Used as defined in clause 7.2.
CC-Output-Octets OC Used as defined in clause 7.2.
CC-Service-Specific-Units OC Used as defined in clause 7.2
Envelop-Reporting OC Used as defined in clause 7.2.
Time-Quota-Mechanism OC Used as defined in clause 7.2.
Service-Specific-Info OC Used as defined in clause 7.2.
Service-Specific-Type OC Used as defined in clause 7.2.
Service-Specific-Data OC Used as defined in clause 7.2.
OC This field contains authorized QoS applicable for service data flow, which
initially triggers the activation of this MSCC instance. Included in first
quota request to rating group if service data flow specific QoS control is in
use, see TS 29.212 [215] for more information. For IP-CAN bearer
QoS-Information specific Rating Group/Service Identifier this field is not included.
For TDF, this field contains bandwidth limitation applicable for application
traffic and only the Max-Requested-Bandwidth-UL and the Max-
Requested-Bandwidth-DL are used.
QoS-Class-Identifier M See TS 29.212 [215] for more information.
Max-Requested-Bandwidth-UL OC See TS 29.212 [215] for more information.
Max-Requested-Bandwidth-DL OC See TS 29.212 [215] for more information.
Extended-Max-Requested-BW-UL OC See TS 29.212 [215] for more information.
Extended-Max-Requested-BW-DL OC See TS 29.212 [215] for more information.
Guaranteed-Bitrate-UL OC See TS 29.212 [215] for more information.
Guaranteed-Bitrate-DL OC See TS 29.212 [215] for more information.
Extended-GBR-UL OC See TS 29.212 [215] for more information.
Extended-GBR-DL OC See TS 29.212 [215] for more information.
Bearer-Identifier OC See TS 29.212 [215] for more information.
Allocation-Retention-Priority OC See TS 29.212 [215] for more information.
Priority-Level OC See TS 29.212 [215] for more information.
Pre-emption-Capability OC See TS 29.212 [215] for more information.
Pre-emption-Vulnerability OC See TS 29.212 [215] for more information.
APN-Aggregate-Max-Bitrate-UL OC See TS 29.212 [215] for more information.
APN-Aggregate-Max-Bitrate-DL OC See TS 29.212 [215] for more information.
Extended-APN-AMBR-UL OC See TS 29.212 [215] for more information.
Extended-APN-AMBR-DL OC See TS 29.212 [215] for more information.
Announcement-Information OC Not used in CCR.
OC This field contains the RAT Type of the IP-CAN bearer that is first reported
for the Rating Group or Rating Group / Service Identifier. If traffic from
multiple access types is included in this report, only one field is included.
3GPP-RAT-Type This field is only applicable when NBIFOM is accepted for the IP-CAN
session.

See TS 29.061 [207] for more information.

OC This field contains the trigger types for a related trigger for another access
in a multi-access PDN connection. This field is only included when the
Related-Trigger Trigger AVP contains a Trigger-Type AVP with value of "indirect change
condition" which is applicable when charging per IP-CAN session for a
multi-access PDN connection.
AVP - Not used in CCR.
Service-Parameter-Info - Not used in 3GPP.
Service-Parameter-Type - Not used in 3GPP.
Service-Parameter-Value - Not used in 3GPP.
CC-Correlation-Id OC This field contains information to correlate CCRs generated for different
components of the service, e.g., transport and service level.
User-Equipment-Info OC This field contains the identification of the identity and terminal capability
the subscriber is using for the connection to mobile network if available.
M This field determines the type of the identifier. The used value is 0 for the
User-Equipment-Info-Type international mobile equipment identifier and software version according
to TS 23.003[224].
User-Equipment-Info-Value M This field contains the user IMEI.
OC-Supported-Features OC Used as defined in IETF 7683 [411], for more details see clause B.

3GPP
Release 15 76 3GPP TS 32.299 V15.4.0 (2018-09)

AVP Category Description

OC-Feature-Vector OC Used as defined in IETF 7683 [411], for more details see clause B.
Proxy-Info OC This field contains information of the host.
Proxy-Host M This field contains the identity of the host that added the Proxy-Info field.
Proxy-State M This field contains state local information.
Route-Record OC This field contains an identifier inserted by a relaying or proxying node to
identify the node it received the message from.
Service-Information OM This parameter holds the individual service specific parameters as defined
in the corresponding 'middle tier' TS.
AVP OC This field contains extended Information.

3GPP
Release 15 77 3GPP TS 32.299 V15.4.0 (2018-09)

6.4.3 Credit-Control-Answer message

The CCA messages, indicated by the Command-Code field set to 272 is sent by the OCF to the CTF in order to reply to
the CCR.

The CCA message format is defined according to RFC 4006 [402] as follows:
<CCA> ::= < Diameter Header: 272, PXY >

< Session-Id >

{ Result-Code }
[ Experimental-Result ]

{ Origin-Host }
{ Origin-Realm }
{ Auth-Application-Id }
{ CC-Request-Type }
{ CC-Request-Number }
[ User-Name ]
[ CC-Session-Failover ]
[ CC-Sub-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Origin-State-Id ]
[ Event-Timestamp ]
[ Granted-Service-Unit ]
*[ Multiple-Services-Credit-Control ]
[ Cost-Information]
[ Low-Balance-Indication ]
[ Remaining-Balance ]
[ Final-Unit-Indication ]
[ Check-Balance-Result ]
[ Credit-Control-Failure-Handling ]
[ Direct-Debiting-Failure-Handling ]
[ Validity-Time]
[ OC-Supported-Features ]
[ OC-OLR ]
*[ Redirect-Host]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
*[ Proxy-Info ]
*[ Route-Record ]
[ Failed-AVP ]
[ Service-Information ]
*[ AVP ]

3GPP
Release 15 78 3GPP TS 32.299 V15.4.0 (2018-09)

Table 6.4.3.1 illustrates the basic structure of a 3GPP Diameter CCA message as used for online charging. This message
is always used by the OCF as specified below, independent of the receiving CTF and the CCR record type that is being
replied to.

Table 6.4.3.1: 3GPP CCA message content

3GPP
Release 15 79 3GPP TS 32.299 V15.4.0 (2018-09)

AVP Category Description

Session-Id M This field identifies the operation session.
Result-Code M This field contains the result of the specific query.
Experimental-Result OC This field contains the Experimental result of the specific query.
Origin-Host M This field contains the identification of the source point of the
operation and the realm of the operation originator.
Origin-Realm M This field contains the realm of the operation originator.
Auth-Application-Id M The field corresponds to the application ID of the Diameter Credit-
Control Application and is defined with the value 4.
M This field defines the transfer type: initial, update, terminate for
CC-Request-Type
session based charging and event for event based charging.
M This field contains the sequence number of the transferred
CC-Request-Number
messages.
User-Name - Not used in 3GPP.
OC This field contains an indication to the CTF whether or not a failover
CC-Session Failover
handling is to be used when necessary.
CC-Sub-session-Id - Not used in 3GPP.
Acct-Multi-Session-Id - Not used in 3GPP.
Origin-State-Id - Not used in 3GPP.
Event-Timestamp - Not used in 3GPP.
Granted-Service-Unit - Not used in 3GPP, see Multiple-Services-Credit-Control.
Tariff-Time-Change - Not used in 3GPP.
CC-Time - Not used in 3GPP.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.
CC-Total-Octets - Not used in 3GPP.
CC-Input-Octets - Not used in 3GPP.
CC-Output-Octets - Not used in 3GPP.
CC-Service-Specific-Units - Not used in 3GPP.
AVP - Not used in 3GPP.
OC This field contains all parameters for the CTF quota management
Multiple-Services-Credit-Control
and defines the quotas to allow traffic to flow.
OC This field contains the amount of granted service units for a particular
Granted-Service-Unit
category.
OC This field contains the switch time when the tariff will be changed.
Tariff-Time-Change
CC-Time OC This field contains the amount of granted time.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.
CC-Total-Octets OC This field contains the amount for sent and received octets.
CC-Input-Octets OC This field contains the amount for received octets.
CC-Output-Octets OC This field contains the amount for sent octets.
OC This field contains the amount for service specific units, e.g. number
CC-Service-Specific-Units
of events.
AVP - Not used in 3GPP.
Requested-Service-Unit - Not used in CCA.
CC-Time - Not used in CCA.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.
CC-Total-Octets - Not used in CCA.
CC-Input-Octets - Not used in CCA.
CC-Output-Octets - Not used in CCA.
CC-Service-Specific-Units - Not used in CCA.
AVP - Not used in 3GPP.
Used-Service-Unit - Not used in CCA.
Reporting-Reason - Not used in CCA.
Tariff-Change-Usage - Not used in CCA.

3GPP
Release 15 80 3GPP TS 32.299 V15.4.0 (2018-09)

AVP Category Description

CC-Time - Not used in CCA.
CC-Money - Not used in 3GPP.
Unit-Value - Not used in 3GPP.
Value-Digits - Not used in 3GPP.
Exponent - Not used in 3GPP.
Currency-Code - Not used in 3GPP.
CC-Total-Octets - Not used in CCA.
CC-Input-Octets - Not used in CCA.
CC-Output-Octets - Not used in CCA.
CC-Service-Specific-Units - Not used in CCA.
Event-Charging-TimeStamp - Not used in CCA.
AVP - Not used in 3GPP.
Tariff-Change-Usage - Not used in 3GPP.
OC This field contains identity of the used service. This ID with the
Service-Identifier Service-Context-ID together forms a unique identification of the
service.
Rating-Group OC This field contains the identifier of a rating group.
G-S-U-Pool-Reference OC Only used in ECUR and SCUR.
G-S-U-Pool-Identifier M Used as defined in DCCA [402].
CC-Unit-Type M Used as defined in DCCA [402].
Unit-Value M Used as defined in DCCA [402].
Value-Digits M Used as defined in DCCA [402].
Exponent OC Used as defined in DCCA [402].
OC This field defines the time in order to limit the validity of the granted
Validity-Time
quota for a given category instance.
Result-Code OC This field contains the result of the query.
OC This field indicates that the Granted-Service-Unit AVP containing the
Final-Unit-Indication
final units for the service.
Final-Unit-Action M Used as defined in DCCA [402].
Restriction-Filter-Rule OC Used as defined in DCCA [402].
Filter-Id OC Used as defined in DCCA [402].
Redirect-Server OC Used as defined in DCCA [402].
Redirect-Address-Type M Used as defined in DCCA [402].
Redirect-Server-Address M Used as defined in DCCA [402].
Time-Quota-Threshold OC Used as defined in clause 7.2.
Volume-Quota-Threshold OC Used as defined in clause 7.2.
Unit-Quota-Threshold OC Used as defined in clause 7.2.
Quota-Holding-Time OC Used as defined in clause 7.2.
Quota-Consumption-Time OC Used as defined in clause 7.2.
Reporting-Reason - Not used in CCA.
Trigger Oc Used as defined in clause 7.2.
Trigger-Type OC Used as defined in clause 7.2.
PS-Furnish-Charging-Information OC Used as defined in clause 7.2.
Refund-Information OC Used as defined in clause 7.2.
AF-Correlation-Information - Not used in CCA.

Envelope-Reporting OC Used as defined in clause 7.2.

Time-Quota-Mechanism OC Used as defined in clause 7.2.
Time-Quota-Type M Used as defined in clause 7.2.
Base-Time-Interval M Used as defined in clause 7.2.
AF-Correlation-Information - Not used in CCA.
Service-Specific-Info - Not used in CCA.
QoS-Information - Not used in CCA.
OC This field contains the Announcement service parameters. Each
Announcement-Information instance specifies a single announcement to be played to the
specified user.
Announcement-Identifier M This field contains a code identifying an announcement to be played.
OC This field contains the parameters necessary to define playback of a
Variable-Part
variable within the announcement.
Variable-Part-Order OC This field identifies the order of the variable to be played back.
Variable-Part-Type M This field identifies the type of the variable to be played back.
Variable-Part-Value M This field identifies the value of the variable to be played back.
OC This field instructs the announcement to be connected at the
Time-Indicator
specified time before granted quota is exhausted.
Quota-Indicator OC This field indicates whether granted quota is to be used during

3GPP
Release 15 81 3GPP TS 32.299 V15.4.0 (2018-09)

AVP Category Description

announcement setup and playback.
OC This field contains the order in which announcements should be
Announcement-Order connected for playback when there are multiple announcements
provided in a single message with the same timing indicator.
OC This field indicates the call party toward whom an announcement is
Play-Alternative
directed.
OC This field indicates whether the announcement is considered private
Privacy-Indicator
and is only to be played to the requested party.
OC This field contains a code indicating the language of the
Language
announcement that should be played.
3GPP-RAT-Type - Not used in CCA.
Related-Trigger - Not used in CCA
AVP - Not used in 3GPP.
Cost-Information OC Used as defined in DCCA [402].
Unit-Value M Used as defined in DCCA [402].
Value-Digits M Used as defined in DCCA [402].
Exponent OC Used as defined in DCCA [402].
Currency-Code M Used as defined in DCCA [402].
Cost-Unit OC Used as defined in DCCA [402].
Low-Balance-Indication Oc This field indicates whether the subscriber account balance went
below a designated threshold set by his account.
Remaining-Balance OC This field contains the remaining balance of the subscriber.
Unit-Value M Used as defined in DCCA [402].
Value-Digits M Used as defined in DCCA [402].
Exponent OC Used as defined in DCCA [402].
Currency-Code M Used as defined in DCCA [402].
Final-Unit-Indication - Not used in 3GPP, see Multiple-Services-Credit-Control.
Final-Unit-Action - Not used in 3GPP.
Restriction-Filter-Rule - Not used in 3GPP.
Filter-Id - Not used in 3GPP.
Redirect-Server - Not used in 3GPP.
Redirect-Address-Type - Not used in 3GPP.
Redirect-Server-Address - Not used in 3GPP.
Check-Balance-Result - Not used in 3GPP.
Credit-Control-Failure-Handling OC Used as defined in DCCA [402].
Direct-Debiting-Failure-Handling OC Used as defined in DCCA [402].
Validity-Time - Not used in 3GPP.
OC-Supported-Features OC Used as defined in IETF 7683 [411], for more details see clause B.
OC-Feature-Vector OC Used as defined in IETF 7683 [411], for more details see clause B.
OC-OLR OC Used as defined in IETF 7683 [411], for more details see clause B.
Redirect-Host OC Used by redirect agent function as specified in [401]. Contains the
host the request should be forwarded to.
Redirect-Host-Usage OC Used by redirect agent function as specified in [401]. Dictates how
the routing entry resulting from the Redirect-Host is to be used.
Redirect-Max-Cache-Time OC Used by redirect agent function as specified in [401]. Contains the
maximum number of seconds the peer and route table entries,
created as a result of the Redirect-Host, will be cached.
Proxy-Info OC This field contains information of the host.
Proxy-Host M This field contains the identity of the host that added the Proxy-Info
field.
Proxy-State M This field contains state local information.
Route-Record OC This field contains an identifier inserted by a relaying or proxying
node to identify the node it received the message from.
Failed-AVP OC This field contains the AVP that could not be processed successfully.
This field can occur only once.
Service-Information OC This parameter holds the individual service specific parameters as
defined in the corresponding 'middle tier' TS.
AVP OC This field contains extended Information.

3GPP
Release 15 82 3GPP TS 32.299 V15.4.0 (2018-09)

6.4.4 Re-Auth-Request message

The DCCA RAR message format is defined according to the Diameter Base Protocol in RFC 6733 [401] and DCCA
specification in RFC 4006 [402]:
<RAR> ::= < Diameter Header: 258, REQ, PXY >

< Session-Id >

{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Destination-Host }
{ Auth-Application-Id }
{ Re-Auth-Request-Type }
[ User-Name ]
[ Origin-State-Id ]
*[ Proxy-Info ]
*[ Route-Record ]
[ CC-Sub-Session-Id ]
[ G-S-U-Pool-Identifier ]
[ Service-Identifier ]
[ Rating-Group ]
*[ AVP ]

Table 6.4.4.1 illustrates the basic structure of a Diameter Credit-Control Re-Auth-Request message as used for online
charging.

Table 6.4.4.1: RAR message contents for online charging

AVP Category Description

Session-Id M This field identifies the operation session.
Origin-Host M This field contains the identification of the source point of the
operation and the realm of the operation originator.
Origin-Realm M This field contains the realm of the operation originator.
Destination-Realm M This field contains the realm of the operator domain. The realm will be
addressed with the domain address of the corresponding public URI.
Destination-Host M This field contains the destination peer address of the OCS identity.
Auth-Application-Id M The field corresponds to the application ID of the Diameter Credit-
Control Application and is defined with the value 4.
M This field is used to inform the CTF of the action expected upon
Re-Auth-Request-Type
expiration of the Authorization-Lifetime
User-Name OC This field contains the username.
Origin-State-Id OC This field contains the state associated to the CTF.
Proxy-Info OC This field contains information of the host.
Proxy-Host M This field contains the identity of the host that added the Proxy-Info
field.
Proxy-State M This field contains state local information.
Route-Record OC This field contains an identifier inserted by a relaying or proxying
node to identify the node it received the message from.
CC-Sub-Session-Id - Not used in 3GPP.
G-S-U-Pool-Identifier OC This field contains an identifier to indicate the credit pool.
OC This field contains identity of the used service. This ID with the
Service-Identifier Service-Context-ID together forms an unique identification of the
service.
Rating-Group OC This field contains the identifier of a rating group.
AVP OC This field contains extended Information.

3GPP
Release 15 83 3GPP TS 32.299 V15.4.0 (2018-09)

6.4.5 Re-Auth-Answer message

The DCCA RAA message format is defined according to the Diameter Base Protocol in RFC 6733 [401] and DCCA
specification in RFC 4006 [402]:
<RAA> ::= < Diameter Header: 258, PXY >

< Session-Id >

{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-State-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
[ Failed-AVP ]
*[ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Host-Cache-Time ]
*[ Proxy-Info ]
[ CC-Sub-Session-Id ]
[ G-S-U-Pool-Identifier ]
[ Service-Identifier ]
[ Rating-Group ]
*[ AVP ]

Table 6.4.5.1 illustrates the basic structure of a Diameter Credit-Control Re-Auth-Answer message as used for online
charging.

Table 6.4.5.1: RAA message contents for online charging

AVP Category Description

Session-Id M This field identifies the operation session.
Result-Code M This field contains the result of the specific query.
Origin-Host M This field contains the identification of the source point of the
operation and the realm of the operation originator.
Origin-Realm M This field contains the realm of the operation originator.
User-Name OC This field contains the username.
Origin-State-Id OC This field contains the state associated to the source point of the
operation.
Error-Message OC This field contains a human readable error message.
Error-Reporting-Host OC This field contains the identity of the Diameter host that sent the
Result-Code AVP to a value other than 2001 (Success) if the host
setting the Result-Code is different from the one encoded in the
Origin-Host AVP.
Failed-AVP OC This field contains the AVP that could not be processed
sucessfully. This field can occur only once.
Redirect-Host OC Used by redirect agent function as specified in [401]. Contains the
host the request should be forwarded to.
Redirect-Host-Usage OC Used by redirect agent function as specified in [401]. Dictates how
the routing entry resulting from the Redirect-Host is to be used.
Redirect-Max-Cache-Time OC Used by redirect agent function as specified in [401]. Contains the
maximum number of seconds the peer and route table entries,
created as a result of the Redirect-Host, will be cached.
Proxy-Info OC This field contains information of the host.
Proxy-Host M This field contains the identity of the host that added the Proxy-Info
field.
Proxy-State M This field contains state local information.
CC-Sub-Session-Id - Not used in 3GPP.
G-S-U-Pool-Identifier - Not used in 3GPP.
Service-Identifier - Not used in 3GPP.
Rating-Group - Not used in 3GPP.
AVP OC This field contains extended Information.

6.4.6 Capabilities-Exchange-Request message

The Capabilities-Exchange-Request message structure shall be as specified in RFC 6733 [401] clause 5.3.1.

3GPP
Release 15 84 3GPP TS 32.299 V15.4.0 (2018-09)

6.4.7 Capabilities-Exchange-Answer message

The Capabilities-Exchange-Answer message structure shall be as specified in RFC 6733 [401] clause 5.3.2.

6.4.8 Device-Watchdog-Request message

The Device-Watchdog-Request message structure shall be as specified in RFC 6733 [401] clause 5.5.1.

6.4.9 Device-Watchdog-Answer message

The Device-Watchdog-Answer message structure shall be as specified in RFC 6733 [401] clause 5.5.2.

6.4.10 Disconnect-Peer-Request message

The Disconnect-Peer-Request message structure shall be as specified in RFC 6733 [401] clause 5.4.1.

6.4.11 Disconnect-Peer-Answer message

The Disconnect-Peer-Answer message structure shall be as specified in RFC 6733 [401] clause 5.4.2.

6.4.12 Abort-Session-Request message

The Abort-Session-Request message structure shall be as specified in RFC 6733 [401] clause 8.5.1.

6.4.13 Abort-Session -Answer message

The Abort-Session-Answer message structure shall be as specified in RFC 6733 [401] clause 8.5.2.

3GPP
Release 15 85 3GPP TS 32.299 V15.4.0 (2018-09)

6.5 Other procedural description of the 3GPP charging applications

6.5.1 Re-Authorization

6.5.1.1 Idle timeout

The server may specify an idle timeout associated with a granted quota using the Quota-Holding-Time AVP.
If no traffic associated with the quota is observed for this time, the client shall understand that the traffic has stopped
and the quota is returned to the server. The client shall start the quota holding timer when quota consumption ceases.
This is always when traffic ceases, i.e. the timer is re-started at the end of each packet. It applies equally to the granted
time quota and to the granted volume quota. The timer is stopped on sending a CCR and re-initialised on receiving a
CCA with the previous used value or a new value of Quota-Holding-Time AVP if received.

Alternatively, if this AVP is not present, a locally configurable default value in the client shall be used.
A Quota-Holding-Time AVP value of zero indicates that this mechanism shall not be used.

6.5.1.2 Change of charging conditions

There are a number of mid-session service events (re-authorization triggers), which could affect the rating of the current
service usage, e.g. end user QoS changes or location updates. When allocating resources, the server may instruct the
Credit-Control client to re-authorize the quota upon a number of different session related triggers that can affect the
rating conditions. The server instruct the Network Element to monitor for such events by using the Trigger AVP
containing one or more Trigger-Type AVPs in the CCA command. These events are in addition to the static triggers
defined in the service specific document (middle tier TS).

Once the OCS has armed one or more triggers using the Trigger AVP at the Network Element, these triggers shall
remain in effect until another Trigger AVP is received for the same Rating Group, where the Network Element shall arm
all triggers present in the Trigger AVP and reset all other triggers. The presence of the Trigger AVP without any Trigger-
Type AVPs in a CCA allows OCS to disable all the triggers that were armed in a previous Trigger AVP.

NOTE: This removes the need for the OCS to send trigger information in every CCA message when they have
not changed.

When one of the armed triggers happen, a credit re-authorization shall be sent to the server including information
related to the service event even if all the granted service units have not been used. The quota is also being reported.

For example, if the Trigger AVP is used, then the client shall only re-authorize the quota for the service usage associated
with events which were included in the last received Trigger AVP.

If the server does not control the events for re-authorization using the Trigger AVP, the Network Element shall only
monitor for default events defined in the relevant service specific document (middle tier TS).

6.5.1.3 Reporting quota usage

The Credit-Control client shall report the quota usage under a number of circumstances. When this happens, the reason
for the quota being reported is notified to the server through the use of the Reporting-Reason AVP in the CCR. The
reason for reporting credit usage can occur directly in the Multiple-Services-Credit-Control AVP, or in the Used-
Service-Units AVP, depending on whether it applies for all quota types or a particular quota type respectively. It shall
not be used at command level. It shall always and shall only be sent when usage is being reported.

When the reason is RATING_CONDITION_CHANGE, the Trigger AVP shall also be included to indicate the specific
armed trigger events which caused the reporting and re-authorization request.

3GPP
Release 15 86 3GPP TS 32.299 V15.4.0 (2018-09)

6.5.1.4 Quota consumption

The consumption of quota is captured using mechanisms described in clause 6.5.1.3.

Volume quota is considered used or consumed in the normal way, corresponding to actual traffic.

The consumption of time quota may be controlled by Quota-Consumption-Time as described in clause 6.5.4, or by
extended mechanisms as described in clause 6.5.7.

6.5.2 Threshold based Re-Authorization triggers

The server may optionally include as part of the Multiple-Services-Credit-Control AVP, when it is providing a quota, an
indication to the client of the remaining quota threshold that shall trigger a quota re-authorization.
The Time-Quota-Threshold AVP indicates the threshold in seconds when the granted quota is time, and the Volume-
Quota-Threshold AVP indicates the threshold in octets when the granted quota is volume.
The Unit-Quota-Threshold AVP indicates the threshold in service specific units, that are defined in the service specific
documents, when the granted quota is service specific.

If the threshold triggers were included along with the quota granted, the Credit-Control client, then, shall seek re-
authorization from the server for the quota when the quota contents fall below the supplied threshold. The client shall
allow service to continue whilst the re-authorization is progress, until the original quota had been consumed.

6.5.3 Termination action

The termination action is sent over the Ro reference point. Two different approaches are specified:

- The Final-Unit-Indication AVP with Final-Unit-Action TERMINATE does not include any other information.
When the user has consumed the final granted units or zero quota has been granted by the OCS, the Network
Element shall terminate the service. This is the default handling applicable whenever the client receives an
unsupported Final-Unit-Action value. The Network Element shall send CCR message with CC-Request-Type
AVP set to the value UPDATE_REQUEST and report the Used-Service-Unit AVP for the service that has
terminated, as defined in RFC 4006 [402].

- Another termination action consists in re-directing packets corresponding to a terminated service (consumption
of the final granted units or zero quota has been granted by the OCS) to an application server. This allows the
client to redirect user originated requests to a top-up server so that network access can be re-instated. This
functionality is achieved with the server returning a "REDIRECT" and redirect-to URL in the Final-Units-Action
AVP of the Multiple-Services-Credit-Control AVP. Upon receiving this result code, the Network Element shall
apply the redirection. The URL should be categorized so that the End-User's ability to reach it is guaranteed.

When zero quota has been granted by the OCS, the termination action shall be enforced at the reception of the CCA
message.

3GPP
Release 15 87 3GPP TS 32.299 V15.4.0 (2018-09)

6.5.4 Quota consumption time

The server may optionally indicate to the client that the quota consumption shall be stopped after a period equal to the
Quota Consumption Time in which no packets are received or at session termination, whichever is sooner. This is
indicated by including the Quota-Consumption-Time AVP in the CCA. The idle period equal to the Quota Consumption
Time is included in the reported usage. The quota is consumed normally during gaps in traffic of duration less than or
equal to the Quota-Consumption-Time. Quota consumption resumes on receipt of a further packet belonging to the
service data flow.

If packets are allowed to flow during a CCR/CCA[Update] exchange, and the Quota-Consumption-Time AVP value in
the provided quota is the same as in the previously provided quota, then the Quota-Consumption-Time runs normally
through this procedure. For example, if 5 seconds of a 10 second QCT timer have passed when a CCR[Update] is
triggered, and the CCA[Update] returns 2 seconds later, then the QCT timer will expire 3 seconds after the receipt of the
CCA and the remaining unaccounted 5 seconds of usage will be recorded against the new quota even though no packets
were transmitted with the new quota.

In the case of a new quota with the Quota-Consumption-Time AVP, or when packets are blocked during the CCR/CCA
[Update] procedure then the Quota-Consumption-Time stops running (if it was running) and quota consumption begins
again when the next service data flow packet matching the Charging Rule is received.

If a Quota-Consumption-Time AVP value of zero is provided, or if no Quota-Consumption-Time AVP is present in the

CCA, the quota is consumed continuously from the point at which it is granted.

6.5.5 Service termination

The OCF may determine that a service requires termination. The OCF may perform this termination synchronously if it
has a CCR pending processing by returning CCA with Result-Code AVP with value DIAMETER-AUTHORIZATION-
REJECTED. If the OCF does not have a pending request (asynchronous), the OCF may trigger an ASR to terminate the
Diameter session related to the service. On reception of an ASR, the CTF shall close the associated Credit-Control
session by sending a CCR [Terminate]. The behaviour of the CTF, in relation to the user session, on reception of an
ASR is detailed in the middle-tier TS. As an alternative to the ASR, the OCF may trigger a RAR to which the CTF
behaves as described in RFC 4006 [402] and the OCF shall return a CCA with Result-Code AVP with value
DIAMETER-AUTHORIZATION-REJECTED for the resulting CCR.

6.5.6 Envelope reporting

6.5.6.1 Envelope reporting in Online Charging

The OCF may determine the need for additional detailed reports identifying start time and end times of specific activity
in addition to the standard quota management provided in RFC 4006 [402]. The OCF controls this by sending a
CCA[INITIAL] with Envelope-Reporting AVP. The OCF may request reports for just time, time and volume, time and
number of events, or time and volume and number of events, through appropriate values in Envelope-Reporting AVP.

The time envelope of the activity to be reported is determined by the mechanism indicated by the OCF in this
CCA[INITIAL], to control the time quota consumption in the CTF.

The selected mechanism is used by the CTF to generate the envelopes, reporting the start and end of each time
envelope, and the data volume transferred and / or the number of events that occurred for the duration of the envelope

NOTE: Envelope reporting is independent of quota management (i.e. there is no interaction).

6.5.6.2 Envelope reporting in Offline Charging

When a particular time quota consumption mechanism is selected by the OCF, the need for reporting detailed time
envelopes in offline charging, may be statically configured in the CTF or dynamically controlled by the OCF using
Offline-Charging AVP.

The selected time quota consumption mechanism is used by the CTF to generate the envelopes, reporting the start and
end of each time envelope, and the data volume transferred and / or the number of events that occurred for the duration
of the envelope.

3GPP
Release 15 88 3GPP TS 32.299 V15.4.0 (2018-09)

6.5.6.3 Envelope reporting - Quota consumption time

In case the time quota consumption mechanism selected by the OCF is per clause 6.5.4, and the OCF indicated the need
for envelope reporting,.the CTF, on receiving the command, monitors the traffic for a period of time controlled by the
Quota-Consumption-Time AVP and reports each period as a single envelope for each Quota-Consumption-Time expiry
where there was traffic, in Envelope AVP.

6.5.6.4 Envelope reporting - Combinational quota

In case the time quota consumption mechanism selected by the OCF is per clause 6.5.7, and the OCF indicated the need
for envelope reporting, the CTF, on receiving the command, monitors the traffic based on information included in Time-
Quota-Mechanism AVP, and reports each corresponding envelope in the Envelope AVP in the CCR.

In case of Continuous Time Period (CTP):

- the first envelope starts on the first traffic, and subsequent envelopes start on the first traffic following the
closure of the previous envelope.

- each envelope ends at expiry of the first base time interval which contains no traffic.

The envelope for CTP includes the last base time interval, i.e. the one which contained no traffic. The end of an
envelope can only be determined "retrospectively".

In case of Discrete Time Period (DTP), an envelope corresponds to exactly one base time interval.

3GPP
Release 15 89 3GPP TS 32.299 V15.4.0 (2018-09)

6.5.7 Combinational quota

The Quota-Consumption-Time mechanism, described in clause 6.5.4, may be extended (and replaced) when granting
time based quota to provide potentially more efficient use of the online charging interface, i.e. reduced traffic and the
algorithms in the OCF are potentially simpler. The alternative handling mechanisms that are defined in this clause are:

1. Continuous Time Period (CTP)

2. Discrete Time Period (DTP)

The mechanisms selected by the OCF is indicated to the CTF with the Time-Quota-Mechanism AVP in the CCA.

The base time interval, specified by the Base-Time-Interval AVP, is a basic unit for consuming
quota. Quota is deemed to be consumed at the start of each base time interval. The CTF shall allow traffic to pass for
the duration of the base time interval.

For DTP, the base time interval defines the length of the discrete time period. Quota consumption
resumes only on the first traffic following the expiry of the DTP.

For CTP, quota consumption continues during consecutive base time intervals in which traffic has
occurred up to and including the first base time interval which contains no traffic. Quota
consumption shall be stopped after this first base time interval expiry which contained no traffic. Quota
consumption resumes only on the first subsequent traffic.

If the CTF receives a Multiple-Services-Credit-Control AVP with both the Quota-Consumption-Time AVP and Time-
Quota-Mechanism AVP, then the Time-Quota-Mechanism AVP takes precedence and the CTF shall behave accordingly.

6.5.8 Online control of offline charging information

The Offline-Charging AVP is used on the Ro interface by the OCS to control the CTF in relation to the mechanism by
which the CTF generates offline charging information, e.g. for flow based charging controls the formation of service
data containers. The information contained, within the Offline-Charging AVP, takes precedence over the default
configuration at the CTF. If the Offline-Charging AVP is not sent in the CCA, the OCS does not control the offline
charging mechanisms and therefore the default configuration at the CTF is employed.

Controls over time usage, defined in clause 6.5.6 and clause 6.5.7, are included.

6.5.9 Support of multiple service

The support of multiple services within a single Diameter session in 3GPP is limited to services that are grouped in one
of the middle tier TSs specified through the Service-Context-Id AVP.

6.5.10 Supported Features mechanism

6.5.10.1 Introduction
Supported Features mechanism is used for 3GPP Charging Applications as specified in TS 29.229 [204] clause 7.2,
based on the Supported-Features AVP.

6.5.10.2 Defining a feature

The concept of feature used by the Supported Features mechanism, applies under a specific domain / subsystem /
service, and is defined as an extension of the base offline and online charging functionality specified in the
corresponding middle tier.

For each middle tier, the base functionality is the one specified by the 3GPP Rel-14 version, and for any extension
introduced from Rel-15, the Supported Features mechanism is required.

For any middle tier created from Rel-15, the Supported Features mechanism is required to be introduced.

Applicability of a feature is defined separately between offline (Rf) and online(Ro) charging.

3GPP
Release 15 90 3GPP TS 32.299 V15.4.0 (2018-09)

Any feature specified for offline and online charging, when invoked by the client, is defined as mandatory to be
supported by the server.

As specified in TS 29.229 [204] clause 7.1.1, if new AVPs are added as part of the feature definition, they shall have the
'M' bit cleared and shall not be defined mandatory in the command ABNF.

6.5.10.3 Supported Feature handling

Any request initiated by the client which makes use of a feature to construct the request, and requires the feature to be
supported by the server, shall include the feature associated to the service-context in the Supported-Features AVP.

The client shall include in the request feature(s) and only feature(s) which are needed to construct the request.

In case multiple features are needed to construct the request, they shall all be included by the client.

As defined in TS 29.229 [204], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-
List-ID and Feature-List AVPs.

The value 10415 (3GPP) is used as Vendor-Id, and the Feature-List-ID and Feature-List are defined per middle tier TS.

Upon receiving any initial Ro or Rf request for a specific domain / subsystem / service, which does not include any
Supported-Features AVP, the server shall include in the answer, if supported, Supported-Features AVPs identifying the
complete set of features supported by the server for this domain / subsystem / service. This applies regardless of the
answer is successful or not.

Upon receiving any initial Ro or Rf request for a specific domain / subsystem / service, which includes the Supported-
Features AVP, the server shall behave as follows:

- If all features indicated in the Supported-Features AVP are supported, and the process for online or offline
charging is successful, a successful answer with the Result-Code AVP set to DIAMETER_SUCCESS is returned
and includes, if supported, Supported-Features AVPs identifying the complete set of features supported by the
server for this domain / subsystem / service.

- If not all the features indicated in the Supported-Features AVP are supported, the answer is returned with
Experimental-Result-Code AVP set to DIAMETER_ERROR_FEATURE_UNSUPPORTED and includes the
Supported-Features AVPs containing lists of all features supported by the server.

- If Supported-Features AVP is not supported by the server, the answer is returned, as per 'M' bit set rule, with the
Result-Code AVP set to DIAMETER_AVP_UNSUPPORTED and a Failed-AVP AVP containing at least one
Supported-Features AVP as received in the request.

During the lifetime of the Diameter session, the client shall use the set of features which are common between its own
set of supported features and the set of supported features indicated by the server during the Diameter session
establishment, in session based charging.

3GPP
Release 15 91 3GPP TS 32.299 V15.4.0 (2018-09)

6.6 Bindings of the operation to protocol application

6.6.0 General
This clause aims to describe the mapping between the protocol independent messages and parameter with the Diameter
messages and AVP utilized on the 3GPP offline and online charging.

6.6.1 Bindings of Charging Data Transfer to Accounting

Table 6.6.1.1 describes the bindings of the Charging Data Transfer operation parameter to the DBPA AVP for 3GPP
offline charging.

Table 6.6.1.1: Bindings to Accounting

Charging Data Transfer element Diameter Accounting AVP

Operation Number Accounting-Record-Number
Operation Type Accounting-Record-Type
Operation Identifier Acct-Application-Id
Operation Interval Acct-Interim-Interval
Destination Domain Destination-Realm
Error Reporting Host Error-Reporting-Host
Origination Timestamp Event-Timestamp
Originator Host Origin-Host
Originator Domain Origin-Realm
Origination State Origin-State-Id
Proxy Information Proxy-Info
Operation Result Result-Code
Route Information Route-Record
Service Information Service-Information
Session Identifier Session-Id
Operation Token Service-Context-Id
User Name User-Name

3GPP
Release 15 92 3GPP TS 32.299 V15.4.0 (2018-09)

6.6.2 Bindings of Debit / Reserve Units to Credit-Control

Table 6.6.2.1 describes the bindings of the Debit / Reserve Units operation parameter to the DCCA AVP for 3GPP
0nline charging.

Table 6.6.2.1: Bindings to Credit-Control

Debit / Reserve Units element DCCA AVP

AoC Type AoC-Request-Type
Cost Information Cost-Information
Destination Domain Destination-Realm
Destination Host Destination-Host
Failed parameter Failed-AVP
Low Balance Indication Low-Balance-Indication
Multiple Operation Multiple-Services-Indicator
Multiple Unit Operation Multiple-Services-Credit-Control
Operation Correlation CC-Correlation-Id
Operation Failover CC-Session-Failover
Operation Failure Action Credit-Control-Failure-Handling
Operation Identifier Auth-Application-Id
Operation Number CC-Request-Number
Operation Result Result-Code
Operation Token Service-Context-Id
Operation Type CC-Request-Type
Origination State Origin-State-Id
Origination Timestamp Event-Timestamp
Originator Domain Origin-Realm
Originator Host Origin-Host
Proxy Information Proxy-Info
Redirection Cache Time Redirect-Max-Cache-Time
Redirection Host Redirect-Host
Redirection Host Usage Redirect-Host-Usage
Remaining Balance Remaining-Balance
Requested Action Requested-Action
Route Information Route-Record
Service Information Service-Information
Session Identifier Session-Id
Subscriber Equipment Number User-Equipment-Info
Subscriber Identifier Subscription-Id
Termination Cause Termination-Cause
User Name User-Name

6.7 Securing Diameter messages

For secure transport of Diameter messages used for offline and online charging application, see 3GPP TS 33.210 [246].

3GPP
Release 15 93 3GPP TS 32.299 V15.4.0 (2018-09)

7 Summary of used Attribute Value Pairs

7.1 Diameter AVPs

7.1.0 General
The use of the Attribute Value Pairs (AVPs) that are defined in the Diameter Protocol is specified in clause 6.2 for
offline charging and in clause 6.4 for online charging. The information is summarized in the table 7.1.0.1 in alphabetical
order. Detailed specification of some of these AVPs is available after the table and for the others can be found from RFC
6733 [401], RFC 4006 [402] and RFC 4005 [407].

Those Diameter AVPs that are used are marked "M", "OM" or "Oc" in the following table.
This implies that their content can be used by the CDF for offline and by the OCF for online charging purposes.
Those Diameter AVPs that are not used are marked "-" in table 7.1.0.1.

Table 7.1.0.1: Use Of IETF Diameter AVPs

3GPP
Release 15 94 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name Must May Should Must
Code ACR ACA CCR CCA Type
not not
Accounting-Input-Octets 363 OC - - - Unsigned64 M - - V
Accounting-Output-Octets 364 OC - - - Unsigned64 M - - V
Accounting-Realtime-Required 483 - - - - Enumerated - - - -
Accounting-Record-Number 485 M M - - Unsigned32 M - - V
Accounting-Record-Type 480 M M - - Enumerated M - - V
Accounting-Sub-Session-Id 287 - - - - Unsigned64 - - - -
Acct-Application-Id 259 OC OC - - Unsigned32 M - - V
Acct-Interim-Interval 85 OC OC - - Unsigned32 M - - V
Acct-Multi-Session-Id 50 - - - - Unsigned32 - - - -
Acct-Session-Id 44 - - - - OctetString - - - -
Auth-Application-Id 258 - - M M Unsigned32 M - - V
AVP * - - - - Grouped - - - -
Called-Station-Id 30 OC - OC - UTF8String M - - V
CC-Correlation-Id 411 - - OC - OctetString - M - V
CC-Input-Octets 412 - - OC OC Unsigned64 M - - V
CC-Money 413 - - - - Grouped - - - -
CC-Output-Octets 414 - - OC OC Unsigned64 M - - V
CC-Request-Number 415 - - M M Unsigned32 M - - V
CC-Request-Type 416 - - M M Enumerated M - - V
CC-Service-Specific-Units 417 - - OC OC Unsigned64 M - - V
CC-Session-Failover 418 - - - OC Enumerated M - - V
CC-Sub-Session-Id 419 - - - - Unsigned64 - - - -
CC-Time 420 - - OC OC Unsigned32 M - - V
CC-Total-Octets 421 - - OC OC Unsigned64 M - - V
CC-Unit-Type 454 - - - M Enumerated M - - V
Check-Balance-Result 422 - - - - Enumerated - - - -
Cost-Information 423 - - - OC Grouped M - - V
Cost-Unit 424 - - - OC UTF8String M - - V
Credit-Control 426 - - - - Enumerated - - - -
Credit-Control-Failure-Handling 427 - - - OC Enumerated M - - V
Currency-Code 425 - - - M Unsigned32 M - - V
Destination-Host 293 OC - OC - DiamIdent M - - V
Destination-Realm 283 M - M - DiamIdent M - - V
Direct-Debiting-Failure-Handling 428 - - - OC Enumerated M - - V
Error-Message 281 - - - - UTF8String - - - -
Error-Reporting-Host 294 - OC - - DiamIdent - - - V,M
Event-Timestamp 55 OC OC OC - Time M - - V
Experimental-Result 297 - OC - OC Grouped - - - V,M
Experimental-Result-Code 298 - OC - OC Unsigned32 - - - V,M
Exponent 429 - - - OC Integer32 M - - V
Failed-AVP 279 - - - OC Grouped M - - V
Filter-Id 11 - - - OC UTF8String M - - V
Final-Unit-Action 449 - - - OC Enumerated M - - V
Final-Unit-Indication 430 - - - OC Grouped M - - V
Granted-Service-Unit 431 - - - OC Grouped M - - V
G-S-U-Pool-Identifier 453 - - - OC Unsigned32 M - - V
G-S-U-Pool-Reference 457 - - - OC Grouped M - - V
Multiple-Services-Credit-Control 456 - - OC OC Grouped M - - V
Multiple-Services-Indicator 455 - - OM - Enumerated M - - V
OC-Feature-Vector 622 - - OC OC Unsigned64 - - - V,M
OC-OLR 623 - - - OC Grouped - - - V,M
OC-Reduction-Percentage 627 - - - OC Unsigned32 - - - V,M
OC-Report-Type 626 - - - OC Enumerated - - - V,M
OC-Sequence-Number 624 - - - OC Unsigned64 - - - V,M
OC-Supported-Features 621 - - OC OC Grouped - - - V,M
OC-Validity-Duration 625 - - - OC Unsigned32 - - - V,M
Origin-Host 264 M M M M DiamIdent M - - V
Origin-Realm 296 M M M M DiamIdent M - - V
Origin-State-Id 278 OC OC OC - Unsigned32 M - - V
Proxy-Info 284 OC OC OC OC Grouped M - - V
Proxy-Host 280 M M M M DiamIdent M - - V
Proxy-State 33 M M M M OctetString M - - V
Rating-Group 432 OC - OC OC Unsigned32 M - - V
Redirect-Address-Type 433 - - - M Enumerated M - - V
Redirect-Host 292 - - - OC DiamURI M - - V
Redirect-Host-Usage 261 - - - OC Enumerated M - - V
Redirect-Max-Cache-Time 262 - - - OC Unsigned32 M - - V
Redirect-Server 434 - - - OC Grouped M - - V
Redirect-Server-Address 435 - - - M UTF8String M - - V
Requested-Action 436 - - OC - Enumerated M - - V

3GPP
Release 15 95 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name Must May Should Must
Code ACR ACA CCR CCA Type
not not
Requested-Service-Unit 437 - - OC - Grouped M - - V
Restriction-Filter-Rule 438 - - - OC IPFilterRule M - - V
Result-Code 268 - M - M Unsigned32 M - - V
Route-Record 282 OC - OC OC DiamIdent M - - V
Service-Context-Id 461 OM - M - UTF8String M - - V
Service-Identifier 439 OC - OC OC Unsigned32 M - - V
Service-Parameter-Info 440 - - - - Grouped - - - -
Service-Parameter-Type 441 - - - - Unsigned32 - - - -
Service-Parameter-Value 442 - - - - OctetString - - - -
Session-Id 263 M M M M UTF8String M - - V
Subscription-Id 443 OC - OM - Grouped M - - V
Subscription-Id-Data 444 M - M - UTF8String M - - V
Subscription-Id-Type 450 M - M - Enumerated M - - V
Tariff-Change-Usage 452 - - OC - Enumerated M - - V
Tariff-Time-Change 451 - - OC Time M - - V
Termination-Cause 295 - OC - Enumerated M - - V
Unit-Value 445 - - - M Grouped M - - V
Used-Service-Unit 446 - - OC - Grouped M - - V
User-Equipment-Info 458 OC - OC - Grouped - M - V
User-Equipment-Info-Type 459 OM - M - Enumerated - M - V
User-Equipment-Info-Value 460 OM - M - OctetString - M - V
User-Name 1 OC OC OC - UTF8String M - - V
Value-Digits 447 - - - M Integer64 M - - V
Validity-Time 448 - - - OC Unsigned32 M - - V
Vendor-Id 266 - - - - Unsigned32 - - - -
Vendor-Specific-Application-Id 260 - - - - Grouped - - - -

NOTE 1: Result-Code AVP is defined in Diameter Base Protocol in RFC 6733 [401]. Values which are used in
offline and online charging applications are defined below.

NOTE 2: Experimental-Result AVP is defined in Diameter Base Protocol in RFC 6733 [401]. Values which are
used in offline and online charging applications are defined below.

7.1.1 Accounting-Input-Octets AVP

The Accounting-Input-Octets AVP (AVP code 363) contains the number of octets transmitted during the data container
recording interval, reflecting the volume counts for uplink traffic for a data flow.

7.1.2 Void

7.1.3 Accounting-Output-Octets AVP

The Accounting-Output-Octets AVP (AVP code 364) contains the number of octets transmitted during the data container
recording interval, reflecting the volume count for downlink traffic for a data flow.

7.1.4 Void

7.1.5 Acct-Application-Id AVP

The Acct-Application-Id AVP (AVP code 259) shall contain the value of 3 as defined in RFC 6733 [401] according
TS 29.230 [206].

7.1.6 Auth-Application-Id AVP

The Auth-Application-Id AVP (AVP code 258) shall contain the value of 4 as defined in RFC 4006 [402] according
TS 29.230 [206].

3GPP
Release 15 96 3GPP TS 32.299 V15.4.0 (2018-09)

7.1.7 Called-Station-Id AVP

The Called-Station-Id AVP (AVP code 30) shall contain the Access Point Name (APN) the user is connected to.

7.1.8 Event-Timestamp AVP

The Event-Timestamp AVP (AVP code 55) shall contain the time when the chargeable event is received in the CTF.

7.1.8A Experimental-Result AVP

The Experimental-Result AVP (AVP code 297) defined in RFC 6733 [401], shall contain the values used in offline and
online charging applications. The Vendor-ID AVP shall contain 3GPP (10415), and following values are used for
Experimental-Result-Code:

Permanent Failures (5xxx):

5011 DIAMETER_ERROR_FEATURE_UNSUPPORTED
At least one feature included in the request sent by the CTF is not supported by the CDF or OCF. This value
is defined in TS 29.229 [204]

7.1.9 Multiple-Services-Credit-Control AVP

The Multiple-Services-Credit-Control AVP (AVP code 456) is of type grouped as specified in RFC 4006 [402]. It
contains additional 3GPP specific charging parameters.

It has the following ABNF grammar:

<Multiple-Services-Credit-Control> ::= < AVP Header: 456 >

[ Granted-Service-Unit ]
[ Requested-Service-Unit ]
* [ Used-Service-Unit ]
[ Tariff-Change-Usage ]
* [ Service-Identifier ]
[ Rating-Group ]
* [ G-S-U-Pool-Reference ]
[ Validity-Time ]
[ Result-Code ]
[ Final-Unit-Indication ]
[ Time-Quota-Threshold ]
[ Volume-Quota-Threshold ]
[ Unit-Quota-Threshold ]
[ Quota-Holding-Time ]
[ Quota-Consumption-Time ]
* [ Reporting-Reason ]
[ Trigger ]
[ PS-Furnish-Charging-Information ]
[ Refund-Information ]
* [ AF-Correlation-Information]
* [ Envelope ]
[ Envelope-Reporting ]
[ Time-Quota-Mechanism ]
* [ Service-Specific-Info ]
[ QoS-Information ]
* [ Announcement-Information ]
[ 3GPP-RAT-Type ]
[ Related-Trigger ]
* [ AVP ]

3GPP
Release 15 97 3GPP TS 32.299 V15.4.0 (2018-09)

7.1.10 Rating-Group AVP

The Rating-Group AVP (AVP code 432), is defined in RFC 4006 [402]. It contains the charging key (defined in TS
23.203 [218]). Each quota allocated to a Diameter CC session has a unique Rating Group value as specified in RFC
4006 [402].

7.1.11 Result-Code AVP

This subclause defines new Result-Code AVP (AVP code 268) values that shall be supported by all Diameter
implementations that conform to the present document. The Result-Code AVP operates as described in RFC 6733 [401]
and RFC 4006 [402]. The following result code descriptions are examples of the possible uses for the code:

Transient Failures (4xxx):

4010 DIAMETER_END_USER_SERVICE_DENIED
The OCF denies 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.
4011 DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE
The OCF determines that the service can be granted to the end user but no further Credit-Control
needed for the service (e.g. service is free of charge or is treated for offline charging).
4012 DIAMETER_CREDIT_LIMIT_REACHED
The OCF denies the service request since the end- user's account could not cover the requested service. If the
CCR contained used-service-units they are deducted, if possible.

Permanent Failures (5xxx):

5003 DIAMETER_AUTHORIZATION_REJECTED
The OCF denies the service request in order to terminate the service for which credit is requested. For
example this error code is used to inform IP CAN bearer has to be terminated in the CCR message or to
inform blacklist the rating group in the Multiple-Service-Credit-Control AVP.
5030 DIAMETER_USER_UNKNOWN
The specified end user could not be found in the OCF.
5031 DIAMETER_RATING_FAILED
This error code is used to inform the CTF that the OCF cannot rate the service request due to insufficient
rating input, incorrect AVP combination or due to an AVP or an AVP value that is not recognized or supported
in the rating. For Flow Based Charging this error code is used if the Rating group is not recognized. The
Failed-AVP AVP MUST be included and contain a copy of the entire AVP(s) that could not be processed
successfully or an example of the missing AVP complete with the Vendor-Id if applicable. The value field of
the missing AVP should be of correct minimum length and contain zeroes.

3GPP
Release 15 98 3GPP TS 32.299 V15.4.0 (2018-09)

7.1.12 Service-Context-Id AVP

The Service-Context-Id AVP is defined in RFC 4006 [402]. It is of type UTF8String and contains a unique identifier of
the Diameter Credit-Control service specific document that applies to the request.
This is an identifier allocated by the service provider/operator, by the service element manufacturer or by a
standardization body and MUST uniquely identify a given Diameter Credit-Control service specific document. For
offline charging, this identifies the service specific document ('middle tier' TS) on which associated CDRs should based.
The format of the Service-Context-Id is:

"extensions".MNC.MCC."Release"."service-context" "@" "domain"

The 3GPP specific values for "service-context" "@" "domain" are:

[email protected] for PS charging

[email protected] for CPDT charging
[email protected] for Exposure function API charging
[email protected] for IMS charging
[email protected] for MMS service charging
[email protected] for LCS service charging
[email protected] for PoC service charging
[email protected] for MBMS service charging
[email protected] for SMS service charging
[email protected] for MMTel service charging
[email protected] for VCS charging
[email protected] for ProSe charging
[email protected] for Monitoring Event charging
[email protected] for AoC Service Information
[email protected] for ABMF Rc information

The "Release" indicates the 3GPP Release the service specific document is based upon e.g. 12 for Release 12.

As a minimum, "Release"."service-context" "@" "domain" shall be used. If the minimum is used all operator
provisionable parameters (Oc and Om) are optional.

The MNC.MCC identifies the operator implementing the service specific document, which is used to determine the
specific requirements for the operator configurable parameters.

The "extensions" is operator specific information to any extensions in a service specific document.

7.1.13 Service-Identifier AVP

The Service-Identifier AVP (AVP code 439), is defined in RFC 4006 [402]. For further details, please refer the middle-
tier specification.

7.1.14 Used-Service-Unit AVP

The Used-Service-Unit AVP (AVP code 446) is of type grouped as specified in RFC 4006 [402]. It contains additional
3GPP specific charging parameters.

It has the following ABNF grammar:

<Used-Service-Unit> ::= < AVP Header: 446 >

[ Reporting-Reason ]
[ Tariff-Change-Usage ]
[ CC-Time ]
[ CC-Money ]
[ CC-Total-Octets ]
[ CC-Input-Octets ]
[ CC-Output-Octets ]
[ CC-Service-Specific-Units ]
*[ Event-Charging-TimeStamp ]

3GPP
Release 15 99 3GPP TS 32.299 V15.4.0 (2018-09)

*[ AVP ]

7.1.15 User-Name AVP

The User-Name AVP (AVP code 1) contains the user name in the format of a NAI according to RFC 6733 [401].

7.1.16 Vendor-Id AVP

The Vendor-Id AVP (AVP code 266), as part of the grouped Vendor-Specific-Application-Id AVP, shall contain the value
of 10415, which is the IANA registered value for '3GPP' in TS 29.230 [206].

7.1.17 User-Equipment-Info AVP

The User-Equipment-Info AVP (AVP code 458) is of type grouped and contains the identity and capability of the
terminal the subscriber is using for the connection to network according to IETF RFC 4006 [402] with the following
ABNF grammar:

User-Equipment-Info ::= < AVP Header: 458 >

{ User-Equipment-Info-Type }
{ User-Equipment-Info-Value }

For PS charging, when the User-Equipment-Info-Type AVP (AVP code 459) is set to IMEISV (0), the value within the
User-Equipment-Info-Value AVP (AVP code 460) is of type OctetString and shall be a UTF-8 encoded hexadecimal.
The composition of the IMEISV follows the definition in TS 23.003 [224] . If only IMEI is received a filler ‘F’ is used
to make it 16 digits.

For IMS charging, when the User-Equipment-Info-Type AVP (AVP code 459) is set to IMEISV (0), the value within the
User-Equipment-Info-Value AVP (AVP code 460) is of type OctetString and shall be a UTF-8 encoded decimal. The
composition of the IMEISV follows the definition in TS 23.003 [224]. If only IMEI is received the number of digits are
truncated to 15.

3GPP
Release 15 100 3GPP TS 32.299 V15.4.0 (2018-09)

7.2 3GPP specific AVPs

7.2.0 General
For the purpose of offline charging additional AVPs are used in ACR / ACA and for online charging additional AVPs are
used in CCR / CCA. All 3GPP specific AVPs mentioned are relevant for both offline and online charging unless
specifically excluded. The information is summarized in the following table 7.2.0.1 along with the AVP flag rules.

The 3GPP Charging Application uses the value 10415 (3GPP) as Vendor-Id.

Detailed descriptions of AVPs that are used specifically for 3GPP charging are provided in the subclauses below the
table. However, for AVPs that are just borrowed from other applications only the reference (e.g. TS 29.229 [204]), is
provided in the following table and the detailed description is not repeated.

Where 3GPP RADIUS VSAs are re-used, they shall be translated to Diameter AVPs as described in RFC 4005 [407]
with the exception that the 'M' flag shall be set.

3GPP
Release 15 101 3GPP TS 32.299 V15.4.0 (2018-09)

Table 7.2.0.1: 3GPP specific AVPs

3GPP
Release 15 102 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
3GPP-Charging-Characteristics 13 refer [207]
X - X -
3GPP-Charging-Id 2 refer [207]
X - X -
3GPP-GGSN-MCC-MNC 9 refer [207]
X - X -
3GPP-IMSI 1 refer [207]
- - X -
3GPP-IMSI-MCC-MNC 8 refer [207]
X - X -
3GPP-MS-TimeZone 23 refer [207]
X - X -
3GPP-NSAPI 10 refer [207]
X - X -

3GPP-OC-Specific-Reduction 1320 - - - X Grouped M

3GPP-OC-Rating-Group 1321 - - - X Unsigned32 M

3GPP-OC-Request-Type 1322 - - - X Enumerated M

3GPP-PDP-Type 3
X - X - refer [207]
3GPP-PS-Data-Off-Status 4406 V,M -
X - X - Enumerated
3GPP-RAT-Type 21 refer [207]
X - X -
3GPP-Selection-Mode 12 refer [207]
X - X -
3GPP-Session-Stop-Indicator 11 refer [207]
- - X -
3GPP-SGSN-MCC-MNC 18 refer [207]
X - X -
3GPP-User-Location-Info 22 refer [207]
X - X -
Access-Availability-Change-Reason 2833 refer [215]
X - - -
Access-Network-Charging-Identifier-Value
503 X - X - refer [214]
Access-Network-Info-Change Grouped - -
4401 X - - - V,M
Access-Network-Information OctetString - -
1263 X - X - V,M
Access-Transfer-Information Grouped - -
2709 X - X - V,M
Access-Transfer-Type Enumerated - -
2710 X - X - V,M
Account-Expiration 2309 Time - -
- - - X V,M
Accumulated-Cost 2052 Grouped - -
- - - X V,M
Accuracy 3137 refer [245]
X - - -
Adaptations 1217 Enumerated - -
- - X - V,M
ADC-Rule-Base-Name 1095 refer [215] - -
X - X -
Additional-Content-Information 1207 Grouped - -
- - X - V,M
Additional-Exception-Reports 3936 Enumerated - -
X - X - V,M
Additional-Type-Information 1205 UTF8String - -
- - X - V,M
Address-Data 897 UTF8String - -
X - X - V,M
Address-Domain 898 Grouped - -
X - X - V,M
Addressee-Type 1208 Enumerated - -
X - X - V,M
Address-Type 899 Enumerated - -
X - X - V,M

3GPP
Release 15 103 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
AF-Charging-Identifier 505 refer [214]
X - X -
AF-Correlation-Information 1276 Grouped
X - X - V,M - -
Allocation-Retention-Priority 1034 refer [215]
X - X -
Alternate-Charged-Party-Address 1280 UTF8String - -
X - - - V.M
Announcement-Identifier 3905 Unsigned32 - -
- - - X V,M
Announcement-Information 3904 Grouped - -
- - - X V,M
Announcement-Order 3906 - -
- - - X Unsigned32 V,M
Announcing-PLMN-ID 4408 - -
X - - - UTF8String V,M
Announcing-UE-HPLMN-Identifier 3426 UTF8String - -
X - X - V.M
Announcing-UE-VPLMN-Identifier 3427 UTF8String - -
X - X - V.M
AoC-Cost-Information 2053 Grouped - -
- - - X V,M
AoC-Format 2310 Enumerated - -
- - X - V,M
AoC-Information 2054 Grouped - -
- - X X V.M
AoC-Request-Type 2055 Enumerated - -
- - X - V.M
AoC-Service 2311 Grouped - -
- - X - V,M
AoC-Service-Obligatory-Type 2312 Enumerated - -
- - X - V,M
AoC-Service-Type 2313 Enumerated - -
- - X - V,M
AoC-Subscription-Information 2314 Grouped - -
- - X - V,M
API-Content 1309 UTF8String - -
X - X - V M
API-Direction 1310 Enumerated - -
X - X - V M
API-Identifier 1311 OctetString - -
X - X - V M
API-Invocation-Timestamp 1312 Time - -
X - X - V M
API-Network-Service-Node 1315 - -
X - X - Enumerated V M
API-Result-Code 1313 Unsigned32 - -
X - X - V M
API-Size 1314 - -
X - X - Unsigned64 V M
APN-Rate-Control 3933 Grouped - -
X - X - V,M
APN-Rate-Control-Downlink 3934 Grouped - -
X - X - V,M
APN-Rate-Control-Uplink 3935 Grouped - -
X - X - V,M
Applic-ID 1218 UTF8String - -
- - X - V,M

Application-Port-Identifer 3010 X - X - refer[231]

- -
Application-Provided-Called-Party-Address 837 X - X - UTF8String V,M
- -
Application-Server 836 X - X - UTF8String V,M

Application-Server-ID 2101 X - X - refer[223]

Application-Service-Provider-Identity 532 X - - - refer[214]

- -
Application-Server-Information 850 X - X - Grouped V,M

3GPP
Release 15 104 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
Application-Service-Type 2102 X - X - refer[223]

Application-Session-ID 2103 X - X - refer[223]

- -
Application-Specific-Data 3458 X - - - OctetString V,M
Associated-Party-Address 2035 - -
X - X - UTF8String V,M
- -
Associated-URI 856 X - X - UTF8String V,M
- -
Authorised-QoS 849 - - - - UTF8String V,M
- -
Aux-Applic-Info 1219 - - X - UTF8String V,M
- -
Base-Time-Interval 1265 - - - X Unsigned32 V,M
- -
Basic-Service-Code 3411 - - X - Grouped V,M
- -
Bearer-Capability 3412 - - X - OctetString V,M
- -
Bearer-Service 854 X - X - OctetString V,M
BSSID 2716 UTF8String - -
X - X - V,M
- -
Called-Asserted-Identity 1250 X - X - UTF8String V,M
- -
Called-Identity 3916 X - X - UTF8String V,M
- -
Called-Identity-Change 3917 X - X - Grouped V,M
- -
Called-Party-Address 832 X - X - UTF8String V,M
- -
Calling-Party-Address 831 X - X - UTF8String V,M
- -
Carrier-Select-Routing-Information 2023 X - X - UTF8String V,M
- -
Cause-Code 861 X - X - Integer32 V,M
- -
Cellular-Network-Information 3924 X - X - OctetString V,M
- -
CG-Address 846 X - X - Address V,M
- -
Change-Condition 2037 X - - - Integer32 V,M
- -
Change-Time 2038 X - X - Time V,M
- -
Charge-Reason-Code 2118 - - X X Enumerated V,M
- -
Charged-Party 857 X - - - UTF8String V,M
- -
Charging-Characteristics-Selection-Mode 2066 X - X - Enumerated V,M
- -
Charging-Per-IP-CAN-Session-Indicator 4400 X - - - Enumerated V,M

Charging-Rule-Base-Name 1004 X - X - refer [215]

- -
Civic-Address-Information 1305 X - X - UTF8String V M
- -
Class-Identifier 1214 - - X - Enumerated V,M
- -
Client-Address 2018 X - X - Address V,M

CN-IP-Multicast-Distribution 921 X - - - refer [207]

- -
CN-Operator-Selection-Entity 3421 X - - - Enumerated V,M

Communication-Failure-Information 4300 X - - - refer [244]

- -
Content-Class 1220 - - X - Enumerated V,M

3GPP
Release 15 105 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
- -
Content-Disposition 828 X - X - UTF8String V,M

Content-ID 2116 X - X - refer[223]

Content-Provider-ID 2117 X - X - refer[223]

- -
Content-Length 827 X - X - Unsigned32 V,M
- -
Content-Size 1206 - - X - Unsigned32 V,M
- -
Content-Type 826 X - X - UTF8String V,M
- -
Coverage-Info 3459 X - - - Grouped V,M
- -
Coverage-Status 3428 X - - - Enumerated V,M
- -
CP-CIoT-EPS-Optimisation-Indicator 3930 X - - - Enumerated V,M
- -
CPDT-Information 3927 X - - - Grouped V,M
- -
CSG-Access-Mode 2317 X - X - Enumerated V,M

CSG-Id 1437 X - X - refer[219]

- -
CSG-Membership-Indication 2318 X - X - Enumerated V,M
- -
CUG-Information 2304 X - X - OctetString V,M
- -
Current-Tariff 2056 - - X X Grouped V,M
- -
Data-Coding-Scheme 2001 X - X - Integer32 V,M

DCD-Information 2115 X - X - refer[223]

- -
Deferred-Location-Event-Type 1230 - - X - UTF8String V,M
- -
Delivery-Report-Requested 1216 X - X - Enumerated V,M

Delivery-Status 2104 X - X - refer[223]

- -
Destination-Interface 2002 X - X - Grouped V,M
- -
Diagnostics 2039 X - X - Integer32 V,M
Discoveree-UE-HPLMN-Identifier UTF8String - -
4402 X - X - V.M
Discoveree-UE-VPLMN-Identifier UTF8String - -
4403 X - X - V.M
Discoverer-UE-HPLMN-Identifier UTF8String - -
4404 X - X - V.M
Discoverer-UE-VPLMN-Identifier UTF8String - -
4405 X - X - V.M
- -
Domain-Name 1200 X - X - UTF8String V,M
- -
DRM-Content 1221 - - X - Enumerated V,M
- -
Dynamic-Address-Flag 2051 X - X - Enumerated V,M
- -
Dynamic-Address-Flag-Extension 2068 X - X - Enumerated V,M
- -
Early-Media-Description 1272 X - - - Grouped V,M
- -
Enhanced-Diagnostics 3901 X - X - Grouped V,M
- -
Envelope 1266 - - X - Grouped V,M

Envelope-End-Time 1267 - - X - Time V,M

- -
Envelope-Reporting 1268 - - - X Enumerated V,M

3GPP
Release 15 106 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
- -
Envelope-Start-Time 1269 - - X - Time V,M
- -
EPDG-Address 3425 X - - - Address V,M
- -
EPS-Location-Information 1496 X - - - refer [219]

Event 825 X - X - UTF8String V,M

- -
Event-Charging-TimeStamp 1258 - - X - Time V,M

Event-Type 823 X - X - Grouped V,M

Expires 888 X - X - Unsigned32 V,M

- -
Exposure-Function-API-Information 1316 X - X - Grouped V M
- -
External-Identifier 3111 X - X - refer [245]
- -
Feature-List 630 X X X X refer [204] V,M
- -
Feature-List-ID 629 X X X X refer [204] V,M
- -
FE-Identifier-List 4413 X - - - UTF8String V,M
- -
File-Repair-Supported 1224 X - X - Enumerated V,M
- -
Fixed-User-Location-Info 2825 X - X - refer [215]

Flows 510 - - X - refer [214]

Forwarding-Pending 3415 - - X - Enumerated V,M

- -
From-Address 2708 X - X - UTF8String V,M
- -
GGSN-Address 847 X - X - Address V,M
- -
Guaranteed-Bitrate-UL 1026 X - X - refer[215]
- -
IM-Information 2110 X - X - refer[223]
- -
IMS-Application-Reference-Identifier 2601 X - - - UTF8String V,M
- -
IMS-Charging-Identifier 841 X - X - UTF8String V,M
- -
IMS-Communication-Service-Identifier 1281 X - X - UTF8String V,M
- -
IMS-Emergency-Indicator 2322 X - - - Enumerated V,M
- -
IMS-Information 876 X - X - Grouped V,M
- -
IMS-Visited-Network-Identifier 2713 X - X - UTF8String V,M
- -
IMSI-Unauthenticated-Flag 2308 X - X - Enumerated V,M
- -
Incoming-Trunk-Group-Id 852 X - - - UTF8String V,M
- -
Incremental-Cost 2062 - - - X Grouped V,M
- -
Initial-IMS-Charging-Identifier 2321 X - X - UTF8String V,M
- -
Instance-Id 3402 X - X - UTF8String V,M
- -
Interface-Id 2003 - - X - UTF8String V,M
- -
Interface-Port 2004 - - X - UTF8String V,M
- -
Interface-Text 2005 - - X - UTF8String V,M
- -
Interface-Type 2006 - - X - Enumerated V,M

3GPP
Release 15 107 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
- -
Inter-Operator-Identifier 838 X - X - Grouped V,M
- -
Inter-UE-Transfer 3902 X - X - Enumerated V,M
- -
IP-Realm-Default-Indication 2603 X - - - Enumerated V,M
- -
ISUP-Cause 3416 X - X - Grouped V,M
- -
X - X - V,M
ISUP-Cause-Diagnostics 3422 OctetString
- -
X - X - V,M
ISUP-Cause-Location 3423 Unsigned32
- -
X - X - V,M
ISUP-Cause-Value 3424 Unsigned32
- -
- - X - V,M
ISUP-Location-Number 3414 OctetString
- -
Language 3914 - - - X V,M
UTF8String
- -
Layer-2-Group-ID 3429 - - X - V,M
OctetString
1231 - - X - - -
LCS-APN V,M
UTF8String
- -
- - X - V,M
LCS-Client-Dialed-By-MS 1233 UTF8String
- -
- - X - V,M
LCS-Client-External-ID 1234 UTF8String
- -
- - X - V,M
LCS-Client-Id 1232 Grouped
- -
- - X - V,M
LCS-Client-Name 1235 Grouped
- -
- - X - V,M
LCS-Client-Type 1241 Enumerated
- -
- - X - V,M
LCS-Data-Coding-Scheme 1236 UTF8String
- -
- - X - V,M
LCS-Format-Indicator 1237 Enumerated
- -
LCS-Information 878 - - X - Grouped V,M
- -
- - X - V,M
LCS-Name-String 1238 UTF8String
- -
- - X - V,M
LCS-Requestor-ID 1239 Grouped
- -
- - X - V,M
LCS-Requestor-ID-String 1240 UTF8String
- -
2604 X - - - Enumerated V,M
Local-GW-Inserted-Indication
- -
2063 X - - - Unsigned32 V,M
Local-Sequence-Number
- -
- - X - V,M
Location-Estimate 1242 OctetString
- -
- - X - V,M
Location-Estimate-Type 1243 Enumerated
X - - - V,M
Location-Info 3460 Grouped
- - X - V,M
Location-Type 1244 Grouped
- - - X V,M
Low-Balance-Indication 2020 Enumerated
X - - - V,M
Low-Priority-Indicator 2602 Enumerated
Mandatory-Capability 604 X - - - refer [204]

Max-Requested-Bandwidth-DL 515 X - X - refer [214]

- -
Max-Requested-Bandwidth-UL 516 X - X - refer [214]

Maximum-Detection-Time 3131 X - - - refer [245]

Maximum-Number-of-Reports 3128 X - - - refer [245]

3GPP
Release 15 108 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
- -
MBMS-2G-3G-Indicator 907 X - X - refer [207]
- -
MBMS-Charged-Party 2323 X - - - Enumerated V,M

MBMS-Data-Transfer-Start 929 X - - - refer [207]

MBMS-Data-Transfer-Stop 930 X - - - refer [207]

MBMS-GW-Address 2307 X - - - Address V,M

- -
MBMS-Information 880 X - X - Grouped V,M
MBMS-Service-Area - -
903 X - X - refer [207]
MBMS-Service-Type - -
906 X - X - refer [207]
MBMS-Session-Identity - -
908 X - X - refer [207]
MBMS-User-Service-Type - -
1225 X - X - Enumerated V,M
- -
Media-Initiator-Flag 882 X - X - Enumerated V,M
- -
Media-Initiator-Party 1288 X - X - UTF8String V,M
- -
Message-Body 889 X - X - Grouped V,M
- -
Message-Class 1213 X - X - Grouped V,M
- -
Message-ID 1210 X - X - UTF8String V,M

Message-Size 1212 X - X - Unsigned32 V,M

Message-Type 1211 X - X - Enumerated V,M

MMBox-Storage-Requested 1248 - - X - Enumerated V,M

- -
MM-Content-Type 1203 - - X - Grouped V,M
- -
MME-Name 2402 X - - - refer [229]
- -
MME-Number-for-MT-SMS 1645 X - - - refer [230]
- -
MME-Realm 2408 X - - - refer [229]

MMS-Information 877 - - X - Grouped V,M

MMTel-Information 2030 X - X - Grouped V,M

X - - -
MMTel-SService-Type 2031 - X Unsigned32 V,M
X - - -
Monitored-PLMN-Identifier 3430 - X UTF8String V,M
- -
Monitoring-Duration 3130 X - - - refer [245]
- -
Monitoring-Event-Config-Status 3142 X - - - refer [245]
X - - -
Monitoring-Event-Configuration-Activity 3919 - - Integer32 V,M

Monitoring-Event-Functionality 3922 X - - - Integer32 V,M

X - - -
Monitoring-Event-Information 3921 - - Grouped V,M
X - - -
Monitoring-Event-Report-Data 3920 - - Grouped V,M
- -
Monitoring-Event-Report-Number 3923 X - - - Unsigned32 V,M

Monitoring-Type 3127 X - - - refer [245]

X - - -
Monitoring-UE-HPLMN-Identifier 3431 - X UTF8String V,M

3GPP
Release 15 109 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
X -
Monitoring-UE-Identifier 3432 - X UTF8String V,M
X - - -
Monitoring-UE-VPLMN-Identifier 3433 - X UTF8String V,M

MONTE-Location-Type 3136 X - - - refer [245]

X -
MSC-Address 3417 - X OctetString V,M
- -
MSISDN 701 X - X - refer [221]
- -
MTC-IWF-Address 3406 X - X - Address V,M
refer [215] - -
NBIFOM-Mode 2830 X - X -
refer [215] - -
NBIFOM-Support 2831 X - X -
- -
Neighbour-Node-Address 2705 X - - - V,M
Address
- -
Network-Call-Reference-Number 3418 - - X - V,M
OctetString
- -
Next-Tariff 2057 - - X X Grouped V/M
- -
NIDD-Submission 3928 X - - - Grouped V/M
- -
X - - - V,M
NNI-Information 2703 Grouped
- -
X - - - V,M
NNI-Type 2704 Enumerated
Node-Functionality 862 X - X - Enumerated V,M

Node-Id 2064 X - X - UTF8String V,M

- -
Number-Of-Diversions 2034 X - X - Unsigned32 V,M
- -
Number-Of-Messages-Sent 2019 X - X - Unsigned32 V,M
Number-Of-Messages-Successfully- - -
2111 X - X - refer[223]
Exploded
Number-Of-Messages-Successfully-Sent 2112 X - X - refer[223]

Number-Of-Participants 885 X - X - Unsigned32 V,M

- -
Number-Of-Received-Talk-Bursts 1282 X - - - Unsigned32 V,M
- -
Number-Of-Talk-Bursts 1283 X - - - Unsigned32 V,M
- -
Number-Of-UE-Per-Location-Configuration 4306 X - - - refer [244]

Number-Of-UE-Per-Location-Report 4307 X - - - refer [244]

Number-Portability-Routing-Information 2024 X - X - UTF8String V,M

- -
Offline-Charging 1278 - - - X Grouped V,M
- -
Online-Charging-Flag 2303 X - - - Enumerated V,M
- -
Optional-Capability 605 X - - - refer [204]
refer [238] - -
Origin-App-Layer-User-Id 3600 X - X -
- -
Originating-IOI 839 X - X - UTF8String V,M
- -
Originator 864 X - X - Enumerated V,M
- -
Originator-Address 886 X - X - Grouped V,M
- -
Originator-Interface 2009 X - X - Grouped V,M
- -
Originator-Received-Address 2027 X - X - Grouped V,M

3GPP
Release 15 110 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
- -
Originator-SCCP-Address 2008 X - X - Address V,M
- -
Outgoing-Session-Id 2320 X - X - UTF8String V,M
- -
Outgoing-Trunk-Group-Id 853 X - - - UTF8String V,M
- -
Participant-Access-Priority 1259 X - X - Enumerated V,M
- -
Participant-Action-Type 2049 X - X - Enumerated V,M
- -
Participant-Group 1260 X - X - Grouped V,M
- -
Participants-Involved 887 X - X - UTF8String V,M
- -
PC3-Control-Protocol-Cause 3434 X - X - Integer32 V,M
Integer32 - -
PC3-EPC-Control-Protocol-Cause 3435 X - X - V,M
Enumerated - -
PC5-Radio-Technology 1300 X - X - V M
- -
PDN-Connection-Charging-ID 2050 X - X - Unsigned32 V,M
- -
PDP-Address 1227 X - X - Address V,M
- -
PDP-Address-Prefix-Length 2606 X - X - Unsigned32 V,M
- -
PDP-Context-Type 1247 X - X - Enumerated V,M
- -
Play-Alternative 3913 - - - X Enumerated V,M
- -
PoC-Change-Condition 1261 X - - - Enumerated V,M
- -
PoC-Change-Time 1262 X - - - Time V,M
- -
PoC-Controlling-Address 858 X - X - UTF8String V,M
- -
PoC-Event-Type 2025 X - X - Enumerated V,M
- -
PoC-Group-Name 859 X - X - UTF8String V,M
- -
PoC-Information 879 X - X - Grouped V,M
- -
PoC-Server-Role 883 X - X - Enumerated V,M
- -
PoC-Session-Id 1229 X - X - UTF8String V,M
- -
PoC-Session-Initiation-type 1277 X - X - Enumerated V,M
- -
PoC-Session-Type 884 X - X - Enumerated V,M
- -
PoC-User-Role 1252 X - X - Grouped V,M

PoC-User-Role-IDs 1253 X - X - UTF8String V,M

PoC-User-Role-Info-Units 1254 X - X - Enumerated V,M

Positioning-Data - - X - V,M
1245 UTF8String
- -
Preferred-AoC-Currency - - X - V,M
2315 Unsigned32
Presence-Reporting-Area-Identifier X - X X
2821 refer [215]
Presence-Reporting-Area-Information X - X X
2822 refer [215]
- -
Presence-Reporting-Area-Elements-List X - X X
2820 refer [215]
- -
Presence-Reporting-Area-Status X - X -
2823 refer [215]
Priority 1209 - - X - Enumerated V,M

3GPP
Release 15 111 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
- -
Priority-Indication 3006 X - X - refer [231]
- -
Priority-Level 1046 X - X - refer [215]
- -
Privacy-Indicator 3915 - - - X Enumerated V,M
ProSe-3rd-Party-Application-ID - -
3440 X - X - UTF8String V,M

ProSe-App-Id 3811 X - X -
refer [239]
ProSe-Direct-Communication-Reception- - -
3461 X - - - V,M
Data-Container Grouped
ProSe-Direct-Communication- Transmission- - -
3441 X - - - V,M
Data-Container Grouped
- -
ProSe-Direct-Discovery-Model 3442 X - X - V,M
Enumerated
- -
ProSe-Event-Type 3443 X - X - V,M
Enumerated
- -
ProSe-Function-ID 3602 X - X - refer [238]
- -
ProSe-Function-IP-Address 3444 X - X - V,M
Address
- -
ProSe-Function-PLMN-Identifier 3457 X - X - UTF8String V,M
- -
ProSe-Functionality 3445 X - X - V,M
Enumerated
- -
ProSe-Group-IP-Multicast-Address 3446 X - - - V,M
Address
- -
ProSe-Information 3447 X - X - V,M
Grouped
Enumerated - -
ProSe-Range-Class 3448 X - X - V,M
Enumerated
ProSe-Reason-For-Cancellation 3449 X - X - V,M
Time - -
ProSe-Request-Timestamp 3450 X - X - V,M
Enumerated - -
ProSe-Role-Of-UE 3451 X - X - V,M
Address - -
ProSe-Source-IP-Address 3452 - - X - V,M
- - - OctetString - -
ProSe-Target-Layer-2-ID 4410 X V,M
OctetString - -
ProSe-UE-ID 3453 - - X - V,M
- - - OctetString - -
ProSe-UE-to-Network-Relay-UE-ID 4409 X V,M
refer [239] - -
ProSe-Validity-Timer 3815 X - X -
Enumerated - -
Proximity-Alert-Indication 3454 X - X - V,M
Time - -
Proximity-Alert-Timestamp 3455 X - X - V,M
Time
Proximity-Cancellation-Timestamp 3456 X - X - V,M

PS-Append-Free-Format-Data 867 X - - X Enumerated V,M

- -
PS-Free-Format-Data 866 X - - X OctetString V,M
- -
PS-Furnish-Charging-Information 865 X - - X Grouped V,M
- -
PS-Information 874 X - X X Grouped V,M
- -
QoS-Information 1016 X - X - refer [215]
- -
QoS-Class-Identifier 1028 X - X - refer [215]
- -
Quota-Consumption-Time 881 - - - X Unsigned32 V,M
- -
Quota-Holding-Time 871 - - - X Unsigned32 V,M

3GPP
Release 15 112 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
Quota-Indicator 3912 - - - X Enumerated V,M

Radio-Frequency 3462 X - - - OctetString V,M

- -
Radio-Parameter-Set-Info 3463 X - - - Grouped V.M
- -
Radio-Parameter-Set-Values 3464 X - - - OctetString V,M
- -
Radio-Resources-Indicator 3465 X - - - Integer32 V,M
- -
RAI 909 X - X - refer [207]
- -
RAN-End-Time 1301 X - - - Time V M

RAN-NAS-Release-Cause 2819 X - X - refer [215]

- -
RAN-Secondary-RAT-Usage-Report 1302 X - - - Grouped V M
- -
RAN-Start-Time 1303 X - - - Time V M
- -
Rate-Control-Max-Message-Size 3937 X - X - Unsigned32 V,M
- -
Rate-Control-Max-Rate 3938 X - X - Unsigned32 V,M
- -
Rate-Control-Time-Unit 3939 X - X - Unsigned32 V,M
- -
Rate-Element 2058 - - X X Grouped V,M
- -
Reachability-Information 3140 X - - - refer [245]
- -
Read-Reply-Report-Requested 1222 - - X - Enumerated V,M
- 
Real-Time-Tariff-Information 2305 X - X - Grouped V,M
- 
Reason-Header 3401 X - X - UTF8String V,M
- -
Received-Talk-Burst-Time 1284 X - - - Unsigned32 V,M

Received-Talk-Burst-Volume 1285 X - - - Unsigned32 V,M

- -
Recipient-Address 1201 X - X - Grouped V,M
- -
Recipient-Info 2026 X - X - Grouped V,M
- -
Recipient-Received-Address 2028 X - X - Grouped V,M
- -
Recipient-SCCP-Address 2010 X - X - Address V,M
- -
Reference-Number 3007 X - X - refer [231]
- -
Refund-Information 2022 - - X X OctetString V,M
- -
Related-Change-Condition-Information 3925 X - - - Grouped V,M
- -
Related-Trigger 3926 - - X - Grouped V,M
- -
Related-IMS-Charging-Identifier 2711 X - X V,M
UTF8String
- -
Related-IMS-Charging-Identifier-Node 2712 X - X Address V,M
- -
Relationship-Mode 2706 X - - - V,M
Enumerated
- -
Relay-IP-address 4411 X - - - V,M
Address
- -
Remaining-Balance 2021 - - - X Grouped V,M

Reply-Applic-ID 1223 - - X - UTF8String V,M

- -
Reply-Path-Requested 2011 X - X - Enumerated V,M

3GPP
Release 15 113 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
Reporting-Reason 872 - - X - Enumerated V,M
- -
Requested-Party-Address 1251 X - X - UTF8String V,M
- -
Requested-PLMN-Identifier 3436 X - X - UTF8String V,M
- -
Requesting-EPUID 3816 X - X - refer [239]
- -
Requestor-PLMN-Identifier 3437 X - X - UTF8String V,M

Required-MBMS-Bearer-Capabilities 901 X - X - refer [207]

- -
Role-Of-Node 829 X - X - Enumerated V,M

Role-Of-ProSe-Function 3438 X - X - Enumerated V,M

Route-Header-Received 3403 X - - - UTF8String V,M

- -
Route-Header-Transmitted 3404 X - - - UTF8String V,M
- -
RRC-Cause-Counter 4318 X - - - refer [244]
- -
Scale-Factor 2059 - - X X Grouped V,M
- -
SCEF-Address 1317 X - X - Address V M
- -
SCEF-ID 3125 X - - - refer [245]
- -
SCEF-Reference-ID 3124 X - - - refer [245]
- -
SCS-Address 3941 X - X - Address V,M
- -
SCS-AS-Address 3940 X - X - Grouped V,M
- -
SCS-Realm 3942 X - X - DiameterIdentity V,M

SDP-Answer-Timestamp 1275 X - - - Time V,M

- -
SDP-Media-Component 843 X - X - Grouped V,M
- -
SDP-Media-Description 845 X - X - UTF8String V,M

SDP-Media-Name 844 X - X - UTF8String V,M

SDP-Offer-Timestamp 1274 X - - - Time V,M

- -
SDP-Session-Description 842 X - X - UTF8String V,M

SDP-TimeStamps 1273 X - - - Grouped V,M

- -
SDP-Type 2036 X - X - Enumerated V,M
- -
Secondary-RAT-Type 1304 X - - - V M
OctetString
- -
Serving-Node 2401 X - X -
refer [231]
- -
Serving-Node-Identity 3929 X - - - DiameterIdentity V,M
- -
Served-Party-IP-Address 848 X - - - Address V,M
- -
Server-Capabilities 603 X - - - refer [204]
- -
Server-Name 602 X - - - refer [204]
- -
Service-Data-Container 2040 X - - - Grouped V,M

Service-Generic-Information 1256 X - X - refer [223]

- -
Service-Id 855 X - X - UTF8String V,M

3GPP
Release 15 114 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
Service-Information 873 X - X X Grouped V,M
X - - -
Service-Mode 2032 - X Unsigned32 V,M
- -
Service-Specific-Data 863 X - X - UTF8String V,M
- -
Service-Specific-Info 1249 X - X - Grouped V,M
- -
Service-Specific-Type 1257 X - X - Unsigned32 V,M
X - - -
Serving-Node-Type 2047 - X Enumerated V,M
- -
Serving-PLMN-Rate-Control 4310 X - X -
refer [244]
- -
Session-Direction 2707 X - - - V,M
Enumerated
X - - -
Session-Priority 650 - X refer [204]
X - - -
SGi-PtP-Tunnelling-Method 3931 - X V,M
Enumerated
- -
SGSN-Address 1228 X - X - Address V,M
- -
SGW-Address 2067 X - - - Address V,M
- -
SGW-Change 2065 X - - - Enumerated V,M
- -
SIP-Method 824 X - X - UTF8String V,M
- -
SIP-Request-Timestamp 834 X - X - Time V,M
- -
SIP-Request-Timestamp-Fraction 2301 X - X - Unsigned32 V,M
- -
SIP-Response-Timestamp 835 X - X - Time V,M
- -
SIP-Response-Timestamp-Fraction 2302 X - X - Unsigned32 V,M
- -
SM-Device-Trigger-Indicator 3407 X - X - Enumerated V,M
- -
SM-Device-Trigger-Information 3405 X - X - Grouped V,M
- -
SM-Discharge-Time 2012 X - X - Time V,M
- -
SM-Message-Type 2007 X - X - Enumerated V,M
- -
SM-Protocol-ID 2013 X - X - OctetString V,M

SM-Sequence-Number 3408 X - - - Unsigned32 V,M

SM-Service-Type 2029 - - X - Enumerated V,M

- -
SM-Status 2014 X - X - OctetString V,M
- -
SM-User-Data-Header 2015 X - X - OctetString V,M
- -
SMS-Information 2000 X - X - Grouped V,M
- -
SMS-Node 2016 X - X - Enumerated V,M
- -
SMS-Result 3409 X - - - Unsigned32 V,M
- -
SMSC-Address 2017 X - X - Address V,M
- -
Sponsor-Identity 531 X - - - refer [214]
- -
SSID 1524 X - X - refer [237]
- -
Start-of-Charging 3419 - - X - Time V,M
- -
Start-Time 2041 X - X - Time V,M

3GPP
Release 15 115 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
- -
Status- AS-Code 2702 X - - - Enumerated V,M

Stop-Time 2042 X - X - Time V,M

- -
Submission-Time 1202 X - X - Time V,M
- - - -
Subscriber-Role 2033 - - Enumerated V,M
X X - -
Supported-Features 628 X X refer [204] V,M
X -
Supplementary-Service 2048 - X Grouped V,M
X - - -
TAD-Identifier 2717 - - Enumerated V,M

Talk-Burst-Exchange 1255 X - - - Grouped V,M

- -
Talk-Burst-Time 1286 X - - - Unsigned32 V,M
- -
Talk-Burst-Volume 1287 X - - - Unsigned32 V,M
3601 refer[238] - -
Target-App-Layer-User-Id X - X -
4412 X - - - Address VM - -
Target-IP-Address -
2060 Grouped - -
Tariff-Information X - X X V,M
2306 UTF8String - -
Tariff-XML X - - - V,M
1091 - -
TDF-IP-Address X - X - refer [215]
- - - -
Teleservice 3413 - X OctetString V,M
1401 refer [219] - -
Terminal-Information X - - -
- -
Terminating-IOI 840 X - X - UTF8String V,M
- -
Time-First-Reception 3466 X - - - Time V,M
- -
Time-First-Transmission 3467 X - - - Time V,M

Time-First-Usage 2043 X - - - Time V,M

Time-Indicator 3911 - - - X Unsigned32 V,M

- -
Time-Last-Usage 2044 X - - - Time V,M

Time-Quota-Mechanism 1270 - - - X Grouped V,M

Time-Quota-Threshold 868 - - - X Unsigned32 V,M

- -
Time-Quota-Type 1271 - - - X Enumerated V,M
- -
Time-Stamps 833 X - X - Grouped V,M
- -
Time-Usage 2045 X - - - Unsigned32 V,M
refer [239] - -
Time-Window 3818 X - X -
Unsigned32 - -
TLTRI 1318 X - X - V M
- -
TMGI 900 X - X - refer [207]
- -
Token-Text 1215 - - X - UTF8String V,M
- -
Total-Number-Of-Messages-Exploded 2113 X - X - refer [223]
- -
Total-Number-Of-Messages-Sent 2114 X - X - refer [223]
- -
Traffic-Data-Volumes 2046 X - - - Grouped V,M

3GPP
Release 15 116 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
Traffic-Steering-Policy-Identifier-DL 2836 refer [215]
X - - - - -
Traffic-Steering-Policy-Identifier-UL 2837 refer [215]
X - - - - -
- -
Transcoder-Inserted-Indication 2605 X - - - Enumerated V,M

Transit-IOI-List 2701 X - X - UTF8String V,M

Transmitter-Info 3468 X - - - Grouped V,M

Trigger 1264 - - X X Grouped V,M

- -
Trigger-Type 870 - - X X Enumerated V,M
- -
Trunk-Group-Id 851 X - - - Grouped V,M
- -
TTRI 1319 X - X - Unsigned32 V M
- -
TWAG-Address 3903 X - - - Address V,M
TWAN-User-Location-Info 2714 Grouped - -
X - X - V,M
- -
Type-Number 1204 - - X - Enumerated V,M

UDP-Source-Port 2806 X - X - refer [215]

UE-Local-IP-Address 2805 X - X - refer [215]

- -
UE-Reachability-Configuration 3129 X - - - refer [245]
- -
UNI-PDU-CP-Only-Flag 3932 X - X - Enumerated V,M
- -
Unit-Cost 2061 - - X X Grouped V,M

Unit-Quota-Threshold 1226 - - - X Unsigned32 V,M

- -
Unused-Quota-Timer 4407 - - X X Unsigned32 V,M
Usage-Information-Report-Sequence- - -
3439 X - - - Integer32 V,M
Number
- -
User-CSG-Information 2319 X - X X Grouped V,M
- -
User-Data 606 X - - - refer [204]
- -
User-Location-Info-Time 2812 X - X - refer [215]

User-Participating-Type 1279 X - X - Enumerated V,M

- -
User–Session-Id 830 X - X - UTF8String V,M

UWAN-User-Location-Info 3918 X - X - Grouped V,M

- -
VAS-Id 1102 - - X - refer [213]
- -
Variable-Part 3907 - - - X Grouped V,M

Variable-Part-Order 3908 - - - X Unsigned32 V,M

- -
Variable-Part-Type 3909 - - - X Unsigned32 V,M
- -
Variable-Part-Value 3910 - - - X UTF8String V,M
- -
VASP-Id 1101 - - X - refer [213]
- -
VCS-Information 3410 X - X - Grouped V,M
- -
Visited-PLMN-Id 1407 X - - - refer [230]
- -
VLR-Number 3420 X - X - OctetString V,M

3GPP
Release 15 117 3GPP TS 32.299 V15.4.0 (2018-09)

Used in AVP Flag rules

AVP Value
AVP Name A Must May Should Mu
Code C ACA CCR CCA Type not st
R not
Volume-Quota-Threshold 869 - - - X Unsigned32 V,M
WLAN-Link-Layer-Id 3821 X - X - refer [239] - -
WLAN-Operator-Id 1306 X - X - Grouped V - - M
WLAN-Operator-Name 1307 X - X - UTF8String V - - M
WLAN-PLMN-Id 1308 X - X - UTF8String V - - M

NOTE: Per TS 29.230 [206] the following AVP codes are reserved for the present document:
Before Rel-8: 800 to 899, 1200 to 1299.
Rel-8: 2000 to 2199.
Rel-9: 2300 to 2399.
Rel-10: 2600 to 2699.
Rel-11: 2700 to 2799.
Rel-12: 3400 to 3499.
Rel-13: 3900 to 3999.
Rel-14: 4400 to 4499.
Rel-15: 1300 to 1399.

7.2.0A Access-Network-Info-Change AVP

The Access-Network-Info-Change AVP (AVP code 4401) is of type Grouped and holds information on subsequent
changes in one or two SIP P-header(s) "P-Access-Network-Info" together with the time it was acquired.

It has the following ABNF grammar:

Access-Network-Info-Change :: = < AVP Header: 4401>

* [ Access-Network-Information ]
[ Cellular-Network-Information ]
[ Change-Time ]

7.2.0aA 3GPP-PS-Data-Off-Status AVP

The 3GPP-PS-Data-Off-Status AVP (AVP code 4406) is of type Enumerated and indicated the change in 3GPP PS Data
off status of UE. The following values are defined:

0 Active
1 Inactive

7.2.1 Access-Network-Information AVP

The Access-Network-Information AVP (AVP code 1263) is of type OctetString and indicates one instance of the SIP P-
header "P-Access-Network-Info". In SIP, as per RFC 7315 [404], the content of the "P-Access-Network-Info" header is
known as the access-net-spec. When multiple access-net-spec values are transported in a single "P-Access-Network-
Info" header in comma-separated format, then multiple Access-Network-Information AVPs are used with one access-
net-spec value included in each AVP.

For access types and access classes associated to 3GPP accesses:

- For GERAN access, the cgi-3gpp field contains the CGI;

- For UTRAN access, the utran-cell-id-3gpp field contains the LAI and CI, and the utran-sai-3gpp field contains
the SAI;

- For E-UTRAN access, the utran-cell-id-3gpp field contains the TAI and ECGI;

- For NR access, the utran-cell-id-3gpp field contains the TAI and NCI.

3GPP
Release 15 118 3GPP TS 32.299 V15.4.0 (2018-09)

The SIP "P-Access-Network-Info" header specified in TS 24.229 [202] clause 7.2A.4 contains in particular:

For access types and access classes associated to trusted WLAN access: the i-wlan-node-id field contains the BSSID,
and when available, the operator-specific-GI field contains the Geographical Identifier.

For access types and access classes associated to untrusted WLAN access, the i-wlan-node-id field contains the BSSID,
and UE local IP address, ePDG IP Address, and TCP source port, UDP source port are contained in corresponding
dedicated fields.

7.2.1A Access-Transfer-Information AVP

The Access-Transfer-Information AVP (AVP code 2709) is of type Grouped and provides information on access transfer
for IMS service continuity.

It has the following ABNF grammar:

Access-Transfer-Information :: = < AVP Header: 2709>

[ Access-Transfer-Type ]
* [ Access-Network-Information ]
[ Cellular-Network-Information ]
[ Inter-UE-Transfer ]
[ User-Equipment-Info ]
[ Instance-Id ]
[ Related-IMS-Charging-Identifier ]
[ Related-IMS-Charging-Identifier-Node ]
[ Change-Time ]

7.2.1B Access-Transfer-Type AVP

The Access-Transfer-Type AVP (AVP code 2710) is of type Enumerated and indicates which type of transfer occurred
for IMS service continuity. The following values are defined:

0 PS to CS Transfer
1 CS to PS Transfer
2 PS to PS Transfer
3 CS to CS Transfer

7.2.2 Account-Expiration AVP

The Account-Expiration AVP (AVP code 2309) is of type Time and indicates the subscriber account expiration date and
time of day.

7.2.3 Accumulated-Cost AVP

The Accumulated-Cost AVP (AVP code 2052) is of type Grouped and holds the accumulated cost for the ongoing
session.

It has the following ABNF grammar:

Accumulated-Cost:: = < AVP Header: 2052 >

{ Value-Digits }
[ Exponent ]

7.2.4 Adaptations AVP

The Adaptations AVP (AVP code 1217) is of type Enumerated and indicates whether the originator allows adaptation of
the content (default Yes). The values indicating whether adaptations are allowed are:

3GPP
Release 15 119 3GPP TS 32.299 V15.4.0 (2018-09)

0 Yes
1 No

7.2.5 Additional-Content-Information AVP

The Additional-Content-Information AVP (AVPcode 1207) is of type Grouped and identifies any subsequent content
types. It is used to identify each content (including re-occurences) within an MM when the Type-Number AVP or
Additional-Type-Information AVP from the Content-Type AVP indicate a multi-part content.

It has the following ABNF grammar:

Additional-Content-Information:: = < AVP Header: 1207 >

[ Type-Number ]
[ Additional-Type-Information ]
[ Content-Size ]

7.2.5A Additional-Exception-Reports AVP

The Additional-Exception-Reports AVP (AVP code 3936) is of type Enumerated and indicates whether additional
exception reports are allowed when maximum rate is reached. It has the following values:

0 Not allowed
1 Allowed

7.2.6 Additional-Type-Information AVP

The Additional-Type-Information AVP (AVP code 1205) is of type UTF8String and identifies any additional information
beyond well-known media types or non-well-known media types.

7.2.7 Address-Data AVP

The Address-Data AVP (AVP code 897) is of type UTF8String and indicates the address information and formatted
according type of address indicated in the Address-Type AVP and according to MMS encapsulation [209].

7.2.8 Address-Domain AVP

The Address-Domain AVP (AVP code 898) is of type Grouped and indicates the domain/network to which the
associated address resides. If this AVP is present, at least one of the AVPs described within the grouping shall be
included.

It has the following ABNF:

Address-Domain :: = < AVP Header: 898 >

[ Domain-Name ]
[ 3GPP-IMSI-MCC-MNC ]

7.2.9 Address-Type AVP

The Address-Type AVP (AVP code 899) is of type Enumerated and indicates the type of address carried within the
Address-Information AVP. It has the following values:

0 e-mail address
1 MSISDN
2 IPv4 Address
3 IPv6 Address
4 Numeric Shortcode
5 Alphanumeric Shortcode
6 Other

3GPP
Release 15 120 3GPP TS 32.299 V15.4.0 (2018-09)

7 IMSI

7.2.10 Addressee-Type AVP

The Addressee-Type AVP (AVP code 1208) is of type Enumerated and identifies the how the recipient is addressed in
the header of an MM. The following values are defined:

0 TO
1 CC
2 BCC

7.2.11 AF-Correlation-Information AVP

The AF-Correlation-Information AVP (AVPcode 1276) is of type Grouped and includes the "AF Charging Identifier"
(ICID for IMS) and associated flow identifiers generated by the AF and received by P-GW over Rx/Gx as defined in
TS 29.214 [214] and TS 29.212 [215]. The AF-Correlation-Information is defined per Rating Group or per Rating
Group and Service Identifier when Service Identifier level reporting applies.

When several AF sessions (refer to TS 29.214 [214]) are conveyed over the same bearer, this AVP may appear several
times per MSCC instance.

It has the following ABNF grammar:

AF-Correlation-Information:: = < AVP Header: 1276 >

{ AF-Charging-Identifier }
* [ Flows ]

7.2.12 Alternate-Charged-Party-Address AVP

The Alternate-Charged-Party-Address AVP (AVP code 1280) is of type UTF8String and holds the address of the
alternate charged party determined by an AS at IMS session initiation.

7.2.12aAAnnouncement-Identifier AVP
The Announcement-Identifier AVP (AVP code 3905) is of type Unsigned32. It contains a code identifying an
announcement to be played.

7.2.12aBAnnouncement-Information AVP
The Announcement-Information AVP (AVP code 3904) is of type Grouped and holds the Announcement service
parameters. Each Announcement-Information AVP specifies a single announcement to be played to the specified user.

The Announcement-Order AVP contains the order in which announcements should be connected for playback when
there are multiple Announcement-Information AVPs provided in a single message with the same timing indicator.

It has the following ABNF grammar:

Announcement-Information:: = < AVP Header: 3904 >

{ Announcement-Identifier }
* [ Variable-Part ]
[ Time-Indicator ]
[ Quota-Indicator ]
[ Announcement-Order ]
[ Play-Alternative ]
[ Privacy-Indicator ]
[ Language ]

3GPP
Release 15 121 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.12aC Announcement-Order AVP

The Announcement-Order AVP (AVP code 3906) is of type Unsigned32. It contains the order in which announcements
should be connected for playback when there are multiple Announcement-Information AVPs provided in a single
message with the same timing indicator.

7.2.12aD Announcing-PLMN-ID AVP

The Announcing-PLMN-ID AVP (AVP code4408) is of type UTF8String and contains PLMN identity of the serving
PLMN which signalled the carrier frequency, when this serving PLMN is not the HPLMN nor the VPLMN, if available.

7.2.12A Announcing-UE-HPLMN-Identifier AVP

The Announcing-UE-HPLMN-Identifier AVP (AVP code 3426) is of type UTF8String and contains identifier of
annoucing UE HPLMN.

7.2.12B Announcing-UE-VPLMN-Identifier AVP

The Announcing-UE-VPLMN-Identifier AVP (AVP code 3427) is of type UTF8String and contains identifier of
annoucing UE VPLMN.

7.2.13 AoC-Cost-Information AVP

The AoC-Cost-Information AVP (AVP code 2053) is of type Grouped and holds accumulated and incremental cost
infromation for the AoC service

It has the following ABNF grammar:

AoC-Cost-Information:: = < AVP Header: 2053 >

[ Accumulated-Cost ]
* [ Incremental-Cost ]
[ Currency-Code ]

7.2.14 AoC-Format AVP

The AoC-Format AVP (AVP code 2310) is of type Enumerated and holds the format on how the AoC information shall
be sent to the UE. It can be one of the following values:

0 MONETARY
1 NON_MONETARY
2 CAI

7.2.15 AoC-Information AVP

The AoC-Information AVP (AVP code 2054) is of type Grouped that includes the information required for advice of
charge.

It has the following ABNF grammar:

AoC-Information:: = < AVP Header: 2054 >

[ AoC-Cost-Information ]
[ Tariff-Information ]
[ AoC-Subscription-Information ]

3GPP
Release 15 122 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.16 AoC-Request-Type AVP

The AoC-Request-Type AVP (AVP code 2055) is of type enumerated and tags if the client is looking for AoCI in
conjunction to the Request-Type and Request-Action AVPs. It can be one of the following values:

0 AoC_NOT_REQUESTED
1 AoC_FULL
2 AoC_COST_ONLY
3 AoC_TARIFF_ONLY

7.2.17 AoC-Service AVP

The AoC-Service AVP (AVP code 2311) is of type Grouped and holds the pair of AoC Service type and AoC Service
obligatory type.

It has the following ABNF grammar:

AoC-Service :: = < AVP Header: 2311 >

[ AoC-Service-Obligatory-Type ]
[ AoC-Service-Type ]

7.2.18 AoC-Service-Obligatory-Type AVP

The AoC-Service-Obligatory-Type AVP (AVP code 2312) is of type Enumerated and holds the information if the AoC
information is binding or not. It can be one of the following values:

0 NON_BINDING
1 BINDING

3GPP
Release 15 123 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.19 AoC-Service-Type AVP

The AoC-Service-Type AVP (AVP code 2313) is of type Enumerated and defines the type of AoC information to be
provided to the subscriber. It can be one of the following values:

0 NONE
1 AOC-S
2 AOC-D
3 AOC-E

7.2.20 AoC-Subscription-Information AVP

The AoC-Subscription-Information AVP (AVP code 2314) is of type Grouped and holds the subscription and formatting
parameters received from HSS.

It has the following ABNF grammar:

AoC-Subscription-Information:: = < AVP Header: 2314 >

* [ AoC-Service ]
[ AoC-Format ]
[ Preferred-AoC-Currency ]

7.2.20aAAPI-Content AVP
The API-Content AVP (AVP code 1309) is of type UTF8String and holds the message content (e.g. location, Monitoring
Type) used in the T8 transaction for the API invocation request, if available.

7.2.20bAAPI-Direction AVP
The API-Direction AVP (AVP code 1310) is of type Enumerated and the direction to indicate the API invocation or API
notification. The following values are defined:

0 invocation
1 notification

7.2.20cA API-Identifier AVP

The API-Identifier AVP (AVP code 1311) is of type OctetString and holds the identification of northbound exposure API
for each API invocation.

7.2.20dAAPI-Invocation-Timestamp AVP
The API-Invocation-Timestamp AVP (AVP code 1312) is of type Time, and holds the timestamp of the API invocation
request submitted to the SCEF from SCS/AS.

7.2.20eAAPI-Network-Service-Node AVP
The API-Network-Service-Node AVP (AVP code 1315) is of type Enumerated,and holds the identifier of the network
element as defined in TS 23.682[243], that triggers the API notification.

7.2.20fA API-Result-Code AVP

The API-Result-Code AVP (AVP code 1313) is of type Unsigned32 and holds the result of API Invocation.

7.2.20gAAPI-Size AVP
The API-Size AVP (AVP code 1314) is of type Unsigned64 and indicates the size in bytes of the specified API payload.

3GPP
Release 15 124 3GPP TS 32.299 V15.4.0 (2018-09)

0 MME
1 SGSN
2 HSS
3 PCRF
4 PFDF
5 BMSC
6 CSCF
7 RCAF

7.2.20A APN-Rate-Control AVP

The APN-Rate-Control AVP (AVP code 3933) is of type Grouped and holds the Rate Control parameters applicable to
data PDUs transfers in uplink and downlink direction for this APN.

It has the following ABNF grammar:

APN-Rate-Control :: = < AVP Header: 3933 >

[ APN-Rate-Control-Uplink ]
[ APN-Rate-Control-Downlink]

7.2.20B APN-Rate-Control-Downlink AVP

The APN-Rate-Control-Downlink AVP (AVP code 3934) is of type Grouped and holds the APN Rate Control
parameters applicable to data PDUs transfers in downlink for this APN.

It has the following ABNF grammar:

APN-Rate-Control-Downlink :: = < AVP Header: 3934 >

[ Rate-Control-Time-Unit ]
[ Rate-Control-Max-Rate ]
[ Rate-Control-Max-Message-Size ]

7.2.20C APN-Rate-Control-Uplink AVP

The APN-Rate-Control-Uplink AVP (AVP code 3935) is of type Grouped and holds the APN Rate Control parameters
applicable to data PDUs transfers in uplink for this APN.

It has the following ABNF grammar:

APN-Rate-Control-Uplink :: = < AVP Header: 3935>

[ Additional-Exception-Reports ]
[ Rate-Control-Time-Unit ]
[ Rate-Control-Max-Rate ]

7.2.21 Applic-ID AVP

The Applic-ID AVP (AVP code 1218) is of type UTF8String and holds the identification of the destination application
that the underlying MMS abstract message was addressed to.

7.2.22 Application-Provided-Called-Party-Address AVP

The Application-Provided-Called-Party-Address AVP (AVP code 837) is of type UTF8String and holds the called party
number (SIP URI, E.164), if it is determined by an application server.

3GPP
Release 15 125 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.23 Application-Server AVP

The Application-Server AVP (AVP code 836) is of type UTF8String and holds the SIP URL(s) of the AS(s) addressed
during the session.

7.2.24 Application-Server-Information AVP

The Application-Server-Information AVP (AVP code 850) is of type Grouped and contains information about
application servers visited through ISC interface.

It has the following ABNF grammar:

<Application-Server-Information>::= <AVP Header: 850 >

[ Application-Server ]
* [ Application-Provided-Called-Party-Address ]
[ Status- AS-Code ]

7.2.24A Application-Specific-Data AVP

The Application-Specific-Data AVP (AVP code 3458) is of type OctetString and contains a data block provided by the
application in the UE. The content of each block is application-specific.

3GPP
Release 15 126 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.25 Associated-Party-Address AVP

The Associated-Party-Address AVP (AVP code 2035) is of type UTF8String and is used for MMTel supplementary
service. It holds the address (SIP URI or Tel URI) of the user, the MMTel supplementary service is provided to : the
"forwarding party" for CDIV, the "transferor" for ECT, the "Pilot Identity" for Flexible Alerting (FA), the "Initiator
party" for 3PTY.

7.2.26 Associated-URI AVP

The Associated-URI AVP (AVP code 856) is of type UTF8String and holds a non-barred public user identity (SIP URI
or Tel URI) associated to the the public user identity under registration. This identity is obtained from the P-Associated-
URI header of a 200 OK SIP response to a REGISTER request. This AVP may appear several times when the P-
Associated-URI header contains more than one public user identity.

7.2.27 Authorised-QoS AVP

The Authorised-QoS AVP (AVP code 849) is of type UTF8String and holds the Authorised QoS as defined in TS 23.207
[200] / TS 29.207 [203] and applied via the Go reference point. This AVP is not used.

7.2.28 Aux-Applic-Info AVP

The Aux-Applic-Info AVP (AVP code 1219) is of type UTF8String and holds additional application/implementation
specific control information.

7.2.29 Base-Time-Interval AVP

The Base-Time-Interval AVP (AVP code 1265) is of type Unsigned32. It contains the length of the base time interval,
for controlling the consumption of time quota, in seconds.

7.2.29A Basic-Service-Code AVP

The Basic-Service-Code AVP (AVP code 3411) is of type Grouped and holds service information utilized by a voice call
service. Either a Bearer-Service AVP or a Teleservice AVP is included.

It has the following ABNF grammar:

Basic-Service-Code:: = < AVP Header: 3411 >

[ Bearer-Service ]
[ Teleservice ]

7.2.29B Bearer-Capability AVP

The Bearer-Capability AVP (AVP code 3412) is of type OctetString and indicates the type of bearer capability
connection to the user. The value as described in TS 29.078 [233] shall be used.

7.2.30 Bearer-Service AVP

The Bearer-Service AVP (AVP code 854) is of type OctetString and holds the used bearer service for the PSTN leg of an
IMS session or a voice call service.

7.2.30A BSSID AVP

The BSSID AVP (AVP code 2716) is of type UTF8String and contains the BSSID of the access point where UE is
located in a WLAN Access Network. The format used for BSSID is described in IEEE Std 802.11-2012 [409].

3GPP
Release 15 127 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.31 Called-Asserted-Identity AVP

The Called-Asserted-Identity AVP (AVP code 1250) is of type UTF8String and holds the address (Public User ID: SIP
URI, E.164, etc.) of the finally asserted called party.

The address is obtained from the P-Asserted-Identity SIP header field of the 2xx responses corresponding to a SIP
request either initiating a dialog or a standalone transaction. This field may appear several times in the request when the
P-Asserted-Identity contains both a SIP URI and a Tel URI.

This field shall be present when the P-Asserted-Identity SIP header field is available in the SIP 2xx response.

7.2.31A Called-Identity AVP

The Called-Identity AVP (AVP code 3916) is of type UTF8String and holds the address (Public User ID: SIP URI,
E.164, etc.) of the called party after a change.

The address is obtained from the From SIP header field of a SIP UPDATE request or SIP RE-INVITE request.

7.2.31B Called-Identity-Change AVP

The Called-Identity-Change AVP (AVP code 3917) is of type Grouped and provides the terminating identity address
change and associated time stamp.

It has the following ABNF grammar:

Called-Identity-Change :: = < AVP Header: 3917>

[ Called-Identity ]
[ Change-Time ]

7.2.32 Called-Party-Address AVP

The Called-Party-Address AVP (AVP code 832) is of type UTF8String. It holds the address (SIP URI, Tel URI or URN)
of the party to whom the call is addressed.

For IMS charging (except for SIP Register and SIP Subscription transactions), it holds the address of the party (Public
User ID or Public Service ID) to whom the SIP transaction is posted. The Called-Party-Address AVP shall be populated
with the SIP URI or Tel URI contained in the Request-URI of the outgoing request. For a registration procedure, this
AVP holds the party (Public User ID) to be registered. In this case, the Called-Party-Address AVP is obtained from the
"To" SIP header of the SIP Request. For a subscription procedure this AVP holds the address of the resource for which
the originator wants to receive notifications of change of states. In this case, the Called-Party-Address AVP is obtained
from the outgoing Request-URI of the SIP Request.

For VCS charging, it holds the address (URN is not applicable) which identifies the party to which a voice call is
destined after processing by the Proxy Function. It is converted from the circuit-switched Called Party Number as per
TS 29.163 [234] for the Request-URI header. For a mobile originating call, this AVP contains the Called Party Number
after processing by the Proxy Function (e.g. number normalization).

7.2.33 Calling-Party-Address AVP

The Calling-Party-Address AVP (AVP code 831) is of type UTF8String and, for IMS charging, holds the address (SIP
URI or Tel URI) which identifies the party (Public User Identity or Public Service Identity) initiating a SIP transaction.
It is obtained from the P-Asserted-Identity header of any non-REGISTER SIP Request, either initiating a dialog or a
standalone transaction. This AVP may appear several times when the P-Asserted-Identity header contains both a SIP
URI and a Tel URI. In case no P-Asserted-Identity is known, this AVP list shall include one item with the value
"unknown".

For VCS charging, it holds the address (SIP URI or Tel URI) which identifies the party initiating a voice call. It is
converted from the circuit-switched Calling Party Number as per TS 29.163 [234] for the P-Asserted-Identity header.

3GPP
Release 15 128 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.34 Carrier-Select-Routing-Information AVP

The Carrier-Select-Routing-Information AVP (AVP code 2023) is of type UTF8String. This AVP holds information on
carrier selection performed by S-CSCF/AS. This information is sent over SIP in the Requested URI header.

3GPP
Release 15 129 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.35 Cause-Code AVP

The Cause-Code AVP (AVP code 861) is of type Integer32 and includes the cause code value from IMS node. It is used
in ACR[Stop] and/or ACR[Event] messages. It is also used in the CCR[Terminate] and/or CCR[Event] messages.

Within the cause codes, values  0 are reserved for successful causes while values  1 are used for failure causes. In
case of errors where the session has been terminated as a result of a specific known SIP error code, then the SIP error
code is also used as the cause code.

Successful cause code values

0 Normal end of session

The cause "Normal end of session" is used in Accounting-request[stop] message to indicate that an
ongoing SIP session has been normally released either by the user or by the network (SIP BYE message
initiated by the user or initiated by the network has been received by the IMS node after the reception of
the SIP ACK message).

-1 Successful transaction when 200 Final Response

The cause "Successful transaction" is used in Accounting-request[Event] message to indicate a successful SIP
transaction (e.g. SIP REGISTER, SIP MESSAGE, SIP NOTIFY, SIP SUBSCRIBE when 200 Final Response). It may
also be used by an Application Server to indicate successful service event execution.

-2 End of SUBSCRIBE dialog

The cause "End of SUBSCRIBE dialog" is used to indicate the closure of a SIP SUBSCRIBE dialog . For
instance a successful SIP SUBSCRIBE transaction terminating the dialog has been detected by the IMS
node (i.e. SIP SUBSCRIBE with expire time set to 0).

-2xx 2xx Final Response

The cause-code "2xx Final Response"(except 200) is used when the SIP transaction is terminated due to
an IMS node receiving/initiating a 2xx Final response as described in RFC 3261 [405].

-3xx 3xx Redirection

The cause "3xx Redirection" is used when the SIP transaction is terminated due to an IMS node
receiving/initiating a 3xx response as described in RFC 3261 [405].

-3 End of REGISTER dialog

The cause "End of REGISTER dialog" is used to indicate the closure of a SIP REGISTER dialog. For
instance a successful SIP REGISTER transaction terminating the dialog has been detected by the IMS
node (i.e. SIP REGISTER with expire time set to 0).

Failure cause code values

1 Unspecified error

The cause "Unspecified error" is used when the SIP transaction is terminated due to an unknown error.

4xx 4xx Request failure

The cause "4xx Request failure" is used when the SIP transaction is terminated due to an IMS node
receiving/initiating a 4xx error response as described in RFC 3261 [405].

5xx 5xx Server failure

The cause "5xx Server failure" is used when the SIP transaction is terminated due to an IMS node
receiving/initiating a 5xx error response as described in RFC 3261 [405].

6xx 6xx Global failure

The cause "6xx Global failure" is used when the SIP transaction is terminated due to an IMS node
receiving/initiating a 6xx error response as described in RFC 3261 [405].

3GPP
Release 15 130 3GPP TS 32.299 V15.4.0 (2018-09)

2 Unsuccessful session setup

The cause "Unsuccessful session setup" is used in the Accounting-request[stop] when the SIP session has
not been successfully established (i.e. Timer H expires and SIP ACK is not received or SIP BYE is
received after reception of the SIP 200 OK final response and SIP ACK is not received) as described in
TS 24.229 [202] and in RFC 3261 [405].

3 Internal error

The cause "Internal error" is used when the SIP transaction is terminated due to an IMS node internal
error (e.g. error in processing a request/response).

7.2.35A Cellular-Network-Information AVP

The Cellular-Network-Information AVP (AVP code 3924) is of type OctetString and indicates one instance of the SIP
header "Cellular-Network-Info".

7.2.35B Civic-Address-Information AVP

The Civic-Address-Information AVP (AVP code 1305) is of type OctetString and holds the Civic Address of the Access
Point to which the UE is attached when served under a trusted or untrusted WLAN, as specified for Location-Data in
TS 29.273 [237].

7.2.36 CG-Address AVP

The CG-Address AVP (AVP code 846) is of type Address and holds the IP-address of the charging gateway.

7.2.37 Change-Condition AVP

The Change-Condition AVP (AVP code 2037) is of type Integer32, and indicates the change in charging condition:
(Qos change, tariff time change …) which causes:

- Sending of Accounting-Request from node;

- Volume counts container closing for an IP-CAN bearer;

- Service data container closing;

- ProSe direct communication data container closing;

- Record closing.

The following values are defined :

0 Normal Release
The "Normal Release" value is used to indicate IP-CAN session termination , IP-CAN bearer release or Service
Data Flow Termination; PDN connection to SCEF release.
1 Abnormal Release
2 Qos Change
3 Volume Limit
4 Time Limit
5 Serving Node Change
6 Serving Node PLMN Change
7 User Location Change
8 RAT Change
9 UE TimeZone Change
10 Tariff Time Change
11 Service Idled Out
12 ServiceSpecificUnitLimit
13 Max Number of Changes in Charging conditions
14 CGI-SAI Change
15 RAI Change

3GPP
Release 15 131 3GPP TS 32.299 V15.4.0 (2018-09)

16 ECGI Change
17 TAI Change
18 Service Data Volume Limit
19 Service Data Time Limit
20 Management Intervention
21 Service Stop
22 User CSG Information Change
23 S-GW Change
24 Change of UE Presence in Presence Reporting Area
25 Proximity alerted
26 Time expired with no renewal
27 Requestor cancellation
28 Maximum number of reports
29 PLMN change
30 Coverage status change
31 Removal of access
32 Unavailability of access
33 Access change of service data flow
34 Indirect change condition
35 Maximum number of NIDD submissions
36 Change in UP to UE
37 Serving PLMN Rate Control Change
38 APN Rate Control Change
39 NIDD Submission Response Receipt
40 NIDD Submission Response Sending
41 NIDD Delivery to UE
42 NIDD Delivery from UE Error
43 NIDD Submission Timeout
44 MO exception data counter
45 Change of 3GPP PS Data off Status

NOTE: Values 25-30 are applied for ProSe charging only.

7.2.38 Change-Time AVP

The Change-Time AVP (AVP code 2038) is of type Time.

In EPC Charging, it holds the time in UTC format when the volume counts associated to the IP-CAN bearer/TDF
session, or the service data container, is closed and reported due to charging condition change.

For IMS Charging, it holds the time in UTC format at which the access transfer occurred.

For MMTel Charging, it holds the time in UTC format and it is a time stamp that defines the moment when the
conference participant has an action (e.g. creating the conference, joining in the conference, being invited into the
conference and quiting the conference) triggering the Accounting Request message to CDF.

In ProSe Charging, it holds the time in UTC format when the volume counts associated to the ProSe group
communication container, is closed and reported due to ProSe charging condition change.

7.2.38A Charge-Reason-Code AVP

The Charge-Reason-Code AVP (AVP code 2118) is of type Enumerated and identifies if the Rate-Element corresponds
to a specific charge type. It can be one of the following values:

0 UNKNOWN
1 USAGE
2 COMMUNICATION-ATTEMPT-CHARGE
3 SETUP-CHARGE
4 ADD-ON-CHARGE

3GPP
Release 15 132 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.39 Charged-Party AVP

The Charged-Party AVP (AVP code 857) is of type UTF8String and holds the address (Public User ID: SIP URI, Tel
URI, etc.) of the party to be charged.

For Monitoring Event charging, it contains a string that identifies the entity towards which accounting/charging
functionality is performed by the involved 3GPP network elements.

7.2.39A Charging-Characteristics-Selection-Mode AVP

The Charging-Characteristics-Selection-Mode AVP (AVP code 2066) is of type Enumerated and indicates how the
applied Charging-Characteristics was selected. It may take following values:

0 Serving-Node-Supplied
1 Subscription-specific
2 APN-specific
3 Home-Default
4 Roaming-Default
5 Visiting-Default

7.2.39B Charging-Per-IP-CAN-Session-Indicator AVP

The Charging-Per-IP-CAN-Session-Indicator AVP (AVP code 4400) is of type of Enumerated. It indicates whether the
charging per IP-CAN session is active for offline charging. If this AVP is not present, that means charging per IP-CAN
session is not active.

The following value is defined:

0 Inactive
1 Active

7.2.40 Class-Identifier AVP

The Class-Identifier AVP (AVP code 1214) is of type Enumerated and the values are:

0 Personal
1 Advertisement
2 Informational
3 Auto

7.2.41 Client-Address AVP

The Client-Address AVP (AVP code 2018) is of type Address and is the address of the messaging Node which the OCS
is connected to.

7.2.41A CN-Operator-Selection-Entity AVP

The CN-Operator-Selection-Entity AVP (AVP code 3421) is of type Enumerated and holds the indication on which
entity has selected the Serving Core Network in Network Sharing situations.

It has the following values:

0 The Serving Network has been selected by the UE

1 The Serving Network has been selected by the network

3GPP
Release 15 133 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.42 Content-Class AVP

The Content-Class AVP (AVP code 1220) is of type Enumerated and classifies the content of the MM to the highest
content class to which the MM belongs, as defined in MMS Encapsulation [209]. The classes can be one of the
following:

0 text
1 image-basic
2 image-rich
3 video-basic
4 video-rich
5 megapixel
6 content-basic
7 content-rich

7.2.43 Content-Disposition AVP

The Content-Disposition AVP (AVP code 828) is of type UTF8String and indicates how the message body or a message
body part is to be interpreted (e.g. session, render), as described in RFC 3261 [405].

7.2.44 Content-Length AVP

The Content-Length AVP (AVP code 827) is of type Unsigned32 and holds the size of the message-body, as described in
RFC 3261 [405].

7.2.45 Content-Size AVP

The Content-Size AVP (AVP code 1206) is of type Unsigned32 and indicates the size in bytes of the specified content
type.

7.2.46 Content-Type AVP

The Content-Type AVP (AVP code 826) is of type UTF8String and holds the media type (e.g. application/sdp, text/html)
of the message-body, as described in RFC 3261 [405].

7.2.46aACoverage-Status AVP
The Coverage-Status AVP (AVP code 3428) is of type Enumerated and indicates whether UE is served by E-UTRAN or
not. The following values are defined:

0 Out of coverage
1 In coverage

7.2.46aaA Coverage-Info AVP

The Coverage-Info AVP (AVP code 3459) is of type Grouped and provides information on the coverage status (i.e.,
whether the UE is served by E-UTRAN or not) and the time when the coverage status changed to its current state.
When in E-UTRAN coverage, additionally includes a list of location changes (i.e., ECGI change) and associated time
for each change.

It has the following ABNF grammar:

Coverage-Info :: = < AVP Header: 3459>

[ Coverage-Status ]
[ Change-Time ]
* [ Location-Info ]

3GPP
Release 15 134 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.46abA CP-CIoT-EPS-Optimisation-Indicator AVP

The CP-CIoT-EPS-Optimisation-Indicator AVP (AVP code 3930) is of type Enumerated, and indicates whether Control
Plane CIoT EPS optimisation is used by this PDN connection for data transfer with the UE. The following values are
defined:

0 Not Apply
1 Apply

7.2.46acA CPDT-Information AVP

The CPDT-Information AVP (AVP code 3927) is of type Grouped. Its purpose is to allow the transmission of additional
CP data transfer service specific information elements.

It has the following ABNF grammar:

CPDT-Information :: = < AVP Header: 3927>

[ External-Identifier ]
[ SCEF-ID ]
[ Serving Node Identity ]
[ SGW-Change ]
[ NIDD-submission ]

7.2.46A CSG-Access-Mode AVP

The CSG-Access-Mode AVP (AVP code 2317) is of type Enumerated and holds the mode in which the CSG cell User is
accessing to, operates. It has the following values:

0 Closed mode
1 Hybrid Mode

7.2.46B CSG-Membership-Indication AVP

The CSG-Membership-Indication AVP (AVP code 2318) is of type Enumerated, and indicates the UE is a member of
the accessing CSG cell, if the access mode is Hybrid, as described in TS 29.060 [225], and in TS 29.274 [226]. If this
indication is not present, this means the UE is a Not member of the CSG cell for hybrid access mode. The following
values are defined:

0 Not CSG member

1 CSG Member

3GPP
Release 15 135 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.47 Current-Tariff AVP

The Current-Tariff AVP (AVP code 2056) is of type Grouped and holds tariff information. The Tariff is a formula for
cost calculation given the Used-Service-Unit AVP. The calculated cost is given in the Currency-Code AVP. The formula
sums all the rating elements and multiplies the sum by the Scale-Factor AVP.

It has the following ABNF grammar:

Current-Tariff:: = < AVP Header: 2056 >

[ Currency-Code ]
[ Scale-Factor ]
* [ Rate-Element ]

7.2.48 CUG-Information AVP

The CUG-Information AVP (AVP code 2304) is of type OctetString and holds the "CUG Interlock Code" which
identifies CUG membership within the Network for "Closed User Group" MMTel supplementary service.

7.2.49 Data-Coding-Scheme AVP

The Data-Coding-Scheme AVP (AVP code 2001) is of type Integer32 and contains the data coding scheme of the
message. For SM applications the specific coding is as described in TS 23.040 [216].

7.2.50 DCD-Information AVP

The DCD-Information AVP (AVP code 2115) is of type Grouped. Its purpose is to allow the transmission of service
information elements used for DCD services.

The AVP is defined in OMA-DDS-Charging_Data [223].

7.2.51 Deferred-Location-Event-Type AVP

The Deferred-Location-Even-Type AVP (AVP code 1230) is of type UTF8String and holds information related to a
deferred location request.

7.2.52 Delivery-Report-Requested AVP

The Delivery-Report-Requested AVP (AVP code 1216) is of type Enumerated and indicates whether a delivery report
has been requested by the originator or not. The values for whether a report was requested are:

0 No
1 Yes

7.2.53 Destination-Interface AVP

The Destination-Interface AVP (AVP code 2002) is type Grouped, which contains information related to the Interface
on which the message is to be delivered.

Destination-Interface ::= < AVP Header: 2002 >

[ Interface-Id ]
[ Interface-Text ]
[ Interface-Port ]
[ Interface-Type ]

3GPP
Release 15 136 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.54 Diagnostics AVP

The Diagnostics AVP (AVP code 2039) is of type Integer32 and provides a more detailed cause value from PCN node. It
complements the Change-Condition AVP for Offline Charging.

7.2.54A Discoveree-UE-HPLMN-Identifier AVP

The Discoveree-UE-HPLMN-Identifier AVP (AVP code 4402) of type UTF8String and contains identifier of Discoveree
UE HPLMN.

7.2.54B Discoveree-UE-VPLMN-Identifier AVP

The Discoveree-UE-VPLMN-Identifier AVP (AVP code 4403) is of type UTF8String and contains identifier of
Discoveree UE VPLMN.

7.2.54C Discoverer-UE-HPLMN-Identifier AVP

The Discoverer-UE-HPLMN-Identifier AVP (AVP code 4404) of type UTF8String and contains identifier of Discoverer
UE HPLMN.

7.2.54D Discoverer-UE-VPLMN-Identifier AVP

The Discoverer-UE-VPLMN-Identifier AVP (AVP code 4405) of type UTF8String and contains identifier of Discoverer
UE VPLMN.

7.2.55 Domain-Name AVP

The Domain-Name AVP (AVP code 1200) is of type UTF8String and represents a fully qualified domain name (FQDN).

7.2.56 DRM-Content AVP

The DRM-Content AVP (AVP code 1221) is of type Enumerated and indicates if the MM contains DRM-protected
content. The values are:

0 No
1 Yes

7.2.57 Dynamic-Address-Flag AVP

The Dynamic-Address-Flag AVP (AVP code 2051) is of type Enumerated, and indicates whether the PDP context/PDN
address is statically or dynamically allocated. If this AVP is not present, this means that the address is statically
allocated. The following values are defined:

0 Static
1 Dynamic

7.2.57A Dynamic-Address-Flag-Extension AVP

The Dynamic-Address-Flag-Extension AVP (AVP code 2068) is of type Enumerated, and indicatesthat the IPv4 PDN
address has been dynamically allocated for that particular IP CAN bearer (PDN connection) of PDN type IPv4v6, and
the dynamic IPv6 address is indicated in Dynamic Address Flag. If this AVP is not present, this means that the address is
statically allocated.The following values are defined:

0 Static
1 Dynamic

3GPP
Release 15 137 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.58 Early-Media-Description AVP

The Early-Media-Description AVP (AVP code 1272) is of type grouped and describes the SDP session, media
parameters and timestamps related to media components set to active according to SDP signalling exchanged during a
SIP session establishment before the final successful or unsuccessful SIP answer to the initial SIP INVITE message is
received. Once a media component has been set to active, subsequent status changes shall also be registered.

It has the following ABNF grammar:

<Early-Media-Description>:: = <AVP Header: 1272>

[ SDP-TimeStamps ]
* [ SDP-Media-Component ]
* [ SDP-Session-Description ]

Media can be considered as inactive in range of situations, such as the listed below according to RFC 3264 [408]:

- Media marked with "a=inactive" attribute.

- Media offered with zero bandwith.

In contrast, media with directionality marked as "a=recvonly", "a=sendonly", "a=sendrecv" shall be considered in state
"active" and thus, it may be exchanged in one or both directions.

7.2.58A Enhanced-Diagnostics AVP

The Enhanced-Diagnostics AVP (AVP code 3901) is of type Grouped and provides a set of causes for the release. It
complements the Change-Condition AVP for Offline Charging from PCN Nodes.

It has the following ABNF grammar:

Enhanced-Diagnostics :: = < AVP Header: 3901>

*[ RAN-NAS-Release-Cause ]

NOTE: The RAN-NAS-Release-Cause AVP is under a grouped AVP to allow extensions to other types of release
causes in the future.

7.2.59 Envelope AVP

The Envelope AVP (AVP code 1266) is a grouped AVP which reports the start and end time of one time envelope using
the Envelope-Start-Time and Envelope-End-Time AVPs. Further details of its usage are described in clause 6.5.6 and
clause 6.5.7.

Envelope :: = < AVP Header: 1266>

{ Envelope-Start-Time }
[ Envelope-End-Time ]
[ CC-Total-Octets ]
[ CC-Input-Octets ]
[ CC-Output-Octets ]
[ CC-Service-Specific-Units ]

If an envelope has not been closed at the time of the usage report, then the Envelope-End-Time AVP shall be absent. If
an envelope was started before the reporting interval then the Envelope-Start-Time is nevertheless present and contains
the same time as previously reported, i.e. the actual time of the start of the envelope. The client shall include the volume
reports (the CC-xxxxx-Octets AVPs) or events (CC-Service-Specific-Units AVP) if these were requested in the

3GPP
Release 15 138 3GPP TS 32.299 V15.4.0 (2018-09)

corresponding Envelope-Reporting AVP. The reported volume is always the volume from the beginning of the time
envelope.

In circumstances, in which an envelope is retrospectively deemed to have been closed, e.g. with Quota-Consumption-
Time changes in a CCA, then the client shall include the Envelope AVP for the envelope in the next usage report.

Multiple occurrences of this AVP shall be in chronological order, i.e. the first envelope is listed first in CCR.

7.2.60 Envelope-End-Time AVP

This Envelope-End-Time AVP (AVP code 1267) is of type Time. It is set to the time of the end of the time envelope.

3GPP
Release 15 139 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.61 Envelope-Reporting AVP

This Envelope-Reporting AVP (AVP code 1268) is of type Enumerated and is used in the CCA[INITIAL] to indicate
whether the client shall report the start and end of each time envelope, in those cases in which quota is consumed in
envelopes. It can take the values:

0 DO_NOT_REPORT_ENVELOPES
1 REPORT_ENVELOPES
2 REPORT_ENVELOPES_WITH_VOLUME
3 REPORT_ENVELOPES_WITH_EVENTS
4 REPORT_ENVELOPES_WITH_VOLUME_AND_EVENTS

If this AVP is not included in the CCA[Initial] then the client shall not report the individual envelopes.
If this AVP is included within the Offline-Charging AVP, the value shall dictate the mechanism by which offline
charging information is generated.

7.2.62 Envelope-Start-Time AVP

The Envelope-Start-Time AVP (AVP code 1269) is of type Time. It is set to the time of the packet of user data which
caused the time envelope to start.

7.2.62A EPDG-Address AVP

The EPDG-Address AVP (AVP code 3425) is of type Address and holds the IP-address of the ePDG Node.

7.2.63 Event AVP

The Event AVP (AVP code 825) is of type UTF8String and holds the content of the "Event" header.

7.2.64 Event-Charging-TimeStamp AVP

The Event-Charging-TimeStamp AVP (AVP code 1258) is of type Time, and it holds the timestamp of the event reported
in the CC-Service-Specific-Units AVP when event based charging applies.

7.2.65 Event-Type AVP

The Event-Type AVP (AVP code 823) is of type Grouped and contains information about the type of chargeable
telecommunication service/event for which the ACR and/or CCR message(s) is generated.

It has the following ABNF grammar:

<Event-Type>:: = <AVP Header: 823 >

[ SIP-Method ]
[ Event ]
[ Expires ]

7.2.66 Expires AVP

The Expires AVP (AVP code 888) is of type Unsigned32 and holds the content of the "Expires" header, if available.

7.2.66A FE-Identifier-List AVP

The FE-Identifier-List AVP (AVP code 4413) is of type UTF8String and holds the FE-Identifier-List as defined in TS
24.229 [210] of IMS Network Elements that generates charging information.

The FE-Identifier exchange via SIP signalling is defined in TS 24.229 [210].

3GPP
Release 15 140 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.66aAExposure-Function-API-Information AVP
The Exposure-Function-API-Information AVP (AVP code 1316) is of type Grouped. Its purpose is to allow the
transmission of additional Exposure Function API Information specific information elements.

It has the following ABNF grammar:

Exposure-Function-API-Information :: = < AVP Header: 1316>

* [ Supported-Features ]
[ API-Content ]
[ API-Direction ]
[ API-Identifier ]
[ API-Invocation-Timestamp ]
[ API-Network-Service-Node ]
[ API-Result-Code ]
[ API-Size ]
[ Network-Element ]
[ SCEF-Address ]
[ SCS-AS-Address ]
[ TTRI ]
[ TLTRI ]

3GPP
Release 15 141 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.67 File-Repair-Supported AVP

The File-Repair-Supported AVP (AVP code 1224) is of type Enumerated and indicates whether the MBMS user service
supports point-to-point file repair. The following values are supported:

1 SUPPORTED
The MBMS user service does support point-to-point file repair.
2 NOT_SUPPORTED
The MBMS user service does not support point-to-point file repair.

7.2.67aAForwarding-Pending AVP
The Forwarding-Pending AVP (AVP code 3415) is of type Enumerated and indicates that a forwarded-to-number has
been received and the voice call will be forwarded. When it is not present, the voice call is not expected to be
forwarded. The values are:

0 Forwarding not pending

1 Forwarding pending

7.2.67A From-Address AVP

The From-Address AVP (AVP code 2708) is of type UTF8String and includes the information from the SIP From
header.

7.2.68 GGSN-Address AVP

The GGSN-Address AVP (AVP code 847) is of type Address and holds the IP-address of the P-GW that generated the
GPRS/EPC Charging ID, as described in [1].

7.2.69 IM-Information AVP

The IM-Information AVP (AVP code 2110) is of type Grouped. Its purpose is to allow the transmission of service
information elements used for IM services. The AVP is defined in OMA-DDS-Charging_Data [223].

7.2.70 Incremental-Cost AVP

The Incremental-Cost AVP (AVP code 2062) is of type Grouped and holds the incremental cost since last AoC
interaction for the ongoing session.

It has the following ABNF grammar:

Incremental-Cost:: = < AVP Header: 2062 >

{ Value-Digits }
[ Exponent ]

7.2.70A Instance-Id AVP

The Instance-Id AVP (AVP code 3402) is of type UTF8String and contains a URN generated by the device that uniquely
identifies a specific device amongst all other devices. The Instance Id is transported in the Contact header of a SIP
request associated with the served user.

7.2.71 Interface-Id AVP

The Interface-Id AVP (AVP code 2003) is of type UTF8String and holds the interface identification provided by the
messaging node (originator/destination).

3GPP
Release 15 142 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.72 Interface-Port AVP

The Interface-Port AVP (AVP code 2004) is of type UTF8String and holds the port-identification or contains
information about the transport layer port used by the application associated with the charging event.

7.2.73 Interface-Text AVP

The Interface-Text AVP (AVP code 2005) is of type UTF8String and is the consolidation information about the
application associated with the charging event.

7.2.74 Interface-Type AVP

The Interface-Type AVP (AVP code 2006) is of type Enumerated and contains information about type of interface /
nature of the transaction in the messaging node for which the charging event occurs. The AVP can take the following
values:

0 Unknown
1 MOBILE_ORIGINATING
2 MOBILE_TERMINATING
3 APPLICATION_ORIGINATING
4 APPLICATION_TERMINATION

7.2.74aAInter-UE-Transfer AVP
The Inter-UE-Transfer AVP (AVP code 3902) is of type Enumerated and contains information about type of the transfer.
If this AVP is not present, this means that the type of transfer is Intra-UE transfer. The AVP can take the following
values:

0 Intra-UE transfer
1 Inter-UE transfer

7.2.74A IMS-Application-Reference-Identifier AVP

The IMS-Application-Reference-Identifier AVP (AVP code 2601) is of type UTF8String and holds the IMS Application
Reference Identifier (IARI) as contained in a SIP request to identify an IMS Application as defined in TS 24.229 [202].

Editor's Note: The SIP parameter from which the IMS Application Reference ID (IARI) is to be extracted requires
further investigation in CT1. A mechanism to identify the IARI in use is FFS.

7.2.75 IMS-Charging-Identifier AVP

The IMS-Charging-Identifier AVP (AVP code 841) is of type UTF8String and holds the IMS Charging Identifier (ICID)
as generated by a IMS node for a SIP session and described in TS 24.229 [204].

7.2.76 IMS-Communication-Service-Identifier AVP

The IMS-Communication-Service-Identifier AVP (AVP code 1281) is of type UTF8String and holds the IMS
Communication Service Identifier (ICSI) as contained in the P-Asserted-Service header of a SIP request to identify an
IMS Communication Service as defined in TS 24.229 [202].

7.2.76A IMS-Emergency-Indicator AVP

The IMS-Emergency-Indicator AVP (AVP code 2322) is of type Enumerated, and indicates the IMS session is an IMS
emergency session or IMS registration. If this AVP is not present, this means the IMS session or registration is not
detected as an emergency session or registration. The following values are defined:

0 Non Emergency
1 Emergency

3GPP
Release 15 143 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.77 IMS-Information AVP

The IMS-Information AVP (AVP code 876) is of type Grouped. Its purpose is to allow the transmission of additional
IMS service specific information elements.

It has the following ABNF grammar:

IMS-Information :: = < AVP Header: 876>

[ Event-Type ]
[ Role-Of-Node ]
{ Node-Functionality }
[ User-Session-Id ]
[ Outgoing-Session-Id ]
[ Session-Priority ]
* [ Calling-Party-Address ]
[ Called-Party-Address ]
* [ Called-Asserted-Identity ]
[ Called-Identity-Change ]
[ Number-Portability-Routing-Information ]
[ Carrier-Select-Routing-Information ]
[ Alternate-Charged-Party-Address ]
* [ Requested-Party-Address ]
* [ Associated-URI ]
[ Time-Stamps ]
* [ Application-Server-Information ]
* [ Inter-Operator-Identifier ]
* [ Transit-IOI-List ]
[ IMS-Charging-Identifier ]
* [ SDP-Session-Description ]
* [ SDP-Media-Component ]
[ Served-Party-IP-Address ]
[ Server-Capabilities ]
[ Trunk-Group-ID ]
[ Bearer-Service ]
[ Service-Id ]
* [ Service-Specific-Info ]
* [ Message-Body ]
[ Cause-Code ]
* [ Reason-Header ]
* [ Access-Network-Information ]
[ Cellular-Network-Information ]
* [ Early-Media-Description ]
[ IMS-Communication-Service-Identifier ]
[ IMS-Application-Reference-Identifier ]
[ Online-Charging-Flag ]
[ Real-Time-Tariff-Information ]
[ Account-Expiration ]
[ Initial-IMS-Charging-Identifier ]
* [ NNI-Information ]
[ From-Address ]
[ IMS-Emergency-Indicator ]
[ IMS-Visited-Network-Identifier ]
* [ Access-Network-Info-Change ]
* [ Access-Transfer-Information ]
[ Related-IMS-Charging-Identifier ]
[ Related-IMS-Charging-Identifier-Node ]
[ Route-Header-Received ]
[ Route-Header-Transmitted ]
[ Instance-Id ]
[TAD-Identifier]

3GPP
Release 15 144 3GPP TS 32.299 V15.4.0 (2018-09)

[FE-Identifier-List]

7.2.77A IMS-Visited-Network-Identifier AVP

The IMS-Visited-Network-Identifier AVP (AVP code 2713) is of type UTF8String and contains the contents of the SIP P-
header "P-Visited-Network-ID". with the value according to 3GPP TS 24.229 [202]

- For the roaming architecture for voice over IMS with local breakout, the value of IMS-Visited-Network-
Identifier AVP is a pre-provisioned string that identifies the network of the P-CSCF at the home network.

- For the roaming architecture for voice over IMS with home routed traffic, IMS-Visited-Network-Identifier AVP
is a string that identifies the visited network of the UE including an indication that the P-CSCF is located in the
home network.

7.2.78 IMSI-Unauthenticated-Flag AVP

The IMSI-Unauthenticated-Flag AVP (AVP code 2308) is of type Enumerated, and indicates the served IMSI is not
authenticated. This may occur when emergency bearer service is provided (refer to TS 23.060 [74] and TS 29.274 [91]).
If this flag is not present, this means the served IMSI is authenticated. The following values are defined:

0 Authenticated
1 Unauthenticated

7.2.79 Incoming-Trunk-Group-ID AVP

The Incoming-Trunk-Group-ID AVP (AVP code 852) is of type UTF8String and identifies the incoming PSTN leg.

7.2.79A Initial-IMS-Charging-Identifier AVP

The Initial-IMS-Charging-Identifier AVP (AVP code 2321) is of type UTF8String and holds the Initial IMS Charging
Identifier (ICID) as generated by a IMS node for the initial SIP session created for IMS service continuity.

7.2.80 Inter-Operator-Identifier AVP

The Inter-Operator-Identifier AVP (AVP code 838) is of type Grouped and holds the identification of the network
neighbours (originating and terminating) as exchanged via SIP signalling and described in RFC 7315 [404].

It has the following ABNF grammar:

<Inter-Operator-Identifier>:: = < AVP Header: 838 >

[ Originating-IOI ]
[ Terminating-IOI ]

7.2.80A IP-Realm-Default-Indication AVP

The IP-Realm-Default-Indication-Indication AVP (AVP code 2603) is of type Enumerated and indicates whether the IP
realm used for the SDP media component is the Default IP realm or not. The following values are defined:

0 Default IP Realm Not used

1 Default IP realm used

7.2.80B ISUP-Cause AVP

The ISUP-Cause AVP (AVP code 3416) is of type Grouped and indicates the reason a voice call service is released.
When used for IMS charging, this AVP indicates the reason a CS call is released.

It has the following ABNF:

3GPP
Release 15 145 3GPP TS 32.299 V15.4.0 (2018-09)

ISUP-Cause ::= <AVP Header: 3416>

[ ISUP-Cause-Location ]
[ ISUP-Cause-Value ]
[ ISUP-Cause-Diagnostics ]

7.2.80C ISUP-Cause-Diagnostics AVP

The ISUP-Cause-Diagnostics AVP (AVP code 3422) is of type OctetString and holds the diagnostics field associated
with the release of the voice call service, if available. When used for IMS charging, this AVP holds the diagnostics field
associated with the release of a CS call. Refer to TS 29.078 [233] for supported values.

7.2.80D ISUP-Cause-Location AVP

The ISUP-Cause-Location AVP (AVP code 3423) is of type Unsigned32 and identifies the network in which the event
causing the call release. Refer to TS 29.078 [233] for supported values.

7.2.80E ISUP-Cause-Value AVP

The ISUP-Cause-Value AVP (AVP code 3424) is of type Unsigned32 and identifies the reason a voice call service is
released. When used for IMS charging, this AVP indicates the reason a CS call is released. Refer to TS 29.078 [233] for
supported values.

7.2.80F ISUP-Location-Number AVP

The ISUP-Location-Number AVP (AVP code 3414) is type OctetString and contains the international E.164 indicating
the location number of the served user. It contains an E.164 number as transported in ISUP and is encoded as a TBCD-
string. See TS 29.002 [232] for encoding of TBCD-strings. This AVP does not include leading indicators for the nature
of address and the numbering plan; it contains only the TBCD-encoded digits of the address.

7.2.80Fa Language AVP

The Language AVP (AVP code 3914) is of type UTF8String and contains a code defined in RFC 3066 [410] indicating
the language of the announcement that should be played.

7.2.80G Layer-2-Group-ID AVP

The Layer-2-Group-ID AVP (AVP code 3429) is of type OctetString and carry the identifier of a ProSe communication
group, uniquely represents a specific one-to-many ProSe Direct Communication and is included in CDRs for each
participantes in the specific group. This identity is referred to as "ProSe Layer-2 Group ID" in TS 23.303 [235].

7.2.81 LCS-APN AVP

The LCS-APN AVP (AVP code 1231) is of type UTF8String and contains the APN of the LCS Client.

7.2.82 LCS-Client-Dialed-By-MS AVP

The LCS-Client-Dialed-By-MS AVP (AVP code 1233) is of type UTF8String and holds the number of the LCS Client
dialled by the UE.

7.2.83 LCS-Client-External-ID AVP

The LCS-Client-External-ID AVP (AVP code 1234) is of type UTF8String and holds the identification of the external
LCS Client.

3GPP
Release 15 146 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.84 LCS-Client-ID AVP

The LCS-Client-Id AVP (AVP code 1232) is of type Grouped and holds information related to the identity of an LCS
client.

It has the following ABNF grammar:

<LCS-Client-ID>:: = < AVP Header: 1232 >

[ LCS-Client-Type ]
[ LCS-Client-External-ID ]
[ LCS-Client-Dialed-By-MS ]
[ LCS-Client-Name ]
[ LCS-APN ]
[ LCS-Requestor-ID ]

3GPP
Release 15 147 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.85 LCS-Client-Name AVP

The LCS-Client-Name AVP (AVP code 1235) is of type Grouped and contains the information related to the name of the
LCS Client.

It has the following ABNF grammar:

<LCS-Client-Name>:: = < AVP Header: 1235>

[ LCS-Data-Coding-Scheme ]
[ LCS-Name-String ]
[ LCS-Format-Indicator ]

7.2.86 LCS-Client-Type AVP

The LCS-Client-Type AVP (AVP code 1241) is of type Enumerated and contains the type of services requested by the
LCS Client. It can be one of the following values:

0 EMERGENCY_SERVICES
1 VALUE_ADDED_SERVICES
2 PLMN_OPERATOR_SERVICES
3 LAWFUL_INTERCEPT_SERVICES

7.2.87 LCS-Data-Coding-Scheme AVP

The LCS-Data-Coding-Scheme AVP (AVP code 1236) is of type UTF8String and contains the information of the
alphabet and the language used.

7.2.88 LCS-Format-Indicator AVP

The LCS-Format-Indicator AVP (AVP code 1237) is of type Enumerated and contains the format of the LCS Client
name. It can be one of the following values:

0 LOGICAL_NAME
1 EMAIL_ADDRESS
2 MSISDN
3 URL
4 SIP_URL

7.2.89 LCS-Information AVP

The LCS-Information AVP (AVP code 878) is of type Grouped. Its purpose is to allow the transmission of additional
LCS service specific information elements.

It has the following ABNF grammar:

LCS-Information :: = < AVP Header: 878>

[ LCS-Client-ID ]
[ Location-Type ]
[ Location-Estimate ]
[ Positioning-Data ]
[ 3GPP-IMSI ]
[ MSISDN ]

7.2.90 LCS-Name-String AVP

The LCS-Name-String AVP (AVP code 1238) is of type UTF8String and contains the LCS Client name.

3GPP
Release 15 148 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.91 LCS-Requestor-ID AVP

The LCS-Requestor-ID AVP (AVP code 1239) is of type Grouped and contains information related to the identification
of the Requestor.

It has the following ABNF grammar:

<LCS-Requestor-ID>:: = < AVP Header: 1239 >

[ LCS-Data-Coding-Scheme ]
[ LCS-Requestor-ID-String ]

7.2.92 LCS-Requestor-ID-String AVP

The LCS-Requestor-ID-String AVP (AVP code 1240) is of type UTF8String and contains the identification of the
Requestor and can be e.g. MSISDN or logical name.

7.2.92A Local-GW-Inserted-Indication AVP

The Local-GW-Inserted-Indication AVP (AVP code 2604) is of type Enumerated and indicates if the local GW (TrGW,
IMS-AGW) is inserted or not for the SDP media component.

The following values are defined:

0 Local GW Not Inserted

1 Local GW Inserted

7.2.93 Local-Sequence-Number AVP

The Local-Sequence-Number AVP (AVP code 2063) is of type Unsigned32 and holds the service data container
sequence number : increased by 1 for each service data container closed.

7.2.94 Location-Estimate AVP

The Location-Estimate AVP (AVP code 1242) is of type OctetString and contains an estimate of the location of an MS
in universal coordinates and the accuracy of the estimate. Refers to the geographical area description in TS
23.032 [227] for the internal structure and encoding of this AVP.

7.2.95 Location-Estimate-Type AVP

The Location-Estimate-Type AVP (AVP code 1243) is of type Enumerated and contains one of the following values:

0 CURRENT_LOCATION
1 CURRENT_LAST_KNOWN_LOCATION
2 INITIAL_LOCATION
3 ACTIVATE_DEFERRED_LOCATION
4 CANCEL_DEFERRED_LOCATION

7.2.95A Location-Info AVP

The Location-Info AVP (AVP code 3460) is of type Grouped and provides information on the location (i.e., ECGI) and
associated time for the change to that location.

It has the following ABNF grammar:

Location-Info :: = < AVP Header: 3460>

[ 3GPP-User-Location-Info ]
[ Change-Time ]

3GPP
Release 15 149 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.96 Location-Type AVP

The Location-Type AVP (AVP code 1244) is of type Grouped and indicates the type of location estimate required by the
LCS client.

It has the following ABNF grammar:

Location-Type:: = < AVP Header: 1244>

[ Location-Estimate-Type ]
[ Deferred-Location-Event-Type ]

7.2.97 Low-Balance-Indication AVP

The Low-Balance-Indication AVP (AVP code 2020) is of type Enumerated and indicates if the subscriber balance went
below a designated threshold by its account. This indication can be used to advise the end user about the need to
replenish his balance. It can be one of the following values:

0 NOT-APPLICABLE
1 YES

7.2.97A Low-Priority-Indicator AVP

The Low-Priority-Indicator AVP (AVP code 2602) is of type Enumerated and indicates if the PDN connection has a low
priority, i.e. for Machine Type Communications. It can be one of the following values:

0 NO
1 YES

7.2.97B MBMS-Charged-Party AVP

The MBMS-Charged-Party AVP (AVP code 2323) is of type Enumerated and indicates which party is being charged by
the CDR generated. The following values are supported:

0 Content Provider
1 Subscriber

7.2.98 MBMS-GW-Address AVP

The MBMS-GW-Address AVP (AVP code 2307) is of type Address and holds the IP-address.
This AVP of the MBMS GW that generated the MBMS Charging ID when MBMS GW is stand-alone.

7.2.99 MBMS-Information AVP

The MBMS-Information AVP (AVP code 880) is of type Grouped. Its purpose is to allow the transmission of additional
MBMS service specific information elements.

It has the following ABNF grammar:

MBMS-Information :: = < AVP Header: 880>

[ TMGI ]
[ MBMS-Service-Type ]
[ MBMS-User-Service-Type ]
[ File-Repair-Supported ]
[ Required-MBMS-Bearer-Capabilities ]
[ MBMS-2G-3G-Indicator ]
[ RAI ]
* [ MBMS-Service-Area ]
[ MBMS-Session-Identity ]

3GPP
Release 15 150 3GPP TS 32.299 V15.4.0 (2018-09)

[ CN-IP-Multicast-Distribution ]
[ MBMS-GW-Address ]
[ MBMS-Charged-Party ]
* [ MSISDN ]
[ MBMS-Data-Transfer-Start ]
[ MBMS-Data-Transfer-Stop ]

7.2.100 MBMS-User-Service-Type AVP

The MBMS-User-Service-Type AVP (AVP code 1225) is of type Enumerated indicates type of service the the MBMS
user service that is being delivered. The following values are supported:

1 DOWNLOAD
The MBMS user service of type: download.

2 STREAMING
The MBMS user service is of type: streaming.

3GPP
Release 15 151 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.101 Media-Initiator-Flag AVP

The Media-Initiator-Flag AVP (AVP code 882) is of type Enumerated and indicates which party has requested the
session modification. The default value is '0' indicating the called party initiated the modification:

0 called party
1 calling party
2 unknown

7.2.102 Media-Initiator-Party AVP

The Media-Initiator-Party AVP (AVP code 1288) is of type UTF8String. Enumerated in IMS charging, it holds the
address (SIP URI or Tel URI) of the party (Public User ID or Public Service ID) who initiates the media action, like
adding/removing, connecting/disconnecting the media. The Media Initiator Party shall be populated with the SIP URI or
Tel URI contained in the Request-URI of the outgoing request. It is use for PoC charging.

7.2.103 Message-Body AVP

The Message-Body AVP (AVP Code 889) is of type Grouped AVP and holds information about the message bodies
including user-to-user data.

It has the following ABNF grammar:

<Message-Body>::= < AVP Header: 889 >

{ Content-Type }
{ Content-Length }
[ Content-Disposition ]
[ Originator ]

The message bodies shall not include the bodies' of Content-Type = "application-sdp" as these are captured in other
AVPs.

7.2.104 Message-Class AVP

The Message-Class AVP (AVP code 1213) is of type Grouped.

It has the following ABNF grammar:

Message-Class :: = < AVP Header: 1213 >

[ Class-Identifier ]
[ Token-Text ]

7.2.105 Message-ID AVP

The Message-ID AVP (AVP code 1210) is of type UTF8String and holds the identification of the message being
charged.

7.2.106 Message-Size AVP

The Message-Size AVP (AVP code 1212) is of type Unsigned32. For MMS, it holds the total size in bytes of the MM
calculated according to TS 23.140 [208]. For SMS, it holds the total size in octets of SM including any user data header.

3GPP
Release 15 152 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.107 Message-Type AVP

The Message-Type AVP (AVP code 1211) is of type Enumerated and holds the type of the message according to the
MMS transactions e.g. submission, delivery. The following values are defined and are as specified in MMS
Encapsulation [209]:

1 m-send-req
2 m-send-conf
3 m-notification-ind
4 m-notifyresp-ind
5 m-retrieve-conf
6 m-acknowledge-ind
7 m-delivery-ind
8 m-read-rec-ind
9 m-read-orig-ind
10 m-forward-req
11 m-forward-conf
12 m-mbox-store-conf
13 m-mbox-view-conf
14 m-mbox-upload-conf
15 m-mbox-delete-conf

7.2.108 MM-Content-Type AVP

The MM-Content-Type AVP (AVP code 1203) is of type Grouped and indicates the overall content type of the MM
content and includes information about all the contents of an MM.

It has the following ABNF grammar:

MM-Content-Type :: = < AVP Header: 1203 >

[ Type-Number ]
[ Additional-Type-Information ]
[ Content-Size ]
* [ Additional-Content-Information ]

7.2.109 MMBox-Storage-Requested AVP

The MMBox-Storage-Requested AVP (AVP code 1248) is of type Enumerated and indicates whether an MMBoxstorage
has been requested by the originator MMS User Agent or not. The values for whether an MMBox Storage was
requested are:

0 No
1 Yes

3GPP
Release 15 153 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.110 MMS-Information AVP

The MMS-Information AVP (AVP code 877) is of type Grouped. Its purpose is to allow the transmission of additional
MMS service specific information elements.

It has the following ABNF grammar:

MMS-Information :: = < AVP Header: 877>

[ Originator-Address ]
* [ Recipient-Address ]
[ Submission-Time ]
[ MM-Content-Type ]
[ Priority ]
[ Message-ID ]
[ Message-Type ]
[ Message-Size ]
[ Message-Class ]
[ Delivery-Report-Requested ]
[ Read-Reply-Report-Requested ]
[ MMBox-Storage-Requested ]
[ Applic-ID ]
[ Reply-Applic-ID ]
[ Aux-Applic-Info ]
[ Content-Class ]
[ DRM-Content ]
[ Adaptations ]
[ VASP-Id ]
[ VAS-Id ]

7.2.111 MMTel-Information AVP

The MMTel-Information AVP (AVP code 2030) is of type Grouped. Its purpose is to allow the transmission of additional
MMtel service specific information elements. It holds MMTel supplementary services invoked during MMTel service.

It has the following ABNF grammar:

MMTel-Information :: = < AVP Header: 2030>

* [ Supplementary-Service ]

7.2.111A MMTel-SService-Type AVP

The MMTel-SService-Type AVP (AVP Code 2031) is of type Unsigned32 and identifies the type of MMTel
supplementary service. The following values are defined:

0 Originating Identification Presentation (OIP)

1 Originating Identification Restriction (OIR)
2 Terminating Identification Presentation (TIP)
3 Terminating Identification Restriction (TIR)
4 Communication HOLD (HOLD)
5 Communications Barring (CB )
6 Communication Diversion (CDIV)
8 Communication Waiting (CW)
9 Message Waiting Indication (MWI)
10 Conference (CONF)
11 Flexible Alerting (FA)
12 Completion of Communication to Busy Subscriber (CCBS)
13 Completion of Communications on No Reply (CCNR)
14 Malicious Communication Identification (MCID)
15 Customized Alerting Tone (CAT)

3GPP
Release 15 154 3GPP TS 32.299 V15.4.0 (2018-09)

16 Closed User Group (CUG)

17 Personal Network management (PNM)
18 Customized Ringing Signal (CRS)
19 Advice of Charge (AoC)
20 Explicit Communication Transfer (ECT)

Values  1024 are reserved for specific Network/Manufacturer supplementary services variants.

7.2.111Aa Monitored-PLMN-Identifier AVP

The Monitored-PLMN-Identifier AVP (AVP code 3430) is of type UTF8String and carries Monitored PLMN ID in
MATCH_REPORT request. It corresponds to the Announcing UE VPLMN Identifier when roaming and Announcing
UE HPLMN Identifier when non-roaming. It is referred to as "Monitored PLMN ID” in TS 23.303 [235].

7.2.111AaA Monitoring-Event-Configuration-Activity AVP

The Monitoring-Event-Configuration-Activity AVP (AVP code3919) is of type Enumerated and indicates Monitoring
Event configuration action which triggers the Monitoring Event charging. The AVP may take the values as follows:

0 create
1 transfer
2 update
3 delete

7.2.111AaB Monitoring-Event-Functionality AVP

The Monitoring-Event-Functionality AVP (AVP code 3922) is of type Enumerated and indicates the Monitoring Event
functionality to be charged. The AVP may take the values as follows:

0 Configuration
1 Reporting

7.2.111AaC Monitoring-Event-Information AVP

The Monitoring-Event-Information AVP (AVP code 3921) is of type Grouped. Its purpose is to allow the transmission of
additional Monitoring Event specific information elements.

It has the following ABNF grammar:

Monitoring-Event-Information :: = < AVP Header: 3921>

[ Monitoring-Event-Functionality ]
[ Event-Timestamp ]
[ Monitoring-Event-Configuration-Activity ]
[ SCEF-Reference-ID ]
[ SCEF-ID ]
[ Monitoring-Type ]
[ Maximum-Number-of-Reports ]
[ Monitoring-Duration ]
[ Charged-Party ]
[ Maximum-Detection-Time]
[ UE-Reachability-Configuration ]
[ MONTE-Location-Type ]
[ Accuracy ]
* [ Number-Of-UE-Per-Location-Configuration ]
* [ Monitoring-Event-Report ]

3GPP
Release 15 155 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.111AaD Monitoring-Event-Report-Data AVP

The Monitoring-Event-Report-Data AVP (AVP code 3920) is of type Grouped. Its purpose is to allow the transmission
of charging information associated with an individual Monitoring Event report.

It has the following ABNF grammar:

Monitoring-Event-Report-Data :: = < AVP Header: 3920>

[ Event-Timestamp ]
[ SCEF-Reference-ID ]
[ SCEF-ID ]
[ Monitoring-Event-Report-Number ]
[ Charged-Party ]
[ Subscription-Id ]
[ Monitoring-Type ]
[ Reachability-Information ]
[ EPS-Location-Information ]
[ Communication-Failure-Information ]
* [ Number-Of-UE-Per-Location-Report ]

7.2.111AaE Monitoring-Event-Report-Number AVP

The Monitoring-Event-Report-Number AVP (AVP code 3923) is of type Unsigned32 and indicates the number of the
report being sent for the specific Monitoring Event request from this node.

7.2.111Ab Monitoring-UE-HPLMN-Identifier AVP

The Monitoring-UE-VPLMN-Identifier AVP (AVP code 3431) is of type UTF8String and contains identifier of
monitoring UE HPLMN.

7.2.111Ac Monitoring-UE-Identifier AVP

The Monitoring-UE-Identifier AVP (AVP code 3432) is of type UTF8String and carry identifier of the party who initiate
monitor/match report, i.e. IMSI, which corresponds to UE Identifier parameter in monitor/match report request.

7.2.111Ad Monitoring-UE-VPLMN-Identifier AVP

The Monitoring-UE-VPLMN-Identifier AVP (AVP code 3433) is of type UTF8String and contains identifier of
monitoring UE VPLMN.

7.2.111B MSC-Address AVP

The MSC-Address AVP (AVP code 3417) is type OctetString and contains the international E.164 address of the MSC
that generated the network call reference number. It is encoded as a TBCD-string. See TS 29.002 [232] for encoding of
TBCD-strings. This AVP does not include leading indicators for the nature of address and the numbering plan; it
contains only the TBCD-encoded digits of the address.

7.2.111C MTC-IWF-Address AVP

The MTC-IWF-Address AVP (AVP code 3406) is of type Address and holds the address of MTC-IWF for Machine Type
Communcication, defined in TS 29.337 [231].

7.2.111D Neighbour-Node-Address AVP

The Neighbour-Node-Address AVP (AVP code 2705) is of type Address and holds the control plane IP address of the
neighbouring network contact point that handles the service request in case of interconnection and roaming.

3GPP
Release 15 156 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.111E Network-Call-Reference-Number AVP

The Network-Call-Reference-Number AVP (AVP code 3418) is type OctetString and contains the reference number
generated by the GMSC/MSC for the voice call service. When combined with the identity of the MSC that allocated it
can be used to unambiguously identify the call.

7.2.112 Next-Tariff AVP

The Next-Tariff AVP (AVP code 2057) is of type Grouped and holds tariff information. The Tariff is a formula for cost
calculation given the Used-Service-Unit AVP. The calculated cost is given in the Currency-Code AVP.
The formula sums all the rating elements and multiplies the sum by the Scale-Factor AVP.

It has the following ABNF grammar:

Next-Tariff :: = < AVP Header: 2057 >

[ Currency-Code ]
[ Scale-Factor ]
* [ Rate-Element ]

7.2.112aA NIDD-Submission AVP

The NIDD-Submission AVP (AVP code 3928) is of type Grouped and holds information about the NIDD submission for
CP data transfer.

It has the following ABNF grammar:

NIDD-Submission :: = < AVP Header: 3928>

[ Submission-Timestamp ]
[ Event-Timestamp ]
[ Accounting-Input-Octets ]
[ Accounting-Output-Octets ]
[ Change-Condition ]

Editor’s Note: AVP for result of NIDD submission is ffs.

7.2.112A NNI-Information AVP

The NNI-Information AVP (AVP code 2703) is of type Grouped and holds information about the NNI used for
interconnection and roaming.

It has the following ABNF grammar:

NNI-Information :: = < AVP Header: 2703>

[ Session-Direction ]
[ NNI-Type ]
[ Relationship-Mode ]
[ Neighbour-Node-Address ]

3GPP
Release 15 157 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.112B NNI-Type AVP

The NNI-Type AVP (AVP code 2704) is of type Enumerated and indicates whether the type of used NNI is non-roaming,
roaming without loopback routing or roaming with loopback routing. It has the following values:

0 non-roaming
1 roaming without loopback
2 roaming with loopback

7.2.113 Node-Functionality AVP

The Node-Functionality AVP (AVP code 862) is of type Enumerated and includes the functionality identifier of the
node. The functionality identifier can be one of the following:

0 S-CSCF
1 P-CSCF
2 I-CSCF
3 MRFC
4 MGCF
5 BGCF
6 AS
7 IBCF
8 S-GW
9 P-GW
10 HSGW
11 E-CSCF
12 MME
13 TRF
14 TF
15 ATCF
16 Proxy Function
17 ePDG
18 TDF
19 TWAG
20 SCEF
21 IWK-SCEF

7.2.114 Node-Id AVP

The Node-Id AVP (AVP code 2064) is of type UTF8String and includes an optional, operator configurable identifier
string for the node.

7.2.115 Number-Of-Diversions AVP

The Number-of-Diversions AVP (AVP Code 2034) is of type Unsigned32 and holds the number of diversions related to
a CDIV service. When counting the number of diversions, all types of diversion are included.

7.2.116 Number-Of-Messages-Sent AVP

The Number-Of-Messages-Sent AVP (AVP code 2019) is of type Unsigned32 and indicates the number of SMSs sent by
the IMS application, if applicable. It contains the total number of SMS when concatenated short message for SMS
Offline Charging.

7.2.117 Number-Of-Participants AVP

The Number-Of-Participants AVP (AVP code 885) is of type Unsigned32 and holds the number of invited parties of the
multi-party session when included in the initial charging request message, e.g. in PoC, CONFerence and SIMPLE IM.

3GPP
Release 15 158 3GPP TS 32.299 V15.4.0 (2018-09)

When included in interim / update charging messages, it indicates the number of parties who are currently attached in
the session at the time the interim / update messages are sent.

NOTE: The information to populate this field may be obtained from the TBCP-Talk-Burst-Grant message in PoC
case. The information to populate this field may be obtained from the Diameter Accounting Request
message in MMTel CONF Charging.

7.2.118 Number-Of-Received-Talk-Bursts AVP

The Number-Of-Received-Talk-Bursts AVP (AVP code 1282) is of type Unsigned32 and holds the number of the
received talk bursts.

7.2.119 Number-Of-Talk-Bursts AVP

The Number-Of-Talk-Bursts AVP (AVP code 1283) is of type Unsigned32 and holds the number of the sent talk bursts.

7.2.120 Number-Portability-Routing-Information AVP

The Number-Portability-Routing-Information AVP (AVP code 2024) is of type UTF8String and holds information on
routing number received by the node (e.g. S-CSCF) performing number portability look-up (ENUM/DNS). This
information is also sent over SIP in the Requested URI header enabling other IMS nodes receiving this header to also
report this information.

7.2.121 Offline-Charging AVP

The Offline-Charging AVP (AVP code 1278) is a grouped AVP, which is used to set the parameters required to control
offline charging.

It has the following ABNF grammar:

Offline-Charging ::= < AVP Header:1278 >

[ Quota-Consumption-Time ]
[ Time-Quota-Mechanism ]
[ Envelope-Reporting ]
* [ Multiple-Services-Credit-Control ]
* [ AVP ]

At most one of Quota-Consumption-Time AVP or Time-Quota-Mechanism AVP shall be present, if individual instances
are not included within the Multiple-Services-Credit-Control AVP.

The Multiple-Services-Credit-Control AVPs, if present, shall contain the Rating-Group AVP to identify the category,
optionally one of Quota-Consumption-Time AVP and Time-Quota-Mechanism AVP, and optionally the Envelope-
Reporting AVP.

Any values specified in the Offline-Charging AVP take precedence over the configured defaults. The values of the
parameters specified at Multiple-Services-Credit-Control level take precedence over the values specified directly at
Offline-Charging level. If neither Quota-Consumption-Time AVP nor Time-Quota-Mechanism AVP is included in the
Multiple-Services-Credit-Control AVP, then the general reporting requirements dictated by the Quota-Consumption-
Time AVP or Time-Quota-Mechanism AVP and Envelope-Reporting AVP directly within the Offline-Charging AVP
shall apply.

7.2.122 Online-Charging-Flag AVP

The Online-Charging-Flag AVP (AVP code 2303) is of type Enumerated and indicates the Online Charging Request
was sent based on the provided ECF address from the SIP P-header "P-Charging-Function-Addresses". It has the
following values:

0 ECF address not provided

1 ECF address provided

3GPP
Release 15 159 3GPP TS 32.299 V15.4.0 (2018-09)

3GPP
Release 15 160 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.123 Originating-IOI AVP

The Originating-IOI AVP (AVP code 839) is of type UTF8String (alphanumeric string) and holds the Inter Operator
Identifier (IOI) for the originating network as generated by the IMS Network Element which takes responsibility for
populating this parameter in a SIP request as described in RFC 7315 [404] and TS 24.229 [202]. The Originating IOI
contains the following values:

Type 1 IOI
- IOI of the visited network where the P-CSCF is located for SIP requests directed to the S-
CSCF when initiated by the served user
- IOI of the home network where the S-CSCF is located for SIP requests directed to the TRF in
the visited network when "VPLMN routing" is applied in a Roaming Architecture for Voice
over IMS with Local breakout.
- IOI of the home network where the S-CSCF is located for SIP requests directed to the visited
network P-CSCF when terminated at the served user..
Type 2 IOI
- IOI of the home network of the originating end user where the S-CSCF is located in case a
session is initiated from the IMS. In case of redirection by the S-CSCF, Originating-IOI AVP
indicates the terminating party's network operator from which the session is redirected.
- IOI of the visited network when "VPLMN routing" is applied in a Roaming Architecture for
Voice over IMS with Local breakout.
- IOI of the originating network where the MGCF is located in case a session is initiated from
the PSTN toward the IMS.
Type 3 IOI
- IOI of the home network (originating side or terminating side) where the S-CSCF is located
when forwarding a SIP request as described in TS 24.229 [202] to an AS (proxy, terminating
UA or redirect server or B2BUA).
- IOI of the service provider network where the AS is located when an AS (originating UA or
B2BUA) initiates a SIP request as described in TS 24.229 [202].

For further details on the Type 1, Type 2 and Type 3 IOIs, please refer to TS 32.240 [1].

7.2.124 Originator AVP

The Originator AVP (AVP code 864) is of type Enumerated and indicates the originating party of the message body. The
following values are defined:

0 Calling Party
1 Called Party

7.2.125 Originator-Address AVP

The Originator-Address AVP (AVP code 886) is of type Grouped. Its purpose is to identify the originator of a message.

It has the following ABNF grammar:

Originator-Address :: = < AVP Header: 886 >

[ Address-Type ]
[ Address-Data ]
[ Address-Domain ]

3GPP
Release 15 161 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.126 Originator-Interface AVP

The Originator-Interface AVP (AVP code 2009) is the group AVP which contains information related to the Interface on
which the message originated.

It has the following ABNF grammar:

Originator-Interface ::= < AVP Header: 2009 >

[ Interface-Id ]
[ Interface-Text ]
[ Interface-Port ]
[ Interface-Type ]

7.2.127 Originator-Received-Address AVP

The Originator-Received-Address AVP (AVP code 2027) is of type Grouped. Its purpose is to identify the originator of a
message with the original, unmodified address information as received before any address manipulations has taken
place in the entity generating the charging information. This field allows correlation of address information with
information generated by other nodes in the message flow.

It has the following ABNF grammar:

Originator-Received-Address :: = < AVP Header: 2027>

[ Address-Type ]
[ Address-Data ]
[ Address-Domain ]

7.2.128 Originator-SCCP-Address
The Originator-SCCP-Address AVP (AVP code 2008) is of type Address. It is the "SCCP calling address" used by the
messaging node when receiving a message. This is usually the address of the MSC or SGSN/Serving Node that was
serving the UE when it submitted the message. It contains either a Point Code (ISPC) or a Global Title, where Global
Title represents an E.164 number. The Address Type discriminator in RFC 6733 [401] is set to value 8, E.164, and the
address information is UTF8 encoded.

7.2.128AOutgoing-Session-Id AVP
The Outgoing-Session-Id AVP (AVP code 2320) is of type UTF8String and holds the outgoing session identifier for an
AS acting as B2BUA. For a SIP session the Outgoing-Session-Id AVP contains the SIP Call ID of the outgoing leg, as
defined in RFC 3261 [405].

7.2.129 Outgoing-Trunk-Group-ID AVP

The Outgoing-Trunk-Group-ID AVP (AVP code 853) is of type UTF8String and identifies the outgoing PSTN leg.

7.2.130 Participants-Involved AVP

The Participants-Involved AVP (AVP code 887) is of type UTF8String and holds the list of address (Public User ID: SIP
URI, Tel URI, MSISDN) of the parties who are involved into the PoC session.

3GPP
Release 15 162 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.131 Participant-Group AVP

The Participant-Group AVP (AVP code 1260) is of type Grouped and holds detailed information, e.g. the address
(Public User ID: SIP URI, Tel URI, MSISDN), the access priority parameters, etc, of the party who is involved into the
PoC session.

It has the following ABNF grammar:

< Participant-Group > :: = < AVP Header: 1260>

[ Called-Party-Address ]
[ Participant-Access-Priority ]
[ User-Participating-Type ]

7.2.132 Participant-Access-Priority AVP

Participant-Access-Priority AVP (AVP code 1259) is of type Enumerated. It is a subfield of Participants-Group AVP to
indicate the priority level for users when initiating a new PoC session or participating in a PoC session. The AVP may
take the values as follows:

1 Pre-emptive priority:
The highest level priority. A request with pre-emptive priority SHALL cause the current other requests to
be revoked immediately, unless they are also with pre-emptive priority
2 High priority: Lower than Pre-emptive priority
3 Normal priority: Normal level. Lower than High priority
4 Low priority: Lowest level priority

7.2.133 Participant-Action-Type AVP

The Participant-Action-Type AVP (AVP code 2049) is of type Enumerated and holds the participant's action type during
the conference for Billing Domain's information. The following values are defined according to TS 24.605 [219]:

0 CREATE_CONF
1 JOIN_CONF
2 INVITE_INTO_CONF
3 QUIT_CONF

7.2.134 Void

7.2.135 Void

7.2.135APC3-Control-Protocol-Cause AVP
The PC3-Control-Protocol-Cause AVP (AVP code 3434) is of type Integer32 and holds the particular reason why a
DISCOVERY_REQUEST or MATCH_REPORT messages from the UE have been rejected by the ProSe Function. It is
referred to as "PC3 Control Protocol cause value” in TS 24.334 [236].

7.2.135BPC3-EPC-Control-Protocol-Cause AVP
The PC3-EPC-Control-Protocol-Cause AVP (AVP code 3435) is of type Integer32 and holds the particular reason why
a proximity request messages from the UE have been rejected by the ProSe Function. It is referred to as "PC3 EPC
Control Protocol cause value” in TS 24.334 [236].

3GPP
Release 15 163 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.135C PC5-Radio-Technology AVP

The PC5-Radio-Technology AVP (AVP code 1300) is of type Enumerated and indicates the PC5 radio technology that
the UE used for ProSe Direct Discovery. This AVP may take the value from the following:

0 EUTRA
1 WLAN
2 Both EUTRA and WLAN

3GPP
Release 15 164 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.136 PDN-Connection-Charging-ID AVP

The PDN-Connection-Charging-ID AVP (AVP code 2050) is of type Unsigned32 and contains the charging identifier to
identify different records belonging to same PDN connection. For a PDN connection that is limited to use a single
access at a time this field includes Charging Id of first IP-CAN bearer activated. Together with P-GW address this
uniquely identifies the PDN connection for charging.

Coding of this AVP is same as 3GPP-Charging-Id coding described in TS 29.061 [207].

7.2.137 PDP-Address AVP

The PDP-Address AVP (AVP code 1227) is of type Address and holds the IP-address associated with the IP CAN bearer
session (PDP context / PDN connection). The PDP-Address-Prefix-Length AVP needs not be available for IPv6 typed
IP-address prefix length of 64 bits.

7.2.137APDP-Address-Prefix-Length AVP
The PDP-Address-Prefix-Length AVP (AVP code 2606) is of type Unsigned32 and contains the prefix length of an IPv6
typed PDP-Address AVP. The omission of this AVP for an IPv6 typed IP address implicitly means prefix length of 64
bits, as in this case the 64 bit prefix length default shall be assumed.

7.2.138 PDP-Context-Type AVP

The PDP-Context-Type AVP (AVP code 1247) is of type Enumerated and indicates the type of a PDP context. The
values for requested are:

0 Primary
1 Secondary

This AVP shall only be present in the CCR[Initial].

7.2.138APlay-Alternative AVP
The Play-Alternative AVP (AVP code 3913) is of type Enumerated and indicates the call party toward whom an
announcement is directed.
It has the following values:

0 served party
1 remote party

7.2.139 PoC-Change-Condition AVP

The PoC-Change-Condition AVP (AVP code 1261) is of type Enumerated and contains the reason for closing a
container and the addition of a new container. The AVP may take the following values:

0 ServiceChange
1 VolumeLimit
2 TimeLimit
3 NumberofTalkBurstLimit
4 NumberofActiveParticipants
5 TariffTime

7.2.140 PoC-Change-Time AVP

The PoC-Change-Time AVP (AVP code 1262) is of type Time and is a time stamp that defines the moment when a
container is closed or the CDR is closed.

3GPP
Release 15 165 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.141 PoC-Controlling-Address AVP

The PoC-Controlling-Address AVP (AVP code 858) is of type UTF8String and identifies the PoC server performing the
controlling function for the associated PoC session.

3GPP
Release 15 166 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.142 PoC-Event-Type AVP

The PoC-Event-Type AVP (AVP code 2025) is of type Enumerated and indicates PoC session unrelated charging event.
The AVP may take the values as follows:

0 Normal;
1 Instant Ppersonal Aalert event;
2 PoC Group Advertisement event;
3 Early Ssession Setting-up event;
4 PoC Talk Burst

7.2.143 PoC-Group-Name AVP

The PoC-Group-Name AVP (AVP code 859) is of type UTF8String and identifies a group. Included if the session is a
pre-arranged group session or a chat group session. It can be used for PoC and OMA SIMPE IM Charging, or other
applications.

7.2.144 PoC-Information AVP

The PoC-Information AVP (AVP code 879) is of type Grouped. Its purpose is to allow the transmission of additional
PoC service specific information elements.

It has the following ABNF grammar:

PoC-Information :: = < AVP Header: 879>

[ PoC-Server-Role ]
[ PoC-Session-Type ]
[ PoC-User-Role ]
[ PoC-Session-Initiation-type ]
[ PoC-Event-Type ]
[ Number-Of-Participants ]
* [ Participants-Involved ]
* [ Participant-Group ]
* [ Talk-Burst-Exchange ]
[ PoC-Controlling-Address ]
[ PoC-Group-Name ]
[ PoC-Session-Id ]
[ Charged-Party ]

NOTE: In the ABNF definition of PoC-Information AVP, the Participants-Involved AVP is kept only for backward
compatibility with Releases before the 3GPP Release 7.

7.2.145 PoC-Server-Role AVP

The PoC-Server-Role AVP (AVP code 883) is of type Enumerated and specifies the role of the PoC server. The
identifier can be one of the following:

0 Participating PoC Server

1 Controlling PoC Server
2 Interworking function
3 Interworking selection function

7.2.146 PoC-Session-Id AVP

The PoC-Session-Id AVP (AVP code 1229) is of type UTF8String. It uniquely identifies an end-to-end PoC session and
may be used for correlation between charging information generated by participating and controlling PoC functions.
This information is obtained from the "Contact" header of the SIP message received from the controlling PoC function.

3GPP
Release 15 167 3GPP TS 32.299 V15.4.0 (2018-09)

NOTE: The PoC-Session-Id may not be available in the initial charging interactions for the PoC session.

7.2.147 PoC-Session-Initiation-Type AVP

The PoC-Session-Initiation-Type AVP (AVP code 1277) is of type Enumerated and specifies the type of the PoC session
initiation. The identifier can be one of the following:

0 Pre-established
1 On-demand

7.2.148 PoC-Session-Type AVP

The PoC-Session-Type AVP (AVP code 884) is of type Enumerated and specifies the type of the PoC session. The
identifier can be one of the following, refer Appendix C.5.1 in OMA PoC Control Plane specification [211]:

0 1 to 1 PoC session
1 Chat PoC group session
2 Pre-arranged PoC group session
3 Ad-hoc PoC group session

7.2.149 PoC-User-Role AVP

The PoC-User-Role AVP (AVP code 1252) is of type Grouped. It specifies the role(s) related information of the PoC
User that participating in the PoC Session.

It has the following grammar:

PoC-User-Role :: = <AVP header: 1252>

[ PoC-User-Role-Ids ]
[ PoC-User-Role-info-Units ]

7.2.150 PoC-User-Role-IDs AVP

The PoC-User-Role-IDs AVP (AVP code 1253) is of type UTF8String and identifies the PoC user role.

7.2.151 PoC-User-Role-Info-Units AVP

The PoC-User-Role-Info-Units (AVP code 1254) is of type Enumerated and specify the role type details of PoC users.
The identifier can be one of the following:

1 Moderator
2 Dispatcher
3 Session-Owner
4 Session-Participant

7.2.152 Positioning-Data AVP

The Positioning-Data AVP (AVP code 1245) is of type UTF8String and indicates the usage of each positioning method
that was attempted to determine the location estimate either successfully or unsuccessfully.

7.2.153 Preferred-AoC-Currency AVP

The Preferred-AoC-Currency AVP (AVP code 2315) is of type Unsigned32 and indicates the preferred currency code
that the AoC function would like to get the AoC information. It is specified by using the numeric values defined in the
ISO 4217 standard, refer RFC 4006 [402].

3GPP
Release 15 168 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.154 Priority AVP

The Priority AVP (AVP code 1209) is of type Enumerated and the priority (importance) of the message if specified. For
SMS Charging the value "low" is not applicable. The values are:

0 Low
1 Normal
2 High

7.2.154aA Privacy-Indicator AVP

The Privacy-Indicator AVP (AVP code 3915) is of type Enumerated. It is used to indicate whether the announcement is
considered private and is only to be played to the requested party. It has the following values:

0 NOT_PRIVATE
1 PRIVATE

7.2.154AProSe-3rd-Party-Application-ID AVP
The ProSe-3rd-Party-Application-ID AVP (AVP code 3440) is of type UTF8String and carry A globally unique
identifier identifying a specific 3rd party application, as upper layer of ProSe. It is referred to as "Applicatoin Identity”
in TS 24.334 [236].

7.2.154Aa ProSe-Direct-Communication-Reception-Data-Container AVP

The ProSe-Direct-Communication-Reception-Data-Container AVP (AVP code 3461) is of type Grouped. Its purpose is
to allow the transmission of the container to be reported for ProSe Charging. On encountering change on ProSe
charging condition, this container identifies the volume count for receiving within a ProSe group communication.

It has the following ABNF grammar:

ProSe-Direct-Communication-Reception-Data-Container :: = < AVP Header: 3461>

[ Local-Sequence-Number ]
[ Coverage-Status ]
[ 3GPP-User-Location-Info ]
[ Accounting-Input-Octets ]
[ Change-Time ]
[ Change-Condition ]
[ Visited-PLMN-Id ]
[ Usage-Information-Report-Sequence-Number ]
[ Radio-Resources-Indicator]
[ Radio-Frequency ]

7.2.154BProSe-Direct-Communication-Transmission-Data-Container AVP
The ProSe-Direct-Communication- Transmission-Data-Container AVP (AVP code 3441) is of type Grouped. Its
purpose is to allow the transmission of the container to be reported for ProSe Charging. On encountering change on
ProSe charging condition, this container identifies the volume count for transmitting within a ProSe group
communication.

It has the following ABNF grammar:

ProSe-Direct-Communication- Transmission-Data-Container :: = < AVP Header: 3441>

[ Local-Sequence-Number ]
[ Coverage-status ]
[ 3GPP-User-Location-Info ]
[ Accounting-Output-Octets ]

3GPP
Release 15 169 3GPP TS 32.299 V15.4.0 (2018-09)

[ Change-Time ]
[ Change-Condition ]
[ Visited-PLMN-Id ]
[ Usage-Information-Report-Sequence-Number ]
[ Radio-Resources-Indicator ]
[ Radio-Frequency ]

7.2.154C ProSe-Direct-Discovery-Model AVP

The ProSe-Direst-Discovery-Model AVP (AVP code 3442) is of type Enumerated and indicates model of the Direct
Discovery used by the UE. It is referred to as "Prose Direct Discovery Model” in TS 23.303 [235].The AVP may take
the values as follows:

0 Model A
1 Model B

7.2.154D ProSe-Event-Type AVP

The ProSe-Event-Type AVP (AVP code 3443) is of type Enumerated and indicates ProSe charging event. The AVP may
take the values as follows:

0 Annoucing
1 Monitoring
2 Match Report

7.2.154EProSe-Function-IP-Address AVP
The ProSe-Function-IP-Address AVP (AVP code 3444) is of type Address and holds the IP-address of the ProSe
Function.

7.2.154F ProSe-Function-PLMN-Identifier AVP

The ProSe-Function-PLMN-Identifier AVP (AVP code 3457) is of type UTF8String and contains identifier of Prose
Function resided PLMN.

7.2.154G ProSe-Functionality AVP

The ProSe-Functionality AVP (AVP code 3445) is of type Enumerated and indicates the ProSe functionality UE is
requesting. The AVP may take the values as follows:

0 Direct discovery
1 EPC-level discovery
2 Direct communication

7.2.154H ProSe-Group-IP-Multicast-Address AVP

The ProSe- Group-IP-Multicast-Address AVP (AVP code 3446) is of type Address and holds The IP multicast address to
be used for performing ProSe direct communication. It is referred to as "ProSe Group IP multicast address" in TS
23.303 [235].

7.2.154I ProSe-Information AVP

The ProSe-Information AVP (AVP code 3447) is of type Grouped. Its purpose is to allow the transmission of additional
ProSe service specific information elements.

It has the following ABNF grammar:

3GPP
Release 15 170 3GPP TS 32.299 V15.4.0 (2018-09)

ProSe-Information :: = < AVP Header: 3447>

* [ Supported-Features ]
[ Announcing-UE-HPLMN-Identifier ]
[ Announcing-UE-VPLMN-Identifier ]
[ Monitoring-UE-HPLMN-Identifier ]
[ Monitoring-UE-VPLMN-Identifier ]
[ Monitored-HPLMN-Identifier ]
[ Role-Of-ProSe-Function ]
[ ProSe-App-Id ]
[ ProSe-3rd-Party-Application-ID ]
[ Application-Specific-Data ]
[ ProSe-Event-Type ]
[ ProSe-Direct-Discovery-Model ]
[ ProSe-Function-IP-Address ]
[ ProSe-Function-ID ]
[ ProSe-Validity-Timer ]
[ ProSe-Role-Of-UE ]
[ ProSe-Request-Timestamp ] [ PC3-Control-Protocol-Cause ]
[ Monitoring-UE-Identifier ]
[ Prose-Function-PLMN-Identifier ]
[ Requestor-PLMN-Identifier ]
[ Origin-App-Layer-User-Id ]
[ WLAN-Link-Layer-Id ]
[ Requesting-EPUID ]
[ Target-App-Layer-User-Id ]
[ Requested-PLMN-Identifier ]
[ Time-Window ]
[ ProSe-Range-Class ]
[ Proximity-Alert-Indication ]
[ Proximity-Alert-Timestamp ]
[ Proximity-Cancellation-Timestamp ]
[ ProSe-Reason-For-Cancellation ]
[ PC3-EPC-Control-Protocol-Cause ]
[ ProSe-UE-ID ]
[ ProSe-Source-IP-Address ]
[ Layer-2-Group-ID ]
[ ProSe-Group-IP-Multicast-Address ]
* [ Coverage-Info ]
* [ Radio-Parameter-Set-Info ]
* [ Transmitter-Info ]
[ Time-First-Transmission ]
[ Time-First-Reception ]
* [ ProSe-Direct-Communication-Transmission-Data-Container ]
* [ ProSe-Direct-Communication-Reception-Data-Container ]
[ Announcing-PLMN-ID]
[ ProSe-Target-Layer-2-ID ]
[ Relay-IP-address ]
[ ProSe-UE-to-Network-Relay-UE-ID ]
[ Target-IP-Address ]
[ PC5-Radio-Technology ]

7.2.154J ProSe-Range-Class AVP

The ProSe-Range-Class AVP (AVP code 3448) is of type Enumerated and carry a range class for a specific proximity
request. The AVP may take the values as follows:

0 Reserved

1 50 m

2 100 m

3GPP
Release 15 171 3GPP TS 32.299 V15.4.0 (2018-09)

3 200 m

4 500 m

5 1000 m

6-255 Unused

It is referred to as "Range Class" in TS 24.334 [236].

7.2.154KProSe-Reason-For-Cancellation AVP
The ProSe-Reason-For-Cancellation AVP (AVP code 3449) is of type Enumerated and indicates the reason for
cancellation of an EPC-level discovery request. The AVP may take the values as follows:

0 Proximity Alert sent

1 Time expired with no renewal

2 Requestor cancellation

7.2.154L ProSe-Request-Timestamp AVP

The ProSe-Request-Timestamp AVP (AVP code 3450) is of type Time, and it holds the timestamp when ProSe Request
is received from UE.

7.2.154M ProSe-Role-Of-UE AVP

The ProSe- Role-Of-UE AVP (AVP code 3451) is of type Enumerated and indicates Role of the UE using ProSe. The
AVP may take the values as follows:

0 Announcing UE
1 Monitoring UE
2 Requestor UE
3 Requested UE

7.2.154N ProSe-Source-IP-Address AVP

The ProSe-Source-IP-Address AVP (AVP code 3452) is of type Address and holds the IP address UE used as source
address for performing ProSe direct communication. It is referred to as "source IP address" in TS 23.303 [235].

7.2.154O ProSe-UE-ID AVP

The ProSe-UE-ID AVP (AVP code 3453) is of type OctetString and carry a link layer identifier assigned by the EPS that
uniquely represents the UE in the context of ProSe Direct Communication. It is referred to as "ProSe UE ID" in TS
23.303 [235].

7.2.154Oa ProSe-UE-to-Network-Relay-UE-ID AVP

The ProSe-UE-to-Network-Relay-UE-ID AVP (AVP code4409) is of type OctetString and holds a link layer identifier
that uniquely represents the ProSe UE-to-Network relay UE in the context of ProSe Direct Communication via UE-to-
Network Relay.

7.2.154Ob ProSe-Target-Layer-2-ID AVP

The ProSe-Target-Layer-2-ID AVP (AVP code4410) is of type OctetString and carries the identifier of UE that uniquely
represents a specific one-to-one ProSe Direct Communication.

3GPP
Release 15 172 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.154PProximity-Alert-Indication AVP
The Proximity-Alert-Indication AVP (AVP code 3454) is of type Enumerated and indicates whether proximity alert has
been sent before proximity request cancellation. The AVP may take the values as follows:

0 Alert
1 No Alert

7.2.154Q Proximity-Alert-Timestamp AVP

The Proximity-Alert-Timestamp AVP (AVP code 3455) is of type Time, and it holds the timestamp when proximity alert
is sent, to indicate two UEs are in proximity.

7.2.154R Proximity-Cancellation-Timestamp AVP

The Proximity-Cancellation-Timestamp AVP (AVP code 3456) is of type Time, and it holds the timestamp when
proximity request cancellation is requested.

7.2.155 PS-Append-Free-Format-Data AVP

The PS-Append-Free-Format-Data AVP (AVP code 867) is of type enumerated and indicates if the information sent in
the PS-Free-Format-Data AVP shall be appended to the PS-free-format-data stored for the online-session. The following
values are defined:

0 'Append'
If this AVP is present and indicates 'Append', the P-GW shall append the received PS free format data to the PS
free format data stored for the online charging session.

1 'Overwrite'
If this AVP is absent or in value 'Overwrite', the P-GW shall overwrite all PS free format data already stored for
the online charging session.

The P-GW shall ignore this AVP if no PS free format data is stored for the online charging session.

7.2.156 PS-Free-Format-Data AVP

The PS-Free-Format-Data AVP (AVP code 866) is of type OctectString and holds online charging session specific data.

7.2.157 PS-Furnish-Charging-Information AVP

The PS-Furnish-Charging-Information AVP (AVP code 865) is of type Grouped. Its purpose is to add online charging
session specific information, received via the Ro reference point, onto the Rf reference point in order to facilitate its
inclusion in CDRs. This information element may be received in a CCA message via the Ro reference point. In
situations where online and offline charging are active in parallel, the information element is transparently copied into
an ACR to be sent on the Rf reference point.

It has the following ABNF grammar:

PS-Furnish-Charging-Information :: = < AVP Header: 865>

{ 3GPP-Charging-Id }
{ PS-Free-Format-Data }
[ PS-Append-Free-Format-Data ]

7.2.158 PS-Information AVP

The PS-Information AVP (AVP code 874) is of type Grouped. Its purpose is to allow the transmission of additional PS
service specific information elements.

3GPP
Release 15 173 3GPP TS 32.299 V15.4.0 (2018-09)

It has the following ABNF grammar:

PS-Information :: = < AVP Header: 874>

* [ Supported-Features ]
[ 3GPP-Charging-Id ]
[ PDN-Connection-Charging-ID ]
[ Node-Id ]
[ 3GPP-PDP-Type ]
* [ PDP-Address ]
[ PDP-Address-Prefix-Length ]
[ Dynamic-Address-Flag ]
[ Dynamic-Address-Flag-Extension ]
[ QoS-Information ]
* [ SGSN-Address ]
* [ GGSN-Address ]
* [ TDF-IP-Address ]
* [ SGW-Address ]
* [ ePDG-Address ]
* [ TWAG-Address ]
[ CG-Address ]
[ Serving-Node-Type ]
[ SGW-Change ]
[ 3GPP-IMSI-MCC-MNC ]
[ IMSI-Unauthenticated-Flag ]
[ 3GPP-GGSN-MCC-MNC ]
[ 3GPP-NSAPI ]
[ Called-Station-Id ]
[ 3GPP-Session-Stop-Indicator ]
[ 3GPP-Selection-Mode ]
[ 3GPP-Charging-Characteristics ]
[ Charging-Characteristics-Selection-Mode ]
[ 3GPP-SGSN-MCC-MNC ]
[ 3GPP-MS-TimeZone ]
[ Charging-Rule-Base-Name ]
[ ADC-Rule-Base-Name ]
[ 3GPP-User-Location-Info ]
[ User-Location-Info-Time ]
[ User-CSG-Information ]
* [ Presence-Reporting-Area-Information ]
[ 3GPP2-BSID ]
[ TWAN-User-Location-Info ]
[ UWAN-User-Location-Info ]
[ 3GPP-RAT-Type ]
[ PS-Furnish-Charging-Information ]
[ PDP-Context-Type ]
[ Offline-Charging ]
* [ Traffic-Data-Volumes ]
* [ Service-Data-Container ]
[ User-Equipment-Info ]
[ Terminal-Information ]
[ Start-Time ]
[ Stop-Time ]
[ Change-Condition ]
[ Diagnostics ]
[ Low-Priority-Indicator ]
[ NBIFOM-Mode ]
[ NBIFOM-Support ]
[ MME-Number-for-MT-SMS ]
[ MME-Name ]

3GPP
Release 15 174 3GPP TS 32.299 V15.4.0 (2018-09)

[ MME-Realm ]
[ Logical-Access-ID ]
[ Physical-Access-ID ]
[ Fixed-User-Location-Info ]
[ CN-Operator-Selection-Entity ]
[ Enhanced-Diagnostics ]
[ SGi-PtP-Tunnelling-Method ]
[ CP-CIoT-EPS-Optimisation-Indicator ]
[ UNI-PDU-CP-Only-Flag ]
[ Serving-PLMN-Rate-Control ]
[ APN-Rate-Control ]
[ Charging-Per-IP-CAN-Session-Indicator ]
[ RRC-Cause-Counter ]
[ 3GPP-PS-Data-Off-Status ]
[ SCS-AS-Address ]
[ Unused-Quota-Timer ]
* [ RAN-Secondary-RAT-Usage-Report ]

7.2.159 Quota-Consumption-Time AVP

The Quota-Consumption-Time AVP (AVP code 881) is of type Unsigned32 and contains an idle traffic threshold time in
seconds. This AVP may be included within the Multiple-Services-Credit-Control AVP when this AVP also contains a
Granted-Service-Units AVP containing a CC-Time AVP (i.e. when the granted quota is a time quota).

7.2.160 Quota-Holding-Time AVP

The Quota-Holding-Time AVP (AVP code 871) is of type Unsigned32 and contains the quota holding time in seconds.
The client shall start the quota holding timer when quota consumption ceases. This is always when traffic ceases, i.e.
the timer is re-started at the end of each packet. The Credit-Control Client shall deem a quota to have expired when no
traffic associated with the quota is observed for the value indicated by this AVP. The timer is stopped on sending a CCR
and re-initialised on receiving a CCA with the previous used value or a new value of Quota-Holding-Time if received.

This optional AVP may only occur in a CCA command. It is contained in the Multiple-Services-Credit-Control AVP. It
applies equally to the granted time quota and to the granted volume quota.

A Quota-Holding-Time value of zero indicates that this mechanism shall not be used. If the Quota-Holding-Time AVP is
not present, then a locally configurable default value in the client shall be used.

7.2.160aA Quota-Indicator AVP

The Quota-Indicator AVP (AVP code 3912) is of type Enumerated. It is used to indicate whether granted quota is to be
used during announcement setup and playback. It has the following values:

0 QUOTA_IS_NOT_USED_DURING_PLAYBACK
1 QUOTA_IS_USED_DURING_PLAYBACK

7.2.160ARadio-Frequency AVP
The Radio-Frequency AVP (AVP code 3462) is of type OctetString and identifies the radio frequency used for ProSe
direct communication. The format of the value is according to the ARFCN-ValueEUTRA-r9 ASN.1 data type described
in TS 36.331 [241].

7.2.160BRadio-Parameter-Set-Info AVP
The Radio-Parameter-Set-Info AVP (AVP code 3463) is of type Grouped and provides information on a radio parameter
set configured in the UE for direct communication use. Each set has an associated time stamp of when it became active.

It has the following ABNF grammar:

Radio-Parameter-Set-Info :: = < AVP Header: 3463>

3GPP
Release 15 175 3GPP TS 32.299 V15.4.0 (2018-09)

[ Radio-Parameter-Set-Values ]
[ Change-Time ]

7.2.160C Radio-Parameter-Set-Values AVP

The Radio-Parameter-Set-Values AVP (AVP code 3464) is of type OctetString and provides the radio parameter set
configured in the UE for direct communication. The format of the value is according to the SL-Preconfiguration-r12
ASN.1 data type described in TS 36.331 [241].

7.2.160D Radio-Resources-Indicator AVP

The Radio-Resources-Indicator AVP (AVP code 3465) is of type Integer32 and identifies whether the operator-provided
radio resources or the configured radio resources were used for ProSe direct communication. The allowed values are:

1 Operator-provided
2 Configured

7.2.160Da RAN-End-Timestamp AVP

The RAN-End-Timestamp AVP (AVP code 1301) is of type Time and holds the time in UTC format of the volume
container reported was collected, the end time of the reported usage.

7.2.160Db RAN-Secondary-RAT-Usage-Report AVP

The RAN-Secondary-RAT-Usage-Report AVP (AVP code 1302) is of type Grouped. This contains the volume count as
reported by the RAN for the secondary RAT (separated for uplink and downlink) for the bearer including the time of the
report. The 3GPP-Charging-Id AVP associated to this IP-CAN bearer is included when charging per IP-CAN session is
active.

It has the following ABNF grammar:

RAN-Secondary-RAT-Usage-Report :: = < AVP Header: 1302>

[Secondary-RAT-Type ]
[ RAN-Start-Timestamp ]
[ RAN-End-Timestamp ]
[ Accounting-Input-Octets ]
[ Accounting-Output-Octets ]
[ 3GPP-Charging-Id ]

7.2.160Dc RAN-Start-Timestamp AVP

The RAN-Start-Timestamp AVP (AVP code 1303) is of type Time and holds the time in UTC format of the volume
container reported was collected, the start time of the reported usage.

7.2.160E Rate-Control-Max-Message-Size AVP

The Rate-Control-Max-Message-Size AVP (AVP code 3937) is of type Unsigned32 and holds the maximum data PDU
size in octets.

7.2.160F Rate-Control-Max-Rate AVP

The Rate-Control-Max-Rate AVP (AVP code 3938) is of type Unsigned32 and holds the maximum number of data
PDUs per time unit indicated in Rate-Control-Time-Unit AVP.

3GPP
Release 15 176 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.160G Rate-Control-Time-Unit AVP

The Rate-Control-Time-Unit AVP (AVP code 3939) is of type Unsigned32 and holds a time unit for rate control.It has
the following values:

0 Unrestricted
This value is used to indicate the number of data PDUs is not restricted.

1 Minute
2 Hour
3 Day
4 Week

7.2.161 Rate-Element AVP

The Rate-Element AVP (AVP code 2058) is of type Grouped and holds simple rate element of one dimension. Possible
dimensions are the CC-Unit-Type.

Example: CC-Unit-Type AVP TIME, Unit-Value AVP 6 and Unit-Cost AVP 10 with Exponent AVP 2 should read:
10 cents per 6 seconds time. The currency is context dependent.

IF CC-Unit-Type AVP is MONEY, this is a fixed fee and Unit-Value is ignored.

It has the following ABNF grammar:

Rate-Element :: = < AVP Header: 2058 >

{ CC-Unit-Type }
[ Charge- Reason-Code ]
[ Unit-Value ]
[ Unit-Cost ]
[ Unit-Quota-Threshold ]

7.2.162 Read-Reply-Report-Requested AVP

The Read-Reply-Report-Requested AVP (AVP code 1222) is of type Enumerated and indicates whether a read reply
report has been requested by the originator MMS User Agent or not. The values for whether a report was requested are:

0 No
1 Yes

7.2.163 Void

3GPP
Release 15 177 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.164 Real-Time-Tariff-Information AVP

The Real-Time-Tariff-Information AVP (AVP code 2305) is of type Grouped and holds the tariff information received in
real time according to TS 29.658 [222] in the SIP signalling.

It has the following ABNF grammar:

< Real-Time-Tariff-Information > :: = < AVP Header: 2305 >

[ Tariff-Information ]
[ Tariff-XML ]

7.2.164AReason-Header AVP
The Reason-Header AVP (AVP code 3401) is of type UTF8String and contains the content of the Reason-header in the
SIP BYE and CANCEL. It may contain multiple entries if there are multiple Reason headers within a SIP BYE or
CANCEL.

7.2.165 Received-Talk-Burst-Time AVP

The Received-Talk-Burst-Time AVP (AVP code 1284) is of type Unsigned32 and holds the duration in seconds of the
received talk bursts.

7.2.166 Received-Talk-Burst-Volume AVP

The Received-Talk-Burst-Volume AVP (AVP code 1285) is of type Unsigned32 and holds the volume in bytes of the
received talk bursts.

7.2.167 Recipient-Address AVP

The Recipient-Address AVP (AVP code 1201) is of type Grouped. Its purpose is to identify the recipient of a message.

It has the following ABNF grammar:

Recipient-Address :: = < AVP Header: 1201 >

[ Address-Type ]
[ Address-Data ]
[ Address-Domain ]
[ Addressee-Type ]

3GPP
Release 15 178 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.168 Recipient-Info AVP

The Recipient-Info AVP (AVP code 2026) is of type Grouped. Its purpose is to group information associated with a
recipient. and contains the list of Recipient addresses of the message.

It has the following ABNF grammar:

Recipient-Info :: = < AVP Header: 2026 >

[ Destination-Interface ]
* [ Recipient-Address ]
* [ Recipient-Received-Address ]
[ Recipient-SCCP-Address ]
[ SM-Protocol-ID ]

NOTE 1: This Recipient-Info AVP allows charging for messages with multiple recipients by repeating this AVP for
every recipient. The Recipient-Info AVP unambigiously associates the grouped information to one
specific recipient.

NOTE 2: The SM-Protocol-ID AVP only relates to the recipient when charging MT SMS messages as specified in
TS 23.040 [216].

7.2.169 Recipient-Received-Address AVP

The Recipient-Received-Address AVP (AVP code 2028) is of type Grouped. Its purpose is to identify the recipient of a
message with the original, unmodified address information as received before any address manipulations has taken
place in the entity generating the charging information. This field allows correlation of address information with
information generated by other nodes in the message flow.

It has the following ABNF grammar:

Recipient-Received-Address :: = < AVP Header: 2028>

[ Address-Type ]
[ Address-Data ]
[ Address-Domain ]

7.2.170 Recipient-SCCP-Address
The Recipient-SCCP-Address AVP (AVP code 2010) is of type Address. It is the "SCCP called address" used by the
messaging node when delivering the message. This is usually the address of the MSC or SGSN/Serving Node that is
serving the UE when it delivers the message. It contains a Global Title, where Global Title represents an E.164 number,
and possibly a Point Code (ISPC). The AddressType discriminator in RFC 6733 [401] is set to value 8, E.164, and the
address information is UTF8 encoded.

7.2.171 Refund-Information AVP

The Refund-Information AVP (AVP code 2022) is of type OctetString and it conveys relevant information for the OCS
application relative to refund mechanism. When refund mechanism is implemented in the OCS this AVP may be
included in the CCA of the previous IEC. This AVP shall be used by the CTF in case of a refund scenario and thus shall
be included in the CCR for refund if previously received in CCA for IEC.

7.2.171ARelationship-Mode AVP
The Relationship-Mode AVP (AVP code 2706) is of type Enumerated and indicates whether the other functional entity
(e.g. contact point of the neighbouring network) is regarded as part of the same trust domain. It has the following
values:

0 trusted
1 non-trusted

3GPP
Release 15 179 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.171Aa Related-Change-Condition-Information AVP

The Related-Change-Condition-Information AVP (AVP code 3925) is of type Grouped. Its purpose is to allow the
transmission of the change condition information that occurred on another access of a multi-access PDN connection that
triggered an indirect change condition of the current access. In additional to the identification of the change condition(s)
that occurred on the other access, the supplemental data for that event is also included (e.g., user location information).

It has the following ABNF grammar:

Related- Change-Condition- Information :: = < AVP Header: 3925>

[ SGSN-Address ]
*[ Change-Condition]
[ 3GPP-User-Location-Info ]
[ 3GPP2-BSID ]
[ UWAN-User-Location-Info ]
[ Presence-Reporting-Area-Status ]
[ User-CSG-Information ]
[ 3GPP-RAT-Type ]

7.2.171Ab Related-Trigger AVP

The Related-Trigger AVP (AVP code 3926) is of type Grouped and holds the trigger types for a related trigger for
another access in a multi-access PDN connection. This AVP is only included when the Trigger AVP contains a Trigger-
Type AVP with value of "indirect change condition" which is applicable charging per IP can session for a multi-
accessPDN connection.

It has the following ABNF grammar:

Related-Trigger :: = < AVP Header: 3926 >

* [ Trigger-Type ]

7.2.171BRelated-IMS-Charging-Identifier AVP
The Related-IMS-Charging-Identifier AVP (AVP code 2711) is of type UTF8String and holds the Related IMS Charging
Identifier (ICID) as generated by the Enhanced MSC Server or the P-CSCF for the target access leg of an SRVCC
access transfer.

7.2.171C Related-IMS-Charging-Identifier-Node AVP

The Related-IMS-Charging-Identifier-Node AVP (AVP code 2712) is of type Address and holds the identifier of the
Enhanced MSC Server or the P-CSCF that generated the Related IMS Charging Identifier (ICID).

7.2.171D Relay-IP-address AVP

The Relay-IP-address AVP (AVP code 4411) is of type Address and holds the ProSe UE-to-Network Relay UE IP
address for performing ProSe Direct Communication via UE-to-Network.

7.2.172 Remaining-Balance AVP

The Remaining-Balance AVP (AVP code 2021) is of type Grouped and provides information about the remaining
account balance of the subscriber.

It has the following ABNF grammar:

Remaining-Balance :: = < AVP Header: 2021 >

3GPP
Release 15 180 3GPP TS 32.299 V15.4.0 (2018-09)

{ Unit-Value }
{ Currency-Code }

7.2.173 Reply-Applic-ID AVP

The Reply-Applic-ID AVP (AVP code 1223) is of type UTF8String and holds the identifier of a "reply path", i.e. the
identifier of the application to which delivery reports, read-reply reports and reply-MMs are addressed.

7.2.174 Reply-Path-Requested AVP

The Reply-Path-Requested AVP (AVP code 2011) is of type Enumerated. The possible values are:

0 No Reply Path Set

1 Reply path Set

3GPP
Release 15 181 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.175 Reporting-Reason AVP

The Reporting-Reason AVP (AVP code 872) is of type Enumerated and specifies the reason for usage reporting for one
or more types of quota for a particular category. It can occur directly in the Multiple-Services-Credit-Control AVP, or in
the Used-Service-Units AVP within a CCR command reporting credit usage. It shall not be used at command level. It
shall always and shall only be sent when usage is being reported. The following values are defined for the Reporting-
Reason AVP:

0 THRESHOLD
This value is used to indicate that the reason for usage reporting of the particular quota type indicated in the
Used-Service-Units AVP where it appears is that the threshold has been reached.

1 QHT
This value is used to indicate that the reason for usage reporting of all quota types of the Multiple-Service-
Credit-Control AVP where its appears is that the quota holding time specified in a previous CCA command has
been hit (i.e. the quota has been unused for that period of time).

2 FINAL
This value is used to indicate that the reason for usage reporting of all quota types of the Multiple-Service-
Credit-Control AVP where its appears is that a service termination has happened, e.g. PDP context, IP CAN
bearer termination or service data flow termination.

3 QUOTA_EXHAUSTED
This value is used to indicate that the reason for usage reporting of the particular quota type indicated in the
Used-Service-Units AVP where it appears is that the quota has been exhausted.

4 VALIDITY_TIME
This value is used to indicate that the reason for usage reporting of all quota types of the Multiple-Service-
Credit-Control AVP where its appears is that the credit authorization lifetime provided in the Validity-Time AVP
has expired.

5 OTHER_QUOTA_TYPE
This value is used to indicate that the reason for usage reporting of the particular quota type indicated in the
Used-Service-Units AVP where it appears is that, for a multi-dimensional quota, one reached a trigger condition
and the other quota is being reported.

6 RATING_CONDITION_CHANGE
This value is used to indicate that the reason for usage reporting of all quota types of the Multiple-Service-
Credit-Control AVP where its appears is that a change has happened in some of the rating conditions that were
previously armed (through the Trigger AVP, e.g. QoS, Radio Access Technology,…). The specific conditions that
have changed are indicated in an associated Trigger AVP.

7 FORCED_REAUTHORISATION
This value is used to indicate that the reason for usage reporting of all quota types of the Multiple-Service-
Credit-Control AVP where its appears is that it is there has been a Server initiated re-authorization procedure, i.e.
receipt of RAR command

8 POOL_EXHAUSTED
This value is used to indicate that the reason for usage reporting of the particular quota type indicated in the
Used-Service-Units AVP where it appears is that granted units are still available in the pool but are not sufficient
for a rating group using the pool.

9 UNUSED_QUOTA_TIMER
This value is used to indicate that the reason for usage reporting of all quota types of the Multiple-Service-
Credit-Control AVP where its appears is that the unused quota timer has expired.

The values QHT, FINAL, VALIDITY_TIME, FORCED_REAUTHORISATION, RATING_CONDITION_CHANGE,

UNUSED_QUOTA_TIMER apply for all quota types and are used directly in the Multiple-Services-Credit-Control
AVP, whereas the values THRESHOLD, QUOTA_EXHAUSTED and OTHER_QUOTA_TYPE apply to one particular
quota type and shall occur only in the Used-Service-Units AVP. The value POOL_EXHAUSTED apply to all quota
types using the credit pool and occurs in the Used-Service-Units AVP. It may optionally occur in the Multiple-Services-
Credit-Control AVP if all quota types use the same pool.

3GPP
Release 15 182 3GPP TS 32.299 V15.4.0 (2018-09)

When the value RATING_CONDITION_CHANGE is used, the Trigger AVP shall also be included to indicate the
specific events which caused the re-authorization request.

7.2.176 Requested-Party-Address AVP

The Requested-Party-Address AVP (AVP code 1251) is of type UTF8 String. It holds the address (SIP URI, Tel URI or
URN) of the party to whom the call was originaly addressed.

For IMS charging, it holds the address of the party (Public User ID or Public Service ID) to whom the SIP transaction
was originally posted. The Requested--Party-Address AVP shall be populated with the SIP URI, Tel URI or URN
contained in the Request-URI of the incoming request. This AVP is only present if different from the Called-Party-
Address AVP.

For VCS charging, it holds the address (URN is not applicable) which identifies the party to which a voice call is
destined before processing by the Proxy Function. It is converted from the circuit-switched Called Party BCD Number
as per TS 29.163 [234] for the Request-URI header. This is included only for a mobile originating call.

7.2.176ARequested-PLMN-Identifier AVP
The Requested-PLMN-Identifier AVP (AVP code 3436) is of type UTF8String and contains PLMN identifier of the user
who is targeted in proximity request.

7.2.176BRequestor-PLMN-Identifier AVP
The Requestor-PLMN-Identifier AVP (AVP code 3437) is of type UTF8String and contains PLMN identifier of the user
who initiate proximity request.

7.2.177 Role-Of-Node AVP

The Role-Of-Node AVP (AVP code 829) is of type Enumerated and specifies whether the IMS (except the MRFC) or
VCS node is serving the calling, called, or forwarding party. The identifier can be one of the following:

0 ORIGINATING_ROLE
The node is applying an originating role, serving the calling party.

1 TERMINATING_ROLE
The node is applying a terminating role, serving the called party.

2 FORWARDING_ROLE
The node is applying a originating role, serving the forwarding party.

7.2.177aA Role-Of-ProSe-Function AVP

The Role-Of-ProSe-Function AVP (AVP code 3438) is of type Enumerated and indicates ProSe Function resides in
which PLMN. The AVP may take the values as follows:

0 HPLMN
1 VPLMN
2 Local PLMN

7.2.177ARoute-Header-Received AVP
The Route-Header-Received AVP (AVP code 3403) is of type UTF8String and includes the information in the topmost
route header in a received initial SIP INVITE or non-session related SIP MESSAGE request.

7.2.177BRoute-Header-Transmitted AVP
The Route-Header-Transmitted AVP (AVP code 3404) is of type UTF8String and includes the information in the route
header representing the destination in a transmitted initial SIP INVITE or non-session related SIP MESSAGE request.

3GPP
Release 15 183 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.178 Scale-Factor AVP

The Scale-Factor AVP (AVP code 2059) is of type Grouped and holds simple multiplication factor in the same format as
Unit-Value.

It has the following ABNF grammar:

Scale-Factor :: = < AVP Header: 2059 >

{ Value-Digits }
[ Exponent ]

7.2.178aA SCEF-Address AVP

The SCEF-Address AVP (AVP code 1317) is of type Address and holds the IP-address of the SCEF.

7.2.178ASCS-Address AVP
The SCS-Address AVP (AVP code 3941) is of type Address and holds the IP-address of SCS/AS.

7.2.178BSCS-AS-Address AVP
The SCS-AS-Address AVP (AVP code 3940) is of type Grouped and holds the Address of SCS/AS.

It has the following ABNF grammar:

SCS-AS-Address :: = < AVP Header: 3940>

[ SCS-Realm ]
[ SCS-Address ]

7.2.178C SCS-Realm AVP

The SCS-Realm AVP (AVP code 3942) is of type DiameterIdentity and holds the Diameter Realm Identity of SCS/AS.

7.2.179 SDP-Answer-Timestamp AVP

The SDP-Answer-Timestamp AVP (AVP code 1275) is of type Time and holds the time in UTC format of the response
to the SDP offer.

7.2.180 SDP-Media-Component AVP

The SDP-Media-Component AVP (AVP code 843) is of type Grouped and contains information about media used for a
IMS session.

It has the following ABNF grammar:

SDP-Media-Component ::= < AVP Header: 843 >

[ SDP-Media-Name ]
* [ SDP-Media-Description ]
[ Local-GW-Inserted-Indication ]
[ IP-Realm-Default-Indication ]
[ Transcoder-Inserted-Indication ]
[ Media-Initiator-Flag ]
[ Media-Initiator-Party ]
[ 3GPP-Charging-Id ]
[ Access-Network-Charging-Identifier-Value ]

3GPP
Release 15 184 3GPP TS 32.299 V15.4.0 (2018-09)

[ SDP-Type ]

NOTE: When populating the SDP-Media-Component, either the 3GPP-Charging-ID or the Access-Network-
Charging-Identifier-Value should be present but not both. The 3GPP-Charging-ID is expected to be used
for 3GPP defined IP-CANS (e.g. GPRS) while the Access-Network-Charging-Identifier-Value is used for
non-3GPP defined IP-CANs.

Editor's Note: whether the Access-Network-Charging-Identifier-Value or the 3GPP-Charging-Id will be used of

Charging Id in 5GC is ffs.

7.2.181 SDP-Media-Description AVP

The SDP-Media-Description AVP (AVP code 845) is of type UTF8String and holds the content of SDP lines (i=, c=,
b=, k=, a=, etc.) related to a media description, as described in RFC 4566 [406]. The attributes are specifying the media
described in the SDP-Media-Name AVP.

7.2.182 SDP-Media-Name AVP

The SDP-Media-Name AVP (AVP code 844) is of type UTF8String and holds the content of the SDP "m=" line in a
media description, as described in RFC 4566 [406].

7.2.183 SDP-Offer-Timestamp AVP

The SDP-Offer-Timestamp AVP (AVP code 1274) is of type Time and holds the time in UTC format of the SDP offer.

7.2.184 SDP-Session-Description AVP

The SDP-Session-Description AVP (AVP code 842) is of type UTF8String and holds the content of the SDP line (i=,
c=, b=, k=, a=, etc.) in the session description, as described in RFC 4566 [406].

7.2.185 SDP-TimeStamps AVP

The SDP-TimeStamps AVP (AVP code 1273) is of type Grouped and holds the time of the SDP offer and the SDP
answer.

It has the following ABNF grammar:

SDP-TimeStamps :: = < AVP Header: 1273 >

[ SDP-Offer-Timestamp ]
[ SDP-Answer-Timestamp ]

7.2.186 SDP-Type AVP

The SDP-Type AVP (AVP code 2036) is of type Enumerated and holds information if the SDP media component was of
type SDP offer or SDP answer. The values are:

0 SDP Offer
1 SDP Answer

7.2.186ASession-Direction AVP
The Session-Direction AVP (AVP code 2707) is of type Enumerated and indicates whether the NNI is used for an
inbound or outbound service request on the control plane in case of interconnection and roaming.
It has the following values:

0 inbound

3GPP
Release 15 185 3GPP TS 32.299 V15.4.0 (2018-09)

1 outbound

7.2.187 Served-Party-IP-Address AVP

The Served-Party-IP-Address AVP (AVP code 848) is of type Address and holds the IP address of either the calling or
called party, depending on whether the P-CSCF is in touch with the calling or the called party. This AVP is only
provided by the P-CSCF.

7.2.188 Void

7.2.188ASecondary-RAT-Type AVP
The Secondary-RAT-Type AVP (AVP code 1304) is of type OctetString and Holds the value of Secondary RAT Type, as
provided by the RAN. The field is provided by the RAN and transferred to the S-GW/P-GW in the RAN Traffic Volume
element.

The following values are defined:

0 5G NR

7.2.189 Service-Data-Container AVP

The Service-Data-Container AVP (AVP code 2040) is of type Grouped. Its purpose is to allow the transmission of the
container to be reported for Flow based Charging or application based charging. On encountering change on charging
condition in Flow based Charging, this container identifies the volume count (separated for uplink and downlink),
elapsed time or number of events, per service data flow identified per rating group or combination of the rating group
and service id within an IP-CAN bearer. On encountering change on charging condition in application based Charging,
this container identifies the volume count (separated for uplink and downlink), elapsed time or number of events, per
rating group or combination of the rating group and service identifier within a TDF session.

It has the following ABNF grammar:

Service-Data-Container :: = < AVP Header: 2040>

[ AF-Correlation-Information ]
[ Charging-Rule-Base-Name ]
[ Accounting-Input-Octets ]
[ Accounting-Output-Octets ]
[ Local-Sequence-Number ]
[ QoS-Information ]
[ Rating-Group ]
[ Change-Time ]
[ Service-Identifier ]
[ Service-Specific-Info ]
[ ADC-Rule-Base-Name ]
[ SGSN-Address ]
[ Time-First-Usage ]
[ Time-Last-Usage ]
[ Time-Usage ]
*[ Change-Condition]
[ 3GPP-User-Location-Info ]
[ 3GPP2-BSID ]
[ UWAN-User-Location-Info ]
[ TWAN-User-Location-Info ]
[ Sponsor-Identity ]
[ Application-Service-Provider-Identity ]
* [ Presence-Reporting-Area-Information]
[ Presence-Reporting-Area-Status ]
[ User-CSG-Information ]
[ 3GPP-RAT-Type ]
[ Related-Change-Condition-Information ]

3GPP
Release 15 186 3GPP TS 32.299 V15.4.0 (2018-09)

[ Serving-PLMN-Rate-Control ]
[ APN-Rate-Control ]

[ 3GPP-PS-Data-Off-Status ]
[Traffic-Steering-Policy-Identifier-DL]

[Traffic-Steering-Policy-Identifier-UL]

7.2.190 Service-ID AVP

The Service-ID AVP (AVP code 855) is of type UTF8String and identifies the service the MRFC is hosting or AoC
service. For conferences the conference ID is used as the value of this parameter.

7.2.191 Service-Generic-Information AVP

The Service-Generic-Information AVP (AVP code 1256) is of type Grouped. Its purpose is to allow the transmission of
service information elements used for all services.

The AVP is defined in OMA-DDS-Charging_Data [223].

7.2.192 Service-Information AVP

The Service-Information AVP (AVP code 873) is of type Grouped. Its purpose is to allow the transmission of additional
3GPP service specific information elements which are not described in this document.

It has the following ABNF grammar:

Service-Information :: = < AVP Header: 873>

* [ Subscription-Id ]
[ AoC-Information ]
[ PS-Information ]
[ IMS-Information ]
[ MMS-Information ]
[ LCS-Information ]
[ PoC-Information ]
[ MBMS-Information ]
[ SMS-Information ]
[ VCS-Information ]
[ MMTel-Information ]
[ ProSe-Information ]
[ Service-Generic-Information ]
[ IM-Information ]
[ DCD-Information ]
[ M2M-Information ]
[ CPDT-Information ]

The format and the contents of the fields inside the Service-Information AVP are specified in the middle-tier documents
which are applicable for the specific service. Note that the formats of the fields are service-specific, i.e. the format will
be different for the various services.

The Subscription-Id AVP in Service-Information AVP is only used on the Rf interface.

Further fields may be included in the Service-Information AVP when new services are introduced.

3GPP
Release 15 187 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.193 Service-Mode AVP

The Service-Mode AVP (AVP Code 2032) is of type Unsigned32 and provides the mode for CDIV, CB and ECT MMTel
supplementary services. The following values are defined:

0 Communication Forwarding Unconditional (CFU)

1 Communication Forwarding Busy (CFB)
2 Communication Forwarding No Reply (CRNR)
3 Communication Forwarding on Not Logged-In (CFNL)
4 Communication Deflection (CD
5 Communication Forwarding on Subscriber Not Reachable (CFNRc)
6 Incoming Call Barring (ICB)
7 Outgoing Call Barring (OCB)
8 Anonymous Communication Rejection (ACR)
9 Blind Transfer
10 Consultative Transfer
11 Three-Party (3PTY)
12 Advice of Charge -S (AoC-S)
13 Advice of Charge -D (AoC-D)
14 Advice of Charge -E (AoC-E)

Values  1024 are reserved for specific Network/Manufacturer variants

7.2.194 Service-Specific-Data AVP

The Service-Specific-Data AVP (AVP Code 863) is of type UTF8String and holds the value of the Service-Specific-
Data.

7.2.195 Service-Specific-Info AVP

The Service-Specific-Info AVP (AVP Code 1249) is of type Grouped and holds service specific data if and as provided
by an Application Server, for IMS charging, a PCEF only for pre-defined PCC rules for PS domain charging, or a Proxy
function for VCS charging.

It has the following ABNF grammar:

Service-Specific-Info ::= < AVP Header: 1249 >

[ Service-Specific-Data ]
[ Service-Specific-Type ]

7.2.196 Service-Specific-Type AVP

The Service-Specific-Type AVP (AVP Code 1257) is of type Unsigned32 and holds the type of the Service-Specific-
Data.

7.2.197 Void

7.2.197a Serving-Node-Identity
The Serving-Node-Identity AVP (AVP code 3929) is of type DiameterIdentity and holds the identity of the Serving Node
(e.g. MME from the SCEF) that was used during a report.

3GPP
Release 15 188 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.198 Serving-Node-Type AVP

The Serving-Node-Type AVP (AVP Code 2047) is of type Enumerated and identifies the type of Serving Node. It may
take the following values:

0 SGSN
1 PMIPSGW
2 GTPSGW
3 ePDG
4 hSGW
5 MME
6 TWAN

7.2.198ASGi-PtP-Tunnelling-Method AVP
The SGi-PtP-Tunnelling-Method AVP (AVP Code 3931) is of type Enumerated and indicates whether SGi PtP
tunnelling method is based on UDP/IP or other methods for a non-IP PDN type PDN connection.The following values
are defined:

0 UDP_IP_based
1 Others

7.2.199 SGSN-Address AVP

The SGSN-Address AVP (AVP code 1228) is of type Address and holds the IP-address of the SGSN/Serving Node (e.g.
S-GW, AGW, ePDG, TWAG from the P-GW/TDF and S4-SGSN, MME from the S-GW) that was used during a report.

7.2.199ASGW-Address AVP
The SGW-Address AVP (AVP code 2067) is of type Address and holds the IP-address of the SGW Node.

7.2.200 SGW-Change AVP

The SGW-Change AVP (AVP Code 2065) is of type Enumerated, and indicates this is the first ACR[Start] due to an
inter serving node change (change from SGW, ePDG, TWAG, HSGW). If this AVP is not present, this means this
ACR[Start] is not due to an inter serving node change.

The following values are defined:

0 ACR_Start_NOT_due_to_SGW_Change

1 ACR_Start_due_to_SGW_Change

7.2.201 SIP-Method AVP

The SIP-Method AVP (AVP code 824) is of type UTF8String and holds the name of the SIP Method (INVITE, UPDATE
etc.) causing a accounting request to be sent to the CDF or CCR to be sent to the OCF.

7.2.202 SIP-Request-Timestamp AVP

The SIP-Request-Timestamp AVP (AVP code 834) is of type Time and holds the time in UTC format of the SIP request
(e.g. Invite, Update).

7.2.203 SIP-Request-Timestamp-Fraction AVP

The SIP-Request-Timestamp-Fraction AVP (AVP code 2301) is of type Unsigned32 and holds the miliseconds fraction
in relation to SIP-Request-Timestamp.

3GPP
Release 15 189 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.204 SIP-Response-Timestamp AVP

The SIP-Response-Timestamp AVP (AVP code 835) is of type Time and holds the time in UTC format of the response to
the SIP request (e.g. 200 OK).

7.2.205 SIP-Response-Timestamp-Fraction AVP

The SIP-Response-Timestamp-Fraction AVP (AVP code 2302) is of type Unsigned32 and holds the miliseconds fraction
in relation to SIP-Response-Timestamp.

7.2.205ASM-Device-Trigger-Indicator AVP
The SM-Device-Trigger-Indicator AVP (AVP code 3407) is of type Enumerated, and indicates whether the Short
Message is related to Device Trigger, and which action is requested by the Device trigger. If this AVP is not present, this
means the Short Message is not related to Device Trigger:

0 Not DeviceTrigger

1 Device Trigger request

2 Device Trigger replace

3 Device Trigger recall

7.2.205BSM-Device-Trigger-Information AVP
The SM-Device-Trigger-Information AVP (AVP code 3405) is of type Grouped and holds the specific device trigger
details for the Short Message.

It has the following ABNF grammar:

SM-Device-Trigger-Information :: = < AVP Header: 3405>

[ MTC-IWF-Address ]
[ Reference-Number ]
[ Serving-Node ]
[ Validity-Time ]
[ Priority-Indication ]
[ Application-Port-Identifier ]

7.2.206 SM-Discharge-Time AVP

The SM-Discharge-Time AVP (AVP code 2012) is of type Time. It indicates the time associated with the event being
reported in the SM-Status AVP. It is only used in scenarios in which the delivery of the Delivery-Report (more properly
the Status-Report) is being charged.

For example, if SM-Status has the value 0x00, then the SM-Discharge-Time indicates the time of the delivery of the
original Short Message.

The SMS Node shall ensure the correct encoding of this, as the other AVPs using the type Time, since the SMS
messages use different formats.

7.2.207 SM-Message-Type AVP

The SM-Message-Type AVP (AVP code 2007) is of type Enumerated and indicates the type of the message which
caused the charging interaction. The values are given below:

0 SUBMISSION

1 DELIVERY_REPORT

3GPP
Release 15 190 3GPP TS 32.299 V15.4.0 (2018-09)

2. SM Service Request

3 T4 Device Trigger

4 SM Device Trigger

5 MO-SMS T4 submission

7.2.208 SM-Protocol-Id AVP

The SM-Protocol-ID AVP (AVP code 2013) is of type OctetString and holds an indication of the protocol used for the
SM.

7.2.208ASM-Sequence-Number AVP
The SM-Sequence-Number AVP (AVP code 3408) is of type Unsigned32 and includes the sequence number of the SM
within the concatenated short message when applicable for SMS Offline Charging.

7.2.209 SM-Status AVP

The SM-Status AVP (AVP code 2014) is of type OctetString. The OctetString is of length 1 octet and contains status
information about the delivery of an SM.

7.2.210 SM-User-Data-Header AVP

The SM-User-Data-Header AVP (AVP code 2015) is of type OctetString and contains any user data header extracted
from the user data part of the SM. Encoding is as described in TS 23.040 [216]. Any padding bits are not considered
part of the header and are omitted.

7.2.211 SMS-Information AVP

The SMS-Information AVP (AVP code 2000) is of type Grouped. Its purpose is to allow the transmission of additional
SMS service specific information elements.

It has the following ABNF grammar:

SMS-Information :: = < AVP Header: 2000>

[ SMS-Node ]
[ Client-Address ]
[ Originator-SCCP-Address ]
[ SMSC-Address ]
[ Data-Coding-Scheme ]
[ SM-Discharge-Time ]
[ SM-Message-Type ]
[ Originator-Interface ]
[ SM-Protocol-ID ]
[ Reply-Path-Requested ]
[ SM-Status ]
[ SM-User-Data-Header ]
[ Number-Of-Messages-Sent ]
[ SM-Sequence-Number ]
* [ Recipient-Info ]
[ Originator-Received-Address ]
[ SM-Service-Type ]
[ SMS-Result ]
[ SM-Device-Trigger-Indicator ]
[ SM-Device-Trigger-Information ]

3GPP
Release 15 191 3GPP TS 32.299 V15.4.0 (2018-09)

[ MTC-IWF-Address ]
[ Application-Port-Identifier ]
[ External-Identifier ]

7.2.212 SMS-Node AVP

The SMS-Node AVP (AVP code 2016) is of type Enumerated and identifies the role which the SMS node performs in
relation to the charging event. It takes the following values:

0 SMS Router
1 IP-SM-GW
2 SMS Router and IP-SM-GW
3 SMS-SC

7.2.212ASMS-Result AVP
The SMS-Result AVP (AVP code 3409) is of type Unsigned32 and includes the result of an attempt for a Short Message
transaction (submission or delivery).

3GPP
Release 15 192 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.213 SM-Service-Type AVP

The SM-Service-Type AVP (AVP code 2029) is of type Enumerated and indicates the type of SM service that caused the
charging interaction. The values as defined in TS 22.142 [217] are given below:

0 VAS4SMS Short Message content processing

1 VAS4SMS Short Message forwarding
2 VAS4SMS Short Message Forwarding multiple subscriptions
3 VAS4SMS Short Message filtering
4 VAS4SMS Short Message receipt
5 VAS4SMS Short Message Network Storage
6 VAS4SMS Short Message to multiple destinations
7 VAS4SMS Short Message Virtual Private Network (VPN)
8 VAS4SMS Short Message Auto Reply
9 VAS4SMS Short Message Personal Signature
10 VAS4SMS Short Message Deferred Delivery

11 .. 99 Reserved for 3GPP defined SM services

100 .. 199 Vendor specific SM services

The SM-Service-Type AVP shall be present if the SM-Message-Type AVP has value 2, SM Service Request.

7.2.214 SMSC-Address AVP

The SMSC-Address AVP (AVP code 2017) is of type Address and carries the address of the SMSC, as contained in the
SM.

7.2.214AStart-of-Charging AVP
The Start-of-Charging AVP (AVP Code 3419) is of type Time and holds the time in UTC format which represents the
time origin for charging and may be equivalent to the time call setup is initiated or the time the call is answered
depending on configuration.

7.2.215 Start-Time AVP

The Start-Time AVP (AVP Code 2041) is of type Time and holds the time in UTC format which represents the start of a
user session at the S-GW/P-GW or the start of a voice call in the MSC.

7.2.215AStatus-AS-Code AVP
The Status-AS-Code AVP (AVP Code 2702) is of type Enumerated and only present to specify abnormal response code,
e.g, 4xx, 5xx or Timeout, etc for specific AS when it responds abnormally to S-CSCF.
If AS responds SIP 200 OK, this AVP isn't present in Application-Server-Information AVP.
The AVP may take the values as follows:

0 4xx;
1 5xx;
2 Timeout

7.2.216 Stop-Time AVP

The Stop-Time AVP (AVP Code 2042) is of type Time and holds the time in UTC format which represents the
termination of a user session at the S-GW/P-GW or the termination of a voice call in the MSC.

7.2.217 Submission-Time AVP

The Submission-Time AVP (AVP code 1202) is of type Time and indicates the time at which the message was submitted.

3GPP
Release 15 193 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.218 Subscriber-Role AVP

The Subscriber-Role AVP (AVP code 2033) is of type Enumerated and indicates the role of the subscriber (originating
party or terminating party) in MMTel supplementary services. The role can be one of the following:

0 Originating
1 Terminating

This AVP is not used.

7.2.219 Supplementary-Service AVP

The Supplementary-Service AVP (AVP code 2048) is of type Grouped and holds the specific supplementary service
details for one MMTel supplementary service.

It has the following ABNF grammar:

Supplementary-Service :: = < AVP Header: 2048>

[ MMTel-SService-Type ]
[ Service-Mode ]
[ Number-Of-Diversions ]
[ Associated-Party-Address ]
[ Service-ID ]
[ Change-Time ]
[ Number-Of-Participants ]
[ Participant-Action-Type ]
[ CUG-Information ]
[ AoC-Information ]

7.2.219ATAD-Identifier AVP
The TAD-Identifier AVP (AVP code 2717) is of type Enumerated and indicates the type of access network (CS or PS)
through which the session shall be terminated. It can be one of the following values:

0 CS
1 PS

7.2.220 Talk-Burst-Exchange AVP

The Talk-Burst-Exchange AVP (AVP code 1255) is of type Grouped and holds the talk burst related charging data.

It has the following ABNF grammar:

Talk-Burst-Exchange :: = < AVP Header: 1255 >

{ PoC-Change-Time }
[ Number-Of-Talk-Bursts ]
[ Talk-Burst-Volume ]
[ Talk-Burst-Time ]
[ Number-Of-Received-Talk-Bursts ]
[ Received-Talk-Burst-Volume ]
[ Received-Talk-Burst-Time ]
[ Number-Of-Participants ]
[ PoC-Change-Condition ]

3GPP
Release 15 194 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.221 Talk-Burst-Time AVP

The Talk-Burst-Time AVP (AVP code 1286) is of type Unsigned32 and holds the duration in seconds of the sent talk
bursts.

7.2.222 Talk-Burst-Volume AVP

The Talk-Burst-Volume AVP (AVP code 1287) is of type Unsigned32 and holds the volume in bytes of the sent talk
bursts.

7.2.222ATarget-IP-Address AVP
The Target-IP-Address AVP (AVP code 4412) is of type Address and holds the IP address used as target address for
performing ProSe Direct one-to-one Communication.

7.2.223 Tariff-Information AVP

The Tariff-Information AVP (AVP code 2060) is of type Grouped and holds a tariff definition either from the local
provider or from 3rd party provider. It contains information about the operator and the ID of the service being provided,
the current tariff and possible next tariff after tariff switch time. It may also chain to tariffs provided by intermediate
operators in the chain.

It has the following ABNF grammar:

Tariff-Information :: = < AVP Header: 2060 >

{ Current-Tariff }
[ Tariff-Time-Change ]
[ Next-Tariff ]

7.2.224 Tariff-XML AVP

The Tariff-XML AVP (AVP code 2306) is of type UTF8String and holds the XML body describing the tariff/add-on
charge information exchanged during the SIP transaction, as described in the TS 29.658 [222].

7.2.224ATeleservice AVP
The Teleservice AVP (AVP code 3413) is of type OctetString and holds the used teleservice for the voice call service.

7.2.225 Terminating-IOI AVP

The Terminating-IOI AVP (AVP code 840) is of type UTF8String (alphanumeric string) and holds the Inter Operator
Identifier (IOI) for the terminating network as generated by the IMS Network Element which takes responsibility for
populating this parameter in a SIP response as described in RFC 7315 [404] and TS 24.229 [202].

The Terminating IOI contains the following values:

Type 1 IOI

- IOI of the home network where the S-CSCF is located for SIP responses directed to
the P-CSCF in the visited network when request was initiated by the served user
- IOI of the visited network where the TRF is located for SIP responses directed to
the S-CSCF in the home network when request was initiated by the served user and "VPLMN routing" is applied
in a Roaming Architecture for Voice over IMS with Local breakout.
- IOI of the visited network where the P-CSCF is located for SIP responses directed to
the S-CSCF in the home network when request was terminated at the served user.

Type 2 IOI

3GPP
Release 15 195 3GPP TS 32.299 V15.4.0 (2018-09)

- IOI of the home network of the terminating end user where the S-CSCF is located in case a
session is initiated toward the IMS. In case of redirection by the S-CSCF, Terminating-IOI AVP indicates the
terminating party's network operator to which the session is redirected.
- IOI of the terminating network where the MGCF is located in case a session is initiated from the IMS toward
the PSTN.

Type 3 IOI

- IOI of the service provider network (originating side or terminating side) where the AS (proxy, terminating
UA or redirect server or B2BUA) is located when receiving a SIP request as described in TS 24.229 [202].
- IOI of the home network operator contacted by an AS when an AS (originating UA or B2BUA) initiates a SIP
request as described in TS 24.229 [202].

For further details on the Type 1, Type 2 and Type 3 IOIs, please refer to TS 32.240 [1].

7.2.225ATime-First-Reception AVP
The Time-First-Reception AVP (AVP code 3456) is of type Time and holds the time in UTC format for the first IP
packet received.

7.2.225BTime-First-Transmission AVP
The Time-First-Transmission AVP (AVP code 3467) is of type Time and holds the time in UTC format for the first IP
packet transmitted.

7.2.226 Time-First-Usage AVP

The Time-First-Usage AVP (AVP code 2043) is of type Time and holds the time in UTC format for the first IP packet to
be transmitted and mapped to the current service data container.

7.2.226ATime-Indicator AVP
The Time-Indicator AVP (AVP code 3911) is of type Unsigned32 and instructs the announcement to be connected at the
specified time before granted quota is exhausted, which ranges from zero to a value smaller than the granted quota. A
value of zero means at the time quota is exhausted. Absence of this field indicates that the announcement is to be played
before the IMS session is allowed to continue.

7.2.227 Time-Last-Usage AVP

The Time-Last-Usage AVP (AVP code 2044) is of type Time and holds the time in UTC format for the last IP packet to
be transmitted and mapped to the current service data container.

7.2.228 Time-Quota-Mechanism
The Time-Quota-Mechanism AVP (AVP code 1270) is of type Grouped.

It has the following syntax:

Time-Quota-Mechanism ::= < AVP Header: 1270>

{ Time-Quota-Type }
{ Base-Time-Interval }

The OCS may include this AVP in a Multiple-Services-Credit-Control AVP, when granting time quota.

3GPP
Release 15 196 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.229 Time-Quota-Threshold AVP

The Time-Quota-Threshold AVP (AVP code 868) is of type Unsigned32 and contains a threshold value in seconds. This
AVP may be included within the Multiple-Services-Credit-Control AVP when this AVP also contains a Granted-Service-
Units AVP containing a CC-Time AVP (i.e. when the granted quota is a time quota).

If received, the Credit-Control client shall seek re-authorization from the server for the quota when the quota contents
fall below the supplied threshold. The client shall allow service to continue whilst the re-authorization is progress, until
the time at which the original quota would have been consumed.

7.2.230 Time-Quota-Type AVP

The Time-Quota-Type AVP (AVP code 1271) is of type Enumerated. It is used to indicate which time quota consumption
mechanism shall be used for the associated Rating Group. It has the following values:

0 DISCRETE_TIME_PERIOD
1 CONTINUOUS_TIME_PERIOD

7.2.231 Time-Stamps AVP

The Time-Stamps AVP (AVP code 833) is of type Grouped and holds the time stamp of the SIP REQUEST and the time
stamp of the response to the SIP REQUEST.

It has the following ABNF grammar:

Time-Stamps ::= < AVP Header: 833 >

[ SIP-Request-Timestamp ]
[ SIP-Response-Timestamp ]
[ SIP-Request-Timestamp-Fraction ]
[ SIP-Response-Timestamp-Fraction ]

7.2.232 Time-Usage AVP

The Time-Usage AVP (AVP code 2045) is of type Unsigned32 and holds the effective used time within the service data
container reporting interval.

7.2.232ATLTRI AVP
The TLTRI AVP (AVP code 1318) is of type Unsigned32, and holds the identifies the T8 Long Term Transaction
Reference ID is which refers to long term transaction (e.g. NIDD Configuration, Group Message Request, Monitoring
Event configuration) between the SCEF and the SCS/AS when using T8 interface.

7.2.233 Traffic-Data-Volumes AVP

The Traffic-Data-Volumes AVP (AVP code 2046) is of type Grouped. Its purpose is to allow the transmission of the IP-
CAN bearer container, on encountering change on charging condition for this IP-CAN bearer.This container reports the
volume count (separated for uplink and downlink). The 3GPP-Charging-Id AVP for the IP-CAN bearer is included
when charging per IP-CAN session is active.

It has the following ABNF grammar:

Traffic-Data-Volumes :: = < AVP Header: 2046>

[ QoS-Information ]
[ Accounting-Input-Octets ]
[ Accounting-Output-Octets ]
[ Change-condition ]
[ Change-Time ]
[ 3GPP-User-Location-Info ]

3GPP
Release 15 197 3GPP TS 32.299 V15.4.0 (2018-09)

[ UWAN-User-Location-Info ]
[ 3GPP-Charging-Id ]
[ Presence-Reporting-Area-Status ]
[ User-CSG-Information ]
[ 3GPP-RAT-Type ]
[ Access-Availability-Change-Reason ]
[ Related-Change-Condition-Information ]
[ Diagnostics ]
[ Enhanced-Diagnostics ]
[ CP-CIoT-EPS-Optimisation-Indicator ]
[ Serving-PLMN-Rate-Control ]

7.2.233ATranscoder-Inserted-Indication AVP
The Transcoder-Inserted-Indication AVP (AVP code 2605) is of type Enumerated and indicates if a transcoder is
inserted or not for the SDP media component. The following values are defined:

0 Transcoder Not Inserted

1 Transcoder Inserted

7.2.233BTransit-IOI-List AVP
The Transit-IOI-List AVP (AVP code 2701) is of type UTF8String and holds the Inter Operator Identifiers (IOI) for the
transit networks as generated by the IMS Network Elements which take responsibility for populating this parameter in a
SIP request and response as described in RFC 7315 [404] and TS 24.229 [202]. Multiple occurrences of this AVP shall
be in chronological order, i.e. the value in the SIP request is listed first. If only a value for the SIP response is available,
the Transit-IOI-List for the SIP request shall be included with the value "unknown".

7.2.233C Transmitter-Info AVP

The Transmitter-Info AVP (AVP code 3468) is of type Grouped and provides information on a transmitter detected for
direct communication. Each transmitter is identified by a source IP address and ProSe UE ID.

It has the following ABNF grammar:

Transmitter-Info :: = < AVP Header: 3468>

[ ProSe-Source-IP-Address ]
[ ProSe-UE-ID ]

7.2.234 Token-Text AVP

The Token-Text AVP (AVP code 1215) is of type UTF8String and contains extension information for the Message-Class
AVP.

7.2.235 Trigger AVP

The Trigger AVP (AVP code 1264) is of type Grouped and holds the trigger types. The presence of the Trigger AVP
without any Trigger-Type AVP in a CCA allows OCS to disable all the triggers. The presence of the Trigger AVP in the
CCR identifies the event(s) triggering the CCR.

It has the following ABNF grammar:

Trigger :: = < AVP Header: 1264 >

* [ Trigger-Type ]

3GPP
Release 15 198 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.236 Trigger-Type AVP

The Trigger-Type AVP (AVP code 870) is of type Enumerated and indicates a single re-authorization event type.

When included in the CCA command, the Trigger-Type AVP indicates the events that shall cause the Credit-Control
client to re-authorize the associated quota. The client shall not re-authorize the quota when events which are not
included in the Trigger AVP occur.

When included in the CCR command indicates the specific event which caused the re-authorization request of the
Reporting-Reason with value RATING_CONDITION_CHANGE associated.

It has the following values:

1 CHANGE_IN_SGSN_IP_ADDRESS

This value is used to indicate that a change in the SGSN IP address shall cause the Credit-Control client to ask
for a re-authorization of the associated quota.

2 CHANGE_IN_QOS

This value is used to indicate that a change in the end user negotiated QoS shall cause the Credit-Control client
to ask for a re-authorization of the associated quota.

NOTE 1: This should not be used in conjunction with enumerated values 10 to 23.

3 CHANGE_IN_LOCATION

This value is used to indicate that a change in the end user location shall cause the Credit-Control client to ask
for a re-authorization of the associated quota.

NOTE 2: This should not be used in conjunction with enumerated values 30 to 36.

4 CHANGE_IN_RAT

This value is used to indicate that a change in the radio access technology shall cause the Credit-Control client to
ask for a re-authorization of the associated quota.

5 CHANGE_IN_UE_TIMEZONE
This value is used to indicate that a change in the TimeZone where the end user is located shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

10 CHANGEINQOS_TRAFFIC_CLASS
This value is used to indicate that a change in the end user negotiated traffic class shall cause the Credit-Control
client to ask for a re-authorization of the associated quota.

11 CHANGEINQOS_RELIABILITY_CLASS
This value is used to indicate that a change in the end user negotiated reliability class shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

12 CHANGEINQOS_DELAY_CLASS
This value is used to indicate that a change in the end user negotiated delay class shall cause the Credit-Control
client to ask for a re-authorization of the associated quota.

13 CHANGEINQOS_PEAK_THROUGHPUT
This value is used to indicate that a change in the end user negotiated peak throughput shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

14 CHANGEINQOS_PRECEDENCE_CLASS
This value is used to indicate that a change in the end user negotiated precedence class shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

15 CHANGEINQOS_MEAN_THROUGHPUT
This value is used to indicate that a change in the end user negotiated mean throughput shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

3GPP
Release 15 199 3GPP TS 32.299 V15.4.0 (2018-09)

16 CHANGEINQOS_MAXIMUM_BIT_RATE_FOR_UPLINK
This value is used to indicate that a change in the end user negotiated uplink maximum bit rate shall cause the
Credit-Control client to ask for a re-authorization of the associated quota.

17 CHANGEINQOS_MAXIMUM_BIT_RATE_FOR_DOWNLINK
This value is used to indicate that a change in the end user negotiated downlink maximum bit rate shall cause the
Credit-Control client to ask for a re-authorization of the associated quota.

18 CHANGEINQOS_RESIDUAL_BER
This value is used to indicate that a change in the end user negotiated residual BER shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

19 CHANGEINQOS_SDU_ERROR_RATIO
This value is used to indicate that a change in the end user negotiated SDU error ratio shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

20 CHANGEINQOS_TRANSFER_DELAY
This value is used to indicate that a change in the end user negotiated transfer delay shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

21 CHANGEINQOS_TRAFFIC_HANDLING_PRIORITY
This value is used to indicate that a change in the end user negotiated traffic handling priority shall cause the
Credit-Control client to ask for a re-authorization of the associated quota.

22 CHANGEINQOS_GUARANTEED_BIT_RATE_FOR_UPLINK
This value is used to indicate that a change in the end user negotiated uplink guaranteed bit rate shall cause the
Credit-Control client to ask for a re-authorization of the associated quota.

23 CHANGEINQOS_GUARANTEED_BIT_RATE_FOR_DOWNLINK
This value is used to indicate that a change in the end user negotiated downlink guaranteed bit rate shall cause
the Credit-Control client to ask for a re-authorization of the associated quota.

24 CHANGEINQOS_APN_AGGREGATE_MAXIMUM_BIT_RATE
This value is used to indicate that a change in the APN aggregate maximum bit rate for the IP-CAN session shall
cause the Credit-Control client to ask for a re-authorization of the associated quota. This value is only applicable
when charging per IP-CAN session is active.

30 CHANGEINLOCATION_MCC
This value is used to indicate that a change in the MCC of the serving network shall cause the Credit-Control
client to ask for a re-authorization of the associated quota.

31 CHANGEINLOCATION_MNC
This value is used to indicate that a change in the MNC of the serving network shall cause the Credit-Control
client to ask for a re-authorization of the associated quota.

32 CHANGEINLOCATION_RAC
This value is used to indicate that a change in the RAC where the end user is located shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

33 CHANGEINLOCATION_LAC
This value is used to indicate that a change in the LAC where the end user is located shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

34 CHANGEINLOCATION_CellId
This value is used to indicate that a change in the Cell Identity where the end user is located shall cause the
Credit-Control client to ask for a re-authorization of the associated quota.

35 CHANGEINLOCATION_TAC
This value is used to indicate that a change in the TAC where the end user is located shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

36 CHANGEINLOCATION_ECGI
This value is used to indicate that a change in the ECGI where the end user is located shall cause the Credit-
Control client to ask for a re-authorization of the associated quota.

3GPP
Release 15 200 3GPP TS 32.299 V15.4.0 (2018-09)

40 CHANGE_IN_MEDIA_COMPOSITION
This value is used to indicate that a change in the media composition (as identified within SDP) for an existing
SIP session shall cause the Credit-Control client to ask for a re-authorization of the associated quota.

50 CHANGE_IN_PARTICIPANTS_NMB
This value is used specifically for multi participating session to indicate that a change in the number of active
participants within a session shall cause the Credit-Control client to ask for a re-authorization of the associated
quota.

51 CHANGE_IN_ THRSHLD_OF_PARTICIPANTS_NMB
This value is used specifically to indicate that a change in the threshold of participants number within a session
shall cause the Credit-Control client to ask for a re-authorization of the associated quota.

NOTE 3: The threshold and the granularity of threshold are operator configurable. This should not be used in
conjunction with value 50.

52 CHANGE_IN_USER_PARTICIPATING_TYPE
This value is used specifically to indicate that a change in the user participating type within a session shall cause
the Credit-Control client to ask for a re-authorization of the associated quota.

60 CHANGE_IN_SERVICE_CONDITION
This value is used to indicate that a change in rating conditions associated with a service occurs.
The description of the conditions causing a change are service specific and may be documented in middle-tier
specifications or may be configurable.

61 CHANGE_IN_SERVING_NODE
This value is used to indicate that a change in serving node shall cause the Credit-Control client to ask for a re-
authorization of the associated quota.

62 CHANGE_IN_ACCESS_FOR_A_SERVICE_DATA_FLOW
This value is used to indicate that a change in access for a service data flow shall cause the Credit-Control client
to ask for a re-authorization of the associated quota. This value is only applicable when charging per IP-CAN
session is active for a multi-access PDN connection.

70 CHANGE_IN_USER_CSG_INFORMATION
This value is used to indicate a request of reporting the event that the user enters/leaves a CSG cell. When used
in a CCR, at entry to a CSG cell, the User-CSG-Information AVP shall be provided with the event report. When
used in a CCR without any User-CSG-Information AVP, it indicates the user leaves the CSG cell.

71 CHANGE_IN_HYBRID_SUBSCRIBED_USER_CSG_INFORMATION
This value is used to indicate a request of reporting the event that the user enters/leaves a hybrid cell that the user
subscribes to. When used in a CCR, at entry to a hybrid cell where the user is a member, the User-CSG-
Information AVP shall be provided with the event report. When used in a CCR without any User-CSG-
Information AVP, it indicates the user leaves the hybrid cell he was a member of.

72 CHANGE_IN_HYBRID_UNSUBSCRIBED_USER_CSG_INFORMATION
This value is used to indicate a request of reporting the event that the user enters/leaves a hybrid cell that the user
does not subscribe to. When used in a CCR, at entry to a hybrid cell where the user is not a member, the User-
CSG-Information AVP shall be provided with the event report. When used in a CCR without any User-CSG-
Information AVP, it indicates the user leaves the hybrid cell he was not a member of.

73 CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA
This value is used to indicate a request of reporting the event that the user enters/leaves the area(s) as indicated
in the Presence-Reporting-Area-Information AVP. This includes reporting the initial status at the time the request
is initiated. When used in a CCR, the Presence-Reporting-Area-Identifier AVP and Presence-Reporting-Area-
Status AVP shall be provided in the Presence-Reporting-Area-Information AVP with the event report. For the
UE-dedicated presence area, the Presence-Reporting-Area-Elements-List AVP shall be provided in the Presence-
Reporting-Area-Information AVP. When used in a CCA with a list of PRA(s) , the new list of PRA(s) shall
supersede the previous provided list. In case this trigger is not included in Trigger-Type AVP, it indicates all
PRAs are unsubscribed.74 CHANGE_IN_SERVING_PLMN_RATE_CONTROL
This value is used to indicate that a change in the Serving PLMN Rate Control shall cause the Credit-Control
client to ask for a re-authorization of the associated quota.

3GPP
Release 15 201 3GPP TS 32.299 V15.4.0 (2018-09)

75 CHANGE_IN_APN_RATE_CONTROL
This value is used to indicate that a change in the APN Rate Control shall cause the Credit-Control client to ask
for a re-authorization of the associated quota.

76 CHANGE_IN_3GPP_PS_DATA_OFF
This value is used to indicate that a change in the 3GPP_PS_DATA_OFF shall cause the Credit-Control client to
ask for a re-authorization of the associated quota.

7.2.237 Trunk-Group-ID AVP

The Trunk-Group-ID AVP (AVP code 851) is of type Grouped and identifies the incoming and outgoing PSTN legs.

It has the following ABNF grammar:

Trunk-Group-ID :: = <AVP Header: 851>

[ Incoming-Trunk-Group-ID ]
[ Outgoing-Trunk-Group-ID ]

7.2.237aA TTRI AVP

The TTRI AVP (AVP code 1319) is of type Unsigned32 and holds T8 Transaction Reference ID which refers to
transactions (e.g. Set Chargeable Party Request followed by Set Chargeable Party Response, NIDD Submit, etc.)
between the SCEF and the SCS/AS when using T8 interface.

7.2.237AVoid

7.2.237BVoid

7.2.237Ba TWAG-Address AVP

The TWAG-Address AVP (AVP code 3903) is of type Address and holds the IP-address of the TWAG Node.

3GPP
Release 15 202 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.237C TWAN-User-Location-Info AVP

The TWAN-User-Location-Info AVP (AVP code 2714) is of type Grouped and contains the UE location in a Trusted
WLAN Access Network (TWAN) as TWAN Identifier defined in TS 29.274 [226] .

It has the following ABNF grammar:

TWAN-User-Location-Info :: = < AVP Header: 2714>

{ SSID }
[ BSSID ]
[ Civic-Address-Information ]
[ WLAN-Operator-Id ]
[ Logical-Access-ID ]

7.2.238 Type-Number AVP

The Type-Number AVP (AVP code1204) is of type Enumerated and identifies the well-known media types. The values
are taken from OMNA WSP Content Type Numbers [210].

7.2.238AUNI-PDU-CP-Only-Flag AVP
The UNI-PDU-CP-Only-Flag AVP (AVP code 3932) is of type Enumerated, and indicates whether this PDN connection
is applied with "Control Plane Only flag", i.e. using only S11-U from S-GW when Control Plane CIoT EPS
Optimization is enabled. If this AVP is not present, this means both user plane and control plane can be used in UNI for
PDU transfer, i.e. S1-U and S11-U respectively from S-GW, when Control Plane CIoT EPS Optimization is enabled.
The following values are defined:

0 UNI-PDU-both-UP-CP
1 UNI-PDU-CP-Only

7.2.239 Unit-Cost AVP

The Unit-Cost AVP (AVP code 2061) is of type Grouped and holds monetary value. It has the same format of Unit-
Value AVP.

It has the following ABNF grammar:

Unit-Cost :: = < AVP Header: 2061 >

{ Value-Digits }
[ Exponent ]

7.2.240 Unit-Quota-Threshold AVP

The Unit-Quota-Threshold AVP (AVP code 1226) is of type Unsigned32 and contains a threshold value in service
specific units. This AVP may be included within the Multiple-Services-Credit-Control AVP when this AVP also contains
a Granted-Service-Units AVP containing CC-Service-Specific-Units AVP (i.e. when the granted quota is service
specific) or within Rate-Element AVP..

If received in the context of Multiple-Service-Credit-Control AVP, the Credit-Control client shall seek re-authorization
from the server for the quota when the quota contents fall below the supplied threshold.
The client shall allow service to continue whilst the re-authorization is in progress, up to the volume indicated in the
original quota.

In the context of the Rating-Element AVP it denotes the durability of a Rating Element within a Tariff. I.e. if the service
consumed Unit-Quota-Threshold number of Unit-Types, the next Rating element becomes in effect.

3GPP
Release 15 203 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.240a Unused-Quota-Timer AVP

The Unused-Quota-Timer AVP (AVP code 4407) is of type Unsigned32 and contains a threshold time in seconds for the
time period without any quota granted or any quota being consumed for any rating group belonging to the Gy session.

7.2.240AUser-CSG-Information AVP
The User-CSG-Information AVP (AVP code 2319) is of type Grouped and holds the user "Closed Subscriber Group"
information associated to CSG cell access: it comprises CSG ID within the PLMN, access mode and indication on CSG
membership for the user when hybrid access applies, as defined in TS 29.060 [225] for GPRS case, and in TS 29.274
[226] for EPC case.

It has the following ABNF grammar:

User-CSG-Information :: = < AVP Header: 2319>

{ CSG-Id }
{ CSG-Access-Mode }
[ CSG-Membership-Indication ]

7.2.240BUsage-Information-Report-Sequence-Number AVP
The Usage-Information-Report-Sequence-Number AVP (AVP code 3439) is of type Integer32 and indicates the
sequence number of usage information report, which is used to generate the container.

7.2.241 User-Participating-Type AVP

The User-Participating-Type AVP(AVP code 1279) is of type Enumerated. It is a subfield of Participants-Group AVP to
indicate the user participating type when participating in the PoC session. The AVP may take the values as follows:

0 Normal
1 NW PoC Box
2 UE PoC Box

7.2.242 User-Session-Id AVP

The User-Session-Id AVP (AVP code 830) is of type UTF8String and holds the session identifier. For a SIP session the
User-Session-Id contains the SIP Call ID, as defined in RFC 3261 [405]. When the AS acts as B2BUA, the incoming
Session-ID leg is covered.

7.2.242aaA UWAN-User-Location-Info AVP

The UWAN-User-Location-Info AVP (AVP code 3918) is of type Grouped and contains the UE location in an Unrusted
Wireless Access Network (UWAN). The UWAN User Location Information shall include the UE local IP address and
optionally UDP source port number (if NAT is detected) or TCP source port number. It may also include WLAN
Location Information as TWAN Identifier defined in TS 29.274 [226] .

It has the following ABNF grammar:

UWAN-User-Location-Info :: = < AVP Header: 3918>

{ UE-Local-IP-Address }
[ UDP-Source-Port ]
[ SSID ]
[ BSSID ]
[ TCP-Source-Port ]
[ Civic-Address-Information ]
[ WLAN-Operator-Id ]

3GPP
Release 15 204 3GPP TS 32.299 V15.4.0 (2018-09)

[ Logical-Access-ID ]

7.2.242aA Variable-Part AVP

The Variable-Part AVP (AVP code 3907) is of type Grouped and specifies the order, type, and value of a variable to be
played back within the announcement.

It has the following ABNF grammar:

Variable-Part :: = < AVP Header: 3907 >

[ Variable-Part-Order ]
{ Variable-Part-Type }
{ Variable-Part-Value }

7.2.242aB Variable-Part-Order AVP

The Variable-Part-Order AVP (AVP code 3908) is of type Unsigned32. It contains the order of the variable part within
the announcement to be played back.

7.2.242aC Variable-Part-Type AVP

The Variable-Part-Type AVP (AVP Code 3909) is of type Unsigned32 and holds the type of the variable part.

The following values are defined:

0 Integer
1 Number
2 Time
3 Date
4 Currency
5-127 Reserved for future standardization
128-255 Reserved for operator-defined types

7.2.242aD Variable-Part-Value AVP

The Variable-Part-Value AVP (AVP Code 3910) is of type UTF8String and holds the value of the variable part. Table
7.2.242aD.1 describes the content of the Variable-Part-Value AVP for each of the standardized values of the Variable-
Part-Type AVP.

Table 7.2.242aD.1: Variable-Part-Value AVP Contents

Type Value
Integer String of digits, which shall be announced as a single
number, up to 10 digits.
Number String of digits, which shall be announced as individual
digits, up to 24 digits.
Time A string of digits in the form HHMM.
Date A string of digits in the form of YYYYMMDD.
Currency A string of digits in the form of AAAAAABB, where AAAAAA
is the integral part and BB is the decimal part.

7.2.242AVCS-Information AVP
The VCS-Information AVP (AVP code 3410) is of type Grouped. Its purpose is to allow the transmission of additional
VCS service specific information elements.

It has the following ABNF grammar:

3GPP
Release 15 205 3GPP TS 32.299 V15.4.0 (2018-09)

VCS-Information :: = < AVP Header: 3410>

[ Bearer-Capability ]
[ Network-Call-Reference-Number ]
[ MSC-Address ]
[ Basic-Service-Code ]
[ ISUP-Location-Number ]
[ VLR-Number ]
[ Forwarding-Pending ]
[ ISUP-Cause ]
[ Start-Time ]
[ Start-of-Charging ]
[ Stop-Time ]
[ PS-Free-Format-Data ]

7.2.242BVLR-Number AVP
The VLR-Number AVP (AVP code 3420) is type OctetString and identifies the international E.164 address of the VLR
serving the user. It is encoded as a TBCD-string. See TS 29.002 [232] for encoding of TBCD-strings.
This AVP does not include leading indicators for the nature of address and the numbering plan; it contains only the
TBCD-encoded digits of the address.

7.2.243 Volume-Quota-Threshold AVP

The Volume-Quota-Threshold AVP (AVP code 869) is of type Unsigned32 and contains a threshold value in octets. This
AVP may be included within the Multiple-Services-Credit-Control AVP when this AVP also contains a Granted-Service-
Units AVP containing a CC-Total-Octets AVP, CC-Input-Octets AVP or CC-Output-Octets AVP (i.e. when the granted
quota is a volume quota).

If received, the Credit-Control client shall seek re-authorization from the server for the quota when the quota contents
fall below the supplied threshold. The client shall allow service to continue whilst the re-authorization is progress, up to
the volume indicated in the original quota.

7.2.244 Void

7.2.245 Void

7.2.246 Void

7.2.247 Void

7.2.248 Void

7.2.249 Void

3GPP
Release 15 206 3GPP TS 32.299 V15.4.0 (2018-09)

7.2.250 Void

7.2.251 WLAN-Operator-Id AVP

The WLAN-Operator-Id AVP (AVP code 1306) is of type Grouped and holds the identity of the trusted or untrusted
WLAN Operator.

WLAN-Operator-Id :: = < AVP Header: 1306>

[ WLAN-PLMN-Id ]
[ WLAN-Operator-Name ]

7.2.252 WLAN-Operator-Name AVP

The WLAN-Operator-Name AVP (AVP code 1307) is of type UTF8String and holds the Name of the trusted or
untrusted WLAN Operator, as specified in subclause 19. 8 of 3GPP TS 23.003 [224].

7.2.253 WLAN-PLMN-Id AVP

The WLAN-PLMN-Id AVP (AVP code 1308) is of type UTF8String and holds the PLMN Identity of the trusted or
untrusted WLAN Operator.

3GPP
Release 15 207 3GPP TS 32.299 V15.4.0 (2018-09)

7.3 3GPP2 specific AVPs

For the purpose of offline and online charging, the use of the AVPs defined for 3GPP2 Access is provided in table 7.3.1,
and the specification including the detailed definition and description, is referred to.

These AVPs shall be used together with value 5535 (3GPP2) as Vendor-Id.

Table 7.3.1: 3GPP2 specific AVPs

AVP Used in
AVP Name Reference
Code ACR ACA CCR CCA
3GPP2-BSID 9010 X - X - [215]

7.4 ETSI specific AVPs

For the purpose of offline and online charging, the use of the AVPs defined for Fixed Broadband Access is provided in
table 7.4.1, and the specification including the detailed definition and description, is referred to.

These AVPs shall be used together with value 13019 (ETSI) as Vendor-Id.

NOTE: The Fixed-User-Location-Info AVP is a fixed access specific AVP defined by 3GPP and listed in Table
7.2.0.1. The Fixed-User-Location-Info AVP uses the Vendor-Id specified in clause 7.2.0.

Table 7.4.1: ETSI specific AVPs

AVP Used in
AVP Name Reference
Code ACR ACA CCR CCA
Logical-Access-ID 302 X - X - [300]
Physical-Access-ID 313 X - X - [300]

7.5 oneM2M specific AVPs

For the purpose of offline and online charging, the use of the AVPs defined by oneM2M in oneM2M TS-0004[301] is
provided in table 7.5.1, and the specification including the detailed definition and description, is referred to.

These AVPs shall be used together with value 45687 (oneM2M) as Vendor-Id.

Table 7.5.1: oneM2M specific AVPs

AVP Used in
AVP Name Reference
Code ACR ACA CCR CCA
M2M-Information 1011 X - - - [301]

3GPP
Release 15 208 3GPP TS 32.299 V15.4.0 (2018-09)

Annex A (informative):
Bibliography
a The 3GPP charging specifications

- 3GPP TS 32.250: "Telecommunication management; Charging management; Circuit Switched (CS) domain
charging".

- 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain
charging".

- 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem

(IMS) charging".

- 3GPP TS 32.270: "Telecommunication management; Charging management; Multimedia Messaging Service

(MMS) charging".

- 3GPP TS 32.271: "Telecommunication management; Charging management; Location Services (LCS)

charging".

- 3GPP TS 32.272: "Telecommunication management; Charging management; Push-to-talk over Cellular

(PoC) charging".

- 3GPP TS 32.273: "Telecommunication management; Charging management; Multimedia Broadcast and

Multicast Service (MBMS) charging".

- 3GPP TS 32.274: "Telecommunication management; Charging management; Short Message Service (SMS)
charging".

- 3GPP TS 32.275: "Telecommunication management; Charging management; MultiMedia Telephony

(MMTel) charging".

- 3GPP TS 32.276: "Telecommunication management; Charging management; Voice Call Service Charging".

- 3GPP TS 32.277: "Telecommunication management; Charging management; Proximity-based Services

(ProSe) Charging".

- 3GPP TS 32.280: "Telecommunication management; Charging management; Advice of Charge (AoC)

service".

- 3GPP TS 32.298: "Telecommunication management; Charging management; Charging Data Record (CDR)
encoding rules description".

- 3GPP TS 32.297: "Telecommunication management; Charging management; Charging Data Record (CDR)
file format and transfer".

- 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS)
applications and interfaces".

- 3GPP TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR)
transfer".

- 3GPP TS 32.293: "Telecommunication management; Charging management; Proxy Function".

b Common 3GPP specifications

- 3GPP TS 33.201: "Access domain security".

c other Domain and Service specific 3GPP / ETSI specifications

3GPP
Release 15 209 3GPP TS 32.299 V15.4.0 (2018-09)

d Relevant ITU Recommendations

-
e Relevant IETF RFCs

- IETF RFC 959 (1985): "File Transfer Protocol".

- IETF RFC 1350 (1992): "TFTP Protocol".

Annex B (normative):
3GPP Charging Diameter Overload Control

B.1 DOIC (Diameter Overload Indication Conveyance)

B.1.0 General
The Diameter Base Protocol, IETF RFC 6733 [401], uses the Protocol Error "DIAMETER_TOO_BUSY", in the
Result_Code AVP of the answer to a related request, as a mean for overload control. This is further enhanced using
generic DOIC (Diameter Overload Indication Conveyance) mechanism specified in IETF RFC 7683 [403], which
makes it possible for a server to indicate overload situations to the clients before the server starts rejecting requests due
to overload and thus prevents retransmission of the requests.

This clause specifies the DOIC (Diameter Overload Indication Conveyance) mechanism for Diameter charging
applications.

B.1.1 Reporting node

When the OCS needs to request a reduction in the traffic it is handling due to an overload condition, it shall include the
OC-OLR AVP in answer messages, as defined in clause B.3. The OCS should include the OC-OLR AVP in the answer
messages for as long as the overload condition applies. This shall be based on the OC-Supported-Features AVP, defined
in clause B3, exchanged earlier.

How OCS determines that it is in an overload situation and the severity of the overload is implementation dependent
and based on operator policy.

B.1.2 Reacting node

A CTF acting as a reacting node reports its supported overload capabilities in the OC-Supported-Features AVP and
applies the requested traffic reduction received in OC-OLR AVPs in answer messages to corresponding applicable
requests, as per IETF RFC 7683 [33].

How it achieves the requested traffic reduction is implementation dependent.

B.2 Diameter overload AVPs

B.2.0 General
When the OCS determines the need to request a reduction in the traffic it is handling due to an overload condition, it
shall include the OC-OLR AVP in answer messages, as defined in IETF RFC 7683 [403].

3GPP
Release 15 210 3GPP TS 32.299 V15.4.0 (2018-09)

B.2.1 3GPP-OC-Rating-Group AVP

The OC-Rating-Group AVP (AVP code 1321), is of type Unsigned32. It contains the charging key (defined in TS 23.203
[218]) that the overload control is applied to, i.e. which Rating Groups should be restricted.

B.2.2 3GPP-OC-Request-Type AVP

The OC-Request-Type AVP (AVP code 1322), is of type Enumerated. It contains the CC-Request-Type (defined in IETF
RFC 4006 [402]) that the overload control be applied to, i.e. which types of request that should be restricted. It has the
following values:

1 INITIAL_REQUEST
2 UPDATE_REQUEST
3 TERMINATION_REQUEST
4 EVENT_REQUEST

B.2.3 3GPP-OC-Specific-Reduction AVP

The 3GPP-OC-Specific-Reduction AVP (AVP code 1320) is of type Grouped. It details the for which Rating Group,
type of requests or both the reduction, due to overload, should be applied.

It has the following ABNF grammar:

3GPP-OC-Specific-Reduction :: = < AVP Header: 1320 >

* [ 3GPP-OC-Rating-Group ]
* [ 3GPP-OC-Request-Type ]
[ OC-Reduction-Percentage ]
* [ AVP ]

B.2.4 OC-OLR AVP

The OC-OLR AVP (AVP code 623) is of type Grouped. It has been extended compared to the IETF RFC 7683 [403].

It has the following ABNF grammar:

OC-OLR :: = < AVP Header: 623 >

< OC-Sequence-Number >

< OC-Report-Type >
[ OC-Reduction-Percentage ]
[ OC-Validity-Duration ]
* [ 3GPP-OC-Specific-Reduction ]
* [ AVP ]

3GPP
Release 15 211 3GPP TS 32.299 V15.4.0 (2018-09)

Annex C (informative):
Change history

3GPP
Release 15 212 3GPP TS 32.299 V15.4.0 (2018-09)

Change history
Date TSG TSG Doc. CR Rev Subject/Comment Cat Old New
#
Dec 2007 SP-38 SP-070745 0202 -- Add new AVP codes to satisfy OMA charging requirements C 8.0.0 8.1.0
Dec 2007 SP-38 SP-070745 0203 -- Add new values to PoC-User-Role-info-Units AVP - Align with OMA C 8.0.0 8.1.0
PoC charging requirements
Dec 2007 SP-38 SP-070745 0204 -- Add general description to PoC-Group-Name B 8.0.0 8.1.0
Dec 2007 SP-38 SP-070925 0205 1 Introduce Diameter details for SMS charging B 8.0.0 8.1.0
Mar 2008 SP-39 SP-080059 0206 -- Add IBCF to Node-Functionality AVP list of NEs B 8.1.0 8.2.0
Mar 2008 SP-39 SP-080074 0207 -- Usage of CC-Correlation-Id in online charging - Align with IETF RFC C 8.1.0 8.2.0
4006
Mar 2008 SP-39 SP-080074 0208 -- Align Number-Of-Messages-Sent AVP in Diameter Binding for SMS C 8.1.0 8.2.0
charging with new R8 TS 32.274
Mar 2008 SP-39 SP-080074 0209 -- Corrections on Diameter AVP for SMS Charging F 8.1.0 8.2.0
Mar 2008 SP-39 SP-080074 0210 -- Add on Number Portability and Carrier Select routing information B 8.1.0 8.2.0
Jun 2008 SP-40 SP-080330 0211 -- Correction on SCCP-Address AVPs F 8.2.0 8.3.0
Jun 2008 SP-40 SP-080330 0212 -- Add PoC-Event-Type AVP into PoC-Information B 8.2.0 8.3.0
Jun 2008 SP-40 SP-080330 0213 -- Correction to PoC-Controlling-Address AVP and PoC-Group-Name F 8.2.0 8.3.0
AVP
Sep 2008 SP-41 SP-080466 0214 -- Correction of inconsistencies in Offline Charging and Online F 8.3.0 8.4.0
Charging messages
Sep 2008 SP-41 SP-080330 0215 -- Correction on AVP codes - Alignment with TS 29.230 F 8.3.0 8.4.0
Sep 2008 SP-41 SP-080330 0216 -- Multiple SMS destination - Alignment with TS 23.040 C 8.3.0 8.4.0
Dec 2008 SP-42 SP-080706 0218 - Completion on message tables F 8.4.0 8.5.0
Dec 2008 SP-42 SP-080707 0219 - Service Context Id for MMTEL B 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0220 - Correction on AVP code allocation F 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0221 - Clarification on AVP descriptions for EPC Charging F 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0222 - Add SMS-SC as SMS node type B 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0223 - Additional Address Info for SMS charging B 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0224 - Add charging of SMS services to 32.299 B 8.4.0 8.5.0
Dec 2008 SP-42 SP-080707 0225 - TS 32.299 AVPs Introduction for MMTel charging B 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0226 - Correction on References Section F 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0227 - Addition of SDP offer and answer and clarification on media initiator B 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0228 - Additional non-3GPP access information F 8.4.0 8.5.0
Dec 2008 SP-42 SP-080706 0229 - Add a new value to Trigger-Type AVP B 8.4.0 8.5.0
Dec 2008 SP-42 SP-080852 0217 - TS 32.299 AVPs for offline charging - Rf interface from S-GW and P- B 8.4.0 8.5.0
GW
Mar 2009 SP-43 SP-090206 0232 TS 32.299 MMTel information AVP alignment with 32.275 definition B 8.5.0 8.6.0
Mar 2009 SP-43 SP-090206 0235 Add CONF charging specific parameters B 8.5.0 8.6.0
Mar 2009 SP-43 SP-090203 1 Correction on 'Subscription Id' category used for EPS offline C 8.5.0 8.6.0
0230 Charging
Service-Type and Service-Mode in Supplementary-service AVP :
Mar 2009 SP-43 SP-090203 0231 - F 8.5.0 8.6.0
format change
Mar 2009 SP-43 SP-090206 0232 - SMS AVP structure alignment B 8.5.0 8.6.0
Mar 2009 SP-43 SP-090045 0234 Add Serving-Node-Type AVP to PS-Information in 32.299 B 8.5.0 8.6.0
Mar 2009 SP-43 SP-090206 0235 - AoC Support in Ro B 8.5.0 8.6.0
Mar 2009 SP-43 SP-090045 0236 - EPS Offline Charging - Complete PS-information AVP description B 8.5.0 8.6.0
Multiple subscription-id in service-information for EPS offline
Mar 2009 SP-43 SP-090203 0237 - B 8.5.0 8.6.0
Charging
Missing information in PS information AVP for SGW/PGW CDRs in
Mar 2009 SP-43 SP-090206 0238 - B 8.5.0 8.6.0
EPS offline charging
Jun 2009 SP-44 SP-090432 0243 - Correction of Recipient-Info AVP F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0244 - AVP code allocation for DCD Charging F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0245 - Rel-8 CR 32.299 alignment with RFC 4006 F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0246 - Rel-8 CR 32.299 clarification of ICID F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0247 - Remove generic "Non 3GPP specific information" parameter F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0248 - Correction on PDP context usage F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0249 - Correction on AoC-Information AVP F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0252 - Correction on Refund Information F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0253 - LCS-information AVP not complete F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0254 - PS-information AVP description alignment with 32.251 definition F 8.6.0 8.7.0
Jun 2009 SP-44 SP-090432 0257 - Correction on EPC Charging F 8.6.0 8.7.0
Add MMTel supplementary services FA, CCBS&CCNR, MCID, CAT
Jun 2009 SP-44 SP-090294 0251 - B 8.7.0 9.0.0
for MMTel Charging
Jun 2009 SP-44 SP-090292 0255 - Rel-9 CR 32.299 addition of online charging flag B 8.7.0 9.0.0
Jun 2009 SP-44 SP-090292 0256 - Rel-9 CR 32.299 correction of timestamp granularity B 8.7.0 9.0.0
Sep 2009 SP-45 SP-090536 0258 - Correction on AVP definitions A 9.0.0 9.1.0
Sep 2009 SP-45 SP-090536 0260 - Correction on MMS-Information AVP A 9.0.0 9.1.0
Sep 2009 SP-45 SP-090536 0262 - Rel-9 CR 32.299 correction and alignment with TS 32.280 A 9.0.0 9.1.0
Sep 2009 SP-45 SP-090536 0264 - Error in Number-Portability-Routing-Information AVP definition A 9.0.0 9.1.0
Sep 2009 SP-45 SP-090538 0265 - Add "Closed User Group (CUG)" for MMTel Charging B 9.0.0 9.1.0
Sep 2009 SP-45 SP-090538 0266 - Add 3PTY MMTel supplementary service charging B 9.0.0 9.1.0

3GPP
Release 15 213 3GPP TS 32.299 V15.4.0 (2018-09)

Sep 2009 SP-45 SP-090541 0267 - R9 CR 32299 add MBMS GW address below MBMS information AVP B 9.0.0 9.1.0
Sep 2009 SP-45 SP-090538 0268 - New AVPs for RTTI support in IMS offline charging B 9.0.0 9.1.0
Sep 2009 SP-45 SP-090536 0271 - Correction on Content Type - Alignment with OMA definition A 9.0.0 9.1.0
Sep 2009 SP-45 SP-090537 0272 - Correction of time stamp diameter types F 9.0.0 9.1.0
Sep 2009 SP-45 SP-090536 0274 - Correction of Accounting Input/Output Octets handling A 9.0.0 9.1.0
Sep 2009 SP-45 SP-090537 0275 - Emergency bearer service consideration for charging B 9.0.0 9.1.0
Addition of IP multicast delivery indicator below MBMS information
Sep 2009 SP-45 SP-090536 9.1.0
0277 - AVP A 9.0.0
Dec 2009 SP-46 SP-090720 0279 - Alignment of Address-Type AVP with 32.274 A 9.1.0 9.2.0
Alignment with TS 32.251 for "Volume Limit" and "Time Limit" in
Dec 2009 SP-46 9.2.0
SP-090720 0281 - Change-Condition AVP A 9.1.0
Dec 2009 SP-46 SP-090720 0283 - Multiple Change-Condition AVP for simultaneous Condition changes A 9.1.0 9.2.0
Dec 2009 SP-46 SP-090721 0284 - Editorial clean-up D 9.1.0 9.2.0
Dec 2009 SP-46 SP-090722 0285 - MMTel related AVP applicable for Online Charging B 9.1.0 9.2.0
Dec 2009 SP-46 SP-090720 0287 - Correction on priority session treatment A 9.1.0 9.2.0
Alignment with TS 32.251 for "User location Change" Condition in
Dec 2009 SP-46 9.2.0
SP-090720 0289 - Change-Condition AVP A 9.1.0
Alignment between Change-Condition AVP value with ASN1
Dec 2009 SP-46 9.2.0
SP-090720 0291 - ServiceConditionChange value "serviceStop" A 9.1.0
AVP for Account Expiration Information from OCS to IMS Application
Dec 2009 SP-46 9.2.0
SP-090721 0292 - Servers B 9.1.0
Aligning AoC- Information AVP with RTTI and subscription
Dec 2009 SP-46 9.2.0
SP-090721 0293 - information C 9.1.0
Dec 2009 SP-46 SP-090720 0295 - Correction of Number Portability and Carrier Select information AVPs A 9.1.0 9.2.0
Dec 2009 SP-46 SP-090721 0296 - Add CSG parameters for CSG based online and offline charging B 9.1.0 9.2.0
Mar 2010 SP-47 SP-100041 0297 - Correction on AVP code definitions F 9.2.0 9.3.0
Mar 2010 SP-47 SP-100040 0299 - Correction of Role-of-Node AVP A 9.2.0 9.3.0
Alignment with TS 32.251 for "Charging Characteristics Selection
Mar 2010 SP-47 9.3.0
SP-100040 0301 - Mode" parameter A 9.2.0
Mar 2010 SP-47 SP-100041 0302 - Add CSG parameters for CSG based online and offline charging F 9.2.0 9.3.0
Mar 2010 SP-47 SP-100044 0303 - MMTel related AVP applicable for Online Charging F 9.2.0 9.3.0
Mar 2010 SP-47 SP-100040 0305 - Correction for offline Charging from PGW - 3GPP2 User location A 9.2.0 9.3.0
Mar 2010 SP-47 SP-100041 0306 - Remove unused Service-Condition-Change AVP F 9.2.0 9.3.0
Mar 2010 SP-47 SP-100041 0307 - Correction on SDP handling in IMS Charging F 9.2.0 9.3.0
Add "Personal Network management" MMTel supplementary service
Mar 2010 SP-47 9.3.0
SP-100044 0308 - charging description B 9.2.0
Add "Customized Ringing Signal (CRS)" MMTel supplementary
Mar 2010 SP-47 9.3.0
SP-100044 0309 - service charging description B 9.2.0
Jun 2010 SP-48 SP-100265 0312 - Correction on AVP definitions A 9.3.0 9.4.0
Oct 2010 SP-49 SP-100496 0314 - Correction for Dual IP addresses associated to one PDN connection A 9.4.0 9.5.0
Correction on Charging-Rule-Based-Name AVP - Alignment with TS
Oct 2010 SP-49 SP-100495 A 9.5.0
0317 - 23.203 9.4.0
Oct 2010 SP-49 SP-100496 0319 - Correction on Event Charging with Reservation A 9.4.0 9.5.0
Oct 2010 SP-49 SP-100497 0320 - Correction of Reason-Code AVP F 9.4.0 9.5.0
Dec 2010 SP-50 SP-100756 0328 - Correction of Inter-Operator-Identifier AVP – Align with TS 32.260 A 9.5.0 9.6.0
Dec 2010 SP-50 SP-100757 0322 - Correction of Trigger-Type AVP F 9.5.0 9.6.0
Dec 2010 SP-50 SP-100758 0324 2 Add missing LCS-Format-Indicator AVP value for "SIP_URL" F 9.5.0 9.6.0
Dec 2010 SP-50 SP-100759 0325 2 Replace the Authorized-QoS AVP name with Authorised-QoS AVP F 9.6.0 10.0.0
Add E.164 harmonized address format to the current E.212 in MMS
Mar 2010 SP-51 10.1.0
SP-110109 0329 1 Charging C 10.0.0
Mar 2010 SP-51 SP-110105 0330 3 Adding CDR fields needed for Machine Type Communication B 10.0.0 10.1.0
Add missing enumeration value for E-CSCF network element in
Mar 2010 SP-51 10.1.0
SP-110108 0332 2 Node-Functionality AVP - Align with 32.298 A 10.0.0
Mar 2010 SP-51 SP-110108 0336 1 Add internal structure and encoding for the Location-Estimate AVP A 10.0.0 10.1.0
Mar 2010 SP-51 SP-110109 0340 2 Correction to charging scenarios D 10.0.0 10.1.0
Mar 2010 SP-51 SP-110108 0344 1 Correction of CSG trigger handling - Alignment with TS 29.212 A 10.0.0 10.1.0
Addition of IARI in IMS charging information, alignment with TS
Mar 2010 SP-51 10.1.0
SP-110109 0345 1 22.115 and TS 23.228 B 10.0.0
Mar 2010 SP-51 SP-110109 0347 1 R10 32299 Correction on AVP Subscriber-role F 10.0.0 10.1.0
Add 'Advice Of Charge (AoC)' MMTel supplementary service
Mar 2010 SP-51 10.1.0
SP-110112 0349 - Charging description - Align with 32.275 B 10.0.0
May
SP-52 10.2.0
2011 SP-110281 0352 1 Correction to Re-authorization Request Message F 10.1.0
May
SP-52 10.2.0
2011 SP-110281 0356 1 Correction of RAT-Type AVP, alignment with TS 29.212, Gx interface F 10.1.0
May
SP-52 10.2.0
2011 SP-110404 0359 1 Correction on essential supported fields in EPC Online Charging A 10.1.0
May
SP-52 10.2.0
2011 SP-110404 0362 1 Correction on Rf interface for missing information in SGW CDR A 10.1.0
May
SP-52 10.2.0
2011 SP-110294 0363 1 AVPs enhancement for OMR Charging introduction B 10.1.0
May
SP-52 10.2.0
2011 SP-110280 0365 1 Correction in SCC AS CDR for IMS service continuity A 10.1.0

3GPP
Release 15 214 3GPP TS 32.299 V15.4.0 (2018-09)

May Correction on IMS Application Reference Identifier (IARI) in IMS

SP-52 10.2.0
2011 SP-110281 0366 1 Charging F 10.1.0
May
SP-52 11.0.0
2011 SP-110317 0350 1 Rc Context Definition for Diameter Usage B 10.2.0
Sep 2011 SP-53 SP-110528 0370 - Correction on PDN connection identifier for Charging A 11.0.0 11.1.0
Correction for dynamic address flags associated to PDN connection
Sep 2011 SP-53 11.1.0
SP-110528 0375 - of PDP/PDN type IPv4v6 A 11.0.0
Sep 2011 SP-53 SP-110530 0377 - Correction of RAT Type, alignment with TS 29.061 A 11.0.0 11.1.0
Sep 2011 SP-53 SP-110528 0381 1 Correction on AVP definition - Align with IETF RFC 3588 A 11.0.0 11.1.0
Addition of Sponsored Data Connectivity charging - Align with TS
Sep 2011 SP-53 11.1.0
SP-110541 0393 1 23.203 B 11.0.0
Correction of Dynamic Address Flag usage for IPv4v6 PDN
Dec 2011 SP-54 11.1.0 11.2.0
SP-110708 0420 2 Connection in PS Information AVP A
Dec 2011 SP-54 SP-110711 0412 1 Correction of IPv6 PDP/PDN prefix A 11.1.0 11.2.0
Correction of IETF specified AVP usage in 3GPP charging
Dec 2011 SP-54 11.1.0 11.2.0
SP-110711 0416 - applications A
Dec 2011 SP-54 SP-110712 0394 2 Add Transit IOI to IMS Offline Charging B 11.1.0 11.2.0
Mar 2012 SP-55 SP-120048 0422 1 Add missing Trigger-Type value to address change of UE Timezone A 11.2.0 11.3.0
alignment with TS 29.212
Mar 2012 SP-55 SP-120049 0425 1 Add Status in AVP "Application-Server-Information B 11.2.0 11.3.0
June- SP-56 SP-120362 0428 1 Correction of Serving Node Type, alignment with 29.274 F 11.3.0 11.4.0
2012
June- SP-56 SP-120359 0430 1 Correction of AVP usage, alignment with RFC 4006 A 11.3.0 11.4.0
2012
June- SP-56 SP-120361 0433 1 Correction on AVP definition A 11.3.0 11.4.0
2012
June- SP-56 SP-120362 0434 1 Correction of Multiple Service Credit-Control use F 11.3.0 11.4.0
2012
June- SP-56 SP-120359 0440 1 Correction of diameter AVP usages, alignment with RFC 4006 A 11.3.0 11.4.0
2012
June- SP-56 SP-120360 0447 1 Correction on SGW and PGW Address reporting, alignment with A 11.3.0 11.4.0
2012 29.212
June- SP-56 SP-120374 0448 2 Enhancing IMS charging for RAVEL B 11.3.0 11.4.0
2012
June- SP-56 SP-120362 0449 1 Correction of Termination Action procedure F 11.3.0 11.4.0
2012
June- SP-56 SP-120397 0450 1 Add charging parameters for NetLoc B 11.3.0 11.4.0
2012
June- SP-56 SP-120361 0452 - Correction on PDP-Address-Prefix-Length A 11.3.0 11.4.0
2012
Sep- SP-57 SP-120646 0456 1 Rename Service-type AVP A 11.4.0 11.5.0
2012
Sep- SP-57 SP-120561 0460 - Remove Authorised-Qos from P-CSCF CDR A 11.4.0 11.5.0
2012
Sep- SP-57 SP-120566 0461 1 Correction on the AVP name F 11.4.0 11.5.0
2012
Sep- SP-57 SP-120566 0462 1 Supplementation for Reporting-Reason AVP C 11.4.0 11.5.0
2012
Sep- SP-57 SP-120564 0465 1 Correction of AoC-Information AVP usage A 11.4.0 11.5.0
2012
Sep- SP-57 SP-120562 0467 1 Correction of Called-Party-Address AVP A 11.4.0 11.5.0
2012
Sep- SP-57 SP-120566 0469 1 Correction of calling party handling C 11.4.0 11.5.0
2012
Sep- SP-57 SP-120646 0472 2 Correction on AoC service support A 11.4.0 11.5.0
2012
Sep- SP-57 SP-120627 0473 1 Reference list correction to align with the corrected TS 29.212 title F 11.4.0 11.5.0
2012
Dec- SP-58 SP-120789 0474 1 Correction on the figure description of Centralized Unit Determination F 11.5.0 11.6.0
2012 and Centralized Rating
Dec- SP-58 SP-120789 0476 1 Clarification of Type 1 and Type 2 IOI Usage for IMS Roaming F 11.5.0 11.6.0
2012
Dec- SP-58 SP-120785 0479 2 Emergency Indicator introduction in P-CSCF CDR A 11.5.0 11.6.0
2012
Dec- SP-58 SP-120801 0481 - Correction on NNI-Information AVP F 11.5.0 11.6.0
2012
Dec- SP-58 SP-120792 0482 1 Introduction AVPs description for SMS over MME Charging B 11.5.0 11.6.0
2012
Dec- SP-58 SP-120793 0483 1 Offline Charging description for ATCF B 11.5.0 11.6.0
2012
Dec- SP-58 SP-120789 0484 - Correction on charging for IMS transit functions F 11.5.0 11.6.0
2012
Mar-2013 SP-59 SP-130062 0488 1 Clarification of Type 1 IOI Usage and Multiple Sets of Inter Operator F 11.6.0 11.7.0
Identifiers for IMS Roaming

3GPP
Release 15 215 3GPP TS 32.299 V15.4.0 (2018-09)

SP-130054 0491 1 Related ICID Corrections for SRVCC Charging Correlation F

SP-130050 0495 1 Re-introduce Authorized-Qos AVP specified as unused A
SP-130054 0496 - Correction of LCS-Client-Type AVP definition F
0485 1 Correction on Trigger-Type AVP F
SP-130053 11.7.0 12.0.0
0489 1 Correction of Minimum Service-Context-Id AVP Content F
SP-130270 0502 1 Addition of IMS Visited Network Identifier A
SP-130270 0506 - Correction on AVP definitions A
SP-130271 0517 1 Adjustment on IMEI - alignment to TS 29.274 F
Jun-2013 SP-60 SP-130303 0528 - Correction of User-Equipment-Info-Value : encoding A 12.0.0 12.1.0
SP-130270 0530 1 Introduction of Charging for access to Trusted WLAN Access A
Network in EPC - over S2a
SP-130271 0531 1 Add Reason Header AVP B
SP-130443 0532 - Missing value for ATCF in Node-Functionality AVP F 12.1.0 12.2.0
SP-130435 0533 1 Correction on on data accounting F
Sep- SP-130443 0537 - Missing value for ATCF in Node-Functionality AVP A
SP-61
2013 SP-130435 0539 - Additional Access Network Information Field B
SP-130435 0540 - Align RAR/RAA description with other messages description and F
Correction on proxy-info AVP in RAA
Dec 2013 SP-62 SP-130677 0550 2 Correction for use of Destination-Host AVP in ACR A 12.2.0 12.3.0
SP-130620 0551 1 AVP enhancement for application based charging B
SP-130619 0552 2 Addition of Instance Id for IMS Charging B
SP-130618 0554 - Correction for User Location Info Time A
SP-130671 0559 - Correction on inconsistencies for MMTel Charging A
SP-130620 0560 1 AVP definition for application based charging B
SP-130627 0565 1 Correction for Route Header for IMS Interconnection Charging A
SP-130618 0567 - Correction on Application-Server-Information AVP A
Mar-2014 SP-63 SP-140154 0569 2 Addition of Fixed User Subscription Identifier B 12.3.0 12.4.0
SP-140033 0575 1 Correction of data type for Time-Usage and applicability of Service- A
Specific-Info and AF-Charging-Identifier
SP-140045 0576 1 Introduction of information for SMS offline Charging B
SP-140033 0581 - Correction for S-GW change in Change-Condition AVP A
Jun-2014 SP-64 SP-140336 0582 1 Remove clause 6.3 Editor's Notes F 12.4.0 12.5.0
SP-140337 0583 1 To add AVP definitions and clarifications for application based B
charging to align with TS 32.251
SP-140341 0584 - Introduce Access Line Identifier in PS-Information for Convergent B
Fixed-Mobile scenario
SP-140336 0585 1 Introduce Core Network Operator selection origin for Shared B
Networks
SP-140342 0586 2 Introduction of charging information for Voice Call Service (VCS) B
SP-140339 0587 1 Introduction of charging information for CHIPS - align with TS 32.251 B
SP-140335 0589 - Renaming of TWAN-SSID and TWAN-BSSID AVPs A
SP-140346 0591 1 Correction for TADS indication AVP F
SP-140343 0595 1 Correction to support multiple Transit IOI Lists in IMS Charging A
Jul-2014 - - - - Rapporteur/MCC: General editorial changes and clean-up. - 12.5.0 12.5.1
SP-140565 0596 1 Introduction of Presence Reporting Areas for Charging B
SP-140561 0601 1 Removal of CDIVN service A
SP-140564 0602 1 Corrections for alignment between charging specifications F
Sep- SP-140563 0603 1 Complete ePDG offline charging description B
SP-65 12.5.1 12.6.0
2014 Corrections to include missing fixed user location information for F
SP-140567 0604 - NSWO
SP-140569 0608 1 Correction to define missing AVP for MBMS offline charging A
SP-140563 0609 2 Removal of I-WLAN solution A
Dec- SP-66 Correction on User CSG Information in containers description for A 12.6.0 12.7.0
2014 SP-140802 0614 - EPC offline Charging
SP-140804 0615 1 Correction on Inter Node Change in SGW and ePDG offline charging F
SP-140807 0616 1 Clarification of serving node for TDF F
SP-140803 0618 - Correction to Status-Code AVP A
Mar 2015 SP-67 SP-150070 0625 1 Correction on IETF references A 12.7.0 12.8.0
SP-150066 0627 - Correction for charging based on MBMS Data Transfer Time A
SP-150065 0630 1 Inconsistency correction of subscriber role A
SP-150069 0631 1 Introducing new AVPs for ProSe charging B
SP-150062 0620 - Introduction of reason header in IMS online charging B 12.8.0 13.0.0
Jun 2015 SP-68 SP-150326 0632 1 Correction on 3GPP specific Diameter AVP definitions D 13.0.0 13.1.0
SP-150328 0634 1 Correction on charging information for Voice Call Service (VCS) A
0636 - Correction on Service-Information AVP for ProSe Charging A
SP-150332 0638 1 Alignment of Direct Communications CDR with PC3ch protocol A
SP-150325 0640 - Clarify Cause-code for IMS successful transaction A
SP-150331 0642 1 Correction TDF as Node Functionality A
SP-150318 0643 1 Introduction of multiple Release causes in EPC Charging B
SP-150321 0649 - Correction for dynamic address flags associated to PDN connection A
SP-150323 0653 - Correction of RAT Type - alignment with TS 29.061 A
SP-150326 0655 1 Correction for ProSe Charging D

3GPP
Release 15 216 3GPP TS 32.299 V15.4.0 (2018-09)

SP-150326 0656 1 Support for M2M-Information in the Service-Information AVP B

SP-150321 0657 - Harmonisation of clauses for vendor specific AVP D
Sep 2015 SP-69 SP-150425 0658 - Specification of code point for M2M-Information AVP F 13.1.0 13.2.0
SP-150428 0659 1 Parameter details on enhancements for IMS Service Continuity B
Correction on AVP for concatenated short messages in SMS Offline A
SP-150426 0661 1 Charging
SP-150423 0665 1 Correction on Subscriber-Role AVP specified as unused A
SP-150422 0668 - Correction on reference of User-Location-Info-Time AVP A
SP-150424 0670 1 Correction on AVP definitions F
SP-150425 0671 - Correction on Radio-Resources-Indicator AVP F
SP-150427 0673 - Correction of ABNF for ISUP-Cause AVP A
SP-150422 0676 1 Update of Reference RFC7315 A
SP-150424 0678 1 Correction on mapping between Information Elements and AVPs A
SP-150425 0679 1 Re-use ISUP-Cause AVP for IMS-PSTN Interworking B
Dec 2015 SP-70 Correction for Access-Network-Information AVP due to update to A 13.2.0 13.3.0
SP-150696 0682 - RFC 7315
SP-150704 0685 - Correction on interoperator identifier for IMS Roaming A
SP-150695 0691 1 Correction for when User leaves a CSG A
SP-150703 0692 1 Introduction of TWAG offline charging – charging information B
SP-150705 0698 - Correction on Tariff Information A
SP-150701 0699 - Introduction of ULI TZ Changes in IMS offline and online charging B
SP-150816 0700 1 Definition of AVPs for Announcement service B
Charging support for Terminating Identification Presentation feature B
SP-150698 0702 1 changes in terminating identity
Introduction of NBIFOM Support and NBIFOM Mode information for B
SP-150706 0703 1 PS charging
SP-150693 0704 1 Clarification of charging entity location limitation B
0707 1 Correction on CS Location Information in SIP AS CDR B
SP-150698 0711 1 Cell information received with untrusted WLAN access information B
Mar 2016 SP-71 SP-160040 0712 1 Charging Id assignment for NBIFOM B 13.3.0 13.4.0
Mar 2016 SP-71 SP-160039 0713 - Correction for Variable-Part-Type AVP values F 13.3.0 13.4.0
Mar 2016 SP-71 SP-160034 0714 - Correction for UE identification associated with inter-UE transfer F 13.3.0 13.4.0
Mar 2016 SP-71 SP-160040 0715 1 Correction for Access Availability Change Reason F 13.3.0 13.4.0
Mar 2016 SP-71 SP-160037 0716 1 ULI for untrusted wireless access network correction F 13.3.0 13.4.0
Mar 2016 SP-71 SP-160035 0718 1 Introducing new AVPs for MONTE charging B 13.3.0 13.4.0

3GPP
Release 15 217 3GPP TS 32.299 V15.4.0 (2018-09)

Change history
Date Meeting TDoc CR Rev Cat Subject/Comment New
version
2016-06 SA#72 SP-160416 0719 1 F Correction of cell information received with untrusted WLAN 13.5.0
access information – alignment with TS 24.229
2016-06 SA#72 SP-160416 0720 - F Correction to align AVP code for UWAN-User-Location-Info in 13.5.0
ABNF with table
2016-06 SA#72 SP-160412 0721 1 F Correction for the AVP codes for MONTE charging 13.5.0
2016-06 SA#72 SP-160420 0724 - B Completion of access change of service data flow for NBIFOM 13.5.0
2016-06 SA#72 SP-160420 0725 1 B Completion of change of charging condition for NBIFOM 13.5.0
2016-06 SA#72 SP-160411 0726 3 B Introduce CP data transfer Rf offline charging 13.5.0
2016-06 SA#72 SP-160411 0734 1 B Introduce non-IP PDN and CP CIoT opt in Rf offline charging 13.5.0
2016-06 SA#72 SP-160417 0732 1 F Correction on the AoC-Information AVP and Terminal-Information 14.0.0
AVP
2016-09 SA#73 SP-160623 0736 1 B Complement of Charging per IP-CAN Session 14.1.0
2016-09 SA#73 SP-160621 0739 1 F Introduction of allocated AVPs code ranges - alignement 14.1.0
with 29.230
2016-09 SA#73 SP-160621 0740 1 A Correction of trigger conditions description for NIDD submission 14.1.0
2016-09 SA#73 SP-160621 0741 1 A Correction on AVP Code for Serving PLMN Rate Control - 14.1.0
alignement with 29.230
2016-09 SA#73 SP-160621 0742 1 A Correction on APN Rate Control - Alignment with TS 23.401 14.1.0
2016-09 SA#73 SP-160621 0745 - A Correction on Control Plane CIoT EPS Optimisation Indicator in 14.1.0
PGW - alignement with 23.401
2016-09 SA#73 SP-160621 0746 - A Correction on "MO exception data" RRC establishment cause in 14.1.0
offline charging – alignement with TS 23.401
2016-12 SA#74 SP-160845 0752 1 A Correction on Requested Party Address for Emergency IMS 14.2.0
session
2016-12 SA#74 SP-160851 0754 - A Correction on duplicate values for Change-Condition 14.2.0
2016-12 SA#74 SP-160847 0755 1 F Correction on Access Network Info change with the time in offline 14.2.0
2016-12 SA#74 SP-160847 0756 1 F Correction on Role-Of-node for AS serving the forwarding party 14.2.0
2016-12 SA#74 SP-160847 0757 1 F Correction of Number-Portability-Routing-Information 14.2.0
2016-12 SA#74 SP-160847 0758 1 F Correction of Called-Party-Address and Requested-Party-Address 14.2.0
2016-12 SA#74 SP-160847 0759 1 F Correction of Change-Time to include Access Transfer Time 14.2.0
2017-03 SA#75 SP-170144 0760 1 B Charging enhancement for 3GPP PS Data off 14.3.0
2017-03 SA#75 SP-170133 0761 1 B Addition of the fields for ProSe Charging 14.3.0
2017-03 SA#75 SP-170129 0762 1 B Addition of multiple PRAs support for AULC 14.3.0
2017-03 SA#75 SP-170137 0764 1 A Correction on the APN Rate Control and SCS/AS Address AVP 14.3.0
2017-03 SA#75 SP-170136 0770 1 A Correction removal of Redirect-Address-Type from CCR 14.3.0
2017-03 SA#75 SP-170138 0771 1 B Replace reference to RFC 3588 by RFC 6733 14.3.0
2017-03 SA#75 SP-170138 0772 1 B Introduce clause for Diameter transport security 14.3.0
2017-03 SA#75 SP-170138 0773 1 B New Command CCF in RFC 6733 14.3.0
2017-03 SA#75 SP-170138 0774 - B Remove "encr" and 'P' flag description in AVPs tables 14.3.0
2017-03 SA#75 SP-170134 0775 - B Adding Reporting-Reason for Unused Quota timer 14.3.0
2017-06 SA#76 SP-170498 0776 1 B Implement IMS visited network identifier for S8HR 14.4.0
2017-06 SA#76 SP-170497 0777 1 F Correction on the description of AVPs 14.4.0
2017-06 SA#76 SP-170495 0780 1 B Adding of Unused-Quota-Timer to CCA 14.4.0
2017-06 SA#76 SP-170503 0782 - A Correction of ISUP Cause naming 14.4.0
2017-06 SA#76 SP-170500 0783 - B Introduce T4 Device Trigger charging 14.4.0
2017-06 SA#76 SP-170500 0784 - B Introduce MSISDN-less SMS MO via T4 charging 14.4.0
2017-06 SA#76 SP-170514 0785 1 F Correction of IMEI and IMEISV definition 14.4.0
2017-06 SA#76 SP-170497 0786 1 B Addition of the AVPs for ProSe Discovery and Communication 14.4.0
2017-06 SA#76 SP-170506 0787 1 B Introduction of FE Identifier List AVP 14.4.0
2017-09 SA#77 SP-170653 0788 1 F Clarification on Envelope reporting 14.5.0
2017-09 SA#77 SP-170650 0789 1 B Charging enhancement for eFMSS 15.0.0
2018-01 SA#78 SP-171005 0792 - A Correction where RAN-NAS-Release-Cause is defined as a 15.1.0
squence
2018-01 SA#78 SP-170965 0793 - C PoC-Server-Role AVP extension for OMA CPM Charging 15.1.0
2018-01 SA#78 SP-170966 0794 1 B EPC QoS update to support NR as a secondary RAT 15.1.0
2018-03 SA#79 SP-180068 0796 1 B Add Diameter AVP for charging of WLAN-based ProSe direct 15.2.0
discovery
2018-03 SA#79 SP-180062 0798 1 B Support for secondary RAT reporting from RAN 15.2.0
2018-06 SA#80 SP-180430 0799 2 B Introduce the NAPS API Charging 15.3.0
2018-06 SA#80 SP-180427 0800 1 B Enhance location information in trusted and untrusted WLAN 15.3.0
2018-06 SA#80 SP-180429 0801 - F Correction Access-Network-Info-Change only applicable for Rf 15.3.0
2018-06 SA#80 SP-180432 0803 1 B Adding General information for Diameter Overload Control 15.3.0
2018-06 SA#80 SP-180426 0804 1 B Introduce IMS over 5GS 15.3.0
2018-06 SA#80 SP-180428 0805 1 B Introduce Supported Feature mechanism 15.3.0
2018-06 SA#80 SP-180428 0806 1 B Introduce Supported Feature mechanism AVPs 15.3.0
2018-06 SA#80 SP-180428 0807 - B Introduce Supported Features for PS and ProSe 15.3.0
2018-06 SA#80 SP-180427 0808 1 B Enhance UE location description for IMS charging when over 15.3.0
WLAN
2018-09 SA#81 SP-180834 0809 - F Update the value of secondary RAT type 15.4.0

3GPP
Release 15 218 3GPP TS 32.299 V15.4.0 (2018-09)

2018-09 SA#81 SP-180834 0810 1 F Add 3GPP-Charging-ID to RAN Secondary RAT Usage Report 15.4.0
2018-09 SA#81 SP-180835 0811 1 B Introduction of reporting and reacting overload handling 15.4.0
2018-09 SA#81 SP-180835 0812 2 B Introduction of AVP for Overload Control 15.4.0
2018-09 SA#81 SP-180835 0813 1 B Introduction of overload AVP description 15.4.0

3GPP