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

Glossary term · Core Network

PCF

Policy Control Function

Core Network →

PCF is a Policy Control Function, a 3GPP core network function that provides centralized policy rules and supplies AMF, SMF, and application functions with subscriber, session, and network-slice policies.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
77 specs
Also in
Services, Management
PCF Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

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

TS 23.207Rel-6 → Rel-7

Rel-7 replaced PDF/Go/Gq with PCRF-based policy control, added new Gx/Rx interfaces, and introduced PCC terminology.

Full comparison in TS 23.207 →
TS 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →

Architecture

Where it sits in the network

Evolution Lineage

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
  • PCF counterpart in another generation: PCRF
    “policy interactions between PDN GW and PCRF specified in TS 23.402 [26] are replaced by equivalent interactions between SMF+PGW-C and PCF” TS 23.502

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-15 introduced

The PCF is specified for the first time in Rel-15, with policy control for AMF, SMF and AF, UDR/CHF/NWDAF interactions, and the Npcf services and procedures.

  • “The PCF shall be able to provide Access and Mobility Management related policies to the AMF.” TS 23.503 v15.10.0
  • “The PCF is responsible for policy control decisions and flow based charging control functionalities.” TS 29.512 v15.18.0
  • Addition of PCF services Npcf_UEPolicyControl and Npcf_EventExposure TS 23.501CR0904
Rel-16 specification text

In Rel-16 the PCF gained new behaviour: same-PCF selection for PDU sessions sharing a DNN/S-NSSAI combination via the BSF, DNN replacement policies for the AMF, and ATSSS policy provisioning.

  • “the PCF determines whether the same PCF shall be selected for the SM Policy associations to the same UE ID, S-NSSAI and DNN combination” TS 23.503 v16.15.0
  • “The PCF may provide a policy to the AMF to contact PCF for performing DNN replacement of specific DNNs;” TS 23.503 v16.15.0
  • “If the PCF supports the "ATSSS" feature, the PCF may provide PCC rules and/or session rules of ATSSS policy for the MA PDU session” TS 29.512 v16.23.0
Rel-17 1 CR

In Rel-17 the PCF gained new behaviours: it collects NWDAF analytics directly or via DCCF for policy decisions, may subscribe to the UDR for AM Influence data changes, and can select the same PCF across SM associations.

  • “The PCF shall be able to collect network analytic information from the NWDAF directly or via DCCF, if deployed.” TS 23.503 v17.11.0
  • “the PCF may subscribe to the UDR using the Nudr_DataRepository_Subscribe service operation for notifications about AM Influence data changes” TS 29.513 v17.14.0
  • Selecting the same PCF for AMF and SMF TS 23.501CR2644
Rel-18 specification text

In Rel-18 the PCF gained new behaviours, including slice usage control policies, slice replacement triggers, HR-SBO offloading policies, group data rate control, and NWDAF analytics subscriptions for policy decisions.

  • “If a S-NSSAI in subject to network slice usage control, the PCF may provide a Slice Usage Policy information” TS 23.502 v18.14.0
  • “the PCF may provision the Specific Offloading Policy for the current serving VPLMN.” TS 29.512 v18.13.0
  • “The PCF may, at AM Policy Association establishment or modification, subscribe to network analytics related to "Load Level Congestion"” TS 23.503 v18.12.0
Rel-19 specification text

PCF behaviour changed in Rel-19: it provisions Local Offloading Management Policy, PDU Set and data burst information in PCC rules, uses QoS and policy assistance analytics, and handles non-3GPP device identifier updates.

  • “the PCF may provision the Local Offloading Management Policy to the SMF to determine the traffic offloading to the local part of the DN” TS 29.512 v19.7.0
  • “The PCF may use the network analytics related to "QoS and policy assistance" as input to determine the QoS parameters to apply” TS 23.503 v19.8.0
  • “the PCF shall update the PCC rules associated with the Non-3GPP Device Identifier, if any.” TS 23.502 v19.9.0
Rel-20 1 CR

