Call Detail Record

Description

A Call Detail Record (CDR) is a standardized, machine-readable log entry that captures the essential parameters of a service usage event within a 3GPP network. It is not a single, monolithic record but a family of record types defined for different services (e.g., MOC, MTC, SMS-MO, SMS-MT, GPRS) and generated by various network functions. The core network elements responsible for session and bearer management, such as the MSC Server for circuit-switched calls, the SGSN and GGSN for GPRS, or the MME, SGW, and PGW in the EPC, are the primary CDR generators. These nodes collect relevant information in real-time during the service instance and format it according to strict specifications defined in 3GPP TS 32.250 and related documents.

The architecture of CDR generation and handling involves several key components. The Charging Trigger Function (CTF), embedded within the network element (e.g., MSC, PGW), detects chargeable events and assembles the relevant charging information into a Charging Data Record. This CDR is then forwarded via a standardized interface (like Ga or Rf) to a Charging Data Function (CDF) in offline charging, or to an Online Charging System (OCS) in real-time scenarios. The CDR itself contains numerous fields, including but not limited to: the served party identifiers (MSISDN, IMSI), serving network identity, date and timestamps for session start and stop, duration, data volumes (uplink/downlink), QoS parameters applied, and identifiers for the specific service used. For roaming scenarios, the CDR will also contain Visited and Home PLMN identifiers.

Its role extends far beyond simple billing. CDRs are the primary source for post-processing systems that perform billing mediation, fraud detection, interconnect settlement with other operators, and detailed traffic analysis. The format and content of CDRs have evolved significantly from simple circuit-switched call logs to complex records encompassing IMS sessions, VoLTE calls, and massive IoT data transactions. The standardization ensures interoperability between network equipment from different vendors and between operators for roaming settlements. The processing of CDRs involves collection, correlation (e.g., matching a start record with its corresponding stop record), formatting for specific billing systems, and secure archival, forming the backbone of the operator's business support system (BSS).

Purpose & Motivation

The CDR exists to provide an accurate, auditable, and standardized record of service usage, which is indispensable for commercial telecommunications operations. Its primary purpose is to enable billing and charging, transforming network resource consumption into billable events for subscribers (postpaid) or for real-time credit control (prepaid). Without CDRs, operators would have no objective mechanism to charge for services, making commercial mobile networks financially unviable. It solves the fundamental problem of metering network usage in a multi-vendor, multi-operator environment.

Historically, the concept predates 3GPP, originating in fixed-line telephony (as referenced by ITU-T). In early mobile networks, the need became even more critical due to mobility, roaming, and a wider array of services beyond simple voice calls. The limitations of proprietary, non-standardized logging mechanisms were significant barriers to interoperability, especially for roaming where the home operator must bill its subscriber based on records generated by a visited foreign network. The 3GPP standardization of CDR formats, generation rules, and transfer protocols provided this essential common language.

Furthermore, CDRs address operational and business intelligence problems beyond pure billing. They provide the raw data for traffic engineering, network planning, fraud management (by detecting unusual calling patterns), and regulatory compliance (e.g., lawful interception logging). The evolution of CDRs to include detailed QoS parameters, location information, and service-specific attributes allows operators to implement sophisticated tariff plans, service quality guarantees, and new business models, making them a cornerstone of both network management and business operations.

Key Features

• Standardized format for interoperability across vendors and operators
• Generation triggered by chargeable events (session start, stop, volume threshold)
• Contains comprehensive service data (identities, timestamps, duration, volumes, QoS)
• Supports both offline (post-event billing) and online (real-time charging) scenarios
• Essential for roaming billing and interconnect settlement
• Serves as primary data source for billing mediation, fraud detection, and traffic analysis

Evolution Across Releases

Defining Specifications