3 Configuring Multiple Services Credit Control
Learn how to configure Multiple Services Credit Control in Oracle Communications Elastic Charging Engine (ECE).
Topics in this document:
About Multiple Services Credit Control
ECE supports Multiple-Service Credit Control (MSCC) requests in which a Diameter application performs credit control for multiples services within the same session.
An MSCC request is a list of subrequests targeted to the same customer that share the same operation type and session ID but that individually apply to different charge offers.
When ECE receives MSCC requests, it assigns a different session ID to each of its subrequests. Doing this enables ECE to distinguish one subrequest from another when looking up the active session associated with each subrequest. An MSCC request results in an MSCC response containing a subresponse for each subrequest. Each subresponse contains a status indicating whether the subrequest succeeded or failed.
If you configured ECE to save the rated event information for MSCC requests in the Oracle NoSQL database, note the following:
-
Rated event information is saved for each subrequest.
-
The NoSQL key for the rated event is based on the session ID that ECE assigned (not on the original MSCC request session ID).
-
The ECE session ID in the Oracle NoSQL database is a composite of the original usage request's session ID, the service, and the user identity, separated by underscore characters. For example:
Original MSCC request ID: 1313b2ab-d51e-4545-8bba-25c731daf10b
Usage request's service: VOICE
Usage request's user ID: 650123555
ECE session ID: 1313b2ab-d51e-4545-8bba-25c731daf10b_VOICE_650123555
MSCC support applies to usage requests and query requests.
MSCC support does not include support for credit pools (G-S-U-Pool-Reference AVP where units of the service are pooled in a credit pool) and credit control (as described in section 5.1.2 of IETF RFC 4006).
MSCC AVPs are part of the CCR, and Diameter Gateway expects each Gy interface request type to be included in the MSCC group even if the request contains only a single service. When a CCR is sent without MSCC AVPs, Diameter Gateway validates only the subscriber ID in the CCR and authenticates the subscriber.
See the SampleMultipleServicesLauncher sample program in the ECE SDK for an example of how to send MSCC requests to ECE. For more information, see "ECE Sample Programs".