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

Glossary term · Core Network

CP function

Control Plane Function

Core Network →

CP function is a node with a Control Plane function supporting one or more PFCP entities, identified by a Node ID (FQDN or IP address), and a key element in separating control and user planes in 3GPP core networks.

Introduced
Rel-14
Where
Core Network › Evolved Packet Core
Specifications
2 specs
CP function Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Control Plane (CP) function is a logical node in the 3GPP core network architecture that handles control plane signaling and management functions. It is defined in the context of the Packet Forwarding Control Protocol (PFCP) as specified in 3GPP TS 29.244. The CP function supports one or more PFCP entities, which are responsible for establishing, modifying, and deleting sessions on the user plane. The CP function is identified by a Node ID, which can be either a Fully Qualified Domain Name (FQDN) or an IP address, ensuring unique identification within the network.

In the 5G System architecture, the CP function typically corresponds to the Session Management Function (SMF) or the Control Plane Function of the Serving Gateway (SGW-C) and Packet Data Network Gateway (PGW-C) in 4G. These functions communicate with the User Plane Function (UPF) or SGW-U/PGW-U via the PFCP protocol over the N4 interface (in 5G) or Sxb/Sxc interfaces (in 4G). The CP function is responsible for session management, IP address allocation, policy enforcement, and charging. It also interacts with other core network functions such as the Access and Mobility Management Function (AMF), Policy Control Function (PCF), and Network Exposure Function (NEF) to orchestrate services.

The CP function's architecture is based on the control and user plane separation (CUPS) principle, which allows independent scaling and evolution of control and user planes. This separation enhances flexibility, as the CP function can be centralized while user plane functions are distributed closer to the edge. The CP function uses PFCP to instruct the UPF on how to handle user traffic, including packet detection, forwarding, and QoS enforcement. The Node ID is used in PFCP association setup and session establishment procedures to identify the CP function and its peer UPF.

Key components of the CP function include the PFCP entity, which manages PFCP sessions and node associations, and the Node ID, which is a unique identifier for the CP function. The CP function also maintains state information for sessions and handles error conditions and recovery procedures. It may support multiple PFCP entities for redundancy or load balancing. The CP function's role is critical for network slicing, as it can allocate resources and enforce policies per slice.

The CP function continues to evolve with 5G-Advanced and 6G, incorporating new capabilities such as enhanced session management for edge computing, network data analytics, and AI-driven control. Its identification via Node ID remains fundamental for interoperability and management.

Purpose & Motivation

The CP function was introduced to enable the separation of control and user plane in 3GPP core networks, a concept known as CUPS (Control and User Plane Separation). Prior to CUPS, network elements like the SGW and PGW combined both control and user plane functions, leading to scalability and flexibility limitations. The CP function allows operators to scale control and user planes independently, deploy user plane functions closer to the edge for low latency, and centralize control for efficient management.

The motivation for CUPS and the CP function stems from the need to handle increasing mobile data traffic and diverse service requirements. By separating the control plane, operators can introduce new services and policies without upgrading user plane hardware, and can optimize user plane placement for latency-sensitive applications. The CP function also facilitates network slicing by allowing per-slice control plane instances.

The CP function, identified by a Node ID, solves the problem of uniquely identifying control plane nodes in a multi-vendor, multi-domain environment. The use of FQDN or IP address as Node ID ensures compatibility with existing IP-based networks and DNS systems. This standardization enables seamless interoperability and efficient PFCP association management, which is essential for the reliable operation of 4G and 5G networks.

What changed in its specifications

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

TS 29.244Rel-18 → Rel-19

Rel-19 adds MPQUIC-based steering for multi-access PDU sessions and SMF restoration with alternative-SMF handling. It also adds RTP header handling rules, Media over QUIC payload handling, and N6 delay measurement between UPF and endpoints.

Full comparison in TS 29.244 →

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-15 1 change
  • Usage reports queried by the CP function TS 29.244CR0095
Rel-17 1 change
  • UE IP allocation in CP function with SSET and MPAS TS 29.244CR0599

Defining Specifications

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

SpecificationTitleRelease
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