DNS Orchestration for Transparent 5G Network Function Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Service-Based Architecture (SBA) for 5G networks faces complexity in roaming scenarios due to the need for separate addressing and logic provisioning for non-roaming and roaming scenarios, which complicates the registration of Network Functions (NFs) and requires dedicated discovery and routing logic, leading to increased provisioning difficulties.
Innovation Solution
The introduction of a Network Function Discovery Orchestration (NFDO) function that simplifies NF discovery by using Fully Qualified Domain Names (FQDNs for registration and provisioning, eliminating the need for NFs to indicate roaming sessions and providing separate addressing, thereby enabling transparent routing across PLMNs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate addressing and logic provisioning is implemented for roaming and non-roaming scenarios, then NF discovery and routing can be performed accurately, but the device complexity and provisioning difficulty increase significantly
Solution Approach 1:
The DNS server is configured to handle both roaming and non-roaming scenarios through a single unified interface. By using FQDNs that work universally across different PLMNs and implementing conditional resolution logic within the DNS server itself, the system eliminates the need for separate addressing mechanisms, thereby reducing provisioning complexity while maintaining accurate NF discovery
Solution Approach 2:
The DNS server acts as an intermediary between NF service consumers and NF service producers in roaming scenarios. Instead of requiring complex direct routing logic in NFs, the DNS server mediates the resolution process by translating FQDNs into appropriate IP addresses based on the consumer's PLMN location, thereby simplifying the overall system architecture
2Adaptability or versatility
If dedicated discovery and routing logic is added to NFs for roaming scenarios, then roaming communication can be supported, but the ease of operation and implementation difficulty worsen
Solution Approach 1:
The discovery and routing logic is extracted from the NFs and centralized in the DNS server. NFs only need to perform simple FQDN-based service requests without implementing complex roaming detection or routing determination logic. The DNS server handles all the intelligence related to roaming scenarios, making NF implementation simpler and more uniform across different vendors and scenarios
Solution Approach 2:
The DNS server autonomously determines whether a service request is for roaming or non-roaming based on the FQDN and the requester's PLMN context. The system self-adapts to roaming scenarios without requiring NFs to actively detect or indicate roaming conditions, thereby reducing implementation complexity while maintaining full roaming capability
3Device complexity
If FQDNs are used for NF registration and provisioning instead of IP addresses, then the complexity of NF registration is reduced, but additional DNS configuration and management overhead is introduced
Solution Approach 1:
The patent combines multiple functions into the DNS server: standard domain name resolution, NF service discovery, and roaming routing determination. By merging these functions, the DNS server becomes a single point of configuration that handles both domestic and international service requests, thereby reducing the overall provisioning overhead compared to having separate mechanisms for each function
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and apparatus for configuring a service based architecture for discovery of a Network Function, NF. A method in a Network Function Discovery Orchestration comprises configuring, in a domain name system, DNS, a first DNS entry associating a first domain name of the NF with at least one NF Internet Protocol, IP, address of the NF, and a second DNS entry associating the first domain name with at least one edge security node IP address of an edge security node in the first PLMN, wherein, the first DNS entry is for use in resolving requests for the NF which originate from within the first PLMN, and the second DNS entry is for use in resolving requests for the NF which originate from outside the first PLMN. Further methods and apparatus in a Network Repository Function, a Domain Name System and an edge security node are also provided.