Last updated on MAY 30, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Diameter Gateway
How can one add validation logic for incoming DCCA CCR structures? In Dictionary.xml, only Credit-Control structure with some restrictions can be found.
As is understood, maximum="1" means that this AVP can occur only maximum once, minimum="1" means that this AVP has to occur only minimum once, position="0" means that this AVP will have to be first in incoming CCR structure.
But if one wants validate CCR dedicated for DATA and CCR dedicated for Voice stream and for DATA in CCR, it is always expected that an AVP that does not occur in VOICE, how to manage this requirement?
Need to validate that AVP Origin-State-Id is present in CCR Data and do nothing for this AVP for CCR Voice.
How can one handle this topic in Credit-Control construction (or maybe add new Credit-Control construction)?
Also the Multiple-Services-Credit-Control has its own construction: attribute mandatory="must" means that this AVP has to be present in AVP Group, but it is strictlt for answer dedicated AVP, so how does it work for request validation? There is in only one Multiple-Services-Credit-Control construction, how does it manage validation for Request and Answer differently? Is it hard-coded in Diameter stack?
For Diameter AVP validation one can find logic based on:
boolean required, int minOccurence, int maxOccurence, int position, DiameterAVPDictionaryEntry.FLAGOPTION mandatory (MUST, MAY, MUSTNOT, SHOULDNOT, UNKNOWN;)
What does required mean in these parameters?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms