Description
The Event Based Charging Function (EBCF) is a fundamental component within the 3GPP Online Charging System (OCS). Its role is to execute charging logic in real-time for service events. Unlike session-based or volume-based charging, which are continuous, event-based charging is triggered by discrete occurrences. The EBCF receives charging events from network functions like the Gateway GPRS Support Node (GGSN), Packet Data Network Gateway (PGW), or IMS Call Session Control Functions (CSCFs) via the Ro or Gy reference points. These events carry information such as the subscriber identity, event type, and relevant service parameters.
Architecturally, the EBCF resides within the OCS and works in conjunction with the Account Balance Management Function (ABMF) and the Rating Function (RF). When a charging request arrives, the EBCF processes it. It first performs subscriber identification and retrieves the relevant account information and charging rules from the ABMF. It then uses the RF to determine the monetary or non-monetary cost (in units like credits) associated with the specific event. This rating can be complex, depending on factors like event type, service type, location, time of day, and subscriber tier. After rating, the EBCF instructs the ABMF to deduct the appropriate amount from the subscriber's balance in real-time.
How it works is centered on policy and real-time authorization. For each event, the EBCF must make an immediate decision: authorize the event (if sufficient balance exists) or deny it. For example, when a user sends an MMS, the MMS server sends a charging event to the OCS. The EBCF rates this 'MMS submission' event, checks the balance, and if authorized, allows the MMS to be sent while deducting the cost. It then returns a response to the network element. The EBCF supports various event types, including service events (e.g., content download, SMS, MMS), service configuration events (e.g., activating a call forwarding rule), and management events (e.g., balance top-up). It generates Charging Data Records (CDRs) for billing and auditing purposes.
Purpose & Motivation
The EBCF was created to address the limitations of traditional, simplistic charging models based solely on call duration or megabyte counts. As mobile networks evolved to offer a vast array of services beyond voice—such as messaging (SMS/MMS), content downloads, location-based services, and IMS features—operators needed a flexible way to charge for these discrete, non-continuous transactions. A flat data rate or per-minute voice charge could not capture the value or cost structure of sending an MMS or accessing a premium game level. The EBCF provides the mechanism for this granular, service-aware charging.
Introduced in Release 8 as part of the enhanced OCS architecture, the EBCF solved the problem of real-time credit control for event-based services. It enabled prepaid offerings for non-session services, which was a major business requirement. Without it, operators would have to rely on less accurate offline charging or forced all services into session-based models. The EBCF allows operators to define sophisticated tariff plans that charge different amounts for different types of events, fostering service innovation and personalized pricing. It is a key enabler for the monetization of the vast service ecosystem in modern mobile networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define EBCF. Each summary describes the whole specification, not only this term.
Uncrewed Aerial System Phase 3 added charging support, abbreviations, and definitions. CAPIF Phase 3 added charging support and a new reference point. Energy Efficiency as Service Criteria added clauses for energy KPIs, measurement, and slice charging references.
Full comparison in TS 32.240 →MMS converged charging in 5G system, with architecture, flows, CDR triggers, and message formats defined.
Full comparison in TS 32.270 →Technology family
Charging architecture · Core Network
- R99 CDR, CGF
- Rel-5 OCS
- Rel-6 ABMF, BD, CDF, CTF, EBCF, OCF, OFCS, RF, SBCF
- Rel-8 IMS-GWF
- Rel-15 CCS, CHF
- Rel-16 CEF
- EBCF part of OCF
“The Rc reference point allows the interaction between the online charging functions (SBCF, EBCF) and the ABMF to access the subscribers account balance.” TS 32.296
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 3 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
The Event Based Charging Function is specified for the first time, performing event-based online charging with account/counter control and price requests to the Rating Function.
- “The Event Based Charging Function performs event-based online charging (also referred to as “content charging”) in conjunction with any application server or service NE” TS 32.240 v6.4.0
- “The PriceRequest method is used only for event based charging, i.e. only the EBCF uses this method.” TS 32.296 v6.3.0
- “Step 2: The EBCF requests account and counter information for the subscriber from the Account Balance Management Function.” TS 32.296 v6.3.0
TS 32.296 added procedures in which the EBCF sends price requests to the Rating Function and creates or updates subscriber contexts for correlation in IEC and ECUR scenarios.
- “the EBCF sends a price request to the Rating Function in order to determine the price of the desired service” TS 32.296 v8.3.0
- “In case there is no existing subscriber's context, the EBCF creates a new subscriber's context information.” TS 32.296 v8.3.0
- “The following figure describes the case where the EBCF invokes the PriceRequest method to make reservation but debits after service delivery.” TS 32.296 v8.3.0
TS 32.296 added EBCF call flows showing it requesting account and counter information and debits or reservations from the ABMF (Rating class A), plus an Rc-based Immediate Account Debit scenario.
- “The EBCF requests account and counter information for the subscriber from the ABMF. Only valid for Rating class “A”.” TS 32.296 v11.5.0
- “The EBCF requests the ABMF to debit (or “release” if the service delivery status is unsuccessful) the reservations for the requested service.” TS 32.296 v11.5.0
- “The following figure describes an Immediate Account Debit scenario for the case when the EBCF interacts with an ABMF over an Rc reference point.” TS 32.296 v11.5.0
Defining Specifications
3GPP specifications that define or reference EBCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.278 vj00 | Monitoring Events Offline Charging Specification | Rel-19 read |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 read |
| TS 32.825 va00 | Rc Reference Point Study for ABMF | Rel-10 read |