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

Glossary term · IoT

SCEF

Service Capability Exposure Function

IoT →

SCEF is a core network function that securely exposes cellular IoT network services and capabilities, like device triggering, to authorized third-party servers via a controlled gateway.

Introduced
Rel-13
Where
Core Network › Evolved Packet Core
Specifications
45 specs
SCEF Description Purpose What changed Family Detected Changes Specifications

Description

The Service Capability Exposure Function (SCEF) is a pivotal network element defined from 3GPP Release 13 onwards, specifically architected to support Cellular Internet of Things (CIoT) and Machine-Type Communication (MTC). It resides in the core network, typically within the Service-Based Architecture (SBA) of the 5G Core, though it was initially introduced for the Evolved Packet Core (EPC). The SCEF's primary role is to act as a secure northbound API gateway, abstracting and exposing a defined set of network capabilities to external Application Servers (AS) belonging to service providers or enterprises. It provides a standardized, RESTful API (based on HTTP/JSON) defined in 3GPP TS 29.122 (Nnef).

Architecturally, the SCEF interfaces internally with numerous core network functions. Key interfaces include the T6a interface to the MME (for non-IP device triggering and monitoring), the S6t interface to the HSS (for subscribing to subscriber data changes), and interfaces to the PCRF/PGW for policy and charging control. When an external AS needs to send a downlink message to a dormant IoT device (Device Triggering), it sends an HTTP request to the SCEF's API. The SCEF authenticates and authorizes the request, then uses the T6a interface to instruct the MME to page the device and establish a connection so the data can be delivered. Similarly, for monitoring, the AS can request to be notified when a device becomes available (reachability) or moves (location reporting), and the SCEF manages these subscriptions with the HSS and MME.

How it works involves several key components: an API Exposure Layer that handles the external REST API, a Security and Policy Enforcement function that validates AS credentials and applies access control policies, a Network Function Orchestrator that translates API requests into the appropriate legacy or SBA signaling messages (e.g., Diameter or HTTP/2), and a Subscription Manager that tracks active monitoring requests from ASes. Its role is to enable efficient, network-optimized IoT services. By centralizing exposure, it allows the network to offer valuable services like Non-IP Data Delivery (NIDD) over Control Plane, which is critical for low-power, infrequent data transmissions, while maintaining strict security, privacy, and network resource control. It is the cornerstone of the 3GPP's network exposure framework for IoT.

Purpose & Motivation

The SCEF was created to address specific challenges in the massive-scale deployment of IoT devices over cellular networks. Traditional cellular architectures were designed for human-centric, always-online communication with high data rates. IoT devices, in contrast, are often battery-powered, send very small amounts of data infrequently, and can remain dormant for long periods. The existing method of exposing capabilities—often through direct, bespoke integrations with the PGW or PCRF—was insecure, inefficient, and not scalable for millions of devices. There was no standardized, secure way for a third-party weather sensor service, for example, to request a network-triggered wake-up of its device or to check its connectivity status.

The limitations of previous approaches were clear: a lack of a unified exposure point led to security vulnerabilities, complex integration projects for each new service, and an inability to leverage network optimizations like Control Plane CIoT EPS optimization. The SCEF solves these problems by providing a single, standardized, and secure point of exposure. It abstracts the complex, signaling-intensive network procedures into simple API calls. This allows IoT service providers to easily build applications that interact with their devices without needing to understand Diameter, GTP, or other core network protocols.

Historically, its creation was motivated by the 3GPP's work on CIoT optimizations in Release 13. The SCEF, along with concepts like NIDD and User Plane CIoT EPS optimization, formed a complete package to make cellular networks viable for low-cost, low-power IoT. It enables new business models and services, such as predictive maintenance, smart metering, and asset tracking, by giving service providers controlled access to powerful network intelligence and device management capabilities, thereby transforming the cellular network into an IoT-enabling platform.

What changed in its specifications

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

TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →
TS 23.222Rel-18 → Rel-19

