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.
What changed in its specifications
The latest release-to-release comparison of specifications that define IWF. Each summary describes the whole specification, not only this term.
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 →Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.
Full comparison in TS 23.228 →Technology family
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- 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 sourcesDocumented changes in 13 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.
Introduced in Phase 1 (release dating of the term; no individual change cited).
TS 29.305 first specifies the IWF in Rel-8, mapping Diameter and MAP messages between MME/SGSN and HSS using address and session mapping tables for AIR, ULR, CLR and PUR procedures.
- “When the IWF receives a Diameter message from a Diameter node, it shall map the Diameter message to a MAP message.” TS 29.305 v8.5.0
- “The IWF shall maintain a mapping table (address mapping table) for the assignment relationship.” TS 29.305 v8.5.0
- “The IWF receives an ULR message from the MME, SGSN or combined MME/SGSN.” TS 29.305 v8.5.0
IWF procedures were extended to handle MAP ProvideSubscriberInfo alongside InsertSubscriberData, with new mapping rules between MAP ProvideSubscriberInfo and Diameter IDR/IDA.
- “The IWF receives an (stand alone) InsertSubscriberData or ProvideSubscriberInfo message from the HSS.” TS 29.305 v9.3.0
- “the IWF shall open a MAP dialogue in application context version 3 and populate sub-parameters of ProvideSubscriberInfoArg as described below” TS 29.305 v9.3.0
The IWF's ULR and NOR construction conditions were extended to handle skipSubscriberDataUpdate and ue-srvcc-Capability parameters, adding UE SRVCC capability support to the IWF.
- “or with a skipSubscriberDataUpdate parameter within add-info or with ue-srvcc-Capability parameter but without usedRAT-Type parameter” TS 29.305 v10.4.0
- UE SRVCC Capability Support for IWF TS 29.305CR0018
The IWF gained new SMS interworking procedures between SGd Diameter and MAP, including MO/MT-ForwardSM message handling, routing by SC/MME E.164 address and AVP/parameter mapping.
- “For MO Forward short messages requests, the IWF shall use the SC address (E.164 number) received over SGd for routing over MAP.” TS 29.305 v11.8.0
- “The IWF receives a MT-ForwardSM MAP v3 message from the SMS-GMSC or from the SMS Router.” TS 29.305 v11.8.0
- Add vSRVCC updates to the IWF function TS 29.305CR0021
The IWF interworking scenarios between Diameter SGd/Gdd and MAP were extended from MME-only SGd to MME/SGSN/IP-SM-GW over SGd/Gdd, including new IP-SM-GW support for IMS UE without MSISDN.
- “This interworking scenario also applies between an IP/SM/GW supporting SGd/Gdd interface based on Diameter and central SMS functions” TS 29.305 v12.3.0
- “the IWF shall rely on the E.164 number of the MME/SGSN used to route the MAP message towards the IWF” TS 29.305 v12.3.0
- “A.2 IWF related to the SGd/Gdd interfaces between MME/SGSN and central SMS functions” TS 29.305 v12.3.0
The IWF is specified for the first time as the function providing centralised interworking, identity mapping and protocol translation between MCPTT/MCData systems and LMR systems, with its own security handling.
- “The IWF provides centralised support for interworking between an MCPTT or MCData system and an LMR system.” TS 23.283 v15.4.0
- “The IWF supports any necessary protocol translation and identity mapping between the MC systems and the IWF.” TS 23.283 v15.4.0
- Addition of IWF and IWF-2 TS 23.282CR0080
IWF behaviour was extended in Rel-16: group call and join requests carry implicit floor request and location information, and the IWF supports pre-configured group regroup and broadcast procedures.
- “If floor control is requested by the calling LMR user, an indication of implicit floor request is included.” TS 23.283 v16.8.0
- “The IWF initiates the group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1.” TS 23.283 v16.8.0
- Add Location information to IWF floor request and IWF floor taken messages TS 23.283CR0022
The IWF gained functional alias support (activate, de-activate, query, take over) and new procedures for obtaining MCPTT user profile and group information, plus conference event package handling in the IWF.
- “LMR users homed in the IWF shall have the ability to enable, apply, or disable a functional alias in the MC system” TS 23.283 v17.4.0
- “the IWF shall obtain the MCPTT user profile described in 3GPP TS 24.484 [34].” TS 29.379 v17.5.0
- Add Conference Event Package to IWF TS 29.379CR0010
The IWF gained location information interworking: new IWF-4 reference point to the LMS and IWF location request, provision and subscription procedures with identity translation between MC and LMR systems.
- “The IWF‑4 reference point, which exists between the IWF and the LMS, provides location information exchange between an LMR system and the MC system.” TS 23.283 v18.4.0
- “The IWF in the LMR system can request an MC service user's location information, which is in the MC system, at any time” TS 23.283 v18.4.0
- “The IWF provides interworking to obtain location information for the LMR user associated with the MC service identity it receives.” TS 23.283 v18.4.0
The IWF gained new ad hoc group call procedures and information flows, private call functional alias resolution, call end handling and broadcast group call signalling, while the end-to-end security messaging became MCData-only.
- “10.17.2.2 IWF ad hoc group call request (MCPTT server – IWF and IWF - MCPTT server)” TS 23.283 v19.5.0
- “the IWF abandons the first MCPTT private call request in step 1 and sends a new MCPTT private call request towards the resolved MCPTT ID.” TS 23.283 v19.5.0
- Correction to IWF participating role procedures for Adhoc group call TS 29.379CR0033
The IWF gains new ad hoc group emergency alert procedures and information flows with the MCPTT server, initiating alerts on behalf of LMR users, plus new congestion handling in the controlling role.
- “The IWF initiates the ad hoc group emergency alert on behalf of the LMR system by sending an ad hoc group emergency alert request” TS 23.283 v20.1.0
- “the IWF may initiate on behalf of the LMR user in the LMR system a subsequent MCPTT ad hoc group emergency call” TS 23.283 v20.1.0
- “The IWF performing the controlling role may include a Retry-After header field to the SIP 500 (Server Internal Error) response” TS 29.379 v20.0.0
Defining Specifications
3GPP specifications that define or reference IWF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TR 22.945 v300 | Fax Services Guidance for GSM/UMTS | R99 read |
| TS 23.054 v300 | Shared Interworking Function (SIWF) Stage 2 | R99 read |
| TS 23.146 vj00 | 3G Facsimile Group 3 Technical Realization | 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.283 vk10 | Mission Critical Communication Interworking | Rel-20 read |
| TS 23.782 vf00 | Interworking between LTE MC and non-LTE MC systems | Rel-15 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |
| TR 23.910 v550 | CS Bearer Services in UMTS | Rel-5 read |
| TR 23.976 vj00 | Push Service Requirements Analysis | Rel-19 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.523 vj00 | NGCN-NGN Interconnection Scenarios | Rel-19 read |
| TS 24.525 vj00 | Business Trunking Architecture & Requirements | Rel-19 read |
| TS 24.883 vg00 | MCPTT Interworking with LMR Systems | Rel-16 read |
| TS 25.424 vj00 | UTRAN Iur Interface Data Transport & Signalling | Rel-19 read |
| TR 26.930 vj00 | WebRTC Enhancements for Immersive RTC over 5G | Rel-19 read |
| TS 28.702 vj00 | Core Network NRM IRP Information Service | Rel-19 read |
| TS 29.305 vj00 | Interworking Functions for EPS-Legacy Systems | Rel-19 read |
| TS 29.368 vj00 | Tsp Reference Point Stage 3 Specification | Rel-19 read |
| TS 29.379 vk00 | MCPTT-LMR Interworking Call Control | Rel-20 read |
| TS 29.421 v810 | IMS Interworking with External IP Networks | Rel-8 read |
| TS 29.805 v800 | IWF for MAP-Diameter Interworking | Rel-8 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 33.180 vk10 | Security of the Mission Critical Service (MCX) | Rel-20 read |