PCF gained new behaviour in Rel-20: subscribing to Energy Consumption information from EIF and making policy decisions on it, plus new analytics subscriptions (traffic pattern, abnormal UP traffic).

  • “the PCF shall include the "polChangeReason" attribute set to "ENERGY_SAVING" and may include the "energyConsInfo" attribute” TS 29.512 v20.1.0
  • “The PCF performs discovery and selection of EIF as defined in clause 6.3.27 of TS 23.501 [2] and subscribes/unsubscribes to Energy Consumption information.” TS 23.503 v20.3.0
  • Defining PCF as NF consumer to EIF service TS 29.566CR0014

Defining Specifications

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

SpecificationTitleRelease
TS 03.071 v890 GSM Location Services Stage 2 R99 read
TS 23.171 v390 LCS Stage 2 for UMTS R99 read
TS 23.207 vj00 End-to-End QoS Framework for GPRS Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.380 vk00 IMS Restoration Procedures Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TR 23.745 vh00 Study on App Layer Support for Factories of the Future in 5G Rel-17 read
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TR 23.764 vh10 Study on V2X Application Layer Enhancements Rel-17 read
TS 23.795 vg10 V2X Application Architecture Study Rel-16 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.502 vk00 Non-3GPP Access Network Discovery and Selection Rel-20 read
TS 24.526 vk00 5GS UE Policies Rel-20 read
TS 24.548 vk10 Network Resource Management - SEAL Protocol Specification Rel-20 read
TS 24.549 vj20 SEAL Network Slice Capability Enablement Protocol Rel-19 read
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19 read
TS 26.501 vk00 5G Media Streaming Architecture Rel-20 read
TS 26.502 vj60 5G Multicast-Broadcast User Services Rel-19 read
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 read
TS 26.517 vj30 5G MBS User Service Protocols Rel-19 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TR 26.803 vh00 5G Media Streaming Extensions for Edge Processing Rel-17 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TR 26.806 vi00 Technical Report on Smartly Tethering AR Glasses Rel-18 read
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19 read
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19 read
TS 26.942 vk00 Sustainable Media Metrics and Architectural Impacts for 5G Rel-20 read
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19 read
TS 27.060 vj00 TE-MT Interworking for Packet Domain Rel-19 read
TS 28.540 vk40 5G Network Resource Model (NRM) Stage 1 Rel-20 read
TS 28.802 vf00 Management Study for 5G Network Architecture Rel-15 read
TR 28.840 vi10 Technical Report Rel-18 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.276 vj00 EPS S101/S121/S103 Interfaces Stage 3 Rel-19 read
TS 29.504 vk10 Nudr Unified Data Repository Services Rel-20 read
TS 29.507 vk10 Access and Mobility Policy Control Rel-20 read
TS 29.508 vk10 Session Management Event Exposure Service Rel-20 read
TS 29.512 vk10 Session Management Policy Control Service Stage 3 Rel-20 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.519 vk10 5G UDR Policy and Application Data Services Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.521 vk10 Binding Support Management Service Rel-20 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.523 vk10 Policy Control Event Exposure Service Rel-20 read
TS 29.524 vk00 5GC to NAS Cause Mapping Specification Rel-20 read
TS 29.525 vk10 UE Policy Control Service Rel-20 read
TS 29.534 vk00 5G Access and Mobility Policy Authorization Rel-20 read
TS 29.543 vk10 Data Transfer Policy Control Services Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TS 29.554 vk10 BDT Policy Control Service Rel-20 read
TS 29.558 vk00 Edge Application Enablement APIs Rel-20 read
TS 29.574 vk10 DCCF Service Based Interface Rel-20 read
TS 29.576 vk10 MFAF Service Based Interface Rel-20 read
TS 29.594 vk00 5G Spending Limit Control Service (Nchf) Rel-20 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read
TS 29.867 vk00 IMS Resiliency Enhancement Study Rel-20 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.290 vk00 5G Charging Service-Based Architecture Rel-20 read
TS 32.899 vf10 5G Charging Architecture Study Rel-15 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.528 vj00 Security Assurance for Policy Control Function (PCF) Rel-19 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read
TS 33.794 vj10 Study on Zero Trust Security Enablers for 5G Rel-19 read
TS 33.836 vg10 Security Study for Advanced V2X Services Rel-16 read
TR 33.847 vh10 5G Proximity Services Security Study Rel-17 read
TS 43.059 vj00 GERAN LCS Stage 2 Specification Rel-19 read