CN115701044A

CN115701044A - Method and device for acquiring network topology

Info

Publication number: CN115701044A
Application number: CN202110827059.8A
Authority: CN
Inventors: 储伯森; 沙李; 李良格; 施大年
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-07-21
Filing date: 2021-07-21
Publication date: 2023-02-07

Abstract

The embodiment of the application provides a method and a related device for acquiring network topology, which are used for accelerating the collection of topology information and improving the speed of topology discovery. The embodiment of the application provides a method for acquiring a network topology, which is particularly applied to an XLDP network topology structure, wherein the network topology structure comprises a plurality of nodes, including a first node and a second node for acquiring the network topology; when the network topology structure works initially, the first node acquires the information of the second node; then the first node reports a first message to the second node according to the information of the second node, wherein the first message is used for announcing the topology condition of the first node to the second node, that is, the first message at least comprises the identifier of the first node, the identifier of a third node serving as a neighbor node of the first node, and the identifier of a first port for the first node to communicate with the third node.

Description

Method and device for acquiring network topology

Technical Field

The present application relates to the field of communications, and in particular, to a method and an apparatus for acquiring a network topology.

Background

With the development of communication technology, a large number of communication devices are deployed in each campus or office. In order to manage the devices conveniently, an extremely simple Discovery Protocol (XLDP) architecture is introduced. The XLDP protocol architecture is a very simple centralized topology discovery technology under an X-Lean architecture. The XLDP protocol architecture may be as shown in fig. 1: the root node is a central node of the whole network and is responsible for centralized topology discovery of the whole network, channel maintenance from the root node to each non-root node (including a root port and a downlink path of each non-root node), a protocol state machine and a protocol message transceiving mechanism. And the functional modules of the non-root nodes comprise protocol messaging, a protocol state machine and a device information acquisition/configuration agent. The core process mainly comprises the following steps: and (2) carrying out topology discovery in a centralized manner by the root nodes, only responding by the non-root nodes and reporting the most basic link state, and identifying and assigning the roles of ports through topology calculation to realize centralized forwarding of control messages (all the control messages initiated by the non-root nodes are sent to the root nodes from the root ports, all the control messages initiated by the root nodes are assigned to the output ports along the way, and the non-root nodes are directly forwarded by a source route).

Based on the structure, the XLDP protocol structure needs active detection initiated by the root node when topology discovery is carried out, and non-root nodes do not report actively. At least 4 messages, two round trips, are required for each non-root topology discovery. Large message volume and low speed.

Therefore, a method for increasing the topology discovery speed is urgently needed.

Disclosure of Invention

The embodiment of the application provides a method and a device for acquiring a network topology, which are used for accelerating the collection of topology information and improving the topology discovery speed.

In a first aspect, an embodiment of the present application provides a method for acquiring a network topology, which is specifically applied to an XLDP network topology structure, where the network topology structure includes a plurality of nodes, including a first node and a second node for acquiring the network topology; when the network topology structure works initially, the first node acquires the information of the second node; then the first node reports a first message to the second node according to the information of the second node, wherein the first message is used for announcing the topology condition of the first node to the second node, that is, the first message at least comprises the identifier of the first node, the identifier of a third node serving as a neighbor node of the first node, and the identifier of a first port for the first node to communicate with the third node.

In this embodiment, the second node for acquiring the network topology may also be referred to as a root node (i.e., a root node), and the first node may also be referred to as a non-root node (i.e., a non-root node). The root node is a central node of the whole network topology and is responsible for centralized topology discovery of the whole network, path maintenance from the root node to each non-root node (including a root port (i.e., a port for uplink) and a downlink path of each non-root node), a protocol state machine and a protocol message transceiving mechanism. The non-root node is mainly responsible for protocol message transceiving, a protocol state machine and a device information acquisition/configuration agent. The specific process is as follows: the root nodes collectively discover the network topology, the non-root nodes only respond and report the most basic link state, and the roles of the non-root nodes and the most basic link state are identified and designated through topology calculation, so that the control message is centrally forwarded (all the control messages initiated by the non-root nodes are sent to the root nodes from the root ports, all the control messages initiated by the root nodes are designated along-way exit ports, and the non-root nodes are directly forwarded by a source route).

In this embodiment, after acquiring the information of the second node, the first node for data transmission may actively report topology information of itself to the second node. Therefore, when the network topology comprises a plurality of nodes for data transmission, the second node is prevented from inquiring the topology information of each node for data transmission one by one, so that the collection of the network topology information is accelerated, and the topology discovery speed is improved.

Optionally, the information of the second node may include multiple cases, and the first node may have different operations based on the difference of the information of the second node:

in a possible implementation manner, the information of the second node includes an identifier and indication information of the second node, and the indication information is only used to identify the second node for acquiring the network topology, then the first node acquires a second port that receives the information of the second node, and determines that the second port is a port for forwarding an uplink packet (i.e., a root port of the first node); the first node then sends the first message to the second node through the second port.

In another possible implementation manner, the information of the second node includes an identifier of the second node, indication information, and an identifier of a third port through which the first node communicates with the second node, where the indication information is used to identify the second node for acquiring a network topology, and at this time, the first node may send the first message to the second node through a port corresponding to the identifier of the third port based on the information of the second node.

Optionally, when the first node acquires the information of the second node, the following possible implementation manners may be specifically adopted:

in a possible implementation manner, the first node obtains the statically configured information of the second node, that is, after determining that the second node is the central node in the network topology, the information of the second node is directly pre-stored in the first node in a configuration manner, and in the process of obtaining the network topology, the first node may directly read the information of the second node from its own memory.

In another possible implementation manner, the first node receives a second message sent by the second node, where the second message includes information of the second node. It is understood that the second message may be a link discovery message or a root node advertisement message in this embodiment. If the second message is the root node advertisement message provided in this embodiment, the root node advertisement message may indicate information of the two nodes by using a root node identifier field.

Optionally, after the first node reports the first message to the second node and the second node receives the first message, the second node sends a third message to the first node, where the third message is used to notify the first node that the second node confirms receiving the first message.

