Multipath Domain Name Resolution via Query Duplication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current domain name resolution methods in multipath-access scenarios are inefficient due to sequential querying, potential conflicts between name servers, and reliance on a single access path, leading to delays and reduced reliability.

Innovation Solution

A method that generates and sends duplicated domain name queries to multiple name servers via different access paths, allowing for simultaneous responses and improved reliability by selecting the fastest or highest-priority response.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single DNS request is sent over one access path to a preferred name server, then the device follows a simple sequential querying process, but this leads to extra delay when other name servers could respond faster

Engineering Contradiction:
Improvedomain name resolution speedVSAvoidDNS query delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by sending multiple DNS queries to different name servers simultaneously before knowing which one will respond fastest. The access device pre-duplicates the initial domain name query into multiple multiplied queries and sends them in parallel to different name servers via different access paths, so that the fastest response is received without waiting for sequential queries to exhaust other options.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies partial or excessive action by sending more DNS queries than the traditional single query approach. Instead of sending one query to one preferred name server, the system sends multiple queries to multiple name servers (including preferred and non-preferred ones) simultaneously, using more resources (multiple queries) to achieve better performance (faster resolution).

Inventive Principle:
Principle #16Partial or excessive action

2Loss of information

If multiple name servers hold different information on a query, then comprehensive information is available, but conflicts arise in determining the most suitable IP address

Engineering Contradiction:
Improvename server information completenessVSAvoidIP address determination consistency
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent applies feedback by implementing a selection mechanism that receives responses from multiple name servers and evaluates them according to predefined criteria. The access device compares the multiple responses and selects the most suitable one based on factors such as response time, name server priority, and information validity, providing feedback-based decision making to resolve conflicts between different name server responses.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies parameter changes by introducing multiple evaluation parameters for selecting among multiple name server responses. Instead of accepting any response, the system changes the selection criterion from simple first-come-first-served to multi-parameter evaluation including response time, name server priority, and information consistency, thereby resolving conflicts through parameter-based decision making.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11374896B2Domain name request multiplication for multipath-access
Publication Date: 2022.06.28 DEUTSCHE TELEKOM AG
  • US11374896B2 patent drawing
  • US11374896B2 patent drawing

AI summary

A method for domain name resolution includes: requesting, by an access device, via a resolving request, an IP address based on a present domain name or a domain name based on a present IP address, wherein the access device is configured to have multipath access to a data network via at least two access paths; generating, by the access device, an initial domain name query based on the resolving request; duplicating, by the access device, the initial domain name query into at least two multiplied domain name queries; sending, by the access device, each of the at least two multiplied domain name queries to a respective name server; and receiving, by the access device, a domain name response comprising the requested IP address or the requested domain name from each respective name server.