Event Stream Processing System for Unregistered IoT Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Event stream processing systems fail to process event messages from unregistered IoT devices in real-time, leading to service disruptions as they assume pre-registered objects, resulting in incomplete event processing and service failures.
Innovation Solution
The system automatically generates and registers objects for unregistered IoT devices by creating provisional objects, issuing error messages, and using automatic object generation rules to convert provisional objects to permanent ones, ensuring event processing can continue without service interruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If objects are registered in advance in event processing units according to a predetermined rule, then event processing can be performed efficiently in real-time, but event messages from unregistered IoT devices cannot be processed
Solution Approach 1:
The system performs preliminary registration of objects in event processing units before event processing. However, when an unregistered device sends an event message, the system automatically generates a provisional object and performs registration at that moment, allowing the event to be processed without prior manual registration. This resolves the contradiction by maintaining preliminary registration for efficiency while adding automatic on-demand registration for adaptability.
Solution Approach 2:
The system enables self-service by automatically generating provisional objects and registering them when event messages from unregistered IoT devices are received. The event processing unit autonomously handles the registration process without manual intervention, allowing the system to adapt to new devices while maintaining real-time processing capability.
2Speed
If the system assumes pre-registered objects for event processing, then processing speed is maintained, but service disruptions occur when unregistered devices transmit events
Solution Approach 1:
The system maintains preliminary registration of objects to ensure fast event processing. When an unregistered device transmits an event, the system automatically generates a provisional object and registers it immediately, preventing service disruption. This approach maintains processing speed while ensuring service continuity through automatic fallback registration.
Solution Approach 2:
The system prepares for potential unregistered devices by having a mechanism to generate provisional objects on-demand. This cushioning mechanism ensures that even if a device is not pre-registered, the system can quickly adapt and continue processing without service disruption, thereby maintaining both speed and reliability.
3Adaptability or versatility
If manual or automatic registration based on log output is performed, then unregistered objects can be processed, but real-time stream processing is delayed
Solution Approach 1:
The system eliminates manual registration by implementing automatic generation of provisional objects when unregistered devices send event messages. This self-service mechanism immediately processes the event and registers the object on-the-fly, maintaining real-time processing capability while enabling handling of unregistered objects.
Solution Approach 2:
The system skips the manual registration step by automatically generating provisional objects when needed. This rushing through the registration process happens synchronously with event processing, eliminating delays while maintaining the ability to handle unregistered objects.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An event stream processing system having a processor, wherein the processor registers a temporary object when the object of an event message is unregistered in response to the event message from an event generating device, stores the event message in a pending manner, and issues an error message. The processor converts the temporary object to a permanent object in response to an automatically-issued event generation message in response to the error message, updates state of the object with state value of the held event message, and executes plug-in corresponding to the updated state.