WO2018018568A1

WO2018018568A1 - Multi-controller cooperation method and device

Info

Publication number: WO2018018568A1
Application number: PCT/CN2016/092177
Authority: WO
Inventors: 乔晓强; 李岩
Original assignee: 华为技术有限公司
Priority date: 2016-07-29
Filing date: 2016-07-29
Publication date: 2018-02-01

Abstract

Provided are a multi-controller cooperation method and device for solving a bottleneck of controllers due to centralized deployment of network functions and realizing multi-controller cooperative control of a switch. The method comprises: a primary controller sending a binding trigger message to each secondary controller of at least one secondary controller; the primary controller receiving a binding success message fed back by each secondary controller; and when it is determined, according to the received binding success message, that each of service function units forming a service process is bound, the primary controller sending a service process startup message to at least one secondary controller and a switch, respectively. According to the invention, after each secondary controller is bound with a service function unit, each secondary controller manages and controls the bound service function unit, thereby preventing the bottleneck of controllers due to centralized deployment of network functions.

Description

Multi-controller cooperation method and device

Technical field

The present invention relates to the field of network technologies, and in particular, to a multi-controller cooperation method and apparatus.

Background technique

In the current network, there are many complex network devices, such as routers, gateways, switches, firewalls, and various types of servers. These devices support a variety of different standard protocols, each with its own independent control module, so this distributed control mode leads to complex network deployment management. In order to implement an upgrade or parameter modification of a control function, the network operator may need to operate each device individually.

In order to realize the deployment flexibility and manageability of network elements, the industry has proposed the concept of Software Defined Networking (SDN). The SDN decouples the control logic and forwarding functions of the network element into control plane devices and forwarding plane devices to implement centralized deployment of control logic. The control and maintenance of the network can be easily implemented through centralized deployment of control plane devices. Improve the management efficiency of the network, and at the same time make the forwarding device simpler and more general, which is beneficial to the high performance and reusability of the forwarding device. At present, the idea of SDN is being widely applied to data center networks and telecommunication networks.

Specifically, as shown in FIG. 1 , a network device (Network Device), also referred to as a switch, is a forwarding plane device, and is used to perform packet transmission on the forwarding plane. A network controller (Network Controller), also known as a controller, is a control plane device that is used to configure and manage switches through a control channel. The application is used to implement various network functions, including routing control, tunnel encapsulation, firewall, secure access, and QoS control.

In the prior art, the functions to be implemented by the switch are configured through the network application on the controller. If the switch needs to implement complex network functions, such as routing control, tunnel encapsulation, firewall, secure access, and QoS control, then A variety of web applications need to be installed on the controller. The centralized deployment of such network functions will bring great operational overhead to the controller, which is easy to cause control. On the other hand, when the network needs to be expanded or expanded, the cumulative stacking method can only be adopted. The network application on the controller will become larger and larger, which may cause operational stability and reliability problems. .

Summary of the invention

The embodiments of the present invention provide a multi-controller cooperation method and device, which are used to solve a bottleneck problem caused by centralized deployment of network functions of a controller, and implement a multi-controller cooperative control switch.

In a first aspect, a multi-controller collaboration method includes:

The master controller sends a binding trigger message to each of the at least one secondary controller, where the binding trigger message sent by the ith secondary controller is used to trigger the ith secondary controller and the component The business function unit in each business function unit of the business process establishes a binding relationship, wherein each business function unit constituting the business process is deployed by the main controller as a switch;

The master controller receives a binding success message fed back by each secondary controller, where the binding success message is used to notify the primary controller that the secondary controller is successfully bound to the at least one service function unit;

The main controller sends a service flow start message to the at least one secondary controller and the switch separately when the primary service function unit that is configured to be the service flow is bound according to the received binding success message.

In a possible implementation manner, each service function unit refers to a flow table group or a logical switch, and each service function unit corresponds to one service function.

Therefore, embodiments of the present invention support multiple partitioning methods for business processes.

In a possible implementation manner, the binding trigger message sent by the i-th secondary controller carries the identifier of the service flow and description information of each service function unit that constitutes the service flow.

Therefore, the embodiment of the present invention supports each secondary controller to independently select a service function unit that needs to be bound.

In a possible implementation manner, the binding trigger message sent by the i-th secondary controller Carrying the identifier of the service process, the description information of each service function unit constituting the service process, and the service function name corresponding to the service function unit bound to the i-th secondary controller;

Or the binding trigger message sent by the ith secondary controller carries the identifier of the service flow and the description information of the service function unit to be bound by the ith secondary controller.

Therefore, the embodiment of the present invention supports the main controller to specify the bound service function unit for each secondary controller, which effectively avoids the occurrence of binding conflicts.

In a possible implementation manner, the description information of each service function unit includes a service function name corresponding to the service function unit, a forwarding plane identifier corresponding to the service function unit, the forwarding plane type, and a corresponding corresponding to the service function unit. Each of the jumpable service function unit information, wherein each of the jumpable service function unit information includes a service function name of the jumpable service function unit and a jump instruction corresponding to the jumpable service function unit;

When each service function unit refers to a flow table group, the forwarding plane identifier corresponding to the service function unit is an identifier of the switch, and the forwarding plane type indicates that the switch is a switch supporting a flow table group;

When each service function unit refers to a logical switch, the forwarding plane corresponding to the service function unit is identified as an identifier of the corresponding logical switch, and the forwarding plane type indicates that the switch is a switch that does not support the flow table group.

Therefore, the secondary controller that binds the service function unit in the embodiment of the present invention can obtain detailed information of the binding service function unit, so as to implement effective control and management of the bound service function unit.

In a possible implementation, after the main controller sends the service flow start message to the at least one secondary controller and the switch, the method further includes: the primary controller to the at least one secondary control And the switch respectively send a service flow suspension message;

Adding, by the main controller, at least one service function unit to the service flow;

The primary controller sends a new service function unit notification message to at least one of the at least one secondary controller, where the new service function unit notification message is used to indicate the at least one secondary controller Establishing a binding relationship between the at least one secondary controller and the corresponding newly added service function unit;

The primary controller receives a binding success message sent by at least one secondary controller of the at least one secondary controller;

The primary controller separately sends a service flow recovery message to the at least one secondary controller and the switch.

Therefore, the embodiment of the present invention can implement the newly added service function unit and notify the secondary controller of the information of the newly added service function unit, so as to implement the binding of the newly added service function unit, and the management of the business process is more flexible.

In a possible implementation, before the main controller sends the service flow suspension message to the at least one secondary controller and the switch, the method further includes:

Receiving, by the primary controller, a new service function unit request message sent by the first secondary controller, where the newly added service function unit request message carries the identifier of the service process, and the service function of the newly added service function unit The name and the new service function unit include indication information of the flow table.

Therefore, the embodiment of the present invention can implement a service function unit that is newly requested by the secondary controller, so that the management of the service process is more flexible.

The main controller sends a service function unit unbinding notification message to the second secondary controller, where the service function unit unbinding notification message is used to indicate the second secondary controller and the service function unit that needs to be unbound. Unbinding the relationship, wherein the second secondary controller is any one of the at least one secondary controller;

The main controller receives an unbinding success message sent by the second secondary controller.

Therefore, the embodiment of the present invention can implement the unbinding service function unit, and the management of the service process is more flexible.

Receiving, by the main controller, a service function unit unbinding request sent by the second secondary controller The message that the service function unit unbind request message carries the service function name of the service function unit that needs to be unbound and the identifier of the service process.

Therefore, the embodiment of the present invention can implement the request of the secondary controller to cancel the binding service function unit, so that the management of the service flow is more flexible.

In a possible implementation, after the main controller receives the unbinding success message sent by the second secondary controller, the method further includes:

The main controller sends a service function unit designation message to the third secondary controller, where the service function unit designation message carries the description information of the service function unit that needs to be unbound and the identifier of the service process, where the service The function unit designation message is used to indicate that the third secondary controller establishes a binding relationship with the service function unit that needs to be unbound, and the third secondary controller is any one of the at least one secondary controller. The main controller receives the binding success message sent by the third secondary controller; or the primary controller deletes the service function unit that needs to be unbound in the service process;

Therefore, after the binding of the service function unit is cancelled in the embodiment of the present invention, the main controller may be assigned to other secondary controllers to be bound, or the service function unit may be deleted, so that the business process management is more flexible and comprehensive.

When the main controller determines that each service function unit constituting the service process has been unbound, the service process is deleted.

Therefore, after the binding of the service function unit is cancelled in the embodiment of the present invention, the main controller can delete the business process when the service function units that constitute the business process are unbound, so that the business process management is more flexible and comprehensive.

In a second aspect, a multi-controller cooperation method is characterized by comprising:

