CGI

Cell Global Identifier

Identifier →
Introduced in R99 Also in: Services, Core Network

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.

Category
Identifier
Introduced
R99
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
35 specs
CGI Description Purpose Related Classification 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.

Classification

Specific typesECGIUC-ID
Related approachesTAC

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 4 changes

In Release 15, the CGI function was updated to include the provision of a UE identifier during an initial registration procedure. The release also addressed editorial clarifications regarding the Access Network charging identifier. Furthermore, enhancements were made to the Public Warning System by adding a Message Identifier and Serial Number to the PWS Cancel Request.

  • UE identifier provided during an initial registration procedure TS 24.501CR0679
  • Removal of Editor's note on home network public key and home network public key identifier update and removal of protection scheme identifier TS 24.501CR0845
  • Solve Editor's Note on Access Network charging Identifier TS 32.299CR0816
  • Addition of Message Identifier and Serial Number to PWS Cancel Request TS 38.473CR0479
Rel-16 8 changes

In Release 16, the key update for the Cell Global Identifier (CGI) function was the introduction of a defined maximum number of NR-CGI entries over the E1 interface. This change established a specific scaling limit for this identifier within the network architecture. The release also included corrections to certain erroneous Information Element Identifiers related to network procedures.

  • Maximum number of NR-CGI over E1 [EXT_NRCGI_E1] TS 38.463CR0602
  • 5G-GUTI not globally unique in an SNPN TS 24.501CR1458
  • 5GMM cause value #74 in an SNPN with a globally-unique SNPN identity TS 24.501CR2019
  • Correction of certain erroneous Information Element Identifiers TS 24.501CR2033
  • 5GMM cause value #74 in an SNPN with a globally-unique SNPN identity TS 24.501CR2068
  • Packet filter identifier setting when requesting new packet filters TS 24.501CR2536

+ 2 more changes

Rel-17 9 changes

In Release 17, specific corrections and clarifications were made for the CGI function, particularly regarding its use in the Multicast Broadcast Service (MBS) service area. The release corrected the NR CGI list within the MBS service area and clarified that this area definition can include both an MBS TAI list and an NR CGI list. Additionally, a correction was made to the Global eNB ID within the NGAP interface protocol.

  • Support for handling unknown length of gNB identifier [gNB_ID_Length] TS 38.413CR0571
  • Avoid including both PAP/CHAP and EAP identifiers in PDU session establishment request TS 24.501CR2941
  • Clarification on the setting of packet filter identifier value TS 24.501CR3300
  • Network identifier is not specified TS 24.501CR3389
  • 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
  • Access Technology Identifier satellite NG-RAN TS 24.501CR3636

+ 3 more changes

Rel-18 7 changes

In Release 18, specific corrections and protections were introduced for the N3IWF (Non-3GPP InterWorking Function) identifier information, particularly focusing on its handling within the REGISTRATION REJECT message procedure. Additionally, enhancements were made to identifier structures in other areas, including the addition of context identifiers to BaseRecord and corrections related to the QoS Flow Identifier for QoS and MBS (Multicast/Broadcast Service) support. These updates refined the precision and security of various network and session identifiers beyond the Cell Global Identifier (CGI) scope.

  • Protecting the N3IWF/TNGF identifier information in the REGISTRATION REJECT message TS 24.501CR5932
  • [5GMS_Pro_Ph2] Media delivery session identifier at M4+M7+M11 TS 26.512CR0066
  • Correction for N3IWF identifier IE TS 24.501CR5120
  • Correction related to receiving N3IWF identifier IE in the REGISTRATION REJECT TS 24.501CR5322
  • [EVEX, TEI18] Add context identifiers to BaseRecord TS 26.512CR0076
  • Correction on QoS Flow List and QoS Flow Identifier TS 37.483CR0155

+ 1 more changes

Rel-19 9 changes

In Release 19, the primary enhancements for the CGI function centered on QoS differentiation for non-3GPP device identifiers, introducing support for multiple such identifiers and procedures for suspending or rejecting this QoS differentiation. These updates included corrections and clean-up to the associated connection information IE and its naming for consistency. The changes did not alter the fundamental definitions of cell or UE identifiers like C-RNTI or U-RNTI as described in the core specification.

  • Support of reject QoS differentiation for non-3GPP device identifier(s) TS 24.501CR6926
  • Procedure update for QoS differentiation of non-3GPP device identifiers TS 24.501CR6994
  • Suspending QoS differentiation for non-3GPP device identifier TS 24.501CR7087
  • Correction to the inconsistent LCS correlation identifier TS 24.501CR6380
  • Support of multiple Non-3GPP device identifiers for QoS differentiation TS 24.501CR6925
  • QoS differentiation for non-3GPP device identifiers clean up TS 24.501CR6993

+ 3 more changes

Explore further

Broader topics and technologies where CGI plays a role.

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