IWK-SCEF

InterWorking - Service Capability Exposure Function

IoT →
Introduced in Rel-13

IWK-SCEF is a 3GPP network function for Cellular IoT that interworks between the SCEF and entities like the MME to relay non-IP data, enabling service exposure for devices on optimized CIoT architectures.

Category
IoT
Introduced
Rel-13
Where
Core Network › 5G Core
Specifications
7 specs
IWK-SCEF Description Purpose Related Classification Detected Changes Specifications

Description

The IWK-SCEF (Interworking - Service Capability Exposure Function) is a functional entity introduced in 3GPP Release 13 as part of the Cellular Internet of Things (CIoT) enhancements. Its primary role is to facilitate the interconnection between the Service Capability Exposure Function (SCEF) and the Core Network mobility management nodes—specifically the Mobility Management Entity (MME) and the Serving GPRS Support Node (SGSN)—for certain CIoT services. The SCEF itself is the key node for securely exposing network services and capabilities to third-party Application Servers (AS), but direct interfaces between the SCEF and the MME/SGSN were not originally defined for all procedures.

Architecturally, the IWK-SCEF sits logically between the SCEF and the MME/SGSN. It acts as an intermediary or a proxy for the T6a/T6b interface, which is used for Non-IP Data Delivery (NIDD). NIDD is a CIoT optimization that allows small, infrequent data packets from IoT devices to be transmitted efficiently without the overhead of a full IP stack or PDP context. When an Application Server wants to send or receive NIDD data to/from an IoT device, it communicates with the SCEF over the API-based T8 interface. For the actual data transfer and session management with the device, the SCEF needs to interact with the MME (for LTE) or SGSN (for 2G/3G). The IWK-SCEF provides this interconnection point, relaying NIDD-related messages between the SCEF and the MME/SGSN.

How it works involves specific signaling procedures. For example, for mobile-originated NIDD, the device sends data to the MME. The MME forwards this data to the IWK-SCEF over the T6a interface. The IWK-SCEF then routes it to the appropriate SCEF, which delivers it to the destined Application Server. The reverse path is followed for mobile-terminated NIDD. The IWK-SCEF handles the mapping of identifiers, manages NIDD session contexts, and ensures the secure and reliable transfer of the small data packets. It is a critical component in the CIoT EPS architecture for enabling efficient, network-exposed IoT communication, particularly for devices using the Control Plane CIoT EPS optimization where data is carried over NAS signaling.

Purpose & Motivation

IWK-SCEF was created to resolve a specific architectural gap in the initial CIoT and SCEF framework defined in earlier releases. The SCEF was designed to expose network capabilities, but its direct interconnection with the MME and SGSN for the vital Non-IP Data Delivery (NIDD) service was not fully specified, creating an implementation hurdle for efficient IoT data transport.

The problem it addresses is enabling the SCEF-based exposure model for the new, optimized CIoT architectures. IoT devices often use power-efficient, latency-tolerant communication methods like NIDD over the control plane. To make these device services available to external applications via the SCEF's T8 API, a standardized and secure path from the SCEF to the MME/SGSN was necessary. Without the IWK-SCEF, operators would need proprietary integrations or alternative, less optimal data paths for CIoT devices using NIDD, undermining the efficiency gains of the CIoT optimizations.

Its introduction in Release 13 was motivated by the need to complete the end-to-end architecture for CIoT service exposure. It ensured that the benefits of the SCEF—such as secure API-based access, network capability abstraction, and simplified application development—could be fully realized for the massive IoT market segment. By defining the IWK-SCEF, 3GPP provided a clear, standardized interworking point that enabled scalable deployment of NIDD services, supporting the low-cost, long-battery-life use cases that are central to Cellular IoT.

Classification

Part ofSCEF
Related approachesNIDD

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 1 change

In Release 16, the IWK-SCEF function was refined with corrections to its procedures and capabilities. The release explicitly defined its role in normalizing Monitoring Event reports according to operator policies and detailed the authorization and rejection mechanisms for monitoring requests between the MME/SGSN and the IWK-SCEF. Furthermore, it clarified the function's operation for Non-IP Data Delivery (NIDD) service and the specific use of the T7 reference point to connect the IWK-SCEF to the SCEF in the HPLMN.

Explore further

Broader topics and technologies where IWK-SCEF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.682 vj30 3GPP TS 23682: MTC Architecture Enhancements Rel-19
TS 29.122 vj40 T8 Reference Point for Northbound APIs Rel-19
TS 29.128 vj10 MME/SGSN-SCEF Diameter Interfaces for PDN Interworking Rel-19
TS 32.253 vj00 Charging for Control Plane Data Transfer Rel-19
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.