Service Management Platform for Multi-Provider Cloud Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Application developers face challenges in managing and integrating services from multiple cloud computing platforms and vendors, leading to vendor lock-in, increased learning curves, and complexities in provisioning and billing due to proprietary interfaces and configurations.

Innovation Solution

A service management platform that provides a unified interface for registering and provisioning services from multiple providers, enabling developers to choose best-matching services across vendors, standardizing wiring and cross-integration, and offering a single billing and reporting system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers directly manage services from multiple cloud computing platforms and vendors, then they can access diverse services, but they face increased complexity in integration and management

Engineering Contradiction:
Improveaccess to diverse servicesVSAvoidintegration and management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service management platform acts as an intermediary layer between developers and multiple cloud service providers. It provides a unified interface that abstracts the underlying complexity of different vendors' proprietary interfaces, allowing developers to access diverse services without directly managing the complexity of each provider's system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service management platform implements a universal interface that can interact with multiple different service providers through a single standardized API. This multi-functional approach allows the same platform to manage services from various vendors without requiring separate integration logic for each provider.

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

2Adaptability or versatility

If developers use proprietary interfaces from multiple vendors, then they can access specific services, but they face vendor lock-in and increased learning curves

Engineering Contradiction:
Improveservice selection flexibilityVSAvoidlearning curve and operational simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The service management platform provides a universal developer interface that works with services from multiple vendors. Developers learn one standardized API instead of multiple proprietary interfaces, reducing the learning curve while maintaining the ability to access diverse services from different providers.

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

Solution Approach 2:

The platform mediates between the developer's simplified interface requirements and the vendors' proprietary interfaces. This intermediary layer translates universal commands into vendor-specific operations, allowing developers to avoid vendor lock-in while maintaining ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If service providers offer full sets of services individually, then they can meet customer needs, but they increase operational complexity and reduce focus on core services

Engineering Contradiction:
Improveservice completenessVSAvoidoperational complexity for providers
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service management platform segments the service ecosystem into specialized providers and a coordination layer. Each provider can focus on offering their core services through standardized interfaces, while the platform handles the integration and orchestration, reducing operational complexity for individual providers while maintaining service completeness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The platform provides a universal mechanism for service registration, discovery, and management that works with any service provider. This allows providers to offer their services through a common interface without having to implement complex integration logic, reducing their operational burden while ensuring service availability.

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

4Adaptability or versatility

If developers manage multiple billing systems from different vendors, then they can use services from multiple providers, but they face complexity in unified billing and reporting

Engineering Contradiction:
Improvemulti-provider service usageVSAvoidbilling and reporting complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service management platform merges multiple vendor-specific billing and reporting systems into a single unified interface. It consolidates usage data from different providers and presents consolidated billing information to developers, eliminating the need to manage separate billing relationships with each vendor.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The platform acts as an intermediary billing layer between developers and multiple service providers. It collects usage information from various providers, standardizes the billing data, and presents unified billing and reporting to developers, simplifying the financial management aspect of multi-provider service usage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20200169481A1Decoupling platform as a service providers using a service management platform
Publication Date: 2020.05.28 SAP PORTALS ISRAEL
  • US20200169481A1 patent drawing
  • US20200169481A1 patent drawing
  • US20200169481A1 patent drawing

AI summary

A registration interface is provided to service providers for registering services with a service management platform. The service management platform is configured to provide access to services from multiple service providers to application developers using a same application developer interface. A registration request is received for a service from a service provider. The service is registered to make the service available to application developers. A provision request for the service is received from an application developer. The provision request is forwarded to a broker associated with the service provider. A provision response is received from the broker. The provision response indicates a status of provisioning an instance of the service at the service provider. A create-binding request for binding information for the service is received from the application developer. Binding information is provided to the application developer, in response to the create-binding request.