WO2014179923A1

WO2014179923A1 - Network configuration method, device and system based on sdn

Info

Publication number: WO2014179923A1
Application number: PCT/CN2013/075198
Authority: WO
Inventors: 熊春山; 余芳
Original assignee: 华为技术有限公司
Priority date: 2013-05-06
Filing date: 2013-05-06
Publication date: 2014-11-13
Also published as: CN104429028A; CN104429028B

Abstract

The embodiments of the present invention provide a network configuration method, device and system based on an SDN. The network configuration method based on an SDN comprises: obtaining an allocation result of allocating a controller to a node according to load status information about at least one SDN controller in a controller pool, wherein the allocation result comprises a master controller allocated to the node, and the master controller is an SDN controller in the controller pool; according to the allocation result, sending a node type of the node to the master controller so that the master controller configures a control rule corresponding to the node type for the node according to the node type and sends the control rule to the node. Since a master control device can automatically allocate a master controller and a slave controller to a node according to load conditions of each SDN controller, automatic configuration of a control plane of an SDN on a data plane is realized, thereby improving the configuration efficiency and being capable of well satisfying the network performance requirements of the SDN.

Description

SDN-based network configuration method, device and system

Technical field

The embodiments of the present invention relate to communication technologies, and in particular, to an SDN-based network configuration method, apparatus, and system.

Background technique

Software Defined Network (SDN) is a new type of network architecture. SDN separates the control functions of network devices from network devices and configures network devices with central control nodes. By separating the control plane from the data plane, flexible management and control of network devices is possible.

In SDN, a device for controlling a network device at a control plane is called an SDN controller (Controller); a network device located at a data plane is called a node. In a network for data forwarding, a node can be a router or a switch. In a telecommunication network, a node can be an Authentication Authorization Accounting (AAA) server, a device supporting Dynamic Host Configuration Protocol (DHCP), and a network address translation (NAT). The device, the 3rd Generation Partnership Project (3GPP), an evolved Node B (eNB), a Polic Ic and Charging Rules Function (PCRF), and the like.

Each SDN controller can act as a Master Controller or a Slave Controller, and each node can communicate with multiple SDN controllers. For a single node, only one of the multiple SDN controllers to which it communicates can be the primary controller of the node, and the other one or more SDN controllers can act as the slave controllers of the node. A single SDN controller can act as the primary controller for one or more nodes. The SDN controller that is the primary controller of a node can also act as a slave controller for other nodes. The main controller is used to control the node, and the slave controller is used as the standby controller of the main controller. It is used temporarily as the main controller when the main controller is overloaded or faulty. In addition, the slave controller can also The main controller acts as an information backup. Since the SDN mainly uses the main controller to control and manage the nodes, when multiple nodes communicate with the main controller, the performance requirements of the main controller are high. In such cases, the network performance of the SDN will be limited by the performance of the host controller itself. Summary of the invention

A first aspect of the embodiments of the present invention provides an SDN-based network configuration method, including:

Obtaining, according to load state information of at least one SDN controller in the controller pool, an allocation result of assigning a controller to the node, where the allocation result includes a primary controller allocated to the node, and the primary controller is the controller SDN controller in the pool;

Sending a node type of the node to the main controller, so that the main controller acquires a control rule corresponding to the node type according to the node type, and sends the control rule to the node .

In conjunction with the SDN-based network configuration method provided by the first aspect, in a first possible implementation manner, the allocation result further includes a slave controller allocated to the node;

Correspondingly, the method further includes:

Sending the node identifier of the node to the slave controller, so that the slave controller obtains a control rule corresponding to the node identifier from the master controller or a node corresponding to the node identifier.

In conjunction with the SDN-based network configuration method provided by the first aspect, in a second possible implementation manner, the method further includes:

Transmitting the allocation result to the node, so that the node sends request information carrying the node type to the primary controller according to the allocation result, so that the primary controller is configured according to the node Type, configuring a control rule corresponding to the node type for the node, and sending the control rule to the node.

With reference to the first aspect or the first to the second possible implementation manners, in a third possible implementation manner, the obtaining, by using the load state information of the at least one SDN controller in the controller pool, obtaining a controller for the node The distribution results include:

And respectively configuring weights for the at least one SDN controller according to load state information of the at least one SDN controller; Obtaining an allocation result of the controller for the node according to the weight of the at least one SDN controller.

With reference to the first aspect or the first to the second possible implementation manners, in a fourth possible implementation manner, the method further includes:

Receiving load status information respectively sent by the at least one SDN controller; or separately acquiring load status information from the at least one SDN controller.

In combination with the first aspect or the first to the second possible implementation manners, in a fifth possible implementation manner, the method further includes:

Receiving a node type sent by the node; or

Get the node type of the node from the database.

A second aspect of the embodiments of the present invention provides an SDN-based network configuration method, including:

Receiving a control rule sent by the main controller, where the control rule is a rule for controlling, corresponding to the node type, obtained by the main controller according to a node type, where the main controller is a controller according to the controller The SDN controller selected by the load status information of at least one SDN controller in the pool;

Configure according to the control rules.

In conjunction with the SDN-based network configuration method provided by the second aspect, in a first possible implementation manner, the method further includes:

Receiving an allocation result sent by the main control device, where the allocation result includes the allocated primary controller;

And transmitting, according to the allocation result, request information carrying the node type to the main controller, so that the main controller obtains a control rule corresponding to the node type according to the request information.

With reference to the second aspect or the first possible implementation manner, in a second possible implementation manner, the method further includes:

Transmitting the node type to the master device to cause the master device to send the node type to the master controller.

A third aspect of the embodiments of the present invention provides an SDN-based network configuration method, including: The master controller acquires a control rule corresponding to the node type according to the node type, where the node type is received from the master device, or is obtained from a database, and the master controller is An SDN controller in the controller pool, wherein the main controller is an SDN controller allocated to the node as a main controller according to load status information of at least one SDN controller in the controller pool ;

The primary controller sends the control rule to the node to cause the node to configure according to the control rule.

In conjunction with the SDN-based network configuration method provided by the third aspect, in a first possible implementation manner, the master controller acquires, according to the node type, a control rule corresponding to the node type, including:

The main controller receives request information that is sent by the node and carries the type of the node; and the main controller configures, according to the request information, a control rule corresponding to the node type for the node.

With reference to the third aspect or the first possible implementation manner, in a second possible implementation manner, the method further includes:

The main controller sends the load status information to the main control device, so that the main control device obtains an allocation result of the controller for the node according to load status information of at least one SDN controller in the controller pool. The allocation result includes a primary controller and/or a secondary controller assigned to the node.

