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

Glossary term · Management

CTF

Charging Trigger Function

Management →

CTF is the logical function in 3GPP networks that detects chargeable events and generates charging information for the Online and Offline Charging Systems.

Introduced
Rel-6
Where
Services
Specifications
26 specs
Also in
Core Network, Management
CTF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Charging Trigger Function (CTF) is a fundamental architectural element defined within the 3GPP charging framework. It is not a standalone network node but a logical function embedded within various network entities that provide services, such as the Serving GPRS Support Node (SGSN), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW), Session Management Function (SMF), Application Functions (AF), and IP Multimedia Subsystem (IMS) nodes like the Call Session Control Function (CSCF). The primary role of the CTF is to monitor user and network activity in real-time, identify events that are subject to charging based on operator policies, and subsequently trigger the charging process.

Operationally, the CTF works by applying charging rules and filters to the data flows and signaling messages it processes. When a predefined chargeable event occurs—such as the start of a data session, an IMS voice call establishment, SMS delivery, or consumption of a specific volume of data—the CTF captures the relevant details. These details include subscriber identifiers (e.g., IMSI, MSISDN), session identifiers, timestamps, service identifiers, data volumes, duration, and location information. For offline charging, the CTF assembles this information into Charging Data Records (CDRs) or Charging Events and forwards them to the Charging Data Function (CDF) via the Rf reference point. For online charging, the CTF interacts directly with the Online Charging Function (OCF) via the Ro reference point to request quota reservations and report quota consumption in real-time, enabling immediate credit control.

The internal logic of the CTF is governed by charging policies provisioned by the operator, which define what constitutes a chargeable event, the applicable tariffs, and the required granularity of information. Its implementation must ensure reliability and integrity, as the generated data directly impacts billing. The CTF's design separates the service logic of the network node from the charging logic, allowing for flexible and scalable billing models. It supports various charging methods, including event-based charging (e.g., per SMS), session-based charging (e.g., per voice call), and volume/duration-based charging (e.g., for data traffic).

In the broader charging architecture, the CTF acts as the source and initiator of all charging information. Its correct function is paramount for the entire billing chain. It interfaces with the core charging systems (OCS/OFCS) using standardized Diameter-based protocols (Ro and Rf interfaces), ensuring interoperability between different vendors' equipment. The CTF's ability to generate detailed, correlated records for complex services, like those in IMS, is essential for modern convergent billing systems that charge for voice, data, messaging, and content in a unified manner.

Purpose & Motivation

The CTF was created to address the fundamental business need for accurate, reliable, and flexible charging mechanisms in telecommunications networks. Prior to standardized charging architectures, billing systems were often proprietary, tightly coupled with switch vendors, and incapable of supporting new, packet-based services like GPRS and later 3G/4G data. This lack of standardization made it difficult for operators to introduce innovative service plans, perform real-time credit control, or implement complex charging scenarios like those required for IP Multimedia Subsystem (IMS) services.

The introduction of the CTF as part of the 3GPP Charging System in Release 5 and its refinement in subsequent releases provided a clear, standardized model for separating the service delivery functions from the charging functions. This separation allowed network equipment vendors to focus on service delivery while ensuring a consistent, interoperable method for generating billing records. The CTF solves the problem of detecting monetizable events across a heterogeneous network comprising nodes from multiple vendors. It enables operators to implement diverse business models, including prepaid (online charging) and postpaid (offline charging), from a single triggering point.

Furthermore, the evolution towards all-IP networks and rich communication services demanded a more granular and real-time charging capability. The CTF, through its defined interactions with the OCS, enabled immediate credit checks and quota management, which is crucial for preventing fraud in prepaid services and for offering spend-control features to customers. Its design supports the charging of any service detectable by the network, making it a future-proof cornerstone for monetizing everything from basic connectivity to 5G network slices and edge computing applications.

What changed in its specifications

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

TS 24.334Rel-18 → Rel-19

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

Full comparison in TS 24.334 →
TS 32.240Rel-18 → Rel-19

Uncrewed Aerial System Phase 3 added charging support, abbreviations, and definitions. CAPIF Phase 3 added charging support and a new reference point. Energy Efficiency as Service Criteria added clauses for energy KPIs, measurement, and slice charging references.

Full comparison in TS 32.240 →

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
  • CTF used together with CDF
    “In offline charging, the charging event is transferred to the CDF via the Rf reference point. The CDF produces a matching CDR, which is then sent to the CGF via the Ga reference point.” TS 32.240
  • CTF used together with OCF
    “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
  • CTF used together with CHF
    “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 sources

Documented changes in 10 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

The Charging Trigger Function is defined for the first time in TS 32.240, which specifies it as the function that collects chargeable events and forwards charging events to the CDF and OCS.

  • “The Charging Trigger Function (CTF) generates charging events based on the observation of network resource usage” TS 32.240 v6.4.0
  • “charging events mirroring the resource usage request of the user are transferred from the CTF to the CDF via the Rf reference point” TS 32.240 v6.4.0
  • “set of charging information forwarded by the CTF towards the CDF (offline charging) or towards the OCS (online charging)” TS 32.240 v6.4.0
Rel-8 specification text

