IoT Endpoint Metrics Collection via Device Templates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The management of network-connected devices in the Internet of Things (IoT) environments becomes challenging due to the scale of deployment, as enterprises face difficulties in deploying software updates and tracking performance metrics across tens of thousands of devices, straining IT departments and automated solutions.

Innovation Solution

An IoT management service is introduced that allows IoT endpoints to be registered with a device template, specifying metrics to be collected, which are then tracked and visualized through a management console, enabling administrators to compare performance before and after software updates, using an IoT gateway and management service to facilitate data collection and analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual update deployment is used for IoT devices, then update control is precise, but deployment efficiency is low and cannot scale to tens of thousands of devices

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidupdate control precision
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

An automated update management system acts as an intermediary between administrators and IoT devices. The system includes a server that receives update commands, processes them according to device groups and policies, and automatically distributes updates to target devices. This intermediary layer enables scalable automated deployment while maintaining precise control through configurable update policies, device groupings, and approval workflows.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If automated update deployment is used for IoT devices, then deployment efficiency is high, but update control precision is reduced

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidupdate control reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The automated update system incorporates feedback mechanisms where devices report their status, update completion, and performance metrics back to the server. The server uses this feedback to monitor update deployment progress, detect failures, and trigger remediation actions. This feedback loop ensures reliable automated deployment while maintaining control through real-time monitoring and adaptive response to device states.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-configuring update policies, device groupings, and approval workflows before actual update deployment. Administrators can define update schedules, target device groups, and approval requirements in advance. The server prepares update packages and validates them against policies before distribution. This preliminary configuration ensures that automated deployment proceeds reliably with pre-established control parameters.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If comprehensive performance tracking is implemented across all IoT devices, then performance visibility is complete, but system complexity and resource strain increase

Engineering Contradiction:
Improveperformance visibilityVSAvoidmanagement system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The performance tracking system segments devices into groups based on device type, location, function, or other criteria. Instead of treating all devices uniformly, the system applies different monitoring configurations, metric collections, and analysis methods to different device groups. This segmentation reduces overall system complexity by breaking down the large-scale monitoring problem into manageable segments while maintaining comprehensive visibility through aggregated group-level insights.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts and focuses on only the most relevant performance metrics for each device group rather than collecting all possible data from every device. Based on device types and functions, the system selectively monitors specific parameters (e.g., CPU usage for compute-intensive devices, battery levels for mobile devices, network throughput for communication devices). This extraction approach maintains comprehensive visibility for critical metrics while reducing data volume and processing complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

4Device complexity

If selective performance tracking is implemented, then system complexity is reduced, but performance visibility becomes incomplete

Engineering Contradiction:
Improvemanagement system complexityVSAvoidperformance visibility
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The update management system provides universal functionality that automatically adapts to different device types and monitoring requirements. A single system framework handles diverse device groups with different metric needs through configurable policies and templates. The system can switch between comprehensive and selective monitoring modes based on device characteristics, update requirements, and administrative preferences. This multi-functionality ensures complete performance visibility when needed while maintaining low complexity through standardized processes.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11762647B2IoT endpoint metrics
Publication Date: 2023.09.19 OMNISSA LLC
  • US11762647B2 patent drawing
  • US11762647B2 patent drawing
  • US11762647B2 patent drawing

AI summary

Disclosed are various embodiments for collecting and presenting IoT metrics. A software update package can be deployed to an IoT gateway. A device template used to register an IoT endpoint with an IoT management service can also define metrics that can be collected regarding the performance of the IoT endpoints.