Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

PCC decision

Policy and Charging Control Decision

Core Network →

PCC decision is the policy and charging control rules and attributes provided by the PCF to govern how sessions are treated for QoS, charging, and access control.

Introduced
Rel-7
Where
Core Network › 5G Core
Specifications
3 specs
PCC decision Description Purpose What changed Neighbours Detected Changes Specifications

Description

The PCC decision is a central concept in 3GPP's Policy and Charging Control (PCC) architecture. It represents the output of policy decision-making by the Policy Control Function (PCF) in 5G or the Policy and Charging Rules Function (PCRF) in earlier generations. A PCC decision encompasses a set of rules and parameters that dictate how a service data flow should be handled with respect to policy control (e.g., QoS, gating) and charging control (e.g., online/offline charging). The decision is communicated to enforcement functions such as the Session Management Function (SMF) in 5G or the Policy and Charging Enforcement Function (PCEF) in 4G, which then apply the rules to the user plane traffic.

In the 5G System (5GS), the PCC decision is more granular and can be targeted to different consumers. The PCF can provide a PCC decision for policy and charging control to the SMF, consisting of PCC rules and PDU Session related attributes. It can also provide a decision for access and mobility related control to the AMF, a decision for UE access selection and PDU Session selection related policy to the UE, and a decision for background data transfer policy to the Application Function (AF). This multi-target approach reflects the expanded role of policy in 5G, covering not just session-level QoS but also mobility, UE route selection, and application-specific policies.

The PCC decision is constructed based on various inputs: subscription information from the UDR, application requirements from the AF, network conditions, and operator policies. The PCF evaluates these inputs and generates PCC rules, which are the building blocks of the decision. Each PCC rule contains information such as service data flow filters (to identify the traffic), QoS parameters (e.g., 5QI, ARP, MBR, GBR), charging parameters (e.g., charging key, metering method), and other control information. The decision may also include PDU Session related attributes like the authorized QoS for the session, and for the AMF, access and mobility related policies such as RFSP index or service area restrictions.

Once the PCC decision is made, it is transmitted to the enforcement functions via the appropriate interfaces: N7 (PCF-SMF), N15 (PCF-AMF), N1 (PCF-UE via AMF), and N5 (PCF-AF). The SMF then installs the PCC rules into the UPF, which enforces them on the user plane traffic. The AMF uses the access and mobility policy to control UE registration and mobility. The UE uses the UE policy for access selection and PDU Session establishment. The AF receives background data transfer policies to schedule data transfers. This distributed enforcement ensures that policy decisions are applied consistently across the network.

The PCC decision concept has evolved significantly from its introduction in Release 7. Initially, it was a simple set of PCC rules and IP-CAN bearer attributes provided by the PCRF to the PCEF. Over time, it expanded to include application detection and control (ADC) in Release 11, and with the advent of 5G in Release 16, it was redefined to cover multiple decision types for different network functions. This evolution mirrors the growing complexity of mobile networks and the need for flexible, fine-grained policy control across multiple domains.

Purpose & Motivation

The PCC decision exists to centralize and standardize policy and charging control in mobile networks. Before its introduction, policy control and charging were often handled by separate, proprietary mechanisms, leading to inconsistent enforcement and limited flexibility. The PCC architecture, introduced in Release 7, aimed to unify these functions under a single policy framework, enabling operators to dynamically control QoS, charging, and access based on application requirements and subscriber profiles.

The PCC decision solves the problem of how to translate high-level policy intentions into enforceable rules at the network edge. It provides a structured way for the policy controller (PCRF/PCF) to communicate with enforcement points (PCEF/SMF/UPF) and other consumers (AMF, UE, AF). This separation of decision and enforcement allows for centralized policy management while maintaining distributed enforcement, which is essential for scalability and performance.

Historically, the PCC decision was initially focused on IP-CAN bearer attributes and PCC rules for the PCEF. As networks evolved to 5G, the decision expanded to cover access and mobility, UE policy, and application-specific policies. This reflects the broader role of policy in 5G, where it must support diverse services like URLLC, eMBB, and mMTC, each with different QoS and charging requirements. The PCC decision thus remains a cornerstone of the 5G policy framework, enabling operators to monetize and manage their networks effectively.

What changed in its specifications

The latest release-to-release comparison of specifications that define PCC decision. Each summary describes the whole specification, not only this term.

TS 23.203Rel-16 → Rel-17

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 →
TS 23.503Rel-18 → Rel-19

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 Requests

Specific 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.

Rel-16 1 change
  • Input for PCC decision from NWDAF TS 23.503CR0246
Rel-18 1 change
  • PCC decision based on the input of TSCTSF TS 29.512CR0980

Defining Specifications

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

SpecificationTitleRelease
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.512 vk10 Session Management Policy Control Service Stage 3 Rel-20 read