System and method for preventing broadcast storm through heterogeneous network interconnection

Abstract

The invention further provides a system and a method for preventing the broadcast storm through heterogeneous network interconnection, the first network is provided with the main node and the auxiliary node, the main node and the auxiliary node both store the uniform broadcast domain identifier, and the broadcast domain identifier and the device identifier of the main node in the same broadcast domain are carried in a sent message; and when receiving the message, the equipment node discards the message when the broadcast domain identifier carried by the message is different from the broadcast domain identifier stored by the equipment node, and processes the message when the broadcast domain identifier is the same as the broadcast domain identifier stored by the equipment node. According to the method and the device, a loop can be prevented, a wired link cannot be blocked, a broadcast storm can be effectively prevented, and a wireless MESH network has a basic condition of selecting an optimal MESH routing path.

Description

Technical Field

[0001] The present invention relates to the technical field of heterogeneous wireless networks, and in particular to a system and method for preventing broadcast storms through interconnection of heterogeneous networks. Background Art

[0002] Wireless MESH routing protocols are basically non-standard protocols in the industry, and there are fewer application scenarios for the interconnection of wireless MESH networks with heterogeneous networks, and there are no relevant technical solution standards. When wireless MESH networks and heterogeneous networks are interconnected through multiple wired links, in order to prevent broadcast storms, if the STP anti-loop protocol of traditional wired networks is used, multiple wired links need to be blocked and only one wired link is retained, which will lose the original intention of multiple wired interconnections.

[0003] Two networking scenarios are given as examples:

[0004] Scenario 1: Figure 1 In the networking shown, MESH-R and MESH-X are two heterogeneous wireless MESH networks, each of which has 4 nodes. The two MESH networks are connected together by wires: X1 is connected to R1, and X2 is connected to R2. If the STP protocol is used, one of the wired connections of X1-R1 or X2-R2 will be blocked to prevent loops. Figure 1 Taking blocking X2-R2 as an example, if R4 wants to access X4, the path is: R4-R2-R1-X1-X2-X4, the path will be very long, and it does not achieve the original intention of multiple wired interconnections between heterogeneous MESH networks. It is expected that the X2-R2 link is not blocked, and the best path for R4 to access X4 is: R4-R2-X2-X4.

[0005] Scenario 2: Figure 2 In the networking shown, when the wireless connection between R1 and R2 is weak or there is no wireless connection due to environmental reasons (such as fire door isolation), an optical cable is required to directly connect R1 and R2. Figure 2 The MESH-X network in the network is transformed into a wired interconnection. At this time, the path for R3 to access R4 is: R3—R1--R2—R4, but the transmission path between R1 and R2 is expected to go through the wired network S1-S2, rather than the original wireless network R1-R2 (weak signal), to reduce the end-to-end transmission delay. If the STP anti-loop protocol is used, one of the wired links S1-R1 or S2-R2 will be blocked, and the expectation of wired direct connection cannot be achieved.

[0006] In the above two business scenarios, when the wireless MESH network and the heterogeneous network are interconnected through multiple wired connections, although the STP protocol can prevent loops, it will block multiple wired connections, making the basic condition of "selecting the best MESH routing path" lose its original intention of multiple wired interconnections. Summary of the invention

[0007] Based on the above problems, the present invention provides a system and method for interconnecting heterogeneous networks to prevent broadcast storms, which aims to solve the technical problems of the prior art such as blocking between heterogeneous networks due to anti-ring protocols.

[0008] A system for interconnecting heterogeneous networks to prevent broadcast storms, comprising at least one wireless MESH network, wherein the at least one wireless MESH network is a first network, and a heterogeneous layer 2 network connected to the first network is a second network;

[0009] The device nodes in the first network are divided into primary nodes and secondary nodes. The primary node is connected to the second network by wire and communicates with at least one device node in the first network through the second network. The secondary node is a device node in the first network other than the primary node.

[0010] The master node and all slave nodes associated with the master node form a broadcast domain, and the slave nodes in the broadcast domain perform data transmission with the second network through the master node;

[0011] The master node and all slave nodes in the same broadcast domain store a unified broadcast domain identifier and carry the broadcast domain identifier in the messages sent. The broadcast domain identifier is the device identifier of the master node in the same broadcast domain.

[0012] The device node performs the following operations on the received message:

