Cloud Control Interface for Multi-Provider Application Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud application deployment across multiple providers is hindered by lack of unified APIs, varying security models, persistent storage differences, and increased complexity, leading to manual and costly portability issues and human errors.

Innovation Solution

A control interface that interacts with cloud providers using cloud drivers to abstract provider-specificities, allowing seamless deployment and monitoring across multiple cloud providers by forming a mesh interface and utilizing a cloud provider database for descriptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud providers use their own custom APIs and deployment methods, then each provider can optimize for their specific infrastructure, but developers face increased complexity and difficulty in deploying applications across multiple cloud providers

Engineering Contradiction:
Improvecloud provider specific optimizationVSAvoiddeployment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud provider database and control interface as an intermediary layer between the deployment system and individual cloud providers. This intermediary abstracts the diversity of cloud provider APIs behind a unified interface, allowing developers to deploy applications across multiple providers without directly dealing with each provider's specific complexities. The control interface translates unified deployment commands into provider-specific operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal deployment system that can operate across multiple cloud providers through a common control interface. The cloud provider database stores descriptions of various providers, and the system uses this information to automatically select appropriate deployment strategies. This universal interface handles multiple functions including deployment, monitoring, and coordination across different cloud environments.

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

2Reliability

If developers manually deploy applications across different cloud providers, then they can handle provider-specific details, but this leads to increased human errors and costly portability issues

Engineering Contradiction:
Improvedeployment accuracyVSAvoiddeployment ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements an automated deployment system where the control interface and cloud provider database work together to self-manage the deployment process. The system automatically retrieves cloud provider descriptions from the database, selects appropriate deployment configurations, and executes deployments without requiring manual intervention for each cloud provider. This automation eliminates human errors associated with manual deployment while maintaining ease of operation through a unified interface.

Inventive Principle:
Principle #25Self-service

3Reliability

If cloud providers implement their own security models and storage facilities, then each provider can optimize for their specific requirements, but this creates portability issues and makes it difficult to move applications between providers

Engineering Contradiction:
Improvesecurity and storage optimizationVSAvoidapplication portability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The control interface acts as an intermediary that abstracts cloud provider-specific security models and storage facilities behind a unified interface. The cloud provider database stores descriptions of each provider's capabilities, allowing the system to automatically adapt to different security and storage requirements while maintaining application portability. Applications interact with the unified interface rather than provider-specific implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If the system monitors events and status of deployed components across multiple cloud providers, then it can ensure attribute compliance and reduce errors, but this increases the complexity of the control interface

Engineering Contradiction:
Improveattribute complianceVSAvoidcontrol interface complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the event monitoring and status checking functions into the existing control interface structure. Rather than creating separate monitoring systems for each cloud provider, the control interface integrates these functions and uses the cloud provider database to coordinate monitoring across all providers. This unified approach ensures attribute compliance while managing complexity through consolidation.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11785085B2Control interface for the deployment of an application, system and method using such a control interface
Publication Date: 2023.10.10 AGARIK SAS
  • US11785085B2 patent drawing
  • US11785085B2 patent drawing

AI summary

A control interface for deployment of an application, the control interface running on a specific cloud provider and connected to a plurality of other control interfaces running on a plurality of cloud providers, wherein the control interface is connected to a cloud provider database storing a description of each cloud provider. The control interface includes a cloud driver specific to the cloud provider on which the control interface is running, the cloud driver allowing the control interface to instruct the cloud provider to deploy components of the application. The control interface includes means to receive an attribute file describing the application to deploy; means to select for each component of the application, based on the descriptions provided by the cloud provider database and the attribute file, a cloud provider suitable for the deployment; for each selected cloud provider, means to send to the corresponding control interface the component to deploy.