Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

SGSN

Serving GPRS Support Node

Core Network →

SGSN is the core network node responsible for managing mobility, session management, and authentication for packet-switched data services in 2G/3G GPRS and UMTS networks.

Introduced
R96
Where
Core Network › Legacy Core
Specifications
78 specs
Also in
Services, Radio Access Network, Management, Security
SGSN Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Serving GPRS Support Node (SGSN) is a fundamental core network entity in GSM/GPRS and UMTS networks, dedicated to packet-switched data services. It serves as the central point of control and routing for a mobile subscriber's data session within the network's coverage area. The SGSN's primary roles include mobility management, session management, and user authentication and authorization for packet data access. Physically, it is connected to the Radio Access Network (RAN)—specifically the Base Station Subsystem (BSS) in GSM/GPRS or the Radio Network Controller (RNC) in UMTS—via the Gb or Iu-PS interfaces, respectively. It also connects to the Gateway GPRS Support Node (GGSN) via the Gn interface, which provides the gateway to external packet data networks like the Internet.

From a functional perspective, the SGSN operates by maintaining a context for each attached GPRS/UMTS subscriber. When a mobile station (MS) attaches to the network for packet data services, the SGSN authenticates the user using information from the Home Location Register (HLR) or Authentication Centre (AuC). It then establishes a PDP (Packet Data Protocol) context, which is a logical association between the MS, the SGSN, and the GGSN, defining parameters like the assigned IP address and QoS profile. For mobility, the SGSN tracks the location of the MS at the level of the routing area (a group of cells) and handles routing area updates as the user moves. It routes incoming data packets from the GGSN to the correct RAN element based on the user's current location and routes outgoing packets from the MS towards the GGSN.

The SGSN's architecture includes several key logical components: the mobility management function, which handles attach/detach and location updates; the session management function, which controls PDP context activation, modification, and deactivation; and the packet routing and transfer function. It also performs charging functions, collecting data for billing based on volume or time, and interfaces with charging systems. In UMTS, the SGSN's role expanded to include more sophisticated QoS handling aligned with UMTS bearer services. Throughout its long evolution from Release 99 onwards, the SGSN has been integral to enabling mobile internet access, MMS, and other packet data services before the full migration to LTE/EPC. It represents the core of the packet-switched domain in pre-4G networks, working in tandem with the GGSN to provide a complete data service path.

Purpose & Motivation

The SGSN was created to introduce packet-switched data capabilities into originally voice-centric GSM networks. Before GPRS (General Packet Radio Service), GSM offered only circuit-switched data, which was inefficient for bursty, internet-style traffic. The motivation for the SGSN was to enable efficient, always-on IP-based data services over GSM, leading to mobile email, web browsing, and early mobile applications. It solved the problem of managing mobile subscribers' packet data sessions, including their mobility and authentication, within the cellular network infrastructure.

The historical context is the transition to 2.5G/3G mobile data. The SGSN, alongside the GGSN, formed the GPRS core network, allowing GSM networks to utilize packet switching and share radio resources dynamically among users, dramatically improving data efficiency compared to dedicated circuits. It addressed limitations like the inability to handle IP mobility and session continuity natively. For UMTS, the SGSN evolved to support the new UMTS RAN and enhanced QoS mechanisms, facilitating richer data services. Its enduring presence across many releases underscores its role as the cornerstone of mobile packet data before the clean-slate design of the LTE/EPC, where its functions were redistributed to the MME and S-GW.

What changed in its specifications

The latest release-to-release comparison of specifications that define SGSN. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 23.018Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.018: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.018 →

Evolution Lineage

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
  • SGSN counterpart in another generation: SGW (not stated verbatim in the specifications)
  • SGSN counterpart in another generation: MME
    “3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol"” TS 23.002

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 sources

Documented changes in 18 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.

R96 introduced

Introduced in R96 (release dating of the term; no individual change cited).

R99 specification text

