CPCN

Control Plane data transfer Charging Node

Management →
Introduced in Rel-17

CPCN is a charging node that collects and processes charging data for control plane data transfers via nodes like the MME and SCEF, enabling accurate billing for services such as IoT data delivery.

Category
Management
Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
3 specs
CPCN Description Purpose Related Classification Detected Changes Specifications

Description

The Control Plane data transfer Charging Node (CPCN) is a specialized charging function introduced in 3GPP Release 17 to handle charging for data transfers that occur over the control plane rather than the traditional user plane. In 3GPP networks, certain services—particularly IoT applications and non-IP data delivery (NIDD)—leverage the control plane for small, infrequent data transmissions to optimize network efficiency and device battery life. The CPCN collects, processes, and forwards charging data records (CDRs) generated by network nodes involved in these control plane data transfers, specifically the Mobility Management Entity (MME), Service Capability Exposure Function (SCEF), and Interworking SCEF (IWK-SCEF).

Architecturally, the CPCN operates within the charging system framework defined in 3GPP specifications, interfacing with network functions via standardized reference points. It receives charging events and session information from MME, SCEF, and IWK-SCEF through the Rf (offline charging) or Ro (online charging) interfaces, depending on the deployment scenario. The CPCN aggregates this data, applies charging policies based on subscriber profiles, service types, and data usage, and generates formatted CDRs for billing systems. It supports both event-based charging (for individual transactions) and session-based charging (for prolonged control plane data sessions), ensuring flexibility for diverse IoT service models.

Key components of the CPCN include the charging trigger function, which detects control plane data transfer events; the charging data processing engine, which applies tariff rules and correlates events from multiple nodes; and the CDR generation module, which produces standards-compliant records for downstream billing. The CPCN also integrates with policy control functions to enforce spending limits and real-time charging controls. Its role is critical in monetizing control plane data services, providing operators with detailed visibility into resource usage for IoT deployments, and ensuring regulatory compliance for charging accuracy.

In operation, when an IoT device initiates a control plane data transfer—for example, sending sensor data via NIDD—the MME or SCEF involved in the transaction generates charging information, including data volume, timestamps, device identifier, and service parameters. This information is sent to the CPCN, which validates the data against subscriber policies, calculates charges based on configured tariffs, and creates a CDR. For online charging, the CPCN may interact with the Online Charging System (OCS) to authorize the transaction in real-time before allowing the data transfer to proceed. This ensures prepaid subscribers do not exceed their limits and enables immediate billing for pay-as-you-go IoT services.

Purpose & Motivation

The CPCN was created to address the charging challenges introduced by control plane data transfer mechanisms in 3GPP networks, particularly for IoT and machine-type communication (MTC) services. Prior to its introduction, charging for data transmitted over the control plane was handled inconsistently or as part of general packet data charging, which lacked the granularity and accuracy needed for IoT-specific billing models. Traditional charging systems were optimized for user plane data (e.g., smartphone internet browsing) and struggled to capture the unique characteristics of control plane data transfers, such as small message sizes, infrequent transmission patterns, and non-IP protocols.

Historically, as 3GPP evolved to support massive IoT deployments in Releases 13-16, features like Control Plane CIoT EPS Optimization and NIDD became essential for efficient IoT communication. However, the charging architecture lagged behind, creating a gap in monetization capabilities. Operators needed a way to bill for these services accurately, whether based on message count, data volume, or event-based triggers. The CPCN fills this gap by providing a dedicated charging node that understands the specifics of control plane data transfers, enabling new revenue streams for IoT services while ensuring fair usage tracking.

The CPCN solves several limitations of previous approaches: it separates control plane charging from user plane charging, allowing tailored tariff models; it supports charging for interworking scenarios (via IWK-SCEF) where IoT devices roam between 3GPP and non-3GPP networks; and it enables detailed charging correlation across MME and SCEF nodes, which is crucial for end-to-end service billing. By standardizing CPCN in 3GPP specifications, the industry ensures interoperability between network equipment and billing systems, reducing integration costs and accelerating IoT service deployment.

Classification

Part ofSCEF
Related approachesIWK-SCEF

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 12 changes

In Release 15, the CPCN (Control Plane data transfer Charging Node) function was newly introduced for the control plane data transfer domain, as specified in TS 32.253. This function defines which nodes, such as the SCEF, IWK-SCEF, and MME, can act as the Charging Trigger Function (CTF) to generate charging data records for control plane data transfer. The release also introduced charging for the NEF's northbound APIs and integrated control plane charging with the 5G System's converged charging architecture using the Nchf service interface towards the CHF.

  • Charging enhancement for eFMSS TS 32.298CR0643
  • Introduce the NAPS API Charging TS 32.298CR0657
  • Enhance UE location description for IMS charging when over WLAN TS 32.298CR0662
  • Introduce new Charging Function record type TS 32.298CR0669
  • Addition of SMS Charging to CHF CDR TS 32.298CR0680
  • Introduction of 5GS for SMS charging via Ro Rf TS 32.298CR0684

