Smart Device Event Processing via Registration Table
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional event processing in smart devices is limited to the operating system level, restricting its application to device-level interconnections and interactions between modules, making it difficult to implement complex functionalities and interactions with cloud devices or other smart devices.
Innovation Solution
The proposed solution involves receiving event indications, determining the need for event or control messages based on registration information, and sending these messages between function modules within a smart device or between smart devices and cloud devices, enabling flexible event processing across different levels and devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If event processing is restricted to the operating system level, then system stability is maintained, but adaptability and versatility are reduced
Solution Approach 1:
The event processing system is segmented into multiple levels: operating system level event processing and application level event processing. The OS provides basic event handling capabilities, while the application layer introduces event registration mechanisms that allow flexible event routing to multiple subscribers without complicating the core OS structure. This segmentation enables adaptability at the application level while maintaining OS stability.
Solution Approach 2:
An event registration table and event routing mechanism serve as intermediaries between the operating system and application programs. This intermediary layer allows event messages to be published by one component and subscribed to by multiple others without direct coupling, enhancing versatility while keeping the system architecture manageable through standardized interfaces.
2Adaptability or versatility
If event processing is extended to device-level interconnections and cloud device interactions, then adaptability and versatility are improved, but device complexity increases
Solution Approach 1:
The event processing mechanism is designed with universal applicability across different contexts: internal device module communications, inter-device interactions via IoT protocols, and cloud device communications. The same event registration, publication, and subscription framework handles all these scenarios uniformly, achieving multi-functionality without proportionally increasing complexity.
Solution Approach 2:
The system adds a new dimension to event processing by introducing event registration information that specifies routing destinations (other function modules, IoT devices, or cloud devices). This dimensional extension allows a single event processing framework to handle multiple communication scopes without requiring separate complex systems for each level.
3Productivity
If multiple function modules can subscribe to the same event, then productivity and functionality are enhanced, but device complexity increases
Solution Approach 1:
The event registration mechanism uses copying by storing event subscription information in an event registration table. When an event is published, the system copies the event message to all registered subscribers based on their registration information, enabling efficient one-to-many communication without complex routing logic. This copying approach enhances productivity by allowing multiple function modules to respond to the same event independently.
Data Source
AI summary
Event processing associated with a smart device is disclosed, including: receiving an indication of an event detected by a function module associated with a smart device; determining, based at least in part on event registration information, that an event message is to be sent to a cloud device; and sending the event message to the cloud device. Event processing associated with a smart device also includes: receiving an indication of an event detected by a first function module associated with a smart device; determining, based at least in part on event registration information, that a control message is to be sent to a second function module associated with the smart device; and sending the control message to the second function module associated with the smart device.