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

Glossary term · Core Network

MGCF

Media Gateway Control Function

Core Network →

MGCF is the IMS network element that performs protocol conversion between SIP signaling and legacy circuit-switched signaling and controls the IMS-Media Gateway to enable calls between IMS and traditional telephony networks.

Introduced
Rel-5
Where
Services › IMS
Specifications
57 specs
Also in
Core Network, Management
MGCF Description Purpose What changed Family Detected Changes Specifications

Description

The Media Gateway Control Function (MGCF) is a specialized control-plane function within the IP Multimedia Subsystem (IMS) architecture. Its primary role is to act as a signaling gateway and controller for sessions that need to traverse between the packet-switched IMS domain (which uses SIP - Session Initiation Protocol) and the legacy circuit-switched (CS) telephony world (which uses protocols like ISUP - ISDN User Part or BICC - Bearer Independent Call Control). The MGCF is the IMS counterpart to the CS domain's Media Gateway Controller (MGC), but it is specifically designed to operate within the SIP-centric IMS framework.

Architecturally, the MGCF sits at the boundary between the IMS core and external CS networks like the Public Switched Telephone Network (PSTN) or legacy PLMN. It has several key interfaces. Towards the IMS core, it communicates with the CSCF (Call Session Control Function) using the SIP-based Mg interface. When an IMS user calls a PSTN number, the SIP INVITE is routed to the MGCF. The MGCF then performs protocol translation, converting the SIP signaling into the appropriate ISUP or BICC message. Conversely, for an incoming call from the PSTN, it receives ISUP/BICC signaling and translates it into a SIP INVITE for routing into the IMS. To manage the actual media path, the MGCF controls an IMS-Media Gateway (IMS-MGW) using the H.248 protocol over the Mn interface. It instructs the IMS-MGW to perform necessary media interworking functions, such as transcoding between a packet voice codec (like AMR-WB used in IMS) and a PCM TDM circuit from the PSTN, or playing announcements and tones.

In operation, the MGCF's workflow involves several steps. It performs address analysis and translation (e.g., converting a PSTN E.164 number into a SIP URI for routing within IMS, or vice-versa). It manages the call state for the interworking portion of the session, ensuring signaling coherence between the two disparate domains. The MGCF also interacts with other IMS functions like the Breakout Gateway Control Function (BGCF) for selecting the appropriate network to break out to the CS domain. Its design is crucial for ensuring seamless service continuity, supporting not only basic voice calls but also supplementary services like call forwarding, caller ID, and call waiting across the network boundary.

Purpose & Motivation

The MGCF was created to solve a fundamental challenge in the transition to all-IP networks: how to maintain seamless interoperability between the new, SIP-based IMS and the vast, entrenched infrastructure of the global circuit-switched telephone network. Without the MGCF, IMS would be an isolated 'island' unable to communicate with the billions of existing landline and mobile phones. Its development was motivated by the 3GPP's vision for IMS as the unifying service delivery platform for multimedia services, which necessitated a robust and standardized interworking function.

Historically, as IMS was defined from 3GPP Release 5 onwards, the MGCF addressed the limitations of earlier, proprietary gateway solutions. It provided a standardized, scalable way to handle the complex signaling and media mapping required for inter-domain calls. This allowed network operators to deploy IMS for new services (like VoLTE and RCS) while guaranteeing backward compatibility, protecting their existing investments, and ensuring a smooth migration path for subscribers. The MGCF, together with the IMS-MGW, forms the PSTN/CS gateway subsystem that is essential for the commercial success of any IMS deployment.

What changed in its specifications

The latest release-to-release comparison of specifications that define MGCF. 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.218Rel-18 → Rel-19

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

Full comparison in TS 23.218 →

Technology family

