IoT Service Discovery via DNS-SD TXT Field
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In IoT networks, existing methods require significant reconfiguration of IoT sensors/actuators when network service addresses change, leading to substantial effort and inefficiency in service discovery and connection.
Innovation Solution
A method utilizing DNS-SD via mDNS for IoT devices to dynamically identify and connect to network services using application-layer service identifiers, eliminating the need for IP address reconfiguration by incorporating service identifiers in the TXT field of mDNS responses, allowing decentralized and efficient service discovery and connection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If DNS-SD compliant response includes application-layer service identifier in TXT field, then service identification accuracy is improved, but response data volume increases
Solution Approach 1:
The patent extracts the application-layer service identifier from the general DNS response data by utilizing the TXT field specifically for this purpose. This allows the service identifier to be separated and transmitted independently within the existing DNS-SD framework, improving identification accuracy without requiring a complete redesign of the response structure.
Solution Approach 2:
The TXT field in DNS-SD responses, which is optionally used according to standards, is repurposed to carry application-layer service identifiers. This multi-functional use of the existing TXT field allows it to serve both its original optional purposes and the new function of providing precise service identification, avoiding the need for additional dedicated fields.
2Reliability
If IoT sensors/actuators are reconfigured when network service address changes, then connection accuracy is maintained, but configuration effort increases
Solution Approach 1:
The system enables IoT sensors and actuators to automatically discover and connect to network services using DNS-SD with mDNS without requiring manual reconfiguration. The devices self-service their own service discovery and connection establishment, eliminating the need for user intervention when service addresses change, thus maintaining connection accuracy while eliminating configuration effort.
Solution Approach 2:
The patent implements dynamic service discovery where IoT devices can automatically adapt to changing network service addresses through continuous DNS-SD queries. Instead of static configuration that requires updates when addresses change, the system dynamically resolves service addresses at runtime, allowing automatic adaptation to address changes without manual reconfiguration.
3Reliability
If mapping tables are used for service address resolution, then connection reliability is improved, but system complexity increases
Solution Approach 1:
The patent replaces the mechanical approach of manually maintained mapping tables with an automated DNS-SD resolution system. Instead of using static tables that require manual updates and synchronization, the system uses standardized DNS queries and responses to dynamically resolve service addresses, eliminating the need for complex mapping table management while maintaining connection reliability.
Solution Approach 2:
The patent introduces DNS-SD as an intermediary mechanism between IoT devices and network services. Instead of direct mapping or hard-coded address resolution, the DNS-SD system acts as a mediator that automatically translates service names to addresses through standardized queries and responses, simplifying the overall system architecture while improving reliability through standardized protocols.
Data Source
AI summary
A method is provided for identifying network services in a network having at least one Internet-of-Things network subscriber, in particular Internet-of-Things sensors/actuators, based on domain name system service discovery DNS-SD via a multicast domain name system mDNS. A domain name system service discovery DNS-SD compliant request for a network service type is transmitted by an Internet-of-Things network subscriber to a network having at least one host that provides network services. At least one domain name system service discovery DNS-SD compliant response to the request is received from one of the hosts. The response comprises a text field having a network service identifier. A connection request is transmitted by the Internet-of-Things network subscriber to the host to which the network service identifier is assigned and which provides the desired network service.