Event-Driven IoT Abstraction Rules for Flexible Device Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional approaches for managing IoT devices lack a common mechanism for flexibly controlling interactions, facilitating communications between IoT devices and other network devices, and coordinating operations performed by IoT devices.
Innovation Solution
The implementation of an IoT management service that uses event-driven abstraction through rules, allowing network computing devices to receive and execute actions based on events emitted by IoT devices, with support for various communication protocols via plugins.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional approaches are used for managing IoT devices, then device connectivity is maintained, but flexibility in controlling interactions and coordinating operations is insufficient
Solution Approach 1:
The patent introduces an IoT management service as an intermediary layer between IoT devices and network computing devices. This service receives events from IoT devices, processes them according to configured rules, and coordinates appropriate actions. The intermediary abstracts the complexity of device interactions, providing flexible control without requiring direct complex coordination between devices themselves.
Solution Approach 2:
The system implements dynamic rule-based processing where the behavior of the IoT management service changes based on received events and configured rules. The service can adapt its responses to different event types, enabling flexible control of interactions while maintaining a consistent management architecture that handles diversity through configurable logic rather than hard-coded complexity.
2Productivity
If event-driven abstraction with rules is implemented, then coordination and communication are enhanced, but system architecture complexity increases
Solution Approach 1:
The patent segments the IoT management system into distinct functional components: event reception, rule matching, and action execution. The rule-based system is divided into event identifiers that match specific event types and corresponding action identifiers that trigger specific responses. This segmentation allows efficient coordination through modular processing while managing complexity through clear separation of concerns.
Solution Approach 2:
The IoT management service implements a universal rule-processing mechanism that handles multiple event types and coordination scenarios through a single unified framework. Rather than creating separate coordination logic for each device or event type, the system uses a multi-functional rule engine that can process diverse events and coordinate appropriate actions, improving productivity while containing architecture complexity through reuse.
Data Source
AI summary
Event-driven Internet of Things (IoT) abstraction using rules is disclosed herein. In one embodiment, a network computing device that provides an IoT management (IoTM) service is communicatively coupled to an IoT device. The IoTM service receives multiple rules, each of which comprises an event identifier that identifies an event that the IoT device is capable of emitting, and an action identifier that identifies an action to be performed by the IoTM service (e.g., a command to be issued to the IoT device or an operation to be performed by the IoTM service). Upon receiving a first event emitted by the IoT device, the IoTM service identifies a first rule of the plurality of rules based on a first event identifier of the first rule that matches the first event. The IoTM service then executes a first action, wherein a first action identifier of the first rule identifies the first action.