Global Call Reference

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.

Key Features

• Globally unique identifier for a call/session instance
• Used as a correlation key across network domains
• Incorporates elements for uniqueness (e.g., PLMN ID, timestamp)
• Propagated in control plane signaling messages
• Included in Charging Data Records (CDRs) and Lawful Interception reports
• Enables end-to-end billing, troubleshooting, and compliance

Evolution Across Releases

Defining Specifications