A fourth aspect of the embodiments of the present invention provides an SDN-based network configuration method, including:

Obtaining a control rule corresponding to the node identifier from a node corresponding to the primary controller or the node identifier;

The node identifier is identifier information of the node that is received from the master device; the control rule is a rule for control that is obtained by the master controller according to the node type and corresponding to the node type; The main controller is an SDN controller selected by the main control device according to load status information of at least one SDN controller in the controller pool.

In conjunction with the SDN-based network configuration method provided by the fourth aspect, in a first possible implementation manner, the method further includes:

Transmitting load status information to the main control device for the main control device to be based on the controller The load status information of at least one SDN controller in the pool obtains an allocation result for the node allocation controller, the allocation result including a primary controller and/or a slave controller assigned to the node.

A fifth aspect of the embodiments of the present invention provides a main control device, including:

a processing unit, configured to obtain, according to load state information of at least one SDN controller in the controller pool, an allocation result of the controller for the node, where the allocation result includes a primary controller allocated to the node, the primary controller Is the SDN controller in the controller pool;

a sending unit, configured to send, to the main controller, a node type of the node, where the main controller acquires a control rule corresponding to the node type according to the node type, and the control rule is Sent to the node.

With reference to the main control device provided by the fifth aspect, in a first possible implementation, the allocation result obtained by the processing unit further includes a slave controller allocated to the node;

Correspondingly, the sending unit is further configured to:

In conjunction with the master device provided in the fifth aspect, in a second possible implementation manner, the sending unit is further configured to:

In combination with the fifth aspect or the first to the second possible implementation manners, in a third possible implementation manner, the processing unit is further configured to:

And configuring, according to the load status information of the at least one SDN controller, a weight for the at least one SDN controller; and obtaining, according to the weight of the at least one SDN controller, an allocation result of the controller for the node.

With reference to the fifth aspect or the first to the second possible implementation manners, in the fourth possible implementation manner, the master control device further includes:

An acquiring unit, configured to receive a load status message sent by the at least one SDN controller Or acquiring load status information separately from the at least one SDN controller.

With reference to the fifth aspect or the first to the second possible implementation manners, in the fifth possible implementation manner, the acquiring unit is further configured to:

Receiving a node type sent by the node; or obtaining a node type of the node from a database.

A sixth aspect of the embodiments of the present invention provides a node, including:

a receiving unit, configured to receive a control rule sent by the main controller, where the control rule is a rule for controlling, corresponding to the node type, obtained by the main controller according to a node type, where the main controller is The SDN controller selected by the control device according to load status information of at least one SDN controller in the controller pool;

a configuration unit, configured to perform configuration according to the control rule.

In conjunction with the node provided by the sixth aspect, in a first possible implementation, the receiving unit is further configured to:

Correspondingly, the node further includes:

a sending unit, configured to send request information carrying the node type to the primary controller according to the allocation result, so that the primary controller obtains a control rule corresponding to the node type according to the request information. .

In conjunction with the sixth aspect or the first possible implementation, in a second possible implementation, the sending unit is further configured to:

A seventh aspect of the embodiments of the present invention provides a host controller, including:

a processing unit, configured to acquire, according to a node type, a control rule corresponding to the node type, where the node type is received from a master device, or a type of the node acquired from a database, the master control The controller is an SDN controller in the controller pool, and the master controller is an SDN assigned to the node as a primary controller according to load status information of at least one SDN controller in the controller pool. Controller

a sending unit, configured to send the control rule to the node, so that the node is configured according to The control rules are configured.

In conjunction with the primary controller provided in the seventh aspect, in a first possible implementation, the processing unit is further configured to:

Receiving request information that is sent by the node and carrying the type of the node;

Based on the request information, a control rule corresponding to the node type is configured for the node.

With reference to the seventh aspect or the first possible implementation manner, in a second possible implementation manner, the sending unit is further configured to:

Transmitting the load status information to the main control device, so that the main control device obtains an allocation result of the controller for the node according to load status information of at least one SDN controller in the controller pool, and the allocation result A master controller and/or a slave controller assigned to the node are included.

An eighth aspect of the embodiments of the present invention provides a slave controller, including:

An obtaining unit, configured to acquire, from a node corresponding to the primary controller or the node identifier, a control rule corresponding to the node identifier;

In conjunction with the slave controller provided in the eighth aspect, in a first possible implementation, the slave controller further includes:

a sending unit, configured to send load status information to the main control device, where the main control device obtains an allocation result of the controller for the node according to load status information of at least one SDN controller in the controller pool The allocation result includes a primary controller and/or a secondary controller assigned to the node.

A ninth aspect of the embodiments of the present invention provides a main control device, including:

a processor, a memory, a bus, and a communication interface; the processor, the memory, and the communication interface are connected by the bus and complete communication with each other;

The communication interface is configured to communicate with the node, the main controller, and the slave controller; the memory is configured to store a program; The processor, configured to execute the program;

The program is configured to obtain, according to load state information of at least one SDN controller in the controller pool, an allocation result of the controller for the node, where the allocation result includes a primary controller allocated to the node, where the primary The controller is an SDN controller in the controller pool;

A tenth aspect of the embodiments of the present invention provides a node, including:

The communication interface is configured to be in communication with the main control device, the main controller, and the slave controller; and configured to receive a control rule sent by the main controller, where the control rule is obtained by the main controller according to the node type, a rule for control corresponding to the node type, the main controller is an SDN controller selected by the master device according to load state information of at least one SDN controller in the controller pool;

The memory is configured to store a program;

The processor, configured to execute the program;

The program is configured to be configured according to the control rule.

An eleventh aspect of the embodiments of the present invention provides a main controller, including:

The communication interface is configured to be in communication with the master device, the node, and the slave controller; the memory is configured to store a program;

The processor, configured to execute the program;

The program is configured to obtain, according to a node type, a control rule corresponding to the node type, where the node type is received from a master device, or a type of the node acquired from a database, The main controller is an SDN controller in the controller pool, and the main controller is assigned to the node as a main controller according to load status information of at least one SDN controller in the controller pool. SDN controller;

Sending the control rule to the node, so that the node enters according to the control rule Line configuration.

A twelfth aspect of the embodiments of the present invention provides a slave controller, including: a processor, a memory, a bus, and a communication interface; the processor, the memory, and the communication interface are connected and completed through the bus Communication with each other;

The communication interface is configured to be in communication with the main control device, the node, and the main controller; the memory is configured to store a program;

