Grant ValidityTime is Less than the Actual Granted Units
(Doc ID 2492239.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
During a diameter voice call for a prepaid subscriber, the grant validity time is set to a lower value than the actual granted seconds on ECE/DGW.
Because of this issue, the entire balance is not consumed before it ends the calls and some balance that is left behind, even though few more seconds of call can be rated with the available balance.
Validity Time should be set to at least the same value as GrantedServiceUnit (GSU). GSU is set to 187sec on the current scenario and so the Validity Time should be set to at least 187sec.
The issue can be reproduced at will with the following steps:
1. Login to Customer Center and choose a subscriber having:
: Rating details:
- 0.99/min -> 0.0165 per sec.
- round UP logic up to 2 decimal places, hence the price would be 0.02 per sec
- 13.01 balance.
2. Customer initiates a call: RSU is set to 600 secs.
3. In the response, GSU is set to 600 secs and validity time for this grant is 600 sec which is as expected
4. After 600 secs, an update request - CCR-U - is received, where the RSU is 600 secs. Since the customer only has balance of -3.11 (-13.01 – 9.9), the CCA-U gives GSU of 187 with seconds with FUI, which is correct, but a validity time of 184 seconds which is not as expected.
5. OC3C found the validity of 184 secs and returns a terminate request with 184 secs as USU although 187 sec were given, because of the fact that expiry time was given as 184 secs.
6. Finally after the call the customer is left with -0.07 although with he will still be able to make 4 sec call.
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