Cloud Usage Threshold Enforcement for Daily Spend Increases

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing cloud computing systems lack effective mechanisms to enforce resource usage increase limits, leading to potential inefficiencies and uncontrolled resource consumption, which can result in unexpected costs and performance issues.

Innovation Solution

Implementing a system that calculates daily resource usage increase values and compares them against predefined thresholds, performing remediation actions such as request rejection or sending warnings if the increase exceeds the threshold, while maintaining a table of new and deleted resource requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud computing systems allow flexible resource allocation, then resource utilization and scalability are improved, but uncontrolled resource consumption increases leading to unexpected costs

Engineering Contradiction:

Improveresource allocation flexibilityVSAvoiduncontrolled resource consumption

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system pre-establishes daily usage limits and thresholds before resource consumption occurs. When a user requests resources, the system checks against pre-set limits and proactively prevents excessive consumption by rejecting requests that would exceed daily thresholds, thereby controlling costs while maintaining flexible allocation within bounds

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors resource usage and provides feedback by comparing actual consumption against predefined limits. When usage approaches or exceeds daily thresholds, the system automatically adjusts resource allocation by rejecting further requests, creating a closed-loop control mechanism that balances flexibility with cost control

Inventive Principle:

Principle #23Feedback

2Measurement precision

If the system tracks and monitors resource usage in detail, then billing accuracy and transparency are improved, but system complexity increases

Engineering Contradiction:

Improveusage tracking accuracyVSAvoidsystem complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments resource usage tracking by organizing data into structured tables that categorize resource requests, approvals, and denials by user, resource type, and timestamp. This segmentation enables precise billing calculations while maintaining manageable data organization through standardized schemas rather than complex monolithic systems

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system creates simplified representations of resource usage data in tabular formats that capture essential billing information. These copies of usage data in standardized tables enable accurate billing calculations without requiring complex real-time monitoring systems, reducing overall system complexity while maintaining measurement precision

Inventive Principle:

Principle #26Copying

3Loss of energy

If the system enforces strict usage limits, then cost control is improved, but user flexibility and service availability deteriorate

Engineering Contradiction:

Improveresource consumption controlVSAvoiduser flexibility

Core Design Contradiction:

Loss of energyVSEase of operation

Solution Approach 1:

The system implements dynamic usage limits that can be adjusted based on user needs and consumption patterns. Daily limits are enforced but can be modified through administrative actions, allowing the system to adapt to changing requirements while maintaining cost control. The threshold-based approach provides automatic enforcement without requiring manual intervention for routine cases

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system introduces an intermediary layer of automated threshold checking between resource requests and allocation. This intermediary mechanism automatically enforces usage limits by rejecting requests that would exceed daily thresholds, while still allowing users to operate flexibly within their approved limits without manual intervention or complex user-side monitoring

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20260030073A1Daily Spending Limit Increase Enforcement

Publication Date: 2026.01.29 ORACLE INT CORP

AI summary

Techniques for spending limits in a cloud computing network are disclosed. The system receives a usage request in a cloud computing network for a user. The user having a customer tenancy in the cloud computing network including cloud computing resources. The system determines a cloud computing usage increase value relative to a time frame (such as a day) using at least the usage request. The system determines whether the cloud computing usage increase value exceeds a threshold. Based on determining that the cloud computing usage increase value exceeds the threshold, the system performs a remediation action. The remediation action comprises at least one of rejecting the usage request and bypassing the threshold.