Description
The SMS Function (SMSF) is a 5G core network function introduced in 3GPP Release 15 as part of the Service-Based Architecture (SBA). It is defined in TS 23.501 (System architecture for the 5G System) and further specified in TS 23.540 (Technical realization of SMS in 5G). The SMSF is responsible for the delivery of Short Message Service (SMS) messages over the Non-Access Stratum (NAS) between the UE and the 5G core network. It acts as an intermediary between the Short Message Service Centre (SMSC) and the Access and Mobility Management Function (AMF), enabling SMS delivery without requiring the UE to support IMS or circuit-switched fallback.
Architecturally, the SMSF communicates with the AMF over the N20 interface (or service-based interface Nsmsf). The AMF is responsible for relaying SMS messages between the UE and the SMSF using NAS signalling. When a UE needs to send an SMS (mobile-originated), it encapsulates the SMS message in a NAS message and sends it to the AMF. The AMF forwards the message to the SMSF, which then delivers it to the SMSC using the appropriate interface (e.g., MAP or Diameter). For mobile-terminated SMS, the SMSC sends the message to the SMSF, which forwards it to the AMF, and the AMF delivers it to the UE via NAS signalling. The SMSF also interacts with the Unified Data Management (UDM) to retrieve subscriber data related to SMS services, such as whether the subscriber is authorized for SMS over NAS.
The SMSF supports both SMS over NAS and SMS over IP. For SMS over NAS, the UE must indicate its capability to support SMS over NAS during registration. The AMF selects an SMSF based on the subscriber's profile and network configuration. The SMSF then manages the SMS delivery, including store-and-forward functionality if the UE is temporarily unreachable. The SMSF can also generate delivery reports and handle error cases, such as when the UE is not reachable or when the message is too large.
The SMSF is a key enabler for SMS in 5G, particularly for devices that do not support IMS or for networks that do not deploy IMS. It ensures that SMS remains available as a basic service in 5G, which is critical for many use cases, including IoT devices, legacy applications, and two-factor authentication. The SMSF also supports roaming, allowing subscribers to send and receive SMS while visiting foreign 5G networks. The architecture ensures that SMS delivery is efficient and does not require the overhead of establishing an IMS session for each message.
Since its introduction in Rel-15, the SMSF has been maintained through Rel-20 with no changes to its fundamental definition. However, its specifications have been refined and extended to cover new deployment scenarios, such as SMS over NAS in non-standalone (NSA) and standalone (SA) 5G networks, and interworking with 4G networks. The SMSF is a critical component of the 5G core network, ensuring that SMS continues to be a reliable and ubiquitous service in the 5G era.
Purpose & Motivation
The SMSF was created to address the need for SMS support in 5G networks without relying on legacy circuit-switched infrastructure or IMS. In earlier generations, SMS delivery was tightly coupled with the circuit-switched domain (2G/3G) or required IMS deployment (LTE with SMS over IP). As 5G networks were designed as all-IP, service-based architectures, there was a need for a dedicated network function to handle SMS delivery natively over NAS. The SMSF fills this gap by providing a standardized, efficient mechanism for SMS transport in 5G.
The SMSF solves several problems. First, it enables SMS for UEs that do not support IMS, such as low-cost IoT devices or legacy devices. Second, it avoids the complexity and overhead of establishing IMS sessions for SMS delivery, which is particularly important for machine-type communications where efficiency is critical. Third, it provides a clear separation of concerns, allowing the AMF to focus on mobility management while the SMSF handles SMS-specific procedures. This modular design aligns with the 5G core network's service-based architecture.
Furthermore, the SMSF ensures that SMS remains a reliable service in 5G, supporting essential use cases such as two-factor authentication, service notifications, and person-to-person messaging. It also facilitates roaming by providing a standardized interface for SMS delivery across networks. The introduction of the SMSF in Rel-15 was a key milestone in the evolution of SMS, ensuring its continued relevance in the 5G era. Its maintenance through Rel-20 reflects its stable design and ongoing importance.
What changed in its specifications
The latest release-to-release comparison of specifications that define SMSF. 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 →Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Technology family
Messaging services · Services
- Phase 1 CBC, MO-SMS, MT-SMS, SMS, SMS-CB
- Phase 2 CBE, SMS-GMSC, SMS-IWMSC
- R99 EMS, MMS, MMS User Agent, MMSE
- Rel-4 MMS Relay/Server
- Rel-6 IP-SM-GW, MSCF
- Rel-7 SMS over IP, SMS Router
- Rel-8 SMS over SGs
- Rel-15 CBCF, PWS-IWF, SMS over NAS, SMSF
- Rel-17 Legacy 3GPP Message Gateway, MSGin5G, MSGin5G Client, MSGin5G Server, Non-3GPP Message Gateway
- 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 sourcesDocumented 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.
Rel-15 specifies the SMSF for the first time: the Nsmsf service interface and SMS activation over NAS, UDM registration, MO/MT SMS handling via the AMF, and converged charging.
- “The present document specifies the stage 3 protocol and data model for the Nsmsf Service Based Interface.” TS 29.540 v15.9.0
- “This service allows AMF to authorize SMS and activate SMS for the served user on SMSF.” TS 29.540 v15.9.0
- “The SMSF shall be able to perform convergent charging by interacting with CHF, for charging data related to SMS over NAS.” TS 32.274 v15.4.0
In Rel-16 the SMSF gained an SMSF Set ID in UDM registration, SMSF redirection within SMSF sets, and revised registration, deregistration and SMS-over-NAS procedures with UDM and AMF.
- “If the SMSF belongs to an SMSF Set, the NF Set ID of the SMSF Set shall be included in the request message.” TS 29.503 v16.18.0
- “If an SMSF within an SMSF set redirects a service request to a different SMSF of the set” TS 29.540 v16.10.0
- SMSF Set ID in SMSF Registration TS 29.503CR0337
SMSF gained SBI-based MT SM transmit support indication, separate per-access registration and deregistration for 3GPP and non-3GPP, and new Nsmsf consumers (SMS-GMSC, IP-SM-GW, SMS Router) for downlink SMS payload.
- “the SMSF shall perform seperate individual SMSF registration for each access type.” TS 29.503 v17.22.0
- “If the SMSF supports SBI-based MT SM transmit, the "SBI support indication" of the SMSF shall be included in the SMSF registration information.” TS 29.503 v17.22.0
- “This service also allows the SMS-GMSC, SMS Router and IP-SM-GW to send the SMS payload in downlink direction to the SMSF.” TS 29.540 v17.6.0
SMSF gained a procedure to update parameters such as Memory Available in its UDM registration via PATCH for 3GPP and non-3GPP access, plus related MT-SMS failure handling for UE power saving.
- “When the SMSF detects that the UE has memory available for SMS, the SMSF shall send the update message with ueMemoryAvailableInd set to true.” TS 29.503 v18.13.0
- “The SMSF sends a PATCH request to the resource representing the UE's SMSF registration for 3GPP access” TS 29.503 v18.13.0
- Indication of "Memory Available" from SMSF TS 29.503CR1053
SMSF behaviour was extended in Rel-19, with MPS for Messaging priority handling in the Nsmsf SBI and MT-SMS, SMSF data restoration via resetId re-registration, and corrected charging characteristics use.
- “The SMSF may decide to re-register at the UDM when receiving a data restoration notification containing a matching resetId.” TS 29.503 v19.7.0
- “If the Message Priority header received in step 2 contains a value that indicates MPS, the SMSF may set the transport priority” TS 23.502 v19.9.0
- MPS for Messaging SMSF SBI TS 29.540CR0121
SMSF gains new behaviour: it detects MO-SMS to an Emergency Response Center and forwards it to the SMS-IWMSC/SC with GPSI and ULI, and MT SMS delivery failures are reported in delivery reports.
- “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
- “The SMSF provides the UE GPSI (i.e. the MSISDN) and UE ULI (e.g. Cell-ID) when sending the SMS message” TS 23.502 v20.3.0
- “shall be reported in the MT SMS Delivery Report carried in SmsDeliveryData, and shall not be treated as application errors” TS 29.540 v20.1.0
Defining Specifications
3GPP specifications that define or reference SMSF, 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.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.540 vk00 | 5G Service-Based SMS Architecture | Rel-20 read |
| TR 28.840 vi10 | Technical Report | Rel-18 read |
| TR 28.843 vi10 | Technical Report on Charging Aspects for Vertical Scenarios | Rel-18 read |
| TS 29.337 vj00 | Diameter T4 Interface for MTC Device Triggering | Rel-19 read |
| TS 29.503 vk10 | UDM Service Based Interface | Rel-20 read |
| TS 29.505 vk00 | UDR Services for Subscription Data | Rel-20 read |
| TS 29.518 vk10 | AMF Service Based Interface | Rel-20 read |
| TS 29.540 vk10 | Nsmsf Service-Based Interface for SMSF | Rel-20 read |
| TS 29.577 vk00 | IP-SM-GW and SMS Router SBI Stage 3 | Rel-20 read |
| TR 29.829 vh10 | SMS Service-Based Interfaces for 5G Core | Rel-17 read |
| TS 32.290 vk00 | 5G Charging Service-Based Architecture | Rel-20 read |
| TS 32.291 vk10 | 5G Charging Service-Based Interface | Rel-20 read |
| TS 33.529 vj10 | SCAS for SMSF Security Assurance | Rel-19 read |