Compliance Tables

5 Compliance Tables

Overview

Introduction

This chapter identifies the level of compliance of DCA to Internet Engineering Task Force (IETF) specifications RFC 6733 and RFC 4006, and 3GPP TS 32.299 V10.4.

Compliance to RFC 6733

Introduction

This topic details the compliance of DCA with RFC 6733.

For more information about the compliance levels and notes referred to in the compliance tables, see Compliance Levels and Considerations .

Introduction - Section 1

This table lists the compliances for section 1.

Section	Section Heading	Compliance Level	Comment
1	Introduction	N/A

Protocol Overview - Section 2

This table lists the compliances for section 2.

Section	Section Heading	Compliance Level	Comment
2	Protocol Overview	N/A
2.1	Transport	Fully compliant TCP + SCTP supported	TCP is selected by default
2.2	Security	Partially compliant IPSec through g/w function
2.3	Application Compliance	Fully compliant
2.4	Application Identification	Fully compliant
2.5	Connection Management	Partially compliant	Credit-Control clients (or next hop peers) must establish connection to DCA. DCA does not establish outbound connections. Inbound connections are established and added to pool for use by Diameter sessions. Number of connections per realm is configurable.
2.6	Peers	N/A	A static list of permissible peers is configurable.
2.7	Realm Based Routing	Fully compliant	Responses will be returned to the same realm through the Peer from which the request was received.
2.8	Role of agents	N/A
2.9	Path Authentication	N/A

Headers - Section 3

This table lists the compliances for section 3.

Section	Section Heading	Compliance Level	Comment
3	Headers	N/A
3.1	Command Codes	Partially compliant	CER, CEA, DWR, DWA, DPR, DPA, ASR, ASA, RAA, RAR supported.
3.2	ABNF Specification	Fully compliant
3.3	Naming Conventions	Fully compliant

Diameter AVPs - Section 4

This table lists the compliances for section 4.

Section	Section Heading	Compliance Level	Comment
4	Diameter AVPs	N/A
4.1	AVP Header	Fully compliant
4.2	Basic AVP Data Formats	Fully compliant for all basic types except float32 and float64. Partially compliant for float32 and float64. Float32 and Float64 treated as OctetString.
4.3	Derived AVP Data Formats	Fully compliant	No specific AVPs are defined by default.
4.4	Grouped AVP Values	Fully compliant
4.5	Diameter Base Protocol AVPs	Fully compliant	Support for all AVPs needed for compliance to section 3.1

Diameter AVPs - Section 4

This table lists the compliances for section 5.

Section	Section Heading	Compliance Level
5	Diameter Peers	N/A
5.1	Peer Connections	Fully compliant
5.2	Peer discovery	Non compliant
5.3	Capability Exchange	Fully compliant
5.4	Disconnecting Peer Connections	Fully compliant
5.5	Transport Failure	Fully compliant
5.6	Peer State Machine	Partially compliant

Diameter Message Processing - Section 6

This table lists the compliances for section 6.

Section	Section Heading	Compliance Level	Comment
6	Diameter Message Processing
6.1	Request Routing	Fully compliant	Please note that proxy and forward are not supported
6.2	Diameter Answer Processing	Fully compliant
6.3	Origin-Host AVP	Fully compliant
6.4	Origin- Realm AVP	Fully compliant
6.5	Destination-Host AVP	Fully compliant
6.6	Destination- Realm AVP	Fully compliant
6.7	Routing AVPs	Fully compliant
6.8	Auth-Application-Id AVP	Fully compliant	Will be 4 for Credit-Control
6.9	Acct-Application-Id AVP	Fully compliant	Not used for Credit-Control
6.10	Inband-Security ID AVP	Fully compliant
6.11	Vendor Specific Application-Id AVP	Fully compliant	No variable specific AVPs are defined today. See Section 9 for additional details.
6.12	Redirect-Host AVP	Non compliant	No explicit routing supported.
6.13	Redirect-Host-Usage AVP	Non compliant
6.14	Redirect-Max-Cache-Time AVP	Non compliant

Error Handling - Section 7

This table lists the compliances for section 7.

Section	Section Heading	Compliance Level
7	Error Handling
7.1	Result-Code AVP	Fully compliant
7.2	Error Bit	Fully compliant
7.3	Error-Message ACP	Fully compliant
7.4	Error-Reporting-Host AVP	Fully compliant
7.5	Failed-AVP AVP	Fully compliant
7.6	Experimental Result ACP	Fully compliant
7.7	Experimental Result Code AVP	Fully compliant

Diameter User Sessions - Section 8

This table lists the compliances for section 8.

