Remote Wakeup via Connection Server for IoT Sleep Mode
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote wakeup technologies for networking apparatuses in IoT systems require extensive knowledge of network settings and often rely on router broadcasting, making it difficult to directly wake up remote devices without configuring main boards, network cards, and firewalls, and increasing network packet usage in local area networks.
Innovation Solution
A remote wakeup method involving a connection server that receives a wakeup request packet, generates an apparatus wakeup packet using stored device and connection information, and sends it to the networking apparatus, allowing direct remote waking without requiring network broadcasting or complex settings, enabling the apparatus to wake up from a sleep mode using pre-stored feature data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If the networking apparatus enters sleep mode to save power, then power consumption is reduced, but the ability to receive remote wakeup requests is lost
Solution Approach 1:
The system is divided into two operational modes: sleep mode for power saving and active mode for full functionality. The networking apparatus segments its operation by keeping only essential components (network interface) active in sleep mode while disabling others, enabling it to respond to wakeup packets without full system operation.
Solution Approach 2:
The networking apparatus performs preliminary actions by pre-configuring its network interface and address resolution capabilities before entering sleep mode. This allows the interface to recognize and respond to wakeup packets containing its device identifier without requiring full system activation, thus maintaining remote wakeup capability while in low-power state.
2Reliability
If existing wakeup technologies are used, then remote wakeup function can be implemented, but extensive network settings and knowledge are required
Solution Approach 1:
The networking apparatus performs self-service by automatically generating and maintaining its device identifier and resolving peer device identifiers without requiring manual configuration. The system autonomously handles address resolution and wakeup packet generation, eliminating the need for users to configure main boards, network cards, or firewalls.
Solution Approach 2:
The invention introduces an intermediary mechanism where the networking apparatus uses peer device identifiers stored in its memory to directly address and wake up remote devices. This intermediary approach replaces complex router broadcasting and firewall configurations with a simpler direct addressing scheme based on stored device identifiers.
3Reliability
If router broadcasting is used to wake up devices, then remote wakeup can be achieved, but network packet usage in LAN increases
Solution Approach 1:
The invention extracts the essential wakeup functionality from the complex router broadcasting mechanism. Instead of using broad network broadcasts that require multiple packets and router intervention, the system extracts and uses only the necessary device identifier matching capability, allowing direct targeted wakeup with minimal packet usage.
Data Source
AI summary
A remote wakeup method includes: receiving a wakeup request packet from a first apparatus, obtaining a wakeup information according to the wakeup request packet, generating an apparatus wakeup packet according to the wakeup request packet and the wakeup information, obtaining a connection information corresponding to a second apparatus according to the wakeup request packet, and sending the apparatus wakeup packet to the second apparatus based on the connection information. The wakeup request packet includes a device identifier (UID) of the second apparatus, and the apparatus wakeup packet includes the device identifier of the second apparatus and wakeup information.