Dynamic DNS Service Discovery Metadata Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DNS-based Service Discovery (DNS-SD) techniques often return a list of all device instances capable of providing a service within a large network domain, which can include irrelevant devices, leading to unnecessary scope and inefficiency, especially in decentralized multi-cast DNS environments where the scope is limited to the local network.
Innovation Solution
The implementation of dynamic DNS-SD techniques that utilize metadata associated with the requesting device to filter and refine the search scope, allowing the DNS server to selectively return only relevant service-providing devices based on pre-defined selection rules and constraints, thereby restricting service discovery to a specific logical domain or subset within the query's specified domain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standard DNS-SD returns all service-providing devices in the domain, then completeness of service discovery is improved, but relevance and efficiency deteriorate due to inclusion of irrelevant devices
Solution Approach 1:
The patent segments the service discovery process by introducing metadata-based filtering that divides the broad domain search into targeted sub-domain searches. The DNS server segments the response by including only services matching the requester's metadata criteria, effectively partitioning the service space from a complete but overwhelming list to a relevant subset.
Solution Approach 2:
The patent applies preliminary action by performing metadata-based filtering at the DNS server before returning results. The server pre-processes the service list by comparing against requester metadata (location, device type, user preferences) and filters out irrelevant services before transmission, so the client receives only pre-filtered relevant results rather than filtering itself.
2Adaptability or versatility
If DNS-SD searches the entire domain, then scope of discovery is improved, but loss of time and energy increases due to processing irrelevant devices
Solution Approach 1:
The DNS server performs preliminary filtering based on metadata before returning service lists. By pre-comparing service locations against requester metadata (building, floor, device type) and filtering out mismatches before response generation, the system maintains broad domain scope while eliminating time-wasting irrelevant results.
Solution Approach 2:
The patent applies local quality by making the service discovery scope adaptive to the specific requester's context. Different requesters with different metadata (location, device type, user preferences) receive differently filtered results tailored to their local needs, rather than a uniform complete list for all users.
3Measurement precision
If metadata-based filtering is implemented, then relevance of results is improved, but device complexity increases due to metadata processing requirements
Solution Approach 1:
The patent applies parameter changes by utilizing existing metadata parameters (location, device type, user preferences) that are already collected in DNS infrastructure. Rather than introducing complex new filtering mechanisms, the system changes the selection criteria from blanket inclusion to metadata-based parameter matching, achieving high relevance through relatively simple parameter comparison logic.
Data Source
AI summary
Techniques are provided for performing dynamic DNS-SD. In an embodiment, an apparatus includes one or more databases, one or more transceivers to receive a first Domain Name System (DNS) query from a first computing device, the first DNS query defining a first service discovery name space, and one or more processors in communication with each of the one or more databases and the one or more transceivers. The one or more processors generate and append a first metadata associated with the first computing device to the first DNS query. The one or more transceivers transmit the first DNS query and the first metadata to a Domain Name System (DNS) server computer, receive, from the DNS server computer, a first response responsive to the first DNS query, and relay, to the first computing device, the first response.