Signalling Gateway Function

Description

The Signalling Gateway Function (SGF) operates as a critical interworking node within the IP Multimedia Subsystem (IMS) and 5G Core (5GC) architecture. Its primary role is to translate and relay signalling messages between the IP-based signalling transport (e.g., using SIGTRAN protocols like SCTP/IP) used in modern networks and the traditional Time-Division Multiplexing (TDM)-based Signalling System No. 7 (SS7) used in legacy circuit-switched networks. Architecturally, the SGF is defined as a functional entity that can be implemented as a standalone network element or integrated with other control plane functions. It acts as a termination point for SS7 signalling links (e.g., using MTP2/MTP3) from the legacy circuit-switched network and maps these messages onto appropriate IP transport streams towards the Media Gateway Controller Function (MGCF) or other IMS/5GC entities.

Architecturally, the SGF is defined as a standalone logical function, though it can be co-located with other network functions like the MGCF or the Session Border Controller (SBC). It handles the lower-layer protocol conversion (layers 1-3 of the OSI model) for signalling. For instance, it converts MTP2/MTP3 signalling from an SS7 link into M3UA (MTP3 User Adaptation) over SCTP/IP, which is then conveyed to the MGCF. The MGCF handles the higher-layer application protocol interworking (e.g., between ISUP and SIP). This separation of concerns allows for scalable and flexible network deployments.

In a 5G context, the SGF's role extends to supporting interworking with the 5G Core Network for services like voice call continuity. While 5GC primarily uses HTTP/2-based service-based interfaces, legacy interworking for voice services still requires SS7 connectivity for functions like roaming and interconnection with Public Switched Telephone Networks (PSTN). The SGF enables this by providing the necessary signalling gateway capability, ensuring that 5G subscribers can make and receive calls to/from legacy networks. Its operation is specified in detail across multiple 3GPP technical specifications, defining its interfaces, procedures, and protocol mappings to ensure interoperability between different vendor implementations and network generations.

Purpose & Motivation

The SGF was introduced to address a fundamental challenge in network evolution: the coexistence of new, all-IP network architectures (like IMS and 5GC) with the vast, entrenched infrastructure of legacy circuit-switched networks (2G/3G/PSTN). These legacy networks use the SS7 signalling protocol suite, which is fundamentally different from the IP-based protocols (like SIP and Diameter) used in IMS and 5G. Direct communication between these disparate signalling domains is impossible without a gateway.

Prior to the standardization of functions like the SGF, operators relied on proprietary gateway solutions or integrated signalling capabilities within media gateways. This lack of standardization led to interoperability issues, increased complexity, and higher costs for multi-vendor network deployments. The SGF, as a standardized 3GPP function, provides a clear architectural separation between the signalling gateway and the media gateway controller (MGCF). This separation promotes network flexibility, allowing operators to scale and upgrade these functions independently based on traffic patterns (signalling vs. media).

Its creation was motivated by the long transition period from circuit-switched to packet-switched voice and multimedia services. Operators could not instantly replace their SS7-based networks; they needed a graceful migration path. The SGF enables this by allowing the core signalling intelligence (in the MGCF/IMS) to be deployed on modern IP platforms while still connecting to the global SS7/PSTN network for essential services like call routing, roaming, and number portability. It is a cornerstone for ensuring service continuity and a successful transition to VoLTE and VoNR.

Key Features

• Protocol conversion between SS7 MTP2/MTP3 layers and SIGTRAN adaptation layers (e.g., M3UA) over IP
• Termination of physical SS7 signalling links (E1/T1 timeslots) or IP-based SS7 connections
• Relay of signalling messages between legacy SS7 networks and IP-based core network functions like the MGCF
• Support for essential SS7 signalling procedures required for call setup and teardown with the PSTN
• Scalable architecture allowing standalone or co-located deployment with other network functions
• Standardized interfaces and procedures as per 3GPP specifications to ensure multi-vendor interoperability

Evolution Across Releases

Defining Specifications