ECE works with the following core components:

Elastic Charging Server: Receives and calculates data from ECE clients, performs all billing business logic, such as usage billing, and performs queries and updates on ECE cached data.

Elastic Charging Client: A client library installed on ECE clients that enables ECE clients to connect and send requests to ECE. It is used to send all types of requests: usage, query, update, and management.

Diameter Gateway and RADIUS Gateway: Convert requests received from Diameter and RADIUS clients to ECE Java API requests and responses from Elastic Charging Server back to Diameter and RADIUS requests.

Customer Updater and Pricing Updater: ECE must access pricing data to bill received usage requests. Pricing Updater automatically loads pricing data into the ECE when the PDC publishes pricing data.

ECE builds on Oracle Coherence, a grid application that leverages data grids to manage information and related operations in a distributed environment. ECE distributes functionality across a network of nodes, which are Java applications that contain Oracle Coherence library. ECE also has built-in high availability features, including distributing ECE objects across multiple physical servers, distributed processing, and storing information on multiple nodes and racks to prevent node, machine, and rack failures.

ECE supports multi-site deployments with near-linear scalability, low latency, and high availability through its high-performance and consistent data management architecture. ECE supports converged billing architectures in standalone (SA) and non-standalone (NSA) 5G core networks using HTTP/2 and Diameter gateways. ECE also supports converged billing Mediation for multiple network types, including 5G and hybrid 4G/LTE/5G networks, as well as non-telecom applications, by adding Oracle Communications Offline Mediation Controller (OCOMC).