Release 99 specifies the 3G-SGSN for UMTS: it supports the Iu interface, performs authentication, and manages PMM states and the PS signalling connection, alongside the existing GPRS SGSN role.

  • “The SGSN supports GPRS for GSM (i.e., the Gb interface is supported by the SGSN) and/or UMTS (i.e., the Iu interface is supported by the SGSN).” TS 23.060 v3.17.0
  • “The 3G‑SGSN performs the authentication procedure, and the RNC performs the ciphering procedure based on the algorithm for UMTS.” TS 23.060 v3.17.0
  • “The MS and 3G‑SGSN shall enter the PMM‑CONNECTED state when the PS signalling connection is established between the MS and the 3G‑SGSN.” TS 23.060 v3.17.0
Rel-4 1 CR

SGSN behaviour was changed: it now handles Last Known Service Area reporting in MS Information Response, and the CR titles show corrections to SGSN paging and restart handling.

  • “If an Iu connection for MS exist and UTRAN node cannot determine current Service Area and Last Known Service Area is not reported” TS 23.060 v4.11.0
  • “may report Last Known Service Area with an indication of how long has past since the mobile was known to be in the indicated Service Area.” TS 23.060 v4.11.0
  • Removal of an optional IMSI paging after SGSN restart TS 23.007CR007
Rel-5 1 CR

SGSN behaviour was extended in Rel-5: Intra Domain Connection of RAN Nodes to Multiple CN Nodes lets the new SGSN derive the old SGSN from the old RAI and P-TMSI, and user data is restricted during attach and authentication.

  • “If the new SGSN provides functionality for Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the new SGSN may derive the old SGSN” TS 23.060 v5.13.0
  • “the MS and SGSN should not transmit user data during attach and authentication procedures” TS 23.060 v5.13.0
  • IuFlex support for determining old SGSN during handover/relocation TS 23.003CR037r1
Rel-6 specification text

SGSN procedures were extended in Rel-6: network sharing support (stores selected operator identity, may send Reroute Command), IMEISV in Update Location, access-restriction checks, and mandatory serving network identity with new GGSN parameters.

  • “the SGSN may be informed by the RNS about the identity of the selected core network operator when receiving the Attach Request message” TS 23.060 v6.15.0
  • “The SGSN sends an Update Location (SGSN Number, SGSN Address, IMSI, IMEISV) to the HLR. IMEISV is sent if the ADD function is supported.” TS 23.060 v6.15.0
  • “The SGSN shall send the serving network identity to the GGSN.” TS 23.060 v6.15.0
Rel-7 1 CR

SGSN procedures were extended in Rel-7: Update PDP Context Request now carries CGI/SAI/RAI change support indication and NRSN, and the SGSN handles Direct Tunnel re-establishment and Iu connection checks.

  • “NRSN indicates SGSN support of the network requested bearer control.” TS 23.060 v7.11.0
  • “If Routeing Area Update occurs, the SGSN shall determine whether Direct Tunnel can be used based on the received GPRS CAMEL Subscription Information.” TS 23.060 v7.11.0
  • SGSN number to be included in the ATI response TS 23.078CR0807
Rel-8 specification text

The SGSN gained new Rel-8 responsibilities: providing, storing and forwarding the RFSP Index to RNC/BSC, selecting GGSN or PGW, and interworking over the S4 interface as an S4-SGSN.

  • “the SGSN provides the parameter 'Index to RAT/Frequency Selection Priority' to RNC across Iu and to BSC across Gb” TS 23.060 v8.17.0
  • “The Gn/Gp SGSN shall support selection of GGSN and may optionally support selection of PGW.” TS 23.060 v8.17.0
  • “In S4 mode, the SGSN interworks signalling on the S4 interface with Iu/Gb interface signalling.” TS 23.060 v8.17.0
Rel-9 1 CR

The SGSN's handling of the RFSP Index was enhanced: it now stores subscribed and in-use values, may update the in-use value during Routing Area Update, and may take HPLMN input for roamers.

  • “During the Routing Area Update procedure the SGSN may update the RFSP Index value in use and signal the updated value to the RNC across Iu” TS 23.060 v9.14.0
  • “If there is already an emergency bearer activated, the SGSN shall reject any additional PDP context activation request by the MS for emergency services.” TS 23.060 v9.14.0
  • Enhanced handling of RFSP index at the SGSN/MME TS 29.274CR0419