Optionally, after the first node acquires the information of the second node, the first node may further send a fourth message to a neighboring node thereof, where the fourth message includes the information of the second node; and then the first node receives a fifth message sent by the third node, wherein the fifth message comprises the identifier of the third node, the identifier of a fourth node serving as a neighbor node of the third node, and the identifier of a port for the third node to communicate with the fourth node. That is, in this embodiment, the first node may advertise the information of the second node to its neighboring nodes, and the third node sends a fifth message for advertising its port information to the first node, and then forwards the information of the third node to the second node. Therefore, the second node does not need to wait for the inquiry information to be sent to the third node, and then the third node reports the self topology information to the second node, so that the number of times of signaling transmission of the second node in the network topology can be reduced.

Based on the above solution, if the fifth message further includes indication information, and the indication information is used to identify that the fifth message belongs to an uplink packet, the first node acquires a port communicating with the second node according to the indication information included in the fifth message; the first node then sends the fifth message from the port communicating with the second node. Therefore, the first node can forward the fifth message only according to the indication information in the fifth message without data processing, and the processing amount of the first node is reduced.

Based on the above method for acquiring a network topology, in the method, if there is a failure in communication between the first node and the second node, that is, if the first node loses the root node in the network topology, the first node sends a sixth message to the third node, where the sixth message is used to notify that there is a failure in communication between the first node and the second node. That is, after the first node loses the root node, the first node can notify the neighbor node of the communication failure in real time, so that the neighbor node is prevented from continuously sending the uplink message.

Optionally, if the third node further has a neighboring node of a lower layer, after learning that there is a failure in communication with the second node, the third node also sends a message to the neighboring node of the lower layer to notify that there is a failure in communication between the neighboring node and the second node.

Optionally, if there are at least two ports (i.e. the first port and the fourth port) of the first node that can communicate with the second node, the first node will communicate with the second node through another port (i.e. the fourth port) after a failure occurs in communication between the first node and one of the ports (the first port) of the second node. For example, when the first node communicates with the second node, the first node includes a main port and a standby port, and at a first time, the first node communicates with the second node through the main port; and at the second moment, when a link of the first node and the second node which communicate through the main port fails, the first node is switched to the standby port to communicate with the second node. Therefore, the switching of the network topology can be realized in real time, and the normal network communication is ensured.

In a second aspect, the present application provides a communication device having a function of implementing the behavior of the first node in the first aspect. The function can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible implementation, the apparatus comprises means or modules for performing the steps of the first aspect above. For example, the apparatus includes: the acquisition module is used for acquiring information of a second node for acquiring network topology;

a sending module, configured to send a first message to the second node according to the information of the second node, where the first message includes an identifier of the first node, an identifier of a third node serving as a neighboring node of the first node, and an identifier of a first port through which the first node communicates with the third node.

Optionally, the device further comprises a storage module for storing necessary program instructions and data of the communication device.

In one possible implementation, the communication device includes: a processor and a transceiver, the processor being configured to enable the communication device to perform the respective functions of the method provided by the first aspect described above. The transceiver is configured to instruct communication between the first node and the second node and a third node, send a first message involved in the method to the second node, and send a fourth message involved in the method to the third node. Optionally, the communication device may further include a memory for coupling with the processor that retains program instructions and data necessary for the communication device.

In one possible implementation, when the communication device is a chip within a communication device, the chip includes: the device comprises a processing module and a transceiver module. The transceiver module may be, for example, an input/output interface, a pin, a circuit, or the like on the chip, and the transceiver module acquires information for acquiring a second node of the network topology; and sending a first message to the second node according to the information of the second node, wherein the first message comprises the identifier of the first node, the identifier of a third node serving as a neighbor node of the first node, and the identifier of a first port of the first node for communicating with the third node. The processing module may be, for example, a processor configured to generate the first message and transmit the first message generated by the processor to another chip or module coupled to the chip. The processing module may execute computer executable instructions stored by the memory unit to enable the communication device to perform the method provided by the first aspect. Alternatively, the storage unit may be a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip, such as a read-only memory (ROM) or another type of static storage device that can store static information and instructions, a Random Access Memory (RAM), and the like.

In one possible implementation, the communication device includes: a processor, baseband circuitry, radio frequency circuitry, and an antenna. The processor is used for realizing control of functions of each circuit part, and the baseband circuit is used for generating the first message, carrying out analog conversion, filtering, amplification, up-conversion and other processing through the radio frequency circuit, and then sending the first message to the second node through the antenna. Optionally, the apparatus further comprises a memory that stores program instructions and data necessary for the communication device.

In one possible implementation, the apparatus includes a communication interface to obtain information for obtaining a second node of a network topology; the logic circuitry to generate the first message; the communication interface is further configured to send a first message to the second node according to the information of the second node, where the first message includes an identifier of the first node, an identifier of a third node serving as a neighbor node of the first node, and an identifier of a first port through which the first node communicates with the third node.

The processor mentioned in any of the above may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling program execution of the method for acquiring network topology according to the above aspects.

In a third aspect, an embodiment of the present application provides a computer-readable storage medium, where computer instructions are stored, and the computer instructions are configured to perform the method according to any possible implementation manner of any one of the foregoing aspects.

In a fourth aspect, embodiments of the present application provide a computer program comprising instructions which, when run on a computer, cause the computer to perform the method of any one of the above aspects.

In a fifth aspect, the present application provides a chip system comprising a processor for enabling a communication device to implement the functions referred to in the above aspects, such as generating or processing data and/or information referred to in the above methods. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the communication device to implement the functionality of any of the above aspects. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

In a sixth aspect, an embodiment of the present application provides a communication system, which includes the first node, the second node, and the third node in the above aspect.

Drawings

FIG. 1 is a schematic diagram of the structure of XLDP;

FIG. 2 is another schematic representation of the structure of XLDP;

FIG. 3 is another schematic representation of the structure of XLDP;

FIG. 4 is a schematic diagram of an embodiment of a method for obtaining a network topology according to an embodiment of the present application;

fig. 5 is a schematic diagram of a format of a topology advertisement message in an embodiment of the present application;

