Multi-Cloud Metadata Merging Platform for Instance Consolidation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Merging cloud instances into a single multi-cloud instance is challenging due to conflicts in metadata attributes stored in different formats, leading to configuration errors and inefficient use of computing resources.

Innovation Solution

A metadata merging platform analyzes and identifies conflicting and non-conflicting attributes across different cloud instances, merges non-conflicting attributes, and determines a dominant state for conflicting attributes to generate a target configuration for a unified multi-cloud instance, reducing resource usage by eliminating the need for separate cloud instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple cloud instances are maintained separately to avoid configuration errors, then system reliability is improved, but device complexity and resource usage increase

Engineering Contradiction:
Improveconfiguration error preventionVSAvoidcloud instance management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple cloud instances into a unified multi-cloud instance by consolidating their metadata. The system combines configuration data from multiple sources while maintaining system reliability through automated conflict detection and resolution mechanisms, thereby reducing the number of separate instances needed while preventing configuration errors.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a metadata merging platform as an intermediary that mediates between multiple cloud instances. This platform automatically detects conflicts in metadata attributes, determines dominant states, and resolves conflicts according to predefined rules, enabling reliable merging without manual intervention.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple cloud instances are maintained separately, then configuration errors are avoided, but computing resource efficiency deteriorates

Engineering Contradiction:
Improveconfiguration error preventionVSAvoidcomputing resource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent consolidates multiple cloud instances into a single multi-cloud instance, merging their metadata and configurations. This reduces the number of separate instances requiring computational resources while maintaining reliability through automated conflict resolution, thereby improving computing resource efficiency.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent changes the state of metadata attributes by determining dominant states for conflicting attributes and applying transformation rules. This allows the system to resolve conflicts and merge instances efficiently, improving resource utilization while preventing configuration errors.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If metadata from different cloud instances is merged, then resource usage is reduced, but configuration conflicts increase

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidmetadata conflict management
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a metadata merging platform as an intermediary that automatically manages metadata conflicts. The platform detects conflicting attributes, determines dominant states, and resolves conflicts according to predefined rules, eliminating the need for manual conflict management while enabling efficient resource utilization through instance merging.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements self-service mechanisms where the metadata merging platform automatically resolves conflicts without external intervention. The system autonomously determines dominant states, applies transformation rules, and generates merged configurations, reducing the complexity of manual metadata conflict management.

Inventive Principle:
Principle #25Self-service

4Manufacturing precision

If manual merging of cloud instances is performed, then configuration precision can be controlled, but time consumption increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidmerging process time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements automated self-service mechanisms where the metadata merging platform autonomously detects conflicts, determines dominant states, and resolves conflicts according to predefined rules. This eliminates manual merging operations while maintaining configuration accuracy through systematic conflict resolution, significantly reducing the time required for instance merging.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an automated metadata merging platform that mediates the merging process, replacing manual operations. The platform systematically processes metadata, detects conflicts, and applies resolution rules, maintaining configuration precision while dramatically reducing the time consumption associated with manual merging.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11947504B1Multi-cloud data processing and integration
Publication Date: 2024.04.02 ACCENTURE GLOBAL SOLUTIONS LTD
  • US11947504B1 patent drawing
  • US11947504B1 patent drawing
  • US11947504B1 patent drawing

AI summary

In some implementations, a device may receive a request to merge a first cloud computing instance with a second cloud computing instance to generate a multi-cloud computing instance. The device may access a first application programming interface to obtain a first configuration of the first cloud computing instance. The device may access a second application programming interface to obtain a second configuration of the second cloud computing instance. The device may generate a target configuration based on the first configuration or the second configuration. The device may instantiate a set of resources with the target configuration for the multi-cloud computing instance. The device may provide output identifying the multi-cloud computing instance.