[0013] If the broadcast domain identifier carried in the received message is different from the broadcast domain identifier stored by itself, the message is discarded;

[0014] When the broadcast domain identifier carried in the received message is the same as the broadcast domain identifier stored by itself, the message is processed.

[0015] Furthermore, the primary node and the secondary node periodically broadcast and send a report message, which carries a broadcast domain identifier, routing transmission quality, and a full routing path;

[0016] The secondary node that receives the report message dynamically adjusts the association relationship with the primary node according to the broadcast domain identifier, routing transmission quality, and routing full path in the report message.

[0017] Further, when the secondary node serves as the local end, upon receiving a report message sent by the opposite end that satisfies the first condition, the local end is associated with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0018] The first condition is:

[0019] This end is not associated with any master node; and

[0020] The device identifier of the local end is not in the full route path carried in the report message sent by the other end; and

[0021] The peer has an associated master node.

[0022] Further, when the secondary node serves as the local end, upon receiving a report message sent by the opposite end that satisfies the second condition, the local end is associated with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0023] The second condition is:

[0024] The device identifier of the local end is not in the full route path carried in the report message sent by the other end; and

[0025] This end already has an associated master node; and

[0026] The peer end in the full routing path of the local end is the parent node of the local end.

[0027] Further, when the secondary node serves as the local end, upon receiving a report message sent by the opposite end that satisfies the third condition, the local end is associated with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0028] The third condition is:

[0029] The device identifier of the local end is not in the full route path carried in the report message sent by the other end;

[0030] This end already has an associated master node; and

[0031] The peer node in the local end's own routing path is not the local end's parent node; and

[0032] The difference between the transmission quality of the first route and the transmission quality of the second route is greater than a preset threshold value;

[0033] The first route transmission quality is the route transmission quality calculated by the local end from the local end itself along the full route path in the report message to the primary node in the report message;

[0034] The second routing transmission quality is the routing transmission quality of the entire routing path from the local end to the associated master node calculated by the local end.

[0035] A method for preventing broadcast storms in heterogeneous network interconnection, using the aforementioned system for preventing broadcast storms in heterogeneous network interconnection, comprising:

[0036] Step A1: The master node and all the slave nodes associated with the master node form a broadcast domain. The master node and all the slave nodes in the same broadcast domain store a unified broadcast domain identifier, which is the device identifier of the master node in the same broadcast domain.

[0037] Step A2: the device node carries the broadcast domain identifier in the message sent out;

[0038] Step A3: When the device node receives the message:

[0039] If the broadcast domain identifier carried in the received message is different from the broadcast domain identifier stored in the system, proceed to step A4;

[0040] If the broadcast domain identifier carried in the received message is the same as the broadcast domain identifier stored in the system, proceed to step A5;

[0041] Step A4, discard the message;

[0042] Step A5: Process the message.

[0043] Furthermore, in step A1, the master node and the slave node in the first network periodically broadcast and send report messages, and the report messages carry the broadcast domain identifier, routing transmission quality and the entire routing path. The slave nodes that receive the report messages dynamically adjust the association relationship with the master node based on the broadcast domain identifier, routing transmission quality and the entire routing path in the report messages.

[0044] Further, in step A1, when the secondary node acts as the local end, upon receiving a report message sent by the opposite end that satisfies the first condition, it associates with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0045] The first condition is:

[0046] This end is not associated with any master node; and

[0047] The device identifier of the local end is not in the full route path carried in the report message sent by the other end; and

[0048] The peer has an associated master node.

[0049] Further, in step A1, when the secondary node acts as the local end, upon receiving a report message sent by the opposite end that satisfies the second condition, it will associate with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0050] The second condition is:

[0051] The device identifier of the local end is not in the full route path carried in the report message sent by the other end; and

[0052] This end already has an associated master node; and

[0053] The peer end in the full routing path of the local end is the parent node of the local end.

[0054] Further, in step A1, when the secondary node acts as the local end, upon receiving a report message sent by the opposite end that satisfies the third condition, it will associate with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0055] The third condition is:

[0056] The device identifier of the local end is not in the full route path carried in the report message sent by the other end;

[0057] This end already has an associated master node; and

[0058] The peer node in the local end's own routing path is not the local end's parent node; and

[0059] The difference between the transmission quality of the first route and the transmission quality of the second route is greater than a preset threshold value;

