DNS Server User-Defined Line Routing for Grayscale User Positioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DNS systems face challenges in accurately positioning grayscale users for service platforms, especially when users are divided by different operators or regions, making it difficult to manage and monitor their access effectively.
Innovation Solution
A method and system that utilize user-defined lines to define specific IP address ranges, allowing for more precise targeting of users within those ranges by presetting parsing records to direct terminals to corresponding target servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If users are divided based on operators or regions, then network access management is simplified, but positioning accuracy of grayscale users deteriorates
Solution Approach 1:
The patent segments the user classification system into multiple hierarchical levels: first by operator/region (coarse segmentation), then by user-defined lines within each segment (fine segmentation). This multi-level segmentation allows both simplified management at each level and accurate positioning when combining levels, resolving the contradiction between management simplicity and positioning accuracy.
Solution Approach 2:
The patent adds a new dimension (user-defined line dimension) to the existing classification system. Instead of relying solely on operator/region dimensions, it introduces a third dimension that enables precise user identification. This dimensional expansion allows the system to maintain simple management through hierarchical structure while achieving accurate positioning through multi-dimensional matching.
2Measurement precision
If user-defined lines are introduced for precise user positioning, then positioning accuracy improves, but system complexity increases
Solution Approach 1:
The patent implements preliminary action by pre-defining user-defined lines and their corresponding IP address ranges before actual user access. The DNS server is pre-configured with parsing records that map user-defined lines to specific target servers. This preliminary setup eliminates the need for complex real-time calculations during user access, reducing operational complexity while maintaining high positioning accuracy.
Solution Approach 2:
The patent introduces user-defined lines as an intermediary layer between the terminal and target server. Instead of direct complex matching between terminal IP and target server, the user-defined line acts as a mediator that simplifies the matching process. The DNS server uses this intermediary to resolve domain names to appropriate IP addresses, reducing system complexity while improving positioning accuracy.
3Device complexity
If traditional DNS parsing is used, then system simplicity is maintained, but service delivery flexibility deteriorates
Solution Approach 1:
The patent makes the DNS server multi-functional by enabling it to perform both traditional DNS resolution and user-defined line-based routing. The same DNS server infrastructure handles standard domain name resolution while also supporting customized service delivery through user-defined lines. This universality maintains system simplicity by using existing infrastructure while enhancing service delivery flexibility through additional functionality.
Solution Approach 2:
The patent introduces dynamics by making the DNS parsing process adaptable to different service requirements. Through user-defined lines, the system can dynamically route different users or user groups to different target servers based on service needs. This dynamic capability allows the system to maintain simplicity in structure while achieving flexibility in service delivery through configurable routing rules.
Data Source
AI summary
Embodiments of this application disclose a method for parsing a service platform address by a server. The server receives a DNS parsing request sent by a terminal, the DNS parsing request including a to-be-parsed domain name. The server then obtains target IP information of the terminal based on the DNS parsing request. When the target IP information has a corresponding target user-defined line, the server obtains a preset first parsing record based on the target user-defined line. The server then sends to the terminal a first IP address corresponding to the to-be-parsed domain name based on the preset first parsing record. As such, a corresponding IP address range can be defined using a user-defined line, so that a terminal within the IP address range can obtain a specific IP address corresponding to an access domain name, and provide a service to a user within a more accurate range.