Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

CDR

Charging Data Record

Services →

CDR is the fundamental unit for offline charging, a structured data record generated by network functions to capture resource usage for billing and accounting, detailing service consumption, duration, data volume, and subscriber identity.

Introduced
R99
Where
Services › IMS
Specifications
52 specs
Also in
Core Network, Management
CDR Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

A Charging Data Record (CDR) is a formatted data set produced by Charging Trigger Functions (CTFs) within network elements like the SGSN, GGSN, or P-GW. It documents a specific service usage event, such as a voice call, SMS, or data session. The creation is triggered by predefined charging events (e.g., session start, stop, or volume threshold). The CDR contains numerous fields including a unique record identifier, serving network identity, subscriber identifiers (e.g., IMSI, MSISDN), service data (start/stop time, data volume, QoS), and charging characteristics. Once generated, the CTF forwards the CDR via the Ga interface to a Charging Data Function (CDF) for further processing. The CDF validates, merges related partial records, and formats the CDR before transferring it to a billing domain system. Its role is critical for Offline Charging (OFC), where billing occurs after service consumption. The architecture ensures a clear separation between the network elements generating usage and the centralized charging system, providing an auditable trail for revenue assurance. CDRs are also used for statistical analysis, fraud detection, and network planning beyond pure billing.

Purpose & Motivation

The CDR exists to provide a standardized, reliable mechanism for service usage metering and billing in telecommunications networks. Prior to its formalization, billing systems were often proprietary and tightly coupled with switches, making multi-vendor interoperability and complex tariff plans difficult. The CDR, as defined in 3GPP standards, solves this by creating an abstract, technology-agnostic record of consumption that can be generated by any compliant network function. This separation allows operators to introduce new services and network elements without overhauling their core billing infrastructure. Historically, its introduction in R99 was pivotal for the packet-switched domain of GSM/GPRS, enabling the billing of data services which have variable parameters unlike traditional voice calls. It addresses the problem of correlating usage from multiple network nodes (e.g., roaming scenarios) into a single, billable event for the subscriber.

What changed in its specifications

The latest release-to-release comparison of specifications that define CDR. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 22.115Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 22.115: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 22.115 →

Technology family

Charging architecture · Core Network

  1. R99 CDR, CGF
  2. Rel-5 OCS
  3. Rel-6 ABMF, BD, CDF, CTF, EBCF, OCF, OFCS, RF, SBCF
  4. Rel-8 IMS-GWF
  5. Rel-15 CCS, CHF
  6. Rel-16 CEF

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 sources

Documented changes in 16 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.

R99 introduced

Introduced in R99 (release dating of the term; no individual change cited).

Rel-6 specification text

TS 32.298 appears for the first time in Rel-6, specifying CDR parameters, abstract syntax and encoding rules for all 3GPP CDR types, with the Ga and Bx interfaces carrying CDRs and CDR files.

  • “The present document specifies the CDR parameters, the abstract syntax and encoding rules for all the CDR types that are defined in the charging management TSs” TS 32.298 v6.9.0
  • “For each party to be charged for parts of or all charges of a chargeable event a separate CDR shall be generated” TS 32.298 v6.9.0
Rel-7 specification text

CDR content and generation rules changed: e.g. Direct Tunnel, CGI/SAI and RAI changes now add a 'List of Traffic Data Volumes' container to the CDR, and PoC CDR fields were updated.

  • “When the SGSN establishes or removes a Direct Tunnel between the RNC and the GGSN a "List of Traffic Data Volumes " container shall be added to the CDR.” TS 32.251 v7.8.0
  • “A change in the CGI/SAI shall result in a "List of Traffic Data Volumes" container being added to the CDR” TS 32.251 v7.8.0
  • “Add User Participating Type and Participants Group to PoC CDR and Remove Participants involved from PoC CDR” TS 32.298 v7.5.0
Rel-8 specification text

CDR generation was extended in Rel-8 to EPC/IP-CAN bearers: new SGW-CDR and PGW-CDR types, CDR open/close triggers for S-GW, P-GW and MME changes, and IMS CDR handling updated for SCC AS.

  • “SGW-CDR S-GW (IP-CAN bearer) generated – CDR” TS 32.251 v8.16.0
  • “Start of IP-CAN bearer. Upon encountering this event, a new CDR for this IP-CAN bearer is created” TS 32.251 v8.16.0
  • “SGSN to MME. The IP-CAN bearer CDR is closed in SGSN upon encountering this trigger.” TS 32.251 v8.16.0
Rel-9 specification text

CDR content and generation rules were extended in Rel-9: user CSG information changes now add containers to the CDR, and Emergency Indicator and RTTI parameters were added to IMS CDRs.

  • “A change in user CSG information shall result in a "List of Traffic Data Volumes" container being added to the CDR” TS 32.251 v9.13.0
  • “Emergency Indicator introduction in P-CSCF CDR” TS 32.298 v9.23.0
  • “CDR parameter for RTTI support in IMS offline charging” TS 32.298 v9.23.0
Rel-10 specification text

CDR content was extended in Rel-10: new CDR fields for Machine Type Communication, an Emergency Indicator in the P-CSCF CDR, and a corrected MT-LR CDR aligned with TS 23.271.

Rel-11 specification text

CDR content and generation were extended in Rel-11: new TRF CDR for offline charging, ePDG/MME-related CDR generation, Status field in IMS CDRs, and a loopback indicator in BGCF CDRs.

Rel-12 specification text

Rel-12 adds CDR types and parameters for TDF and ePDG (TDF-CDR, ePDG-CDR, TDF session and ABC handling in a single CDR) and closure triggers for them.

  • “TDF-CDR TDF generated CDR” TS 32.251 v12.13.0
  • “a single CDR is defined to handle both TDF session and ABC information when both are to be used.” TS 32.251 v12.13.0
  • “If both an IPv4 and an IPv6 address of the ePDG is available, the ePDG shall include the IPv4 address in the CDR.” TS 32.298 v12.16.0
Rel-13 specification text

CDR content and triggers were extended in Rel-13: new CP data transfer CDR parameters (SCEF, MME), TWAG-CDR support, and CDR closure triggers for MO exception data and multi-access PDN connections.

  • “5.1.2.4 CP data transfer domain CDR parameters” TS 32.298 v13.12.0
  • “MO exception data counter receipt in the S-GW: This event closes the CDR. A new one is opened if the IP-CAN bearer is still active.” TS 32.251 v13.6.1
  • “If both an IPv4 and an IPv6 address of the TWAG is available, the TWAG shall include the IPv4 address in the CDR.” TS 32.298 v13.12.0
Rel-14 specification text

CDR generation rules were extended: CDR content now covers Presence Reporting Area inactivity and 3GPP PS Data off status triggers, and CDR parameter bindings now map Information Elements as well as AVPs.

  • “change of UE presence in a Presence Reporting Area(s), Serving PLMN Rate Control, APN Rate Control, change of 3GPP PS Data off Status) shall result in a set of” TS 32.251 v14.4.0
  • “the Presence Reporting Area(s) is set to inactive by the serving node are received.” TS 32.251 v14.4.0
  • “Table 6.5.1 describes the mapping of the Information Element, AVP and CDR parameter of ePDG-CDR, TWAG-CDR, SGW-CDR, PGW-CDR and TDF-CDR” TS 32.251 v14.4.0
Rel-15 1 CR

Rel-15 adds the converged-charging CHF CDR, with rules for opening, closing and partial records and new CHF-specific CDR parameters, and extends the CDR specification beyond offline charging only.

  • “A CHF CDR shall be opened when the CHF receives Charging Data Request[Initial].” TS 32.255 v15.5.0
  • “This clause contains the description of each field of the CHF CDRs which are common to all CHF CDRs” TS 32.298 v15.12.0
  • Introduction of CHF CDR generation for SMSF TS 32.274CR0056
Rel-16 1 CR

Rel-16 changed CDR content and generation: a new CHF CDR for the exposure function northbound API, an I-SMF change CDR trigger, CDR handling for ATSSS, and corrections to CHF CDR parameters.

Rel-17 2 CRs

