MD-SAL-based SDN controller middleware control method and system

Abstract

The invention discloses an MD-SAL-based SDN controller middleware control method and system. The method includes that registering the northbound API interface information of the middleware and the driving information of N controller manufacturers to MD-SAL to generate a driving association table; connecting with an application layer according to the northbound API interface information of the middleware and receiving the operation command sent by the application layer, wherein the operation command includes a first identifier of an SDN controller to be operated; determining whether the first identifier matches the driving information in the driving association table according to the first identifier; if yes, converting the operation command into the first API information applicable to the SDN controller to be operated, and forwarding the SDN controller to be operated to perform the corresponding operation for the SDN controller to be operated. According to the invention, the factory locking of the SDN controller due to the northbound API interface can be prevented, and the expansibility of the SDN controller is improved.

Description

technical field [0001] The invention relates to the field of communication technology, in particular to an MD-SAL-based SDN controller middleware control method and system. Background technique [0002] Software Defined Network (Software Defined Network, referred to as SDN) is a new network innovation architecture of Emulex network, and it is a way to realize network virtualization. Its core technology, OpenFlow, separates the control plane and data plane of network equipment to realize Flexible control of network traffic, making the network more intelligent as a pipeline. At present, there are more than 20 kinds of SDN controllers (including commercial and open source) on the market. There is no uniform standard for their northbound interfaces. Each controller has its own northbound API interface. Once the top-level APP depends on a certain One SDN controller northbound API interface will cause vendor lock-in, making it impossible to freely replace different SDN controller...

AI Technical Summary

Problems solved by technology

At present, there are more than 20 kinds of SDN controllers (including commercial and open source) on the market. There is no uniform standard for their northbound interfaces. Each controller has its own northbound API interface. Once the top-level APP depends on a certain A northbound API interface of an SDN controller will cause vendor lock-in, making it impossible to freely replace different SDN controllers

For example, when the original ODL controller is replaced with a Floodlight controller, the code of the upper-layer APP can only be used by modifying the code, which has low scalability and high development costs.

Images