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

Glossary term · Core Network

SMS-GMSC

Short Message Service Gateway MSC

Core Network →

SMS-GMSC is the Gateway MSC that acts as the entry point for Mobile-Terminated Short Messages from an external SMSC, querying the HLR for routing information to forward the SMS.

Introduced
Phase 2
Where
Management
Specifications
6 specs
Also in
Core Network
SMS-GMSC Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Short Message Service Gateway MSC (SMS-GMSC) is a critical functional entity within the Circuit-Switched (CS) domain of 2G/3G core networks, specifically defined for SMS delivery. Its primary role is to serve as the gateway for Mobile-Terminated Short Messages (MT-SM) entering the Public Land Mobile Network (PLMN) from an external Short Message Service Centre (SMSC). When an SMSC has a message destined for a mobile subscriber, it submits the message to the SMS-GMSC, typically via the MAP protocol over SS7 or IP-based SIGTRAN links. The SMS-GMSC is not necessarily a physically distinct node; it is often a functional role implemented within a standard Mobile Switching Centre (MSC).

Upon receiving an MT-SM, the SMS-GMSC's first action is to interrogate the Home Location Register (HLR) to obtain routing information for the destination Mobile Station International Subscriber Directory Number (MSISDN). It sends a MAP_SEND_ROUTING_INFO_FOR_SM message to the HLR. The HLR responds with the current serving MSC address (the MSC where the subscriber is currently registered) and, if available, the Mobile Station Roaming Number (MSRN). Armed with this routing information, the SMS-GMSC then forwards the short message to the identified serving MSC, which is responsible for the final delivery to the mobile device over the radio interface.

The SMS-GMSC also handles error scenarios. If the HLR indicates the subscriber is absent or unknown, the SMS-GMSC will inform the SMSC, which may store the message for later retry. It manages protocol conversion and adaptation between the external SMSC interface and the internal MAP signaling used within the PLMN. In evolved architectures like GSM/UMTS with IP Multimedia Subsystem (IMS), the SMS-GMSC's role is complemented by the IP-SM-GW for SMS over IP, but it remains essential for traditional CS-domain SMS delivery. Its function ensures that the SMSC, which may be operated by a third party, does not need direct knowledge of the subscriber's dynamic location within the network, maintaining network topology abstraction and subscriber privacy.

Purpose & Motivation

The SMS-GMSC was introduced to decouple the external Short Message Service Centre (SMSC) from the internal mobility and routing complexities of the GSM/UMTS network. Before its standardization, an SMSC would need direct, updated knowledge of every subscriber's location to deliver messages, which is impractical due to subscriber mobility and network topology changes. The SMS-GMSC solves this problem by acting as a fixed, known entry point into the network.

Its creation was motivated by the need for a scalable, standardized interface for SMS interworking. It allows multiple external SMSCs (from the same or different operators) to connect to the PLMN via a single, well-defined gateway function. This architecture centralizes the critical task of querying the HLR for routing information, offloading this responsibility from the SMSC. It addresses limitations of earlier, proprietary messaging gateways by providing a standardized 3GPP procedure (MAP signaling) for routing information retrieval and message forwarding, ensuring interoperability between network equipment from different vendors and between different operators' networks. The SMS-GMSC is a cornerstone of the globally interoperable SMS ecosystem.

What changed in its specifications

The latest release-to-release comparison of specifications that define SMS-GMSC. Each summary describes the whole specification, not only this term.

TS 23.060Rel-18 → Rel-19

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 →
TS 29.338Rel-18 → Rel-19

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

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF

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-GMSC used together with SMS Router
    “If an SMS Router is present, the message flow in 15aa is used, except that a 4c Failure Report message is transparently transferred to the SMS‑GMSC from the MSC or SGSN by the SMS Router instead of a 4b Delivery Report.” TS 23.040

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 10 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 2 introduced

Introduced in Phase 2 (release dating of the term; no individual change cited).

R99 specification text

TS 23.060 v3h0 specifies the SMS-GMSC for GPRS: Gd interface to the SGSN, MAP signalling, and mobile-terminated SMS routing via HLR query and forwarding to the SGSN.

  • “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
  • “SMS‑GMSC examines the destination MS Address, and sends a Send Routeing Info For Short Message message to the relevant HLR.” TS 23.060 v3.17.0
  • “SMS‑GMSC forwards the SM to the SGSN.” TS 23.060 v3.17.0
Rel-6 specification text

