Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Mobility

CSFB

Circuit Switched Fallback

Mobility →

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.

Introduced
Rel-8
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
5 specs
CSFB Description Purpose What changed Family Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define CSFB. Each summary describes the whole specification, not only this term.

TS 23.221Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.221: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.221 →
TS 24.292Rel-12 → Rel-13

Rel-13 added mSRVCC message interworking: CGI/UTRAN SAI parameter inclusion is conditional on availability, and MSC Server can subscribe to conference event package.

Full comparison in TS 24.292 →

Technology family

Voice service evolution · Services › IMS

  1. R96 CS voice
  2. Rel-8 1xCSFB, CSFB, ICS, SRVCC
  3. Rel-9 VoLTE
  4. Rel-10 SRVCC enhanced with ATCF
  5. Rel-11 CS to PS SRVCC, vSRVCC
  6. Rel-12 DRVCC
  7. Rel-15 Emergency Services Fallback, EPS fallback, VoNR
  8. Rel-16 5G-SRVCC

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 sources

Documented changes in 10 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.

Rel-8 introduced

CSFB is specified for the first time in Rel-8: TS 23.272 defines CS fallback in EPS, including combined attach/TAU with SMS-only and CSFB Not Preferred indications, and TS 24.301 defines the CSFB response paging handling.

  • “informs the network that the UE is capable and configured to use CS fallback and/or SMS over SGs” TS 23.272 v8.12.0
  • “The purpose of the CSFB response information element is to indicate whether the UE accepts or rejects a paging for CS fallback.” TS 24.301 v8.10.0
  • “the network initiates CS fallback procedures.” TS 24.301 v8.10.0
Rel-9 specification text

CSFB procedures were extended and corrected in Rel-9, adding emergency-call CSFB handling (SGs association state), CS PLMN selection for CSFB, and enhanced 1xRTT CS fallback operation.

  • “When MME detects that the CSFB request is due to emergency call and eNodeB indicates that the UE is not available for the PS service” TS 23.272 v9.15.0
  • “The PLMN selected for CS should be the same that is used for this UE as a target PLMN for PS handovers” TS 23.272 v9.15.0
  • “CS PLMN determination for CSFB” TS 29.118 v9.9.0
Rel-10 specification text

Rel-10 added CSFB priority call handling (MPS): the MME and eNodeB give preferential treatment to priority CSFB requests and the MME sets a "CSFB High Priority" indication towards the eNodeB.

  • “The MME provides preferential treatment to this request and also sets priority indication, i.e. "CSFB High Priority", in the S1AP UE Context Setup/Modification message” TS 23.272 v10.15.0
  • “the eNodeB should provide preferential treatment, e.g. in allocating E-UTRAN radio bearer resources compared to other normal resource requests” TS 23.272 v10.15.0
  • “the service request procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process.” TS 24.301 v10.15.0
Rel-11 1 CR

CSFB gained new behaviour in Rel-11: return to the last used LTE PLMN after CSFB, CSFB indication to MSC and SGSN, and an SRVCC- and CSFB-capable MSC/VLR selected at combined attach/TAU.

  • “Indicating to the MSC that the MO CS service is due to CSFB as specified in TS 29.118 [44].” TS 23.272 v11.10.0
  • “Indicating to the SGSN that the mobility procedure is due to CSFB by adding an indication in Forward Relocation Request and Context Response” TS 23.272 v11.10.0
  • How CSFB UE return back to the former LTE PLMN TS 23.272CR0874
Rel-12 1 CR

CSFB gained new behaviour in Rel-12: a 'CSFB High Priority' indication for priority and emergency calls, last-used-PLMN return handling, and UE TAU/service request handling after failed or cancelled CSFB.

  • “it also sets priority indication, i.e. "CSFB High Priority", in the S1AP message to the eNodeB as specified in TS 36.413 [35].” TS 23.272 v12.6.0
  • “If configured to support the return to the last used PLMN after CSFB, the MME sends a MO CSFB indication via SGs to the MSC” TS 23.272 v12.6.0
  • New CSFB high priority indication for eMPS and emergency call TS 23.272CR0931
Rel-13 1 CR

CSFB behaviour was corrected and extended in Rel-13: a corrected MO CSFB condition, CSFB handling in attempting states, TAU triggers, and CSFB after TAU reject causes #9, #10 or #40.

Rel-14 1 CR

TS 24.301 gained new CSFB handling: MO/MT CSFB in EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, voice domain preference changes, skipping the back-off timer for emergency CSFB calls, and TAU initiation after CSFB failure.

  • “Handling of MO/MT CSFB in EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM” TS 24.301 v14.10.0
  • “Skip back-off timer for emergency CSFB call” TS 24.301 v14.10.0
  • TAU procedure initiation following CSFB failure or CSFB cancellation TS 24.301CR2838
Rel-15 2 CRs

In Rel-15, MT CSFB handling in the UE changed: a new timer T3417ext-mt is started when accepting paging in EMM-CONNECTED mode, and timer expiry during the extended service request procedure is handled.

  • “the UE shall send an EXTENDED SERVICE REQUEST message with the CSFB response IE indicating "CS fallback accepted by the UE", start T3417ext-mt” TS 24.301 v15.8.0
  • Handling of timer expiry during extended service request procedure for MT CSFB TS 24.301CR2900
  • Correction to MT CSFB call failure problem in CONNECTED mode TS 24.301CR2913
Rel-16 3 CRs

CSFB emergency call handling in TS 24.301 was corrected: emergency CSFB for system-fallback UEs, MO CSFB emergency in ATTEMPTING-TO-UPDATE-MM, and no CSFB after emergency services fallback from 5GS.

  • Correct emergency CSFB for UE's performing system fallback TS 24.301CR3224
  • Correction to Handling of MO CSFB Emergency call in EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM TS 24.301CR3367
  • No CSFB following emergency services fallback from 5GS TS 24.301CR3410
Rel-17 2 CRs

TS 24.301 in Rel-17 corrects the inclusion condition of the CSFB response IE and handles the collision of the TAU procedure for RACS with the ESR procedure for CSFB.

  • Collision of TAU procedure for RACS and ESR procedure for CSFB TS 24.301CR3530
  • Correction on inclusion condition of CSFB response IE TS 24.301CR3742

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 read
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 48.008 vj00 BSS-MSC Interface Layer 3 Procedures Rel-19 read