Interconnection platform for real-time configuration and management of a cloud-based services exchange

Patent metadata

Field	Value
Publication number	US-2024223443-A1
Application number	US-202418607373-A
Country	US
Kind code	A1
Filing date	Mar 15, 2024
Priority date	Oct 30, 2014
Publication date	Jul 4, 2024
Grant date	—

Abstract

In one example, a cloud-based services exchange comprises a plurality of interconnection assets configured to connect a customer of the cloud-based services exchange to one or more cloud service providers, the plurality of interconnection assets including a virtual circuit by which the customer accesses a cloud service from the one or more cloud service providers; and an orchestration engine configured to modify the plurality of interconnection assets.

First claim

What is claimed is:

1 . A system comprising:
a plurality of cloud exchanges located in respective metropolitan areas, wherein each cloud exchange of the cloud exchanges includes one or more data centers located in the corresponding metropolitan area for the cloud exchange, and wherein each of the data centers includes interconnection assets for connecting networks of customers of a cloud exchange provider of the cloud exchanges; and an interconnection platform configured for execution by one or more computing devices, wherein the interconnection platform comprises:
one or more application programming interfaces (APIs) that include endpoints representing different resources of the cloud exchanges to provide, to the customers, programmable access to interconnection assets of the cloud exchanges;
one or more cloud exchange API services for accessing services of the interconnection platform to modify network infrastructures of any of the cloud exchanges,
wherein the interconnection platform is configured to receive, from a customer device associated with a first customer of the customers, a first request invoking a first endpoint of the endpoints, the first request specifying a HyperText Transfer Protocol POST method and requesting a virtual circuit to enable communications between a port for the first customer and a first cloud service within a first cloud exchange of the cloud exchanges, wherein the port is located within one of the data centers, wherein the interconnection platform is configured to receive, from a provider device associated with a cloud service provider for the first cloud service, a second request invoking the first endpoint of the endpoints, the request specifying a PATCH method, and wherein the interconnection platform is configured to, in response to determining the second request indicates the cloud service provider accepts the virtual circuit, orchestrate the cloud exchange API services to modify the network infrastructure of the first cloud exchange to create the virtual circuit to enable communications between the port for the first customer and the first cloud service within the first cloud exchange.

2 . The system of claim 1 ,
wherein the interconnection platform is configured to, in response to determining the second request indicates the cloud service provider rejects the virtual circuit, output a notification message to the customer device that the virtual circuit has been rejected.

3 . The system of claim 1 ,
wherein, to orchestrate the cloud exchange API services, the interconnection platform is configured to use a first API service of the cloud exchange API services to invoke a microservice, provided by the cloud service provider, to enable a port for the first cloud service.

4 . The system of claim 1 ,
wherein a cloud service provider network of the cloud service provider is connected to one or more ports of the first cloud exchange, wherein the second request, received from the provider device, specifies a first port of the one or more ports of the first cloud exchange, and wherein, to orchestrate the cloud exchange API services, the interconnection platform is configured to create the virtual circuit to enable communications between the port for the first customer to the first port specified in the second request.

5 . The system of claim 1 ,
wherein the first request, received from the first customer, specifies a first metropolitan area of the metropolitan areas, wherein the interconnection platform is configured to, based on the first metropolitan area in which the first cloud exchange is located, orchestrate the cloud exchange API services to modify the network infrastructure of the first cloud exchange to create the virtual circuit.

6 . The system of claim 5 ,
wherein, to orchestrate the cloud exchange API services, the interconnection platform is configured to invoke a metro service to validate the first metropolitan area and to modify, in response to receiving an indication from the metro service that the first metropolitan area is valid, the network infrastructure of the first cloud exchange to create the virtual circuit.

7 . The system of claim 1 ,
wherein the interconnection platform is configured to receive, from the customer device, a third request invoking a metro endpoint of the endpoints, and wherein the interconnection platform is configured to, in response to the third request, output a list of all metropolitan areas in which a cloud exchange is located or in which the first customer has purchased a port of a data center of the cloud exchange provider.

8 . The system of claim 1 ,
wherein the interconnection platform is configured to received, from the customer device, a third request invoking a metro endpoint of the endpoints and including a cloud_exchange_enabled flag, and wherein the interconnection platform is configured to, in response to the third request, filter a list of all metropolitan areas that include a data center of the cloud exchange provider to generate and output a list of all metropolitan areas in which a cloud exchange is located.

9 . The system of claim 1 ,
wherein the interconnection platform is configured to receive, from the customer device, a third request invoking a port endpoint of the endpoints, wherein the interconnection platform is configured to, in response to the third request, output a list of port structures for ports purchased by the first customer from the cloud exchange provider, and wherein each port structure includes a port identifier for an owned port, a metropolitan area in which the owned port is located, and a data center identifier for a data center in which the owned port is located.

10 . The system of claim 9 ,
wherein the third request specifies a metropolitan area, and wherein the interconnection platform is configured to, in response to the third request, filter all ports in the data centers that are purchased by the first customer to generate the list of port structures to include only port structures for owned ports located in a data center in the specified metropolitan area.

11 . The system of claim 9 ,
wherein the third request specifies a metropolitan area and a data center within the metropolitan area, and wherein the interconnection platform is configured to, in response to the third request, filter all ports in the data centers that are purchased by the first customer to generate the list of port structures to include only port structures for owned ports located in the specified metropolitan area and the specified data center.

12 . The system of claim 1 ,
wherein the interconnection platform is configured to receive, from the customer device, a third request invoking a cloud services endpoint of the endpoints, and wherein the interconnection platform is configured to, in response to the third request, output a list of cloud services data structures specifying cloud services available at the cloud exchanges.

13 . The system of claim 12 ,
wherein each of the cloud services data structures indicates a cloud service name of a cloud service, a metropolitan area in which the cloud service is available, and a list of data centers in the metropolitan area in which the cloud service is available.

14 . An interconnection platform for a plurality of cloud exchanges, comprising:
one or more processors coupled to memory; one or more application programming interfaces (APIs) that include endpoints representing different resources of the cloud exchanges to provide, to customers of a cloud exchange provider of the cloud exchanges, programmable access to interconnection assets

Assignees

• Equinix Inc

Inventors

• Kumar Parveen
• Maheshwari Gagan
• Jeyapaul Jaganathan
• Lillie Brian J

Classifications

• H04L41/00

  Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks · CPC title

• H04L47/70

  Admission control; Resource allocation · CPC title

• H04L41/0803 Primary

  Configuration setting · CPC title

• G06F8/30 Primary

  Creation or generation of source code · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title