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

Glossary term · Management

OFCS

Offline Charging System

Management →

OFCS is a core network function that collects and processes charging data records after a service session for billing, enabling post-paid billing without real-time credit control.

Introduced
Rel-6
Where
Core Network › Evolved Packet Core
Specifications
13 specs
Also in
Services
OFCS Description Purpose What changed Neighbours Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define OFCS. 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 23.060Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.060 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-6 Initial

Introduced the standardized Offline Charging System architecture for 3GPP networks. Defined the core components: Charging Trigger Function (CTF), Charging Data Function (CDF), and Charging Gateway Function (CGF). Established the Rf (CDF) and Ga (CGF) reference points, using Diameter for transport, to support charging for PS domain, IMS, and other services.

Defining Specifications

3GPP specifications that define or reference OFCS, 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 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.125 v700 Flow Based Charging Architecture Rel-7 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19 read
TS 29.219 vj00 Sy Reference Point Stage 3 Specification Rel-19 read
TS 29.817 vc10 Study on XML-based Rx interface for PCC Rel-12 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19 read
TS 32.820 v801 Study on Evolved 3GPP Charging Architecture Rel-8 read
TS 32.869 vf00 Diameter Overload Control for Charging Interfaces Rel-15 read