Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · IoT

IWK-SCEF

InterWorking - Service Capability Exposure Function

IoT →

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.

Introduced
Rel-13
Where
Core Network › 5G Core
Specifications
7 specs
Also in
Services
IWK-SCEF Description Purpose What changed Family Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define IWK-SCEF. Each summary describes the whole specification, not only this term.

TS 23.682Rel-18 → Rel-19

Rel-19 adds an MPS for Messaging indication to TS 23.682. It covers configuring this indication via SCEF, storing it in the HSS and MME, and related procedure references.

Full comparison in TS 23.682 →
TS 29.122Rel-18 → Rel-19

Rel-19 adds XR and media QoS extensions with burst-size fields, QoS monitoring with bitrate reporting, and energy efficiency monitoring types to TS 29.122. It also adds Multimedia Priority Service for messaging and CAPIF Phase 3 header updates.

Full comparison in TS 29.122 →

Technology family

Network exposure and analytics · Core Network

  1. Rel-11 SCS/AS
  2. Rel-13 IWK-SCEF, SCEF
  3. Rel-15 CAPIF, NEF, NWDAF
  4. Rel-16 SCEF+NEF
  5. Rel-17 ADRF, AnLF, DCCF, L-NEF, MDAF, MFAF, MTLF
  6. Rel-18 RE-NWDAF
  • IWK-SCEF used together with SCEF
    “When deployed, the IWK-SCEF is located in the VPLMN for inter-connection with the SCEF of the HPLMN.” TS 23.682

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 sources

Documented changes in 5 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.

Rel-13 introduced

IWK-SCEF is specified for the first time in Rel-13: it relays and normalizes monitoring and NIDD signalling between MME/SGSN and SCEF in roaming, applies roaming policies, and generates charging records.

  • “When the IWK-SCEF receives a Reporting-Information-Request command from the MME/SGSN it shall deliver the request to the SCEF after applying the roaming policies” TS 29.128 v13.5.0
  • “For roaming case, the Interworking SCEF (IWK-SCEF) is optionally deployed and located in the VPLMN” TS 32.253 v13.1.0
  • “When the IWK-SCEF receives a MO Data Request from the MME, it shall forward the request to the SCEF.” TS 29.128 v13.5.0
Rel-14 specification text

IWK-SCEF now relays MO/MT data and connection management messages between SCEF and MME or SGSN, not only MME, and takes on charging ID handling and non-IP data relay.

  • “When the IWK-SCEF receives a MO Data Request from the MME or SGSN, it shall forward the request to the SCEF.” TS 29.128 v14.6.0
  • “The IWK-SCEF relays the non-IP data between the MME/SGSN and the SCEF.” TS 23.682 v14.8.0
  • “the IWK-SCEF may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes” TS 29.128 v14.6.0
Rel-15 specification text

IWK-SCEF behaviour changed: it now deletes stored continuous monitoring configurations locally once deletion criteria are met, and its authorization and reporting handling for monitoring events was refined.

  • “If the deletion criteria are met, the IWK-SCEF shall delete the Monitoring event locally.” TS 29.128 v15.6.0
  • “the IWK-SCEF (if it is used in the visited PLMN) or the SCEF, then each of these nodes shall locally delete” TS 23.682 v15.10.0
  • “If the IWK-SCEF has a Maximum Number of Reports stored for this monitoring task, the IWK-SCEF shall decrease its value by one.” TS 23.682 v15.10.0
Rel-16 1 CR

IWK-SCEF behaviour was changed in Rel-16: it handles SCEF-Reference-ID-for-Deletion-Ext AVPs, the Monitoring Indication reporting rules were revised, and 23.682 received an IWK-SCEF correction.

  • “If the received SCEF Reference ID for Deletion (either in SCEF-Reference-ID-for-Deletion or in SCEF-Reference-ID-for-Deletion-Ext AVPs) does not exist, the IWK-SCEF shall set” TS 29.128 v16.6.0
  • “When the maximum number of reports is reached for a Continuous Monitoring Request or in the case of a One-time Monitoring Request, the IWK-SCEF ends the reporting” TS 23.682 v16.10.0
  • IWK-SCEF correction TS 23.682CR0422
Rel-18 specification text

IWK-SCEF behaviour for immediate monitoring event reports changed: it now normalizes the report and sends it to the SCEF as a separate Reporting-Information-Request, instead of returning it in the Configuration-Information-Answer.

  • “The IWK-SCEF shall normalize the event report and send the normalized monitoring event report towards the SCEF as a separate Reporting-Information-Request message.” TS 29.128 v18.0.0
  • “The IWK-SCEF may normalize the event report and return it in the Configuration-Information-Answer.” TS 29.128 v18.0.0
  • “shall be locally consumed at the IWK-SCEF and the IWK-SCEF shall not route such information s beyond it” TS 29.128 v18.0.0

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 Architecture for MTC and SCEF Enhancements Rel-19 read
TS 29.122 vk10 T8 SCEF Service Exposure APIs Rel-20 read
TS 29.128 vj20 MME/SGSN Interfaces for PDN Interworking Rel-19 read
TS 32.253 vj00 Charging for Control Plane Data Transfer Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read