DNS over CoAP Mapping for IoT Connectivity

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods face challenges in providing end-to-end reachability and security for Domain Name System (DNS) communications, particularly in Internet of Things (IoT) scenarios where constrained devices may not support native DNS, leading to connectivity issues and vulnerabilities.

Innovation Solution

The solution involves encoding DNS queries and responses in Constrained Application Protocol (CoAP) messages using a mapping scheme, enabling DNS functionality over CoAP and employing Datagram Transport Layer Security (DTLS) for integrity and confidentiality, thus facilitating end-to-end DNS connectivity in IoT scenarios where native DNS is not supported.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If DNS is used for name resolution in IoT scenarios, then domain name lookup capability is provided, but connectivity issues and security vulnerabilities occur due to lack of native DNS support in constrained devices

Engineering Contradiction:

Improvedomain name lookup capabilityVSAvoidconnectivity and security

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces CoAP as an intermediary protocol to enable DNS functionality over constrained networks. Instead of requiring native DNS support in constrained devices, the system uses CoAP messages with custom options to carry DNS queries and responses, providing reliable connectivity and security through CoAP's built-in mechanisms while maintaining domain name lookup capability

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the protocol parameters by mapping DNS protocol elements (queries, responses, resource records) onto CoAP message structures. This parameter transformation allows DNS functionality to operate over CoAP, resolving the contradiction between adaptability and reliability by adapting DNS to work within CoAP's more reliable and secure framework

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If native DNS is implemented in constrained devices, then DNS functionality is available, but device complexity and resource consumption increase

Engineering Contradiction:

ImproveDNS functionalityVSAvoiddevice complexity and resource consumption

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes CoAP universally applicable by extending it to handle DNS functionality in addition to its original purposes. By defining custom CoAP options for DNS operations, the system allows a single protocol to serve multiple functions, eliminating the need for separate native DNS implementation in constrained devices and thereby reducing device complexity

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent creates a simplified copy of DNS functionality that operates over CoAP. Instead of implementing the full DNS protocol stack in constrained devices, the system uses CoAP messages that replicate DNS query and response structures, providing DNS capability with minimal device complexity by leveraging the existing CoAP infrastructure

Inventive Principle:

Principle #26Copying

3Reliability

If DNS over CoAP is implemented, then end-to-end DNS connectivity is achieved in constrained environments, but protocol complexity increases due to mapping requirements

Engineering Contradiction:

Improveend-to-end DNS connectivityVSAvoidprotocol mapping complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the DNS protocol operations into distinct CoAP message components, with specific custom options for different DNS functions (queries, responses, resource records). This segmentation provides clear structure and reliability while managing complexity through systematic organization of mapping rules for each segment

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12143355B2Node, another node, and methods performed thereby for supporting domain name system over constrained application protocol

Publication Date: 2024.11.12 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

A method performed by a node (111) supporting operation on a Constrained Application Protocol (CoAP), but incapable of supporting operation on a Domain Name System (DNS) protocol. The node (111) encodes (402) a DNS query into a first message (601, 701), which has a format supported by the CoAP. The DNS query is mapped to the CoAP format of the first message (601, 701) based on a mapping scheme. The node (111) then initiates sending (403) the first message (601, 701) to another node (112) operating in the communications network (100). The another node (112) supports operation on the CoAP and on the DNS protocol. The node (111) finally receives (404) a second message (620, 706) from the another node (112), which has the format supported by the CoAP. The second message (620, 706) comprises the DNS response to the sent DNS query. The DNS response is mapped to the CoAP format of the second message (620, 706) based on the mapping scheme.