DPF

Direct Services Provisioning Function

Services →
Introduced in Rel-9

DPF is a network function that enables the direct provisioning of services to a User Equipment without requiring it to be attached to the 3GPP network for control-plane signaling.

Category
Services
Introduced
Rel-9
Where
Services › IMS
Specifications
7 specs
DPF Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofSCEF
Related approachesNEF

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-9, normative work from Rel-15.

Rel-15 7 changes

In Release 15, the DPF (Direct Services Provisioning Function) was updated to support WLAN Direct Discovery as an alternative technology for ProSe Direct Discovery. Specifically, the ProSe Direct Services Provisioning Management Object (MO) was updated to accommodate this WLAN integration. This allowed the DPF to provision necessary configuration information, such as relay service codes for MCPTT groups, for services utilizing this new discovery method.

  • FEC for mission critical services TS 23.280CR0043
  • Header compression for MC services over MBMS TS 23.280CR0058
  • Inclusion of WLAN direct discovery technologies as an alternative for ProSe Direct Discovery: WLAN technology agnostic part TS 23.303CR0324
  • Inclusion of WLAN direct discovery technologies as an alternative for ProSe Direct Discovery: NAN specific part TS 23.303CR0325
  • Update to ProSe Direct Services Provisioning MO for WLAN Direct Discovery TS 24.333CR0060
  • Update to DDF for ProSe Direct Services Provisioning MO for WLAN Direct Discovery TS 24.333CR0049

+ 1 more changes

Rel-16 1 change

In Release 16, the DPF (Direct Services Provisioning Function) gained a new capability for functional alias alternative addressing specifically for MCX services. This enhancement allows the DPF to provide an alternative addressing mechanism, such as a relay service code, which can be allocated for MCPTT groups and provided to the user equipment. This supports scenarios where confidentiality of user identities is required or for use with temporary MCPTT IDs prior to full authentication.

  • Functional alias alternative addressing for MCX services TS 23.280CR0187
Rel-19 1 change

In Release 19, the DPF (Direct Services Provisioning Function) saw changes focused on tightening access to Mission Critical (MC) services. Specifically, external applications' access to these MC services was removed. This adjustment refines the provisioning and management of MC service parameters, such as relay service codes for MCPTT groups, ensuring they are handled within a more controlled and secure framework.

  • Removing external applications access to MC services TS 23.280CR0604

Explore further

Broader topics and technologies where DPF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.179 vd50 MCPTT Functional Architecture Rel-13
TS 23.280 vk10 Common Architecture for Mission Critical Services Rel-20
TS 23.303 vj00 Proximity Services (ProSe) Stage 2 Rel-19
TS 23.379 vk00 MCPTT Functional Architecture Rel-20
TS 24.333 vj00 ProSe Management Objects for UE Configuration Rel-19
TS 32.844 vc00 Charging for ProSe Direct Communication in Public Safety Rel-12
TS 33.812 v920 M2M Remote Subscription Management Security Rel-9