Description
SM termination (Short Message termination) refers to the final delivery phase of a Short Message Service (SMS) message to an SMS-capable User Equipment (UE). It is the mobile-terminated (MT) counterpart to SM origination, and it encompasses all procedures required to route and deliver a short message from the network to the destination subscriber. The term is defined in 3GPP TS 23.040, which specifies the Technical realization of the Short Message Service, and is referenced in TS 23.204 for SMS over IP and in TS 23.824 for study work on SMS evolution. SM termination covers both traditional SMS delivered over signalling channels (e.g., via NAS signalling in EPS and 5GS, or via the control channel in GERAN/UTRAN) and SMS over IP, where the message is transported as an IMS message using SIP MESSAGE and the IP Short Message Gateway (IP-SM-GW).
Architecturally, SM termination involves several core network elements. In a 2G/3G network, the Short Message Service Centre (SMSC) receives or generates the message, queries the Home Location Register (HLR) for routing information, and forwards the message to the visited Mobile Switching Centre (MSC) or Serving GPRS Support Node (SGSN), which then delivers it to the UE over the appropriate radio interface. In an LTE/EPS network, the SMSC interacts with the Home Subscriber Server (HSS) and the Mobility Management Entity (MME), and the message is delivered to the UE via NAS signalling using the SGs interface or via the IP-SM-GW for SMS over IP. In 5G, the SMS Function (SMSF) handles the delivery of SMS over NAS to the UE, interacting with the Access and Mobility Management Function (AMF) and the Unified Data Management (UDM).
The process of SM termination begins when the SMSC receives a mobile-terminated short message. The SMSC sends a routing information request to the HLR/HSS to determine the location of the destination subscriber. The HLR/HSS responds with the address of the serving node (MSC/SGSN/MME/AMF/SMSF). The SMSC then forwards the message to that node. The serving node pages the UE if necessary, establishes a signalling connection, and delivers the short message using the appropriate protocol (e.g., CP-DATA in GERAN/UTRAN, NAS message in EPS/5GS). The UE acknowledges receipt, and the acknowledgement is relayed back to the SMSC. If delivery fails, the SMSC may retry or store the message for later delivery.
For SMS over IP, the UE registers with IMS and indicates SMS capabilities. The IP-SM-GW acts as an interworking function between the SMSC and the IMS domain. When a mobile-terminated message arrives, the IP-SM-GW encapsulates the SMS in a SIP MESSAGE request and sends it to the UE via the IMS core (P-CSCF, S-CSCF). The UE responds with a SIP 200 OK, which the IP-SM-GW translates into a delivery report for the SMSC. This allows SMS delivery over LTE/5G without relying on legacy circuit-switched fallback.
SM termination is critical because it ensures that subscribers can receive text messages regardless of the access technology they are using. It supports essential services such as two-factor authentication, service notifications, and person-to-person messaging. The evolution from Rel-8 through Rel-19 has maintained the fundamental definition while extending support to new access types (LTE, 5G) and to SMS over IP, ensuring backward compatibility and seamless interworking.
Purpose & Motivation
SM termination exists to provide a standardized mechanism for delivering short messages to mobile subscribers. Before its definition, SMS delivery was handled by proprietary or vendor-specific implementations, which led to interoperability problems between networks. The introduction of TS 23.040 established a common technical realization that allowed any SMSC to deliver messages to any UE, regardless of the manufacturer or network operator. This was essential for the global success of SMS as a ubiquitous messaging service.
As networks evolved from 2G to 3G, LTE, and 5G, the need arose to support SMS delivery over new radio technologies and packet-switched domains. The original circuit-switched SMS delivery mechanisms were not suitable for all-IP networks, so 3GPP introduced SMS over IP (also known as SMS over IMS) in Rel-7 and later refined it. SM termination procedures were extended to handle delivery via the IP-SM-GW, ensuring that subscribers could continue to receive SMS even when camping on LTE or 5G networks without circuit-switched fallback. This was particularly important for roaming and for ensuring service continuity during technology transitions.
Furthermore, SM termination addresses the need for reliable store-and-forward delivery. The SMSC can store messages when the UE is unreachable and attempt delivery later, which is a key differentiator from other messaging services. The standardized termination procedures ensure that delivery attempts, acknowledgements, and failure notifications are handled consistently across all network types, providing a predictable user experience. The ongoing maintenance of the definition across Releases 8 to 19 reflects the continued importance of SMS as a foundational service, even in the era of rich messaging and 5G.
What changed in its specifications
The latest release-to-release comparison of specifications that define SM termination. Each summary describes the whole specification, not only this term.
Rel-19 adds Multimedia Priority Service (MPS) for Messaging to TS 23.204. The MPS indication is stored in HSS/UDM, and Resource-Priority and transport priority are set in P-CSCF, IP-SM-GW and SMS-GMSC.
Full comparison in TS 23.204 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference SM termination, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.204 vj10 | SMS over generic IP access; Stage 2 | Rel-19 read |
| TS 23.824 va00 | IP-SM-GW enhancements for CPM-SMS Interworking | Rel-10 read |