fig. 6 is a schematic diagram illustrating a format of a topology confirmation message according to an embodiment of the present application;

FIG. 7 is a schematic diagram of another embodiment of a method for obtaining a network topology according to an embodiment of the present application;

fig. 8 is a schematic diagram of a format of a root node advertisement message in an embodiment of the present application;

fig. 9 is a schematic diagram of another embodiment of a method for acquiring a network topology according to an embodiment of the present application;

FIG. 10 is a diagram of an embodiment of discovering a network topology when the network topology fails according to an embodiment of the present application;

FIG. 11 is a diagram illustrating a network topology failure according to an embodiment of the present application;

FIG. 12 is a diagram of another embodiment of discovering a network topology when the network topology fails according to an embodiment of the present application;

FIG. 13 is another schematic diagram of a network topology failure according to an embodiment of the present application;

fig. 14 is a schematic diagram of another embodiment of a method for acquiring a network topology according to an embodiment of the present application;

fig. 15 is a schematic diagram of an embodiment of a communication device in an embodiment of the present application;

fig. 16 is a schematic diagram of another embodiment of the communication device in the embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application are described below with reference to the accompanying drawings, and it is obvious that the described embodiments are only some embodiments of the present application, but not all embodiments. As can be known to those skilled in the art, with the advent of new application scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

The terms "first," "second," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Moreover, the terms "comprises," "comprising," and any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not expressly listed or inherent to such process, method, article, or apparatus. The naming or numbering of the steps appearing in the present application does not mean that the steps in the method flow have to be executed in the chronological/logical order indicated by the naming or numbering, and the named or numbered process steps may be executed in a modified order depending on the technical purpose to be achieved, as long as the same or similar technical effects are achieved. The division of the units presented in this application is a logical division, and in practical applications, there may be another division, for example, multiple units may be combined or integrated in another system, or some features may be omitted, or not executed, and in addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some interfaces, and the indirect coupling or communication connection between the units may be in an electrical or other similar form, which is not limited in this application. Furthermore, the units or sub-units described as the separate parts may or may not be physically separate, may or may not be physical units, or may be distributed in a plurality of circuit units, and some or all of the units may be selected according to actual needs to achieve the purpose of the present disclosure.

For convenience of understanding, some terms in the embodiments of the present application are explained:

XLDP (X-Bean Discovery Protocol): the method is a very simple centralized topology discovery technology under an X-Lean architecture, a central device initiates topology discovery information in a centralized manner, other devices only need to make very simple response to automatically construct topology, automatically discover uplink and downlink, and keep a table-free and stateless state, so that a campus switch is free from rule and configuration, plug and play are realized, service and device are truly decoupled, and management of a campus is simplified. An exemplary architecture of which may be shown in fig. 1, wherein the network topology under the X-Lean architecture includes root nodes and non-root nodes (which may also be referred to as node1 and node2 in fig. 1).

root node: also known as the root node. The root node is a central node of a network topology under the whole X-Lean architecture and is responsible for centralizing whole network topology discovery, channel maintenance from the root node to each non-root node (including a root port (i.e. a port used for uplink) and a downlink path of each non-root node), a protocol state machine and a protocol message transceiving mechanism.

Non-root nodes: also referred to as child nodes. The non-root node is mainly responsible for protocol message transceiving, a protocol state machine and a device information acquisition/configuration agent.

root port: also called root port, that is, the port for receiving the downlink packet sent by the root node.

Non-root port: and a port for receiving the uplink message sent by the non-root node.

Based on the architecture shown in fig. 1, the communication flow between the root node and the non-root node may be as follows: the root nodes collectively perform network topology discovery, non-root nodes only perform response and report the most basic link state, and the role of a port is identified and designated through topology calculation, so that the centralized forwarding of control messages (such as XLDP messages shown in figure 1) is realized (all control messages initiated by the non-root nodes are sent to the root nodes from the root ports, all control messages initiated by the root nodes are designated as outgoing ports, and the non-root nodes are directly forwarded by a source route). In an exemplary scheme, the structure between the root node and the non-root node may be as shown in fig. 2 and 3:

in the XLDP structure shown in FIG. 2, the root node is S1, which includes non-root ports: port1 and port2, the non-root node comprising S2, S3 and S4, wherein the S2 comprises a root port3 and a non-root port4, the S3 comprises a root port5, and the S4 comprises a root port6. The S1, the S2 and the S4 form a link, wherein the S2 and the S4 are mutually neighbor nodes, and the S4 needs to communicate with the S1 through the S2; and the S3 and the S1 form another link. If the S1 needs to send a downlink message to the S4, the S1 sends the downlink message to the S2 through the port1, and the S2 receives the downlink message through the port3, and then the S2 sends the downlink message to the S4 through the port4, and the S4 receives the downlink message through the port6.

In the XLDP structure shown in fig. 3, the root node is S1, and the root node includes a non-root port: port1 and port2, the non-root nodes comprising S2, S3 and S4, wherein the S2 comprises a root port3 and a non-root port4, the S3 comprises a root port5 and a non-root port6, the S4 comprises a root port7 and a root port8, wherein, only one port will work at the same time in the port7 and the port8, that is, a master root port can be set between the port7 and the port8, as shown in fig. 3, the port7 is a master root port, and the port8 is a slave root port. The S1, the S2 and the S4 form a link, wherein the S2 and the S4 are mutually neighbor nodes, and the S4 is communicated with the S1 through the S2; the S1, the S3 and the S4 form another link, the S3 and the S4 are also neighboring nodes, and the S4 can also communicate with the S1 through the S3. As shown in fig. 3, when the port7 is a master root port, if the S1 needs to send a downlink message to the S4, the S1 sends the downlink message to the S2 through the port1, the S2 receives the downlink message through the port3, the S2 sends the downlink message to the S4 through the port4, and the S4 receives the downlink message through the port6.

