Description
Background Data Transfer (BDT) is a standardized 5G service feature introduced in 3GPP Release 15 that enables network operators to manage and schedule data transmissions for applications that do not require immediate delivery. The service operates through a policy-based framework where the network determines optimal transmission windows based on network conditions, subscription profiles, and application requirements. BDT is implemented within the 5G Core Network's Policy Control Function (PCF) and Session Management Function (SMF), working in conjunction with the User Plane Function (UPF) to enforce scheduled data transfer policies.
The architecture of BDT involves several key components: the Application Function (AF) that requests background transfer capabilities, the Policy Control Function (PCF) that creates and manages BDT policies, the Session Management Function (SMF) that enforces these policies at the session level, and the User Plane Function (UPF) that implements the actual data transfer scheduling. The Network Exposure Function (NEF) may also be involved when third-party applications request BDT services through external APIs. The system uses standardized interfaces including N5 (PCF-AF), N7 (SMF-PCF), and N4 (SMF-UPF) to coordinate BDT operations across network functions.
BDT works through a multi-step process: first, an application or network function identifies traffic eligible for background transfer based on QoS requirements and application characteristics. The PCF then creates BDT policies specifying parameters such as maximum allowed delay, preferred time windows, data volume limits, and network conditions for activation. These policies are communicated to the SMF, which translates them into specific session rules. The UPF implements these rules by buffering, delaying, or scheduling data transmissions according to the established parameters. The system continuously monitors network conditions and can dynamically adjust BDT parameters to optimize performance.
The service supports various operational modes including time-based scheduling (specific time windows), network condition-based scheduling (when network load is below certain thresholds), and hybrid approaches. BDT policies can be applied at different granularities: per subscriber, per application, per data network name (DNN), or per network slice. The system includes mechanisms for policy conflict resolution, charging correlation for scheduled transfers, and reporting of BDT execution status to both network functions and external applications when authorized.
Purpose & Motivation
BDT was created to address the growing challenge of network congestion caused by massive amounts of non-urgent data traffic in 5G networks. As IoT deployments expanded and applications like software updates, cloud backups, and content synchronization became ubiquitous, networks faced increasing pressure from background traffic competing with latency-sensitive applications. Traditional approaches treated all data equally, leading to inefficient resource utilization during peak hours and degraded performance for critical services.
Previous 3GPP releases lacked standardized mechanisms for managing background traffic efficiently. Operators implemented proprietary solutions or relied on basic QoS differentiation, which proved insufficient for the scale and complexity of 5G use cases. The limitations included inability to coordinate transfers across multiple applications, lack of standardized APIs for third-party integration, and insufficient granularity in scheduling controls. BDT provides a standardized framework that enables predictable network behavior while maintaining service quality for all applications.
The technology solves several key problems: it reduces network congestion during peak hours by shifting non-urgent traffic to off-peak periods, improves energy efficiency for both network infrastructure and user devices by optimizing transmission timing, enables new business models for differentiated background data services, and provides tools for network operators to manage the explosion of machine-type communications in 5G networks. By creating a standardized approach, 3GPP ensured interoperability across vendors and enabled global deployment of efficient background data management solutions.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (84 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Background Data Transfer (BDT) function was newly introduced, enabling an Application Function to negotiate future data transfer policies with the network via the Npcf_BDTPolicyControl_Create service operation. This introduced procedures for negotiating time windows and conditions for bulk transfers, applying these policies to UEs, and storing the associated BDT Reference ID in the UDR. The release also defined the integration of these policies into URSP rules and PDU Session policy control, along with clarifications for the BDT API and network area information.
- Background Data Transfer data TS 29.519CR0014
- Correction for background data transfer for TS 23.503 TS 23.503CR0003
- BDT: clarification on network area information and ASP identifier TS 23.503CR0121
- BDT API Update TS 29.122CR0014
- Complete the openAPI definition for BDT API TS 29.122CR0017
- http details in BDT procedure TS 29.513CR0036
+ 4 more changes
In Release 16, the BDT function was enhanced to include a BDT warning notification procedure for policy re-negotiation, enabled the PCF to utilize network analytics for calculating BDT policies, and introduced the delivery of BDT policies to the UE for storage as URSP rules. Additionally, support was added for retrieving BDT policy data for multiple BDT reference IDs and for managing BDT references within PDU session policy control subscription information.
- Update of TS 23.503 for Rel.16 BDT Notification TS 23.503CR0205
- Use of analytics for background data transfer TS 23.503CR0206
- Adding Support for Delivering Background Data Transfer Polices to the UE TS 23.503CR0242
- Removal of Editor's note for BDT warning notification and define send for notification in TS23.503 TS 23.503CR0256
- PDU session management for Background Data Transfer TS 23.503CR0271
- BDT Warning Notification Support TS 29.122CR0175
+ 24 more changes
In Release 17, key enhancements for Background Data Transfer (BDT) included the introduction of URSP rule generation based on the BDT policy to guide UE routing, the formalization of BDT policy re-negotiation procedures, and the support for a PATCH method to update NIDD downlink data transfer resources. Additionally, the release provided clarifications and corrections for handling applied BDT policy data and for failure authorization results related to BDT reference IDs.
- Add the support for PATCH method for the update of a NIDD DL Data transfer resource TS 29.122CR0547
- URSP rule generation based on BDT policy and related information TS 23.503CR0632
- Faliure authorization result of BDT reference Id for ChargeableParty API request TS 29.122CR0324
- Handling of query parameters in Applied BDT Data TS 29.519CR0332
- Correction in the handling of individual Applied BDT Policy Data resource TS 29.519CR0347
- Clarify the BDT warning description with degraded Network performance TS 23.503CR0589
+ 2 more changes
In Release 18, the BDT (Background Data Transfer) function was enhanced with specific negotiation procedures and data handling improvements. New capabilities included negotiation for Planned Data Transfer with QoS (PDTQ) requirements and the introduction of a BDT warning notification procedure that can trigger policy re-negotiation. Furthermore, clarifications and corrections were made regarding BDT negotiation data, the Bdt policy data type, and the storage of the BDT warning notification indication and ASP address in the UDR.
- Negotiation of the time window for Application Data Transfer TS 23.503CR0764
- Updates to BDT on ASP Id TS 29.122CR0702
- Transferring the NSCE_NetworkSliceAdaptation API to TS 29.435 TS 29.549CR0220
- Corrections on Planned Data Transfer with QoS (PDTQ) Policy TS 23.503CR1152
- Clarification on information transferred between TSCTSF and PCF for DetNet TS 23.503CR1171
- [5GMS_Pro_Ph2] Completion of media session handling client API for Background Data Transfer TS 26.510CR0010
+ 5 more changes
In Release 19, the BDT function was enhanced to introduce a new "Energy indicator" as an input from the AF during policy negotiation, allowing the AF to express a preference for transferring data in time windows that consume lower energy. The release also introduced support for an "Expedited Transfer indication" from the AF to the NEF and included corrections and updates to the BDT negotiation procedure to incorporate this energy-related information into the policy decision. Furthermore, it added the capability to provision URSP rules specifically for Background Data Transfer.
- BDT Energy Criteria TS 23.503CR1420
- Enhancements for AF/AS triggered expedite data transfer TS 23.503CR1448
- Energy indicator for BDT policy TS 29.122CR0923
- Providing Expedited Transfer indication from AF to NEF TS 29.122CR0941
- Support content breakpoint information for downlink delivery during DD context transfer TS 29.548CR0020
- BDT support and related corrections in SS_NetworkResourceAdaptation API TS 29.549CR0395
+ 18 more changes
In Release 20, the new Background Data Transfer (BDT) function was introduced, enabling an Application Function to negotiate future data transfer time windows with the network via the PCF. This includes procedures for BDT policy negotiation and application to UEs, and it incorporates an Energy indicator to allow the AF to request transfers during periods of lower network energy consumption.
- Adding BDT, PDTQ and UE policy control for network energy saving TS 23.503CR1612
Explore further
Broader topics and technologies where BDT plays a role.
Defining Specifications
3GPP specifications that define or reference BDT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.503 vk00 | 5G Policy and Charging Control Framework | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 26.510 vj10 | Media Delivery APIs for 5GMS and RTC Systems | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 29.122 vj40 | T8 Reference Point for Northbound APIs | Rel-19 |
| TS 29.513 vj40 | 5G PCC Signalling Flows & QoS Mapping | Rel-19 |
| TS 29.519 vj40 | UDR Usage for Policy & Exposure Data | Rel-19 |
| TS 29.522 vj40 | 5G NEF Northbound APIs Stage 3 | Rel-19 |
| TS 29.548 vj40 | SEAL Data Delivery Server Services Stage 3 | Rel-19 |
| TS 29.549 vj40 | SEAL API Specification for Vertical Applications | Rel-19 |
| TS 29.554 vj10 | 5G Background Data Transfer Policy Control Service | Rel-19 |