Overwrite AVP Flags Validation for Diameter Control Agent
(Doc ID 2188561.1)
Last updated on OCTOBER 04, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.
This article aims to provide a mechanism for overriding AVP flags validation in the Diameter Control Agent (DCA) gateway.
The Diameter Control Agent (DCA) is a SLEE interface used to translate between Diameter messages and Camel messages.
Diameter is a protocol which has been designed to supersede RADIUS, and which facilitates AAA (Authentication, Authorization and Accounting), and Credit-Control.
The DCA acts as a Diameter based credit control server. In doing so, it provides an interface to the Prepaid Charging product (CCS component), to facilitate the use of the billing functionality provided there.
AVP Flags - according to RFC 6733 (Diameter Base Protocol), Diameter AVPs carry specific authentication, accounting, authorization, and routing information as well as configuration details for the request and reply. AVP has following frame format:
| AVP Code |
|V M P r r r r r| AVP Length |
| Vendor-ID (opt) |
| Data ...
For more details about each AVP component please have a look on the above document - RFC 6733; right now we are interested only on AVP Flags.
The AVP Flags field informs the receiver how each attribute must be handled:
: The 'V' bit, known as the Vendor-Specific bit, indicates whether the optional Vendor-ID field is present in the AVP header. When set, the AVP Code belongs to the specific vendor code address space.
: The 'M' bit, known as the Mandatory bit, indicates whether the receiver of the AVP MUST parse and understand the semantics of the AVP including its content. The receiving entity MUST return an appropriate error message if it receives an AVP that has the M-bit set but does not understand it.
: The 'P' bit - P-Protected Bit - If this bit is set indicates that Avp data is encrypted for end-to-end security.
: The 'r' bit - Reserved bits and SHOULD be set to 0.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document