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

Glossary term · Services

MO-SMS

Mobile Originated Short Message Service

Services →

MO-SMS is the mobile-originated process where a device initiates and sends a short text message to the network, enabling fundamental person-to-person messaging across 3GPP generations.

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

Description

Mobile Originated Short Message Service (MO-SMS) refers to the standardized procedure by which a User Equipment (UE) originates and transmits a Short Message (SM) to a Short Message Service Center (SM-SC) via the mobile network. It is a core service in 3GPP systems, defined across multiple releases since GSM. The process involves the UE composing a message and sending it through the network infrastructure, which routes it to the intended recipient via the SM-SC. The architecture includes the UE, the Radio Access Network (RAN), the Core Network (CN) elements like the MSC (in circuit-switched domains) or the AMF/MME (in packet-switched domains), and the SM-SC, which stores and forwards messages.

How it works: When a user sends an SMS, the UE encapsulates the message text and destination address in an SM protocol data unit. In traditional circuit-switched networks (2G/3G), the UE establishes a signaling connection and sends the MO-SMS via the MSC, which interacts with the SM-SC over MAP protocols. In packet-switched networks (4G/5G), MO-SMS can be transported over IP using the IP Short Message Gateway (IP-SM-GW) or via NAS signaling through the AMF in 5G. The UE sends the SMS in a NAS transport message to the AMF, which forwards it to the SM-SC via the SMSF (SMS Function) in the 5G Core. Key components include the UE's SMS application, the network's SMS routing functions, and the SM-SC, which ensures delivery.

MO-SMS's role has evolved from a basic text service to a critical component for authentication, notifications, and IoT communication. It remains integral despite the rise of OTT messaging, due to its reliability, universality, and use in backend services. The procedures ensure interoperability across devices and networks, with specifications covering encoding, signaling, and error handling.

Purpose & Motivation

MO-SMS was created to provide a standardized, reliable method for mobile devices to send short text messages, originating in GSM (2G) as part of the Short Message Service. It solved the problem of enabling simple, efficient person-to-person communication without requiring a voice call, leveraging unused signaling channels in cellular networks. Historically, before SMS, mobile communication was limited to voice, and the introduction of MO-SMS in 3GPP Release 5 (though conceptually earlier in GSM) allowed for asynchronous messaging, which became immensely popular.

The technology addresses the need for low-bandwidth, store-and-forward messaging that works across different networks and devices. Limitations of previous approaches included proprietary messaging systems or lack of interoperability; MO-SMS standardized the process, ensuring global compatibility. Its creation was motivated by the growing demand for text-based services, and it has since evolved to support enhanced features like concatenated messages, Unicode for international characters, and integration with IP networks in later releases. MO-SMS remains relevant for its robustness, wide coverage, and use in critical services like two-factor authentication and alerts, even as data-based messaging apps have emerged.

What changed in its specifications

The latest release-to-release comparison of specifications that define MO-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 6 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-14 specification text

TS 23.682 adds MSISDN-less MO-SMS via T4, where a subscribed UE sends SMS to the SCS/AS through SMS-SC and MTC-IWF with a defined procedure.

  • “MSISDN-less MO-SMS via T4 is subscription based. The subscription provides the information whether a UE is allowed to originate MSISDN-less MO-SMS.” TS 23.682 v14.8.0
  • “supports the delivering of SMS payload to SCS using Short Message Mobile Originated (MO-SMS) procedure via MTC-IWF.” TS 23.682 v14.8.0
Rel-15 specification text

Adds a new MSISDN-less MO-SMS procedure via T8, where the SMS-SC delivers the payload to the SCEF over T4 instead of to the MTC-IWF.

  • “Figure 5.17.3-1 shows the procedures for MSISDN-less MO-SMS via T8.” TS 23.682 v15.10.0
  • “SMS-SC uses the destination SME address (long/short code of the SCS/AS) to identify the corresponding SCEF based on a pre-configured mapping table.” TS 23.682 v15.10.0
Rel-16 1 CR

The procedure for MSISDN-less MO-SMS via T4 was corrected in TS 23.682 for Rel-16.

  • Correction on Procedure for MSISDN-less MO-SMS via T4 TS 23.682CR0431
Rel-17 1 CR

TS 24.501 in Rel-17 adds handling of MO-SMS over non-3GPP access, extending where mobile-originated SMS can be sent.

Rel-18 1 CR

Reference points of the IP-SM-GW for MO-SMS were added to TS 23.540 in Rel-18, specifying the interfaces used for mobile-originated SMS handling.

Defining Specifications

3GPP specifications that define or reference MO-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