The processor, configured to execute the program;

The program is configured to obtain, from a node corresponding to the primary controller or the node identifier, a control rule corresponding to the node identifier;

A thirteenth aspect of the embodiments of the present invention provides an SDN-based communication system, including the foregoing main control device, at least one node, at least one main controller, and at least one slave controller; A node, a communication connection between the primary controller and the slave controller.

The SDN-based network configuration method, device, and system provided by the embodiment of the present invention obtain the allocation result of the controller for the node according to the load state information of the at least one SDN controller in the controller pool, according to the distribution result. a primary controller assigned to the node, the node type of the node is sent to the primary controller, so that the primary controller can configure a control rule corresponding to the node type according to the node type, and The control rule is sent to the node, and the node can perform corresponding configuration according to the control rule. Since the main control device can automatically allocate the main controller and the slave controller to the node according to the load condition of each SDN controller, the automatic control of the data plane by the control plane of the SDN is realized, the configuration efficiency is improved, and the configuration can be satisfactorily satisfied. SDN network performance requirements. DRAWINGS

FIG. 1 is a schematic structural diagram of an SDN-based network configuration method according to an embodiment of the present invention; FIG. 2 is a schematic structural diagram of another SDN-based network configuration method according to an embodiment of the present invention; Figure

FIG. 3 is a schematic structural diagram of a main control device according to an embodiment of the present disclosure;

FIG. 3b is a schematic structural diagram of another main control device according to an embodiment of the present disclosure;

FIG. 3c is a schematic structural diagram of still another main control device according to an embodiment of the present disclosure;

4a is a schematic structural diagram of a node according to an embodiment of the present invention;

FIG. 4b is a schematic structural diagram of another node according to an embodiment of the present disclosure;

4c is a schematic structural diagram of still another node according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a main controller according to an embodiment of the present disclosure;

FIG. 5b is a schematic structural diagram of another main controller according to an embodiment of the present disclosure;

6a is a schematic structural diagram of a slave controller according to an embodiment of the present invention;

Figure 6b is a schematic structural diagram of another slave controller according to an embodiment of the present invention; Figure 6c is a schematic structural diagram of another slave controller according to an embodiment of the present invention; Figure 7 is a SDN-based communication system according to an embodiment of the present invention; Schematic diagram of the structure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS In order to solve the problem that the network performance of the SDN is limited by the performance of the main controller itself, the embodiments of the present invention utilize a primary control device and at least one SDN controller to form a controller pool on the control plane of the SDN. (controller pool). The SDN controllers in the controller pool may also be referred to as common controllers with respect to the master device. By controlling the SDN controllers in the controller pool by the master device, the SDN controllers can work in coordination to achieve load balancing.

Each SDN controller in the controller pool is in communication with the master device; each SDN controller is in communication with each node in the data plane; the master device is in communication with each node in the data plane.

The embodiments of the present invention provide an SDN-based network configuration method. For other types of networks or systems in which the control plane is separated from the data plane, the method described in the embodiments of the present invention can also be configured.

The main control device in the embodiments of the present invention may be an independent device, or may be a functional module disposed on other devices in the control plane; the node may be a router, a switch, an AAA server, or a device supporting DHCP. , NAT device, eNB or PCRF, etc.; the master control The master control ler and the slave controller are the SDN controllers in the controller pool. The specific SDN controller works as the master controller or as the slave controller. The control device is configured according to a preset policy.

FIG. 1 is a schematic structural diagram of an SDN-based network configuration method according to an embodiment of the present invention, including:

101. The main control device obtains an allocation result of the controller for the node according to load state information of at least one SDN controller in the controller pool. The allocation result includes a primary controller allocated to the node, and the primary controller is an SDN controller in the controller pool.

Specifically, the main control device acquires load status information of each SDN controller in the controller pool. In various embodiments of the present invention, the load status information includes information such as resource utilization, memory usage, and remaining storage capacity of a central processing unit (CPU).

After collecting the load status information of each SDN controller, the master device can allocate the master controller to the nodes from the SDN controllers of the controller pool according to the principle of load balancing.

It should be noted that, since the steps of the main control device for allocating the main controller to the node are performed separately for each node, the embodiments of the present invention are described by taking only one node as an example.

Since the SDN controller as the primary controller of the node needs to perform more data processing and operations, it is preferred to select a lightly loaded SDN controller among the SDN controllers connected to the node. Wherein, the method for determining the load severity of the SDN controller based on the load status information may adopt an implementation similar to that in the prior art.

After determining the weight of each SDN controller, the main control unit assigns a main controller to the node according to actual needs. The identification information of the primary controller assigned to the node is used as the allocation result. Accordingly, after receiving the allocation result, the other device can know which SDN controller is the primary controller according to the identification information in the allocation result.

102. The master device sends the node ID, the node type, and the role of the controller of the node to the primary controller.

Specifically, the main controller serving the node is determined by the main control device, and the specific control performed on the node is performed by the main controller. Since the main controller needs to control the node according to the node type of the node, the control rule for controlling the node is obtained. Therefore, the master device sends the node type of the node to the node information of the primary controller in the allocation result. The main controller corresponding to the identification information of the main controller.

In order to make the main controller know that it is assigned as the main controller of the node, the main control device will notify the main controller of the node identifier of the node while transmitting the node type of the node to the main controller. And the role information that the main controller itself is assigned. Thus, the master controller can know which node it is the master controller for, and the node type of the node.

Since the nodes can be multiple devices as described above, and the control rules for controlling different devices may be different, multiple programs may be preset in the main controller, and corresponding control rules are adopted for different devices. The node type of a node can be the device type of the node, or other information.

103. The main controller acquires a control rule corresponding to the node type according to the node type, and sends the control rule to the node.

Specifically, after receiving the node type sent by the master device, the master controller configures a control rule corresponding to the node type for the node. The correspondence between the node type and the control rule may be preset in the main controller; or may be preset in the database, and accordingly, the main controller may perform a search in the database according to the node type, thereby obtaining the node The control rule corresponding to the type.

After obtaining the control rule corresponding to the node type, the main controller sends the control rule to the node. Since the main controller receives the node identifier of the node while receiving the node type, the main controller can send the control rule to the node corresponding to the node identifier according to the node identifier. The node can be configured according to the control rule, thereby implementing the network configuration of the control plane to the data plane.

