CSFB

Circuit Switched Fallback

Mobility →
Introduced in Rel-8 Also in: Radio Access Network

CSFB is a 3GPP mechanism enabling LTE devices to access legacy circuit-switched voice and SMS services by temporarily falling back to 2G or 3G networks.

Category
Mobility
Introduced
Rel-8
Where
Core Network › 5G Core
Also touches
1 segments
Specifications
5 specs
CSFB Description Purpose Detected Changes Specifications

Description

Circuit Switched Fallback (CSFB) is a standardized mobility solution defined by 3GPP that enables User Equipment (UE) camped on an LTE network to access circuit-switched (CS) domain services—primarily voice calls and SMS—by temporarily redirecting the UE to a 2G (GERAN) or 3G (UTRAN) network that supports these legacy services. The architecture relies on tight integration between the LTE Evolved Packet Core (EPC) and the legacy Circuit Switched Core network, facilitated by the SGs interface between the Mobility Management Entity (MME) in the EPC and the Mobile Switching Center (MSC) Server in the CS core. This interface enables combined EPS/IMSI attach procedures, paging coordination, and mobility management for CS services while the UE is registered in LTE.

When a CSFB-capable UE performs initial attachment to the LTE network, it indicates CSFB capability to the MME, which then performs a combined EPS/IMSI attach via the SGs interface to register the UE both for LTE packet services and for CS services in the legacy MSC. The MSC maintains the UE's CS registration state and considers the UE to be in an 'SGs-associated' state, with the MME acting as a proxy for CS domain signaling. For mobile-terminated CS services (like an incoming voice call), the MSC sends a paging request via SGs to the MME, which then pages the UE over the LTE radio interface using S1-AP signaling. Upon receiving the page, the UE initiates CSFB procedures to transition to a 2G/3G cell.

The actual fallback mechanism involves several possible methods defined in 3GPP specifications. The most common is PS Handover, where the network prepares a handover of the UE from LTE to a 2G/3G cell with a dedicated traffic channel allocated for the CS call. Alternatively, Cell Change Order (CCO) or RRC Connection Release with Redirection can be used, where the UE is instructed to leave LTE and camp on a specified 2G/3G cell, then establish a CS connection there. The choice depends on network capabilities, UE support, and operator configuration. After the CS service (e.g., voice call) concludes, the UE typically returns to LTE using mechanisms like Fast Return or idle mode reselection, depending on network policies and UE capabilities.

Key network elements involved include the UE (which must support CSFB and the relevant 2G/3G radio access technologies), the eNodeB (which manages the radio resource control during fallback), the MME (which coordinates with the MSC and handles mobility management), and the MSC Server (which provides the CS service logic). The solution requires the LTE and 2G/3G coverage areas to overlap sufficiently, and the UE must support measurements and procedures for the target RAT. CSFB was a critical interim solution that allowed operators to launch LTE data services quickly while relying on mature, existing circuit-switched networks for voice, buying time for the development and deployment of native LTE voice solutions like VoLTE.

Purpose & Motivation

CSFB was created to address a fundamental challenge in the early deployment of LTE networks: LTE was designed as an all-IP, packet-switched-only system with no native support for circuit-switched services, yet voice telephony and SMS were essential revenue-generating services that operators could not abandon. When LTE was first standardized in Release 8, IP Multimedia Subsystem (IMS)-based Voice over LTE (VoLTE) was still immature, required significant IMS core deployment, and lacked widespread device support. Operators needed a practical way to offer voice services on their new LTE networks without waiting for full VoLTE ecosystems to develop.

The technology solved the problem of service continuity for subscribers migrating to LTE devices and networks. Without CSFB, LTE-only devices would have been unable to make or receive traditional voice calls, which would have severely limited LTE adoption. CSFB allowed operators to leverage their existing investments in circuit-switched core networks (MSCs) and radio access networks (GERAN/UTRAN) while rolling out LTE for high-speed data. It provided a bridge technology that ensured subscribers could use a single device for both LTE data and legacy voice, with seamless fallback triggered automatically when a voice call was initiated or received.

CSFB addressed specific limitations of previous approaches, which might have involved dual-radio devices operating simultaneously on LTE and 2G/3G, leading to higher battery consumption and cost. By standardizing the fallback procedures, 3GPP enabled efficient, network-controlled mobility between RATs. It also solved the paging coordination problem—ensuring that incoming CS calls could reach a UE camped on LTE through signaling between the MME and MSC. This made LTE deployment commercially viable in the 2010-2015 timeframe, serving as the dominant voice solution for LTE until VoLTE matured and became widely deployed.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (5 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.

Rel-15 3 changes

In Release 15, the CSFB function was updated with specific corrections to improve reliability. These included corrections to the fallback procedure during RRC connection establishment and to the intra-band fallback behavior when using FeatureSetsPerCC. Furthermore, a correction was made to the dedicated PUCCH configuration used for the fallback configuration.

  • Correction to fallback to the RRC connection establishment TS 36.331CR3918
  • Correction on intra-band fallback behavior with FeatureSetsPerCC TS 36.331CR3990
  • Correction to pucch-ConfigDedicated for fallback configuration TS 36.331CR3277
Rel-16 2 changes

In Release 16, the CSFB function was updated with the introduction of a new voice fallback indication. A further correction was made regarding the establishment cause value used during the procedure for enhanced EPS voice fallback.

  • Introduction of voice fallback indication TS 36.331CR4136
  • Correction on establishment cause value upon enhanced EPS voice fallback TS 36.331CR4236

Explore further

Broader topics and technologies where CSFB plays a role.

Defining Specifications

3GPP specifications that define or reference CSFB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 48.008 vj00 BSS-MSC Interface Layer 3 Procedures Rel-19