DNS Node Selection Using Location Information in ePDG Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The standard DNS mechanism for ePDG node selection in wireless communication systems relies on mapping source IP addresses to ePDGs, which does not utilize current location information, leading to unoptimized routing and negatively affecting the quality of service for voice calls.
Innovation Solution
Incorporating an enhanced DNS (eDNS) bit field in DNS request messages to convey location information, such as zip code, latitude/longitude, or last TAI, allowing the DNS server to select an appropriate ePDG based on this information, thereby optimizing routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standard DNS mechanism is used for ePDG node selection, then device complexity is reduced, but routing optimization is insufficient leading to degraded quality of service
Solution Approach 1:
The DNS request message is segmented to include separate fields: source IP address field and enhanced DNS bit field. The enhanced DNS bit field is further segmented to contain type indicator and location information, allowing the system to separate routing optimization functions from standard DNS operations while maintaining backward compatibility.
Solution Approach 2:
The enhanced DNS bit field acts as an intermediary mechanism that carries location information from the UE to the DNS server without disrupting the standard DNS request-response flow. This intermediary structure enables routing optimization while preserving the existing DNS protocol framework.
2Productivity
If location information is incorporated in DNS request messages, then routing optimization is improved, but message structure complexity increases
Solution Approach 1:
The enhanced DNS bit field is designed with multi-functionality: it can carry different types of location information (zip code, latitude/longitude, TAI) based on the type indicator, and can be optionally included in DNS requests. This universal structure handles various routing scenarios without requiring separate message formats for each location type.
Solution Approach 2:
The system changes the parameter representation by encoding location information in a compact enhanced DNS bit field with a type indicator. Instead of using full-length location parameters, the system uses condensed representations (e.g., TAI codes, abbreviated coordinates) that reduce message overhead while maintaining routing precision.
3Measurement precision
If eDNS bit field is used to convey location information, then node selection accuracy is improved, but information processing complexity increases
Solution Approach 1:
The UE performs preliminary action by determining its location information and encoding it in the enhanced DNS bit field before sending the DNS request. The DNS server performs preliminary parsing of the type indicator to identify the location format, preparing for optimized node selection before actual matching occurs. This preliminary processing reduces the complexity of real-time decision-making.
Solution Approach 2:
Instead of the DNS server querying the UE for location information, the inversion approach has the UE proactively providing location information in the DNS request. This reverses the traditional information flow, reducing the processing burden on the DNS server and enabling more precise node selection based on UE-provided data.
Data Source
AI summary
In some implementations, a domain name system (DNS) server may receive, from a user equipment (UE), a DNS request message that indicates location information. The DNS server may select a node for the UE based on the location information. The DNS server may transmit, to the UE, an indication of the node.