The first secondary controller receives the binding trigger message sent by the primary controller, where the binding trigger message is used to trigger the service in the first secondary controller and each service functional unit constituting the service flow. The functional unit establishes a binding relationship, where each service functional unit constituting the business process is deployed by the primary controller for the switch;

Establishing a binding relationship between the first secondary controller and the at least one service function unit;

The first secondary controller sends a binding success message to the primary controller, where the binding success message is used to notify the primary controller that the first secondary controller is bound to the at least one service functional unit. success;

The first secondary controller receives a service flow initiation message sent by the primary controller.

In a possible implementation manner, the binding trigger message carries an identifier of the service process and description information of each service function unit that constitutes the service process;

Before the first secondary controller establishes a binding relationship with the at least one service function unit, the method further includes:

The first secondary controller determines, according to the description information of each service function unit that constitutes the service flow, at least one service function unit as a service function unit to be bound.

In a possible implementation manner, the binding trigger message carries an identifier of the service process, description information of each service function unit that constitutes the service process, and a service that the first secondary controller needs to bind. The name of the business function corresponding to the functional unit;

The first secondary controller establishes a binding relationship with the at least one service function unit, including:

Determining, by the first secondary controller, a service function unit to be bound according to a service function name corresponding to the service function unit to be bound by the first secondary controller that is carried in the binding trigger message, where the first auxiliary The controller establishes a binding relationship with the service function unit to be bound.

Or the binding trigger message sent by the ith secondary controller carries the identifier of the service flow and the description information of the service function unit to be bound by the ith secondary controller;

Determining, by the first secondary controller, the service function unit to be bound according to the description information of the service function unit to be bound by the first secondary controller that is carried in the binding trigger message, the first auxiliary control The controller establishes a binding relationship with the service function unit to be bound.

In a possible implementation, after the first secondary controller receives the service flow start message sent by the primary controller, the method further includes:

Receiving, by the first secondary controller, a service flow suspension message sent by the primary controller;

The first secondary controller receives the new service function unit notification message sent by the primary controller, and the newly added service function unit notification message is used to indicate that the first secondary controller and the newly added service function unit are established. Binding relationship

Establishing a binding relationship between the first secondary controller and the newly added service function unit;

Sending, by the first secondary controller, a binding success message to the primary controller;

The first secondary controller receives a service flow recovery message sent by the primary controller.

In a possible implementation, before the first secondary controller receives the service flow suspension message sent by the primary controller, the method further includes:

The first secondary controller sends a new service function unit request message to the primary controller, where the newly added service function unit request message carries the identifier of the service flow and the service function name of the newly added service function unit. And the newly added service function unit includes indication information of the flow table;

In a possible implementation manner, the first secondary controller receives the primary controller to send After the business process startup message, it also includes:

The first secondary controller receives a service function unit unbinding notification message sent by the primary controller, where the service function unit unbinding notification message is used to indicate that the first secondary controller needs to be unbound. The business function unit unbinds the relationship;

The first secondary controller cancels the binding relationship with the service function unit that needs to be unbound;

The first secondary controller sends an unbinding success message to the primary controller.

In a possible implementation, after the first secondary controller receives the service flow suspension message sent by the primary controller, the method further includes:

The first secondary controller sends a service function unit unbinding request message to the main controller, where the service function unit unbinding request message carries the service function name and the service function unit of the service function unit that needs to be unbound. The identification of the business process.

In a third aspect, a multi-controller collaboration device includes:

a transceiver unit, configured to send a binding trigger message to each of the at least one secondary controller, where the binding trigger message sent by the ith secondary controller is used to trigger the ith secondary controller Establishing a binding relationship with the service function unit in each service function unit constituting the business process, where each service function unit constituting the business process is deployed by the device as a switch;

And receiving, by the each secondary controller, a binding success message, where the binding success message is used to notify the device that the secondary controller is successfully bound to the at least one service function unit;

a processing unit, configured to send, according to the received binding success message, each service function unit constituting the service flow, to the at least one secondary controller and the switch, respectively, by using the transceiver unit Process start message.

In a possible implementation, the binding trigger message sent by the ith secondary controller carries an identifier of the service flow, description information of each service function unit constituting the service flow, and the ith The name of the service function corresponding to the service function unit bound to the secondary controller;

In a possible implementation, after the service flow start message is sent to the at least one secondary controller and the switch, the processing unit is further configured to:

Transmitting, by the transceiver unit, a service flow suspension message to the at least one secondary controller and the switch respectively;

Adding at least one business function unit in the business process;

Transmitting, by the transceiver unit, a new service function unit notification message to at least one of the at least one secondary controller, where the newly added service function unit notification message is used to indicate the at least one secondary controller Establishing a binding relationship between the at least one secondary controller and the corresponding newly added service function unit;

Receiving, by the transceiver unit, a binding success message sent by at least one secondary controller of the at least one secondary controller;

Transmitting, by the transceiver unit, a service flow recovery message to the at least one secondary controller and the switch, respectively.

In a possible implementation, before the service flow suspension message is sent to the at least one secondary controller and the switch, the processing unit is further configured to:

Receiving, by the transceiver unit, a new service function unit request message sent by the first secondary controller, where the newly added service function unit request message carries the identifier of the service flow, and the service function of the newly added service function unit The name and the new service function unit include indication information of the flow table.

Transmitting, by the transceiver unit, a service function unit unbinding notification message to the second secondary controller, where the service function unit unbinding notification message is used to indicate the second secondary controller and the service function unit that needs to be unbound Unbinding the relationship, wherein the second secondary controller is any one of the at least one secondary controller;

Receiving, by the transceiver unit, an unbinding success message sent by the second secondary controller.

Receiving, by the transceiver unit, a service function unit unbinding request message sent by the second secondary controller, where the service function unit unbinding request message carries the service function name of the service function unit that needs to be unbound The identification of the business process.

In a possible implementation, after receiving the unbinding success message sent by the second secondary controller, the processing unit is further configured to:

Transmitting, by the transceiver unit, a service function unit designation message to the third secondary controller, where the service function unit designation message carries the description information of the service function unit that needs to be unbound and the identifier of the service process, where the service a functional unit designation message is used to indicate the third secondary controller Establishing a binding relationship with the service function unit that needs to be unbound, the third secondary controller is any one of the at least one secondary controller, and the third secondary controller sends the third secondary controller by using the transceiver unit. Binding success message; or deleting the business function unit that needs to be unbound in the business process;

When it is determined that each business function unit constituting the business process has been unbound, the business process is deleted.

A fourth aspect is a multi-controller collaboration device, including:

a transceiver unit, configured to receive a binding trigger message sent by the main controller, where the binding triggering message is used to trigger a binding relationship between the device and a service function unit in each service function unit that constitutes a service process, where The various service functional units constituting the business process are deployed by the primary controller for the switch;

a processing unit, configured to establish a binding relationship with at least one service function unit;

The transceiver unit is further configured to send a binding success message to the main controller, where the binding success message is used to notify the main controller that the device is successfully bound to the at least one service function unit;

And receiving a business process startup message sent by the primary controller.

Before the binding relationship is established with the at least one service function unit, the processing unit is further configured to:

Determining at least one service function unit as a service function unit to be bound according to description information of each service function unit constituting the service process.

In a possible implementation manner, the binding trigger message carries an identifier of the service process, description information of each service function unit that constitutes the service process, and a service function unit that is required to be bound by the device. Business function name;

When a binding relationship is established with at least one service function unit, the processing unit is configured to:

And determining a to-be-bound service function unit according to the service function name corresponding to the service function unit to be bound to the device, and establishing a binding relationship with the to-be-bound service function unit.

Determining, according to the description information of the service function unit to be bound to the device that is carried in the binding trigger message, the service function unit to be bound, and establishing a binding relationship with the service function unit to be bound.

In a possible implementation, after receiving the service flow start message sent by the main controller, the processing unit is further configured to:

Receiving, by the transceiver unit, a service flow suspension message sent by the primary controller;

Receiving, by the transceiver unit, the sending, by the main controller, a new service function unit notification message, The newly added service function unit notification message is used to indicate that the device establishes a binding relationship with the newly added service function unit;

Establishing a binding relationship with the newly added service function unit;

Sending, by the transceiver unit, a binding success message to the primary controller;

Receiving, by the transceiver unit, a service flow recovery message sent by the primary controller.

In a possible implementation, before receiving the service flow suspension message sent by the main controller, the processing unit is further configured to:

Sending, by the transceiver unit, a new service function unit request message to the main controller, where the newly added service function unit request message carries an identifier of the service process, a service function name and a location of the newly added service function unit. The newly added service function unit includes indication information of the flow table;

Receiving, by the transceiver unit, a service function unit unbinding notification message sent by the main controller, where the service function unit unbinding notification message is used to indicate that the device is unbound from a service function unit that needs to be unbound. relationship;

Unbinding the business function unit that needs to be unbound;

An unbinding success message is sent to the primary controller by the transceiver unit.

