Offline Charging System

Description

The Offline Charging System (OFCS) is a fundamental component of the 3GPP charging architecture, specifically designed for non-real-time billing scenarios. It operates on the principle of collecting detailed usage information from various network elements after a service has been delivered. The primary data unit is the Charging Data Record (CDR), which is generated by Charging Trigger Functions (CTFs) embedded within network nodes like the SGSN, GGSN, P-GW, or S-CSCF. These CTFs detect chargeable events—such as the start, modification, or end of a data session, voice call, or SMS—and compile the relevant information into a CDR. This record contains fields like the subscriber's identity (e.g., IMSI, MSISDN), session details (start/stop times, duration), service identifiers, and data volume consumed.

The architecture of OFCS is defined by the Charging Data Function (CDF) and the Charging Gateway Function (CGF). The CDF receives the charging events from the CTFs via the Rf reference point, which uses the Diameter base protocol with the Diameter Credit Control Application (DCCA). The CDF validates, formats, and assembles these events into complete, consistent CDRs. These CDRs are then transferred to the CGF via the Ga reference point, typically using protocols like FTP or FTPS. The CGF acts as a gateway, performing functions such as CDR buffering, consolidation, correlation (e.g., linking partial records from different nodes for a single session), and error handling before forwarding the finalized CDRs to the operator's Billing Domain (BD) for long-term storage and invoice generation.

OFCS supports multiple service domains, including Circuit Switched (CS) telephony, Packet Switched (PS) data, and IP Multimedia Subsystem (IMS) services, allowing for converged billing. Its role is strictly offline; it does not interact with online account balances or perform real-time credit authorization. This separation from the Online Charging System (OCS) allows for flexible billing models like monthly subscriptions, volume-based tariffs, and detailed itemized billing. The system's design ensures reliability and non-repudiation of charging data, which is critical for operator revenue assurance and regulatory compliance.

Purpose & Motivation

The OFCS was created to address the fundamental business need for accurate, reliable, and detailed billing of telecommunications services in post-paid subscription models. Prior to standardized offline charging, operators relied on proprietary systems that made interoperability complex and multi-vendor network deployments difficult. The 3GPP standardization of OFCS, beginning in Release 6, provided a unified framework for collecting usage data from all network domains, enabling operators to bill for a wide array of services—voice, data, messaging, and multimedia—from a single, consistent platform.

Its creation was motivated by the limitations of real-time charging for all services. While online charging is necessary for prepaid services, it introduces latency and complexity for services where immediate credit control is not required. OFCS solves this by decoupling the billing process from the service delivery path. This allows the network to deliver services without pausing to check credit, improving user experience and network efficiency for post-paid customers. It also enables the generation of detailed, auditable records essential for customer invoices, business intelligence, fraud detection, and regulatory reporting. The system's evolution has been driven by the need to support new services, higher data volumes, and more complex charging scenarios introduced in later 3GPP releases.

Key Features

• Generation of standardized Charging Data Records (CDRs) for all service domains
• Architecture based on Charging Data Function (CDF) and Charging Gateway Function (CGF)
• Utilizes Diameter protocol over the Rf reference point for event collection
• Supports CDR correlation and consolidation for sessions spanning multiple network nodes
• Enables flexible, non-real-time billing models like subscriptions and tiered data plans
• Provides reliable transfer of billing records to the operator's Billing Domain

Evolution Across Releases

Defining Specifications