Decentralized Rule Processing for IoT Device Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The centralized structure of existing IoT systems leads to performance inefficiencies due to excessive traffic on the central server, making the system prone to failure and requiring additional hub devices for low-specification devices, which increases costs and complexity for users. Additionally, the trigger-oriented rule writing method is not intuitive, requiring users to think in terms of triggers rather than desired actions.
Innovation Solution
A decentralized approach where user devices store and execute rules independently, with a controller managing operations and transmitting rules to peripheral devices, allowing users to define actions first and automatically designating devices for rule execution, thereby reducing system load and enhancing user intuitiveness.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a centralized structure is used where all rules are processed by one central server, then rule management is simplified, but system performance deteriorates due to excessive traffic on the central server
Solution Approach 1:
The patent divides the centralized rule processing function into distributed rule engines deployed across multiple user devices. Each user device executes local rules independently, segmenting the monolithic rule processing workload into parallel distributed operations, thereby reducing central server traffic while maintaining manageable rule organization through the rule repository.
2Device complexity
If a centralized structure is used where all rules are processed by one central server, then centralized control is maintained, but system reliability deteriorates as the entire system fails when the central server fails
Solution Approach 1:
The patent segments the centralized rule engine into multiple distributed rule engines across different user devices. This distribution ensures that if one rule engine or the central server fails, other rule engines continue to operate independently, maintaining system reliability through fault isolation and continued local rule execution.
Solution Approach 2:
User devices are empowered to execute rules locally through embedded rule engines without requiring continuous central server operation. Each device serves itself by autonomously evaluating and executing its local rules, reducing dependency on the central server and improving system availability during server outages.
3Adaptability or versatility
If additional hub devices are provided to support low specification devices, then device compatibility is improved, but device complexity and cost increase
Solution Approach 1:
Low specification devices execute rules directly through locally deployed rule engines without requiring intermediary hub devices. Each device independently manages its own rule execution, eliminating the need for additional hub infrastructure and reducing system complexity while maintaining broad device compatibility.
4Device complexity
If a trigger-oriented rule writing method is used, then rule processing logic is simplified, but ease of operation deteriorates as users must think in terms of triggers rather than desired actions
Solution Approach 1:
The patent inverts the traditional trigger-oriented rule writing approach by allowing users to specify desired actions first, then automatically determining the appropriate triggers. This inversion makes rule creation more intuitive for users while maintaining simplified processing logic through automated trigger identification by the rule engine.
Data Source
AI summary
A user device, a method of driving the user device, an apparatus for providing a service, and a method of driving the apparatus for providing the service are provided. The user device includes a storage configured to receive a rule related to performing an operation of the device and to store the rule, and a controller configured to control to perform a former priority operation based on a determination result of the former priority operation included in the stored rule, and to transmit the rule to a periphery device for performing a latter priority operation included in the rule in response to the former priority operation being completed.