Service Discovery Server Shared Space for Ad-Hoc Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In ad-hoc networks, discovering IP addresses through DNS is challenging, especially for components with arbitrary IP addresses that do not maintain a single IP address, making it difficult for clients to communicate across multiple networks.
Innovation Solution
A discovery apparatus and method that creates a shared space on a server for clients to jointly use intrinsic information like IP addresses, names, and port numbers, allowing discovery and communication between clients across multiple networks, even those not registered in DNS, using a transceiver, storage unit, and controller to manage shared information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DNS is used for discovering IP addresses, then components with fixed IP addresses can be identified, but components with arbitrary IP addresses in ad-hoc networks cannot be discovered
Solution Approach 1:
The patent introduces a service discovery server as an intermediary between clients. The server maintains a shared space that stores mapping information between component names and IP addresses. Clients query this shared space to discover other components, eliminating the need for direct DNS reliance and enabling discovery of components with arbitrary IP addresses through the intermediary's centralized registration mechanism.
Solution Approach 2:
The service discovery server provides universal discovery functionality across different network types (ad-hoc networks, wired networks) and component types. The shared space serves multiple clients simultaneously, allowing any component registered with the server to be discovered by any other client, making the system universally applicable regardless of network configuration or component IP address assignment method.
2Adaptability or versatility
If DNS registration is required for component discovery, then structured naming can be maintained, but components not registered in DNS cannot be discovered
Solution Approach 1:
The patent implements self-service by allowing components to automatically register their own information with the service discovery server. When a component joins a network, it autonomously sends its name and IP address to the server, which then stores this information in the shared space. This eliminates the need for manual DNS administration and allows any component to be discovered without prior registration configuration.
Solution Approach 2:
The system dynamically adapts to component加入 and departure events. When components join or leave the network, their registration status in the shared space is automatically updated. This dynamic mechanism allows the discovery system to adapt to changing network topologies and component configurations without requiring static DNS records, enabling discovery of components that would traditionally require manual registration.
3Reliability
If components maintain fixed IP addresses, then DNS resolution works reliably, but components with changing IP addresses cannot be consistently discovered
Solution Approach 1:
The service discovery server implements feedback mechanisms by automatically updating the shared space when components change their IP addresses or join/leave the network. The server receives feedback about component status changes from network events and proactively updates the mapping information. This feedback loop ensures that clients always receive current and accurate IP address information, maintaining discovery reliability even when components use dynamic or changing IP addresses.
Data Source
AI summary
A discovery apparatus among a plurality of networks including at least one client includes: a transceiver which transmits and receives shared information and a request message to and from the client within the plurality of networks, the shared information being intrinsic information of the clients; a storage unit which receives the shared information from the transceiver and stores the shared information of the transceiver; and a controller which creates a shared space, which stores the shared information in the storage unit, in accordance with the request message received through the transceiver, and manages the shared information stored in the shared space.