In a possible implementation, after receiving the service flow suspension message sent by the primary controller, the processing unit is further configured to:

Sending, by the transceiver unit, a service function unit unbinding request message to the main controller, where the service function unit unbinding request message carries the service function name of the service function unit that needs to be unbound and the service The identity of the process.

In a fifth aspect, a main controller includes:

transceiver;

a memory for storing instructions; and

a processor, coupled to the memory and the transceiver, for executing instructions to execute the instructions Perform the following steps:

Sending, by the transceiver, a binding trigger message to each of the at least one secondary controller, where the binding trigger message sent for the i-th secondary controller is used to trigger the ith secondary controller Establishing a binding relationship with the service function unit in each service function unit constituting the business process, where each service function unit constituting the business process is deployed by the device as a switch;

And determining, according to the received binding success message, that each service function unit constituting the service flow is bound, respectively, sending, by the transceiver, a service flow start message to the at least one secondary controller and the switch.

In a sixth aspect, a secondary controller includes:

transceiver;

a memory for storing instructions; and

A processor, coupled to the memory and the transceiver, for executing instructions to perform the following steps when executing the instructions:

Receiving, by the transceiver, the primary controller sends a binding trigger message, where the binding triggering message is used to trigger the device to establish a binding relationship with the service functional unit in each service functional unit constituting the service flow, where the service is formed Each service functional unit of the process is deployed by the primary controller as a switch;

Establishing a binding relationship with at least one business function unit;

Sending, by the transceiver, a binding success message to the main controller, where the binding success message is used to notify the main controller that the device is successfully bound to the at least one service function unit;

In summary, in the embodiment of the present invention, the primary controller sends a binding trigger message to each of the at least one secondary controller, that is, the primary controller can directly specify the service functional unit bound to each secondary controller. The secondary controller may also select the service function unit that it wishes to bind, and the primary controller receives the binding success message fed back by each secondary controller, and the primary controller successfully cancels according to the received binding. When it is determined that each service function unit constituting the service process is bound, the service flow start message is separately sent to the at least one secondary controller and the switch. Therefore, after each secondary controller is bound to the service function unit, the network application required to implement the service function corresponding to the bound service function unit can be separately deployed on each secondary controller, and each secondary controller is bound to the network application. The business function unit manages and controls the controller to avoid the bottleneck caused by the centralized deployment of the network function, and implements multiple controllers to cooperatively control the business process in the switch.

DRAWINGS

1 is a schematic diagram of an SDN network architecture in the background art of the present invention;

2 is a schematic diagram of an SDN network architecture including an OF Controller and an OF Switch according to an embodiment of the present invention;

3 is a flowchart of an overview of cooperation of multiple controllers according to an embodiment of the present invention;

4 is a specific process of multi-controller cooperation in an embodiment of the present invention;

FIG. 5 is a second specific process of multi-controller cooperation according to an embodiment of the present invention;

FIG. 6 is a specific process of adding a binding service function unit according to an embodiment of the present invention;

FIG. 7 is a specific process of unbinding a service function unit according to an embodiment of the present invention;

8 is a schematic structural diagram of a multi-controller cooperation device according to an embodiment of the present invention;

9 is a second schematic structural diagram of a multi-controller cooperation device according to an embodiment of the present invention;

10 is a schematic structural diagram of a main controller according to an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a secondary controller according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

First, the application scenario involved in the embodiment of the present invention is briefly introduced.

In the prior art, the OpenFlow protocol is a typical technology of an SDN network. The network elements in the OpenFlow protocol include an OpenFlow controller (corresponding to the network controller in FIG. 1 and hereinafter referred to as OF Controller) and an OpenFlow switch (corresponding to the network device in FIG. 1 , hereinafter referred to as OF Switch). The OF Controller controls the flow table in the OF Switch by pre-specified interface operations, thereby achieving the purpose of controlling data forwarding.

Specifically, as shown in FIG. 2, in the SDN network, the OF Controller is a control plane device in the SDN network architecture, and is responsible for determining the forwarding action of the service flow according to the packet characteristics, and sending the flow rule corresponding to the service flow to the OF Switch. The OF Switch is a user plane device in the SDN network architecture. It is also called a forwarding plane device. It acquires and stores the flow rules from the OF Controller, and performs corresponding forwarding or processing on the packets conforming to the flow rule.

The OF Controller can configure and manage the OF Switch through the control channel. There are multiple channels in an OF Switch, which can be connected to multiple OF Controllers at the same time, as shown in Figure 2.

In the prior art, the controller can implement the business process to the switch and group the flow tables that constitute the business process. Specifically, the controller sends a packet indication message to the switch, where the packet indication message is used to instruct the switch to group at least one flow table constituting the service flow. Therefore, the controller can directly deliver the packetized service flow to the switch, or send the service flow to the switch, and then group the flow table that constitutes the service process. At this time, the service flow in the switch is configured by at least one flow table. Group composition.

Similarly, for a switch that does not support a flow table group, the controller can divide each flow table constituting the business process into at least one logical switch by a configuration mode (for example, OF Config). It should be noted that the logical switch is physically composed of at least one flow table in the switch, and can be logically regarded as a single switch. The controller divides each flow table constituting the business process into at least one logical switch, which is completed through a configuration port, and the controller sends a packet indication message to the switch through the service port.

Further, the controller can also bind and unbind the flow table group in the switch, and add the flow table group and the delete flow table group. Specifically, for the flow table group binding, the controller sends the switch to the switch. The flow table group binding message, the flow table group binding message carries the identification information of the flow table group to be bound, and the flow table group binding message is used to establish a binding relationship between the controller and the flow table group to be bound, so that the control is performed. The device handles the binding flow table group management. The device unbinds the flow table group, and the controller sends a flow table group unbinding message to the switch. The flow table group unbinding message carries the identification information of the flow table group to be unbound. For the new flow table group, the controller sends a new group indication message to the switch, and the newly added group indication message is used to instruct the switch to group at least one newly added flow table. The controller sends a flow table group deletion message to the switch for deleting the flow table group. The flow table group deletion message carries the identification information of the flow table group to be deleted or deletes the indication information of all the flow table groups.

For the same reason, for a switch that does not support the flow table group, bind and unbind the logical switch, and add a logical switch and delete the logical switch in the configuration mode (for example, OF Config mode).

The OF Controller (hereinafter referred to as "Master") with the Master attribute is the primary controller, and the OF Controller (hereinafter referred to as Equal) with the Equal attribute is the secondary controller.

The interaction process between the main controller, the first secondary controller, and the switch is taken as an example to illustrate how the multi-controller cooperation is implemented in the embodiment of the present invention.

Referring to FIG. 3, an embodiment of the present invention provides a multi-controller cooperation method, including:

Step 300: The primary controller sends a binding trigger message to each of the at least one secondary controller.

The binding trigger message sent by the i-th secondary controller is used to trigger the binding relationship between the i-th secondary controller and the service functional unit in each service functional unit that constitutes the service process, where each of the service flows is formed. The business function unit is deployed by the primary controller for the switch.

Specifically, each service function unit refers to a flow table group or a logical switch, and each service function unit corresponds to one service function.

Step 310: The first secondary controller establishes a binding relationship with the at least one service function unit.

Step 320: The first secondary controller sends a binding success message to the primary controller, where the binding success message is used to notify the primary controller that the first secondary controller is successfully bound to the at least one service functional unit.

Step 330: The main controller determines, according to the received binding success message, each of the constituent business processes. When the service function units are all bound, the service flow start message is sent to at least one secondary controller and the switch respectively.

The above is only described by taking the first secondary controller as an example, and the first secondary controller is any one of at least one secondary controller.

Optionally, for step 300, the binding trigger message sent by the ith secondary controller may be the following two situations:

In the first case, the binding trigger message sent by the i-th secondary controller carries the identifier of the service process and the description information of each service function unit that constitutes the service process.

The description information of each service function unit includes a service function name corresponding to the service function unit, a forwarding plane identifier corresponding to the service function unit, a forwarding plane type, and information of each jumpable service function unit corresponding to the service function unit, Each of the jumpable service function unit information includes a service function name of the jumpable service function unit and a jump instruction corresponding to the jumpable service function unit.

In addition, when each service function unit refers to a flow table group, the forwarding plane corresponding to the service function unit is identified as an identifier of the switch, and the forwarding plane type indicates that the switch is a switch that supports the flow table group;

When each service function unit refers to a logical switch, the forwarding plane corresponding to the service function unit is identified as the identifier of the corresponding logical switch, and the forwarding plane type indicates that the switch is a switch that does not support the flow table group.

Specifically, taking the first secondary controller as an example, before the first secondary controller establishes a binding relationship with the at least one service function unit, the first secondary controller carries the binding trigger message sent by the first secondary controller. The description information of each service function unit constituting the business process, the first secondary controller selects at least one service function unit as the service function unit to be bound.

