Metaproperty Schema for Cloud Deployment Data Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing platforms require significant expertise and complexity to manage, especially in provisioning virtual machines, leading to burdensome data transfer and computational resource overload during deployment customization due to the large number of initial application component properties that need to be processed.

Innovation Solution

The approach involves interpreting part of the initial application component properties as metaproperties, allowing for reduced data volume and computational resource load by using a metaproperty schema and workflow processor to generate processed application component properties, thereby limiting data transfer and resource loading during deployment customization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all initial application component properties are processed during deployment customization, then complete configuration is achieved, but data transfer volume and computational resource load increase significantly

Engineering Contradiction:
Improveconfiguration completenessVSAvoiddata transfer volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential properties from the complete set of initial application component properties. A metaproperty schema defines which properties are necessary for deployment customization, separating them from optional or redundant properties. This extraction reduces data transfer volume while maintaining configuration completeness for critical deployment parameters.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the properties into different categories: metaproperties (essential for deployment), optional properties, and excluded properties. This segmentation allows the system to process only the necessary metaproperties during deployment customization, reducing computational resource load and data transfer while maintaining reliability for core deployment functions.

Inventive Principle:
Principle #1Segmentation

2Reliability

If all initial application component properties are processed during deployment customization, then complete configuration is achieved, but computational resource load increases significantly

Engineering Contradiction:
Improveconfiguration completenessVSAvoidcomputational resource load
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential properties from the complete set of initial application component properties. A metaproperty schema defines which properties are necessary for deployment customization, separating them from optional or redundant properties. This extraction reduces data transfer volume while maintaining configuration completeness for critical deployment parameters.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the properties into different categories: metaproperties (essential for deployment), optional properties, and excluded properties. This segmentation allows the system to process only the necessary metaproperties during deployment customization, reducing computational resource load and data transfer while maintaining reliability for core deployment functions.

Inventive Principle:
Principle #1Segmentation

3Manufacturing precision

If extensive manual intervention is required for deployment customization, then precise control is achieved, but ease of operation decreases

Engineering Contradiction:
Improvedeployment control precisionVSAvoiddeployment ease of operation
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent implements self-service through automated property processing. The metaproperty schema and workflow processor automatically identify, extract, and process the necessary properties from initial application component properties without requiring manual intervention. This automation maintains deployment control precision while significantly improving ease of operation, allowing users to deploy applications with minimal manual configuration effort.

Inventive Principle:
Principle #25Self-service

4Quantity of substance

If a metaproperty schema and workflow processor are used to process only essential properties, then data transfer volume is reduced, but system complexity increases

Engineering Contradiction:
Improvedata transfer volumeVSAvoidprocessing system complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent implements a universal metaproperty schema that can be applied across different application types and deployment scenarios. This schema provides a standardized framework for identifying essential properties, reducing the need for custom processing logic for each application. The workflow processor uses this universal schema to automatically handle property extraction and processing, reducing data transfer volume while managing system complexity through standardization.

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

Data Source

PatentUS10628232B2Methods and apparatus for limiting data transferred over the network by interpreting part of the data as a metaproperty
Publication Date: 2020.04.21 VMWARE INC
  • US10628232B2 patent drawing
  • US10628232B2 patent drawing
  • US10628232B2 patent drawing

AI summary

Methods and apparatus to customize deployment using metaproperties are disclosed. An example deployment metaproperty manager can generate a first metaproperty payload including an initial application component metaproperty of an application component that provides a logical template of an application. A deployment event broker can reply-back to the deployment metaproperty manager with a second metaproperty payload that includes a processed application component metaproperty.