Modular Service Management Framework for Hybrid Cloud Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Implementing a hybrid cloud environment with multiple vendor systems is complex due to differing business logic and technical viability, requiring labor-intensive manual methods for service management.

Innovation Solution

A modular service management (MSM) framework that integrates multiple cloud orchestrators and service management platforms through a gateway system, rules and conditions engine, and data conversion modules to automate service request processing and data format conversion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual methods are used to manage multi-vendor cloud systems, then integration of disparate service management platforms is achieved, but labor intensity and complexity increase tremendously

Engineering Contradiction:
Improveintegration capabilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (service broker, gateway, or adapter) that mediates between disparate service management platforms and cloud orchestrators. This intermediary handles protocol translation, data format conversion, and process coordination, enabling integration of multi-vendor systems without requiring manual configuration or direct point-to-point connections between incompatible platforms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the integration functionality into modular components including service brokers, gateways, adapters, and orchestrators. Each component handles specific tasks such as authentication, resource provisioning, or data translation independently. This modular architecture reduces overall system complexity by breaking down the integration challenge into manageable, reusable modules that can be configured separately.

Inventive Principle:
Principle #1Segmentation

2Reliability

If each vendor implements their own service management platform with different business logic, then vendor-specific functionality is optimized, but system interoperability and ease of operation deteriorate

Engineering Contradiction:
Improvevendor-specific functionalityVSAvoidoperational simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements universal service management platforms that can interact with multiple cloud orchestrators from different vendors through standardized interfaces. The service broker or gateway provides multi-functional capabilities to handle various cloud environments (public, private, hybrid) and multiple SM protocols (ITSM, NFV, Orchestration) through a single unified system, eliminating the need for separate vendor-specific management approaches.

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

Solution Approach 2:

The patent employs parameter changes by transforming data between different protocols and formats. The gateway or adapter layer dynamically adjusts parameters such as data structure, communication protocols, and authentication methods to match the requirements of different cloud orchestrators while maintaining a consistent interface for service management operations.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If automation is increased to reduce manual efforts in hybrid cloud management, then productivity improves, but system complexity and difficulty of detecting and measuring increase

Engineering Contradiction:
Improveautomation levelVSAvoidsystem monitoring complexity
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent incorporates feedback mechanisms where the service broker or gateway continuously monitors the state of cloud resources and service management processes. Automated feedback loops detect issues such as provisioning failures, resource allocation problems, or protocol incompatibilities and trigger corrective actions or notifications, reducing the need for manual monitoring while maintaining system visibility.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If data format conversion is implemented between SM platforms and cloud orchestrators, then interoperability improves, but processing time and loss of time increase

Engineering Contradiction:
ImproveinteroperabilityVSAvoiddata conversion time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring data format templates, protocol mappings, and conversion rules in the gateway or adapter layer before actual service requests are processed. Common data transformation scenarios are pre-established through configuration files or metadata schemas, allowing the system to perform rapid format conversion by simply instantiating pre-defined templates rather than performing complex real-time transformations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10171560B2Modular framework to integrate service management systems and cloud orchestrators in a hybrid cloud environment
Publication Date: 2019.01.01 KYNDRYL INC
  • US10171560B2 patent drawing
  • US10171560B2 patent drawing
  • US10171560B2 patent drawing

AI summary

A system, method and program product are provided for integrating a plurality of cloud orchestrators and service management (SM) platforms to provide a hybrid cloud environment. A system is disclosed that includes: interface system that includes a first gateway for providing communications with SM platforms that adhere to an SM protocol and a second gateway for providing communications with the plurality of cloud orchestrators, wherein the SM protocol defines a set of management processes for handling service requests; a service request processing system that processes service requests from SM platforms using selected cloud orchestrators, wherein the service request processing system includes a set of management modules in which each management module processes activities associated with of a different one of the management processes; a rules and conditions engine that includes logic to select a cloud orchestrator to be used to service an inputted service request; and a set of data conversion modules, wherein each data conversion module includes logic that converts data associated with an SM platform to a data format required by a one of the cloud orchestrators.