IoT Device Interaction Throttling via Feedback Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IoT devices often experience overload when the number of interactions from user interfaces exceeds a threshold, leading to an inability to respond to all requests, which can result in service discontinuation and poor user experience.

Innovation Solution

A computing system that includes a performance monitor to detect when the load exceeds a threshold, triggering a message service to send slow-down messages to user interfaces, reducing their interaction rate to prevent overload and ensure continuous service delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the number of interactions from user interfaces with IoT devices increases, then the service coverage and user experience improve, but the IoT device experiences overload and cannot respond to all requests

Engineering Contradiction:
Improveservice coverageVSAvoidresponse capability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements a feedback mechanism where the IoT device monitors interaction rates from user interfaces and sends throttle messages when the interaction rate exceeds a threshold. This feedback loop allows the system to dynamically adjust interaction rates, preventing overload while maintaining service coverage. The feedback ensures that user interfaces receive real-time information about system capacity and adjust their behavior accordingly.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically adjusts the interaction rate between user interfaces and IoT devices based on real-time load conditions. Instead of using a fixed interaction rate, the system modulates the rate dynamically by sending throttle messages when thresholds are exceeded, allowing the system to adapt to changing conditions and maintain reliability while maximizing productivity.

Inventive Principle:
Principle #15Dynamics

2Loss of time

If the interaction rate between user interfaces and IoT devices is increased, then data freshness and user experience improve, but the computational load on IoT devices exceeds thresholds causing service discontinuation

Engineering Contradiction:
Improvedata freshnessVSAvoidcomputational load
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The system applies preliminary anti-action by sending throttle messages to user interfaces before the computational load causes service discontinuation. When the interaction rate approaches the threshold, the system proactively reduces the interaction rate by sending throttle messages, preventing the harmful effect of overload before it occurs. This anticipatory approach maintains data freshness within acceptable limits while avoiding service disruption.

Inventive Principle:
Principle #9Preliminary anti-action

3Reliability

If throttling is applied to reduce interaction rates, then IoT device overload is prevented, but user interface refresh rates are reduced

Engineering Contradiction:
Improveservice continuityVSAvoidrefresh rate
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system applies partial throttling rather than complete blocking of interactions. When thresholds are exceeded, the system sends throttle messages that reduce the interaction rate to an acceptable level rather than stopping interactions entirely. This partial action maintains service continuity while minimizing the impact on refresh rates, achieving a balance between reliability and data freshness.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11095566B2Embedded device interaction restrictions
Publication Date: 2021.08.17 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11095566B2 patent drawing
  • US11095566B2 patent drawing
  • US11095566B2 patent drawing

AI summary

In some examples, a non-transitory machine-readable medium can include instructions executable by a processing resource to: monitor a quantity of interactions between a plurality of user interfaces with an embedded device, determine when the quantity of interactions with the embedded device exceeds a threshold, send a slow-down message to a portion of the plurality of user interfaces in response to the interactions with the embedded device exceeding the threshold, and restrict a portion of the quantity of interactions with the embedded device when the quantity of interactions continues to exceed the threshold for a quantity of time after the slow-down message was sent to the portion of the plurality of user interfaces.