Rel-19 adds CAPIF Phase 3 procedures for unpublishing service APIs between interconnected core functions, revoking API invoker and resource owner authorization, open discovery of service APIs, and UE-hosted API invoker access to resources owned by other UEs.

Full comparison in TS 23.222 →

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
  • SCEF counterpart in another generation: NEF
    “In order to support interworking with EPC, the NEF is integrated with SCEF as a combined SCEF+NEF node for network exposure as defined in clause 5.17.5 of TS 23.501 [2].” TS 23.502
  • SCEF used together with IWK-SCEF
    “When deployed, the IWK-SCEF is located in the VPLMN for inter-connection with the SCEF of the HPLMN.” TS 23.682
  • SCEF used together with CAPIF
    “The SCEF may support CAPIF. When CAPIF is supported, the SCEF supports the CAPIF API provider domain functions.” TS 23.682
  • SCEF extended by SCEF+NEF
    “The SCEF+NEF exposes over N33 the same API as the SCEF supports over T8.” TS 23.501

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 8 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

SCEF is specified for the first time in Rel-13 as the entity securely exposing 3GPP network services and capabilities to third-party SCS/AS, including monitoring, NIDD, QoS and background data transfer.

  • “The Service Capability Exposure Function (SCEF) provides a means to securely expose the services and capabilities provided by 3GPP network interfaces.” TS 23.682 v13.11.0
  • “The SCEF is always within the trust domain.” TS 23.682 v13.11.0
  • Introduction of non-IP data delivery via the SCEF for cellular IoT TS 23.682CR0160
Rel-14 specification text

SCEF gained new roles and requirements in Rel-14, including rate control, NIDD buffering, group monitoring report handling, Enhanced Coverage Restriction control, NIDD authorization update, and MBMS TMGI allocation.

  • “The SCEF applies rate control as described in TS 23.401 [7] clause 4.7.7.” TS 23.682 v14.8.0
  • “When the SCEF needs to query the current settings of Enhanced Coverage Restriction, it shall send a CIR command to the HSS” TS 29.336 v14.8.0
  • “The SCEF initiates TMGI allocation by the BM-SC” TS 23.682 v14.8.0
Rel-15 specification text

In Rel-15 the SCEF gained CAPIF API provider support, group MT NIDD handling, new error handling for monitoring events, and expanded monitoring event report processing over S6t.

  • “The SCEF may support CAPIF. When CAPIF is supported, the SCEF supports the CAPIF API provider domain functions.” TS 23.682 v15.10.0
  • “When the SCEF receives a Group MT NIDD request from the SCS/AS, the SCEF queries the HSS to resolve the group members” TS 23.682 v15.10.0
  • “the SCEF shall reject the request by sending a "400 Bad Request" HTTP error response with the application error "EVENT_FEATURE_MISMATCH".” TS 29.122 v15.18.0
Rel-16 1 CR

SCEF behaviour changed in Rel-16: extended 64-bit SCEF Reference IDs on S6t/T6a, new CIR delete-all flags, and 29.122 API corrections such as failure responses and URI handling.

  • “if the feature "Extended Reference IDs" (see clause 8.4.23.1) is supported by the SCEF and the HSS, the term "SCEF Reference ID" shall refer to the content of the 64-bit long” TS 29.336 v16.4.0
  • “the HSS shall delete all Monitoring events configured by the SCEF for the subscriber.” TS 29.336 v16.4.0
  • Failure response for SCEF northbound APIs TS 29.122CR0307
Rel-17 1 CR

SCEF behaviour was extended in Rel-17: it now handles subscription limits and duplicate requests with the enNB feature, supports dynamic group UE add/cancel in monitoring, and handles HTTP PATCH and redirection.

  • “If the "enNB" feature is supported and the SCEF receives an HTTP POST request to create a subscription resource for a monitoring event” TS 29.122 v17.14.0
  • “the Exclude-Identifiers AVP may be included to cancel the event monitoring for the listed UEs in a group” TS 29.336 v17.4.0
  • Support redirection for pure 4G SCEF northbound APIs TS 29.122CR0406
Rel-18 1 CR

