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

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 28 changes

In Release 15, the Charging Enablement Function (CEF) was newly introduced as a specialized function for network slice performance and analytics charging. Specifically, the CEF was defined to subscribe to management services (MnS) or Network Data Analytics Function (NWDAF) services to collect charging information, and to then trigger charging by consuming the Nchf service from the Charging Function (CHF). This enabled converged charging based on performance metrics and analytics for specific network slices.

  • Introduce the Northbound API charging TS 32.240CR0394
  • Introduction of 5G in charging architecture TS 32.240CR0396
  • Introduction of 5G converged charging TS 32.240CR0397
  • Introduction of 5G in charging mechanisms TS 32.240CR0399
  • Introduce the 5G charging in clause 3 TS 32.240CR0401
  • Charging mode clarifications in Converged Charging System TS 32.240CR0402

+ 22 more changes

Rel-16 23 changes

In Release 16, the Charging Enablement Function (CEF) was enhanced to specifically support network slice performance and analytics charging, enabling it to subscribe to performance management services (MnS) and Network Data Analytics services (Nnwdaf). This allowed the CEF to collect charging information based on network slice performance metrics and analytics, and report this information to the Charging Function (CHF) for charging purposes. The release also introduced support for Post Event Charging (PEC) scenarios and clarified the CEF's role in consuming management and analytics services to trigger converged charging.

  • Introduction of AMF in charging architecture TS 32.240CR0409
  • Add offline only charging TS 32.290CR0025
  • Add offline only charging service definition TS 32.290CR0026
  • Add offline only charging service scenario TS 32.290CR0035
  • Correct offline only charging service API name TS 32.290CR0043
  • Add offline only charging service message content TS 32.290CR0052

+ 17 more changes

Rel-17 38 changes

In Release 17, the Charging Enablement Function (CEF) was enhanced to support performance and analytics-based charging for network slices, specifically by enabling subscription to Network Data Analytics (Nnwdaf) services and performance management services. The CEF's role was defined to collect charging information related to network slice performance metrics, such as latency, and trigger charging by consuming Nchf services upon detecting a chargeable event.

  • Add PGW in logical ubiquitous charging architecture- service based interface TS 32.240CR0413
  • Introduction of 5G DDNMF in charging architecture for 5GS TS 32.240CR0429
  • Addition of the 5G LAN service charging TS 32.240CR0434
  • Charging architecture for Local Breakout TS 32.240CR0439
  • Addition of the architecture for 5G LAN charging TS 32.240CR0442
  • Enhance charging architecture for Edge Computing TS 32.240CR0443

+ 32 more changes

Rel-18 41 changes

In Release 18, the Charging Enablement Function (CEF) was enhanced to support new network slice performance and analytics charging, where the CEF subscribes to performance management (MnS) and Network Data Analytics (Nnwdaf) services to collect charging information based on specific network slice performance metrics. This release specifically introduced the CEF's capability to trigger charging for network slice performance and analytics by consuming Nchf services, supporting a Post Event Charging (PEC) scenario.

  • Adding New Consumer for MMS in Charging Architecture TS 32.240CR0446
  • Slice-aware charging for Roaming partners TS 32.240CR0467
  • Add MB-SMF in charging architecture for 5GS TS 32.240CR0470
  • Add charging support for TSN service TS 32.240CR0473
  • Add annex for B2B charging TS 32.240CR0474
  • Update B2B charging principles TS 32.240CR0475

+ 35 more changes

Rel-19 49 changes

In Release 19, the Charging Enablement Function (CEF) was extended to support new charging scenarios, including for Multi-Operator Core Network (MOCN) performance, AIoT services, and disaster roaming. Specifically, the CEF's role as a consumer of performance management services (MnS) was defined for MOCN performance converged charging, subscribing to gNB performance measurements. The release also introduced charging support for new services like UAS, satellite-based MVNO services, and Ranging and Sidelink Positioning, with corresponding additions to data types and OpenAPI extensions.

  • Rel-19 CR 28.201 Add charging architecture for MOCN TS 28.201CR0017
  • Rel-19 CR 28.201 Add charging requirement for MOCN TS 28.201CR0018
  • Rel-19 CR 28.201 Addition of charging information for MOCN TS 28.201CR0023
  • Introduction of GMLC in charging architecture for 5GS TS 32.240CR0491
  • Rel-19 CR 32.240 Add charging support to AIoT service TS 32.240CR0510
  • Rel-19 CR 32.240 CAPIF Logical Charging Architecture TS 32.240CR0511

+ 43 more changes

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