Description
The Billing Domain (BD) is a fundamental concept in 3GPP charging architecture, defined as the part of the operator network that lies outside the telecommunication network and is responsible for receiving and processing charging information from core network charging functions. It is specifically applicable to offline charging scenarios, where charging information is collected after the service usage has occurred, as opposed to online charging where credit control is performed in real-time. The BD encompasses functions that provide billing mediation and billing or other end applications, such as statistical analysis. The BD interfaces with the Charging Gateway Function (CGF) or the Charging Data Function (CDF) within the core network, typically via the Ga or Bx reference points, to receive Charging Data Records (CDRs). These CDRs contain detailed information about service usage, including volume, duration, and QoS parameters. The BD then processes these records to generate bills or other outputs. The architecture ensures that the core network remains focused on real-time operations while the BD handles the potentially complex and less time-critical tasks of billing and analysis. The BD is not involved in online charging; that role is fulfilled by the Online Charging System (OCS), which interacts with network elements in real-time to authorize and monitor usage. The separation of offline and online charging domains allows operators to implement flexible charging models and to integrate with external billing systems without impacting network performance. The BD may include multiple sub-functions, such as mediation, rating, and billing, which can be distributed across different systems. Mediation functions normalize and correlate CDRs from various network elements, while rating functions apply tariffs to usage, and billing functions generate invoices. The BD is a key component in ensuring accurate and timely billing for services, and its design must consider scalability, reliability, and security. Over the releases, the definition of BD has remained stable, reflecting its well-established role in 3GPP networks.
Purpose & Motivation
The Billing Domain exists to separate the complex, often batch-oriented processes of billing and mediation from the real-time operations of the telecommunication network. This separation allows network elements to focus on their primary functions—such as call control, data transport, and session management—without being burdened by the intricacies of billing systems, which may involve multiple external systems, varying tariff structures, and regulatory requirements. By offloading charging data processing to the BD, operators can achieve better performance and scalability in the core network. Historically, before the formalization of the BD concept in 3GPP, billing functions were often tightly integrated with network elements, leading to inefficiencies and difficulties in adapting to new services and pricing models. The introduction of the BD in Release 8 provided a standardized architectural framework that enabled operators to deploy flexible and scalable charging solutions. It also facilitated interoperability between network equipment from different vendors and billing systems from various providers. The BD addresses the need for offline charging, where immediate credit control is not required, such as for postpaid subscribers or for services that are billed periodically. It complements the Online Charging System, which handles prepaid and real-time charging. Together, they form a comprehensive charging architecture that supports diverse business models.
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference Billing Domain, 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.250 vj00 | Circuit Switched Offline Charging | Rel-19 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 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.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.295 vj00 | 3GPP Charging: CDR Transfer via GTP' Protocol | Rel-19 read |
| TS 32.297 vj00 | Charging Data Record File Transfer | Rel-19 read |
| TS 32.298 vk10 | Charging Data Record Specification | Rel-20 read |