Directory Name Service

Description

The Directory Name Service (DNS) in 3GPP is a critical infrastructure component based on the Internet Engineering Task Force (IETF) standards, specifically RFC 1034 and RFC 1035. It operates as a distributed database that resolves Fully Qualified Domain Names (FQDNs) into corresponding IP addresses and other resource records, such as NAPTR (Naming Authority Pointer) and SRV (Service) records. Within the 3GPP architecture, DNS is used extensively by core network functions for dynamic discovery and selection of peer network elements. For instance, during the establishment of a Packet Data Network (PDN) connection, the Packet Data Network Gateway (PGW) or Session Management Function (SMF) may be selected based on DNS queries that consider the Access Point Name (APN), subscriber's location, and network policies. The system employs a hierarchical structure with root servers, top-level domains, and authoritative name servers specific to the operator's network (e.g., epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org). DNS queries are initiated by various network functions, including the Mobility Management Entity (MME), Serving GPRS Support Node (SGSN), Home Subscriber Server (HSS), and Policy and Charging Rules Function (PCRF), to locate services like the PGW/SMF, HSS/UDM, or application servers. The resolution process involves recursive and iterative queries, with caching mechanisms at resolvers to improve efficiency and reduce latency. DNS is also pivotal for inter-operator connectivity, enabling the resolution of FQDNs for roaming scenarios and interconnection between different Public Land Mobile Networks (PLMNs). In 5G systems, DNS remains essential for service-based architecture (SBA), where Network Function (NF) instances register their profiles and endpoints in the Network Repository Function (NRF), and consumer NFs use DNS-based service discovery to find appropriate producer NFs based on service names, NF types, and other selection criteria.

Purpose & Motivation

DNS was introduced to solve the problem of static, hard-coded network element addressing, which was inflexible and difficult to manage in large-scale, dynamic mobile networks. Prior to its adoption, network configurations required manual updates of IP addresses in network elements, leading to operational complexity, scalability issues, and increased risk of errors during network expansions or failures. The primary motivation was to enable automated, dynamic discovery and selection of network functions, which is essential for load balancing, redundancy, and efficient resource utilization. DNS provides a standardized, scalable mechanism for service and node discovery across the core network, supporting features like APN resolution, PGW/SMF selection, and inter-operator roaming. It abstracts the underlying network topology, allowing operators to deploy and relocate network functions without reconfiguring every dependent element. This flexibility is crucial for the evolution towards cloud-native, virtualized networks and 5G's service-based architecture, where network functions can be instantiated and scaled elastically. DNS also facilitates the implementation of advanced traffic steering policies, network slicing, and multi-vendor interoperability by providing a common resolution framework.