IMS functions · Services › IMS

  1. R99 OSA-SCS
  2. Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
  3. Rel-6 IBCF, IMS-ALG, TrGW
  4. Rel-7 E-CSCF, IMS-AGW
  5. Rel-8 MRB, SCC AS
  6. Rel-9 EATF
  7. Rel-10 ATCF, ATGW
  • MGCF used together with IM-MGW
    “When referring specifically to the IP Multimedia CN Subsystem entity, the term IMS-MGW is used.” TS 23.002
  • MGCF used together with BGCF
    “If the routing determination is such that the breakout is to occur in the same network in which the BGCF is located, then the BGCF shall select a MGCF that will be responsible for the interworking with the PSTN/CS Domain.” TS 23.228

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 14 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-5 introduced

MGCF is specified for the first time in Rel-5, with a UA role, SIP-to-circuit-switched call handling, H.248 control of the MGW, and session flows with the PSTN.

  • “The MGCF shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.5” TS 24.229 v5.26.0
  • “When the MGCF receives an indication of an incoming call from a circuit-switched network, the MGCF shall:” TS 24.229 v5.26.0
  • “The MGCF uses H.248 [19] to control a Media Gateway, and communicates with the SS7 network.” TS 23.228 v5.15.0
Rel-6 specification text

TS 29.332 first appears in Rel-6, specifying the Mn interface and H.248 profile between the MGCF and IM-MGW; 24.229 and 23.228 also add MGCF precondition, charging and forking behaviour.

  • “The present document describes the protocol to be used on the Media Gateway Control Function (MGCF) – IM Media Gateway (IM-MGW) interface.” TS 29.332 v6.14.0
  • “The MGCF sends an Add.req command with the following information.” TS 29.332 v6.14.0
  • “The MGCF shall send an UPDATE request when the following conditions are fulfilled:” TS 24.229 v6.30.0
Rel-7 specification text

MGCF behaviour in SIP signalling was extended: it must use a GRUU as contact address, handle requests addressed to its GRUUs, and set inactive mode in the initial SDP offer when local preconditions are not met.

  • “The MGCF shall use a GRUU referring to itself (as specified in RFC 5627 [93]) when inserting a contact address” TS 24.229 v7.34.0
  • “The MGCF shall handle requests addressed to its currently valid GRUUs when received outside of the dialog in which the GRUU was provided.” TS 24.229 v7.34.0
  • “then the MGCF shall set the inactive mode (by including an attribute "a=inactive") in an initial SDP offer” TS 24.229 v7.34.0
Rel-8 specification text

In Rel-8 the MGCF gained new responsibilities: retrieving number portability data over legacy interfaces, correcting hanging contexts and terminations, and handling H.245 media adaptation and MONA/SPC procedures on the Mn interface.

  • “Alternatively, per operator policy, the MGCF may support legacy interfaces to retrieve number portability data.” TS 23.228 v8.12.0
  • “The MGCF is in charge of correcting any detected mismatch, by substracting hanging terminations or clearing hanging contexts” TS 29.332 v8.12.0
  • “The MGCF is in charge of sending the corresponding H.245 message to the CS side to request for the media adaption.” TS 29.332 v8.12.0
Rel-9 specification text

MGCF behaviour in TS 24.229 gained new requirements since Rel-7, including NP data retrieval, preferred circuit carrier access, Resource-Priority handling, overlap signalling and 199 response handling.

Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.

  • “The MGCF may support retrieval of NP data, subject to local policy.” TS 24.229 v9.31.0
  • “Upon receiving a 199 (Early Dialog Terminated) provisional response to an established early dialog the MGCF shall release resources specifically related to that early dialog.” TS 24.229 v9.31.0
  • “If resource priority in accordance with RFC 4412 [116] is required for a dialog, then the MGCF shall include the Resource-Priority header field” TS 24.229 v9.31.0
Rel-10 specification text

MGCF gained new requirements in Rel-10, including ECN negotiation and instructing the MGW to apply ECN procedures, plus OMR support and UA procedures per TS 29.079.

  • “If the MGCF receives a SDP offer containing ECN attribute "a=ecn-capable-rtp" as specified in RFC 6679 [188]” TS 24.229 v10.29.0
  • “then the MGCF will instruct the MGW to apply ECN procedures.” TS 24.229 v10.29.0
  • “If the MGCF supports OMR it shall also perform the UA procedures described in 3GPP TS 29.079 [11D].” TS 24.229 v10.29.0
