Description
The Policy Counter is a fundamental concept in 3GPP policy and charging control, introduced in Release 11. It represents a mechanism within the Online Charging System (OCS) or, in later releases, the Charging Function (CHF) to track spending applicable to a subscriber. The policy counter allows the Policy and Charging Rules Function (PCRF) in 4G or the Policy Control Function (PCF) in 5G to make policy decisions based on the subscriber's accumulated usage or spending, enabling use cases such as spending limits, fair usage policies, and tiered services.
In the 3GPP architecture, the Policy Counter is typically implemented in the OCS (for 4G) or CHF (for 5G). The PCRF/PCF can request the status of one or more policy counters from the OCS/CHF via the Sy interface (in 4G) or the N28 interface (in 5G). The OCS/CHF maintains the counters and provides notifications when certain thresholds are reached. The PCRF/PCF can then apply appropriate policy rules, such as blocking or throttling the subscriber's traffic when a spending limit is exceeded.
The Policy Counter is defined in several 3GPP specifications: TS 23.203 (Policy and Charging Control Architecture) for 4G, TS 23.503 (Policy and Charging Control Framework for the 5G System) for 5G, and stage 3 specifications TS 29.213 (Policy and Charging Control signalling flows and QoS parameter mapping), TS 29.219 (Policy and Charging Control: Spending Limit Reporting over Sy reference point), and TS 29.594 (5G System; Spending Limit Control Service). These specifications detail the signaling procedures, message formats, and information elements used to manage policy counters.
How it works: When a subscriber establishes a session, the PCRF/PCF may query the OCS/CHF for the status of relevant policy counters. The OCS/CHF responds with the current counter values and may subscribe to notifications for threshold crossings. As the subscriber uses services, the OCS/CHF updates the counters based on charging events. When a counter reaches a predefined threshold, the OCS/CHF notifies the PCRF/PCF, which then enforces new policy rules. For example, if a subscriber exceeds their monthly data allowance, the PCRF/PCF might reduce the QoS or block further data usage until the next billing cycle.
The Policy Counter is a key enabler for flexible charging and policy integration. It allows operators to offer personalized plans, such as zero-rated services or time-based bundles, and to enforce spending limits in real-time. In 5G, the integration with the CHF (which combines online and offline charging functions) further enhances the capabilities, supporting converged charging and policy control for diverse services like network slicing and IoT.
Purpose & Motivation
The Policy Counter was introduced to address the need for real-time spending tracking and policy enforcement in mobile networks. Before its introduction, policy control and charging were largely separate, making it difficult to apply dynamic policy decisions based on a subscriber's spending or usage. Operators wanted to offer tiered services, spending limits, and fair usage policies that required up-to-date information on subscriber consumption. The Policy Counter provides a standardized mechanism for the PCRF/PCF to query and receive notifications about spending from the charging system, enabling integrated policy and charging control.
In 4G networks, the Sy interface was defined to connect the PCRF with the OCS, allowing the PCRF to request policy counter status and receive notifications. This enabled use cases like spending limits, where the PCRF could block or throttle traffic when a subscriber reached a certain spending threshold. The Policy Counter also supported promotional offers, such as bonus data that could be tracked separately.
With the advent of 5G, the concept evolved to use the CHF and the N28 interface, aligning with the service-based architecture and converged charging. The Policy Counter remains essential for 5G's diverse service offerings, including network slicing, where different slices may have different charging and policy requirements. The evolution from OCS to CHF in Release 20 reflects the ongoing convergence of charging functions in 5G, simplifying the architecture and improving efficiency.
What changed in its specifications
The latest release-to-release comparison of specifications that define Policy counter. Each summary describes the whole specification, not only this term.
NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.
Full comparison in TS 23.203 →Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.
Full comparison in TS 23.503 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference Policy counter, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.203 vk10 | Policy and Charging Control Architecture | Rel-20 read |
| TS 23.503 vk30 | 5G Policy and Charging Control Framework | Rel-20 read |
| TS 29.213 vj30 | PCC Procedures and Flows | Rel-19 read |
| TS 29.219 vj00 | Sy Reference Point Stage 3 Specification | Rel-19 read |
| TS 29.594 vk00 | 5G Spending Limit Control Service (Nchf) | Rel-20 read |