Diameter Parameters
Diameter Parameters
Several simple parameters are available to configure N2IWF general Diameter behaviour. Each parameter is specified as a LogicApp service global variable. These parameters are all simple definitions, not complex types or N2SVCD rule engine rulesets.
| Parameter | Type | Description |
|---|---|---|
DIAMETER_CHARGE_MODEL |
String | The charging model to use for all sessions through this IWF instance. Possible values are:
scur). |
DIAMETER_SEND_SUBSCRIPTION_ID |
Boolean | Whether to send subscriber information inside a Diameter Subscription-Id AVP or not.Should be enabled for strict compatibility with RFC 4006. At least one of DIAMETER_SEND_SUBSCRIPTION_ID and DIAMETER_SEND_SUBSCRIPTION_ID_EXTENSION must be enabled.(Default = true). |
DIAMETER_SEND_SUBSCRIPTION_ID_EXTENSION |
Boolean | Whether to send subscriber information inside a Diameter Subscription-Id-Extension AVP or not.Should be enabled for strict compatibility with RFC 8506. At least one of DIAMETER_SEND_SUBSCRIPTION_ID and DIAMETER_SEND_SUBSCRIPTION_ID_EXTENSION must be enabled.(Default = false). |
DIAMETER_SEND_MSISDN |
Boolean | Whether to send the subscriber MSISDN (derived depending on the input protocol to the OCS in Diameter requests. At least one of DIAMETER_SEND_MSISDN, DIAMETER_SEND_URI, and DIAMETER_SEND_IMSI must be enabled.(Default = true). |
DIAMETER_SEND_IMSI |
Boolean | Whether to send the subscriber IMSI (derived depending on the input protocol to the OCS in Diameter requests. At least one of DIAMETER_SEND_MSISDN, DIAMETER_SEND_URI, and DIAMETER_SEND_IMSI must be enabled.(Default = false). |
DIAMETER_SEND_URI |
Boolean | Whether to send the subscriber URI (derived depending on the input protocol to the OCS in Diameter requests. At least one of DIAMETER_SEND_MSISDN, DIAMETER_SEND_URI, and DIAMETER_SEND_IMSI must be enabled.(Default = false). |
DIAMETER_REQUIRE_ALL_SUB_IDS |
Boolean | Whether to require all forms of subscriber ID specified by DIAMETER_SEND_MSISDN, DIAMETER_SEND_URI, and DIAMETER_SEND_IMSI. If this parameter is true, then a session will be rejected if any of the identifiers configured cannot be populated. If this parameter is false, then sessions will be allowed to proceed as long as at least one configured subscriber identifier is populated.(Default = true). |
DIAMETER_TIME_ROUNDING |
String | The rounding method to apply for times provided by the network, where required. Times that are already an even number of seconds (including 0) will not be modified. Possible values are:
ceiling). |
DESTINATION_HOST_FROM_CCA |
Boolean | Controls the presence and value of the Diameter Destination-Host AVP, in conjunction with the N2SVCD Diameter application configuration parameter force_destination_host.If this parameter is set to false, no special handling will occur for this AVP and theDestination-Host will be set according to the Diameter application setting.If set to true, no Destination-Host AVP will be sent in initial requests, and subsequent requests will include a Destination-Host AVP with a value taken from the last received response’s Origin-Host AVP. In this case, the Diameter application setting should be false to avoid the Destination-Host potentially changing between requests.(Default = false). |
DIAMETER_SPLIT_EDRS |
Boolean | Whether to write a single EDR containing both the Diameter request and response details (false) or whether to write separate EDRs for the Diameter request and response (true).(Default = false)_. |
DIAMETER_SID_PREFIX |
String | The prefix to use for Diameter Session-Id values generated.(Default = n2iwf). |
DIAMETER_USE_MSCC |
Boolean | Whether to put rating AVPs inside a Diameter Multiple-Services-Credit-Control AVP or not.If set to false, rating AVPs will be placed at the root level.(Default = true). |
DIAMETER_CLOSE_ROOT |
Boolean | Whether to close root sessions when the Multiple-Services-Credit-Control sub-session is closed with aResult-Code that is not 2xxx.If set to false, no Credit-Control-Request (TERMINATE) will be sent in such cases.(Default = true). |
Charging Models
The N2IWF supports all three online charging models described by 3GPP TS 32.299.
Note that the N2IWF supports only 3GPP centralised rating, i.e. rating using non-monetary units.
Event Charging with IEC
The IEC charging model operates as a single request and response to the OCS for any given input message. If the charging request is successful, the message is allowed to proceed in the appropriate manner for the input protocol but no further OCS requests are made; the charge is debited immediately during the initial charging interaction.
IEC charging includes the ability to process a refund where applicable. The semantics of what this looks like are specific to the input protocol, but will always be another invocation of the IEC charging model with the refund message.
IEC charging is supported only for CAMEL SMS in the N2IWF.
Event Charging with ECUR
The ECUR charging model operates with an initial request and response to the OCS for any given input message. If the charging request is successful, the message is allowed to proceed in the appropriate manner for the input protocol with a reservation held open on the OCS. The reservation will then be voided or confirmed by another message from the network indicating the success or failure of the interaction.
ECUR charging is supported only for CAMEL SMS in the N2IWF.
Session Charging with SCUR
The SCUR charging model is similar to the ECUR model, but allows for interim charging requests as the session continues, in addition to the initial and final requests. Each interim charging request can extend the original reservation, as determined by the OCS.
SCUR charging is supported only for CAMEL/INAP and SIP calls in the N2IWF.