The SDN-based network configuration method provided by the embodiment of the present invention obtains an allocation result of a controller for a node according to load state information of at least one SDN controller in the controller pool, and the node included in the allocation result is the node. The assigned primary controller sends the node type of the node to the primary controller, so that the primary controller can configure a control rule corresponding to the node type according to the node type, and the control rule Sent to the node, the node can be configured accordingly according to the control rule. Since the main control device can automatically allocate the main controller and the subordinate controller to the node according to the load condition of each SDN controller, the automatic control of the data plane by the control plane of the SDN is realized, the configuration efficiency is improved, and the configuration can be better. Meet the network performance requirements of SDN. FIG. 2 is a schematic structural diagram of another SDN-based network configuration method according to an embodiment of the present invention, including:

201. The main control device obtains an allocation result of the controller for the node according to load state information of at least one SDN controller in the controller pool. The allocation result further includes a primary controller and a secondary controller allocated to the node.

Specifically, the implementation manner described in step 101 may be included. The difference from step 101 is that after collecting the load status information of each SDN controller, the main control device not only allocates a primary controller but also a node to the node. Assign a slave controller.

Since the slave controller is used as the backup controller of the master controller, when the master device assigns the slave controller to the node, it can be connected from the node after preferentially using the lightly loaded SDN controller as the master controller. In the SDN controller, one or more SDN controllers are selected as slave controllers.

The master device can also allocate a master controller and/or a slave controller to the node according to the load balancing principle, and the specific implementation manner is as follows.

For the node that newly joins the SDN, the main control device selects the SDN controller with light load according to the load and weight of each SDN controller, and uses it as the main node of the node when it is expected that it will not be overloaded or overloaded. Controller; The master device can combine the requirements for the slave controller load and assign the number of slave controllers to each node to select the appropriate number of slave controllers for that node.

For a node that is already in SDN, when the master reassigns the primary controller for it, first check the load status of the existing slave controller of the node.

If the node has only one slave controller, and the load condition of the slave controller has not reached the overload or overload, and the slave controller is converted to the master controller of the node, no overload or overload is expected. In this case, the slave controller can be converted to the master controller of the node. Further, the master device re-assigns the other SDN controller to the node as a new slave controller, or converts the original master controller into a slave controller of the node.

If the node has multiple slave controllers, the load conditions of these slave controllers can be compared. When the above conditions are met, the SDN controller with the lightest load is used as the master controller of the node. If an existing slave controller is converted to a master controller, the original master controller can also be converted to a slave controller accordingly. If the existing slave controller of the node does not satisfy the above conditions, the master device may select the SDN controller with the lightest load from among other SDN controllers. Is the primary controller for this node. When multiple SDN controllers satisfy the above conditions and the load conditions are equivalent, the distance between the physical locations can be further considered, and the SDN controller with the closer distance from the node is selected as its main controller.

Correspondingly, the allocation result obtained by the main control device further includes identification information of the SDN controller as the slave controller, so that after receiving the allocation result, the other device may be known as the main control according to the identification information in the allocation result. Which SDN controller is the slave controller and the slave controller.

Further, the manner in which the main control device obtains the load status information of each SDN controller in the controller pool may be implemented in the following two manners.

One is that the master device receives the load status information sent by the at least one SDN controller.

Specifically, each SDN controller periodically detects the load status according to the received trigger information, forms load status information according to the detected load condition, and sends the load status information to the main control device, to The master control device can assign a master controller and/or a slave controller to the node according to the load status information of each SDN.

Alternatively, the master device obtains load status information from the at least one SDN controller.

Specifically, the master device actively obtains its own load status information from each SDN controller periodically, or according to the received trigger information, so that the node can be assigned a primary controller according to the load status information of each SDN. Or slave controller.

The load status information may include actual load conditions of the SDN controller, such as CPU resource utilization, memory usage, and remaining storage capacity, and may also include parameters for measuring the weight of the load, so that the master device according to the parameter The load and weight of the SDN controller can be known. The parameter form specifically included in the load status information may be determined according to a pre-configured communication protocol between the master device and the SDN controller.

It should be noted that, since the master device obtains the load status information of each SDN controller in the controller pool at the initial time, and periodically or irregularly learns the load status information of each SDN controller during the operation, the present invention The methods described in the embodiments may be performed periodically or irregularly, thereby dynamically selecting a more appropriate SDN controller as a primary controller for the node according to the current load and weight of each SDN controller in the controller pool. / or slave controller. Further, the method in which the main control device allocates the main controller and/or the slave controller to the node according to the load status information of each SDN controller may adopt the following implementation manner.

And the main control device separately configures a weight for the at least one SDN controller according to the load state information of the at least one SDN controller; and obtains, according to the weight of the at least one SDN controller, a controller for the node Assign results.

Specifically, after obtaining the load status information of each SDN controller, the main control device may respectively allocate corresponding weights for each SDN controller according to pre-configured rules according to the load and weight of each SDN controller. Therefore, when the main control device allocates the main controller and/or the slave controller to the node, the main control device allocates according to the weight corresponding to the SDN controller to which the node is connected, that is, selects the light load SDN controller represented by the weight. Select as the primary controller and one or more of the other SDN controllers as slave controllers.

Further, when a new SDN controller is added to the controller pool, after the SDN controller is started, its load status information is reported to the master device, and the master device sets its weight to a higher value.

The main control device increases the load of the SDN controller according to the higher weight, preferentially assigns the newly added node to the SDN controller, or preferentially when the other SDN controller is overloaded, overloaded or faulty The node served by the SDN controller in this case is transferred to the SDN controller with the higher weight. When the load of the SDN controller reaches a certain threshold, or when a new node is successfully assigned to the SDN controller, the SDN controller updates its load status information to the master device. The master device will accordingly lower its weight.

202. The master device sends the node type of the node to the primary controller, and sends the node identifier of the node to the slave controller.

Specifically, in addition to transmitting the node type of the node to the primary controller assigned to the node, the master device also sends the node identifier of the node to the slave controller assigned to the node.

Further, the method in which the master device acquires the node type of the node may adopt the following two implementation manners.

One is that the master device receives the node type sent by the node.

Specifically, the node sends its node type to the master device before the master device allocates the master controller and/or the slave controller. Accordingly, the master device receives its node type sent by the node. The other is that the master device acquires the node type of the node from the database.

Specifically, the master device acquires the node type of each node from the database before allocating the master controller and/or the slave controller to the node. The correspondence between the identification information of the node and the node type is pre-stored in the database. Different nodes can be distinguished by their respective identification information. Accordingly, the main control device can query the node type corresponding to the node identifier from the database according to the identification information of the node as the node type of the node.

203. The main controller acquires a control rule corresponding to the node type according to the node type, and sends the control rule to the node.

