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

Glossary term · Core Network

MSC

Mobile services Switching Centre

Core Network →

MSC is the core network switch in GSM networks that handles circuit-switched voice calls, mobility management, call routing, and handovers, connecting to the radio access via the A interface.

Introduced
Phase 1
Where
Services › IMS
Specifications
77 specs
Also in
Core Network, Radio Access Network, Management
MSC Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Mobile Services Switching Centre (MSC) is a central component of the GSM (Global System for Mobile Communications) and early 3GPP circuit-switched core network. It functions as a telephone exchange for mobile subscribers, providing call switching, mobility management, and supplementary services. Architecturally, the MSC interfaces with the Base Station Subsystem (BSS) via the standardized A interface, which carries both signaling (using the Base Station System Application Part, BSSAP) and user traffic (circuit-switched voice). It also connects to other MSCs, the Home Location Register (HLR), Visitor Location Register (VLR), and the Public Switched Telephone Network (PSTN) or other external networks.

Operationally, the MSC is responsible for call control, including setup, routing, and teardown of mobile-originated and mobile-terminated circuit-switched calls. It handles mobility management functions such as location registration, location updating, and handover between different cells or MSCs to maintain call continuity as a user moves. The MSC also interacts with the VLR (often co-located) to retrieve subscriber profile and service data for authentication and service authorization. For supplementary services like call forwarding, barring, and conference calling, the MSC executes the necessary logic and interacts with the HLR.

In the network hierarchy, the MSC can serve as a Gateway MSC (GMSC) when it interfaces with external networks, determining the routing for incoming calls by querying the HLR. Its role is purely circuit-switched, handling Time Division Multiplexing (TDM) based voice channels. The MSC does not manage packet-switched data; that function is handled by separate nodes like the SGSN in the packet core. Its operation is defined by a vast set of 3GPP specifications covering protocols, interfaces, and services, making it a highly standardized and interoperable network element.

Purpose & Motivation

The MSC was created to provide the core switching functionality for mobile telephone networks, enabling automated call routing and subscriber mobility. Prior to cellular systems, mobile telephony was manual or used primitive radio systems without seamless handover. The MSC, as part of the GSM architecture, solved the problem of automating call switching and enabling users to move across different coverage areas while maintaining an active call, a fundamental requirement for mass-market mobile communication.

It addressed the limitations of earlier analog mobile systems (like 1G) by introducing digital switching and standardized interfaces, which improved voice quality, security, and network efficiency. The MSC's separation of control and user planes, along with its integration with databases like the HLR/VLR, allowed for advanced features such as international roaming and a wide range of subscriber services. Its creation was motivated by the need for a scalable, reliable, and standardized core network element to support the explosive growth of GSM services globally.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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

Rel-19 brings only minor changes to TS 23.009: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.009 →

Evolution Lineage

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

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 16 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 1 introduced

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

R99 1 CR

Release 99 extends MSC handover to UMTS with 3G_MSC roles for inter-3G_MSC handover/relocation, optionally supporting the A-interface, and adds CAMEL MSC behaviour for CSI-based call control.

  • “handover between Radio Network Subsystems connected to different 3G_MSCs, this is termed an Inter-3G_MSC handover/relocation.” TS 23.009 v3.14.0
  • “The MSC in this category can optionally be a 3G_MSC supporting the A-interface.” TS 23.009 v3.14.0
  • Clarifications of 3G_MSC‑A and 3G_MSC‑B roles TS 23.009
Rel-4 1 CR

Rel-4 changes MSC behaviour: a flexible Iu option lets an RNS connect to several MSCs, and a bearer-independent CS core splits the MSC into MSC server and MGW.

  • “From release 4 onwards, as a network option, an RNS can have Iu interfaces to more than one MSC.” TS 23.009 v4.9.0
  • “The GMSC server and MSC server shall provide the call control and mobility management functions, and the media gateway shall provide the bearer control and transmission resource functions.” TS 23.205 v4.11.0
  • Role of MSC server in FP UP version negotiation for TrFO TS 23.153CR024
