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

Glossary term · Core Network

MSC Server

Mobile Switching Centre Server

Core Network →

MSC Server is the control-plane element of a split mobile switching centre, handling call, session, mobility, and signalling functions.

Introduced
Rel-4
Where
Core Network › Legacy Core
Specifications
2 specs
MSC Server Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The MSC Server is the control-plane element of a split mobile switching centre introduced in 3GPP Release 4. In traditional GSM and early UMTS architectures, an MSC combined call control, mobility management, signalling, and media switching in a single network node. Release 4 separated these functions into an MSC Server, which handles signalling and session control, and a media gateway, which handles bearer and media transport. This split reflects the softswitch model used in IP telephony and allows circuit-switched core networks to migrate toward packet and IP transport without abandoning the existing mobile services architecture.

The MSC Server is responsible for the logical control of mobile subscribers and calls. It interfaces with the radio access network through elements such as the BSC in GSM or the RNC in UMTS, and it communicates with other core network nodes such as the HLR, VLR, GMSC, SCP, and SGSN. It performs subscriber registration, authentication coordination, location updating, call setup and teardown, handover control, routing, and supplementary services. Although the MSC Server does not normally carry user media itself, it controls the media gateway that establishes and modifies the bearer path between the radio access network and external networks such as PSTN, ISDN, or IP networks.

Media control is performed through a gateway control protocol, typically H.248/Megaco over the Mc interface between the MSC Server and the media gateway. The Nc interface is used for control-plane signalling between MSC Servers, while the Nb interface carries user-plane media between media gateways. This architecture allows signalling to be transported over IP while media can be carried over IP or TDM depending on the gateway configuration. The MSC Server therefore acts as the signalling brain of the circuit-switched domain, while the media gateway acts as the transport plane. The separation enables more flexible scaling, because control capacity and bearer capacity can be dimensioned independently.

In operation, when a mobile subscriber attaches to the network, the MSC Server receives signalling messages from the radio network and interacts with the HLR and VLR to authenticate the subscriber and update location information. For a voice call, the MSC Server processes call control messages, selects routing, and instructs the media gateway to create or modify connections. During handover, the MSC Server coordinates the transfer of the call between radio cells and, if necessary, between media gateways. It maintains the logical state of the call and subscriber, while the media gateway maintains the physical or logical bearer resources. This division of labour is central to Release 4 and later circuit-switched architectures.

The MSC Server also supports interworking with packet-domain elements. In combined GSM/UMTS/GPRS networks, the MSC Server can interact with the SGSN for mobility and subscriber information, and it can support services that require coordination between circuit-switched and packet-switched domains. As networks evolved toward IMS and all-IP architectures, the MSC Server remained important for legacy voice and emergency services, but its role increasingly became one of interworking between traditional circuit-switched signalling and newer IP-based control planes. Understanding the MSC Server is therefore essential for studying the transition from monolithic MSCs to modern, decomposed mobile core networks.

Purpose & Motivation

The MSC Server was created to solve the architectural problem of monolithic circuit-switched switching in mobile networks. In earlier GSM networks, the MSC handled both signalling and media in the same physical node, which made scaling, transport flexibility, and migration to IP difficult. As UMTS and packet core networks matured, operators needed a way to separate control-plane functions from bearer-plane functions. This would allow signalling to be carried over IP, media to be aggregated in gateways, and network elements to be scaled independently according to control load and traffic capacity.

Release 4 introduced the MSC Server as part of a softswitch architecture that aligned mobile core networks with broader telecommunications trends. The motivation was to reduce cost and complexity by allowing IP transport, to support pooling of media gateways, and to enable gradual migration from TDM-based networks to packet-based networks. The MSC Server addresses the limitations of the traditional MSC by preserving the familiar circuit-switched service model while changing the internal architecture. It allows operators to continue supporting voice, mobility, and signalling services, but with a more modular and scalable implementation. This separation also made it easier to introduce new interfaces, improve resilience, and coordinate with other core network elements such as SGSNs and later IMS nodes.

