Universal Connector Automating Cloud Service Broker Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of cloud applications with cloud service broker platforms is hindered by the lack of fully-automated API services, leading to time-consuming connector development and validation processes.

Innovation Solution

An automated, universal connector system that receives connector packages from independent software vendors, processes subscription requests, and translates API calls, enabling seamless integration with cloud service broker platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional connector development methods are used, then integration functionality is achieved, but development time and validation time increase significantly

Engineering Contradiction:
Improveintegration functionalityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining connector templates with standardized structures, metadata schemas, and integration patterns before actual integration needs arise. These templates include pre-configured connection logic, authentication mechanisms, and data mapping frameworks that can be quickly instantiated and customized for specific cloud applications, eliminating the need to build connectors from scratch each time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent employs copying by creating reusable connector templates that can be replicated and adapted for multiple cloud applications. Instead of developing unique integration solutions for each application, the system copies proven connector patterns and customizes them through configuration, significantly reducing development and validation time while maintaining integration reliability

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If custom connectors are developed for each cloud application, then specific application requirements are met, but device complexity increases

Engineering Contradiction:
Improveapplication-specific requirementsVSAvoidconnector complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by designing a standardized connector framework that can interface with multiple different cloud applications through a common architecture. The framework includes universal components for authentication, data synchronization, error handling, and configuration management that work across various applications, reducing the need for custom development while still meeting application-specific requirements through configurable parameters and adapters

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

Solution Approach 2:

The patent applies segmentation by dividing connector functionality into modular, independent components such as authentication modules, data mapping modules, synchronization modules, and configuration modules. Each module can be independently developed, tested, and configured, allowing complex integration requirements to be broken down into manageable segments that reduce overall system complexity while maintaining adaptability

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3704834B1Integrating cloud applications into a cloud service broker platform using an automated, universal connector package
Publication Date: 2023.07.19 CLOUDBLUE LLC
  • EP3704834B1 patent drawingFigure 1
  • EP3704834B1 patent drawingFigure 1A
  • EP3704834B1 patent drawingFigure 1B

AI summary

A method for integrating cloud applications into a cloud service broker (CSB) platform using an automated, universal connector, the method includes receiving at a connector hub, a connector package for a software from an independent software vendor device, creating a connector instance for the connector package for integration with the CSB platform, the CSB platform further configured to provide licenses for the software, receiving at the cloud service broker computing device via a CSB platform interface, a subscription request for the software, the subscription request comprising an activity selected from a group consisting of a creation, change and deletion, transmitting to a universal connector device by a CSB platform controller, the subscription request, processing, at the universal connector device, the subscription request, notifying a customer relationship management (CRM) device, by the universal connector device, of the subscription request, storing the subscription request in a CRM database, obtaining approval by the universal connector device, for the subscription request, processing, at the universal connector device, the subscription request, upon receiving a request approval, and transmitting a subscription approval result to the CSB platform, the CSB platform displaying subscription approval result to a subscribe.