Edge DNS Mediation Service for IoT Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IoT devices experience high latency when communicating with cloud-based applications due to long-distance, high-latency links, making it impractical to use cloud computing resources.

Innovation Solution

Implementing an Edge DNS Mediation Service (EDMS) that intercepts DNS requests from IoT devices and routes traffic directly to an optimal edge network, eliminating the need for cloud-based DNS systems and reducing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If IoT devices communicate with cloud-based applications over long-distance links, then computing and storage facilities are available, but significant latency is experienced

Engineering Contradiction:
Improveavailability of computing and storage facilitiesVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system segments the centralized cloud infrastructure into distributed edge computing nodes deployed geographically closer to IoT devices. This segmentation allows devices to access computing and storage facilities locally rather than over long-distance links, reducing latency while maintaining availability through multiple distributed access points.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an Edge DNS Mediation Service as an intermediary between IoT devices and edge computing resources. This mediator intercepts DNS requests, determines optimal edge instances based on device location and service requirements, and routes traffic accordingly, enabling efficient access to distributed edge facilities without direct device configuration changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If cloud-based DNS systems are used for IoT devices, then centralized management is maintained, but traffic routing efficiency is reduced due to long-distance communication

Engineering Contradiction:
Improvecentralized DNS managementVSAvoidtraffic routing efficiency
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The system performs preliminary actions by pre-configuring edge DNS mediation services at distributed edge locations with knowledge of available computing and storage facilities. When DNS requests are intercepted, the pre-positioned edge DNS services can immediately determine optimal routing based on stored facility information and current device location, eliminating the need for real-time communication with centralized cloud DNS systems.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If edge computing resources are used, then latency is reduced, but device configuration changes are required

Engineering Contradiction:
ImprovelatencyVSAvoiddevice configuration
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The Edge DNS Mediation Service implements self-service by autonomously intercepting DNS requests from IoT devices, determining optimal edge instances based on device identity and location, and routing traffic without requiring any configuration changes on the devices. The system automatically manages the steering logic and facility mapping, freeing devices from configuration complexity while achieving low-latency access.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12335828B2Systems and methods for device traffic steering using edge DNS mediation service (EDMS)
Publication Date: 2025.06.17 VERIZON PATENT & LICENSING INC
  • US12335828B2 patent drawing
  • US12335828B2 patent drawing
  • US12335828B2 patent drawing

AI summary

A method may include storing, at a network device, a user device identifier associated with a user device that has subscribed to access an edge service, an edge service identifier associated with the edge service, and an edge device identifier associated with an edge device at an edge network to provide the edge service; receiving, at the network device, a request to access the edge service, wherein the request includes the user device identifier and the edge service identifier; performing, by the network device, a lookup to determine the edge device identifier; and transmitting, by the network device and to the user device, the edge device identifier for accessing the edge service at the edge device.