What changed in its specifications

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

TS 23.002Rel-13 → Rel-14

Rel-14 added Control and User Plane Separation for EPC nodes, allowing S-GW, PDN-GW, and TDF to split into control and user plane entities, with TS 23.214 references.

Full comparison in TS 23.002 →
TS 23.205Rel-18 → Rel-19

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

Full comparison in TS 23.205 →

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

Rel-4 introduced

TS 23.205 first specifies the bearer-independent CS core network, defining the (G)MSC server's information flows with media gateways, including restoration, out-of-service and re-register procedures.

  • “The stage 2 shall cover the information flow between the GMSC server, MSC server and media gateways.” TS 23.205 v4.11.0
  • “If a (G)MSC server discovers that it wants to go out of service it starts a (G)MSC Server Out of Service procedure.” TS 23.205 v4.11.0
  • “the (G)MSC server can initiate the (G)MSC Server Ordered Re-register procedure.” TS 23.205 v4.11.0
Rel-5 specification text

TS 23.205 v5g0 specifies the MSC Server for the first time in this evidence, covering Iu signalling termination, MGW control over Mc, GERAN capability handling, and MGW recovery auditing.

  • “The MSC Server terminates the Iu control plane signalling and its transport bearer” TS 23.205 v5.16.0
  • “The MSC server shall take the indicated GERAN capabilities into account as well as the received MS capabilities when negotiating a service.” TS 23.205 v5.16.0
  • “the (G)MSC Server shall audit the termination state of all physical terminations (10.9)” TS 23.205 v5.16.0
Rel-6 specification text

The MSC Server gained new responsibilities: it may omit MGW selection and the Reserve Circuit procedure during service based handover, and it activates trace sessions toward the MGW.

  • “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 Signalling based activation the MSC server shall forward the Trace Session activation to GERAN with BSSAP signaling” TS 23.205 v6.9.0
Rel-8 specification text

The MSC Server gains new Rel-8 roles: IMS registration on behalf of ICS users over I2, session interworking with the CS-MGW, SRVCC session transfer handling, and enhanced SRNS relocation and CAT handling.

  • “If the flag is set to true, the MSC Server shall attempt the IMS registration using the I2 reference point.” TS 23.292 v8.8.0
  • “the MSC Server shall perform interworking between the I2 reference point and CS signalling” TS 23.292 v8.8.0
  • “the MSC Server enhanced for ICS shall subscribe to the registration event package described in TS 23.228 [2] on behalf of the ICS User” TS 23.292 v8.8.0
Rel-9 specification text

In Rel-9 the MSC Server gained new behaviour: it indicates media capabilities in registration, handles emergency sessions via existing procedures, performs TMSI reallocation and Update Location, and initiates session transfer with E-STN-SR.

  • “The MSC Server shall indicate in the registration the media capabilities that it supports (audio, or audio and video).” TS 23.292 v9.8.0
  • “For emergency session, the MSC Server initiates the Session Transfer by using the locally configured E-STN-SR and by including the equipment identifier.” TS 23.216 v9.9.0
  • “the MSC Server performs a MAP Update Location to the HSS/HLR.” TS 23.216 v9.9.0
Rel-10 specification text

MSC Server behaviour changed: it may attempt IMS registration via I2 only when the VPLMN flag is set and a roaming agreement is known, and it now handles Session Transfer failures.

  • “the MSC Server shall attempt the IMS registration using the I2 reference point.” TS 23.292 v10.6.0
  • “then MSC Server shall reject this PS To CS Request with a Reject cause pointing to either permanent or temporary” TS 23.216 v10.6.0
  • “The MSC Server indicates its capability to support MSC Server assisted mid-call feature during Access Transfer.” TS 23.237 v10.13.0
Rel-11 specification text

