WO2017143722A1 - Procédé de mise en œuvre de fonction de réseau, dispositif de commande et élément de réseau - Google Patents

Procédé de mise en œuvre de fonction de réseau, dispositif de commande et élément de réseau Download PDF

Info

Publication number
WO2017143722A1
WO2017143722A1 PCT/CN2016/089652 CN2016089652W WO2017143722A1 WO 2017143722 A1 WO2017143722 A1 WO 2017143722A1 CN 2016089652 W CN2016089652 W CN 2016089652W WO 2017143722 A1 WO2017143722 A1 WO 2017143722A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
port
protocol
network
distributed control
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/089652
Other languages
English (en)
Chinese (zh)
Inventor
肖敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2017143722A1 publication Critical patent/WO2017143722A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements

Definitions

  • the embodiments of the present invention relate to, but are not limited to, Software Defined Network (SDN) technology, and in particular, to a network function implementation method, a control device, and a network element.
  • SDN Software Defined Network
  • FIG. 1 is a schematic diagram of the SDN network component architecture in the related art, as shown in Figure 1.
  • the SDN adopts an architecture in which the control plane is separated from the data plane.
  • the control plane of the SDN is implemented by the SDN controller, and the data plane of the SDN is implemented by the network element, and the SDN controller and the network element are connected through the SDN southbound interface.
  • the SDN controller sends a forwarding table to the network element through the SDN southbound interface, so as to control the data forwarding, so as to achieve separation of data forwarding and forwarding control.
  • the network element needs to support the SDN South running between the network element and the SDN controller.
  • interface control protocol such as the OpenFlow protocol
  • other traditional control protocols such as the bidirectional forwarding detection (BFD) protocol, the link layer discovery protocol (LLDP), and the intra-domain, need to be supported between the network element and the network element. Routing Protocol (IGP), etc.
  • IGP Routing Protocol
  • the SDN southbound interface control protocol running between the network element and the SDN controller is called a centralized control protocol, and other traditional control protocols running between the network element and the network element are called distributions. Control protocol. That is to say, the network element must support both the centralized control protocol and the distributed control protocol.
  • the centralized control protocol can also implement the network functions that the distributed control protocol can implement, the centralized control protocol and the distributed control protocol will have different functions when implementing the same network functions such as operation, management, and maintenance (OAM) functions. Performance and real-time, and different SDN application scenarios have different requirements for the performance and real-time performance of the same network function. Therefore, for many SDN application scenarios, the network element needs to support the distributed control protocol and implement certain network functions by using the distributed control protocol to meet the performance and real-time requirements of these SDN application scenarios for these network functions.
  • OAM operation, management, and maintenance
  • the embodiment of the invention provides a network function implementation method, a control device and a network element, which can avoid the problem that the centralized control protocol and the distributed control protocol conflict when implementing the same network function at the same time.
  • the embodiment of the present invention provides a network function implementation method.
  • a software-defined network SDN controller establishes a control connection with a network element, the method includes:
  • the SDN controller queries the type of the distributed control protocol that the network element can support and the enabled state of the distributed control protocol on each port of the network element;
  • the SDN controller turns off the centralized control protocol on the port for implementing the same network functions as the distributed control protocol.
  • the method further includes: implementing the network function by using a centralized control protocol for a port in which the network element does not enable a distributed control protocol to implement a network function.
  • the SDN controller queries the type of the distributed control protocol that the network element can support and the enabled state of the distributed control protocol on each port of the network element, including:
  • the SDN controller sends a query message to the network element, where the query message is used to query the type of the distributed control protocol that the network element can support and the enable state of the distributed control protocol on each port of the network element;
  • the response message carries a distributed control protocol type that the network element can support, and an enabled state of the distributed control protocol on each port of the network element.
  • the response message is an extended network element function response OFPT_FEATURES_REPLY message.
  • the method further includes: the network element notifying the SDN of the enabled control state of the distributed control protocol type and/or the distributed control protocol on the port of the network element by using an advertisement message Controller.
  • the advertisement message is an extended OpenFlow asynchronous message.
  • the method further includes: the SDN controller sends a command message to the network element, where the command message is used to instruct the network element to enable or disable one or more distributed control protocols supported by the network element. Running on each port of the network element.
  • the command message configures an OFPT_SET_CONFIG message for the extended network element or an extended network element port modification OFPT_PORT_MOD message.
  • the distributed protocol information carried by the extension adopts a package format of a type-length-assignment TLV;
  • the Type field of the TLV indicates that the TLV carries distributed protocol information.
  • the Length field indicates the total length of all n distributed protocol tuples
  • the Assign Value field consists of n distributed protocol tuples, each of which contains three more fields: the distributed protocol type, the port number, and the enabled state.
  • the embodiment of the present invention further provides a control device, including a query module and a control module, where
  • the query module is configured to query the type of the distributed control protocol that the network element can support and the enable state of the distributed control protocol on each port of the network element when establishing a control connection with the network element;
  • the control module is configured to close the port on the port for enabling the same network function as the distributed control protocol for the port in which the distributed control protocol is enabled.
  • control module is further configured to implement the network function by using a centralized control protocol for a port in which the distributed control protocol is not enabled.
  • the method further includes: a first processing module, configured to receive a distributed control protocol type and/or a distributed control protocol supported by the network element from the network element, and the enabling state of each port of the network element changes The change information is output to the control module.
  • a first processing module configured to receive a distributed control protocol type and/or a distributed control protocol supported by the network element from the network element, and the enabling state of each port of the network element changes The change information is output to the control module.
  • control module is further configured to: send a command message to the network element, where the command The message is used to instruct the network element to enable or disable the operation of one or more distributed control protocols supported by the network element on each port of the network element.
  • the embodiment of the present invention further provides a network element, including:
  • the interface module is configured to receive the query message from the control device, and send, to the second processing module, which distributed control protocol and the various distributed control protocols are enabled on the ports of the network element according to the query message.
  • Status notification notification ;
  • the second processing module is configured to receive the query notification, and return a response message to the control device according to the query notification, where the response message carries the distributed control protocol type that the network element that needs to be queried can support, and the distributed control protocol is on each port of the network element.
  • the enabled state is configured to receive the query notification, and return a response message to the control device according to the query notification, where the response message carries the distributed control protocol type that the network element that needs to be queried can support, and the distributed control protocol is on each port of the network element.
  • the interface module is further configured to: receive a command message from the control device, and send a command notification to the second processing module according to the command message;
  • the second processing module is further configured to: receive a command notification, and enable or disable the operation of one or more distributed control protocols supported by the network element to which the network element belongs to each port of the network element according to the command notification.
  • an embodiment of the present invention further provides a computer readable storage medium, where the computer storable medium stores computer executable instructions, where the computer executable instructions are used to perform network function implementation of any of the foregoing method.
  • the technical solution of the present application includes: when a control connection is established between the SDN controller and the network element, the SDN controller queries the distributed control protocol type and the distributed control protocol that the network element can support in the network element. An enabled state on each port; for a port in which the distributed control protocol is enabled, the SDN controller turns off the centralized control protocol on the port for implementing the same network functions as the distributed control protocol.
  • the WLAN controller does not use the centralized control protocol to implement the same network function on the same network element port. The problem of conflicts between the centralized control protocol and the distributed control protocol while implementing the same network function is avoided.
  • FIG. 2 is a flowchart of a method for implementing a network function according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a format of a message extension TLV according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a control device according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a first embodiment of an SDN controller controlling an LLDP protocol according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a second embodiment of an SDN controller controlling a BFD protocol according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a third embodiment of an SDN controller simultaneously controlling an LLDP protocol and a BFD protocol according to an embodiment of the present invention
  • FIG. 9 is a schematic diagram of a fourth embodiment of an SDN controller controlling an IGP protocol according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for implementing a network function according to an embodiment of the present invention, when an SDN controller and a network When a control connection is established between the elements, as shown in Figure 2, it includes:
  • the SDN controller sends a query message to the network element to query which distributed control protocols the network element can support and various distributed control protocols on the ports of the network element.
  • the network element receives the query message from the SDN controller, it returns a response message to report to the SDN controller various types of distributed control protocols supported by the network element itself, and various distributed control protocols. Enable status on each port of the NE.
  • the step further includes: the network element uniformly coding the distributed control protocols, for example, assigning codewords 1 to a distributed control protocol, such as LLDP, and assigning codewords 2 to a distributed control protocol, such as BFD.
  • a distributed control protocol such as LLDP
  • codewords 2 to a distributed control protocol, such as BFD.
  • each distributed control protocol has a unique codeword corresponding to the distributed control protocol.
  • the two enabled states of the various distributed control protocols on each port of the network element include an Enabled state and a Disabled state.
  • the query message sent by the SDN controller to the network element may use the network element function query (OFPT_FEATURES_REQUEST) message defined in the OpenFlow protocol; the response message sent by the network element to the SDN controller may be responded by the network element function defined in the OpenFlow protocol (OFPT_FEATURES_REPLY)
  • the message extension is obtained, and the extended protocol information of the extension can be encapsulated in a Type-Length-Value (TLV) format.
  • FIG. 3 is a schematic diagram of a format of a message extension TLV according to an embodiment of the present invention.
  • the Type field of the TLV indicates that the TLV carries distributed protocol information; the Length field indicates the total length of all n distributed protocol tuples; the Value field consists of n distributed protocol tuples, each distributed protocol tuple It also contains three fields: distributed protocol types such as codeword, port number, and enable status.
  • OpenFlow provides an open protocol that can be used on different switches and routers. Program the flow table.
  • the network function can still be implemented by using a centralized control protocol.
  • the WLAN controller does not use the centralized control protocol to implement the same network function on the same network element port. The problem of conflicts between the centralized control protocol and the distributed control protocol while implementing the same network function is avoided.
  • the network element in the SDN network may be controlled by multiple SDN controllers at the same time, and in addition to being controlled by the SDN controller, the network element may also be managed by the network management system and/or the network element configuration point, so during the network operation,
  • the distributed control protocol type supported by the network element and/or the enabling status of various distributed control protocols on each port of the network element may occur without prior knowledge of the SDN controller.
  • the embodiment of the present invention further includes:
  • the information about the type of the distributed control protocol that the network element can support and/or the change status of the enabled state of the distributed control protocol on each port of the network element is advertised to the SDN controller through an advertisement message.
  • the SDN controller closes the port that uses the centralized control protocol to implement the same network function, and the port for which the network element is not enabled with the distributed control protocol to implement the network function.
  • the network function is still implemented using a centralized control protocol.
  • the advertisement message may use the extended OpenFlow asynchronous message, that is, the extended distributed protocol state advertisement message, and the extended distributed protocol state advertisement message also carries the distributed protocol information in the TLV encapsulation format as shown in FIG. .
  • the SDN controller knows in real time the various types of distributed control protocols supported by the network element, and each Based on the enabled state of the distributed control protocol on each port of the network element, the method further includes:
  • the SDN controller sends a command message to the network element to instruct the network element to enable or disable the operation of one or more distributed control protocols supported by the network element on each port of the network element. That is to say, the SDN controller can modify the enabling state of each distributed control protocol supported by the network element on each port of the network element as needed.
  • the command message can be obtained by using the network element configuration (OFPT_SET_CONFIG) message defined in the OpenFlow protocol.
  • the extended OFPT_SET_CONFIG message also carries the distributed protocol information in the TLV encapsulation format as shown in FIG. 3.
  • the command message can also be obtained by using a network element port modification (OFPT_PORT_MOD) message extension defined in the OpenFlow protocol.
  • the extended OFPT_PORT_MOD message carries a distributed protocol type field and an enable status field.
  • FIG. 4 is a schematic structural diagram of a control device according to an embodiment of the present invention. As shown in FIG. 4, at least a query module and a control module are included;
  • the query module is configured to query the type of the distributed control protocol that the network element can support and the enable state of the distributed control protocol on each port of the network element when establishing a control connection with the network element;
  • the control module is configured to close the port on the port for enabling the same network function as the distributed control protocol for the port in which the distributed control protocol is enabled.
  • the query module is specifically configured to: when establishing a control connection with the network element, send a query message to the network element to query which distributed control protocols the network element can support and various distributed control protocols on the ports of the network element.
  • the status of the enable state is received from the network element to return various types of distributed control protocols supported by the network element and the response status of the various distributed control protocols on the ports of the network element.
  • the control module is also configured to implement the network function using a centralized control protocol for ports where the distributed control protocol is not enabled.
  • the control device of the embodiment of the present invention further includes: a first processing module, configured to receive a distributed control protocol type and/or a distributed control protocol supported by the network element from the network element, and the enabling state of each port of the network element changes The change information is output to the control module.
  • control module is further configured to: send a command message to the network element, to indicate that the network element modifies, for example, enabling or disabling the running of one or more distributed control protocols supported by the network element on each port of the network element.
  • FIG. 5 is a schematic structural diagram of a network element in an embodiment of the present invention, including at least an interface module and a second processing module;
  • the interface module is configured to receive the query message from the control device, and send, to the second processing module, which distributed control protocol and the various distributed control protocols are enabled on the ports of the network element according to the query message.
  • Status notification notification ;
  • the second processing module is configured to receive the query notification, and return a response message to the control device according to the query notification, where the response message carries the distributed control protocol type that the network element that needs to be queried can support, and the distributed control protocol is on each port of the network element.
  • the enabled state is configured to receive the query notification, and return a response message to the control device according to the query notification, where the response message carries the distributed control protocol type that the network element that needs to be queried can support, and the distributed control protocol is on each port of the network element.
  • the second processing module is further configured to notify the control device of the change information of the distributed control protocol type and/or the distributed control protocol supported by the network element to which the network element belongs to the network element.
  • the interface module is further configured to: receive a command message from the control device, and send a command notification to the second processing module according to the command message;
  • the second processing module is further configured to: receive a command notification, and enable or disable the operation of one or more distributed control protocols supported by the network element to which the network element belongs to each port of the network element according to the command notification.
  • FIG. 6 is a schematic diagram of a first embodiment of an SDN controller controlling an LLDP protocol according to an embodiment of the present invention.
  • an OpenFlow centralized control protocol is assumed between an SDN controller and a network element.
  • the LLDP distributed control protocol is run between the network element 1 and the network element 2.
  • the SDN controller controls the LLDP protocol supported by the network element by using the extended OpenFlow protocol, including:
  • the SDN controller learns by sending an inquiry message that both the network element 1 and the network element 2 support the LLDP protocol.
  • the LLDP protocol is enabled on port 1 of network element 1 and port 2 of network element 2. Specifically include:
  • the SDN controller sends a query message to the network element 1 to query which distributed control protocols the network element 1 can support and various distributed control protocols in the network element 1
  • the enable state on each port after receiving the query message sent by the SDN controller, the network element 1 returns a response message, and reports to the SDN controller that the network element 1 itself supports the LLDP protocol, and the LLDP protocol is on each port of the network element 1. Enable status.
  • the SDN controller sends a query message to the network element 2 to query which distributed control protocols and various distributed control protocols the network element 2 can support.
  • the enabled state on the port among them,
  • the query message sent by the SDN controller to the network element 1 and the network element 2 may use the OFPT_FEATURES_REQUEST query message defined in the OpenFlow protocol, and the response message replied by the network element 1 and the network element 2 to the SDN controller may be responded by the OFPT_FEATURES_REPLY defined in the OpenFlow protocol.
  • the message extension is obtained, and the distributed protocol information carried by the extension can be in the encapsulation format of the Type-Length-Value (TLV). As shown in FIG. 3, the Type field of the TLV indicates that the TLV carries the distributed protocol.
  • the Length field indicates the total length of all n distributed protocol tuples
  • the Value assignment field consists of n distributed protocol tuples, each of which contains three fields: a distributed protocol type such as a code Word, port number, and enable status.
  • both the port 1 of the network element 1 and the port 2 of the network element 2 are enabled with the LLDP protocol, so that the network element 1 and the network element 2 can implement the network function of mutual discovery by using the LLDP protocol.
  • the SDN controller does not use the OpenFlow protocol on the port 1 of the network element 1 and the port of the network element 2
  • the network function of the mutual discovery is implemented on the network 1 so that the port 1 of the network element 1 receives two types of conflicting LLDP packets at the same time: the port 2 of the network element 2 transmits LLDP packets and the SDN controller passes the OpenFlow.
  • the protocol indicates that the LLDP packet sent by the port 2 of the network element 2 causes the LLDP protocol state machine on the port 1 of the network element 1 to be confused.
  • the network management system independent of the SDN controller respectively connects the port 1 of the network element 1
  • the LLDP protocol enable state on the port 2 of the network element 2 is changed from the enable to the off, and the network element 1 and the network element 2 respectively report the change by sending an advertisement message to the SDN controller.
  • the advertisement message sent by the network element 1 and the network element 2 to the SDN controller may use an extended OpenFlow asynchronous message, that is, an extended distributed protocol state advertisement message, and is also carried in the extended distributed protocol state advertisement message.
  • the illustrated distributed protocol information is used in a TLV encapsulation format
  • the SDN controller learns that the port 1 of the network element 1 and the port 2 of the network element 2 are no longer enabled with the LLDP protocol to implement the mutual discovery network function, the SDN controller starts to use the OpenFlow protocol on the port 1 of the network element 1 and the port of the network element 2.
  • the SDN controller sends a Packet_out message containing the LLDP packet and the sending port number to the network element 1, instructing the network element 1 to send the LLDP packet from the port 1, and the network element 2 will receive the received packet.
  • the LLDP packet and the receiving port number are sent to the SDN controller through the Packet_in message.
  • the SDN controller sends the Packet_out message containing the LLDP packet and the sending port number to the network element 2, indicating that the network element 2 is sent out from the port 2.
  • LLDP packet, and the network element 1 sends the received LLDP packet and the receiving port number to the SDN controller through the Packet_in message.
  • the SDN controller can implement the mutual discovery network function on the port 1 of the network element 1 and the port 2 of the network element 2 by using the OpenFlow protocol.
  • the SDN controller may also instruct the port 1 of the network element 1 and the port 2 of the network element 2 to enable the LLDP protocol by sending a command message to the network element 1 and the network element 2, respectively.
  • the SDN controller stops using the OpenFlow protocol to implement mutual discovery network functions on port 1 of network element 1 and port 2 of network element 2. among them,
  • the command message sent by the SDN controller to the network element 1 and the network element 2 can be obtained by using the OFPT_SET_CONFIG message defined in the OpenFlow protocol.
  • the extended OFPT_SET_CONFIG message also carries the distributed protocol as shown in FIG.
  • the command message sent by the SDN controller to the network element 1 and the network element 2 can also be extended by the OFPT_PORT_MOD message defined in the OpenFlow protocol.
  • the extended OFPT_PORT_MOD message carries a distributed protocol type field and an enable status field.
  • the SDN controller re-enables the automatic between the network element 1 and the network element 2.
  • the mutual discovery can send a command message to the network element 1 and the network element 2, respectively, indicating that the port 1 of the network element 1 and the port 2 of the network element 2 re-enable the LLDP protocol.
  • the SDN controller stops using the OpenFlow protocol on port 1 of the network element 1 and The network function of mutual discovery is implemented on port 2 of network element 2.
  • FIG. 7 is a schematic diagram of a second embodiment of an SDN controller controlling a BFD protocol according to an embodiment of the present invention.
  • an OpenFlow centralized control protocol is assumed between an SDN controller and a network element.
  • the BFD distributed control protocol is run between the network element 3 and the network element 4.
  • the SDN controller controls the BFD protocol supported by the network element by using the extended OpenFlow protocol, including:
  • the SDN controller knows that the network element 3 supports the BFD protocol and the BFD protocol is in the closed state on port 3 of the network element 3, and the network element 4 does not support the BFD protocol. Specifically include:
  • the SDN controller sends an inquiry message to the network element 3 to query which distributed control protocols the network element 3 can support and various distributed control protocols in the network element 3.
  • the SDN controller sends an inquiry message to the network element 4 to query which distributed control protocols and various distributed control protocols the network element 4 can support.
  • the enabling state of each port of the network element 4 after receiving the query message sent by the SDN controller, the network element 4 returns a response message, and reports to the SDN controller the distributed control protocol supported by the network element 4, wherein there is no BFD protocol. That is, the network element 4 does not support the BFD protocol. That is to say, the BFD protocol is disabled on the port 3 of the network element 3, and the network element 4 does not support the BFD protocol, so that the network element 3 and the network element 4 cannot use the BFD protocol to implement the network function for real-time monitoring of the link state.
  • the SDN controller learns that the port 3 of the network element 3 and the port 4 of the network element 4 have not enabled the BFD protocol to implement the network function of real-time monitoring of the link state
  • the port of the network element 3 and the port of the network element 4 are started by using the OpenFlow protocol. 4 Network function to realize real-time monitoring of link status.
  • the SDN controller sends a Packet_out message containing the BFD packet and the sending port number to the network element 3, and instructs the network element 3 to send the BFD packet from the port 3,
  • the SDN controller sends a BFD packet to the network element 4 to instruct the network element 4 to process the received BFD packet.
  • the SDN controller sends the BFD packet and the port number to the network element 4.
  • the packet_out message indicates that the network element 4 sends the BFD packet from the port 4, and the SDN controller sends the flow table of the BFD packet to the network element 3 to instruct the network element 3 to process the received BFD packet.
  • the SDN controller can implement the network function of real-time monitoring of the link state on the port 3 of the network element 3 and the port 4 of the network element 4 by using the OpenFlow protocol.
  • the network management system is independent of the SDN controller and the BFD protocol is newly installed on the network element 4, and the BFD protocol on the port 4 of the network element 4 is in the closed state.
  • the network element 4 can report the advertised message to the SDN controller. The above changes.
  • the SDN controller may also instruct the port 3 of the network element 3 and the port 4 of the network element 4 to enable the BFD protocol by sending a command message to the network element 3 and the network element 4 respectively.
  • the SDN controller stops using the OpenFlow protocol to implement the network function of link state real-time monitoring on port 3 of network element 3 and port 4 of network element 4.
  • the SDN controller learns that the BFD protocol is newly installed on the network element 4, and the BFD protocol on the port 4 of the network element 4 is in the closed state
  • the link state between the network element 3 and the network element 4 is enabled in real time.
  • the monitoring can send a command message to the network element 3 and the network element 4, respectively, indicating that the port 3 of the network element 3 and the port 4 of the network element 4 enable the BFD protocol.
  • the SDN controller stops using the OpenFlow protocol in the network element 3 Network function of real-time monitoring of link status on port 3 and port 4 of network element 4.
  • FIG. 8 is a schematic diagram of a third embodiment of the SDN controller simultaneously controlling the LLDP protocol and the BFD protocol according to the embodiment of the present invention.
  • the OpenFlow set is run between the SDN controller and the network element.
  • the LLDP protocol and the BFD distributed control protocol are run between the network element 1 and the network element 2.
  • the SDN controller simultaneously performs the LLDP protocol and the BFD protocol supported by the network element through the extended OpenFlow protocol. Control, including:
  • the SDN controller knows that the network element 5 supports the LLDP protocol and the BFD protocol, and the LLDP protocol is enabled on the port 5 of the network element 5, and the BFD protocol is disabled on the port 5 of the network element 5, and the network element is closed. 6
  • the LLDP protocol is supported and the BFD protocol is not supported.
  • the LLDP protocol is enabled on port 6 of the network element 6. Specifically include:
  • the SDN controller sends a query message to the network element 5 to query which distributed control protocols the network element 5 can support and various distributed control protocols in the network element 5.
  • the LLDP and BFD protocols are supported by the SDN controller. Enable status on each port of element 5.
  • the SDN controller sends a query message to the network element 6 to query which distributed control protocols and various distributed control protocols the network element 6 can support.
  • the NE 6 returns a response message after receiving the query message sent by the SDN controller, and reports the distributed control protocol supported by the network element 6 and the distributed control protocol to the SDN controller.
  • there is an LLDP protocol and no BFD protocol that is, the network element 6 supports the LLDP protocol and does not support the BFD protocol.
  • the LLDP protocol is enabled on the port 5 of the network element 5 and the port 6 of the network element 6, so that the network element 5 and the network element 6 can implement the network function of mutual discovery by using the LLDP protocol.
  • the SDN controller does not use the OpenFlow protocol to implement the network function of mutual discovery on the port 5 of the network element 5 and the port 6 of the network element 6 to avoid conflicts.
  • the SDN controller If the BFD protocol is disabled on the port 5 of the network element 5, the network element 6 does not support the BFD protocol. Therefore, the network element 5 and the network element 6 cannot use the BFD protocol to implement the network function for real-time monitoring of the link state. Then, after the SDN controller knows that the port 5 of the network element 5 and the port 6 of the network element 6 have not enabled the BFD protocol to implement the network function for real-time monitoring of the link state, the SDN controller starts to use the OpenFlow protocol on port 5 and network element 6 of the network element 5. Network function for real-time monitoring of link status on port 6.
  • the network management device independently of the SDN controller separately changes the LLDP protocol enable state on the port 5 of the network element 5 and the port 6 of the network element 6 from the enable to the off, and then includes: the network element 5
  • the network element 6 and the network element 6 respectively report the change by sending an announcement message to the SDN controller.
  • the network management system is independent of the SDN controller, the BFD protocol is newly installed on the network element 6, and the BFD protocol on the port 6 of the network element 6 is in the closed state, and the network element 6 sends an advertisement message to the SDN controller. Report the above changes.
  • the OpenFlow protocol is used to implement the port 5 of the network element 5 and the port 6 of the network element 6 by using the OpenFlow protocol. Network features discovered by each other.
  • the SDN controller may also indicate that the port 5 of the network element 5 and the port 6 of the network element 6 simultaneously enable the LLDP protocol by sending a command message to the network element 5 and the network element 6, respectively. BFD protocol.
  • the SDN controller stops using the OpenFlow protocol to implement the mutually discovered network function and the network function of the link state real-time monitoring on the port 5 of the network element 5 and the port 6 of the network element 6.
  • the SDN controller learns that the LLDP protocol on the port 5 of the network element 5 and the port 6 of the network element 6 is changed from the enabled state to the closed state, the automatic mutual discovery between the network element 5 and the network element 6 is re-enabled.
  • the command message may be sent to the network element 5 and the network element 6, respectively, and the port 5 of the network element 5 and the port 6 of the network element 6 are respectively enabled to re-enable the LLDP protocol.
  • the SDN controller stops using the OpenFlow protocol on port 5 of the network element 5 and The network function of mutual discovery is implemented on port 6 of the network element 6.
  • a command message may be sent to the network element 5 and the network element 6 to indicate that the port 5 of the network element 5 and the port 6 of the network element 6 enable the BFD protocol.
  • the SDN controller stops using the OpenFlow protocol in the network element 5. The network function of real-time monitoring of link status is implemented on port 5 and port 6 of network element 6.
  • FIG. 9 is a schematic diagram of a fourth embodiment of an SDN controller controlling an IGP protocol according to an embodiment of the present invention.
  • an OpenFlow centralized control protocol is assumed between an SDN controller and a network element.
  • the IGP distributed control protocol is run between the network element 7, the network element 8, and the network element 9.
  • the SDN controller controls the IGP protocol supported by the network element by using the extended OpenFlow protocol, including:
  • the SDN controller knows that the network element 7, the network element 8, and the network element 9 support the IGP protocol, and the IGP protocol is on port 7 and port 8 of the network element 7, port 7 and port 8 of the network element 8, and the network. Both port 9 and port 10 of element 9 are enabled. Specifically include:
  • the SDN controller sends a query message to the network element 7 to query which distributed control protocols and various distributions the network element 7 can support.
  • the SDN controller sends a query message to the network element 8 to query which distributed control protocols and various distributed control protocols the network element 8 can support.
  • the enabled state on the top Similarly, once the control connection is established between the SDN controller and the network element 9, the SDN controller sends a query message to the network element 9 to query which distributed control protocols and various distributed control protocols the network element 9 can support.
  • the enabled state on the top a response message after receiving the query message sent by the SDN controller, and reports to the SDN controller that the network element 9 supports the IGP protocol, and the IGP protocol is on each port of the network element 9.
  • the port 7 and the port 8 of the network element 7, the port 7 and the port 8 of the network element 8, and the port 9 and the port 10 of the network element 9 are both enabled with the IGP protocol, so that the network element 7 and the network element 8 are And the network element 9 can implement the network function of routing and forwarding by using the IGP protocol.
  • the SDN controller learns that port 7 and port 8 of the network element 7, port 7 and port 8 of the network element 8, and port 9 and port 10 of the network element 9 are enabling the IGP protocol to implement the network function of routing and forwarding
  • the network function of routing forwarding is implemented on port 7 and port 8 of network element 7, port 7 and port 8 of network element 8, and port 9 and port 10 of network element 9 by using the OpenFlow protocol. That is, the SDN controller does not calculate the route between the network element 7, the network element 8, and the network element 9, and does not use the OpenFlow protocol to deliver the corresponding forwarding flow to the network element 7, the network element 8, and the network element 9.
  • the forwarding table generated by the IGP protocol on the network element 7, the network element 8, and the network element 9 is in conflict with the forwarding flow table sent by the SDN controller through the OpenFlow protocol, causing confusion on the forwarding state of the network element.
  • the network management system independent of the SDN controller respectively connects port 7 and port 8 of the network element 7, port 7 and port 8 of the network element 8, and port 9 and port 10 of the network element 9 to the IGP protocol.
  • the enable state is changed from enabled to off, and includes: the network element 7, the network element 8, and the network element 9 respectively report the change by sending an advertisement message to the SDN controller.
  • the SDN controller starts after knowing that port 7 and port 8 of the network element 7, port 7 and port 8 of the network element 8, and port 9 and port 10 of the network element 9 are no longer enabled with the network function of the IGP protocol for routing and forwarding.
  • the SDN controller calculates the routes between port 7 and port 8 of network element 7, port 7 and port 8 of network element 8, and port 9 and port 10 of network element 9, forming each network element.
  • the corresponding forwarding flow table is corresponding to the calculated route, and then the corresponding forwarding flow table is delivered to the network element 7, the network element 8, and the network element 9 through the OpenFlow protocol.
  • the SDN controller can implement the network function of routing and forwarding on the port 7 and port 8 of the network element 7, the port 7 and port 8 of the network element 8, and the port 9 and port 10 of the network element 9 by using the OpenFlow protocol.
  • the SDN controller may also indicate the port 7 and the port 8 of the network element 7 and the network element 8 by sending a command message to the network element 7, the network element 8, and the network element 9, respectively.
  • Ports 7 and 8, and port 9 and port 10 of network element 9 enable the IGP protocol.
  • the SDN controller stops using the OpenFlow protocol to implement the network function of route forwarding on port 7 and port 8 of network element 7, port 7 and port 8 of network element 8, and port 9 and port 10 of network element 9.
  • the SDN controller learns that the port 7 and port 8 of the network element 7, the port 7 and port 8 of the network element 8, and the port 9 and port 10 of the network element 9 are changed from the enabled state to the closed state, Re-enable the route forwarding between the network element 7, the network element 8, and the network element 9, and send a command message to the network element 7, the network element 8, and the network element 9, respectively, indicating port 7 and port 8 of the network element 7, Port 7 and port 8 of network element 8, port 9 and port 10 of network element 9 re-enable the IGP protocol.
  • the SDN controller stops using the OpenFlow protocol in the network element 7 Port 7 and port 8, port 7 and port 8 of network element 8, port 9 and port 10 of network element 9 implement network functions for route forwarding.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the network function implementation method, the control device and the network element provided by the embodiment of the present invention when the SDN controller learns that a certain port of the network element is enabling the distributed control protocol to implement a certain network function, the centralized control protocol is no longer used in the same network element port. Implementing the same network function avoids the conflict between the centralized control protocol and the distributed control protocol when simultaneously implementing the same network function.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé de mise en œuvre de fonction de réseau, un dispositif de commande et un élément de réseau. Le procédé comprend les étapes suivantes : lorsqu'une connexion de commande est établie entre un contrôleur de réseau défini par logiciel (SDN) et l'élément de réseau, le contrôleur de SDN s'enquiert du type d'un protocole de commande répartie que l'élément de réseau peut prendre en charge et d'états d'activation du protocole de commande répartie sur chaque port de l'élément de réseau ; et pour un port sur lequel le protocole de commande répartie est dans un état activé, le contrôleur de SDN arrête un protocole de commande centralisée sur le port qui est utilisé pour mettre en œuvre la même fonction de réseau que le protocole de commande répartie. Dans le procédé technique décrit par l'invention, lorsque le contrôleur de SDN apprend qu'un certain port de l'élément de réseau permet au protocole de commande répartie de mettre en œuvre une fonction de réseau, le contrôleur de SDN n'utilise plus le protocole de commande centralisée pour mettre en œuvre la même fonction de réseau sur le même port de l'élément de réseau, ce qui permet d'éviter la situation dans laquelle des conflits peuvent survenir lorsque le protocole de commande centralisée et le protocole de commande répartie réalisent simultanément la même fonction de réseau.
