Cloud Services Bus Catalog for Heterogeneous Service Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise service bus designs fail to adequately address the scale, heterogeneous participation, and dynamics associated with a mature Cloud computing services bus model, making it challenging for Cloud providers to manage and interoperate with multiple disparate services across unrelated Clouds.

Innovation Solution

A Cloud services bus is implemented to dynamically generate and maintain a catalog of integrated services from multiple Clouds, allowing for the management of constantly changing service levels and enabling third-party partners to create new service catalog entries, thereby facilitating the presentation of integrated services across distinct Clouds.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional enterprise service bus designs are used, then basic service integration is achieved, but the system cannot adequately address the scale, heterogeneous participation, and dynamics of mature Cloud computing environments

Engineering Contradiction:
Improveadaptability to heterogeneous Cloud servicesVSAvoidcomplexity of service bus architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service bus architecture is segmented into modular components including service registry, service repository, service composition engine, and service execution environment. Each component handles specific aspects of service management independently, enabling the system to scale and adapt to heterogeneous Cloud services without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A standardized service bus acts as an intermediary layer between diverse Cloud services and clients. This mediator translates and coordinates communications between heterogeneous services, enabling seamless integration while abstracting the underlying complexity from both service providers and consumers.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple disparate services from different Clouds are integrated, then service variety and capability are improved, but management and coordination become more difficult

Engineering Contradiction:
Improveservice integration capabilityVSAvoidease of service management
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The service bus implements universal service interfaces and standardized protocols that work across all Cloud services regardless of their native environments. This multi-functional framework enables diverse services to be managed through a common interface, simplifying operations while maintaining broad integration capability.

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

Solution Approach 2:

The system dynamically adjusts service parameters such as quality of service levels, resource allocation, and service composition based on real-time conditions. This flexibility allows the service bus to optimize management operations while accommodating the varying characteristics of integrated Cloud services.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If service levels are made dynamic to reflect changing Cloud conditions, then service quality is improved, but system complexity increases

Engineering Contradiction:
Improveservice level qualityVSAvoidcomplexity of service level management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service bus implements continuous feedback mechanisms that monitor service performance, resource availability, and quality of service metrics in real-time. This feedback drives automatic adjustments to service levels and routing decisions, improving reliability while automating the management complexity rather than increasing it.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Service levels and service compositions are designed to be dynamic rather than static. The system automatically reconfigures service paths, adjusts quality parameters, and reallocates resources based on changing conditions, enabling high reliability through adaptability rather than through complex manual management.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8924559B2Provisioning services using a cloud services catalog
Publication Date: 2014.12.30 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8924559B2 patent drawing
  • US8924559B2 patent drawing
  • US8924559B2 patent drawing

AI summary

The present invention provides a system and method for provisioning Cloud services by establishing a Cloud services catalog using a Cloud service bus within a Cloud computing environment. In one embodiment, there is a Cloud services catalog manager configured to connect a plurality of Clouds in a Cloud computing environment; maintain a catalog of integrated Cloud services from the plurality of connected Clouds; and display an index of the integrated services on a user interface. Using this system and method will allow for multiple disparate services, offered by different partners, across unrelated, physically distinct Clouds to be presented as an index of integrated services.