Further, when the service function unit is a flow table group, the first secondary controller establishes a binding relationship with the flow table group to be bound in the switch. When the service function unit is a logical switch, the first secondary controller establishes a binding relationship with the logical switch to be bound in the logical switch.

A scenario for implementing multi-controller cooperation is described below using FIG. 4 as an example.

S401: The master customizes the business process and deploys to the OF Switch.

The master customizes the service process and deploys it to the OF Switch, which is the service flow initialization process of each OF Switch by Mater. After the initialization process is successful, each OF Switch contains multiple flow table groups or multiple OPLSs. Here, the number of OF switches is taken as an example. Similarly, the Master can customize various business processes and deploy them to each OF Switch.

Specifically, when the OF Switch is a switch supporting the flow table group, the Master customizes the service-based Pipeline to send a packet indication message (OFPT_BP_MOD) to the OF Switch.

When the OF Switch is a switch that does not support the flow table group, the master configures the resources of each OpenFlow Logical Switch (OFLS) and the connection relationship between them through the OF Config.

It should be noted that the embodiment of the present invention does not limit the manner in which the service flow customization of the forwarding plane is implemented, and how to implement at least one flow table constituting the service function unit into the service function units.

S402: The Master sends a service flow initialization message (Init_BP_Notification) to each Equal.

Init_BP_Notification is an implementation of the binding trigger message. It is sent after the master determines that the business process is successfully initialized. Init_BP_Notification is used to notify each new new forwarding surface processing process. Init_BP_Notification contains the parameter process, whose structure is:

Process_id: ID of the business process

[bs_role]n: A list of information of each business function unit in the business process, the order of which represents the position of each business function unit in the business process, wherein the structure of bs_role is:

Bs_name: name of the business function;

Datapath_id: forwarding surface identification information;

Type: forwarding face type;

[Gotos]n: A list of business function unit information can be jumped. The structure is:

Bs_name: The name of the service function that can be redirected to the service function unit;

Instruction: jump to the jump instruction of the jumpable business function unit

When each service function unit refers to a flow table group, the forwarding plane corresponding to the service function unit The identifier is the ID of the OF Switch, and the forwarding plane type indicates that the switch is a switch that supports the flow table group.

When each service function unit refers to a logical switch, the forwarding plane identifier corresponding to the service function unit is an identifier corresponding to the OFLS, and the forwarding plane type indicates that the switch is a switch that does not support the flow table group.

Optionally, the instruction may adopt a Goto-TG instruction, and the Goto-TG carries a bs_name, or other instructions, such as carrying an output port, a destination Mac address, and the like in other manners of instructions.

S403: Each Equal determines the business function unit to be bound according to the Process in Init_BP_Notification.

S404: Establish a connection between each Equal and the OF Switch where the selected service function unit is located.

S405: Each Equal binds the selected business function unit.

Specifically, when each service function unit refers to a flow table group, Equal sends a flow table group binding message (OFPT_TG_MOD) to the OF Switch, where the message carries the service function name (ie, bs_name) of the selected service function unit.

When each service function unit refers to a logical switch, Equal sends an OFLS binding message OFPT_ROLE_REQUEST message to the OF Switch, where the message carries the service function name (ie, bs_name) of the selected service function unit.

S406: Each Equal sends a binding success message (Bind_BR_Notification) to the Master.

Bind_BR_Notification is sent when Equal determines that the binding is successful with the selected business function unit.

S407: The master sends a service flow start message (Activate_BP_Notification) to all the Equals and the Switch.

Activate_BP_NotificationMaster is sent when the Master determines that all business functional units in the business process have been bound.

At this time, each Equal interacts with the service function unit and the corresponding flow table that it controls, and completes the specific service functions of the service function unit, including packet reporting, flow table delivery, and the like.

Therefore, according to the method provided by the embodiment of the present invention, each Equal is provided according to the master. The entire description of the service function units of the business process, the service function unit to be bound, and the binding of at least one selected service function unit, and the service function unit corresponding to the binding of each Equal is implemented. The network application required for the business function, each Equal manages and controls the bound business function unit, avoids the bottleneck caused by the centralized deployment of the network function of the controller, and realizes the business process of the multiple controllers cooperatively controlling the switch. .

The second case: the binding trigger message sent by the i-th secondary controller carries the identifier of the service flow, the description information of each service function unit constituting the service flow, and the service function unit to be bound by the i-th secondary controller. The corresponding service function name; or the binding trigger message sent by the i-th secondary controller carries the identifier of the service flow and the description information of the service function unit to be bound by the i-th secondary controller.

Compared with the first case, the secondary controller needs to determine the service function unit to be bound by itself. In the second case, the primary controller selects the corresponding bound service function unit for each secondary controller. .

Another scenario for implementing multi-controller cooperation is described below using FIG. 5 as an example. In FIG. 5, steps similar to those of FIG. 4 are omitted and will not be described again.

S501: The master customizes the business process and deploys it to the OF Switch.

S502: The Master sends a service flow initialization message (Init_BP_Notification) to each Equal.

S503: The Mater sends a service function unit designation message (Designate_BR_Notification) to each Equal.

The two messages corresponding to the foregoing S502 and S503 can be sent to each Equal at one time, or can be sent to each Equal in two times. Here, the two transmissions are taken as an example for description. Both forms of message transmission can be implemented as binding trigger messages.

Specifically, for each Equal, the messages corresponding to S502 and S503 respectively may be selected to carry different content.

The first case: If the Init_BP_Notification message contains the process parameter, only the service function unit to be bound to the Equal is required in Designate_BR_Notification. The name of the business function. The process parameter is the same as the process parameter described in the above S402, and is not described here.

For example, the Designate_BR_Notification carries [bs_name]n, and the surface master wants a list of service names corresponding to the plurality of service functional units bound by the Equal.

The second case: If the Init_BP_Notification message does not include the process parameter, the Designate_BR_Notification carries the identifier of the service process and the description information of the service function unit to which the Equal needs to be bound.

For example, [bs_role]n: A list of descriptions of multiple business function units that the Master wants to assume for the Equal.

S504: Each Equal and the Master establish a connection between the OF Switchs where the designated service function unit is located.

S505: Each Equal binds a specified business function unit.

S506: Each Equal sends a binding success message (Bind_BR_Notification) to the Master.

Bind_BR_Notification is sent when Equal determines that the binding with the specified business function unit is successful.

S507: The master sends a business process start message (Activate_BP_Notification) to all Equals and Switches.

Therefore, in the method provided by the embodiment of the present invention, the master specifies the service function unit to be bound for each Equal, and each Equal completes binding to at least one selected service function unit, and each Equal is separately deployed to implement binding. The network application required by the service function corresponding to the service function unit, each Equal manages and controls the bound service function unit, avoids the bottleneck caused by the centralized deployment of the network function of the controller, and realizes cooperative control of multiple controllers. Business process in the switch.

In addition, the embodiment of the present invention further provides a method for adding a binding service function unit and deleting a binding service function unit.

For a scenario where a new service function unit is added, there are two possible implementation scenarios:

The first scenario is triggered by the first secondary controller, and the first secondary controller sends a new service function unit request message to the primary controller, and the primary controller notifies each secondary controller and the switch to suspend the service flow. And adding at least one service function unit to the switch according to the newly added service function unit request message, and then feeding back the new service function unit response message to the first auxiliary controller, and the first secondary controller receives the response message and binds the new message. At least one business function unit is added. Finally, the primary controller notifies each secondary controller and switch to resume business processes.

The newly added service function unit request message carries the identifier of the service process, the service function name of the newly added service function unit, and the new service function unit includes the indication information of the flow table.

Or, the first secondary controller is still triggered by the first secondary controller, and the primary controller adds at least one service function unit to the switch according to the newly added service function unit request message sent by the first secondary controller, and sends the new controller to the at least one secondary controller. The service function unit specifies a message, and at least one of the secondary controllers herein may or may not include the first secondary controller. Each of the secondary controllers that have received the new service function unit designation message is bound to the new service function unit corresponding to the new service function unit specified for the secondary controller in the new service function designation message. Finally, the primary controller notifies each secondary controller and switch to resume business processes.

The first secondary controller is any one of the secondary controllers.

For example, when the service function unit that is currently bound to the service is determined to be added by the service function unit, the new service function unit request message is sent to the master. The master adds the required service function unit to the account. Equal1 is then bound by Equal1. Since the new business function unit is related to the original business function unit, it is more convenient to manage it uniformly by Equal1.

The second scenario is triggered by the primary controller. After the primary controller notifies each secondary controller and switch to suspend the service process, add at least one service function unit to the switch, and then feed the at least one secondary controller to add a new service function unit. Specify a message. Each of the secondary controllers that have received the new service function unit designation message is bound to the new service function unit corresponding to the new service function unit specified for the secondary controller in the new service function designation message. Finally, the primary controller notifies each secondary controller and switch to resume business processes.

