Remote Device Management via DNS Notification Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current remote access systems face challenges in efficiently managing increasing network sizes and user demands due to resource-intensive communication protocols, leading to scalability issues and high costs, particularly in maintaining persistent secured connections and frequent polling of remote access servers.
Innovation Solution
Implementing a secondary server, such as a DNS server, to handle lightweight communication protocols, reducing the need for expensive direct connections between remote devices and primary servers by using table entries to indicate communication requests, allowing devices to initiate connections only when necessary.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If devices maintain dedicated secured communication connections with the remote access server, then remote access reliability is improved, but resource consumption and system cost increase significantly
Solution Approach 1:
Devices periodically poll the DNS server for updates instead of maintaining continuous secured connections. The polling occurs at scheduled intervals, allowing devices to check for pending communications without keeping expensive SSL/TLS connections open constantly. This periodic action reduces resource consumption while maintaining the ability to receive remote access requests reliably.
Solution Approach 2:
A DNS server is introduced as an intermediary between devices and the remote access server. The DNS server receives communication requests from the remote access server and relays notification information to devices through standard DNS queries. This intermediary approach allows devices to be notified of pending communications without requiring direct secured connections to be maintained, reducing overall system resource consumption.
2Speed
If devices frequently poll the remote access server to check for communication requests, then responsiveness is improved, but the number of session connections and resource usage increase
Solution Approach 1:
The DNS server acts as an intermediary that absorbs the polling load. Devices poll the DNS server for notification information rather than directly polling the remote access server. The DNS server consolidates communication request information and delivers it to devices in response to standard DNS queries, reducing the burden on the remote access server while maintaining responsive communication.
Solution Approach 2:
The system uses DNS notification information as a copy or representation of communication request status. Instead of devices directly querying the remote access server for communication status, they query the DNS server for notification records that copy the essential information about pending communications. This copying mechanism reduces direct server interactions while preserving responsiveness.
3Use of energy by moving object
If the polling interval is increased to reduce session connections, then resource consumption decreases, but latency in responding to access requests increases
Solution Approach 1:
The DNS server provides feedback to devices about communication request status through notification information in DNS responses. When the remote access server has a pending communication request, it notifies the DNS server, which then includes notification information in DNS query responses to devices. This feedback mechanism allows devices to be promptly informed of communication requests without requiring frequent polling, balancing resource consumption with responsive latency.
Data Source
AI summary
A highly scalable primary server is provided to serve an increasing number of users and remote devices. Instead of communicating with a primary server using an expensive communication protocol, a remote device communicates with a secondary server using a less expensive protocol to determine whether the primary server desires to communicate control instructions to the remote device. When the primary server has a request to control the remote device, the primary server creates a table entry to the secondary server to notify the remote device of a request to communicate. Upon polling the secondary server and learning of the created table entry, the remote device establishes a communication connection with the primary server to receive the instructions for controlling the remote device. In this manner, the demand for resources needed for communication with the primary server is significantly reduced.