Rel-11 specification text

MGCF behaviour was extended: in Rel-11 it conveys location information from the E-CSCF, sets the "np" parameter and handles FAX/T.38 terminations, and it also appears in transit/roaming routing as an egress point.

  • “The MGCF can translate the location information if included in INVITE (i.e. both the geographic” TS 24.229 v11.31.0
  • “To configure FAX terminations, the MGCF shall signal "udptl" or " tcp" in an SDP m-line” TS 29.332 v11.3.0
  • “selecting appropriate egress point (e.g., MGCF for CS/PSTN, IBCF to other IMS networks, or I-CSCF for termination in own network)” TS 23.228 v11.11.0
Rel-12 specification text

MGCF procedures in TS 24.229 changed: P-Charging-Vector now carries icid-value in MGCF-generated responses, and the MGCF may add a Priority header with "psap-callback" for verified PSAP callbacks.

  • “The MGCF shall set the type 2 "term-ioi" header field parameter to a value that identifies the network in which the MGCF resides” TS 24.229 v12.27.0
  • “If the MGCF has verified that the request is for a PSAP callback, then depending on local policy it may include a Priority header field” TS 24.229 v12.27.0
  • “procedures related to the handling of the IP-CAN bearer rejection, modification or release are not applicable to the MGCF.” TS 24.229 v12.27.0
Rel-13 specification text

TS 24.229 added MGCF requirements for P-Charging-Vector handling in subsequent requests and responses, precondition support during session modification, and 503/500 responses on codec unavailability.

  • “add a P-Charging-Vector header field with the "icid-value" header field parameter set to the value populated in the initial request for the dialog” TS 24.229 v13.23.0
  • “the MGCF shall indicate support of the precondition mechanism during a session modification” TS 24.229 v13.23.0
  • “send 503 (Service Unavailable) response if the type of codec was acceptable but none were available” TS 24.229 v13.23.0
Rel-14 1 CR

MGCF procedures in TS 24.229 changed in Rel-14: added logging of SIP requests with "logme", Response-Source insertion in failure responses, and revised P-Charging-Vector handling including fe-identifier.

  • “The MGCF shall log all SIP requests and responses that contain a "logme" header field parameter in the SIP Session-ID header field” TS 24.229 v14.21.0
  • “the MGCF shall include the stored "fe-identifier" header field parameter in the P-Charging-Vector header field” TS 24.229 v14.21.0
  • Charging Completeness: Procedures at the MGCF TS 24.229CR5876
Rel-15 specification text

MGCF gains the ability to add attestation information to outgoing SIP INVITE requests based on trunk identity or other sources, and the Attestation-Info and Origination-Id header field extensions now apply to it.

  • “If configured through policies, the MGCF adds to the SIP INVITE attestation information based on the trunk identity or other sources of the request.” TS 23.228 v15.5.0
  • “IF A.4/121 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - the Attestation-Info header field extension, MGCF, AS, IBCF.” TS 24.229 v15.20.0
Rel-17 specification text

MGCF procedures were extended so that, if priority is supported, it gives priority to transactions or dialogs and adjusts treatment per the latest authorized Resource-Priority header field or backwards indication value.

  • “the MGCF shall give priority over other transactions or dialogs. This allows special treatment of such transactions or dialogs.” TS 24.229 v17.19.0
  • “the MGCF shall adjust the priority treatment of transactions or dialogs according to the most recently received authorized Resource-Priority header field” TS 24.229 v17.19.0
Rel-18 specification text

MGCF is now required to ignore data channel media descriptors in received SIP request bodies and to set their media port to zero in the SIP response sent to the IMS network.

  • “the MGCF shall ignore them, and the MGCF shall set the data channel media port number in the data channel media descriptors as zero” TS 24.229 v18.11.0
Rel-19 specification text

The 24.229 profile table condition for transferring an updated MSD for PSAP callback was revised, covering MGCF among the roles, so support depends on A.4/127 rather than being optional.

  • “IF (A.3/1 AND A.4/127) OR A.3/2A OR A.3/6 OR A.3/7 OR A.3/9 THEN o ELSE IF (A.3/1 AND NOT A.4/127) THEN x ELSE n/a” TS 24.229 v19.7.0
  • “IF A.3/2A OR A.3/6 OR A.3/7 OR A.3/9 THEN o ELSE IF A.3/1 THEN x ELSE n/a” TS 24.229 v19.7.0

Defining Specifications

3GPP specifications that define or reference MGCF, 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
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.231 vj00 SIP-I based CS core network stage 2 Rel-19 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.278 vj00 CAMEL for IMS Stage 2 Specification Rel-19 read
TS 23.417 v700 IMS Core Component for NGN Architecture Rel-7 read
TS 23.517 v800 IMS Core Architecture for TISPAN NGN Rel-8 read
TS 23.806 v700 Voice Call Continuity between CS and IMS Rel-7 read
TS 23.815 v500 IMS Charging Implications Rel-5 read
TS 23.849 vb00 IMS Roaming Resource Control Study Rel-11 read
TS 24.147 vj00 IMS Conferencing Protocol Details Rel-19 read
TS 24.228 v590 IP Multimedia Call Control Signaling Flows Rel-5 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.405 v700 Conference Service Protocol Description Rel-7 read
TS 24.407 v830 OIP and OIR Simulation Services Protocol Rel-8 read
TS 24.411 v830 3GPP TS 24411 v830: Anonymous Communication Rejection and Communication Barring Rel-8 read
TS 24.416 v700 Malicious Call Identification Service Rel-7 read
TS 24.428 v720 Common Basic Communication Procedures Rel-7 read
TS 24.429 v700 Explicit Communication Transfer (ECT) Service Specification Rel-7 read
TS 24.454 v840 Closed User Group (CUG) Protocol Specification Rel-8 read
TS 24.504 v8m0 Communication Diversion (CDIV) Protocol Specification Rel-8 read
TS 24.505 v810 Protocol Description of the Conference Service Rel-8 read
TS 24.508 v820 TIP and TIR Service Protocol Description Rel-8 read
TS 24.516 v830 MCID Protocol Specification for NGN Rel-8 read
TS 24.524 vj00 Hosted Enterprise Services Architecture Rel-19 read
TS 24.528 v830 Common Basic Communication Procedures for IMS Services Rel-8 read
TS 24.529 v820 Explicit Communication Transfer (ECT) Simulation Service Rel-8 read
TS 24.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19 read
TS 24.605 vj00 3GPP CONF Service Protocol Specification Rel-19 read
TS 24.607 vj10 OIP and OIR Supplementary Services Stage 3 Rel-19 read
TS 24.616 vj00 Malicious Call Identification (MCID) Protocol Rel-19 read
TS 24.628 vj00 Common Basic Communication Procedures in IMS Rel-19 read
TS 24.629 vj00 Explicit Communication Transfer (ECT) Protocol Rel-19 read
TS 24.819 v700 IMS Services via Fixed Broadband Access Rel-7 read
TR 24.930 vj00 IMS Session Setup Signalling Flows Rel-19 read
TS 26.114 vk11 IMS Multimedia Telephony Client Rel-20 read
TR 26.944 vj00 QoE, ESQoS and SQoS metrics for 3G multimedia services Rel-19 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 28.705 vj00 IMS NRM IRP Information Service Rel-19 read
TS 29.332 vj00 MGCF-IM-MGW Interface Protocol (Mn) Rel-19 read
TS 29.412 v810 Control Procedures for Trunk Gateways in NGN Networks Rel-8 read
TS 29.424 v801 H.248 Profile for Trunking Media Gateways Rel-8 read
TS 29.863 v820 IMS-CS Multimedia Interworking Feasibility Study Rel-8 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.260 vk10 IMS Charging Management Rel-20 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19 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.850 ve00 IMS Charging Correlation Methods Study Rel-14 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read