+ 6 more changes

Rel-16 11 changes

In Release 16, the CPCN function was enhanced to support converged charging via the NEF interacting with the CHF using the Nchf service, aligning with the 5G System architecture. Key additions included new charging parameters for interworking with EPC, 5WWC, NSM, and enhanced diagnostics for 5G charging. Furthermore, corrections and clarifications were made for AF Charging Identifiers, NEF charging identities, and the inclusion of Rate-Control information and Serving PLMN Rate Control triggers in Charging Data Records (CDRs).

  • Definition of charging parameter for interworking with EPC TS 32.298CR0722
  • Add 5WWC charging information TS 32.298CR0814
  • Introduction of NSM charging information TS 32.298CR0820
  • Add the NS performance and analytics charging parameter TS 32.298CR0825
  • Correction of AF Charging Identifier naming TS 32.298CR0740
  • Correction of missing AF Charging Id in string format TS 32.298CR0821

+ 5 more changes

Rel-17 13 changes

In Release 17, the CPCN function was enhanced to support new charging scenarios for 5G capabilities. Specifically, this included the addition of charging information for 5G LAN, Cellular IoT (CIoT), and 5G Proximity Services (ProSe) into the Charging Data Records (CDRs) generated by the Charging Function (CHF). Furthermore, the release introduced charging for IMS and MMTel converged services and added the Edge Application Server (EAS) ID for Edge Computing charging.

  • Addition of IMS converged charging ASN.1 TS 32.298CR0887
  • Addition of MMTel converged charging ASN.1 TS 32.298CR0888
  • Additional charging information for the 5G LAN charging TS 32.298CR0889
  • Add charging information related to CIoT in CHF CDR TS 32.298CR0890
  • Introduce 5G ProSe charging information to CHF CDR TS 32.298CR0901
  • Introduce 5G ProSe charging to CHF CDR TS 32.298CR0902

+ 7 more changes

Rel-18 20 changes

In Release 18, the CPCN function was enhanced to support charging for new 5G capabilities, including the introduction of charging for Network Slice-Specific Authentication and Authorization (NSSAA) and for the Network Slice Admission Control Function (NSACF). The release also added specific charging identifiers for Standalone Non-Public Networks (SNPN) and Public Network Integrated Non-Public Networks (PNI-NPN) to enable accurate billing for these deployment models. Furthermore, charging support was extended for 5G satellite access and backhaul, as well as for 5G Multicast/Broadcast Services (MBS) supported by the SMF and MB-SMF.

  • Addition of MMS converged charging information TS 32.298CR0920
  • Add Identifier of SNPN for 5G data connectivity charging TS 32.298CR0938
  • Add Identifier of SNPN for 5G connection and mobility charging TS 32.298CR0939
  • Slice-aware charging for Roaming partners TS 32.298CR0945
  • Add identifier for PNI-NPN charging TS 32.298CR0951
  • Introduction of NSACF charging TS 32.298CR0969

+ 14 more changes

Rel-19 14 changes

In Release 19, the CPCN function was enhanced to support charging for new services including AIoT, Avatar communication, and UAS, as well as for new procedures like Ranging and Sidelink Positioning, 5GS LCS, and store-and-forward satellite operations for SMS and UP CIoT. The charging framework was also extended for layer 3 multi-hop ProSe UE-to-Network relay communication and UE-satellite-UE scenarios. These additions introduced new charging information and CDR parameters to the existing Nchf-based converged charging architecture for control plane data transfer.

  • Add charging information to CDR for Ranging and Sidelink Positioning TS 32.298CR1022
  • Rel-19 CR 32.298 Add charging support to AIoT service TS 32.298CR1032
  • Extend CHF-CDR for 5G LCS converged charging TS 32.298CR1034
  • Rel-19 CR 32.298 Charging information for IMS DC application download charging TS 32.298CR1035
  • Rel-19 CR TS 32.298 Add charging information to CDR for 5GS LCS TS 32.298CR1038
  • Rel-19 CR 32.298 Add charging information for store and forward satellite operation of SMS service TS 32.298CR1039

+ 8 more changes

Explore further

Broader topics and technologies where CPCN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 28.816 vh00 Charging for 5G Cellular IoT Rel-17
TS 32.253 vj00 Charging for Control Plane Data Transfer Rel-19
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19