CEF

Charging Enablement Function

Management →
Introduced in Rel-16 Also in: Core Network

CEF is a 5G network function that standardizes and centralizes the exposure of charging-related data and events to external applications via a unified interface.

Category
Management
Introduced
Rel-16
Where
Management
Also touches
1 segments
Specifications
15 specs
CEF Description Purpose Related Classification Detected Changes Specifications

Description

The Charging Enablement Function (CEF) is a service-based network function introduced in 5G System (5GS) architecture to provide a standardized, centralized mechanism for charging enablement. It operates within the 5G Core (5GC) network's management and orchestration domain, specifically as part of the Charging Function (CHF) architecture. The CEF acts as an intermediary that exposes charging-related capabilities and events to external Application Functions (AFs) and other network functions through well-defined service-based interfaces (SBIs), primarily based on HTTP/2 and JSON. Its primary role is to decouple the charging logic from service logic, allowing for more flexible and dynamic charging scenarios.

Architecturally, the CEF interacts with the Charging Function (CHF) to obtain charging data and policies. It provides a northbound interface (Nchf) to external entities, such as Application Functions (AFs) or third-party service providers, enabling them to request charging sessions, receive notifications for charging events, and influence charging decisions. The CEF supports both online and offline charging models. For online charging, it can interact with the Online Charging System (OCS) via the CHF to perform real-time credit control. For offline charging, it can collect and forward charging data records (CDRs) to the Offline Charging System (OFCS).

Key components of the CEF include the Charging Enablement Service, which handles the exposure of charging capabilities, and the Event Exposure Service, which manages subscriptions and notifications for charging-related events. The CEF implements the Nchf_SpendingLimitControl service, allowing AFs to set spending limits for users or services, and the Nchf_ConvergedCharging service, which provides a unified interface for converged charging scenarios. It also supports policy integration, working with the Policy Control Function (PCF) to enforce charging-related policies based on network conditions, user subscriptions, and service requirements.

The CEF's operation involves several steps: first, an external AF subscribes to charging events via the CEF; second, the CEF forwards these subscriptions to the CHF; third, when a charging event occurs (e.g., data usage threshold reached), the CHF notifies the CEF; and finally, the CEF relays the notification to the AF. This enables real-time charging interactions, such as triggering service upgrades or notifying users of usage limits. The CEF also supports batch processing for offline charging, where it aggregates CDRs before forwarding them to the OFCS. Its role is critical in enabling service-based charging, where charging is tailored to specific services, network slices, or quality of service (QoS) levels, facilitating new monetization strategies in 5G networks.

Purpose & Motivation

The Charging Enablement Function (CEF) was introduced in 3GPP Release 16 to address the limitations of previous charging architectures, which were often rigid, vendor-specific, and lacked standardized interfaces for external integration. In earlier generations (e.g., 4G), charging systems were primarily designed for voice and data services, with limited support for dynamic, service-based charging required by 5G use cases like network slicing, IoT, and edge computing. The traditional charging interfaces were not well-suited for real-time interactions with external applications, hindering innovation and the adoption of new business models.

The CEF solves these problems by providing a standardized, service-based interface that decouples charging logic from service logic, enabling more flexible and dynamic charging scenarios. It allows external Application Functions (AFs) and third-party service providers to directly interact with the charging system, facilitating real-time charging, spending limit control, and event notifications. This is particularly important for 5G networks, which support diverse services with varying QoS requirements, such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). The CEF enables operators to monetize these services more effectively by offering tailored charging plans and real-time charging capabilities.

Historically, charging systems evolved from circuit-switched networks to packet-switched networks, but they remained largely isolated from external applications. The CEF represents a shift towards open, programmable charging architectures, aligning with the broader 5G vision of network softwarization and service-based architecture (SBA). By standardizing the exposure of charging capabilities, the CEF reduces integration complexity, promotes interoperability between different vendors' equipment, and accelerates the deployment of new services. It also addresses the need for converged charging, where online and offline charging are unified, supporting both prepaid and postpaid models seamlessly. This evolution is driven by the demand for more agile, customer-centric charging solutions in the era of digital transformation and 5G.

Classification

Part ofCHF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change

In Release 16, the Charging Enablement Function (CEF) was introduced to enable converged charging specifically for network slice performance and analytics. The CEF was defined as a consumer of management services (MnS) from an MnS Producer and analytics services (Nnwdaf) from the NWDAF, subscribing to this information to detect chargeable events and then trigger charging via the Nchf service towards the CHF. Its newly specified capabilities include supporting Post Event Charging (PEC) scenarios and reporting charging information per network slice based on configurable trigger conditions like performance indicator thresholds.

  • Update description of Charging Enablement Function TS 28.201CR0004
Rel-17 3 changes

In Release 17, the CEF (Charging Enablement Function) was updated to act as a consumer of the Nnwdaf_EventsSubscription service from the NWDAF, in addition to its existing role. Furthermore, its NFType value was defined, and the specification for the triggers it uses to invoke charging towards the CHF was corrected.

  • Correction on triggers for CEF based architecture TS 28.202CR0004
  • NFType value for CEF TS 29.510CR0625
  • Updates CEF as NWDAF consumer of Nnwdaf_EventsSubscription service TS 29.520CR0240

Explore further

Broader topics and technologies where CEF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 28.201 vj20 5G Network Slice Performance Analytics Charging Rel-19
TS 28.202 vj00 5G Network Slice Management Charging Rel-19
TS 28.310 vj20 Energy Efficiency Management for 5G Networks Rel-19
TR 28.815 vh00 Charging Study for Edge Computing Rel-17
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18
TS 28.880 vj00 Study on 5G Energy Efficiency & Saving Rel-19
TS 29.510 vj50 NRF Service Based Interface Protocol Rel-19
TS 29.520 vj40 5G Network Data Analytics Services Stage 3 Rel-19
TS 29.552 vj40 5G Network Data Analytics Signalling Flows Rel-19
TS 32.240 vj40 Charging Management Architecture & Principles Rel-19
TS 32.257 vj00 Edge Computing Charging Management Rel-19
TS 32.290 vj50 5G Charging for Service Based Interface Rel-19
TS 32.291 vj40 Charging Management: Service-Based Interface Protocol Rel-19
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19
TR 32.847 vi00 Technical Report Rel-18
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.