Circuit-Switched Fallback (CSFB) and the SGs Interface
Early LTE deployments were primarily designed for packet data services and lacked native voice support. To address this gap, 3GPP introduced Circuit-Switched Fallback (CSFB) in Release 8, allowing a UE attached to LTE to temporarily fall back to a legacy circuit-switched network — GERAN or UTRAN — to access voice and other CS-domain services, such as CS Unrestricted Digital Information (UDI) video, Location Services (LCS), and Unstructured Supplementary Service Data (USSD), by reusing existing CS infrastructure, whenever suitable legacy radio coverage is available.
However, once a UE is attached to LTE, it is no longer directly connected to the legacy circuit-switched domain. Consequently, the MSC Server cannot page the UE for an incoming circuit-switched call. The network therefore requires mechanisms to coordinate subscriber registration between the EPS and circuit-switched domains, and to support SMS delivery while the UE remains on LTE.
To address these requirements, 3GPP introduced the SGs interface between the Mobility Management Entity (MME) and the Mobile Switching Centre (MSC) Server. The SGs interface enables the delivery of circuit-switched paging messages towards the LTE/EPS domain, and supports combined EPS and International Mobile Subscriber Identity (IMSI) attach and detach procedures, thereby allowing the network to maintain both packet-switched and circuit-switched service contexts simultaneously. In addition, the SGs interface is also used to support the delivery of Short Message Service (SMS) messages while the UE remains attached to LTE.
Deployment Scenarios
1. Operator has deployed only LTE and IMS is not yet deployed
When a UE is being served by E-UTRAN and overlapping GERAN or UTRAN coverage is also available, the UE is allowed to fall back to GERAN or UTRAN through Circuit-Switched Fallback (CSFB) in EPS to enable the provision of voice and other circuit-switched (CS) domain services.
2. Operator has deployed IMS, but LTE coverage is not yet universal
CS Fallback and IMS-based services co-exist within the same operator's network. IMS-based services, including VoLTE, are used to provide voice and the other services listed above while the UE is within LTE coverage. CSFB continues to provide these services when the UE is in an area covered only by GERAN or UTRAN, without any overlapping LTE (and hence IMS) coverage.
SMS Only over SGs
Mobile-originated (MO) and mobile-terminated (MT) SMS are delivered through the SGs interface, without invoking CS Fallback to GERAN or UTRAN. This is useful when a subscriber's home operator does not support SMS delivery through IMS, and the subscriber roams into a visited PLMN that provides only LTE coverage. In such cases, the visited operator can deploy a single MSC with an SGs interface to handle SMS delivery for such subscribers.
3GPP TS 23.272 lists “Multiple PLMNs selection for the CS domain” as one of the defined functions of a CS Fallback and/or SMS-over-SGs enabled MME, alongside RAT selection for the CS domain and VLR/LAI derivation.
Multiple PLMN Selection for the CS Domain
In network sharing deployments, a single radio access network is shared by multiple mobile operators, each operating its own core network and PLMN identity. There are two configurations:
- Multi-Operator Core Network (MOCN) — Only the radio access network is shared, while each operator retains a separate, independent core network.
- Gateway Core Network (GWCN) — The radio access network and also core network nodes are shared among operators.
In such a shared radio network, more than one PLMN may be broadcast as available for the CS domain at a given cell. When a UE requiring CS Fallback registers or requests service, the MME will select one of the available PLMNs and the corresponding operator's MSC Server. This selection is based on PLMN information provided by the eNodeB, the UE's current Tracking Area Identity (TAI) and previously used Location Area Identity (LAI), and locally configured operator selection policies for the preferred CS-domain RAT. The MME then includes the selected PLMN identity in the Location Area Identity (LAI) it allocates to the UE, which is passed to both the UE and the MSC/VLR, ensuring the UE is directed to a CS network belonging to the correct, consistently-selected operator — the same operator subsequently used for any related PS handovers or other CSFB mobility procedures.
“Supporting UEs” can recognize network sharing and indicate their preferred core network operator to the RAN, whereas for “non-supporting UEs,” the shared network itself selects an operator - with redirection to another operator's core network possible if the first-chosen one cannot serve the UE.
Roaming Subscribers and CSFB
When a subscriber roams onto a visited network (VPLMN) that has deployed both LTE and 2G/3G, CSFB uses the visited operator's own CS network — the UE falls back to the VPLMN's GERAN/UTRAN. Roaming introduces a specific complication for mobile-terminated (incoming) calls: the MSC/VLR that initially sends the CS paging request may differ from the MSC/VLR the UE ultimately registers with after falling back, due to MSC/VLR pool boundaries in the visited network. TS 23.272 defines two mechanisms to address this — Mobile Terminating Roaming Retry or the lower-latency Mobile Terminating Roaming Forwarding — and allows operators to choose between them by policy. A related mechanism tracks the “last used LTE PLMN ID” across nodes, helping the UE return efficiently to the correct visited-network LTE cell once the CS call ends.
Roaming Retry for CSFB
This procedure is applicable for mobile terminated calls where the MSC, to which the UE sends the LAU, is different from the MSC that sent the paging message to the UE. The procedure is based on the 'Mobile Terminating Roaming Retry Call' procedure defined in TS 23.018 and there is an only minor adaptation of the procedure to support CS fallback. UE includes the "CSMT" flag in the location update request message so that the signalling link is maintained for longer in case the IAM is delayed by the HLR.
Roaming Forward for CSFB
This procedure is applicable for mobile terminated calls where the MSC, to which the UE sends the LAU, is different from the MSC that sent the paging message to the UE. The procedure is based on the 'Mobile Terminating Roaming Forward Call’ procedure defined in TS 23.018 and there is an only minor adaptation of the procedure to support CS fallback. UE includes the "CSMT" flag in the location update request message so that the signalling link is maintained for longer in case the IAM is delayed by the HLR. Terminating Roaming Retry (MTRR) The UE includes the "CSMT" flag in the location update request message so that the signalling link is maintained for longer in case the IAM is delayed by the old MSC/VLR.
A note on MTRR and MTRF
Mobile Terminating Roaming Retry (MTRR)
In case of a Mobile terminating call, during the call routing to the VMSC, if the subscriber moves to a new VMSC call, old VMSC shall instruct to GMSC to release the ISUP connection to old VMSC and retry the terminating call setup towards the new MSC.
When a terminating call arrives at the GMSC, the GMSC sends a Send Routing Information (SRI) request to the HLR (HSS). The HLR (HSS) responds with an SRI Ack identifying the subscriber's current serving MSC/VLR. The GMSC routes the call to this MSC.
However, if the subscriber has since moved to a new VLR, the GMSC's routing information is now stale — the old VLR pages for a subscriber who is no longer there, and the call would fail.
Old VMSC Receives a MAP Cancel Location Message while paging is going onProvided the GMSC, HLR (HSS), and MSC/VLR all support MTRR, HLR (HSS) will send a MAP Cancel Location message message to the old VLR upon receipt of the MAP Update Location from the new VLR. The old MSC/VLR stops paging, if paging was ongoing, and sends a Resume Call Handling (RCH) message to the GMSC with the MT Roaming Retry Information Element (IE). Upon receipt of the RCH message with the MT Roaming Retry IE, the GMSC acknowledges the RCH message, releases the call towards the old MSC/VLR, and re-sends a new SRI to the HLR (HSS). The HLR (HSS) responds back with an SRI Ack identifying the subscriber's new serving MSC/VLR, and the GMSC routes the call to the new MSC.
Mobile Terminating Roaming Forward (MTRF)
In case of a Mobile terminating call, during the call routing to the VMSC, if the subscriber moves to a new VMSC call, old VMSC shall forward the call to new MSC.
Old VMSC Receives a MAP Cancel Location Message while paging is going onAn HLR supporting the "mobile terminating roaming forwarding" feature will send a MAP Cancel Location message to the old VLR upon receipt of the MAP Update Location from the new VLR. If the old VLR receives a MAP Send Identification message containing the MTRF Supported flag it shall not trigger any MAP Provide Roaming Number request to the new terminating VLR until is has received the MAP Cancel Location message. Upon receipt of a MAP Cancel Location message while ongoing paging, the old VLR shall send a MAP Provide Roaming Number request (including the MTRF Indicator and the parameters received from the HLR in the MAP Provide Roaming Number) to the new terminating VLR. The new terminating MSC/VLR shall then allocate an MSRN to allow the call to be routed from the old MSC to the new MSC and send it to the old VLR within the MAP Provide Roaming Number response.
References:
3GPP TS 23.018 and TS 23.272