For details, refer to the implementation described in step 103.

Further, the master device may also send the assignment result to the node.

Specifically, after obtaining the allocation result, the main control device may further send the allocation result to the node, and accordingly, the node may learn the SDN controller as its main controller and/or the slave controller according to the received allocation result. Which SDN controllers are in the controller pool.

Before the main controller configures the control rule for the node, the node may further send request information carrying the node type to the main controller according to the allocation result, and request the main controller to configure a control rule for the node.

The main controller receives the request information that is sent by the node and carries the node type, configures a control rule corresponding to the node type for the node according to the request information, and sends the control rule to the node.

After the master controller sends the control rule to the node, the node configures according to the received control rules, thereby realizing the automatic configuration of the node.

After transmitting the control rule to the node, the main controller can also send its current load status information to the main control device, so that the main control device updates the load status information of the main controller.

204. The slave controller acquires a control rule corresponding to the node identifier from a node corresponding to the primary controller or the node identifier.

Specifically, the node identifier may be an identifier of the node (Identity), an Internet Protocol (IP) address of the node, or a Ful ly Qual ifi ed Domain Name (FQDN) of the node.

The control rules configured for the node are determined by the primary controller, and the nodes can be connected from the primary controller. The control rules configured for it are received, that is, the control controller |J is included in both the primary controller and the node. If the slave controller needs to obtain the control rule, it can be obtained from the node or the master controller according to the node identifier, so that the master controller, the slave controller, and the node include the control rules configured by the master controller for the node.

Thereby, the control rules of each node stored in the slave controller, the master controller, and the node can be made uniform. When the primary controller fails, or the connection between the node and the primary controller fails, the secondary controller can temporarily act as a backup.

FIG. 3 is a schematic structural diagram of a main control device according to an embodiment of the present invention. As shown in FIG. 3a, the main control device includes:

The processing unit 1 is configured to obtain, according to load state information of at least one SDN controller in the controller pool, an allocation result of the controller for the node, where the allocation result includes a primary controller allocated to the node, where the primary The controller is an SDN controller in the controller pool;

a sending unit 12, configured to send, to the main controller, a node type of the node, where the main controller acquires a control rule corresponding to the node type according to the node type, and the control Rules are sent to the node.

Further, the allocation result obtained by the processing unit 1 1 further includes a slave controller allocated to the node;

Correspondingly, the sending unit 12 is further configured to:

Sending the node identifier of the node to the slave controller, so that the slave controller obtains a control rule corresponding to the node identifier from the master controller or a node corresponding to the node identifier. Further, the sending unit 12 is further configured to:

Further, the processing unit 1 1 is further configured to:

FIG. 3b is a schematic structural diagram of another main control device according to an embodiment of the present invention, as shown in FIG. 3b. The main control device may further include:

The obtaining unit 13 is configured to receive load status information sent by the at least one SDN controller, respectively, or obtain load status information from the at least one SDN controller.

Further, the obtaining unit 13 is further configured to:

FIG. 3 is a schematic structural diagram of still another main control device according to an embodiment of the present invention. As shown in FIG. 3c, the main control device includes:

The processor 21, the memory 22, the bus 23, and the communication interface 24. The processor 21, the memory 22 and the communication interface 24 are connected by a bus 23 and communicate with each other.

The processor 21 may be a single-core or multi-core central processing unit (CPU), or an specific integrated circuit (ASIC), or an one configured to implement an embodiment of the present invention. Multiple integrated circuits.

The memory 22 can be a high speed RAM memory or a nonvolatile memory.

(non-volati le memory ), such as at least one disk storage.

The communication interface 24 is for communicating with a node, a master controller, and/or a slave controller. The memory 22 is used to store the program 221. Specifically, the program 221 may include program code, where the program code includes computer operation instructions.

The processor 21 runs the program 221 to execute:

Specifically, the method for performing the SDN-based network configuration by the main control device provided by the embodiment of the present invention may be referred to the implementation manners in the foregoing corresponding method embodiments, and details are not described herein again.

The master control device provided by the embodiment of the present invention obtains an allocation result of the controller for the node according to the load state information of the at least one SDN controller in the controller pool, according to the distribution node. The primary controller allocated for the node is sent to the primary controller, so that the primary controller can configure the node corresponding to the node type according to the node type. The rule sends the control rule to the node, and the node can perform corresponding configuration according to the control rule. Since the main control device can automatically allocate the main controller and the subordinate controller to the node according to the load condition of each SDN controller, the automatic control of the data plane by the control plane of the SDN is realized, the configuration efficiency is improved, and the configuration can be better. Meet the network performance requirements of SDN.

4a is a schematic structural diagram of a node according to an embodiment of the present invention. As shown in FIG. 4a, the node includes:

The receiving unit 31 is configured to receive a control rule sent by the main controller, where the control rule is a rule for control that is obtained by the main controller according to the node type and corresponding to the node type, where the main control is The SDN controller selected by the master device according to load status information of at least one SDN controller in the controller pool;

The configuration unit 32 is configured to perform according to the control rule.

FIG. 4b is a schematic structural diagram of another node according to an embodiment of the present invention. As shown in FIG. 4b, the receiving unit 31 is further configured to:

Correspondingly, the node may further include:

The sending unit 33 is configured to send, according to the allocation result, request information carrying the node type to the main controller, so that the main controller obtains control corresponding to the node type according to the request information. rule.

Further, the sending unit 33 is further configured to:

4c is a schematic structural diagram of another node according to an embodiment of the present invention. As shown in FIG. 4c, the node includes:

The processor 41, the memory 42, the bus 43, and the communication interface 44. The processor 41, the memory 42 and the communication interface 44 are connected by a bus 43 and communicate with each other.

Processor 41 may be a single core or multi-core central processing unit (Central Process ing Unit, CPU), or an Specific Integrated Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

The memory 42 may be a high speed RAM memory or a non-volatile memory such as at least one disk memory.

The communication interface 44 is communicatively coupled to the main control device, the main controller, and/or the slave controller, and configured to receive a control rule sent by the main controller, where the control rule is obtained by the main controller according to the node type, and The rule for controlling the node type, the master controller is an SDN controller selected by the master device according to load state information of at least one SDN controller in the controller pool.

The memory 42 is used to store the program 421. Specifically, program code 421 may include program code, and the program code includes computer operation instructions.

The processor 41 runs the program 421 to execute:

Configure according to the control rules.

Specifically, the method for performing the SDN-based network configuration of the node provided by the embodiment of the present invention may be referred to the implementation manner described in the foregoing method embodiment, and details are not described herein again.

