Description
The IP Short Message Gateway (IP-SM-GW) is a core network element defined in 3GPP specifications to facilitate Short Message Service (SMS) delivery over IP-based access networks. Its primary role is to act as an intermediary and protocol converter between the legacy SMS infrastructure, which is based on circuit-switched signaling (MAP over SS7), and IP-based user equipment. The gateway appears as a Mobile Switching Center/Visitor Location Register (MSC/VLR) or a Short Message Service Center (SMSC) to the legacy network, while presenting an IP-based interface (typically using SIP protocols as part of IMS) to the UE.
Architecturally, the IP-SM-GW is often integrated with or closely associated with the IP Multimedia Subsystem (IMS). It implements the functionality defined in 3GPP TS 23.204 and TS 24.341. When a UE is registered only over IP (e.g., via VoLTE, VoWiFi, or a data connection), the IP-SM-GW registers the user's IP address and MSISDN with the Home Subscriber Server (HSS) as the current serving node for SMS. For Mobile-Terminated (MT) SMS, the SMSC routes the message to the IP-SM-GW based on this HSS information. The IP-SM-GW then converts the MAP message into a SIP MESSAGE request and delivers it to the UE over the IP path (e.g., via the IMS Core).
For Mobile-Originated (MO) SMS, the process is reversed. The UE sends a SIP MESSAGE containing the SMS payload to the IP-SM-GW via IMS. The IP-SM-GW extracts the content, formats it into a standard MAP message, and forwards it to the SMSC for delivery to the recipient. The gateway handles essential functions like delivery reports, converting between SIP and MAP status codes, and managing subscriber visibility (hiding the IP nature of the delivery from the legacy SMSC). It also supports SMS over non-3GPP access (like WLAN) and is a key component for enabling SMS service in networks that have deployed Circuit-Switched Fallback (CSFB) or where the radio access is LTE-only (without a circuit-switched domain).
Purpose & Motivation
The IP-SM-GW was created to solve a critical service continuity problem during the transition from circuit-switched (2G/3G) to all-IP (4G/5G) network architectures. SMS is a ubiquitous, reliable, and highly profitable service. Early LTE deployments (pre-VoLTE) were data-only (packet-switched), with no native circuit-switched domain to carry voice calls or SMS. Without a solution, LTE devices would lose SMS capability, which was unacceptable for users and operators.
Initial workarounds like Circuit-Switched Fallback (CSFB) for SMS forced the device to temporarily fall back to a 2G/3G network to send/receive messages, causing delay and signaling overhead. The IP-SM-GW provided a more elegant, native IP solution. It allowed operators to offer SMS as an IP application from day one of their LTE deployments, independent of voice strategy. This was a key enabler for early LTE devices and data-centric services.
Furthermore, the IP-SM-GW facilitated the introduction of rich communication services and VoLTE/VoWiFi by ensuring that the foundational SMS service remained available over the same IP connection used for voice and data. It bridged the gap between the old and new network cores, protecting the investment in legacy SMSC infrastructure while enabling service evolution. Its creation was motivated by the need to maintain a vital service, reduce dependency on legacy radio networks, and pave the way for fully IP-based communication.
What changed in its specifications
The latest release-to-release comparison of specifications that define IP-SM-GW. Each summary describes the whole specification, not only this term.
Added QoS provisioning for 3GPP/WLAN interworking, IMS emergency call support over WLAN, private network access, external AAA server authentication/accounting, and external AAA server initiated tunnel disconnection.
Full comparison in TS 23.234 →Added MPS priority handling for messaging across HSS, SMS Router, and network elements with new AVPs and DSCP values. Added NR-Cell-Global-Identity as optional IE for originating and MT UE cells in emergency LCS routing.
Full comparison in TS 29.338 →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 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.
Introduced in Rel-6 (release dating of the term; no individual change cited).
IP-SM-GW is specified for the first time, providing protocol interworking for SM delivery between IP-based UEs and the SC, with authorization, domain retry, HLR/HSS interfaces and MAP support.
- “The IP-SM-GW shall provide the protocol interworking for delivery of the short message between the IP-based UE and the SC.” TS 23.204 v7.6.0
- “Supporting the registration and de-registration from the IP-SM-GW to the HLR/HSS for SMS delivery.” TS 23.204 v7.6.0
- “This service is also used by external Short Message Gateway (IP-SM-GW) for updating the IP-SM-GW Number stored in the HLR.” TS 29.002 v7.15.0
The IP-SM-GW gained new responsibilities in Rel-8: re-attempting delivery in another domain, checking UE IMS capability, selecting transport or service-level interworking, and reporting delivery status to the HSS.
- “The IP‑SM‑GW takes responsibility to re-attempt the delivery of the message in another domain which is listed in the sequence of the priority” TS 23.204 v8.5.0
- “the IP-SM-GW shall verify the registration status of the UE.” TS 23.204 v8.5.0
- Behaviour of the IP-SM-GW for SM Delivery Status Report TS 29.002CR0875
IP-SM-GW gained new behaviour in Rel-9: it can use UE-reachability subscription in the MME and SGSN, and its Sh interface handling of UE reachability was changed.
- “This service is also used by a Service Related Entity (e.g. the IP-SM-GW) to activate a one-time subscription of UE-reachability” TS 29.002 v9.13.0
- IP-SM-GW UE reachability handling over Sh TS 29.329CR0143
IP-SM-GW gained new behaviour: interworking with OMA CPM/chat sessions, ISF-based interworking decisions, and MAP timer guidance and SC Address handling in Rel-10.
- “or is registered in IMS but does not advertise the Converged IP Messaging, SIMPLE IM or SMSIP capability, the Short Message shall not be interworked” TS 23.204 v10.2.0
- “If an ISF is deployed in the network, the ISF may take the decision to interwork using SMS and sends the message to the IP-SM-GW” TS 23.204 v10.2.0
- Prevention of Timeout in IP-SM-GW TS 29.002CR0957
IP-SM-GW gained new behaviour in Rel-11: it can return or forward to MME addresses (SGd), is a MAP target node with new indicators, and can update its Diameter address in the HLR.
- “Alternatively, the IP-SM-GW may return the address(es) of the current MSC, SGSN and/or MME” TS 23.204 v11.5.0
- “This parameter is used by the external IP-SM-GW for updating the IP-SM-GW Number and IP-SM-GW Diameter Address stored in the HLR.” TS 29.002 v11.12.0
- “This indicator indicates by its presence that the IP-SM-GW shall try to deliver the short message via IMS without retrying to other domains.” TS 29.002 v11.12.0
IP-SM-GW gained new behaviour for MSISDN-less SMS: delivering via SIP-URI, returning and forwarding MSISDN-less correlation IDs to the SMSC for retries, and handling IMSI-addressed device triggering.
- “IP-SM-GW forwards both the SM and MSISDN-less correlation ID to the SMSC for storage and for subsequent retries.” TS 23.204 v12.5.0
- “IP-SM-GW shall return a MSISDN-less correlation ID along with an indication of temporary error pointing to unsuccessful delivery attempt” TS 23.204 v12.5.0
- “The E/Gd/Gdd/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 v12.5.0
The SM Delivery Timer value may now be sent to the SGSN or MSC/VLR as well as the IP-SM-GW, and message 8 gets an 'Otherwise' branch with the SMS-GMSC timer value.
- “This parameter indicates the SM Delivery Timer value set in the SMS-GMSC to the IP-SM-GW, SGSN or MSC/VLR.” TS 29.002 v13.6.0
- “Otherwise, The message should include the timer value used at the SMS-GMSC for the” TS 29.002 v13.6.0
Rel-14 specifies that for T4 device triggering the HLR must not forward the request to an IP-SM-GW or SMS Router, and a CR addresses the SC Address in the IP-SM-GW Register Response.
- “the HLR may return up to three serving node numbers and shall not forward the request to an IP-SM-GW or SMS Router” TS 29.002 v14.5.0
- SC Address in IP-SM-GW Register Response TS 29.002CR1231
IP-SM-GW behaviour was extended in Rel-15 to handle SMSF as a delivery target alongside MSC/SGSN/MME, including MT SMS domain selection and returning SMSF addresses.
- “The IP-SM-GW forwards the Short Message to the domain which is listed in the fifth place in its priority list.” TS 23.204 v15.0.0
- “the IP-SM-GW may return the address(es) of the current MSC, SGSN, MME and/or SMSF” TS 23.204 v15.0.0
- MT SMS domain selection by IP-SM-GW TS 23.204CR0109
IP-SM-GW gained responsibility to retry SM delivery in other domains, report accurate delivery status to the HSS, and manage UNRI and UE-reachability notification; Rel-16 also adds IP-SM-GW registration over Nudm.
- “The IP‑SM‑GW takes responsibility to re-attempt the delivery of the message in another domain” TS 23.204 v16.0.0
- “the IP-SM-GW clears local UNRI and informs HLR/HSS that the UE is available again.” TS 23.204 v16.0.0
- “The HSS sends a PUT request to the resource .../{ueId}/registrations/ip-sm-gw, to create an IP-SM-GW registration” TS 29.503 v16.18.0
Rel-17 adds SBI support for the IP-SM-GW: an SBI Support Indication in registration, and a new Nipsmgw SMService offering SBI-based MT SM transmit, specified in TS 29.577.
- “If the IP-SM-GW indicated support for SBI-based SMS when registering in HSS, "SBI Support Indication" shall be included in the IP-SM-GW registration information.” TS 29.503 v17.22.0
- “The Nipsmgw_SMService service provides SBI-based MT SM transmit through IP-SM-GW.” TS 29.577 v17.2.0
- Add SBI support Indication for IP-SM-GW. TS 29.503CR0864
Rel-18 adds IP-SM-GW reference points for MO-SMS and updates the IP-SM-GW MT-SMS service operations and deregistration text, including a corrected TS 23.632 figure reference.
- IP-SM-GW Reference Points for MO-SMS TS 23.540CR0019
- “The NF Service Consumer shall send a POST request to the resource representing the UE's Mobile Terminated Short Message Information resource” TS 29.577 v18.4.0
IP-SM-GW gains MPS for Messaging behaviour: it applies MPS Resource-Priority to SIP messages and sets MPS transport priority on outgoing Short Messages, handling them with priority.
- “If the MPS for Messaging indication for the UE is activated, the IP-SM-GW applies an MPS appropriate Resource-Priority information to the SIP message” TS 23.204 v19.1.0
- “the IP-SM-GW sets the transport priority of the outgoing Short Message to a value appropriate for MPS and handles the Short Message with priority.” TS 23.204 v19.1.0
Defining Specifications
3GPP specifications that define or reference IP-SM-GW, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 read |
| TS 29.338 vj30 | Diameter protocols for SMS in MME/5GS | Rel-19 read |
| TS 29.577 vk00 | IP-SM-GW and SMS Router SBI Stage 3 | Rel-20 read |