Based on the XLDP framework, the embodiment of the present application provides the following technical solutions: the XLDP network topology structure comprises a plurality of nodes, wherein the plurality of nodes comprise a first node and a second node used for acquiring the network topology; when the network topology structure works initially, the first node acquires the information of the second node; then the first node reports a first message to the second node according to the information of the second node, wherein the first message is used for announcing the topology condition of the first node to the second node, that is, the first message at least comprises the identifier of the first node, the identifier of a third node serving as a neighbor node of the first node, and the identifier of a first port for the first node to communicate with the third node.

It can be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a Long Term Evolution (Long Term Evolution) System, an LTE (Frequency Division Duplex) System, an LTE Time Division Duplex (FDD) System, a Time Division Duplex (TDD) System, a Universal Mobile Telecommunications System (UMTS), a 5G Communication System, and a future wireless Communication System.

The first node, the second node or the third node in this application may be a user equipment or a network equipment. The User Equipment (UE) may also refer to a terminal device, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved PLMN network, etc. The Network device may be a device for communicating with a user equipment, and for example, may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB, or eNodeB) in an LTE system, or may be a Network side device in a relay Station, an access point, a vehicle-mounted device, a wearable device, and a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) Network for future evolution, and the like.

The following describes a method for acquiring a network topology according to the present application with reference to the drawings.

Taking the structure shown in fig. 2 as an example, S2 is the first node, S1 is the second node, and S4 is the third node. Specifically, referring to fig. 4, an embodiment of the method for acquiring a network topology according to the present application includes:

401. the first node acquires the information of the second node through static configuration.

After the XLDP network structure is constructed and the second node is determined to be a communication device for acquiring the network topology, the first node directly prestores the information of the second node in a memory of the first node in a static configuration manner.

In this embodiment, the information of the second node includes an identifier of the second node and indication information, where the indication information is used to identify the second node and to obtain a network topology;

or,

the information of the second node includes an identification of the second node, indication information, and an identification of a third port through which the first node communicates with the second node.

As shown in fig. 2, after S1 is confirmed as a root node, the user may statically configure the information of S1 to S2. At this time, the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure), and indication information. Or, the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure), indication information, and port information (e.g., port1 and port3 shown in fig. 2) communicated between S1 and S2.

402. The first node sends a first message to the second node, the first message including an identifier of the first node, an identifier of a third node that is a neighbor node of the first node, and an identifier of a first port through which the first node communicates with the third node.

After the second node triggers and acquires the network topology, the first node reads the pre-stored information of the second node; and then reporting the first message to the second node according to the information of the second node. The first message is mainly used for reporting topology information of the first node in the network topology to the second node. The first message may therefore include an identification of the first node, an identification of a third node that is a neighbor node to the first node, and an identification of a first port through which the first node communicates with the third node.

In this embodiment, the operation of the first node sending the first message according to the information of the second node may be as follows:

in one possible implementation, the first node confirms that the port receiving the information of the second node is a port for communicating with the second node, and then the first node sends the first message to the second node according to the port for communicating with the second node. As shown in fig. 2, when the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure) and indication information, S2 confirms that port3 of S1 information is received, and is a port through which S2 communicates with S1; the S2 then reports the first message to the S1 via the port 3.

In another possible implementation manner, the first node acquires the communication ports of the first node and the second node according to the information of the second node, and then reports the first message to the second node through the communication port. As shown in fig. 2, when the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure), indication information, and an indication that port3 and port1 are ports between the first node and the second node, the S2 confirms that port3 is a port through which S2 communicates with S1 through the information of S1; the S2 then reports the first message to the S1 via the port 3.

403. The second node sends a third message to the first node, the third message being used to acknowledge receipt of the first message.

After the second node receives the first message sent by the first node, the second node sends an acknowledgement response to the first node, that is, the second node sends a third message to the first node, and the third message is used for acknowledging the receipt of the first message.

In this embodiment, the first message may be named a Topology Notification Message (TNM), and the third message may be named a Topology Notification Acknowledgement Message (TNAM). It is understood that the first message and the third message may also have other possible naming manners, and are not limited herein.

In this embodiment, the first message at least includes the following fields:

dev _ ID: which may be identified using 32 bytes. Which is specifically used to indicate the unique identity of the device that sent this TNM message.

Nbr _ Dev _ ID, which may be identified in 32 bytes. The device unique identity of the neighbor node indicating the device that sent the TNM message. Here, the illegal Nbr _ Dev _ ID may be represented by an indication value FFFFFFFF.

Port _ ID: which may be identified using 2 bytes. It is used to represent the port identification in the forwarding table and to encapsulate the path information of the downlink message. I.e. the port identity indicating the communication between the device sending this TNM message and its neighbour nodes. For example, in the structure shown in fig. 2, when the S2 reports the topology information to the S1, it may be used to identify a communication port between S2 and S4 as port4.

It is understood that the first message may also include other fields, and the specific format thereof may be as shown in fig. 5:

DMAC: which may be identified using 6 bytes. It is specifically used to indicate a media access control address (MAC) of the destination. In an exemplary embodiment, the index value may be 01-80-C2-00-00-0E.

SMAC: which may be identified using 6 bytes. It is specifically used to indicate the source MAC, i.e. the MAC of the device that generated the protocol message.

Eth _ Type: which may be identified using 2 bytes. Which is used to indicate XLDP protocol identification. In an exemplary scheme, the indication value may be 0x88DD.

Path _ Type: which may be identified using 2 bytes. Which is used to indicate the uplink message identity. In an exemplary scheme, the indicated value may be 0xA002.

Msg _ Type: it can be identified using 7 bits (bit). Which is used to indicate that the message requires the opposite device to support XLDP protocol type. In an exemplary scheme, the message may be represented as a TNM message by an indication value of 18.

Length: which may be identified using 9 bits (bits). Which is used to indicate the length of the message after the length field.

Seq _ Num: which may be identified using 4 bytes. The method is specifically used for labeling the messages sent by the non-root nodes, and different serial numbers identify different messages sent by the non-root nodes.

Dev _ Type: which may be identified using 1 byte. Which is used to indicate the device type of the device that sent this TNM message. Such as 1 identifying the switch and 2 identifying the AP.

Port _ Sum: which may be identified using 2 bytes. Which indicates how many ports the device sending this TNM message has.