PCT/CN2016/089652 2016-02-22 2016-07-11 Procédé de mise en œuvre de fonction de réseau, dispositif de commande et élément de réseau Ceased WO2017143722A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610097496.8A CN107104811B (zh) 2016-02-22 2016-02-22 一种网络功能实现方法及控制装置
CN201610097496.8 2016-02-22

Publications (1)

Publication Number Publication Date
WO2017143722A1 true WO2017143722A1 (fr) 2017-08-31

Family

ID=59658774

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/089652 Ceased WO2017143722A1 (fr) 2016-02-22 2016-07-11 Procédé de mise en œuvre de fonction de réseau, dispositif de commande et élément de réseau

Country Status (2)

Country Link
CN (1) CN107104811B (fr)
WO (1) WO2017143722A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110650167B (zh) * 2018-06-26 2021-02-23 华为技术有限公司 通信方法和装置
CN109412850B (zh) * 2018-10-25 2022-02-11 新华三技术有限公司合肥分公司 消息订阅控制方法及装置
CN116048642B (zh) * 2023-01-30 2026-04-21 济南浪潮数据技术有限公司 一种lldp使能状态的控制方法、装置及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104320345A (zh) * 2014-10-30 2015-01-28 杭州华三通信技术有限公司 Sdn网络中拓扑信息收集的方法及装置
CN104735001A (zh) * 2013-12-24 2015-06-24 中兴通讯股份有限公司 软件定义网络中的链路发现方法、装置及系统
EP2975807A1 (fr) * 2013-03-15 2016-01-20 ZTE Corporation Procédé et appareil pour découvrir un dispositif de plan de commande basé sur un protocole openflow

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2375023B (en) * 2001-04-26 2003-07-16 Marconi Comm Ltd Improvements in and relating to telecommunications networks
US8249104B2 (en) * 2008-10-30 2012-08-21 Futurewei Technologies, Inc. Optical network terminal management and control interface over Ethernet
CN103001887B (zh) * 2012-11-22 2018-01-05 中兴通讯股份有限公司 一种链路保活方法、控制器及交换机
US9729425B2 (en) * 2012-11-29 2017-08-08 Futurewei Technologies, Inc. Transformation and unified control of hybrid networks composed of OpenFlow switches and other programmable switches
US9100285B1 (en) * 2012-12-18 2015-08-04 Juniper Networks, Inc. Dynamic control channel establishment for software-defined networks having centralized control
US10333779B2 (en) * 2013-04-10 2019-06-25 Huawei Technologies Co., Ltd. System and method for providing a software defined protocol stack
WO2015051856A1 (fr) * 2013-10-11 2015-04-16 Xieon Networks S.À.R.L. Établissement d'un chemin de données centralisé augmenté avec une messagerie de commande répartie
CN104702438B (zh) * 2015-03-13 2018-04-06 新华三技术有限公司 Pe设备管理方法以及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2975807A1 (fr) * 2013-03-15 2016-01-20 ZTE Corporation Procédé et appareil pour découvrir un dispositif de plan de commande basé sur un protocole openflow
CN104735001A (zh) * 2013-12-24 2015-06-24 中兴通讯股份有限公司 软件定义网络中的链路发现方法、装置及系统
CN104320345A (zh) * 2014-10-30 2015-01-28 杭州华三通信技术有限公司 Sdn网络中拓扑信息收集的方法及装置