The node provided by the embodiment of the present invention receives the control rule configured by the main controller, and performs corresponding configuration according to the control rule, where the control rule is configured by the main controller according to the node type of the node, because the main control device can be configured according to The load status of each SDN controller automatically assigns the primary controller and the slave controller to the node, which realizes the automatic configuration of the data plane by the control plane of the SDN, improves the efficiency of the configuration, and can better meet the network performance requirements of the SDN. .

FIG. 5a is a schematic structural diagram of a main controller according to an embodiment of the present invention. As shown in FIG. 5a, the main controller includes:

The processing unit 51 is configured to acquire, according to the node type, a control rule corresponding to the node type, where the node type is received from the master device, or the type of the node acquired from the database, the master The controller is an SDN controller in the controller pool, and the master controller is assigned to the node as a primary controller according to load status information of at least one SDN controller in the controller pool. SDN controller;

The sending unit 52 is configured to send the control rule to the node, so that the node is configured according to the control rule. Further, the processing unit 51 is further configured to:

And receiving, by the node, request information that carries the node type; and, according to the request information, configuring a control rule corresponding to the node type for the node.

Further, the sending unit 52 is further configured to:

FIG. 5b is a schematic structural diagram of another main controller according to an embodiment of the present invention. As shown in FIG. 5b, the main controller includes:

The processor 61, the memory 62, the bus 63, and the communication interface 64. The processor 61, the memory 62 and the communication interface 64 are connected by a bus 63 and communicate with each other.

The processor 61 may be a single-core or multi-core central processing unit (CPU), or an specific integrated circuit (ASIC), or one configured to implement an embodiment of the present invention. Multiple integrated circuits.

The memory 62 may be a high speed RAM memory or a non-volatile memory such as at least one disk memory.

The communication interface 64 is for communicating with a master device, a node, and/or a slave controller. The memory 62 is used to store the program 621. Specifically, the program 621 may include program code, and the program code includes a computer operation instruction.

The processor 61 runs the program 621 to execute:

Obtaining, according to the node type, a control rule corresponding to the node type, where the node type is received from a master device, or a type of the node acquired from a database, where the primary controller is a controller pool In the SDN controller, the main controller is an SDN controller allocated to the node as a main controller according to load status information of at least one SDN controller in the controller pool;

The control rules are sent to the node to cause the node to configure according to the control rules.

Specifically, the main controller provided by the embodiment of the present invention performs the SDN-based network configuration. For the method, refer to the implementation manners described in the foregoing method embodiments, and details are not described herein again. The main controller provided by the embodiment of the present invention configures a control rule corresponding to the node type according to the node type, and sends the control rule to the node, and the node can perform corresponding configuration according to the control rule. Since the main control device can automatically allocate the main controller and the subordinate controller to the node according to the load condition of each SDN controller, the automatic control of the data plane by the control plane of the SDN is realized, the configuration efficiency is improved, and the configuration can be better. Meet the network performance requirements of SDN.

6a is a schematic structural diagram of a slave controller according to an embodiment of the present invention. As shown in FIG. 6a, the slave controller includes:

The obtaining unit 71 is configured to obtain, from the node corresponding to the primary controller or the node identifier, a control rule corresponding to the node identifier.

FIG. 6b is a schematic structural diagram of another slave controller according to an embodiment of the present invention. As shown in FIG. 6b, the slave controller may further include:

The sending unit 72 is configured to send load status information to the main control device, where the main control device obtains an allocation for the node allocation controller according to load status information of at least one SDN controller in the controller pool. As a result, the assignment result includes a primary controller and/or a slave controller assigned to the node.

FIG. 6c is a schematic structural diagram of still another slave controller according to an embodiment of the present invention. As shown in FIG. 6c, the slave controller includes:

The processor 81, the memory 82, the bus 83, and the communication interface 84. The processor 81, the memory 82, and the communication interface 84 are connected by a bus 83 and communicate with each other.

The processor 81 may be a single core or multi-core central processing unit (CPU), or an Specific Integrated Integrated Circuit (ASIC), or one or more configured to implement the embodiments of the present invention. integrated circuit.

The memory 82 can be a high speed RAM memory or a nonvolatile memory. (non-volati le memory ), such as at least one disk storage.

The communication interface 84 is for communicating with a master device, a node, and/or a host controller. The memory 82 is used to store the program 821. Specifically, the program 821 may include program code, and the program code includes computer operation instructions.

The processor 81 runs the program 821 to execute:

Specifically, the method for performing the SDN-based network configuration by the slave controller provided by the embodiment of the present invention may be referred to the implementation manners in the foregoing corresponding method embodiments, and details are not described herein again.

The slave controller provided by the embodiment of the present invention acquires a control rule corresponding to the node identifier from a node corresponding to the node identifier or from the master controller, and enables each of the slave controller, the master controller, and the node to be stored. The control rules of the nodes are consistent. When the primary controller fails, or the connection between the node and the primary controller fails, the secondary controller can temporarily play the role of backup.

FIG. 7 is a schematic structural diagram of an SDN-based communication system according to an embodiment of the present invention. As shown in FIG. 7, the communication system includes:

Main control device 1, at least one node 2, at least one main controller 3 and at least one slave controller 4;

The main control device 1, the node 2, the main controller 3 and the slave controller 4 are in communication connection.

Specifically, the method for performing the SDN-based network configuration in the SDN-based communication system provided by the embodiment of the present invention can be referred to the implementation manners in the foregoing corresponding method embodiments, and details are not described herein again.

The following describes an SDN-based communication system by way of example.

The main control device coordinates the control and/or service authority of the SDN controller in the controller pool according to the load balancing principle, and maintains the load status information of the SDN controller in the controller pool, such as the CPU. Resource utilization, memory usage, and remaining storage capacity. The master device can also maintain the topology relationship between the SDN controller and the node.

When the SDN controller is the primary controller for some nodes, the control rules are configured for the nodes based on information obtained from the topology database and the policy database.

The topology database includes a controller-related topology information database and a node-related topology information database.

The controller-related topology information database maintains topology location information related to each SDN controller in the controller pool, including topology location information of the SDN controller and predefined type information. The topological location information of the SDN controller includes: Internet Protocol version 4 (IPv4) address, Internet Protocol version 6, IPv6 address or FQDN of the SDN controller. The predefined type information of the SDN controller is used to distinguish the information of the SDN controller from the master device. That is to say, the predefined type information of the SDN controller and the master device is different.

