DNS Sampling for Client Discovery and Cache Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In content distribution networks (CDNs), existing systems struggle to optimize routing of client requests to the closest cache server and properly load balance among multiple cache servers due to the authoritative DNS server's lack of awareness about the number of client systems served by a local DNS server, their location, and ingress points, leading to potential disruptions and inefficiencies.

Innovation Solution

A system and method that utilize a tracking IP address to collect and analyze content request data, allowing for the determination of client system characteristics served by a local DNS server, which is then used to optimize routing and load balancing among cache servers by providing information to the authoritative DNS server and route controller.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the authoritative DNS server lacks awareness about client systems served by local DNS servers, then the system structure remains simple and decentralized, but routing optimization and load balancing cannot be effectively implemented

Engineering Contradiction:
Improverouting optimizationVSAvoidDNS server awareness structure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a sampling-based intermediary mechanism where the authoritative DNS server periodically samples local DNS servers to gather information about client systems. This intermediary sampling process allows the authoritative server to obtain routing and load balancing information without requiring continuous awareness or direct tracking of all client systems, thus resolving the contradiction between routing optimization and system complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of requiring complete awareness of all client systems, the patent applies partial action by having the authoritative DNS server sample only a subset of local DNS servers and their client information. This partial sampling provides sufficient data for routing optimization and load balancing decisions without the overhead of complete system awareness, effectively resolving the technical contradiction

Inventive Principle:
Principle #16Partial or excessive action

2Productivity

If complete client system information is collected and tracked, then routing and load balancing can be optimized, but system complexity and resource consumption increase

Engineering Contradiction:
Improvecontent delivery efficiencyVSAvoidinformation collection system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements partial action by collecting only sampled information from a subset of client systems through periodic sampling of local DNS servers. This partial information collection provides sufficient data for routing and load balancing optimization without requiring complete tracking of all client systems, thus improving content delivery efficiency while limiting system complexity

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The authoritative DNS server performs periodic sampling of local DNS servers rather than continuous monitoring. This periodic action allows the system to update routing and load balancing information at intervals, achieving good content delivery efficiency while significantly reducing the complexity and resource consumption associated with continuous information collection

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS8650282B2Systems and method to discover clients associated with local domain name server using sampling
Publication Date: 2014.02.11 AT&T INTELLECTUAL PROPERTY I L P
  • US8650282B2 patent drawing
  • US8650282B2 patent drawing
  • US8650282B2 patent drawing

AI summary

A system includes an analyzer module, a content request data collection module, and a domain name server. The content request data collection module is configured to receive a content request sent to a tracking address, collect content request information about the content request, and provide the content request information to the analyzer module. The domain name server is configured to receive an address request from a local domain name server for a cache server address, provide a tracking address to the local domain name server, collect address request information about the address request, and provide the address request information to the analyzer module. The analyzer module is configured to receive the address request information and the content request information, and determine properties of clients served by the local domain name server based on the address request information and the content request information.