IoT Alert Monitoring Agents for Low-Traffic Fault Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The scalability and efficiency of monitoring and fault detection in Internet of Things (IoT) devices are hindered by network traffic and resource constraints, leading to increased costs and reduced operational lifetime due to continuous data streaming for telemetry, which is not feasible for large numbers of remotely deployed devices.

Innovation Solution

Implementing a monitoring agent within IoT devices that sends alert messages only when pre-defined alert limits are breached, using a dynamically configurable alert scoring scheme and sample window length to manage resource usage and network load, allowing for complex condition monitoring and remote updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If continuous data streaming is implemented for telemetry monitoring, then fault detection capability is improved, but network traffic and energy consumption increase significantly

Engineering Contradiction:
Improvefault detection capabilityVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system implements periodic sampling of operational parameters at configurable intervals, replacing continuous data streaming. The monitoring agent collects data at discrete time points and only transmits alerts when threshold breaches occur, significantly reducing energy consumption while maintaining fault detection capability through strategic periodic observation rather than continuous monitoring.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system extracts and transmits only the critical information (alert messages when thresholds are breached) rather than continuously streaming all operational data. The monitoring agent filters operational parameters and only communicates when pre-defined alert limits are exceeded, removing unnecessary data transmission and reducing energy consumption while preserving essential fault detection functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If continuous data streaming is implemented for telemetry monitoring, then fault detection capability is improved, but network traffic increases significantly

Engineering Contradiction:
Improvefault detection capabilityVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system extracts and transmits only the critical information (alert messages when thresholds are breached) rather than continuously streaming all operational data. The monitoring agent filters operational parameters and only communicates when pre-defined alert limits are exceeded, removing unnecessary data transmission and reducing network traffic while preserving essential fault detection functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements periodic sampling of operational parameters at configurable intervals, replacing continuous data streaming. The monitoring agent collects data at discrete time points and only transmits alerts when threshold breaches occur, significantly reducing network traffic while maintaining fault detection capability through strategic periodic observation rather than continuous monitoring.

Inventive Principle:
Principle #19Periodic action

3Reliability

If central controlling and monitoring is implemented for large numbers of devices, then fault management capability is improved, but scalability is reduced

Engineering Contradiction:
Improvefault management capabilityVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system implements self-service monitoring at the device level through monitoring agents that autonomously collect operational parameters, compare them against pre-defined alert limits, and generate alerts locally. This eliminates the need for centralized polling and control, allowing each device to independently manage its own monitoring functions and enabling scalable deployment across large numbers of devices without proportionally increasing central infrastructure requirements.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The monitoring function is segmented and distributed to individual devices through local monitoring agents rather than being centralized. Each device independently performs data collection, analysis, and alert generation, dividing the monitoring workload across numerous autonomous units. This segmentation enables the system to scale to large device populations without overwhelming central infrastructure.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If alert limits are made dynamically configurable, then adaptability is improved, but device complexity increases

Engineering Contradiction:
ImproveconfigurabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements dynamic configurability of alert limits and sampling intervals that can be adjusted based on operational conditions and device priorities. The monitoring agent supports configurable parameters including alert thresholds, sampling rates, and notification preferences, allowing adaptation to different device types and operational contexts while maintaining a relatively simple core monitoring architecture through standardized configuration interfaces.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11373505B2Alert system for internet of things (IOT) devices
Publication Date: 2022.06.28 INTEL CORP
  • US11373505B2 patent drawing
  • US11373505B2 patent drawing
  • US11373505B2 patent drawing

AI summary

A method and apparatus for monitoring operational parameters in an IoT device is provided. An exemplary method includes performing a statistical analysis of a system metric. A determination is made as to whether an alert limit has been breached. If so, a message is constructed and dispatched to a server.