SMS

Short Message Service

Services →
Introduced in R99 Also in: Core Network, Radio Access Network, Management

SMS is a globally standardized mobile network service for exchanging short alphanumeric messages between subscribers or from applications, widely used for person-to-person communication, notifications, and alerts.

Category
Services
Introduced
R99
Where
Services › Codecs
Also touches
3 segments
Specifications
75 specs
SMS Description Purpose Related Classification Detected Changes Specifications

Description

Short Message Service (SMS) is a core telecommunication service defined by 3GPP that enables the transmission of short text messages, typically up to 160 characters per message segment, between mobile devices or between applications and devices. It operates as a store-and-forward service, meaning messages are not sent directly from sender to recipient but are routed through a central network element called the Short Message Service Centre (SMSC). The SMSC stores the message and forwards it to the recipient's device when it is available, ensuring delivery even if the recipient is temporarily unreachable. SMS uses signaling channels in the mobile network, specifically the SDCCH (Standalone Dedicated Control Channel) in GSM or similar control channels in later technologies, allowing it to work independently of voice or data sessions, which makes it highly reliable and efficient.

Architecturally, SMS involves several key network components. The Mobile Station (MS) or User Equipment (UE) is the endpoint that originates or receives messages. The Base Station Subsystem (BSS) or Radio Access Network (RAN) handles the radio interface transmission. In the core network, the Mobile Switching Centre (MSC) or Serving GPRS Support Node (SGSN) in 2G/3G, or the Mobility Management Entity (MME) in 4G/5G, manages mobility and session control for SMS delivery. The SMSC is the central hub that stores, processes, and routes messages, interacting with the HLR (Home Location Register) to obtain routing information and subscriber status. For SMS over IP in later releases, elements like the IP-SM-GW (IP Short Message Gateway) are introduced to interface with IMS. The service supports various message types, including mobile-originated (MO), mobile-terminated (MT), and cell broadcast messages for area-wide alerts.

SMS works through a series of signaling procedures. For a mobile-originated SMS, the UE sends the message to the MSC/MME via the radio access network. The MSC/MME forwards it to the SMSC using MAP (Mobile Application Part) signaling in legacy networks or Diameter/SIP in IP-based systems. The SMSC queries the HLR to find the recipient's current serving node and then delivers the message to that node, which pushes it to the UE. Delivery reports are sent back to confirm success. SMS also supports concatenation for longer messages (split into multiple segments), compression, and encoding schemes like GSM 7-bit alphabet or UCS-2 for Unicode. Its integration into the network's control plane ensures low latency and high availability, making it a critical service for two-factor authentication, emergency alerts, and machine-to-machine (M2M) communication.

Purpose & Motivation

SMS was created to provide a simple, efficient text-based communication method for mobile users, leveraging unused capacity in the control signaling channels of GSM networks. Introduced in early GSM standards (pre-3GPP, later formalized in R99), it addressed the need for a low-cost, asynchronous messaging service that could operate alongside voice calls without requiring dedicated data connections. Initially, it enabled person-to-person texting, which quickly became popular due to its convenience and affordability compared to voice calls.

Over time, SMS evolved to solve broader communication challenges. It provided a reliable channel for service notifications, such as voicemail alerts and roaming updates, and later for application-to-person (A2P) services like banking alerts and marketing messages. The store-and-forward mechanism solved the problem of recipient unavailability, ensuring message delivery even when devices were off. As networks advanced to 3G, 4G, and 5G, SMS remained essential due to its universality and interoperability across different operators and technologies, supporting migration to all-IP cores through enhancements like SMS over IMS. Its robustness and global reach have made it a foundational service for critical communications, including emergency alerts and two-factor authentication, despite the rise of OTT messaging apps.

Classification

