Resource Specification Language Wrapper for Cloud Marketplace Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud marketplace systems lack a standardized mechanism for users to specify resources they wish to contribute and apply access controls, leading to incompatibility across different providers and a lack of control over resource deployment.

Innovation Solution

Implementing a resource specification language wrapper that encodes contribution requests and access controls in a standardized format, such as XML, to enable seamless transmission and decoding within cloud marketplace systems, allowing users to specify resources and access controls for deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a standardized resource specification language wrapper is implemented, then compatibility and interoperability across different cloud providers are improved, but device complexity increases due to the need for encoding and decoding mechanisms

Engineering Contradiction:
ImprovecompatibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a resource specification language wrapper as an intermediary layer between user resource contributions and cloud marketplace systems. This wrapper standardizes resource descriptions using XML format with predefined templates, enabling different cloud providers to interchange resource specifications without direct integration complexity. The wrapper acts as a universal translator that resolves incompatibility issues while maintaining manageable system complexity through standardized interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The resource specification language wrapper is designed as a universal format that can represent multiple types of computational resources (CPU, memory, storage, bandwidth) and access control policies within a single standardized structure. This multi-functional wrapper eliminates the need for provider-specific formats, achieving broad compatibility across diverse cloud environments while the template-based approach keeps the implementation complexity bounded.

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

2Reliability

If access controls are specified within the contribution request, then security and user control are improved, but manufacturing precision deteriorates due to difficulties in encoding and transmitting control parameters

Engineering Contradiction:
ImprovesecurityVSAvoidencoding precision
Core Design Contradiction:
ReliabilityVSManufacturing precision

Solution Approach 1:

The patent implements access control specifications as predefined templates within the resource contribution request wrapper, establishing security parameters before resource deployment. The wrapper includes structured elements for access policies, authentication methods, and permission levels that are encoded in advance using standardized XML schemas. This preliminary encoding of security parameters ensures precise transmission without loss or ambiguity, as the control structures are defined upfront rather than constructed dynamically.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The resource specification language wrapper transforms access control parameters into standardized XML format with defined data types and validation rules. By converting security parameters into a structured parameter system with explicit schemas, the wrapper ensures precise encoding and decoding of access control information. The parameter-based approach maintains security integrity while enabling accurate transmission across different cloud marketplace systems.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If a bid system is used for resource allocation, then adaptability is improved allowing flexible resource trading, but loss of information increases due to lack of standardized resource description formats

Engineering Contradiction:
ImproveflexibilityVSAvoidinformation loss
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent segments resource specifications into distinct, standardized XML elements within the wrapper, including separate sections for resource type, quantity, performance characteristics, and access controls. This segmentation ensures that each aspect of the resource description is captured in a dedicated field with explicit data types, preventing information loss during transmission. The modular structure allows bid systems to process and compare resources systematically while maintaining complete information integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The resource specification language wrapper enforces homogeneity by requiring all resource contributions to conform to a unified XML schema with consistent element structures and data formats. This homogeneous representation eliminates information loss that would occur with heterogeneous formats, enabling bid systems to accurately compare and evaluate resources from different providers without interpretation errors or data degradation.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS8880700B2Delivery of user-controlled resources in cloud environments via a resource specification language wrapper
Publication Date: 2014.11.04 RED HAT INC
  • US8880700B2 patent drawing
  • US8880700B2 patent drawing
  • US8880700B2 patent drawing

AI summary

Embodiments relate to systems and methods for the delivery of user-controlled resources in cloud environments via a resource specification language wrapper. In embodiments, the user of a client machine may wish to contribute resources from that machine to a cloud-based network via a network connection over a limited or defined period. To expose the user-controlled resources to one or more clouds for use the user may transmit a contribution request encoding the user-controlled resources in a specification language wrapper, such as an XML (extensible markup language) wrapper. The specification language wrapper can embed the set of user-controlled resources, such as processor time, memory, and/or other resources, in an XML or other format to transmit to a marketplace engine which can place the set of user-controlled resources into a resource pool, for selection by marketplace clouds. The specification language wrapper can indicate access controls or restrictions on the contributed resources.