IoT Alert System Using Analytics and Rules Engines

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Fleet operators face challenges in receiving timely and relevant alerts regarding geofencing, device behavior, and driver behavior for moving IoT/M2M devices, such as vehicles, as existing solutions lack efficient sorting, evaluation, and notification mechanisms based on pre-defined criteria and conditions.

Innovation Solution

A system and method for issuing alerts that includes a storage database, analytics engine, and rules engine to receive, sort, and evaluate device information from mobile devices, determining if specified conditions are met, and sending notifications through various channels like email, SMS, or push notifications based on pre-defined thresholds and rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If device information from multiple IoT devices is monitored without efficient sorting and evaluation mechanisms, then comprehensive monitoring coverage is achieved, but alert processing efficiency and timeliness deteriorate

Engineering Contradiction:
Improvemonitoring coverageVSAvoidalert processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the alert processing system into three distinct functional modules: an analytics engine that sorts device information based on pre-determined criteria, a rules engine that evaluates sorted information against specified conditions, and a notification system that issues alerts. This segmentation allows each module to specialize in a specific task, improving overall processing efficiency while maintaining comprehensive monitoring coverage across multiple IoT devices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary sorting of device information using the analytics engine before evaluation by the rules engine. By pre-sorting data based on relevant criteria (such as device type, location, or priority), the system prepares information in advance for faster evaluation and alert generation, thereby improving processing efficiency without compromising monitoring comprehensiveness.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If all device information is evaluated against all possible conditions, then comprehensive alert coverage is achieved, but computational complexity and processing time increase

Engineering Contradiction:
Improvealert coverageVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the evaluation process into two sequential stages: sorting by the analytics engine based on pre-determined criteria, followed by condition evaluation by the rules engine. This segmentation reduces complexity by organizing information systematically before applying evaluation rules, allowing comprehensive alert coverage without evaluating all information against all conditions simultaneously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The analytics engine performs preliminary sorting and filtering of device information before it reaches the rules engine for condition evaluation. This preliminary action reduces the volume and complexity of data that requires full condition evaluation, thereby maintaining comprehensive alert coverage while reducing overall system complexity and processing requirements.

Inventive Principle:
Principle #10Preliminary action

3Speed

If real-time alert notification is implemented for all devices, then operational responsiveness is improved, but system resource consumption increases

Engineering Contradiction:
Improvealert response timeVSAvoidsystem resource consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The patent implements partial action by selectively issuing alerts only when device information satisfies specified conditions defined in the rules engine. Rather than notifying for all device events, the system applies conditional logic to determine which events warrant alert notification, thereby maintaining operational responsiveness while reducing unnecessary resource consumption from excessive alert generation.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The notification system is segmented as a separate module that receives only filtered and evaluated information from the rules engine. This segmentation ensures that alert notifications are generated only for conditions that meet predefined criteria, improving response time for critical events while avoiding resource waste from notifying about all device activities regardless of significance.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11627195B2Issuing alerts for IoT devices
Publication Date: 2023.04.11 AERIS COMM INC
  • US11627195B2 patent drawing
  • US11627195B2 patent drawing
  • US11627195B2 patent drawing

AI summary

In one example embodiment, a computer-implemented method and system for issuing alerts are disclosed. The method includes receiving device information for one or more mobile devices; sorting the received device information based on pre-determined criteria; evaluating the sorted device information to determine if the device information satisfies a specified condition; and issuing alert based on the determination. The system for issuing alerts includes a storage database, wherein the storage database receives device information for one or more mobile devices; an analytics engine, wherein the analytics engine sorts the received device information based on pre-determined criteria; a rules engine, wherein the rules engine evaluates the sorted device information to determine if the device information satisfies a specified condition and issues alerts based on the determination.