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 (93 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- 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
- 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
- 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
- Alignment of BDT policy re-negotiation TS 29.513CR0231
+ 1 more changes
- Updates to BDT on ASP Id TS 29.122CR0702
- BDT_Configuration_request API support with description update TS 29.549CR0194
- BDT_Configuration_request API support with resources and data model update TS 29.549CR0196
- BDT_Negotiation_notification support with description update TS 29.549CR0197
- BDT_Negotiation_Notification support with Notification message and data model update TS 29.549CR0198
- BDT_Configuration_request API support with open API update TS 29.549CR0199
+ 9 more changes
- Adding BDT, PDTQ and UE policy control for network energy saving TS 23.503CR1612
- Enhancements to the support of Energy aware BDT negotiation TS 29.513CR0644
- Enhancements to the support of Energy aware BDT negotiation TS 29.513CR0643
- BDT Policy Removal Corrections TS 29.554CR0116
- Enhancements to the support of Energy aware BDT negotiation TS 29.554CR0118
- Clarification on the interactions between PCF and UDR for BDT and PDTQ negotiation TS 23.503CR1659
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 vk20 | 5G System Policy and Charging Control Framework | Rel-20 |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 |
| TS 26.510 vj20 | 5G Media Streaming and Real-Time Communication APIs | Rel-19 |
| TS 26.804 vk00 | 5G Media Streaming Architecture Extensions | Rel-20 |
| TS 29.122 vk00 | T8 Reference Point Protocol for SCEF and SCS/AS | Rel-20 |
| TS 29.513 vk00 | Policy and Charging Control in 5G System | Rel-20 |
| TS 29.519 vk00 | UDR Policy, Application & Exposure Data Service | Rel-20 |
| TS 29.522 vk00 | NEF Northbound Interface Specification | Rel-20 |
| TS 29.548 vk00 | SEAL Data Delivery Server Services | Rel-20 |
| TS 29.549 vk01 | SEAL Services APIs | Rel-20 |
| TS 29.554 vk00 | BDT Policy Control Service (Npcf_BDTPolicyControl) | Rel-20 |