Cloud-Connector Server Multi-Tenant Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing systems face challenges in efficiently managing and aggregating resources across multiple cloud facilities due to interdependencies spanning multiple hierarchical levels of abstraction, leading to difficulties in providing high availability, fault tolerance, and load balancing in distributed and heterogeneous environments.

Innovation Solution

A distributed system comprising a cloud-connector server, cloud-connector nodes, and service-provider nodes that cooperate to provide services across multiple clouds, enabling multi-cloud aggregation and management through a cloud-director level of abstraction, which facilitates secure and efficient distribution of resources and services across geographically and operationally distinct cloud facilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple cloud facilities are aggregated into a distributed system, then resource utilization and service availability are improved, but system complexity and management difficulty increase

Engineering Contradiction:
Improveservice availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud-connector server as an intermediary component that mediates between multiple cloud facilities and the virtual data center. This server manages connections, coordinates resource allocation, and handles communication protocols, thereby reducing the complexity burden on individual cloud facilities while maintaining high service availability across the distributed system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The cloud-connector server performs multiple functions including resource orchestration, load balancing, fault tolerance management, and inter-cloud communication. By consolidating these diverse functions into a single multi-functional component, the system achieves improved reliability without proportionally increasing overall system complexity.

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

2Ease of operation

If hierarchical levels of abstraction are added to manage cloud resources, then resource management capability is improved, but interdependencies and coordination difficulty increase

Engineering Contradiction:
Improveresource management capabilityVSAvoidcoordination difficulty
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the cloud management system into distinct hierarchical layers: virtual data center layer, cloud-connector server layer, and individual cloud facility layer. Each layer has specific responsibilities and interfaces, allowing resource management operations to be performed at appropriate levels without creating excessive interdependencies. The segmentation isolates coordination complexity to specific layer boundaries.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a temporal dimension to resource management through event-driven coordination mechanisms. Instead of synchronous multi-level coordination that increases complexity, the system uses asynchronous events and callbacks that allow higher-level abstraction to manage resources without immediately coordinating with lower levels, thereby reducing coordination difficulty while maintaining management capability.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If cloud facilities are geographically dispersed, then service coverage and redundancy are improved, but network latency and communication overhead increase

Engineering Contradiction:
Improvefault toleranceVSAvoidnetwork latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action through pre-established connection pools and cached communication channels between cloud-connector servers and cloud facilities. Instead of creating new network connections on-demand which increases latency, the system pre-provisions communication paths during idle periods, allowing rapid failover and coordination when geographic dispersion is required for fault tolerance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies local quality by allowing each geographically dispersed cloud facility to maintain local state and make local decisions about resource allocation and fault response. Rather than requiring constant centralized coordination that increases communication overhead, local nodes operate autonomously within their regions and only communicate with the cloud-connector server when necessary, reducing network latency while maintaining fault tolerance.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11856050B2Multi-tenant-cloud-aggregation and application-support system
Publication Date: 2023.12.26 VMWARE INC
  • US11856050B2 patent drawing
  • US11856050B2 patent drawing
  • US11856050B2 patent drawing

AI summary

The present application is directed to a distributed system that provides multi-cloud aggregation and that includes a cloud-connector server, cloud-connector nodes, and one or more service-provider nodes that cooperate to provide services that are distributed across multiple clouds. A service-provider node obtains tenant-associated information from a virtual data center in which the service-provider node is installed and provides the tenant-associated information to the cloud-connector server.