Description
The Short Message Service Interworking MSC (SMS-IWMSC) is the functional counterpart to the SMS-GMSC, handling the outbound path for Mobile-Originated Short Messages (MO-SM) within 2G/3G Circuit-Switched core networks. When a mobile subscriber sends an SMS, the message is first delivered over the radio interface to their current serving MSC. The serving MSC, recognizing the message as mobile-originated, then forwards it to the SMS-IWMSC. The SMS-IWMSC serves as the designated gateway from the PLMN to the external Short Message Service Centre (SMSC). Like the SMS-GMSC, it is typically a functional role collocated within a physical MSC.
The SMS-IWMSC receives the MO-SM from the serving MSC via internal MAP signaling (MAP_FORWARD_SHORT_MESSAGE). Its key responsibility is to determine the correct destination SMSC for the message. This routing decision is often based on configuration, such as a default SMSC for the subscriber's home network or a specific SMSC address provided by the HLR during subscriber profile retrieval. The SMS-IWMSC then performs any necessary protocol adaptation and submits the message to the identified external SMSC, usually using the same MAP-based interface (e.g., MAP_MT_FORWARD_SHORT_MESSAGE) over SS7 or IP links.
This entity also manages delivery reports and failures in the mobile-originated direction. If the external SMSC confirms successful receipt, the SMS-IWMSC may relay a positive delivery report back through the serving MSC to the originating mobile device. Conversely, if the SMSC rejects the message or is unreachable, the SMS-IWMSC handles the error and may inform the serving MSC. The SMS-IWMSC provides a single, controlled egress point for all MO-SM traffic, allowing for centralized billing, lawful interception, and message screening before messages leave the operator's network. It works in tandem with the SMS-GMSC to form the complete SMS gateway functionality for the CS domain.
Purpose & Motivation
The SMS-IWMSC was standardized to provide a controlled and standardized exit point from the PLMN for subscriber-originated text messages, mirroring the entry-point function of the SMS-GMSC. Its creation solved the problem of how a serving MSC, which handles subscriber mobility, should route an outgoing SMS to a potentially external and fixed SMSC. Without a dedicated interworking function, each MSC would need direct connectivity and routing configurations for all possible SMSCs, leading to operational complexity and scaling issues.
This architecture centralizes the interworking function, simplifying network management and enabling features like centralized billing for originated messages and consistent application of regulatory requirements (e.g., content filtering, lawful interception) at the network border. It addresses the limitation of having mobile-originated traffic exit the network in an ad-hoc manner from any MSC. By funneling all MO-SM traffic through the SMS-IWMSC, operators gain a strategic point of control and visibility for outbound messaging services. It was a key component in making SMS a reliable, billable, and manageable service for network operators.
What changed in its specifications
The latest release-to-release comparison of specifications that define SMS-IWMSC. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.060 →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
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
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 9 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 Phase 2 (release dating of the term; no individual change cited).
TS 23.060 v3h0 specifies SMS-IWMSC for the first time, including its Gd connection to the SGSN and its role passing mobile-originated SMs to the SM-SC.
- “The SMS‑GMSC and SMS‑IWMSC are connected to the SGSN via the Gd interface to enable the SGSN to support SMS.” TS 23.060 v3.17.0
- “3) SMS‑IWMSC passes the SM to the addressed SM‑SC.” TS 23.060 v3.17.0
- “5) SMS‑IWMSC returns a Forward Short Message Result message to the SGSN indicating successful delivery of the SM.” TS 23.060 v3.17.0
TS 29.338 (first appears in this release) specifies the SMS-IWMSC's role and detailed behaviour on the SGd interface with the MME for forwarding mobile originated short messages to the SMS-SC.
- “This procedure shall be used between the serving MME and the SMS-IWMSC to forward mobile originated short messages from a mobile user to a Service Centre.” TS 29.338 v11.3.0
- “the SMS-IWMSC shall check if the SMS-SC is known, if it is not, an Experimental-Result-Code set to DIAMETER_ERROR_SM_DELIVERY_FAILURE” TS 29.338 v11.3.0
The SMS-IWMSC's MO Forward Short Message procedure now also applies to the SGSN and the IP-SM-GW as the originating node, not only the MME, with errors returned to the MME or the SGSN.
- “This procedure shall be used between the serving MME or SGSN or IP-SM-GW and the SMS-IWMSC” TS 29.338 v12.6.0
- “shall be returned to the MME or the SGSN.” TS 29.338 v12.6.0
TS 29.338 now has the SMS-IWMSC advertise S6c/SGd Diameter application support, receive Alert-Service-Centre-Requests from the HSS and answer them, and use the DRMP AVP for message priority.
- “is sent from the HSS to the SMS-IWMSC and from the MME or SGSN to the SMS-GMSC (possibly via an SMS Router)” TS 29.338 v13.5.0
- “is sent from the SMS-IWMSC to the HSS and from the SMS-GMSC to the MME or SGSN” TS 29.338 v13.5.0
- “The MME, HSS, SMS-IWMSC, SMS-GMSC and SMS Router shall advertise support of the Diameter S6c Application over the S6c interface” TS 29.338 v13.5.0
The SMS-IWMSC gains a new role: it forwards mobile-originated short messages to the MTC-IWF over T4 using the SGd MO-Forward-Short-Message procedure, with specified routing AVPs and capability advertisement.
- “This procedure may also be used between the SMS-IWMSC and the MTC-IWF to forward mobile originated short messages from a mobile user to an MTC-IWF” TS 29.338 v14.4.0
- “The SMS-IWMSC shall be able to obtain the address/name of the MTC-IWF and the associated home network domain name” TS 29.338 v14.4.0
- “The MTC-IWF and SMS-IWMSC shall advertise support of the Diameter SGd Application over the T4 interface” TS 29.338 v14.4.0
The SGd interface between the SMS-IWMSC, SMS-GMSC and SMS Router now also covers the SMSF alongside the MME as an endpoint.
- “- for the SGd interface between the MME/SMSF, the SMS-IWMSC, the SMS-GMSC and the SMS Router.” TS 29.338 v15.4.0
TS 29.510 gains NF profile data for the SMS-IWMSC, with TAI, SUPI and MSISDN serving ranges, the Niwmsc_SMService service, and NF registration and discovery support.
- “List of ranges of MSISDNs supported by the SMS-IWMSC.” TS 29.510 v17.16.0
- “Niwmsc_SMService service offered by the SMS-IWMSC” TS 29.510 v17.16.0
- NF registration and discovery of SMS-IWMSC TS 29.510CR0724
The MME must include MPS-Priority AVP, an MPS DSCP and DRMP AVP in requests toward the SMS-IWMSC when the MPS-for-Messaging bit is set in the last IDR or ULA.
- “The MME shall include the MPS-Priority AVP, shall include a DSCP with a value appropriate for MPS” TS 29.338 v19.3.0
- “in requests toward the SMS-IWMSC if the MPS-for-Messaging bit in the MPS-Priority AVP” TS 29.338 v19.3.0
Defining Specifications
3GPP specifications that define or reference SMS-IWMSC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 28.702 vj00 | Core Network NRM IRP Information Service | Rel-19 read |
| TS 29.338 vj30 | Diameter protocols for SMS in MME/5GS | Rel-19 read |
| TS 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 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 52.402 vj00 | GSM Performance Management Measurements | Rel-19 read |