Port _ Name: which may be identified using 32 bytes. Which is used to identify the name of one of the ports of the device that sent the TNM message.

Port _ State: which may be identified using 1 byte. Which is used to indicate the status of the device port that sent this TNM message. In an exemplary scheme, the port may be indicated by an indicator value of 1 for uplink and an indicator value of 0 for downlink.

XLDP _ enable: which may be identified using 1 byte. And the port opposite equipment is used for indicating whether the port opposite equipment of the equipment sending the TNM message supports the XLDP protocol or not. In an exemplary scheme, the support may be indicated by an indication value of 1, and the support may be indicated by an indication value of 0.

Nbr _ Port _ Name: which may be identified using 32 bytes. Indicating the port name of the neighbor node of the device sending the TNM message with which the device sending the TNM message is communicating. For example, in the structure shown in fig. 2, if the S2 reports the topology information to the S1, the communication port between the S2 and the S4 may be identified as port4, and the port at which the S4 receives the downlink packet sent by the S2 is identified as port6.

The third message includes at least the following fields:

msg _ Type: it can be identified using 7 bits (bit). Which is used to indicate that the message requires the opposite device to support XLDP protocol type. In an exemplary scheme, the indication value of 19 may be used to indicate that the message is a TNAM message.

It is understood that the third message may also include other fields, the specific format of which may be as shown in fig. 6:

DMAC: which may be identified using 6 bytes. It is specifically used to indicate a media access control address (MAC) of the destination. In an exemplary embodiment, the indicator value may be 01-80-C2-00-00-0E.

SMAC: which may be identified using 6 bytes. It is specifically used to indicate the source MAC, i.e. the MAC of the device that generated the protocol packet.

Path _ Type: which may be identified using 2 bytes. Which is used for indicating the downlink message identification. In an exemplary scheme, the indicated value may be 0xA001.

Seq _ Num: which may be identified using 4 bytes. It is specifically used to label the message sent by the root node, which corresponds to the sequence number of the TNM information.

Dev _ ID: which may be identified using 32 bytes. Which is specifically used to indicate the unique identity of the device receiving this TNAM message.

Dev _ Type: which may be identified using 1 byte. Which is used to indicate the device type of the device receiving this TNM message. Such as 1 identifying the switch and 2 identifying the AP.

Specifically referring to fig. 7, another embodiment of the method for acquiring a network topology according to the present application includes:

701. and the first node and the second node mutually send neighbor advertisement messages to confirm that the first node and the second node are neighbor nodes.

After the device is powered on, neighbor advertisement messages (NNM) are mutually sent between adjacent devices (root nodes and non-root nodes, non-root nodes and non-root nodes) to inform the opposite terminal that the opposite terminal has XLDP capability. Therefore, the first node and the second node send NNM to each other to inform the opposite end of XLDP capability.

702. The second node sends a second message to the first node, the second message including information of the second node.

And when the second node confirms that the first node is a non-root node and the first node is a neighbor node of the non-root node, the second node sends the second message to the first node, wherein the second message comprises the information of the second node.

In this embodiment, the information of the second node includes an identifier of the second node and indication information, where the indication information is used to identify the second node and is used to obtain a network topology;

or,

As shown in fig. 2, after S1 is confirmed as a root node, S1 sends information of S1 to S2. At this time, the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure), and indication information. Or, the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure), indication information, and port information (e.g., port1 and port3 shown in fig. 2) communicated between S1 and S2.

703. The first node sends a first message to the second node, the first message including an identifier of the first node, an identifier of a third node that is a neighbor node of the first node, and an identifier of a first port through which the first node communicates with the third node.

After the first node acquires the information of the second node through a second message sent by the second node, the first node reports the first message to the second node according to the information of the second node. The first message is mainly used for reporting topology information of the first node in the network topology to the second node. The first message may therefore include an identification of the first node, an identification of a third node that is a neighbor node to the first node, and an identification of a first port through which the first node communicates with the third node.

in one possible implementation manner, the first node confirms that the port receiving the information of the second node is the port for communicating with the second node, and then the first node sends the first message to the second node according to the port for communicating with the second node. As shown in fig. 2, when the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure) and indication information, S2 confirms that port3 of S1 information is received, and is a port through which S2 communicates with S1; the S2 then reports the first message to the S1 via the port 3.

704. The second node sends a third message to the first node, the third message being used to acknowledge receipt of the first message.

In this embodiment, the second message may be named a Root Notification Message (RNM). It is understood that the second message may also have other possible naming manners, which are not limited herein.

In this embodiment, the second message at least includes the following fields:

root _ Dev _ ID, which may be identified in 32 bytes. Which is specifically used to indicate the device unique identity of the root node. Here, the illegal Root _ Dev _ ID may be represented by an indication value FFFFFFFF (i.e. when the S2 advertises the Root node information to the S4, for example, in the structure shown in fig. 2, if the indication value of Root _ Dev _ ID is FFFFFFFF, it indicates that the communication between the S2 and the S1 has a fault).

It will be appreciated that the second message may also include other fields, the specific format of which may be as shown in fig. 8:

DMAC: which may be identified using 6 bytes. It is specifically used to indicate the destination media access control address (MAC). In an exemplary embodiment, the index value may be 01-80-C2-00-00-0E.

Path _ Type: which may be identified using 2 bytes. Which is used to indicate the XLDP capability negotiation message. In an exemplary scheme, the indicated value may be 0xA003.

Msg _ Type: it can be identified using 7 bits (bit). Which is used to indicate that this message requires the opposite device to support XLDP protocol type. In an exemplary scheme, the message may be denoted as an RNM message by an indication value of 4.

Dev _ ID: which may be identified using 32 bytes. Which is specifically used to indicate the unique identity of the device that sent the RNM message. For example, in the structure shown in fig. 2, when the S1 sends the RNM information to the S2, the RNM information is used to identify the device identifier of the S1.

Root _ Port _ Name, which may be identified in 32 bytes. Which is specifically used to indicate the root port name. For example, in the structure shown in fig. 2, when the S2 sends the RNM information to the S4, the port identifier is used to identify the port identifier used by the S2 to receive the downlink packet sent by the S1.

