Bearer Capability 1

Description

Bearer Capability 1 (BC1) is a fundamental information element within the 3GPP call control protocol, specifically used in the SETUP message for circuit-switched (CS) calls. It resides in the Bearer Capability information element, which describes the characteristics of the bearer service requested by the user equipment (UE) for a voice or data call. The BC1 parameter is defined as the 'first' or preferred bearer capability, allowing the UE to signal its primary service requirement to the network. The network uses this information, along with other parameters in the Bearer Capability IE, to perform compatibility checking, resource allocation, and interworking functions.

Architecturally, BC1 is processed by the core network's Mobile Switching Center (MSC) in GSM/UMTS. When a UE initiates a mobile-originated call, it includes the Bearer Capability information element in the SETUP message sent over the radio interface (via the Base Station Subsystem) to the MSC. The MSC analyzes the BC1 value to determine the type of bearer service being requested—such as speech, unrestricted digital information (UDI) for circuit-switched data, or 3.1 kHz audio. This analysis is critical for the MSC to select the correct codec, allocate a suitable traffic channel (TCH), and establish a compatible connection through the network, potentially involving interworking with the Public Switched Telephone Network (PSTN) or other PLMNs.

Technically, the BC1 parameter is encoded as a bit field within the Bearer Capability IE structure defined in 3GPP TS 24.008. Its value corresponds to a specific bearer service defined in the ITU-T I.200 series recommendations, which are mapped into 3GPP specifications. For example, a BC1 value indicating 'speech' tells the network to prepare for a voice call using a speech codec like AMR or EFR. The network's response in the CALL PROCEEDING or ALERTING message may include a Bearer Capability IE with a confirmed BC1 value, indicating the bearer service that will actually be used, which might differ from the request due to network capabilities or negotiation.

BC1's role extends beyond simple service indication; it is integral to service interworking and fallback procedures. In scenarios like circuit-switched fallback (CSFB) from LTE, the UE includes BC1 in the SETUP message to indicate the desired CS service (e.g., voice) when reverting to a 2G/3G network. Furthermore, BC1 supports dual-tone multi-frequency (DTMF) signaling compatibility and modem interworking for fax/data calls by specifying the appropriate bearer type. Its proper interpretation ensures end-to-service compatibility and quality of service (QoS) for the user, making it a cornerstone of traditional circuit-switched telephony services in 2G and 3G networks.

Purpose & Motivation

BC1 was created to enable service differentiation and reliable call setup in early digital cellular networks like GSM. Prior to standardization, there was a need for a structured way for a mobile terminal to signal what type of communication service it intended to establish—whether a standard voice call, a data call using a modem, or a fax transmission. The Bearer Capability information element, with BC1 as a key component, provided this mechanism, allowing the network to understand the service requirements and allocate appropriate network resources (e.g., a full-rate traffic channel for speech versus a data-optimized channel).

It solved the problem of service incompatibility and inefficient resource usage. Without a precise bearer capability indication, the network might assume a default service (like speech) for all calls, leading to failed data connections or poor voice quality. BC1 allowed for explicit negotiation, ensuring that if a user wanted to make a data call, the network would not attempt to use speech compression codecs that would corrupt the data stream. This was particularly important for early mobile data services and fax-over-cellular, which required transparent digital channels.

Historically, BC1's definition in Release 99 (and its carry-over from GSM Phase 2+) established a foundation for circuit-switched service control that persisted through UMTS. It addressed limitations of analog systems and early digital protocols that lacked detailed service descriptors. As networks evolved towards all-IP in LTE and 5G, the relevance of BC1 diminished for native packet-switched services, but it remained critical for legacy CS interoperability, CSFB, and ensuring backward compatibility for voice services during the transition to VoLTE and VoNR.

Key Features

• Indicates preferred circuit-switched bearer service type (e.g., speech, UDI, 3.1 kHz audio) in call setup
• Encoded within the Bearer Capability information element of call control messages (e.g., SETUP)
• Used by the MSC for resource allocation, codec selection, and interworking decisions
• Supports service negotiation and compatibility checking between UE and network
• Essential for circuit-switched fallback (CSFB) procedures from LTE to 2G/3G
• Enables interworking with PSTN and legacy data services (fax, modem)

Evolution Across Releases

Defining Specifications