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.
What changed in its specifications
The latest release-to-release comparison of specifications that define GGSN. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-8 added I-WLAN PLMN selection procedures, USIM list usage, user preferences, EHPLMN handling, and HPLMN steering.
Full comparison in TS 22.234 →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
- GGSN counterpart in another generation: PGW
“the SGSN uses the L-GW address included by HNB in RANAP messages as the GGSN/PGW address to be used” TS 23.060
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 15 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.
Introduced in R96 (release dating of the term; no individual change cited).
The GGSN is specified for the first time in Release 99 specs (TS 23.060, 29.060, 29.061) as the gateway to external PDNs, handling PDP context creation, address allocation and GTP tunnelling.
- “The Gateway GPRS Support Node (GGSN) is the node that is accessed by the packet data network due to evaluation of the PDP address.” TS 23.060 v3.17.0
- “it is the responsibility of the GGSN to allocate and release the dynamic PDP address” TS 23.060 v3.17.0
- “The GGSN creates a new entry in its PDP context table and generates a Charging Id.” TS 23.060 v3.17.0
GGSN behaviour was corrected and extended in Rel-4: Update PDP Context Response handling was clarified, the GGSN control-plane address must not change, and the GGSN's role in PDP context creation and relocation was specified.
- GGSN address for control plane must not be changed in "Update PDP Context Response" TS 29.060CR268r1
- Correction/Clarification of GGSN handling of Update PDP Context Response TS 29.060CR194
- “The new entry allows the GGSN to route PDP PDUs between the SGSN and the external PDP network, and to start charging.” TS 23.060 v4.11.0
In Rel-5 the GGSN gained IPv4/IPv6 dual-address handling in GTP, new session-handling rules for Create PDP Context, and IMS-related policy-control and P-CSCF discovery functions.
- “an IPv4/IPv6 capable GGSN shall include IPv6 addresses in the fields GGSN Address for Control Plane and GGSN Address for user traffic” TS 29.060 v5.14.0
- “The GGSN shall support IPv6 addresses and protocol for IMS signalling and IMS bearers.” TS 29.061 v5.9.1
- “The GGSN shall support DiffServ edge functionality.” TS 23.207 v5.10.0
GGSN gained MBMS handling (authorisation toward BM-SC, MBMS Notification Request, MBMS context handling), plus new Gmb interface, SBLP policy enforcement, and dual IP version address handling in Rel-6.
- “an MBMS capable GGSN shall initiate the authorisation procedure towards the BM-SC as outlined within TS29.061 [27]” TS 29.060 v6.21.1
- “the GGSN shall authorize the PDP context activation/modification messages that are subject to service based local policy by sending an authorization request to the PDF” TS 23.207 v6.6.0
- Removal of the GGSN address for Contorol Plane in the Delete MBMS Context Request TS 29.060CR485
GGSN behaviour changed in Rel-7: it handles MS Info Change Reporting, network-requested bearer control (BCM), and Gx-based PCC policy enforcement in place of Go/SBLP.
- “If the MS Info Change Reporting mechanism is to be started or stopped for this subscriber, then the GGSN shall include the MS Info Change Reporting Action IE” TS 29.060 v7.17.0
- “The GGSN sends an Initiate PDP Context Activation Request message to the SGSN to initiate the Secondary PDP Context Activation Procedure for network requested bearer control.” TS 29.060 v7.17.0
- “When Gx is enabled the GGSN shall handle Create PDP Context Requests as specified in 3GPP TS 29.212 [75].” TS 29.061 v7.12.0
GGSN behaviour changed in Rel-8: the GGSN gained MS Info Change Reporting and MBMS IP multicast signalling, the P-GW/GGSN was added in TS 23.060 text, and IPv6 autoconfiguration was limited to stateless.
- “The MS Info Change Reporting Action IE is used by the GGSN to enable and disable the MS Info Change Reporting mechanism.” TS 29.060 v8.16.0
- “the GGSN shall inform the SGSN that an IP multicast based user plane is available for the MBMS session” TS 29.060 v8.16.0
- “To indicate to the MS that stateless address autoconfiguration shall be performed, the GGSN shall leave the M‑flag cleared in the Router Advertisement messages.” TS 29.061 v8.12.0
GGSN behaviour was extended in Rel-9: IPv4v6 dual-address PDP types, CSG information change reporting, emergency traffic blocking and RADIUS/Diameter re-authorization for deferred IPv4 address allocation.
- “If the CCRSI bit field is set to 0 or the Extended Common Flags IE is not included in the message, the GGSN shall assume” TS 29.060 v9.14.0
- “The PDN GW/GGSN shall block any traffic that is not from or to addresses of network entities” TS 23.060 v9.14.0
- “the GGSN may intiate RADIUS re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation” TS 29.061 v9.16.0
GGSN gained APN-congestion overload control with a GGSN Back-Off Time indication to the SGSN, plus IPv6 prefix delegation (DHCPv6 server role) and updated PDP type cause handling.
- “the GGSN may include the GGSN Back-Off Time IE to indicate the time during which the SGSN should refrain from sending subsequent PDP Context requests” TS 29.060 v10.12.0
- “When performing overload control the GGSN rejects PDP context requests.” TS 23.060 v10.14.0
- “The GGSN acts as the DHCP server and fulfils the role of a "Delegating Router" according to RFC 3633 [105].” TS 23.060 v10.14.0
GGSN behaviour changed in Rel-11: it can request user location from the SGSN via Update PDP Context Request (RetLoc), and it interacts with the PCRF to deliver location and time zone information.
- “The GGSN shall include the Extended Common Flags IE and set the RetLoc (Retrieve Location) bit field to 1 if it requests the SGSN” TS 29.060 v11.11.0
- “The GGSN may interact with PCRF (refer to TS 23.203 [88]), e.g. to deliver User Location Information and/or UE Time Zone Information” TS 23.060 v11.12.0
- Providing Serving Network Information to the GGSN TS 29.060CR0902r2
GGSN behaviour changed in Rel-12: GTP now handles per-PDN-connection MS Info Change Reporting with Linked NSAPI, and the GGSN/P-GW gains P-CSCF restoration and APCO-based authentication handling.
- “then the GGSN shall include the MS Info Change Reporting Action IE in the message and shall set the value of the Action field appropriately.” TS 29.060 v12.9.0
- “then the GGSN/P-GW shall act as specified in 3GPP TS 23.380 [95], clause 5.” TS 29.061 v12.12.0
- Introduction of Operator Group GGSN TS 23.060CR1779
GGSN behaviour changed in Rel-13: it sets the Delay Tolerant Connection Indication for delay-tolerant PDN connections, handles MS Info Change Notification per PDN connection, and supports holding procedures after a power-saving rejection.
- “If the PDN connection is "Delay Tolerant", the GGSN shall set the DTCI (Delay Tolerant Connection Indication) bit of the Extended Common Flags II to 1.” TS 29.060 v13.7.0
- “The GGSN shall consider that the SGSN supports the MS Info Change Notification procedure per PDN connection upon receipt of an MS Info Change Notification Request” TS 29.060 v13.7.0
- “then the GGSN re-attempts the same procedure after it receives the indication that the is UE available for end to end signalling” TS 23.060 v13.8.0
GGSN behaviour was extended in Rel-14: Non-IP PDP type support with a GGSN-to-AS PtP tunnel, and 3GPP PS Data Off support indication and charging reporting.
- “the GGSN shall include the 3GPP PS Data Off Support Indication in the Create PDP Context Response PCO if it supports the 3GPP PS Data Off feature” TS 23.060 v14.8.0
- “the GGSN/P-GW shall forward the received data to the AS over the Gi/SGi PtP tunnel associated with the GTP-U tunnel” TS 29.061 v14.4.0
- GGSN selection for DECOR at PDP Context Activation TS 23.060CR2013
GTP behaviour of the GGSN changed: IMSI or IMEI(SV) is now included in Update PDP Context Request and checked by the GGSN, and IPv4/IPv6 address handling between SGSN and GGSN was revised.
- “The IMSI, if available, should be included and the GGSN should use the IMSI to verify if the Update PDP Context Request message is received for the right UE context.” TS 29.060 v15.6.0
- “The IMEI(SV) should be included if the IMSI is not available and the GGSN should use the IMEI(SV) to verify” TS 29.060 v15.6.0
- IP addressing between IPv4/IPv6 capable SGSN and GGSN TS 29.060CR1064
Defining Specifications
3GPP specifications that define or reference GGSN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TR 21.978 v300 | CAMEL Control of VoIP Services Feasibility Study | R99 read |
| TS 22.234 vd10 | 3GPP-WLAN Interworking Index Specification | Rel-13 read |
| TR 22.945 v300 | Fax Services Guidance for GSM/UMTS | R99 read |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.125 v700 | Flow Based Charging Architecture | Rel-7 read |
| TS 23.141 vj00 | Presence Service Stage 2 Architecture | Rel-19 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 read |
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 read |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 read |
| TS 23.228 vk10 | IP Multimedia Core Network Subsystem | Rel-20 read |
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 23.327 vd10 | 3GPP-WLAN Mobility Stage 2 Description | Rel-13 read |
| TS 23.802 v700 | Enhanced End-to-End QoS Architecture | Rel-7 read |
| TS 23.815 v500 | IMS Charging Implications | Rel-5 read |
| TR 23.923 v300 | Mobile IP+ Feasibility Study for UMTS/GPRS | R99 read |
| TR 23.976 vj00 | Push Service Requirements Analysis | Rel-19 read |
| TR 23.979 vj00 | PoC over 3GPP Systems Architectural Requirements | Rel-19 read |
| TR 23.981 vj00 | IPv4 IMS Interworking and Migration Study | Rel-19 read |
| TS 24.228 v590 | IP Multimedia Call Control Signaling Flows | Rel-5 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 26.237 vj00 | IMS for PSS and MBMS Control | Rel-19 read |
| TS 26.346 vj30 | MBMS User Services Specification | Rel-19 read |
| TR 26.944 vj00 | QoE, ESQoS and SQoS metrics for 3G multimedia services | Rel-19 read |
| TR 26.946 vj00 | MBMS User Services Overview | Rel-19 read |
| TS 27.060 vj00 | TE-MT Interworking for Packet Domain | Rel-19 read |
| TS 28.702 vj00 | Core Network NRM IRP Information Service | Rel-19 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.119 vj00 | GTP for GLR in 3GPP Networks | Rel-19 read |
| TS 29.199 | 3GPP TS 29.199 | R96 read |
| TS 29.281 vj20 | GTPv1-U Protocol Specification | Rel-19 read |
| TS 31.111 vj40 | 3GPP TS 31111 vj40: USIM Application Toolkit | Rel-19 read |
| TS 31.112 v800 | USAT Interpreter System Architecture and Functionality | Rel-8 read |
| TS 32.101 vj00 | PLMN Management Principles and Requirements | Rel-19 read |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |
| TS 32.252 vc00 | 3GPP WLAN Interworking Charging | Rel-12 read |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.278 vj00 | Monitoring Events Offline Charging Specification | Rel-19 read |
| TS 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 read |
| TS 32.622 vb10 | Generic Network Resources NRM | Rel-11 read |
| TS 32.632 vb00 | Core Network Resources NRM | Rel-11 read |
| TS 32.732 vb00 | IMS Network Resource Model Information Service | Rel-11 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 32.833 vb00 | Fixed-Mobile Convergence Management Study | Rel-11 read |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 read |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 read |
| TS 33.141 vj00 | Security for Presence Service (Ut reference point) | Rel-19 read |
| TS 33.203 vk00 | IMS Security Features and Mechanisms | Rel-20 read |
| TS 33.822 v800 | Inter-Access Mobility Security Architecture | Rel-8 read |
| TS 33.863 ve20 | Security for Battery-Efficient IoT Device to Enterprise | Rel-14 read |
| TS 33.978 v800 | Early IMS Security Interim Solution | Rel-8 read |
| TS 43.064 vj00 | GPRS Radio Interface Lower-Layer Functions | Rel-19 read |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 read |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 read |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 read |
| TS 52.402 vj00 | GSM Performance Management Measurements | Rel-19 read |