Trace Reference

Description

The Trace Reference is a key identifier within the 3GPP trace management framework, defined in TS 32.421 and referenced in TS 25.413. It uniquely identifies a Trace Session on a global scale, enabling network elements and management systems to correlate trace records generated during that session. The Trace Reference is typically composed of the Management System (MS) IP address or a unique identifier of the Element Manager (EM) and a locally unique number assigned by the EM. This combination ensures global uniqueness, as the EM identifier is unique within the network.

When a Trace Session is activated, the Element Manager generates a Trace Reference and includes it in the Trace Session Activation message sent to the network element (e.g., RNC, SGSN, MME). The network element stores this reference and includes it in all trace records generated during the session. When records are forwarded to a Trace Collection Entity (TCE), the Trace Reference allows the TCE to group records belonging to the same Trace Session, even if they originate from different network elements or are generated at different times.

The Trace Reference is distinct from the Trace Recording Session Reference, which identifies a specific recording session within a Trace Session. While the Trace Reference remains constant for the duration of a Trace Session, the Trace Recording Session Reference may change each time recording is triggered. Together, these identifiers provide a hierarchical naming scheme that supports both session-level and recording-level correlation.

In multi-vendor and multi-technology networks, the Trace Reference is essential for interoperability. It allows a centralized management system to activate a trace session across multiple network elements and then collect and analyze the resulting data in a unified manner. The global uniqueness property ensures that there is no ambiguity, even in large networks with many EMs and network elements.

The Trace Reference has been part of the 3GPP trace framework since Rel-6. Its definition has remained stable, with only minor editorial changes across releases. The Rel-8 revision clarified the definition to explicitly state that it identifies a Trace Session and is globally unique, referencing Figure 2 for the structure. Subsequent releases maintained this definition, underscoring the fundamental role of the Trace Reference in trace management.

Purpose & Motivation

The Trace Reference exists to provide a globally unique identifier for Trace Sessions, solving the problem of correlating trace data across multiple network elements and management systems. Without a unique reference, it would be impossible to reliably associate trace records with the session that generated them, especially in large networks where multiple trace sessions may be active simultaneously.

Before the introduction of the Trace Reference, tracing was often ad-hoc and lacked a standardized way to identify sessions. This made it difficult to collect and analyze trace data from different sources, as there was no common key to link records. The Trace Reference addresses this by combining an EM identifier with a local number, ensuring global uniqueness and enabling centralized management.

The Trace Reference also facilitates the distribution of trace sessions across network elements. When an operator activates a trace session, the Trace Reference is propagated to all involved elements, allowing them to generate records that can be later merged. This is particularly important for tracing mobility events, where a subscriber may move across multiple cells and network elements. The Trace Reference ensures that all records from the session can be correlated, providing a complete picture of the subscriber's activity.

Over time, the Trace Reference has proven to be a robust and scalable solution, remaining essentially unchanged since its introduction. Its design reflects the need for a simple yet effective identifier that works across heterogeneous networks and vendor equipment.