Cloud Orchestration Engine for Multi-Cloud System Convergence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manually configuring and building cloud-based system solutions for multiple clients is time-consuming and resource-intensive, as each installation requires customization and resource reservation across different clouds.

Innovation Solution

An orchestration engine that interfaces with various clouds to build infrastructure, install and configure software and services, and converge connections between clouds, providing an on-demand system solution with a simplified interface for clients.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual configuration and customization is performed for each client, then system functionality and client-specific requirements are met, but time consumption and resource costs increase significantly

Engineering Contradiction:
Improveclient-specific customizationVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring cloud service templates with standard functionalities and relationships before client deployment. The orchestration engine stores these pre-configured templates and automatically instantiates them for multiple clients, eliminating the need for manual configuration each time. This resolves the contradiction by maintaining adaptability through template customization while dramatically reducing time consumption through automated deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies copying by creating reusable cloud service templates that can be replicated across multiple clients. The orchestration engine copies these standardized service configurations and automatically adapts them to individual client requirements through parameter substitution. This resolves the contradiction by enabling rapid duplication of proven configurations while maintaining client-specific adaptability through customizable parameters.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If manual configuration and customization is performed for each client, then system functionality and client-specific requirements are met, but resource costs increase due to repeated reservations

Engineering Contradiction:
Improveclient-specific customizationVSAvoidresource costs
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent applies universality by designing cloud service templates that serve multiple clients with similar requirements. The orchestration engine manages a library of universal service configurations that can be instantiated for any client needing those functionalities. This resolves the contradiction by reducing redundant resource reservations while maintaining the ability to customize services for specific client needs through template parameters.

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

Solution Approach 2:

The patent applies discarding and recovering by allowing temporary resource reservations during the configuration phase, then recovering and consolidating resources into shared pool after deployment. The orchestration engine manages resource lifecycle, releasing client-specific reservations once standardized services are activated. This resolves the contradiction by minimizing persistent resource consumption while enabling necessary customization during setup.

Inventive Principle:
Principle #34Discarding and recovering

3Productivity

If automated orchestration is implemented, then deployment speed and resource efficiency improve, but system complexity increases

Engineering Contradiction:
Improvedeployment speedVSAvoidorchestration system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies intermediary by introducing an orchestration engine as a mediator between client requirements and cloud service deployment. This intermediary layer handles the complexity of automation, resource management, and configuration orchestration, while presenting a simplified interface to clients. This resolves the contradiction by containing system complexity within the orchestration layer while maintaining high deployment speed and efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies segmentation by dividing the orchestration system into modular components: template management, resource allocation, service instantiation, and configuration management. Each module handles specific aspects of the deployment process independently. This resolves the contradiction by making the complex orchestration system manageable and maintainable through modular design, while preserving automated deployment benefits.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If multiple clouds are integrated to provide comprehensive solutions, then system versatility and functionality improve, but connection management and convergence complexity increase

Engineering Contradiction:
Improvemulti-cloud capabilityVSAvoidconnection management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies merging by consolidating multiple cloud service connections and configurations into unified service templates. The orchestration engine manages connections across different cloud providers through standardized interface definitions within templates. This resolves the contradiction by enabling multi-cloud versatility while reducing connection management complexity through unified template-based abstraction.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11934818B2Cloud orchestration engine
Publication Date: 2024.03.19 GOOGLE LLC
  • US11934818B2 patent drawing
  • US11934818B2 patent drawing
  • US11934818B2 patent drawing

AI summary

An orchestration engine that interfaces with the various clouds to implement the system solution. The orchestration engine builds, configures, and converges the single system solution. The orchestration engine builds the system by instantiating machines and services on the various clouds. The orchestration engine configures the system according to input from the client and the solution provider and then converges the various systems by establishing relationships and connections between the various services. Optionally, the orchestration engine also runs tests to verify that the system is working properly. Once the system has been built, configured and converged, the orchestration engine provides the client with a single entry point for using the system solution.