Description
The Baseline DNS Action Information Template (BD) is a structured data model defined within 3GPP specifications, primarily under the Operations, Administration and Maintenance (OAM) and Policy and Charging Control (PCC) frameworks. It serves as a standardized format for encoding information related to DNS actions—such as queries, responses, redirections, or filtering instructions—that need to be communicated between network management systems, policy servers, and network functions. The template is designed to be extensible and interoperable, ensuring that different vendors' equipment and software can interpret and execute DNS-related policies uniformly. Its architecture is typically expressed in XML or other data modeling languages, with defined elements for action types, target domains, IP addresses, TTL (Time to Live) values, and precedence rules.
In operation, the BD template is utilized within management interfaces like the Np reference point (between the PCRF and the AF) or within OAM systems to provision DNS policies. For instance, a Policy and Charging Rules Function (PCRF) might use a BD to instruct a Traffic Detection Function (TDF) or a User Plane Function to apply specific DNS handling—like blocking access to certain domains or redirecting DNS queries to a secure resolver. The template's key components include identifiers for the action (e.g., 'allow', 'deny', 'redirect'), parameters specifying the DNS records or domain names involved, and optional metadata such as validity periods or logging requirements. This structured approach allows for fine-grained control over DNS traffic, which is essential for implementing parental controls, enterprise security policies, or network optimization strategies.
The BD's role in the network is pivotal for enabling dynamic and automated DNS policy enforcement without manual intervention. It integrates with 3GPP's broader policy ecosystem, including the PCC architecture defined in TS 23.203, to support real-time service decisions based on subscriber profiles, network conditions, or application requirements. By providing a baseline template, 3GPP ensures that DNS actions can be consistently applied across multi-vendor deployments, reducing integration complexity and enhancing network reliability. Moreover, the template supports scalability by allowing network operators to define reusable policy rules that can be applied to large subscriber bases, facilitating efficient management of DNS-related services in evolving 5G and IoT environments.
Purpose & Motivation
The BD was created to address the need for standardized DNS policy management in 3GPP networks, particularly as services became more dependent on dynamic and application-aware traffic handling. Prior to its introduction, DNS-related actions were often implemented using proprietary or ad-hoc methods, leading to interoperability challenges between different network elements and management systems. This lack of standardization made it difficult to deploy consistent DNS policies—such as content filtering, parental controls, or traffic steering—across heterogeneous network environments, hindering service agility and increasing operational costs.
Motivated by the growing importance of DNS in service delivery and security, 3GPP introduced the BD in Release 8 as part of enhancements to the PCC and OAM frameworks. It solves the problem of fragmented DNS policy enforcement by providing a common template that can be used across various interfaces, such as those between the PCRF, AF, and TDF. This enables operators to implement centralized policy control for DNS actions, ensuring that subscribers receive uniform service experiences regardless of the underlying network equipment. Historically, this was driven by the expansion of mobile broadband and the need for more sophisticated traffic management capabilities beyond basic charging and QoS.
Furthermore, the BD facilitates automated network operations by allowing DNS policies to be dynamically provisioned and updated based on real-time conditions, such as network congestion or security threats. It addresses limitations of earlier approaches that relied on static configurations or manual interventions, which were inefficient and error-prone. By embedding DNS action information into a standardized template, 3GPP has enabled more robust and scalable solutions for managing DNS in the context of evolving technologies like 5G, network slicing, and IoT, where flexible and reliable DNS handling is critical for service functionality and security.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (116 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the BD (Baseline DNS Action Information Template) function was newly introduced specifically for 5G Charging. This addition established a standardized template to structure charging data, alongside other enhancements like improved location information for WLAN access and the addition of rate-control information and triggers.
- Enhance location information in trusted and untrusted WLAN TS 32.251CR0503
- Introduce the Bd for 5G Charging TS 32.297CR0030
- Enhance location information in trusted and untrusted WLAN TS 32.298CR0658
- Adding Rate-Control information and triggers TS 32.251CR0513
- Correction on the User Information TS 32.255CR0001
- Correction of NF Consumer Information TS 32.255CR0035
+ 8 more changes
In Release 16, the BD function was enhanced to include new charging information for interworking with the Evolved Packet Core (EPC) and for 5G data connectivity involving the Intermediate Session Management Function (I-SMF). The release also introduced charging details for Multi-Access (MA) PDU sessions, including support for non-3GPP access, and added specific information for VoLTE and 5WWC (5G Wireless and Wireline Convergence) charging.
- Add VoLTE information TS 32.251CR0516
- Add description of charging information for offline only charging TS 32.255CR0039
- Definition of charging information for interworking with EPC TS 32.255CR0059
- Definition of charging information for interworking with EPC TS 32.255CR0072
- Add I-SMF PDU session charging information TS 32.255CR0118
- Adding I-SMF in 5G data connectivity charging information TS 32.255CR0129
+ 21 more changes
In Release 17, the key enhancement for the Baseline DNS Action Information Template (BD) function was the introduction of a "Key of Map in Data Structure for Baseline DNS Pattern." This addition provided a new structural element for organizing pattern-related information within the template's data framework. Other changes in the release focused on corrections to existing charging and reporting procedures, such as for PDU session information and presence reporting areas.
- Add Charging Information for URLLC Charging TS 32.255CR0278
- Additional charging information for the 5G LAN charging TS 32.255CR0355
- Add charging information of 5GS CIoT TS 32.255CR0364
- Add charging information for 5GS usage for Edge Computing TS 32.255CR0368
- Introduction of 5G ProSe converged charging information TS 32.277CR0044
- Add GERAN/UTRAN user location information TS 32.298CR0874
+ 14 more changes
In Release 18, the BD function was enhanced to support new charging scenarios, including the addition of specific charging information for Time-Sensitive Communication (TSC) traffic, 5G Multicast/Broadcast Services (MBS), and satellite access and backhaul. It also introduced updates for converged charging information and expanded inter-Charging Function (CHF) data exchange. Furthermore, the template was updated to enforce VPLMN-specific offloading information for IP address ranges and to support caller and callee information within PDU session charging.
- BaselineDNSPattern for HR-SBO roaming TS 29.556CR0027
- Enforcement of VPLMN specific offloading information for IP addresses ranges TS 29.556CR0034
- Support of Caller and Callee Information in PDU session charging TS 32.255CR0429
- Rel-18 CR 32.255 Addition of CHF information TS 32.255CR0477
- Add charging information for the satellite backhaul TS 32.255CR0479
- Add charging information for TSC traffic charging TS 32.255CR0492
+ 29 more changes
In Release 19, the BD function was enhanced to support new charging information for emerging services, including store-and-forward satellite operations for SMS and UP CIoT, as well as for Ranging and Sidelink Positioning. Additionally, it was extended to include charging-related information for ProSe Multi-Hop UE-to-Network and Layer-3 UE-to-UE relay communication. The release also introduced the capability to carry network slice energy-related information within the charging framework.
- Rel-19 CR 32.240 Support the energy related information per network slice TS 32.240CR0498
- Add charging information for store and forward satellite operation of SMS service TS 32.251CR0521
- Add charging information for store and forward satellite operation with UP CIoT TS 32.251CR0523
- Introduction of converged charging information for Ranging and Sidelink Positioning TS 32.271CR0026
- Extend charging information and bindings for 5G LCS converged charging TS 32.271CR0034
- Add charging-related information in support of ProSe Multi-Hop UE-to-Network communication TS 32.277CR0054
+ 13 more changes
In Release 20, the "BD" function was enhanced to address charging impacts from enhanced QoS handling in XRM. This was achieved by adding new information elements to the Baseline DNS Action Information Template. These additions provided the necessary data to accurately correlate and charge for services utilizing the improved QoS mechanisms.
- Rel-20 TS 32.255 Add information elements to address charging impacts from enhanced QoS handling in XRM TS 32.255CR0616
Explore further
Broader topics and technologies where BD plays a role.
Defining Specifications
3GPP specifications that define or reference BD, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 26.906 vj00 | HEVC Evaluation for 3GPP Services | Rel-19 |
| TR 26.948 vj00 | Video enhancements for 3GPP Multimedia Services | Rel-19 |
| TS 29.556 vj40 | EASDF Service Based Interface Protocol | Rel-19 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 |
| TS 32.252 vc00 | 3GPP WLAN Interworking Charging | Rel-12 |
| TS 32.253 vj00 | Charging for Control Plane Data Transfer | Rel-19 |
| TS 32.254 vj21 | Charging for Northbound APIs | Rel-19 |
| TS 32.255 vk10 | Telecom Management; Charging for 5G Data Connectivity | Rel-20 |
| TS 32.256 vj40 | 5G Connection & Mobility Charging Spec | Rel-19 |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.273 vj00 | MBMS Charging Management | Rel-19 |
| TS 32.277 vj20 | Charging Management for Proximity Services (ProSe) | Rel-19 |
| TS 32.278 vj00 | Monitoring Events Offline Charging Specification | Rel-19 |
| TS 32.279 vj00 | 5G MBS Session Converged Charging | Rel-19 |
| TS 32.295 vj00 | 3GPP Charging: CDR Transfer via GTP' Protocol | Rel-19 |
| TS 32.297 vj00 | Charging Data Record File Transfer | Rel-19 |
| TS 32.298 vj30 | Charging Data Record (CDR) Parameter Specification | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 32.821 v1900 | SON OAM Architecture for Home NodeB | Rel-9 |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 |
| TR 38.808 vh00 | Study on NR above 52.6 GHz to 71 GHz | Rel-17 |