Description
Backward Call Indicators (BCI) are a collection of parameters transmitted in the backward direction (from the called party's network toward the calling party's network) within ISDN User Part (ISUP) and Bearer Independent Call Control (BICC) signaling messages. These indicators are defined in 3GPP TS 29.163 as part of the Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks specification. The BCI parameters are carried in specific information elements that provide essential details about the call's termination side to the originating network.
During call setup procedures, when a call traverses from a CS network to an IP Multimedia Subsystem (IMS) network or vice versa, the BCI parameters are extracted from incoming ISUP messages and mapped to appropriate SIP headers or BICC parameters. This mapping occurs at the Media Gateway Control Function (MGCF) or other interworking functions. The BCI includes critical information such as the nature of the called party's line, whether the called party is a payphone, whether echo control devices are present, and other network-specific characteristics that affect call handling.
Key components of BCI include parameters like the Called Party's Status Indicator, which indicates whether the called party is free, busy, or has an unknown status; the Charge Indicator, which provides information about charging arrangements; and the Echo Control Device Indicator, which signals whether echo control is required. These parameters are encoded as bit fields within specific octets of the signaling messages, allowing for efficient transmission while maintaining backward compatibility with legacy systems.
The role of BCI in the network is crucial for maintaining service quality and proper call routing across heterogeneous network environments. When a call originates in a CS network and terminates in an IMS network, the BCI parameters ensure that the IMS network can apply appropriate policies and treatments based on the characteristics of the originating network. Similarly, when calls flow in the opposite direction, BCI helps the CS network understand the capabilities and requirements of the IMS network, enabling seamless service delivery across network boundaries.
Purpose & Motivation
BCI was created to address the challenges of interworking between circuit-switched and packet-switched networks during the transition to all-IP networks. As telecommunications evolved from traditional PSTN/ISDN networks to IP-based IMS architectures, there was a critical need to preserve call-related information that was essential for proper call handling, billing, and service quality. Without BCI, important parameters about the called party's line characteristics and network conditions would be lost when calls crossed network boundaries, leading to degraded service quality and incorrect billing.
Historically, ISUP signaling in CS networks contained numerous parameters that provided detailed information about call characteristics, but these parameters were not natively supported in IP-based signaling protocols like SIP. The creation of BCI provided a standardized mechanism to map these critical parameters between different signaling domains. This was particularly important during the early phases of IMS deployment when most calls still originated or terminated in legacy CS networks, requiring robust interworking solutions.
BCI solves the problem of information loss during network transitions by ensuring that essential call parameters are preserved and properly interpreted across different network generations. It addresses limitations of previous approaches that either dropped important signaling information or used proprietary mapping solutions that hindered interoperability between equipment from different vendors. By standardizing the backward call indicators in 3GPP specifications, network operators could deploy multi-vendor solutions while maintaining consistent call handling and service quality across hybrid network environments.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the work on the Backward Call Indicators (BCI) function focused on corrections and reference updates for its interworking, specifically addressing the mapping of the ISUP location and Q.850 location parameters. This ensured proper protocol conversion between SIP in the IMS and ISUP in legacy CS networks at the Media Gateway Control Function (MGCF). The release also included interworking corrections for the Connected subaddress Information Element carried in the ISUP CON message.
- 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
- Correction of the Backward call indicators parameter interworking TS 29.163CR1031
- Reference Update for the ISUP Q.850 location parameter TS 29.163CR1044
In Release 16, the enhancements for the Backward Call Indicators (BCI) function included a reference update for the ISUP Cause Location parameter to align with a new IETF RFC and defined the mapping of the SIP History-Info header field to the ISUP Original Called Number parameter. These updates provided more precise protocol interworking between SIP in the IMS and legacy ISUP networks at the Media Gateway Control Function (MGCF). The changes ensured improved support for call diversion history and cause code information transfer across network domains.
Explore further
Broader topics and technologies where BCI plays a role.
Defining Specifications
3GPP specifications that define or reference BCI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.163 vj00 | Interworking between 3GPP IM CN and CS networks | Rel-19 |