BROKERING SERVICES FROM PARTNER CLOUD PLATFORMS

• US 20180316772A1
• Filed: 04/28/2017
• Published: 11/01/2018
• Est. Priority Date: 04/28/2017
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Eberlein, Peter, Atanasov, Momchil, Galabova, Martina
• Granted Patent: US 10,693,989 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/562 Brokering proxy services
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A Proxy Service Broker on a Hoster Platform as a Service (PaaS) receives a request for a Service Catalog including PaaS services available from a Partner PaaS. Using the Proxy Service Broker, creation of an instance of a Partner PaaS service selected from the Service Catalog is initiated. Using the Proxy Service Broker, a call is transmitted to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS. An Application is deployed on the Hoster PaaS to consume the instance of the Partner PaaS service. The deployed Application is bound with the instance of the Partner PaaS service and directly consumes the bound Partner PaaS service.

Claims

1. A computer-implemented method, comprising:

receiving, at a Proxy Service Broker on a Hoster Platform as a Service (PaaS), a request for a Service Catalog including PaaS services available from a Partner PaaS;

initiating creation, using the Proxy Service Broker, of an instance of a Partner PaaS service selected from the Service Catalog;

transmitting, using the Proxy Service Broker, a call to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS;

deploying an Application on the Hoster PaaS to consume the instance of the Partner PaaS service;

binding the deployed Application with the instance of the Partner PaaS service; and

directly consuming the bound Partner PaaS service with the deployed Application.

2. The computer-implemented method of claim 1, wherein the Service Catalog of PaaS services is stored on and returned by the Proxy Service Broker.

3. The computer-implemented method of claim 1, wherein the Proxy Service Broker is associated with a Developer Space associated with the Hoster PaaS.

4. The computer-implemented method of claim 1, wherein the unique service identifier for the created instance of the Partner PaaS service is created by the Proxy Service Broker to avoid name clashes on the Partner PaaS.

5. The computer-implemented method of claim 1, comprising transmitting, using the Proxy Service Broker, a call to the Partner Service Broker on the Partner PaaS to create a service key for the created instance of the Partner PaaS service.

6. The computer-implemented method of claim 5, wherein a single service user is used to transmit the call to create the instance of the Partner PaaS service and to create the service key for the created instance of the Partner PaaS service.

7. The computer-implemented method of claim 5, wherein the calls to the Partner PaaS from the Proxy Service Broker are Representational State Transfer (REST) calls.

8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:

receiving, at a Proxy Service Broker on a Hoster Platform as a Service (PaaS), a request for a Service Catalog including PaaS services available from a Partner PaaS;

initiating creation, using the Proxy Service Broker, of an instance of a Partner PaaS service selected from the Service Catalog;

transmitting, using the Proxy Service Broker, a call to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS;

deploying an Application on the Hoster PaaS to consume the instance of the Partner PaaS service;

binding the deployed Application with the instance of the Partner PaaS service; and

directly consuming the bound Partner PaaS service with the deployed Application.

9. The non-transitory, computer-readable medium of claim 8, wherein the Service Catalog of PaaS services is stored on and returned by the Proxy Service Broker.

10. The non-transitory, computer-readable medium of claim 8, wherein the Proxy Service Broker is associated with a Developer Space associated with the Hoster PaaS.

11. The non-transitory, computer-readable medium of claim 8, wherein the unique service identifier for the created instance of the Partner PaaS service is created by the Proxy Service Broker to avoid name clashes on the Partner PaaS.

12. The non-transitory, computer-readable medium of claim 8, further comprising one or more instructions executable to transmit, using the Proxy Service Broker, a call to the Partner Service Broker on the Partner PaaS to create a service key for the created instance of the Partner PaaS service.

13. The non-transitory, computer-readable medium of claim 12, wherein a single service user is used to transmit the call to create the instance of the Partner PaaS service and to create the service key for the created instance of the Partner PaaS service.

14. The non-transitory, computer-readable medium of claim 12, wherein the calls to the Partner PaaS from the Proxy Service Broker are Representational State Transfer (REST) calls.

15. A computer-implemented system, comprising:

a computer memory; and

a hardware processor interoperably coupled with the computer memory and configured to perform operations comprising;

receiving, at a Proxy Service Broker on a Hoster Platform as a Service (PaaS), a request for a Service Catalog including PaaS services available from a Partner PaaS;

initiating creation, using the Proxy Service Broker, of an instance of a Partner PaaS service selected from the Service Catalog;

transmitting, using the Proxy Service Broker, a call to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS;

deploying an Application on the Hoster PaaS to consume the instance of the Partner PaaS service;

binding the deployed Application with the instance of the Partner PaaS service; and

directly consuming the bound Partner PaaS service with the deployed Application.

16. The computer-implemented system of claim 15, wherein the Service Catalog of PaaS services is stored on and returned by the Proxy Service Broker.

17. The computer-implemented system of claim 15, wherein the Proxy Service Broker is associated with a Developer Space associated with the Hoster PaaS.

18. The computer-implemented system of claim 15, wherein the unique service identifier for the created instance of the Partner PaaS service is created by the Proxy Service Broker to avoid name clashes on the Partner PaaS.

19. The computer-implemented system of claim 15, further configured to transmit, using the Proxy Service Broker, a call to the Partner Service Broker on the Partner PaaS to create a service key for the created instance of the Partner PaaS service.

20. The computer-implemented system of claim 19, wherein:

a single service user is used to transmit the call to create the instance of the Partner PaaS service and to create the service key for the created instance of the Partner PaaS service; and

the calls to the Partner PaaS from the Proxy Service Broker are Representational State Transfer (REST) calls.