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

Glossary term · Management

OCF

Offline Charging Function

Management →

OCF is the core network function that collects usage data, formats it into Charging Data Records (CDRs), and forwards them for billing post-paid subscribers.

Introduced
Rel-6
Where
Core Network › Legacy Core
Specifications
14 specs
Also in
Services, Management
OCF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Offline Charging Function (OCF) is a fundamental element within the 3GPP Charging System, specifically designed for offline (post-paid) charging scenarios. It operates on the principle of collecting resource usage information after the network resources have been consumed. The OCF resides within the Charging Trigger Function (CTF), which is embedded in various network elements like the SGSN, GGSN, MSC, or IMS entities. When a service is rendered, the CTF detects charging-relevant events and generates Charging Data (CD). This data is then sent via the Rf reference point to the Charging Data Function (CDF). The CDF, a key sub-component of the OCF architecture, is responsible for assembling the received charging events into coherent, session-based Charging Data Records (CDRs). These CDRs are formatted according to 3GPP specifications and contain detailed information such as subscriber identity, service used, data volume, duration, timestamps, and serving network element. The CDF then forwards the completed CDRs via the Ga reference point to the Charging Gateway Function (CGF). The CGF acts as a gateway, performing tasks like CDR buffering, validation, consolidation, and correlation before ultimately transferring the records to the network operator's Billing Domain (BD) for further processing and invoice generation. The entire OCF process is governed by the offline charging architecture defined in 3GPP TS 32.240, ensuring a standardized, reliable, and auditable flow of charging information from network usage to financial settlement. Its role is passive from the service control perspective, as it does not influence the service delivery in real-time but is crucial for the commercial and operational backend.

Purpose & Motivation

The OCF was created to provide a standardized, reliable, and scalable mechanism for operators to charge customers for network and service usage after the fact (post-paid billing). Prior to standardized offline charging, operators relied on proprietary systems within each network element to log usage, leading to inconsistencies, integration challenges, and difficulties in creating unified customer invoices. The 3GPP-defined OCF architecture solves these problems by establishing a clear separation between the network elements that generate charging events and the centralized functions that process them into billable records. It addresses the critical business need for revenue assurance by ensuring that all chargeable events are captured, accurately recorded, and delivered to the billing system. The creation of the OCF in Release 99 was motivated by the transition to packet-switched services (GPRS) and the increasing complexity of service offerings, which required a more robust and flexible charging framework than what was available for legacy circuit-switched voice. It provides the foundation for itemized billing, billing dispute resolution, and financial reporting.

What changed in its specifications

The latest release-to-release comparison of specifications that define OCF. 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.057Rel-4 → Rel-5

Rel-5 added MExE Classmark 4 for CLI Compact Profile devices, covering architecture, security, charging, and capability negotiation.

Full comparison in TS 23.057 →

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
  • OCF decomposed into SBCF
    “The Session Based Charging Function (SBCF) performs session based charging on the bearer level using the CAP interface towards MSC and SGSN, and the Ro reference point towards other network elements.” TS 32.296
  • OCF decomposed into EBCF
    “The Rc reference point allows the interaction between the online charging functions (SBCF, EBCF) and the ABMF to access the subscribers account balance.” TS 32.296
  • OCF counterpart in another generation: CHF
    “For each chargeable event, a matching charging event is formed and immediately sent to its destination, i.e. the CDF in offline charging, the OCF in online charging or CHF in the converged charging.” TS 32.240
  • OCF used together with CTF
    “In online charging, charging events mirroring the resource usage request of the user are transferred from the CTF to the OCF via the Ro reference point.” TS 32.240
  • OCF used together with ABMF
    “The Rc reference point allows the interaction between the online charging functions (SBCF, EBCF) and the ABMF to access the subscribers account balance.” TS 32.296
  • OCF used together with RF
    “The Re reference point allows the interaction between the online charging functions (SBCF, EBCF) and the RF.” TS 32.296
  • OCF part of OCS (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 sources

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

Rel-6 introduced

Introduced in Rel-6 (release dating of the term; no individual change cited).

Rel-11 specification text

OCF gained new account-handling operations toward the ABMF over Rc (reservation, debit, refund, balance query) plus a Sy reference point to the PCRF for policy enforcement.

  • “Sy Reference point for policy enforcement between OCF and the PCRF” TS 32.296 v11.5.0
  • “In this operation the OCF refund monetary units to the subscriber’s account in the ABMF.” TS 32.296 v11.5.0
  • “In this operation the OCF queries the subscriber’s account in the ABMF.” TS 32.296 v11.5.0
Rel-15 specification text

The converged charging architecture now places the Online Charging Function (OCF) inside the Charging Function, alongside the CDF, as part of a four-module charging system.

  • “The Charging Function includes Online Charging Function (OCF) and Charging Data Function (CDF).” TS 32.240 v15.5.0

Defining Specifications

3GPP specifications that define or reference OCF, 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.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19 read
TS 23.125 v700 Flow Based Charging Architecture Rel-7 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider 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.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14 read