DNS Override for Edge Computing Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication systems, such as LTE and NR, face challenges in efficiently managing DNS requests, leading to increased latency and strain on networks, as applications typically resolve domain names to remote content servers rather than edge content servers, which can reduce the benefits of edge computing.

Innovation Solution

The method involves intercepting DNS requests from applications and overriding the destination address to an edge DNS server, and upon successful response, changing the source address back to the core DNS server, allowing applications to access cached content from edge servers without being aware of the change, thereby reducing latency and network strain.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If DNS requests are sent to remote DNS servers, then applications can resolve domain names to remote content servers, but latency increases and network strain increases

Engineering Contradiction:
ImproveDNS resolution latencyVSAvoidnetwork efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The patent introduces an edge DNS server as an intermediary between the application and the remote DNS server. The edge DNS server intercepts DNS requests locally at the network edge, resolves them to edge content servers, and returns the results to the application. This intermediary approach eliminates the need for applications to directly contact remote DNS servers, thereby reducing latency and network strain while maintaining transparent DNS resolution functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary action by pre-positioning DNS servers at the network edge before content delivery occurs. The edge DNS server is already in place and ready to intercept and resolve DNS requests locally, eliminating the need for applications to traverse the entire network to reach remote DNS servers. This preliminary positioning of DNS resolution capability at the edge reduces both latency and network load.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If DNS requests are intercepted and redirected to edge DNS server, then latency is reduced and edge computing benefits are achieved, but application transparency may be compromised

Engineering Contradiction:
ImproveDNS resolution latencyVSAvoidapplication transparency
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The edge DNS server acts as an invisible intermediary that transparently intercepts and resolves DNS requests. The application continues to use standard DNS resolution mechanisms without modification, while the edge DNS server silently redirects requests to appropriate edge content servers. This intermediary approach maintains application transparency by preserving the standard DNS interaction model while achieving the performance benefits of edge computing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements copying by creating a local copy of DNS resolution capability at the network edge. The edge DNS server replicates DNS resolution functionality locally, allowing requests to be resolved without contacting remote servers. This copying of DNS functionality to the edge enables transparent local resolution while maintaining compatibility with standard DNS protocols and application expectations.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP4115596B1Domain name system (DNS) override for edge computing
Publication Date: 2024.04.10 QUALCOMM INC
  • EP4115596B1 patent drawingFigure 1
  • EP4115596B1 patent drawingFigure 2
  • EP4115596B1 patent drawingFigure 3

AI summary

Certain aspects of the present disclosure provide techniques for a domain name system (DNS) override for edge computing. Embodiments include receiving signaling indicating an address of a DNS server. Embodiments include receiving signaling indicating an address of an edge DNS server. Embodiments include intercepting a DNS request from an application. Embodiments include changing a destination address of the DNS request to the address of the edge DNS server. Embodiments include intercepting a DNS response from the edge DNS server that is sent in response to the DNS request. Embodiments include upon determining that the DNS response does not comprise a failure notification, changing a source address of the DNS response to the address of the DNS server.