Granted Patent B2

US 11,748,079 · App. 16/889,451 · Granted Sep 5, 2023

Inventors: Vladimir Grebenshikov (Moscow, RU); Maxim Kuzkin (Irvine, CA); Alexander Khaerov (Moscow, RU)

Assignee: CloudBlue LLC

G06F8/60G06F9/547G06Q30/0641

Abstract

Claims (38)

1. A method for creating and distributing Application Programming Interface (API) connectors in a cloud service brokerage system, the method comprising:

receiving, from a developer via a developer UI portal of a developer portal computing device, connector descriptor information for an API connector associated with a cloud service;

receiving, from the developer via the developer UI portal, one or more resource types of a model of the API connector;

building, via a connector builder of the developer portal computing device, the API connector based on a stored framework for development of a backend for the connector, wherein the API connector is built as a function of the connector descriptor information and the one or more resource types, wherein the framework comprises code configured to enable customization depending on a model defined by the developer;

analyzing, by an expert system of the developer portal computing device, whether a previous version of the API connector associated with the cloud service has been published;

determining, by the expert system and subsequent to a determination that the previous version of the API connector has been published, a coincidence level between the API connector and the previous version of the API connector;

comparing, by the expert system, the coincidence level against a coincidence level threshold; and

relating, by the expert system, the API connector with the previous version of the API connector as a new version of the previous version of the API connector;

determining, by the connector builder, one or more differences between the API connector and the previous version of the API connector;

generating, by the connector builder, one or more upgrade instructions as a function of the determined one or more differences,

wherein generating a connector package comprises generating the connector package as a function of the one or more upgrade instructions;

generating, by the connector builder, the connector package for the built API connector; and

transmitting, by the connector builder, the generated connector package to a connector hub of a cloud service marketplace computing device, using the connector package to create one or more instances of the API connector.

2. The method of claim 1 , further comprising:

analyzing, via the expert system of the developer portal computing device, whether another service should be related to the API connector;

identifying, by the expert system, whether one or more other services could be related to the API connector; and

relating, by the expert system and subsequent to having identified the one or more other services could be related to the API connector, the one or more other services.

3. The method of claim 1 , further comprising receiving, from the developer via the developer UI portal, an identifier associated with a connector skeleton from a connector skeleton database of the developer portal computing device, wherein the connector skeleton is usable to generate the framework for creating the connector, and wherein receiving the one or more resource types of the API connector comprises receiving the one or more resource types of the API connector based on the connector skeleton.

4. The method of claim 1 , wherein receiving the connector descriptor information includes receiving a title of the service, a type of the service, an icon associated with the service, and one or more service provider instructions.

5. A method for creating and distributing cloud service integration connectors in a cloud service brokerage system, the method comprising:

receiving, from a developer via a developer UI portal of a developer portal computing device, connector descriptor information for a cloud service integration connector associated with a cloud service;

receiving, from the developer via the developer UI portal, one or more resource types of a model of the cloud service integration connector;

building, via a connector builder of the developer portal computing device, the cloud service integration connector based on a stored framework for development of a backend for the connector, wherein the cloud service integration connector is built as a function of the connector descriptor information and the one or more resource types, wherein the framework comprises code configured to enable customization depending on a model defined by the developer;

analyzing, by an expert system of the developer portal computing device, whether a previous version of the cloud service integration connector associated with the cloud service has been published;

determining, by the expert system and subsequent to a determination that the previous version of the cloud service integration connector has been published, a coincidence level between the cloud service integration connector and the previous version of the cloud service integration connector;

comparing, by the expert system, the coincidence level against a coincidence level threshold; and

relating, by the expert system, the cloud service integration connector with the previous version of the cloud service integration connector as a new version of the previous version of the cloud service integration connector;

determining, by the connector builder, one or more differences between the cloud service integration connector and the previous version of the cloud service integration connector; and

generating, by the connector builder, one or more upgrade instructions as a function of the determined one or more differences,

wherein generating a cloud service integration connector package comprises generating the cloud service integration connector package as a function of the one or more upgrade instructions;

generating, by the connector builder, the cloud service integration connector package for the built cloud service integration connector; and

transmitting, by the connector builder, the generated cloud service integration connector package to a connector hub of a cloud service marketplace computing device, using the cloud service integration connector package to create one or more instances of the cloud service integration connector, wherein the cloud service integration connector comprises an Application Programming Interface (API) connector.

6. The method of claim 5 , further comprising:

analyzing, via the expert system of the developer portal computing device, whether another service should be related to the cloud service integration connector;

identifying, by the expert system, whether one or more other services could be related to the cloud service integration connector; and

relating, by the expert system and subsequent to having identified the one or more other services could be related to the cloud service integration connector, the one or more other services.

7. The method of claim 5 , further comprising receiving, from the developer via the developer UI portal, an identifier associated with a connector skeleton from a connector skeleton database of the developer portal computing device, wherein the connector skeleton is usable to generate the framework for creating the cloud service integration connector, and wherein receiving the one or more resource types of the cloud service integration connector comprises receiving the one or more resource types of the cloud service integration connector based on the connector skeleton.

8. The method of claim 5 , wherein receiving the connector descriptor information includes receiving a title of the service, a type of the service, an icon associated with the service, and one or more service provider instructions.

Assignments (11)