Description
The Billing Domain (BD) is a core component within the 3GPP Charging and Billing architecture, specifically defined in the Management and Orchestration (MAN) and Charging (CH) specifications. It functions as the system that receives, processes, and formats Charging Data Records (CDRs) or Event Data Records (EDRs) generated by the network's Charging Trigger Functions (CTFs) located in various network elements like the PGW, SMF, or application servers. The BD applies complex business logic, including tariff plans, discounts, promotions, and taxation rules, to transform raw usage data into billable items for end customers or for inter-operator settlements.
Architecturally, the BD interfaces with the Charging Data Function (CDF) or the Converged Charging System (CCS) via standardized reference points, such as the Bx interface for offline charging or the Nchf interface for online charging in 5G systems. It encompasses several sub-functions: the Billing Mediation Function, which normalizes and correlates records from different sources; the Rating Function, which assigns monetary value to service units; and the Billing Account Management function, which manages customer accounts and invoice generation. The BD must ensure data integrity, security, and compliance with regulatory requirements throughout this processing chain.
Its role extends beyond simple invoice generation. The BD supports various billing models, including pre-paid, post-paid, and hybrid models, and is essential for new service monetization like network slicing, IoT connectivity, and edge computing services in 5G. It provides the necessary feedback loop for policy control by settling financial transactions and enabling real-time balance management for online charging scenarios. The BD's outputs are detailed customer invoices, financial reports, and data feeds to business support systems (BSS) for customer relationship management and analytics.
Purpose & Motivation
The Billing Domain exists to automate and standardize the monetization of telecommunications services, solving the fundamental business problem of converting network resource consumption into revenue. Prior to standardized domains, billing was often a proprietary, siloed process tied to specific services, making it difficult to charge for complex, bundled offerings or to ensure accurate inter-operator settlements in multi-vendor, roaming environments. Its creation was motivated by the need for a scalable, reliable, and flexible system that could keep pace with the explosion of digital services beyond simple voice calls, such as data sessions, messaging, and content delivery.
Historically, as networks evolved from 2G to 3G and beyond, the variety and volume of chargeable events increased dramatically. The BD, as formalized in 3GPP, provides a unified framework that separates the billing logic from the network's real-time session control. This separation allows operators to introduce new tariffs and services without modifying core network equipment. It addresses the limitations of earlier, non-standardized approaches by ensuring audit trails, preventing revenue leakage through robust record generation and handling procedures, and enabling support for complex regulatory requirements like itemized billing and tax calculation. In essence, the BD transforms technical network events into commercial transactions, forming the financial backbone of the operator's business.
What changed in its specifications
The latest release-to-release comparison of specifications that define BD. Each summary describes the whole specification, not only this term.
Enhanced EASDF DNS context creation and response handling for I-SMF based local offloading management; added MoQ relay IP address support in PSA UPF and DNS response building with feature negotiation for Release 19.
Full comparison in TS 29.556 →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 →Technology family
Charging architecture · Core Network
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 Billing Domain is defined for the first time as the part of the operator network outside the core network that receives and processes CDR files from core network charging functions, for offline charging, via the Bx reference point.
- “Billing Domain: part of the operator network, which is outside the core network, that receives and processes CDR files from the core network charging functions.” TS 32.240 v6.4.0
- “The Bx reference point supports interaction between a Charging Gateway Function and the Billing Domain. The information crossing this reference point is comprised of CDR files.” TS 32.240 v6.4.0
TS 32.240 gained a reference point to the Billing Domain for SMS-SC offline charging, and its offline-charging text on the BD interface was reworked.
- “Introduction of Reference Point to the Billing Domain for SMS-SC Offline Charging” TS 32.240 v12.6.0
The Billing Domain definition in TS 32.240 was reworded so it receives CDR files from the charging functions rather than only the core network charging functions, broadening its scope.
- “which receives and processes CDR files from the charging functions.” TS 32.240 v16.5.0
- “which receives and processes CDR files from the core network charging functions.” TS 32.240 v16.5.0
Defining Specifications
3GPP specifications that define or reference BD, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 26.906 vj00 | HEVC Evaluation for 3GPP Services | Rel-19 read |
| TR 26.948 vj00 | Video enhancements for 3GPP Multimedia Services | Rel-19 read |
| TS 29.556 vk00 | EASDF Service Based Interface Stage 3 | Rel-20 read |
| 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.252 vc00 | 3GPP WLAN Interworking Charging | Rel-12 read |
| TS 32.253 vj00 | Charging for Control Plane Data Transfer | Rel-19 read |
| TS 32.254 vk00 | 3GPP TS 32.254: Charging for Northbound APIs | Rel-20 read |
| TS 32.255 vk30 | 5G Data Connectivity Converged Charging | Rel-20 read |
| TS 32.256 vk10 | 5G Connection and Mobility Charging | 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.279 vj00 | 5G MBS Session Converged Charging | 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 |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 32.821 v900 | SON OAM for Home NodeB (LTE/UMTS) | Rel-9 read |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 read |
| TR 38.808 vh00 | Study on NR above 52.6 GHz to 71 GHz | Rel-17 read |