ECE Fails To Reserve Remaining Balance During Successive CCR Requests
(Doc ID 2700625.1)
Last updated on AUGUST 18, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Elastic Charing Engine (ECE) fails to reserve remaining balance when Credit Control Request (CCR) is received upon Validity-Time expiration.
Some background details:
The Default Quota enabled for data usage is 300MB. When a customer starts the session, ECE grants the default quota to use within a Validity-Time (as 1 hour).
In case the customer consumes this 300MB in the session and continues it, a new update request shall be sent from gateway requesting for next reservation.
If customer has less than 300MB, let's say 280MB and starts a data usage session, he will be granted with 280 MB for usage with Validity-Time set for 1 hour.
He can use less than the granted quota, say 100MB within this validity time, then Gateway (GGSN) sends the next update request saying 100MB has been used within the validity time and customer wants to continue the session. At this time ECE registers 100MB used and try to reauthorize remaining balance (180MB in this case) as quota for usage in next hour.
With ECE 18.104.22.168.11 this is not happening, customer is not granted with remaining 180MB for usage and he will not be able to use the remaining balance data
Also, the activeReservation in BalanceCache of ECE shows zero (instead of remaining 180MB):
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