Rel-10 1 CR

SGSN gained APN-based and general NAS congestion control, rejecting MM/SM requests with back-off timers, plus overload throttling of downlink low-priority notifications and new ULI/CSG reporting behaviour.

  • “The SGSN may reject the Session Management (SM) requests from the MS” TS 23.060 v10.14.0
  • “Under general overload conditions the SGSN may reject Mobility Management signalling requests from MSs.” TS 23.060 v10.14.0
  • MME/SGSN overload control by throttling of DL low priority traffic TS 29.274CR0848
Rel-11 specification text

SGSN behaviour changed in Rel-11: congestion control now stores back-off time per MS/APN only for requests without low access priority, and the SGSN must set the Homogenous Support of IMS Voice over PS indication in HSS messages.

  • “The SGSN may store a Session Management back-off time per MS and APN when congestion control is active for an APN” TS 23.060 v11.12.0
  • “the SGSN shall include the "Homogenous Support of IMS Voice over PS Sessions" indication set to "Supported".” TS 23.060 v11.12.0
  • “The SGSN shall make use of this procedure to request to become registered for SMS.” TS 29.272 v11.14.0
Rel-12 1 CR

SGSN behaviour was extended in Rel-12, including SIPTO GW relocation and selection, Implicit Detach timer handling for PSM with Active Time, and periodic RAU timer allocation using the MS-requested value.

  • “When the SGSN decides upon the need for GW relocation, the SGSN deactivates the impacted PDN connections indicating "reactivation requested"” TS 23.060 v12.11.0
  • “When the mobile reachable timer expires and the SGSN stores an Active Time for the MS, the SGSN knows that the MS entered PSM” TS 23.060 v12.11.0
  • Gateway selection by SGSN depending on E-UTRAN roaming agreement TS 23.060CR1773
Rel-13 specification text

In Rel-13 the SGSN gained group-based and APN-and-group NAS congestion control, SM back-off handling, high latency communication buffering and Pending Data indication, and SGSN selection with DCN support.

  • “The SGSN may detect the NAS signalling congestion associated with the MSs belonging to a particular group.” TS 23.060 v13.8.0
  • “The SGSN may reject the Session Management (SM) requests from the MS belonging to this particular group” TS 23.060 v13.8.0
  • “the SGSN may include a Pending Data indication in the next RANAP message towards the UTRAN” TS 23.060 v13.8.0
Rel-14 specification text

SGSN behaviour was extended in Rel-14: it handles Enhanced Coverage Restricted parameter, Non-IP PDP type, T6b/SCEF connection indication on detach, and restricts NIDD Submit Requests under load.

  • “SGSN receives Enhanced Coverage Restricted parameter from the HLR.” TS 23.060 v14.8.0
  • “If the SGSN establishes a PDP contexct of PDP type Non-IP, header compression shall not be used for the PDP context.” TS 23.060 v14.8.0
  • “the SGSN may restrict NIDD Submit Request messages that its SCEFs are generating on it, if configured to do so.” TS 23.060 v14.8.0
Rel-15 specification text

SGSN behaviour was changed in Rel-15: Modify PDP Context is exempted from back-off rejection for PS Data Off reporting, SGSN may restrict NR secondary RAT access, and it handles NOR failures without detaching.

  • “The SGSN may immediately reject any subsequent request from the MS targeting to the APN before the stored Session Management back-off time is expired except Modify PDP Context Request” TS 23.060 v15.5.0
  • “the MME/SGSN, based on local policy, may restrict access for NR as secondary RAT when all relevant entities except HSS supports it.” TS 29.272 v15.10.0
  • “the MME or SGSN shall not trigger a detach for the subscriber based only on this failure.” TS 29.272 v15.10.0
Rel-16 2 CRs

SGSN behaviour changed in Rel-16: it now interworks with 5G, handles combined MME/SGSN feature support, and has updated mobility/PRA and BDWI handling over GTP-C S3/S16 and S6d.

  • SGSN Interworking with 5G TS 29.272CR0820
  • Supported Features for combined MME/SGSN TS 29.272CR0821
  • “the new MME/SGSN shall invoke data forwarding if there is an SGW change” TS 29.274 v16.13.0