For example, after adding a service function unit, the master specifies the new service function of the Equal2 pair that has been bound to the related service function unit according to the service function corresponding to the new service function unit. The unit can be bound.

In addition, when the main controller notifies each of the secondary controllers and the switch to restore the service process, the service flow recovery message may carry the description information of each service function unit that constitutes the service process or the description of the newly added at least one service function unit. information.

Figure 6 shows the specific process for the above two newly added binding service functional units.

S601: Equal1 sends a new service function unit request message (Add_BR_Request) to the master.

The message includes:

Bs_name: Name of the business function of the new business function unit.

Table_numbers: Number of flow tables for new business function units.

It should be noted that S601 is an optional step.

S602: The Master sends a service flow suspension message (Deactivate_BP_Notification) to all Equal and OF switches, and suspends the business process.

S603: The Master adds a new service function unit and corresponding resources.

Specifically, S603 can be implemented in the following two ways:

When each service function unit refers to a flow table group, the master sends a new packet indication message (OFPT_TG_MOD) to the OF Switch to add a new flow table group.

When each service function unit refers to an OFLS, the master adds OFLS and corresponding resources through OF Config and modifies the connection relationship between them.

S604a: The Master returns a new service function unit request response message (Add_BR_Response) to the Equal1 requesting to add the service function unit.

The message carries the description information of the added service function unit, that is, bs_role.

It should be noted that S604a is a step required to perform a scenario in which S601 is executed.

