TWI646803B - Heterogeneous software defined network controller and management device and method thereof - Google Patents

Abstract

The main purpose of the present invention is to solve the difficulties encountered in using the heterogeneous software to define the network controller for the discovery of the network topology, and to design a standardized unified format that can be recognized by other brands of the network domain. The link layer discovers the protocol format and its packets, so that the topology of the heterogeneous domain can be fully detected. In addition, by using an elastic link layer discovery protocol format resolution method, the management device of the present invention can be compatible with a commercial SDN controller to achieve integration of multiple schemes.

Description

Heterogeneous software definition network controller and management device and method thereof

The present invention relates to a software-defined network controller, and more particularly to a heterogeneous software-defined network controller and a management apparatus and method thereof.

According to the technology evolution of software defined networking (SDN), most existing SDN controllers use a custom link layer discovery protocol (LLDP) packet format to perform the SDN physical machine. The topology of the exchanger is looking for. Therefore, when the domain is complex and has multiple heterogeneous SDN controllers to control the network environment, the problem that the boundary domain topology cannot be detected due to different LLDP packet formats will occur. For example: Open Daylight and RUY two SDN open source controllers use different LLDP packet formats. The Open Daylight controller's LLDP Chassis ID TLV Subtype uses MAC Address 4 to represent the unique representation of each SDN entity switch. No., and the RYU controller is represented by the Locally assigned 7 of the Subtype of the Chassis ID TLV, and uses the self-planned ID number as the value to be called.

The above phenomenon causes Open Daylight to discard the LLDP packets sent by RUY, and thus it is impossible to know that the border SDN entity switch of the bottom controller and the SDN entity switch of the RYU are connected, forming a separate management mode, and thus cannot be obtained. Comprehensive domain topology. In addition, when the commercial SDN controller is introduced, the same problem arises, that is, the heterogeneous SDN network controller cannot be effectively integrated and managed.

The existing SDN network architecture development orientation is mostly the use of multiple SDN controllers. For example, because the SDN controller has the limitation of control and function, it is usually used in a single equipment room to use one controller, and the heterogeneous SDN controller is used outside the exit or other equipment room. Therefore, this issue is a key issue for good management of heterogeneous SDN controllers and SDN networks.

The present invention provides a method for managing a hetero-software-defined networking (SDN) controller, comprising: defining a link layer discovery protocol in response to receiving a registration request of a software-defined network controller , LLDP) packet format. Transmitting a template of the link layer discovery protocol packet format to the software defined network controller. And receiving a message from the software defined network controller to update the domain topology.

The present invention provides a method for defining a network management domain topology in a heterogeneous software, suitable for a software-defined network controller, the method comprising: transmitting a registration request. In response to transmitting the registration request, a template for the newly defined link layer discovery protocol packet format is received. And managing the domain topology based on the link layer discovery protocol packet format.

