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

Glossary term · Management

CGF

Charging Gateway Functionality

Management →

CGF is the network function that collects, correlates, and forwards charging data records from network elements to the billing domain for accurate service billing and accounting.

Introduced
R99
Where
Core Network › Legacy Core
Specifications
35 specs
Also in
Management, Services
CGF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Charging Gateway Functionality (CGF) is a core component within the 3GPP charging architecture, specifically defined for offline charging. It operates as an intermediary between the network elements that generate charging events and the billing system (or billing domain). Network elements, such as the SGSN, GGSN, P-GW, or S-GW, generate raw charging data in the form of Charging Data Records (CDRs) or partial CDRs. These elements send this data to the CGF using standardized interfaces, primarily the Ga reference point. The CGF's primary technical role is to act as a concentrator and mediator. It receives these CDRs, performs correlation if multiple partial records belong to a single service session (e.g., correlating SGSN and GGSN records for a single PDP context), and assembles them into complete, validated CDRs. It also buffers records to ensure reliable delivery, handles failures and retransmissions, and forwards the consolidated CDR files to the billing system via the Bx reference point, typically using protocols like FTP or FTPS.

Architecturally, the CGF can be implemented as a standalone network node or integrated with other charging functions. In early 3GPP releases, it was a distinct logical function. Its internal components include interfaces for Ga and Bx, a CDR processing and correlation engine, persistent storage for buffering, and management functions for monitoring its performance and load. The CGF ensures data integrity and sequence, which is vital for accurate billing. It may also perform format conversion, translating the CDRs from the ASN.1-encoded format used over Ga into a format suitable for the billing domain, such as a comma-separated value (CSV) file or a specific proprietary format.

The CGF's operation is crucial for the offline charging paradigm, where charging information is collected after the service is rendered. It provides a single point of collection for the network, simplifying the billing system's integration. By handling reliability and correlation, it shields the billing domain from the complexities and potential instabilities of the real-time network elements. This separation of concerns allows network elements to focus on service delivery while the CGF manages the charging data logistics. In modern networks, especially with the introduction of 5G and the Charging Function (CHF), the principles of the CGF are embodied within the Charging Trigger Function (CTF) and Charging Data Function (CDF) for offline charging, but the CGF as a standalone gateway concept remains foundational for legacy and convergent billing systems.

Purpose & Motivation

The CGF was created to address the growing complexity of billing in mobile packet-switched networks introduced with GPRS and 3G. Prior to its standardization, network operators faced significant challenges in collecting usage data from multiple, distributed network elements (like SGSNs and GGSNs) reliably. These elements could generate vast amounts of charging data, and a direct, point-to-point connection from each element to the billing system was inefficient, unreliable, and difficult to scale. The billing systems were not designed to handle the potential data loss, network congestion, or the need for correlation of records from different nodes. The CGF solved this by introducing a dedicated gateway function.

