Description
Mobile Terminated Short Message Service (MT-SMS) is the process by which a Short Message Service Center (SMSC) delivers a text message to a User Equipment (UE). The architecture involves several network entities: the originating entity (which could be another UE or an application), the SMSC, the Home Location Register (HLR) or Home Subscriber Server (HSS) for routing information, the Mobile Switching Center (MSC) for circuit-switched networks, or the Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) for packet-switched networks in later releases. The process begins when the SMSC receives a message for a subscriber. It queries the HLR/HSS to obtain the current routing information (e.g., the serving MSC or SGSN/MME address). The SMSC then forwards the message to this serving node via the MAP (Mobile Application Part) protocol in GSM/UMTS or Diameter in LTE/5G. The serving node pages the UE and, upon response, establishes the necessary signaling connection to deliver the SMS payload. In LTE and 5G, SMS can be delivered over both Circuit-Switched Fallback (CSFB) and the IP Multimedia Subsystem (IMS) via the SGs and SGd interfaces, respectively, or directly over the Non-Access Stratum (NAS) as SMS over NAS. The MT procedure is tightly integrated with mobility management, ensuring message delivery even when the user is roaming. It supports both point-to-point and cell broadcast modes. Reliability mechanisms include delivery reports and retry attempts upon failure. The service is defined across a vast range of 3GPP specifications, covering service requirements, architecture, protocols, and charging.
Purpose & Motivation
The purpose of MT-SMS is to provide a reliable, store-and-forward mechanism for delivering text messages to mobile subscribers. It solved the problem of asynchronous, non-real-time communication where the recipient might be temporarily unavailable (e.g., powered off or out of coverage). Before SMS, mobile communication was primarily voice-centric. SMS introduced a low-bandwidth, highly efficient data service that leveraged existing signaling channels, minimizing network impact. Its creation was motivated by the need for a simple, ubiquitous messaging service that could work across all GSM (and later 3GPP) networks globally. It addressed the limitation of requiring both parties to be simultaneously available, as required by voice calls. The MT component specifically ensures that the network can initiate delivery to a mobile device, which is essential for any service where the originator is not the UE itself, such as alerts, notifications, and application-to-person messages. Its standardization ensured interoperability between different network operators and equipment vendors, which was crucial for its global success.
Key Features
- Store-and-forward delivery mechanism
- Utilizes signaling channels (e.g., SDCCH in GSM, NAS in LTE/5G)
- Interworks with HLR/HSS for subscriber location and routing
- Supports delivery reports and failure notifications
- Can be delivered via CSFB, SMS over NAS, or IMS in later architectures
- Global interoperability through standardized MAP and Diameter procedures
Evolution Across Releases
Introduced as a core GSM service. Initial architecture relied on the GSM MAP protocol, with the SMSC communicating with the MSC/VLR and HLR for routing and delivery over the circuit-switched network's signaling channels.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 21.978 | 3GPP TS 21.978 |
| TS 22.031 | 3GPP TS 22.031 |
| TS 22.034 | 3GPP TS 22.034 |
| TS 22.101 | 3GPP TS 22.101 |
| TS 22.105 | 3GPP TS 22.105 |
| TS 22.944 | 3GPP TS 22.944 |
| TS 23.018 | 3GPP TS 23.018 |
| TS 23.031 | 3GPP TS 23.031 |
| TS 23.035 | 3GPP TS 23.035 |
| TS 23.050 | 3GPP TS 23.050 |
| TS 23.057 | 3GPP TS 23.057 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.078 | 3GPP TS 23.078 |
| TS 23.101 | 3GPP TS 23.101 |
| TS 23.107 | 3GPP TS 23.107 |
| TS 23.146 | 3GPP TS 23.146 |
| TS 23.207 | 3GPP TS 23.207 |
| TS 23.218 | 3GPP TS 23.218 |
| TS 23.278 | 3GPP TS 23.278 |
| TS 23.540 | 3GPP TS 23.540 |
| TS 23.725 | 3GPP TS 23.725 |
| TS 23.910 | 3GPP TS 23.910 |
| TS 23.923 | 3GPP TS 23.923 |
| TS 25.222 | 3GPP TS 25.222 |
| TS 26.130 | 3GPP TS 26.130 |
| TS 27.007 | 3GPP TS 27.007 |
| TS 27.060 | 3GPP TS 27.060 |
| TS 28.816 | 3GPP TS 28.816 |
| TS 29.061 | 3GPP TS 29.061 |
| TS 29.078 | 3GPP TS 29.078 |
| TS 29.122 | 3GPP TS 29.122 |
| TS 29.502 | 3GPP TS 29.502 |
| TS 29.542 | 3GPP TS 29.542 |
| TS 32.102 | 3GPP TR 32.102 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.270 | 3GPP TR 32.270 |
| TS 32.271 | 3GPP TR 32.271 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.276 | 3GPP TR 32.276 |
| TS 32.293 | 3GPP TR 32.293 |
| TS 32.849 | 3GPP TR 32.849 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 38.201 | 3GPP TR 38.201 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.340 | 3GPP TR 38.340 |
| TS 38.410 | 3GPP TR 38.410 |
| TS 38.413 | 3GPP TR 38.413 |
| TS 43.802 | 3GPP TR 43.802 |