Inferensys

Glossary

Control-User Plane Separation (CUPS)

A 5G core network architecture that decouples the control plane functions, which manage sessions and mobility, from the user plane functions, which forward data packets, allowing them to be scaled and placed independently for optimized energy and performance.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
CORE ARCHITECTURE

What is Control-User Plane Separation (CUPS)?

A foundational 5G architecture decoupling session management from data forwarding for independent scaling and placement.

Control-User Plane Separation (CUPS) is a 3GPP-defined architecture that decouples the control plane functions (managing sessions, mobility, and policy) from the user plane functions (forwarding data packets) in the packet core, allowing them to be scaled, placed, and upgraded independently.

By centralizing control logic while distributing user plane nodes closer to the network edge, CUPS enables energy-efficient network slicing by allowing operators to scale down or sleep idle user plane resources without disrupting session state, directly reducing power consumption in the data plane.

ARCHITECTURAL DECOUPLING

Key Architectural Features of CUPS

Control-User Plane Separation (CUPS) fundamentally restructures the 5G core by splitting the control plane from the user plane, enabling independent scaling, placement, and lifecycle management for optimized energy efficiency and performance.

01

Independent Scalability

CUPS allows the Session Management Function (SMF) in the control plane and the User Plane Function (UPF) in the user plane to scale independently based on demand.

  • Control Plane: Scales with signaling load (session creation, mobility events)
  • User Plane: Scales with data throughput (packet forwarding volume)

This prevents over-provisioning of one plane to accommodate the other, directly reducing idle power consumption during low-traffic periods.

02

Geographic Distribution

The UPF can be deployed at the network edge, close to the user, while the SMF remains in a centralized data center. This minimizes backhaul latency and reduces the energy required to transport user data across long distances.

  • Centralized control plane for global policy management
  • Distributed user plane for local breakout and edge computing
  • Enables Edge Slice architectures for latency-sensitive applications
03

Packet Processing Optimization

Decoupling enables the UPF to be implemented on specialized, energy-efficient hardware optimized solely for high-speed packet forwarding.

  • Accelerator Offloading: UPF functions like GTP-U encapsulation can run on FPGAs or SmartNICs
  • Dynamic Voltage and Frequency Scaling (DVFS): Applied independently to UPF workloads based on traffic load
  • Eliminates the overhead of running control plane logic on packet processing nodes
04

Sleep Mode Coordination

CUPS enables precise Sleep Mode Coordination by allowing the control plane to orchestrate power states across distributed user plane instances.

  • The SMF can signal idle UPFs to enter deep sleep states
  • Wake-Up Signal (WUS) mechanisms can reactivate specific UPFs only when sessions require them
  • Enables Cell Discontinuous Transmission (Cell DTX) alignment with core network power states for end-to-end energy savings
05

Slice-Aware Energy Management

CUPS is foundational for Energy-Efficient Network Slicing. Each network slice instance can have its own dedicated or shared UPF instances, managed independently.

  • Slice-Level Energy Models can quantify per-slice power consumption
  • Energy-Aware Slice Selection can steer users to slices with the lowest carbon footprint
  • Enables Slice Remapping to consolidate traffic onto fewer UPFs during low load, allowing others to power down
06

Enhanced Resilience and Fault Isolation

A failure in a UPF instance does not necessarily disrupt control plane functions, and vice versa. This isolation improves overall network resilience.

  • Control plane can rapidly reassign sessions to healthy UPFs
  • Slice Isolation is strengthened by separating control and user plane fault domains
  • Enables hitless software upgrades of the SMF without impacting active user data flows
CUPS ARCHITECTURE

Frequently Asked Questions

Clear, technically precise answers to the most common questions about Control-User Plane Separation in 5G core networks.

Control-User Plane Separation (CUPS) is a 3GPP-defined architectural transformation that decouples the control plane functions (CPFs) from the user plane functions (UPFs) within the packet core, allowing them to be scaled, placed, and managed independently. In a CUPS architecture, the control plane—responsible for session management, mobility, authentication, and policy enforcement—runs on centralized servers, while the user plane—which handles high-speed packet forwarding, classification, and QoS enforcement—can be distributed to the network edge. This separation is achieved by splitting the traditional monolithic gateway (SGW, PGW) into a control plane gateway (SGW-C, PGW-C) and a user plane gateway (SGW-U, PGW-U), connected via the standardized Sx interface using the Packet Forwarding Control Protocol (PFCP). The decoupling means a single control plane instance can manage multiple geographically dispersed user plane nodes, enabling ultra-low latency services by placing UPFs close to end-users while maintaining centralized session control.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.