Policy Control Function

Description

The Policy Control Function is a centralized network function in the 3GPP policy architecture. In the 5G System, it is defined as a core network function that provides policy rules to other functions, including the Access and Mobility Management Function, Session Management Function, and Application Function. The PCF is the service-based successor to the Policy and Charging Rules Function used in earlier 3GPP releases. Its role is to make policy decisions that combine subscriber profile data, service requirements, network slice information, roaming status, and operator policy.

Architecturally, the PCF is typically deployed as a stateless network function in a cloud-native core. It exposes services through the 5G Service-Based Interface, using HTTP/2 and JSON. Common PCF services include Npcf_SMPolicyControl for session policies, Npcf_AMPolicyControl for access and mobility policies, Npcf_PolicyAuthorization for application policy authorization, and Npcf_UEPolicyControl for UE policy delivery. The PCF may retrieve subscription and policy data from a Unified Data Repository, interact with the Network Repository Function for discovery, and communicate with charging functions or an Online Charging System for PCC-related decisions.

The PCF operates by responding to policy association requests. When an AMF registers a subscriber or changes access context, it may request access and mobility policy from the PCF. When an SMF establishes or modifies a PDU session, it requests session-level policies that define QoS, charging, traffic steering, and local breakout behavior. When an AF needs resources for an application, it may request policy authorization through the PCF, either directly or via a Network Exposure Function. The PCF evaluates the request against subscriber entitlements, network slice policies, roaming agreements, and operator rules, then returns policy decisions or triggers notifications when conditions change.

The function matters because it separates policy decision-making from policy enforcement. In earlier packet and IMS architectures, policy control was often distributed or tied to specific gateway nodes. In 5G, the PCF enables centralized, reusable policy logic across multiple network functions and deployment scenarios. It supports network slicing by applying slice-specific policies, enables roaming and non-3GPP access by coordinating AMF and SMF decisions, and allows dynamic QoS and charging control without requiring changes to the transport nodes.

The PCF also supports convergence between policy and charging. It can interact with charging systems to ensure that QoS levels, gating, and session continuity reflect the subscriber balance and service plan. In deployments where online charging is used, the PCF may coordinate with the OCS or Charging Function through Sy-like or service-based charging interfaces. The glossary definition of PCF refers to this logical policy-control function, not to any particular vendor implementation or physical server.

From an implementation perspective, multiple PCF instances can serve different regions, slices, or subscriber groups. Policy data may be preloaded from the UDR or retrieved dynamically. The PCF can maintain policy associations for sessions and subscribers, but it is designed to be scalable and resilient so that policy decisions can be recovered or re-established after failure. This design aligns with the 3GPP goal of a service-based, virtualized core network.

Purpose & Motivation

The PCF exists to provide a centralized, service-based policy decision point for 5G core networks. Earlier policy architectures, especially the PCRF, used point-to-point Diameter interfaces and were closely tied to gateway-based enforcement. That model worked for LTE and IMS, but it was less suitable for cloud-native 5G deployments, network slicing, multiple access types, and dynamic service exposure.

The PCF addresses these limitations by exposing policy services to AMF, SMF, AF, and other functions through the Service-Based Interface. It decouples policy logic from transport nodes, allowing policy rules to be reused across sessions, slices, and access networks. It also supports stateless deployment, horizontal scaling, and integration with the Unified Data Repository, which aligns with 3GPP goals for virtualized and distributed core networks.

Motivation for PCF includes the need to manage complex 5G use cases: enhanced mobile broadband, ultra-reliable low-latency communications, massive IoT, roaming, non-3GPP access, and network slicing. Each scenario may require different QoS, charging, traffic steering, and security policies. The PCF provides a single point for composing these policies based on subscriber profile, network slice, and service context. It also preserves the PCC relationship with charging systems, ensuring that policy and online charging remain coordinated in modern architectures.