Section	Section Heading	Compliance Level	Comment
8	Diameter User Sessions
8.1	Authorization Session State Machine	Non Complaint
8.2	Accounting Session State Machine	Partially compliant	Implements only the server side of the state machine
8.3	Server-Initiated Re-Auth	Fully compliant
8.4	Session Termination	Not applicable	Not used by DCA for server-side Credit-Control
8.5	Abort Session	Fully compliant
8.6	Inferring Session Termination from Origin-State-Id	Non compliant
8.7	Auth-Request-Type AVP	Non compliant
8.8	Session-Id AVP	Fully compliant
8.9	Authorization-Lifetime AVP	Non compliant
8.10	Auth-Grace-Period AVP	Non compliant
8.11	Auth-Session-State AVP	Non compliant
8.12	Re-Auth-Request-Type AVP	Non compliant
8.13	Session Timeout AVP	Fully compliant
8.14	User Name AVP	Fully compliant
8.15	Termination Cause	Fully compliant
8.16	Origin State ID AVP	Fully compliant	`
8.17	Session Binding AVP	Non compliant
8.18	Session-Server-Failover AVP	Non compliant
8.19	Multi-Round-Time-Out AVP	Non compliant
8.20	Class AVP	Non compliant
8.21	Event Timestamp AVP	Fully compliant

Accounting - Section 9

This table lists the compliances for section 9.

Section	Section Heading	Compliance Level	Comment
9	Accounting
9.1	Server Directed Model	N/A - Offline.	See Note NC-1. Not applicable to DCA for offline charging. For online charging.
9.2	Protocol Messages	N/A - Offline.	See Note NC-1. Not applicable to DCA for offline charging. For online charging. No IP compression is supported at this time. Support for negotiation is however provided.
9.3	Application document requirements	N/A - Offline.	See Note NC-1. Not applicable to DCA for offline charging. For online charging. See Credit Control Application defined in RFC 4006.
9.4	Fault Resilience	N/A - Offline.	See Note NC-1. Not applicable to DCA for offline charging. For online charging. Please note that only the server side is implemented.
9.5	Accounting Records	N/A - Offline	See Note NC-1. Not applicable for Credit-Control or online charging.
9.6	Correlation of Accounting Records	N/A - Offline.	See Note NC-1. Not applicable for Credit-Control or online charging.
9.7	Accounting Command-Codes	N/A - Offline.	See Note NC-1. Not applicable for Credit-Control or online charging.
9.8	Accounting AVPs	N/A - Offline.	See Note NC-1. Not applicable for Credit-Control or online charging.

AVP Occurrence Table - Section 10

This table lists the compliances for section 10.

Section	Section Heading	Compliance Level	Comment
10	AVP Occurrence Table	Partial compliant	As detailed elsewhere in this document and as needed for CER, CEA, DWR, DWA, DPR, DPA, RAR, RAA.

IANA Considerations - Section 11

This table lists the compliances for section 11.

Section	Section Heading	Compliance Level	Comment
11	IANA Considerations
11.1	AVP Header	Fully compliant
11.2	Diameter Header	Fully compliant
11.3	AVP Values	Fully compliant	As detailed elsewhere in this document and as needed for CER, CEA, DWR, DWA, DPR, DPA, RAR, RAA. Please note that unused AVPs are ignored by the client implementation.
11.4	Diameter TCP/SCTP Port Numbers	Fully compliant
11.5	SCTP Payload Protocol Identifiers	Fully compliant
11.6	NAPR Service Fields	Fully compliant	This information is updated when the client package is installed

Diameter Protocol Related Configurable Parameters - Section 12

This table lists the compliances for section 12.

Section	Section Heading	Compliance Level	Comment
12	Diameter Protocol Related Configurable Parameters	Partial compliant	Statically configured peers are supported.

Security Considerations - Section 13

This table lists the compliances for section 13.

Section	Section Heading	Compliance Level	Comment
13	Security Considerations	Partially compliant	Note: Use of network provided IPSec may be used in deployments. TLS is not supported. End-to-End security is not supported.

Compliance to RFC 4006

Introduction

This topic details the compliance of DCA with RFC 4006.

For more information about the compliance levels and notes referred to in the compliance tables, see Compliance Levels and Considerations .

Introduction - Section 1

This table lists the compliances for sections 4.2 and 4.3 of the "Programmer’s Guide - Service Charging Based on Diameter Charging Control Node 5.

Section	Section Heading	Compliance Level	Comment
4.2.1	Messages	Fully compliant
4.2.2	Diameter Base Protocol AVPs	Partially compliant	Refer to Draft 8 compliance above.
4.2.3	Defined Application Specific AVPs	Fully compliant	Values may be set according to configuration.
4.2.4	Description of Application Specific AVPs	Fully compliant	Values may be set according to configuration.
4.3.1	Service Charging Types	Fully compliant
4.3.2	Service Charging Methods	Fully compliant
4.3.3	List of Service Operations with Scenarios	Fully compliant

Architecture Model - Section 2

This table lists the compliances for section 2.

Section	Section Heading	Compliance Level	Comment
2	Architecture Model	Partial compliant	Authentication and Authorization messages are not used.

Credit-Control Messages - Section 3

This table lists the compliances for section 3.

Section	Section Heading	Compliance Level	Comment
3	Credit-Control Messages	Fully compliant

Credit-Control Application Overview - Section 4

This table lists the compliances for section 4.

Section	Section Heading	Compliance Level	Comment
4	Credit-Control Application Overview
4.1	Service-Specific Rating Input and Interoperability	Fully compliant	Details of specific AVP implementation is given later in this document.

Session Based Credit-Control - Section 5

This table lists the compliances for section 5.

Section	Section Heading	Compliance Level	Comment
5	Session Based Credit-Control
5.1.1	Basic Tariff-Time Change Support	Non compliant
5.1.2	Credit Control for Multiple Services within a Sub Session	Partially compliant	G-S-U-Pool-Reference is not supported. See also notes on Service-Identifier AVP.
5.2	First Interrogation	Fully compliant
5.3	Intermediate Interrogation	Fully compliant
5.4	Final Interrogation	Fully compliant
5.5	Server-Initiated Credit Re-Authorization	Partially Compliant. DCA supports RAR at all (sub)sessions granularity
5.6	Graceful Service Termination	Partially compliant	Graceful service termination with "Redirect Action" is supported.
5.7	Failure Procedures	Fully compliant	Managed through BFT in control plans.

One Time Event - Section 6

This table lists the compliances for section 6.

Section	Section Heading	Compliance Level
6	One Time Event
6.1	Service Price Enquiry	Fully compliant
6.2	Balance Check	Fully compliant
6.3	Direct Debit	Fully compliant
6.4	Refund	Fully compliant
6.5	Failure Procedure	Fully compliant

Credit-Control State Machine - Section 7

This table lists the compliances for section 7.

Section	Section Heading	Compliance Level	Comment
7	Credit-Control State Machine	Fully compliant	Server side only is implemented.

Credit-Control AVPs - Section 8

This table lists the compliances for section 8.

Note In the table below, where an AVP is labeled as "Non compliant", DCA has the ability to utilize the DCA AvpMapping Configuration and ACS to possibly enable partial or limited compliance. The DCA AvpMapping Configuration combined with the features provided by ACS and the ACS Control Plan together make up a powerful toolset for service design and permit further customization beyond the default capabilities provided by DCA.

Section	Section Heading	Compliance Level	Comment
8	Credit-Control AVPs
8.1	CC-Correlation-ID AVP	Fully compliant	Ignored unless mapped to an IDP extension by the AVP mappings in eserv.config.
8.2	CC-Request-Number AVP	Fully compliant	Implemented as per suggestion in RFC 4006
8.3	CC-Request-Type AVP	Fully compliant
8.4	CC-Session-Failover AVP	Fully compliant	Not set, which according to RFC is equivalent to AVP set to FAILOVER-NOT-SUPPORTED
8.5	CC-Sub-Session-Id AVP	Non compliant
8.6	Check-Balance-Result AVP	Fully compliant
8.7	Cost-Information AVP	Fully compliant	For Request-Action type PRICE_ENQUIRY, success case, this comes from the value of extension 603 in the INAP Connect. Otherwise, not set.
8.8	Unit Value	Fully compliant
8.9	Exponent AVP	Fully compliant
8.10	Value Digits AVP	Fully compliant
8.11	Currency-Code AVP	Fully compliant
8.12	Cost-Unit AVP	Fully compliant
8.13	Credit-Control AVP	Fully compliant
8.14	Credit-Control-Failure-Handling AVP	Fully compliant
8.15	Direct-Debit-Failure-Handling	Fully compliant
8.16	Multiple-Services-Credit-Control AVP	Partially compliant	G-S-U-Pool-Reference is not supported.
8.17	Granted-Service-Unit AVP	Fully compliant	Multiple unit types are fully supported, for Basic Credit Control as well as Multiple Services Credit Control. In the case of Multiple Services Credit Control, one or more unit types are permitted per Multiple-Services-Credit-Control AVP.
8.18	Requested-Service-Unit AVP	Fully compliant	Multiple unit types are fully supported, for Basic Credit Control as well as Multiple Services Credit Control. In the case of Multiple Services Credit Control, one or more unit types are permitted per Multiple-Services-Credit-Control AVP.
8.19	Used-Service-Unit AVP	Fully compliant	Multiple unit types are fully supported, for Basic Credit Control as well as Multiple Services Credit Control. In the case of Multiple Services Credit Control, one or more unit types are permitted per Multiple-Services-Credit-Control AVP.
8.20	Tariff-Time-Change AVP	Fully compliant
8.21	CC-Time AVP	Fully compliant
8.22	CC-Money AVP	Fully compliant
8.23	CC-Total-Octets AVP	Fully compliant
8.24	CC-Input-Octets ACP	Fully compliant
8.25	CC-Output-Octets ACP	Fully compliant
8.26	CC-Service-Specific-Units AVP	Fully compliant
8.27	Tariff-Change-Usage AVP	Fully compliant
8.28	Service-Identifier AVP	Fully compliant	For multiple services, DCA allows for one or more service-identifier per Multiple-Services-Credit-Control (MSCC) AVP. Where both Service-Identifier and Rating-Group have been specified within the same MSCC AVP, the Service-Identifier will take precedence. If multiple Service-Identifier AVPs are provided per Multiple-Services-Credit-Control AVP, then DCA may be configured to either: Only charge for the first Service-Identifier encountered. This is based on the following statement in RFC 4006: "Note that each instance of this AVP carries units related to one or more services or related to a single rating group." Or create a separate charging sub-session, for each session identifier supplied. In this case each charging sub-session will be reported back in a separate Multiple-Services-Credit-Control AVP.
8.29	Rating-Group AVP	Fully compliant	For multiple services, DCA allows for multiple MSCC AVPs with each MSCC containing a different RatingGroup. If more than one Multiple-Services-Credit-Control AVP are received (each containing a distinct Rating Group), then DCA will create a separate charging sub-session, for each Rating Group supplied. In this case each charging sub-session will be reported back in a separate Multiple-Services-Credit-Control AVP.
8.30	G-S-U Pool Reference AVP	Non compliant
8.31	G-S-U Pool Identifier AVP	Non compliant
8.32	CC-Unit-Type AVP	Fully compliant
8.33	Validity-Time AVP	Fully compliant
8.34	Final-Unit-Indication AVP	Fully compliant
8.35	Final-Unit-Action AVP	Fully compliant
8.36	Restriction-Filter-Rule AVP	Non compliant	These rules are defined using the Oracle Control Plan Editor.
8.37	Redirect-Server AVP	Fully compliant	Please note that SIP E.164 addresses must be used for voice and SMS sessions
8.38	Redirect-Address-Type AVP	Fully compliant
8.39	Redirect-Server-Address AVP	Fully compliant
8.40	Multiple-Services-Indicator AVP	Fully compliant
8.41	Requested-Action AVP	Fully compliant
8.42	Service-Context-Id AVP	Fully compliant
8.43	Service-Parameter-Info AVP	Fully compliant	May be mapped in configuration to indicate supplementary rating information.
8.44	Service-Parameter-Type AVP	Fully compliant	May be mapped in configuration to indicate supplementary rating information.
8.45	Service-Parameter-Value AVP	Fully compliant	May be mapped in configuration to indicate supplementary rating information.
8.46	Subscription-Id AVP	Fully compliant
8.47	Subscription-Id-Type AVP	Fully compliant	E164 and SIP URI are used today.
8.48	Subscription-Id-Data AVP	Fully compliant
8.49	User-Equipment-Info AVP	Compliant by Configuration	See Note C-1.
8.50	User-Equipment-Info-Type AVP	Non compliant	Ignored unless mapped to an IDP extension by the AVP mappings in eserv.config.
8.51	User-Equipment-Info-Data AVP	Non compliant

Result Code AVP Values - Section 9

This table lists the compliances for section 9.

Section	Section Heading	Compliance Level
9	Result Code AVP Values
9.1	Transient Failures	Fully compliant
9.2	Permanent Failures	Fully compliant

AVP Occurrence Table - Section 10

This table lists the compliances for section 10.

Section	Section Heading	Compliance Level
10	AVP Occurrence Table
10.1	Credit-Control AVP Table	Fully compliant
10.2	Re-Auth-Request/Answer Table AVP	Non-compliant. These AVPs provide a greater RAR granularity than DCA currently supports.

RADIUS/Diameter Credit-Control Interworking Model - Section 11

This table lists the compliances for section 11.

Section	Section Heading	Compliance Level	Comment
11	RADIUS/Diameter Credit-Control Interworking Model	Fully compliant

IANA Considerations - Section 12

This table lists the compliances for section 12.

Section	Section Heading	Compliance Level	Comment
12	IANA Considerations	Fully compliant

Credit-Control Application Related Parameters - Section 13

This table lists the compliances for section 13.

Section	Section Heading	Compliance Level	Comment
13	Credit-Control Application Related Parameters	Fully compliant	Tcc session supervision timer is supported timers are supported.

Security Considerations - Section 14

This table lists the compliances for section 14.

Section	Section Heading	Compliance Level	Comment
14	Security Considerations	Partially compliant	Use of network provided IPSec may be used in deployments.
14.1	Direct Connection with Redirect	Non compliant	Statically configured peers are supported.

Compliance to 3GPP TS 32.299 V10.4

Introduction

This topic details the compliance of DCA with 3GPP TS 32.299 V10.4.

For more information about the compliance levels and notes referred to in the compliance tables, see Compliance Levels and Considerations .

3GPP TS 32.299 V11.3.0 compliance

Compliance is specified for 3GPP TS 32.299 V10.4 specification with the following highlighted:

[V11.3] - Where this mark appears, the specific section only applies to V11.3 of the specification.

Section 5

DCA is an on-line charging application. All references and text relating to off-line charging are not applicable and are marked as "N/A - Offline" in the tables below.

This table lists the compliances for Section 5.

Section	Section Heading	Compliance Level	Comment
5	3GPP charging applications requirements	Fully compliant for On-line Charging only
5.1	Offline Charging Scenarios	N/A - Offline	Offline charging not applicable to DCA Note NC-1
5.2	Online Charging scenarios
5.2.1	Basic principles
5.2.2	Charging Scenarios
5.2.2.1	Immediate Event Charging
5.2.2.1.1	Decentralized Unit Determination and Centralized Rating	Fully compliant	Debit Units Request will be implemented in Credit-Control-Request (CCR) and Debit Units Response in Credit-Control-Answer (CCA).
5.2.2.1.2	Centralized Unit Determination and Centralized Rating	Fully compliant	As above
5.2.2.1.3	Decentralized Unit Determination and Decentralized Rating	Fully compliant	As above
5.2.2.1.4	Further Options	N/A	Service delivery options are not determined by DCA.
5.2.2.2	Event charging with Reservation
5.2.2.2.1	Decentralized Unit Determination and Centralized Rating	Fully compliant	Debit Units Request will be implemented in Credit-Control-Request (CCR) and Debit Units Response in Credit-Control-Answer (CCA).
5.2.2.2.2	Centralized Unit Determination and Centralized Rating	Fully compliant
5.2.2.2.3	Decentralized Unit Determination and Decentralized Rating	Fully compliant
5.2.2.3	Session charging with Reservation
5.2.2.3.1	Decentralized Unit Determination and Centralized Rating	Fully compliant	Debit Units Request will be implemented in Credit-Control-Request (CCR) and Debit Units Response in Credit-Control-Answer (CCA).
5.2.2.3.2	Centralized Unit Determination and Centralized Rating	Fully compliant
5.2.2.3.3	Decentralized Unit Determination and Decentralized Rating	Fully compliant
5.2.3	Basic Operations	Compliant using CCR/CCR messages. See Section Credit Control Request and Response AVPs for details.	DCA 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.
5.3	Other requirements
5.3.1	Re-authorization	Compliant by Configuration	Compliant by Configuration with limitations. Mid-Session tariff changes may not be possible. See Note C-3 and Note C-1 for limitations.
5.3.2	Threshold based re-authorization triggers	Non compliant
5.3.3	Termination action	Compliant
5.3.4	Account Expiration	Compliant by Configuration	Compliant by Configuration with limitations. May require use of other Convergent Charging Controller products and additional set up and signaling or traffic handling requirements. Also see Note C-3 and Note C-1 for other limitations

Section 6

This table lists the compliances for Section 6.

Section	Section Heading	Compliance Level	Comment
6	3GPP Charging Applications – Protocol Aspects	-
6.1	Basic Principles for Diameter Offline Charging	N/A - Offline	Offline charging not applicable for DCA Note NC-1
6.1.1	Event based charging	N/A - Offline	Not Applicable, For Offline Charging
6.1.2	Session based charging	N/A - Offline	Not Applicable, For Offline Charging
6.1.3	Offline charging error cases - Diameter procedures	N/A - Offline	Not Applicable, For Offline Charging
6.1.3.1	CDF connection failure	N/A - Offline	Not Applicable, For Offline Charging
6.1.3.2	No reply from CDF	N/A - Offline	Not Applicable, For Offline Charging
6.1.3.3	Duplicate detection	N/A - Offline	Not Applicable, For Offline Charging
6.1.3.4	CDF detected failure
6.2	Message Contents for Offline Charging	-
6.2.1	Summary of Offline Charging Message Formats	N/A - Offline	Not Applicable, For Offline Charging
6.2.1.1	General	N/A - Offline	Not Applicable, For Offline Charging
6.2.1.2	Structure for the Accounting Message Formats	N/A - Offline	Not Applicable, For Offline Charging
6.2.2	Accounting-Request Message	N/A - Offline	Not Applicable, For Offline Charging
6.2.3	Accounting-Answer Message	N/A - Offline	Not Applicable, For Offline Charging
6.3	Basic Principles for Diameter Online charging	-
6.3.1	Online Specific Credit Control Application Requirements	Fully compliant
6.3.2	Diameter Description on the Ro reference point	-
6.3.2.1	Basic Principles	N/A
6.3.3	Immediate Event Charging (IEC)	Fully compliant	DCA supports Event Request with DirectDebit requested action. DCA also supports the Refund Account, Check Balance, Price Enquiry requested actions (RFC 4006).
6.3.4	Event Charging with Unit Reservation (ECUR)	Fully compliant	DCA supports Initial Request followed by Terminate Request CCR/CCA messages.
6.3.5	Session Charging with Unit Reservation (SCUR)	Fully compliant	DCA supports Initial Request followed by one or more Update Requests CCR/CCA and a Terminate Request CCR/CCA.
6.3.6	Error Cases and Scenarios	Fully compliant	DCA always sends TERMINATE Credit-Control-Failure-Handling AVP to the network element.
6.3.6.1	Duplicate Detection	Fully compliant
6.3.6.2	Reserve Units and Debit Units Operation Failure	Fully compliant. For compliance to RFC 6733 and RFC 4006, see sections above titled: Compliance to RFC 6733 Compliance to RFC 4006
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	Non compliant
6.3.7.2	Support of Tariff Changes using Validity Time AVP	Partially compliant	When the validity-time is up (as indicated by the AVP), the client must come back to ask for more. At this point the rating engine (VWS) can choose to grant more quota which is charged at a different new rate.
6.3.8	Support of Re-authorisation	Fully compliant
6.3.9	Support of Failure Handling	Partially compliant	CTF aspects are not applicable. DCA is fully compliant for the OCF aspects for the TERMINATE Credit Control Failure Handling AVP; DCA always send the TERMINATE Credit Control Failure Handling AVP in the CCA. Other Credit Control Failure Handling AVP values are not used.
6.3.10	Support of Failover	Non compliant	DCA does not support mid-session failover within a realm, as described in RFC 4006, including the use of the CC-Session-Failover AVP. Failover of newly commenced Credit Control sessions to different SLCs is permitted.
6.3.11	Credit Pooling	Non compliant
6.4	Message formats for Online Charging	-
6.4.1	Summary of Online Charging Message Formats	-
6.4.1.1	General	N/A
6.4.1.2	Structure for the Credit Control Message Formats	N/A
6.4.2	Credit-Control-Request Message	Fully compliant	DCA fully complies to the CCR message format structure. However, not all optional AVPs may be supported. See section titled Credit Control Request and Response AVPs .
6.4.3	Credit-Control-Answer Message	Fully compliant	DCA fully complies to the CCA message format structure. However, not all optional AVPs may be supported. See section titled Credit Control Request and Response AVPs .
6.4.4	Re-Auth-Request Message	Non compliant	DCA fully complies to the RAR message format structure. However, not all optional AVPs may be supported. See section titled Re-Auth Request and Response AVPs in Chapter 4.
6.4.5	Re-Auth-Answer Message	Non compliant	DCA fully complies to the RAA message format structure. However, not all optional AVPs may be supported. See section titled Re-Auth Request and Response AVPs in Chapter 4.
6.4.6	Capabilities-Exchange-Request Message	Fully compliant	DCA fully complies with the CER message format structure. See section titled Capabilities Exchange Messages for further details.
6.4.7	Capabilities-Exchange-Answer Message	Fully compliant	DCA fully complies with the CEA message format structure. See section titled Capabilities Exchange Messages for further details.
6.4.8	Device-Watchdog-Request Message	Fully compliant	DCA fully complies with the message format structure. See section titled Device Watchdog Messages for further details.
6.4.9	Device-Watchdog-Answer Message	Fully compliant	DCA fully complies with the message format structure. See section titled Device Watchdog Messages for further details.
6.4.10	Disconnect-Peer-Request Message	Fully compliant	DCA fully complies with the message format structure. See section titled Disconnect Peer Messages for further details.
6.4.11	Disconnect-Peer-Answer Message	Fully compliant	DCA fully complies with the message format structure. See section titled Disconnect Peer Messages for further details.
6.4.12	Abort-Session-Request Message	Fully compliant	DCA fully complies with the message format structure. See section titled Abort Session Request (ASR) for further details.
6.4.13	Abort-Session -Answer Message	Fully compliant	DCA fully complies with the message format structure. See section titled Abort Session Request (ASR) for further details.
6.5	Other procedural description of the 3GPP charging applications	-
6.5.1	Re-authorization	-
6.5.1.1	Idle timeout	Compliant by Configuration	Fully compliant without additional configuration, that is, if this AVP is not present, a locally configurable default value in the client shall be used. If DCA is configured with a Quota-Holding-Time value of zero, this indicates that this mechanism shall not be used. For non-zero configured times, compliant with Limitations. See Note C-3. If configured for a specific service, Quota-Holding-Time AVP can be statically set or mapped from ACS through a field set by the Control Plan. The timer is run on the client and DCA still relies on Requested/Granted/Used-Service-Units AVPs.
6.5.1.2	Change of charging conditions	Non compliant
6.5.1.3	Reporting quota usage	Non compliant
6.5.2	Threshold based re-authorization triggers	Fully compliant	DCA has Quota Threshold configurations which are used in MSCC.
6.5.3	Termination action	Fully compliant	DCA support "REDIRECT" Final-Units-Action AVP and redirect to a Redirect Server.
6.5.4	Quota consumption time	Non compliant	The 3GPP specification states "The server may optionally indicate...". This is optional functionality which is not implemented.
6.5.5	Service Termination	Fully compliant	The CCA Result Code is configurable. Also see section titled Abort Session Request (ASR) .
6.5.6	Envelope reporting	Non compliant
6.5.7	Combinational quota	Non compliant
6.5.8	Online control of offline charging information	Non compliant
6.6	Bindings of the operation to protocol application
6.6.1	Bindings of Charging Data Transfer to Accounting	N/A - Offline
6.6.2	Bindings of Debit / Reserve Units to Credit-Control	Fully compliant	DCA uses the DCCA shown in the table. See "Credit Control Requests " for details.

Section 7

This table lists the compliances for section 7.

Section	Section Heading	Compliance Level	Comment
7	Summary of used Attribute Value
7.1	Diameter AVPs	See 7.1 - Use Of IETF Diameter AVPs
7.2	3GPP specific AVPs	See 7.2 - 3GPP specific AVPs
7.3	3GPP2 Accesses specific AVPs	Compliant by Configuration	Note C-3, Note NC-4

7.1 - Use Of IETF Diameter AVPs

This table lists the compliances for section 7.1

AVP Name	AVP Code	ACR	ACA	CCR	CCA	Value Type	Compliance Level	Comment	Reference
Accounting-Input-Octets	363	OC	-	-	-	Unsigned64	N/A - Offline	Note NC-1	7.1.1
Accounting-Output-Octets	364	OC	-	-	-	Unsigned64	N/A - Offline	Note NC-1	7.1.3
Accounting-Realtime-Required	483	-	-	-	-	Enumerated	N/A - Offline	Note NC-1
Accounting-Record-Number	485	M	M	-	-	Unsigned32	N/A - Offline	Note NC-1
Accounting-Record-Type	480	M	M	-	-	Enumerated	N/A - Offline	Note NC-1
Accounting-Sub-Session-Id	287	-	-	-	-	Unsigned64	N/A - Offline	Note NC-1
Acct-Application-Id	259	OC	OC	-	-	Unsigned32	Compliant by Configuration	Fully compliant when used in Capabilities Negotiation. Compliant by Configuration when used as statically mapped AVP or mapped from ACS field through Control Plan.	7.1.5
Acct-Interim-Interval	85	OC	OC	-	-	Unsigned32	N/A - Offline	Note NC-1
Acct-Multi-Session-Id	50	-	-	-	-	Unsigned32	Partially compliant	Not sent but will be returned in CCA if received in CCR.
Acct-Session-Id	44	-	-	-	-	OctetString	Non compliant
Auth-Application-Id	258	-	-	M	M	Unsigned32	Fully compliant		7.1.6
AVP	*	-	-	-	-	Grouped	-
Called-Station-Id	30	OC	-	OC	-	UTF8String	Compliant by Configuration	Note C-1	7.1.7
CC-Correlation-Id	411	-	-	OC	-	OctetString	Compliant by Configuration	Note C-1, Note NC-4
CC-Input-Octets	412	-	-	OC	OC	Unsigned64	Fully compliant	Basic Credit Control and MSCC
CC-Money	413	-	-	-	-	Grouped	Fully compliant	Basic Credit Control and MSCC
CC-Output-Octets	414	-	-	OC	OC	Unsigned64	Fully compliant	Basic Credit Control and MSCC
CC-Request-Number	415	-	-	M	M	Unsigned32	Fully compliant
CC-Request-Type	416	-	-	M	M	Enumerated	Fully compliant
CC-Service-Specific-Units	417	-	-	OC	OC	Unsigned64	Fully compliant	Basic Credit Control and MSCC
CC-Session-Failover	418	-	-	-	OC	Enumerated	Non compliant
CC-Sub-Session-Id	419	-	-	-	-	Unsigned64	Fully compliant	Will be returned in CCA if received in CCR.
CC-Time	420	-	-	OC	OC	Unsigned32	Fully compliant	Basic Credit Control and MSCC
CC-Total-Octets	421	-	-	OC	OC	Unsigned64	Fully compliant	Basic Credit Control and MSCC
CC-Unit-Type	454	-	-	-	M	Enumerated	Compliant by configuration	Note C-1
Check-Balance-Result	422	-	-	-	-	Enumerated	Fully compliant	For Check Balance
Cost-Information	423	-	-	-	OC	Grouped	Fully compliant	For Price Enquiry
Cost-Unit	424	-	-	-	OC	UTF8String	Fully compliant	For Price Enquiry
Credit-Control	426	-	-	-	-	Enumerated	-
Credit-Control-Failure-Handling	427	-	-	-	OC	Enumerated	Fully compliant	Always set to TERMINATE
Currency-Code	425	-	-	-	M	Unsigned32	Fully compliant	Basic Credit Control and MSCC
Destination-Host	293	-	-	OC	-	DiamIdent	Fully compliant
Destination-Realm	283	M	-	M	-	DiamIdent	Fully compliant
Direct-Debiting-Failure-Handling	428	-	-	-	OC	Enumerated	Compliant by Configuration	Note C-3
Error-Message	281	-	-	-	-	UTF8String	Compliant by Configuration	Note C-3
Error-Reporting-Host	294	-	OC	-	-	DiamIdent	N/A - Offline	Note NC-1
Event-Timestamp	55	OC	OC	OC	-	Time	Fully compliant		7.1.8
Exponent	429	-	-	-	OC	Integer32	Fully compliant
Failed-AVP	279	-	-	-	OC	Grouped	Fully compliant
Filter-Id	11	-	-	-	OC	UTF8String	Non compliant
Final-Unit-Action	449	-	-	-	OC	Enumerated	Fully compliant	Set to TERMINATE or REDIRECT
Final-Unit-Indication	430	-	-	-	OC	Grouped	Fully compliant	Set for Final Unit Action REDIRECT
Granted-Service-Unit	431	-	-	-	OC	Grouped	Fully compliant	Basic Credit Control and MSCC
G-S-U-Pool-Identifier	453	-	-	-	OC	Unsigned32	Non compliant	Note NC-5
G-S-U-Pool-Reference	457	-	-	-	OC	Grouped	Non compliant	Note NC-5
Multiple-Services-Credit-Control	456	-	-	OC	OC	Grouped	Partially compliant	Fully compliant with the supported sub-AVPs shown below: Granted-Service-Unit Requested-Service-Unit Used-Service-Unit Service-Identifier Rating-Group Validity-Time Result-Code Time-Quota-Threshold Volume-Quota-Threshold Final-Unit-Indication Tariff-Change-Usage Quota-Holding-Time	7.1.9
								Non compliant or Partially compliant by configuration if the following AVPs can be statically set or mapped from ACS fields through the Control Plan: Unit-Quota-Threshold 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 AVP
Multiple-Services-Indicator	455	-	-	OM	-	Enumerated	Fully compliant
Origin-Host	264	M	M	M	M	DiamIdent	Fully compliant
Origin-Realm	296	M	M	M	M	DiamIdent	Fully compliant
Origin-State-Id	278	OC	OC	OC	-	Unsigned32	Fully compliant
Proxy-Info	284	OC	OC	OC	OC	Grouped	Compliant by Configuration	Note C-1, Note C-3
Proxy-Host	280	M	M	M	M	DiamIdent	Compliant by Configuration	Note C-1, Note C-3
Proxy-State	33	M	M	M	M	OctetString	Compliant by Configuration	Note C-1, Note C-3
Rating-Group	432	OC	-	OC	OC	Unsigned32	Fully compliant		7.1.10
Redirect-Address-Type	433	-	-	M	M	Enumerated	Fully compliant
Redirect-Host	292	-	-	-	OC	DiamURI	Non compliant	Note NC-5
Redirect-Host-Usage	261	-	-	-	OC	Enumerated	Non compliant	Note NC-5
Redirect-Max-Cache-Time	262	-	-	-	OC	Unsigned32	Non compliant	Note NC-5
Redirect-Server	434	-	-	-	OC	Grouped	Fully compliant
Redirect-Server-Address	435	-	-	-	M	UTF8String	Fully compliant
Requested-Action	436	-	-	OC	-	Enumerated	Fully compliant
Requested-Service-Unit	437	-	-	OC	-	Grouped	Fully compliant	Basic Credit Control and MSCC
Restriction-Filter-Rule	438	-	-	-	OC	IPFilterRule	Non compliant
Result-Code	268	-	M	-	M	Unsigned32	Fully compliant	Basic Credit Control and MSCC Additional mapping flexibility available through DCA AvpMapping Configuration	7.1.11
Route-Record	282	OC	-	OC	OC	DiamIdent	Compliant by Configuration	Note C-1, Note C-3 ACS Control Plan Modify Node
Service-Context-Id	461	OM	-	M	-	UTF8String	Fully compliant		7.1.12
Service-Identifier	439	OC	-	OC	OC	Unsigned32	Fully compliant	Basic Credit Control and MSCC	7.1.13
Service-Parameter-Info	440	-	-	-	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Service-Parameter-Type Service-Parameter-Value
Service-Parameter-Type	441	-	-	-	-	Unsigned32	Compliant by Configuration	Note C-1
Service-Parameter-Value	442	-	-	-	-	OctetString	Compliant by Configuration	Note C-1
Session-Id	263	M	M	M	M	UTF8String	Fully compliant
Subscription-Id	443	OC	-	OM	-	Grouped	Fully compliant
Subscription-Id-Data	444	M	-	M	-	UTF8String	Fully compliant
Subscription-Id-Type	450	M	-	M	-	Enumerated	Fully compliant
Tariff-Change-Usage	452	-	-	OC	-	Enumerated	Fully compliant
Tariff-Time-Change	451	-		-	OC	Time	Fully compliant
Termination-Cause	295	OC	-	-	-	Enumerated	N/A - Offline	Note NC-1
Unit-Value	445	-		-	M	Grouped	Fully compliant
Used-Service-Unit	446	-		OC	-	Grouped	Fully compliant	Basic Credit Control and MSCC	7.1.14
User-Equipment-Info	458	OC		OC	-	Grouped	Compliant by configuration	Note C-1
User-Equipment-Info-Type	459	OM		M	-	Enumerated	Compliant by Configuration	Note C-1
User-Equipment-Info-Value	460	OM		M	-	OctetString	Compliant by Configuration	Note C-1
User-Name	1	OC	OC	OC	-	UTF8String	Compliant by Configuration	Note C-1	7.1.15
Value-Digits	447	-	-	-	M	Integer64	Fully compliant
Validity-Time	448	-	-	-	OC	Unsigned32	Fully compliant
Vendor-Id	266	-	-	-	-	Unsigned32	Fully compliant		7.1.16
Vendor-Specific-Application-Id	260	-	-	-	-	Grouped	Compliant by Configuration	Inbuilt support if configured. See sub-AVPs: Vendor-Id Auth-Application-Id Acct-Application-Id

7.2 - 3GPP specific AVPs

DCA is an on-line charging application; off-line charging is not applicable.

The table below specifies the compliance level for on-line charging only.

For example:

Where an AVP is marked as both off-line and on-line, the compliance level stated is for on-line charging only.
Where an AVP is marked as only for off-line use, the AVP is marked as Non-compliant.

This table lists the compliances for section 7.2.

AVP Name	AVP Code	ACR	ACA	CCR	CCA	Value Type	Compliance Level	Comment	Reference
3GPP-Charging-Characteristics	13	X	-	X	-	refer [207]	Compliant by configuration	Note NC-5	3GPP TS 29.061 (PLMNPDN)
3GPP-Charging-Id	2	X	-	X	-	refer [207]	Compliant by configuration	Note C-1, Note NC-4	3GPP TS 29.061 (PLMNPDN)
3GPP-GGSN-MCC-MNC	9	X	-	X	-	refer [207]	Compliant by configuration	Note G-2, Note C-2	3GPP TS 29.061 (PLMNPDN)
3GPP-IMSI	1	-	-	X	-	refer [207]	Compliant by configuration	Note G-2, Note C-2	3GPP TS 29.061 (PLMNPDN) 3GPP TS 32.271 (LCS)
3GPP-IMSI-MCC-MNC	8	X	-	X	-	refer [207]	Compliant by configuration	Note G-2, Note C-2	3GPP TS 29.061 (PLMNPDN)
3GPP-MS-TimeZone	23	X	-	X	-	refer [207]	Compliant by configuration	Note C-1, Note G-2	3GPP TS 29.061 (PLMNPDN)
3GPP-NSAPI	10	X	-	X	-	refer [207]	Compliant by configuration	Note C-1, Note G-2	3GPP TS 29.061 (PLMNPDN)
3GPP-PDP-Type	3	X	-	X	-	refer [207]	Compliant by configuration	Note C-1, Note G-2	3GPP TS 29.061 (PLMNPDN)
3GPP-RAT-Type	21	X	-	X	-	refer [207]	Compliant by configuration	Note C-1, Note G-2	3GPP TS 29.061 (PLMNPDN) 3GPP TS 32.251 (PS) - Sec 6.3.2.1 3GPP TS 32.270 (MMS)
3GPP-Selection-Mode	12	X	-	X	-	refer [207]	Compliant by configuration	Note C-1, Note G-2	3GPP TS 29.061 (PLMNPDN)
3GPP-Session-Stop-Indicator	11	-	-	X	-	refer [207]	Compliant by configuration	Note C-1	3GPP TS 29.061 (PLMNPDN)
3GPP-SGSN-MCC-MNC	18	X	-	X	-	refer [207]	Compliant by configuration	Note G-2,-Note C-2	3GPP TS 29.061 (PLMNPDN)
3GPP-User-Location-Info	22	X	-	X	-	refer [207]	Compliant by configuration	Note G-2, Note C-1	3GPP TS 29.061 (PLMNPDN) 3GPP TS 32.251 (PS) - Sec 6.3.2.1 3GPP TS 32.270 (MMS)
Access-Network-Charging-Identifier-Value	503	X	-	X	-	refer [214]	N/A - Non-Ro	Note NC-2	3GPP TS 29.214 (Policy Rx)
Access-Network-Information	1263	X	-	X	-	OctetString	Compliant by configuration	Note C-1	7.2.1 3GPP TS 32.260 (IMS)
Account-Expiration	2309	-	-	-	X	Time	Compliant by configuration	Note C-1	7.2.2 3GPP TS 32.260 (IMS)
Accumulated-Cost	2052	-	-	-	X	Grouped	Compliant by configuration and dependent on sub-AVPs and external system	Note NC-3	7.2.3
Adaptations	1217	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.4 3GPP TS 32.270 (MMS)
Additional-Content-Information	1207	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Type-Number Additional-Type-Information Content-Size	7.2.5
Additional-Type-Information	1205	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.6
Address-Data	897	-	-	X	-	UTF8String	Compliant by configuration	Note C-2	7.2.7
Address-Domain	898	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Domain-Name 3GPP-IMSI-MCC-MNC	7.2.8
Addressee-Type	1208	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.10
Address-Type	899	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.9
AF-Charging-Identifier	505	-	-	X	-	refer [214]	N/A - Non-Ro	Note NC-2	3GPP TS 29.214 (Policy Rx)
AF-Correlation-Information	1276	X	-	X	-	Grouped	N/A - Non-Ro	Note NC-2 Rx/Gx Interface See sub-AVPs: AF-Charging-Identifier Flows	7.2.11 3GPP TS 29.214 (Policy-Rx) and TS 29.212 (Policy-Gx)
Allocation-Retention-Priority	1034	X	-	X	-	refer [215]	N/A - Non-Ro	Note NC-2	3GPP TS 29.212 (Policy-Gx)
Alternate-Charged-Party-Address	1280	X	-	-	-	UTF8string	N/A - Offline	Note NC-1	7.2.12 3GPP TS 32.260 (IMS)
AoC-Cost-Information	2053	-	-	X	X	Grouped	Compliant by configuration and dependent on external system	Note NC-3	7.2.13 3GPP TS 32.280 (AoC)
AoC-Format	2310	-	-	X	-	Enumerated	Compliant by configuration and dependent on external system	Note NC-3	7.2.14 3GPP TS 32.280 (AoC)
AoC-Information	2054	-	-	-	X	Grouped	Compliant by configuration and dependent on sub-AVPs and external system	Note NC-3	7.2.15 3GPP TS 32.280 (AoC)
AoC-Request-Type	2055	-	-	X	-	Enumerated	Compliant by configuration and dependent on external system	Note NC-3	7.2.16 3GPP TS 32.280 (AoC)
AoC-Service	2311	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs and external system	Note NC-3	7.2.17 3GPP TS 32.280 (AoC)
AoC-Service-Obligatory-Type	2312	-	-	X	-	Enumerated	Compliant by configuration and dependent on external system	Note NC-3	7.2.18 3GPP TS 32.280 (AoC)
AoC-Service-Type	2313	-	-	X	-	Enumerated	Compliant by configuration and dependent on external system	Note NC-3	7.2.19 3GPP TS 32.280 (AoC)
AoC-Subscription-Information	2314	-	-	X	-	Grouped	Compliant by configuration and dependent on external system	Note NC-3	7.2.20 3GPP TS 32.280 (AoC)
Application-Provided-Called-Party-Address	837	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.22
Application-Server	836	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.23
Application-Server-ID	2101	X	-	X	-	refer[223]	Compliant by configuration	Note C-1, Note NC-4
Application-Service-Provider-Identity	532	X	-	-	-	refer[214]	N/A - Offline	Note NC-1 Note NC-2	3GPP TS 29.214 (Policy Rx)
Application-Server-Information	850	X	-	X	-	Grouped	Compliant by configuration and Dependent on sub-AVPs	Note C-1 See sub-AVPs: Application-Server Application-Provided-Called-Party-Address	7.2.24 3GPP TS 32.260 (IMS)
Application-Service-Type	2102	X	-	X	-	refer[223]	Compliant by configuration	Note C-1
Application-Session-ID	2103	X	-	X	-	refer[223]	Compliant by configuration	Note C-1, Note NC-4
Applic-ID	1218	-	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.21 3GPP TS 32.270 (MMS)
Associated-Party-Address	2035	X	-	X	-	UTF8String	Compliant by configuration	Note C-2	7.2.25
Associated-URI	856	X	-	X	-	UTF8String	Compliant by configuration	Note C-2	7.2.26 3GPP TS 29.061 3GPP TS 32.260 (IMS)
Authorised-QoS	849	X	-	-	-	UTF8String	N/A - Offline	Note NC-1	7.2.27
Aux-Applic-Info	1219	-	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.28 3GPP TS 32.270 (MMS)
Base-Time-Interval	1265	-	-	-	X	Unsigned32	Compliant by configuration	Note C-3	7.2.29
Bearer-Service	854	X	-	-	-	OctetString	N/A - Offline	Note NC-1	7.2.30 3GPP TS 32.260 (IMS)
Called-Asserted-Identity	1250	X	-	X	-	UTF8String	Compliant by configuration	Note C-2	7.2.31
Called-Party-Address	832	X	-	X	-	UTF8String	Compliant by configuration	Note C-2	7.2.32 3GPP TS 32.260 (IMS) 3GPP TS 32.272: (PoC)
Calling-Party-Address	831	X	-	X	-	UTF8String	Compliant by configuration	Note C-2	7.2.33 3GPP TS 32.260 (IMS)
Carrier-Select-Routing-Information	2023	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.34 3GPP TS 32.260 (IMS) / SIP
Cause-Code	861	X	-	X	-	Integer32	Compliant by configuration	Note C-1	7.2.35 3GPP TS 32.260 (IMS) 3GPP TS 32.272: (PoC)
CG-Address	846	X	-	X	-	Address	Compliant by configuration	Note C-2	7.2.36 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Change-Condition	2037	X	-	-	-	Integer32	N/A - Offline	Note NC-1	7.2.37 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Change-Time	2038	X	-	-	-	Time	N/A - Offline	Note NC-1	7.2.38
Charged-Party	857	X	-	-	-	UTF8String	N/A - Offline	Note NC-1	7.2.39
Charging-Characteristics-Selection-Mode	2066	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.39A
Charging-Rule-Base-Name	1004	X	-	X	-	refer [215]	N/A - Non-Ro	Note NC-2 (S9 or Gx/Sd Interface)	3GPP TS 32.251 (PS) - Sec 6.3.2.1 3GPP TS 29.212 (Policy-Gx)
Class-Identifier	1214	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.40
Client-Address	2018	-	-	X	-	Address	Compliant by configuration	Note C-2	7.2.41
CN-IP-Multicast-Distribution	921	X	-	-	-	refer [207]	N/A - Offline	Note NC-1
Content-Class	1220	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.42 3GPP TS 32.270 (MMS)
Content-Disposition	828	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.43 RFC 3261 3GPP TS 32.272: (PoC)
Content-ID	2116	X	-	X	-	refer[223]	Compliant by configuration	Note C-1, Note NC-4
Content-Provider-ID	2117	X	-	X	-	refer[223]	Compliant by configuration	Note C-1, Note NC-4
Content-Length	827	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1	7.2.44 RFC 3261
Content-Size	1206	-	-	X	-	Unsigned32	Compliant by configuration	Note C-1	7.2.45 RFC 3261
CSG-Access-Mode	2317	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.46A
CSG-Id	1437	X	-	X	-	refer[219]	Compliant by configuration	Note C-1
CSG-Membership-Indication	2318	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.46B
Content-Type	826	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.46 RFC 3261 3GPP TS 32.272: (PoC)
Current-Tariff	2056	-	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note C-3, Note NC-5, Note NC-7 See: Currency-Code Scale-Factor Rate-Element	7.2.47
CUG-Information	2304	X	-	X	-	OctetString	Compliant by configuration	Note C-1	7.2.48
Data-Coding-Scheme	2001	-	-	X	-	Integer32	Compliant by configuration	Note C-1	7.2.49
DCD-Information	2115	X	-	X	-	refer[223]	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Content-ID Content-provider-ID	7.2.50 OMA-DDS-Charging
Deferred-Location-Event-Type	1230	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.51 3GPP TS 32.271 (LCS)
Delivery-Report-Requested	1216	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.52 3GPP TS 32.270 (MMS)
Delivery-Status	2104	X	-	X	-	refer[223]	Compliant by configuration	Note C-1	OMA-DDS-Charging
Destination-Interface	2002	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Interface-Id Interface-Text Interface-Port Interface-Type	7.2.53
Diagnostics	2039	X	-	X	-	Integer32	Compliant by configuration	Note C-1	7.2.54 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Domain-Name	1200	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.55
DRM-Content	1221	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.56 3GPP TS 32.270 (MMS)
Dynamic-Address-Flag	2051	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.57 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Dynamic-Address-Flag-Extension	2068	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	3GPP TS 32.251 (PS) - Sec 6.3.2.1
Early-Media-Description	1272	X	-	-	-	Grouped	N/A - Offline	Note NC-1	7.2.58 3GPP TS 32.260 (IMS)
Envelope	1266	-	-	X	-	Grouped	Compliant by configuration	Note C-4	7.2.59
Envelope-End-Time	1267	-	-	X	-	Time	Compliant by configuration	Note C-4	7.2.60
Envelope-Reporting	1268	-	-	-	X	Enumerated	Compliant by configuration	Note C-4	7.2.61
Envelope-Start-Time	1269	-	-	X	-	Time	Compliant by configuration	Note C-4	7.2.62
Event	825	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.63 3GPP TS 32.260 (IMS)
Event-Charging-TimeStamp	1258	-	-	X	-	Time	Compliant by configuration	Note C-1	7.2.64
Event-Type	823	X	-	X	-	Grouped	Compliant by configuration	Note C-1 (SIP)	7.2.65 3GPP TS 32.260 (IMS)
Expires	888	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1 (SIP)	7.2.66 3GPP TS 32.260 (IMS)
File-Repair-Supported	1224	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.67 3GPP TS 32.273 (MBMS)
Flows	510	-	-	X	-	refer [214]	N/A - Non-Ro	Note NC-2	3GPP TS 29.214 (Policy Rx)
GGSN-Address	847	X	-	X	-	Address	Compliant by configuration	Note C-2	7.2.68 3GPP TS 32.273 (MBMS) 3GPP TS 32.272: (PoC)
Guaranteed-Bitrate-UL	1026	X	-	X	-	refer[215]	N/A - Non-Ro	Note NC-2	3GPP TS 29.212 (Policy-Gx)
IM-Information	2110	X	-	X	-	refer[223]	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Total-Number-Of-Messages-Sent Total-Number-Of-Messages-Exploded Number-Of-Messages-Successfully-Sent Number-Of-Messages-Successfully-Exploded	7.2.69 OMA-DDS-Charging
IMS-Application-Reference-Identifier	2601	X	-	-	-	UTF8String	N/A - Offline	Note NC-1	7.2.74A 3GPP TS 32.260 (IMS)
IMS-Charging-Identifier	841	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.75 3GPP TS 32.260 (IMS)
IMS-Communication-Service-Identifier	1281	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.76 3GPP TS 32.260 (IMS)
IMS-Information	876	X	-	X	-	Grouped	Compliant by configuration	Note C-1	7.2.77 3GPP TS 32.260 (IMS) 3GPP TS 32.272: (PoC)
IMSI-Unauthenticated-Flag	2308	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.78 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Incoming-Trunk-Group-Id	852	X	-	-	-	UTF8String	N/A - Offline	Note NC-1	7.2.79
Incremental-Cost	2062	-	-	X	X	Grouped	Compliant by configuration and dependent on external system	Note NC-3	7.2.70 3GPP TS 32.280 (AoC)
Initial-IMS-Charging-Identifier	2321	X	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.79A 3GPP TS 32.260: IMS
Interface-Id	2003	-	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.71
Interface-Port	2004	-	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.72
Interface-Text	2005	-	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.73
Interface-Type	2006	-	-	X	-	Enumerated	Compliant by configuration	Note C-1, Note NC-4	7.2.74
Inter-Operator-Identifier	838	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See: Originating-IOI Terminating-IOI	7.2.80 3GPP TS 32.260 (IMS) IETF RFC 3455 (SIP)
IP-Realm-Default-Indication	2603	X	-	-	-	Enumerated	N/A - Offline	Note NC-1	7.2.80A
LCS-Client-Dialed-By-MS	1233	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.82 3GPP TS 32.271 (LCS)
LCS-Client-External-ID	1234	-	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.83 3GPP TS 32.271 (LCS)
LCS-Client-Id	1232	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note NC-4 See sub-AVPs: LCS-Client-Type LCS-Client-External-ID LCS-Client-Dialed-By-MS LCS-Client-Name LCS-APN LCS-Requestor-ID	7.2.84 3GPP TS 32.271 (LCS)
LCS-APN	1231	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.81 3GPP TS 32.271 (LCS)
LCS-Client-Name	1235	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: LCS-Data-Coding-Scheme LCS-Name-String LCS-Format-Indicator	7.2.85 3GPP TS 32.271 (LCS)
LCS-Client-Type	1241	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.86 3GPP TS 32.271 (LCS)
LCS-Data-Coding-Scheme	1236	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.87 3GPP TS 32.271 (LCS)
LCS-Format-Indicator	1237	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.88 3GPP TS 32.271 (LCS)
LCS-Information	878	-	-	X	-	Grouped	Compliant by configuration	Note 1 See sub-AVPs: LCS-Client-ID Location-Type Location-Estimate Positioning-Data 3GPP-IMSI MSISDN	7.2.89 3GPP TS 32.271 (LCS)
LCS-Name-String	1238	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.90 3GPP TS 32.271 (LCS)
LCS-Requestor-Id	1239	-	-	X	-	Grouped	Compliant by configuration	Note C-1, Note NC-4 See sub-AVPs: LCS-Data-Coding-Scheme LCS-Requestor-ID-String (MSISDN or Logical Name)	7.2.91 3GPP TS 32.271 (LCS)
LCS-Requestor-Id-String	1240	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.92 3GPP TS 32.271 (LCS)
Local-GW-Inserted-Indication	2604	X	-	-	-	Enumerated	N/A - Offline	Note NC-1	7.2.92A (SDP)
Local-Sequence-Number	2063	X	-	-	-	Unsigned32	N/A - Offline	Note NC-1	7.2.93
Location-Estimate	1242	-	-	X	-	OctetString	Compliant by configuration	Note C-1 and using Raw Data (Note G-2)	7.2.94 3GPP TS 32.271 (LCS)
Location-Estimate-Type	1243	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.95 3GPP TS 32.271 (LCS)
Location-Type	1244	-	-	X	-	Grouped	Compliant by configuration	Note C-1 See sub-AVPs: Location-Estimate-Type Deferred-Location-Event-Type	7.2.96 3GPP TS 32.271 (LCS)
Low-Balance-Indication	2020	-	-	-	X	Enumerated	Compliant by configuration	Note C-3	7.2.97
Low-Priority-Indicator	2602	X	-	-	-	Enumerated	N/A - Offline	Note NC-1	7.2.97A 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Mandatory-Capability	604	X	-	-	-	refer [204]	N/A - Offline	Note NC-1
Max-Requested-Bandwidth-DL	515	X	-	X	-	refer [214]	N/A - Non-Ro	Note NC-2	3GPP TS 29.214 (Policy Rx)
Max-Requested-Bandwidth-UL	516	X	-	X	-	refer [214]	N/A - Non-Ro	Note NC-2	3GPP TS 29.214 (Policy Rx)
MBMS-2G-3G-Indicator	907	X	-	X	-	refer [207]	Compliant by configuration	Note C-1	3GPP TS 29.061 (PLMN«PDN) 3GPP TS 32.273 (MBMS)
MBMS GW-Address	2307	X	-	-	-	Address	N/A - Offline	Note NC-1	7.2.98
MBMS-Information	880	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: 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 CN-IP-Multicast-Distribution MBMS GW-Address	7.2.99 3GPP TS 32.273 (MBMS)
MBMS-Service-Area	903	X	-	X	-	refer [207] OctetString	Compliant by configuration	Note C-1, Note NC-6	3GPP TS 29.061 (PLMN«PDN) 3GPP TS 32.273 (MBMS)
MBMS-Service-Type	906	X	-	X	-	refer [207] Enumerated	Compliant by configuration	Note C-1	3GPP TS 29.061 (PLMN«PDN) 3GPP TS 32.273 (MBMS)
MBMS-Session-Identity	908	X	-	X	-	refer [207] OctetString	Compliant by configuration	Note C-1, Note NC-6	3GPP TS 29.061 (PLMN«PDN) 3GPP TS 32.273 (MBMS)
MBMS-User-Service-Type	1225	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.100 3GPP TS 32.273 (MBMS)
Media-Initiator-Flag	882	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.101 3GPP TS 32.272: (PoC) 3GPP TS 32.260: (IMS)
Media-Initiator-Party	1288	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.102 3GPP TS 32.272: (PoC)
Message-Body	889	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Content-Type Content-Length Content-Disposition Originator	7.2.103 3GPP TS 32.260 (IMS)
Message-Class	1213	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Class-Identifier Token-Text	7.2.104 3GPP TS 32.270 (MMS)
Message-ID	1210	-	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.105
Message-Size	1212	-	-	X	-	Unsigned32	Compliant by configuration	Note C-1	7.2.106 3GPP TS 32.270 (MMS)
Message-Type	1211	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.107 3GPP TS 32.270 (MMS)
MMBox-Storage-Requested	1248	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.109 3GPP TS 32.270 (MMS)
MM-Content-Type	1203	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Type-Number Additional-Type-Information Content-Size Additional-Content-Information	7.2.108 3GPP TS 32.270 (MMS)
MMS-Information	877	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: 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.110 3GPP TS 32.270 (MMS)
MMTel-Information	2030	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Supplementary-Service	7.2.111
MSISDN	701	-	-	X	-	refer [221]	Complaint by configuration	Note C-2	3GPP TS 29.329 (Sh I/F) 3GPP TS 32.271 (LCS)
Next-Tariff	2057			X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note NC-5, Note NC-7 See: Currency-Code Scale-Factor Rate-Element	7.2.112
Node-Functionality	862	X	-.	X	-	Enumerated	Complaint by configuration	Note C-1	7.2.113
Node-Id	2064	X	-	X	-	UTF8String	Complaint by configuration	Note C-1	7.2.114 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Number-Of-Diversions	2034	X	-	X	-	Unsigned32	Complaint by configuration	Note C-1	7.2.115
Number-Of-Messages-Sent	2019	X	-	X	-	Unsigned32	Complaint by configuration	Note C-1	7.2.116
Number-Of-Messages-Successfully-Exploded	2111	X	-	X	-	refer[223]	Compliant by configuration	Note C-1	OMA-DDS-Charging
Number-Of-Messages-Successfully-Sent	2112	X	-	X	-	refer[223]	Compliant by configuration	Note C-1	OMA-DDS-Charging
Number-Of-Participants	885	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1	7.2.117 3GPP TS 32.272: (PoC)
Number-Of-Received-Talk-Bursts	1282	X	-	-	-	Unsigned32	N/A - Offline	Note NC-1	7.2.118
Number-Of-Talk-Bursts	1283	X	-	-	-	Unsigned32	N/A - Offline	Note NC-1	7.2.119
Number-Portability-Routing-Information	2024	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.120 3GPP TS 32.260 (IMS)
Offline-Charging	1278	-	-	-	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note NC-1 See sub-AVPs: Quota-Consumption-Time Time-Quota-Mechanism Envelope-Reporting Multiple-Services-Credit-Control	7.2.121
Online-Charging-Flag	2303	X	-	-	-	Enumerated	N/A - Offline	Note NC-1	7.2.122 3GPP TS 32.260 (IMS)
Optional-Capability	605	X	-	-	-	refer [204]	N/A - Offline	Off-line Charging
Originating-IOI	839	X	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4 (SIP)	7.2.123 IETF RFC 3455 (SIP) 3GPP TS 32.260 (IMS)
Originator-SCCP-Address	2008	-	-	X	-	Address	Compliant by configuration	Note C-2	7.2.128
Originator	864	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.124
Originator-Address	886	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Address-Type Address-Data Address-Domain	7.2.125 3GPP TS 32.270 (MMS)
Originator-Received-Address	2027	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Address-Type Address-Data Address-Domain	7.2.127
Originator-Interface	2009	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Interface-Id Interface-Text Interface-Port Interface-Type	7.2.126
Outgoing-Session-Id	2320	X	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.128A 3GPP TS 32.260 (IMS)
Outgoing-Trunk-Group-Id	853	X	-	-	-	UTF8String	N/A - Offline	Off-line Charging	7.2.129
Participant-Access-Priority	1259	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.132 3GPP TS 32.272: (PoC)
Participant-Action-Type	2049	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.133
Participant-Group	1260	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Called-Party-Address Participant-Access-Priority User-Participating-Type	7.2.131 3GPP TS 32.272: (PoC)
Participants-Involved	887	X	-	X	-	UTF8String	Compliant by configuration	Note C-2	7.2.130 3GPP TS 32.272: (PoC)
PDG-Address	895	X	-	X	-	Address	Compliant by configuration	Note C-1	7.2.134
PDG-Charging-Id	896	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1, Note NC-4	7.2.135
PDN-Connection-Charging-ID	2050	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1, Note NC-4	7.2.136 3GPP TS 32.251 (PS) - Sec 6.3.2.1
PDP-Address	1227	X	-	X	-	Address	Compliant by configuration	Note C-1	7.2.137 3GPP TS 32.270 (MMS)
PDP-Context-Type	1247	X	-	X	-	Enumerated	Compliant by configuration	Note C-1, Note NC-4 Note NC-2 for Gn/Gp	7.2.138 3GPP TS 32.251 (PS) - Sec 6.3.2.1
PDP-Address-Prefix-Length	2606	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1, Note NC-2
PoC-Change-Condition	1261	X	-	-	-	Enumerated	N/A - Offline	Note NC-1	7.2.139
PoC-Change-Time	1262	X	-	-	-	Time	N/A - Offline	Note NC-1	7.2.140
PoC-Controlling-Address	858	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.141 3GPP TS 32.272: (PoC)
PoC-Event-Type	2025	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.142 3GPP TS 32.272: (PoC)
PoC-Group-Name	859	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.143 3GPP TS 32.272: (PoC)
PoC-Information	879	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: 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	7.2.144 3GPP TS 32.272: (PoC)
PoC-Server-Role	883	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.145 3GPP TS 32.272: (PoC)
PoC-Session-Id	1229	X	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.146 3GPP TS 32.272: (PoC)
PoC-Session-Initiation-type	1277	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.147 3GPP TS 32.272: (PoC)
PoC-Session-Type	884	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.148 3GPP TS 32.272: (PoC)
PoC-User-Role	1252	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: PoC-User-Role-Ids PoC-User-Role-info-Units	7.2.149 3GPP TS 32.272: (PoC)
PoC-User-Role-IDs	1253	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.150 3GPP TS 32.272: (PoC)
PoC-User-Role-info-Units	1254	X	-	X	-	Enumerated	Compliant by configuration	Note C-1 Possible values: 1. Moderator 2. Dispatcher 3. Session-Owner 4. Session-Participant	7.2.151 3GPP TS 32.272: (PoC)
Positioning-Data	1245	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.152 3GPP TS 32.271 (LCS) 3GPP TS 25.305 3GPP TS 43.059
Preferred-AoC-Currency	2315	-	-	X	-	Unsigned32	Compliant by configuration and Dependent on External System	Note NC-3	7.2.153 3GPP TS 32.280 (AoC) RFC 4006
Priority	1209	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.154
Priority-Level	1046	X	-	X	-	refer [215]	N/A - Non-Ro	Note NC-2	3GPP TS 29.212 (Policy-Gx)
PS-Append-Free-Format-Data	867	X	-	-	X	Enumerated	Compliant by configuration	Note C-3	7.2.155
PS-Free-Format-Data	866	X	-	-	X	OctetString	Compliant by configuration	Note C-3	7.2.156
PS-Furnish-Charging-Information	865	X	-	-	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-3	7.2.157 3GPP TS 32.251 (PS) - Sec 5.3.2.3, 6.3.2.1
PS-Information	874	X	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note 1, Note 5 ( TS 32.251) See sub-AVPs: User Location Info (PoC) GGSN Address (PoC)	7.2.158 3GPP TS 32.251 (PS) - Sec 6.3.2.1 3GPP TS 32.270 (MMS) 3GPP TS 32.272: (PoC) 3GPP TS 32.273 (MBMS)
QoS-Information	1016	X	-	X	-	refer [215]	N/A - Non-Ro	Note NC-2	3GPP TS 29.212 (Policy-Gx)
QoS-Class-Identifier	1028	X	-	X	-	refer [215]	N/A - Non-Ro	Note NC-2	3GPP TS 29.212 (Policy-Gx)
Quota-Consumption-Time	881	-	-	-	X	Unsigned32	Compliant by configuration if configured. If not configured, compliant (as AVP is optional and not required)	Note C-3	7.2.159
Quota-Holding-Time	871	-	-	-	X	Unsigned32	Compliant by configuration	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. Note C-3 If Dynamic Quota is enabled, then Quota-Holding-Time is taken from the appropriate Dynamic Quota set configuration. For more information, see Dynamic Quota Config section in Charging Control Services User's Guide.	7.2.160
RAI	909	X	-	X	-	refer [207] UTF8String	Compliant by configuration	Note C-1, Note NC-6	3GPP TS 29.061 (PLMN«PDN)
Rate-Element	2058	-	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note NC-3 See sub-AVPs: CC-Unit-Type Reason-Code Unit-Value Unit-Cost Unit-Quota-Threshold
Read-Reply-Report-Requested	1222	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.162 3GPP TS 32.270 (MMS)
Real-Time-Tariff-Information	2305	X	-	-	-	Grouped	N/A - Offline	Note NC-1	7.2.164 3GPP TS 32.260 (IMS)
Received-Talk-Burst-Time	1284	X	-	-	-	Unsigned32	N/A - Offline	Note NC-1	7.2.165
Received-Talk-Burst-Volume	1285	X	-	-	-	Unsigned32	N/A - Offline	Note NC-1	7.2.166
Recipient-Address	1201	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Address-Type Address-Data Address-Domain Addressee-Type	7.2.167 3GPP TS 32.270 (MMS)
Recipient-Info	2026	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Destination-Interface Recipient-Address Recipient-Received-Address Recipient-SCCP-Address SM-Protocol-ID	7.2.168
Recipient-Received-Address	2028	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Address-Type Address-Data Address-Domain	7.2.169
Recipient-SCCP-Address	2010	-	-	X	-	Address	Compliant by configuration	Note C-2	7.2.170
Refund-Information	2022	-	-	X	X	OctetString	Compliant by configuration	Note C-1, Note C-3, Note G-2.	7.2.171
Remaining-Balance	2021	-	-	-	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Unit-Value Currency-Code	7.2.172
Reply-Applic-ID	1223	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.173 3GPP TS 32.270 (MMS)
Reply-Path-Requested	2011	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.174
Reporting-Reason	872	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.175
Requested-Party-Address	1251	X	-	X	-	UTF8String	Compliant by configuration	Note C-2	7.2.176 3GPP TS 32.260 (IMS)
Required-MBMS-Bearer-Capabilities	901	X	-	X	-	refer [207] UTF8String	Compliant by configuration	Note C-1	3GPP TS 29.061 (PLMN«PDN)
Role-Of-Node	829	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.177 3GPP TS 32.260 (IMS)
Scale-Factor	2059	-	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note C-3 See sub-AVPs: Value-Digits Exponent	7.2.178
SDP-Answer-Timestamp	1275	X	-	-	-	Time	N/A - Offline	Note NC-2	7.2.179
SDP-Media-Component	843	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: SDP-Media-Name SDP-Media-Description Local-GW-Inserted-Indication IP-Realm-Default-Indication Transcoder-Inserted-Indication Media-Initiator-Flag Media-Initiator-Party Authorised-QoS 3GPP-Charging-Id Access-Network-Charging-Identifier-Value SDP-Type	7.2.180 3GPP TS 32.260 (IMS) 3GPP TS 32.272: (PoC)
SDP-Media-Description	845	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.181
SDP-Media-Name	844	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.182
SDP-Offer-Timestamp	1274	X	-	-	-	Time	N/A - Offline	Note NC-1	7.2.183
SDP-Session-Description	842	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.184 3GPP TS 32.260 (IMS) 3GPP TS 32.272: (PoC)
SDP-TimeStamps	1273	X	-	-	-	Grouped	N/A - Offline	Note NC-1	7.2.185 3GPP TS 32.260 (IMS)
SDP-Type	2036	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.186
Served-Party-IP-Address	848	X	-	-	-	Address	N/A - Offline	Note NC-1	7.2.187 3GPP TS 32.260 (IMS) 3GPP TS 32.272: (PoC)
Server-Capabilities	603	X	-	-	-	refer [204]	N/A - Offline	Note NC-1	3GPP TS 32.260 (IMS)
Server-Name	602	X	-	-	-	refer [204]	N/A - Offline	Note NC-1
Service-Data-Container	2040	X	-	-	-	Grouped	N/A - Offline	Note NC-1	7.2.189 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Service-Generic-Information	1256	X	-	X	-	Refer[223] Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Application-Server-ID Application-Service-Type Application-Session-ID Delivery-Status	7.2.191
Service-Id	855	X	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-7	7.2.190 3GPP TS 32.260 (IMS) 3GPP TS 32.271 (LCS)
Service-Information	873	X	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note L-Note C-3, Note NC-7 See sub-AVPs: Subscription-Id AoC-Information PS-Information WLAN-Information IMS-Information MMS-Information LCS-Information PoC-Information BMS-Information SMS-Information MMTel-Information Service-Generic-Information IM-Information DCD-Information	7.2.192 3GPP TS 32.270 (MMS) 3GPP TS 32.272: (PoC) 3GPP TS 32.273 (MBMS)
Service-Mode	2032	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1	7.2.193
Service-Specific-Data	863	X	-	-	-	UTF8String	N/A - Offline	Off-line Charging	7.2.194 3GPP TS 32.272: (PoC)
Service-Specific-Info	1249	X	-	-	-	Grouped	N/A - Offline	Off-line Charging	7.2.195 3GPP TS 32.260 (IMS)
Service-Specific-Type	1257	X	-	-	-	Unsigned32	N/A - Offline	Off-line Charging	7.2.196
Serving-Node-Type	2047	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.198 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Session-Priority	650	X	-	X	-	Refer [204]	N/A - Non-Ro	Note NC-2
SGSN-Address	1228	X	-	X	-	Address	Compliant by configuration	Note C-1	7.2.199
SGW-Address	2067	X	-	-	-	Address	N/A - Offline	Note NC-1	7.2.199A 3GPP TS 32.251 (PS) - Sec 6.3.2.1
SGW-Change	2065	X	-	-	-	Enumerated	N/A - Offline	Note NC-1	7.2.200 3GPP TS 32.251 (PS) - Sec 6.3.2.1
SIP-Method	824	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.201 (IMS/SIP)
SIP-Request-Timestamp-Fraction	2301	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1	7.2.203
SIP-Request-Timestamp	834	X	-	X	-	Time	Compliant by configuration	Note C-1	7.2.202
SIP-Response-Timestamp-Fraction	2302	X	-	X	-	Unsigned32	Compliant by configuration	Note C-1	7.2.205
SIP-Response-Timestamp	835	X	-	X	-	Time	Compliant by configuration	Note C-1	7.2.204
SM-Discharge-Time	2012	-	-	X	-	Time	Compliant by configuration	Note C-1	7.2.206
SM-Message-Type	2007	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.207
SM-Protocol-ID	2013	-	-	X	-	OctetString	Compliant by configuration	Note C-1	7.2.208
SMSC-Address	2017	-	-	X	-	Address	Compliant by configuration	Note C-1	7.2.214
SMS-Information	2000	-	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: 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 Recipient-Info Originator-Received-Address SM-Service-Type	7.2.211
SMS-Node	2016	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.212
SM-Service-Type	2029	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.213
SM-Status	2014	-	-	X	-	OctetString	Compliant by configuration	Note C-1, Note G-2	7.2.209
SM-User-Data-Header	2015	-	-	X	-	OctetString	Compliant by configuration	Note C-1, Note G-2	7.2.210
Sponsor-Identify	531	X	-	-	-	refer[214]	N/A - Offline	Note NC-1
Start-Time	2041	X	-	-	-	Time	N/A - Offline	Note NC-1	7.2.215 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Status	2702	X	-	-	-	Enumerated	N/A - Offline	Note NC-1	7.2.215A [V11.3]
Stop-Time	2042	X	-	-	-	Time	N/A - Offline	Note NC-1	7.2.216 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Submission-Time	1202	-	-	X	-	Time	Compliant by configuration	Note C-1	7.2.217 3GPP TS 32.270 (MMS)
Subscriber-Role	2033	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.218
Supplementary-Service	2048	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: Service-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.219
Talk-Burst-Exchange	1255	X	-	-	-	Grouped	N/A - Offline	Note NC-1	7.2.220
Talk-Burst-Time	1286	X	-	-	-	Unsigned32	N/A - Offline	Note NC-1	7.2.221
Talk-Burst-Volume	1287	X	-	-	-	Unsigned32	N/A - Offline	Note NC-1	7.2.222
Tariff-Information	2060	X	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note NC-5, Note NC-7 See sub-AVPs: Current-Tariff Tariff-Time-Change Next-Tariff	7.2.223
Tariff-XML	2306	X	-	-	-	UTF8String	N/A - Offline	Note NC-1	7.2.224
Terminal-Information	1401	X	-	X	-	refer [219]	N/A - Offline	Note C-1, Note NC-1 Offline charging (Online charging uses User-Equipment Info) Note NC-1	3GPP TS 29.272 (MME&SGSN) 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Terminating-IOI	840	X	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.225 IETF RFC 3455 (SIP) 3GPP TS 32.260 (IMS)
Time-First-Usage	2043	X	-	-	-	Time	N/A - Offline	Note NC-1	7.2.226
Time-Last-Usage	2044	X	-	-	-	Time	N/A - Offline	Note NC-1	7.2.227
Time-Quota-Mechanism	1270	-	-	-	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-3 See sub-AVPs: Time-Quota-Type Base-Time-Interval	7.2.228
Time-Quota-Threshold	868	-	-	-	X	Unsigned32	Fully compliant		7.2.229
Time-Quota-Type	1271	-	-	-	X	Enumerated	Compliant by configuration	Note C-3	7.2.230
Time-Stamps	833	X	-	X	-	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1 See sub-AVPs: SIP-Request-Timestamp SIP-Response-Timestamp SIP-Request-Timestamp-Fraction SIP-Response-Timestamp-Fraction	7.2.231 3GPP TS 32.260 (IMS)
Time-Usage	2045	X	-	-	-	Unsigned32	N/A - Offline	Note NC-1	7.2.232
TMGI	900	X	-	X	-	refer [207] OctetString	Compliant by configuration	Note C-1, Note G-2, Note NC-4
Token-Text	1215	-	-	X	-	UTF8String	Compliant by configuration	Note C-1	7.2.234
Total-Number-Of-Messages-Exploded	2113	X	-	X	-	refer[223]	Compliant by configuration	Note C-1	OMA-DDS-Charging
Total-Number-Of-Messages-Sent	2114	X	-	X	-	refer[223]	Compliant by configuration	Note C-1	OMA-DDS-Charging
Traffic-Data-Volumes	2046	X	-	-	-	Grouped	N/A - Offline	Note NC-1	7.2.233 3GPP TS 32.251 (PS) - Sec 6.3.2.1
Transcoder-Inserted-Indication	2605	X	-	-	-	Enumerated	N/A - Offline	Note NC-1	7.2.233A
Transit-IOI-List	2701	X	-	-	-	UTF8String	N/A - Offline	Note NC-1	7.2.233B [V11.3] 3GPP TS 32.260 (IMS)
Trigger	1264	-	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note L-Note C-3 See sub-AVP: Trigger-Type	7.2.235 3GPP TS 32.272: (PoC)
Trigger-Type	870	-	-	X	X	Enumerated	Compliant by configuration	Note C-1	7.2.236
Trunk-Group-Id	851	X	-	-	-	Grouped	N/A - Offline	Note NC-1	7.2.237 3GPP TS 32.260 (IMS)
Type-Number	1204	-	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.238
Unit-Cost	2061	-	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note C-1, Note C-3 See sub-AVPs: Value-Digits Exponent	7.2.239
Unit-Quota-Threshold	1226	-	-	-	X	Unsigned32	Compliant by configuration	Note C-3, Note C-5	7.2.240
User-CSG-Information	2319	X	-	X	X	Grouped	Compliant by configuration and dependent on sub-AVPs	Note L-1, Note C-3, Note NC-4 See sub-AVPs: CSG-Id CSG-Access-Mode CSG-Membership-Indication	7.2.240A 3GPP TS 32.251 (PS) - Sec 6.3.2.1
User-Data	606	X	-	-	-	refer [204]	N/A - Offline	Note NC-1
User-Participating-Type	1279	X	-	X	-	Enumerated	Compliant by configuration	Note C-1	7.2.241 3GPP TS 32.272: (PoC)
User–Session-Id	830	X	-	X	-	UTF8String	Compliant by configuration	Note C-1, Note NC-4	7.2.242 3GPP TS 32.260 (IMS)
VAS-Id	1102	-	-	X	-	refer [213]	N/A - Non-Ro	Note C-1, Note NC-4	3GPP TS 29.140 (MM10) 3GPP TS 32.270 (MMS)
VASP-Id	1101	-	-	X	-	refer [213]	N/A - Non-Ro	Note C-1, Note NC-4	3GPP TS 29.140 (MM10) 3GPP TS 32.270 (MMS)
Volume-Quota-Threshold	869	-	-	-	X	Unsigned32	Fully compliant	If Dynamic Quota is enabled, then Volume-Quota-Threshold is taken from the appropriate range in Dynamic Quota configuration. For more informaton, see Dynamic Quota Config section in Charging Control Services User's Guide.	7.2.243

7.2 - 3GPP specific AVPs as per TS 32.299 v14.5.0

This table lists the compliances for section 7.2 as per TS 32.299 v14.5.0.

Compliance Levels:

CBC = Compliant By Configuration
CBCDS = Compliant By Configuration and dependent on sub-AVPS
NONRO = N/A - Non-Ro

AVP Name	Compliance Level	Comment	Reference
3GPP-PS-Data-Off-Status	CBC	Note C-1	TS 32.299
Access-Availability-Change-Reason	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Access-Network-Info-Change	CBC	Note C-1	TS 32.260 (IMS)
Access-Transfer-Information	CBCDS	Note C-1	TS 32.260 (IMS)
Access-Transfer-Type	CBC	Note C-1	TS 32.260 (IMS)
Accuracy	NONRO	Note NC-2	TS 29.336 (HSS)
ADC-Rule-Base-Name	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Additional-Exception-Reports	CBC	Note C-1, Note G-2
Alternate-Charged-Party-Address	CBC	Note C-1	TS 32.260 (IMS)
Announcement-Identifier	CBC	Note C-1	TS 32.299
Announcement-Information	CBCDS	Note C-1	TS 32.299
Announcement-Order	CBC	Note C-1, Note G-2	TS 32.299
Announcing-PLMN-ID	CBC	Note C-1	TS 32.277 (ProSe)
Announcing-UE-HPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Announcing-UE-VPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
APN-Rate-Control	CBC	Note C-1	TS 32.251 (PS)
APN-Rate-Control-Downlink	CBC	Note C-1	TS 32.251 (PS)
APN-Rate-Control-Uplink	CBC	Note C-1	TS 32.251 (PS)
Application-Port-Identifier	CBC	Note C-1	TS 32.299
Application-Specific-Data	CBC	Note C-1	TS 32.277 (ProSe)
Basic-Service-Code	CBC	Note C-1	TS 32.276 (VCS)
Bearer-Capability	CBC	Note C-1	TS 32.276 (VCS)
BSSID	CBC	Note C-1	TS 32.251 (PS)
Called-Identity	CBC	Note C-1	TS 32.260 (IMS)
Called-Identity-Change	CBCDS	Note C-1	TS 32.260 (IMS)
Cellular-Network-Information	CBC	Note C-1	TS 32.260 (IMS)
Charging-Per-IP-CAN-Session-Indicator	CBC	Note C-1	TS 32.251 (PS)
CN-Operator-Selection-Entity	NONRO	Note NC-1
Communication-Failure-Information	NONRO	Note NC-2 TS 32.278 (MEC)
Coverage-Info	CBC	Note C-1	TS 32.277 (ProSe)
Coverage-Status	CBC	Note C-1	TS 32.277 (ProSe)
CP-CIoT-EPS-Optimisation-Indicator	NONRO	Note NC-2 TS 32.251 (PS)
CPDT-Information	NONRO	Note NC-2	TS 32.299
Discoveree-UE-HPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Discoveree-UE-vPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Discoverer-UE-HPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Discoverer-UE-vPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
EPDG-Address	NONRO	Note NC-2	TS 32.299
EPS-Location-Information	NONRO	Note NC-2	TS 29.272 (MME)
External-Identifier	CBC	Note C-1	TS 32.299
FE-Identifier-List	NONRO	Note NC-2	TS 24.229 (SIP)
Fixed-User-Location-Info	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Forwarding-Pending	CBC	Note C-1	TS 32.276 (VCS)
From-Address	CBC	Note C-1	TS 32.260 (IMS)
IMS-Emergency-Indicator	CBC	Note C-1	TS 32.260 (IMS)
IMS-Visited-Network-Identifier	CBC	Note C-1	TS 32.260 (IMS)
Instance-Id	CBC	Note C-1	TS 32.260 (IMS)
Inter-UE-Transfer	CBC	Note C-1	TS 32.260 (IMS)
ISUP-Cause	CBC	Note C-1	TS 32.276 (VCS)
ISUP-Cause-Diagnostics	CBC	Note C-1	TS 32.276 (VCS)
ISUP-Location	CBC	Note C-1	TS 32.276 (VCS)
ISUP-Value	CBC	Note C-1	TS 32.276 (VCS)
ISUP-Location-Number	CBC	Note C-1	TS 32.276 (VCS)
Language	CBC	Note C-1	TS 32.299
Layer-2-Group-Id	CBC	Note C-1	TS 32.277 (ProSe)
LCS-APN	CBC	Note C-1	TS 32.271 (LCS)
Location-Info	CBC	Note C-1	TS 32.277 (ProSe)
Maximum-Detection-Time	NONRO	Note NC-2	TS 29.336 (HSS)
Maximum-Number-Of-Reports	NONRO	Note NC-2	TS 29.336 (HSS)
MBMS-Charged-Party	NONRO	Note NC-2	TS 32.273 (MBMS)
MBMS-Data-Transfer-Start	NONRO	Note NC-2	TS 32.273 (MBMS)
MBMS-Data-Transfer-Stop	NONRO	Note NC-2	TS 32.273 (MBMS)
MME-Name	NONRO	Note NC-2	TS 29.173 (LCS)
MME-Number-for-MT-SMS	NONRO	Note NC-2	TS 29.272 (MME)
MME-Realm	NONRO	Note NC-2	TS 29.173 (LCS)
MMTel-SService-Type	CBC	Note C-1	TS 32.299
Monitored-HPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Monitoring-Duration	NONRO	Note NC-2	TS 29.336 (HSS)
Monitoring-Event-Config-Status	NONRO	Note NC-2	TS 29.336 (HSS)
Monitoring-Event-Configuration-Activity	NONRO	Note NC-2 TS 32.278 (MEC)
Monitoring-Event-Functionality	NONRO	Note NC-2 TS 32.278 (MEC)
Monitoring-Event-Information	NONRO	Note NC-2 TS 32.278 (MEC)
Monitoring-Event-Report-Data	NONRO	Note NC-2 TS 32.278 (MEC)
Monitoring-Event-Report-Number	NONRO	Note NC-2 TS 32.278 (MEC)
Monitoring-Type	NONRO	Note NC-2	TS 29.336 (HSS)
Monitoring-UE-HPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Monitoring-UE-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Monitoring-UE-VPLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
MONTE-Location-Type	NONRO	Note NC-2	TS 29.336 (HSS)
MSC-Address	CBC	Note C-1	TS 32.276 (VCS)
MTC-IWF-Address	CBC	Note C-1	TS 32.299
NBIFOM-Mode	NONRO	Note NC-2	TS 29.212 (Policy Gx)
NBIFOM-Support	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Neighbour-Node-Address	NONRO	Note NC-2	TS 29.658 (SIP)
Network-Call-Reference-Number	CBC	Note C-1	TS 32.276 (VCS)
NIDD-Submission	NONRO	Note NC-2	TS 32.299
NNI-Information	NONRO	Note NC-2	TS 29.658 (SIP)
NNI-Type	NONRO	Note NC-2	TS 29.658 (SIP)
Number-Of-UE-Per-Location-Configuration	NONRO	Note NC-2	TS 29.128 (MME)
Number-Of-UE-Per-Location-Report	NONRO	Note NC-2	TS 29.128 (MME)
Origin-App-Layer-User-Id	CBC	Note C-1	TS 32.277 (ProSe)
PC3-Control-Protocol-Cause	CBC	Note C-1	TS 32.277 (ProSe)
PC3-EPC-Control-Protocol-Cause	CBC	Note C-1	TS 32.277 (ProSe)
Play-Alternative	CBC	Note C-1	TS 32.299
Presence-Reporting-Area-Identifier	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Presence-Reporting-Area-Information	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Presence-Reporting-Area-Elements-List	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Presence-Reporting-Area-Status	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Priority-Indication	CBC	Note C-1	TS 32.299
Privacy-Indicator	CBC	Note C-1	TS 32.299
ProSe-Direct-Discovery-Model	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Event-Type	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Function-ID	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Function-IP-Address	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Function-PLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Functionality	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Information	CBCDS	Note C-1	TS 32.277 (ProSe)
ProSe-Range-Class	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Reason-For-Cancellation	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Request-Timestamp	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Role-Of-UE	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Target-Layer-2-ID	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-UE-ID	CBC	Note C-1	TS 32.277 (ProSe)
ProSe-Validity-Timer	CBC	Note C-1	TS 32.277 (ProSe)
Proximity-Alert-Indication	CBC	Note C-1	TS 32.277 (ProSe)
Proximity-Alert-Timestamp	CBC	Note C-1	TS 32.277 (ProSe)
Proximity-Cancellation-Timestamp	CBC	Note C-1	TS 32.277 (ProSe)
Quota-Indicator	CBC	Note C-1	TS 32.299
Radio-Frequency	CBC	Note C-1	TS 32.277 (ProSe)
Radio-Parameter-Set-Info	CBC	Note C-1	TS 32.277 (ProSe)
Radio-Parameter-Set-Values	CBC	Note C-1	TS 32.277 (ProSe)
Radio-Resources-Indicator	CBC	Note C-1	TS 32.277 (ProSe)
RAN-NAS-Release-Cause	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Rate-Control-Max-Message-Size	CBC	Note C-1	TS 32.251 (PS)
Rate-Control-Max-Rate	CBC	Note C-1	TS 32.251 (PS)
Rate-Control-Time-Unit	CBC	Note C-1	TS 32.251 (PS)
Reachability-Information	NONRO	Note NC-2	TS 29.336 (HSS)
Reason-Header	CBC	Note C-1	TS 32.260 (IMS)
Related-Change-Condition-Information	NONRO	Note NC-2	TS 32.251 (PS)
Related-Trigger	CBC	Note C-1	TS 32.299
Related-IMS-Charging-Identifier	CBC	Note C-1	TS 32.260 (IMS)
Related-IMS-Charging-Identifier-Node	CBC	Note C-1	TS 32.260 (IMS)
Relationship-Mode	NONRO	Note NC-2	TS 29.658 (SIP)
Relay-IP-address	CBC	Note C-1	TS 32.277 (ProSe)
Requested-PLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Requesting-EPUID	CBC	Note C-1	TS 32.277 (ProSe)
Requested-PLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Requestor-PLMN-Identifier	CBC	Note C-1	TS 32.277 (ProSe)
Role-Of-ProSe-Function	CBC	Note C-1	TS 32.277 (ProSe)
Route-Header-Received	NONRO	Note NC-2	TS 32.260 (IMS)
Route-Header-Transmitted	NONRO	Note NC-2	TS 32.260 (IMS)
RRC-Cause-Counter	NONRO	Note NC-2	TS 29.128 (MME)
SCEF-ID	NONRO	Note NC-2	TS 29.336 (HSS)
SCEF-Reference-ID	NONRO	Note NC-2	TS 29.336 (HSS)
SCS-Address	CBC	Note C-1	TS 32.251 (PS)
SCS-AS-Address	CBCDS	Note C-1	TS 32.251 (PS)
SCS-Realm	CBC	Note C-1	TS 32.251 (PS)
Serving-Node	CBC	Note C-1	TS 32.299
Serving-Node-Identity	NONRO	Note NC-2	TS 32.299
Serving-PLMN-Rate-Control	CBS	Note C-1	TS 29.128 (MME)
Session-Direction	NONRO	Note NC-2	TS 29.658 (SIP)
Session-Priority	CBC	Note C-1	TS 32.260 (IMS)
SGi-PtP-Tunnelling-Method	CBC	Note C-1	TS 32.251 (PS)
SM-Device-Trigger-Indicator	CBC	Note C-1	TS 32.299
SM-Device-Trigger-Information	CBCDS	Note C-1	TS 32.299
SMS-Result	CBC	Note C-1	TS 32.299
Sponsor-Identity	NONRO	Note NC-2	TS 29.214 (PCC)
SSID	CBC	Note C-1	TS 32.251 (PS)
Start-Of-Charging	CBC	Note C-1	TS 32.276 (VCS)
Status-AS-Code	NONRO	Note NC-2	TS 32.260 (IMS)
TAD-Identifier	NONRO	Note NC-2	TS 32.260 (IMS)
Target-App-Layer-User-Id	CBC	Note C-1	TS 32.277 (ProSe)
Target-IP-Address	CBC	Note C-1	TS 32.277 (ProSe)
Teleservice	CBC	Note C-1	TS 32.276 (VCS)
Time-First-Reception	CBC	Note C-1	TS 32.277 (ProSe)
Time-First-Transmission	CBC	Note C-1	TS 32.277 (ProSe)
Time-Indicator	CBC	Note C-1	TS 32.299
Time-Window	CBC	Note C-1	TS 32.277 (ProSe)
Transit-IOI-List	CBC	Note C-1	TS 32.260 (IMS)
Transmitter-Info	CBC	Note C-1	TS 32.277 (ProSe)
TWAG-Address	NONRO	Note NC-2	TS 32.251 (PS)
TWAN-User-Location-Info	CBCDS	Note C-1	TS 32.251 (PS)
UDP-Source-Port	CBC	Note C-1	TS 32.251 (PS)
UE-Local-IP-Address	CBC	Note C-1	TS 32.251 (PS)
UE-Reachability-Configuration	NONRO	Note NC-2	TS 29.336 (HSS)
UNI-PDU-CP-Only-Flag	CBC	Note C-1	TS 32.251 (PS)
Unused-Quota-Timer	CBC	Note C-1	TS 32.251 (PS)
Usage-Information-Report-Sequence-Number	NONRO	Note NC-2	TS 32.277 (ProSe)
UWAN-User-Location_Info	CBCDS	Note C-1	TS 32.251 (PS)
User-Location-Info-Time	NONRO	Note NC-2	TS 29.212 (Policy Gx)
Variable-Part	CBC	Note C-1	TS 32.299
Variable-Part-Order	CBC	Note C-1	TS 32.299
Variable-Part-Type	CBC	Note C-1	TS 32.299
Variable-Part-Value	CBC	Note C-1	TS 32.299
VCS-Information	CBCDS	Note C-1	TS 32.276 (VCS)
Visited-PLMN-Id	NONRO	Note NC-2	TS 29.272 (MME)
VLR-Number	CBC	Note C-1	TS 32.276 (VCS)
WLAN-Link-Layer-Id	CBC	Note C-1	TS 32.277 (ProSe)

Compliance Levels and Considerations

Definition of compliance levels

Compliance Level	Meaning
Fully compliant	DCA understands and supports the AVP. Will provide the functionality intended. Where relevant, scope of compliance indicated by accompanying note.
Non compliant	DCA does not support the AVP. However limited AVP support can still be obtained using the DCA configuration and the feature set provided by ACS. See indicated "NC" Notes and "G" Notes.
Compliant by configuration	DCA does not use the AVP. However partial or full AVP support can still be obtained using DCA configuration and the feature set provided by ACS. See indicated Note(s).
N/A - Offline	DCA is an online charging application. The AVP is marked for use with ACR/ACA offline charging and is not applicable to DCA. See Note NC-1.
N/A - Non-Ro	DCA is an online charging application (Ro Interface). See Note NC-2.

Considerations

Where a specific AVP is marked as "Compliant by configuration", the compliance level is limited by the notes below:

Note C-1

The specific AVP can be mapped through DCA AvpMapping configuration and used in the ACS control plan such as in branch decisions and inclusion in ACS generated EDRs and in various fields and records (for example, to complete the information collected for rating of the session).

Note that currently some limitations exists in the capabilities of ACS and CCS. If Convergent Charging Controller CCS Prepaid Charging is used, the specific AVP (if relevant) may be used to select a Tariff Plan only at the start of a charging session (for example, at CCR Initial Requests for session based reservations) or for a re-engaged session* by using the ACS Tariff Plan Override control plan node. For some scenarios (for example, in a UATB Node for a non re-engaged session), the tariff plan cannot be subsequently changed mid-session. See Convergent Charging Controller Charging Control Services User's Guide and Charging Control Services Technical Guide for details.

Where applicable, "Note C-2" may also apply.

The above limitations are based on the current service logic used for rating (that is, when using the UATB node). The interface provides the flexibility to allow future customized service logic nodes (through SDK or future developments), and future product capabilities, to utilize (and set) values mid-session.

Non-complaint, if the requirements cannot be meet by any of the approaches described above:

See Note NC-4 where applicable.
See NC-6 for OctetString and UTF8String AVPs that contain sub-fields or are formatted using data structures not supported by DCA.

* A re-engaged session is one where DCA treats the inbound Diameter CCR Update Request as an Initial Request and creates a new charging session through ACS. An example is when a new requested unit type is received in an Update Request for an existing service. See Diameter Control Agent Technical Guide for full details.

DCA may be used in different network configurations:

(i) with Convergent Charging Controller Prepaid Charging/VWS and the standard UATB Node in the ACS control plans.(ii) with a convergent billing engine (Oracle BRM or third party using Convergent Charging Controller DCD)(iii) with (i) or (ii) but with Custom development (using SDK).

Limitations described here apply to (i) only.

These limitations may be non-existent in (ii) and (iii).

Note C-2

Where the specific AVP is an address, "Note C-1" above applies except that, in addition to mapping to acsProfile fields, the specific AVP may be mapped to a predefine set of INAP address fields (for example, the called or calling party number) and sent to ACS and used in the ACS control plan such as in branch decisions and inclusion in ACS generated EDRs or in various fields and records. If the AVP is mapped as an acsProfile field (for example, through Raw Data mapping), the Profile may be copied to the relevant ACS address field (for example, Session Data's calling party number or equivalent). The scope is limited by the featureset and capabilities of ACS and CCS.

If Convergent Charging Controller CCS Prepaid Charging is used, the address† (if applicable) may be used in the rating of the call when address-based CLI-DN tariffs are applied. For some scenarios (for example‡, in a UATB Node for a non re-engaged session), if the specific AVP is mapped to a location-specific address, the location information cannot be updated mid-session to change or update the tariff used for rating of the current session. The Tariff Plan (once selected at the start of the UATB session) cannot be subsequently changed mid-session.

Also, session based Convergent Charging Controller CCS Prepaid Charging when used with the Convergent Charging Controller VWS has the following limitations:

Use of 2 addresses for CLI-DN tariffs. However, if additional addresses are to be used to determine the rating (and if inclusion of the additional information in ACS generated EDRs is not sufficient), other CCS feature have to be employed such as Tariff Plan Override.
Use of address fields that are digits only (that is, UTF8String AVP Format) or that which where the digits can be extracted from (for example, TEL URI such as "tel:+12015550123"). The CLI-DN tariffs only deal with pure digit-based addresses. Non-digit addresses cannot be handled and have to be mapped externally before these can be used in the CLI-DN tariffs.

The above VWS-specific limitations are not applicable if BRM is used instead of Convergent Charging Controller CCS Prepaid Charging. See Note C-3. Consult BRM documentation and the Convergent Charging Controller <BCD_Tg_fn> for details.

Non-complaint, if the requirements cannot be met by any of the approaches described above; See "Note NC-4".

† Only specific numbers (for example, Calling Party or Called Party numbers) can be used for CLI-DN Rating. See Charging Control Services Technical Guide for details.

‡ Tariff plan override node permits configuration according to changes in location mid-call/mid-session.

However this depends on the sending of ATI messages which DCA does not currently support.

Note C-3

For outbound AVPs, fully compliant AVP values are set in the service logic.

For outbound AVPs that are compliant by configuration, user-configurable mappable values may be mapped from:

An ACS field (for example, an acsProfile Session Data fields).
A literal (fixed value or constant) or a literal that is dependent on the value of another AVP field or acsProfile field

In any case, the AVP mapping must be applied for a specific service.

If the outbound AVP forms a request to the Diameter client, the following restrictions apply:

The outbound AVP is fixed to a specific outbound diameter message type as defined by the configuration. This may restrict the message sequence or scenarios required to be supported.
The request to the diameter client in the form of outbound AVPs in the Diameter response message may result in subsequent AVPs that are "Compliant by configuration" to be sent to DCA. See Note C-1 for details, however if these inbound AVPs required.

Non-complaint, if the requirements cannot be meet by any of the approaches described above; See "Note NC-5".

Note C-4

DCA does not contain inbuilt support for envelop reporting. Partial or limited compliance may be possible by configuration and restricting the use of the AVP:

To a specific service
With a single set value or a limited range of values
To specific messages or under a limited set of scenarios (message flows) only

Non-Compliance Issues

NC-1

DCA is an online charging application. AVPs associated only with offline charging are marked as "N/A". However, if the specific AVP is received, "Note C-1" can still be applied for this AVP.

NC-2

AVPs associated with non-Ro interfaces are marked as "N/A". However, if the specific AVP is received, "Note C-1" can still be applied for this AVP.

NC-3

When used with the Convergent Charging Controller VWS, DCA does not provide inbuilt support for the AoC Service. If no configuration is applied:

DCA is able to receive AoC (Advice of Charge) AVPs in the inbound Diameter request messages (all unconfigured AVPs are simply ignored),
DCA will not send AoC AVPs in the outbound Diameter messages.
DCA does supports Diameter Event based Price Enquiry which allows for reporting the price of the call/session separately from the call/session itself (for example, before the call).

With the appropriate configuration:

For session based charging, sending of AoC information AVPs at the end of the call is not readily supported without configuration issues.
For event based charging, when the Named Event node is used in the ACS control plan, DCA may be able to map the session charge into outbound AoC information AVPs but under a restricted set of conditions (See Diameter Control Agent Technical Guide and Charging Control Services Technical Guide for details).
Sending of real-time (AoC) information (for example, to provide accumulated cost for ongoing usage every 5 seconds) is not supported. DCA is non-compliant for real-time AoC service when used with the Convergent Charging Controller VWS.
Any Diameter responses sent will be limited by DCA's AvpMapping configuration, the ACS UATB control plan node (for Session-based charging) and "Note C-1" (above).
When used with BRM or the Convergent Charging Controller DCD application, support for the AoC Service is dependent on the external billing or rating system. See G-2 and G-3 for details and specific limitations.

Generic capabilities and limitations for sending outbound information are summarized in Note C-3 and NC-5.

NC-4

Not compliant if the specific AVP is a context or identifier or field that requires correlation with another session for tariff determination of the current session and/or the specific AVP involves other service-specific correlation or if the charging session flow involves non-standard session-control or real-time requirement that cannot be handled by the capabilities and featureset of DCA and/or the ACS control plan.

Note that Northbound convergent billing/rating engines may offer the ability to correlate this information. The ability to do this is dependent on the capabilities of the target convergent platform. See Note G-3.

NC-5

Non compliant if the outbound AVP is a concept that ACS does not understand (that is, AVP value cannot be mapped from any available ACS field) and the AVP cannot be dealt with using the DCA AvpMapping configuration (for example, by assigning a fixed constant per applicable service to be returned in the Diameter response message).

Note however that new fields can be defined as a user-defined ACS Profile and used in the ACS control plan and subsequently mapped to an outbound AVP. This may or may not provide the level of functionality or compliance required.

NC-6

For some highly complex data structure, the DCA Raw Data AvpMapping feature may not be sufficient to provide adequate compliance (see Note G-2 for additional details).

For example, if a complex AVP contains multiple subfields and:

only subfield-1 is required and subfield-1 is always present and always located at the start of the AVP and has a known fixed length, then this subfield can be extracted and hence DCA complies for the specific AVP.
only subfield-8 is required, but subfield-8 does not have a known (well-defined) offset within the AVP value and it is not the first or last subfield in the AVP and it's length is variable, then it is likely that DCA would not comply for the specific AVP.

NC-7

DCA does not support non-Ro interface messages, Price Request/Response, Tariff Request/Response, Service Usage Request/Response; DCA also does not support AVPs associated with these messages. Non-compliant if AVP is received in these messages.

However Note C-1 still applies for support messages such as Credit Control Request/Response.

DCA also supports Event-based Price Enquiry when sent over the Ro interface.

General

For all compliance levels (including some non-compliant AVPs), the following notes apply.

Note that all "G" notes below apply to all AVPs shown in 7.1 and 7.2.

Note G-1

The AVP can be received by DCA without causing adverse conditions. If no Inbound AvpMapping is configured, DCA will simply ignore the AVP. If an Inbound AvpMapping is configured, see Note C-1.

The AVP will not be sent by DCA in outbound diameter message if no Outbound AvpMapping is configured. If an Outbound AvpMapping is configured, see Note C-3.

Note G-2

DCA Raw Data Mapping can be used to extract information (sub-fields) from AVPs that contain complex data structures. If DCA Raw Data mapping is used, the specific AVP value (or a sub-field) can be mapped from an OctetString to ACS. This feature allows unsupported AVP formats to be mapped but is limited to the capabilities of the Raw Data feature described in the Diameter Control Agent Technical Guide. See NC-6 for additional details.

Note G-3

The specific AVP can be passed through to the Convergent Charging Controller DCD Application to a third Party Convergent Billing Engine (using Diameter Credit-Control). Compliance would depend on the capabilities of the external Credit-Control server (The capabilities of the external Credit-Control server is out-of-scope). Also, if during mid-session (CCR Update) requests, the units (used-service-units AVP) is determined to be not sufficiently exhausted (based on specific CCS threshold parameters; see Charging Control Services Technical Guide for details), the SLC (CCS/ACS) may not request additional units from the external Credit-Control server. This feature may restrict timely pass-through of specific AVPs and may impact services that require proper real-time transfer of AVPs through the SLC.

Note G-4

For convergent deployments where BRM is used for rating (as opposed to VWS) compliance would depend on the capabilities of BRM (the BRM specifics are out-of-scope; consult BRM documentation for details). Also, if during mid-session (CCR Update) requests, the units (used-service-units AVP) is determined to be not sufficiently exhausted (based on specific CCS threshold parameters; see Charging Control Services Technical Guide for details), the SLC (CCS/ACS) may not request additional units from the BRM server. This feature may restrict timely pass-through of specific AVPs and may impact services that require proper real-time transfer of AVPs through the SLC.

Note G-5

If configured to use an external billing system, compliance would depend on the capabilities of external system and with the limitations described in Notes G-2 and G-3 above.