Also Published As

Publication number Publication date
CN107104811A (zh) 2017-08-29
CN107104811B (zh) 2021-08-17

Similar Documents

Publication Publication Date Title
US11374857B2 (en) Network device management method and apparatus, and system for indicating a network device to perform management operation
CN106375231B (zh) 一种流量切换方法、设备及系统
CN102594689B (zh) 一种分布式网络控制方法及装置
KR101473783B1 (ko) 터널링을 이용한 다이나믹 서비스 체이닝 제어 방법 및 장치
US20220078076A1 (en) Method, Apparatus, and System for Communication Between Controllers in TSN
CN102006184B (zh) 堆叠链路管理方法、装置及网络设备
EP2974147B1 (fr) Réseau hybride sans boucle
US10404544B2 (en) Network topology determining method and apparatus, and centralized network status information storage device
CN101488879B (zh) 以太网生成树协议的网络设备中的故障保护方法及装置
CN104702438B (zh) Pe设备管理方法以及装置
CN108028801B (zh) 一种基于sdn的arp实现方法及装置
WO2016165463A1 (fr) Procédé de compte rendu de défaillance de liaison basé sur un réseau défini par logiciel et dispositif de réacheminement
US10122654B2 (en) Divided hierarchical network system based on software-defined networks
CN104301238A (zh) 一种报文处理方法、装置及系统
US10805169B2 (en) Topology determining method, message response method, controller, and switch
JP2016502329A (ja) 仮想シャーシシステムにおけるパススルーモードのためのシステムおよび方法
WO2017143722A1 (fr) Procédé de mise en œuvre de fonction de réseau, dispositif de commande et élément de réseau
WO2018219103A1 (fr) Procédé et dispositif de détermination d'état de liaison
CN107070791A (zh) 一种sdn网络系统及其数据传输方法
WO2012146104A1 (fr) Procédé, dispositif et système de mise à jour d'informations de port
WO2016065925A1 (fr) Dispositif et procédé de remplacement de contrôleur
CN115134232A (zh) 一种虚拟路由器管理方法、设备、系统和存储介质
CN120528860A (zh) 一种基于bfd的会话管理方法、设备及介质
CN102780614B (zh) 生成树协议布线组功能启用方法、设备及系统
CN118827353A (zh) 一种信息传输方法和设备

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16891172

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16891172

Country of ref document: EP

Kind code of ref document: A1