Description
A charging event is a fundamental unit of charging information in 3GPP networks. It is defined as a set of charging information forwarded by the Charging Trigger Function (CTF) towards the Charging Data Function (CDF) for offline charging, or towards the Online Charging System (OCS) for online charging. Each charging event corresponds to exactly one chargeable event, which is an activity that may incur a charge, such as a voice call, a data session, or the use of a specific service.
The charging event serves as the atomic unit of charging data. It contains all the necessary information for the charging system to rate and bill the usage, including identifiers, timestamps, volume counts, and service-specific parameters. The CTF, which is typically located in the network element that provides the service (e.g., SGSN, GGSN, P-GW, IMS node), detects chargeable events and generates charging events accordingly.
In offline charging, charging events are sent to the CDF, which processes them and generates Charging Data Records (CDRs). These CDRs are then transferred to the billing domain via the Charging Gateway Function (CGF). In online charging, charging events are sent to the OCS, which performs real-time rating and credit control. The OCS may authorize the service, deny it, or grant a quota based on the subscriber's account balance.
The charging event concept is specified in multiple 3GPP specifications, including TS 32.240 (Charging architecture and principles), TS 32.251 (Packet Switched domain charging), TS 32.270 (IMS charging), and others. It has been part of the 3GPP charging framework since Release 8 and its definition has remained unchanged through Release 19, demonstrating its stability and fundamental importance.
Purpose & Motivation
The charging event exists to provide a standardized and granular way to capture and convey charging information in 3GPP networks. Before the introduction of this concept, charging systems often relied on proprietary or technology-specific mechanisms, which made it difficult to support multiple access technologies, roaming, and converged services. The charging event abstraction allows the charging system to be independent of the underlying network technology and service type.
The charging event solves the problem of how to represent a chargeable occurrence in a consistent manner across different network domains. By defining a charging event as a set of charging information that matches exactly one chargeable event, 3GPP ensures that the charging system can accurately correlate usage with billing. This is essential for both offline and online charging, as it enables precise rating and prevents over- or under-charging.
Furthermore, the charging event concept facilitates the integration of new services and charging models. As new services are introduced, they can define their own charging events with specific parameters, while still adhering to the common framework. This extensibility has allowed the 3GPP charging architecture to evolve and support a wide range of services, from basic voice and data to advanced IMS and IoT applications.
What changed in its specifications
The latest release-to-release comparison of specifications that define Charging event. 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 →Rel-19 adds charging for store-and-forward satellite operation to TS 32.251. It introduces new MME charging triggers, a new MME UP CIoT record, and new satellite fields in SMS records.
Full comparison in TS 32.251 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced: 'a set of charging information forwarded by the CTF towards the CDF (offline charging) or towards the OCS (online charging). Each charging event matches exactly one chargeable event.' This established the core concept of charging events in the 3GPP charging architecture.
Defining Specifications
3GPP specifications that define or reference Charging event, 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.251 vj00 | PS Domain Charging Management | Rel-19 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.276 vj00 | VCS Online Charging from Proxy Function | 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.293 vj00 | Proxy Function in Domestic Service Provider | Rel-19 read |
| TS 32.849 vd00 | IMS Roaming Charging Study | Rel-13 read |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 read |