Part ofIMS
Related approachesMAP

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (31 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 9 changes

In Release 15, the SMS function was enhanced with the introduction of offline charging for the IP-SM-GW and the addition of SMS charging information to the CHF (Charging Function) CDR. Furthermore, the release enabled MT SMS domain selection by the IP-SM-GW and introduced 5GS for SMS charging via the Ro and Rf interfaces.

  • Addition of SMS Charging to CHF CDR TS 32.298CR0680
  • Addition of SMS info to CHF CDR TS 32.298CR0682
  • Introduction of 5GS for SMS charging via Ro Rf TS 32.298CR0684
  • Introduction of offline charging for IP-SM-GW TS 32.298CR0685
  • MT SMS domain selection by IP-SM-GW TS 23.204CR0109
  • Incorrect references to HSS triggered events in the SMS, MMS clauses TS 33.107CR0292

+ 3 more changes

Rel-16 6 changes

In Release 16, the updates to the SMS function primarily involved charging data record (CHD) corrections and service enhancements for specific scenarios. This included aligning procedures for UE reachability notifications from the IP-SM-GW and introducing an identifier translation mechanism to support MSISDN-less mobile-originated SMS service. The corrections focused on ensuring accurate data capture in CHF CDRs for elements like the message class, node address, message reference, and originator/recipient information.

  • Id translation for MSISDN-less MO SMS service TS 29.505CR0112
  • Alignment to 23.040 on UE reachability notification from IP-SM-GW TS 23.204CR0119
  • Correction of SMS message class in CHF CDR TS 32.298CR0839
  • Correction of SMS node address in CHF CDR TS 32.298CR0836
  • Correction of mandatory SMS message reference in CHF CDR TS 32.298CR0838
  • Correction of SMS originator and recipient info in CHF CDR TS 32.298CR0841
Rel-17 3 changes

In Release 17, the SMS function was enhanced by introducing the NEF and MNPF into the Service-Based Interface (SBI) architecture for SMS and by enabling an MSISDN-less MO SMS service. Additionally, protocol selection for MT SMS delivery via the IP-SM-GW or SMS Router was specified. These updates expanded the architectural flexibility and subscriber service options for messaging within 5G systems.

  • Add NEF and MNPF in SBI-based SMS system architecture TS 23.540CR0002
  • MSISDN-less MO SMS Service TS 29.829CR0001
  • Protocol selection for MT SMS with IP-SM-GW/SMS Router in TR29.829 TS 29.829CR0002
Rel-18 4 changes

In Release 18, the SMS function was updated to enhance its Service-Based Interface (SBI) architecture. Key changes included ensuring compatibility for the UDM when it does not support SMS over SBI, refining the procedures for Mobile-Originated SMS fallback to legacy methods, and defining the IP-SM-GW reference points specifically for MO-SMS. Furthermore, the release introduced mechanisms for the SBI-based discovery of SMS-related network entities.

  • Compatibility of UDM not supporting SMS SBI TS 23.540CR0013
  • Modify of the description of MO SMS fallback to legacy way TS 23.540CR0016
  • IP-SM-GW Reference Points for MO-SMS TS 23.540CR0019
  • SBI-based discovery of SMS-related entities TS 23.540CR0018
Rel-19 9 changes

In Release 19, key enhancements for SMS included the support and clarification of MPS (Mission Critical Services) priority for SMS delivered over IP and over the NAS Service-Based Interface (SBI). Furthermore, the release introduced specific charging information to support the store-and-forward operation of the SMS service when used over satellite networks.

  • Support of MPS priority for SMS over IP TS 23.204CR0120
  • MPS priority for Messaging SMS over NAS SBI TS 23.540CR0020
  • Add charging information for store and forward satellite operation of SMS service TS 32.251CR0521
  • Rel-19 CR 32.298 Add charging information for store and forward satellite operation of SMS service TS 32.298CR1039
  • MPS transport priority clarification for SMS over IP TS 23.204CR0121
  • MPS priority for Messaging SMS over NAS SBI TS 23.540CR0022

+ 3 more changes

Explore further

Broader topics and technologies where SMS plays a role.

Defining Specifications

3GPP specifications that define or reference 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 22.022 vj00 ME Personalisation Features for GSM/3G Rel-19
TS 22.101 vk00 Service Principles for PLMNs Rel-20
TS 22.105 vj00 Telecommunication Services Framework Rel-19
TS 22.112 v1800 USAT Gateway System Specification Rel-8
TS 22.121 v1400 Virtual Home Environment Requirements Rel-5
TS 22.140 vj00 MMS Stage 1 Requirements Rel-19
TS 22.242 vj00 DRM Service Requirements Rel-19
TS 22.401 v1800 Videotelephony Service Requirements for NGN Rel-8
TS 22.811 v1700 Network Selection Mechanisms Overview Rel-7
TR 22.940 vj00 IMS Messaging Requirements Analysis Rel-19
TR 22.942 vj00 SMS Value-Added Services Requirements Rel-19
TR 22.945 v1300 Fax Services Guidance for GSM/UMTS Rel-4
TR 22.949 vj00 Privacy Requirements Study for 3GPP Services Rel-19
TS 23.039 v1400 SMSC to SME Interface Protocols Rel-5
TS 23.048 v1400 Secured Packets for UICC Remote Management Rel-5
TS 23.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19
TS 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TS 23.066 vj00 Mobile Number Portability Technical Realization Rel-19
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19
TS 23.107 vj00 UMTS QoS Framework Rel-19
TS 23.110 vj00 Access Stratum Services Specification Rel-19
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19
TS 23.171 v1300 LCS Stage 2 Specification for UMTS Rel-4
TS 23.204 vj10 SMS over generic IP access; Stage 2 Rel-19
TS 23.207 vj00 End-to-End QoS Framework for GPRS Rel-19
TS 23.271 vj00 LCS Stage 2 Specification Rel-19
TS 23.540 vj20 5G Service Based SMS Stage 2 Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 23.722 vf10 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-15
TS 23.811 v1800 Service Level Interworking SMS-IM Rel-8
TS 23.824 va00 IP-SM-GW enhancements for CPM-SMS Interworking Rel-10
TR 23.976 vj00 Push Service Requirements Analysis Rel-19
TR 23.979 vj00 PoC over 3GPP Systems Architectural Requirements Rel-19
TR 23.981 vj00 IPv4 IMS Interworking and Migration Study Rel-19
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TR 26.862 vh00 Immersive Teleconferencing & Telepresence for Remote Terminals Rel-17
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19
TS 29.118 vj10 MME-VLR Interface for CS Fallback & SMS Rel-19
TS 29.198 v1900 OSA API Overview Specification Rel-9
TS 29.199 v1900 Multimedia Messaging Web Services Rel-9
TS 29.505 vj50 UDR Service for Subscription Data Usage Rel-19
TR 29.829 vh10 SMS Service-Based Interfaces for 5G Core Rel-17
TS 31.112 v1800 USAT Interpreter System Architecture Rel-8
TS 31.113 v1800 USAT Interpreter Byte Code Specification Rel-8
TS 31.114 v1800 USAT Interpreter Transmission Protocol Rel-8
TS 31.115 vj00 Secured Packet Structure for UICC Applications Rel-19
TS 31.121 vi50 UICC-terminal interface test specification Rel-18
TS 31.131 vj00 C Language Binding for (U)SIM API Rel-19
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19
TS 32.240 vj40 Charging Management Architecture & Principles Rel-19
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19
TS 32.251 vj00 PS Domain Charging Management Rel-19
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19
TS 32.297 vj00 Charging Data Record File Transfer Rel-19
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19
TS 32.622 vb10 Generic Network Resources IRP NRM Rel-11
TS 32.632 vb00 Core Network Resources IRP: Network Resource Model Rel-11
TS 32.732 vb00 IMS Network Resource Model IRP: Information Service Rel-11
TS 32.808 v1800 Common User Profile Storage Framework Rel-8
TS 32.819 v800 Element Management Layer OS Functions Rel-8
TS 32.863 vd00 PM Measurement Metadata Definition Rel-13
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 33.108 vj00 LI Handover Interface Specification Rel-19
TS 34.131 vj00 SIM API C Language Test Specification Rel-19
TR 38.882 vi00 Technical Report on UE Location Service Rel-18
TS 41.033 ve00 GSM Lawful Interception Interface Requirements Rel-14
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19
TS 45.820 vd10 CIoT for Internet of Things Rel-13