Rel-5 specification text

In Rel-5 the MSC gained new behaviour: it sends UESBI-Iu to the RAN and target MSC during handover, and passes an Iu Supported Codecs List to the target MSC.

  • “it shall send UESBI-Iu to the RNS-B during intra-3G_MSC handover/relocation and during subsequent inter-3G_MSC handover/relocation back to 3G_MSC-A” TS 23.009 v5.12.0
  • “3G_MSC-B shall select an Iu Selected codec from the Iu Supported Codecs List provided by MSC-A/3G_MSC-A in the MAP-PREPARE-HANDOVER request” TS 23.009 v5.12.0
  • “when applied, a BSS or an RNS can be connected to more than one MSC.” TS 23.009 v5.12.0
Rel-6 specification text

MSC/MSC server behaviour changed in Rel-6: MGW selection and TDM circuit reservation may be omitted for service based handover, trace session activation to the MGW was added, and directed-retry handling was extended.

  • “For GSM, if performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit MGW selection at this time.” TS 23.205 v6.9.0
  • “the MSC Server activates the Trace Session to the MGW by using the trace activation procedure.” TS 23.205 v6.9.0
  • “If the requested bearer service cannot be provided in GSM, 3G_MSC-A shall indicate in the A-ASSIGNMENT-REQUEST message that handover to UMTS should be performed.” TS 23.009 v6.5.0
Rel-7 specification text

MSC behaviour changed: 3G_MSC-B codec selection now depends on supported-codec-list capability, and MSC gained trunk-originated CAMEL support via TO-CSI with the O-BCSM extended to trunk originating calls.

  • “When processing trunk originating calls requiring CAMEL support, the TO-CSI informs the MSC to request instructions from the gsmSSF.” TS 23.078 v7.10.0
  • “If the Iu Supported Codecs List was not received or 3G_MSC-B does not support the selection of codec based on the Iu-Supported Codecs List” TS 23.009 v7.1.1
  • “If the (G)MSC does not wish to sustain an association with the MGW, the response sent to the MGW may indicate an alternative MGCId signalling address” TS 23.205 v7.8.0
Rel-8 specification text

MSC behaviour was extended in Rel-8: it supports AoIP-based 'BSS Internal Handover with MSC Support' and SRVCC handover control, and MSC Servers enhanced for ICS gain a UA role with IMS registration.

  • “A "BSS Internal Handover with MSC Support" shall only be used if AoIP is supported by both MSC and BSS” TS 23.009 v8.3.0
  • “During a SRVCC handover, SRVCC MSC initiates and controls all the Circuit Switch handover procedure” TS 23.009 v8.3.0
  • “The MSC Server enhanced for ICS shall provide the UA role as defined in Annex A of 3GPP TS 24.229 [11]” TS 24.292 v8.21.0
Rel-9 specification text

MSC roles gained new requirements in Rel-9: MSC-B provides transcoder resources and handles AoIP codec lists in inter-MSC handover, rejects subsequent handover to CSG cells, and an MSC server can be enhanced for ICS.

  • “If AoIP is supported and no transcoder is inserted in the BSS, then 3G_MSC‑B shall provide transcoder resources.” TS 23.009 v9.4.0
  • “the MSC shall reject any request for a subsequent inter-MSC inter-system handover to a CSG cell when acting in the role of an MSC-B” TS 23.009 v9.4.0
  • “The MSC Server enhanced for ICS shall provide the UA role as defined in Annex A of 3GPP TS 24.229 [11]” TS 24.292 v9.19.0
Rel-10 1 CR

