User Plane Entity

Description

The User Plane Entity (UPE) was a core network architectural concept introduced during the 3GPP System Architecture Evolution (SAE) work for Long-Term Evolution (LTE). It was defined as the logical node responsible for all user plane (data traffic) processing related to a User Equipment (UE) in the Evolved Packet System (EPS). The UPE's primary role was to serve as the gateway between the LTE radio access network (E-UTRAN) and external Packet Data Networks (PDNs), such as the internet or IMS services. Architecturally, it was envisioned to combine the functions of mobility anchoring and packet routing/forwarding. It maintained the bearer context for the UE, which included parameters like QoS levels and packet filters, and was responsible for applying corresponding packet forwarding policies.

In operation, the UPE would receive user data packets from the eNodeB via the S1-U interface. It would then inspect these packets, match them against the established bearer contexts, and apply the necessary QoS treatment (e.g., scheduling, marking) before forwarding them towards the destined PDN via the SGi interface. In the reverse direction, it would receive packets from the PDN, determine the correct bearer and associated eNodeB for the target UE, and forward them accordingly. A key aspect of its function was to act as the mobility anchor for inter-eNodeB handovers within LTE; the user plane path would switch between eNodeBs while the UPE endpoint remained stable, ensuring seamless data continuity.

The UPE was a central component in the early, flattened all-IP architecture of the EPC, designed to reduce latency and improve efficiency compared to the 3G UMTS core. However, as the SAE work progressed, the functional decomposition was refined. The responsibilities initially grouped under the UPE were later split into two separate, physically deployable network functions: the Serving Gateway (SGW) and the Packet Data Network Gateway (PGW). The SGW took on the local mobility anchoring and eNodeB interconnection role, while the PGW became the ultimate anchor point for UE mobility and the interface to external networks. Thus, the UPE remains an important historical concept that illustrates the architectural design process leading to the finalized LTE EPC.

Purpose & Motivation

The UPE was conceived to address the limitations of the 3G UMTS core network architecture, which was often perceived as complex and hierarchical, with separate domains for circuit-switched and packet-switched traffic. The primary motivation for SAE and the UPE concept was to define a simplified, high-performance, all-IP core network optimized for packet data to support the high-speed, low-latency promises of LTE radio technology. It aimed to solve problems like network latency, cost of ownership, and scalability for mobile broadband data explosion.

The historical context is the mid-2000s transition from voice-centric 3G to data-centric 4G. Previous approaches, like the GGSN and SGSN in UMTS, involved multiple tunneling protocols and network layers that added processing overhead and latency. The UPE represented a clean-slate design to flatten the architecture, reducing the number of network hops for user data. It aimed to create a single, powerful user plane entity that could efficiently handle packet routing, policy enforcement, and mobility, thereby simplifying network deployment and operation. Its creation was driven by the need for an architecture that could scale linearly with data traffic while maintaining stringent QoS for emerging services like real-time video and gaming.

Key Features

• Logical aggregation of user plane gateway functions
• Mobility anchoring point for intra-LTE handovers
• Packet routing and forwarding between E-UTRAN and PDN
• QoS enforcement based on bearer contexts
• Interface termination for S1-U and SGi reference points
• Evolutionary precursor to the SGW and PGW split

Evolution Across Releases

Defining Specifications