WO2016183253A1 - Plateforme de réseau programmable pour échange de services en nuage - Google Patents

Plateforme de réseau programmable pour échange de services en nuage Download PDF

Info

Publication number
WO2016183253A1
WO2016183253A1 PCT/US2016/031943 US2016031943W WO2016183253A1 WO 2016183253 A1 WO2016183253 A1 WO 2016183253A1 US 2016031943 W US2016031943 W US 2016031943W WO 2016183253 A1 WO2016183253 A1 WO 2016183253A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud
service
network
sendee
services
Prior art date
Application number
PCT/US2016/031943
Other languages
English (en)
Inventor
Ravindra Rao
Original Assignee
Equinix, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US15/001,839 external-priority patent/US9967350B2/en
Application filed by Equinix, Inc. filed Critical Equinix, Inc.
Priority to JP2016573993A priority Critical patent/JP6495949B2/ja
Priority to CN201680001701.4A priority patent/CN106464742B/zh
Priority to AU2016262538A priority patent/AU2016262538B2/en
Priority to BR112016029203A priority patent/BR112016029203A2/pt
Priority to EP16725682.5A priority patent/EP3155759B1/fr
Priority to CA2951944A priority patent/CA2951944C/fr
Priority to SG11201610055VA priority patent/SG11201610055VA/en
Priority to EP19193146.8A priority patent/EP3588861B1/fr
Priority to EP23175205.6A priority patent/EP4236252A3/fr
Publication of WO2016183253A1 publication Critical patent/WO2016183253A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications

Definitions

  • the invention relates to computer networks and, more specifically, to facilitating service provisioning and delivery among cloud service customers and cloud service providers.
  • Cloud computing refers to the use of dynamically scalable computing resources accessible via a network, such as the Internet.
  • the computing resources often referred to as a “cloud, " provide one or more services to users. These services may be categorized according to service types, which may include for examples, applications/software, platforms, infrastructure, virtualization, and servers and data storage.
  • service types may include for examples, applications/software, platforms, infrastructure, virtualization, and servers and data storage.
  • the names of service types are often prepended to the phrase "as-a-Service” such that the delivery of applications/software and infrastructure, as examples, may be referred to as Software-as- a-Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (laaS), respectively.
  • SaaS Software-as- a-Service
  • PaaS Platform-as-a-Service
  • laaS Infrastructure-as-a-Service
  • cloud-based services or, more simply, “cloud services” refers not only to sen/ices provided by a cloud, but also to a form of sen-ice provisioning in which cloud customers contract with cloud sendee providers for the online delivery of sendees provided by the cloud.
  • Cloud service providers manage a public, private, or hybrid cloud to facili tate the online deliver ⁇ ' of cloud services to one or more cloud customers.
  • this disclosure describes a programmable network platform for dynamically programming a cloud-based sendee exchange (“cloud exchange”) to responsivelv and assuredly fulfill sen/ice requests that encapsulate business requirements for services provided by the cloud exchange and/or cloud service providers coupled to the cloud exchange.
  • the programmable network platform as described herein may, as a result, orchestrate a business-level sendee across heterogeneous cloud service providers according to well-defined service policies, quality of service, service level agreements, and costs, and further according to a service topology for the business-level service.
  • the programmable network platform enables the cloud service provider that administers the cloud exchange to dynamically configure and manage the cloud exchange to, for instance, facilitate virtual connections for cloud services delivery from multiple cloud sendee providers to one or more cloud customers.
  • the cloud exchange may enable cloud customers to bypass the public Internet to directly connect to cloud sendees providers so as to improve performance, reduce costs, increase the security and privacy of the connections, and leverage cloud computing for additional applications.
  • enterprises, network carriers, and SaaS customers for instance, can at least in some aspects integrate cloud services with their internal applications as if such services are part of or otherwise directly coupled to their own data center network.
  • a programmable network platform operates according to a distributed model in which a centralized network controller (CNC) manages globally-distributed and intelligent logic in the form of network field units (NFUs).
  • the CNC may receive a business sendee request via an interface and convert the business sendee request into business instantiation parameters and network provisioning parameters to be delivered and assured as a business sendee within the cloud exchange.
  • the CNC thus operates as a central intelligent processing unit of the programmable network platform.
  • Each instantiation of a programmable network platform may have one logical instance of this intelligent logic (i .e., the CNC).
  • the CNC may- provide service assurance using a Monitor, Analyze, Plan and Execute (MAPE) loop methodology and is implemented to ensure the sendee level agreements are adhered to by the se ' ice.
  • MEE Monitor, Analyze, Plan and Execute
  • the various NFUs are distributed among globally-distributed cloud exchange points of a cloud exchange provider that administers the programmable network platform.
  • Each NFU receives network instantiation commands/parameters from the CNC and instantiates and configures the network resource(s) that is needed to deliver the service.
  • the NFU has the intelligence to deliver and assure network services according to CNC requests.
  • the NFU further has the capability of communicating with a third party orchestration system, if needed by the service request.
  • the NFU applies a separate MAPE loop to ensure that the network se dees delivered by the unit is assured for the life cycle of the service
  • a programmable network platform described herein may provide for orchestrating a sendee thai involves both native and third-party components as single sendee while ensuring policy, security, and SLA consistency.
  • the programmable network platform may orchestrate the third-part ⁇ ' sendee components using a third-party (or "partner") orchestration module (or "plugin").
  • a third-party orchestration module allows a third-party orchestration system to register its capabilities (e.g., sendee catalog, policy, security and SLA) with the programmable network platform.
  • the cloud sendee provider may use the programmable network platform to direct the third-party orchestration system, via the corresponding third-party orchestration module, as part of the workflow for the sendee delivery to stand-up and deliver a third-party sendee for the sendee.
  • the programmable network platform described herein may provision a cloud exchange to deliver services made up of multiple constituent services provided by multiple different cloud sendee providers.
  • Each of these constituent services is referred to herein as a "micro-sendee" in that it is part of an overall service applied to sendee traffic. That is, a plurality of micro-sendees may be applied to sendee traffic in a particular "arrangement,” “ordering,” or “topology,” in order to make up an overall sendee for the sendee traffic.
  • the micro-sendees themselves may be applied or offered by the cloud service providers.
  • the programmable network platform may in tins way orchestrate a business-level sen ice across heterogeneous cloud sendee providers.
  • the programmable network platform exposes interfaces by which a portal, console (e.g., user interface application), or other application may define the sendee policy, quality, SLAs, and cost as a coordinated sendee topology made up of micro-services provided by different cloud service providers (or "cloud vendors").
  • a portal, console e.g., user interface application
  • Each micro-sendee may have a corresponding sendee policy, quality, SLA, and cost, as part of the overall, end-to-end business service definition.
  • the programmable network platform When provided with a service definition for an end-to-end service having multiple component micro-sendees, the programmable network platform orchestrates each of the micro-sendees within the cloud exchange and stitches the micro-sendees together according to the defined topology in order to reify the end-to-end service within die cloud exchange data plane (e.g., an edge network for the cloud exchange).
  • die cloud exchange data plane e.g., an edge network for the cloud exchange.
  • the cloud exchange interconnects, in the data plane, micro-services provided by respective cloud se dees providers on behalf of and for the benefit of a customer of the cloud exchange.
  • the cloud exchange provider may facilitate business transactions between the cloud sen/ice providers and customers.
  • a programmable network platform as described herein may orchestrate each of the micro-services within the cloud exchange and stitch the micro-services together according to the defined topology in order to reify the end-to-end service within the cloud exchange.
  • the service definition for an end-to-end service may enable a user of the programmable network platform to define not only the end-to-end service but also the sen-ice topology in such a ways as to ensure the correct sequencing of the micro-sendees sendee chain.
  • the data encapsulated in the data model for the service definition may also include the authoritative sendee owner for business purposes (e.g., billing and SLA assurance).
  • the "user” may refer to a customer, the cloud exchange provider, or a cloud service provider that is the authoritative sendee owner.
  • the programmable network platform (and/or other orchestration systems such as software-defined networking (SDN) controllers or orchestrators) may be enabled to recognize a service request as a request for a set of micro-services that make up the entire senice.
  • the sendee definition includes several sections that will enable the programmable network platform to provide the senice of chaining several services, whether of native services provided by the cloud exchange provider or of cloud sendees provided one or multiple cloud senice providers.
  • the cloud exchange provider that administers the programmable network platform is able to provide a chaining service that, when given respective definitions for multiple micro-services and a topology (or sequence) for the multiple micro-sendees, interconnects the micro-sendees according to the topology to facilitate an end-to-end service.
  • the data model thus provides data with which the programmable network platform can effectively instantiate the requested chain of services and to also ensure that the services thus rendered are chained in the correct topology.
  • the data model may be divided by the programmable network platform into one or more senice requests that the native programmable network platform for the cloud exchange may issue to other sendee orchestration systems to complete.
  • Other service orchestration systems may include, e.g., SDN controllers and/or orchestration systems for cloud sen/ice providers that facilitate NFV -instantiation and service traffic routing to/from NFV instances.
  • a method comprises receiving, by a programmable network platform for a cloud-based services exchange point within a data center, a service request that includes a service definition according to a data model, wherein the service definition specifies a plurality of cloud services provided by respective cloud service provider networks operated by respective cloud service providers, wherein the service request further specifies a topology for the plurality of cloud services; and provisioning, by the programmable network platform responsive to the service request, the cloud-based services exchange point to forward service traffic for the plurality of cloud services according to the topology for the plurality of cloud services,
  • a network data center comprises a cloud-based sen/ices exchange point comprising a network, the cloud-based services exchange point operated by a cloud exchange provider that operates the network data center: and a programmable network platform comprising at least one programmable processor configured to receive a service request that includes a service definition according to a data model, wherein the service definition specifies a plurality of cloud services provided by respective cloud service provider networks operated by respective cloud service providers, wherein the sen-ice request further specifies a topology for the plurality of cloud services, and wherein the service definition specifies each of the plurality of cloud services according to a common micro-sendee definition; and provision, responsive to the service request, the cloud-based sen/ices exchange point to forward sendee traffic for the plurality of cloud services according to the topology for the plurality of cloud services.
  • a method comprises receiving, by a programmable network platform for a cloud-based services exchange point within a data center, a sendee request that specifies a plurality of cloud sendees provided by respective cloud sen/ice provider networks operated by respective cloud service providers, wherein the sendee request further specifies a topology for the plurality of cloud sendees; and provisioning, by the programmable network platform responsive to the sendee request, the cloud-based services exchange point to forward service traffic for the plurality of cloud services according to the topology for the plurality of cloud services.
  • network data center comprises a cloud-based sendees exchange point comprising a network, the cloud-based services exchange point operated by a cloud exchange provider that operates the network data center; and a programmable network platform comprising at least one programmable processor configured to receive a service request that specifies a plurality of cloud services provided by respective cloud service provider networks operated by respective cloud service providers, wherein the service request further specifies a topology for the plurality of cloud sendees; and provision, responsive to the sendee request, the cloud-based services exchange point to forward service traffic for the plurality of cloud sendees according to the topology for the plurality of cloud sendees.
  • programmable network platform comprises at least one programmable processor: a third-part ⁇ ' orchestration module configured for execution by the at least one programmable processor to communicate with a cloud sendee provider orchestration system; and a centralized network controller configured for execution by the at least one programmable processor to receive a service request that specifies a cloud sendee applied by a cloud service provider network operated by a cloud service provider on a network of a cloud exchange operated by a cloud exchange provider, wherein the centralized network controller is further configured to, in response to the sendee request, invoke the third-party orchestration module to communicate with the cloud sendee provider orchestration system to request that the cloud sendee provider orchestrate the cloud sendee on the network of the cloud exchange, and wherein the centralized network controller provisions the network of the cloud exchange within a data center to deliver the cloud service from the cloud sendee provider network attached to the network of the cloud exchange to a customer network attached to the network of the cloud exchange.
  • a method comprises receiving, by a centralized network controller of a programmable network platform, a service request that specifies a cloud sen ice applied by a cloud sendee provider network operated by a cloud sendee provider on a network of a cloud exchange operated by a cloud exchange provider; invoking, by the centralized network controller in response to the service request, a third-party orchestration module to communicate with the cloud sendee provider orchestration system, to request that the cloud sendee provider orchestrate the cloud sendee on the network of the cloud exchange; and provisioning, by the centralized network controller, the network of the cloud exchange within a data center to deliver the cloud service, from the cloud sendee provider network attached to the cloud-based sendees exchange point, to a customer network attached to the cloud-based sendees exchange point.
  • network data center comprises a cloud exchange comprising a network, the cloud exchange operated by a cloud exchange provider; and a programmable network platform comprising at least one programmable processor; a third-party orchestration module to communicate with a cloud service provider orchestration system; and a centralized network controller configured for execution by the at least one programmable processor to receive a service request that specifies a cloud service applied by a cloud service provider network operated by a cloud service provider on the network of a cloud exchange, wherein the centralized network controller is further configured to, in response to the service request, invoke the third-party orchestration module to communicate with the cloud service provider orchestration system to request that the cloud service provider orchestrate the cloud service on the network of the cloud exchange, and wherein the centralized network controller provisions the network of the cloud exchange to deliver the cloud sen/ice from the cloud sen/ice provider network attached to the network of the cloud exchange to a customer network attached to the network of the cloud exchange.
  • a method comprises providing, by a centralized network control (CNC) system, a software interface to receive service requests for configuration of services within an edge network of one or more network data centers that are controlled by the CNC system; receiving, by the CNC system, and via the software interface, a service request to configure a sen/ice within the edge network of the network data center, wherein the edge network within the one or more network data centers connects through one or more switching fabrics of the one or more network data centers; generating, by the CNC system and based on the service request, a network service definition that specifies one or more sendee requirements to implement the sendee; determining, by the CNC system and based on the network service definition, at least one network field unit that is capable of servicing the sendee request, wherein the network field unit controls a portion of the edge network, wherein the network sendee definition is usable by the at least one network field unit to configure the portion of the edge network to provide the service; and sending, by the CNC system and to the at least one network
  • centralized network control (CNC) system comprises one or more computer processors; and a memory comprising instructions that when executed by the one or more computer processors cause the one or more computer processors to provide a software interface to receive sendee requests for configuration of sen/ices within an edge network of one or more network data centers that are controlled by the CNC system; receive, via the software interface, a sen/ice request to configure a sen-ice within the edge network of the network data center, wherein the edge network within the one or snore network data centers connects through one or more switching fabrics of the one or more network data centers; generate, based on the service request, a network sen-ice definition that specifies one or more se -ice requirements to implement the sendee; determine, based on the network service definition, at least one network field unit that is capable of servicing the sen- ice request, wherein the network field unit controls a portion of the edge network, wherein the network sendee definition is usable by the at least
  • a method comprises receiving, by at least one network field unit, a network sendee definition that specifies one or more service requirements to implement a network sen-ice within a portion of an edge network of one or more network data centers, wherein the network service definition is usable by the at least one network field unit to configure the portion of the edge network to provide the network service, wherein the portion of the edge network within one or more network data centers connect through one or more switching fabrics of the one or more network data centers; determining, by the network field unit and based on the network sendee definition, one or more particular, physical devices of the edge network that are usable to provide the sendee; and configuring, by the network field unit, the one or more particular, physical devices of the edge network to provide the network service.
  • a network field unit comprises one or more computer processors; and a memory comprising instructions that when executed by the one or more computer processors cause the one or more computer processors to receive a network sen-ice definition that specifies one or more service requirements to implement a network sendee within a portion of an edge network of one or more network data centers, wherein the network sendee definition is usable by the at least one network field unit to configure the portion of the edge network to provide the network sendee, wherein the portion of the edge network within one or more network data centers connect through one or more switching fabrics of the one or more network data centers; determine, based on the network sendee definition, one or more particular, physical devices of the edge network that are usable to provide the service; and
  • a method comprises providing, by a programmable network platform (PNP), a software interface to receive sen'ice requests for configuration of services within an edge network of one or more network data centers that are controlled by the PNP: receiving, by the PNP and via the software interface, a sen/ice request to configure a network service within the edge network of the one or more network data centers, wherein the edge network within the one or more network data centers connect through one or more switching fabrics of the one or more network data centers; generating, by the PNP and based on the service request, a network service definition that specifies one or more sen'ice requirements to implement the network sendee; determining, by the PNP and based on the network service definition, at least one network field unit that is capable of servicing the service request, wherein the network field unit controls a portion of the edge network, wherein the network sendee definition is usable by the at least one network field unit to configure the portion of edge netw ork to provide the sendee; determining, by a programmable network platform
  • a programmable network platform comprises one or more computer processors; and a memory comprising instructions that when executed by the one or more computer processors cause the one or more computer processors to provide a software interface to receive sendee requests for configuration of services within an edge network of one or more network data centers that are controlled by the PNP; receive a service request to configure a network service within the edge network of the one or more network data, centers, wherein the edge network within the one or more network data centers connect through one or more switching fabrics of the one or more network data centers; generate a network sendee definition that specifies one or more sendee requirements to implement the network sendee; determine, by the PNP and based on the network service definition, at least one network field unit that is capable of servicing the service request, wherein the network field unit controls a portion of the edge network, wherein the network sendee definition is usable by the at least one network field unit to configure the portion of edge network to provide the sendee; determine, based on the network service definition
  • FIG. 1 is a block diagram that illustrates a high-level vie of a data center that provides an operating environment for a cloud-based sendees exchange.
  • FIG. 2 is a block diagram illustrating a high-level view of a data center that provides an operating environment for a cloud-based services exchange, according to techniques described herein.
  • FIGS. 3A-3B are block diagrams illustrating example network infrastructure and sen-ice provisioning by a programmable network platform for a cloud exchange that aggregates the cloud services of multiple cloud senice providers for provisioning to customers of the cloud exchange provider and aggregates access for multiple customers to one or more cloud sendee providers, in accordance with techniques described in this disclosure.
  • FIG. 4 is a block diagram illustrating an example of a data center-based cloud exchange point in which routers of the cloud exchange point are configured by programmable network platform with VPN routing and fonvarding instances for routing and forwarding aggregated service traffic from multiple cloud service provider networks to a customer network, according to techniques described herein.
  • FIG. 5 is a block diagram illustrating a platform for a software controlled network, the platform operating in accordance with one or more techniques of the present disclosure.
  • FIG. 6 is a block diagram illustrating an example sendee provisioning engine, in accordance with one or more techniques of the present disclosure.
  • FIG. 7 is a block diagram illustrating an example sendee assurance engine, in accordance with one or more techniques of the present disclosure.
  • FIG. 8 is a block diagram illustrating an example network provisioning engine, in accordance with one or more techniques of the present disclosure.
  • FIG. 9 is a block diagram illustrating an example network assurance engine, in accordance with one or more techniques of the present disclosure.
  • FIG. 10 is a block diagram illustrating a programmable network platform, in accordance with one or more techniques of the present disclosure.
  • FIG. 11 is a block diagram illustrating an example user interface to request a sen-ice, in accordance with one or more techniques of the present disclosure.
  • FIG. 12 is a block diagram illustrating an example user interface to display a cost estimate for a service, in accordance with one or more techniques of the present disclosure.
  • FIG. 13 is a conceptual diagram illustrating example components for a programmable network platform operating according to techniques described in this disclosure.
  • FIG. 14A is a block diagram that illustrates an example configuration of a programmable edge network that has been configured to apply multiple native services to cloud senice traffic aggregated by a cloud exchange from multiple cloud service providers for delivery to a customer.
  • FIG. 14B is a block diagram that illustrates an example configuration of a programmable edge network that has been configured to offer an end-to-end service that is a sequence of multiple constituent micro-services applied by respective cloud service providers.
  • FIG. 15 is a conceptual diagram illustrating interfaces among components for programming a cloud exchange using a programmable network platform according to techniques described in this disclosure.
  • FIG. 16 is a block diagram illustrating a programmable network platform that includes interfaces by w hich external applications may configure a cloud exchange to facilitate deliveiy of cloud sendees from cloud service providers according to techniques described in this disclosure.
  • FIG. 17 is a block diagram illustrating further details of one example of a computing device that operates in accordance with one or more techniques of the present disclosure.
  • this disclosure describes a programmable network platform for reai- time configuration and management of a cloud-based services exchange ("cloud exchange " ').
  • the interconnection platform provides customers of the exchange, e.g., enterprises, network carriers, and SaaS customers, with secure, private, virtual connections to multiple cloud service providers (CSPs) globally.
  • CSPs cloud service providers
  • the multiple CSPs participate in the cloud exchange by virtue of their having at least one accessible port in the cloud exchange by which a customer can connect to the one or more cloud services offered by the CSPs, respectively.
  • a cloud exchange is described that allows private networks of any customer to be directly cross-connected to any other customer at a common point, thereby allowing direct exchange of network traffic between the networks of the customers.
  • Customers may include network carriers (or network sen-ice providers), enterprises, and other users of cloud services offered by one or more cloud service providers.
  • FIG. 1 illustrates a conceptual view? of a network system. 2 having a metro-based cloud exchange that provides multiple cloud exchange points according to techniques described herein.
  • Each of cloud-based services exchange points 128A- 128D (described hereinafter as “cloud exchange points” and collectively referred to as “cloud exchange points 128 ' ') of cloud-based services exchange 100 (“cloud exchange 100") may represent a different data center geographically located within the same metropolitan area ("metro- based,” e.g., in New York City, New York; Silicon Valley, California; Seattle-Tacoma, Washington; Minneapolis-St.
  • cloud exchange 00 may include more or fewer cloud exchange points 128.
  • a cloud exchange 100 includes just one cloud exchange point 128.
  • a cloud exchange provider may deploy instances of cloud exchanges 100 in multiple different metropolitan areas, each instance of cloud exchange 100 having one or more cloud exchange points 128.
  • Each of cloud exchange points 128 includes network infrastructure and an operating environment by which cloud customers 108A-108D (collectively, “cloud customers 108") receive cloud services from multiple cloud sendee providers 110A-- 110N (collectively, “cloud service providers 110").
  • Cloud customers 108 may receive cloud-based services directly via a layer 3 peering and physical connection to one of cloud exchange points 128 or indirectly via one of network service providers 106A- 106B (collectively, "NSPs 106," or alternatively, '"carriers 106").
  • NSPs 106 provide '"cloud transit” by maintaining a physical presence within one or more of cloud exchange points 128 and aggregating layer 3 access from one or customers 108.
  • NSPs 106 may peer, at layer 3, directly with one or more cloud exchange points 128 and in so doing offer indirect layer 3 connectivity and peering to one or more customers 108 by which customers 108 may obtain cloud sen/ices from the cloud exchange 100.
  • Each of cloud exchange points 128, in the example of FIG. 1, is assigned a different autonomous system number (ASN).
  • ASN autonomous system number
  • cloud exchange point 128A is assigned ASN 1
  • cloud exchange point 128B is assigned ASN 2, and so forth.
  • Each cloud exchange point 128 is thus a next hop in a path vector routing protocol (e.g., BGP) path from cloud service providers 110 to customers 108.
  • BGP path vector routing protocol
  • each cloud exchange point 128 may, despite not being a transit network having one or more wide area network links and concomitant Internet access and transit policies, peer with multiple different autonomous systems via external BGP (eBGP) or other exterior gateway routing protocol in order to exchange, aggregate, and route service traffic from one or more cloud service providers 110 to customers.
  • eBGP external BGP
  • cloud exchange points 128 may internalize the eBGP peering relationships that cloud service providers 1 10 and customers 108 would maintain on a pair-wise basis.
  • a customer 108 may configure a single eBGP peering relationship with a cloud exchange point 128 and receive, via the cloud exchange, multiple cloud sen-ices from one or more cloud sen/ice providers 110.
  • the cloud exchange points may learn routes from these networks in other way, such as by static configuration, or via Routing Information Protocol (RIP), Open Shortest Path First (OSPF), Intermediate System-to-intermediate System (IS-IS), or other route distribution protocol.
  • RIP Routing Information Protocol
  • OSPF Open Shortest Path First
  • IS-IS Intermediate System-to-intermediate System
  • customer 108C is illustrated as having contracted with a cloud exchange provider for cloud exchange 100 to directly access layer 3 cloud services via cloud exchange points 128C.
  • customer I08D receives redundant layer 3 connectivity to cloud service provider 110A, for instance.
  • Customer 108C in contrast, is illustrated as having contracted with the cloud exchange provider for cloud exchange 100 to directly access layer 3 cloud services via cloud exchange point 128C and also to have contracted with NSP 106B to access layer 3 cloud services via a transit network of the NSP 106B.
  • Customer 108B is illustrated as having contracted with multiple NSPs 106A, 106B to have redundant cloud access to cloud exchange points 128A, 128B via respective transit networks of the NSPs 106A, 106B.
  • the contracts described above are instantiated in network infrastructure of the cloud exchange points 128 by L3 peering configurations within switching devices of NSPs 106 and cloud exchange points 128 and L3 connections, e.g., layer 3 virtual circuits, established within cloud exchange points 128 to interconnect cloud service provider 110 networks to NSPs 106 networks and customer 108 networks, all having at least one port offering connectivity within one or more of the cloud exchange points 128.
  • cloud exchange 100 allows a corresponding one of customer customers 108A, 108B of any network service providers (NSPs) or "carriers" 106A-106B (collectively, “carriers 106") or other cloud customers including customers 108C to be directly cross-connected, via a virtual layer 2 (L2) or layer 3 (L-3) connection to any other customer network and/or to any of CSPs 1 10, thereby allowing direct exchange of network traffic among the customer networks and CSPs 110.
  • NSPs network service providers
  • carriers 106A-106B collectively, “carriers 106”
  • L2 virtual layer 2
  • L-3 layer 3
  • Carriers 106 may each represent a network service provider that is associated with a transit network by which network subscribers of the carrier 106 may access cloud sen-ices offered by CSPs 110 via the cloud exchange 100.
  • customers of CSPs 110 may include network carriers, large enterprises, managed service providers (MSPs), as well as Software-as-a-Service (SaaS), Platform-aaS (PaaS), Infrastructure-aaS (laaS), Virtualization-aaS (VaaS), and data Storage-aaS (dSaaS) customers for such cloud-based services as are offered by the CSPs 110 via the cloud exchange 100.
  • MSPs managed service providers
  • SaaS Software-as-a-Service
  • PaaS Platform-aaS
  • laaS Infrastructure-aaS
  • VaaS Virtualization-aaS
  • dSaaS data Storage-aaS
  • cloud exchange 100 streamlines and simplifies the process of partnering CSPs 1 10 and customers (via carriers 106 or directly) in a transparent and neutral manner.
  • One example application of cloud exchange 100 is a co-location and interconnection data center in which CSPs 110 and carriers 106 and/or customers 108 may already have network presence, such as by having one or more accessible ports available for interconnection within the data center, which may represent any of cloud exchange points 128.
  • This allows the participating carriers, customers, and CSPs to have a wide range of interconnectivity options within the same facility.
  • a carrier/customer may in this way have options to create many-to-many interconnections with only a one-time hook up to one or more cloud exchange points 128.
  • cloud exchange 100 allows customers to interconnect to multiple CSPs and cloud services.
  • cloud exchange 100 includes a programmable network platform 120 for dynamically programming cloud exchange 100 to responsively and assuredly fulfill sen-ice requests that encapsulate business requirements for sendees provided by cloud exchange 100 and/or cloud service providers 110 coupled to the cloud exchange 100.
  • the programmable network platform 120 as described herein may, as a result, orchestrate a business-level sendee across heterogeneous cloud service providers 110 according to well-defined sen-ice policies, quality of sen-ice policies, sendee level agreements, and costs, and further according to a service topology for the business-level sendee.
  • the programmable network platform 120 enables the cloud service provider that administers the cloud exchange 100 to dynamically configure and manage the cloud exchange 100 to, for instance, facilitate virtual connections for cloud-based sendees delivery from multiple cloud service providers 1 10 to one or more cloud customers 108.
  • the cloud exchange 100 may enable cloud customers 108 to bypass the public Internet to directly connect to cloud sendees providers 1 10 so as to improve performance, reduce costs, increase the security and privacy of the connections, and leverage cloud computing for additional applications.
  • enterprises, network carriers, and SaaS customers for instance, can at least in some aspects integrate cloud services with their internal applications as if such sendees are part of or otherwise directly coupled to their own data center network.
  • Programmable network platform 120 may represent an application executing within one or more data centers of the cloud exchange 100 or alternatively, off-site at a back office or branch of the cloud provider (for instance). Programmable network platform 120 may be distributed in whole or in part among the data centers, each data center associated with a different cloud exchange point 128 to make up the cloud exchange 100. Although shown as administering a single cloud exchange 100, programmable network platform 120 may control service provisioning for multiple different cloud exchanges. Alternatively or additionally, multiple separate instances of the programmable network platform 120 may control service provisioning for respective multiple different cloud exchanges.
  • programmable network platform 120 includes a service interface (or " 'service API") 114 that defines the methods, fields, and/or other software primitives by which applications may invoke the programmable network platform 120.
  • the service interface 114 may allow carriers 106, customers 108, cloud service providers 110, and/or the cloud exchange provider programmable access to capabilities and assets of the cloud exchange 100.
  • the service interface 114 may facilitate machine-to-machine communication to enable dynamic provisioning of virtual circuits in the cloud exchange for interconnecting customer and cloud service provider networks.
  • the programmable network platform 120 enables the automation of aspects of cloud services provisioning.
  • the sendee interface 114 may provide an automated and seamless way for customers to establish, de-install and manage interconnection with multiple, different cloud providers participating in the cloud exchange.
  • FIG. 2 is a block diagram illustrating a high-level view of a data center 201 that provides an operating environment for a cloud-based sendees exchange 200, according to techniques described herein.
  • Cloud-based services exchange 200 (“cloud exchange 200") allows a corresponding one of customer networks 204D, 204E and NSP networks 204A- 204C (collectively, "'private' or 'earner' networks 204") of any NSPs 106A-106C or other cloud customers including customers 108A, 108B to be directly cross-connected, via a layer 3 (L3) or layer 2 (L2) connection to any other customer network and/or to any of cloud service providers I I 0A-- HON, thereby allowing exchange of cloud service traffic among the customer networks and CSPs 110.
  • L3 layer 3
  • L2 layer 2
  • Data center 201 may be entirely located within a centralized area, such as a warehouse or localized data center complex, and provide power, cabling, security, and other sendees to NSPs, customers, and cloud service providers that locate their respective networks within the data center 201 (e.g., for co-location) and/or connect to the data center 201 by one or more external links.
  • a centralized area such as a warehouse or localized data center complex
  • Network service providers 106 may each represent a network service provider that is associated with a transit network by which network subscribers of the NSP 106 may access cloud sen-ices offered by CSPs 110 via the cloud exchange 200.
  • customers of CSPs 110 may include network carriers, large enterprises, managed service providers (MSPs), as well as Software-as-a-Service (SaaS), Platform-aaS (PaaS), Infrastructure-aaS (laaS), Virtualization-aaS (VaaS), and data Storage-aaS (dSaaS) customers for such cloud-based sen/ices as are offered by the CSPs 110 via the cloud exchange 200.
  • MSPs managed service providers
  • SaaS Software-as-a-Service
  • PaaS Platform-aaS
  • laaS Infrastructure-aaS
  • VaaS Virtualization-aaS
  • dSaaS data Storage-aaS
  • cloud exchange 200 streamlines and simplifies the process of partnering CSPs 110 and customers 108 (indirectly via NSPs 106 or directly) in a transparent and neutral manner.
  • One example application of cloud exchange 200 is a co- location and interconnection data center in which CSPs 110, NSPs 106 and/or customers 108 may already have network presence, such as by having one or more accessible ports available for interconnection within the data center. This allows the participating carriers, customers, and CSPs to have a wide range of interconnectivity options in the same facility.
  • Cloud exchange 200 of data center 201 includes network infrastructure 222, that provides a L2/L3 switching fabric by which CSPs 110 and customers/NSPs interconnect.
  • cloud exchange 200 allows customers to interconnect to multiple CSPs and cloud services using network infrastructure 222 within data center 201, which may represent any of the edge networks described in this disclosure, at least in part.
  • NSP 106A can expand its services using network 204B of NSP 106B.
  • a NSP 106 may be able to generate additional revenue by offering to sell its network sendees to the other carriers.
  • NSP 106C can offer the opportunity to use NSP network 204C to the other NSPs.
  • Cloud exchange 200 includes an programmable network platform 120 that exposes at least one sendee interfaces, which may include in some examples and are alternatively referred to herein as application programming interfaces (APIs) in that the APIs define the methods, fields, and/or other software primitives by which applications may invoke the programmable network platform 120.
  • the software interfaces allow NSPs 206 and customers 108 programmable access to capabilities and assets of the cloud exchange 200.
  • the programmable network platform 120 may alternatively be referred to as a controller, provisioning platform, provisioning system, service orchestration system, etc., for establishing end-to-end services including, e.g., connectivity between customers and cloud service providers according to techniques described herein.
  • the software interfaces presented by the underlying interconnect platform provide an extensible framework that allows software developers associated with the customers of cloud exchange 200 (e.g., customers 108 and NSPs 206) to create software applications that allow and leverage access to the programmable network platform 120 by which the applications may request that the cloud exchange 200 establish connectivity between the customer and cloud services offered by any of the CSPs 110.
  • these buyer-side software interfaces may allow customer applications for NSPs and enterprise customers, e.g., to obtain authorization to access the cloud exchange, obtain information regarding available cloud services, obtain active ports and metro area details for the customer, create virtual circuits of varying bandwidth to access cloud services, including dynamic selection of bandwidth based on a purchased cloud service to create on-demand and need based virtual circuits to cloud service providers, delete virtual circuits, obtain active virtual circuit information, obtain details surrounding CSPs partnered with the cloud exchange provider, obtain customized analytics data, validate partner access to interconnection assets, and assure service delivery.
  • the software interfaces may allow software developers associated with cloud providers to manage their cloud services and to enable customers to connect to their cloud sendees.
  • these seller-side software interfaces may allow cloud service provider applications to obtain authorization to access the cloud exchange, obtain information regarding available cloud services, obtain active ports and metro area details for the provider, obtain active port details in a given data center for the provider, approve or reject virtual circuits of varying bandwidth created by customers for the purpose of accessing cloud services, obtain virtual circuits pending addition and confirm addition of virtual circuits, obtain virtual circuits pending deletion and confirm deletion of virtual circuits, obtain customized analytics data, validate partner access to interconnection assets, and assure service delivery.
  • the service interface 114 facilitates machine-to- machine communication to enable dynamic se dee provisioning and service delivery assurance.
  • the programmable network platform 120 enables the automation of aspects of cloud services provisioning.
  • the software interfaces may- provide an automated and seamless way for customers to establish, de-install and manage interconnection with multiple, different cloud providers participating in the cloud exchange.
  • the programmable network platform 120 may in various examples execute on one or virtual machines and/or real servers of data center 201, or off-site.
  • network infrastructure 222 represents the cloud exchange switching fabric and includes multiple ports that may be dynamically interconnected with virtual Circuits by, e.g., invoking service interface 114 of the programmable network platform 120. Each of the ports is associated with one of carriers 106, customers 108, and CSPs 110.
  • FIGS. 3A-3B are block diagrams illustrating example network infrastructure and service provisioning by a programmable network platform for a cloud exchange that aggregates the cloud services of multiple cloud service providers for provisioning to customers of the cloud exchange provider and aggregates access for multiple customers to one or more cloud sendee providers, in accordance with techniques described in this disclosure.
  • customer networks 308A-308C (collectively, "customer networks 308"), each associated with a different customer, access a cloud exchange point within a data center 300 in order receive aggregated cloud sendees from one or more cloud sendee provider networks 320, each associated with a different cloud sendee provider 110.
  • Customer networks 308 each include endpoint devices that consume cloud services provided by cloud sendee provider network 320.
  • Example endpoint devices include servers, smart phones, television set-top boxes, workstations, laptop/tablet computers, video gaming systems, teleconferencing systems, media players, and so forth.
  • Customer networks 308A-308B include respective provider edge/autonomous system, border routers (PE/ASBRs) 310A-310B.
  • PE/ASBRs 310A, 310B may- execute exterior gateway routing protocols to peer with one of PE routers 302A-302B ("PE routers 302" or more simply "PEs 302") over one of access links 316A-316B (collectively, ' " access links 316").
  • each of access links 316 represents a transit link between an edge router of a customer network 308 and an edge router (or autonomous system border router) of cloud exchange point 303.
  • PE 310A and PE 302A may directly peer via an exterior gateway protocol, e.g., exterior BGP, to exchange L3 routes over access link 316A and to exchange L3 data traffic between customer network 308A and cloud service provider networks 320.
  • Access links 316 may in some cases represent and alternatively be referred to as attachment circuits for IP-VPNs configured in IP / MPLS fabric 301, as described in further detail below.
  • Access links 316 may in some cases each include a direct physical connection between at least one port of a customer network 308 and at least one port of cloud exchange point 303, with no intervening transit network.
  • Access links 316 may operate over a VLAN or a stacked VLAN (e.g, QinQ), a VxLAN, an LSP, a GRE tunnel, or other type of tunnel.
  • PE routers 302 may additionally offer, via access Sinks 316, L2 connectivity between customer networks 308 and cloud sen/ice provider networks 320.
  • a port of PE router 302A may be configured with an L2 interface that provides, to customer network 308A, L2 connectivity to cloud service provider 320A via access link 316A, with the cloud service provider 320A router 312A coupled to a port of PE router 304 A that is also configured with an L2 interface.
  • the port of PE router 302A may be additionally configured with an L3 interface that provides, to customer network 308A, L3 connectivity to cloud service provider 320B via access links 316A.
  • PE 302A may be configured with multiple L2 and/or L3 sub-interfaces such that customer 308A may be provided, by the cloud exchange provider, with a one-to-many connection to multiple cloud service providers 320.
  • IP / MPLS fabric 301 is configured with an L2 bridge domain (e.g., an L2 virtual private network (L2VPN) such as a virtual private LAN service (VPLS), E-LINE, or E-LAN) to bridge L2 traffic between a customer-facing port of PEs 302 and a CSP-facing port of cloud sen/ice providers 320.
  • L2VPN L2 virtual private network
  • VPLS virtual private LAN service
  • E-LINE virtual private LAN service
  • E-LAN virtual private LAN service
  • a cloud service provider 320 and customer 308 may have access links to the same PE router 302, 304, which bridges the L2 traffic using the bridge domain.
  • IP / MPLS fabric 301 is configured with a L3 virtual routing and forwarding instances (VRFs), as described in further detail below with respect to FIG. 4.
  • VRFs virtual routing and forwarding instances
  • Each of access links 316 and aggregation links 322 may include a network interface device (NID) that connects customer network 308 or cloud sendee provider 328 to a network link between the NID and one of PE routers 302, 304.
  • NID network interface device
  • Each of access links 316 and aggregation links 322 may represent or include any of a number of different types of links that provide L2 and/or L3 connectivity.
  • customer network 308C is not an autonomous system having an autonomous system number.
  • Customer network 308C may represent an enterprise, network sendee provider, or other customer network that is within the routing footprint of the cloud exchange point.
  • Customer network includes a customer edge (CE) device 311 that may execute exterior gateway routing protocols to peer with PE router 302B over access link 316C.
  • CE customer edge
  • any of PEs 310A-310B may alternatively be or otherwise represent CE devices.
  • Access links 316 include physical links. PE/ASBRs 310A-310B, CE device 311, and PE routers 302A-302B exchange L2/L3 packets via access links 316. In this respect, access links 316 constitute transport links for cloud access via cloud exchange point 303. Cloud exchange point 303 may represent an example of any of cloud exchange points 128. Data center 300 may represent an example of data center 201.
  • Cloud exchange point 303 aggregates customers 308 access to the cloud exchange point 303 and thence to any one or more cloud service providers 320.
  • FIGS. 3A-3B e.g., illustrate access links 316A-316B connecting respective customer networks 3Q8A-308B to PE router 302A of cloud exchange point 303 and access link 316C connecting customer network 308C to PE router 302B.
  • Any one or more of PE routers 302, 304 may comprise ASBRs.
  • PE routers 302, 304 and IP/MPLS fabric 301 may be configured according to techniques described herein to interconnect any of access links 316 to any of cloud aggregation links 322.
  • cloud sen-ice provider network 320A e.g., needs only to have configured a single cloud aggregate link (here, access link 322A) in order to provide services to multiple customer networks 308. That is, the cloud service provider operating cloud sendee provider network 302A does not need to provision and configure separate service links from cloud sendee provider network 302A to each of PE routers 310, 311, for instance, in order to provide sendees to each of customer network 308.
  • Cloud exchange point 303 may instead cross-connect cloud aggregation link 322A and PE 312A of cloud sendee provider network 320A to multiple cloud access links 316 to provide layer 3 peering and network reachability for the cloud sendees delivery .
  • a single customer network e.g., customer network 308A
  • Cloud exchange point 303 may instead cross-connect cloud access link 316A (again, as one example) to multiple cloud aggregate links 322 to provide layer 3 peering and network reachability for the cloud services delivery to customer network 308A.
  • Cloud service provider networks 320 each includes sen d ers configured to provide one or more cloud sendees to users. These sendees may be categorized according to service types, which may include for examples, applications/software, platforms, infrastructure, virtualization, and servers and data storage.
  • Example cloud services may- include content/media delivery, cloud-based storage, cloud computing, online gaming, IT sendees, etc.
  • Cloud service provider networks 320 include PE routers 312A-312D that each executes an exterior gateway routing protocol, e.g., eBGP, to exchange routes with PE routers 304A-304B (collectively, "PE routers 304") of cloud exchange point 303.
  • Each of cloud sendee provider networks 320 may represent a public, private, or hybrid cloud.
  • Each of cloud service provider networks 320 may have an assigned autonomous system number or be part of the autonomous system footprint of cloud exchange point 303.
  • IP/MPLS fabric 301 interconnects PEs 302 and PEs 304.
  • IP/MPLS fabric 301 include one or more switching and routing devices, including PEs 302, 304, that provide IP/MPLS switching and routing of IP packets to form an IP backbone.
  • IP/MPLS fabric 301 may implement one or more different tunneling protocols (i .e., other than MPLS) to route traffic among PE routers and/or associate the traffic with different IP -VPNs.
  • IP/MPLS fabric 301 implement IP virtual private networks (IP-VPNs) to connect any of customers 308 with multiple cloud service provider networks 320 to provide a data center-based 'transport' and layer 3 cross-connect.
  • IP-VPNs IP virtual private networks
  • sendee provider-based IP backbone networks require wide-area network (WAN) connections with limited bandwidth to transport service traffic from layer 3 sendees providers to customers
  • WAN wide-area network
  • IP/MPLS fabric 301 implements IP- VPNs using techniques described in Rosen & Rekhter, "BGP/MPLS IP Virtual Private Networks (VPNs)," Request for Comments 4364, February 2006, Internet Engineering Task Force (IETF) Network Working Group, the entire contents of which is incorporated by reference herein.
  • a customer network 308 and cloud service provider network 320 may connect via respective links to the same PE router of IP / MPLS fabric 301 ,
  • Access links 316 and aggregation links 322 may include attachment circuits that associate traffic, exchanged with the connected customer network 308 or cloud se dee provider network 320, with virtual routing and forwarding instances (VRFs) configured in PEs 302, 304 and corresponding to IP -VPNs operating over IP/MPLS fabric 301 .
  • VRFs virtual routing and forwarding instances
  • PE 302A may exchange IP packets with PE 31 OA on a bidirectional label- switched path (LSP) operating over access link 316A, the LSP being an attachment circuit for a VRF configured in PE 302A.
  • LSP label- switched path
  • PE 304 A may exchange IP packets with PE 312A on a bidirectional label-switched path (LSP) operating over access link 322A, the LSP being an attachment circuit for a VRF configured in PE 304A.
  • LSP label-switched path
  • Each VRF may include or represent a different routing and forwarding table with distinct routes.
  • PE routers 302, 304 of IP / MPLS fabric 301 may be configured in respective hub- and-spoke arrangements for cloud services, with PEs 304 implementing cloud service hubs and PEs 302 being configured as spokes of the hubs (for various hub-and-spoke instances / arrangements).
  • a hub-and-spoke arrangement ensures that service traffic is enabled to flow between a hub PE and any of the spoke PEs, but not directly between different spoke PEs.
  • PEs 302 advertise routes, received from PEs 310, to PEs 304, which advertise the routes to PEs 312.
  • For northbound service traffic i.e., from a customer to a CSP
  • PEs 304 advertise routes, received from PEs 312, to PEs 302, which advertise the routes to PEs 310.
  • the cloud exchange point 303 provider may configure a full mesh arrangement whereby a set of PEs 302, 304 each couple to a different customer site network for the customer.
  • the IP/MPLS fabric 301 implements a layer 3 VPN (L3VPN) for cage-to-cage or redundancy traffic (also known as east-west or horizontal traffic).
  • L3VPN may effectuate a closed user group whereby each customer site network can send traffic to one another but cannot send or receive traffic outside of the L3 VPN.
  • PE routers may couple to one another according to a peer model without use of overlay networks. That is, PEs 310 and PEs 312 may not peer directly with one another to exchange routes, but rather indirectly exchange routes via IP / MPLS fabric 301.
  • cloud exchange point 303 is configured to implement multiple layer 3 virtual circuits 330A-330C (collectively, "virtual circuits 330") to interconnect customer network 308 and cloud service provider networks 322 with end-to-end IP paths.
  • Each of cloud service providers 320 and customers 308 may be an endpoint for multiple virtual circuits 330, with multiple virtual circuits 330 traversing one or more attachment circuits between a PE PE or PE/CE pair for the IP / MPLS fabric 301 and the CSP/customer.
  • a virtual circuit 330 represents a layer 3 path through IP / MPLS fabric 301 between an attachment circuit connecting a customer network to the fabric 301 and an attachment circuit connecting a cloud service provider network to the fabric 301.
  • Each virtual circuit 330 may include at least one tunnel (e.g., an LSP and/or Generic Route Encapsulation (GRE) tunnel) having endpoints at PEs 302, 304.
  • GRE Generic Route Encapsulation
  • Each virtual circuit 330 may include a different hub-and-spoke network configured in IP / MPLS network 301 having PE routers 302, 304 exchanging routes using a full or partial mesh of border gateway protocol peering sessions, in this example a full mesh of Multiprotocol Interior Border Gateway Protocol (MP-iBGP) peering sessions.
  • MP-iBGP or simply MP-BGP is an example of a protocol by which routers exchange labeled routes to implement MPLS-based VPNs.
  • PEs 302, 304 may exchange routes to implement IP-VPNs using other techniques and/or protocols.
  • PE router 312A of cloud service provider network 320A may send a route for cloud service provider network 320A to PE 304A via a routing protocol (e.g., eBGP) peering connection with PE 304A.
  • PE 304A associates the route with a hub-and-spoke network, which may have an associated VRF, that includes spoke PE router 302A .
  • PE 304A then exports the route to PE router 302 A;
  • PE router 304A may export the route specifying PE router 304A as the next hop router, along with a label identifying the hub-and-spoke network.
  • PE ro ter 302A sends the route to PE router 310B via a routing protocol connection with PE 310B.
  • PE router 302 A may- send the route after adding an autonomous system number of the cloud exchange point 303 (e.g., to a BGP autonomous system path (AS ⁇ 1 ⁇ ) attribute) and specifying PE router 302A as the next hop router.
  • Cloud exchange point 303 is thus an autonomous system " 'hop" in the path of the autonomous systems from customers 308 to cloud service providers 320 (and vice-versa), even though the cloud exchange point 303 may be based within a data center.
  • PE router 310B installs the route to a routing database, such as a BGP routing information base (RIB) to provide layer 3 reachability to cloud service provider network 320A.
  • RIB BGP routing information base
  • PE routers 310B, 302A, 304A, and 312A may perform a similar operation in the reverse direction to forward routes originated by customer network 308B to PE 312A and thus provide connectivity from cloud service provider network 320A to customer network 308B.
  • PE routers 312B, 304A, 302A, and 310B exchange routes for customer network 308B and cloud service provider 320B in a manner similar to that described above for establishing virtual circuit 330B.
  • cloud exchange point 303 within data center 300 internalizes the peering connections that would otherwise be established between PE 310B and each of PEs 3 I2A, 312B so as to perform cloud aggregation for multiple layer 3 cloud services provided by different cloud service provider networks 320A, 320B and deliver the multiple, aggregated layer 3 cloud services to a customer network 308B having a single access link 316B to the cloud exchange point 303.
  • fully interconnecting customer networks 308 and cloud service provider networks 320 would require 3x3 peering connections between each of PEs 310 and at least one of PEs 312 for each of cloud service provider networks 320.
  • PE 310A would require a layer 3 peering connection with each of PEs 312.
  • cloud exchange point 303 may fully interconnect customer networks 308 and cloud service provider networks 320 with one peering connection per site PE (i.e., for each of PEs 310 and PEs 312) by internalizing the layer 3 peering and providing data center-based 'transport ' ' between cloud access and cloud aggregate interfaces.
  • PEs 304 may be configured to import routes from PEs 302 and to export routes received from PEs 312, using different asymmetric route targets.
  • PEs 302 may be configured to import routes from PEs 304 and to export routes received from PEs 310 using the asymmetric route targets.
  • PEs 302, 304 may be configured to implement advanced L3VPNs thai each includes a basic backbone L3VPN of IP/MPLS fabric 301 together with extranets of any of customer networks 308 and any of cloud service provider networks 320 attached to the basic backbone L3VPN.
  • Each advanced L3VPN constitutes a cloud se dee delivery network from a cloud se dee provider network 320 to one or more customer networks 308, and vice-versa.
  • cloud exchange point 303 enables any cloud service provider network 320 to exchange cloud service traffic with any customer network 308 while internalizing the layer 3 routing protocol peering connections that would otherwise be established between pairs of customer networks 308 and cloud service provider networks 320 for any cloud service connection between a given pair.
  • the cloud exchange point 303 allows each of customer networks 308 and cloud service provider networks 320 to establish a single (or more for redundancy or other reasons) layer 3 routing protocol peering connection to the data center-based layer 3 cross-connect.
  • PEs 302, 304 By filtering routes from cloud service provider networks 320 to customer networks 308, and vice-versa, PEs 302, 304 thereby control the establishment of virtual circuits 330 and the flow of associated cloud sendee traffic between customer networks 308 and cloud service provider networks 320 within a data center 300.
  • Routes distributed into MP-iBGP mesh 318 may be VPN ⁇ IPv4 routes and be associated with route distinguishers to distinguish routes from different sites having overlapping address spaces.
  • J Programmable network platform 120 may receive service requests for creating, reading, updating, and/or deleting end-to-end services of the cloud exchange point 303.
  • programmable network platform 120 may configure PEs 302, 304 and/or other network infrastructure of IP/MPLS fabric 301 to provision or obtain performance or other operations information regarding the service.
  • Operations for provisioning a sendee and performed by programmable network platform 120 may include configuring or updating VRFs, installing SDN forwarding information, configuring LSPs or other tunnels, configuring BGP, configuring access links 316 and aggregation links 322, or otherwise modifying the configuration of the IP / MPLS fabric 301.
  • Other operations may include making service requests to an orchestration system for cloud sendee provider networks 320, as described in further detail below.
  • FIG. 4 is a block diagram illustrating an example of a data center-based cloud exchange point in which routers of the cloud exchange point are configured by- programmable network platform 120 with VPN routing and forwarding instances for routing and forwarding aggregated service traffic from multiple cloud service provider networks to a customer network, according to techniques described herein.
  • PE routers 302A and 304 A of IP / MPLS fabric 301 are configured with VRFs.
  • PE 302A is configured with VRFs 402A and 404A
  • PE 304A is configured with VRFs 402B and 404B.
  • VRF 402A is configured to import routes exported by VRF 402B
  • VRF 402B is configured to import routes exported by VRF 402A
  • the configuration may include asymmetric route targets for import/export between VRFs 402A, 402B.
  • VRF 40 A is configured to import routes exported by VRF 402B
  • VRF 402B is configured to import routes exported by VRF 402A.
  • the configuration may include asymmetric route targets for import/export between VRFs 402A, 402B. This configuration whereby a customer is able to access multiple layer 3 sendees from different CSPs each associated with separate VRFs to access the layer 3 sendees provides isolation of respective traffic exchanged with the CSPs.
  • PE 302A may be configured with a single VRF to import routes exported by both VRF 402B and VRF 404B.
  • PEs 302, 304 may be further configured to bridge layer 2 traffic between customer 308B and cloud service providers 320.
  • PE 304A operates BGP or other route distribution protocol peering connections 406B, 408B with respective PEs 3 12A, 3 I 2B to exchange routes with respective cloud service provider networks 320A, 320B.
  • PE 302A operates a BGP or other route distribution protocol peering connection 410 with PE 310B to exchange routes with customer network 308B.
  • PEs 302A, 304A may be statically configured with routes for the sice networks.
  • An administrator or a programmable network platform described herein for cloud exchange point 303 may configure PEs 302A, 304A with the VRF 402A-402B, 404A- 404B in order to leak routes between PEs 312 and PE 310B and facilitate layer 3 connectivity for end-to-end IP paths illustrated here by virtual circuits 330, while potentially optimizing the end-to-end IP paths by fostering data center-based or at least metro-based connectivity.
  • Cloud exchange point 303 may thus provide dedicated cloud service provider access to customer network 308B by way of private and/or public routes for the cloud service provider networks 320.
  • cloud exchange point 303 may provide dedicated cloud service provider distribution to multiple customer networks 308 by way of private and/or public routes for the customer networks 308, Neither PE 310B nor any of PEs 302 A, 304A need access to the full Internet BGP routing table in order to reach cloud sendee provider networks 320 or customer networks 308. Moreover, PEs 302A, 304 A may be configured to aggregate customer/CSP routes and/or service traffic based on any one or more of physical, IP, se dee, and VRFs.
  • FIG. 5 is a block diagram illustrating a platform for a software controlled network, the platform operating in accordance with one or more techniques of the present disclosure.
  • FIG. 5 illustrates a programmable network platform 10000 that includes multiple components, which collectively provide for dynamic configuration and management of a cloud-based services exchange, or '"cloud exchange.” These components may provide virtual connections for cloud sen-ices delivery from multiple cloud service providers to one or more cloud customers.
  • Programmable network platform 10000 includes centralized network control (CNC) system 10002, one or more network field units (NFUs) 10004, software-defined networking (SDN) controller 10006, hardware configurators 10008, infrastructure data collectors 10010, and information technology systems (10010).
  • CNC network control
  • NFUs network field units
  • SDN software-defined networking
  • Programmable network platform 10000 may provide for the orchestration of a service across multiple service providers and allow one of the service providers to be the service owner in terms of the sendee monitoring, assurance and billing. Programmable network platform 10000 may provide the process and apparatus for multiple sendee provider orchestration system to securely communicate with each other to deliver a combined service on demand in a single click manner. Programmable network platform 10000 may represent an example instance of programmable network platform 120 or another programmable network platform, controller, or system described herein for provisioning sendees and assuring sendee delivery.
  • CNC sy stem 10002 enables the automation of aspects of cloud sendees provisioning.
  • CNC system 10002 may provide one or more software interfaces that allow customers to establish, de-install and manage interconnections with multiple, different cloud providers participating in the cloud exchange in an automated and seamless manner.
  • CNC system 10002 may include logic to receive a business service request via an API call and convert that into the necessary business instantiation parameters and network provisioning parameters to be delivered and assured as a business service.
  • CNC system 10002 may be the central intelligent processing unit of the orchestration sy stem (e.g., programmable network platform 10000) and there may be one logical instance of this intelligent logic present per instantiation, CNC system 10002 also has the capability of communicating with a third party- orchestration system if needed by the service request.
  • CNC system 10002 may provide service assurance using a Monitor, Analyze, Plan and Execute (MAPE) loop methodology, as further discussed in this disclosure, and is implemented to ensure the sen' ice level agreements are adhered to by the service,
  • MEE Plan and Execute
  • NFU 10004 is implemented as a self-contained unit that receives requests or instructions from CNC system 10002 to configure network mfrastracture of a cloud exchange point for one or more services.
  • NFU 10004 may comprise a combination of hardware and software.
  • NFU 10004 may be a virtual machine.
  • NFU 10004 receives requests or instructions CNC system 10002 based on customer requests submitted to CNC system 10002.
  • NFU 10004 may determine whether sufficient resources exist to provide the services requested by CNC system 10002. If sufficient resources exist, NFU 10004 may communicate or otherwise interoperate with SDN controller 10006, hardware configurators 10008, and infrastructure data collectors 10010 to configure the network infrastructure to provide the requested service.
  • NFU 10004 may represent a globally distributed intelligent logical unit that receives network instantiation commands from CNC system 10002 and instantiates and configures the network resource that is needed to deliver the service, NFU 10004 may have the intelligence to deliver and assure network services as per the request of CNC system 10002. NFU 10004 may have its own MAPE loop (e.g., as shown in FIG. 9) to ensure that the network services delivered by the unit is assured for the life cycle of the service.
  • MAPE loop e.g., as shown in FIG. 9
  • multiple cloud exchange points may be geographically dispersed.
  • Each geographically positioned cloud exchange point may have a corresponding NFU that is geographically positioned at the same location as the respective cloud exchange point.
  • the corresponding NFU may configure and otherwise manage the network infrastructure of the particular geographically-positioned cloud exchange point.
  • a particular NFU may receive requests or instructions from CNC system 10002 and configure the network infrastructure of the cloud exchange point that is managed by the particular NFU .
  • multiple cloud exchange points of a metropolitan area make up a metro-based cloud exchange managed by a single NFU.
  • 010 ⁇ ] NFU 10004 may therefore represent the distributed processing unit of programmable network platform 10000, which provides programmable network platform 10000 with the ability to horizontal scale and deliver and assure services.
  • NFU 10004 is the component of programmable network platform 10000 that may provide the functionality of delivering the services in a vendor agnostic and form factor agnostic manner. As shown in FIG. 5, NFU 10004 has several software components that enable the distributed processing unit to deliver the services.
  • CNC system 10002 includes a service selector 10012.
  • service selector 10012 may operate as an API gateway.
  • service selector 10012 may expose software interfaces defined according to one or more APIs.
  • Requests and/or instructions received by service selector 10012 may be include the form of create, read, update, and/or delete (CRUD) requests made with respect to services provided by and/or delivered by the cloud exchange.
  • Applications may invoke endpoints of the APIs provided by service selector 10012, which may in turn invoke service provisioning engine 10014.
  • Service selector 10012 may execute on one or virtual machines and/or real servers, for instance. Although shown as a single element in FIG. 5, service selector 10012 may comprise a cluster of one or more physical and/or virtual computing machines executing on one or more physical processors.
  • service selector 10012 provides a service catalog that describes available sen-ices and providers for the available services.
  • Service provisioning engine 10014 may receive requests to provision services from service selector 10012.
  • Service provisioning engine 10014 in conjunction with network field unit 10004, organizes, directs and integrates underlying hardware and software sub-systems for managing various aspects of service provisioning within the network infrastructure as well as cloud senices management.
  • sen ice provisioning engine 10014 may provide a rule-driven workflow engine that operates between service selector 10012 and the underlying interconnect platform of a cloud exchange that is configured by network field unit 10004.
  • sendee provisioning engine 10014 can be invoked via sendee selector 10012 by customer- proprietary applications, a cloud provider-based customer portal, and/or cloud service provider systems, for direct participation with the programmable network platform of a cloud exchange network infrastructure that is configured by network field unit 10004.
  • service provisioning engine 10014 may include a third-party sendee connector that communicates with the third party orchestration systems to ensure that the service is adequately networked together to provide the end-to-end cloud-based sendee fulfillment.
  • NFU 10004 may receive instructions and/or requests from CNC system 10002, which NFU 10004 uses to provision sendees at one or more cloud exchange points.
  • Service provisioning engine 10014 may query and store sen-ice telemetry and analytics data (STAD) 10016 in one or more data stores.
  • STAD 10016 may include metrics about the quantity, type, definition, and consumers of services that are configured by service provisioning engine 10014,
  • STAD 100 6 may include analytics information based on raw metrics data from NFU 10004.
  • analysis information of STAD 10016 may include historical statistics and/or real-time statistics, which may be analyzed on various dimensions, such as consumer, sendee type, service use, to name only a few examples.
  • CNC system 10002 may also include financial logic 10018.
  • Financial logic 10018 may store accounting information for customers. For instance, financial logic 10018 may store billing information for customers, such as name, address, phone number, email, to name only a few examples.
  • service provisioning engine 10014 configures a service for a customer that includes a service charge
  • financial logic 10018 may store such expense information. In this way, financial logic 10018 may provide an accounting of services purchased by a customer and provide billing for such services.
  • CNC system 10002 may include Information Technology (IT) gateway 10020 that interfaces with IT systems 100022.
  • IT systems 100022 may include one or more computing devices, such as desktop computers, tablets, smartphones, and servers, to name only a few examples.
  • IT systems 100022 may provide one or more user interfaces to administrators, which may use IT systems 100022 to administer CNC system 10002.
  • IT systems 100022 may, for example, receive user inputs to configure CNC system 10002 and/or NFU 10004. Based on the user inputs, IT systems 100022 may send requests and/or instructions to CNC system 10002, which are received by IT gateway 10020.
  • CNC system. 10002 may provide or otherwise expose one or more RESTful interfaces that can be called or otherwise invoked by IT systems 100022.
  • IT gateway 10020 may route such instructions or requests to other components within CNC system 10002 for further processing based on the type of requests and/or instructions.
  • NFU 10004 may receive requests or instructions from. CNC system 10002 to provision one or more services.
  • Network provisioning engine 10024 may receive the requests and/or instructions from service provisioning engine 10014.
  • Network provisioning engine 10024 may determine whether sufficient resources exist to satisfy a request for a service to be configured at a cloud exchange point.
  • network provisioning engine 10024 may query one or more components such as SDN controller 10006, hardware configurators 10008, and/or network telemetry and analytics data (NTAD) 10026.
  • NTAD network telemetry and analytics data
  • network provisioning engine 10024 may send instructions and/or requests to one or more of SDN controller 10006 and/or hardware configurators 10008 that cause each respective component to be configured to provision the requested sen/ice.
  • network provisioning engine 10024 provides the functionality of selecting the vendor, and form factor in which the se dee is delivered.
  • Network provisioning engine 10024 also provides the policy manager functionality to ensure the service is delivered in the correct order of operations.
  • network provisioning engine 10024 of NFU 10004 may include a Network Appliance Sizing Engine (not shown) that provides the functionality of ensuring the network appliance is properly sized for the appropriate SLA to be delivered by the appliance.
  • NFU 10004 may include a Device Selection and Handler (not shown) that provides the functionality of selecting the correct device to deliver the service, and convert the network commands to the appropriate configuration commands for the selected device.
  • NFU 10014 may access a list that describes the capabilities of virtual and/or dedicated appliances within the cloud exchange for providing native sendees, such as firewall (FW), network address translation (NAT), and deep-packet inspection (DPI), to service traffic traversing the cloud exchange.
  • NFU 10004 may select a device from the list to satisfy the sendee request, as described in further detail below with respect to FIG. 8, for instance.
  • Network provisioning engine 10024 may query and store network telemetry and analytics data (NTAD) 10026 in one or more data stores.
  • NTAD 10026 may include metrics about the quantity, type, definition, of network and resource configurations that are configured by NFU 10004.
  • NTAD 10026 may include analytics information from infrastructure data collectors 10010 based on raw metrics data for resources used in a particular service. For instances, analysis information of NTAD 10026 may include historical statistics and/or real-time statistics.
  • one or more SDN controllers 10006 may configure network resources, such as routers, switches, bridges, and the like, which provide the physical infrastructure to carry network traffic through a cloud exchange point.
  • One or more hardware configurators 10008 may configure hardware resources, such as servers or the above-mentioned network resources; resources within servers and network resources including processor allocation, memory allocation; storage appliances; other hardware resources; and software configurations that may be configured to provision services to a customer.
  • One or more infrastructure data collectors 10010 may collect metrics about the quantity, type, definition, of network and resource configurations that are configured by NFU 0004. For instance, infrastructure data collectors 10010 may monitor and measure metrics of network resources and any other resources configured to provision sen/ices to a customer. Infrastructure data collectors 10010 may store such metrics in NTAD 10026.
  • NFU 10004 and CNC system 10002 may include network assurance engine 10028 and service assurance engine 10030, respectively.
  • Network assurance engine 10028 may determine, based on NTAD 10026, whether infrastructure configured to provide services is providing a satisfactory level of service. For example, outages, resource consumption overages, hardware and/or software failures or problems, and other events may affect the quality of sen/ices provided by the network infrastructure at a cloud exchange point.
  • Network assurance engine 10028 may monitor NTAD 10026, and in some cases, send information to service assurance engine 10030. In some examples, the information may include alerts if service levels are not being met, or more specifically alerts for outages, resource consumption overages, hardware and/or software failures or problems.
  • information sent by network assurance engine 10028 to service assurance engine 0030 may be informational rather than based on a specific event.
  • network assurance engine 10028 may send information about the performance of infrastructure to service assurance engine on a particular schedule or interval, and/or on continuous or real-time basis.
  • NTAD 10026 may contain a set of structured and/or unstructured databases that enable the service provisioning engine 10014 and network assurance engine 10028 to appropriately store and retrieve data to support the operation of programmable network platform 10000.
  • Network assurance engine 10028 may provide the functionality of assuring the network configuration created is assured as per the networking SLAs requested by CNC system 10002.
  • the Network Assurance Engine is comprised of several sub-components that deliver the assurance through a MAPE loop including: (1) Monitoring, which is performed by several data collectors that are programmed to monitor and gather data for a given sen/ice; (2) Analyzing, which analyzes the data collected by the data collectors to compare and ensure that the services are compliant with the requested SLAs (3) Planning, which in the e vent a service or set of services are out of compliance, a planning module will make the decisions if the current non-compliance can be mitigated locally or needs to escalated to the CNC system 10002 for further processing; and (4) Executing, which is based on the decisions taken by the planning module to execute actions in the event the non-compliance can be locally mitigated.
  • Service assurance engine 10030 may receive information from network assurance engine 10028 and may compare the information with service level information, such as service level agreements, included in STAD 100 6. By comparing information about the performance of infrastructure with service level information in STAD 10016, service assurance engine may send service level information to customers using one or more service assurance APIs, and whether such service level agreements are being met. In this way, customers may monitor or otherwise evaluate the quality of service provided by one or more cloud exchange points.
  • service level information such as service level agreements
  • programmable network platform 10000 may bridge business systems, such as customers and cloud sen/ice providers, with operations systems, such as the network infrastructure of one or more cloud exchange points to improve operational efficiency. As such, programmable network platform 10000 may provide improved visibility to monitor and assure the end-to-end service and its components. Accordingly, programmable network platform 10000, unlike conventional systems may include the capability to perform the provisioning and assurance of services across multiple orchestration systems for multiple cloud providers.
  • CNC system 10002 may operate as the master controller that performs the function of receiving a sen/ice request that encapsulates the business requirements for the service, and using business, network and partner sub-system logic to instantiate and assure the service. As shown in FIG. 5, CNC system.
  • Programmable network platform 10000 may provide a distributed orchestration system for creating sendees and distributing the intelligence of delivering and assuring services. Additionally, programmable network platform 10000 may provide a distributed system that is able to communicate with third party service orchestration systems and deliver a distributed service, as described in further detail below with respect to FIG. 6.
  • Programmable network platform 10000 may provide service orchestration of a business level sen/ice across heterogeneous service providers.
  • the definition of the service policy, quality, service level agreements and cost as a coordinated service topology may be provided at programmable network platform 10000.
  • Programmable network platform 1 000 may define the individual sub-component level topology, policy, SLA and cost in terms of specification and enforcement.
  • Programmable network platform 10000 is an intelligent centralized service delivery and assurance system with the ability to have fault mitigation Monitor/Analyze/Plane/Execute (MAPE) loop, as shown in FIGS. 7 and 9 that will ensure the service delivered by the system is assured to adhere the service level agreement for the life cycle of the sendee.
  • Programmable network platfonn 10000 not only delivers sen-ices that can be offered by its own delivery infrastructure but also has the capability to communicate across other third-party orchestration systems to deliver a combined homogeneous sendee.
  • Programmable network platform 10000, or more specifically CNC system 10002 may be the central control center for both operations and business related functions to be performed.
  • NFU 10004 and CNC system 10002 may also fulfill the need for having a distributed orchestration system for creating sendees and distributing the intelligence of delivering and assuring service. Additionally, NFU 10004 and CNC system 10002 may- fulfill the need for the distributed system to be able to communicate with third party sendee orchestration systems to deliver a distributed sendee.
  • Programmable network platfonn 10000 provides the advantage of providing a distributed, horizontally scaling architecture.
  • CNC 10002 and one or more NFUs 10004 may provide the functionality of delivering and assuring a business sendee into two distinctly separate functions, (1) CNC - may handle the function of converting the business request into sendee parameters, (2) NFU - may handle the function of converting the service parameters into network parameters and instantiating the service.
  • FIG. 6 is a block diagram illustrating sendee provisioning engine 10014 of FIG . 5 in further detail, in accordance with one or more techniques of the present disclosure.
  • service provisioning engine 10014 may include a service policy manager 10400.
  • Sendee policy manager 10400 may receive sendee requests and/or instructions from other components of CNC system 10002, such as service selector 10012, sendee assurance engine 10030, financial logic 10018 and IT gateway 10020. Requests and/or instructions received by service policy manager 10400 may take the form of create, read, update, and/or delete (CRUD) requests.
  • Sendee policy manager 10400 may provide a set of APIs that allow other components of CNC system 1000 to send service requests and/or instructions to service policy manager 10400.
  • Sendee policy manager 10400 may direct such service requests and/or instractions to other components within sendee policy manager 1 400.
  • Sendee provisioning engine 10014 may include native sendees 10402 and third- part ⁇ ' services orchestrated via third-party orchestration modules 10404.
  • Native sendees 10402 may include services designed and/or implemented by an operator of CNC system 10002. For instance, native services may be used to configure virtual circuits at one or more cloud exchange points. Examples of native seraces 10402 may include but are not limited to a port semce 10402A, one or more layer 3 (L3) connectivity services 10402B, one or more layer 2 (L2) connectivity services 10402C, and one or more connectivity services provided in an OS1 layer that is greater than L3 such as Application, Presentation, Session, and Transport layer services ("L3+ services 10402D").
  • Port service 10402A may identify and/or configure one or more ports to provide one or more services at a cloud exchange point.
  • L2, L3 and L3+ services may refer to the OS1 or TCP/IP layer at which a particular service is applied.
  • a programmable network platform described herein may provide for orchestrating a sendee that involves both native and third-party components as single service while ensuring policy, security, and service level agreement (SLA) consistency.
  • the programmable network platform may orchestrate the third-party service components using a third-party (or "partner") orchestration module (or "plugin").
  • a third-party orchestration module allows a third-party orchestration system to register its capabilities (e.g., service catalog, policy, security and SLA) with the programmable network platform.
  • the cloud service provider may use the programmable network platform to direct the third-party orchestration system, via the corresponding third-party orchestration module, as part of the workflow for the service delivery to stand-up and deliver a third-party service for the service.
  • the programmable network platform may be adapted and extended by registering (or updating) third-party orchestration modules for any third-party orchestration system. This may allow the cloud service provider that administers the programmable network platform to provide interconnectivity between customers and cloud service providers to also broker and delivery layer 3 services of the cloud service providers to the customers.
  • service provisioning engine 10014 may include one or more third-party orchestration modules 10404 to enable orchestration of cloud services by the service provisioning engine 10014.
  • third-party orchestration modules 10404 may be designed and/or implemented by respective cloud service providers, other than administrators of a cloud-exchange point. Although designed and implemented by third parties, third-party orchestration modules 10404 are hosted and executed at a cloud exchange point. In this way, third parties may design and implement third-party orchestration modules 10404 that are hosted and executed at a cloud exchange point.
  • Each of third-party orchestration modules 10404 may present a common interface to the service provisioning engine 10014 for requesting cloud sendees from the cloud sen-ice providers.
  • the interface may include a catalog interface by which a cloud service provider can publish its list of available cloud services, together with available policy, security, SLA parameters, and costs for the cloud services, to the programmable network platform.
  • the programmable network platform may replicate the list of available cloud services for the various cloud service providers to customers via a customer portal.
  • cloud service providers for respective third-party orchestration modules 10404 may each offer a data storage service and publish this offering via the third-party orchestration modules 10404.
  • the programmable network platform with which a given third-party orchestration module 10404 has registered may invoke the common interface to request orchestration of one of the offered cloud services.
  • the third-party orchestration module 10404 responsively communicates with an orchestration system of the corresponding cloud service provider to cause the cloud service provider network to set up the requested layer 3 cloud sendee according to sendee parameters in the request.
  • service parameters may include policy, sendee-specific information specific to the type of layer 3 cloud service (e.g., a data storage size for a dSaaS sendee), connectivity information (e.g., L3 address for a customer or another cloud service provider network), QoS information, among other parameters.
  • the third-party orchestration module 10404A may receive connectivity information that enables the cloud exchange to connect to the instantiated cloud service.
  • This connectivity information may include, e.g., a layer 3 route to the service; a VxLAN, VLAN, or other tunnel identifier usable by a cloud service provider network-facing cloud exchange router for accessing the cloud senice (for instance, forwarding sendee traffic to the cloud service or identifying sendee traffic for the cloud sendee received by the cloud exchange point from the cloud service provider network).
  • the third-party orchestration module 10404A provides the connectivity information 1405 to the senice provisioning engine 10014 (e.g., via the common interface), which uses the connectivity information and STAD 10406 to procure service data and eventually to generate the network provisioning data at 10410.
  • STAD 10406 provides sendee provisioning engine 10014 with indications
  • third-party orchestration modules 10404 manage the setup in response to sen/ice requests made by the sendee provisioning engine 10034 via a common interface.
  • Third-party orchestration module 10404 may be configured with connectivity information for communicating with respective cloud service providers, including respective cloud sendee provider orchestration systems. Cloud service providers may update third-party orchestration modules 10404 by pushing up-to-date new or modified se ice catalogs and service pricing information. The cloud exchange provider may therefore avoid having to pull this information from the cloud service providers.
  • Each of third-party orchestration modules 10404 may represent an application executing on one or more data center servers of the cloud exchange and administered by the cloud exchange provider; a software plugin, module, or linked library; or another machine-executable code executable in conjunction with the programmable network platform and capable of satisfying sendee requests for third-party orchestration in the manner described above.
  • third- part ⁇ ' orchestration modules 10404 allow the cloud service provider to become an authoritative owner of an end-to-end sendee that include at least one component sendee (or "micro-service") provided by a cloud service provider.
  • the end-to-end service may include multiple micro-sendees from multiple different cloud sendee providers each associated with a different third-part ⁇ 7 orchestration module 10404.
  • the end-to-end sendee may also include one or more native sendees (such as any of the NFVs described herein) applied by the cloud exchange.
  • Consolidation of service provisioning permits the cloud exchange provider to offer unified billing to customers, whereby the cloud exchange provider bills the customer for a cloud sendee provider-provided sendee according to cost information received from the cloud sendee provider and passes payment through to the cloud service provider.
  • the cloud exchange provider also bills the customer for any native services, including layer 3 or other connectivity, NFVs, etc.
  • FTG. 6 illustrates sendee provisioning, described as follows.
  • Senice policy- manager 10400 may receive a senice request to configure a particular senice.
  • the request may specify one of third party services 10404, such as third party sen ice 10404A.
  • the request may require the use of one or more ports, thereby invoking port service 10402A.
  • the request may further require an L3 service, thereby invoking L3 se dee 10402B.
  • Sendee provisioning engine 10014 may perform a set of operations 10406- 10410 to configure the requested service.
  • Service provisioning engine 10014 may perform one or more operations 10406 that procure service data for the requested service. To procure the service data, service provisioning engine 10014 may query and/or store data with business gateway 10412 and/or STAD 10016, as previously described in FIG. 5. Business gateway 10412 may include one or more APIs for interfacing with financial logic 10018, as illustrated in FIG. 5. For instance, service provisioning engine 10014 may send billing information for the requested sendee to business gateway 10412, which may send the information to financial logic 10018. Financial logic 10018 may associate the billing information for the sendee with a particular account. Service provisioning engine 10014 may also store information in STAD 10016 that identifies the sendee and one or more properties of the service.
  • STAD 10016 For instance, if the service includes a particular geographic location, particular service level request, etc., such details along with an identifier of the sendee may be stored in STAD 10016. After the sendee has been implemented and is being used, STAD 10016 metrics for the service may be updated and stored in STAD 10016.
  • sendee provisioning engine 10014 may perform one or more operations 10408 to select one or more NFUs.
  • Sendee provisioning engine 10014 may select the one or more NFUs based on the initial request or instructions received from service selector 10012. For instance, if the request specifies a particular geographic location, sendee provisioning engine 10014 may select an NFU for the particular geographical location. If the request specifies a particular quantity or type of resources, sendee provisioning engine 10014 may determine one or more NFUs that manage one or more cloud exchange points with sufficient resources to satisfy the particular quantity and/or type of resources requested. Service provisioning engine 10014 may query STAD 10016 to determine quantities and/or type of resources managed by different NFUs.
  • sendee provisioning engine 10014 may perform one or more operations to generate network provisioning data at 10410, For instance, sendee provisioning engine 10014 may translate a higher-level service request received from a customer into network provisioning data comprising a more specific set of instructions and/or requests that sen-ice provisioning engine 10014 sends to one or more NFUs.
  • An NFU that receives the network provisioning data may configure network infrastructure based on the network provisioning data to provide the requested sen'ice,
  • FIG. 7 is a block diagram illustrating service assurance engine 10030 of FIG. 5 in further detail, in accordance with one or more techniques of the present disclosure.
  • service assurance engine 10030 may receive information from network assurance engine 10028 and may compare the information with senice level information, such as senice level agreements, included in STAD 10016. By comparing information about the performance of infrastructure with service level information in STAD 10016, senice assurance engine may send senice level information to customers using one or more senice assurance APIs, and whether such senice level agreements or other performance thresholds are being met.
  • senice assurance engine 10030 may perform one or more operations 16000-10608.
  • Senice assurance engine 10030 may retrieve service data 1600.
  • Service data may include definitions and/or descriptions of services that have been requested by customers and provisioned at one or more cloud exchange points.
  • service assurance engine 10030 may monitor the actual performance of cloud exchange points that provide the requested senices.
  • senice assurance engine 10030 may query or otherwise receive performance data 10602 from STAD 10030 that is populated by CNC system 10002 with data from one or more components, such as NFU 10004.
  • Service assurance engine 10030 may analyze the performance data in conjunction with the senice data to identify anomalies, problems, or deficient performance associated with a senice provisioned by a cloud exchange point 10604. For example, senice assurance engine 10030 may determine that one or more conditions, criteria and/or thresholds are satisfied that indicate an anomaly, problem, or deficient performance 10604. If such conditions, criteria and/or thresholds are satisfied, senice assurance engine 10030 may perform one or more remedial actions.
  • Service assurance engine 10030 may store one or more remedial actions 10606.
  • remedial actions may refer to one or more operations that may be taken by one or more components of CNC system 10002 to remedy an anomaly, problem, or deficient performance.
  • a remedial action may be associated at service assurance engine 10030 with one or more conditions. For instance, w r hen service assurance engine 10030 determines that one or more conditions, criteria and/or thresholds are satisfied, service assurance engine 10030 may determine remedial actions associated with the one or more conditions, criteria and/or thresholds. Examples of remedial actions may include re-allocating resources to continue providing a particular sen/ice at a cloud exchange point, and sending one or more notifications to one or more recipients, to name only a few examples.
  • an administrator and/or customer may configure the remedial actions and/or one or more conditions, criteria and/or thresholds prior to or at the time a service is provisioned at a cloud exchange point. In this way, if the one or more conditions, criteria and/or thresholds are satisfied with respect to a cloud exchange point, service assurance engine 10030 may determine the corresponding remedial actions.
  • service assurance engine 10030 may- execute one or more remedial actions 10608.
  • service assurance engine 10030 may communicate the remedial actions to service provisioning engine 10014, which carries out the operations defined by the remedial actions. In this way, service assurance engine 10030 may monitor and respond, in an automated manner, to an anomaly, problem., or deficient performance by performing one or more remedial actions.
  • FIG. 8 is a block diagram illustrating network provisioning engine 10024 of FIG. 5 in further detail, in accordance with one or more techniques of the present disclosure.
  • Network provisioning engine 10024 of may receive network service definitions, instructions, and/or requests from service provisioning engine 10014 of CNC system 10002.
  • Network provisioning engine 10024 uses the network service definitions, instructions, and/or requests to configure infrastructure managed by NFU 10004 in order to provision network services at one or more cloud exchange points.
  • a "network sendee definition,” as used herein, is data defining parameters for provisioning a network service at least partially instantiate by configuring a network of network devices that offer network services.
  • Network services may include network services provided by (native service) or delivered by (cloud service or third-party sen/ice) the cloud exchange to a consumer of the aforementioned network service(s).
  • network provisioning engine 10024 may verify the contents and format of the a network service definition, instructions and/or requests 10800. For example, network provisioning engine 10024 may determine whether the network sendee definition, instructions and/or requests are valid. If the contents and/or format are invalid, network provisioning engine 10024 may send a response to se dee provisioning engine 10014 indicating the invalidity of the contents and/or format,
  • network provisioning engine 10802 may choose a vendor to provide the sendee based on the a network sendee definition, instructions and/or requests. For instance, CNC system 10002 may allow a customer or cloud sendee provider to select from a set of vendor equipment, one or more particular types of vendor equipment to provide a particular sendee. As an example, a cloud service provider may specify a particular vendor to provide a firewall sendee. The a network sendee definition, instructions and/or requests received by network provisioning engine 10024 from CNC system 10002 may specify a particular vendor to provide the service.
  • Network provisioning engine 1 024 may determine whether equipment for the particular vendor is available to provide the se ' ice. If not available, network provisioning engine 10024 may send a response to sen/ice provisioning engine 10014 indicating the unavailability of the vendor equipment.
  • network provisioning engine 10024 may choose a particular form factor for the vendor equipment 10804.
  • the form factor may be specified based on die a network service definition, instructions and/or requests received by network provisioning engine 10024 from service provisioning engine 10014.
  • network provisioning engine 10024 may automatically determine the form factor for the vendor equipment based on one or more parameters in the a network sendee definition, instructions and/or requests.
  • the one or more parameters may not specify the form factor; however, network provisioning engine 10024 may determine, based on the parameters, that a particular form factor of vendor equipment will satisfy the requirements of the a network service definition, instructions and/or requests.
  • the parameters may specify a particular type of functionality and/or resource requirement that network provisioning engine 10024 may use to determine which form factor of vendor equipment can satisfy the re ariesments.
  • Network provisioning engine 10024 may determine sizing for the vendor equipment and/or verify' capacity of the vendor equipment 10806, In some examples, network provisioning engine 10024 may query NTAD 10026 to determine current resource allocation and usage for infrastructure of a cloud exchange point that is managed by network provisioning engine 10024.
  • the infrastructure may include the vendor equipment identified by network provisioning engine 10024 for the a network se dee definition, instructions and/or requests received from service provisioning engine 10014. Based on the requirements of the instructions and/or requests received from CNC 10002 and the current resource allocation and usage from NTAD 10026, network provisioning engine 10024 may determine whether adequate resources exist at the vendor equipment determined by network provisioning engine 10024 to provision the requested service.
  • network provisioning engine 10024 may send a response to service provisioning engine 10014 indicating the insufficient sizing and/or capacity for the vendor equipment.
  • network provisioning engine 10024 may obtain a device handler to the specific vendor equipment 10808.
  • a device handler may be an identifier that uniquely identifies a particular device. Such devices may include the vendor equipment included in the infrastructure of one or more cloud exchange points.
  • network provisioning engine 10024 may configure or otherwise send one or more requests and/or instructions to SDN controller 10006 and/or hardware configurators 10008 to configure the device identified by the device handier 10810.
  • the requests may specify create, read, update, or delete operations to perform with respect to the device identified by the device handler.
  • FIG. 9 is a block diagram illustrating network assurance engine 10028 of FIG. 5 in further detail, in accordance with one or more techniques of the present disclosure.
  • network assurance engine 10028 may send information to service assurance engine 10030, which may compare the information with service level information, such as service level agreements, included in STAD 10016.
  • Service level information such as service level agreements
  • Network assurance engine 10030 may query NTAD 10026 in a similarly manner that service assurance engine 10030 queries STAD 10016.
  • network assurance engine may send network level information to customers using one or more network assurance APIs, and whether sendee level agreements or other performance thresholds are being met.
  • network assurance engine 10028 may perform one or more operations 11000-110010.
  • Network assurance engine 10028 may retrieve network data 11000.
  • Network data may include actual bandwidth, dropped packets, latency, uptime, to name only a few examples.
  • network assurance engine 10028 may monitor the actual performance of cloud exchange points that provide the requested services.
  • network assurance engine 10028 may query or otherwise receive performance data 11002 from NTAD 10026 that is populated by NFU 10004.
  • Network assurance engine 10028 may analyze the performance data in conjunction with the sendee data to identify anomalies, problems, or deficient performance associated with network infrastructure of a cloud exchange point 11004. For example, network assurance engine 10028 may determine that one or more conditions, criteria and/or thresholds are satisfied that indicate an anomaly, problem, or deficient performance 11004. If such conditions, criteria and/or thresholds are satisfied, network assurance engine 11004 may perform one or more remedial actions.
  • Network assurance engine 10028 may store one or more remedial actions 11006.
  • remedial actions may refer to one or more operations that may be taken by one or more components of CNC system 10002 to remedy an anomaly, problem, or deficient performance.
  • a remedial action may be associated at network assurance engine 10028 with one or more conditions. For instance, when network assurance engine 10028 determines that one or more conditions, criteria and/or thresholds are satisfied, network assurance engine 10028 may determine remedial actions associated with the one or more conditions, criteria and/or thresholds. Examples of remedial actions may indicate re-allocating resources to continue providing a particular service at a cloud exchange point and/or sending one or more notifications to one or more recipients, to name only a few examples.
  • an administrator and/or customer may configure the remedial actions and/or one or more conditions, criteria and/or thresholds prior to or at the time a service is provisioned at a cloud exchange point. In this way, if the one or more conditions, criteria and/or thresholds are satisfied with respect to a cloud exchange point, network assurance engine 10028 may determine the corresponding remedial actions.
  • network assurance engine 10028 may- execute one or more remedial actions 11008.
  • network assurance engine 10028 may communicate the remedial actions to network provisioning engine 10024, which carries out the operations defined by the remedial actions.
  • network assurance engine 10028 may monitor and respond, in an automated manner, to an anomaly, problem, or deficient performance by performing one or more remedial actions.
  • FIG. 10 is a block diagram illustrating a programmable network platform 1 1600, in accordance with one or more techniques of the present disclosure.
  • Programmable network platform 1 1600 may represent an example instance of programmable network platform 120, programmable network platform 10000, or other programmable network platform described in this disclosure .
  • programmable network platform 1 1600 may include a centralized network control (CNC) system 1 1601 that controls data fabric 1 1614.
  • Data fabric 11614 may be configured by CNC system 11601 to provide one or more services, including virtual connections, which allow customers 1 1610 to use services provided by cloud service providers 1 1616.
  • Customers 1 1610 may desire to directly cross-connect to cloud service providers 1 1616 at a common point, such as data fabric 1 1614, thereby allowing direct exchange of network traffic between the networks of the customers and cloud service providers.
  • one or more services may be applied by data, fabric 1 1614 to network traffic forwarded between customers 1 1610 and cloud sen/ice providers 1 1616.
  • a customer may configure an L3 connection service with a firewall between the customer and a cloud service provider using data fabric 1 1614.
  • infrastructure that implements data fabric 1 1614 may be logically divided as edge and core network infrastructure.
  • Edge network infrastructure may include network devices that couple the core network of data fabric 1 1614 to customer and cloud service provider networks.
  • Core network infrastructure may include network devices that forward network traffic through the core network of data fabric 1 1614.
  • CNC system 1 1601 includes edge network control module 1 1618 that configures and provisions services at network devices included in the edge network infrastructure of data fabric 1 1614.
  • CNC system 16601 also includes core network control module 1 1620 that configures and provisions services at network devices included in the core network infrastructure of data fabric 1 1614.
  • edge and/or core network control modules 1 1618, 1 1620 may be included in one or more NFUs and/or distributed between NFUs and CNC system 1 1601.
  • a customer of customers 11610 may desire to access one or more services provided by cloud service providers 11616.
  • the customer may desire to access an office productivity service of cloud service providers 11616.
  • the customer may submit a request using user portal 1 1602 for an L3 connection and firewall provided at data fabric 11614 that allows for the direct exchange of network traffic between the customer and the cloud service provider of the office productivity service.
  • Example user interfaces provided by user portal 11602 are illustrated in FIGS. 1 1 and 12.
  • CNC system 11601 receives the request for the L3 connection service.
  • Edge network control module 1 1618 and core network control module 11620 may each configure edge network infrastructure and core network infrastmcture, respectively, for the L3 connection service.
  • edge and core network control modules 11618, 11620 may identify one or more NFUs that will configure network infrastructure to provide the L3 connection service. For instance, edge network control 11618 may identify a first set of one or more NFUs to configure edge network infrastructure, while core network control module 11620 may identify a second set of one or more NFUs to configure core network infrastructure.
  • network control 1 1618 may directly configure edge network infrastmcture that couples the customer network to the core network of data fabric 11614 and the cloud service provider 11616 to the core network of data fabric 11614.
  • edge network control module 11618 may send instructions and/or requests for the L3 connection service and firewall service to one or more NFUs that configure the edge network infrastmcture that couples the customer network to the core network of data fabric 1 1614 and the cloud service provider 11616 to the core netw ork of data fabric 116.14.
  • core network control module 1 1620 may send instructions and/or requests for the L3 connection service and firewall to one or more NFUs that configure the core network infrastructure of data fabric 11614 and the cloud service pro vider 11616 to the core network of data fabric 11614.
  • NFUs that configure the core network infrastructure of data fabric 11614 and the cloud service pro vider 11616 to the core network of data fabric 11614.
  • the customer of customers 11610 that requested the L3 connection sendee may directly connect, via a network service provider and data fabric 11614, to the office productivity service.
  • one or more IT systems 1 1604 may be coupled to CNC system 11601.
  • IT systems 11604 may include one or more computing devices, such as desktop computers, tablets, smartphones, and servers, to name only a few examples.
  • IT systems 11604 may provide one or more user interfaces to administrators, which may use IT systems 11604 to administrate 11601.
  • IT systems 11604 may, for example, receive user inputs to configure CNC system. 11601.
  • IT systems 1 1604 may send requests and/or instructions to CNC system 1 1601.
  • CNC system 11601 may provide or otherwise expose one or more RESTful interfaces that can be invoked by IT systems 11604.
  • FIG. 11 is a block diagram illustrating an example user interface .12200 to request a sen-ice, in accordance with one or more techniques of the present disclosure.
  • a centralized network control system such as CNC system 10002 or CNC system 11601, or a portal to such, as system, may generate user interface 12200 for display.
  • user interface 12200 may be implemented as one or more HTML documents that may be rendered in a web browser.
  • User interface 12200 may be implemented in a standalone application that is executable on a mobile computing device, desktop computing device, or laptop device to name only a few examples, and that invokes a programmable network platform in a manner described herein. For example purposes, user interface 12200 is illustrated in a web browser in FIG. 11.
  • user interface 12200 may allow a user to configure an L3 connection sendee.
  • User interface 12200 may include a side menu 12202, which lists each different type of service that may be configured by a user.
  • Side menu 12202 may include one or more elements, where each respective element corresponds to a particular type of sen- ice.
  • An element may be selected by a user, which displays a corresponding user interface to configure the type of sendee associated with the element. For instance, as shown in FIG. 11, an element that corresponds to configuring a L3 connection sendee has been selected by the user. Accordingly, user interface 12200 includes user interface elements to configure a L3 connection sendee.
  • user interface 12200 includes a user interface element 12004, such as a label, that displays the type of sendee definition being configured by the user.
  • user interface element 12004 includes "L3 Connect" as the type of sendee definition that is being configured by the user, which may correspond to a L3 connection service.
  • the term "sendee definition" refers to data defining parameters for provisioning a business level sendee, within a cloud exchange, for one or more network sendees provided by (native service) or delivered by (cloud sendee or third-pariy service) the cloud exchange to a consumer of the aforementioned service(s).
  • a sendee definition may define multiple services within an overall sendee, including for each sen'ice one or more sen'ice requirements to implement the service.
  • Implementing a service may include both service orchestration and network provisioning, for instance.
  • Native services may include, e.g., a port service, L3 connectivity sen'ice, L2 sen'ice, L3+ service, firewall, NAT, DPI, and other native services applied within the cloud exchange to cloud sendee traffic from a cloud sen'ice provider network to modify, inspect, shape (e.g., filter or apply QoS), and/or deliver the cloud service traffic.
  • Cloud services may include Software-as-a-Service (SaaS), Platfonn-aaS (PaaS), Infrastructure - aaS (laaS), Virtualization-aaS (VaaS), and data Storage-aaS (dSaaS) sendees, such as content/media delivery, cloud-based storage, cloud computing, online gaming, IT services, etc.
  • SaaS Software-as-a-Service
  • PaaS Platfonn-aaS
  • laaS Infrastructure - aaS
  • VaaS Virtualization-aaS
  • dSaaS data Storage-aaS
  • sendee definition may specify cloud exchange endpoints and other connectivity information for connecting to a cloud sen'ice, policies, SLA, and/or QoS for a sendee, an originator, an owner, a service identifier, a destination, for example. Additional examples of service definitions are described below.
  • Certain parameters of the sendee definition such as bandwidth, policies, SLA, and QoS for the sendee to be applied within the cloud exchange, may be alternatively referred to as "sendee requirements" in that the requestor requires that the service be applied/delivered in such as manner as to meet such requirements.
  • user interface 12200 may include a user interface element 12006 that enables a user to select or otherwise specify a geographic location.
  • the geographic location may be a location of a customer site and/or a location of a cloud exchange point.
  • the user may use user interface element 12006 to provide a geographic location in San Jose, CA.
  • user interface element 12006 may be implemented as a drop-down menu that is pre-populated with available locations or may be implemented as a text input field in which the user may enter a location.
  • User interface 12200 may include a user interface element 12008 that enables a user to select or otherwise specify a network segment for the L3 connection service for the customer.
  • the network segment is defined by a range of layer 3 addresses, such as Internet Protocol (IP) addresses 12008.
  • IP Internet Protocol
  • the user may use user interface element 12008 to provide an IP address range of 10.10.10.0/24.
  • user interface element 12008 may be implemented as a drop-down menu that is pre-populated with available network segment values or may be implemented as a text input field in which the user may enter a network segment value.
  • User interface 12200 rnay include one or more user interface elements 12010 that enable a user to select or otherwise specify minimum and/or maximum performance requirements for the L3 connection service. For instance, a variety of bandwidths may be associated with the one or more user interface elements 12 10 from which the user may- select a minimum and/or maximum performance requirement for the service.
  • example performance requirements, selectable by the user include 1Mbps, 10 Mbps, 100 Mbps, 1 Gbps, 10 Gbps, 40 Gbps, and 100 Gbps.
  • user interface element 12010 may be implemented as a drop-down menu that is pre-populated with available bandwidths, a set of radio buttons or checklists where each selectable element has a corresponding bandwidth, or may be implemented as a text input field in which the user may enter a bandwidth.
  • User interface 12200 may include one or more user interface elements 12012, 12014, and 12016 that enable a user to, respectively, specify whether the bandwidth is burstable, specify an Excess Information Rate (EIR), and/or specify a maximum latency.
  • EIR Excess Information Rate
  • user interface element 12012 may be implemented as a checkbox
  • user interface element 12012 may be implemented as a text input field
  • user interface element 12016 may be implemented as a text input field, although other types of user interface elements may be also be used.
  • User interface 12200 may include one or more user interface elements 12018 that enable a user to select or otherwise specify an uptime or availability requirement for the L3 connection senice. For instance, a variety of availability levels may be associated with the one or more user interface elements 12018 from which the user may select an uptime or availability requirement for the service. In the example of FIG. 11, example uptime or availability requirements, selectable by the user, include 99.9999%, 99.999%, 99.995%, 99.99%, 99%, and 90% uptime.
  • user interface element 12018 may be implemented as a drop-down menu that is pre-populated with uptime or availability values, a set of radio buttons or checklists where each selectable element has a corresponding uptime or availability, or may be implemented as a text input field in which the user may enter an uptime or availability.
  • User interface 12200 may include one or more user interface elements 12020 that enable a user to select or otherwise specify a cloud service provider for the L3 connection service. For instance, the customer may select one or more cloud service providers that provide services which the customer may consume using the L3 connection service.
  • user interface elements 12020 may be implemented as a drop- down menu that is pre-populated with cloud service providers, a set of radio buttons or checklists where each selectable element has a corresponding cloud service provider, or may be implemented as a text input field in which the user may enter a cloud service provider.
  • User interface 12200 may include a user interface element 12022 that enables a user to select or otherwise specify a network segment for the L3 connection service for the cloud se dee provider. In some examples, the network segment is defined by a range of layer 3 addresses, such as Interact Protocol (IP) addresses 12022.
  • IP Interact Protocol
  • User interface 12200 may include one or more user interface elements 12024, 12026, and 12028 that enable a user to, respectively, select Distributed Denial-of-Service protection for the sen'ice, the Distributed Denial-of-Service protection provider, and/or a redirect IP address.
  • user interface element 12024 may be implemented as a radio button or checkbox
  • user interface element 12026 may be implemented as a dropdown list
  • user interface element 12028 may be implemented as a text input fi eld, although other types of user interface elements may be also be used.
  • User interface 12200 may include a user interface element 12030 to submit the selected and/or inputted values of user interface 12200 for further processing.
  • User interface element 12030 is implemented as a button in FIG. 1 1.
  • the selected and/or inputted values of user interface 12200 may ⁇ be validated and may be further processed to implement the service and/or provide an estimate of cost to implement the service to the user before actually implementing the service.
  • FIG. 12 is a block diagram illustrating an example user interface 12400 to display a cost estimate for a service, in accordance with one or more techniques of the present disclosure.
  • a centralized network control system such as CNC system 30002 or CNC system 11601, or a portal to such as system, may generate user interface 12400 for display.
  • user interface 12400 may be implemented as one or more HTML documents that may be rendered in a web browser.
  • User interface 12400 may be implemented in a standalone application that is executable on a mobile computing device, desktop computing device, or laptop device to name only a few examples, and that invokes a programmable network platform in a manner described herein. For example purposes, user interface 12400 is illustrated in a web browser in FIG. 12.
  • user interface 12400 may provide cost information for a service based on user input provided for user interface 12200 in FIG. 11.
  • user interface 12400 may include one or more user interface elements 12402 that include the input values provided by the user in user interface 12200 of FIG. 11. Accordingly, a user may review the input values to determine that the value are correct. If the user desires to change one or more values, the user may select user interface element 12204, which causes user interface 12200 to again be displayed with the input values, thereby allowing the user to update or otherwise change such input values.
  • user interface element 12204 may include user interface elements that allow the user to update or otherwise make changes to input values in user interface 12204 without returning to user interface 12200.
  • User interface 12400 may include one or more user interface elements that included one or more costs for the requested service.
  • user interface 12400 may include user interface element 32406, which displays a cost-per-month of the requested sen/ice. By outputting the cost-per-month for the requested service, the user may evaluate the cost of the service.
  • other cost values may be included in user interface 12400.
  • user interface 12400 may include itemized costs corresponding to one or more input values of user interface elements 12402.
  • alternative itemized costs for alternative input values may also be included in user interface 12400.
  • the alternative cost for 99.999% uptime may be included in user interface 12400.
  • the user upon reviewing the cost information, may select user interface element 12406 (e.g., a button) to submit the request for the service.
  • CNC system 10002 may configure one or more cloud exchange points to provision the service requested by the user based on the input values shown in user interface 12400.
  • FIG. 13 is a conceptual diagram illustrating example components for a programmable network platform operating according to techniques described in this disclosure.
  • programmable network platform 12500 includes a centralized network control component 12504 ("CNC 12504") that interfaces with a plurality of decentralized network field units 12508A-12508C ("NFUs 12508 " ') to provision devices of edge network 12600 and assure the delivery of layer 3 cloud services to customers.
  • Each of the NFUs 12508 may provision a different subset of devices, or ''portion of," edge network 12600.
  • edge network 12600 may include devices distributed among numerous cloud exchange points or metro-based cloud exchanges, each cloud exchange point or metro-based cloud exchange being provisioned for sen/ices by a different NFU 12508.
  • Programmable network platform 12500 may represent, e.g., an example instance of programmable network platform 120.
  • CNC 12504 may represent an example instance of CNC 1002 or CNC 11601.
  • NFUs 12508 may eacli represent an example instance of NFU 1004.
  • User portal 12502 represents client-side software for interfacing with the programmable network platform 12500 and may represent a customer portal, customer applications, a cloud exchange provider application, a console such as a command-line interface or graphical user interface, and/or a cloud service provider-developed application. Users/clients may include customers, the cloud exchange provider, and cloud service providers.
  • a controller such as the programmable network platform described herein, may provision the cloud exchange with services made up of multiple constituent services provided by different cloud service providers.
  • Each of these constituent services is referred to herein as a "micro-service” in that it is part of an overall service applied to service traffic. That is, a plurality of micro-services may be applied to service traffic in a particular "arrangement,” “ordering,” or “topology,” in order to make up an overall service for the service traffic.
  • Micro-sendees may be applied by cloud service providers or within the cloud exchange.
  • the programmable network platform may in this way orchestrate a business-level service across heterogeneous sendee providers.
  • the programmable network platform exposes interfaces by which a portal, console (e.g., user interface application), or other application may define the sendee policy, quality, sendee level agreements (SLAs), and cost as a coordinated sendee topology made up of micro-sendees provided by different cloud sendee providers (or "cloud vendors").
  • Each micro-service may have a corresponding service po cy, quality, SLA, and cost, as part of the overall, end-to-end business sendee definition, as described in further detail below.
  • the programmable network platform may orchestrate each of the micro-services within the cloud exchange and stitch the micro-sendees together according to the defined topology in order to reify the end-to-end sendee within the cloud exchange (or edge network that includes the cloud exchange).
  • the cloud exchange interconnects, in the data plane, micro-sendees provided by respective cloud sendees providers on behalf of and for the benefit of a customer of the cloud exchange or of at least one of the cloud sendee providers.
  • FIG. 14A is a block diagram that illustrates an example configuration of a programmable edge network that has been configured to apply multiple native sendees to cloud service traffic aggregated by a cloud exchange from multiple cloud service providers for delivery to a customer.
  • Edge network 12600 may include any of the data center-based cloud exchanges or cloud exchange points described herein, such as cloud exchange points 128 of FIG. 1 , cloud exchange 200 of FIG. 2, and the cloud exchange point of FIG. 10 including data fabric 11614.
  • Edge network 12600 includes network infrastructure including layer 3 (L3) forwarding elements 12622A-12622B (collectively, “forwarding elements 12622”), which may include one or more routers, switches, and other L3 forwarding devices. Although not shown, edge network 12600 may also include, for example, one or more non-edge (core) switches, routers, hubs, gateways, security devices such as firewalls, intrusion detection, and/or intrusion prevention devices, computer terminals, laptops, printers, databases, wireless mobile devices such as cellular phones or personal digital assistants, wireless access points, bridges, cable modems, application accelerators, or other network devices.
  • core non-edge
  • Edge network 12600 further includes servers 12640A-12640B (collectively, “servers 12640") that offer one or more compute/computing farms by which the edge network 12600 may offer services to customer 12604 and/or apply services to service traffic for customer 12604.
  • Servers 12640 may represent x86 or other real or general- purpose servers configured to apply and/or offer sen-ices to customers.
  • Servers 12640 may also include special-purpose appliances or containers for applying services to service traffic between customers and cloud service providers 12,606.
  • Such services may include, e.g., NAT, DPI, FW, DDOS mitigation, and other native services that may be applied by the cloud exchange edge network 12600 controlled by the cloud exchange provider and as configured by programmable network platform 12500.
  • the cloud exchange provider that manages, administers, and configures edge network 12600 facilitates the application of such native services to service traffic exchanged between customer 12604 and any of cloud se dee providers 12606A-12606D ("CSPs 12606"), each of which may represent any of cloud service providers 110 for instance.
  • CSPs 12606 cloud se dee providers 12606A-12606D
  • Edge network 12600 is configured with virtual NAT (vNAT) sendee 12614 for application to sendee traffic sourced by or destined to CSP 12606A, virtual Deep Packet Inspection (vDPl) sendee 12616 for application to service traffic sourced by or destined to CSP 12606B, and virtual Firewall (vFW) sendee 12618 for application to sendee traffic sourced by or destined to CSP 12606C, all such sendee traffic sourced by or destined to customer 12604.
  • vNAT virtual NAT
  • vDPl Deep Packet Inspection
  • vFW virtual Firewall
  • Services 12614, 12616, and 12618 may represent Network Function Virtuaiization (NFV) services in that the services virtualize functions frequently offered by network service providers employing dedicated service appliances (e.g., NAT, DPI, and firewall devices, whether employed separately or by an integrated Unified Threat Management (UMT) device, e.g.). While this example illustrates and describes virtual services (or NFVs), the services may be applied by controllers, appliances, or containers administered by the cloud exchange provider.
  • NFV Network Function Virtuaiization
  • PE router 12602 in this example represents a real or virtual PE router that aggregates sen-ice traffic from multiple cloud sendee providers 12606 for delivery to a single customer 12604.
  • Programmable network platform 12500 configures the PE router 12602 to import and export L3 routes for the cloud sen'ice providers 12606 to enable aggregated layer 3 cloud sendee cloud sendee delivery, as described above with respect to FIGS. 1-4.
  • programmable network platform 12500 allows customers, cloud sendee providers, and/or the cloud exchange provider to configure edge network 12600 with sen-ices 12614, 12616, and 12618 for assured deliver ⁇ - of cloud sendee traffic from respective cloud sendee providers 12606A-12606C.
  • a controller such as the programmable network platform described herein, may provision a L3 cloud-based sen-ices exchange ("cloud exchange") to deliver sendees made up of multiple constituent services provided by different cloud sen-ice providers and in some cases by the cloud exchange itself.
  • cloud exchange L3 cloud-based sen-ices exchange
  • Each of these constituent services is referred to herein as a "micro-service” in that it is part of an overall sendee applied to sen-ice traffic. That is, a plurality of micro-sendees may be applied to service traffic in a particular '"arrangement,” “ordering,” or “topology,” in order to make up an overall service for the service traffic.
  • the micro-sendees themselves may be applied or offered by the cloud sen'ice providers.
  • the programmable network platform may in this way orchestrate a business-level sen-ice across heterogeneous cloud service providers.
  • the programmable network platform exposes application programming interfaces (APIs) by which a portal, console (e.g., user interface application), or other application may define the sendee policy, quality, service level agreements (SLAs), and cost as a coordinated sen-ice topology made up of micro-sendees provided by different cloud service providers (or "cloud vendors").
  • Each micro-service may have a corresponding service policy, quality, SLA, and cost, as part of the overall, end-to-end business sendee definition, as described in further detail below.
  • the programmable network platform When provided with a service definition for an end-to-end sendee having multiple component micro-services, the programmable network platform orchestrates each of the micro-services within the cloud exchange and stitches the micro- services together according to the defined topology in order to reify the end-to-end sen' ice within the cloud exchange data plane (e.g., an edge network for the cloud exchange).
  • the cloud exchange interconnects, in the data plane, micro- services provided by respective cloud services providers on behalf of and for the benefit of a customer of the cloud exchange. In doing so, the cloud exchange provider may facilitate business transactions between the cloud service providers and customers.
  • FIG. 14B is a block diagram that illustrates an example configuration of a programmable edge network that has been configured to offer an end-to-end service that is a sequence of multiple constituent micro-services applied by respective cloud service providers.
  • Edge network 12600 may include any of the data, center-based cloud exchanges or cloud exchange points described herein, such as cloud exchange points 128 of FIG. 1, cloud exchange 200 of FIG. 2, and the cloud exchange point of FIG. 10 including data, fabric 11614.
  • Micro-services for an overall service established for a customer may include a mix of Software-as-a-Service (SaaS), Platform-aaS (PaaS), Infrastructure -aaS (laaS), Virtualization-aaS (VaaS), and data Storage-aaS (dSaaS) services in any ordering.
  • SaaS Software-as-a-Service
  • PaaS Platform-aaS
  • laaS Infrastructure -aaS
  • VaaS Virtualization-aaS
  • dSaaS data Storage-aaS
  • different cloud service providers 12606 may execute applications that analyze application data of service traffic 12612 to generate reporting data, store application data, generate new application data for sending as additional service traffic 12612 along the sequence of m icro-sendees, and so forth.
  • each of cloud service providers 12606 offers/executes a micro-service that edge network 12600 arranges (or "chains") together to form, an overall multi-cloud service for customer 12604. More specifically, in some aspects, the programmable network platform 12500 configures a router (or forwarder) 12602 to stitch togetlier the micro-services offered by respective various cloud senice providers 12606 into an overall service to apply to packets of sendee traffic 12612.
  • the customer 12604 may use the programmable network platform 12500 to select and arrange the micro-services of cloud service providers 12606 for at least some of the service traffic originated or received by the customer 12604 network.
  • the programmable network platform 12500 may offer the customer connectivity to multiple different cloud service providers.
  • the programmable network platform 12500 configures the edge network 12600 to provision connectivity for the micro-services for the customer 12604.
  • Selecting a cloud service provider may include entering connectivity parameters for the micro-service offered by the cloud service provider. Such connectivity parameters may include L3 routes and bandwidth or other QoS requirements.
  • router 12602 receives L3 routes for each of the cloud service provider 12606 networks that enable the router 12602 to forward service traffic 12612 along the overall end-to-end service path.
  • the programmable network platform 12500 may, for instance, configure one or more servers 12620A to execute a virtual router (or configure a dedicated router) that includes VRFs for each of the cloud sendee provider 12606 networks.
  • the VRFs may be associated with route targets to establish a hub- and-spoke topology for sending and receiving service traffic 12612, with router 12602, to and from the cloud service provider 12606 networks that offer the micro-sendees.
  • the cloud exchange provider that administers edge network 12600 may alleviate customer 12604 from establishing, administering, and at least in some instances assuring the end-to-end sendee that is made up of micro-sendees of cloud service providers 12606.
  • Customer 12604 for instance, can forward service traffic 12612 to edge network 12600 in accordance with cloud exchange provider routes and need not peer with cloud sendee provider 12606 networks in order to obtain routes for each of those networks.
  • the cloud exchange point of edge network 12600 internalizes the L3 routing protocol peering arrangements with the cloud service provider 12606 networks and imports the L3 routes to cloud sen ice provider 12606 networks in order to l sw ard sendee traffic along the topology of the overall sendee.
  • Router 12602 may include VRFs configured by the programmable network platform to import and export respective L3 routes for the services provided by cloud sendee providers 12606.
  • the router 12602 may receive the routes from the programmable network platform in some instances, or receive the routes via peering sessions with the provider edge (PE) routers of edge network 12600 that connect the cloud exchange to any of the cloud sendee provider 12606 networks.
  • PE provider edge
  • the edge network 12600 may advertise, to customer 12604, L3 routes of the cloud exchange point autonomous system NATed with L3 routes of the cloud sendee provider 12606D network by the cloud exchange, L3 routes for the vNAT service 12614, (in this example that includes a NAT service), or L3 routes of the cloud sen-ice provider 12606D network. In tins way, the edge network 12600 may aggregate the delivery of multiple, multi-cloud L3 sendees to customer 12604.
  • FIG. 14B illustrates the delivery, by edge network 12600, of an end-to-end sendee made up of multiple micro-services to sendee traffic 12612.
  • the customer 12604 network sends service traffic 12612 to edge network 12600 and destined for a network address within a prefix advertised as an L3 route by the edge network 12600 to the customer 12604 network.
  • Sendee traffic 12612 may include one or more packet flows, each packet flow associated with one or more packets that include application-layer data generated and/or consumed by an application executing within the customer 12604 network.
  • a cloud sendee provider 12606D may inject application data via router 12602 to an application executed by the cloud sendee provider 12606C network to analyze the application data, which sends the analyzed application data for processing to the cloud service provider 12606B network, which in turns send the application data for storage to a dSaaS-providmg cloud sendee provider 12606A network.
  • router 12602 receives sen ice traffic 12612, determines the first micro-sendee for service traffic 12612, and directs the sen/ice traffic 12612 to the cloud service provider 12606A network.
  • the cloud service provider 12606A network applies its micro-sen' ice returns the sendee traffic 12612 (which may be modified from the sendee traffic originated by the customer 12604 in accordance with the micro-sendee applied by cloud service provider 12606A) to router 12602.
  • Router 12602 determines the next micro-service for sendee traffic 12612 and forw ards the sendee traffic 12612 to cloud sendee provider 12606B.
  • the cloud sendee provider 12606B network applies its micro-service and returns the sendee traffic 12612 (which may be modified in accordance with the micro-sendee applied by cloud sendee provider 12606B) to router 12602.
  • Router 12602 determines the next micro-service for sendee traffic 12612 and forwards the sen/ice traffic 12612 to cloud sendee provider 12606C.
  • the cloud service provider 12606C network applies its micro-sendee and returns the sendee traffic 12612 (which may he modified in accordance with the micro-sendee applied by cloud sen-ice provider 12606C) to router 12602.
  • Router 12602 determines the next micro-service for service traffic 12612 and forwards the service traffic 12612 to cloud service provider 12606D.
  • CSPs 12606 may originate and edge network 12600 may deliver service traffic downstream to customer 12604, with edge network 12600 applying a set of micro-services to such downstream service traffic.
  • the cloud service provider 12606D network may include or otherwise represent a content delivery network (CDN).
  • CDN may offer streaming video, streaming audio, streaming multimedia, gaming content, or other content delivery services to customers, and in this case to customer 12604 via the cloud exchange.
  • the edge network 12600 including a cloud exchange interconnects, in the data plane, micro-services provided by respective cloud services providers 12606 on behalf of and for the benefit of a customer 12604 of the cloud exchange or of at least one of the cloud service providers.
  • a programmable network platform may orchestrate each of the micro-services within the cloud exchange and stitch the micro- services together according to the defined topology in order to reify the end-to-end service within the cloud exchange (or edge network that includes the cloud exchange).
  • the service definition for an end-to-end service may enable a user of the programmable network platform to define not only the end-to-end service but also the service topology in such a ways as to ensure the correct sequencing of the micro-services service chain.
  • the data encapsulated in the data model for the sendee definition may also include the authoritative sendee owner for business purposes (e.g., billing and SLA assurance).
  • the "user” may refer to a customer, the cloud exchange provider, or a cloud service provider that is the authoritative sendee owner.
  • the programmable network platform (or other orchestration systems such as SDN controllers or orchestrators) may be enabled to recognize a service request as a request for a set of micro-services that make up the entire sendee.
  • the service definition includes several sections that will enable the programmable network platform to provide the sendee of chaining several services, whether of native services provided by the cloud exchange provider or of cloud services provided one or multiple cloud sendee providers.
  • die cloud exchange provider thai administers the programmable network platform is able to provide a service chain that, when given respective definitions for multiple micro-services and a topology (or sequence) for the multiple micro-services, interconnects the micro-services according to the topology to facilitate an end-to-end service.
  • the data model thus provides data with which the programmable network platform can effecti vely instantiate the requested chain of services and to also ensure that the services thus rendered are chained in the correct topology.
  • the data model may be divided by the programmable network platform into one or more service requests that the native programmable network platform for the cloud exchange may issue to other service orchestration systems to complete.
  • Other sendee orchestration systems may include, e.g., SDN controllers and/or orchestration systems for cloud sendee providers thai facilitate NFV-instantiation and service traffic routing to/from NFV instances.
  • a sendee definition conforming to a multi-cloud, multi-service data model of the described techniques may specify an overall end-to-end sendee associated with one or more of ( 1) an originator, (2) an owner, (3) a identifier, (4) a destination, and (5) a topology.
  • the originator refers to the end-to-end sendee requestor, typically but not exclusively a customer of the cloud exchange.
  • the owner refers to the authoritative sendee owner that, e.g., handles and is responsible for billing and charging to the originator/customer on behalf of the cloud sendee providers.
  • the identifier uniquely identifies the end-to-end sendee within the cloud exchange.
  • the destination refers to the cloud exchange where the requested service is instantiated.
  • the topology determines the sequence of an array of micro-services included in the sendee definition.
  • Each micro-sendee defined within a sendee definition may be an element of an array of micro-sendees.
  • a micro-sendee may be associated in the data, model with one or more of (1 ) descriptive information, (2) a first or "customer" endpoint, (3) a second or " 'cloud service provider” endpoint, (4) policies to be applied by the cloud exchange for the micro-sendee, (5) Quality -of-Service (QoS) parameters for the micro-sendee, and (6) a time range for the micro-service.
  • (1 ) descriptive information e.g., (2) a first or "customer" endpoint, (3) a second or " 'cloud service provider” endpoint, (4) policies to be applied by the cloud exchange for the micro-sendee, (5) Quality -of-Service (QoS) parameters for the micro-sendee, and (6) a time range for the micro-service.
  • QoS Quality -of-Service
  • the descriptive information may include a unique identifier for the micro-sendee within the cloud exchange .
  • the first endpoint for the data model may specify a customer identifier to which the cloud exchange is to attach for service delivery, and a sendee key.
  • a sendee key is the license key obtained by a customer for purposes of instantiating and activating a requested service.
  • the cloud exchange may obtain the sen/ice key from the cloud service provider and use the se dee key to instantiate and activate the service.
  • the second endpoint for the data model may specify a cloud service provider identifier to which the cloud exchange is to attach for service delivery, and a service key.
  • Each endpoint description for the first and second endpoint may also include endpoint specific data, such as a metro location identifier, port identifiers, data center identifiers, virtual circuits and virtual circuit bandwidth, profiles, and configuration, and so forth.
  • the policies may identify the configuration and settings to be applied on corresponding micro-services.
  • a policy may include firewall rales for a firewall micro-service within the service chain.
  • Another policy may include packet inspection rules for a DPI micro-service.
  • Another policy may specify the QoS to be applied for a QoS micro-service.
  • the time range is used to specify the duration for which the service metrics are to be reported when querying the status of the se dee. In some examples, the time range is used only during the READ operation of the service.
  • the programmable network sendee data model may be used by a service interface of any of the examples of programmable network platforms described herein to allow external applications to define a topology of micro-sendees.
  • MS_API definition is an example of a programmable network sendee data model, according to techniques described herein:
  • SRVC_Num Integer // Number of SRVC_API elements
  • the MS API end-to-end service definition data model includes SRVC Tag and SRVC Value containers.
  • the SRVC Tag container includes values associated with the overall service definition. Specifically, SRVC_Orig specifies the originator, SRVC_Owner specifies the authoritative owner for the service, SRVC_accID specifies the account identifier belonging to the sen/ice originator that identifies the originator to the cloud exchange provider., SRVC Dest specifies the the cloud exchange where the requested service is instantiated, and SRVC_Topology specifies a sequence of an array of micro-services specified in the SRVC Value container.
  • the SRVC Value is a micro-service definition container and includes one or more micro-service definitions for respective micro-services.
  • the following SRVC_API data model is an example of a micro-service definition, e.g., for the MS_API definition model above:
  • the above service definition includes service definition ("Srvc_Defh”), policy (“Policy”), quality of sen-ice (“QOS”), and time range (“TirneRange”) containers for specifying and obtaining characteristics of a micro-service via the programmable network platform.
  • the service definition container specifies descriptive information for the micro- service, including Srvc_AccID, Srvc_Type, Srvc_Oper_Type, Srvc JD, Target_SP, Srvc Vendor.
  • Srvc AccID is a unique account identifier that identifies a particular service originator uniquely with the particular target service provider, Target SP.
  • Srvc_Type may be applicable only when native cloud exchange services are provided and,defines the type of cloud exchange sen-ice being delivered.
  • Sivc Oper Type specifies the operation type, i.e., one of the CRUD operations.
  • Sn r c ID is to be provided by the originator for an already existing (e.g., already created) sen-ice for which a Read, Update or Delete operations are to be performed.
  • Target_SP is the target sendee provider that provides the requested sen-ice
  • the EndPointl container defines a first endpoint of the cloud exchange for the micro-seniee and specifies a sen-ice provider identifier (SP_ID) to which the cloud exchange is to attach for sen-ice delivery using a service key or license key.
  • the Endpoint2 container defines a second endpoint of the cloud exchange for the micro- sen-ice and specifies a cloud sen-ice provider identifier ("CSP_ID") to which the cloud exchange is to attach for service deliver -, and a senice key.
  • Each endpoint description for the first and second endpoints also includes endpoint specific data, such as a metro location identifier, port identifiers, data center identifiers, and so forth.
  • the policies in the Policy container may identify the configurations settings that needs to be applied to the senice being instantiated, examples of policies for said services including firewall rules, NAT rules, encryption policies, WAN optimization policies, and so forth. In other words, the policies determine how the services applied will be configured for application to the senice traffic between the first and second endpoints for the micro-service.
  • the QoS parameters in the QOS container specify the QoS to be applied to service traffic for the micro-service.
  • the time range in the TirneRange container specifies a start time and end time that define a duration of the micro-service, during which the programmable network platform may provide assurance to the originator and/or owner using the sen' ice identifier ("Srvc_ID").
  • the interface for communicating sendee definitions according to the data model may include extensible Markup Language (XML) or JavaScript Object Notation (JSON) over HTTP/HTTPS. That is, the cloud exchange provider may define an XML/JSON interface that receives service definitions according to the above-described exampled service data mode, and expose HTTP endpoints by which to receive such service definitions.
  • XML extensible Markup Language
  • JSON JavaScript Object Notation
  • FIG. 15 is a conceptual diagram illustrating interfaces among components for programming a cloud exchange using a programmable network platform according to techniques described in this disclosure.
  • Programmable network platform 12500 exposes a service API 12710 for service delivery and data access.
  • This various embodiments of APIs and other interfaces described elsewhere in this disclosure for communicating with embodiments of programmable network platform 12500 may all represent examples of service API 12710.
  • Se dee API 12710 may use a programmable network service data model, such as MS A PI described above, for defining an end-to-end se ice made up of a topology of micro-sendees.
  • Meta console 12704 represents a platform manufactured by the cloud service provider, usable by cloud sendee provider technicians or operators, e.g., that invokes the sendee API 12710 of programmable network platform 12500.
  • CX or customer portal 12702 represents a platform manufactured by the cloud sendee provider, usable by enterprise/customer/CSP technicians or operators, e.g., that invokes the service API 12710 of programmable network platform. 12500.
  • Cloud exchange developer (CX API) 32700 represents third-party developed or cloud- service provider-developed platforms created by third-party developers (e.g., CSP or customer developers) or cloud exchange provider developers that invoke service API 12710 to request services from the programmable network platform 12500.
  • Business Applications 12706 may store accounting information for customers. For instance, Business Applications 12706 may store billing information for customers, such as name, customer identifier, address, phone number, email, to name only a few examples. When programmable network platform 12500 configures a sendee for a customer that includes a service charge, Business Applications 12706 may store such expense information. In this way, Business Applications 12706 may provide an accounting of services purchased by a customer and provide unified billing for such services.
  • the API between Business Applications 12706 and programmable network platform 12500 may include PACE integration,
  • FIG. 16 is a block diagram illustrating a programmable network platform that includes interfaces by which external applications may configure a cloud exchange to facilitate delivery of cloud services from cloud service providers according to techniques described in this disclosure.
  • programmable network platform 12500 exposes a sen-ice API 12820 for service delivery and data access.
  • This various embodiments of APIs and other interfaces described elsewhere in tins disclosure for communicating with embodiments of programmable network platform 12500 may all represent examples of service API 12820.
  • Service API 12820 includes, in this example, at least one third-party plugin 12810 developed by cloud service providers and executed by the programmable network platform 12500 to request and establish layer 3 cloud services from the cloud service providers.
  • Plugin 12810 may represent any of third-party orchestration modules 10404.
  • the plugin 12810 may implement a common plugin interface for the programmable network platform 12500 and translate interface methods, fields, etc., to a cloud service provider interface for CSP orchestration.
  • programmable network platform 12500 may invoke plugin 12810 to request a service instance from a cloud service provider for the cloud exchange provider (e.g., a 60 GB data storage service).
  • Plugin 12810 for the cloud service provider receives the request and invokes CSP orchestration system 12800 to allow the cloud sendee provider to orchestrate the instantiation of the requested service.
  • CSP orchestration 12800 via plugin 12810 then returns connectivity information in the fonn of a "network handle" to the programmable network platform 12500.
  • the network handle includes information by which the cloud exchange can connect to the instantiated, requested service.
  • the network handle may- include a VxLAN or VLAN identifier, a layer 3 route or network address, tunnel information and/or cloud aggregate link information.
  • the programmable network platform 12500 uses the network handle to configure edge network 12600 to connect to the instantiated, requested sendee, and to interconnect at least one customer network to the instantiated, requested service.
  • Operations portal 12804 represents a platform manufactured by the cloud sendee provider, for use by cloud service provider 12804 technicians or operators, e.g., that invokes the service API 12820 of programmable network platform 12500.
  • CSP orchestration system 12800 represents one or more systems developed by the cloud service providers and usable by the programmable network platform 12500 to request layer 3 services from the cloud service providers.
  • API gateway 12802 offers a high-level API by which customer-developed platforms or a cloud service provider-developed customer portal may request services from the programmable network platform 12500. Additional details of the API gateway and high-level API are found in U.S. Provisional Patent Appln. No. 62/072,976, incorporated above.
  • FIG. 17 is a block diagram illustrating further details of one example of a computing de vice that operates in accordance with one or more techniques of the present disclosure.
  • FIG. 17 may illustrate a particular example of a server or other computing device 13500 that includes one or more processor(s) 13502 for executing any one or more of the programmable network platform components (e.g., CNC, NFU, etc.), or any other system, application, or module described herein.
  • Other examples of computing device 13500 may be used in other instances. Although shown in FIG.
  • a computing device may be any component or system that includes one or more processors or other suitable computing environment for executing software instructions and, for example, need not necessarily include one or more elements shown in FIG. 17 (e.g., communication units 13506; and in some examples components such as storage device(s) 13508 may not be co-located or in the same chassis as other components).
  • computing device 13500 includes one or more processors 13502, one or more input devices 13504, one or more communication units 13506, one or more output devices 13512, one or more storage devices 13508, and user interface (UI) device 13510, and communication unit 13506.
  • Computing device 13500 in one example, further includes one or more applications 13522, programmable network platform application(s) 13524, and operating system 13516 that are executable by computing device 13500.
  • Each of components 13502, 13504, 13506, 13508, 13510, and 13512 are coupled (physically, communicatively, and/or operatively) for inter-component communications.
  • communication channels 13514 may include a system bus, a network connection, an inter-process communication data structure, or any other method for communicating data.
  • components 13502, 13504, 13506, 13508, 13510, and 13512 may be coupled by one or more communication channels 13514.
  • Processors 13502 are configured to implement functionality and/or process instructions for execution within computing device 13500.
  • processors 13502 may be capable of processing instructions stored in storage device 13508.
  • Examples of processors 13502 may include, any one or more of a microprocessor, a controller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or equivalent discrete or integrated logic circuitry.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field-programmable gate array
  • One or more storage devices 13508 may be configured to store information within computing device 13500 during operation.
  • Storage device 13508, in some examples, is described as a computer-readable storage medium.
  • storage device 13508 is a temporary memory, meaning that a primary purpose of storage device 13508 is not long-term storage.
  • Storage device 13508, in some examples, is described as a volatile memory, meaning that storage device 13508 does not maintain stored contents when the computer is turned off. Examples of volatile memories include random access memories (RAM), dynamic random, access memories (DRAM), static random access memories (SRAM), and other forms of volatile memories known in the art.
  • RAM random access memories
  • DRAM dynamic random, access memories
  • SRAM static random access memories
  • storage device 13508 is used to store program instructions for execution by processors 13502.
  • Storage device 13508, in one example, is used by software or applications running on computing device 13500 to temporarily store information during program execution.
  • Storage devices 13508 also include one or more computer- readable storage media.
  • Storage devices 13508 may be configured to store larger amounts of information than volatile memory.
  • Storage devices 13508 may further be configured for long-term storage of information.
  • storage devices 13508 include non-volatile storage elements. Examples of such non-volatile storage elements include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
  • Computing device 13500 also includes one or more communication units 13506.
  • Computing device 13500 utilizes communication units 13506 to communicate with external devices via one or more networks, such as one or more wired/wireless/mobile networks.
  • Communication units 13506 may include a network interface card, such as an Ethernet card, an optical transceiver, a radio frequency transceiver, or any other type of device that can send and receive information.
  • computing device 13500 uses communication unit 13506 to communicate with an external device.
  • Computing device 13500 also includes one or more user interface devices 13510.
  • User interface devices 13510 are configured to receive input from a user through tactile, audio, or video feedback.
  • Examples of user interface devices(s) 13510 include a presence-sensitive display, a mouse, a keyboard, a voice responsive system, video camera, microphone or any other type of device for detecting a command from, a user.
  • a presence-sensitive display includes a touch-sensitive screen.
  • One or more output devices 13512 may also be included in computing device 13500.
  • Output device 13512 in some examples, is configured to provide output to a user using tactile, audio, or video stimuli .
  • Output device 13512 in one example, includes a presence-sensitive display, a sound card, a video graphics adapter card, or any other type of device for converting a signal into an appropriate form understandable to humans or machines.
  • Additional examples of output device 13512 include a speaker, a cathode ray tube (CRT) monitor, a liquid crystal display (LCD), or any other type of device that can generate intelligible output to a user.
  • CTR cathode ray tube
  • LCD liquid crystal display
  • Computing device 13500 may include operating system 13516.
  • Operating system 33516 controls the operation of components of computing device 13500.
  • operating system 13516 in one example, facilitates the communication of one or more applications 13522 and programmable network platform application(s) 13524 with processors 13502, communication unit 13506, storage device 13508, input device 13504, user interface devices 13510, and output device 13512.
  • Application 522 and programmable network platform appiication(s) 13524 may also include program instructions and/or data that are executable by computing device 33500.
  • Example programmable network platform application(s) 33524 executable by- computing device 13500 may include any one or more of centralized network control application 13550 (' " CNC 13550”) and network field unit application 13552 ("NFU 13552”), each illustrated with dashed lines to indicate that these may or may not be executable by any given example of computing device 13500.
  • Centralized network control 13550 may include instructions for causing computing device 13500 to perform one or more of the operations and actions described in the present disclosure with respect to centralized network control .
  • CNC 13550 may include instructions that cause computing device 13500 to establish, deinstall and manage interconnections with multiple, different cloud service providers participating in the cloud exchange in an automated and seamless manner.
  • Network Field Unit 13552 may include instructions for causing computing device 13500 to perform one or more of the operations and actions described in the present disclosure with respect to network field units.
  • NFU 13552 may include instructions that cause computing device 13500 to receive requests or instructions from a CNC executing on another server, e.g., in a different geographically location such as a different data center, to configure network infrastructure of a cloud exchange point in order to provision one or more sen-ices.
  • a method comprising receiving, by a programmable network platform for a cloud-based sendees exchange point within a data center, a sendee request that includes a sendee definition according to a data model, wherein the sendee defmition specifies a plurality of cloud services provided by respective cloud sen/ice provider networks operated by respective cloud service providers, wherein the sendee request further specifies a topology for the plurality of cloud services: and provisioning, by the programmable network platform responsive to the sendee request, the cloud-based services exchange point to forward service traffic for the plurality of cloud services according to the topology for the plurality of cloud sendees.
  • Clause 3 The method of clause 1, wherein the service definition includes an authoritative sendee owner for an overall service comprising the plurality of cloud services.
  • Clause 7 The method of clause 1, wherein the service definition includes a value specifying a number of the plurality of cloud services.
  • Clause 8 The method of clause 1, wherein the service definition specifies each of the plurality of cloud services according to a common micro-service definition.
  • Clause 1 1. The method of clause 8, wherein the common micro-service definition specifies a quality of service definition that defines a quality of service to apply to a cloud service.
  • Clause 13 The method of clause 1 , wherein to specify the plurality of cloud services the service definition includes an array of a plurality of micro-service definitions that define corresponding cloud services of the plurality of cloud services.
  • a network data center comprising a cloud-based services exchange point comprising a network, the cloud-based services exchange point operated by a cloud exchange provider that operates the network data center; and a programmable network platform comprising at least one programmable processor configured to receive a service request that includes a service definition according to a data model, wherein the service definition specifies a plurality of cloud services provided by respective cloud service provider networks operated by respective cloud service providers, wherein the service request further specifies a topology for the plurality of cloud sen/ices, and wherein the service definition specifies each of the plurality of cloud services according to a common micro-service definition: and provision, responsive to the service request, the cloud-based services exchange point to forward service traffic for the plurality of cloud sen/ices according to the topology for the plurality of cloud services.
  • Clause 15 The network data center of clause 14, wherein the common micro- service definition specifies a first end oint that identifies a first cloud service provider for a cloud service and a second endpoint that identifies one of a customer and a second cloud service provider,
  • Clause 17 The network data center of clause 14, wherein the common micro- service definition specifies a quality of sendee definition that defines a quality of service to apply to a cloud service.
  • Clause 18 The network data center of clause 14, wherein the common micro- service definition specifies a time range definition that defines a range of time during which the cloud-based sen/ices exchange is to provide assurance of the delivery of a cloud service by the cloud-based services exchange.
  • Clause 19 The network data center of clause 14, wherein to specify the plurality of cloud services the sen-ice definition includes an array of a plurality of micro- service definitions that define corresponding cloud services of the plurality of cloud sendees.
  • a non-transitory computer readable medium comprising instructions that, when executed, cause at least one programmable processor of a programmable network platform for a data center-based cloud exchange to perform operations comprising receiving a sendee request that includes a sendee definition according to a data model, wherein the sendee definition specifies a plurality of cloud services provided by respective cloud service provider networks operated by respective cloud sendee providers, wherein the sendee request further specifies a topology for the plurality of cloud sendees; and provisioning, to the service request, the cloud-based sendees exchange point to forward sendee traffic for the plurality of cloud services according to the topology for the plurality of cloud sendees.
  • a method comprising receiving, by a programmable network platfonn for a cloud-based services exchange point within a data center, a service request that specifies a plurality of cloud se dees provided by respective cloud service provider networks operated by respective cloud service providers, wherein the service request further specifies a topology for the plurality of cloud sendees; and provisioning, by the programmable network platform responsive to the service request, tlie cloud-based sendees exchange point to forward service traffic for the plurality of cloud sendees according to the topology for the plurality of cloud sendees.
  • provisioning the cloud-based services exchange point comprises configuring, by tlie programmable network platform, a virtual router of the cloud-based sendees exchange point to receive respective layer 3 routes for the cloud sendee provider networks, and wherein the virtual router forwards the sendee traffic according to the layer 3 routes for the cloud sendee provider networks according to the topology for the plurality of cloud sendees.
  • the cloud-based sendees exchange point comprises a layer three (L3) autonomous system operated by a cloud exchange provider and located within a data center, wherein the L3 autonomous system comprises an Internet Protocol network interconnecting a plurality of provider edge (PE) routers by a plurality of tunnels, and wherein to provision the cloud-based sendees exchange point the programmable network platform configures the plurality of PE routers to establish an end-to-end L3 path comprising one of the plurality of tunnels and connecting, at layer 3, each of the cloud sendee provider networks to the virtual router.
  • L3 autonomous system comprises an Internet Protocol network interconnecting a plurality of provider edge (PE) routers by a plurality of tunnels
  • PE provider edge
  • Clause 4 The method of clause 3, wherein to provision tlie cloud-based services exchange point the programmable network platform configures the plurality of PE routers with configuration data defining respective virtual private network routing and forwarding instances (VRFs) for the plurality of cloud services, wherein the plurality of PE routers receive, via a first routing protocol, the respective layer 3 routes for the cloud sendee provider networks, and wherein the virtual router receives the respective layer 3 routes for the cloud sendee provider networks, via a second routing protocol, from the plurality of PE routers.
  • VRFs virtual private network routing and forwarding instances
  • provisioning the cloud-based services exchange point comprises configuring, by tlie programmable network platform, a virtual router of the cloud-based sendees exchange point with respective layer 2 virtual private networks for the cloud sendee provider networks, and wherein the virtual router forwards the service traffic according to the respective layer 2 virtual private networks for the cloud sen/ice provider networks according to the topology for the plurality of cloud services.
  • Clause 6 The method of clause 1, wherein the sendee request conforms to a service definition that identifies the service request as a request for the plurality of cloud services.
  • Clause 8 The method of clause 7, wherein the authoritative service owner is a cloud exchange provider that operates the cloud-based services exchange.
  • Clause 10 The method of clause 1, wherein the service request is originated by a customer of the cloud-based sendees exchange.
  • Clause 1 1. The method of clause 1, further comprising sending, by the programmable network platform for each cloud service of the plurality of cloud services, a sendee request for the cloud sen ice to an orchestration system for the corresponding cloud service provider network to cause the orchestration system to orchestrate the cloud sendee within the cloud sendee provider network.
  • Clause 12 The method of clause 1, wherein the sendee request further specifies a native sendee applied by the cloud-based sendees exchange point, the method further comprising provisioning, by the programmable network platform responsive to the service request, the cloud-based services exchange point to apply the native service to service traffic for at least one of the plurality of cloud services.
  • a network data center comprising a cloud-based sendees exchange point comprising a network, the cloud-based services exchange point operated by a cloud exchange provider that operates the network data center; and a programmable network platform comprising at least one programmable processor configured to receive a sendee request that specifies a plurality of cloud sendees provided by respective cloud sendee provider networks operated by respective cloud service providers, wherein the sendee request further specifies a topology for the plurality of cloud services: and provision, responsive to the service request, the cloud-based sendees exchange point to forward sendee traffic for the plurality of cloud services according to the topology for the plurality of cloud services.
  • provisioning the cioud-based se dees exchange pomt comprises configuring, by the programmable network platform., a virtual router of the cloud-based sendees exchange point to receive respective layer 3 routes for the cloud sendee provider networks, and wherein the virtual router forwards the service traffic according to the layer 3 routes for the cloud service provider networks according to the topology for the plurality of cloud se dees.
  • the cloud-based services exchange point comprises a layer three (L3) autonomous system operated by a cloud exchange provider and located within the network data center, wherein the L3 autonomous system, comprises an Internet Protocol network interconnecting a plurality of provider edge (PE) routers by a plurality of tunnels, and wherein to provision the cloud- based services exchange point the programmable network platform configures the plurality of PE routers to establish an end-to-end L3 path comprising one of the plurality of tunnels and connects, at layer 3, each of the cloud sendee provider networks to the virtual router.
  • L3 autonomous system comprises an Internet Protocol network interconnecting a plurality of provider edge (PE) routers by a plurality of tunnels, and wherein to provision the cloud- based services exchange point the programmable network platform configures the plurality of PE routers to establish an end-to-end L3 path comprising one of the plurality of tunnels and connects, at layer 3, each of the cloud sendee provider networks to the virtual router.
  • PE provider edge
  • provisioning the cloud-based sendees exchange point comprises configuring, by the programmable network platform, a virtual router of the cloud-based sendees exchange point with respective layer 2 virtual private networks for the cloud service provider networks, and wherein the virtual router forwards the service traffic according to the respective layer 2 virtual private networks for the cloud sendee provider networks according to the topology for the plurality of cloud sendees.
  • Clause 17 The network data center of clause 13, wherein the service request conforms to a sendee definition that identifies the sendee request as a request for the plurality of cloud sendees.
  • Clause 18 The network data center of clause 13, wherein the sendee request specifies an authoritative service owner for an overall service comprising the plurality of cloud sendees.
  • Clause 19 The network data center of clause 13, wherein the sendee request specifies a service identifier for an overall service comprising the plurality of cloud services.
  • a non-transitory computer readable medium comprising instructions that, when executed, cause at least one programmable processor of a programmable network platform for a data center-based cloud exchange to perform operations comprising receiving a service request that specifies a plurality of cloud services provided by respective cloud service provider networks operated by respective cloud service providers, wherein the service request further specifies a topology for the plurality of cloud sendees; and provisioning, to the sendee request, the cloud-based sen-ices exchange point to fonvard sendee traffic for the plurality of cloud services according to the topology for the plurality of cloud sendees.
  • a programmable network platform comprising at least one programmable processor; a third-party orchestration module configured for execution by the at least one programmable processor to communicate with a cloud service provider orchestration system: and a centralized network controller configured for execution by the at least one programmable processor to receive a sendee request that specifies a cloud sendee applied by a cloud service provider network operated by a cloud sendee provider on a network of a cloud exchange operated by a cloud exchange provider, wherein the centralized network controller is further configured to, in response to the service request, invoke the third-party orchestration module to communicate with the cloud sendee provider orchestration system to request that the cloud sendee provider orchestrate the cloud sendee on the network of the cloud exchange, and wherein the centralized network controller provisions the network of the cloud exchange within a data center to deliver the cloud sendee from the cloud sendee provider network attached to the network of the cloud exchange to a customer network attached to the network of the cloud exchange.
  • Clause 5 The programmable network platform of clause 1, wherein the centralized network controller is further configured to receive, from the third-party orchestration module, connectivity information for the cloud service, and wherein to provision the network of the cloud exchange to deliver the cloud service, the centralized network controller is further configured to provision, based on the connectivity information, the network of the cloud exchange to enable network connectivity between the network of the cloud exchange and the cloud service provider network for deliver ⁇ ' of the cloud service.
  • the connectivity information comprises at least one of a Virtual Local Area Network (VLAN) identifier, a Vx Local Area Network (VxLAN) identifier, a route specifying a network address of the cloud service provider network, and a port in the network of the cloud exchange.
  • VLAN Virtual Local Area Network
  • VxLAN Vx Local Area Network
  • the third- party orchestration module comprises a first third-party orchestration module
  • cloud service provider orchestration system comprises a first cloud service provider orchestration system
  • the cloud service provider comprises a first cloud service provider
  • the cloud service provider network comprises a first cloud service provider network
  • the cloud service comprises a first cloud service
  • the sendee request comprises a first service request
  • the programmable network platform further comprising a second third-party orchestration module configured for execution by the at least one programmable processor to communicate with a second cloud service provider orchestration system
  • the centralized network controller is further configured for execution by the at least one programmable processor to receive a second service request that specifies a second cloud service applied by a second cloud service provider network on the network of the cloud exchange
  • the centralized network controller is further configured to, in response to the second sendee request, invoke the second third-party orchestration module to communicate with the second cloud sendee provider orchestration system to request that
  • Clause 8 The programmable network platform of clause 7, wherein the first third-party orchestration module and second third-party orchestration module register a common interface with the centralized network controller by which the centralized network controller can invoke the first third-party orchestration module and second third- part ⁇ ' orchestration module to orchestrate services.
  • the network of the cloud exchange comprises a layer three (L3) autonomous system operated by the cloud exchange provider and located within a data center; a plurality of attachment circuits configured to connect, within the data center, plurality of cloud service provider networks to the L3 autonomous system, the plurality of cloud se dee provider networks including the cloud service provider network; and one or more attachment circuits configured to connect, within the data center, one or more customer networks to the L3 autonomous system, the one or more customer networks including the customer network, wherem the centralized network controller provisions the L3 autonomous system to interconnect the plurality of cloud service provider networks and the one or more customer networks by establishing end-to-end network paths between the plurality of cloud se dee provider networks and the one or more customer networks, each end-to-end network path including one of the plurality of attachment circuits connecting the respective plurality of cloud sen-ice provider networks to the L3 autonomous system and also including one of the one or more attachment circuits connecting the respective one or more customer networks to the
  • Clause 13 The programmable network platform of clause 1, wherein the network of the cloud exchange comprises a layer three (13) autonomous system operated by the cloud exchange provider and located within a data center, wherein the L3 autonomous system comprises an Internet Protocol network interconnecting a plurality of provider edge (PE) routers by a plurality of tunnels, and wherein to provision the network of the cloud exchange the centralized network controller is further configured to configure the plurality of PE routers to establish an end-to-end L3 path comprising one of the plurality of tunnels and connecting, at layer 3, the cloud service provider network to the customer network.
  • PE provider edge
  • a method comprising receiving, by a centralized network controller of a programmable network platform, a service request that specifies a cloud service applied by a cloud service provider network operated by a cloud service provider on a network of a cloud exchange operated by a cloud exchange provider; invoking, by the centralized network controller in response to the service request, a third-party orchestration module to communicate with the cloud service provider orchestration system, to request that the cloud service provider orchestrate the cloud service on the network of the cloud exchange; and provisioning, by the centralized network controller, the network of the cloud exchange within a data center to deliver the cloud service, from the cloud service provider netw ork attached to the cloud-based services exchange point, to a customer network attached to the cloud-based sendees exchange point.
  • Clause 15 The method of clause 14, further comprising receiving, by the centralized network controller from the third-party orchestration module, a list of sen-ices offered by the cloud service provider network.
  • Clause 16 The method of clause 14, wherein the centralized network controller is further configured to send the list of services to a customer portal application for display to a customer that operates the customer network.
  • the connectivity information comprises at least one of a Virtual Local Area Network (VLAN) identifier, a Vx Local Area Network (VxLAN) identifier, a route specifying a network address of the cloud service provider network, and a port in the cloud-based services exchange point.
  • VLAN Virtual Local Area Network
  • VxLAN Vx Local Area Network
  • Clause 19 The method of clause 14, wherein the network for the cloud exchange comprises an edge network operated by the cloud exchange provider, and wherein to provision the network for the cloud exchange the centralized network controller provisions the edge network to receive cloud service traffic for the cloud service and for distribution to the customer network.
  • a network data center comprising a cloud exchange comprising a network, the cloud exchange operated by a cloud exchange provider; and a programmable network platform comprising at least one programmable processor; a third-party orchestration module to communicate with a cloud service provider orchestration system; and a centralized network controller configured for execution by the at least one programmable processor to receive a service request that specifies a cloud sen-ice applied by a cloud service provider network operated by a cloud service provider on the network of a cloud exchange, wherein the centralized network controller is further configured to, in response to the sendee request, invoke the third-party orchestration module to communicate with the cloud service provider orchestration system to request that the cloud sendee provider orchestrate the cloud sendee on the network of the cloud exchange, and wherein the centralized network controller provisions the network of the cloud exchange to deliver the cloud sendee from the cloud service provider network attached to the network of the cloud exchange to a customer network attached to the network of the cloud exchange.
  • a method comprising providing, by a centralized network control (CNC) system., a software interface to receive service requests for configuration of services within an edge network of one or more network data centers that are controlled by tire CNC system; receiving, by the CNC system and via the software interface, a service request to configure a service within the edge network of the network data center, wherein the edge network within the one or more network data centers connects through one or more switching fabrics of the one or more network data centers; generating, by the CNC system and based on the service request, a network se dee definition that specifies one or more service requirements to implement the service; determining, by the CNC system and based on the network service definition, at least one network field unit that is capable of servicing the service request, wherein the network field unit controls a portion of the edge network, wherein the network service definition is usable by the at least one network field unit to configure the portion of the edge network to prov ide the service; and sending, by the CNC system and to the at least one network field unit, the network service definition to
  • Clause 2 The method of clause 1 , further comprising monitoring, by the CNC system, performance data for the service that is received from the at least one network field unit; comparing, by the CNC system, the performance data with at least one of the service requirements and service telemetry and analytics data stored by the CNC system to determine whether the sendee requirements are satisfied by performance of the portion of the edge network; responsive to determining that the service requirements for the sendee are not satisfied, determining, by the CNC system, at least one remedial action to satisfy the service requirements for the service; and executing, by the CNC system, the at least one remedial action.
  • Clause 4 The method of clause 1, wherein the one or more sendee requirements specify at least one of a type of service, a geographic location for the sendee, a bandwidth for the sendee, an indication whether the bandwidth is burstable, an Excess Information Rate (EIR), a maximum latency for the bandwidth, a minimum availability level of the service, a cloud service provider for the sendee, or one or more security properties for the se dee.
  • EIR Excess Information Rate
  • Clause 6 The method of clause 1 , further comprising responsive to configuring the at least one network sendee of service at the portion of the edge network, storing, by the CNC system, billing information that indicates a fee for provisioning the se ' ice to a requestor of the sendee: and sending, by the CNC system, an indication of the billing information to the requestor of the sendee.
  • Clause 7 The method of clause 1, wherein the one or more network data centers are geographically dispersed, and wherein a plurality of network field units are geographically dispersed, respectively, with the one or more geographically dispersed network data centers, each of the plurality of network field units controlling a respective portion of the edge network.
  • Clause 8 The method of clause 1, wherein the sen' ice requirements of the service definition do not specify particular, physical devices of the edge network, and wherein the network service definition is usable by the at least one network field unit to configure the particular, physical devices of the edge network.
  • a centralized network control (CNC) system comprising one or more computer processors; and a memory comprising instructions that when executed by the one or more computer processors cause the one or more computer processors to provide a software interface to receive senice requests for configuration of services within an edge network of one or more network data centers that are controlled by the CNC system; receive, via the software interface, a service request to configure a service within the edge network of the network data center, wherein the edge network within the one or more network data centers connects through one or more switching fabrics of the one or more network data centers; generate, based on the se dee request, a network service definition that specifies one or more service requirements to implement the service; determine, based on the network service definition, at least one network field unit that is capable of servicing the service request, wherein the network field unit controls a portion of the edge network, wherein the network service definition is usable by the at least one network field unit to configure the portion of the edge network to provide the service; and send, to the at least one network field unit, the network
  • Clause 14 The CNC system of clause 10, wherein the sendee comprises at least one of a layer-3 interconnection senice, a firewall sendee, a data storage senice, a software-as-a-service (SaaS) service, an analytics service, a network address translation service, or a deep-packet inspection sendee.
  • a layer-3 interconnection senice a firewall sendee
  • a data storage senice a software-as-a-service (SaaS) service
  • SaaS software-as-a-service
  • an analytics service e.g., a network address translation service
  • network address translation service e.
  • Clause 15 The CNC system of clause 10, wherein the memory comprises instructions that when executed by the one or more computer processors cause the one or more computer processors to responsive to configuring the at least one network service of service at the portion of the edge network, store billing information that indicates a fee for provisioning the service to a requestor of the service; and send an indication of the billing information to the requestor of the sen/ice,
  • Clause 18 The CNC system, of clause 10, wherein the service is a first service, wherein the memory comprises instructions that when executed by the one or more computer processors cause the one or more computer processors to configure the edge netw ork to aggregate first cloud service traffic originating from a first cloud service provider and second cloud sendee traffic originating from a second cloud sendee provider; and configure the edge network to deliver the aggregated cloud service traffic.
  • a non-transitory computer readable medium comprising instructions that, when executed, cause at least one programmable processor of a centralized network control (CNC) system to perform operations comprising providing a software interface to receive service requests for configuration of sendees within an edge network of one or more network data centers that are controlled by the CNC system; receiving, via the software interface, a sendee request to configure a sendee within the edge network of the network data center, wherein the edge network within the one or more network data centers connects through one or more switching fabrics of the one or more network data centers; generating, based on the service request, a network sendee definition that specifies one or more sendee requirements to implement the sendee; determining, based on the network service definition, at least one network field unit that is capable of servicing the service request, wherein the network field unit controls a portion of the edge network, wherein the network sendee definition is usable by the at least one network field unit to configure the portion of the edge network to provide the sendee; and
  • CNC centralized
  • Clause 20 The non-transitor - computer readable medium of clause 19 comprising instructions that, when executed, cause the at least one programmable processor to perform operations comprising monitoring performance data for the sendee that is received from the at least one network field unit; comparing the performance data with at least one of the service requirements and senice telemetry and analytics data stored by the CNC system to determine whether the senice requirements are satisfied by performance of the portion of the edge network; responsive to determining that the service requirements for the senice are not satisfied, determining at least one remedial action to satisfy the senice requirements for the senice; and executing the at least one remedial action.
  • a method comprising receiving, by at least one network field unit, a network service definition that specifies one or more senice requirements to implement a network service within a portion of an edge network of one or more network data centers, wherein the network senice definition is usable by the at least one network field unit to configure the portion of the edge network to provide the network service, wherein the portion of the edge network within one or more network data centers connect through one or more switching fabrics of the one or more network data centers; determining, by the network field unit and based on the network senice definition, one or more particular, physical devices of the edge network that are usable to provide the service; and configuring, by the network field unit, the one or more particular, physical devices of the edge network to provide the network senice.
  • configuring the one or more particular, physical devices of the edge network further comprises sending, by the network field unit, and to at least one of a Software-Defined Network (SDN) controller or a hardware configurator, one or more instructions that are usable by the least one of the SDN controller or the hardware configurator to configure the one or more particular, physical devices of the edge network to provide the network service.
  • SDN Software-Defined Network
  • Ciause S The method of clause 4, wherein executing the at least one remedial action comprises reconfiguring at least the portion of the edge network or a different portion of the edge network.
  • Clause 6 The method of clause 4, further comprising responsive to determining that the service requirements for the network service are not satisfied, sending, by the network field unit, in format ion that indicates that the service requirements for the network service are not satisfied to a CNC system.
  • Clause 7 The method of clause I, wherein configuring one or more particular, physical devices of the edge network to provide the network service further comprises configuring a plurality of provider edge routers included in the portion of the edge network to define one or more virtual private network routing and forwarding instances (VRFs) for the network service.
  • VRFs virtual private network routing and forwarding instances
  • a network field unit comprising one or more computer processors
  • a memory comprising instructions that when executed by the one or more computer processors cause the one or more computer processors to receive a network se dee definition that specifies one or more service requirements to implement a network sendee within a portion of an edge network of one or more network data centers, wherein the network service definition is usable by the at least one network field unit to configure the portion of the edge network to provide the network sen/ice, wherein the portion of the edge network within one or more network data centers connect through one or more switching fabrics of the one or more network data centers; determine, based on the network service definition, one or more particular, physical devices of the edge network that are usable to provide the service; and
  • Clause 9 The network field unit of clause 8, wherein the memory comprises instructions that when executed by the one or more computer processors cause the one or more computer processors to send, to at least one of a Software-Defined Network (SDN) controller or a hardware configurator, one or more instructions that are usable by the least one of the SDN controller or the hardware configurator to configure the one or more particular, physical devices of the edge network to provide the network service.
  • SDN Software-Defined Network
  • Clause 10 The network field unit of clause 8, wherein the one or more network data centers are geographically dispersed, and wherein a plurality of network field units that includes the network field unit are geographically dispersed, respectively, with the one or more geographically dispersed network data centers, each of the plurality ' of network field units controlling respective portion of the edge network.
  • Clause 11 The network field unit of clause 8, wherein the memory comprises instructions that when executed by the one or more computer processors cause the one or more computer processors to monitor performance data for the network service that is received from at least one of an SDN controller, a hardware configurator, or an infrastructure data collector; compare the performance data with at least one of performance conditions or network telemetry and analytics data stored by the CNC system to determine whether the service requirements for the network sendee are satisfied by performance of the portion of the edge network; responsive to determining that the service requirements for the network service are not satisfied, determine at least one remedial action to satisfy the service requirements for the network service; and execute the at least one remedial action.
  • Clause 13 The network field unit of clause 8, wherein the memory comprises instructions that when executed by the one or more computer processors cause the one or more computer processors to responsive to determining that the service requirements for the network service are not satisfied, send information that indicates that the service requirements for the network sen' ice are not satisfied to a CNC system,
  • a non-transitory computer readable medium comprising instructions that, when executed, cause at least one programmable processor of a network field unit to perform operations comprising receiving a network service definition that specifies one or more service requirements to implement a network service within a portion of an edge network of one or more network data centers, wherein the network service definition is usable by the at least one network field unit to configure the portion of the edge network to provide the network service, wherein the portion of the edge network within one or more network data centers connect through one or more switching fabrics of the one or more network data centers; determining, based on the network service definition, one or more particular, physical devices of the edge network that are usable to provide the service: and configuring the one or more particular, physical devices of the edge network to provide the network service.
  • Clause 16 The non-transitory computer readable medium of clause 15 comprising instructions that, when executed, cause the at least one programmable processor of the network field unit to perform operations comprising sending to at least one of a Software-Defined Network (SDN) controller or a hardware configurator, one or more instructions that are usable by the least one of the SDN controller or the hardware configurator to configure the one or more particular, physical devices of the edge network to provide the network service.
  • SDN Software-Defined Network
  • Clause 17 The non-transitory computer readable medium of clause 15, wherein the one or more network data centers are geographically dispersed, and wherein a plurality of network field units that includes the network field unit are geographically dispersed, respectively, with the one or more geographically dispersed network data centers, each of the plurality of network field units controlling respective portion of the edge network.
  • Clause 18 The non-transitory computer readable medium of clause 15 comprising instructions that, when executed, cause the at least one programmable processor of the network field unit to perform operations comprising monitoring performance data for the network service that is received from at least one of an SDN controller, a hardware configurator, or an infrastructure data collector; comparing the performance data with at least one of performance conditions or network telemetry and analytics data stored by the CMC system to determine whether the service requirements for the network service are satisfied by performance of the portion of the edge network; responsive to determining that the sendee requirements for the network sendee are not satisfied, determining at least one remedial action to satisfy the service requirements for the network service; and executing the at least one remedial action,
  • Clause 2.0 The non-transitory computer readable medium of clause 15 comprising instructions that, when executed, cause the at least one programmable processor of the network field unit to perform operations comprising responsive to determining that the sendee requirements for the network sendee are not satisfied, sending information that indicates that the sendee requirements for the network sendee are not satisfied to a CNC system.
  • a method comprising providing, by a programmable network platform (PNP), a software interface to receive service requests for configuration of services within an edge network of one or more network data centers that are controlled by the PNP; receiving, by the PNP and via the software interface, a service request to configure a network service within the edge network of the one or more network data centers, wherein the edge network within the one or more network data centers connect through one or more switching fabrics of the one or more network data centers; generating, by the PNP and based on the sendee request, a network service definition that specifies one or more sendee requirements to implement the network service; determining, by the PNP and based on the network service definition, at least one network field unit that is capable of sen/icing the se dee request, wherein the network field unit controls a portion of the edge network, wherein the network service definition is usable by the at least one network field unit to configure the portion of edge network to provide the service: determining, by the at least one network field unit and based on
  • Clause 2 The method of clause 1 , further comprising monitoring, by the PNP, performance data for the sen/ice that is received from the at least one network field unit; comparing, by the PNP, the performance data with at least one of the service requirements of the service and service telemetr ⁇ ' and analytics data stored by the PNP to determine whether the service requirements for the service are satisfied by performance of the portion of the edge network; responsive to determining that the sen/ice requirements for the service are not satisfied, determining, by the PNP, at least one remedial action to satisfy the service requirements for the service; and executing, by the PNP, the at least one remedial action.
  • Clause 4 The method of clause 1, wherein the one or more se dee requirements specify at least one of a type of sendee, a geographic location for the service, a bandwidth for the sendee, whether the bandwidth is burstable, an Excess Information Rate (EIR), a maximum latency for the bandwidth, an minimum availability level of the service, a cloud service provider for the sendee, or one or more security properties for the sendee.
  • EIR Excess Information Rate
  • Clause 5 The method of clause I , wherein the sendee comprises at least one of a layer 3 interconnection service, a firewall sendee, a data storage sendee, a software- as-a-service (SaaS) service, an analytics service, network address translation sendee, or a deep-packet inspection sendee.
  • a layer 3 interconnection service e.g., a Layer 3 interconnection service, a firewall sendee, a data storage sendee, a software- as-a-service (SaaS) service, an analytics service, network address translation sendee, or a deep-packet inspection sendee.
  • SaaS software- as-a-service
  • Clause 6 The method of clause 1, further comprising responsive to the at least one network field unit configuring the service at the portion of the edge network, storing, by the PNP, billing information that indicates a fee for provisioning the service to a requestor of the service: and sending, by the PNP, an indication of the billing information to the requestor of the service,
  • Clause 7 The method of clause 1, wherein the one or more network data centers are geographically dispersed, and wherein a plurality of network field units are geographically dispersed, respectively, with the one or more geographically dispersed network data centers, each of the plurality of network field units controlling respective interconnection assets of one of the plurality of network data centers.
  • Clause 8 The method of clause 7, wherein the service request does not specify particular, physical dev ices of the interconnection assets, and wherein the network service definition is usable by the at least one network field unit to configure the particular, physical devices of the interconnection assets.
  • configuring the one or more particular, physical devices of the edge network further comprises sending, by the network field unit, and to at least one of a Software-Defined Network (SDN) controller or a hardware configurator, one or more instructions that are usable by the least one of the SDN controller or the hardware configurator to configure the one or more particular, physical devices of the edge network to provide the service.
  • SDN Software-Defined Network
  • Clause 11 The method of clause 1, wherein the one or more network data centers are geographically dispersed, and wherein a plurality of network field units that includes the network field unit are geographically dispersed, respectively, with the one or more geographically dispersed network data centers, each of the plurality of network field units controlling respective interconnection assets of one of the plurality of network data centers.
  • a programmable network platform comprising one or more computer processors; and a memory comprising instructions that when executed by the one or more computer processors cause the one or more computer processors to provide a software interface to receive sen/ice requests for configuration of services within an edge network of one or more network data centers that are controlled by the PNP; receive a service request to configure a network service within the edge network of the one or more network data centers, wherein the edge network within the one or more network data centers connect through one or more switching fabrics of the one or more network data centers; generate a network service definition that specifies one or more service requirements to implement the network service; determine, by the PNP and based on the network service definition, at least one network field unit that is capable of servicing the sen-ice request, wherein the network field unit controls a portion of the edge network, wherem the network service definition is usable by the at least one network field umt to configure the portion of edge network to provide the sendee: determine, based on the network sendee definition, one or more particular, physical devices
  • Clause 14 The PNP of clause 13, wherein the memory comprises instructions that when executed by the one or more computer processors cause the one or more computer processors to monitor performance data for the sendee that is received from, the at least one network field unit; compare the performance data with at least one of the service requirements of the sendee and sendee telemetry and analytics data stored by the PNP to determine whether the service requirements for the sendee are satisfied by performance of the portion of the edge network; responsive to determining that the sendee requirements for the service are not satisfied, determine at least one remedial action to satisfy the sendee requirements for the sendee; and execute the at least one remedial action.
  • Clause 16 The PNP of clause 13, wherein the one or more service requirements specify at least one of a type of service, a geographic location for the service, a bandwidth for the service, whether the bandwidth is burstable, an Excess Information Rate (E1R), a maximum latency for the bandwidth, an minimum availability level of the service, a cloud service provider for the service, or one or more security properties for the sen/ice.
  • E1R Excess Information Rate
  • Clause 17 The PNP of clause 13, wherein the service comprises at least one of a layer 3 interconnection service, a firewall service, a data storage service, a software- as-a-service (SaaS) service, an analytics service, network address translation service, or a deep-packet inspection service.
  • a layer 3 interconnection service e.g., a firewall service, a data storage service, a software- as-a-service (SaaS) service, an analytics service, network address translation service, or a deep-packet inspection service.
  • SaaS software- as-a-service
  • Clause 18 The PNP of clause 13, wherein the memory comprises instructions that when executed by the one or more computer processors cause the one or more computer processors to responsive to the at least one network field unit configuring the sen- ice at the portion of the edge network, store billing information that indicates a fee for provisioning the service to a requestor of the service: and send an indication of the billing information to the requestor of the service.
  • Clause 19 The PNP of clause 13, wherein the one or more network data centers are geographically dispersed, and wherein a plurality of network field units are geographically dispersed, respectively, with the one or more geographically dispersed network data centers, each of the plurality of network field units controlling respective interconnection assets of one of the plurality of network data centers.
  • Clause 20 The PNP of clause 13, wherein the service request does not specify particular, physical devices of the interconnection assets, and wherein the network service definition is usable by the at least one network field unit to configure the particular, physical devices of the interconnection assets.
  • Clause 2A At least one computing device configured to perform the method of clause 1 A.
  • this disclosure may be directed to an apparatus such as a processor or an integrated circuit device, such as an integrated circuit chip or chipset.
  • an apparatus such as a processor or an integrated circuit device, such as an integrated circuit chip or chipset.
  • the techniques may be realized at least in part by a computer-readable data storage medium comprising instructions that, when executed, cause a processor to perform one or more of the methods described above.
  • the computer-readable data storage medium may- store such instructions for execution by a processor.
  • a computer-readable medium may form part of a computer program product, which may include packaging materials.
  • a computer-readable medium may comprise a computer data storage medium such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), Flash memory, magnetic or optical data storage media, and the like.
  • RAM random access memory
  • ROM read-only memory
  • NVRAM non-volatile random access memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory magnetic or optical data storage media, and the like.
  • an article of manufacture may comprise one or more computer-readable storage media.
  • the computer-readable storage media may comprise non- transitory media.
  • the term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal.
  • a non-transitory storage medium may store data that can, over time, change (e.g., in RAM or cache).
  • the code or instructions may be software and/or firmware executed by processing circuitry including one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other equivalent integrated or discrete logic circuitry.
  • DSPs digital signal processors
  • ASICs application-specific integrated circuits
  • FPGAs field-programmable gate arrays
  • the term "processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein.
  • functionality described in this disclosure may be provided within software modules or hardware modules.

Abstract

Selon certains exemples, l'invention concerne un centre de données en réseau qui comprend un point d'échange de services en nuage comprenant un réseau, le point d'échange de services en nuage étant exploité par un fournisseur d'échange en nuage qui exploite le centre de données en réseau ; et une plateforme de réseau programmable comprenant au moins un processeur programmable pour recevoir une requête de service qui spécifie une pluralité de services en nuage fournis par des réseaux de fournisseur de service en nuage respectifs exploités par des fournisseurs de service en nuage respectifs, la requête de service spécifiant en outre une topologie pour la pluralité de services en nuage ; et provisionner, en réponse à la requête de service, le point d'échange de services en nuage pour acheminer du trafic de service pour la pluralité de services en nuage conformément à la topologie pour la pluralité de services en nuage.
PCT/US2016/031943 2015-05-12 2016-05-11 Plateforme de réseau programmable pour échange de services en nuage WO2016183253A1 (fr)

Priority Applications (9)

Application Number Priority Date Filing Date Title
JP2016573993A JP6495949B2 (ja) 2015-05-12 2016-05-11 クラウドベースのサービス交換用のプログラム可能なネットワークプラットフォーム
CN201680001701.4A CN106464742B (zh) 2015-05-12 2016-05-11 用于基于云的服务交换的可编程网络平台
AU2016262538A AU2016262538B2 (en) 2015-05-12 2016-05-11 Programmable network platform for a cloud-based services exchange
BR112016029203A BR112016029203A2 (pt) 2015-05-12 2016-05-11 plataforma de rede programável para troca de serviços com base em nuvem
EP16725682.5A EP3155759B1 (fr) 2015-05-12 2016-05-11 Plateforme de réseau programmable pour échange de services en nuage
CA2951944A CA2951944C (fr) 2015-05-12 2016-05-11 Plateforme de reseau programmable pour echange de services en nuage
SG11201610055VA SG11201610055VA (en) 2015-05-12 2016-05-11 Programmable network platform for a cloud-based services exchange
EP19193146.8A EP3588861B1 (fr) 2015-05-12 2016-05-11 Platforme de réseau programmable pour les échanges des services basées sur un réseau cloud
EP23175205.6A EP4236252A3 (fr) 2015-05-12 2016-05-11 Platforme de réseau programmable pour les échanges des services basées sur un réseau cloud

Applications Claiming Priority (14)

Application Number Priority Date Filing Date Title
US201562160547P 2015-05-12 2015-05-12
US62/160,547 2015-05-12
US15/001,839 US9967350B2 (en) 2015-05-12 2016-01-20 Third-party orchestration module for a cloud exchange programmable network platform
US15/001,919 US10237355B2 (en) 2015-05-12 2016-01-20 Software-controlled cloud exchange
US15/001,766 US10015268B2 (en) 2015-05-12 2016-01-20 Multi-cloud, multi-service data model
US15/001,875 US10291726B2 (en) 2015-05-12 2016-01-20 Network field unit for a cloud-based services exchange
US15/001,862 US10250699B2 (en) 2015-05-12 2016-01-20 Centralized network control for a cloud-based services exchange
US15/001,875 2016-01-20
US15/001,862 2016-01-20
US15/001,919 2016-01-20
US15/001,822 US10021197B2 (en) 2015-05-12 2016-01-20 Multiple cloud services delivery by a cloud exchange
US15/001,822 2016-01-20
US15/001,839 2016-01-20
US15/001,766 2016-01-20

Publications (1)

Publication Number Publication Date
WO2016183253A1 true WO2016183253A1 (fr) 2016-11-17

Family

ID=56084389

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/031943 WO2016183253A1 (fr) 2015-05-12 2016-05-11 Plateforme de réseau programmable pour échange de services en nuage

Country Status (1)

Country Link
WO (1) WO2016183253A1 (fr)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106656630A (zh) * 2017-01-13 2017-05-10 北京中电普华信息技术有限公司 一种电力营销业务应用系统及其构建方法、平台
WO2018232022A1 (fr) * 2017-06-13 2018-12-20 Equinix, Inc. Échange d'appairage de service
WO2019074952A3 (fr) * 2017-10-10 2019-05-23 Google Llc Profilage de jeu basé sur un échantillon distribué avec métadonnées de jeu et mesures, et plateforme d'api de jeu prenant en charge un contenu tiers
WO2020026756A1 (fr) * 2018-08-02 2020-02-06 日本電信電話株式会社 Dispositif d'aide à la création de catalogue, procédé d'affichage d'écran d'aide et procédé d'aide à la création de catalogue
US10827006B2 (en) 2018-05-22 2020-11-03 At&T Intellectual Property I, L.P. Policy-driven homing service system
US10898812B2 (en) 2018-04-02 2021-01-26 Google Llc Methods, devices, and systems for interactive cloud gaming
US10944783B2 (en) 2018-07-12 2021-03-09 At&T Intellectual Property I, L.P. Dynamic denial of service mitigation system
US11077364B2 (en) 2018-04-02 2021-08-03 Google Llc Resolution-based scaling of real-time interactive graphics
US11110348B2 (en) 2018-04-10 2021-09-07 Google Llc Memory management in gaming rendering
US11140207B2 (en) 2017-12-21 2021-10-05 Google Llc Network impairment simulation framework for verification of real time interactive media streaming systems
US11305186B2 (en) 2016-05-19 2022-04-19 Google Llc Methods and systems for facilitating participation in a game session
CN114567546A (zh) * 2022-03-02 2022-05-31 杭州吉网通信技术有限公司 一种idc自动业务开通系统及使用方法
US11369873B2 (en) 2018-03-22 2022-06-28 Google Llc Methods and systems for rendering and encoding content for online interactive gaming sessions
US11662051B2 (en) 2018-11-16 2023-05-30 Google Llc Shadow tracking of real-time interactive simulations for complex system analysis
US11768697B2 (en) 2020-03-23 2023-09-26 Fujitsu Limited Storage medium and container moving method
US11872476B2 (en) 2018-04-02 2024-01-16 Google Llc Input device for an electronic system
CN114567546B (zh) * 2022-03-02 2024-05-14 杭州吉网通信技术有限公司 一种idc自动业务开通系统及使用方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120147894A1 (en) * 2010-12-08 2012-06-14 Mulligan John T Methods and apparatus to provision cloud computing network elements
US20140122683A1 (en) * 2012-10-30 2014-05-01 Futurewei Technologies, Inc. System and Method for Virtual Network Abstraction and Switching
WO2014147197A1 (fr) * 2013-03-20 2014-09-25 Wolting Holding B.V. Compilateur et procédé pour des réseaux définis par le logiciel
US20150067171A1 (en) * 2013-08-30 2015-03-05 Verizon Patent And Licensing Inc. Cloud service brokering systems and methods

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120147894A1 (en) * 2010-12-08 2012-06-14 Mulligan John T Methods and apparatus to provision cloud computing network elements
US20140122683A1 (en) * 2012-10-30 2014-05-01 Futurewei Technologies, Inc. System and Method for Virtual Network Abstraction and Switching
WO2014147197A1 (fr) * 2013-03-20 2014-09-25 Wolting Holding B.V. Compilateur et procédé pour des réseaux définis par le logiciel
US20150067171A1 (en) * 2013-08-30 2015-03-05 Verizon Patent And Licensing Inc. Cloud service brokering systems and methods

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11305186B2 (en) 2016-05-19 2022-04-19 Google Llc Methods and systems for facilitating participation in a game session
CN106656630A (zh) * 2017-01-13 2017-05-10 北京中电普华信息技术有限公司 一种电力营销业务应用系统及其构建方法、平台
WO2018232022A1 (fr) * 2017-06-13 2018-12-20 Equinix, Inc. Échange d'appairage de service
US11758007B2 (en) 2017-06-13 2023-09-12 Equinix, Inc. Service peering exchange
EP4113955A1 (fr) * 2017-06-13 2023-01-04 Equinix, Inc. Systeme d'échange de service
US11044326B2 (en) 2017-06-13 2021-06-22 Equinix, Inc. Service peering exchange
WO2019074952A3 (fr) * 2017-10-10 2019-05-23 Google Llc Profilage de jeu basé sur un échantillon distribué avec métadonnées de jeu et mesures, et plateforme d'api de jeu prenant en charge un contenu tiers
US11684849B2 (en) 2017-10-10 2023-06-27 Google Llc Distributed sample-based game profiling with game metadata and metrics and gaming API platform supporting third-party content
US11140207B2 (en) 2017-12-21 2021-10-05 Google Llc Network impairment simulation framework for verification of real time interactive media streaming systems
US11369873B2 (en) 2018-03-22 2022-06-28 Google Llc Methods and systems for rendering and encoding content for online interactive gaming sessions
US10898812B2 (en) 2018-04-02 2021-01-26 Google Llc Methods, devices, and systems for interactive cloud gaming
US11077364B2 (en) 2018-04-02 2021-08-03 Google Llc Resolution-based scaling of real-time interactive graphics
US11872476B2 (en) 2018-04-02 2024-01-16 Google Llc Input device for an electronic system
US11110348B2 (en) 2018-04-10 2021-09-07 Google Llc Memory management in gaming rendering
US10827006B2 (en) 2018-05-22 2020-11-03 At&T Intellectual Property I, L.P. Policy-driven homing service system
US10944783B2 (en) 2018-07-12 2021-03-09 At&T Intellectual Property I, L.P. Dynamic denial of service mitigation system
JP2020022108A (ja) * 2018-08-02 2020-02-06 日本電信電話株式会社 カタログ作成支援装置、支援画面表示方法およびカタログ作成支援方法
WO2020026756A1 (fr) * 2018-08-02 2020-02-06 日本電信電話株式会社 Dispositif d'aide à la création de catalogue, procédé d'affichage d'écran d'aide et procédé d'aide à la création de catalogue
US11662051B2 (en) 2018-11-16 2023-05-30 Google Llc Shadow tracking of real-time interactive simulations for complex system analysis
US11768697B2 (en) 2020-03-23 2023-09-26 Fujitsu Limited Storage medium and container moving method
CN114567546A (zh) * 2022-03-02 2022-05-31 杭州吉网通信技术有限公司 一种idc自动业务开通系统及使用方法
CN114567546B (zh) * 2022-03-02 2024-05-14 杭州吉网通信技术有限公司 一种idc自动业务开通系统及使用方法

Similar Documents

Publication Publication Date Title
EP3155759B1 (fr) Plateforme de réseau programmable pour échange de services en nuage
WO2016183253A1 (fr) Plateforme de réseau programmable pour échange de services en nuage
US11228641B1 (en) Inter-metro connectivity network connect
US11552889B1 (en) Layer three instances for a cloud-based services exchange
US10129078B2 (en) Orchestration engine for real-time configuration and management of interconnections within a cloud-based services exchange
US9983860B1 (en) Continuous application delivery monitoring
US20210359948A1 (en) Virtual gateways in a cloud exchange
US10523631B1 (en) Communities of interest in a cloud exchange
US10439888B2 (en) Interconnect engine for interconnection facilities
US10878483B1 (en) Method, system, and medium for asset-based permissions management for resellers of cloud exchange assets

Legal Events

Date Code Title Description
REEP Request for entry into the european phase

Ref document number: 2016725682

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2016725682

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2951944

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2016573993

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2016262538

Country of ref document: AU

Date of ref document: 20160511

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16725682

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112016029203

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112016029203

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20161213

WWE Wipo information: entry into national phase

Ref document number: 11201610055V

Country of ref document: SG

NENP Non-entry into the national phase

Ref country code: DE