Non-IP Data Delivery

Description

Non-IP Data Delivery (NIDD) is a core network capability standardized by 3GPP to efficiently support Machine-Type Communication (MTC) and Internet of Things (IoT) devices. It allows for the transmission of small, application-layer data units that are not encapsulated within an IP packet. This is achieved by transporting the data payload directly over the control plane signaling protocols, specifically the Non-Access Stratum (NAS) protocol between the User Equipment (UE) and the Mobility Management Entity (MME) in 4G, or the Access and Mobility Management Function (AMF) in 5G. The data bypasses the traditional user plane bearers (PDN connections or PDU sessions), which are designed for continuous, high-volume IP traffic.

The architectural implementation involves key network functions. In the EPS (4G) architecture, the Serving Gateway (SGW) and Packet Data Network Gateway (PGW) are not used for NIDD traffic. Instead, the MME interacts directly with a Service Capability Exposure Function (SCEF) via the T6a interface. The SCEF acts as an API gateway, securely exposing the NIDD service to external Application Servers (AS). It provides non-IP data delivery, device triggering, and monitoring capabilities. In the 5G System (5GS), the analogous function is the Network Exposure Function (NEF), which interacts with the AMF for control plane data transport.

The procedure for NIDD involves the UE indicating its capability for control plane CIoT EPS/5GS optimizations during attach or registration. When the device or the network has data to send, it is encapsulated within a NAS transport message. For Mobile Originated (MO) data, the UE includes the application data in a NAS message sent to the MME/AMF. The MME/AMF then forwards this data to the SCEF/NEF, which delivers it to the designated AS. For Mobile Terminated (MT) data, the process is reversed: the AS sends data to the SCEF/NEF, which triggers a downlink NAS message to the device via the MME/AMF.

NIDD plays a critical role in enabling massive IoT deployments by significantly reducing signaling and power consumption. Since it uses the always-on signaling connection maintained for mobility management, it eliminates the need for the device to activate a data radio bearer and perform a Service Request procedure for each small data transmission. This is ideal for devices sending infrequent status updates, meter readings, or sensor data, leading to extended battery life (often up to 10 years) and reduced core network processing load.

Purpose & Motivation

NIDD was created to address the fundamental inefficiency of using traditional IP-based mobile data connections for the unique traffic patterns of IoT devices. Early IoT/MTC deployments used standard mobile data, which required establishing a full Packet Data Protocol (PDP) context or PDN connection—a process involving significant signaling exchange and radio resource allocation—even to send a few bytes of data. This was highly wasteful of network resources and device battery power, making large-scale deployments economically and technically challenging.

The primary motivation was to optimize the network for 'sporadic small data transmission,' a hallmark of many MTC applications like smart meters, asset trackers, and environmental sensors. 3GPP recognized that the overhead of IP headers (often 40 bytes for IPv4 or 60+ bytes for IPv6) could be larger than the actual application data payload. By allowing data to be sent without IP encapsulation over the existing control plane signaling path, NIDD drastically reduces protocol overhead and signaling latency.

Historically, NIDD was a key component of the Cellular Internet of Things (CIoT) optimizations introduced in 3GPP Release 13. It solved the limitations of previous approaches by reusing the secure, authenticated NAS signaling connection, thereby providing a lightweight, always-available data path. This enabled new business models and services requiring ultra-low power consumption and high connection density, which were not feasible with conventional mobile broadband architectures.