Mesh Gateway Wake-Up Control for Low-Power IoT Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT devices face challenges with high power consumption due to always-on gateways and lack of efficient power-saving mechanisms, adversely affecting battery life and electricity consumption in smart home environments.
Innovation Solution
A gateway system with an IoT end device and host MPU that includes a radio coprocessor to maintain an active mesh network while the host MPU is in sleep mode, using a wired interface and non-volatile memory to store communication protocols, and a wake-up trigger mechanism to activate the host MPU upon specific events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the gateway and infrastructure are always on to maintain network connectivity, then network availability and responsiveness are improved, but power consumption increases
Solution Approach 1:
The gateway is segmented into multiple functional components with different power states: the host MPU can enter sleep mode to save power, while the IoT end device with radio coprocessor remains active to maintain mesh network connectivity. This segmentation allows selective power management where only essential functions remain operational.
Solution Approach 2:
The IoT end device acts as an intermediary between the sleep-mode host MPU and the active mesh network. It receives wake-up triggers from mesh devices and communicates with the host MPU when needed, enabling the gateway to maintain network presence without requiring the main processing unit to be always on.
2Use of energy by stationary object
If the host MPU enters sleep mode to save power, then power consumption is reduced, but network responsiveness and connectivity may deteriorate
Solution Approach 1:
The IoT end device performs preliminary actions by maintaining the mesh network active and listening for trigger events while the host MPU is in sleep mode. When a trigger occurs, the IoT end device is already positioned to immediately wake the host MPU, ensuring minimal disruption to network responsiveness.
Solution Approach 2:
The IoT end device provides self-service functionality by autonomously managing wake-up triggers and maintaining mesh network operations independent of the host MPU state. It can detect trigger events and manage communications without requiring continuous host MPU involvement, enabling the system to maintain responsiveness while saved power.
3Adaptability or versatility
If battery-operated IoT devices use traditional communication protocols, then compatibility is achieved, but power consumption increases
Solution Approach 1:
The system changes operational parameters by implementing duty cycling and event-driven communication in the mesh network. Devices can remain in low-power states and only activate when trigger events occur, significantly reducing average power consumption while maintaining full protocol compatibility through the standardized mesh network interface.
Data Source
AI summary
In one embodiment , a gateway includes: a host main processing unit (MPU), the host MPU having at least one core and at least one first transceiver to communicate with one or more first wireless devices in a wireless local area network (WLAN) according to a Wi-Fi protocol; and an Internet of Things (IoT) end device coupled to the host MPU via a wired interface, the IoT end device having at least one second transceiver to communicate with one or more second wireless devices in a mesh network according to at least one mesh protocol. The IoT end device is configured to cause the host MPU to exit a sleep mode in response to a trigger event from at least one of the one or more second wireless devices.