In 23.060 the HLR's Send Routeing Info For Short Message handling toward the SMS-GMSC changed: the result may carry SGSN and/or MSC numbers, and barred MT SMS gets an error response.

  • “If the MT SMS is barred, the HLR returns a Send Routing Info for Short Message Error message with an appropriate cause.” TS 23.060 v6.15.0
  • “The result may contain the MS's current SGSN Number, the MSC Number, or both.” TS 23.060 v6.15.0
Rel-11 specification text

SMS-GMSC gains S6c/SGd Diameter behaviour: it retrieves routing info from the HSS, may receive two serving node addresses, and delivers MT SMS over SGd to the selected serving node.

  • “The SMS-GMSC shall make use of this procedure to retrieve the routing information needed for routing the short message to the serving MSC or MME or SGSN” TS 29.338 v11.3.0
  • “This bit shall be set if the SMS-GMSC supports receiving of two serving nodes addresses from the HSS.” TS 29.338 v11.3.0
  • “the SMS-GMSC shall relay this information to the HSS.” TS 29.338 v11.3.0
Rel-12 specification text

SMS-GMSC gained support for Diameter-based delivery of MT short messages over the Gdd interface to the SGSN, and uses the SGSN Diameter identity returned in the routing info answer.

  • “The SMS-GMSC shall make use of this procedure over the SGd interface or over the Gdd interface for the delivery of a MT short message” TS 29.338 v12.6.0
  • “the SMS-GMSC or the SMS Router shall use the received Diameter address if the SMS-GMSC or the SMS Router transfers the terminating short message over the SGd or the Gdd interface.” TS 29.338 v12.6.0
  • “The result also contains the SGSN Diameter identity if the SGSN number is present and if Gdd is supported.” TS 23.060 v12.11.0
Rel-13 1 CR

SMS-GMSC gained new behaviour in Rel-13: it may signal a maximum retransmission time and retransmit pending MT SMS when alerted by the MME/SGSN, supporting eDRX and power-saving UEs.

  • “The SMS-GMSC may include the Maximum-Retransmission-Time AVP in the MT Forward Short Request to indicate that it is capable to retransmit the Short Message” TS 29.338 v13.5.0
  • “When receiving an Alert Service Centre request, the SMS-GMSC shall retransmit pending MT SMS(s) for the destination user identified by the User Identifier Alert” TS 29.338 v13.5.0
  • Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX TS 29.338CR0019
Rel-14 specification text

The DRMP AVP may now be used to set the DSCP marking for transport of the associated Diameter message.

  • “The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message.” TS 29.338 v14.4.0
Rel-15 specification text

The SMS-GMSC's S6c/SGd routing-information retrieval now covers SMSF registered for 3GPP and non-3GPP access, with an SMSF-Support feature and SMSF-related AVPs handled by the SMS-GMSC.

  • “retrieve the routing information needed for routing the short message to the serving MSC or MME or SGSN or SMSF registered for 3GPP access” TS 29.338 v15.4.0
  • “If the feature "SMSF-Support" is not supported by the SMS-GMSC, IP-SM-GW, or SMS Router, the AVPs SMSF-3GPP-Address” TS 29.338 v15.4.0
  • “When the SMS-GMSC requests routing information from UDM/HSS for a UE not registered in 5GC” TS 23.502 v15.17.0
Rel-17 specification text

UDM stores the SC address in the MWD list only for an SMS-GMSC using non-SBI interfaces, and an SBI-capable entity is handled through an Nudm_EventExposure subscription; the paragraph also references TS 23.540.

  • “In the case that the service-related entity is an SMS-GMSC using non-SBI interfaces, the UDM stores the SC address within the MWD list.” TS 23.502 v17.15.0
Rel-19 specification text

SMS-GMSC gains MPS-for-Messaging priority handling (MPS-Priority AVP, DSCP, DRMP) and new retry/alert behaviour on RDA and SMSF address handling for MT SMS delivery.

  • “the SMS-GMSC shall immediately retry MT SMS delivery via the newly provided serving node(s).” TS 29.338 v19.3.0
  • “the SMS-GMSC shall include a Message Priority header (or DRMP) to indicate priority information towards SMSF.” TS 23.502 v19.9.0
  • “the SMS-GMSC sets the Diameter priority and DSCP for SMS messages to values that are appropriate for MPS.” TS 23.272 v19.1.0

Defining Specifications

3GPP specifications that define or reference SMS-GMSC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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.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