S604b: The master sends a service function unit designation message (Designate_BR_Notification to the selected account, the message carries the description information of the added service function unit.

It should be noted that S604b may be a step required to execute a scenario in which S601 is executed, or may be a step required to execute a scenario in which S601 is not executed. Figure 6 shows only one special case, the Master sends Designate_BR_Notification to Equal1. The Master can also choose to send Designate_BR_Notification to other Equals.

S605: The new business function unit is bound to Equal1.

S606: The equal1 sends a binding success message (Bind_BR_Notification) to the master to notify the binding result.

S607: The Master sends a Service Flow Recovery message (Activate_BP_Notification) message to all the Equals.

Activate_BP_Notification can be used to start both the business process and the recovery business process. The Activate_BP_Notification sent contains the updated business process information (Update_BP_Notification). For example, Update_BP_Notification can contain at least one [bs_role]n of the latest process or update.

For the scenario of deleting a bound service function unit, there are two possible implementation scenarios:

In the first scenario, triggered by the first secondary controller, the first secondary controller sends a service function unit unbinding request message, and the primary controller notifies all the secondary controllers and switches to suspend the service flow, and the primary controller controls the first secondary control. The device sends a sending service function unit unbinding response message, and the service function unit unbinding notification message is used to indicate that the first secondary controller is unbinding with the service function unit that needs to be unbound, wherein the first secondary controller is At least one of the secondary controllers; the primary controller receives the unbinding success message sent by the first secondary controller.

The service function unit unbind request message carries the service function name and the identifier of the service process of the service function unit that needs to be unbound.

For example, when Equal1 wants to unbind a service function unit that is currently bound to itself, it can send a service function unit unbind request message to the master. The Master informs that Equal1 can unbind the service function unit and receive the unbinding success message fed back by Equal1.

The second scenario is triggered by the primary controller, and the primary controller notifies all the secondary controllers and switches to suspend the service process, and the primary controller sends a sending service function unit unbinding notification message to the first secondary controller, and the service function unit is unbound. The notification message is used to instruct the first secondary controller to unbind the business function unit that needs to be unbound. The main controller receives the unbind sent by the first secondary controller Success message.

For example, when the master wants to cancel the binding relationship between the service function unit and the current service function unit, the master can notify Equal2 to unbind the service function unit and receive the unbinding success message fed back by Equal2.

FIG. 7 shows a specific process for the above two unbundling service function units.

S701: The Equal sends a service function unit unbinding request message (Unbind_BR_Request) to the master.

The message carries bs_name, indicating the business function unit that needs to be unbound.

It should be noted that S701 is an optional step.

S702: The Master sends a service flow suspension message (Deactivate_BP_Notification) to all Equal and OF switches, and suspends the business process.

S703a: The Master returns the service function unit unbind response message (Unbind_BR_Response) to the Equal of the request cancellation business function unit.

S703a is a step that is required to be performed for the scenario in which S701 is executed.

S703b: The master sends a service function unit unbinding notification message (Cancel_BR_Notification) to the corresponding premium.

This message carries the parameter bs_name.

It should be noted that S703b is a step required to perform a scenario in which S701 is not executed.

Figure 7 is only a special case. The Equal that is requested to cancel the binding of the service function unit is the same as the Equal that the Master wants to cancel the binding relationship.

S704: Equal cancels the binding for the unit that needs to cancel the business function.

Specifically, S704 can be implemented in the following two ways:

When each service function unit refers to a flow table group, Equal sends an OFPT_TG_MOD message to the OF Switch, and cancels the binding relationship with the flow table group corresponding to the service function unit.

When each service function unit refers to an OFLS, Equal disconnects the OFLS corresponding to the service function unit.

S705: Equal sends an unbinding success message (Unbind_BR_Notification) to the master. Notify the unbinding result;

After executing S705, the master can select another Equal to bind the service function unit, and then resume the business process, or the master initiates deletion of the service function unit, and then resumes the business process, or after determining that the service function unit is unbound, When each business function unit that constitutes a business process has been unbound, the business process is deleted.

The Master initiates the deletion of the service function unit in the following two ways:

When each service function unit is a flow table group, the master sends a flow table group deletion message (OFPT_TG_MOD) to the OF switch, and carries the service function name of the flow table group indicated by the service process unit.

When each service function unit refers to an OFLS, the master deletes the OFLS and corresponding resources through OF Config and modifies the connection relationship.

The Master can delete the business process in the following two ways:

When each service function unit is a flow table group, the master sends a flow table group deletion message (OFPT_BP_MOD) to the Switch, indicating that all flow table groups included in the service flow are deleted.

When each service function unit refers to an OFLS, the Master deletes all OFLSs through OF Config.

Based on the same inventive concept, a multi-controller cooperation device is also provided in the embodiment of the present invention, and the device may be the main controller in the embodiment shown in FIG. The device may be used to perform the method embodiment corresponding to FIG. 3 above. Therefore, the implementation manner of the multi-controller cooperation device provided by the embodiment of the present invention may be referred to the implementation manner of the method, and details are not described herein again.

Referring to FIG. 8 , an embodiment of the present invention provides a multi-controller cooperation device, which has a function of implementing a behavior of a main controller in an example of the foregoing method, and the function may be implemented by hardware, or may execute corresponding software through hardware. achieve. The hardware or software includes one or more modules corresponding to the functions described above.

The device comprises a transceiver unit 80 and a processing unit 81, which can perform corresponding functions in the above method examples, specifically:

The transceiver unit 80 is configured to send a binding touch to each of the at least one secondary controller Sending a message, wherein the binding trigger message sent by the i-th secondary controller is used to trigger the binding relationship between the i-th secondary controller and the service function unit in each service function unit that constitutes the service flow, where The various service functional units constituting the business process are deployed by the device for the switch;

The processing unit 81 is configured to determine, according to the received binding success message, that each service function unit constituting the service flow is bound, by using the transceiver unit 80 to the at least one secondary controller and the switch respectively Send a business process start message.

When each service function unit refers to a logical switch, the service function unit corresponds to the turn The sender ID is the identifier of the corresponding logical switch. The forwarding plane type indicates that the switch is a switch that does not support the flow table group.

In a possible implementation, after the service flow start message is sent to the at least one secondary controller and the switch, the processing unit 81 is further configured to:

Transmitting, by the transceiver unit 80, a service flow suspension message to the at least one secondary controller and the switch respectively;

Adding at least one business function unit in the business process;

Transmitting, by the transceiver unit 80, a new service function unit notification message to at least one of the at least one secondary controller, where the newly added service function unit notification message is used to indicate the at least one secondary controller At least one secondary controller establishes a binding relationship with the corresponding newly added service function unit;

Receiving, by the transceiver unit 80, a binding success message sent by at least one secondary controller of the at least one secondary controller;

Transmitting, by the transceiver unit 80, a service flow recovery message to the at least one secondary controller and the switch, respectively.

In a possible implementation, before the service flow suspension message is sent to the at least one secondary controller and the switch, the processing unit 81 is further configured to:

Receiving, by the transceiver unit 80, a new service function unit request message sent by the first secondary controller, where the newly added service function unit request message carries the identifier of the service flow and the service of the newly added service function unit. The function name and the newly added service function unit include indication information of the flow table.

Transmitting, by the transceiver unit 80, a service function unit unbinding notification message to the second secondary controller, where the service function unit unbinding notification message is used to indicate the second secondary controller and the requirement Unbinding the business function unit unbinding relationship, wherein the second secondary controller is any one of the at least one secondary controller;

Receiving, by the transceiver unit 80, an unbinding success message sent by the second secondary controller.

Receiving, by the transceiver unit 80, a service function unit unbinding request message sent by the second secondary controller, where the service function unit unbinding request message carries the service function name of the service function unit that needs to be unbound And the identification of the business process.

In a possible implementation, after receiving the unbinding success message sent by the second secondary controller, the processing unit 81 is further configured to:

Sending, by the transceiver unit 80, a service function unit designation message to the third secondary controller, where the service function unit designation message carries the description information of the service function unit that needs to be unbound and the identifier of the service flow, The service function unit designation message is used to indicate that the third secondary controller establishes a binding relationship with the service function unit that needs to be unbound, and the third secondary controller is any one of the at least one secondary controller. Receiving, by the transceiver unit 80, a binding success message sent by the third secondary controller; or deleting the service function unit that needs to be unbound in the service flow;

Based on the same inventive concept, a multi-controller cooperation device is also provided in the embodiment of the present invention, and the device may be the secondary controller in the embodiment shown in FIG. The device may be used to perform the method embodiment corresponding to FIG. 4 above. Therefore, the implementation manner of the multi-controller cooperation device provided by the embodiment of the present invention may be referred to the implementation manner of the method, and details are not described herein again.

Based on the same inventive concept, a multi-controller cooperation device is also provided in the embodiment of the present invention, and the device may be the secondary controller in the embodiment shown in FIG. The device may be used to perform the method embodiment corresponding to FIG. 3 above. Therefore, the implementation manner of the multi-controller cooperation device provided by the embodiment of the present invention may be referred to the implementation manner of the method, and details are not described herein again.

Referring to FIG. 9 , an embodiment of the present invention provides a multi-controller cooperation device, which has a function of implementing a behavior of a secondary controller in the foregoing method example, and the function may be implemented by hardware, or may execute corresponding software through hardware. achieve. The hardware or software includes one or more modules corresponding to the functions described above.

Specifically, the device includes a transceiver unit 90 and a processing unit 91, which can perform corresponding functions in the above method examples, wherein:

The transceiver unit 90 is configured to receive, by the main controller, a binding trigger message, where the binding trigger message is used to trigger the device to establish a binding relationship with a service function unit in each service function unit constituting the service flow, where The various service functional units constituting the business process are deployed by the primary controller for the switch;

The processing unit 91 is configured to establish a binding relationship with the at least one service function unit.

The transceiver unit 90 is further configured to send a binding success message to the main controller, where the binding success message is used to notify the main controller that the device is successfully bound to the at least one service function unit;

Before the binding relationship is established with the at least one service function unit, the processing unit 91 is further configured to:

When the binding relationship is established with the at least one service function unit, the processing unit 91 is configured to:

In a possible implementation, after receiving the service flow start message sent by the main controller, the processing unit 91 is further configured to:

Receiving, by the transceiver unit 90, a service flow suspension message sent by the primary controller;

Receiving, by the transceiver unit 90, the main controller sends a new service function unit notification The new service function unit notification message is used to indicate that the device establishes a binding relationship with the newly added service function unit.

Establishing a binding relationship with the newly added service function unit;

Sending, by the transceiver unit 90, a binding success message to the primary controller;

Receiving, by the transceiver unit 90, a service flow recovery message sent by the primary controller.

In a possible implementation, before receiving the service flow suspension message sent by the main controller, the processing unit 91 is further configured to:

Sending, by the transceiver unit 90, a new service function unit request message to the main controller, where the new service function unit request message carries an identifier of the service flow, a service function name of the newly added service function unit, and The newly added service function unit includes indication information of the flow table;

Receiving, by the transceiver unit 90, a service function unit unbinding notification message sent by the main controller, where the service function unit unbinding notification message is used to indicate that the device is unbind from a service function unit that needs to be unbound. Relationship

Unbinding the business function unit that needs to be unbound;

An unbinding success message is sent to the primary controller by the transceiver unit 90.

In a possible implementation, after receiving the service flow suspension message sent by the main controller, the processing unit 91 is further configured to:

Transmitting, by the transceiver unit 90, a service function unit unbinding request message to the main controller, where the service function unit unbinding request message carries the service function name of the service function unit that needs to be unbound and the The identity of the business process.

It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner. The functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be used The form of hardware implementation can also be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.

Based on the same inventive concept, a main controller is also provided in the embodiment of the present invention, which is a physical device of the device shown in FIG.

Referring to FIG. 10, an embodiment of the present invention provides a main controller, including:

Transceiver 1001;

a memory 1002 for storing instructions; and

The processor 1003 is connected to the memory 1002 and the transceiver 1001, respectively, for executing instructions to perform the following steps when executing the instructions:

Sending, by the transceiver 1001, a binding trigger message to each of the at least one secondary controller, where the binding trigger message sent for the i-th secondary controller is used to trigger the ith secondary control Establishing a binding relationship with the service function unit in each service function unit constituting the business process, where each service function unit constituting the business process is deployed by the device as a switch;

When it is determined that each service function unit constituting the service flow is bound according to the received binding success message, the service flow start message is separately sent to the at least one secondary controller and the switch by the transceiver 1001.

Based on the same inventive concept, a secondary controller is also provided in the embodiment of the present invention, which is a physical device of the device shown in FIG.

Referring to FIG. 11, an embodiment of the present invention provides a secondary controller, including:

Transceiver 1101;

a memory 1102 for storing instructions; and

The processor 1103 is respectively connected to the memory 1102 and the transceiver 1101 for executing an instruction to perform the following steps when executing the instruction:

Receiving, by the transceiver 1101, the primary controller sends a binding triggering message, where the binding triggering message is used to trigger the device to establish a binding relationship with the service functional unit in each service functional unit constituting the service flow, where Each service functional unit of the business process is deployed by the primary controller for the switch;

Establishing a binding relationship with at least one business function unit;

Sending, by the transceiver 1101, a binding success message to the main controller, where the binding success message is used to notify the main controller that the device is successfully bound to the at least one service function unit;

It should be noted that the connection manner between the parts shown in FIG. 10 and FIG. 11 is only one possible example, and the transceiver and the memory are both connected to the processor, and there is no connection between the transceiver and the memory. Or, it can be other possible connections.

In summary, in the embodiment of the present invention, the primary controller sends a binding trigger message to each of the at least one secondary controller, that is, the primary controller can directly specify the service functional unit bound to each secondary controller. The secondary controller may also select a service function unit that is to be bound by the secondary controller, and the primary controller receives the binding success message fed back by each secondary controller, and the primary controller determines, according to the received binding success message, that the service flow is formed. When each service function unit is bound, a service flow start message is separately sent to the at least one secondary controller and the switch. Therefore, after each secondary controller is bound to the service function unit, the network application required to implement the service function corresponding to the bound service function unit can be separately deployed on each secondary controller, and each secondary controller is bound to the network application. Business function units are managed and controlled to avoid bottlenecks caused by centralized deployment of network functions. Multiple controllers cooperatively control the business processes in the switch.

Therefore, the method provided by the embodiment of the present invention can implement distributed coordinated control of multiple controllers based on service flows for the SDN network, greatly simplifying the calculation processing overhead of each controller node, and improving the scalability of the network. Help network expansion and upgrade. In addition, the shared control of the multi-control network element to the switch reduces the signaling forwarding level, optimizes the signaling path, and reduces the processing delay of the control signaling, compared to the hierarchical control architecture for the multi-control network element.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be performed by a program, and the program may be stored in a computer readable storage medium, which is non-transitory ( English: non-transitory) media, such as random access memory, read-only memory, flash memory, hard disk, solid state disk, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), CD (English: optical disc) And any combination thereof.

The present invention has been described with reference to the respective flowcharts and block diagrams of the method and apparatus of the embodiments of the invention. It will be understood that each flow and block of the flowchart illustrations. FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. A device that implements the functions specified in one or more blocks of a flowchart or a plurality of flows and block diagrams.

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

A multi-controller cooperation method, comprising:

The master controller sends a binding trigger message to each of the at least one secondary controller, where the binding trigger message sent by the ith secondary controller is used to trigger the ith secondary controller and the component The business function unit in each business function unit of the business process establishes a binding relationship, wherein each business function unit constituting the business process is deployed by the main controller as a switch;

The master controller receives a binding success message fed back by each secondary controller, where the binding success message is used to notify the primary controller that the secondary controller is successfully bound to the at least one service function unit;

