Description
The Charging Function (CHF) is a fundamental component within the 5G Core Network (5GC) architecture, specifically part of the Charging framework. It operates as a producer of charging events, interacting with other Network Functions (NFs) like the Session Management Function (SMF) and Policy Control Function (PCF) via service-based interfaces (e.g., Nchf). The CHF is responsible for collecting usage information, applying charging policies, and generating Charging Data Records (CDRs) or Charging Events. These records are then forwarded to the Charging Data Function (CDF) for long-term storage and eventual processing by the billing system.
Architecturally, the CHF is defined as a standalone Network Function that can be deployed independently, supporting both offline and online charging modes. In online charging, it performs credit control in real-time, granting or denying service units based on a user's account balance and policy rules. This involves direct interaction with the user's balance management system. For offline charging, it collects usage data after the service is rendered, correlating events from multiple NFs to produce consolidated CDRs. The CHF supports a converged charging system, meaning it can handle charging for any service type (e.g., data, voice, IoT, network slicing) through a unified framework.
Key components of the CHF's operation include the Charging Trigger Function (CTF), which is logically embedded within other NFs like the SMF to detect chargeable events, and the Charging Data Function (CDF) for record storage. The CHF itself implements the charging logic, determining tariff times, applying rating, and managing quotas. It uses standardized reference points such as Nchf (for service-based communication with other NFs) and Rf/Ga (for legacy offline/online charging interfaces if needed). Its design is highly flexible, supporting event-based, session-based, and volume-based charging, which is essential for 5G's diverse service offerings like network slicing and edge computing.
The CHF's role is critical for monetizing 5G services. It enables operators to implement sophisticated, real-time charging strategies, such as dynamic pricing, QoS-based charging, and slice-specific billing. By decoupling charging from session management, 5G allows for more agile service deployment and innovative business models, including third-party service charging. The CHF ensures that all network resource usage is accurately measured, rated, and recorded, forming the basis for revenue assurance and customer billing in modern telecom networks.
Purpose & Motivation
The CHF was introduced in 3GPP Release 15 as part of the new 5G Core (5GC) architecture to address the limitations of previous charging systems in 4G EPC. In 4G, charging was tightly coupled with specific network elements like the PGW (via Gy/Gz interfaces), which made it inflexible and difficult to adapt to new services. The 4G charging architecture was primarily designed for traditional mobile broadband, struggling with real-time, service-differentiated charging required for IoT, network slicing, and edge services.
The primary motivation for creating a dedicated CHF was to enable a converged, service-based charging framework that could support the diverse use cases promised by 5G. This separation allows charging logic to be applied independently of the underlying network topology or session state, facilitating innovation. It solves the problem of monolithic charging systems by providing a modular, cloud-native NF that can scale dynamically and integrate with modern IT systems via APIs.
Historically, charging evolved from simple call detail records in circuit-switched networks to more complex data charging in packet-switched networks. The CHF represents the next step, designed for a software-defined, service-oriented core. It addresses the need for real-time charging for on-demand services, support for network slicing where each slice may have a different charging model, and the ability to charge for third-party applications and services directly through the network. This enables new revenue streams and business models essential for 5G's economic viability.
What changed in its specifications
The latest release-to-release comparison of specifications that define CHF. Each summary describes the whole specification, not only this term.
Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.
Full comparison in TS 23.503 →Architecture
Where it sits in the network
- Mobile Network → 5G Core → CHF (Policy & Charging)
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
- CHF part of CCS
“The Converged Charging System (CCS) consists of four distinct modules, namely the CHF, the Account Balance Management Function (ABMF)” TS 32.240
- CHF counterpart in another generation: OCF
“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
- CHF counterpart in another generation: CDF
“The CDRs generation is performed by the CHF acting as a CDF, which transfers them to the CGF.” TS 32.255
- CHF used together with CTF
“The CTF generates charging events towards to the CHF for converged online and offline charging processing.” TS 32.255
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.
The CHF is specified for the first time in Rel-15: it is added to the 5G architecture, with Nchf converged charging behaviour, CHF-CDR generation and CHF selection/discovery.
- Introduce Charging Function in overall architecture TS 23.501CR0793
- Introduce new Charging Function record type TS 32.298CR0669
- “A CHF CDR shall be opened when the CHF receives Charging Data Request[Initial].” TS 32.255 v15.5.0
In Rel-16 the CHF gained CHF-controlled quota management suspend/resume, a revised CHF selection priority order, offline-only charging support, and new CHF CDRs such as AMF CHF CDRs.
- “CHF may decide to authorize the service and suspend the quota management for that Rating Group.” TS 32.255 v16.14.0
- “The CHF selection by the SMF is done at the PDU session establishment, this selection shall be based on the following” TS 32.255 v16.14.0
- “Introduce AMF CHF CDRs” TS 32.298 v16.14.0
In Rel-17 the CHF gained new behaviour: redundant-transmission-aware quota allocation, CHF set and retry handling, and CHF CDR extensions for ProSe, CIoT, edge computing and IMS charging.
- “The CHF can be aware of redundant transmission type (i.e.dual connectivity, redundant transmission on N3/N9 and redundant transmission at transport layer)” TS 32.255 v17.14.0
- “Failover handling indication informs NF Consumer whether alternative CHF is supported.” TS 32.290 v17.8.0
- Add Edge Computing related CHF CDR(s) definition and ASN.1 format TS 32.298CR0903
Rel-18 extends CHF with CHF-to-CHF (consumer/producer) interaction, quota management and failure handling, MVNO A-CHF architectures with N47/N107, and new CHF CDR content.
- “For the communication between consumer CHF and producer CHF, converged charging is supported.” TS 32.290 v18.10.0
- “the N107 reference point is used for the interactions between CHF owned by the MNO and A-CHF owned by the MVNO.” TS 32.255 v18.11.0
- “consumer CHF decides how to handle the charging session with NF (CTF) based on the operator agreement” TS 32.290 v18.10.0
Rel-19 adds CHF Group ID based discovery and selection via UDM charging characteristics and NRF, plus CHF-side behaviour changes such as a new session identifier after inactivity termination.
- “The UDM provided charging characteristics (see annex A) may be used to indicate CHF instance ID(s), CHF set ID(s), CHF Group ID.” TS 32.255 v19.7.0
- “The CHF instance ID(s), CHF set ID(s), CHF Group ID can be used for the NRF based CHF discovery” TS 32.255 v19.7.0
- CHF discovery and selection based on CHF Group ID TS 23.501CR6286
Rel-20 adds CHF behaviour for unreachable CHF handling, storing and resending charging data requests, and inter-CHF request handling when charging sessions cannot be associated or time out.
- “In case the CHF is determined not reachable, the CTF uses application level failure handling and may store Charging Data Request(s) or charging information.” TS 32.290 v20.0.0
- “A Charging Data Request [Update] received by a CHF, which cannot be associated to any existing charging session” TS 32.290 v20.0.0
- “consumer CHF can continue the charging session with NF (CTF) and store the charging information for settlement, and suspend quota management” TS 32.290 v20.0.0
Defining Specifications
3GPP specifications that define or reference CHF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.503 vk30 | 5G Policy and Charging Control Framework | Rel-20 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 |
| TR 28.815 vh00 | Charging Study for Edge Computing | Rel-17 read |
| TR 28.816 vh00 | Charging for 5G Cellular IoT | Rel-17 read |
| TR 28.822 vh00 | Charging for 5G LAN Services Study | Rel-17 read |
| TR 28.827 vi00 | Technical Report on 5G Charging for Roaming Scenarios | Rel-18 read |
| TR 28.840 vi10 | Technical Report | Rel-18 read |
| TS 28.849 vj10 | CAPIF Phase2 Charging Study | Rel-19 read |
| TS 29.507 vk10 | Access and Mobility Policy Control | Rel-20 read |
| TS 29.510 vk10 | NRF Service-Based Interface | Rel-20 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 29.513 vk10 | 5G PCC Signalling Flows | Rel-20 read |
| TS 29.514 vk10 | Policy Authorization Service | Rel-20 read |
| TS 29.525 vk10 | UE Policy Control Service | Rel-20 read |
| TS 29.561 vk10 | 5G Network Interworking Procedures | Rel-20 read |
| TS 29.594 vk00 | 5G Spending Limit Control Service (Nchf) | Rel-20 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | 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.257 vj00 | Edge Computing Charging Management | Rel-19 read |
| TS 32.260 vk10 | IMS Charging Management | Rel-20 read |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 read |
| TS 32.277 vj20 | Charging Management for Proximity Services (ProSe) | Rel-19 read |
| TS 32.279 vj00 | 5G MBS Session Converged Charging | Rel-19 read |
| TS 32.290 vk00 | 5G Charging Service-Based Architecture | Rel-20 read |
| TS 32.291 vk10 | 5G Charging Service-Based Interface | Rel-20 read |
| TR 32.846 vh00 | Charging for ProSe in 5GS | Rel-17 read |
| TR 32.847 vi00 | Technical Report | Rel-18 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.128 vj80 | Lawful Interception Protocols and Procedures | Rel-19 read |
| TS 33.515 vk00 | 5G SMF Security Assurance Specification | Rel-20 read |
| TS 33.928 vj30 | LI ADMF Provisioning Logic for LI Functions | Rel-19 read |