Router Node Cross-Subnet Service Discovery via Consensus Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional mDNS/DNS-SD functionality is limited to operating within a single local link, making it ineffective in small multi-subnet networks like wireless mesh networks, where devices connected to different access points cannot discover services across links, and complex domain management is required.
Innovation Solution
A router node equipped with a transceiver and signal processor supporting a consensus protocol, such as DNCP or HNCP, caches and distributes mDNS resource records across the network, allowing service discovery across multiple subnets without the need for domain enumeration or separate domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If mDNS operates only in the local link, then service discovery works within a single LAN segment, but service discovery fails across multiple subnets in mesh networks
Solution Approach 1:
The patent segments the service discovery function by introducing a dedicated service discovery router node that operates independently from client devices. This router node receives mDNS queries from clients, forwards them to the appropriate subnet, and returns results, thereby enabling cross-subnet service discovery while maintaining local mDNS operation integrity.
Solution Approach 2:
The service discovery router node acts as an intermediary between clients in one subnet and services in another subnet. It receives mDNS queries from clients, translates them into appropriate multicast queries for the target subnet, and relays the responses back to the originating client, thus mediating cross-subnet communication without requiring changes to client or service devices.
2Adaptability or versatility
If conventional DNS is used with manual configuration, then service discovery can work across networks, but network management complexity increases requiring IT professionals
Solution Approach 1:
The system enables self-service by allowing the service discovery router node to automatically perform DNS-like service discovery functions without manual configuration. The router node autonomously receives mDNS queries, forwards them to appropriate subnets, and returns results, eliminating the need for manual DNS zone file configuration and IT professional intervention.
Solution Approach 2:
The patent merges the functionality of conventional DNS service discovery with mDNS by having the service discovery router node handle both types of queries. This integration allows the system to provide cross-network service discovery capabilities traditionally associated with DNS while maintaining the simplicity and automatic nature of mDNS, without requiring separate manual configuration systems.
3Adaptability or versatility
If mDNS queries are forwarded to remote subnets, then service discovery works across mesh networks, but network traffic increases
Solution Approach 1:
The service discovery router node performs preliminary actions by maintaining a cache of service information from previously discovered services in different subnets. When a client queries for services, the router first checks its cache and can provide results without forwarding the query to remote subnets, thereby reducing network traffic while still enabling cross-subnet service discovery.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A router node for a network is described. The router node comprises: a transceiver; an interface operably coupled to the transceiver; and a signal processor operably coupled to the transceiver and configured to support a consensus protocol. The signal processor is operably coupled to a cache and configured to receive and distribute resource records to other nodes in the network via the interface and store the resource records in the cache.