The main controller sends a service flow start message to the at least one secondary controller and the switch separately when the primary service function unit that is configured to be the service flow is bound according to the received binding success message.
The method according to claim 1, wherein each service function unit refers to a flow table group or a logical switch, and each service function unit corresponds to a service function.
The method according to claim 1 or 2, wherein the binding trigger message sent by the i-th secondary controller carries an identifier of the service flow and a description of each service function unit constituting the service flow. information.
The method according to claim 1 or 2, wherein the binding trigger message sent by the i-th secondary controller carries an identifier of the service flow and a description of each service function unit constituting the service flow. Information and a service function name corresponding to the service function unit bound to the i-th secondary controller;

Or the binding trigger message sent by the ith secondary controller carries the identifier of the service flow and the description information of the service function unit to be bound by the ith secondary controller.
The method according to claim 3 or 4, wherein the description information of each service function unit includes a service function name corresponding to the service function unit, a forwarding plane identifier corresponding to the service function unit, the forwarding plane type, Each of the jumpable service function unit information corresponding to the service function unit, wherein each of the jumpable service function unit information includes the jumpable service function unit The business function name and the jump instruction corresponding to the jumpable business function unit;

When each service function unit refers to a flow table group, the forwarding plane identifier corresponding to the service function unit is an identifier of the switch, and the forwarding plane type indicates that the switch is a switch supporting a flow table group;

When each service function unit refers to a logical switch, the forwarding plane corresponding to the service function unit is identified as an identifier of the corresponding logical switch, and the forwarding plane type indicates that the switch is a switch that does not support the flow table group.
The method according to any one of claims 1 to 5, further comprising: after the main controller sends a service flow start message to the at least one secondary controller and the switch, The controller sends a service flow suspension message to the at least one secondary controller and the switch respectively;

Adding, by the main controller, at least one service function unit to the service flow;

The primary controller sends a new service function unit notification message to at least one of the at least one secondary controller, where the new service function unit notification message is used to indicate the at least one secondary controller Establishing a binding relationship between the at least one secondary controller and the corresponding newly added service function unit;

The primary controller receives a binding success message sent by at least one secondary controller of the at least one secondary controller;

The primary controller separately sends a service flow recovery message to the at least one secondary controller and the switch.
The method of claim 6, wherein before the main controller sends the service flow suspension message to the at least one secondary controller and the switch, the method further includes:

Receiving, by the primary controller, a new service function unit request message sent by the first secondary controller, where the newly added service function unit request message carries the identifier of the service process, and the service function of the newly added service function unit The name and the new service function unit include indication information of the flow table.
The method according to any one of claims 1 to 7, wherein after the main controller sends a service flow start message to the at least one secondary controller and the switch respectively, The main controller sends a service flow suspension message to the at least one secondary controller and the switch respectively;

The main controller sends a service function unit unbinding notification message to the second secondary controller, where the service function unit unbinding notification message is used to indicate the second secondary controller and the service function unit that needs to be unbound. Unbinding the relationship, wherein the second secondary controller is any one of the at least one secondary controller;

The main controller receives an unbinding success message sent by the second secondary controller.
The method of claim 8, wherein before the main controller sends the service flow suspension message to the at least one secondary controller and the switch, the method further includes:

Receiving, by the main controller, a service function unit unbinding request message sent by the second secondary controller, where the service function unit unbinding request message carries the service function name of the service function unit that needs to be unbound and The identification of the business process.
The method according to claim 8 or 9, wherein after the main controller receives the unbinding success message sent by the second secondary controller, the method further includes:

The main controller sends a service function unit designation message to the third secondary controller, where the service function unit designation message carries the description information of the service function unit that needs to be unbound and the identifier of the service process, where the service The function unit designation message is used to indicate that the third secondary controller establishes a binding relationship with the service function unit that needs to be unbound, and the third secondary controller is any one of the at least one secondary controller. The main controller receives the binding success message sent by the third secondary controller; or the primary controller deletes the service function unit that needs to be unbound in the service process;

The primary controller separately sends a service flow recovery message to the at least one secondary controller and the switch.
The method according to claim 8 or 9, wherein after the main controller receives the unbinding success message sent by the second secondary controller, the method further includes:

When the main controller determines that each service function unit constituting the service process has been unbound, the service process is deleted.
A multi-controller cooperation method, comprising:

The first secondary controller receives the binding trigger message sent by the primary controller, where the binding trigger message is used to trigger the binding of the first secondary controller to the service functional unit in each service functional unit constituting the service flow. Relationship, wherein each business function unit constituting the business process is deployed by the main controller for the switch;

Establishing a binding relationship between the first secondary controller and the at least one service function unit;

The first secondary controller sends a binding success message to the primary controller, where the binding success message is used to notify the primary controller that the first secondary controller is bound to the at least one service functional unit. success;

The first secondary controller receives a service flow initiation message sent by the primary controller.
The method according to claim 12, wherein each service function unit refers to a flow table group or a logical switch, and each service function unit corresponds to a service function.
The method according to claim 12 or 13, wherein the binding trigger message carries an identifier of the service flow and description information of each service function unit constituting the service flow;

Before the first secondary controller establishes a binding relationship with the at least one service function unit, the method further includes:

The first secondary controller determines, according to the description information of each service function unit that constitutes the service flow, at least one service function unit as a service function unit to be bound.
The method according to claim 12 or 13, wherein the binding trigger message carries an identifier of the service flow, description information of each service function unit constituting the service flow, and the first secondary controller The name of the business function corresponding to the business function unit to be bound;

The first secondary controller establishes a binding relationship with the at least one service function unit, including:

Determining, by the first secondary controller, a service function unit to be bound according to a service function name corresponding to the service function unit to be bound by the first secondary controller that is carried in the binding trigger message, where the first auxiliary The controller establishes a binding relationship with the service function unit to be bound.

Or the binding trigger message sent by the i-th secondary controller carries the service flow Demyimating the description information of the service function unit bound to the i-th secondary controller;

The first secondary controller establishes a binding relationship with the at least one service function unit, including:

Determining, by the first secondary controller, the service function unit to be bound according to the description information of the service function unit to be bound by the first secondary controller that is carried in the binding trigger message, the first secondary controller Establish a binding relationship with the service function unit to be bound.
The method according to claim 14 or 15, wherein the description information of each service function unit includes a service function name corresponding to the service function unit, a forwarding plane identifier corresponding to the service function unit, the forwarding plane type, Each of the jumpable service function unit information corresponding to the service function unit, wherein each of the jumpable service function unit information includes a service function name of the jumpable service function unit and a jump corresponding to the jumpable service function unit instruction;

When each service function unit refers to a flow table group, the forwarding plane identifier corresponding to the service function unit is an identifier of the switch, and the forwarding plane type indicates that the switch is a switch supporting a flow table group;

When each service function unit refers to a logical switch, the forwarding plane corresponding to the service function unit is identified as an identifier of the corresponding logical switch, and the forwarding plane type indicates that the switch is a switch that does not support the flow table group.
The method according to any one of claims 12 to 16, wherein after the first secondary controller receives the service flow start message sent by the primary controller, the method further includes:

Receiving, by the first secondary controller, a service flow suspension message sent by the primary controller;

The first secondary controller receives the new service function unit notification message sent by the primary controller, and the newly added service function unit notification message is used to indicate that the first secondary controller and the newly added service function unit are established. Binding relationship

Establishing a binding relationship between the first secondary controller and the newly added service function unit;

Sending, by the first secondary controller, a binding success message to the primary controller;

The first secondary controller receives a service flow recovery message sent by the primary controller.
The method of claim 17, wherein before the first secondary controller receives the service flow suspension message sent by the primary controller, the method further includes:

The first secondary controller sends a new service function unit request message to the primary controller, where the newly added service function unit request message carries the identifier of the service flow and the service function name of the newly added service function unit. And the newly added service function unit includes indication information of the flow table;
The method according to any one of claims 14 to 18, further comprising: after the first secondary controller receives the service flow start message sent by the primary controller,

Receiving, by the first secondary controller, a service flow suspension message sent by the primary controller;

The first secondary controller receives a service function unit unbinding notification message sent by the primary controller, where the service function unit unbinding notification message is used to indicate that the first secondary controller needs to be unbound. The business function unit unbinds the relationship;

The first secondary controller cancels the binding relationship with the service function unit that needs to be unbound;

The first secondary controller sends an unbinding success message to the primary controller.
The method of claim 19, after the first secondary controller receives the service flow suspension message sent by the primary controller, further comprising:

The first secondary controller sends a service function unit unbinding request message to the main controller, where the service function unit unbinding request message carries the service function name and the service function unit of the service function unit that needs to be unbound. The identification of the business process.
A multi-controller cooperation device, comprising:

a transceiver unit, configured to send a binding trigger message to each of the at least one secondary controller, where the binding trigger message sent by the ith secondary controller is used to trigger the ith secondary controller Establishing a binding relationship with the service function unit in each service function unit constituting the business process, where each service function unit constituting the business process is deployed by the device as a switch;

