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

Glossary term · Protocol

PFCP

Packet Forwarding Control Protocol

Protocol →

PFCP is the 3GPP protocol that separates the control and user planes, enabling the control plane to program forwarding rules, QoS policies, and charging instructions into the user plane.

Introduced
Rel-14
Where
Core Network › 5G Core
Specifications
5 specs
PFCP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Packet Forwarding Control Protocol (PFCP) is a key protocol defined by 3GPP for communication between the control plane and the user plane in both the Evolved Packet Core (EPC) and the 5G Core (5GC) network architectures. It operates over the Sx interface (between SGW-C/PGW-C and SGW-U/PGW-U) in EPC and the N4 interface (between SMF and UPF) in 5GC. PFCP is a master-slave protocol where the control plane function (CPF), such as the Session Management Function (SMF), acts as the master node, and the user plane function (UPF), such as a UPF or PGW-U, acts as the slave node. The protocol uses a request-response mechanism, with the CPF sending commands and the UPF executing them and reporting back.

The core function of PFCP is to allow the control plane to remotely manage the behavior of the user plane without being in the data path. This is achieved through the management of Packet Detection Rules (PDRs), Forwarding Action Rules (FARs), QoS Enforcement Rules (QERs), and Usage Reporting Rules (URRs), collectively known as PFCP Association, Session, and Rules. A PDR contains packet matching information (like IP headers and ports) to identify a specific flow. Each PDR is linked to a FAR, which dictates what to do with matched packets (e.g., forward, drop, buffer, or send to the CPF). QERs apply rate policing and marking, while URRs trigger usage reporting for charging.

When a user session is established, the SMF uses PFCP Session Establishment procedures to program these rules into the UPF. As data packets arrive, the UPF's fast-path processing matches them against the installed PDRs and executes the corresponding FARs and QERs. This enables features like uplink classifier, branching point, traffic steering, and QoS enforcement directly in the user plane. PFCP also supports heartbeat mechanisms for node liveness detection and session reporting procedures, where the UPF can inform the CPF of events like usage thresholds being reached or the detection of the start/end of a traffic flow. This clear separation, enabled by PFCP, is the foundation of the Control and User Plane Separation (CUPS) architecture.

Purpose & Motivation

PFCP was created to enable the Control and User Plane Separation (CUPS) architecture, a major evolution in core network design. Traditional network elements like the SGW and PGW were monolithic, combining both control signaling and data forwarding in a single physical or logical node. This tight coupling limited scalability, as control and user plane resources had to scale together, and hindered flexible deployment, as the data plane could not be distributed independently to be closer to users.

The development of PFCP directly addressed these limitations. By defining a standard protocol, it allowed the control plane (responsible for signaling, policy, and session management) to be separated from the user plane (responsible for high-speed packet forwarding). This enables independent scaling of control and user plane resources. Network operators can deploy centralized control functions for efficiency while distributing stateless user plane functions (UPFs) to the network edge for low-latency services. PFCP provides the precise language for the control plane to 'program' the forwarding behavior of the user plane dynamically, which is essential for supporting network slicing, on-demand service creation, and efficient traffic management in modern 5G and advanced 4G networks.

What changed in its specifications

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

TS 23.527Rel-18 → Rel-19

Rel-19 added procedures for UDR restoration during subscriber data migration, AMF resynchronization indication, and multicast MBS session restoration for N3mb path failure.

Full comparison in TS 23.527 →
TS 26.804Rel-18 → Rel-19

Rel-19 adds CMCD reporting, multi-source media delivery, content steering, QoS enhancements, and QUIC-based streaming.

Full comparison in TS 26.804 →

Protocol Stack

Technology family

Core signalling protocols · Core Network

  1. Phase 1 MAP
  2. Phase 2 ISUP
  3. R96 CAP
  4. R99 GTP-C, GTP-U, GTPv1-C
  5. Rel-4 BICC
  6. Rel-5 Diameter, SIP
  7. Rel-8 GTPv2-C
  8. Rel-14 PFCP
  9. Rel-15 HTTP/2 SBI

Also in this family (introduction release not pinned to a single defining specification): INAP, M2PA, SIGTRAN

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 7 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-14 introduced

