Description
The GSM EDGE Radio Access Network (GERAN) is the collective term for the radio network infrastructure that implements the GSM, GPRS, and EDGE radio technologies as defined by 3GPP. Architecturally, GERAN is composed of Base Station Subsystems (BSS). Each BSS consists of two main elements: the Base Transceiver Station (BTS), which houses the radio transceivers and antennas for one or more cells, and the Base Station Controller (BSC), which manages radio resources, handles handovers, and controls the BTSs. The BSC performs critical functions like frequency allocation, power control, and the management of traffic and signaling channels (e.g., SDCCH, TCH).
GERAN connects to the core network via two key interfaces. For circuit-switched (CS) voice and SMS services, it uses the A-interface to link the BSC with the Mobile Switching Center (MSC). For packet-switched (PS) data services via GPRS and EDGE, it uses the Gb-interface to connect the BSC (or a dedicated Packet Control Unit - PCU) with the Serving GPRS Support Node (SGSN). The radio interface, known as the Um interface, uses a combination of FDMA (dividing the spectrum into 200 kHz carriers) and TDMA (dividing each carrier into 8 time slots). EDGE (Enhanced Data rates for GSM Evolution) introduced advanced modulation (8-PSK alongside GMSK) and coding schemes, significantly boosting data rates within the same TDMA structure.
Within a multi-RAT (Radio Access Technology) environment, GERAN's role evolved from being the sole RAN to interworking with UMTS (UTRAN) and LTE (E-UTRAN). Specifications define mechanisms for handover and cell reselection between GERAN and these newer networks, allowing for service continuity. The BSC manages both CS and PS resources, and with the introduction of EDGE, it also handles the adaptive modulation and coding that defines EDGE's higher throughput. GERAN specifications cover everything from the physical layer (modulation, burst structures) in the 45-series specs, to layer 2 and 3 protocols (e.g., RLC/MAC, BSSGP over Gb) in the 44 and 48-series, and to performance requirements in the 51-series.
Purpose & Motivation
GERAN was formally defined as a term to encompass the evolved 2G radio access network that included both the original GSM standard and its packet-data enhancements, GPRS and EDGE. Its creation solved the problem of providing a clear architectural definition for the radio network that supported both voice-centric circuit-switched services and emerging internet-based packet-switched data services under a single umbrella. Before this consolidation, specifications often referred separately to GSM radio and GPRS radio aspects.
The historical motivation was the need to evolve the successful GSM network to handle data efficiently, leading first to GPRS (a packet overlay) and then to EDGE (a radio enhancement). GERAN represents the culmination of this evolution, maximizing the utility of the deployed 200 kHz carrier TDMA infrastructure. It addressed the limitation of slow circuit-switched data (CSD) by introducing always-on packet connectivity (GPRS) and then significantly boosting its speed (EDGE), enabling early mobile internet experiences. As 3G (UMTS) emerged, defining GERAN allowed for clearer specifications on how this legacy network would interwork and coexist with the new WCDMA-based UTRAN, ensuring a smooth transition and global roaming across multiple generations of technology.
What changed in its specifications
The latest release-to-release comparison of specifications that define GERAN. 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-19 brings only minor changes to TS 23.009: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.009 →Technology family
Radio access technologies · Radio Access Network
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 17 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 Rel-4 (release dating of the term; no individual change cited).
GERAN gains Iu-mode support in the packet domain: the SGSN connects to the GERAN BSS via Gb or Iu, with GERAN BSS/BSC treated as RNS/RNC when serving an MS in Iu mode.
- “The SGSN is connected to the GERAN base station system through the Gb or Iu interface and/or to the UTRAN through the Iu interface.” TS 23.060 v5.13.0
- “the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an MS in Iu mode.” TS 23.060 v5.13.0
- Introduction of GERAN Iu-mode TS 23.153CR031
TS 23.060 added packet-switched handover for GERAN A/Gb mode, with PS Handover Request Context transferred between SGSNs for GERAN-to-GERAN and GERAN-to-Iu mode handover.
- “During the PS handover procedure the PS Handover Request Context containing packet flow specific information needs to be transferred between SGSNs.” TS 23.060 v6.15.0
- “3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2".” TS 23.060 v6.15.0
GAN specifications added PS handover between GAN and GERAN/UTRAN cells, including procedures and messages for handover to a GERAN target cell.
- “8.23 PS Handovers between GAN mode and GERAN/UTRAN mode” TS 43.318 v7.5.0
- “For the case of PS handover to a GERAN cell, the GA-PSR Handover Command message shall include the set of PSI or SI messages” TS 44.318 v7.9.0
- “PS handover: A mobile station with one or more ongoing PS domain services moves between a GAN cell and a GERAN/UTRAN cell.” TS 43.318 v7.5.0
GERAN gained new Rel-8 roles: interworking with E-UTRAN/EPS (ISR, TAU timer handling, RFSP index to BSC) and PS handover between GERAN and UTRAN, plus AoIP signalling between MSC and GERAN.
- “provides a mechanism to limit signalling during cell‑reselection in idle mode between GERAN and E‑UTRAN or between UTRAN and E‑UTRAN” TS 23.060 v8.17.0
- “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
- Signalling between MSC and GERAN AoIP-mode TS 23.153CR0114
Rel-9 specs add requirements involving GERAN: emergency bearer services are not supported in the GERAN PS domain, so handover and relocation to GERAN are prevented, and GAN handover reporting of GERAN cells is changed.
- “Emergency bearer service is not supported in GERAN PS domain. Relocation to A/Gb mode shall be prevented” TS 23.060 v9.14.0
- “the Routing Area Update shall be rejected with a cause code indicating that access to GERAN is not allowed.” TS 23.060 v9.14.0
- “If the UE has an ongoing emergency bearer service the source eNodeB shall not initiate PS handover to GERAN.” TS 23.401 v9.16.0
Rel-10 added GERAN support for Extended Access Barring and low access priority signalling, with the BSS able to inhibit random access via Implicit Reject.
- “NOTE: For this release of the specification, Extended Access Barring is only supported for GERAN.” TS 23.060 v10.14.0
- “SGSN signalling or GERAN O&M can trigger GERAN to initiate Extended Access Barring in the GERAN for certain subcategories of MSs.” TS 23.060 v10.14.0
- Correction of PS suspension procedure in CSFB to GERAN A/Gb mode TS 23.272CR0691
Rel-11 adds Service Class Indicator support for A/Gb mode GERAN, where the SGSN passes SCI to GERAN to map into RRM behaviour, and extends Extended Access Barring handling to GERAN.
- “The A/Gb mode GERAN uses the information from the SGSN to determine whether to map, and how to map, the SCI to the related RRM behaviour.” TS 23.060 v11.12.0
- “it copies it, without modifying its value, into a Gb interface information element that is sent by the SGSN in the downlink Gb interface user data packet to the GERAN access.” TS 23.060 v11.12.0
- GWCN for GERAN TS 23.251CR0062
GERAN Iu mode functionality was declared no longer maintained or enhanced since Rel-9 and removed, and deferred ULI/CGI change reporting for GERAN was corrected.
- “functionality related to GERAN Iu mode is neither maintained nor enhanced since Rel‑9.” TS 23.060 v12.11.0
- Removal of GERAN Iu mode TS 23.060CR1806
- “For GERAN, the SGSN may be configured to report CGI/RAI changes only when the SGSN receives an uplink LLC PDU” TS 23.060 v12.11.0
GERAN-specific behaviour was changed in TS 23.060: paging for MTC in GERAN, low access priority use for GERAN access, and GERAN CGI/SAI/RAI change reporting when PFC procedures are not supported.
- Paging for MTC in GERAN TS 23.060CR1981
- Use of low access priority for GERAN access TS 23.060CR1929
- “For GERAN, when SGSN, BSS or MS don't support PFC procedures, the SGSN shall report a CGI/SAI/RAI change as soon as it is detected.” TS 23.060 v13.8.0
Rel-14 extends GERAN with support for Non-IP and SCEF connections, plus Dedicated Core Network selection (DECOR and enhanced DECOR) in the GERAN BSS and its signalling.
- Adding support for NonIP & SCEF in GERAN TS 23.401CR3052
- Introduction of enhanced DECOR for GERAN TS 44.018CR1065
- “CIoT EPS Optimisations are not supported by GERAN and UTRAN in this release of the specifications.” TS 23.401 v14.11.0
Rel-15 adds GERAN interworking with 5GS: identifier use for GERAN/UTRAN-5GS mobility, GERAN/UTRAN access restriction handling at inter-RAT handover, and rSRVCC-aligned UE radio capability handling.
- Use of identifiers for mobility between GERAN/UTRAN and 5GS TS 23.060CR2035
- “At inter-RAT handover from GERAN/UTRAN, the Access Restriction for NR is either already in the MME's UE context” TS 23.401 v15.13.0
- Null interworking with GERAN/UTRAN CS domain TS 23.501CR0524
For GERAN mobility, the MME must now restrict GERAN/UTRAN in the Handover Restriction List for RLOS-attached UEs and for UEs with only an Ethernet PDN connection, and GERAN radio capability changes now trigger a new UE Radio Capability ID.
- “for a RLOS attached UE, the MME shall restrict mobility to GERAN and UTRAN, and include GERAN and UTRAN in the Handover Restriction List.” TS 23.401 v16.14.0
- “Ethernet PDN Type is not supported in GERAN/UTRAN.” TS 23.401 v16.14.0
- “a change in UE Radio Access capability (e.g. due to GERAN radio capability change” TS 23.401 v16.14.0
Rel-17 adds support for GERAN/UTRAN access in 5GS interworking, including SMF+PGW-C support, mobility between GERAN/UTRAN and E-UTRAN/5GS, and GERAN/UTRAN user location information in charging and N7.
Rel-18 CRs correct and clarify GERAN-related behaviour, including UE access to GERAN/UTRAN over Gn/Gp, the Unit Count Inactivity Timer for GERAN/UTRAN access, and protection against improper reselection to GERAN/UTRAN.
The HSS may now inform the MME of an inter-country inter-PLMN mobility restriction, which is not present in the OLD text for GERAN/UTRAN roaming restriction.
- “The HSS may also inform the MME that inter-country inter-PLMN mobility” TS 23.401 v20.1.0
Defining Specifications
3GPP specifications that define or reference GERAN, 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 |
| TS 22.034 vj00 | High Speed Circuit Switched Data (HSCSD) Stage 1 | Rel-19 read |
| TS 22.240 vj00 | 3GPP Generic User Profile Requirements | Rel-19 read |
| TS 23.009 vj00 | Handover Procedures in PLMNs | Rel-19 read |
| TS 23.034 vj00 | HSCSD Stage 2 Service Description | Rel-19 read |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.107 vj00 | UMTS QoS Framework | Rel-19 read |
| TS 23.205 vj00 | Bearer Independent CS Core Network Stage 2 | Rel-19 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.231 vj00 | SIP-I based CS core network stage 2 | Rel-19 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.802 v700 | Enhanced End-to-End QoS Architecture | Rel-7 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 |
| TS 24.161 vj00 | Network-Based IP Flow Mobility (NBIFOM) | Rel-19 read |
| TS 24.206 v750 | Voice Call Continuity Between CS and IMS | Rel-7 read |
| TS 24.312 vj00 | ANDSF Management Objects Specification | Rel-19 read |
| TS 25.123 vj00 | Radio Resource Management for TDD | Rel-19 read |
| TS 25.133 vj00 | UTRAN RRM Requirements for FDD | Rel-19 read |
| TS 25.331 vj01 | UTRAN Radio Resource Control Protocol | Rel-19 read |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 25.420 vj00 | Iur Interface Introduction for UTRAN | Rel-19 read |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 read |
| TR 25.912 vj00 | Evolved UTRA and UTRAN Technical Report | Rel-19 read |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 read |
| TR 26.952 vj00 | EVS Codec Selection, Verification & Characterization | Rel-19 read |
| TR 26.976 vj00 | AMR-WB Codec Characterization & Verification | Rel-19 read |
| TS 28.606 vc10 | CN and non-3GPP interworking NRM IRP Solution Sets | Rel-12 read |
| TS 28.616 vj00 | EPC and non-3GPP access NRM IRP SS definitions | Rel-19 read |
| TS 28.626 vj00 | State Management Data Definition IRP Solution Set | Rel-19 read |
| TS 28.653 vj00 | UTRAN NRM IRP Solution Set Definition | Rel-19 read |
| TS 28.654 vj00 | GERAN NRM IRP Requirements | Rel-19 read |
| TS 28.655 vj00 | GERAN NRM IRP Information Service | Rel-19 read |
| TS 28.656 vj00 | GERAN NRM IRP Solution Set Definitions | Rel-19 read |
| TS 28.659 vk00 | E-UTRAN NRM Solution Set Definitions | Rel-20 read |
| TS 28.703 vj00 | Core Network NRM IRP Solution Set Definitions | Rel-19 read |
| TS 28.706 vj00 | IMS NRM IRP Solution Set definitions | Rel-19 read |
| TS 28.707 vj00 | EPC NRM IRP Requirements | Rel-19 read |
| TS 28.733 vj00 | TN NRM IRP Solution Set Definitions | Rel-19 read |
| TR 31.900 vj00 | 3GPP TS 31.900: Security Interworking Guidance | Rel-19 read |
| TS 32.152 ve10 | IRP Information Service UML Repertoire | Rel-14 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 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.410 vj00 | 3GPP TS 32.410: Key Performance Indicators (KPI) | Rel-19 read |
| TS 32.615 v920 | Bulk CM XML File Format Definition | Rel-9 read |
| TS 32.616 vj00 | Bulk CM IRP Solution Set Definitions | Rel-19 read |
| TS 32.625 v900 | Bulk CM XML File Format for Generic Network Resources | Rel-9 read |
| TS 32.626 vb20 | Generic NRM IRP Solution Sets | Rel-11 read |
| TS 32.635 v910 | Core Network Resources IRP Bulk CM XML Format | Rel-9 read |
| TS 32.636 vb00 | Core Network Resources IRP Solution Set | Rel-11 read |
| TS 32.641 vb00 | UTRAN Network Resources IRP Requirements | Rel-11 read |
| TS 32.645 v930 | UTRAN Bulk CM XML File Format | Rel-9 read |
| TS 32.646 vc00 | UTRAN NRM IRP Solution Set Definitions | Rel-12 read |
| TS 32.651 vb00 | GERAN Network Resources IRP Requirements | Rel-11 read |
| TS 32.652 vc00 | GERAN Network Resources NRM for Configuration Management | Rel-12 read |
| TS 32.655 v920 | GERAN NRM Bulk CM XML File Format | Rel-9 read |
| TS 32.656 vc00 | GERAN NRM IRP Solution Set Definitions | Rel-12 read |
| TS 32.675 v900 | Configuration Management Bulk CM XML File Format | Rel-9 read |
| TS 32.676 vc00 | 3GPP TS 32.676: State Management IRP Solution Set | Rel-12 read |
| TS 32.715 v900 | TN interface NRM IRP XML file format definition | Rel-9 read |
| TS 32.716 vb00 | TN NRM IRP Solution Sets | Rel-11 read |
| TS 32.725 v900 | Repeater NRM Bulk CM XML File Format | Rel-9 read |
| TS 32.726 vb00 | Repeater NRM IRP Solution Set | Rel-11 read |
| TS 32.735 v910 | IMS NRM IRP Bulk CM XML File Format | Rel-9 read |
| TS 32.736 vb00 | IMS NRM IRP Solution Set Definitions | Rel-11 read |
| TS 32.751 vb00 | EPC NRM IRP Requirements | Rel-11 read |
| TS 32.765 v960 | E-UTRAN NRM IRP XML Definitions | Rel-9 read |
| TS 32.766 vb90 | E-UTRAN NRM Solution Sets | Rel-11 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 33.102 vj10 | 3G Security Architecture Specification | Rel-19 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 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 36.133 vj60 | LTE Radio Resource Management Requirements | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.302 vj00 | E-UTRA Physical Layer Services | Rel-19 read |
| TS 36.304 vj30 | LTE UE Idle Mode Procedures | Rel-19 read |
| TS 36.306 vj30 | E-UTRA UE Radio Access Capability Parameters | Rel-19 read |
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |
| TS 37.320 vj40 | MDT Overall Description (Stage 2) | Rel-19 read |
| TS 38.331 vj40 | NR Radio Resource Control (RRC) | Rel-19 read |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | 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.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 read |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 read |
| TR 44.901 vj00 | Extended NACC for External Cell Change | Rel-19 read |
| TR 45.902 vj00 | Flexible Layer One (FLO) for GERAN | Rel-19 read |