I-MGCF

Incoming - Media Gateway Control Function

Core Network →
Introduced in Rel-7

I-MGCF is the IMS functional component that handles incoming call sessions from circuit-switched networks by performing protocol interworking and controlling a Media Gateway for media conversion.

Category
Core Network
Introduced
Rel-7
Where
Services
Specifications
4 specs
I-MGCF Description Purpose Related Classification Detected Changes Specifications

Description

The Incoming - Media Gateway Control Function (I-MGCF) is a critical network element within the 3GPP IP Multimedia Subsystem (IMS) architecture, specifically designed to handle session control for incoming calls originating from external circuit-switched (CS) networks, such as the Public Switched Telephone Network (PSTN) or legacy Public Land Mobile Networks (PLMN). It acts as a signaling gateway and controller at the border between the packet-switched IMS domain and the circuit-switched world. The primary role of the I-MGCF is to perform protocol interworking between the ISUP (ISDN User Part) or BICC (Bearer Independent Call Control) signaling used in CS networks and the SIP (Session Initiation Protocol) used within the IMS. Upon receiving an incoming ISUP/BICC call, the I-MGCF terminates the CS signaling, interprets the call setup information, and initiates a corresponding SIP session towards the IMS core. It controls an associated Media Gateway (MGW) via the H.248 (Megaco) protocol, instructing it to establish the necessary bearer connections and perform media conversion between the Time-Division Multiplexing (TDM) or circuit-switched bearer channels and the packet-based RTP/RTCP streams used in IMS. The I-MGCF interacts with other IMS entities like the Breakout Gateway Control Function (BGCF) for routing decisions and the Home Subscriber Server (HSS) for service authorization. Its operation is detailed across several 3GPP specifications, including TS 24.411 (ISUP to SIP mapping), TS 24.428 (guidelines), TS 24.528 (configuration), and TS 29.163 (interworking signaling). By fulfilling this role, the I-MGCF is a cornerstone for fixed-mobile convergence and the seamless integration of legacy telephony services with modern IP-based multimedia services.

Purpose & Motivation

The I-MGCF was created to solve a fundamental problem in network evolution: how to connect the vast, existing infrastructure of circuit-switched telephony networks to the new, all-IP IMS core. Without a dedicated interworking function, subscribers on legacy networks would be isolated from the advanced multimedia services offered by IMS, and vice-versa. The I-MGCF provides a standardized, scalable gateway that translates not just the media (via the MGW) but, more importantly, the call control signaling. This allows network operators to introduce IMS incrementally without disrupting existing PSTN/PLMN services. It addresses the limitations of previous, often proprietary, gateway solutions by defining a clear functional split between call control (I-MGCF) and media processing (MGW), following the IMS principle of separating control and user planes. Its creation in Release 7 was motivated by the need to solidify IMS as a mature architecture capable of supporting carrier-grade telephony services, including interconnection with other operators' networks. It enabled the vision of a unified core network that could serve both mobile and fixed access technologies, making services like Voice over LTE (VoLTE) and Rich Communication Services (RCS) interoperable with the global telephone network.

Classification

Part ofMGCF
Related approachesBGCF

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-7, normative work from Rel-15.

Rel-15 5 changes

In Release 15, updates for the I-MGCF function primarily involved reference updates for specific ISUP parameters, including the location parameter and the Q.850 location parameter. Additionally, a change was introduced concerning the interworking of the Connected subaddress Information Element carried within an ISUP CON message. The core procedures for the I-MGCF, such as mapping a 433 (Anonymity Disallowed) response to ISUP Cause Value 24 for call rejection, continued to follow the specifications of ES 283 003 [2].

  • Interwork of Connected subaddress IE carried in ISUP CON message TS 29.163CR1026
  • Reference Update for the ISUP location parameter TS 29.163CR1018
  • Reference Update for the ISUP location parameter TS 29.163CR1020
  • Reference Update for the ISUP location parameter TS 29.163CR1023
  • Reference Update for the ISUP Q.850 location parameter TS 29.163CR1044
Rel-16 3 changes

In Release 16, the I-MGCF function was enhanced with specific protocol mappings for the Anonymous Communication Rejection (ACR) service, defining the interworking between SIP responses and ISUP cause codes. This included the precise mapping of a SIP 433 (Anonymity Disallowed) response to the ISUP Cause Value "call rejected due to ACR supplementary service" in the Release (REL) message, and vice versa. Additionally, updates were made to the mapping of the SIP History-Info header field to the ISUP Original Called Number parameter to support the identification of diverted communications.

  • Reference Update for the ISUP Cause Location Parameter Draft TS 29.163CR1057
  • Reference Update for the ISUP Cause Location Parameter Draft TS 29.163CR1061
  • Mapping of History-Info header field to ISUP Original called number TS 29.163CR1069

Explore further

Broader topics and technologies where I-MGCF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 24.411 v1830 ACR and CB Service Protocol Specification Rel-8
TS 24.428 v1700 Common Basic Communication Procedures Rel-7
TS 24.528 v830 Common Basic Communication Procedures for IMS Services Rel-8
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19