DNS Server Caching for Content Delivery Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Information-Centric Networking (ICN) architectures face challenges such as reliance on caching in dense populations, unstructured namespaces leading to ambiguity in content provider authority, and lack of secure key discovery and verification mechanisms.

Innovation Solution

The Domain Name Data Networking (DNDN) system leverages DNS infrastructure to store and retrieve content by name, utilizing DNS servers for caching and security, enabling efficient content delivery, secure key management, and scalable name management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If ICN architectures use caching in dense populations, then content delivery efficiency is improved, but device complexity and deployment difficulty increase

Engineering Contradiction:
Improvecontent delivery efficiencyVSAvoiddeployment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces DNS servers as intermediary nodes that perform caching functions. Instead of requiring every network node to implement complex ICN caching logic, DNS servers act as mediators that cache content objects and their associated names, simplifying the overall system architecture while maintaining content delivery efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes DNS servers multi-functional by enabling them to perform both traditional DNS resolution and ICN caching operations. This allows existing DNS infrastructure to serve dual purposes, reducing deployment complexity while improving content delivery efficiency through caching.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If ICN uses unstructured namespaces, then content provider flexibility is improved, but name resolution ambiguity increases

Engineering Contradiction:
Improvecontent provider flexibilityVSAvoidname resolution ambiguity
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where DNS servers verify name-to-content mappings and provide authoritative responses. When a content object is cached, the associated name is stored in the DNS zone file, and the DNS server can verify and resolve names authoritatively, eliminating ambiguity while preserving provider flexibility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Content providers can self-assign names to their content objects and publish these mappings in DNS zone files. The DNS infrastructure then automatically manages the name resolution process, providing structured verification without restricting provider flexibility in name assignment.

Inventive Principle:
Principle #25Self-service

3Reliability

If ICN implements data-centric security, then content authenticity is improved, but key discovery and verification complexity increases

Engineering Contradiction:
Improvecontent authenticityVSAvoidkey management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces DNS servers as intermediary trust anchors for key verification. Instead of requiring end systems to directly discover and verify content provider keys, DNS servers act as mediators that store and verify cryptographic keys associated with domain names, simplifying the key management process while maintaining authenticity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts key management functions from individual content delivery systems and centralizes them in DNS servers. By taking out the complex key discovery and verification processes and consolidating them in authoritative DNS infrastructure, the overall system complexity is reduced while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

4Loss of energy

If DNS servers cache content objects, then network overhead is reduced, but memory resource requirements increase

Engineering Contradiction:
Improvenetwork overheadVSAvoidmemory resources
Core Design Contradiction:
Loss of energyVSQuantity of substance

Solution Approach 1:

The patent implements partial caching where DNS servers cache content objects selectively based on demand and available resources. Instead of caching all possible content, the system caches only frequently accessed or strategically important content objects, reducing memory requirements while still achieving network overhead reduction for cached items.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent implements dynamic caching policies where DNS servers adjust their caching behavior based on available memory resources, access patterns, and content priorities. The caching capacity and strategy adapt dynamically to system conditions, optimizing the balance between network overhead reduction and memory resource consumption.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11824829B2Methods and systems for domain name data networking
Publication Date: 2023.11.21 VERISIGN INC
  • US11824829B2 patent drawing
  • US11824829B2 patent drawing
  • US11824829B2 patent drawing

AI summary

Systems, devices and methods for a Domain Name Data Networking (DNDN) content delivery system are disclosed. Embodiments perform operations including obtaining a content object having a unique identifier. The operations also include storing a local instance of the content object in association with DNS resource records and the unique identifier. The operations further include providing the local instance of the content to a client in response to receiving a request from the client including the unique identifier.