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

Glossary term · Services

SMS

Short Message Service

Services →

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.

Introduced
Phase 1
Where
Services › IMS
Specifications
75 specs
Also in
Core Network, Management, Radio Access Network
SMS Description Purpose What changed Family Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define 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 22.101Rel-16 → Rel-17

Rel-17 added support for Multi-USIM devices, emergency call handling, and definitions for MUSIM UEs.

Full comparison in TS 22.101 →

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
  • SMS extended by EMS
    “Enhanced Messaging is based on standard mechanism in GSM SMS messaging.” TS 23.040
  • SMS extended by MSGin5G
    “If the UE supports a legacy 3GPP message service (e.g. SMS, NIDD, or CB) and does not support the MSGin5G Service (i.e. UE has no MSGin5G Client), the message will be translated to the appropriate message delivery mechanism by the Legacy 3GPP Message Gateway.” TS 23.554
  • SMS extended by SMS over IP
    “The clause describes the procedures for the support of transport-level interworking between Short Message service and encapsulated Short Message via IP service” TS 23.204
  • SMS coexists with MMS
    “The present document serves as a foundation for the development of MMS. It describes a new service which has no direct equivalent in the previous ETSI/GSM world or in the fixed network world.” TS 23.140
  • SMS used together with Legacy 3GPP Message Gateway
    “For SMS delivery mechanism, the Legacy 3GPP Message Gateway sends SMS to the Legacy 3GPP UE through the SMSC according to the procedure in TS 23.204 [13] or the procedure in clause 4.13.3 of TS 23.502 [7].” TS 23.554

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 15 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-7 1 CR

TS 23.204 first specifies the capabilities, architecture and interfaces for supporting SMS over a generic IP-CAN using IMS, including registration and MO/MT transfer.

  • “The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities” TS 23.204 v7.6.0
  • “a registration and de-registration mechanism shall be supported where UEs are required to explicitly indicate their ability to send and receive SMS over IP messages.” TS 23.204 v7.6.0
  • Addition of SMS over IP functionality TS 23.078CR0813
Rel-8 1 CR

Rel-8 adds SMS over SGs for EPS (no CS fallback, NAS signalling via MME and MSC Server) and extends SMS-over-IP interworking with SIMPLE IM, including status reports and E-UTRAN procedures.

  • “SMS support is based on the connectionless SGs reference point between the MME and the MSC Server and use of NAS signalling between the UE and the MME” TS 23.272 v8.12.0
  • “If an SMS user requests an SMS status report that the message was delivered to the recipient, then an SMS status report shall be generated” TS 23.204 v8.5.0
  • Update of TS 23.204 for SMS over IP procedures for E-UTRAN TS 23.204CR0074
Rel-9 1 CR

Rel-9 specifies SMS over SGs and SMS over S102 for EPS, with an SMS-only attach/TAU indication, MME and UE support requirements, and NAS handling of SMS.

  • “The support of SMS over SGs is mandatory for UE and MME and MSC supporting CS fallback” TS 23.272 v9.15.0
  • “If the UE needs SMS service but not CSFB, the UE shall include an "SMS-only" indication in the combined EPS/IMSI Attach Request.” TS 23.272 v9.15.0
  • Correction for SMS via SGs charging TS 23.018CR0170
Rel-10 specification text

SMS handling changed in Rel-10: SMS over SGs gained MSC/VLR selection and paging by IMSI for SMS, MO SMS handling while T3346 runs, and CPM interworking with SMS via IP-SM-GW and ISF.

  • “An MME that supports SMS over SGs may use the same procedure as for CS Fallback.” TS 23.272 v10.15.0
  • “If the paging message includes a UE Paging Identity set to the UE's IMSI, the paging procedure is performed according to subclause 5.6.2.2.2.” TS 24.301 v10.15.0
  • “The service-level interworking shall support interworking between OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17] and Short Message Service” TS 23.204 v10.2.0
Rel-11 specification text

Rel-11 adds the 'SMS in MME' option: an MME can register with the HSS as an MSC for MT SMS and provide SMS without SGs or CS fallback, and IP-SM-GW can appear to the SMS-GMSC as an MME.

  • “this specification includes an SMS in MME architecture option for SMS services only. This functionality does not trigger any CS Fallback and does not require SGs.” TS 23.272 v11.10.0
  • “the HSS registers the MME as an MSC for MT SMS” TS 23.272 v11.10.0
  • “The E/Gd/SGd interface allows the IP-SM-GW to connect to the SMS‑GMSC, appearing to the SMS‑GMSC as an MSC, SGSN or MME.” TS 23.204 v11.5.0
Rel-12 1 CR

