Software defined networking (sdn) controller orchestration and network virtualization for data center interconnection

Abstract

A data center interconnection (DCI) network may comprise a data center controller (DCC) managing a plurality of data centers (DCs) interconnected by a provider network managed by a network provider controller (NPC). The provider network may be an OpenFlow based software defined networking (SDN) transport network. The DCC may initiate a virtual network service (VNS) negotiation with the NPC to connect the DCs and may specify a network abstraction granularity level. The NPC may respond by computing paths through the provider network accordingly and providing the DCC with one or more virtual networks (VNs). The DCC may compute virtual paths through the VNs and send virtual network element (VNE) connection setup commands to the DCC. The DCC may convert the VNE connection setup commands into network element (NE) commands to setup connections in NEs of the provider network. The DCC and the NPC may perform fault monitoring, detection, and recovery.

1 . A method by a network provider controller, comprising:
 receiving, from a client controller, a set of endpoints managed by the client controller that are to be connected and traffic characteristics that need to be supported between the set of endpoints;   establishing a virtual network (VN) in response to the client controller;   allocating network resources for the VN; and   notifying the client controller of availability of the VN between the endpoints.   
     
     
         2 . The method of  claim 1 , wherein the traffic characteristics comprise one or more of bandwidth and Quality of Service (QoS). 
     
     
         3 . The method of  claim 1  further comprising:
 receiving virtual network element (VNE) connection setup commands for a path through the VN from the client controller; and 
 converting one of the VNE connection setup commands into a command to configure a network element (NE) represented by a VNE in the path. 
 
     
     
         4 . The method of  claim 1  further comprising:
 receiving virtual network element (VNE) connection setup commands for a path through the VN from the DCC, wherein a VNE in the path represents a sub-network in a provider network; 
 triggering a path computation on the VNE; and 
 configuring each network element (NE) within the computed path of the sub-network in the provider network. 
 
     
     
         5 . The method of  claim 1  further comprising exchanging fault monitoring information with the client controller, wherein the fault monitoring information comprises a VN resources failing, a VN resources partial failing, a VN resources degrading, or faults in virtual network connections. 
     
     
         6 . The method of  claim 1 , wherein the client controller is a data center (DC) controller, the end points are endpoints in one or more DCs associated with the DC controller. 
     
     
         7 . A network provider controller, comprising:
 a transceiver;   a memory storing instructions for execution by one or more processors,:   one or more processors coupled to the transceiver that execute computer instructions stored in the memory to cause the network provider controller to:   receive, from the client controller, a set of endpoints that are managed by the client controller that are to be connected and traffic characteristics that need to be supported between the set of endpoints;   provide a virtual network (VN) in response to the client controller;   allocate network resources to fulfil the VN; and   send one or more messages to notify the client controller of availability of the VN for transport of information between the endpoints.   
     
     
         8 . The network provider controller of  claim 7 , wherein the VN is computed according to a granularity of the VN, the VN is expressed of virtual network elements and virtual links. 
     
     
         9 . The network provider controller of  claim 7 , wherein the network provider controller is further configured to:
 receive virtual network element (VNE) connection setup commands for a path through the VN from the client controller; and   convert one of the commands into a command to configure a network element (NE) represented by a VNE in the path.   
     
     
         10 . The network provider controller of  claim 7 , wherein:
 the network provider controller is further configured to: receive a VN connection delete request message from the client controller; and   to convert the VN connection delete request message into connection delete commands for network nodes along a connection path in the VN.   
     
     
         11 . A client controller, comprising:
 at least one processor; and   a memory coupled to the at least one processor and storing instructions for execution by the at least one processor to cause the client controller to:
 compute a virtual path through a virtual network (VN), wherein the VN is provided by a network provider controller; and 
 send virtual network element (VNE) connection setup commands for VNEs in the computed virtual path to the network provider controller. 
   
     
     
         12 . The client controller of  claim 11 , wherein the processor is further configured to execute the instructions to cause the network provider controller to:
 initiate a virtual network service (VNS) negotiation with the network provider controller by sending a VNS negotiation initiation message to the network provider controller, wherein the a VNS negotiation initiation message comprises a set of endpoints associated with the VN, the endpoints are managed by the client controller.   
     
     
         13 . The client controller of  claim 12 , wherein the VNS request further comprises a traffic matrix element comprising traffic characteristics between the endpoints. 
     
     
         14 . The client controller of  claim 13 , wherein the traffic matrix element comprises a connectivity type parameter and wherein the connectivity type parameter comprises a point-to-point (P2P) connection, a point-to-multipoint (P2MP) connection, a multipoint-to-multipoint (M2MP) connection, a rooted multipoint, or combinations thereof. 
     
     
         15 . The client controller of  claim 11 , wherein the processor is further configured to execute the instructions to cause the network provider controller to:
 sent, to the network provider controller, a fault message that indicates a detected fault in a remote data center associated with the client controller, the client controller being a data center controller.