Dynamic Resource Broker for Cloud Infrastructure Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud computing systems are limited by the static nature of their underlying hardware infrastructure, which restricts dynamic resource allocation and efficiency, leading to underutilization of resources and increased costs due to the need for permanent capacity expansion.
Innovation Solution
A method and system for infrastructure sharing among service providers, where a first service provider identifies and registers available computing capacity from a second service provider, allowing for dynamic provisioning and deployment of resources to meet customer demands, leveraging available resources from multiple systems to create a composite service without permanent changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If cloud computing systems provision dynamically scalable resources to meet customer computational demands, then service adaptability and customer satisfaction are improved, but the static nature of the underlying hardware pool limits resource allocation efficiency and increases costs
Solution Approach 1:
The patent combines multiple static hardware pools from different cloud service providers into a unified dynamic resource pool. The resource broker merges available computing capacity, storage, and networking resources from multiple providers, allowing virtualized resources to be dynamically allocated across the combined pool while maintaining individual provider ownership and billing.
Solution Approach 2:
The system transforms static hardware infrastructure into dynamic resource allocation by implementing a resource broker that continuously discovers, registers, and provisions resources based on real-time demand. The broker enables dynamic scaling of computing, storage, and networking resources without permanent hardware changes, allowing resources to be rapidly deployed and retired as needed.
2Reliability
If cloud computing systems allocate resources to meet peak demand, then service reliability is improved, but permanent capacity expansion is required leading to resource underutilization and increased costs
Solution Approach 1:
The resource broker enables a single hardware pool to serve multiple customers and multiple service providers simultaneously. Resources are universally allocated based on demand, allowing the same physical infrastructure to support various workloads at different times, thereby eliminating the need for each provider to maintain dedicated over-provisioned capacity for peak demands.
Solution Approach 2:
The system enables temporary resource allocation where computing capacity, storage, and networking resources are provisioned during peak demand periods and then released back to the pool when demand decreases. This allows resources to be recovered and reallocated to other uses, preventing permanent capacity expansion and reducing resource underutilization.
3Stability of the object's composition
If cloud computing systems use a static hardware pool for resource provisioning, then infrastructure stability is improved, but resource allocation flexibility and efficiency deteriorate
Solution Approach 1:
The patent implements a nested architecture where virtualized resources are layered over the static hardware pool, with the resource broker operating at the virtualization layer. This nested structure allows dynamic resource management and flexible allocation at the virtual level while the underlying physical infrastructure remains stable and unchanged, resolving the contradiction between stability and flexibility.
Data Source
AI summary
One or more programs in a computing environment of a first service provider obtain an indication from a portion of an infrastructure of a second service provider, where the portion of the infrastructure has available computing capacity, and where the portion of an infrastructure includes at least one component. The one or more programs determine if the first service provider can deploy the portion as a portion of services deployed from the first service provider and based on making the determination that the first service provider can deploy the portion of the infrastructure, the one or more programs register the portion of the infrastructure to make it available for deployment by the first service provider. The one or more programs provision the at least one component for deployment by the first service provider in a service that includes the at least one component.