[0060] The first route transmission quality is the route transmission quality calculated by the local end from the local end itself along the full route path in the report message to the primary node in the report message;

[0061] The second routing transmission quality is the routing transmission quality of the entire routing path from the local end to the associated master node calculated by the local end.

[0062] The beneficial technical effect of the present invention is that the present invention can prevent loops without blocking wired links, can effectively prevent broadcast storms, and enables the wireless MESH network to have the basic conditions for "selecting the best MESH routing path". BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1-2 This is an illustration of broadcast storms caused by anti-loop in heterogeneous networks in the prior art;

[0064] Figure 3 A schematic diagram of the architecture of a system for interconnecting heterogeneous networks to prevent broadcast storms according to the present invention;

[0065] Figure 4 A schematic diagram of switching broadcast domains of device nodes in a system for preventing broadcast storms through interconnection of heterogeneous networks according to the present invention;

[0066] Figure 5 The present invention is a flowchart of the steps of a method for interconnecting heterogeneous networks to prevent broadcast storms. DETAILED DESCRIPTION

[0067] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0068] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

[0069] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, but they are not intended to limit the present invention.

[0070] See also Figure 3 , the present invention provides a system for interconnecting heterogeneous networks to prevent broadcast storms, including at least one wireless MESH network, wherein the at least one wireless MESH network is a first network, and a heterogeneous layer 2 network connected to the first network is a second network;

[0071] The device nodes in the first network are divided into a main node and a secondary node. The main node is connected to the second network by wire, and is interconnected with another device node in the first network through the second network. The secondary node is a device node in the first network other than the main node.

[0072] The master node and all slave nodes associated with the master node form a broadcast domain, and the slave nodes in the broadcast domain transmit data with the second network through the master node; a slave node can only be associated with one master node at a time, that is, it cannot be associated with two or more master nodes at the same time;

[0073] The master node and all slave nodes in the same broadcast domain store a unified broadcast domain identifier and carry the broadcast domain identifier in the messages sent. The broadcast domain identifier is the device identifier of the master node in the same broadcast domain.

[0074] Each device node performs the following operations on the received message:

[0075] If the broadcast domain identifier carried in the received message is different from the broadcast domain identifier stored by itself, the message is discarded;

[0076] When the broadcast domain identifier carried in the received message is the same as the broadcast domain identifier stored by itself, the message is processed.

[0077] Specifically, there may be one or more master nodes.

[0078] Specifically, the second network is but not limited to a wired network, a wireless star network, and a wireless MESH network. The core idea of ​​the present invention is to configure the role of the master node in the first network. The master node can use MAP (MESH AP), which is defined as a MESH device node interconnected with the heterogeneous network (second network), similar to an AP access point, that is, there are two conditions for becoming a master node. One is that the device node must be connected to the second network by wire, and the second condition is that the device node can communicate with another device node through the second network. Therefore, in the same MESH network, there are at least two MAPs, that is, at least two master nodes, and these two master nodes (MAP nodes) and the heterogeneous network (second network) can communicate with each other through wires.

[0079] For example Figure 3As shown, in the first network, i.e., the MESH-R network, M1 / M2 are MAP nodes, and M1 / M2 can interoperate in the second network, i.e., the heterogeneous MESH-X network. If M2 and X2 have no wired connection, then M1 will not be a MAP node either, because M1 cannot interoperate with any node in the first network, the MESH-R network, in the MESH-X network; if R3 and X3 also have a wired connection, then R3 is also a MAP node, allowing three or even more MAP nodes.

[0080] For other non-master node device nodes and slave nodes, they can only be directly or indirectly associated with one MAP node (master node). The broadcast domain ID (broadcast domain identifier) ​​saved by the slave node is equal to the device identifier of the master node, i.e., the device ID. Each master node forms a broadcast domain, and broadcast / multicast messages can only be forwarded within the same broadcast domain. The slave nodes of the MESH network can only forward broadcast messages to heterogeneous networks (such as Figure 3 MESH-X network) to control broadcast / multicast / flooding domains and avoid loops.

[0081] Messages between broadcast domains formed by different master nodes cannot communicate directly with each other and are forwarded through the first network. Figure 3 As shown in the figure, broadcasts of M1 / R3 / R5 (device nodes in the M1 broadcast domain) and M2 / R4 / R6 (device nodes in the M2 broadcast domain) cannot communicate directly with each other, and both need to be indirectly forwarded through the heterogeneous MESH-X network.

[0082] Each slave node must be directly or indirectly associated with a master node nearby, and cannot be associated with two MESH devices at the same time. When there is no master node, the slave nodes all belong to broadcast domain 0, for example Figure 3 The default value of domain 0 in the broadcast domain identifier of each device node is 0, but data forwarding also follows the same principle: the same broadcast domain can forward or receive broadcast / multicast messages.

[0083] For the master node, its own device identification (device ID) is used as the broadcast domain representation (broadcast domain ID), and the device IDs of the entire network cannot conflict. It depends on the broadcast domain generated by M1, which is called the M1 broadcast domain. Figure 3 There are two broadcast domains: M1 broadcast domain and M2 broadcast domain.

[0084] Specifically, a broadcast domain identification field is added to the message header. When a message is sent, the broadcast domain identifier is carried. When a node receives a message, if the broadcast domain identifier of the message is the same as the broadcast domain identifier it saves, that is, the device identifier of the associated master node, it is considered to be in the same broadcast domain, and the message is processed, including receiving or forwarding. If the broadcast domain identifiers are different, they are considered to be different broadcast domains and are discarded, ensuring that messages between broadcast domains formed by different master nodes cannot communicate directly, and forwarding of messages in different broadcast domains needs to be achieved through the first network. Messages within the same broadcast domain can be directly received and forwarded within the broadcast domain.

[0085] The present invention can prevent loops without blocking wired links, can effectively prevent broadcast storms, and provides basic conditions for the on-demand routing shortest path algorithm, so that the wireless MESH network has the basic conditions for "selecting the best MESH routing path".

[0086] It should be noted that the message and the report message are different, and the message does not include the report message.

[0087] Furthermore, the primary node and the secondary node in the first network periodically broadcast and send a report message, wherein the report message carries a broadcast domain identifier, a routing transmission quality, and a full routing path;

[0088] The secondary node that receives the report message dynamically adjusts the association with the primary node according to the broadcast domain identifier, routing transmission quality, and routing full path in the report message.

[0089] When the master node receives the report message, no adjustment is made.

[0090] All MESH nodes, including master nodes and slave nodes, need to broadcast and send Report messages regularly in the entire wireless network. The report messages carry the following information: MAP ID (broadcast domain identifier), TxCost (route transmission quality), and TxPath (route full path).

[0091] MAP ID: When the device node is a primary node, the MAP ID is its own device ID; when the node is a secondary node, the MAP ID is the device ID of the associated primary node. The default value is 0.

[0092] TxCost: The routing transmission quality of the entire routing path from the current node to the associated master node. When the node is the master node, the TxCost in the report message sent is 0; when the node is a slave node, the TxCost in the report message sent is the routing transmission quality of the entire routing path from the slave node to the associated master node. When there is no associated master node, TxCost is the default value 0xFFFF. The routing transmission quality is based on comprehensive considerations such as the transmission rate, delay, and signal strength of the entire routing path.

[0093] TxPath: The full routing path from this node to the associated master node (the shortest routing path to the master node saved for data transmission). The TxPath in the report message sent by the master node is empty. Specifically, the full routing path is composed of the device identifiers of the secondary nodes that are passed in sequence to reach the associated master node (including the master node). If there is equipment MAP0→R1→R2→R3, the TxPath of MAP0 is empty, the TxPath of R1 is (MAP0), the TxPath of R2 is (R1, MAP0), and the TxPath of R3 is (R2, R1, MAP0). The meaning of this field: to prevent circular paths, such as preventing R1→R2→R3→R1.

[0094] Further, when the secondary node acts as the local end, upon receiving a report message sent by the opposite end that satisfies the first condition, it associates with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0095] The first condition is:

[0096] This end is not associated with any master node; and

[0097] The device identifier of the local end is not in the full route path carried in the report message sent by the other end; and

[0098] The peer has an associated master node.

[0099] Specifically, the opposite end refers to a device node in the first network. Relative to the local end, the opposite end is a secondary node as the local end. The opposite end is the device node whose report message broadcast in the first network is directly received by the local end.

[0100] Further, when the secondary node serves as the local end, upon receiving a report message sent by the opposite end that satisfies the second condition, the primary node associated with the local end is updated to the primary node associated with the opposite end, that is, the local end is associated with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0101] The second condition is:

[0102] The device identifier of the local end is not in the full route path carried in the report message sent by the other end; and

[0103] This end already has an associated master node; and

[0104] The peer end in the full routing path of the local end is the parent node of the local end.

[0105] Further, when the secondary node serves as the local end, upon receiving a report message sent by the opposite end that satisfies the third condition, the secondary node switches the primary node associated with the local end to the primary node associated with the opposite end, that is, the local end is associated with the primary node corresponding to the opposite end, so as to join the broadcast domain where the opposite end is located;

[0106] The third condition is:

[0107] The device identifier of the local end is not in the full route path carried in the report message sent by the other end;

[0108] This end already has an associated master node; and

[0109] The peer node in the local end's own routing path is not the local end's parent node; and

[0110] The difference between the transmission quality of the first route and the transmission quality of the second route is greater than a preset threshold value;

[0111] The first route transmission quality is the route transmission quality calculated by the local end itself along the entire route path in the report message to the main node in the report message;

[0112] The second routing transmission quality is the routing transmission quality of the entire routing path from the local end to the associated master node calculated by the local end.

[0113] The processing flow of the master node receiving the report message is: no processing is performed.

[0114] The processing flow of the secondary node that receives the report message is as follows.

[0115] After receiving the report message from the other end (whether it is a secondary node or a primary node), the secondary node analyzes the report message and first determines whether it is in the full routing path of the report message broadcast by the other end, that is, whether its own device identifier exists in the full routing path of the report message.

[0116] If it exists, no processing is required.

[0117] If it does not exist, the secondary node determines whether it has an associated primary node. If it does not have an associated primary node, it determines whether the peer receiving the report message is associated with a primary node or the peer itself is a primary node. If the peer is not associated with a primary node or is a primary node, no processing is performed. If the peer is a primary node, it is associated with the peer. If the peer is associated with a primary node, the secondary node is also associated with the primary node associated with the peer, and accesses the broadcast domain of the primary node of the peer. This is usually the process of finding and joining the broadcast domain of the nearest primary node when the secondary node is powered on or initialized and has no associated primary node.

[0118] If it does not exist, and the secondary node determines that it has an associated primary node, it will continue to determine whether the peer that sent the report message is its parent node. This is determined by whether the first device identifier of its current full route path is the device identifier of the peer. If so, it indicates that the peer and the secondary node may be moving together. Although it is still in the broadcast domain of the original associated primary node, the primary node associated with the parent node has changed to the new primary node. Therefore, the secondary node changes its primary node to the primary node of the peer and joins the broadcast domain where the peer is located. At this time, the secondary node updates the saved broadcast domain identifier to the device identifier of the primary node associated with the peer, that is, updates the broadcast domain identifier to join the new broadcast domain. At the same time, the routing transmission quality and the full route path are updated.

[0119] If it does not exist, and the secondary node determines that it has an associated primary node, but the peer end that sends the report message is not the secondary node's own parent node, this means that although the secondary node is already associated with the primary node, the secondary node is moving. Whether it needs to switch to the new primary node's broadcast domain or remain in the existing broadcast domain is determined by the route transmission quality. The difference between the transmission quality of the first route and the transmission quality of the second route is greater than the preset threshold value, which means that the transmission quality of the first route is much higher than that of the second route. At this time, the secondary node can consider switching to the broadcast domain of the new primary node. If it is not greater than the preset threshold value, it means that the transmission quality of the first route is similar to the second route and may even be lower than the transmission quality of the second route, indicating that data transmission from the path of the existing associated primary node is more efficient, so it remains in the existing broadcast domain and no changes are made. Figure 4 As shown in the figure, assuming that M1 and R3 devices are arranged at fixed positions on the 1st floor, and M2 and R4 are arranged at fixed positions on the 2nd floor, M1 / M2 can communicate with each other through the heterogeneous network MESH-X. When the handheld device R5 walks from the 1st floor to the 2nd floor, the reselection process of the master node will be automatically triggered, and the user will not be aware of the switch.

[0120] R5 was originally indirectly associated with M1 through R3, and could receive Report messages from neighbors R3 / R4 at the same time. When the user carried R5 from the 1st floor (domain 1) to the 2nd floor (domain 2), the cost relationship with neighbors R3 / R4 changed (closer to R4), triggering the process of re-selecting the master node: A) First, obtain the shortest route full path R5-R3-M1 to the associated master node, and the route full path R5-R4-M2 corresponding to the associated master node in the Report message received from neighbor R4. B) If the difference between the route transmission cost of the path R5-R4-M2 and the route transmission cost of the path R5-R3-M1 is greater than the preset threshold value, re-associate with the better device M2 (that is, update the broadcast domain identifier, route transmission cost, and route full path stored by itself).

[0121] It should be noted that the report message is reachable in one hop and is not forwarded. That is, when the secondary node and the primary node receive the report message sent by other nodes, they only receive it but do not forward it.

[0122] The master node will be changed according to the actual configuration.

[0123] When the master node is changed to a non-master node, the broadcast domain identifier is set to 0, the Report message sent is changed, and the above association process is repeated.

[0124] When a non-master node is changed to a master node, the broadcast domain identifier is set to its own device identifier and the Report message sent is changed.

[0125] When the above two changes occur, the neighbor node may trigger the process of re-electing the master node after receiving the Report message.

[0126] See also Figure 5 The present invention also provides a method for preventing broadcast storms in heterogeneous network interconnection, using the aforementioned system for preventing broadcast storms in heterogeneous network interconnection, comprising:

[0127] Step A1: The master node and all the slave nodes associated with the master node form a broadcast domain. The master node and all the slave nodes in the same broadcast domain save a unified broadcast domain identifier, which is the device identifier of the master node in the same broadcast domain.

[0128] Step A2: the device node carries the broadcast domain identifier in the message sent out;

[0129] Step A3: When the device node receives the message:

[0130] If the broadcast domain identifier carried in the received message is different from the broadcast domain identifier stored in the system, proceed to step A4;

[0131] If the broadcast domain identifier carried in the received message is the same as the broadcast domain identifier stored in the system, proceed to step A5;

[0132] Step A4, discard the message;

[0133] Step A5: Process the message.

[0134] The core idea of ​​the present invention is to configure the role of the master node in the first network. The master node can use MAP (MESH AP), which is defined as a MESH device node interconnected with the heterogeneous network (second network), similar to an AP access point, that is, there are two conditions for becoming a master node. One is that the device node must be connected to the second network by wire, and the second condition is that the device node can communicate with another device node through the second network. In the same MESH network, there are at least two MAPs, that is, at least two master nodes, and these two master nodes (MAP nodes) and the heterogeneous network (second network) can communicate with each other through wires.

[0135] Messages between broadcast domains formed by different master nodes cannot communicate directly with each other and are forwarded through the first network. Figure 3 As shown in the figure, broadcasts of M1 / R3 / R5 (device nodes in the M1 broadcast domain) and M2 / R4 / R6 (device nodes in the M2 broadcast domain) cannot communicate directly with each other, and both need to be indirectly forwarded through the heterogeneous MESH-X network.

[0136] The present invention can prevent loops without blocking wired links, can effectively prevent broadcast storms, and provides basic conditions for the on-demand routing shortest path algorithm, so that the wireless MESH network has the basic conditions for "selecting the best MESH routing path".

[0137] Furthermore, in step A1, the primary node and secondary node in the first network periodically broadcast and send report messages, which carry the broadcast domain identifier, routing transmission quality and the entire routing path. The secondary node that receives the report message dynamically adjusts the association relationship with the primary node based on the broadcast domain identifier, routing transmission quality and the entire routing path in the report message.

[0138] All MESH nodes, including master nodes and slave nodes, need to broadcast and send Report messages regularly in the entire wireless network. The report messages carry the following information: MAP ID (broadcast domain identifier), TxCost (route transmission quality), and TxPath (route full path).

[0139] MAP ID: When the device node is a primary node, the MAP ID is its own device ID; when the node is a secondary node, the MAP ID is the device ID of the associated primary node. The default value is 0.

[0140] TxCost: The routing transmission quality of the entire routing path from the current node to the associated master node.

[0141] TxPath: The full routing path from this node to the associated master node (the shortest routing path to the master node saved for data transmission).

[0142] Further, in step A1, when the secondary node serves as the local end, upon receiving a report message sent by the opposite end that satisfies the first condition, it associates with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located;

[0143] The first condition is:

[0144] This end is not associated with any master node; and

[0145] The device identifier of the local end is not in the full route path carried in the report message sent by the other end; and

[0146] The peer has an associated master node.

[0147] Further, in step A1, when the secondary node serves as the local end, upon receiving a report message sent by the opposite end that satisfies the second condition, the primary node associated with itself is updated to the primary node associated with the opposite end, that is, the local end is associated with the primary node corresponding to the opposite end, so as to join the broadcast domain where the opposite end is located;

[0148] The second condition is:

[0149] The device identifier of the local end is not in the full route path carried in the report message sent by the other end; and

[0150] This end already has an associated master node; and

[0151] The peer end in the full routing path of the local end is the parent node of the local end.

[0152] Further, in step A1, when the secondary node serves as the local end, upon receiving a report message sent by the opposite end that satisfies the third condition, the secondary node switches the primary node associated with itself to the primary node associated with the opposite end that sends the report message, that is, the local end is associated with the primary node corresponding to the opposite end, so as to join the broadcast domain where the opposite end is located;

[0153] The third condition is:

[0154] The device identifier of the local end is not in the full route path carried in the report message sent by the other end;

[0155] This end already has an associated master node; and

[0156] The peer node in the local end's own routing path is not the local end's parent node; and

[0157] The difference between the transmission quality of the first route and the transmission quality of the second route is greater than a preset threshold value;

[0158] The first route transmission quality is the route transmission quality calculated by the local end from the local end itself along the full route path in the report message to the primary node in the report message;

[0159] The second routing transmission quality is the routing transmission quality of the entire routing path from the local end to the associated master node calculated by the local end.

[0160] It should be noted that the report message is reachable in one hop and is not forwarded. That is, when the secondary node and the primary node receive the report message sent by other nodes, they only receive it but do not forward it.

[0161] The master node will be changed according to the actual configuration.

[0162] When the master node is changed to a non-master node, the broadcast domain identifier is set to 0, the Report message sent is changed, and the above association process is repeated.

[0163] When a non-master node is changed to a master node, the broadcast domain identifier is set to its own device identifier and the Report message sent is changed.

[0164] When the above two changes occur, the neighbor node may trigger the process of re-electing the master node after receiving the Report message.

[0165] The above are only preferred embodiments of the present invention, and are not intended to limit the implementation methods and protection scope of the present invention. Those skilled in the art should be aware that all solutions obtained by equivalent substitutions and obvious changes made using the description and illustrations of the present invention should be included in the protection scope of the present invention.

Claims

1. A system for preventing broadcast storms by interconnecting heterogeneous networks, comprising at least one wireless MESH network, characterized in that: At least one of the wireless MESH networks is a first network, and a heterogeneous layer 2 network connected to the first network is a second network; The device nodes in the first network are divided into a main node and a secondary node, the main node is connected to the second network by wire, and communicates with at least one device node in the first network through the second network, and the secondary node is a device node in the first network other than the main node; The master node and all the slave nodes associated with the master node form a broadcast domain, and the slave nodes located in the broadcast domain perform data transmission with the second network through the master node; The master node and all the slave nodes located in the same broadcast domain store a unified broadcast domain identifier, and carry the broadcast domain identifier in the sent message, where the broadcast domain identifier is the device identifier of the master node in the same broadcast domain; The device node performs the following operations on the received message: When the broadcast domain identifier carried in the received message is different from the broadcast domain identifier stored by itself, the message is discarded; When the broadcast domain identifier carried in the received message is the same as the broadcast domain identifier stored by itself, the message is processed.

2. A system for preventing broadcast storms by interconnecting heterogeneous networks as claimed in claim 1, characterized in that: The primary node and the secondary node both broadcast and send report messages at regular intervals, wherein the report messages carry the broadcast domain identifier, the routing transmission quality, and the full routing path; The secondary node that receives the report message dynamically adjusts the association relationship with the primary node according to the broadcast domain identifier, routing transmission quality, and routing full path in the report message.

3. A system for preventing broadcast storms by interconnecting heterogeneous networks as claimed in claim 2, characterized in that: When the secondary node serves as the local end, upon receiving the report message sent by the opposite end and the first condition is met, the local end is associated with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located; The first condition is: This end is not associated with any of the master nodes; and The device identifier of the local end is not in the full routing path carried by the report message sent by the other end; and The peer has an associated master node.

4. A system for preventing broadcast storms by interconnecting heterogeneous networks as claimed in claim 2, characterized in that: When the secondary node serves as the local end, upon receiving the report message sent by the opposite end and satisfying the second condition, the local end is associated with the primary node corresponding to the opposite end, so as to join the broadcast domain where the opposite end is located; The second condition is: The device identifier of the local end is not in the full routing path carried by the report message sent by the other end; and The local terminal is already associated with the master node; and The peer end in the full routing path of the local end is the parent node of the local end.

5. The system for preventing broadcast storms by interconnecting heterogeneous networks as claimed in claim 2, characterized in that: When the secondary node serves as the local end, upon receiving the report message sent by the opposite end and satisfying the third condition, the local end is associated with the primary node corresponding to the opposite end, so as to join the broadcast domain where the opposite end is located; The third condition is: The device identifier of the local end is not in the full routing path carried by the report message sent by the other end; The local terminal is already associated with the master node; and The peer node in the local end's own routing path is not the local end's parent node; and The difference between the transmission quality of the first route and the transmission quality of the second route is greater than a preset threshold value; The first route transmission quality is a route transmission quality calculated by the local end from the local end itself along the full route path in the report message to the primary node in the report message; The second routing transmission quality is the routing transmission quality of the entire routing path from the local end to the associated master node calculated by the local end.

6. A method for preventing broadcast storms in heterogeneous network interconnection, characterized in that: A system for preventing broadcast storms by interconnecting heterogeneous networks according to any one of claims 1 to 5, comprising: Step A1, the master node and all the slave nodes associated with the master node form a broadcast domain, the master node and the slave nodes in the same broadcast domain store a unified broadcast domain identifier, and the broadcast domain identifier is a device identifier of the master node in the same broadcast domain; Step A2, the device node carries the broadcast domain identifier in the message sent out; Step A3, when the device node receives the message: If the broadcast domain identifier carried in the received message is different from the broadcast domain identifier stored in the device, proceed to step A4; If the broadcast domain identifier carried in the received message is the same as the broadcast domain identifier stored in the system, proceed to step A5; Step A4, discarding the message; Step A5: Process the message.

7. A method for preventing broadcast storms in heterogeneous network interconnection as claimed in claim 6, characterized in that: In step A1, the primary node and the secondary node in the first network periodically broadcast and send report messages, wherein the report messages carry the broadcast domain identifier, routing transmission quality, and the entire routing path. The secondary node that receives the report message dynamically adjusts the association relationship with the primary node based on the broadcast domain identifier, routing transmission quality, and the entire routing path in the report message.

8. A method for preventing broadcast storms in heterogeneous network interconnection as claimed in claim 7, characterized in that: In the step A1, when the secondary node acts as the local end, upon receiving the report message sent by the opposite end and satisfying the first condition, the secondary node associates with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located; The first condition is: This end is not associated with any of the master nodes; and The device identifier of the local end is not in the full routing path carried by the report message sent by the other end; and The peer has an associated master node.

9. A method for preventing broadcast storms in heterogeneous network interconnection as claimed in claim 7, characterized in that: In the step A1, when the secondary node acts as the local end, upon receiving the report message sent by the opposite end and satisfying the second condition, the secondary node will associate with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located; The second condition is: The device identifier of the local end is not in the full routing path carried by the report message sent by the other end; and The local terminal is already associated with the master node; and The peer end in the full routing path of the local end is the parent node of the local end.

10. The method for preventing broadcast storms in heterogeneous network interconnection according to claim 7, characterized in that: In the step A1, when the secondary node acts as the local end, upon receiving the report message sent by the opposite end and satisfying the third condition, the secondary node will associate with the primary node corresponding to the opposite end to join the broadcast domain where the opposite end is located; The third condition is: The device identifier of the local end is not in the full routing path carried by the report message sent by the other end; The local terminal is already associated with the master node; and The peer node in the local end's own routing path is not the local end's parent node; and The difference between the transmission quality of the first route and the transmission quality of the second route is greater than a preset threshold value; The first route transmission quality is a route transmission quality calculated by the local end from the local end itself along the full route path in the report message to the primary node in the report message; The second routing transmission quality is the routing transmission quality of the entire routing path from the local end to the associated master node calculated by the local end.

Images