Compact Schedule Execution for Offline IoT Device Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing embedded systems in devices lack network connectivity, role-based access control, remote interface capabilities, and remote control capabilities, limiting their functionality and reliability, especially when network connectivity is unavailable.
Innovation Solution
A network-connected device platform that generates and stores schedules in a compact format on remote devices or gateway devices, allowing them to execute events independently of cloud connectivity through a scheduler module, ensuring coordinated functionality even without network access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network connectivity is added to embedded systems, then remote control capabilities and reliability are improved, but device complexity and resource consumption increase
Solution Approach 1:
The system is divided into two parts: a cloud server that maintains comprehensive schedules and embedded devices that execute local schedules. This segmentation allows the device to gain remote control capabilities through cloud connectivity while keeping the device itself simple by only implementing a schedule executor, not a full scheduling system.
Solution Approach 2:
Schedules are prepared and translated into compact formats in advance on the cloud server before being transmitted to embedded devices. This preliminary action ensures that devices receive ready-to-execute instructions, improving reliability without requiring complex scheduling logic at the device level.
2Adaptability or versatility
If cloud server scheduling is used, then remote control capabilities are improved, but reliability deteriorates when network connectivity is unavailable
Solution Approach 1:
The cloud server translates comprehensive schedules into compact formats and transmits them to devices in advance. Devices store these compact schedules locally and can execute them independently when disconnected from the cloud, ensuring continuous operation and maintaining reliability even without network connectivity.
Solution Approach 2:
The system creates a local copy of the schedule in a compact format that the embedded device can store and execute independently. This copy enables the device to maintain scheduled functionality without continuous cloud connectivity, resolving the reliability issue while preserving remote control capabilities through the original cloud-based schedule management.
3Adaptability or versatility
If comprehensive schedules are transmitted to remote devices, then functionality is improved, but resource consumption and device complexity increase
Solution Approach 1:
The schedule format is transformed from a comprehensive, detailed structure into a compact representation with reduced parameters. This parameter change allows the same functional information to be transmitted and stored using fewer resources, enabling embedded devices with limited memory and processing power to execute schedules efficiently.
Solution Approach 2:
The essential scheduling information is extracted from the comprehensive cloud-based schedule and transmitted in a minimal compact format to the device. Only the necessary parameters for execution are transferred, reducing network bandwidth consumption and device storage requirements while maintaining full functionality.
Data Source
AI summary
In an embodiment, a processing device receives an instruction to schedule an event associated with a remote target device, generates a schedule for the remote target device, and transmits the schedule to the remote target device. The processing device receives usage information from the remote target device and additional usage information from other remote devices. The processing device applies a machine learning algorithm to the usage information and the additional usage information to determine an update to the schedule. The processing device updates the schedule and sends the update to the remote target device.