MSC Server enhanced for ICS registration behaviour changed: retry handling after failed initial registrations now follows RFC 5626 backoff, Service-Route storage is bound to the contact address, and reg-id/outbound are excluded.

  • “After a maximum of 2 consecutive unsuccessful initial registration attempts, the MSC server enhanced for ICS shall implement the mechanism defined in subclause 4.5 of IETF RFC 5626” TS 24.292 v10.16.0
  • “The MSC server enhanced for ICS shall not include the "reg-id" header field parameter in the Contact header field” TS 24.292 v10.16.0
  • Clarification of the behaviour of the MSC Server enhanced for ICS TS 23.292CR0169
Rel-11 1 CR

Rel-11 adds MSC server enhancements for vSRVCC, new roles and procedures for SRVCC/vSRVCC MSC, and ICS-related MSC server SIP behaviour such as Feature-Caps and P-Access-Network-Info handling.

  • “vSRVCC MSC initiates and controls all the Circuit Switch handover procedure, from its initiation” TS 23.009 v11.2.0
  • “vSRVCC MSC performs query to SCC AS to determine whether to perform the SRVCC or vSRVCC procedure” TS 23.009 v11.2.0
  • Add description for MSC server enhanced for vSRVCC TS 23.009CR0135
Rel-12 1 CR

MSC server behaviour changed in Rel-12: it handles group calls over AoIP, uses the iotl parameter (RFC 7549) in SIP signalling, and optimal routing when GMSC and new MSC/VLR are the same node.

  • “it shall send the BSC IP address and UDP Port to the MGW Access bearer termination using the Configure RTP Connection Point procedure.” TS 23.205 v12.1.0
  • “if the MSC server supports indicating the traffic leg as specified in IETF RFC 7549 [50] and if required by local policy” TS 24.292 v12.10.0
  • MTRF Optimal Routing when the GMSC and new MSC/VLR are the same node TS 23.018CR0198
Rel-13 specification text

In TS 24.292, the MSC server enhanced for ICS may now subscribe to the conference event package, where previously it was prohibited, and must handle conference events after SRVCC.

  • “the MSC server enhanced for ICS may subscribe to the conference event package, as described in 3GPP TS 24.147 [7] subclause 5.3.1.2; and” TS 24.292 v13.4.0
  • “the MSC server enhanced for ICS shall not subscribe to the conference event package; and” TS 24.292 v13.4.0
Rel-14 1 CR

MSC Server enhanced for ICS gained new behaviour in Rel-14, including interaction with IMS for emergency calls and a Response-Source header in SIP failure responses.

  • Allowing ICS MSC to interact with IMS for IMS emergency call handling. TS 23.167CR0303
  • “the MSC Server enhanced for ICS may insert a Response-Source header field with an "fe" header field parameter” TS 24.292 v14.1.0
Rel-15 1 CR

The MSC server enhanced for ICS must now save P-Called-Party-ID from the initial INVITE and use it to set P-Asserted-Identity in 1xx/2xx responses, plus related signalling handling.

  • “The MSC server enhanced for ICS shall save a copy of the P-Called-Party-ID header field if present in the received initial SIP INVITE request.” TS 24.292 v15.1.0
  • “When the MSC server enhanced for ICS sends a 1xx or 2xx response the MSC server enhanced for ICS shall set the P-Asserted-Identity header field” TS 24.292 v15.1.0
  • MSC server using P-Called-Party-ID for PAI TS 24.292CR0352
Rel-16 1 CR

MSC Server behaviour at 5G-SRVCC was corrected/extended so that it performs a TMSI reallocation and a MAP Update Location.

  • MSC Server performing a TMSI reallocation and a MAP Update Location at 5G-SRVCC TS 23.216CR0371
Rel-17 2 CRs

