Description
The Gateway Mobile Services Switching Centre (GMSC) is a pivotal functional node in the circuit-switched (CS) domain of 2G (GSM) and 3G (UMTS) mobile networks. It is essentially a Mobile Switching Centre (MSC) with the specific additional role of interfacing the Public Land Mobile Network (PLMN) with external networks. These external networks include other PLMNs, the Public Switched Telephone Network (PSTN), and Integrated Services Digital Network (ISDN). The GMSC's primary technical function is to determine the current serving MSC (Visited MSC or VMSC) of a called mobile subscriber when a call originates from outside the subscriber's home network.
Architecturally, the GMSC contains the full call switching and signaling capabilities of a standard MSC. Its key differentiator is its interaction with the Home Location Register (HLR). When a call is routed to a GMSC (typically because the dialed number is a Mobile Station International Subscriber Directory Number, or MSISDN), the GMSC does not initially know which MSC is currently serving the target subscriber. It therefore sends a signaling message, specifically a Send Routing Information (SRI) request via the Mobile Application Part (MAP) protocol, to the subscriber's HLR. The HLR, which maintains the subscriber's profile and current location area, queries the relevant Visitor Location Register (VLR) to obtain a temporary routing number called the Mobile Station Roaming Number (MSRN).
The HLR returns this MSRN to the GMSC. The MSRN is a temporary, network-internal number that points to the current VMSC. Armed with the MSRN, the GMSC can then route the incoming call through the network's CS core to the correct VMSC. The VMSC, upon receiving the call setup request with the MSRN, correlates it with the actual International Mobile Subscriber Identity (IMSI) of the called party and completes the call setup to the mobile station. This process, known as call routing and interrogation, is transparent to the calling party and enables seamless mobility. In many network implementations, all MSCs may have GMSC functionality, or dedicated nodes may be deployed as gateways.
Purpose & Motivation
The GMSC was created to solve the fundamental problem of routing calls to a mobile subscriber whose location is not fixed and is unknown to the external, fixed telephone network. In the pre-cellular era, telephone switches routed calls based on a fixed geographic association of a directory number. This model breaks completely for mobile users. The GMSC, in conjunction with the HLR/ VLR database system, introduced the intelligence needed to decouple a subscriber's identity (MSISDN) from their physical network attachment point.
Its development was a cornerstone of the GSM architecture, enabling true terminal mobility across wide geographic areas. Before this architecture, mobile systems were often limited to local or regional operation without efficient inter-network calling. The GMSC model provided a scalable, standardized method for any external switch (in the PSTN or another country's mobile network) to route a call to a single, well-known gateway (the GMSC) of the subscriber's home network. The home network's GMSC then takes responsibility for finding the subscriber wherever they are, using its internal location databases. This separation of external routing (to the home network) and internal, dynamic routing (to the visited location) is what made global mobile roaming commercially and technically feasible.
What changed in its specifications
The latest release-to-release comparison of specifications that define GMSC. Each summary describes the whole specification, not only this term.
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 →Rel-19 brings only minor changes to TS 23.078: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.078 →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
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 12 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 1 (release dating of the term; no individual change cited).
Release 99 specifies the GMSC's CAMEL role: it receives T-CSI from the HLR, suspends call processing at detection points and reports call events to the gsmSSF through new GMSC-HLR, GMSC-gsmSSF and GMSC-MSC interfaces.
- “the GMSC receives an O/D/T‑CSI from the HLR, indicating the GMSC to request instructions from the gsmSSF” TS 23.078 v3.19.0
- “T-CSI identifies the subscriber as having terminating CAMEL services in the GMSC” TS 23.078 v3.19.0
- “will occur only if the GMSC supports CAMEL phase 2 or later” TS 23.018 v3.12.0
The CUG information element sent by the GMSC now depends on the GMSC itself supporting CUG, rather than the HPLMN supporting it, and the CAMEL_MT_GMSC_ANSWER call to the VMSC was removed.
- “Shall be present if the GMSC received it in the IAM and the GMSC supports CUG, otherwise shall be absent.” TS 23.018 v4.7.0
- “Shall be present if the GMSC received it in the IAM and the HPLMN supports CUG, otherwise shall be absent.” TS 23.018 v4.7.0
GMSC gained CAMEL phase 4 support: it indicates supported CAMEL phase and downloadable CSIs to the HLR in Send Routeing Info and informs the gsmSCF of offered functionalities.
- “If a GMSC supports at least one CAMEL phase 4 CSI, then the GMSC indicates in the Send Routeing Info to the HLR the phase of CAMEL” TS 23.078 v5.12.0
- “For MF calls at the GMSC, triggering at DP Collected_Info shall be strictly based on the Forwarded-to-Number received from HLR” TS 23.078 v5.12.0
- “the VMSC/gsmSSF or GMSC/gsmSSF indicates in the IF the CAMEL phase 4 functionalities offered to the gsmSCF” TS 23.078 v5.12.0
GMSC behaviour changed in Rel-6: CAMEL GMSC SDL procedures were corrected, and the GMSC now may send MAP Release_Resources to the VMSC if an ISUP REL arrives before the SRI ack.
- “If an ISUP REL message is received at the GMSC between sending of SRI and receiving of SRI ack, the GMSC does not send IAM to the VMSC.” TS 23.018 v6.6.0
- Redundantly modifying call parameter in CAMEL_MT_GMSC_Notify_CF TS 23.078CR732
- Removal of Int_O_Exception from CAMEL_OCH_MSC2 and CAMEL_MT_GMSC_DISC5 TS 23.078CR739
Rel-7 added a mobile terminating roaming retry procedure in which the GMSC handles Resume Call Handling, re-sends SRI to the HLR and relays the call to the new MSC.
- “the old VMSC shall instruct the GMSC to resume terminating call procedure by sending a MAP Resume Call Handling message.” TS 23.018 v7.7.0
- “A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the GMSC address and the MT Roaming Retry Supported IE in the first SRI sent to the HLR.” TS 23.018 v7.7.0
- “Missing SRIack negative response to ISUP release cause mapping in GMSC” TS 23.018 v7.7.0
The GMSC gains a specified requirement to include an eMLPP priority parameter when it supports eMLPP and the call is an eMLPP call, with priority levels A and B mapped to call priority 0.
- “This parameter should be present if the GMSC supports the eMLPP feature and if the call is an eMLPP call.” TS 23.018 v8.5.0
The GMSC gains MT Roaming Retry behaviour: it includes the MT Roaming Retry Supported IE in the SRI and, on an 'absent subscriber' response with reason mtRoamingRetry, releases the T-CSI dialogue and re-sends a new SRI.
- “The GMSC shall release the T-CSI dialogue (if existing) and retry the terminating call setup towards the new MSC by sending an additional SRI” TS 23.018 v9.4.0
- “A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the GMSC address, and the MT Roaming Retry Supported IE” TS 23.018 v9.4.0
- “the GMSC re-sends a new SRI to the HLR (still a 'basic call' interrogation type) using a new call reference number.” TS 23.018 v9.4.0
Rel-10 text removes the super-charger MAP Send Identification triggers for the RCH procedure and adds returning the VMSC Address with the MSRN from the HLR to the GMSC in the SRI ack.
- “the HLR shall pass in the SRI ack to the GMSC the MSRN and the VMSC Address received in the PRN ack” TS 23.018 v10.4.0
- “Upon receipt of the ISUP IAM message which was preceeded by a MAP Cancel Location message, or upon receipt of the MAP Cancel Location message while paging” TS 23.018 v10.4.0
TS 23.018 now specifies GMSC behaviour for mobile terminating roaming retry (Resume Call Handling), domain selection via HLR interrogation, enhanced CLI handling and anonymous call rejection announcements.
- “Receipt of the MT Roaming Retry Supported IE in the PRN indicates that the GMSC supports the Resume Call Handling procedure” TS 23.018 v11.4.0
- “This procedure shall also be performed if the GMSC supports the ACR supplementary service.” TS 23.018 v11.4.0
- “The GMSC will play an announcement towards the calling user to signal that the call is rejected due to anonymous call rejection” TS 23.018 v11.4.0
TS 23.018 adds MTRF Optimal Routing when GMSC and new MSC/VLR are the same node: the GMSC sends its address and call reference in MAP Send Routing Information, and the new MSC/VLR delivers the MT call directly.
- “The GMSC shall include the GMSC address and the Call reference number used by the GMSC for this call in the MAP Send Routing Information” TS 23.018 v12.2.0
- “The new MSC/VLR shall determine that it also performs the GMSC function for the call identified by the Call Reference Number” TS 23.018 v12.2.0
- MTRF Optimal Routing when the GMSC and new MSC/VLR are the same node TS 23.018CR0198
SMS-GMSC behaviour for MT SM retransmission to UEs in eDRX was changed: retransmission at the time requested in the Delivery Report and triggering during inter MME/SGSN mobility.
Defining Specifications
3GPP specifications that define or reference GMSC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.044 v300 | GSM Teletex Service Support | R99 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.226 vj00 | Global Text Telephony (GTT) Stage 2 | Rel-19 read |
| TS 23.806 v700 | Voice Call Continuity between CS and IMS | Rel-7 read |
| TS 24.206 v750 | Voice Call Continuity Between CS and IMS | Rel-7 read |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 read |
| TS 28.702 vj00 | Core Network NRM IRP Information Service | 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.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.276 vj00 | VCS Online Charging from Proxy Function | Rel-19 read |
| TS 32.293 vj00 | Proxy Function in Domestic Service Provider | 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 |
| TR 22.945 v300 | Fax Services Guidance for GSM/UMTS | R99 read |
| TS 24.228 v590 | IP Multimedia Call Control Signaling Flows | Rel-5 read |