Its creation was motivated by the need for a standardized, robust, and scalable intermediary. The CGF centralizes the collection point, allowing network elements to send data to a nearby or logically centralized gateway using a lightweight protocol (like GTP' over Ga). This reduces the load and connection complexity on the billing system itself. It solves the problem of data reliability through buffering and retransmission mechanisms, ensuring that no charging data is lost due to temporary network or billing system failures. Furthermore, it addresses the critical issue of correlation. A single user session (like web browsing) often involves multiple network nodes; the CGF correlates the partial CDRs from these nodes into a single, coherent record that accurately represents the entire service usage, which is essential for correct billing.

Historically, the CGF enabled the commercial viability of data services by providing a dependable mechanism to monetize packet data usage. It separated the transport and mediation of charging data from the actual billing logic, allowing both domains (network and business support systems) to evolve independently. This architectural choice future-proofed the charging infrastructure, supporting the explosion of data services from 2.5G through to 4G and forming the conceptual basis for charging in 5G systems.

What changed in its specifications

The latest release-to-release comparison of specifications that define CGF. Each summary describes the whole specification, not only this term.

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 →
TS 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →

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
  • CGF part of CCS
    “The Converged Charging System (CCS) consists of four distinct modules, namely the CHF, the Account Balance Management Function (ABMF), the Charging Gateway Function (CGF) and the Rating Function (RF).” TS 32.240
  • CGF used together with CDF
    “The CDRs produced by the CDF are transferred immediately to the Charging Gateway Function (CGF) via the Ga reference point. The CGF acts as a gateway between the 3GPP network and the BD.” TS 32.240
  • CGF part of OFCS (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 12 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.

R99 introduced

Introduced in R99 (release dating of the term; no individual change cited).

Rel-6 specification text

Rel-6 specifies the CGF as the function that receives CDRs from the CDF over Ga, stores them, builds CDR files and transfers them to the Billing Domain over Bx, in push or pull mode.

  • “The CGF acts as a gateway between the 3GPP network and the Billing Domain. It uses the Bx reference point for the transfer of CDR files to the BD.” TS 32.240 v6.4.0
  • “The CGF is responsible for persistent CDR storage, for preparing CDR files and transferring them to the BD via the Bx reference point.” TS 32.240 v6.4.0
  • “The Ga is the reference point from the Charging Data Function (CDF) to the Charging Gateway Function (CGF), which is intended for the transport of Charging Data Records (CDRs).” TS 32.295 v6.1.0
Rel-7 specification text

PCRF may now provide CGF/OCS addresses per PDP session to the PCEF (GGSN), superseding the CGF addresses in the charging characteristics profile; the Gz reference point is now between PCEF and CGF.

  • “PCRF may also provide CGF/OCS addresses to PCEF (GGSN) per PDP session.” TS 32.251 v7.8.0
  • “Gz Offline charging reference point between a PCEF and a CGF.” TS 32.251 v7.8.0
Rel-8 specification text

CGF handling was reworked for EPC/PS charging: CDRs from PCN/S-GW/P-GW go to the CGF, CGF address selection follows P-GW/S-GW rules, and the Bp reference point now refers to the Packet Switched CGF.

  • “If the CGF address is configured in the P-GW’s selected charging characteristics behaviour, the P-GW shall apply it for the PGW-CDRs.” TS 32.251 v8.16.0
  • “In the roaming case, or if no CGF address is received from the P-GW, the S-GW shall use the CGF address from its own applied charging characteristics behaviour” TS 32.251 v8.16.0
  • “PCRF may also provide CGF/OCS addresses to P-GW per IP CAN bearer session.” TS 32.251 v8.16.0
Rel-11 specification text

CDR generation towards the CGF now also covers the MME generating S-SMO-CDR and S-SMT-CDR, and the ePDG generating a new ePDG-CDR.

  • “the S-SMO-CDR, S-SMT-CDR by the MME,the SGW-CDR by the S-GW, the ePDG-CDR by the ePDG” TS 32.251 v11.13.0
  • “conditions for adding information to, and closing the ePDG-CDR for generation towards the CGF” TS 32.251 v11.13.0
Rel-12 specification text

The CGF's scope in Rel-12 was updated: the Bw reference point for WLAN CGF was discontinued, and the Bpr (ProSe CGF) and Bsm (SMS CGF) reference points for CDR file transfer were added.

  • “Bpr Reference point for CDR file transfer between ProSe CGF and the BD.” TS 32.297 v12.2.0
  • “Bw Reference point for the CDR file transfer from the WLAN CGF to the BD (discontinued in Release 12).” TS 32.297 v12.2.0
Rel-13 specification text

New reference points Bcp and Bmn were added for CDR file transfer from CP data transfer and Monitoring Event CGF instances to the billing domain, and TWAG-CDRs now go to the CGF.

  • “Bmn Reference point for the CDR file transfer from the Monitoring Event CGF to the BD.” TS 32.240 v13.2.0
  • “Bcp Reference point for the CDR file transfer from the CP data transfer CGF to the BD.” TS 32.240 v13.2.0
  • “closing the TWAG-CDR for generation towards the CGF” TS 32.251 v13.6.1
Rel-15 specification text

Rel-15 adds CGF-specific CDR file transfer reference points to the Billing Domain (5G data connectivity, exposure function, monitoring event) and places CGF as a module of the converged charging system.

  • “Reference point for the CDR file transfer from the 5G Data Connectivity CGF to the BD.” TS 32.297 v15.4.0
  • “the Bx reference point connects the CGF in each network domain, service or subsystem to the Billing Domain.” TS 32.297 v15.4.0
  • “the Charging Gateway Function (CGF) and the Rating Function (RF)” TS 32.240 v15.5.0
Rel-16 specification text

New Bam and Bns reference points were added for CDR file transfer from the 5G connection and mobility CGF and from the Network slice CGF to the Billing Domain.

  • “Reference point for the CDR file transfer from the 5G connection and mobility CGF to the BD.” TS 32.297 v16.2.0
  • “Reference point for the CDR file transfer from the Network slice CGF to the BD.” TS 32.297 v16.2.0
Rel-17 specification text

Rel-17 adds new Bec and Btsn reference points for CDR file transfer from Edge Computing and TSN CGFs to the Billing Domain, and adds CGF deployment options.

  • “Bec Reference point for the CDR file transfer from the Edge Computing CGF to the BD.” TS 32.297 v17.3.0
  • “Btsn Reference point for the CDR file transfer from the TSN CGF to the BD.” TS 32.297 v17.3.0
Rel-18 specification text

New reference points (Bns, Bnsac, Bnssaa) were added for CDR file transfer from the Network slice, NSACF and NSSAAF CGFs to the Billing Domain.

  • “Bnsac Reference point for the CDR file transfer from the NSACF CGF to the BD.” TS 32.297 v18.1.0
  • “Bnssaa Reference point for the CDR file transfer from the NSSAAF CGF to the BD.” TS 32.297 v18.1.0
Rel-19 specification text

Rel-19 adds Store-and-Forward satellite charging, where the MME and SCEF send charging information about S&F satellite access to the CGF or Billing Domain, and MME-CDRs are generated towards the CGF.

  • “the MME onboard/ground sends a charging data request to CGF or Billing Domain with charging information about satellite access running in S&F mode” TS 32.251 v19.0.0
  • “conditions for adding information to, and closing the MME-CDR for generation towards the CGF” TS 32.251 v19.0.0

Defining Specifications

3GPP specifications that define or reference CGF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.682 vj30 Architecture for MTC and SCEF Enhancements Rel-19 read
TS 23.815 v500 IMS Charging Implications Rel-5 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 28.201 vj20 5G Network Slice Performance Analytics Charging Rel-19 read
TS 28.203 vi10 Charging management Rel-18 read
TS 28.204 vi11 Charging management Rel-18 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.253 vj00 Charging for Control Plane Data Transfer Rel-19 read
TS 32.254 vk00 3GPP TS 32.254: Charging for Northbound APIs Rel-20 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.256 vk10 5G Connection and Mobility Charging Rel-20 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.270 vj00 MMS Charging Management Specification Rel-19 read
TS 32.271 vj20 3GPP LCS Charging Management Spec Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.273 vj00 MBMS Charging Management Rel-19 read
TS 32.277 vj20 Charging Management for Proximity Services (ProSe) Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.279 vj00 5G MBS Session Converged Charging Rel-19 read
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read
TS 32.295 vj00 3GPP Charging: CDR Transfer via GTP' Protocol 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.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.632 vb00 Core Network Resources NRM Rel-11 read
TS 32.732 vb00 IMS Network Resource Model Information Service Rel-11 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.825 va00 Rc Reference Point Study for ABMF Rel-10 read