The node-related topology information database maintains the topology location information of the node, including the topology location information of the node and the node type. The topological location information of a node includes: The IPv4 address, IPv6 address, or FQDN of the node. When a node has multiple ports, each port can correspond to a different IP address or FQDN. Node node types can include: Authentication, Authorization and Accounting (AAA), DHCP Proxy, DHCP Server, Network Address Translation (NAT), Firewall (Firewall) , Transmission Control Protocol (TCP) proxy (Proxy), Hypertext Transfer Protocol (HTTP) proxy (Proxy), ± or Name System (DNS) server (Server), wireless Network Controller (RNC), Base Station Controller (BSC), Serving General Packet Radio Service Support Node (SGSN), Mobility Management Mobility Management Entity, MME), Serving Gateway (SGW), Packet Data Network Gateway (PGW), Policy charging and rules function (PCRF), Home Subscriber (Home Subscriber) Server, HSS), Mobile switching center (MSC), Vi sited location register (VLR), etc.

Any two or more of the above-mentioned controller-related topology information database, node-related topology information database, and policy information database may be combined as needed. The access rights to the database can be set so that only the master device has access to the topology information database. When the topology location information of a node or SDN changes, the topology information database is updated accordingly.

The policy information database includes the correspondence between node types and control rules. Each node type corresponds to a set of basic function types, and the same function may exist in the set of basic function types corresponding to different node types. Corresponding to each function, corresponding to a piece of control information, correspondingly, each node type corresponds to a plurality of control information, and a plurality of pieces of control information constitute a control rule IJ, so each node corresponds to a corresponding control rule.

Each SDN controller in the controller pool is pre-configured with the address information of the master device, such as the IPv4 address, IPv6 address, or FQDN of the master device. The SDN controller and the master device are pre-configured with information identifying their respective types.

The method for the master device to obtain the load status information of each SDN controller may include the following two implementation manners.

In one mode, after the SDN controller is powered on, the IP address of the master device is obtained according to the address information of the pre-configured master device, and the master device is communicated according to the IP address. The SDN controller sends its node type and load status information to the master device.

The benefit of this implementation is better adaptability and scalability. When a new SDN controller is added, it only needs to pre-configure the address information of the master device and the information indicating that it is an SDN controller, and after it is powered on, it can be added to the controller pool of the SDN. Plug & Play functionality. Since the plug-and-play function is implemented, there is no need to make other modifications to the master device and each SDN controller, so it has very good scalability.

In another mode, after the main control device is powered on, the main control device queries the controller related topology information database, obtains the IP address and corresponding type information of each SDN controller in the controller pool, and correspondingly according to the IP address. The SDN controller sends a request to obtain its status information; the SDN controller that receives the request feeds back its load status information to the master device.

The advantage of this implementation is that the main control device can centrally control each SDN in the controller pool. Control and management. For example, if the master device does not send the above request to one of the SDN controllers in the controller pool, the function of the SDN controller is turned off.

In addition, before the main control device communicates with the SDN controller, it can also use the security process to perform mutual authentication and establish a secure transmission channel for both parties.

The usual way is to use the Public Key Infrastructure (PKI) mechanism. The main control device and the SDN controller respectively have digital certificates, through digital certificates and related security protocols, such as Transport Layer Security Protocol (TLS), Internet Key Exchange (IKE) version 2 ( Version 4) Wait for the identity of both parties and establish a secure channel. After passing the mutual authentication, the SDN controller will send its load status information to the master device, and accordingly, the master device can receive the load status information sent by the SDN controller. If other security measures are used, such as physical security, that is, the communication connection between the master device and the SDN controller is physically secure, the mutual identity authentication before them can be turned off.

After the master device obtains the load status information of each SDN controller, the configuration of the node can be implemented in the following two ways.

One mode is mainly applicable to devices at the access layer and the aggregation layer. The characteristics of the access layer and the aggregation layer device are that the devices on the data plane are widely distributed and have a large number of devices.

Specifically, after the node is powered on, the IP address of the master device is obtained according to the address information of the pre-configured master device; and the security process is completed with the master device to perform mutual authentication and establish a secure transmission channel between the two parties.

The node communicates with the master device according to the IP address, sends the node type to the master device, and requests the master device to deliver the distribution result.

The master device determines the SDN controller serving the node and the roles of the SDN controller according to the load status information of the SDN controller in the controller pool and the load balancing original, wherein the role includes the SDN controller as the The primary or secondary controller of the node.

The master device sends the allocation result to each SDN controller allocated to the node, which may include the IP address of the node, the node type, and the role of the corresponding SDN controller and its IP address. The master device also delivers the allocation result to the node, including the IP address of the SDN controller assigned to the node and the respective roles of the SDN controllers. Node and assignment results The indicated master controllers complete the security process to authenticate each other and establish a secure transmission channel for both parties.

The node sends a request for obtaining a control rule to the primary controller; the request includes the IP address and node type of the node. The main controller queries the policy information database according to the node type, obtains a control rule set corresponding to the node type, and formulates a control rule of the node. The master controller issues the control rule to the node.

The main controller updates its load status information to the master device. After receiving the control rule from the master device, the node may push the control rule to the slave controller; the slave controller may also acquire the control rule configured for the node by interacting with the master controller, and is particularly suitable for the application in the master. The physical communication distance between the controller and the slave controller is relatively close.

The benefit of this implementation is better adaptability and scalability. When a new node joins, it only needs to pre-configure the address information of the master device and the node type of the node. After power-on, the node can join the network and realize the plug-and-play function. Because of the plug-and-play, there is no need to make other modifications to each SDN controller, so it has very good scalability.

The other way is mainly applied to the equipment at the core layer. The characteristics of the core layer equipment are the better stability in terms of deployment.

Specifically, after the main control device is powered on, query the topology information database related to the node, and obtain the IP address and node type of each node. The master device determines the SDN controller serving the node and the roles of the SDN controller according to the load status information and the load balancing principle of the SDN controller in the controller pool, wherein the role includes the SDN controller as the node Primary controller or slave controller.

The master device sends the allocation result to each SDN controller allocated to the node, which may include the IP address of the node, the node type, and the role of the corresponding SDN controller and its IP address.

The security process is completed between the master device and the node to perform mutual authentication and establish a secure transmission channel between the two parties, and then the allocation result is sent to the node, including the IP address of the SDN controller allocated for the node and the The corresponding roles of the SDN controllers. The node completes the security process between the primary controller indicated in the assignment result to authenticate each other and establish a secure transmission channel for both parties.

