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.
Key Features
- Standardized XML-based template structure for DNS action information
- Support for multiple DNS action types including allow, deny, and redirect
- Integration with 3GPP Policy and Charging Control (PCC) architecture
- Extensible parameters for domain names, IP addresses, and TTL values
- Enables dynamic provisioning and real-time policy enforcement
- Facilitates interoperability across multi-vendor network equipment
Evolution Across Releases
Introduced the Baseline DNS Action Information Template as part of initial PCC and OAM enhancements. Defined the core structure for encoding DNS actions, enabling basic policy control for DNS queries and responses. Supported integration with early PCRF and TDF functions to allow standardized DNS policy enforcement in mobile networks.
Defining Specifications
| Specification | Title |
|---|---|
| TS 26.906 | 3GPP TS 26.906 |
| TS 26.948 | 3GPP TS 26.948 |
| TS 29.556 | 3GPP TS 29.556 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.250 | 3GPP TR 32.250 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.252 | 3GPP TR 32.252 |
| TS 32.253 | 3GPP TR 32.253 |
| TS 32.254 | 3GPP TR 32.254 |
| TS 32.255 | 3GPP TR 32.255 |
| TS 32.256 | 3GPP TR 32.256 |
| TS 32.270 | 3GPP TR 32.270 |
| TS 32.271 | 3GPP TR 32.271 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.273 | 3GPP TR 32.273 |
| TS 32.277 | 3GPP TR 32.277 |
| TS 32.278 | 3GPP TR 32.278 |
| TS 32.279 | 3GPP TR 32.279 |
| TS 32.295 | 3GPP TR 32.295 |
| TS 32.297 | 3GPP TR 32.297 |
| TS 32.298 | 3GPP TR 32.298 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 32.821 | 3GPP TR 32.821 |
| TS 32.850 | 3GPP TR 32.850 |
| TS 38.808 | 3GPP TR 38.808 |