Description
The Local PDN Gateway (L-GW) is a core network user plane function that acts as the gateway between the User Equipment (UE) and a local data network or the internet, but is deployed in a decentralized manner, often at the network edge near the radio base station (e.g., eNodeB in LTE, gNB in 5G). Architecturally, it incorporates the functions of a traditional PDN Gateway (PGW), such as IP address allocation, packet filtering, policy enforcement, and charging, but within a localized scope. In LTE, it is a logical component that can be collocated with the HeNB (Home eNodeB) in a residential or enterprise setting for LIPA, or deployed at a network aggregation point for SIPTO. In 5G, its functions are subsumed by the User Plane Function (UPF) when deployed at the edge, with the Local UPF being the equivalent entity.
How it works depends on the deployment scenario. For Local IP Access (LIPA), the L-GW is integrated with the HeNB Gateway or the HeNB itself. When a UE attaches and requests a LIPA connection, the Mobility Management Entity (MME) selects the collocated L-GW, and user plane traffic is routed directly from the HeNB to the L-GW and then to the local network (e.g., a home or enterprise LAN), without traversing the operator's core network. This provides low latency and offloads local traffic. For Selected IP Traffic Offload (SIPTO), the L-GW is deployed at a network aggregation point (like a regional data center). The MME or SGSN selects this L-GW based on traffic routing policies, allowing specific IP traffic (e.g., internet traffic) to exit to the internet locally, reducing load on the central PGW and core network transport.
Key components and interfaces include the S5/S8 interface (GTP-based) for communication with the Serving Gateway (SGW) in 3GPP architectures, though in localized deployments like LIPA, this path may be internal. It also implements the Gi interface toward the external PDN (Packet Data Network). The L-GW performs per-bearer packet processing, applying Quality of Service (QoS) policies, and interacts with the Policy and Charging Rules Function (PCRF) for dynamic policy control. Its role is critical for enabling edge computing, low-latency applications (like industrial IoT, AR/VR), and efficient traffic management by bringing gateway functions closer to the user.
Purpose & Motivation
The L-GW was created to solve the problems of network congestion, latency, and inefficient routing for local traffic. In traditional mobile architectures, all user plane traffic, even traffic destined for a local network in the same building as the base station, was routed through a centralized PGW deep in the core network. This 'tromboning' effect introduced unnecessary latency, consumed backhaul and core network resources, and was inefficient for bandwidth-intensive or delay-sensitive applications.
The initial motivation in Release 10 was to support residential and enterprise femtocell (HeNB) deployments with Local IP Access (LIPA), allowing UEs to access local resources (e.g., printers, media servers) directly without impacting the macro network. This addressed the limitation of previous femtocell architectures that still backhauled all traffic to the core. Subsequently, the concept was extended to Selected IP Traffic Offload (SIPTO) at the network edge to offload internet-bound traffic, reducing load on central gateways and improving user experience for services like video streaming.
Historically, L-GW paved the way for network edge intelligence and traffic localization. It addressed the growing demand for mobile data and the need for more efficient network architectures. The limitations of a purely centralized gateway model became apparent with the rise of IoT and real-time applications. L-GW, and its evolution into the Local UPF in 5G, directly motivated the shift toward distributed user planes and edge computing, which are foundational to 5G's low-latency and high-efficiency promises.
What changed in its specifications
The latest release-to-release comparison of specifications that define L-GW. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.060 →Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.
Full comparison in TS 23.401 →Technology family
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
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 sourcesDocumented changes in 4 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-10 introduces the L-GW as a local gateway collocated with the HeNB/HNB for LIPA, with defined user-plane handling, Correlation ID, S5 release at handover, and security requirements.
- “The Local IP Access is achieved using a Local GW (L-GW) colocated with the HeNB.” TS 23.401 v10.13.0
- “the L-GW forwards the first packet on the S5 tunnel to the S‑GW to initiate the "Network Triggered Service Request" procedure” TS 23.401 v10.13.0
- “the Local Gateway (L-GW) shall be an optional element. The L-GW shall be tightly integrated with the H(e)NB” TS 33.320 v10.5.0
Rel-11 corrected L-GW functions in 23.401/23.060 (static GW, VPLMN LIPA roaming) and updated 33320 so L-GW connections and IP addresses are tunnelled and assigned via the SeGW.
- “Correction of L-GW functions for 23.401” TS 23.401 v11.11.0
- “LIPA L-GW clarification on static GW and VPLMN LIPA roaming” TS 23.401 v11.11.0
- “Any connection between the H(e)NB/L-GW and the H(e)NB-GW or core network shall be tunnelled through the Backhaul Link.” TS 33.320 v11.6.0
L-GW gains support for SIPTO at the Local Network, both collocated with the (H)eNB/HNB and as a stand-alone GW with S-GW, including L-GW selection, PDN connection re-establishment on handover and bearer restrictions.
- “the (H)eNB shall request using intra-node signalling the collocated L-GW to re-establish the SIPTO at the Local Network PDN connection.” TS 23.401 v12.11.0
- “The Local GW (L-GW) shall reject any UE requested bearer resource modification.” TS 23.401 v12.11.0
- Introduction of Collocated L-GW for SIPTO@LN TS 36.300CR0602
Rel-13 extends L-GW to dual connectivity: LIPA and SIPTO@LN with a collocated L-GW are supported in the MeNB or SeNB, with new L-GW address and correlation signalling.
- “SIPTO@LN with co-located L-GW in the SeNB. For this scenario, only the SCG bearer option is supported for the SIPTO bearer.” TS 36.300 v13.14.0
- “The LIPA function may be supported for the SCG bearer alternative, in the case that the Secondary eNB is a HeNB with a collocated L-GW” TS 23.401 v13.14.0
- “The SeNB supports basic P-GW functions in the collocated L-GW such as support of the SGi interface corresponding to SIPTO@LN;” TS 36.300 v13.14.0
Defining Specifications
3GPP specifications that define or reference L-GW, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 24.008 vk10 | NAS Call, Mobility and Session Procedures | Rel-20 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 read |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 25.467 vj00 | UTRAN Architecture for 3G Home Node B | Rel-19 read |
| TS 33.320 vj00 | H(e)NB Subsystem Security Architecture | Rel-19 read |
| TS 33.545 vk10 | NR Femto Security Architecture | Rel-20 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.413 vj20 | S1 Application Protocol (S1AP) for E-UTRAN | Rel-19 read |
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 read |
| TS 36.875 vd10 | Dual Connectivity Extension Requirements | Rel-13 read |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 read |
| TS 29.274 vk00 | GTPv2-C Control Plane Protocol | Rel-20 read |
| TS 29.303 vk00 | DNS Procedures for EPS and 5G Interworking | Rel-20 read |