Rel-12 adds MSISDN-less SMS operation between IMS UEs via the IP-SM-GW, a Diameter Gdd interface for SMS with the SGSN, and SMS-only handling updates in NAS.

  • “It shall provide for the transport of Mobile Originating Short Message Service from IMS UE that supports MSISDN-less SMS operation to other IMS UE.” TS 23.204 v12.5.0
  • Addition of Diameter Gdd interface for SMS with SGSN TS 23.060CR1810
  • “a UE operating in CS/PS mode 2 and a UE operating in CS/PS mode 1 with "IMS voice available" shall not attempt to use CS fallback” TS 24.301 v12.13.0
Rel-13 specification text

Rel-13 extends SMS support: NB-IoT-only UEs can get SMS with a plain EPS attach or TAU, SMS can be carried over Control Plane CIoT EPS optimisation, and MT SMS is handled in extended idle-mode DRX.

  • “A UE that only supports NB-IoT (see TS 23.401 [2]) may request SMS service and use the EPS Attach, TA Update and EPS Detach procedures.” TS 23.272 v13.6.0
  • “to enable SMS transfer the Service Request procedures defined in TS 23.401 [2] are not used for MO SMS” TS 23.272 v13.6.0
  • “the MME shall indicate "SMS only" in the Additional update result IE” TS 24.301 v13.12.0
Rel-14 2 CRs

SMS handling changed: MO SMS over T4 added, SMS over SGs enabled for NB-IoT only UEs, and NAS RRC establishment cause and "SMS only" behaviour updated.

  • MO SMS over T4 TS 23.682CR0220
  • Enabling SMS over SGs for NB-IoT only UEs TS 24.301CR2709
  • “In NB-S1 Mode, if a CONTROL PLANE SERVICE REQUEST is to transfer MO SMS” TS 24.301 v14.10.0
Rel-15 1 CR

Rel-15 extends SMS to the 5G System: SMS over NAS with SMSF, MT SMS domain selection, SMS subscription handling and UE reachability for SMS delivery were specified or revised.

  • “Clause 4.13 defines the additional procedures or additions to the existing procedures to support specific services such as SMS over NAS.” TS 23.502 v15.17.0
  • “SMSF: the SMS Function as defined in TS 23.501 [23].” TS 23.204 v15.0.0
  • Removal of one step SMS procedure TS 23.502CR0326
Rel-16 1 CR

SMS handling was extended in Rel-16: MSISDN-less MO SMS, SMS deregistration over NAS, UE reachability for SMS notifications, and SMS delivery re-attempts across domains by the IP-SM-GW.

  • Introduction of the MSISDN-less MO SMS Service TS 23.501CR0826
  • “AMF invokes Nsmsf_SMService_Deactivate service operation to trigger the release of UE Context for SMS on SMSF” TS 23.502 v16.19.0
  • “The IP‑SM‑GW takes responsibility to re-attempt the delivery of the message in another domain” TS 23.204 v16.0.0
Rel-17 1 CR

Rel-17 adds service-based (SBI) SMS support in 5GS: TS 23.540 is referenced for SMS delivery procedures, and SMS registration, reachability events and alert handling are updated.

  • “If SMS delivery is allowed, the procedure defined in TS 23.040 [7] or TS 23.540 [84] applies.” TS 23.502 v17.15.0
  • “This event is detected when the UDM receives UE memory available for SMS indication from the SMSF as part of Alert procedure” TS 23.502 v17.15.0
  • SMS with HTTP/2 SBI in 5GS TS 23.040CR0161
Rel-18 2 CRs

Rel-18 changes MT SMS handling: the AMF now tells the SMSF when a UE using power saving is unreachable, stores the reachability request and pages the UE once reachable, with a new failure-report path.

  • “the AMF further stores the information received in the Namf_MT_EnableUEReachability request and pages the UE when UE is considered reachable.” TS 23.502 v18.14.0
  • MT SMS handling for UE in power saving TS 23.502CR4481
  • Updates to introduce SMS service in NEF southbound API TS 29.591CR0098
Rel-19 1 CR

Rel-19 adds MPS priority treatment for SMS over NAS and SMS over IP, including the MPS for Messaging indication, priority DRMP/DSCP and paging priority for MT SMS.

  • “Support MPS priority treatment (e.g. determining the DRMP value in the messages related to SMS delivery, Paging Priority setting when paging is triggered for UE in CM-IDLE mode)” TS 23.272 v19.1.0
  • “the paging shall be initiated with priority.” TS 24.301 v19.8.0
  • MPS support for MO and MT SMS over NAS procedure TS 23.272CR0975
Rel-20 1 CR

SMS gains support for mobile-originated messages to an Emergency Response Centre, with UE, MME/MSC and SMSF detection via the RP-DA field and delivery to the SMS-IWMSC/SC with MSISDN and location.

  • “the UE provides the 3GPP defined "SMS to Emergency Response Centre" number with associated service type in the RP-DA field of the RP-DATA header” TS 23.272 v20.0.0
  • “When the SMSF detects an MO-SMS to Emergency Response Center based on the RP-DA field of the RP-DATA header” TS 23.502 v20.3.0
  • Adding support for SMS to Emergency Response Centre TS 23.502CR5685

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