And receiving, by the each secondary controller, a binding success message, where the binding success message is used to notify the device that the secondary controller is successfully bound to the at least one service function unit;

a processing unit, configured to send, according to the received binding success message, each service function unit constituting the service flow, to the at least one secondary controller and the switch, respectively, by using the transceiver unit Process start message.
The device of claim 21, wherein each business function unit is a A flow table group or a logical switch, each business function unit corresponding to a business function.
The device according to claim 21 or 22, wherein the binding trigger message sent by the i-th secondary controller carries an identifier of the service flow and a description of each service function unit constituting the service flow. information.
The device according to claim 21 or 22, wherein the binding trigger message sent by the i-th secondary controller carries an identifier of the service flow and a description of each service function unit constituting the service flow. Information and a service function name corresponding to the service function unit bound to the i-th secondary controller;

Or the binding trigger message sent by the ith secondary controller carries the identifier of the service flow and the description information of the service function unit to be bound by the ith secondary controller.
The device according to claim 23 or 24, wherein the description information of each service function unit includes a service function name corresponding to the service function unit, a forwarding plane identifier corresponding to the service function unit, the forwarding plane type, Each of the jumpable service function unit information corresponding to the service function unit, wherein each of the jumpable service function unit information includes a service function name of the jumpable service function unit and a jump corresponding to the jumpable service function unit instruction;

When each service function unit refers to a flow table group, the forwarding plane identifier corresponding to the service function unit is an identifier of the switch, and the forwarding plane type indicates that the switch is a switch supporting a flow table group;

When each service function unit refers to a logical switch, the forwarding plane corresponding to the service function unit is identified as an identifier of the corresponding logical switch, and the forwarding plane type indicates that the switch is a switch that does not support the flow table group.
The device according to any one of claims 21 to 25, wherein after the service flow start message is sent to the at least one secondary controller and the switch, the processing unit is further configured to:

Transmitting, by the transceiver unit, a service flow suspension message to the at least one secondary controller and the switch respectively;

Adding at least one business function unit in the business process;

Transmitting, by the transceiver unit, a new service function unit notification message to at least one of the at least one secondary controller, where the newly added service function unit notification message is used to indicate the at least one secondary controller Establishing a binding relationship between the at least one secondary controller and the corresponding newly added service function unit;

Receiving, by the transceiver unit, a binding success message sent by at least one secondary controller of the at least one secondary controller;

Transmitting, by the transceiver unit, a service flow recovery message to the at least one secondary controller and the switch, respectively.
The device according to claim 26, wherein the processing unit is further configured to: before transmitting the service flow suspension message to the at least one secondary controller and the switch, respectively:

Receiving, by the transceiver unit, a new service function unit request message sent by the first secondary controller, where the newly added service function unit request message carries the identifier of the service flow, and the service function of the newly added service function unit The name and the new service function unit include indication information of the flow table.
The device according to any one of claims 21 to 27, wherein after the service flow start message is sent to the at least one secondary controller and the switch, the processing unit is further configured to:

Transmitting, by the transceiver unit, a service flow suspension message to the at least one secondary controller and the switch respectively;

Transmitting, by the transceiver unit, a service function unit unbinding notification message to the second secondary controller, where the service function unit unbinding notification message is used to indicate the second secondary controller and the service function unit that needs to be unbound Unbinding the relationship, wherein the second secondary controller is any one of the at least one secondary controller;

Receiving, by the transceiver unit, an unbinding success message sent by the second secondary controller.
The device according to claim 28, wherein the processing unit is further configured to: before transmitting the service flow suspension message to the at least one secondary controller and the switch, respectively:

Receiving, by the transceiver unit, a service function unit sent by the second secondary controller to unbind And the service function unit unbinding request message carries the service function name of the service function unit that needs to be unbound and the identifier of the service process.
The device according to claim 28 or 29, wherein after receiving the unbinding success message sent by the second secondary controller, the processing unit is further configured to:

Transmitting, by the transceiver unit, a service function unit designation message to the third secondary controller, where the service function unit designation message carries the description information of the service function unit that needs to be unbound and the identifier of the service process, where the service The function unit designation message is used to indicate that the third secondary controller establishes a binding relationship with the service function unit that needs to be unbound, and the third secondary controller is any one of the at least one secondary controller. Receiving, by the transceiver unit, a binding success message sent by the third secondary controller; or deleting the service function unit that needs to be unbound in the service process;

Transmitting, by the transceiver unit, a service flow recovery message to the at least one secondary controller and the switch, respectively.
The device according to claim 28 or 29, wherein after receiving the unbinding success message sent by the second secondary controller, the processing unit is further configured to:

When it is determined that each business function unit constituting the business process has been unbound, the business process is deleted.
A multi-controller cooperation device, comprising:

a transceiver unit, configured to receive a binding trigger message sent by the main controller, where the binding triggering message is used to trigger a binding relationship between the device and a service function unit in each service function unit that constitutes a service process, where The various service functional units constituting the business process are deployed by the primary controller for the switch;

a processing unit, configured to establish a binding relationship with at least one service function unit;

The transceiver unit is further configured to send a binding success message to the main controller, where the binding success message is used to notify the main controller that the device is successfully bound to the at least one service function unit;

And receiving a business process startup message sent by the primary controller.
The device according to claim 32, wherein each service function unit refers to a flow table group or a logical switch, and each service function unit corresponds to a service function.
The device according to claim 32 or 33, wherein the binding trigger message carries an identifier of the service flow and description information of each service function unit constituting the service flow;

Before the binding relationship is established with the at least one service function unit, the processing unit is further configured to:

Determining at least one service function unit as a service function unit to be bound according to description information of each service function unit constituting the service process.
The device according to claim 32 or 33, wherein the binding trigger message carries an identifier of the service flow, description information of each service function unit constituting the service flow, and binding required by the device. The name of the business function corresponding to the business function unit;

When a binding relationship is established with at least one service function unit, the processing unit is configured to:

And determining a to-be-bound service function unit according to the service function name corresponding to the service function unit to be bound to the device, and establishing a binding relationship with the to-be-bound service function unit.

Or the binding trigger message sent by the ith secondary controller carries the identifier of the service flow and the description information of the service function unit to be bound by the ith secondary controller;

When a binding relationship is established with at least one service function unit, the processing unit is configured to:

Determining, according to the description information of the service function unit to be bound to the device that is carried in the binding trigger message, the service function unit to be bound, and establishing a binding relationship with the service function unit to be bound.
The device according to claim 34 or 35, wherein the description information of each service function unit includes a service function name corresponding to the service function unit, a forwarding plane identifier corresponding to the service function unit, the forwarding plane type, Each of the jumpable service function unit information corresponding to the service function unit, wherein each of the jumpable service function unit information includes a service function name of the jumpable service function unit and a jump corresponding to the jumpable service function unit instruction;

When each service function unit refers to a flow table group, the forwarding plane identifier corresponding to the service function unit is an identifier of the switch, and the forwarding plane type indicates that the exchange is to support the exchange of the flow table group. machine;

When each service function unit refers to a logical switch, the forwarding plane corresponding to the service function unit is identified as an identifier of the corresponding logical switch, and the forwarding plane type indicates that the switch is a switch that does not support the flow table group.
The device according to any one of claims 32 to 36, wherein after receiving the service flow start message sent by the main controller, the processing unit is further configured to:

Receiving, by the transceiver unit, a service flow suspension message sent by the primary controller;

Receiving, by the transceiver unit, the sending, by the main controller, a new service function unit notification message, where the newly added service function unit notification message is used to indicate that the device establishes a binding relationship with the newly added service function unit;

Establishing a binding relationship with the newly added service function unit;

Sending, by the transceiver unit, a binding success message to the primary controller;

Receiving, by the transceiver unit, a service flow recovery message sent by the primary controller.
The device according to any one of claims 37, wherein the processing unit is further configured to: before receiving the service flow suspension message sent by the main controller:

Sending, by the transceiver unit, a new service function unit request message to the main controller, where the newly added service function unit request message carries an identifier of the service process, a service function name and a location of the newly added service function unit. The newly added service function unit includes indication information of the flow table;
The device according to any one of claims 32 to 38, wherein after receiving the service flow start message sent by the main controller, the processing unit is further configured to:

Receiving, by the transceiver unit, a service flow suspension message sent by the primary controller;

Receiving, by the transceiver unit, a service function unit unbinding notification message sent by the main controller, where the service function unit unbinding notification message is used to indicate that the device is unbound from a service function unit that needs to be unbound. relationship;

Unbinding the business function unit that needs to be unbound;

An unbinding success message is sent to the primary controller by the transceiver unit.
The apparatus according to claim 39, wherein said main controller transmits After the business process pause message, the processing unit is further configured to:

Sending, by the transceiver unit, a service function unit unbinding request message to the main controller, where the service function unit unbinding request message carries the service function name of the service function unit that needs to be unbound and the service The identity of the process.