Rel-17 specification text

Rel-17 adds SGSN/MME requirements: sending notifications to the SCEF on communication failure after handover, extended buffering for intermittent satellite coverage, and handling of deleted MSISDN or External Identifiers.

  • “The source MME/SGSN shall set the NSCF (Notify SCEF about Communication Failure events) flag to "1"” TS 29.274 v17.12.0
  • “The MME/SGSN shall also delete those monitoring events related to the deleted MSISDN.” TS 29.272 v17.9.0
  • “or is only in coverage intermittently (e.g. the UE is using satellite access with a known maximum interval between coverage occasions)” TS 23.401 v17.11.0
Rel-18 specification text

The combined MME/SGSN may set Skip Subscriber Data only after a previous identical location update, must not set it otherwise, and must not set it when including SMS-Register-Request in the ULR.

  • “Otherwise the MME/SGSN shall not set the "Skip Subscriber Data" flag in the ULR-Flags.” TS 29.272 v18.7.0
  • “the MME/SGSN shall not set the "Skip Subscriber Data" flag within the ULR-Flags AVP.” TS 29.272 v18.7.0
Rel-19 1 CR

In TS 29.272, SGSN gains SMS registration handling in the HSS via the Update Location Request, and supports store-and-forward for satellite access monitoring events.

  • “An Update Location Request sent by an SGSN that is already registered for SMS in the HSS” TS 29.272 v19.6.0
  • “This bit shall be set if Store and Forward operation for satellite access monitoring event is supported in the MME/SGSN.” TS 29.272 v19.6.0
  • MME/SGSN registration for SMS TS 29.272CR0886

Defining Specifications

3GPP specifications that define or reference SGSN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 03.071 v890 GSM Location Services Stage 2 R99 read
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 21.978 v300 CAMEL Control of VoIP Services Feasibility Study R99 read
TR 22.945 v300 Fax Services Guidance for GSM/UMTS R99 read
TR 22.980 vj00 Network Composition Feasibility Study Rel-19 read
TS 23.018 vj00 Basic call handling in 3GPP CS domain Rel-19 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19 read
TS 23.107 vj00 UMTS QoS Framework Rel-19 read
TS 23.119 vj00 Gateway Location Register (GLR) Stage 2 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.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.251 vj00 Network Sharing Stage 2 Specification Rel-19 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.815 v500 IMS Charging Implications Rel-5 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 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.065 v310 GPRS Subnetwork Dependent Convergence Protocol R99 read
TS 24.161 vj00 Network-Based IP Flow Mobility (NBIFOM) 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 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19 read
TS 25.412 vj00 Iu Interface Signalling Transport Specification Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TS 26.346 vj30 MBMS User Services Specification 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.102 vk00 USIM Application Specification Rel-20 read
TR 31.900 vj00 3GPP TS 31.900: Security Interworking Guidance 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.254 vk00 3GPP TS 32.254: Charging for Northbound APIs Rel-20 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.296 vj00 Online Charging System (OCS) Architecture 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.102 vj10 3G Security Architecture Specification Rel-19 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.320 vj00 H(e)NB Subsystem Security Architecture Rel-19 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.805 vc00 3GPP Network Product Security Assurance Methodology Rel-12 read
TS 33.822 v800 Inter-Access Mobility Security Architecture Rel-8 read
TS 33.859 vb10 UTRAN Key Hierarchy Study Rel-11 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.129 vj00 PS Handover in GERAN A/Gb and GAN Modes Rel-19 read
TS 43.130 vj00 Iur-g Interface Overview Rel-19 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19 read
TS 44.065 vj00 GPRS SNDCP Specification Rel-19 read
TS 44.160 vg00 GERAN Iu Mode RLC/MAC Protocol Specification Rel-16 read
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read
TS 48.016 vj00 Gb Interface Network Service Specification Rel-19 read
TS 52.402 vj00 GSM Performance Management Measurements Rel-19 read