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

Glossary term · Identifier

CGI

Cell Global Identifier

Identifier →

CGI is the globally unique identifier for a mobile network cell, formed by combining the MCC, MNC, LAC, and Cell Identity to enable precise identification and routing across the network.

Introduced
R99
Where
Radio Access Network
Specifications
35 specs
Also in
Services, Core Network
CGI Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Cell Global Identifier (CGI) is a fundamental addressing element within 3GPP mobile networks, providing a globally unambiguous label for every cell. Its primary function is to uniquely distinguish one cell from all others worldwide, which is a critical requirement for call routing, handover management, subscriber location tracking, and various network operations and maintenance tasks. The CGI is not a standalone number but a structured concatenation of several existing identifiers defined within the PLMN (Public Land Mobile Network) architecture. This hierarchical construction ensures global uniqueness through the combination of country, network, regional, and local identifiers.

The structure of the CGI is defined as: CGI = MCC + MNC + LAC + CI. The Mobile Country Code (MCC) is a three-digit code (e.g., 234 for the UK) defined by the ITU. The Mobile Network Code (MNC) is a two- or three-digit code identifying the specific network operator within that country (e.g., 30 for EE UK). Together, the MCC and MNC form the PLMN ID, which uniquely identifies the operator's network. The Location Area Code (LAC) is a fixed-length code (typically 16 bits) assigned by the network operator to identify a location area, which is a group of cells used for paging and location updating. Finally, the Cell Identity (CI) is a fixed-length code (typically 16 bits) assigned by the operator to uniquely identify a cell within a given location area.

From an architectural perspective, the CGI is used by multiple network elements. In the Radio Access Network (RAN), the base station (Node B, eNodeB, gNB) broadcasts its CGI (or components thereof) on the broadcast channel (BCCH) so that User Equipment (UE) can identify the serving cell. The UE reports the CGI of neighboring cells during measurement reports, which the network uses for handover decisions. In the Core Network, the CGI is crucial for the Mobility Management Entity (MME) in LTE or the Access and Mobility Management Function (AMF) in 5GC to track the UE's precise location for paging and session management. It is also a key parameter in the Gateway Mobile Location Center (GMLC) for emergency services and commercial location-based services, and it is a mandatory field for lawful interception interfaces.

Operationally, the CGI enables all mobility procedures. During a handover, the source cell includes the CGI of the target cell in the handover request message to uniquely identify the destination. For location services, a request containing a subscriber's identifier can be translated by the network into the last known CGI, providing a coarse-grained location. In network management systems, performance metrics (e.g., call drop rate, traffic load) are collected and reported per CGI, allowing operators to monitor and optimize network performance on a per-cell basis. Its global uniqueness prevents any ambiguity when integrating networks from different operators or during international roaming, ensuring seamless service continuity and accurate billing.

Purpose & Motivation

The Cell Global Identifier was created to solve the fundamental problem of unambiguously identifying a specific radio cell anywhere in the world within the global mobile telecommunications system. Prior to standardized global addressing, networks could use proprietary or non-unique cell identifiers, which would cause conflicts during roaming, inter-operator handovers, and network integration. This lack of a universal scheme would hinder mobility, complicate fault isolation, and make nationwide or global network management and service provisioning nearly impossible. The CGI provides this necessary universal addressing layer.

The primary motivation was to support advanced mobility and network management in digital cellular networks like GSM (where it was first standardized) and its successors. As networks grew larger and more complex, and as roaming between operators and countries became a standard service requirement, a structured, hierarchical identifier became essential. The CGI allows the network to precisely route calls and data sessions, manage handovers between cells (even those from different vendors or, in some cases, different operators), and accurately log events for billing, security, and performance analysis. It is the cornerstone for location-based services, as it provides the network-known position of a subscriber.

Furthermore, the CGI addresses regulatory and operational requirements. For emergency services (e.g., E-911 in the US), the network must provide the location of a caller. The CGI serves as a key piece of location information that can be translated into a geographical area. For lawful interception, authorities require logs and intercepts associated with a specific location, which is enabled by tagging data with the CGI. Its design also simplifies network planning and expansion, as operators can administer Cell Identities within their assigned Location Areas and PLMN without risk of global collision, ensuring scalable and future-proof network growth.

What changed in its specifications

The latest release-to-release comparison of specifications that define CGI. 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.057Rel-4 → Rel-5

Rel-5 added MExE Classmark 4 for CLI Compact Profile devices, covering architecture, security, charging, and capability negotiation.

Full comparison in TS 23.057 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change
  • Maximum number of NR-CGI over E1 [EXT_NRCGI_E1] TS 38.463CR0602
Rel-17 2 changes
  • The MBS service area received in PDU SESSION ESTABLISHMENT ACCEPT message can include both of MBS TAI list and NR CGI list TS 24.501CR3661
  • Correction for NR CGI list in the MBS service area TS 24.501CR3955

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.031 vj00 Fraud Information Gathering System (FIGS) Stage 1 Rel-19 read
TS 23.031 vj00 Fraud Information Gathering System (FIGS) - Stage 2 Rel-19 read
TS 23.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.292 vj00 IMS Centralized Services (ICS) Architecture Rel-19 read
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 25.133 vj00 UTRAN RRM Requirements for FDD Rel-19 read
TS 25.709 vf00 Simplified HS-SCCH for UMTS Study Rel-15 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 read
TS 26.849 vc10 MBMS Operation on Demand (MooD) Rel-12 read
TR 26.926 vj00 Traffic Models & Quality Evaluation for Media/XR in 5G Rel-19 read
TR 26.955 vj00 Video Codec Analysis for 5G Services Rel-19 read
TR 26.956 vj01 Beyond 2D Video Formats & Codecs Study Rel-19 read
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19 read
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 36.133 vj60 LTE Radio Resource Management Requirements Rel-19 read
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19 read
TS 37.473 vj00 W1 Application Protocol (W1AP) Specification Rel-19 read
TS 37.483 vj40 E1 Application Protocol (E1AP) Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read
TS 38.423 vj40 NG-RAN Xn Application Protocol Rel-19 read
TS 38.463 vj00 E1 Application Protocol (E1AP) Rel-19 read
TS 38.473 vj40 F1 Application Protocol (F1AP) Rel-19 read
TS 41.033 ve00 GSM Lawful Interception Interface Requirements Rel-14 read
TS 43.020 vj00 Security Procedures for GSM 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.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read