MSC Server behaviour changed: it adds User Location Info/UE Time Zone to INVITEs, handles vSRVCC video bearers and SRVCC priority mapping from ARP, and indicates IMS registration status and ATCF updates.

  • “The MSC Server adds the User Location Information (e.g. CGI or SAI) and/or UE Time Zone Information to the INVITE.” TS 23.292 v11.8.0
  • “If SCC AS indicates current active session is voice and video, the MSC Server requests UTRAN radio resources for BS30 bearer” TS 23.216 v11.11.0
  • “the MSC Server may indicate to the SCC AS the wish to be updated with the UE's IMS registration status” TS 23.237 v11.11.0
Rel-12 1 CR

MSC Server behaviour changed: it may now subscribe to IMS conference events after access transfer, initiates transfer for pre-alerting sessions, and has revised announcement handling during session transfer.

  • “The MSC Server enhanced for ICS may subscribe to the conference related events in IMS.” TS 23.292 v12.5.0
  • “The MSC Server initiates Access Transfer towards SCC AS for the alerting or pre-alerting session.” TS 23.237 v12.10.0
  • Enhanced MSC Server announcement during Session Transfer TS 23.237CR0483
Rel-13 specification text

The MSC Server must now inform the UE of conference events it receives from IMS, and sends them if the UE subscribes to the conference event package; the MAP Update Location after TMSI reallocation applies only to non-emergency sessions.

  • “when the MSC server receives the conference related events, it should inform the UE of the events.” TS 23.292 v13.4.0
  • “if the UE has a subscription for the conference event package, the MSC server should send the conference related events to UE.” TS 23.292 v13.4.0
Rel-14 specification text

MSC Server enhanced for ICS gains emergency-call handling via the new I6 reference point to the E-CSCF, including IMS emergency registration and eCall indication, plus optional Combined CS Access Authentication.

  • “MSC Server shall perform a registration for the support of emergency services (emergency registration) to IMS via I2.” TS 23.292 v14.2.0
  • “The I6 reference point shall be used to route emergency service control signalling between the MSC Server enhanced for ICS and the E-CSCF.” TS 23.292 v14.2.0
  • “an MSC Server that has been enhanced for ICS may support the Combined CS Access Authentication procedure as specified in Annex G.” TS 23.292 v14.2.0
Rel-15 specification text

MSC Server, if supported, is now required to withhold the PS-CS Response to the source MME/SGSN until it gets a positive or negative indication from IMS, or normal error handling such as timeout applies.

  • “MSC Server, if supported, shall be configured to not return a PS-CS Response to source MME/SGSN until it receives either a positive or negative indication” TS 23.216 v15.3.0
Rel-16 1 CR

Rel-16 adds 5G-SRVCC support in which the MSC Server enhanced for SRVCC is triggered by MME_SRVCC via Sv, handles emergency session transfer and location continuity, and reallocates TMSI with a MAP Update Location.

  • “This additional function is provided by the MSC Server (i.e., MSC Server enhanced for SRVCC) and the MME_SRVCC.” TS 23.216 v16.7.0
  • “MSC Server then initiates the IMS service continuity procedure with the locally configured E-STN-SR to the serving IMS.” TS 23.216 v16.7.0
  • MSC Server performing a TMSI reallocation and a MAP Update Location at 5G-SRVCC TS 23.216CR0371
Rel-17 1 CR

Rel-17 adds SRVCC handling in which the MSC Server signals 'Session Transfer leg establishment error' causes, and CRs add MSC Server Identity in Forward Relocation Response and Namf_Location_EventNotify.

  • “the MSC Server indicates an error cause pointing to either permanent or temporary "Session Transfer leg establishment error" in PS to CS complete notification message” TS 23.216 v17.1.0
  • “the MSC Server rejects a PS To CS Request with a Reject cause pointing to either permanent or temporary "Session Transfer leg establishment error"” TS 23.216 v17.1.0
  • MSC Server Identity in Forward Relocation Response during SRVCC handover TS 29.274CR2060

Defining Specifications

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

SpecificationTitleRelease
TS 23.002 vj00 3GPP System Architecture Overview Rel-19 read
TS 23.205 vj00 Bearer Independent CS Core Network Stage 2 Rel-19 read