Cloud Computing Nodes for Aggregating Multi-Source Resources

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing architectures face challenges in providing seamless access to resources from multiple cloud service providers, requiring tenants to manage different interfaces and handle resource aggregation and management across internal and external cloud systems, which can be complex and inefficient.

Innovation Solution

The introduction of cloud computing nodes (CCNs) that act as building block interfaces, enabling the aggregation and management of resources from multiple cloud systems, providing a unified tenant API for accessing resources without the need to know the underlying infrastructure, and facilitating hybrid cloud architectures that combine internal and external resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If tenants directly access multiple cloud service providers, then resource diversity and flexibility are improved, but system complexity and management difficulty increase

Engineering Contradiction:
Improveresource diversityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud exchange as an intermediary layer between tenants and multiple cloud service providers. This cloud exchange acts as a mediator that abstracts the complexity of managing multiple cloud connections, allowing tenants to access diverse cloud resources through a unified interface while the cloud exchange handles the backend complexity of resource aggregation and management across multiple providers.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If tenants manage multiple cloud interfaces directly, then access to diverse cloud resources is improved, but operational complexity and time consumption increase

Engineering Contradiction:
Improvecloud resource accessVSAvoidoperational simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The cloud exchange is designed as a universal platform that can interface with multiple different cloud service providers through standardized protocols and APIs. It provides a single unified interface that performs multiple functions including resource aggregation, authentication, load balancing, and resource allocation across diverse cloud providers, eliminating the need for tenants to manage multiple separate cloud interfaces.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If cloud resources are aggregated from multiple sources, then resource availability and scalability are improved, but management complexity and coordination overhead increase

Engineering Contradiction:
Improveresource availabilityVSAvoidmanagement complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The cloud exchange implements feedback mechanisms that continuously monitor resource availability, utilization, and performance across multiple cloud providers. Based on this feedback, the system dynamically adjusts resource allocation, load distribution, and routing decisions to optimize resource availability and scalability while automatically managing the complexity of coordinating multiple cloud sources without requiring manual intervention.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9467395B2Cloud computing nodes for aggregating cloud computing resources from multiple sources
Publication Date: 2016.10.11 VMWARE INC
  • US9467395B2 patent drawing
  • US9467395B2 patent drawing
  • US9467395B2 patent drawing

AI summary

A disclosed example method to aggregate resources in a cloud involves receiving a request for a resource at a first tenant application programming interface provider of an internal cloud service. The example method involves using a virtualization platform application programming interface client of the internal cloud service to access the resource when the resource is an internal resource. When the resource is an external resource, a tenant application programming interface client of the internal cloud service is used to send a second request for the resource to a second tenant application programming interface provider of an external cloud service.