Cloud Resource Usage Monitoring System for Dynamic Threshold Adjustment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing systems lack transparency in managing computing resources and costs, making it difficult for developers and administrators to understand how updates, user increases, or malicious attacks impact resource usage, leading to unexpected expenses and potential security threats.

Innovation Solution

A system that monitors computing resource usage, compares it to predefined thresholds, and generates notifications for abnormal usage, allowing for dynamic adjustments and security threat detection, enabling administrators to manage resources effectively and prevent unnecessary costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software applications are updated regularly to add features and improve functionality, then the application evolves and scales past initial configurations, but computing resource usage increases and costs become difficult to predict and manage

Engineering Contradiction:
Improvesoftware evolutionVSAvoidresource management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system continuously monitors computing resource usage metrics and provides feedback to administrators when usage patterns change or thresholds are exceeded. This feedback mechanism enables proactive management of evolving software applications by alerting administrators to resource consumption changes that result from software updates or feature additions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system establishes baseline resource usage metrics and predefined thresholds before software updates are deployed. By having these reference points prepared in advance, administrators can quickly assess whether new software versions are causing unexpected resource consumption increases without needing to analyze complex usage patterns from scratch.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If cloud providers offer on-demand computing power that adjusts based on usage, then flexibility and scalability improve, but billing models become complicated and difficult to understand

Engineering Contradiction:
Improvecomputing flexibilityVSAvoidbilling complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system provides continuous feedback on actual computing resource consumption compared to billed amounts, enabling administrators to verify billing accuracy and understand the relationship between usage patterns and costs. This transparency simplifies the complex billing models by providing clear, actionable data about what is being charged for.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system automatically monitors and tracks resource usage without requiring administrators to manually calculate or understand complex billing formulas. By self-serve the monitoring and comparison functions, the system reduces the cognitive burden of understanding provider billing models while maintaining accurate cost tracking.

Inventive Principle:
Principle #25Self-service

3Reliability

If computing resources are reserved to ensure adequate processing power for software applications, then service reliability improves, but unexpected expenses occur when usage exceeds expectations

Engineering Contradiction:
Improveservice reliabilityVSAvoidunexpected costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system continuously compares actual resource usage against reserved capacity and billing thresholds, providing real-time feedback when usage approaches or exceeds expected levels. This enables administrators to identify unexpected cost drivers and adjust reservations or software configurations to eliminate waste while maintaining necessary service reliability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system monitors resource usage at granular levels, identifying specific features or code sections that cause excessive resource consumption. By addressing only the problematic partial components rather than reducing overall reservations, the system maintains service reliability while eliminating unnecessary cost overruns from specific software elements.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If the system monitors computing resource usage continuously to detect abnormal patterns, then security threat detection improves, but system complexity and processing overhead increase

Engineering Contradiction:
Improvesecurity detectionVSAvoidmonitoring system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system focuses monitoring efforts on specific security-relevant metrics and predefined threshold conditions rather than analyzing all possible system parameters. By concentrating on critical security indicators such as abnormal resource consumption patterns, the system achieves effective threat detection without the complexity of comprehensive system-wide analysis.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10243973B2Cloud optimizer
Publication Date: 2019.03.26 TANGOE US INC
  • US10243973B2 patent drawing
  • US10243973B2 patent drawing
  • US10243973B2 patent drawing

AI summary

A system that communicates with one or more host providers to monitor a computing load on the computing resources of the host providers and then compares this computing load or usage with expected threshold values to determine if notifications should be generated to alert administrators or the host provider of unexpected usage. The system also provides dynamic adjustment of the thresholds based on increased usage that is desired such as a large number of unique users accessing the software application to use the software application in a way that generates revenue or the potential for revenue for the software application provider.