SCEF behaviour in T8 monitoring handling changed: it now rejects requests with specific application errors in ProblemDetails (e.g. EVENT_UNSUPPORTED, RESOURCES_EXCEEDED, DUPLICATE_REQUEST) and checks parameters against operator policy ranges.

  • “the SCEF shall reject the request by sending an HTTP "403 Forbidden" error response including the "RESOURCES_EXCEEDED" application error” TS 29.122 v18.10.0
  • “the SCEF shall reject the request by sending an HTTP "400 Bad Request" HTTP error response including the "EVENT_FEATURE_MISMATCH" application error” TS 29.122 v18.10.0
  • Adding SCEF+NEF deployment option TS 23.289CR0082
Rel-19 1 CR

SCEF T8 API behaviour changed: security and authorization now depend on whether CAPIF is used, with scope checks in tokens, and the MPS for Messaging indication is added to network parameter configuration via SCEF.

  • “When the SCEF supports CAPIF for external exposure and CAPIF is used, the provisions of clause 7.2 shall apply for authorizing the access” TS 29.122 v19.7.0
  • MPS for Messaging Indication parameter provisioning via SCEF TS 29.122CR0880
  • “The response shall include a Location header field containing an alternative target URI of the resource located in an alternative SCEF.” TS 29.122 v19.7.0
Rel-20 1 CR

CR adds an integrated deployment of the SCEF and NEF with CAPIF in TS 23.222, a new deployment option for the SCEF itself.

  • New Integrated deployment of the SCEF and the NEF with the CAPIF TS 23.222CR0356

Defining Specifications

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

SpecificationTitleRelease
TS 22.830 vg10 Business Role Models for Network Slicing Rel-16 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.222 vk10 Common API Framework (CAPIF) Rel-20 read
TS 23.286 vk10 V2X Application Enabler Architecture Rel-20 read
TS 23.433 vk40 SEAL Data Delivery Architecture Rel-20 read
TS 23.434 vk10 Service Enabler Architecture Layer (SEAL) for Verticals Rel-20 read
TS 23.554 vj80 MSGin5G Service Application Architecture Rel-19 read
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TS 23.682 vj30 Architecture for MTC and SCEF Enhancements Rel-19 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 23.722 vf10 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-15 read
TR 23.745 vh00 Study on App Layer Support for Factories of the Future in 5G Rel-17 read
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TS 24.301 vk10 EPS NAS Mobility and Session Management Rel-20 read
TS 24.538 vj40 MSGin5G Service Protocol Specification Rel-19 read
TS 24.542 vj00 SEAL Notification Management Protocol Rel-19 read
TS 24.545 vj40 SEAL Location Management Protocol Specification Rel-19 read
TS 24.560 vk10 AIMLE SEAL Services Stage 3 Rel-20 read
TS 26.348 vj00 xMB Interface Specification Rel-19 read
TR 28.816 vh00 Charging for 5G Cellular IoT Rel-17 read
TS 28.849 vj10 CAPIF Phase2 Charging Study Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 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 29.153 vj00 Ns Reference Point Protocol between SCEF and RCAF Rel-19 read
TS 29.154 vj00 Nt Reference Point Protocol Rel-19 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.222 vk10 CAPIF Northbound API Protocol Rel-20 read
TS 29.250 vj00 Nu Reference Point Stage 3 Specification Rel-19 read
TS 29.251 vj00 Gw/Gwn Reference Points Stage 3 Specification Rel-19 read
TS 29.272 vj60 MME and SGSN Diameter interfaces to HSS/CSS/EIR Rel-19 read
TS 29.336 vk00 Diameter-based Interfaces for MTC and Packet Data Networks Rel-20 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.549 vk10 SEAL Service APIs Rel-20 read
TS 29.558 vk00 Edge Application Enablement APIs Rel-20 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.253 vj00 Charging for Control Plane Data Transfer Rel-19 read
TS 32.254 vk00 3GPP TS 32.254: Charging for Northbound APIs Rel-20 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.187 vj00 Security for Machine-Type Communications Enhancements Rel-19 read