Local Network Device Identification via External Server DNS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for identifying and addressing devices in a local network, such as telephones in a home network, are unsatisfactory, especially for small devices without displays, as they rely heavily on gateway/router support and are resource-intensive, and licensing-dependent.
Innovation Solution
A method where a device in a local network logs onto a server (e.g., www.mygigaset.com) to transmit address/identification information, allowing users to access this information via a browser, enabling easy device configuration by redirecting to the internal IP address based on the external IP address shared by the server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DHCP service is used to make device name known at server, then device identification is improved, but dependency on gateway/router capability increases
Solution Approach 1:
The device autonomously performs DNS service by storing its own name and IP address information in its memory, eliminating the need for gateway/router DNS support. The device can independently provide identification services without relying on network infrastructure capabilities.
Solution Approach 2:
The DNS service function is extracted from the gateway/router and relocated to the device itself. By taking out the dependency on gateway/router DNS support, the device can independently manage its own identification and provide this information to users without infrastructure requirements.
2Ease of operation
If UPnP profile with broadcasts is used, then device addressability is improved, but implementation complexity and memory resources increase
Solution Approach 1:
The complex UPnP broadcast mechanism is replaced by a simple static DNS service implementation. Instead of using resource-intensive broadcasts and complex protocols, the device provides its identification information through a straightforward DNS service that stores name and IP address mappings, significantly reducing implementation complexity and memory requirements.
Solution Approach 2:
The invention uses a simple, lightweight DNS service implementation that replaces the heavy UPnP protocol stack. By using a minimalistic approach with basic DNS records stored in memory, the system achieves device addressability without the complexity and resource consumption of full UPnP implementation.
3Ease of operation
If device displays its own IP address, then identification is simplified, but device requirements for display capability increase
Solution Approach 1:
A web server acts as an intermediary between the device and the user. Instead of requiring the device to directly display its IP address, the web server provides a user-friendly interface where users can input the device name and receive the corresponding IP address, eliminating the need for display capabilities on the device itself.
Solution Approach 2:
The display function is extracted from the device and relocated to a web server. The device simply stores its identification information in memory, while the web server handles the user interaction and presentation, allowing devices without display capabilities to still be easily identified by users.
Data Source
AI summary
The invention relates to identifying and/or addressing a data terminal device (DEE1) of a local network (LNW, LAN, W-LAN, Ethernet, Powerline) such that address/identification information (AID-INF3) of the data terminal device of the local network is available to a user of the local network in a simple and comfortable manner, wherein the data terminal device registers with a terminal system (ESY) due to a triggering event (ALE), indicated for example, by the URL ‘www.mygigaset.com’ and present, for example, in a large area network (GNW, WAN, MAN, INTERNET), and transmits thereto address/identification information, for example modifiable information (AID-INF1), referencing the local network and the large area network. Said address/identification information is stored by the terminal system. Subsequently, in a further data terminal device (DEE2) of the local network, the URL ‘www.mygigaset.com’ is entered into the terminal system, a connection is established with the terminal system, and address/identification information, for example modifiable information (AID-INF2), referencing the large area network is transmitted. The terminal system compares the transmitted address/identification information (AID-INF1, AID-INF2) to each other, and transmits to the further data terminal device a part of the address/identification information (AID-INF1) referring back to the local network as the address/identification information (AID-INF3) of the data terminal device (DEE1), because both data terminal devices are present in the same local network, in order that said data terminal device can communicate directly with the data terminal device (DEE1).