Description
Bearer Independent Call Control (BICC) is a signalling protocol architecture standardized by 3GPP that decouples call control from the underlying bearer technology. It was developed to allow traditional narrowband ISDN User Part (ISUP) services to be provided over a variety of transport networks, including ATM and IP. BICC is defined primarily in 3GPP Technical Specifications 23.153 (out-of-band transcoder control), 23.205 (bearer-independent circuit-switched core network), 23.231 (SIP-I and BICC interworking), and 24.259 (BICC interworking with SIP-I). The protocol stack consists of a call control layer (BICC CS) and a bearer control layer (BICC BC). The call control layer is based on ISUP messages but is extended to support bearer-independent operation, while the bearer control layer uses protocols such as IPBCP (IP Bearer Control Protocol) or AAL2 signalling to set up and manage the actual transport bearers. This separation allows the call control function to be located in a Media Gateway Controller (MGC) or Softswitch, while the bearer is terminated in a Media Gateway (MGW). The MGC and MGW communicate via the H.248/Megaco protocol, which is used to control the media gateway resources.
The BICC architecture introduces the concept of a Serving Node (SN) and a Gateway Node (GN). The SN handles the call control and service logic, while the GN provides the bearer interworking between different transport technologies. The BICC protocol supports the Nc interface between MGCs and the Mc interface between MGC and MGW. The Nc interface uses BICC signalling to establish, modify, and release calls, and to negotiate bearer characteristics. The Mc interface uses H.248 to control the media gateway, including bearer establishment, modification, and release. BICC also defines the Nb interface between media gateways for bearer transport. The protocol supports both ATM and IP transport for the bearer, and it can interwork with legacy ISUP networks through a gateway function.
One of the key features of BICC is its ability to support the full set of ISUP supplementary services, such as call forwarding, call waiting, and conference calling, even when the bearer is packet-based. This is achieved by carrying the ISUP parameters in BICC messages and mapping them to the appropriate bearer control actions. BICC also supports the separation of call and bearer control, which allows for more efficient use of network resources and enables the deployment of a distributed architecture. The protocol includes mechanisms for bearer establishment, such as the 'forward bearer establishment' and 'backward bearer establishment' procedures, which allow the bearer to be set up either before or after the called party answers. BICC also supports the negotiation of codecs and other bearer characteristics through the use of the BICC Bearer Control Protocol (BCP).
In a typical BICC call flow, the calling party's MGC receives an ISUP IAM message from the access network. The MGC then sends a BICC IAM message to the called party's MGC over the Nc interface. The called party's MGC may then instruct its MGW to set up a bearer using H.248. Once the bearer is established, the called party's MGC sends a BICC ANM message back to the calling party's MGC, and the call is connected. The BICC protocol also supports mid-call bearer modification, which allows the bearer characteristics to be changed during a call, for example to support codec changes or to add media streams. BICC is an important enabler for the migration of traditional circuit-switched networks to packet-switched networks, as it allows operators to reuse their existing ISUP-based services while taking advantage of the cost and flexibility benefits of packet transport.
BICC has been widely deployed in 3GPP networks, particularly in the core network for voice services. It is used in the IMS (IP Multimedia Subsystem) for interworking with circuit-switched networks, and it is also used in the CS domain of 3GPP networks for call control between MSCs and MGWs. The protocol continues to be relevant in the context of 5G, where it can be used for voice over NR (VoNR) interworking with legacy networks. BICC is specified in a number of 3GPP releases, and its latest enhancements are included in Release 19. The protocol is also used in other standards bodies, such as ITU-T, where it is known as BICC (Bearer Independent Call Control) and is specified in Q.1902 series recommendations.
Purpose & Motivation
BICC was created to address the limitations of traditional circuit-switched networks, which were based on TDM (Time Division Multiplexing) technology and were inflexible and expensive to scale. As operators began to deploy packet-switched networks based on ATM and IP, they needed a way to provide the same voice services over these new transport technologies without having to redesign their entire service infrastructure. BICC solves this problem by separating call control from bearer control, allowing the call control to remain based on ISUP while the bearer can be any packet technology. This separation also enables a distributed architecture where the call control and bearer functions can be located in different network elements, leading to more efficient use of resources and easier scalability.
Another motivation for BICC was the need to support the full set of ISUP supplementary services over packet networks. Previous approaches, such as simply carrying ISUP over IP (ISUP over IP), did not provide a clean separation of call and bearer control and were not well-suited for a distributed architecture. BICC provides a standardized way to carry ISUP parameters and to map them to bearer control actions, ensuring that services like call forwarding, call waiting, and conference calling work seamlessly over packet transport. BICC also supports the interworking of different transport technologies, such as ATM and IP, which was important during the transition period when operators had a mix of transport technologies in their networks.
Finally, BICC was designed to be extensible and to support future services. It includes mechanisms for negotiating bearer characteristics, such as codecs and bandwidth, and it supports mid-call bearer modification. This makes it suitable for a wide range of services, including voice, video, and multimedia. BICC has been adopted by 3GPP as the standard for bearer-independent call control in the core network, and it continues to be enhanced in subsequent releases to support new requirements, such as interworking with IMS and 5G networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define BICC. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.153: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.153 →Rel-19 brings only minor changes to TS 23.205: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.205 →Technology family
Core signalling protocols · Core Network
- Phase 1 MAP
- Phase 2 ISUP
- R96 CAP
- R99 GTP-C, GTP-U, GTPv1-C
- Rel-4 BICC
- Rel-5 Diameter, SIP
- Rel-8 GTPv2-C
- Rel-14 PFCP
- Rel-15 HTTP/2 SBI
Also in this family (introduction release not pinned to a single defining specification): INAP, M2PA, SIGTRAN
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 7 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
TS 23.153 v4.0.0 first specifies out-of-band transcoder control over BICC on the Nc interface, including Supported, Available and Selected Codec lists and BICC CS2 APM-based codec negotiation procedures.
- “The OoBTC signalling procedures shall be supported by the call control protocol on the Nc interface, for example codec negotiation, codec modification” TS 23.153 v4.14.0
- “Supported Codecs List (BICC) – this list is used on NNI (BICC) OoBTC signalling.” TS 23.153 v4.14.0
- “Available Codecs List (BICC) – this is the list of codecs available for the NNI connection.” TS 23.153 v4.14.0
BICC codec negotiation (Supported/Available Codecs List) was extended to cover AMR-WB and GERAN Iu mode, including AMR-WB single codec handling and selected-codec inclusion criteria.
- “If a Single Codec information element for an AMR-WB codec is included in the Supported Codecs List (BICC), the intermediate node shall” TS 23.153 v5.12.0
- “In UTRAN or GERAN Iu mode, when constructing the codec configurations for AMR or AMR-WB codecs in the Supported Codecs List (BICC)” TS 23.153 v5.12.0
- “If the Selected Codec (BICC) is an AMR-WB codec, it shall be considered as included in the Available Codecs List (BICC)” TS 23.153 v5.12.0
BICC interworking is specified for the first time: TS 29.163 gains BICC forward bearer establishment procedures and TS 29.332 gains a clause on transactions for terminations towards BICC networks.
- “Figure 37 shows the message sequence chart for the CS network originating session with BICC forward bearer establishment.” TS 29.163 v6.12.1
- “This Clause is only applicable for terminations towards BICC Networks. The support of terminations towards BICC networks is optional.” TS 29.332 v6.14.0
- “17 Transactions towards BICC” TS 29.332 v6.14.0
Interworking specs extended BICC handling: 29.163 adds BICC+STCmtp interworking and multimedia/data calls, 29.332 adds BICC termination types and procedures, and 23.153 changes the BICC Supported Codec List ordering.
- “principles of interworking between the 3GPP IM CN subsystem and BICC/ISUP based legacy CS networks, in order to support IM basic voice, data and multimedia calls” TS 29.163 v7.28.0
- “BICC IP (meaning applies to terminations towards BICC with IP transport)” TS 29.332 v7.12.0
- “using a Supported Codec List (BICC) ordered as:” TS 23.153 v7.2.0
Rel-8 adds BICC-related interworking: overlap signalling (SAM) interworking between SIP and BICC/ISUP in 29.163, and a new SIP-I to BICC network interworking clause in 29.235.
- “the I-MGCF shall generate a SAM and pass it to outgoing BICC/ISUP procedures.” TS 29.163 v8.32.0
- “The following subclauses define the signalling interworking between the Bearer Independent Call Control (BICC) protocol” TS 29.235 v8.9.0
- “When creating the Supported Codecs List (BICC or SIP-I), only codecs supported in GERAN with either "Full IP" or TFO shall be included” TS 23.153 v8.3.0
TS 29.163 added BICC-specific interworking content in Rel-10: a message sequence chart for CS-network-originating session setup with BICC (IMS CAT, early session) and new SIP/ISUP-BICC interworking subclauses at I-MGCF and O-MGCF.
- “shows an example message sequence chart for an CS network originating Session Setup with BICC, where IMS CAT is provided by early session model.” TS 29.163 v10.22.0
- “9.2.11.1a Incoming Call Interworking from SIP to ISUP/BICC at I-MGCF” TS 29.163 v10.22.0
- “9.2.11.1b Outgoing Call Interworking from ISUP/BICC to SIP at O-MGCF” TS 29.163 v10.22.0
BICC codec negotiation in TS 23.153 was extended to cover EVS codecs, with new rules for Supported, Selected and Available Codecs Lists and EVS configuration handling.
- “If a Single Codec information element for the UMTS_EVS codec type is included in the Supported Codecs List (BICC), the intermediate node shall:” TS 23.153 v13.2.0
- “if the Selected Codec (BICC) is an EVS codec, the terminating MSC Server shall specify exactly one configuration” TS 23.153 v13.2.0
- “If the Single Codec Information Element is included in a Selected Codec (BICC), only Config-EVS-Code is included.” TS 29.163 v13.13.0
Defining Specifications
3GPP specifications that define or reference BICC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.153 vj00 | Out-of-Band Transcoder Control Stage 2 | Rel-19 read |
| TS 23.205 vj00 | Bearer Independent CS Core Network Stage 2 | Rel-19 read |
| TS 23.231 vj00 | SIP-I based CS core network stage 2 | Rel-19 read |
| TR 23.977 vj00 | Bandwidth/Resource Savings & Speech Quality Requirements | Rel-19 read |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 read |
| TS 24.292 vj00 | IMS Centralized Services (ICS) Protocol | Rel-19 read |
| TS 26.454 vj00 | EVS Codec Mapping for 3G CS Networks | Rel-19 read |
| TS 29.163 vj00 | Interworking between 3GPP IM CN and CS networks | Rel-19 read |
| TS 29.205 vj00 | BICC Protocols for Bearer-Independent CS Core Network | Rel-19 read |
| TS 29.231 vj00 | Application of SIP-I Protocols to CS Core Network | Rel-19 read |
| TS 29.232 vj00 | Mc Interface Protocol Profile | Rel-19 read |
| TS 29.235 vj00 | SIP-I CS Core Network Interworking | Rel-19 read |
| TS 29.332 vj00 | MGCF-IM-MGW Interface Protocol (Mn) | Rel-19 read |
| TS 29.414 vj00 | Nb Interface Bearer Transport & Control Protocols | Rel-19 read |
| TS 32.408 vj00 | UMTS/GSM Performance Management Measurements | Rel-19 read |
| TS 48.103 vj00 | A Interface User Plane Transport Protocols | Rel-19 read |