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

Glossary term · Core Network

CS-MGW

Circuit Switched Media Gateway

Core Network →

CS-MGW is a network element that performs media conversion and transcoding between circuit-switched networks like PSTN and packet-switched IP networks to enable voice and CS data services over IP transport.

Introduced
Rel-4
Where
Core Network › Evolved Packet Core
Specifications
3 specs
CS-MGW Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Circuit Switched Media Gateway (CS-MGW) is a critical functional entity within the 3GPP Core Network, specifically in the Circuit Switched (CS) domain. It acts as a bridge between traditional Time Division Multiplexing (TDM) based circuit-switched networks, such as the Public Switched Telephone Network (PSTN) and Integrated Services Digital Network (ISDN), and packet-switched networks based on Internet Protocol (IP) or Asynchronous Transfer Mode (ATM). Architecturally, the CS-MGW is controlled by the Media Gateway Control Function (MGCF) via the H.248 (Megaco) protocol, which is standardized in 3GPP as the Mn interface. The MGCF provides the call control and signaling intelligence, while the CS-MGW executes the media plane operations as commanded. This separation of control and user planes is a fundamental principle of the Gateway Control architecture adopted by 3GPP.

From a functional perspective, the CS-MGW's primary role is media processing. It terminates bearer channels from the CS network (e.g., E1/T1 trunks with TDM timeslots) and media streams from the PS network (e.g., Real-time Transport Protocol (RTP) streams over IP). Its core operations include media conversion, transcoding, and bearer processing. Media conversion involves adapting the transport format, for instance, converting a 64 kbps PCM voice channel from a TDM circuit into an RTP/UDP/IP packet stream for transmission over an IP network, and vice-versa. Transcoding is the process of converting between different speech codecs, which is essential when the codec used in the mobile network (e.g., AMR) differs from the codec used in the fixed network (e.g., G.711). The CS-MGW may also perform echo cancellation, tone generation (e.g., dial tone, busy tone), and conferencing functions for multiparty calls.

The CS-MGW interfaces with several other network elements. On the CS side, it connects to the legacy circuit-switched network via TDM interfaces. Within the 3GPP IP Multimedia Subsystem (IMS) or the CS core, it connects to the MGCF for control (Mn interface) and to other media gateways or endpoints for user plane traffic. In the context of Mobile Switching Centre (MSC) server-based architecture, introduced in 3GPP Release 4, the CS-MGW is the user plane termination point that is controlled by an MSC Server. This allows the traditional monolithic MSC to be split into a call control server (MSC Server) and a media processing entity (CS-MGW), enabling more flexible and scalable network deployments. The CS-MGW is therefore a key enabler for network modernization, allowing operators to migrate their voice infrastructure to all-IP backbones while maintaining interoperability with legacy circuit-switched services and networks.

Purpose & Motivation

The CS-MGW was created to address the fundamental challenge of network convergence between legacy circuit-switched telephony and emerging packet-switched networks. Prior to its introduction, voice services were exclusively delivered over dedicated TDM circuits, which are efficient for constant-bit-rate voice but inflexible and costly for data transport. The rise of IP as a universal networking protocol presented an opportunity to carry voice as packetized data, offering statistical multiplexing gains, simplified infrastructure, and the potential for integrated multimedia services. However, a direct bridge was needed to interconnect these two disparate technological worlds without disrupting existing services.

The primary problem the CS-MGW solves is the interworking of bearer traffic and basic call features between TDM and IP/ATM domains. It allows mobile network operators to modernize their core networks by deploying IP-based transport and control (e.g., using MSC Servers) while still connecting to the global PSTN/ISDN, which remained predominantly TDM-based for many years. This transition was economically motivated, as IP networks are generally cheaper to build, maintain, and scale. The CS-MGW, under the control of an MGCF or MSC Server, handles the complex real-time media processing required for this interworking, insulating the call control logic from the specifics of the underlying bearer technology. Its creation was a critical step in the evolution towards all-IP core networks and was a foundational component for the later introduction of the IMS for multimedia services.

What changed in its specifications

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

TS 23.221Rel-18 → Rel-19

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

Full comparison in TS 23.221 →
TS 23.236Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.236: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 23.236 →

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 8 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

