MO-SMS

Mobile Originated Short Message Service

Services →
Introduced in Rel-5

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.

Category
Services
Introduced
Rel-5
Where
Security
Specifications
3 specs
MO-SMS Description Purpose Related Classification 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.

Classification

Part ofSMS
Related approachesMT-SMS

Evolution Across Releases

Rel-5 Initial

Introduced MO-SMS for UMTS with enhanced procedures in 3GPP specs, supporting SMS over packet-switched networks and integration with IP-based services. Defined architecture involving UE, core network, and SM-SC for reliable message origination.

Explore further

Broader topics and technologies where MO-SMS plays a role.

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 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.048 v1400 Secured Packets for UICC Remote Management Rel-5
TS 31.115 vj00 Secured Packet Structure for UICC Applications Rel-19