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.
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 →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 →Technology family
Charging architecture · Core Network
- R99 CDR, CGF
- Rel-5 OCS
- Rel-6 ABMF, BD, CDF, CTF, EBCF, OCF, OFCS, RF, SBCF
- Rel-8 IMS-GWF
- Rel-15 CCS, CHF
- Rel-16 CEF
- OFCS decomposed into CDF
“The Offline Charging System (OFCS) is a grouping of charging functions used for offline charging. It collects and processes charging events from one or more CTFs, and it generates CDRs for subsequent offline downstream billing processes.” TS 32.240
- OFCS decomposed into CGF (not stated verbatim in the specifications)
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 6 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.
TS 23.125 v6.8.0 introduces the OFCS as part of Flow Based Charging, specifying its addresses, per-PDP-context reporting and its role as the offline charging system alongside the OCS.
- “The Offline Charging System is specified in TS 32.240 [3].” TS 23.125 v6.8.0
- “There may be several OFCSs in a PLMN. To allow for this case, OFCS addresses” TS 23.125 v6.8.0
- “For each PDP context, there shall be a separate OCS request/OFCS reporting” TS 23.125 v6.8.0
The Offline Charging System (OFCS) is specified for the first time in the PCC architecture, with its own functional entity, the Gz reference point to the PCEF, and OFCS address provisioning from the PCRF.
- “The Gz reference point resides between the PCEF and the OFCS.” TS 23.203 v7.14.1
- “The addresses provided by the PCRF shall have a higher priority than the pre-configured ones.” TS 23.203 v7.14.1
- “6.2.6 Offline Charging System (OFCS)” TS 23.203 v7.14.1
The PCRF may now provide charging information with OFCS/OCS addresses to the PCEF, overriding predefined addresses and superseding the primary and secondary OFCS/OCS addresses in the charging characteristics profile.
- “the PCRF may provide Charging information containing OFCS and/or OCS addresses to the PCEF defining the offline and online charging system addresses respectively” TS 23.203 v8.15.0
- “the charging information supersedes the Primary OFCS/OCS address and Secondary OFCS/OCS address in the charging characteristics profile” TS 23.203 v8.15.0
Rel-9 adds PCRF-controlled reporting of user CSG information change to the OFCS, via the new CSG-Information-Reporting AVP, with a level of detail requested by the PCRF.
- “The reporting of User CSG information to the OFCS shall be done on the level of detail as requested by the PCRF” TS 23.203 v9.14.0
- “it is sent from the PCRF to the PCEF to request the PCEF to report the user CSG information change to the OFCS” TS 29.212 v9.19.0
OFCS offline charging is extended to the TDF: a new Gzn reference point between TDF and OFCS, and PCRF-provided OFCS/OCS addresses and CSG reporting now apply to the TDF as well as the PCEF.
- “The Gzn reference point resides between the TDF and the OFCS.” TS 23.203 v12.11.0
- “Upon the initial interaction with the TDF, the PCRF may provide Charging information containing OFCS and/or OCS addresses to the TDF” TS 23.203 v12.11.0
The PCRF may now provide CSG-Information-Reporting AVPs throughout the IP-CAN/TDF session lifetime, not only at establishment, to request CSG change reports to the OFCS.
- “throughout the lifetime of the IP-CAN/TDF session, to request the PCEF/TDF to report the user CSG information change” TS 29.212 v15.9.0
- “NOTE: OFCS can be seen as a special deployment of CCS.” TS 32.240 v15.5.0
Defining Specifications
3GPP specifications that define or reference OFCS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |