Loop detection method, apparatus and system

Abstract

Provided are a loop detection method, apparatus and system, which relate to the technical field of communications. The method is applied to an EasyMesh network, and comprises: a network device sending loop detection information by means of a first port, wherein the loop detection information comprises a loop detection identifier, and at least one of a source device identifier, which is used for indicating an initiating device of the loop detection information, and a source port identifier; and when a message, which is received by the network device by means of a second port, comprises the loop detection information, determining that the present device forms a loop in the EasyMesh network. In this way, compared with an STP-based loop detection method, which involves steps such as changing a specified port on the basis of a topology structure of a network and performing reconvergence after a topology change, the present loop detection method has simpler steps for sending, receiving and detecting loop detection information, thereby improving the loop detection efficiency.

Description

Loop detection methods, devices and systems

[0001] This application claims priority to Chinese Patent Application No. 202411057551.1, filed with the State Intellectual Property Office of China on August 1, 2024, entitled “Loop Detection Method, Apparatus and System”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a loop detection method, apparatus and system. Background Technology

[0003] Due to user demand for wireless network coverage in scenarios such as homes, industries, and shopping malls, the application of wireless mesh networks is increasing. EasyMesh is a basic standard for interconnecting different access points (APs), defining the protocol for controlling the interconnection of APs from different manufacturers. EasyMesh networks can be interconnected via wireless networks or wired networks, resulting in relatively complex networking schemes. User errors or switching of AP uplink modes can lead to loops within the EasyMesh network.

[0004] If a loop detection method based on the spanning tree protocol (STP) is used, it takes a long time to detect and converge when the network topology changes, resulting in low loop detection efficiency. Summary of the Invention

[0005] This application provides a loop detection method, apparatus, and system to solve the problem of low loop detection efficiency.

[0006] Firstly, a loop detection method is provided, applied to network devices in an EasyMesh network. The loop detection method includes: the network device sending loop detection information through a first port, which may be a wired port or a wireless port. When the network device receives a message through a second port that includes the loop detection information, it is determined that the network device has formed a loop in the EasyMesh network. There may be one or more second ports. The loop detection information includes at least one of a loop detection identifier, a source device identifier, or a source port identifier, wherein the source device identifier indicates the device initiating the loop detection information, and the source port identifier indicates the port initiating the loop detection information.

[0007] Based on the above loop detection method, network devices in an EasyMesh network send loop detection information through a first port and receive it through a second port. By determining whether they have received their own loop detection information, they can determine whether a loop has formed in the EasyMesh network. This method can extract the loop detection identifier, source device identifier, or source port identifier carried in the loop detection information without increasing the packet type or corresponding detection methods, thus achieving loop detection in the EasyMesh network. Compared to loop detection methods based on the Spanning Tree Protocol, which require changing specified ports according to the network topology and re-converging after each topology change, the loop detection method provided in this application has simpler steps for sending and receiving loop detection information and for detection, improving loop detection efficiency.

[0008] As one possible implementation, loop detection information includes a source device identifier or a source port identifier. When the source device identifier indicates a network device or the source port identifier indicates a port of a network device, it is determined that the network device has formed a loop in the EasyMesh network.

[0009] As one possible implementation, the loop detection information only includes a loop detection identifier. In this case, only one network device in the network initiates loop detection. When the network device that initiated the loop detection receives a packet containing the loop detection identifier, it is determined that this network device has formed a loop in the EasyMesh network.

[0010] One possible implementation is to include loop detection information in the 1905.1 topology discovery message of the EasyMesh protocol. Thus, by simply carrying loop detection information in the message fields specified by the EasyMesh protocol, network devices can extract the loop detection identifier, source port identifier, or source device identifier carried in the loop detection information without increasing the message type or corresponding detection methods, thereby achieving loop detection in the EasyMesh network.

[0011] Optionally, the 1905.1 topology discovery message includes a type-length-value (TLV) structure. The TLV structure includes a type field, a length field, and a value field. The type field includes a loop detection identifier, and the value field includes a source device identifier and / or a source port identifier.

[0012] As one possible implementation, the 1905.1 topology discovery message includes a forwarding indicator field. The value of the forwarding indicator field indicates whether the packet is forwarded by the network device. When the forwarding indicator field indicates that the 1905.1 topology discovery message is being forwarded by the network device, the network device sends the 1905.1 topology discovery message through at least one port.

[0013] Optionally, the forwarding indicator field of the 1905.1 topology discovery message is configured by the device that initiates the 1905.1 topology discovery message to indicate a value that the message is forwarded by the network device.

[0014] One possible implementation is that the network device acts as a proxy node in the EasyMesh network. The network device sends 1905.1 topology discovery messages to the control node through at least one port connected to it within the EasyMesh network. In this way, the network device determines whether the 1905.1 topology discovery message needs to be forwarded based on the forwarding indicator field, forwarding only the messages that need to be forwarded, thus avoiding forwarding messages that terminate on its own device and reducing bandwidth utilization.

[0015] As one possible implementation, network devices periodically send loop detection information through at least one port. Alternatively, network devices may send loop detection information through at least one port when the EasyMesh network topology changes. Thus, the transmission of loop detection information can be periodic or triggered by specific network conditions of the EasyMesh network, adapting to different network environments and improving the applicability of the loop detection method.

[0016] As one possible implementation, network devices discard loop detection information if the source device identifier or source port identifier indicates a port on a network device other than themselves. Thus, if the EasyMesh network has only two network levels, each network device only performs subsequent loop detection steps on its own initiated loop detection information, reducing the bandwidth consumption of loop detection information in the network and its resource consumption on network devices. Each additional hop in the EasyMesh network can be considered as adding one level to the EasyMesh network.

[0017] As one possible implementation, when the source device identifier of the loop detection information points to a network device other than itself, or the source port identifier points to a port of a network device other than itself, the network device sends the loop detection information through at least one port. Thus, if there are three or more levels of the EasyMesh network, each network device, in addition to performing subsequent loop detection steps on its own initiated loop detection information, will also forward loop detection information initiated by other network devices, thereby achieving loop detection in multi-level networks.

[0018] As one possible implementation, when a network device detects a loop in the EasyMesh network, it issues an alarm message to facilitate troubleshooting by administrators.

[0019] As one possible implementation, when a network device determines that a loop has formed in an EasyMesh network, it closes either the initiating port or the receiving port based on the network quality corresponding to the initiating port of the loop detection information and the receiving port of the network device receiving the loop detection information. Optionally, if there are multiple receiving ports, the initiating port and the port with the best network quality among the multiple receiving ports are retained, while the remaining ports are closed. In this way, the network device can perform loop detection and removal for loops between wired and wireless ports. Since loop detection and removal are based on the data carried by the loop detection information, it does not require overall network topology detection, avoiding the slow convergence speed problem caused by topology changes and improving the efficiency of loop detection and removal.

[0020] Optionally, loop detection information is carried by a 1905.1 topology discovery message. The 1905.1 topology discovery message includes a TLV structure, which comprises a type field, a length field, and a value field. The value field includes a source port identifier, a source port type identifier, and a source port network quality identifier, the latter indicating the network quality of the initiating port.

[0021] Optionally, network quality includes one or more of port speed, port latency, port packet loss rate, and port signal-to-noise ratio. Thus, when a network device breaks a loop, it determines which port to close based on the network quality of different ports within the loop, ensuring network transmission quality after the loop is broken.

[0022] Secondly, a loop detection device is provided. This loop detection device includes a transceiver module and a processing module. The transceiver module is used to transmit loop detection information through at least one port; the loop detection information includes at least one of a loop detection identifier, a source device identifier, or a source port identifier, wherein the source device identifier indicates the device initiating the loop detection information, the source port identifier indicates the port initiating the loop detection information, and the at least one port includes a wired port and / or a wireless port. The processing module is used to filter loop detection information from received packets based on the loop detection identifier. The processing module is further used to determine that a loop has been formed in the EasyMesh network if the source device identifier of the loop detection information indicates the network device or the source port identifier indicates a port of the network device.

[0023] As one possible implementation, loop detection information is included in the 1905.1 topology discovery message of the EasyMesh protocol.

[0024] As one possible implementation, the 1905.1 topology discovery message includes a Type Length Value (TLV) structure. The TLV structure includes a type field, a length field, and a value field. The type field includes a loop detection identifier, and the value field includes a source device identifier or a source port identifier.

[0025] As one possible implementation, the 1905.1 topology discovery message includes a forwarding indicator field, the value of which is used to indicate that the 1905.1 topology discovery message is forwarded by network devices.

[0026] As one possible implementation, the network device is a proxy node in the EasyMesh network. Specifically, the transceiver module is used to send 1905.1 topology discovery messages to the control node via at least one port connected to the control node in the EasyMesh network.

[0027] As one possible implementation, the transceiver module is specifically used to periodically send loop detection information through at least one port.

[0028] As one possible implementation, the transceiver module is specifically used to send loop detection information through at least one port when the topology of the EasyMesh network changes.

[0029] As one possible implementation, the processing module is also configured to discard loop detection information if the source device identifier of the loop detection information indicates a network device other than the network device or the source port identifier indicates a port of a network device other than the network device.

[0030] As one possible implementation, the processing module is also used to: send loop detection information through at least one port when the source device identifier of the loop detection information indicates a network device other than the network device or the source port identifier indicates a port of a network device other than the network device.

[0031] As one possible implementation, the processing module is also used to: determine if a network device forms a loop in the EasyMesh network, instruct the transceiver module to issue an alarm message, and facilitate manual troubleshooting.

[0032] As one possible implementation, the processing module is also used to: determine if a loop has formed in the EasyMesh network, and based on the network quality corresponding to the initiating port of the loop detection information and the receiving port of the network device receiving the loop detection information, close the initiating port or the receiving port. Optionally, if there are multiple receiving ports, only the initiating port and the port with the best network quality among the multiple receiving ports are retained, and the remaining ports are closed.

[0033] As one possible implementation, loop detection information is carried by a 1905.1 topology discovery message. The 1905.1 topology discovery message includes a TLV structure, which includes a type field, a length field, and a value field. The value field includes the source port identifier, the source port type identifier, and the source port network quality identifier. The source port network quality identifier is used to indicate the network quality of the initiating port.

[0034] As one possible implementation, network quality includes one or more of port rate, port latency, port packet loss rate, and port signal-to-noise ratio.

[0035] As one possible implementation, the loop detection device described above may also include other modules that perform the operational steps of the loop detection method described in the first aspect.

[0036] Regarding the technical principles and beneficial effects of the second aspect, please refer to the relevant description of the first aspect mentioned above, which will not be repeated here.

[0037] Thirdly, a network device is provided, including a memory and a processor, wherein the memory stores at least one instruction, which is loaded and executed by the processor to implement the loop detection method described in any possible implementation of the first aspect above.

[0038] Fourthly, a loop detection system is provided, the system being based on an EasyMesh network, the system comprising a control node and at least one proxy node, the control node being connected to the at least one proxy node, and any one of the at least one proxy node being used to execute the loop detection method described in any possible implementation of the first aspect above.

[0039] Fifthly, a computer program (product) is provided, the computer program (product) comprising: computer program code, which, when executed by a computer, causes the computer to perform the loop detection method described in any possible implementation of the first aspect above.

[0040] In a sixth aspect, a chip is provided, including a processor for retrieving and executing instructions stored in a memory, such that a communication device on which the chip is mounted performs the loop detection method described in any possible implementation of the first aspect above.

[0041] In a seventh aspect, another chip is provided, comprising: an input interface, an output interface, a processor, and a memory, wherein the input interface, the output interface, the processor, and the memory are connected via an internal connection path, and the processor is used to execute code in the memory, wherein when the code is executed, the processor is used to execute the loop detection method described in any possible implementation of the first aspect above.

[0042] Eighthly, a computer-readable storage medium is provided, the storage medium storing at least one instruction, the instruction being loaded and executed by a processor to implement the loop detection method described in any possible implementation of the first aspect above. Attached Figure Description

[0043] Figure 1 is a schematic diagram of a network architecture provided in this application;

[0044] Figure 2 is a schematic flowchart of a loop detection method provided in this application;

[0045] Figure 3 is a flowchart illustrating another loop detection method provided in this application;

[0046] Figure 4 is a schematic diagram of another network architecture provided in this application;

[0047] Figure 5 is a structural schematic diagram of a loop detection device provided in this application;

[0048] Figure 6 is a schematic diagram of the structure of a network device provided in this application. Detailed Implementation

[0049] The terminology used in the implementation section of this application is only for explaining specific embodiments of this application and is not intended to limit this application. For example, the loop detection method provided in the embodiments of this application can be applied to scenarios using EasyMesh networks in the field of communication. The following is a brief introduction to the technologies that may be involved in this application.

[0050] (1) EasyMesh

[0051] EasyMesh is a standardized technology for home networks designed to extend and unify the management of the entire home network by connecting multiple wireless access points (APs). Compared to traditional wireless network extenders, EasyMesh offers greater flexibility and scalability.

[0052] An EasyMesh network typically consists of multiple network devices connected via wired or wireless means, such as routers and gateways. These network devices include one controller and at least one agent.

[0053] The control node is the control logic entity in a multi-AP network. In a multi-AP network, the control node receives and processes information such as network metrics and device capabilities of the fronthaul APs, clients, and backhaul links through the proxy node. The control node also sends control commands to the proxy node. The control node provides the devices in the multi-AP network with the function of accessing its network.

[0054] A proxy node is a logical entity that executes commands from the control node. It reports information such as network metrics and device capabilities of the fronthaul AP, clients, and backhaul links to the control node. In an EasyMesh network, all APs play the role of a proxy node.

[0055] (2) 1905.1

[0056] The Institute of Electrical and Electronics Engineers (IEEE) 1905.1 defines an abstraction layer (AL) shared by various home networking technologies, providing a common data control service access point for interoperability between heterogeneous home networking technologies of IEEE 1901, IEEE 802.11, IEEE 802.3 and MoCA 1.1 standards and 1905.1 networks.

[0057] The 1905.1 protocol specifies that interaction is conducted through the 1905.1 Control Message Data Unit (CMDU). When a 1905.1 CMDU exceeds the maximum frame length, it needs to be fragmented. The receiver reassembles all CMDU fragments after receiving them and then transmits them to the upper-layer application. The 1905.1 CMDU currently supports the following message types: topology discovery message, topology notification message, topology query message, topology response message, vendor specific message, and link metric query message.

[0058] (3) TLV

[0059] The EasyMesh protocol's 1905.1 topology discovery message (or topology discovery packet) defines a type-length-value (TLV). TLV is a commonly used data serialization format, primarily used for encoding the payload of data packets or messages.

[0060] Type is used to identify the type or meaning of a field, essentially labeling the data field. It can be a number, a character, or other predefined identifier to indicate the specific meaning of the data that follows. In some specifications, Type can be a single byte or multiple bytes, depending on the number and range of identifiers required.

[0061] The Length field represents the length of the Value field. It can be one byte, two bytes, or more, depending on the maximum possible length of the Value. The Length field typically uses variable-length encoding, which saves space by using fewer bits to represent the length of a shorter Value.

[0062] Value is the actual data content, and its type and length are determined by the preceding Type. It can be an integer, a string, a block of binary data, etc. Because the TLV format allows for variable value lengths, it can flexibly handle data of different types and lengths.

[0063] (4) Ring Road

[0064] A network loop, also known as a network connection loop, is a concept in computer networks that refers to the phenomenon where data packets are transmitted in a loop within the network and fail to reach their destination. This situation typically leads to degraded network performance and may even cause network paralysis. Network loops can be divided into two types: physical loops and logical loops. Physical loops are usually caused by misconfigurations of network devices or connecting lines. For example, if two switches are connected through multiple paths, a physical loop may be formed. Logical loops are caused by incorrect routing table configurations or routing protocol failures. When a router's routing table contains incorrect paths pointing to unreachable networks, data packets will be transmitted in a loop between routers and fail to reach their final destination.

[0065] Currently, loop detection in networks typically employs a loop detection method based on the Spanning Tree Protocol (STP). However, in complex network scenarios such as EasyMesh networks, which simultaneously include wired ports, wireless ports, and a large number of network devices, the STP-based loop detection method suffers from long convergence times due to topology changes, resulting in low efficiency in loop detection and resolution.

[0066] This application provides a loop detection method, particularly a loop detection method based on loop detection information in an EasyMesh network. The method is applied to network devices in an EasyMesh network, whereby the network device sends loop detection information through a first port. The loop detection information includes at least one of a loop detection identifier, a source device identifier, or a source port identifier. The source device identifier indicates the device that initiated the loop detection, and the source port identifier indicates the port that initiated the loop detection information. The first port includes a wired port and / or a wireless port. The network device filters out the loop detection information from packets received at a second port, which can be one or more. When the source device identifier of the loop detection information indicates a network device or the source port identifier indicates a port of the network device, the network device determines that a loop has formed in the EasyMesh network.

[0067] Based on the above loop detection method, network devices in an EasyMesh network send loop detection information through a first port. Whether or not they receive their own loop detection information determines whether a loop has formed within the EasyMesh network. This method enables loop detection in EasyMesh networks without increasing message types or corresponding detection methods. Therefore, compared to loop detection methods based on the Spanning Tree Protocol, which require changing specified ports according to the network topology and re-converging after each topology change, the loop detection method provided in this application has simpler steps for sending and receiving loop detection information and for the detection process itself, thus improving loop detection efficiency.

[0068] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0069] Figure 1 is a schematic diagram of a network architecture provided in this application. The network structure 100 may include multiple network devices and terminal devices based on an EasyMesh network, and may also be referred to as a loop detection system. The network architecture 100 includes network device 101, network device 102, network device 103, terminal device 104, and terminal device 105.

[0070] Network devices can be switches, routers, gateways, optical line terminals (OLTs), access points (APs), or other types of devices, used to forward or process packets from terminal devices. This application does not limit the deployment location of the network devices.

[0071] As one possible implementation, network devices 101, 102, and 103 are all gateways. Network device 101 is the control node in the EasyMesh network, acting as the primary gateway. Network devices 102 and 103 are proxy nodes in the EasyMesh network, acting as secondary gateways. Optionally, in a fiber-to-the-room (FTTR) scenario, network device 101 can also be an FTTR master device, and network devices 102 and 103 can also be FTTR slave devices.

[0072] Network device 101, network device 102, and network device 103 each include at least one port, and the at least one port includes a wired port or a wireless port.

[0073] Network device 101 is connected to network device 102 through one port and also through another port. Network device 101 is connected to network device 103 through one port. For example, network device 101 may be wired to network device 102 and network device 103 through two local area network (LAN) ports (LAN1 and LAN2 ports as shown in Figure 1), and wirelessly connected to network device 102 through a WLAN port. Alternatively, network device 101 may be wired to network device 102 and network device 103 through two LAN ports, and also connected to network device 102 through another LAN port other than the two LAN ports.

[0074] Network device 102 is wired to the LAN port of network device 101 via a LAN port (LAN1 port as shown in Figure 1), and network device 103 is wired to the LAN port of network device 101 via a LAN port (LAN1 port as shown in Figure 1). Network device 102 is also wirelessly connected to the WLAN port of network device 101 via a WLAN port. The WLAN port can be used to connect to the WLAN ports of other network devices via Wi-Fi.

[0075] Network device 102 is connected to terminal device 104, and network device 103 is connected to terminal device 105. For example, network device 102 is connected to terminal device 104 via a WLAN port, and network device 103 is connected to terminal device 105 via a WLAN port. Here, the WLAN port can be regarded as an air interface.

[0076] Terminal devices can also be referred to as terminals, terminal nodes, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. Terminal devices can be access points (APs), mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals such as programmable logic controllers (PLCs) in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and so on. The embodiments of this application do not limit the specific technology or device form used in the terminal devices. Terminal device 101 is used to communicate with other devices through network devices.

[0077] It should be understood that Figure 1 is a simplified schematic diagram for ease of understanding only. The network architecture 100 may also include other network devices and / or other terminal devices, and the connection relationships between nodes may also vary, which are not shown in Figure 1.

[0078] Next, the loop detection method provided in the embodiments of this application will be described in detail with reference to the accompanying drawings. Here, the loop detection method is implemented by network device 102 in the network architecture 100 in Figure 1 as an example to illustrate the specific steps of the loop detection method.

[0079] Figure 2 is a schematic flowchart of a loop detection method provided in this application. Referring to Figure 2, the loop detection method may include the following steps 210-250.

[0080] Step 210: Network device 102 sends loop detection information through the first port.

[0081] Network device 102 sends loop detection information through its first port. The loop detection information can be sent via broadcast, multicast, or other methods. The first port initiating the loop detection can be any port on network device 102. For example, network device 102 includes a WLAN port, a LAN1 port, a LAN2 port, and a LAN3 port; network device 102 sends loop detection information through the WLAN port.

[0082] As one possible implementation, when network device 102 is a proxy node without broadcast functionality, the first port can be the port through which network device 102 connects to a control node such as network device 101. That is, network device 102 sends loop detection information to network device 101 through the port connected to network device 101. For example, network device 102 sends loop detection information through a WLAN port and / or a LAN1 port.

[0083] Loop detection information includes at least one of a loop detection identifier, a source device identifier, or a source port identifier. The loop detection identifier indicates that the information is a loop detection message. The source device identifier indicates the device that initiated the loop detection message, i.e., the device that generates and sends the loop detection message, such as network device 102. The source port identifier indicates the port from which the loop detection message originated.

[0084] As one possible implementation, the loop detection information only includes the loop detection identifier. In this case, there is only one network device in the network architecture 100, namely network device 102, which serves as the initiating device for loop detection.

[0085] As one possible implementation, loop detection information includes source device identifier or source port identifier. In this case, multiple devices in network architecture 100 can act as loop detection initiators. For example, network device 101, network device 102, and network device 103 can all initiate loop detection.

[0086] Optionally, loop detection information can be carried by the 1905.1 topology discovery message in the EasyMesh protocol. The 1905.1 topology discovery message is a standard defined by IEEE, and the Wi-Fi Alliance used the IEEE 1905.1 topology discovery message as part of the EasyMesh protocol. For details on the loop detection information, please refer to Tables 1-3 and related descriptions; they will not be repeated here.

[0087] Among these, loop detection information, such as the 1905.1 topology discovery message, requires the highest quality of service (QoS) guarantee. For example, WLAN ports need to ensure that 1905.1 topology discovery messages are sent with the highest priority. Network device 102 can control the sending priority of 1905.1 topology discovery messages based on the priority field carried by the 1905.1 topology discovery message itself, or it can control the sending priority of 1905.1 topology discovery messages based on the priority configured on the port.

[0088] Step 220: Network device 101 receives loop detection information sent by network device 102.

[0089] Network device 101 receives loop detection information sent by network device 102 through a port connected to network device 102.

[0090] As one possible implementation, network device 101 may have one or more ports connected to network device 102. For example, the LAN1 port of network device 101 may be connected to the LAN1 port of network device 102, and the WLAN port of network device 101 may be connected to the WLAN port of network device 102. Network device 101 may receive loop detection information through its own LAN1 port and also through its own WLAN port.

[0091] Step 230: Network device 101 sends loop detection information through at least one port.

[0092] Network device 101 sends loop detection information through at least one port. The loop detection information can be sent via broadcast, multicast, or other methods.

[0093] As one possible implementation, at least one port is all ports of network device 101 except for the port receiving loop detection information. For example, if network device 101 includes a WLAN port, a LAN1 port, a LAN2 port, and a LAN3 port, then network device 101 will transmit the loop detection information received by the WLAN port through the LAN1 port, LAN2 port, and LAN3 port respectively. Similarly, network device 101 will transmit the loop detection information received by the LAN1 port through the WLAN port, LAN2 port, and LAN3 port respectively.

[0094] Step 240: Network device 102 receives loop detection information sent by network device 101 through the second port.

[0095] Network device 102 receives loop detection information sent by network device 101 through a second port connected to network device 101.

[0096] As one possible implementation, network device 102 may have one or more ports connected to network device 101. For example, the LAN1 port of network device 102 may be connected to the LAN1 port of network device 101, and the WLAN port of network device 101 may be connected to the WLAN port of network device 102.

[0097] Optionally, the loop detection information initiated by network device 102 is received through a second port other than the port used to initiate the loop detection information. For example, loop detection information sent by network device 102 to network device 101 through LAN1 port is forwarded back to the WLAN port of network device 102 by network device 101 through WLAN port. Similarly, loop detection information sent by network device 102 to network device 101 through WLAN port is forwarded back to the LAN1 port of network device 102 by network device 101 through LAN1 port.

[0098] As one possible implementation, when only network device 102 initiates loop detection in network architecture 100, network device 102 can filter out the loop detection information initiated by network device 102 from the received packets based on the loop detection identifier. Specifically, network device 102 filters out one or more loop detection information from the received packets, and the one or more loop detection information includes the loop detection information initiated by network device 102.

[0099] As one possible implementation, when multiple devices in network architecture 100 initiate loop detection, network device 102 filters out loop detection information initiated by network device 102 from the received packets based on the source device identifier or source port identifier. Specifically, network device 102 filters out one or more loop detection information from the received packets, and the one or more loop detection information includes loop detection information initiated by network device 102.

[0100] Step 250: Determine that network device 102 has formed a loop in the EasyMesh network, issue an alarm, or close the network quality port corresponding to the initiating port of the loop detection information and the receiving port of the loop detection information.

[0101] As one possible implementation, when only network device 102 initiates loop detection in network architecture 100, network device 102 can determine that network device 102 has formed a loop in EasyMesh network upon receiving loop detection information.

[0102] As one possible implementation, when multiple devices in the network architecture 100 initiate loop detection, if the source device identifier of the loop detection information indicates that the network device 102 has formed a loop in the EasyMesh network or the source port identifier indicates that the port of the network device 102 has formed a loop.

[0103] As one possible implementation, the source port identifier is used to indicate the port from which the loop detection information was initiated. When the port indicated by the source port identifier is a port of network device 102 itself, it indicates that network device 102 has formed a loop in the EasyMesh network.

[0104] As one possible implementation, the source device identifier is used to indicate the device that initiated the loop detection information. When the device indicated by the source device identifier is network device 102, it means that network device 102 has formed a loop in the EasyMesh network.

[0105] Optionally, the source device identifier or source port identifier will not change during the transmission of loop detection information among devices in network architecture 100.

[0106] In a possible embodiment of this application, network device 102 may take measures such as issuing an alarm or shutting down a port upon detecting a loop forming in the EasyMesh network:

[0107] As one possible implementation, network device 102 issues alarm information to facilitate troubleshooting by administrators;

[0108] As one possible implementation, network device 102 shuts down the port with poorer network quality among the first port and the second port that initiates the loop detection information and receives the loop detection information, based on the network quality of the first port that initiates the loop detection information and the second port that receives the loop detection information. Optionally, if there are multiple second ports, only the first port and the port with the best network quality among the multiple second ports are retained, and the remaining ports are shut down.

[0109] As one possible implementation, the network quality of the initiating port can be carried by loop detection information, i.e., the 1905.1 topology discovery message includes the network quality of the initiating port.

[0110] Optionally, network quality includes one or more of port rate, port latency, port packet loss rate, and port signal-to-noise ratio.

[0111] For example, for an Ethernet port, network quality can be one or more of the following: port negotiation rate, port duplex mode, port packet loss rate, and cable quality (Category 4 / Category 5 / Category 6 cable).

[0112] For example, for a WLAN port, network quality can be one or more of the following: air interface negotiation rate, air interface negotiated received signal strength indicator (RSSI), air interface latency, air interface packet loss rate, air interface duty cycle, and number of interfering access points. Here, air interface rate can be considered as port rate, air interface latency as port latency, air interface packet loss rate as port packet loss rate, and air interface interference as port signal-to-noise ratio.

[0113] The network quality of the aforementioned initiating port can be obtained by the initiating device of the loop detection information, i.e., network device 102, detecting the initiating port of the loop detection information. Network device 102 encapsulates the network quality into the loop detection information.

[0114] The network quality of the aforementioned receiving port can be obtained by the loop detection information initiating device, i.e., network device 102, through detection of the receiving port of the loop detection information.

[0115] Based on the above steps, network devices in the EasyMesh network can compare the network quality of the initiating port with the network quality of the receiving port according to the loop detection information, and thus select to close the port with poor network quality. This eliminates loops in the EasyMesh network while ensuring the network quality of data transmission in the EasyMesh network.

[0116] The loop detection method has been described above using the example of network device 102 initiating loop detection information. In possible embodiments of this application, the loop detection information may also be initiated by network device 101, i.e., the control node in the EasyMesh network. In this case, network device 101 executes the steps of network device 102 in steps 210-250 above, and network device 102 executes the steps of network device 101 in steps 210-250 above. These steps will not be repeated here.

[0117] The loop detection method provided in this application has been described in general with reference to Figure 2 above. The loop detection information will be described in detail below with reference to Tables 1-3.

[0118] Loop detection information can be carried by the 1905.1 topology discovery message in the EasyMesh protocol. The Ethernet frame structure of the 1905.1 message is shown in Table 1. Optionally, encapsulating the Ethernet frame of the 1905.1 message with the header of the IEEE 802.11 protocol can enable wireless air interface transmission.

[0119] Table 1

[0120] The payload in the frame structure of the 1905.1 message can carry the 1905.1 topology discovery message. The frame structure of the 1905.1 topology discovery message is shown in Table 2.

[0121] Table 2

[0122] The forwarding indicator is used to indicate whether a message is forwarded or terminated on this device.

[0123] As one possible implementation, 1905.1 protocol TLVs are used to carry loop detection information. The frame structure of 1905.1 protocol TLVs is shown in Table 3.

[0124] Table 3

[0125] In this context, GPON refers to gigabit-capable passive optical network. EPON refers to Ethernet passive optical network. XGSPON refers to 10-gigabit symmetric passive optical network. XGPON refers to 10-gigabit-capable passive optical network. The air interface rate corresponding to 802.11a / b / g / n refers to the transmission rate corresponding to the air interface operating frequency band specified by each protocol. Specifically, the channel corresponding to the air interface operating frequency band specified by each protocol negotiates different modes under different distances and environments, and different modes correspond to different transmission rates.

[0126] As shown in Table 3, the type field in the TLV structure includes a loop detection identifier, that is, the value of the type field is used to represent the loop detection identifier.

[0127] The value fields in the TLV structure include the source device identifier and / or source port identifier, which indicate the device that initiated the loop detection information. The initiating device is the device that first sends the loop detection information, i.e., the device indicated by the source address of the loop detection information. The device that receives and forwards the loop detection information is not the initiating device.

[0128] Alternatively, the source device identifier can be the media access control (MAC) address, product serial number (SN), or other variables that can identify the device of the device initiating the loop detection information.

[0129] Alternatively, the source device representation can also be data outside the TLV structure. For example, the source address field in the header of a 1905.1 topology discovery message serves as the source device identifier.

[0130] Optionally, the source port identifier can be the port number used by the device that initiated the loop detection information to send the loop detection information.

[0131] Optionally, the source port rate can be an indicator of the network quality of the initiating port in step 270 above. In possible embodiments of this application, the value field may also carry one or more other network quality indicators besides the source port rate, such as port latency, port packet loss rate, port signal-to-noise ratio, etc.

[0132] Based on the aforementioned method of using 1905.1 topology discovery messages to carry loop detection information, devices in the EasyMesh network do not need to specifically support new protocols for loop detection. Devices from different manufacturers can all implement loop detection and resolution in the EasyMesh network based on the 1905.1 messages in the EasyMesh protocol. This ensures the simplicity of the loop detection method while improving its applicability.

[0133] The above text provides a detailed explanation of the specific format of loop detection information. Next, with reference to Figures 3 and 4, we will provide an exemplary explanation of how to perform loop detection and removal based on the loop detection information carried by the 1905.1 topology discovery message.

[0134] Please refer to Figure 3, which is a flowchart illustrating another loop detection method provided in this application. Taking the control node (e.g., network device 101) and agent node (e.g., network device 102, network device 103) in network architecture 100 as examples, the loop detection method based on 1905.1 topology discovery messages may include the following steps 410-470.

[0135] Step 410: Election of control node and proxy node among all nodes.

[0136] The election of control nodes and agent nodes is supported by the EasyMesh protocol, and will not be elaborated on here.

[0137] Step 420: The proxy node sends a 1905.1 topology discovery message to all ports.

[0138] Each agent node in the EasyMesh network periodically sends 1905.1 topology discovery messages through all its ports.

[0139] As one possible implementation, the period for the proxy node to send 1905.1 topology discovery messages can be any duration, such as 5 seconds, 20 seconds, 2 minutes, or 10 minutes.

[0140] Optionally, the 1905.1 topology discovery message includes loop detection information, the details of which can be found in Tables 1-3, and will not be repeated here.

[0141] Step 430: When the 1905.1 topology discovery message indication message received by the control node is forwarded on this device, the 1905.1 topology discovery message is forwarded.

[0142] As one possible implementation, if the control node forwards the 1905.1 topology discovery message indication message within its own device, it may broadcast the loop detection information within the 1905.1 group. Here, "own device" refers to the control node that receives the 1905.1 topology discovery message.

[0143] Optionally, when the relay Indicator field value of the 1905.1 topology discovery message is 1, it indicates that the 1905.1 topology discovery message is forwarded on this device. When the relay Indicator field value of the 1905.1 topology discovery message is 0, it indicates that the 1905.1 topology discovery message is terminated on this device and does not need to be forwarded.

[0144] The relay Indicator field, also known as the forwarding indicator field, is configured by the device that initiates the 1905.1 topology discovery message. For example, if the broker node that generates the 1905.1 topology discovery message configures the relay Indicator field value to 1, subsequent nodes forwarding the 1905.1 topology discovery message will not modify the relay Indicator field value.

[0145] Step 440: The proxy node receives the 1905.1 topology discovery message.

[0146] The proxy node receives the 1905.1 topology discovery message sent by the control node.

[0147] Step 450: When the topology discovery message in 1905.1 is initiated by the proxy node, extract the TLV structure.

[0148] As one possible implementation, if the proxy node has a loop detection identifier in the TLV structure of the 1905.1 topology discovery message, or the source device identifier is the identifier of the proxy node's own device, or the source port identifier is the port of the proxy node's own machine, then the proxy node determines that the 1905.1 topology discovery message was initiated by the proxy node itself, and then the proxy node extracts other information from the TLV structure.

[0149] The 1905.1 topology discovery message contains a TLV structure, the details of which can be found in Tables 1-3.

[0150] Step 460: The proxy node determines whether there is a loop between the ports of its device based on the source device identifier or source port identifier in the TLV structure.

[0151] As one possible implementation, when the source port of the 1905.1 topology discovery message is identified as a port of this device, the proxy node determines that there is a loop between the initiating port and the receiving port of the 1905.1 topology discovery message.

[0152] Step 470: The proxy node discovers the network quality of the initiating and receiving ports of the message based on the 1905.1 topology, keeps one port, and closes the rest.

[0153] In a possible implementation of this application, the proxy node discards the 1905.1 topology discovery message after closing the port to remove the loop.

[0154] Furthermore, since the network devices in the Easymesh network in Figure 1 only have two levels (e.g., network device 101 is a first-level network device, and network devices 102 and 103 are second-level network devices), the proxy node discards the 1905.1 topology discovery message when it is not initiated by the local machine.

[0155] In other possible embodiments, as shown in Figure 4, the network devices in the EasyMesh network may be in more than two levels. That is, the WLAN port of network device 102 is connected to the WLAN port of the next-level network device, and the LAN1 port of network device 102 is connected to the LAN1 port of the next-level network device, forming a loop between these four ports. In order for each network device in the EasyMesh network to forward 1905.1 topology discovery messages sent by other network devices besides itself, thereby detecting the loop formed by multiple levels of network devices, when the 1905.1 topology discovery message is not initiated by the proxy node itself, the proxy node sends the 1905.1 topology discovery message through at least one port of the proxy node itself (or all ports of the proxy node).

[0156] Optionally, to prevent broadcast storms caused by control nodes and agent nodes when forwarding 1905.1 topology discovery messages, the 1905.1 topology discovery message may also include a forwarding count identifier field. The device initiating the 1905.1 topology discovery message initializes the initial value of the forwarding count identifier field. The initial value of the forwarding count identifier field corresponds to the number of network device levels in the EasyMesh network. For example, if the control nodes and agent nodes in the EasyMesh network are connected in a tree topology with a depth of 3 (i.e., the number of network device levels is 3), the initial value of the forwarding count identifier field is 3. In other words, when a network device forwards the same 1905.1 topology discovery message 3 times, it discards the message and stops forwarding it.

[0157] In possible embodiments of this application, in addition to the proxy node performing loop detection based on the 1905.1 topology discovery message, the control node can also perform loop detection based on the 1905.1 topology discovery message. The execution subject of the loop detection method provided in this embodiment is not limited.

[0158] To complement the loop detection method provided in the embodiments of this application, this application also provides a loop detection device 500, which is used to perform the loop detection method described above. As shown in FIG5, the device includes:

[0159] The transceiver module 510 is used to send loop detection information through at least one port; the loop detection information includes a loop detection identifier, and also includes a source device identifier or a source port identifier, the source device identifier is used to indicate the initiating device of the loop detection information, the source port identifier is used to indicate the initiating port of the loop detection information, and at least one port includes a wired port and / or a wireless port.

[0160] The processing module 520 is used to filter out loop detection information from received messages based on the loop detection identifier, the source device identifier, or the source port identifier.

[0161] As one possible implementation, loop detection information is included in the 1905.1 topology discovery message of the EasyMesh protocol.

[0162] As one possible implementation, the 1905.1 topology discovery message includes a Type Length Value (TLV) structure. The TLV structure includes a type field, a length field, and a value field. The type field includes a loop detection identifier, and the value field includes a source device identifier.

[0163] As one possible implementation, the 1905.1 topology discovery message includes a forwarding indicator field, the value of which indicates whether the packet is forwarded by a network device. Specifically, the transceiver module 510 is used to send a 1905.1 topology discovery message through at least one port when the forwarding indicator field indicates that the 1905.1 topology discovery message is forwarded by a network device.

[0164] In one possible implementation, the network device acts as a proxy node in the EasyMesh network. The 1905.1 topology discovery message includes a forwarding indicator field, the value of which indicates whether the packet is forwarded by the network device. When the forwarding indicator field indicates that the 1905.1 topology discovery message has been forwarded by the network device, the network device sends the 1905.1 topology discovery message to the control node through at least one port connected to the control node in the EasyMesh network.

[0165] As one possible implementation, the transceiver module 510 is specifically used to periodically send loop detection information through at least one port.

[0166] As one possible implementation, the transceiver module 510 is specifically used to send loop detection information through at least one port when the topology of the EasyMesh network changes.

[0167] As one possible implementation, the processing module 520 is also configured to discard loop detection information when the source device identifier of the loop detection information indicates a network device other than the network device itself or the source port identifier indicates a port of a network device other than the network device itself.

[0168] As one possible implementation, the processing module 520 is also used to: send loop detection information through at least one port when the source device identifier of the loop detection information indicates a network device other than the network device itself or the source port identifier indicates a port of a network device other than the network device itself.

[0169] As one possible implementation, the processing module 520 is also used to: determine if a loop is formed in the EasyMesh network by a network device, instruct the transceiver module to issue an alarm message, so as to facilitate manual troubleshooting.

[0170] As one possible implementation, the processing module 520 is also used to: determine if a loop has formed in the EasyMesh network, and close the initiating port or the receiving port corresponding to the loop detection information initiating port and the receiving port of the network device receiving the loop detection information, based on the network quality. Optionally, if there are multiple receiving ports, only the initiating port and the port with the best network quality among the multiple receiving ports are retained, and the remaining ports are closed.

[0171] As one possible implementation, loop detection information is carried by a 1905.1 topology discovery message. The 1905.1 topology discovery message includes a TLV structure, which includes a type field, a length field, and a value field. The value field includes the source port identifier, the source port type identifier, and the source port network quality identifier. The source port network quality identifier is used to indicate the network quality of the initiating port.

[0172] As one possible implementation, network quality includes one or more of port rate, port latency, port packet loss rate, and port signal-to-noise ratio.

[0173] It should be understood that the device shown in Figure 5 above is only illustrated by the division of the above-described functional modules. In practical applications, the functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the device and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process is detailed in the method embodiments, which will not be repeated here.

[0174] Figure 6 is a schematic diagram of the structure of a network device provided in this embodiment. As shown in Figure 6, the network device 600 includes a processor 610, a bus 620, a memory 630, a communication interface 640, and a memory unit 650 (also referred to as a main memory unit). The processor 610, the memory 630, the memory unit 650, and the communication interface 640 are connected through the bus 620.

[0175] It should be understood that in this embodiment, the processor 610 may be a CPU, but it may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0176] The processor may also be a graphics processing unit (GPU), a neural network processing unit (NPU), a microprocessor, or one or more integrated circuits used to control the execution of the program in this application.

[0177] The communication interface 640 is used to enable communication between the network device 600 and external devices or components. In this embodiment, when the network device 600 is used to implement the function of any of the network devices in FIG1, the communication interface 640 is used as a physical port for sending and receiving data packets.