Nbr _ Dev _ ID, which may be identified in 32 bytes. Which is specifically used to indicate the unique identity of the neighbor device connected to the root port of the device sending the RNM information. Here, the illegal Nbr _ Dev _ ID may be represented by an indication value FFFFFFFF. For example, in the structure shown in fig. 2, when the S2 sends the RNM information to the S4, the RNM information is used to identify the device identifier of the S1.

Nbr _ Port _ Name: which may be identified using 32 bytes. It is specifically used to indicate the neighbor port name of the neighbor device connected to the root port of the device that sent the RNM information. Such as the structure shown in fig. 2, is used to identify the port1 when the S2 sends the RNM information to the S4.

Specifically referring to fig. 9, another embodiment of the method for acquiring a network topology according to the present application includes:

901. and the first node and the third node mutually send neighbor advertisement messages to confirm that the first node and the third node are mutually neighbor nodes.

After the device is powered on, neighbor advertisement messages (NNM) are mutually sent between adjacent devices (root nodes and non-root nodes, non-root nodes and non-root nodes) to inform the opposite terminal that the opposite terminal has XLDP capability. Therefore, the first node and the third node send NNM to each other to inform the opposite end of XLDP capability.

902. The first node sends a fourth message to the third node, the fourth message including information of the second node.

When the first node confirms that the second node is a non-root node and the third node is a neighbor node of the second node, the first node sends the fourth message to the third node, and the fourth message comprises information of the second node.

or,

As shown in fig. 2, after S2 confirms that S1 is a root node, S2 sends the information of S1 to S4. At this time, the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure), and indication information. Or, the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure), indication information, and port information (such as port4 and port6 shown in fig. 2) communicated between S2 and S4.

903. The third node sends a fifth message to the first node, where the fifth message includes an identifier of the third node, an identifier of a fourth node that is a neighbor node of the third node, and a port identifier of the third node communicating with the fourth node.

After the third node acquires the information of the second node through a fourth message sent by the first node, the third node reports the fifth message to the first node according to the information of the second node. The fifth message is mainly used for reporting the topology information of the third node in the network topology to the second node. The fifth message may therefore comprise an identification of the third node, an identification of the fourth node as a neighbor node of the third node, and an identification of the port through which the third node communicates with the fourth node. It is understood that the fourth node includes at least the first node, and may include other nodes as well.

In this embodiment, the operation of the third node sending the fifth message according to the information of the second node may be as follows:

in a possible implementation manner, the third node confirms that the port receiving the information of the second node is a port for communicating with the second node (i.e., a port sending the uplink packet), and then the third node sends the fifth message through the port sending the uplink packet. As shown in fig. 2, when the information of S1 includes the identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure) and indication information, the S4 confirms that the port6 of S1 information is received, and sends an uplink packet to the port of S4; the S4 then sends the fifth message to the S21 via the port6.

In another possible implementation manner, the third node obtains the communication port between the third node and the second node according to the information of the second node, and then reports the fifth message to the second node through the communication port. As shown in fig. 2, when the information of S1 includes an identifier of S1 (in this embodiment, the identifier of S1 may be a device identifier, or a reference identifier of S1 in a network structure), indication information, and an instruction that the port6 sends an uplink packet to the third node, the S4 confirms that the port6 sends an uplink packet to the port of S4 through the information of S1; the S4 then sends the fifth message to the S21 through the port6.

904. The first node receives the fifth message and forwards the fifth message to the second node.

In this embodiment, the fifth message may further include indication information, where the indication information is used to indicate the first node to forward the port identifier of the fifth message. The first node then forwards the fifth message to the second node based on the port indicated in the fifth message after receiving the fifth message.

As shown in fig. 2, after acquiring the information of S1, S4 generates a fifth message for reporting the topology information of S4, and at the same time, indicates in the fifth message that S2 can forward the fifth message through port2, so that S2, after receiving the fifth message, forwards the fifth message to S1 according to port2 indicated by the fifth message.

905. The second node sends a seventh message to the first node, the seventh message acknowledging receipt of the fifth message.

After the second node receives the fifth message sent by the third node, the second node sends an acknowledgement response to the third node, that is, the second node sends a seventh message to the third node, where the seventh message is used to acknowledge the receipt of the first message. Since the first node is located between the third node and the second node, the second node needs to send the seventh message to the first node first.

906. The first node receives the seventh message and forwards the seventh message to the third node.

Similarly, the seventh message may further include indication information, where the indication information is used to indicate the port identifier of the seventh message to be forwarded by the first node. The first node then forwards the seventh message to the third node based on the port indicated in the seventh message after receiving the seventh message.

In the structure shown in fig. 2, after acquiring the topology information of S4, S1 generates a seventh message used to confirm that the fifth message of the topology information of S4 is received, and at the same time, the seventh message indicates that S2 can forward the seventh message through the port4, so that after receiving the seventh message, S2 forwards the seventh message to S4 according to the port4 indicated by the seventh message.

In this embodiment, the fourth message has the same format as the second message, the fifth message has the same format as the first message, and the seventh message has the same format as the third message, which are not described herein again.

The above mainly describes the method for acquiring the network topology in the embodiment of the present application, and based on the above scheme, the following describes a scheme when a communication failure occurs in the network topology.

Taking the structure shown in fig. 2 as an example, S2 is the first node, S1 is the second node, and S4 is the third node. Specifically referring to fig. 10, an embodiment of a method for acquiring a network topology according to the present application includes:

1001. and when the first node confirms that the communication between the first node and the second node has a fault, the first node sends a sixth message to the third node, wherein the sixth message is used for notifying that the communication with the second node has the fault.

When there is a failure in communication between the first node and the second node, and the first node confirms that the root node is lost, the first node sends a sixth message to the third node, where the sixth message is used to notify the third node that there is a failure in communication between the first node and the second node. As shown in fig. 11, if there is a failure in the communication between S1 and S2, the S2 will notify the S4 that the communication between S1 and S2 is failed. At this time, the root port (port 3) of S1 will be restored to a non-root port.

1002. The third node confirms that there is a failure in communication with the second node.

