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

Glossary term · Services

MT-SMS

Mobile Terminated Short Message Service

Services →

MT-SMS is the network-to-device direction of the Short Message Service where the core network receives a message from an external source and delivers it to the target mobile device.

Introduced
Phase 1
Where
Services
Specifications
3 specs
MT-SMS Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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

Full comparison in TR 21.905 →
TS 23.048Rel-4 → Rel-5

Rel-5 added applet management commands, minimum security level specification, and a security layer relation to Open Platform architecture.

Full comparison in TS 23.048 →

Technology family

Messaging services · Services

  1. Phase 1 CBC, MO-SMS, MT-SMS, SMS, SMS-CB
  2. Phase 2 CBE, SMS-GMSC, SMS-IWMSC
  3. R99 EMS, MMS, MMS User Agent, MMSE
  4. Rel-4 MMS Relay/Server
  5. Rel-6 IP-SM-GW, MSCF
  6. Rel-7 SMS over IP, SMS Router
  7. Rel-8 SMS over SGs
  8. Rel-15 CBCF, PWS-IWF, SMS over NAS, SMSF
  9. Rel-17 Legacy 3GPP Message Gateway, MSGin5G, MSGin5G Client, MSGin5G Server, Non-3GPP Message Gateway
  10. Rel-18 Broadcast Message Gateway

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 9 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.

Phase 1 introduced

Introduced in Phase 1 (release dating of the term; no individual change cited).

Rel-8 specification text

A note in the circuit-switched fallback procedure specifies that the MME cannot tell whether an MT-SMS will trigger user plane traffic or an MO SMS, so normal eNodeB procedures should release S1 resources.

  • “the MME does not know whether the MT-SMS might cause the initiation of user plane traffic or an MO SMS” TS 23.272 v8.12.0
Rel-11 specification text

For 'SMS in MME', the MME can re-register with the HSS and supply its identity and address for MT-SMS delivery and routing, and SMS subscription data includes MT-SMS barring status.

  • “to provide the HSS with the MME identity to be used for MT-SMS delivery” TS 23.272 v11.10.0
  • “The MME sends a Location Update Request (SMS in MME feature flag, MME address for MT-SMS routing” TS 23.272 v11.10.0
  • “The SMS subscription data include for example the barring status of MO-SMS and MT-SMS and the MSISDN.” TS 23.272 v11.10.0
Rel-13 specification text

MT-SMS handling gained new behaviour: paging handling for extended DRX UEs and a failure case for triggering when MT-SMS is barred.

Rel-15 1 CR

MT-SMS over NAS procedures are specified for the 5G system, including access type selection, retransmission on the other access type upon failure, failure reports to SMS-GMSC, and URRP-AMF/MWD handling.

  • “the AMF determines the Access Type to transfer the MT-SMS based on operator local policy.” TS 23.502 v15.17.0
  • “if the MT-SMS delivery over one Access Type has failed, the AMF, based on operator local policy, may re-attempt” TS 23.502 v15.17.0
  • MT-SMS over NAS re-transmission upon delivery failure on one Access Type TS 23.502CR0480
Rel-16 specification text

TS 23.632 text for the first time specifies MT-SMS routing information retrieval, delivery failure handling and target nodes (SMSF registered at UDM) for 5GS, including retrieval over Nudr.

  • “in 5GS MT-SMS target nodes are the 3GPP-SMSF and the Non3GPP-SMSF registered at the UDM” TS 23.632 v16.6.0
  • “the UDM provides a negative response (Absent Subscriber SM) to the HSS” TS 23.632 v16.6.0
  • “the SMS-GMSC retrieves routing information from the HSS for MT-SMS delivery when the HSS uses the Nudr SBI” TS 23.632 v16.6.0
Rel-17 specification text

UDM now returns Absent Subscriber SM only when the UE is unreachable for MT-SMS for any access type, and MWD list handling also references TS 23.540.

  • “If the UE is not reachable for MT-SMS in 5GS for any access type” TS 23.632 v17.3.0
  • “store the SC address in the MWD list as defined in TS 23.040 [7] or TS 23.540 [84]” TS 23.502 v17.15.0
Rel-18 1 CR

MT-SMS delivery failure handling was extended so the SMSF reports failure to the SMS-GMSC also when the UE applies power saving enhancement and the AMF cannot deliver the message.

  • “including the cases that UE applies power saving enhancement as described in step 4 of clause 4.13.3.6” TS 23.502 v18.14.0
  • Clarification on MT-SMS Delivery Failure TS 23.632CR0041
Rel-19 specification text

AMF and MME/SMSF now apply MPS for Messaging priority handling to MT-SMS, including paging priority and RAN Paging Priority IE in Downlink NAS Transport for RRC-INACTIVE UEs.

  • “the AMF shall include the service priority value (RAN Paging Priority IE as in TS 38.413 [10]) appropriate for MPS for Messaging” TS 23.502 v19.9.0
  • “upon receipt of an MT-SMS from the SMS-GMSC marked with a DRMP associated with MPS for Messaging” TS 23.272 v19.1.0

Defining Specifications

3GPP specifications that define or reference MT-SMS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.048 v590 Secured Packets Structure for SMS and UICC Management Rel-5 read
TS 31.115 vj00 Secured Packet Structure for UICC Applications Rel-19 read