Remote Device Linking via Administration Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional remote surveillance and control technologies using Power Line Communication (PLC) are limited by the need for manual IP and domain name management, which is complex and vulnerable to hacker attacks, and lack expandability to accommodate varying device types and quantities.
Innovation Solution
A remote information communication system with an administration server that manages a list of linking servers and devices, allowing proximal devices to establish connections with remote devices through an API without needing to know their IP addresses or domain names, using a linking server to facilitate secure and scalable connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional PLC technology is used with manual IP and domain name management, then devices can be connected to the network, but the system becomes vulnerable to hacker attacks and requires complex manual management
Solution Approach 1:
The patent introduces an administration server as an intermediary that manages device registration and connection requests. The server maintains a database of registered devices and their identifiers, mediating all connections between proximal and remote devices. This eliminates the need for manual IP/domain name management while enhancing security through centralized authentication and identification management.
2Adaptability or versatility
If fixed IP addresses and domain names are used for device identification, then devices can be located and controlled, but the system lacks expandability when device types and quantities vary
Solution Approach 1:
The patent implements a dynamic device identification system where devices are assigned unique identifiers upon registration with the administration server. The server dynamically manages the device database, allowing new devices to be registered and existing devices to be updated without requiring fixed pre-configured IP addresses or domain names. This enables the system to adapt to varying device types and quantities while maintaining ease of operation through automated identifier management.
3Ease of operation
If device identifiers (IP addresses, domain names) are made public for access, then remote control is enabled, but the devices become exposed to hacker sniffing and attacks
Solution Approach 1:
The administration server acts as a secure intermediary that handles all device identification and authentication. Instead of exposing device identifiers publicly, the server receives connection requests from proximal devices, verifies them against the registered device database, and establishes secure connections. This mediation process enables remote access while protecting devices from hacker sniffing and attacks by never exposing actual device identifiers to the public network.
4Reliability
If manual renewal of IPs and domain names is required when devices increase or change, then network connectivity is maintained, but user operational burden increases significantly
Solution Approach 1:
The system implements self-service automation where the administration server automatically manages device registration, identifier assignment, and connection management. When new devices are added or existing devices change, they automatically register with the server and receive updated identifiers without requiring user intervention for IP/domain name renewal. The server handles all connectivity maintenance tasks automatically, eliminating the operational burden on users while ensuring reliable network connectivity.
Data Source
AI summary
A remote information communication system comprises an administration server, at least one linking server and at least one remote device. The linking method of the remote information communication system comprises steps of: the administration server authenticating the remote device and linking server; the proximal device requesting the administration server to find out a specified remote device; the administration server responding an address of the linking server for establishing a link with the specified remote device; the proximal device linking with the linking server through the address responded from the administration server to find out the specified remote device via the linking server; and the linking server establishing a link between the proximal device and the specified remote device.