[0178] Bus 620 may include a pathway for transmitting information between the aforementioned components (such as processor 610, memory unit 650, and memory 630). In addition to a data bus, bus 620 may also include a power bus, control bus, and status signal bus. However, for clarity, all buses are labeled as bus 620 in the figure. Bus 620 may be a Peripheral Component Interconnect Express (PCIe) bus, or an Extended Industry Standard Architecture (EISA) bus, a Unified Bus (Ubus or UB), a Compute Express Link (CXL) bus, a Cache Coherent Interconnect for Accelerators (CCIX) bus, etc. Bus 620 can be divided into address bus, data bus, control bus, etc.

[0179] As an example, network device 600 may include multiple processors. A processor may be a multi-core (multi-CPU) processor. Here, a processor can refer to one or more devices, circuits, and / or computing units used to process data (e.g., computer program instructions).

[0180] It is worth noting that Figure 6 only shows an example of a network device 600 including one processor 610 and one memory 630. Here, the processor 610 and the memory 630 are used to indicate a type of device or equipment. In specific embodiments, the number of each type of device or equipment can be determined according to business requirements.

[0181] Memory cell 650 may be volatile memory or non-volatile memory, or may include both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0182] The memory 630 can correspond to the storage medium used to store computer instructions and other information in the above method embodiments, such as a disk, like a mechanical hard disk or a solid-state hard disk.

[0183] The network device 600 described above can be a general-purpose device or a special-purpose device. For example, network device 600 can be an edge device (e.g., a box carrying a chip with processing capabilities). Alternatively, network device 600 can also be a network device, a server, or other device with computing capabilities.

[0184] It should be understood that the network device 600 according to this embodiment can correspond to the loop detection device 500 in this embodiment, and can correspond to the corresponding subject executing the method according to FIG2. The above and other operations and / or functions of each module in the loop detection device 500 are respectively for implementing the corresponding process of the method in FIG2. For the sake of brevity, they will not be described in detail here.

[0185] The method steps in this embodiment can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in an electronic device (such as a network device). Of course, the processor and storage medium can also exist as discrete components in an electronic device.

[0186] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD). The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A loop detection method, characterized by, A method applied to a network device in an EasyMesh network, the method comprising: sending loop detection information through a first port, the first port comprising a wired port and / or a wireless port; determining that the network device forms a loop in the EasyMesh network when the loop detection information is included in a packet received by the network device through a second port.

2. The method of claim 1, wherein, The loop detection information comprises at least one of a loop detection identifier, a source port identifier, or a source device identifier, the source port identifier being used to indicate an initiating port of the loop detection information, and the source device identifier being used to indicate an initiating device of the loop detection information.

3. The method of claim 2, wherein, The loop detection information comprises the source port identifier or the source device identifier, and when the source device identifier of the loop detection information indicates the network device or the source port identifier indicates a port of the network device, it is determined that the network device forms a loop in the EasyMesh network.

4. The method according to any one of claims 1 to 3, characterized in that, The loop detection information is in a 1905.1 topology discovery message in an EasyMesh protocol.

5. The method of claim 4, wherein, The 1905.1 topology discovery message comprises a forwarding indicator field, and a value of the forwarding indicator field is used to indicate that the 1905.1 topology discovery message is forwarded by the network device.

6. The method of claim 4, wherein, The network device is a proxy node in the EasyMesh network, and the sending of the loop detection information through the first port comprises: sending the 1905.1 topology discovery message to a control node through a port connected to the control node in the EasyMesh network.

7. The method according to any one of claims 1 to 6, characterized in that, The sending of the loop detection information through the first port comprises: sending the loop detection information through the first port in a case where a topology structure of the EasyMesh network changes.

8. The method according to any one of claims 1 to 7, characterized in that, The method further comprises: discarding the loop detection information in a case where the source device identifier of the loop detection information indicates a network device other than the network device or the source port identifier indicates a port of a network device other than the network device.

9. The method according to any one of claims 1-7, characterized in that, The loop detection information further comprises a forwarding times identifier, a value of the forwarding times identifier is decremented by one after the loop detection information is forwarded each time, and the method further comprises: sending the loop detection information through at least one port in a case where the source device identifier of the loop detection information indicates a network device other than the network device or the source port identifier indicates a port of a network device other than the network device, and the value of the forwarding times identifier is greater than zero.

10. The method according to any one of claims 1-9, characterized in that, The second port is one or more, and the determining that the network device forms a loop in the EasyMesh network comprises: retaining one of the first port and the second port according to network qualities corresponding to the first port and the second port, and closing the remaining port.

11. The method of claim 10, wherein, The network quality comprises one or more of an air interface negotiation rate, an air interface negotiation received signal strength indication (RSSI), an air interface delay, an air interface packet loss rate, an air interface duty cycle, and a number of interfering APs.

12. The method of claim 11, wherein, The loop detection information further comprises a source port network quality identifier, and the source port network quality identifier is used to indicate a network quality of the initiating port.

13. A loop detection apparatus, characterized by The method further comprises: a transceiving module, configured to send loop detection information through at least one port; the loop detection information comprises at least one of a loop detection identifier, a source port identifier or a source device identifier, the source port identifier is used to indicate an initiating port of the loop detection information, the source device identifier is used to indicate an initiating device of the loop detection information, and the at least one port comprises a wired port and / or a wireless port; a processing module, configured to filter loop detection information from received packets, and determine that the network device forms a loop in the EasyMesh network.

14. A loop detection system characterized by, The system is based on an EasyMesh network, and the system comprises a control node and at least one proxy node, the control node is connected with the at least one proxy node respectively, and any one of the at least one proxy node is configured to execute the loop detection method according to any one of claims 1-12.

15. A network device, comprising: comprising a processor and a memory; the processor is configured to execute instructions stored in the memory, so that the network device executes the method according to any one of claims 1-12.

16. A computer program product comprising instructions, characterized in that, when the instructions are executed by the network device, the network device executes the method according to any one of claims 1-12.

Images