The third node, after receiving the sixth message, confirms that there is a failure in communication with the second node over this link. As shown in fig. 11, at this time, the root port (port 6) of S4 will be restored to a non-root port.

Taking the structure shown in fig. 3 as an example, S2 is the first node, S1 is the second node, and S4 is the third node. Specifically referring to fig. 12, an embodiment of a method for acquiring a network topology according to the present application includes:

1201. and when the first node confirms that the communication between the first node and the second node has a fault, the first node sends a sixth message to the third node, wherein the sixth message is used for notifying that the communication with the second node has the fault.

When there is a failure in communication between the first node and the second node, and the first node confirms that the root node is lost, the first node sends a sixth message to the third node, where the sixth message is used to notify the third node that there is a failure in communication between the first node and the second node. As shown in fig. 13, if there is a failure in the communication between S1 and S2, the S2 will notify the S4 that the communication between S1 and S2 is failed. At this time, the root port (port 3) of S1 will be restored to a non-root port.

1202. And the third node confirms that the communication with the second node has a fault and acquires a spare root port to communicate with the second node.

The third node, upon receiving the sixth message, acknowledges that there is a failure in communication with the second node on this link, and thus switches to communication with the second node on the backup link. As shown in fig. 13, at this time, the primary root port (port 7) of S4 will be restored to a non-root port, and the standby root port (port 8) will be switched to a primary root port.

Specifically, referring to fig. 14, an embodiment of the method for acquiring a network topology according to the present application includes:

1401. the first node acquires information of the second node.

In this embodiment, the first node may obtain the information of the second node in a manner described in any one of fig. 4 to 13, which is not described herein again in detail.

1402. The first node sends a first message to the second node according to the information of the second node, wherein the first message comprises the identification of the first node, the identification of a third node serving as a neighbor node of the first node, and the identification of a first port of the first node for communicating with the third node.

In this embodiment, the first node may report the first message to the second node in a manner described in any one of fig. 4 to 13. And will not be described herein in detail.

The above describes a method for acquiring a network topology in the embodiment of the present application, and the following describes a communication device in the embodiment of the present application.

Specifically, referring to fig. 15, in this embodiment, the communication device 1500 includes: the device comprises an acquisition module 1501 and a sending module 1502, wherein the acquisition module 1501 and the sending module 1502 are connected through a bus. The communication device 1500 may be the first node in the above method embodiments, and may also be configured as one or more chips within the first node. The communication device 1500 may be adapted to perform some or all of the functionality of the first node in the above-described method embodiments.

In an exemplary scheme, the obtaining module 1501 may be configured to perform step 401 or step 702 in the foregoing method embodiments. For example, the obtaining module 1501 is configured to obtain information of a second node used for obtaining the network topology; the sending module 1502 may be configured to execute step 402, or step 703, or step 902 in the foregoing method embodiment, for example, the sending module 1502 sends a first message to the second node according to the information of the second node, where the first message includes an identifier of the first node, an identifier of a third node that is a neighbor node of the first node, and an identifier of a first port through which the first node communicates with the third node.

Optionally, the communication device 1500 further includes a storage module and a processing module, where the storage module is coupled to the processing module, so that the processing module can execute computer-executable instructions stored in the storage module to implement the functions of the terminal in the foregoing method embodiments. In one example, the memory module optionally included in the communication device 1500 may be a memory unit within a chip, such as a register, a cache, etc., and the memory module may also be a memory unit located outside the chip, such as a ROM or other types of static memory devices that can store static information and instructions, a RAM, etc. The processing module in the communication device 1500 is configured to generate the first message or the fourth message.

It should be understood that the flow executed between the modules of the communication device in the corresponding embodiment of fig. 15 is similar to the flow executed by the first node in the corresponding method embodiment of fig. 4 to fig. 14, and details are not repeated here.

Fig. 16 shows a schematic diagram of a possible structure of a communication device 1600 in the above embodiment, and the communication device 1600 may be configured as the first node. The communication device 1600 may include: a processor 1602, a computer-readable storage medium/memory 1603, a transceiver 1604, an input device 1605, and an output device 1606, and a bus 1601. Wherein the processor, transceiver, computer readable storage medium, etc. are connected by a bus. The embodiments of the present application do not limit the specific connection medium between the above components.

In one example, the transceiver 1604 obtains information for obtaining a second node of the network topology;

the processor 1602 generates the first message;

the transceiver 1604 sends a first message to the second node according to the information of the second node, where the first message includes an identifier of the first node, an identifier of a third node that is a neighbor node of the first node, and an identifier of a first port through which the first node communicates with the third node.

In one example, the processor 1602 obtains information for obtaining a second node of the network topology; generating the first message; the transceiver 1604 sends a first message to the second node according to the information of the second node, where the first message includes an identifier of the first node, an identifier of a third node that is a neighbor node of the first node, and an identifier of a first port through which the first node communicates with the third node.

In one example, the processor 1602 may include baseband circuitry, e.g., may generate the first message or the fourth message. The transceiver 1604 may comprise radio frequency circuitry to modulate, amplify, etc., the first message or the fourth message before transmitting to the second node or the third node.

In yet another example, the processor 1602 may run an operating system that controls functions between various devices and appliances. The transceiver 1604 may comprise baseband circuitry and radio frequency circuitry, and may process the first message or the fourth message for transmission to the second node or the third node, for example, via the baseband circuitry and the radio frequency circuitry.

The transceiver 1604 and the processor 1602 may implement corresponding steps in any one of the embodiments of fig. 4 to fig. 14, which are not described herein in detail.

It is understood that fig. 16 merely illustrates a simplified design of a communication device, and in practical applications, the communication device may include any number of transceivers, processors, memories, etc., and all communication devices that may implement the present application are within the scope of the present application.

