Description
Mobile Terminated Short Message Service (MT-SMS) refers to the reception of a Short Message by a Mobile Station (MS) or User Equipment (UE). It is one half of the bidirectional SMS service, the other being Mobile Originated SMS (MO-SMS). MT-SMS is a store-and-forward service where a message, typically text, is delivered from a Short Message Entity (SME) – such as another mobile user, a voicemail system, or an application server – to a recipient's mobile device via the cellular network's core infrastructure.
The architecture for MT-SMS involves several network functions. In a GSM/UMTS network, the central entity is the Short Message Service Center (SM-SC), which stores and forwards messages. For an MT-SMS, the SM-SC receives the message from the originating SME and queries the Home Location Register (HLR) or Home Subscriber Server (HSS) to determine the current serving Mobile Switching Center (MSC) or Mobility Management Entity (MME) for the target subscriber. The SM-SC then forwards the message to this serving MSC (for CS SMS over GSM/UMTS) or MSC/IWF/MME (for SMS over IP in later generations). The serving MSC, in turn, pages the mobile device if it is idle and delivers the message over the signaling channels (e.g., using the Mobile Application Part (MAP) protocol for transport and the connection management and mobility management layers for delivery).
In LTE and 5G networks, which are packet-switched only, SMS delivery evolved. For MT-SMS in LTE, it is delivered over the IP-based SGs interface between the MME and the MSC, which is part of the Circuit-Switched Fallback (CSFB) mechanism for SMS, or via the IP-SM-GW (IP Short Message Gateway) using the Diameter-based SGd interface for SMS over IP (SMSIP). In 5G, MT-SMS is natively supported as an IP-based service. The 5G core network (5GC) uses the Short Message Service Function (SMSF) as the termination point for the SM-SC. The SMSF interacts with the AMF (Access and Mobility Management Function) to deliver the message to the UE over the NAS (Non-Access Stratum) signaling connection, utilizing the Nsmsf service-based interface. The message is carried transparently over the N1 reference point between the UE and the AMF.
The technical procedure for MT-SMS involves several layers. At the application layer, the message is formatted according to TP (Transfer Protocol) parameters defined in 3GPP TS 23.040. The network layers handle routing, security, and reliable delivery. Key protocols include MAP in legacy cores, Diameter for SMSIP, and HTTP/2 for service-based interfaces in 5GC. The delivery is a signaling procedure, not requiring a dedicated user-plane bearer, which allows SMS to be delivered even when the device is in idle mode or not engaged in a voice or data session. This makes it a highly reliable and ubiquitous service. MT-SMS remains a critical service for person-to-person communication, two-factor authentication, service notifications, and machine-to-person alerts, despite the rise of OTT messaging applications.
Purpose & Motivation
MT-SMS was created as part of the original GSM Short Message Service to enable a reliable, network-based text messaging system. Its purpose was to provide a simple, store-and-forward communication channel that was independent of voice calls and could reach a subscriber even when their phone was switched off or out of coverage temporarily (messages would be stored and delivered upon availability). It solved the problem of asynchronous, non-urgent text-based communication in early digital mobile networks.
The historical motivation stems from the GSM standard's development in the late 1980s and early 1990s. SMS was initially a minor add-on, using spare capacity on the signaling channels used for call setup and location updating. MT-SMS, specifically, allowed the network to initiate delivery of information to the subscriber, enabling services like voicemail notifications, news alerts, and later, interactive services. It addressed the limitation of paging systems and numeric displays by providing a bidirectional alphanumeric messaging capability.
Over successive 3GPP releases, the purpose of MT-SMS expanded and its implementation evolved to maintain relevance. With the transition to all-IP networks in LTE and 5G, where traditional circuit-switched domains were removed, a major problem arose: how to continue delivering this ubiquitous service. This motivated the development of SMS over IP (SMSIP) and later the native SMS support in 5GC via the SMSF. MT-SMS today solves the problem of universal, interoperable, and secure message delivery for critical services (like banking OTPs, emergency alerts, and carrier notifications) across diverse network generations and architectures, ensuring backward compatibility and service continuity as networks evolve.
Key Features
- Store-and-forward delivery ensures message receipt even if recipient is temporarily unavailable
- Utilizes network signaling channels (not user plane bearers) for efficient, widespread delivery
- Supported across all cellular generations (GSM, UMTS, LTE, 5G) with evolving transport mechanisms
- Enables critical services like two-factor authentication, service notifications, and emergency alerts
- Relies on core network elements like SM-SC, HLR/HSS, MSC, MME, SMSF for routing and delivery
- Defined by comprehensive 3GPP specifications covering service requirements, protocols, and interworking
Evolution Across Releases
Continued enhancements for 5G SMS, including support for extended message length, improved interworking with legacy networks, and alignment with new 5G core network features like network slicing and edge computing.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.048 | 3GPP TS 23.048 |
| TS 31.115 | 3GPP TR 31.115 |