DNS Discoverer Micro-Service for 4G Endpoint Address Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications networks face challenges in actively discovering and maintaining address information for 4G service endpoints, particularly due to insufficient information for load balancing and the burden on consumer NFs to directly query DNS servers for IP address changes, scaling events, and DNS server availability.
Innovation Solution
A DNS discoverer micro-service is implemented, separate from consumer NFs or SCPs, which receives DNS resolution requests, stores address information with TTL, monitors FQDNs for changes, and notifies consumers of updates, using a REST server interface and database to manage and track IP addresses associated with 4G service endpoints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If consumer NFs directly query DNS servers to discover IP address changes, then IP address information can be obtained, but the complexity and burden on consumer NFs increases
Solution Approach 1:
The patent introduces a DNS discoverer micro-service as an intermediary between consumer NFs and DNS servers. This micro-service actively queries DNS servers for IP address changes and pushes notifications to consumer NFs, eliminating the need for consumer NFs to directly communicate with DNS servers and maintain timers. The intermediary handles DNS protocol complexity and timing management, simplifying the consumer NF implementation while maintaining reliable IP address discovery.
Solution Approach 2:
The DNS discoverer micro-service autonomously performs DNS queries, monitors IP address changes, and actively pushes notifications to consumers without requiring them to initiate repeated queries. The system self-manages the discovery process, including handling TTL expiration and detecting scaling events, thereby reducing the operational burden on consumer NFs while ensuring reliable address information updates.
2Reliability
If consumer NFs maintain timers for DNS response expiration, then IP address updates can be detected, but the operational complexity and resource consumption increases
Solution Approach 1:
The DNS discoverer micro-service acts as an intermediary that assumes responsibility for maintaining timers and scheduling DNS queries. Instead of each consumer NF managing its own timers and query schedules, the micro-service centrally manages timing for all consumers, simplifying operational complexity while ensuring reliable detection of IP address updates through systematic TTL-based re-querying.
Solution Approach 2:
The system implements a centralized copy of the timer management functionality within the DNS discoverer micro-service. Rather than duplicating timer maintenance logic in every consumer NF, a single instance manages timing for all consumers and distributes updated IP address information, reducing operational complexity while maintaining update reliability across the system.
3Reliability
If each consumer NF reconfigures when DNS server changes occur, then connectivity is maintained, but the system adaptability and automation decreases
Solution Approach 1:
The DNS discoverer micro-service implements a feedback mechanism where it actively monitors DNS server availability and detects changes in DNS server addresses. When changes are detected, the micro-service automatically updates its configuration and pushes notifications to consumer NFs, eliminating the need for manual reconfiguration. This feedback loop enhances system adaptability to DNS server changes while maintaining reliable connectivity.
Solution Approach 2:
The system performs preliminary detection and configuration updates through the DNS discoverer micro-service before consumer NFs are affected by DNS server changes. By proactively monitoring DNS server status and pre-updating configurations, the system maintains connectivity without requiring reactive manual reconfiguration of individual consumer NFs, thereby improving adaptability while ensuring reliability.
4Ease of manufacture
If producer NFs register only FQDN without individual IP addresses, then service registration is simplified, but load balancing capability deteriorates
Solution Approach 1:
The system segments the service registration process into two independent parts: (1) Producer NFs register only FQDN at the service level, keeping registration simple; (2) The DNS discoverer micro-service separately discovers and manages multiple IP addresses associated with each FQDN through active DNS queries. This segmentation allows simplified registration while enabling load balancing across multiple discovered IP addresses, as the micro-service retrieves all associated addresses and can distribute traffic appropriately.
Solution Approach 2:
The DNS discoverer micro-service acts as an intermediary that bridges the gap between simplified FQDN-only registration and load balancing requirements. It actively queries DNS servers to resolve FQDNs into multiple IP addresses, maintains the mapping between FQDNs and their associated addresses, and provides this information to consumer NFs for load balancing purposes. This intermediary enables both registration simplicity and effective load balancing without requiring producer NFs to manually register individual IP addresses.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
A method for discovering and tracking addresses associated with 4G service endpoints includes receiving, from a requesting node, a first domain name system (DNS) resolution or monitoring request including a fully qualified domain name (FQDN) of a 4G service endpoint. The method further includes querying a DNS server using the FQDN from the first DNS resolution or monitoring request. The method further includes receiving, from the DNS server, a first response including an address associated with the 4G service endpoint and storing the address associated with the 4G service endpoint in a database. The method further includes communicating the address associated with the 4G service endpoint to the requesting node. The method further includes monitoring the FQDN for changes in address associated with the FQDN. The method further includes notifying the requesting node of the changes in address associated with the FQDN.