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.
Key Features
- Mobility management for packet-switched subscribers (attach/detach, location/routing area updates)
- Session management including PDP context activation, modification, and deactivation
- User authentication and authorization for packet data access
- Packet routing and transfer between RAN (Gb/Iu-PS) and GGSN (Gn)
- Charging data collection for packet data services
- QoS management for UMTS bearer services
Evolution Across Releases
The SGSN was introduced as a core component of the GPRS architecture, providing mobility and session management for packet-switched data in GSM networks. It connected to the BSS via the Gb interface and to the GGSN via Gn, handling PDP contexts, authentication via HLR, and routing area updates.
Defining Specifications
| Specification | Title |
|---|---|
| TS 03.071 | 3GPP TR 03.071 |
| TS 21.905 | 3GPP TS 21.905 |
| TS 21.978 | 3GPP TS 21.978 |
| TS 22.945 | 3GPP TS 22.945 |
| TS 22.980 | 3GPP TS 22.980 |
| TS 23.018 | 3GPP TS 23.018 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.078 | 3GPP TS 23.078 |
| TS 23.107 | 3GPP TS 23.107 |
| TS 23.119 | 3GPP TS 23.119 |
| TS 23.125 | 3GPP TS 23.125 |
| TS 23.141 | 3GPP TS 23.141 |
| TS 23.171 | 3GPP TS 23.171 |
| TS 23.207 | 3GPP TS 23.207 |
| TS 23.221 | 3GPP TS 23.221 |
| TS 23.228 | 3GPP TS 23.228 |
| TS 23.251 | 3GPP TS 23.251 |
| TS 23.271 | 3GPP TS 23.271 |
| TS 23.327 | 3GPP TS 23.327 |
| TS 23.815 | 3GPP TS 23.815 |
| TS 23.851 | 3GPP TS 23.851 |
| TS 23.923 | 3GPP TS 23.923 |
| TS 23.976 | 3GPP TS 23.976 |
| TS 23.979 | 3GPP TS 23.979 |
| TS 23.981 | 3GPP TS 23.981 |
| TS 24.065 | 3GPP TS 24.065 |
| TS 24.161 | 3GPP TS 24.161 |
| TS 24.228 | 3GPP TS 24.228 |
| TS 24.229 | 3GPP TS 24.229 |
| TS 25.305 | 3GPP TS 25.305 |
| TS 25.412 | 3GPP TS 25.412 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.346 | 3GPP TS 26.346 |
| TS 27.060 | 3GPP TS 27.060 |
| TS 28.702 | 3GPP TS 28.702 |
| TS 29.061 | 3GPP TS 29.061 |
| TS 29.119 | 3GPP TS 29.119 |
| TS 29.199 | 3GPP TS 29.199 |
| TS 29.281 | 3GPP TS 29.281 |
| TS 31.102 | 3GPP TR 31.102 |
| TS 31.900 | 3GPP TR 31.900 |
| TS 32.102 | 3GPP TR 32.102 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.252 | 3GPP TR 32.252 |
| TS 32.254 | 3GPP TR 32.254 |
| TS 32.271 | 3GPP TR 32.271 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.278 | 3GPP TR 32.278 |
| TS 32.296 | 3GPP TR 32.296 |
| TS 32.401 | 3GPP TR 32.401 |
| TS 32.622 | 3GPP TR 32.622 |
| TS 32.632 | 3GPP TR 32.632 |
| TS 32.732 | 3GPP TR 32.732 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 32.833 | 3GPP TR 32.833 |
| TS 33.102 | 3GPP TR 33.102 |
| TS 33.107 | 3GPP TR 33.107 |
| TS 33.108 | 3GPP TR 33.108 |
| TS 33.320 | 3GPP TR 33.320 |
| TS 33.401 | 3GPP TR 33.401 |
| TS 33.805 | 3GPP TR 33.805 |
| TS 33.822 | 3GPP TR 33.822 |
| TS 33.859 | 3GPP TR 33.859 |
| TS 33.863 | 3GPP TR 33.863 |
| TS 33.978 | 3GPP TR 33.978 |
| TS 43.064 | 3GPP TR 43.064 |
| TS 43.129 | 3GPP TR 43.129 |
| TS 43.130 | 3GPP TR 43.130 |
| TS 43.318 | 3GPP TR 43.318 |
| TS 43.901 | 3GPP TR 43.901 |
| TS 43.902 | 3GPP TR 43.902 |
| TS 44.065 | 3GPP TR 44.065 |
| TS 44.160 | 3GPP TR 44.160 |
| TS 44.318 | 3GPP TR 44.318 |
| TS 48.016 | 3GPP TR 48.016 |
| TS 52.402 | 3GPP TR 52.402 |