MSC Server identity is now conveyed in SRVCC signalling: the Forward Relocation Response (TS 29.274) and Namf_Location_EventNotify (TS 29.518) were corrected or extended to carry it.

  • MSC Server Identity in Forward Relocation Response during SRVCC handover TS 29.274CR2060
  • MSC Server Identity in Namf_Location_EventNotify during SRVCC handover TS 29.518CR0764

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 21.978 v300 CAMEL Control of VoIP Services Feasibility Study R99 read
TS 22.053 vj00 Tandem Free Operation (TFO) Stage 1 Rel-19 read
TS 22.121 v531 Virtual Home Environment Service Requirements Rel-5 read
TR 22.945 v300 Fax Services Guidance for GSM/UMTS R99 read
TS 23.009 vj00 Handover Procedures in PLMNs Rel-19 read
TS 23.039 v500 SMSC to SME Interface Protocols Rel-5 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.127 v610 Virtual Home Environment Stage 2 Specification Rel-6 read
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19 read
TS 23.171 v390 LCS Stage 2 for UMTS R99 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.226 vj00 Global Text Telephony (GTT) Stage 2 Rel-19 read
TS 23.236 vj00 Intra Domain Connection of RAN Nodes to Multiple CN Nodes Rel-19 read
TS 23.251 vj00 Network Sharing Stage 2 Specification Rel-19 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.806 v700 Voice Call Continuity between CS and IMS Rel-7 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 read
TR 23.910 v550 CS Bearer Services in UMTS Rel-5 read
TR 23.976 vj00 Push Service Requirements Analysis Rel-19 read
TS 24.206 v750 Voice Call Continuity Between CS and IMS Rel-7 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19 read
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19 read
TS 24.802 vc10 II-NNI Traversal Scenario Determination Rel-12 read
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19 read
TS 25.412 vj00 Iu Interface Signalling Transport Specification Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 25.453 vj00 PCAP Protocol Specification Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TR 26.916 ve20 eSRVCC Transcoding Minimization Study Rel-14 read
TR 26.975 vj00 AMR Speech Codec Performance Background Rel-19 read
TR 26.978 vj00 AMR Noise Suppression Selection Phase Technical Report Rel-19 read
TS 27.010 vj00 Multiplexing Protocol for UE-TE Interface Rel-19 read
TS 28.062 vj00 Tandem Free Operation (TFO) Service Description Rel-19 read
TS 28.622 vk40 Generic Network Resource Information Service Rel-20 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TS 29.198 v340 OSA R99 API Stage 3 Specification R99 read
TS 29.278 vj00 CAMEL Application Part (CAP) for IMS Phase 4 Rel-19 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures 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.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.401 vj00 Performance Management Concept & Requirements Rel-19 read
TS 32.405 vj00 UTRAN Performance Measurements Specification Rel-19 read
TS 32.406 vj00 Performance Management for CN PS Domain Rel-19 read
TS 32.407 vj00 PM; CN CS Domain; UMTS/GSM measurements Rel-19 read
TS 32.408 vj00 UMTS/GSM Performance Management Measurements 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 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.849 vd00 VoLTE Roaming Charging Scenarios Rel-13 read
TS 33.102 vj10 3G Security Architecture Specification Rel-19 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.856 vg10 Security for 5G to 3G Voice Continuity Rel-16 read
TS 33.859 vb10 UTRAN Key Hierarchy Study Rel-11 read
TS 41.033 ve00 GSM Lawful Interception Interface Requirements Rel-14 read
TS 43.020 vj00 Security Procedures for GSM Rel-19 read
TS 43.129 vj00 PS Handover in GERAN A/Gb and GAN Modes Rel-19 read
TS 43.130 vj00 Iur-g Interface Overview Rel-19 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19 read
TS 44.160 vg00 GERAN Iu Mode RLC/MAC Protocol Specification Rel-16 read
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read
TS 46.055 vj00 GSM Enhanced Full Rate Speech Codec Performance Rel-19 read
TS 49.008 vj00 BSSAP on E-interface for inter-MSC handover Rel-19 read
TS 52.021 vj00 GSM A-bis Interface Network Management Rel-19 read
TS 52.402 vj00 GSM Performance Management Measurements Rel-19 read