PFCP is specified for the first time in Rel-14, defining the protocol between control plane and user plane functions of split SGW, PGW and TDF, including its reference points and procedures.

  • “The present document specifies the Packet Forwarding Control Protocol (PFCP) used on the interface between the control plane and the user plane function” TS 29.244 v14.8.0
  • “PFCP shall be used over the Sxa, Sxb, Sxc and the combined Sxa/Sxb reference points.” TS 29.244 v14.8.0
  • “shall utilize PFCP Heartbeat Request and Heartbeat Response messages to detect and handle a peer PFCP entity failure or restart.” TS 23.007 v14.6.0
Rel-15 specification text

PFCP was extended in Rel-15 to the 5G N4 interface alongside Sx, with common PFCP sessions and associations for SMF/UPF, plus new restoration and heartbeat procedures.

  • “The prefix PFCP in message and procedure names is used to indicate that messages and procedures are common and used on Sx and N4 reference point.” TS 29.244 v15.10.0
  • “The CP function controls the packet processing in the UP function by establishing, modifying or deleting PFCP Session contexts” TS 29.244 v15.10.0
  • “an SMF and UPF shall utilize the PFCP Heartbeat Request and Heartbeat Response messages to detect a peer PFCP entity failure or restart” TS 23.527 v15.3.0
Rel-16 1 CR

PFCP gained new procedures in Rel-16: SMF-set redirection of UPF-initiated requests, restoration indication on session re-establishment, recovery timestamp handling, and PFCP association and session release enhancements.

  • “An SMF may redirect a UPF initiated PFCP session related request to another PFCP entity pertaining to the same SMF or to a different SMF” TS 29.244 v16.13.0
  • “the SMF shall include a restoration indication in the PFCP Session Establishment Request message to indicate to the UPF it is for a restoration” TS 23.527 v16.7.0
  • PFCP messages bundling TS 29.244CR0285
Rel-17 1 CR

PFCP was extended in Rel-17 to N4mb for MBS, with standalone PFCP sessions, SMF set takeover and redirection of UPF-initiated requests, and PFCP-based session restoration and FQ-CSID handling.

  • “A PFCP session refers to both Sx and/or N4 sessions, or to an N4mb session.” TS 29.244 v17.10.0
  • “the UPF shall set the SEID field to zero in the header of the PFCP request and include the CP F-SEID” TS 29.244 v17.10.0
  • PFCP Session Set Modification to restore PFCP Sessions TS 29.244CR0544
Rel-18 1 CR

PFCP gained new behaviour in Rel-18, including user plane inactivity timer updates, UE level measurement activation via Trace Information, extended DL buffering control, and session retention/move handling for SMF sets.

  • “the CP function may activate UE level measurement only (i.e. without trace) during a PFCP session establishment or a PFCP session modification procedure” TS 29.244 v18.10.0
  • “When the UP function receives an updated User Plane Inactivity Timer from the CP function, the UP function shall immediately update the PDU Session inactivity timer” TS 29.244 v18.10.0
  • PFCP Association Release procedure with the MPAS feature TS 29.244CR0802
Rel-19 2 CRs

PFCP gained SMF-set restoration behaviour in Rel-19: UPF may move PFCP sessions to an alternative SMF, with sessions excluded from restoration and alternative SMFs provided per PFCP session.

  • “The UPF may send a PFCP Session Report Request message proactively to an alternative SMF in the SMF set” TS 23.527 v19.5.0
  • Providing alternative SMF(s) per PFCP Session TS 29.244CR0911
  • Restore PFCP Sessions at an alternative SMF TS 29.244CR0914
Rel-20 1 CR

PFCP gained node-level mitigation actions: the SMF can provision Node Level Mitigation Actions Rules to the UPF in PFCP Association Setup/Update messages, applied to all PFCP sessions, for abnormal user plane traffic.

  • “the SMF may provision one or more Node Level Mitigation Actions Rules” TS 29.244 v20.1.0
  • “the UPF shall apply the requested mitigation actions for abnormal user plane traffic” TS 29.244 v20.1.0
  • PFCP per Node procedure for SMF to trigger mitigation actions towards UPF on non-PDU session level TS 23.502CR5637

Defining Specifications

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

SpecificationTitleRelease
TS 23.527 vk00 5G Restoration Procedures for N4 Interface Rel-20 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TR 29.820 vh00 Study on PFCP Best Practice Rel-17 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read