Command Header Identifier

Description

The Command Header Identifier (CHI) is a critical component within the 3GPP Lawful Interception (LI) framework, specifically used on the standardized Handover Interface (HI). The HI is the interface between a Lawful Enforcement Monitoring Facility (LEMF) – the agency-side system – and one or more Intercepting Control Elements (ICEs) within the network operator's domain, such as a Serving GPRS Support Node (SGSN) or Gateway GPRS Support Node (GGSN) in GPRS/UMTS core networks. The CHI is a field within the protocol data units (PDUs) exchanged on this interface. Its primary function is to unambiguously identify the type of command being sent or the type of report being delivered, acting as a message type identifier that dictates how the receiving entity must parse and process the accompanying payload.

Technically, the CHI is defined as part of the ASN.1-based protocol specification for the HI (HI2 and HI3 interfaces). Each lawful interception operation, such as the activation of an interception, deactivation, or the delivery of an Intercept Related Information (IRI) report or Content of Communication (CC) data, is represented by a specific command or message type. The CHI value in the header of a PDU signals this type to the receiver. For example, one CHI value corresponds to an 'activateIntercept' command from the LEMF to the ICE, while another distinct CHI value corresponds to an 'IRIReport' sent from the ICE to the LEMF. This clear demarcation is essential for the reliable, state-machine-driven operation of the interception session.

The architecture relies on the CHI to ensure that complex, multi-step interception procedures are executed correctly. Upon receiving a PDU, the network entity (ICE or LEMF) first examines the CHI. Based on this identifier, it invokes the appropriate handler function and uses the corresponding ASN.1 structure definition to decode the remainder of the message body, which contains parameters like the target identifier (e.g., IMSI), interception scope, and delivery addresses. This separation of command identification (via CHI) from parameter parsing is a fundamental design pattern that enhances protocol robustness, simplifies implementation, and ensures that malformed or unexpected messages can be rejected or handled gracefully, which is paramount for a legally sensitive system.

In the broader LI architecture, the CHI's role is foundational but contained. It does not govern the interception logic itself but is the key that unlocks the correct interpretation of every transaction on the HI. Its standardized definition across all 3GPP-compliant network elements and LEMFs is what enables multi-vendor interoperability. A law enforcement agency can issue an interception order using equipment from vendor A, and it will be correctly understood and acted upon by a core network node from vendor B, precisely because both adhere to the same CHI values and associated message structures as codified in 3GPP TS 33.108 and the protocol-specific specs like TS 29.228 (for IMS). This interoperability is a non-negotiable requirement for lawful interception to function in modern, heterogeneous networks.

Purpose & Motivation

The Command Header Identifier (CHI) was created to solve a fundamental problem in automating and standardizing lawful interception across global telecommunications networks. Prior to comprehensive standards like those from 3GPP, interception mechanisms were often proprietary, vendor-specific, or country-specific. This created significant obstacles for law enforcement agencies (LEAs) who needed to intercept communications in networks built with equipment from multiple vendors, and for network operators who faced complex, costly integration challenges for every new LEA interface or network upgrade. The CHI, as part of the standardized HI protocol, provides a common 'language' for interception commands.

The specific purpose of the CHI is to ensure unambiguous communication. In a legally mandated and technically complex process like lawful interception, there is zero tolerance for misinterpretation. A command to 'activate interception' must never be mistaken for a 'delivery report.' The CHI field acts as this unambiguous label. Its creation was motivated by the need for a robust, state-aware protocol that could manage the full lifecycle of an interception—activation, periodic reporting, content delivery, and deactivation—over a potentially unreliable IP network connection between the LEA and the operator. By clearly identifying each message type, the CHI enables the receiving system to maintain correct session state and execute the correct procedures, which is critical for maintaining the integrity of evidence and complying with judicial warrants.

Furthermore, the CHI facilitates scalability and future-proofing. As new types of interception-related messages or enhanced capabilities are required (e.g., for new services like IMS or 5G), new CHI values can be defined and standardized without overhauling the entire protocol framework. This allows the lawful interception architecture to evolve alongside the network itself. The CHI, therefore, is not just a technical field but an enabler of a standardized, interoperable, and legally compliant interception ecosystem that balances operational needs for LEAs with the technical and business realities of network operators.

Key Features

• Uniquely identifies lawful interception command and report types
• Enables reliable parsing and processing of HI protocol messages
• Foundation for state-machine operation of interception sessions
• Ensures multi-vendor interoperability across LEMF and network equipment
• Facilitates unambiguous communication for legally sensitive operations
• Allows for protocol extensibility through definition of new values

Evolution Across Releases

Defining Specifications