Description
Immediate Event Charging (IEC) is a fundamental component of the 3GPP Online Charging System (OCS). It operates on a 'pay-before' paradigm for event-based services. The core architectural elements involved are the Charging Trigger Function (CTF), typically embedded within the network node providing the service (e.g., SMSC, MMSC), and the Online Charging System (OCS) itself, which includes the Charging Data Function (CDF) for charging events and the Account Balance Management Function (ABMF) for managing user balances.
The process begins when a user initiates a chargeable event, such as sending an SMS. The CTF detects this event and formulates a Credit Control Request (CCR) message using the Diameter Ro protocol. This CCR, of type EVENT_REQUEST, is sent to the OCS. The request includes details like the service identifier, requested service units (e.g., one SMS), and subscriber identity. The OCS then performs rating, based on the user's profile and tariff, and checks the subscriber's account balance in the ABMF.
If sufficient funds are available, the OCS reserves the appropriate monetary amount (or equivalent credit units) and responds with a Credit Control Answer (CCA) granting the service units. This response is immediate and authorizes the CTF to allow the service event to proceed. Crucially, the OCS then deducts the reserved amount from the user's account. The entire transaction—reservation and deduction—is performed in a single, atomic interaction. The service is only delivered if the credit authorization is successful. This contrasts with session-based charging where credit is granted for a duration or volume and is periodically re-authorized. IEC is designed for low-latency, high-reliability transactions to minimize service delivery delay while guaranteeing prepayment.
Purpose & Motivation
IEC was created to address the charging needs of non-session-based, transactional services that became popular with the rise of mobile messaging and content. Prior to standardized online charging, many value-added services used offline charging (CDRs), which incurred a risk of non-payment (bad debt) as services were delivered before the billing system could process charges. For prepaid subscribers, this was particularly problematic, as their account balance could be exhausted mid-transaction without a mechanism to prevent it.
The introduction of IEC in Release 4 provided a real-time, secure charging mechanism tailored for discrete events. It solved the prepaid problem by integrating balance checks and deductions directly into the service delivery logic. This enabled operators to confidently offer a wide array of pay-per-use services (e.g., premium SMS, ringtone downloads) knowing revenue was assured. It also improved the customer experience for prepaid users by providing immediate feedback on whether a transaction could proceed based on their balance, avoiding failed service attempts after partial processing. IEC standardized the interaction between network elements and the charging system, allowing for interoperability between vendors and fostering a vibrant ecosystem of value-added service providers.
What changed in its specifications
The latest release-to-release comparison of specifications that define IEC. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-17 added support for Multi-USIM devices, emergency call handling, and definitions for MUSIM UEs.
Full comparison in TS 22.101 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference IEC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.101 vl00 | 3GPP Service Principles for PLMNs | Rel-21 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TS 28.203 vi10 | Charging management | Rel-18 read |
| TS 28.204 vi11 | Charging management | Rel-18 read |
| TS 28.849 vj10 | CAPIF Phase2 Charging Study | Rel-19 read |
| TS 31.121 vj00 | UICC Application Test Specification | Rel-19 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |
| TS 32.254 vk00 | 3GPP TS 32.254: Charging for Northbound APIs | Rel-20 read |
| TS 32.256 vk10 | 5G Connection and Mobility Charging | Rel-20 read |
| TS 32.260 vk10 | IMS Charging Management | Rel-20 read |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 read |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.273 vj00 | MBMS Charging Management | Rel-19 read |
| TS 32.274 vj10 | SMS Charging Management Specification | Rel-19 read |
| TS 32.277 vj20 | Charging Management for Proximity Services (ProSe) | Rel-19 read |
| TS 32.278 vj00 | Monitoring Events Offline Charging Specification | Rel-19 read |
| TS 32.280 vj00 | Advice of Charge (AoC) Framework | Rel-19 read |
| TS 32.290 vk00 | 5G Charging Service-Based Architecture | Rel-20 read |
| TS 32.291 vk10 | 5G Charging Service-Based Interface | Rel-20 read |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 read |
| TS 32.299 vj00 | Diameter Charging Applications for 3GPP | Rel-19 read |
| TS 32.869 vf00 | Diameter Overload Control for Charging Interfaces | Rel-15 read |