CDR content and generation were extended in Rel-17: new CHF CDR types and fields (IMS, Edge Computing, 5G ProSe, CIoT, GERAN/UTRAN) and updated CDR handling for converged charging.

  • Add Edge Computing related CHF CDR(s) definition and ASN.1 format TS 32.298CR0903
  • Addition of the IMS Charging in the CHF CDR TS 32.298CR0922
  • “A CHF CDR shall be opened when the CHF receives Charging Data Request [Initial].” TS 32.260 v17.5.0
Rel-18 2 CRs

Rel-18 extends CDR content and handling: invocation timestamp, TSN, satellite access/backhaul charging information and triggers added to CHF CDRs, plus inter-CHF CDR information and an Individual Partial record mechanism.

  • “a new CDR shall be opened for each Charging Data Request [Initial, Update, Termination], charging information shall be added and the CDR shall then be closed.” TS 32.298 v18.10.0
  • Add the support of 5G satellite access charging to CHF CDR TS 32.298CR0986
  • Addition of inter-CHF CDR information TS 32.255CR0511
Rel-19 2 CRs

CDR content and triggers were extended in Rel-19: new charging information for ranging, sidelink positioning, 5GS LCS and ProSe relay, and a corrected CHF CDR open/close trigger.

  • “Partial CDRs may be closed upon reception of a Charging Data Request[Update] message, which is sent by the network entity to the CHF.” TS 32.260 v19.3.0
  • Add charging information to CDR for Ranging and Sidelink Positioning TS 32.298CR1022
  • Add charging information for UE-satellite-UE charging to CHF CDR TS 32.298CR1042
Rel-20 3 CRs

Rel-20 adds new CDR parameters in TS 32.298 for QoS report enhancement, multi-modality service charging and host PLMN ID under INS, and corrects CHF CDR trigger and CauseForRecClosing descriptions.

  • Add CDR parameters to support charging aspects of QoS report enhancement TS 32.298CR1070
  • Add CDR parameters to support charging aspects of multi-modality service TS 32.298CR1071
  • Add CDR parameters of host PLMN ID under INS case TS 32.298CR1079

Defining Specifications

3GPP specifications that define or reference CDR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.115 vj11 3GPP Charging and Billing Service Aspects Rel-19 read
TS 22.121 v531 Virtual Home Environment Service Requirements Rel-5 read
TS 22.234 vd10 3GPP-WLAN Interworking Index Specification Rel-13 read
TR 22.950 vj00 Feasibility Study on Priority Service Rel-19 read
TS 22.976 3GPP TS 22.976 R99 read
TS 23.039 v500 SMSC to SME Interface Protocols Rel-5 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.125 v700 Flow Based Charging Architecture Rel-7 read
TS 23.140 v690 MMS Stage 2 & 3 Specification Rel-6 read
TS 23.167 vk10 IMS Emergency Services Rel-20 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.222 vk10 Common API Framework (CAPIF) Rel-20 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.682 vj30 Architecture for MTC and SCEF Enhancements Rel-19 read
TS 23.815 v500 IMS Charging Implications Rel-5 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.802 vc10 II-NNI Traversal Scenario Determination Rel-12 read
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TS 28.203 vi10 Charging management Rel-18 read
TS 28.204 vi11 Charging management Rel-18 read
TR 28.816 vh00 Charging for 5G Cellular IoT Rel-17 read
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18 read
TS 28.849 vj10 CAPIF Phase2 Charging Study Rel-19 read
TS 28.891 vk00 CAPIF Converged Charging Study Rel-20 read
TS 28.893 vk00 ISAC Charging Study Rel-20 read
TS 29.333 vj00 MRFC-MRFP Mp Interface Protocol Rel-19 read
TS 29.421 v810 IMS Interworking with External IP Networks Rel-8 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.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.296 vj00 Online Charging System (OCS) Architecture 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.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.825 va00 Rc Reference Point Study for ABMF Rel-10 read
TR 32.846 vh00 Charging for ProSe in 5GS Rel-17 read
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14 read
TS 32.869 vf00 Diameter Overload Control for Charging Interfaces Rel-15 read
TS 33.849 ve00 3GPP Privacy Principles and Guidelines Rel-14 read