Description
The User Plane Gateway (UPGW) is a core network architectural component defined within the 5G system framework. It functions as a dedicated user plane entity that handles the forwarding, routing, and processing of user data packets. Architecturally, the UPGW is part of the User Plane Function (UPF) concept but is specifically highlighted in early 5G studies (e.g., TR 38.801, TR 38.912) as a potential gateway point for traffic. It interfaces with the Radio Access Network (RAN) via the N3 interface and with the data network via the N6 interface, operating under the control of the Session Management Function (SMF) through the N4 interface.
Its operation involves packet inspection, buffering, and QoS enforcement based on policies provided by the control plane. The UPGW can apply traffic steering rules, perform deep packet inspection for service-aware routing, and support features like uplink classifier and branching point functions as defined for the UPF. It is a key enabler for local breakout, allowing traffic to be routed to local data networks or edge computing applications without traversing the central core, thereby reducing latency.
In the context of network slicing, the UPGW can be instantiated as part of a specific network slice to provide isolated user plane resources tailored to a service's requirements, such as enhanced Mobile Broadband (eMBB) or Ultra-Reliable Low-Latency Communications (URLLC). Its deployment can be centralized or distributed at the network edge, facilitating multi-access edge computing (MEC) scenarios. The UPGW's role is integral to achieving the 5G goals of flexible, software-defined networking and efficient resource utilization.
Purpose & Motivation
The UPGW was introduced to address the need for a more flexible and scalable user plane architecture in 5G networks, moving beyond the monolithic Gateway GPRS Support Node (GGSN) and Packet Data Network Gateway (PGW) of previous generations. Traditional 4G EPC architectures tightly coupled control and user plane functions, limiting deployment flexibility and making it difficult to optimize for diverse service requirements like low latency or high bandwidth. The drive towards network slicing, edge computing, and service-based architectures necessitated a disaggregated approach.
Its creation was motivated by the requirement to support a wide variety of 5G use cases, from massive IoT to critical communications. By decoupling the user plane, operators can deploy UPGW instances closer to the user at the network edge to minimize latency for applications like autonomous driving or industrial automation. It also enables more efficient traffic routing and processing, allowing for innovative service delivery models. The UPGW concept laid the groundwork for the standardized UPF defined in 5G Phase 1 (Release 15), providing a study baseline for user plane evolution.
Key Features
- User plane traffic forwarding and routing
- Support for local breakout and edge computing
- QoS enforcement and packet marking
- Traffic steering and branching point functionality
- Integration with network slicing for isolated data paths
- Interface with control plane via service-based architecture (N4)
Evolution Across Releases
Initially introduced in study items and technical reports (TR 38.801, TR 38.912) as part of early 5G architecture exploration. It defined the concept of a flexible user plane gateway separate from control functions to enable network slicing and edge service support. The initial capabilities focused on basic packet forwarding and session anchoring.
The UPGW concept was largely absorbed and formalized into the standardized User Plane Function (UPF) within the 5G Core (5GC) architecture. Release 15 specified detailed protocols and interfaces (N3, N4, N6, N9) for the UPF, expanding its role with features like uplink classifier, branching point, and packet inspection.
Defining Specifications
| Specification | Title |
|---|---|
| TS 38.801 | 3GPP TR 38.801 |
| TS 38.912 | 3GPP TR 38.912 |