Cloud Application Throttling via Dynamic Resource Thresholds

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based SaaS applications face challenges in managing computing resource usage effectively, leading to increased costs due to inconsistent billing models and variable resource demands.

Innovation Solution

A system and method that intercepts computing requests, determines delays to keep resource usage below thresholds, and uses machine learning to predict usage patterns and adjust hosting plans accordingly, while generating alerts and automating actions based on resource monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If resource usage is allowed to scale dynamically to meet demand, then application performance is improved, but computing resource costs increase

Engineering Contradiction:
Improveapplication performanceVSAvoidcomputing resource costs
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent implements dynamic threshold adjustment for resource usage by monitoring actual application performance metrics and billing costs in real-time. The system automatically modifies resource thresholds based on observed usage patterns, allowing the application to scale dynamically when performance requires it while preventing unnecessary scaling when costs are the primary concern. This dynamic adaptation resolves the contradiction by making the scaling behavior responsive to actual needs rather than static or overly aggressive.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system establishes a feedback loop that continuously monitors application performance metrics, resource usage patterns, and billing costs. This feedback mechanism allows the system to learn from past decisions and adjust future resource allocation accordingly. By incorporating cost feedback alongside performance feedback, the system can identify when scaling provides genuine performance benefit versus when it merely increases costs, thereby resolving the contradiction between performance improvement and cost control.

Inventive Principle:
Principle #23Feedback

2Reliability

If maximum resources are reserved to ensure performance during peak demand, then application reliability is improved, but cost increases due to paying for unused capacity during low demand

Engineering Contradiction:
Improveapplication reliabilityVSAvoidcost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by setting resource thresholds below the maximum possible capacity but above the minimum required for basic operation. Instead of reserving full maximum resources, the system determines optimal threshold levels that provide sufficient capacity for typical workload while avoiding payment for excessive unused resources. The threshold can be dynamically adjusted to match actual demand patterns, ensuring reliability when needed while minimizing costs during lower demand periods.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system changes the resource allocation parameter from a static maximum reservation to a dynamic threshold that adjusts based on monitored performance and cost metrics. By modifying this parameter adaptively, the system can maintain reliability during peak demand while reducing resource allocation during low demand periods, thereby resolving the contradiction between ensuring sufficient capacity and minimizing payment for unused resources.

Inventive Principle:
Principle #35Parameter changes

3Loss of energy

If resource usage thresholds are set low to control costs, then computing resource costs are reduced, but application performance may be compromised

Engineering Contradiction:
Improvecomputing resource costsVSAvoidapplication performance
Core Design Contradiction:
Loss of energyVSProductivity

Solution Approach 1:

The system performs preliminary monitoring and analysis of application performance patterns before setting final resource thresholds. By预先 observing how the application behaves under different load conditions and identifying performance-critical resource levels, the system can establish thresholds that are low enough to control costs but high enough to maintain acceptable performance. This preliminary action prevents setting thresholds that would be too restrictive without requiring real-time performance degradation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables the application to essentially self-regulate resource usage by implementing automated monitoring and dynamic threshold adjustment. The application monitors its own performance metrics and resource consumption, automatically adjusting resource allocation to maintain performance within acceptable ranges while controlling costs. This self-service approach ensures that cost-control measures do not compromise performance because the system actively manages the trade-off rather than applying fixed restrictive limits.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12277448B2Cloud application threshold based throttling
Publication Date: 2025.04.15 TANGOE US INC
  • US12277448B2 patent drawing
  • US12277448B2 patent drawing
  • US12277448B2 patent drawing

AI summary

Systems and methods are provided for intercepting computing requests and modifying the execution timing thereof based on thresholds and minimum performance criteria and/or adjusting hosted services plans in order to monitor and control costs of hosting software applications on hosted provider computing resources.