The present invention provides an apparatus for managing a heterogeneous software-defined network controller, comprising: a transceiver, transmitting or receiving data. A storage unit that records multiple modules. And the processing unit is coupled to the storage unit, and accesses and executes the modules stored by the storage unit, where the modules include: a centralized link layer discovery protocol reorganization definition module and a heterogeneous software definition network control The domain topology detection module. The centralized link layer discovery protocol reorganization definition module includes: a link layer discovery protocol registration module, which receives a registration request of a software definition network controller through the transceiver, and defines a link layer discovery protocol based on the registration request ( A link layer discovery protocol (LLDP) packet format and a template for transmitting the link layer discovery protocol packet format to the software defined network controller. The domain topology detection module of the heterogeneous software definition network controller includes: a centralized heterogeneous domain topology management module, which receives messages from the software defined network controller to update the domain topology.

The invention provides a software defined network controller, comprising: a transceiver, transmitting a registration request. And a processor configured to: receive, in response to transmitting the registration request, a template of the newly defined link layer discovery protocol packet format through the transceiver. And managing the domain topology based on the link layer discovery protocol packet format.

Based on the above, the present invention proposes a heterogeneous software definition network controller and a management apparatus and method thereof, which can automatically detect a full domain topology. The centralized link layer discovery protocol reassembly definition module is linked to the topology collection application of each SDN controller to define and flexibly transmit the link layer discovery protocol packet format. The domain topology detection module of the heterogeneous software definition network controller uses the centralized heterogeneous domain topology management module to trigger the events of each controller to send LLDP packets, and integrates the heterogeneous domain topology data.

The above described features and advantages of the invention will be apparent from the following description.

1 is a schematic diagram of an apparatus 10 for managing a heterogeneous SDN controller in accordance with an embodiment of the present invention. Device 10 includes, but is not limited to, storage unit 100, processor 130, and transceiver 140. The storage unit 100 can be any type of fixed or removable random access memory (RAM), read only memory (ROM), flash memory, hard disk drive, solid state hard A solid-state drive or similar component or combination of the above components, and used to record a plurality of modules, including: a centralized link layer discovery protocol reorganization definition module 110 and a heterogeneous software definition network controller domain extension Park detection module 120. The processor 130 is coupled to the storage unit 100 and may be a central processing unit (CPU) or other programmable general purpose or special purpose microprocessor (Microprocessor), digital signal processor (DSP), and programmable. Controller, Special Application Integrated Circuit (ASIC) or other similar component or combination of the above. In the embodiment of the present invention, the processing unit 140 is configured to perform all functions of the device 10 for managing the heterogeneous SDN controller, and can access and execute the modules recorded in the storage unit 100. The transceiver 140 is configured to transmit and receive wireless signals. Transceiver 140 can also perform operations such as low noise amplification, impedance matching, mixing, upconversion or down conversion, filtering, amplification, and the like.

The centralized link layer discovery protocol reorganization definition module 110 defines a standardized LLDP packet format for reassembly, and provides an elastic adjustment mechanism. The currently supported LLDP packet format can be assigned in response to active registration of the SDN controller, and the SDN controller is assigned a unique system identifier for subsequent communication. The domain topology detection module 120 of the heterogeneous software definition network controller can be regarded as the most important monitoring framework module, and the standardized link layer discovery protocol packet is used to detect the domain extension of the heterogeneous SDN controller. Park, and through the centralized heterogeneous domain topology management module 121 to achieve the integration of topology information, to achieve the visibility of the entire domain.

The main function of the centralized link layer discovery protocol reorganization definition module 110 is to unify the LLDP packet format of each SDN controller, and enable the heterogeneous SDN controller to resolve the topology detection information transmitted by itself. The method includes a link layer discovery protocol format operation module 111, a protocol format resource and a software definition network controller relationship knowledge base 112, a link layer discovery protocol reassembly module 113, and a link layer discovery agreement registration module 114.

The link layer discovery protocol format operation module 111 is configured to provide an input layer defined link layer discovery protocol packet format. It is assumed that the device 10 for managing the heterogeneous SDN controller is used to manage the SDN controllers having different LLDP packet formats, such as RYU and OpenDaylight (ODL), in the always-on network environment, and the link layer discovery protocol format operation module 111 can generate The LLDP packet format 200 shown in FIG. 2 includes, but is not limited to, at least one of the following: a chassis identification code 210, a port ID 211, and a time to live 212. The system name 213 and the type/length/value (TLV) field of the end of LLD PDU of the link layer discovery protocol data unit (LLDPDU) 214 . The link layer discovery protocol format operation module 111 transmits the same LLDP packet format 200 to a plurality of SDN controllers having different LLDP packet formats to operate in accordance with the same LLDP packet format 200. For example, in the prior art, the format of the format of the LLDP field of the LLDP packet used by the RY controller of the RYU and the format of the TLV field of the LLDP packet used by the SDN controller of the ODL will be the format of the TLV field. Not the same. However, in an embodiment of the present invention, the link layer discovery protocol format operation module 111 will transmit the same LLDP packet format 200 to the RYU and the ODL SDN controller, so that the SDN controllers use the same LLDP packet format. Data transfer.

In the LLDP packet format 200, the system name 213 is used to indicate the system name code of the heterogeneous SDN controller. The Subtype field of the chassis ID 210 uses the Locally assigned 7 format to indicate the ID of the SDN switch. The subtype field of the 埠ID 211 also uses the Locally assigned 7 format to indicate the number of the SDN switch port.

The protocol format resource and the software definition network controller relationship knowledge base 112 are used to provide a record SDN controller specific identification code and LLDP packet format.

The main function of the link layer discovery protocol reassembly module 113 is to parse the packet format obtained by the recombination link layer discovery protocol format operation module 111, and whether the packet format of the comparison input conforms to the basic rules of the link layer discovery protocol, wherein the basic rule It contains four fields: Chassis ID TLV, Port ID TLV, Time to live TLV and End of LLDPDU TLV.

The main function of the link layer discovery protocol registration module 114 is to process the registration request proposed by the SDN controller, and give the system name code and link layer discovery protocol packet format uniquely identified by each SDN controller.

The main function of the domain topology detection module 120 of the heterogeneous software definition network controller is to automatically detect and integrate the domain topology managed by the heterogeneous SDN controller, and obtain cross-regional network connection information. Provides the overall topology of the user's global network. The method includes: a centralized heterogeneous domain topology management module 121 and a domain topology knowledge base 122 of a heterogeneous software definition network controller.

The main function of the centralized heterogeneous domain topology management module 121 is to detect and collect the topology connection information, the switch and the connection information returned by each SDN controller, and obtain the cross-heterogeneous SDN control after integration and information reorganization. The topology of the domain can automatically detect the change of the topology of the domain.

The main function of the domain topology knowledge base 122 of the heterogeneous software definition network controller is the knowledge of the road network topology.

3 is a schematic diagram of an SDN controller 30 and a network managed thereby, wherein the SDN controller 30 may be an SDN controller using any of the LLDP packet formats, such as RYU or ODL, in accordance with an embodiment of the present invention.

The SDN controller 30 can include, but is not limited to, a storage unit 300, a processor 330, and a transceiver 340. The storage unit 300 can be any type of fixed or removable random access memory (RAM), read only memory (ROM), flash memory, hard disk drive, solid state hard A solid-state drive or similar component or combination of the above components is used to record the heterogeneous domain topology monitoring application module 310. The processor 330 is coupled to the storage unit 300 and may be a central processing unit (CPU) or other programmable general purpose or special purpose microprocessor (Microprocessor), digital signal processor (DSP), and programmable. Controller, Special Application Integrated Circuit (ASIC) or other similar component or combination of the above. In the embodiment of the present invention, the processing unit 340 is configured to perform all functions of the SDN controller 30, and can access and execute the modules recorded in the storage unit 300. The transceiver 340 is configured to transmit and receive wireless signals. Transceiver 340 can also perform operations such as low noise amplification, impedance matching, mixing, upconversion or down conversion, filtering, amplification, and the like.

Referring to FIG. 1 and FIG. 3 simultaneously, in the following embodiments, it will be assumed that the device 10 managing the heterogeneous SDN controller manages at least two heterogeneous SDN controllers having different LLDP packet formats in the same heterogeneous network ( For example, an SDN controller using a RYU packet format and an SDN controller using an ODL packet format, and the heterogeneous SDN control can be implemented by the SDN controller 30 of the present invention.

Go back to Figure 3. In FIG. 3, the SDN network to which the SDN controller 30 is connected may include an SDN switch and a port. The heterogeneous domain topology monitoring application module 310 is used to receive the domain topology knowledge, analyze the LLDP packet format required by the current environment, and collect the LLDP packet format sent by the heterogeneous SDN controller to achieve a preliminary topology. Integration. The heterogeneous domain topology monitors the application module 310 and performs the work of returning the topology knowledge to the centralized heterogeneous domain topology management module 121. The algorithms of the heterogeneous domain topology monitoring application module 310 are portable, portable and available for different programming languages.

4 is a flow diagram 400 of a method of managing an SDN controller that may be performed by the centralized link layer discovery protocol reassembly definition module 110, in accordance with an embodiment of the present invention. Figure 4 illustrates the steps for the SDN controller to register and obtain a standardized link layer discovery protocol packet format.

In step S401, the SDN controller 30 sends a registration request to the link layer discovery protocol registration module 114, requesting the link layer discovery agreement registration module 114 to provide the subsequently used system name code and LLDP packet format 200.

In step S402, in response to receiving the registration request sent by the SDN controller 30, the link layer discovery agreement registration module 114 determines whether the SDN controller is a device within the control range of the device 10. If YES, the process proceeds to step S404, and if not, the process proceeds to step S403.

In step S403, the link layer discovery protocol registration module 114 reports a message that the SDN controller 30 cannot be registered to the SDN controller 30.

In step S404, the link layer discovery protocol registration module 114 queries the protocol format resource and the software defined network controller relationship knowledge base 112, and generates an LLDP packet format 200 for the SDN controller 30.

In step S405, the link layer discovery protocol registration module 114 creates a system name that is specific to the SDN controller 30.

In step S406, the link layer discovery protocol registration module 114 transmits the template of the LLDP packet format 200 and the system name unique to the SDN controller 30 to the SDN controller 30. The SDN controller 30 can update the domain topology based on the LLDP packet format 200.

5 is a flow chart 500 of a topology topology detection module 120 of a heterogeneous software-defined network controller monitoring a connection and topology of an SDN switch, which may define a network by a heterogeneous software, in accordance with an embodiment of the present invention. The domain topology detection module 120 of the controller and the SND controller 30 are implemented. The flow chart 500 mainly describes updating the domain topology based on the connection status event of the SDN controller obtained by the SDN controller. When a new SDN switch connection is generated, a topology monitoring mechanism is started to perform this connection and network detection.

In step S501, the SDN controller 30 receives a connection error event transmitted by the switch within the control range.

At step S502, the SDN controller 30 performs event analysis and decision on the transaction event. When the transaction event is a new SDN switch connection, the process proceeds to step S503. Otherwise, if the transaction event is to delete an SDN switch connection, the process proceeds to step S507.

If the SDN controller 30 determines in step S502 that the transaction event is to add a new SDN switch port, in step S503, the SDN controller 30 transmits the event related information of the newly added SDN switch port to the centralized heterogeneous domain topology. The management module 121 notifies the currently added port ID of the centralized heterogeneous domain topology management module 121 and the ID of the SDN switch to which it belongs. Next, in step S504, the centralized heterogeneous domain topology management module 121 updates the received information to the domain topology knowledge base 122 of the associated heterogeneous software definition network controller, thereby updating the network topology.

Optionally, in step S505, the SDN controller 30 may perform a new connection, add a pre-join job, and add the new port information to the LLDP packet that is periodically transmitted, where the LLDP packet is periodically transmitted. Used to periodically detect connections in the domain topology. A flowchart for periodically transmitting LLDP packets can be referred to FIG. 6 and subsequent descriptions.

Optionally, in step S506, the SDN controller 30 may perform a one-time transmission of the LLDP process to confirm the current topology of the new connection. A flow chart for transmitting LLDP at one time can also be referred to FIG. 6 and subsequent descriptions. Steps S505 and S506 are optional implementation steps, and the present invention is not limited to the order in which the two are implemented.

If the SDN controller 30 determines in step S502 that the transaction event is to delete the information of an existing SDN switch port, in step S507, the SDN controller 30 transmits the event related message for deleting the SDN switch port to the centralized heterogeneous domain. The topology management module 121 requires the centralized heterogeneous domain topology management module 121 to delete the information of the SDN switch port. Next, in step S508, the centralized heterogeneous domain topology management module 121 deletes the information of the SDN switch port stored in the domain topology knowledge base 122 of the heterogeneous software definition network controller.

Optionally, in step S509, the SDN controller 30 deletes the information of the SDN switch connected to the periodically transmitted LLDP packet. In other words, subsequent periodic domain topology detection will bypass the deleted SDN switch port.

6 is a flow diagram 600 of transmitting LLDP packets periodically or once, which may be implemented by SDN controller 30, in accordance with an embodiment of the present invention. The main purpose of flowchart 600 is to detect the topology of the domain by transmitting LLDP packets on a regular or one-time basis.

In step S601, the SDN controller 30 periodically requests the switch within the control range to transmit the LLDP packet to the switch port, wherein the periodic time range can be flexibly adjusted. In an embodiment of the invention, the periodic time is one unit of 5 seconds.

In step S602, the SDN controller 30 receives the LLDP packet forwarded by the switch. Specifically, when the SDN switch receives the LLDP packet for detecting, the SDN switch forwards the SDN controller to the SDN controller 30, and the SDN controller 30 Record the topology connection information within the scope of control.

In step S603, the SDN controller 30 determines whether the format of the received LLDP packet conforms to the basic rule of the LLDP packet. If the basic rule is not met, the SDN controller 30 discards the received LLDP packet in step S604. Otherwise, the process proceeds to step S605.

In step S605, the SDN controller 30 parses the content data of the LLDP packet, and reorganizes the topology connection information based on the LLDP packet, and combines it into the heterogeneous domain topology connection information.

In step S606, the SDN controller 30 determines whether the heterogeneous domain topology connection information already exists. If the heterogeneous domain topology connection information is the existing data, the process proceeds to step S607, otherwise, the process proceeds to step S608.

In step S607, the SDN controller 30 updates the time stamp of the heterogeneous domain topology connection information. At this time, the SDN controller 30 does not need to notify the heterogeneous domain topology management module 121 separately. In this way, the information communication is too frequent and the module resources are depleted. The timestamp mechanism can be used to automatically detect the trustworthiness of the topology of the domain. For details, please refer to Figure 7.

In step S608, the SDN controller 30 gives a time stamp for the time formed by the heterogeneous domain topology connection information.

In step S609, the SDN controller 30 transmits an update message of the heterogeneous domain topology connection information to the heterogeneous domain topology management module 121.

After step S607 or step S609, the flowchart 600 may return to execution step S601. As such, it can be considered as a process of periodically transmitting LLDP packets. If only steps S602 to S609 are implemented, it can be considered that the flow of transmitting the LLDP packet is performed once.

7 is a flow diagram 700 of a mechanism for periodically transmitting LLDP packets to detect timestamps used in a domain topology, which may be implemented by SDN controller 30, in accordance with an embodiment of the present invention. The main purpose of the flowchart 700 is to reflect the real situation of the topology state, and to avoid the damage of the SDN switch or the damage of the connection port, the damage information cannot be transmitted in time, and the real domain topology cannot be presented immediately.

In step S701, the SDN controller 30 periodically checks the time stamp of the heterogeneous domain topology connection information.

In step S702, the SDN controller 30 determines whether the time stamp is overdue, wherein the overdue criterion is a parameter that can be flexibly adjusted. In an embodiment of the invention, 15 seconds is used as the overdue time, and the regular time is 5 seconds as a unit. In other words, if the topology information cannot be obtained after three times in a regular time, the SDN controller 30 will judge that the heterogeneous domain topology connection information is overdue (ie, the timestamp is overdue). If the time stamp expires, the process proceeds to step S704, and if not, the process proceeds to step S703.

In step S703, the SDN controller 30 continues to retain the heterogeneous domain topology connection information. On the other hand, in step S704, the SDN controller 30 transmits the deleted heterogeneous domain topology connection information to the centralized heterogeneous domain topology management module 121.

In summary, the present invention provides a heterogeneous software definition network controller and a management apparatus and method thereof, which are defined by reorganizing a standardized link layer discovery protocol and a centralized control method for detecting a heterogeneous software to define a network controller, automatically Detect the full domain topology. The system of the present invention comprises a centralized link layer discovery protocol reorganization definition module and a domain topology detection module of a heterogeneous software definition network controller. The centralized link layer discovery protocol reorganization definition module is linked to the topology collection application of each SDN controller, and is used to define and elastically transmit the link layer discovery protocol packet format, so that the topology collection application installed in each controller is configured. It is possible to collect heterogeneous domain data using a uniformly standardized link layer discovery protocol. The domain topology detection module of the heterogeneous software definition network controller uses the centralized heterogeneous domain topology management module to trigger the events of each controller to send LLDP packets, and integrates the heterogeneous domain topology data to achieve cross-domain Comprehensive presentation of regional comprehensive domain topology data.

The features and effects of the invention:

The heterogeneous software definition network controller and the management apparatus and method thereof provided by the embodiments of the present invention have the following advantages when compared with other conventional technologies: 1. The invention has a unified LLDP packet format technology for the SDN network. The road device is modified to design a suitable LLDP format. When the topology of the network is detected under the domain controlled by multiple SDN controllers, the format of the topology collection and the format of the LLDP packet are different, which makes it difficult for the respective policies to be integrated, and the upper OSS/BSS system cannot be Get the overall picture of the domain. The invention can expand the characteristics of the application by using the software definition network, and design a unified and flexible LLDP format mechanism, and the software of the LLDP packet format is different, but the software of the same LLDP packet format defines the heterogeneous network controller of the network controller. The domain topology monitoring application triggers the event request for sending LLDP packets through the switch under the SDN controller or the SDN controller requests the upper module to send LLDP packets, because the packets sent by each controller have the same format, so Can be identified for each other, the final controller will then send the completed data to the main management module of the overall network topology; centralized heterogeneous domain topology management module. 2. The invention has an elastic LLDP packet parsing mechanism, and is compatible with a commercial SDN controller through an LLDP packet format that can be flexibly modified according to the network environment, and an elastic LLDP packet format parsing method, thereby achieving integration of multiple schemes. It is suitable for the SDN controller management of multiple brands of heterogeneous networks. In addition, the heterogeneous domain topology monitoring application of the software-defined network controller can flexibly input the required format when a new commercial SDN controller is imported. The old heterogeneous domain topology monitoring application does not need to modify the code. Just fill in the required information and quickly use the new SDN controller to achieve fast deployment of the SDN controller. 3. Due to the existing environment, known systems have difficulty recognizing the global topology when there are multiple different brands of controllers managing the domain. Taking RYU and OpenDaylight as an example, because the LLDP packet formats sent by the two are different, the packets sent by the two cannot be identified by the other party and will be discarded. Therefore, each controller can only obtain local topology information, and the connection between each part. It will not be recognized. However, the method and system for centrally controlling and detecting the domain topology of the heterogeneous software-defined network controller using the recombination definition standardized link layer discovery protocol of the present invention can break through the current technical difficulties.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and any one of ordinary skill in the art can make some changes and refinements without departing from the spirit and scope of the present invention. The scope of the invention is defined by the scope of the appended claims.

10‧‧‧Devices for managing heterogeneous SDN controllers

100, 300‧‧‧ storage unit

110‧‧‧Centralized Link Layer Discovery Protocol Reorganization Definition Module

111‧‧‧Link Layer Discovery Protocol Format Operation Module

112‧‧‧Commitment format resource and software definition network controller relationship knowledge base

113‧‧‧Link layer discovery agreement reorganization module

114‧‧‧Link Layer Discovery Protocol Registration Module

120‧‧‧Heteromorphic software defines the network topology detection module of the network controller

121‧‧‧Centralized heterogeneous domain topology management module

122‧‧‧Heterogeneous software defines the domain topology knowledge base of the network controller

130, 330‧‧‧ processor

140, 340‧‧‧ transceiver

200‧‧‧LLDP packet format

210‧‧‧chassis identification code

211‧‧‧埠ID

212‧‧‧Aging time

213‧‧‧System Name

214‧‧‧End of LLDPDU

30‧‧‧SDN Controller

310‧‧‧ Heterogeneous Domain Topology Monitoring Application Module

400, 500, 600, 700‧‧‧ Method flow

S401, S402, S403, S404, S405, S406, S501, S502, S503, S504, S505, S506, S507, S508, S509, S601, S602, S603, S604, S605, S606, S607, S608, S609, SS701, S702, S703, S704‧‧‧ steps

1 is a schematic diagram of an apparatus for managing a heterogeneous SDN controller in accordance with an embodiment of the present invention. 2 is a LLDP packet format in accordance with an embodiment of the present invention. 3 is a schematic diagram of an SDN controller and the network it manages in accordance with an embodiment of the present invention. 4 is a flow chart of a method of managing an SDN controller in accordance with an embodiment of the present invention. 5 is a flow chart of monitoring the connection and topology of a SDN switch by a domain topology detection module of a heterogeneous software-defined network controller in accordance with an embodiment of the present invention. 6 is a flow diagram of transmitting LLDP packets periodically or once, in accordance with an embodiment of the present invention. 7 is a flow diagram of a mechanism for periodically transmitting LLDP packets to detect timestamps used in a domain topology, in accordance with an embodiment of the present invention.

Claims (10)

A method for managing a heterogeneous software defining a network controller, configured to manage a first software defined network controller and a second software defined network controller, wherein the first software defines a first link used by the network controller The layer discovery protocol packet format is different from the second link layer discovery protocol packet format used by the second software definition network controller, the method comprising: responsive to receiving the first software defined network controller from the heterogeneous network a registration request, defining a third link layer discovery protocol packet format, wherein the third link layer discovery protocol packet format is different from the first link layer discovery protocol packet format, and different from the second link layer discovery protocol a packet format; transmitting a template of the third link layer discovery protocol packet format to the first software-defined network controller; and receiving a message from the first software-defined network controller to update the domain topology. The method of claim 1, further comprising: determining whether the first software defines a network controller to comply with a control scope, and if so, defining the third link layer discovery protocol packet format; Otherwise, the first software defined network controller cannot be registered to the first software defined network controller. The method of claim 1, further comprising: selecting a type/length/value corresponding to the chassis identification code, the 埠 identification code, the aging time, and the end of the link layer discovery protocol data unit (Type/Length/Value , The TLV) field is used to determine whether the third link layer discovery protocol packet format conforms to the basic rules of the link layer discovery protocol packet. The method of claim 1, further comprising: updating the domain topology in response to receiving a related message of the connection state event. A method for defining a network management domain topology in a heterogeneous software, suitable for a software-defined network controller, the method comprising: the first software defining a network controller to transmit a registration request through a heterogeneous network, wherein the heterogeneous network The first software defined network controller and the second software defined network controller, wherein the first link layer discovery protocol packet format used by the first software defined network controller is different from the second software defined network The second link layer discovery protocol packet format used by the path controller; in response to transmitting the registration request, receiving a template of the newly defined link layer discovery protocol packet format, wherein the newly defined link layer discovery protocol packet format is different And discovering the protocol packet format at the first link layer, and different from the second link layer discovery protocol packet format; and managing the domain topology based on the newly defined link layer discovery protocol packet format. The method of claim 5, further comprising: determining whether the link layer discovery protocol packet format conforms to a basic rule of a link layer discovery protocol packet, and if yes, discovering the link layer based on the new definition The protocol packet format to reorganize the heterogeneous domain topology connection information; and if not, discard the new defined link layer discovery protocol packet format this. The method of claim 6, further comprising: determining whether the heterogeneous domain topology connection information already exists, and if yes, updating a timestamp of the heterogeneous domain topology connection information; and If not, the time stamp is given for the time formed by the heterogeneous domain topology connection information, and an update message of the heterogeneous domain topology connection information is sent. The method of claim 5, further comprising: the switch within the control scope periodically transmitting the packet of the newly defined link layer discovery protocol packet format to the switch port. A device for managing a heterogeneous software defining a network controller, configured to manage a first software defined network controller and a second software defined network controller, wherein the first software defines a first link used by the network controller The layer discovery protocol packet format is different from the second link layer discovery protocol packet format used by the second software definition network controller, and the device includes: a transceiver, transmitting or receiving data; and a storage unit, recording multiple modules; And the processing unit is coupled to the storage unit and accesses and executes the modules stored by the storage unit, where the modules include: a centralized link layer discovery protocol reorganization definition module, including: link layer discovery The protocol registration module receives the registration request of the first software-defined network controller from the heterogeneous network through the transceiver, defines a third link layer discovery protocol packet format, and transmits the request according to the registration request. Sending a template of the link layer discovery protocol packet format to the first software-defined network controller, where the third link layer discovery protocol packet format is different from the first link layer discovery protocol packet format, and different from the The second link layer discovers the protocol packet format; the heterogeneous software defines the domain topology detection module of the network controller, including: a centralized heterogeneous domain topology management module, and receives the network control from the first software definition Message to update the domain topology. A software-defined network controller adapted to use a first link layer discovery protocol packet format, including: a transceiver to transmit a registration request over a heterogeneous network, wherein the heterogeneous network includes a second software-defined network controller, and The first link layer discovery protocol packet format is different from the second link layer discovery protocol packet format used by the second software-defined network controller; and the processor is configured to perform: in response to transmitting the registration request, Receiving, by the transceiver, a template of a newly defined link layer discovery protocol packet format, where the newly defined link layer discovery protocol packet format is different from the first link layer discovery protocol packet format, and different from the second chain The layer layer discovers the protocol packet format; and manages the domain topology based on the newly defined link layer discovery protocol packet format.