Gateway GPRS Support Node

Description

The Gateway GPRS Support Node (GGSN) is a fundamental component of the General Packet Radio Service (GPRS) and Universal Mobile Telecommunications System (UMTS) packet-switched core networks. It serves as the gateway between the cellular network and external packet data networks (PDNs) such as the Internet, corporate intranets, or other service networks. The GGSN is responsible for IP address allocation to mobile stations, session management, policy enforcement, and charging. It was first introduced in 3GPP Release 99 (R99) and has been maintained through subsequent releases, although its role has evolved with the introduction of the Evolved Packet Core (EPC) and 5G Core (5GC).

Architecturally, the GGSN is connected to the Serving GPRS Support Node (SGSN) via the Gn/Gp interface within the same Public Land Mobile Network (PLMN), and to external PDNs via the Gi interface. It maintains Packet Data Protocol (PDP) contexts for each active session, which include the mobile station's IP address, QoS profile, and routing information. When a mobile station requests a PDP context activation, the SGSN forwards the request to the GGSN, which validates the request, allocates an IP address (either dynamically or statically), and establishes the data path. The GGSN also enforces policies such as access control, traffic shaping, and charging based on the subscriber's profile and operator policies.

In terms of functionality, the GGSN performs several key tasks: it acts as the anchor point for mobility, ensuring that the IP address remains stable even when the mobile station moves between SGSNs; it provides packet filtering and firewall capabilities; it supports charging data collection and reporting to the Charging Gateway Function (CGF); and it may implement lawful interception as required by regulatory authorities. The GGSN also supports multiple PDP contexts per user, enabling simultaneous access to different PDNs or different QoS levels.

With the introduction of LTE and the Evolved Packet Core, the GGSN's role was largely taken over by the Packet Data Network Gateway (PGW) and the Serving Gateway (SGW). However, in networks that support interworking between 2G/3G and LTE, the GGSN can be integrated with the SGW/PGW to provide seamless mobility. In 5G, the User Plane Function (UPF) assumes similar gateway responsibilities. Despite these evolutions, the GGSN remains relevant in legacy deployments and in specifications for interworking scenarios.

The GGSN is specified in numerous 3GPP documents, including TS 23.060 (General Packet Radio Service description), TS 29.061 (Interworking between PLMN and PDNs), and TS 32.251 (Charging management). Its continued presence in releases up to Rel-19 indicates its enduring importance in supporting legacy GPRS/UMTS networks and interworking with newer technologies.

Purpose & Motivation

The GGSN was created to provide a gateway between GPRS/UMTS packet-switched networks and external packet data networks, enabling mobile users to access the Internet and other IP-based services. Before GPRS, cellular networks were primarily circuit-switched, limiting data services to low-speed circuit-switched data. The introduction of GPRS in R99 brought packet-switched data, and the GGSN was essential to route packets between the mobile network and external networks, manage IP addresses, and enforce QoS and charging policies.

The GGSN solves several problems: it provides a stable IP anchor point for mobile users, allowing them to maintain their IP address while roaming within the network; it enables differentiated QoS treatment for different traffic types; and it supports charging based on data volume, duration, and QoS. It also allows operators to enforce security and access control policies at the network edge.

Historically, the GGSN was a separate physical node, but with the advent of LTE, its functions were split between the SGW and PGW, and later integrated into the UPF in 5G. However, the GGSN concept persists in interworking scenarios and legacy networks, demonstrating the importance of a centralized gateway for packet data services. Its design influenced the architecture of subsequent core network elements, ensuring continuity of service across generations.