Device Information Management via Event-Driven Notification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional device information management systems place excessive loads on middle-level and low-level devices due to constant polling processes, even when no new devices are added, leading to inefficient resource utilization and increased load on devices.
Innovation Solution
A device information management system where the client acquires and transmits device information to the server only when a new device is added, using separate communication channels for device-client and server-client communication, allowing for efficient registration and management of device information without unnecessary loads, and includes features for device driver installation, information request, unique device identification, version information, and setting management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If middle-level devices constantly execute polling processes to check for low-level devices, then the server can collect device information, but the load on middle-level and low-level devices becomes excessive
Solution Approach 1:
Instead of middle-level devices actively polling low-level devices, the patent inverts the approach by having low-level devices passively notify middle-level devices when they are added. The low-level device sends a notification to the middle-level device, which then forwards the information to the server. This eliminates the need for continuous polling and reduces the load on all devices while maintaining reliable device information collection.
Solution Approach 2:
The low-level device performs self-notification when it is added to the system. Rather than being discovered through polling, the low-level device actively informs the middle-level device of its presence by sending a notification. This self-service mechanism ensures device information is collected reliably without imposing continuous polling loads on the devices.
2Productivity
If middle-level devices periodically execute polling processes even when no low-level device is added, then device information can be collected, but the process becomes wasteful and increases load unnecessarily
Solution Approach 1:
The patent eliminates wasteful polling by inverting the discovery mechanism. Low-level devices send notifications to middle-level devices when added, so the server receives information push rather than pull. This ensures device information is collected efficiently only when needed (when devices are added), eliminating unnecessary periodic polling operations and reducing energy consumption.
Solution Approach 2:
The patent replaces continuous or periodic polling actions with event-driven notification. Instead of middle-level devices executing polling processes at regular intervals regardless of device presence, the system uses periodic notification only when low-level devices are actually added. This reduces wasteful processing while maintaining collection efficiency.
3Loss of information
If low-level devices reply to polling processes, then device information can be transmitted to the server, but the load on low-level devices becomes heavy when no new devices are added
Solution Approach 1:
The patent inverts the information transmission direction. Instead of low-level devices passively responding to polling requests, they actively send notifications to middle-level devices when added. This ensures device information is transmitted to the server without imposing reply loads on low-level devices, as they initiate the communication only when necessary.
Solution Approach 2:
The low-level device performs self-notification when added to the system, initiating the information transmission process itself rather than waiting for polling requests. This self-service approach ensures device information is transmitted reliably while minimizing the load on low-level devices by eliminating unnecessary reply operations.
Data Source
AI summary
There is provided a device information management system, including a server, a client and a device in which the server and the client are configured to communicate with each other via a first communication channel while the client and the device are configured to communicate with each other via a second communication channel different from the first communication channel and device information is transmitted from the device to the client via the second communication channel and from the client to the server via the first communication channel and registered in a database of the server. The device includes a device-side information supplying unit configured to supply the device information to the client via the second communication channel.