The processor 1602 involved in the communication device 1600 may be a general-purpose processor, such as a CPU, a Network Processor (NP), a microprocessor, etc., or may be an ASIC, or one or more integrated circuits for controlling the execution of programs according to the present invention. But also Digital Signal Processors (DSPs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The controller/processor can also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, and the like. Processors typically perform logical and arithmetic operations based on program instructions stored within memory.

The bus 1601 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industrial Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 16, but this is not intended to represent only one bus or type of bus.

The computer-readable storage medium/memory 1603 referred to above may also hold an operating system and other application programs. In particular, the program may include program code comprising computer operating instructions. More specifically, the memory may be ROM, other types of static storage devices that may store static information and instructions, RAM, other types of dynamic storage devices that may store information and instructions, disk storage, and the like. Memory 1603 may be a combination of the types of storage described above. And the computer-readable storage medium/memory described above may be in the processor, may be external to the processor, or distributed across multiple entities including the processor or processing circuitry. The computer-readable storage medium/memory described above may be embodied in a computer program product. By way of example, a computer program product may include a computer-readable medium in packaging material.

Alternatively, embodiments of the present application also provide a general-purpose processing system, such as that commonly referred to as a chip, including one or more microprocessors that provide processor functionality; and an external memory providing at least a portion of the storage medium, all connected together with other supporting circuitry via an external bus architecture. The memory stores instructions that, when executed by the processor, cause the processor to perform some or all of the steps of the method of the first communication device to obtain a network topology in the embodiment of fig. 4-14, and/or other processes for the techniques described herein.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may consist of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a terminal. Of course, the processor and the storage medium may reside as discrete components in a communication device.

It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, which are essential or part of the technical solutions contributing to the prior art, or all or part of the technical solutions, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Claims

1. A method of obtaining a network topology, comprising:

a first node acquires information of a second node for acquiring network topology;

and the first node sends a first message to the second node according to the information of the second node, wherein the first message comprises the identifier of the first node, the identifier of a third node serving as a neighbor node of the first node, and the identifier of a first port for the communication between the first node and the third node.

2. The method of claim 1, wherein the information of the second node comprises an identifier of the second node and indication information, the indication information is used for identifying the second node for obtaining a network topology, and the sending, by the first node, the first message to the second node according to the information of the second node comprises:

the first node acquires a second port for receiving the information of the second node;

the first node sends the first message to the second node through the second port.

3. The method of claim 1, wherein the information of the second node comprises: the identification of the second node, indication information and the identification of a third port through which the first node communicates with the second node, where the indication information is used to identify the second node for acquiring a network topology, and the sending, by the first node, a first message to the second node according to the information of the second node includes:

and the first node sends the first message to the second node through a port corresponding to the identifier of the third port based on the information of the second node.

4. The method according to any of claims 1 to 3, wherein the first node obtaining information for obtaining a second node of a network topology comprises:

the first node acquires the information of the second node which is statically configured; or

The first node receives a second message from the second node, the second message including information of the second node.

5. The method according to any one of claims 1 to 4, further comprising:

the first node receives a third message from the second node, the third message confirming receipt of the first message.

6. The method according to any one of claims 1 to 5, further comprising:

the first node sends a fourth message to the third node, wherein the fourth message comprises the information of the second node;

the first node receives a fifth message sent by the third node, wherein the fifth message comprises an identifier of the third node, an identifier of a fourth node serving as a neighbor node of the third node, and a port identifier of communication between the third node and the fourth node;

the first node sends the fifth message to the second node.

7. The method of claim 6, wherein the fifth message further includes indication information, the indication information is used to identify that the packet belongs to an uplink packet, and the sending, by the first node, the fifth message to the second node includes:

the first node acquires a port communicated with the second node according to the indication information included in the fifth message;

the first node sends the fifth message from the port in communication with the second node.

8. The method according to any one of claims 1 to 7, further comprising:

and after the communication between the first node and the second node fails, the first node sends a sixth message to the third node, wherein the sixth message is used for notifying that the communication with the second node fails.

9. The method according to any one of claims 1 to 8, further comprising:

and the first node communicates with the second node through a fourth port after the communication between the first node and the second node has a fault.

10. A communication device, comprising:

the acquisition module is used for acquiring information of a second node for acquiring network topology;

a sending module, configured to send a first message to the second node according to the information of the second node, where the first message includes an identifier of the first node, an identifier of a third node serving as a neighbor node of the first node, and an identifier of a first port through which the first node communicates with the third node.

11. The communications device according to claim 10, wherein the information of the second node includes an identifier of the second node and indication information, the indication information is used to identify the second node for acquiring a network topology, and the acquiring module is specifically used to acquire a second port for receiving the information of the second node;

the sending module is specifically configured to send the first message to the second node through the second port.

12. The communications device of claim 10, wherein the information of the second node comprises: the sending module is specifically configured to send the first message to the second node through a port corresponding to the identifier of the third port based on the information of the second node.

13. The communications device according to any one of claims 10 to 12, wherein the obtaining module is specifically configured to obtain information of the second node in a static configuration; or,

the communication device further comprises a receiving module, configured to receive a second message from the second node, where the second message includes information of the second node.

14. The communications device of any one of claims 10 to 13, further comprising a receiving module configured to receive a third message from the second node, the third message being configured to acknowledge receipt of the first message.

15. The communications device according to any one of claims 10 to 14, wherein the sending module is further configured to send a fourth message to the third node, the fourth message including information of the second node;

the communication device further includes a receiving module, configured to receive a fifth message sent by the third node, where the fifth message includes an identifier of the third node, an identifier of a fourth node serving as a neighbor node of the third node, and a port identifier of a communication between the third node and the fourth node;

the sending module is further configured to send the fifth message to the second node.

16. The communications device according to claim 15, wherein the fifth message further includes indication information, where the indication information is used to identify that the packet belongs to an uplink packet, and the obtaining module is specifically configured to obtain, according to the indication information included in the fifth message, a port for communicating with the second node;

the sending module is specifically configured to send the fifth message from the port communicating with the second node.

17. The communications device according to any one of claims 10 to 16, wherein the sending module is further configured to send a sixth message to the third node after the communication between the first node and the second node has failed, where the sixth message is used to notify that the communication with the second node has failed.

18. The communication device according to any of claims 10 to 17, wherein the sending module is further configured to communicate with the second node through a fourth port after a failure occurs in the communication between the first node and the second node.