My Oracle Support Banner

ECE Balance Mismatch During Federation Conflict Resolution (Doc ID 2999645.1)

Last updated on JANUARY 29, 2024

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


On Oracle Communications Elastic Charging Engine (ECE) version, Cloud Native (CN) Deployment

It is observed that the ECE cache are not in sync while the rating is ongoing for the customer when the rating request are coming within a shorter time span.

Basically the scenario here is, the customer is roaming and he falls under customerGroup2 in ECE and the Granted-Service-Unit (GSU) for the subsequent update request is 1050 KB. Once the data session is turned on the usage request are going to site 2 ECE and the balance is getting federated to the other site. But if the request interval is very short, since before the federation completes, both the Balance cache are not in alignment and the OOB code is trying to resolve the conflict.

Consider the sample scenario where after an update request, as within the interval of 1 sec, another update is coming in site 1, one can see the conflict resolution logic of code is getting called. Similarly there are multiple such instances, and even once the customer has breached entire data, because of this conflict resolution, it can be observed in site 1 ECE cache that still the customer can browse some data but in actual the entire balance has been consumed which was impacted in site2.

This would lead to incorrect representation of the balance to end customer or any transaction happening from Oracle Communications Billing and Revenue Management (BRM) to ECE.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.