The node sends a request for obtaining a control rule to the primary controller; the request includes the IP address and node type of the node. The main controller queries the policy information database according to the node type, and obtains the node type pair. The set of control rules should be used to formulate the control rules for the node. The master controller sends the control rule to the node. The main controller updates its load status information to the master device.

The master device can also directly push the control rule to the node if the node does not request acquisition of the control rule.

The benefit of this implementation is that it provides unified control and management of the various nodes in the network. If the master controller does not push a control rule to a node, it means that the function of the node is turned off.

After receiving the control rule from the master device, the node may push the control rule to the slave controller; the slave controller may also acquire the control rule configured for the node by interacting with the master controller, and is particularly suitable for the application in the master. The physical communication distance between the controller and the slave controller is relatively close.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, when executed, The steps of the foregoing method embodiments are performed; and the foregoing storage medium includes: various media that can store program codes, such as ROM, RAM, disk or optical disk.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting thereof; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

Claim

A network configuration method based on a software-defined network SDN, comprising: obtaining, according to load state information of at least one SDN controller in a controller pool, an allocation result of a controller for a node, where the allocation result includes a primary controller assigned to the node, the primary controller being an SDN controller in the controller pool;

2. The SDN-based network configuration method according to claim 1, wherein the allocation result further comprises a slave controller allocated to the node;

Correspondingly, the method further includes:

The SDN-based network configuration method according to claim 1, wherein the method further includes:

The SDN-based network configuration method according to any one of claims 1 to 3, wherein the obtaining the allocation of the node allocation controller according to the load state information of the at least one SDN controller in the controller pool The results include:

And configuring, according to load state information of the at least one SDN controller, a weight for each of the at least one SDN controller;

And assigning a distribution result of the controller to the node according to the weight of the at least one SDN controller.

The SDN-based network configuration method according to any one of claims 1 to 3, wherein the method further comprises:

Receiving load status information respectively sent by the at least one SDN controller; or The load status information is separately obtained from the at least one SDN controller.

Receiving a node type sent by the node; or

Get the node type of the node from the database.

7. An SDN-based network configuration method, comprising:

Configure according to the control rules.

The SDN-based network configuration method according to claim 7, wherein the method further includes:

The SDN-based network configuration method according to claim 7 or 8, wherein the method further comprises:

10. An SDN-based network configuration method, comprising:

The master controller acquires a control rule corresponding to the node type according to the node type, where the node type is received from the master device, or is obtained from a database, and the master controller is An SDN controller in the controller pool, wherein the main controller is an SDN controller allocated to the node as a main controller according to load status information of at least one SDN controller in the controller pool ;

The SDN-based network configuration method according to claim 10, wherein the master controller acquires a control rule corresponding to the node type according to a node type, where: the main controller receives the And sending, by the node, request information that carries the node type; and the primary controller configures, according to the request information, a control rule corresponding to the node type for the node.

The SDN-based network configuration method according to claim 10 or 11, wherein the method further comprises:

The main controller sends the load status information to the main control device, so that the main control device obtains an allocation result of the controller for the node according to load status information of at least one SDN controller in the controller pool. The allocation result includes a primary controller and a node assigned to the node

/ or slave controller.

13. An SDN-based network configuration method, comprising:

The SDN-based network configuration method according to claim 13, wherein the method further includes:

15. A main control device, comprising:

a sending unit, configured to send, to the main controller, a node type of the node, where the main controller acquires a control rule corresponding to the node type according to the node type, and Sending the control rule to the node.

The master device according to claim 15, wherein the allocation result obtained by the processing unit further includes a slave controller allocated to the node;

Correspondingly, the sending unit is further configured to:

The main control device according to claim 15, wherein the sending unit is further configured to:

The main control device according to any one of claims 15-17, wherein the processing unit is further configured to:

The main control device according to any one of claims 15-17, wherein the main control device further comprises:

And an acquiring unit, configured to receive load status information separately sent by the at least one SDN controller; or separately obtain load status information from the at least one SDN controller.

The main control device according to any one of claims 15-17, wherein the obtaining unit is further configured to:

21. A node, comprising:

a receiving unit, configured to receive a control rule sent by the main controller, where the control rule is a rule for controlling, corresponding to the node type, obtained by the main controller according to a node type, where the main controller is The control device is based on the load status of at least one SDN controller in the controller pool SDN controller for information selection;

The node according to claim 21, wherein the receiving unit is further configured to:

Correspondingly, the node further includes:

The node according to claim 21 or 22, wherein the sending unit is further configured to:

24. A main controller, comprising:

And a sending unit, configured to send the control rule to the node, so that the node is configured according to the control rule.

The main controller according to claim 24, wherein the processing unit is further configured to:

The main controller according to claim 24 or 25, wherein the transmitting unit is further configured to:

27. A slave controller, comprising:

The slave controller according to claim 27, wherein the slave controller further comprises:

29. A master control device, comprising:

The communication interface for communicating with a node according to any one of claims 21-23, in communication with the main controller of any of claims 24-26, and with claim 27 or The slave controller communication connection described in 28;

The memory is configured to store a program;

The processor, configured to execute the program;

30. A node, comprising:

The communication interface for communicating with a master device according to any one of claims 15-20, in communication with the host controller of any of claims 24-26, and with the claims The slave controller communication connection of 27 or 28, configured to receive a control rule sent by the main controller, where the control rule is used by the main controller according to the node type and corresponding to the node type for control a rule, the primary controller is an SDN controller selected by the master device according to load status information of at least one SDN controller in the controller pool;

The memory is configured to store a program;

The processor, configured to execute the program;

The program is configured to be configured according to the control rule.

31. A main controller, comprising:

The communication interface for communicating with a master device according to any one of claims 15-20, in communication with a node according to any of claims 21-23, and with claim 27 or The slave controller communication connection described in 28;

The memory is configured to store a program;

The processor, configured to execute the program;

32. A slave controller, comprising:

a processor, a memory, a bus, and a communication interface; the processor, the memory, and the communication interface are connected by the bus and complete communication with each other; The communication interface for communicating with a master device according to any of claims 15-20, in communication with a node according to any of claims 21-23, and with claim 24- The main controller communication connection of any one of 26;

The memory is configured to store a program;

The processor, configured to execute the program;

33. An SDN-based communication system, comprising: the master device according to any one of claims 15-20 or according to claim 29, at least one of claims 21-23 Or a node according to claim 30, at least one main controller according to any one of claims 24-26 or according to claim 31, and at least one of claims 27 or 28. Or the slave controller of claim 32;

The master device, the node, the master controller and the slave controller are in communication connection.