SS7 Interworking With LTE Through SGs And CSFB
LTE was designed around packet services, while traditional mobile voice depends on circuit-switched core networks and SS7 procedures. The SGs interface provides a bridge between the LTE Mobility Management Entity (MME) and the legacy Mobile Switching Centre (MSC), allowing operators to support voice and SMS while moving customers towards an all-IP architecture.
Circuit Switched Fallback (CSFB) uses that bridge when an LTE handset needs a circuit-switched call. The device leaves LTE temporarily, registers with the older radio access network, and places or receives the call through the MSC. Understanding this process requires knowledge of LTE mobility, SGsAP, MAP, ISUP, MTP3, and practical call-routing behaviour.
Why LTE Still Needs Legacy Voice
LTE packet data does not inherently provide traditional telephony. A network with no IMS voice service can still offer voice by directing an LTE-attached handset to 2G or 3G for the call. The MSC then handles call control, supplementary services, charging, and interconnection with the PSTN.
CSFB was especially useful during early LTE rollouts, when operators had broad legacy radio coverage but limited VoLTE deployment. It allowed customers to browse over LTE and continue making ordinary mobile calls without waiting for a complete IMS rollout.
How The SGs Interface Connects Networks
SGs links the MME in the EPC with an MSC Server or MSC. Its signalling uses SGsAP over SCTP and IP, while the MSC continues to interact with the circuit-switched core using established protocols such as BSSAP, MAP, and ISUP. The interface carries mobility coordination, paging, location updates, and SMS-related procedures.
The MME maintains an association between the LTE subscriber and the serving MSC. When an incoming call arrives, the MSC can request paging through SGs. The MME then pages the handset over LTE, and the device responds by initiating a fallback procedure. Engineers troubleshooting SCTP associations can review M3UA management messages alongside SGs and MME logs.
What Happens During A CSFB Call
For a mobile-originated call, the handset sends an Extended Service Request to the MME, indicating that a circuit-switched voice service is required. The MME coordinates with the MSC and radio network, after which the handset moves to a suitable GERAN or UTRAN frequency. The call then proceeds through normal circuit-switched signalling.
For a mobile-terminated call, the MSC sends an SGs paging request towards the MME. Once the handset answers, the network supplies the required redirection or handover information. Timings matter: delayed paging, unsuccessful radio reselection, or a lost SGs association can produce call setup failures that users describe simply as “it won’t connect”.
SMS over SGs follows a related model. Mobile-originated and mobile-terminated SMS can use the LTE attachment and MSC relationship without requiring a voice bearer. This made SGs valuable even for customers who rarely used CSFB voice.
Comparing Voice Delivery Options
| Feature | CSFB | VoLTE | Legacy 2G/3G Voice |
|---|---|---|---|
| Primary access | LTE with fallback | LTE packet bearer | GERAN or UTRAN |
| Core service | MSC circuit switching | IMS | MSC circuit switching |
| Call setup | Usually slower | Usually faster | Established legacy process |
| LTE data during call | Interrupted or restricted | Continues normally | Not applicable |
| Main dependency | SGs, legacy radio, MSC | IMS, SBC, QoS, EPC | Legacy radio and SS7 |
| Long-term role | Transitional | Strategic | Retirement path |
VoLTE removes the need for radio fallback by keeping voice on LTE, but it introduces IMS registration, SIP, policy control, dedicated QoS, and interoperability requirements. CSFB remains simpler in some environments, although it is less attractive where older radio networks are being retired.
Timers, Routing And SS7 Dependencies
Successful interworking depends on consistent subscriber data and routing. The HLR, VLR, MME, MSC, and radio network must agree on the subscriber’s location and service state. MAP procedures support mobility and SMS, while ISUP controls the circuit-switched call path towards other mobile networks, fixed operators, and international gateways.
Routing errors may appear as missing subscriber information, incorrect called-party numbers, or failed inter-operator termination. Supplementary services add further complexity; for example, ISUP call diversion can alter forwarding indicators and affect how downstream switches interpret the call.
Timers should be reviewed across the full chain rather than in isolation. SGs paging, NAS service requests, radio redirection, MSC call setup, and ISUP Address Complete Messages all contribute to the user’s perceived delay. A mismatch can cause duplicate paging, premature release, or a call that reaches voicemail unexpectedly.
Australian Deployment Realities
Australia provides a useful example of why migration planning matters. Telstra, Optus, and Vodafone-TPG have operated with different coverage footprints, spectrum strategies, and roaming arrangements across Sydney, Melbourne, Brisbane, and regional areas. A handset may have excellent LTE data in a city but depend on a different fallback layer in remote Queensland, Western Australia, or along long highways.
The national 3G shutdown changed the practical value of CSFB. Operators and handset vendors have had to prioritise VoLTE compatibility, emergency calling, and device provisioning rather than assuming that every LTE handset can fall back to 3G. The ability to reach Triple Zero (000), including during congestion or limited-service conditions, must be tested as part of migration and acceptance work.
Useful engineering checks include:
- Verify SGs association state, SCTP reachability, and M3UA or signalling gateway alarms.
- Confirm IMSI, TMSI, LAI, routing area, and VLR data remain consistent.
- Test mobile-originated and mobile-terminated calls across each operator interconnect.
- Measure fallback time in dense Sydney cells and weak-coverage regional locations.
- Validate SMS over SGs, voicemail access, call forwarding, and supplementary services.
- Test Triple Zero handling and approved emergency-call behaviour on supported devices.
A Practical Migration Path
CSFB is best treated as an interworking mechanism rather than a permanent substitute for LTE voice. It preserves service while operators build reliable VoLTE coverage, certify handsets, and retire older radio technologies. Its continued usefulness depends on the availability of a compatible circuit-switched access layer.
For Australian networks, the sensible technical focus is end-to-end observability: correlate MME, SGsAP, SCTP, MSC, radio, IMS, and ISUP events using consistent timestamps and subscriber identifiers. The practical takeaway is to validate every fallback and emergency scenario on the actual operator, device, and coverage combination before declaring LTE voice migration complete.
