InterWorking Function

Description

The InterWorking Function (IWF) is a conceptual and functional entity within 3GPP architectures whose primary role is to ensure interoperability between disparate network systems. It is not a single, monolithic node but a logical function that can be implemented in various physical network elements depending on the specific interworking scenario. The IWF performs necessary adaptations, including protocol conversion, message mapping, signal translation, and media transcoding, to bridge technological gaps. It essentially hides the differences between the interconnected networks, allowing them to exchange information and deliver services as if they were part of a homogeneous system.

Architecturally, an IWF sits at the boundary between two network domains. For example, in early circuit-switched core networks, an IWF was used to interwork between GSM's MAP signaling and ISDN's DSS1 signaling. In the context of IP Multimedia Subsystem (IMS), an IWF can facilitate interworking between SIP-based IMS networks and legacy circuit-switched telephony networks, handling the conversion between SIP messages and ISUP/BICC signaling protocols. Another key instance is the Interworking IMS (IW IMS) function defined for service continuity between IMS and non-IMS domains. The IWF contains the necessary application logic and state machines to interpret incoming messages from one domain, map parameters and information elements to their equivalents in the target domain, and generate the corresponding outgoing messages.

From an implementation perspective, the IWF function may be integrated into existing nodes like a Media Gateway (MGW) for media plane interworking or a Media Gateway Control Function (MGCF) for signaling interworking in IMS. It manages critical tasks such as address translation, codec negotiation and adaptation, bearer establishment coordination, and supplementary service mapping. Its operation is defined in numerous 3GPP specifications covering areas like core network signaling, IMS, emergency services, and messaging. The IWF is a fundamental enabler for service continuity, roaming, and the phased migration from legacy networks to new 3GPP systems, ensuring that subscribers can communicate and access services across technological generations.

Purpose & Motivation

The IWF exists to solve the fundamental problem of heterogeneity in telecommunications. Networks evolve through generations (2G, 3G, 4G, 5G) and coexist with other fixed and wireless technologies. Without interworking functions, these networks would be isolated islands, unable to communicate or share services. The IWF was motivated by the need for backward compatibility during network transitions and for enabling seamless service delivery across multi-vendor, multi-technology environments.

Historically, one of the first major needs for an IWF arose with the introduction of GSM, which required interconnection with the existing global PSTN/ISDN fixed networks. This required translating between GSM-specific MAP signaling and the ISUP signaling used in fixed networks. As networks evolved to packet-switched cores and IMS, new interworking challenges emerged, such as connecting SIP-based VoIP services to the legacy circuit-switched voice network. The IWF addresses the limitations of previous siloed approaches by providing a standardized point of adaptation, defined in 3GPP specs, which allows for predictable and interoperable connectivity.

Furthermore, the IWF concept enables convergence and service innovation. It allows new network capabilities (like rich communication services in IMS) to be made available to users on legacy networks, and vice-versa. It is crucial for emergency calls, lawful interception, and roaming scenarios where a user on one network type must access services in another. By abstracting the complexity of protocol differences, the IWF reduces integration costs for operators and ensures a consistent user experience, which was a key commercial and technical driver for its pervasive use across 3GPP standards.

Key Features

• Performs protocol conversion and message mapping between different network domains (e.g., MAP to ISUP, SIP to ISUP)
• Enables service continuity and interoperability across heterogeneous networks (3GPP, non-3GPP, legacy)
• Can be implemented as a standalone node or integrated into existing network functions (e.g., MGCF, SGSN)
• Handles both control plane (signaling) and user plane (media) adaptation where required
• Manages address translation, codec negotiation, and bearer coordination for end-to-end service setup
• Provides a standardized point for regulatory feature interworking (e.g., emergency services, lawful intercept)

Evolution Across Releases

Defining Specifications