Multicloud Container Deployment via Central Routing Hub

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing multiple deployments of network applications across different cloud environments with varying interfaces and deployment languages is challenging due to differences in cloud provider offerings, leading to increased complexity and management difficulties.

Innovation Solution

A system and method for deploying containerized applications from a central application management hub to multiple cloud environments, utilizing a routing table to determine network paths and send packets for deployment, enabling consistent deployment across diverse cloud platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional deployment methods are used for different cloud environments, then each cloud provider's specific deployment language and techniques can be utilized, but the complexity of managing multiple deployments increases significantly

Engineering Contradiction:
Improvedeployment compatibilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a intermediary deployment management system that translates between a standardized deployment interface and the specific deployment languages of different cloud providers. This intermediary layer handles the complexity of managing multiple cloud environments while maintaining simplicity for the user, resolving the contradiction between adaptability and management complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal deployment interface that can interact with multiple different cloud providers through a single standardized method. This universal interface performs multiple functions by adapting to different cloud environments internally while presenting a consistent external API, thereby reducing management complexity while maintaining broad compatibility.

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

2Adaptability or versatility

If multiple cloud providers are used to meet diverse application requirements, then service quality and pricing options improve, but the interfaces and deployment languages differ making management difficult

Engineering Contradiction:
Improvecloud provider selectionVSAvoiddeployment management
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The deployment management system acts as an intermediary that abstracts away the differences in interfaces and deployment languages of multiple cloud providers. It provides a unified control plane that simplifies operations while maintaining the ability to deploy to diverse cloud environments, thus improving ease of operation without sacrificing cloud provider selection flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the deployment process into two distinct layers: a standardized user-facing interface layer and provider-specific implementation layers. This segmentation allows users to interact with a simple unified interface while the complex provider-specific operations are handled separately, making multi-cloud management easier without limiting provider choices.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12494993B2Multicloud hosting for containerized applications
Publication Date: 2025.12.09 ROYAL BANK OF CANADA
  • US12494993B2 patent drawing
  • US12494993B2 patent drawing
  • US12494993B2 patent drawing

AI summary

A method for deploying a containerized application from a central application management hub to a plurality of cloud environments, the method comprising the steps of: receiving a containerized application suitable for deployment; receiving an environment file designating a first environment and a second environment of the plurality of cloud environments; consulting a routing table to determine a first network path associated with the first environment and a second network path associated with the second environment; generating packets of the containerized application; and sending the packets on the first network path and the second network path; wherein the containerized application is received by a respective operators of the first environment and the second environment for subsequent deployment.