Event Charging Function

Description

The Event Charging Function (ECF) is a fundamental logical entity within the 3GPP Online Charging System (OCS) architecture, as defined in the TS 32.2xx series specifications. It operates in real-time, performing immediate rating and charging for network resource usage as service events occur. The ECF is responsible for processing 'charging events' triggered by network functions like the MSC, SGSN, GGSN, P-CSCF, or AS. A charging event represents a discrete unit of service consumption, such as the establishment of a voice call, the sending of an SMS, a data session activation, or the delivery of a content download. The ECF's primary role is to determine the monetary or non-monetary cost of such an event and to authorize it based on the user's account balance in the OCS.

The ECF interacts with other OCS components through the standardized Ro reference point (Diameter protocol). When a network element (acting as a Charging Trigger Function, CTF) detects a billable event, it sends a Credit Control Request (CCR) to the ECF. The ECF then engages with the Account Balance Management Function (ABMF) to check the subscriber's account balance and with the Rating Function (RF) to determine the cost of the requested service unit. Based on this information, the ECF makes an authorization decision. If credit is available, it reserves an appropriate amount from the balance and responds with a Credit Control Answer (CCA) granting a quota of units (e.g., seconds of call time, volume of data in bytes, number of messages). The network element then allows the service to proceed and consumes this quota. Upon quota exhaustion or service termination, a new CCR is sent, and the ECF deducts the used amount from the account and may grant a new quota. This process ensures real-time balance control.

Architecturally, the ECF can be deployed in different models. In the 'Event-Based Charging' model, it handles immediate, discrete events like SMS or MMS. It also plays a key role in 'Session-Based Charging' through its integration with the Session Charging Function (SCF), where it may handle specific events within a longer session. The ECF is central to enabling prepaid services, real-time spending limit controls (e.g., for data bundles), and convergent charging where services from multiple domains (voice, data, messaging) draw from a single balance. Its operation is critical for operators to prevent revenue leakage, offer flexible tariff plans, and provide subscribers with immediate feedback on their credit consumption.

Purpose & Motivation

The ECF was created to address the fundamental business requirement for real-time, or 'online', charging and prepaid services in mobile networks. Traditional 'offline' charging (based on CDRs) introduced a delay between service usage and billing, which was unsuitable for prepaid subscribers who need immediate deduction from their account balance to prevent debt. Prior to standardized OCS architectures, vendors implemented proprietary prepaid solutions that were tightly coupled with specific network switches, limiting flexibility and interoperability.

The standardization of the ECF within the 3GPP OCS framework, starting in Release 5, solved these problems by decoupling the charging logic from the network elements. It established a clear, open interface (Ro) for all network functions to request credit authorization in a consistent manner. This allowed for the creation of a centralized, real-time charging platform that could serve multiple services (circuit-switched, packet-switched, IMS) from a single subscriber balance. The ECF enabled operators to launch sophisticated prepaid offerings, implement real-time spending controls for postpaid users, and rapidly introduce new services with complex event-based tariffs. It was a key enabler for the prepaid business model that drove massive mobile adoption globally and remains essential for modern convergent charging.

Key Features

• Processes real-time charging events for service authorization
• Interacts with Rating Function (RF) for tariff determination
• Communicates with Account Balance Management Function (ABMF) for balance checks and updates
• Uses Diameter Ro interface for communication with network CTFs
• Grants and manages usage quotas (time, volume, events)
• Supports both event-based charging (e.g., SMS) and session-based charging events

Evolution Across Releases

Defining Specifications