DPF

Direct Services Provisioning Function

Services
Introduced in Rel-9
The Direct Services Provisioning Function (DPF) is a network function that enables the direct provisioning of services to a User Equipment (UE) without requiring the UE to be attached to the 3GPP network for control-plane signaling. It is a key enabler for IoT and MTC services, allowing efficient, network-triggered wake-up and data delivery to devices in power-saving states.

Description

The Direct Services Provisioning Function is a logical function that facilitates service delivery to a UE, particularly one configured for Power Saving Mode (PSM) or extended idle mode Discontinuous Reception (eDRX), by interfacing with the core network. It acts as a service layer endpoint that can receive downlink data or trigger requests from an external Services Capability Server (SCS) or Application Server (AS). When such data arrives for a UE that is not reachable via normal paging (e.g., in PSM), the DPF stores this data and associates it with a trigger event.

Architecturally, the DPF can be implemented as part of a Services Capability Server (SCS) within the 3GPP network exposure framework or as a separate entity. It interacts with the core network's Service Capability Exposure Function (SCEF) in 4G or the Network Exposure Function (NEF) in 5G Core. The key operation involves the DPF requesting the network to perform a Device Triggering procedure. It sends a Device Trigger Request message to the SCEF/NEF, which then forwards it to the Mobility Management Entity (MME) in 4G or the Access and Mobility Management Function (AMF) in 5G. The network then attempts to deliver a non-access stratum (NAS) notification or a Short Message Service (SMS) to the UE to prompt it to re-attach and establish a data connection to retrieve the waiting data.

How it works involves a store-and-notify mechanism. The DPF holds the downlink data or service command. It then uses the Device Triggering service to send a small wake-up signal (the trigger) to the UE via the core network's signaling paths. This trigger contains just enough information to instruct the UE to initiate a Mobile Originated (MO) procedure. Once the UE attaches, it can contact its service platform (which may be co-located with or connected to the DPF) to pull the waiting data. This model reverses the classic 'always-on' downlink push, optimizing for IoT device battery life.

Purpose & Motivation

The DPF was created to solve a critical problem in Machine-Type Communication (MTC) and Internet of Things (IoT): how to send data to a device that is in a deep power-saving state to maximize battery life. Traditional cellular networks require a device to be periodically reachable for paging to receive downlink data. Power Saving Mode (PSM) and eDRX, introduced for IoT, break this model by allowing devices to sleep for very long periods, making them unreachable for downlink traffic. The DPF provides a mechanism to 'wake up' such devices in a network-efficient way.

It addresses the limitations of previous approaches where the only option was to wait for the device to wake up on its own schedule (Mobile Originated traffic only) or to use always-on connections that drain battery. The DPF enables a 'network-triggered' service model, which is essential for many IoT applications like firmware updates, remote control commands, or alarm acknowledgements that need to originate from the network side.

Its development and standardization in 3GPP (starting in Rel-9 and enhanced in later releases) were motivated by the massive scale projections for IoT. The DPF, as part of the broader Machine-Type Communication (MTC) and Cellular IoT (CIoT) feature set, allows operators to offer efficient, scalable services for millions of low-power devices. It facilitates new business models and applications where devices can remain dormant for years yet remain responsive to critical network-initiated commands.

Key Features

  • Enables downlink data delivery and service triggering to UEs in power-saving states (PSM, eDRX)
  • Interfaces with core network exposure functions (SCEF in 4G, NEF in 5G) for Device Triggering
  • Stores downlink data or service commands awaiting device availability
  • Initiates Non-Access Stratum (NAS) notifications or SMS-based wake-up signals to UEs
  • Key component of 3GPP's MTC and CIoT architectures for efficient network-initiated communication
  • Supports the 'Mobile Terminated' service model for battery-constrained IoT devices

Evolution Across Releases

Rel-9 Initial

The Direct Services Provisioning Function concept was introduced as part of early Machine-Type Communication (MTC) enhancements. The initial architecture defined its role in interfacing with the network to trigger devices, primarily focusing on enabling basic network-initiated communication for MTC applications.

Defining Specifications

SpecificationTitle
TS 23.179 3GPP TS 23.179
TS 23.280 3GPP TS 23.280
TS 23.303 3GPP TS 23.303
TS 23.379 3GPP TS 23.379
TS 24.333 3GPP TS 24.333
TS 32.844 3GPP TR 32.844
TS 33.812 3GPP TR 33.812