The CS-MGW is specified for the first time, with general principles for its resource use, anchoring at handover, and transcoder placement in the core network.

  • “The first CS-MGW involved in a call will become the Anchor CS-MGW for this call during and after handover” TS 23.221 v4.2.0
  • “it shall not be necessary to have the CS-MGW co-located with the MSC Server;” TS 23.221 v4.2.0
  • “The trancoders are located in the core network. They may be located in the CS-MGW at the border to the RAN” TS 23.221 v4.2.0
Rel-8 specification text

TS 29.292 first specifies the CS-MGW's role in interworking between the IM CN subsystem and the CS domain, including transcoding, Mb/IuCS interworking and MSC Server-CS-MGW procedures.

  • “The CS-MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination.” TS 29.292 v8.11.0
  • “the CS-MGW shall interwork procedures between the IuCS and Mb reference points as specified in 3GPP TS 29.414 [18] clause 7.4.” TS 29.292 v8.11.0
  • “The CS-MGW shall reply to the MSC Server with the selected local speech codec(s) and the selected local IP address and UDP port(s).” TS 29.292 v8.11.0
Rel-10 specification text

CS-MGW and MSC Server may act as ECN endpoints for Multimedia Telephony, with the ECN procedures of TS 29.163 applying, and the MSC server instructs through-connection for early media from the IMS side.

  • “may then act as an ECN endpoint to enable ECN with a local ECN-capable terminal within a local network” TS 29.292 v10.9.0
  • “The ECN procedures described in TS 29.163 [46], clause 9.2.11, for MGCF and IM-MGW are then applicable for MSC Server and the CS-MGW.” TS 29.292 v10.9.0
Rel-11 specification text

CS-MGW (with MSC Server) gains support for priority treatment of MPS calls/sessions, applying the MPS procedures from TS 29.163 clause 9.4.

  • “An MSC Server and a CS-MGW may support the priority treatment of a call/session identified as an MPS call/session.” TS 29.292 v11.9.0
  • “The MPS procedures described in TS 29.163 [46], clause 9.4, for MGCF and IM-MGW are then applicable for MSC Server and the CS-MGW.” TS 29.292 v11.9.0
Rel-12 specification text

For TS 29.292, the MSC Server and CS-MGW may now support ICE (at least ICE lite) and EVS transcoding, and the MSC Server must use revised Reserve/Configure RTP Connection Point procedures with the CS-MGW.

  • “if ICE is supported, the MSC Server and the CS-MGW shall at least support ICE lite as specified in IETF RFC 5245” TS 29.292 v12.7.0
  • “The MSC Server and the CS-MGW may support transcoding to and from the EVS speech codec.” TS 29.292 v12.7.0
Rel-14 specification text

CS-MGW gained new information elements and procedures for ICE (lite and full connectivity checks), ECN handling, priority treatment, and ECN failure and ICE check result notifications on the MSC Server interface.

  • “This information element requests the CS-MGW to perform ICE connectivity check as defined by IETF RFC 5245 [60]. It is only applicable for full ICE.” TS 29.292 v14.8.0
  • “This information element requests the CS-MGW to apply ECN procedures.” TS 29.292 v14.8.0
  • “This information element requests the CS-MGW to apply priority treatment for the terminations and bearer connections in the specified context.” TS 29.292 v14.8.0
Rel-17 specification text

The ICE functionality that MSC Server and CS-MGW may support now references IETF RFC 8445 and RFC 8839 instead of the obsolete RFC 5245.

  • “An MSC Server and a CS-MGW may support ICE functionality as specified in IETF RFC 8445 [69] and IETF RFC 8839 [70]” TS 29.292 v17.0.0
  • “An MSC Server and a CS-MGW may support ICE functionality as specified in IETF RFC 5245 [60]” TS 29.292 v17.0.0
Rel-18 specification text

The MSC Server and CS-MGW may now support transcoding to and from the IVAS speech and audio codec, following the requirements in clause 9.2.13.4 of TS 29.163.

  • “The MSC Server and the CS-MGW may support transcoding to and from the IVAS speech and audio codec.” TS 29.292 v18.1.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.236 vj00 Intra Domain Connection of RAN Nodes to Multiple CN Nodes Rel-19 read
TS 29.292 vj00 IMS Centralized Services (ICS) Interworking Rel-19 read