Local Gateway

Description

The Local Gateway (LGW) is a user plane function defined in the 3GPP architecture for traffic offload at the edge of the mobile network. Its primary role is to terminate the user plane path from the Radio Access Network (e.g., eNodeB in LTE) and provide direct local breakout of data traffic to the internet or specific local services. Architecturally, the LGW is typically co-located with or placed in close proximity to the base station (e.g., at a multi-RAT base station or a small cell gateway), forming a local anchor point for user data.

In operation, when a user's data session is eligible for local offload (e.g., accessing the public internet), the core network's control plane (MME, SGSN) establishes a bearer where the user plane path runs between the User Equipment (UE) and the LGW, rather than the traditional central Packet Data Network Gateway (P-GW). The LGW performs key gateway functions locally: it acts as the point of IP address allocation for the UE (using a local IP address pool), performs packet routing and forwarding, enforces local Quality of Service (QoS) policies, and handles charging data generation for the offloaded traffic. It maintains a connection to the central core network for control signaling (e.g., via the SGi interface) to receive policy updates and report charging information.

The LGW is a key component in architectures like Selected IP Traffic Offload (SIPTO) at the local network. It enables low-latency applications and efficient handling of high-volume, best-effort internet traffic. By offloading this traffic, it reduces the load on the mobile backhaul and the central core network elements (P-GW), leading to cost savings and improved scalability. The LGW works in conjunction with control plane entities to ensure seamless mobility; for example, if a user moves out of the LGW's service area, the session may be seamlessly transferred (or 'relocated') to a central P-GW.

Purpose & Motivation

The LGW was created to address the explosive growth of mobile data traffic, particularly bandwidth-intensive but latency-tolerant internet traffic (like video streaming, web browsing). This traffic was causing congestion and scalability challenges in the mobile backhaul and the centralized core network gateways (GGSN/P-GW). Routing all data through a central point was becoming inefficient and costly.

Its development was motivated by the need for network architecture optimization and the emergence of low-latency use cases. By offloading traffic locally, operators could reduce transport costs, improve network performance for local services, and lay the groundwork for edge computing. It solved the problem of inefficient 'tromboning' where local traffic had to travel to a distant central gateway and back. The LGW, as part of SIPTO and later edge computing paradigms, provided a standardized way to decentralize the user plane, bringing content and applications closer to the end-user to enable services like augmented reality, industrial IoT, and real-time gaming.

Key Features

• Local user plane termination and IP anchor point close to the RAN
• Enables Selected IP Traffic Offload (SIPTO) at the local network
• Allocates local IP addresses to UEs from a dedicated pool
• Performs packet routing, forwarding, and QoS enforcement locally
• Generates local charging data records for offloaded traffic
• Supports session continuity mechanisms for mobility events

Evolution Across Releases

Defining Specifications