The CTF text in TS 32.240 was revised: examples moved from GPRS PDP context to IP CAN bearer, a refund-on-failure case was added, and the IMS GWF/S-CSCF CTF text was extended.

  • “the resource usage fails and the CTF may return the failure to the OCS to initiate a refund for the original resource usage.” TS 32.240 v8.6.0
  • “if support for Ro based online charging is required instead of / or in addition to application server or MRFC, a special CTF is” TS 32.240 v8.6.0
  • “whether a session shall be started (session based charging, e.g. IP CAN bearer)” TS 32.240 v8.6.0
Rel-12 specification text

In Rel-12 the CTF's architecture was extended: the CTF Accounting Metrics Collection and Accounting Data Forwarding components may be split between UE and network element, and the CTF is specified for ProSe charging.

  • “In service-specific cases, the CTF functional components of Accounting Metrics Collection and Accounting Data Forwarding are divided between the UE and the network element or service element.” TS 32.240 v12.6.0
  • “For the ProSe Direction Communication Service, the CTF is divided into two functional blocks as described in Annex D of TS 32.240 [1].” TS 32.277 v12.3.0
  • “Refer to TS 32.296 [53] for details on the relation between the network elements (i.e. the embedded online enhanced CTF) and the SBCF or EBCF” TS 32.240 v12.6.0
Rel-14 specification text

CTF-hosting IMS NEs and ASs must, per operator policy, add their address or identifier to initial SIP requests and include the list received in the final response in charging events.

  • “each IMS NE for which the CTF is generating charging events, shall include its own address or specific NE identifier into the initial SIP request” TS 32.240 v14.4.0
  • “The list of addresses or identifiers received in the final response shall be included in the charging event generated by the CTF.” TS 32.240 v14.4.0
Rel-15 1 CR

The CTF's role in 5G service-based converged charging was specified: it interacts with the CHF over Nchf, with Create/Update/Release/Notify operations and event and session charging flows.

  • “The NFs with CTF interact with CHF using Nchf interface for converged online and offline charging.” TS 32.290 v15.7.0
  • “The NF (CTF) the CTF generates charging data related to the delivered service and sends the request for the CHF” TS 32.290 v15.7.0
  • Correction on CTF in 5G Charging TS 32.290CR0003
Rel-16 specification text

The CTF's behaviour changed in Rel-16: it now interacts with the CHF over Nchf for offline-only charging as well, gains blocking and non-blocking modes, and reports used units in Charging Data Requests.

  • “The NFs with CTF interact with CHF using Nchf interface for converged charging or offline only charging.” TS 32.290 v16.10.0
  • “The Nchf_OfflineOnlyCharging_Create operation provides means for NF (CTF) to request initial report of service usage.” TS 32.291 v16.17.0
  • “NF (CTF) may use blocking mode instead when risk of quota overdraft is more important than latency.” TS 32.290 v16.10.0
Rel-17 specification text

CTF split into AMC/ADF blocks is extended to 5G ProSe Direct Discovery/Communication over PC5, with ADF in the 5G DDNMF over the new PC3a reference point (TS 23.304).

  • “ADF) function block of the CTF in the 5G DDNMF over the PC3a reference point defined in TS 23.304 [241]” TS 32.277 v17.5.0
Rel-18 specification text

The CTF's behaviour changed: an NF with CTF can connect to one or two CHFs for the same chargeable event, with CTF failure handling and quota requests adapted and new B2B charging interactions added.

  • “One NF with CTF can be connected to one or two CHFs for the same chargeable event.” TS 32.290 v18.10.0
  • “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 v18.10.0
  • “the NF (CTF) collects and reports the charging information per consumer to a consumer CHF (i.e. C-CHF)” TS 32.240 v18.9.0
Rel-19 1 CR

CTF behaviour was extended: the application server is added as a CTF for UE-satellite-UE communication charging, and the CHF's handling of requests from an NF consumer (CTF) was specified, covering timeouts and concurrent quota requests.

  • Add AS as CTF for UE-satellite-UE Communication Charging TS 32.260CR0452
  • “In case a NF consumer (CTF) requires new units to be granted for the same rating group in SCUR charging scenario” TS 32.290 v19.5.0
Rel-20 1 CR

Rel-20 TS 32.290 adds CTF failure handling: when the CHF is unreachable the CTF applies application-level failure handling and may store Charging Data Requests, which are later sent once the connection is re-established.

  • “the CTF uses application level failure handling and may store Charging Data Request(s) or charging information” TS 32.290 v20.0.0
  • Rel-20 CR TS 32.290 Handling of stored charging data requests in CTF and V-CHF TS 32.290CR0256

Defining Specifications

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

SpecificationTitleRelease
TS 24.334 vj00 ProSe Protocols and Procedures Rel-19 read
TR 28.816 vh00 Charging for 5G Cellular IoT Rel-17 read
TS 28.849 vj10 CAPIF Phase2 Charging Study 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.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.276 vj00 VCS Online Charging from Proxy Function 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.291 vk10 5G Charging Service-Based Interface Rel-20 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider 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.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.849 vd00 VoLTE Roaming Charging Scenarios Rel-13 read
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14 read
TS 33.303 vj00 ProSe Security Specification for EPS Rel-19 read