PEC

Post Event Charging

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

PEC is a 5G charging architecture where charging data records are generated and processed only after a service session or event has fully concluded.

Category
Management
Introduced
Rel-16
Where
Management
Also touches
2 segments
Specifications
8 specs
PEC Description Purpose Related Classification Detected Changes Specifications

Description

Post Event Charging (PEC) is a charging paradigm introduced in 3GPP Release 16 as part of the 5G system. It represents a shift from traditional online (OCS) and offline charging, where charging interactions occur during the session. In PEC, the network does not interact with the charging system in real-time during the service delivery. Instead, usage data is collected locally by the network function (e.g., SMF, PCF) serving the user. After the service data session or a specific service event is completed, the network function generates a Charging Data Record (CDR) or a similar usage report. This record is then forwarded to the Charging Function (CHF) for rating and billing in a post-processing manner. The architecture relies on pre-established policies and quotas agreed upon between the network and the CHF before service initiation. These policies define the charging rules, such as flat rates, event-based charges, or volume thresholds, which the network function applies locally. Key components include the PCF for policy control, the SMF for session management and CDR generation, and the CHF which acts as the billing domain. PEC is particularly managed within the Service Based Interface (SBI) framework of the 5G Core, using HTTP/2-based Nchf services. This method reduces signaling load and latency because it eliminates the need for real-time credit checks and quota updates during the session, which is ideal for machine-type communications and other services where immediate billing authorization is not critical.

Purpose & Motivation

PEC was developed to address the limitations of existing online charging systems (OCS) in handling massive numbers of low-cost, low-latency transactions expected in 5G, particularly for Internet of Things (IoT) and massive Machine-Type Communication (mMTC) scenarios. Traditional online charging requires real-time dialogue between network functions and the OCS for quota management and credit control, which introduces signaling overhead and latency that can be prohibitive for services involving billions of small, frequent events. Offline charging, while avoiding real-time interaction, still involves generating detailed records during the session and may not be flexible for new business models. PEC solves this by decoupling charging from the real-time service flow. It allows operators to implement simple, event-based charging models (e.g., per device, per transaction, or flat-rate) efficiently. The motivation stems from the need for scalable and cost-effective charging for 5G verticals like industrial IoT, where devices generate vast amounts of small data transactions. By processing charges after the fact based on pre-agreed policies, PEC reduces network signaling congestion, lowers operational costs, and enables new monetization strategies for high-volume, low-value services.

Classification

Part ofCHF
Related approachesOCSCDR

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 1 change

In Release 16, the Post Event Charging (PEC) function was enhanced to specifically support the reporting of network slice performance and analytics charging information. The Charging Enablement Function (CEF) was defined to generate Charging Data Requests for PEC scenarios, including those for Multi-Operator Core Network (MOCN) performance measurement, which are exchanged with the Charging Function (CHF). Furthermore, corrections and clarifications were made to the procedural flows for PEC to ensure proper operation.

  • Correction of flows for IEC, ECUR and PEC TS 32.274CR0079

Explore further

Broader topics and technologies where PEC plays a role.

Defining Specifications

3GPP specifications that define or reference PEC, 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.203 vi10 Charging management Rel-18
TS 28.204 vi11 Charging management Rel-18
TS 28.849 vj10 CAPIF Phase2 Charging Study Rel-19
TS 32.254 vj21 Charging for Northbound APIs Rel-19
TS 32.256 vj40 5G Connection & Mobility Charging Spec Rel-19
TS 32.274 vj10 SMS Charging Management Specification Rel-19
TS 32.291 vj40 Charging Management: Service-Based Interface Protocol Rel-19
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.