Description
The Call Identifier Code (CIC) serves as a fundamental identifier in 3GPP circuit-switched networks, providing unambiguous identification of individual calls or physical transmission circuits. In its primary application as a Call Identifier Code, CIC uniquely identifies a specific call instance across multiple network elements and interfaces, allowing different nodes (such as MSC, GMSC, and MGW) to reference the same call consistently during setup, maintenance, and teardown procedures. This identifier is crucial for call correlation, billing records generation, and troubleshooting across distributed network architectures.
As a Circuit Identifier Code, CIC identifies specific physical or logical circuits within transmission systems, particularly in the context of interworking between different network domains. This usage is especially important in scenarios involving legacy circuit-switched networks and modern IP-based networks, where the CIC helps map traditional circuit identifiers to corresponding resources in packet-switched domains. The code follows specific numbering and formatting conventions defined in 3GPP specifications to ensure interoperability between equipment from different vendors.
The CIC operates within the signaling protocols defined in 3GPP specifications, particularly in ISUP (ISDN User Part) and BICC (Bearer Independent Call Control) protocols. During call setup, the originating exchange assigns a CIC value that remains associated with the call throughout its duration. This identifier appears in various signaling messages, including Initial Address Message (IAM), Answer Message (ANM), and Release Message (REL), enabling all participating nodes to maintain consistent call state information.
In network architecture, CIC plays a critical role in several key functions: it facilitates accurate billing by providing a reference point for charging records across multiple network elements; it enables efficient troubleshooting by allowing network operators to trace specific calls through the network; and it supports lawful interception requirements by providing a consistent identifier for targeted communications. The CIC's persistence throughout the call lifecycle makes it indispensable for maintaining call integrity in complex, multi-vendor network environments.
Purpose & Motivation
The CIC was created to address the fundamental need for unambiguous call identification in telecommunications networks. In early telephony systems, as networks grew in complexity and involved multiple switching centers, there was no standardized method to uniquely identify individual calls across different network elements. This limitation made call tracing, billing correlation, and fault isolation extremely challenging, especially in multi-vendor environments where different equipment manufacturers used proprietary identification schemes.
Prior to standardized identifiers like CIC, network operators faced significant operational challenges: billing disputes arose from inconsistent call records across network nodes; troubleshooting required manual correlation of multiple log files; and inter-carrier settlements were complicated by incompatible identification methods. The introduction of CIC in 3GPP specifications provided a standardized approach that enabled interoperability between different network elements and between networks operated by different service providers.
The historical context for CIC's development includes the transition from analog to digital switching and the increasing need for automated operations support systems. As networks evolved to support higher volumes of traffic and more complex services, manual methods of call identification became impractical. The CIC specification in 3GPP Release 5 formalized what had been evolving in various forms in earlier telecommunications standards, creating a consistent framework that could scale with the growth of mobile networks and support emerging requirements like number portability and advanced billing systems.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-5, normative work from Rel-15.
In Release 15, the primary updates to the CIC function involved reference updates for ISUP location parameters and the Q.850 location parameter to ensure alignment with current standards. Additionally, a change was introduced to enable the interworking of the Connected subaddress Information Element when it is carried within an ISUP CON (Connect) message. These modifications focused on maintaining interoperability and correct parameter handling in circuit-switched signaling.
- Interwork of Connected subaddress IE carried in ISUP CON message TS 29.163CR1026
- Reference Update for the ISUP location parameter TS 29.163CR1018
- Reference Update for the ISUP location parameter TS 29.163CR1020
- Reference Update for the ISUP location parameter TS 29.163CR1023
- Reference Update for the ISUP Q.850 location parameter TS 29.163CR1044
In Release 16, the enhancements for the CIC-related function focused on updating references and mappings for interworking with legacy ISUP signaling. Specifically, the release included reference updates for the ISUP Cause Location Parameter and defined the mapping of the SIP History-Info header field to the ISUP Original Called Number parameter.
Explore further
Broader topics and technologies where CIC plays a role.
Defining Specifications
3GPP specifications that define or reference CIC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.205 vj00 | Bearer Independent CS Core Network Stage 2 | Rel-19 |
| TS 29.163 vj00 | Interworking between 3GPP IM CN and CS networks | Rel-19 |
| TR 43.903 vj00 | Feasibility Study for A-interface over IP | Rel-19 |