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

Glossary term · Identifier

GCR

Global Call Reference

Identifier →

GCR is a unique identifier assigned to a call or session across multiple network domains to enable end-to-end correlation of charging, fault management, and lawful interception data.

Introduced
Rel-5
Where
Services › IMS
Specifications
10 specs
Also in
Core Network
GCR Description Purpose What changed Specifications

Description

The Global Call Reference (GCR) is a globally unique identifier used within 3GPP networks to tag a specific instance of a communication service, such as a voice call, a video session, or a data session. Its primary role is to provide a correlation key that can be used to link all records and events associated with that single communication instance as it traverses different network elements, different operator networks, and different administrative domains (e.g., visited and home networks). The GCR is generated at the call/session establishment, typically by the network entity that initiates the charging or control process for that session.

Technically, the GCR is structured to ensure global uniqueness. It often incorporates elements such as a network operator identifier (like the PLMN ID), a timestamp, and a locally unique sequence number generated by the creating node. This structured approach prevents collisions. The GCR is then propagated in signaling messages (e.g., within Diameter or MAP protocols) to all relevant network functions involved in the call, including Call Session Control Functions (CSCFs), Media Gateway Control Functions (MGCFs), charging systems (OCS, OFCS), and Lawful Interception gateways.

When a charging data record (CDR) or an interception-related information (IRI) report is generated by any network node for that call, the GCR is included. This allows a billing system or a law enforcement monitoring facility to collate all partial records from various nodes—such as the S-CSCF, MGW, and breakout gateway—into a single, coherent view of the entire call. Similarly, in fault management, alarms or performance measurements from different segments of the call path can be correlated using the GCR to diagnose end-to-end service quality issues.

Purpose & Motivation

The GCR was created to solve the problem of correlating information for a single call that spans multiple, potentially heterogeneous, network segments and administrative domains. In early mobile networks and especially in multi-operator/inter-PLMN scenarios, charging, troubleshooting, and lawful interception were challenging because each network element generated its own local records with local identifiers. There was no standardized way to definitively link these records back to the same call instance.

This lack of correlation led to several problems: billing disputes between operators regarding roaming calls, difficulties in compiling complete call detail records for customer invoices, inefficiencies in fault isolation across network boundaries, and complexities in meeting lawful interception requirements that demand a complete, correlated record of a target's communication. The GCR, introduced as a standardized concept, provides a common key that all parties agree to use and propagate. It addresses these limitations by enabling unambiguous association. Its creation was motivated by the need for robust inter-operator settlement, accurate end-to-end service assurance, and compliance with regulatory mandates for interception, becoming a foundational element for service management in a globally interconnected mobile ecosystem.

What changed in its specifications

The latest release-to-release comparison of specifications that define GCR. 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 29.205Rel-9 → Rel-10

LCLS-CN adds negotiation, status, configuration, and service application message formats and procedures.

Full comparison in TS 29.205 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-5 Initial

Introduced the Global Call Reference (GCR) concept within the IMS architecture specifications. It defined its purpose for correlating charging records across multiple network functions and between different operators' networks, establishing the foundational requirements for its structure and propagation in initial IMS signaling.

Defining Specifications

3GPP specifications that define or reference GCR, 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 23.284 vj00 Local Call Local Switch Stage 2 Rel-19 read
TS 23.796 vg00 FRMCS Architectural Analysis Rel-16 read
TS 23.889 va00 Local Call Local Switch Core Network Impact Study Rel-10 read
TS 29.205 vj00 BICC Protocols for Bearer-Independent CS Core Network Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 43.020 vj00 Security Procedures for GSM Rel-19 read
TS 43.068 vj00 Voice Group Call Service (VGCS) Stage 2 Rel-19 read
TS 43.069 vj00 Voice Broadcast Service (VBS) Stage 2 Rel-19 read
TS 48.008 vj00 BSS-MSC Interface Layer 3 Procedures Rel-19 read