Cloud Resource Reclamation Sequencing for Dependency-Safe Shutdowns

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing systems face challenges in gracefully shutting down resources to prevent data loss and disruptions during reclamation, particularly in complex, distributed deployments across multiple regions, which can generate significant network traffic and consume resources.

Innovation Solution

A method and system for automatically processing dependencies between cloud computing resources to facilitate graceful shutdowns, allowing decentralized reclamation with reduced network traffic and a reversible intermediate suspend state for resource reuse.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If cloud computing resources are distributed across multiple regions to reduce latency and network congestion, then user experience is improved, but determining dependencies and coordinating shutdowns becomes more complex

Engineering Contradiction:
ImprovelatencyVSAvoiddependency determination complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent segments the cloud computing resources into hierarchical levels (first level, second level, etc.) based on their dependency relationships. Each level can be managed independently during shutdown operations, allowing the system to handle distributed multi-region deployments without requiring global coordination of all resources simultaneously. This segmentation reduces the complexity of determining dependencies across distributed regions.

Inventive Principle:
Principle #1Segmentation

2Reliability

If a graceful shutdown process is implemented to prevent data loss and corruption, then data integrity is improved, but the shutdown process takes longer to complete

Engineering Contradiction:
Improvedata integrityVSAvoidshutdown duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary actions by first identifying and shutting down dependent resources (second level) before shutting down the primary resources (first level). This preliminary ordering of shutdown actions ensures that data dependencies are respected, preventing data loss and corruption, while also optimizing the overall shutdown duration by systematically progressing through the resource hierarchy.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If cloud computing resources are permanently reclaimed to free up hardware, then resource utilization is improved, but the ability to recover and restart resources is lost

Engineering Contradiction:
Improveresource utilizationVSAvoidresource recoverability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent changes the state parameter of cloud computing resources from a binary state (active/inactive) to a multi-state model that includes an intermediate suspended state. Resources can be transitioned to this suspended state during reclamation, allowing them to be temporarily removed from active use to free up hardware while maintaining the capability to recover and restart them later if needed, thus balancing resource utilization with recoverability.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250377954A1Cloud computing resource reclamation orchestration
Publication Date: 2025.12.11 ORACLE INT CORP
  • US20250377954A1 patent drawing
  • US20250377954A1 patent drawing
  • US20250377954A1 patent drawing

AI summary

A computer-implemented method includes, in response to receiving a reclamation request for a tenant of a cloud computing environment at a resource reclamation service: determining, at the resource reclamation service, a set of dependencies for computing resources of the tenant within the cloud computing environment, the set of dependencies including a first level including a first subset of the computing resources and a second level including a second subset of the computing resources; executing, at the resource reclamation service, a first set of reclamation actions for the first subset of computing resources; determining, at the resource reclamation service, whether the first set of reclamation actions is complete; and executing, at the resource reclamation service, a second set of reclamation actions for the second subset of computing resources in response to determining that the first set of reclamation actions is complete.