Low-Power Device Script Update via Segmented Transmission
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Low-power networked devices face challenges in software updates due to power constraints, leading to extended active states and inefficient battery usage, which can result in debilitating network downtime and impractical physical updates.
Innovation Solution
A method where low-power devices wake up periodically to perform tasks, query for software updates, and receive the update in small parcels over extended periods, allowing them to return to a low-power state between transmissions, thereby reducing continuous power usage and enabling routine operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the low-power device remains in an active state to receive a large software update, then the software update can be completed, but the device experiences extended active state and high power consumption
Solution Approach 1:
The software update is divided into multiple small parcels or packets that are transmitted separately. The device receives these parcels in small increments during its active periods, then returns to low-power state between transmissions, avoiding the need to remain continuously active for the entire update duration.
2Reliability
If the low-power device queries for software updates frequently, then update availability can be detected, but the device experiences increased active state time and reduced battery life
Solution Approach 1:
The device queries for software updates periodically at predetermined intervals rather than continuously. This periodic querying allows the device to maintain update awareness while spending the majority of time in low-power state, significantly reducing active state duration and power consumption.
3Use of energy by moving object
If the software update is transmitted in small parcels over extended periods, then power consumption is reduced, but the total update time is extended
Solution Approach 1:
The device performs its scheduled tasks and queries for updates during its normal periodic active periods without requiring dedicated update time slots. By integrating update reception into existing operational cycles, the system avoids extending the overall operational timeline while maintaining low power consumption throughout the process.
4Reliability
If physical access is used to provide power during software updates, then updates can be performed on power-constrained devices, but the process becomes burdensome and time-consuming
Solution Approach 1:
The device autonomously receives software updates during its normal periodic active periods without requiring physical human intervention. The system automatically queries for updates, receives parcels during active windows, and manages the update process independently, eliminating the need for administrators to physically access each device for power provision or manual updates.
Data Source
AI summary
A mobile device connected to a wireless sensor network may receive a script update in a series of transmissions from a network management device, the transmissions being broken up over an extended period of time. The transmissions may be as small as one or several packets that make up a portion of the script. Each transmission is sent and received in coordination with a predetermined active cycle of the mobile device, i.e., during the normal mode of operation for the mobile device. A device may transition from a low-power (sleep) state to an active (awake) state to perform its routine functions. During this active time, a network management device sends a message to the mobile device indicating the availability of a script update. The mobile device, in response, transmits to the network management device a requested amount of update data it wishes to receive during this period of activity. Once the requested amount of update data has been received, the mobile device returns to a low-power state, during which it receives no additional data transmissions.