CN110972163A - ZigBee terminal node network management method and system - Google Patents
ZigBee terminal node network management method and system Download PDFInfo
- Publication number
- CN110972163A CN110972163A CN201911221700.2A CN201911221700A CN110972163A CN 110972163 A CN110972163 A CN 110972163A CN 201911221700 A CN201911221700 A CN 201911221700A CN 110972163 A CN110972163 A CN 110972163A
- Authority
- CN
- China
- Prior art keywords
- node
- network
- zigbee terminal
- reconnection
- terminal node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 28
- 238000000034 method Methods 0.000 claims abstract description 62
- 238000012544 monitoring process Methods 0.000 claims abstract description 9
- 238000011084 recovery Methods 0.000 claims description 16
- 238000004220 aggregation Methods 0.000 claims description 2
- 230000002776 aggregation Effects 0.000 claims description 2
- 101100129499 Arabidopsis thaliana MAX2 gene Proteins 0.000 description 6
- 101100129496 Arabidopsis thaliana CYP711A1 gene Proteins 0.000 description 5
- 101100083446 Danio rerio plekhh1 gene Proteins 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000005304 joining Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 2
- 230000005059 dormancy Effects 0.000 description 2
- 230000007958 sleep Effects 0.000 description 2
- XUIMIQQOPSSXEZ-UHFFFAOYSA-N Silicon Chemical compound [Si] XUIMIQQOPSSXEZ-UHFFFAOYSA-N 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 229910052710 silicon Inorganic materials 0.000 description 1
- 239000010703 silicon Substances 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the application provides a ZigBee terminal node network management method and a ZigBee terminal node network management system, wherein the ZigBee terminal node is added into a first father node network, then network information is stored, the first father node is monitored, and whether the first father node is disconnected or not is analyzed; if the first father node is disconnected, the ZigBee terminal node executes a reconnection process according to the preset reconnection upper limit times and analyzes whether reconnection is successful or not; if the ZigBee terminal node is failed to reconnect, the ZigBee terminal node clears network information, monitors a channel and executes a new network adding process; the ZigBee terminal node detects a second father node meeting the requirement in a channel according to a preset network access upper limit number, and adds a new network; if the ZigBee terminal node is added into a new network before the network access upper limit times, storing network information; otherwise, monitoring the channel again after the preset delay time, detecting a third father node meeting the requirement, and adding a new network; the ZigBee terminal nodes can be accessed to the network in time after the ZigBee terminal nodes lose the father nodes.
Description
Technical Field
The application relates to the technical field of wireless data transmission, in particular to a ZigBee terminal node network management method and system.
Background
In the standard ZigBee protocol, for example, an Ember Znet protocol stack SDK is introduced by a silicon labs company, when a terminal node cannot detect any qualified father node, the father node is lost, the terminal node loses the network, and if the qualified father node is on-line again after a period of time, the terminal node is still in the state of losing the network without the father node and cannot perform any communication. It is desirable to provide a solution to the problem of re-networking after an end node loses its parent.
Disclosure of Invention
The embodiment of the application aims to provide a ZigBee terminal node network management method and a ZigBee terminal node network management system, which are used for achieving the technical effect of timely solving the network access problem after a ZigBee terminal node loses a father node.
In a first aspect, an embodiment of the present application provides a ZigBee terminal node network management method, including that a ZigBee terminal node joins a first father node network, stores network information, monitors the first father node, and analyzes whether the first father node is disconnected; if the first father node is disconnected, the ZigBee terminal node executes a reconnection process according to a preset reconnection upper limit number, and analyzes whether reconnection is successful; if the ZigBee terminal node is failed to reconnect, the ZigBee terminal node clears the network information, monitors a channel and executes a new network adding process; the ZigBee terminal node detects a second father node meeting the requirement in a channel according to a preset network access upper limit number, and adds a new network; if the ZigBee terminal node is added into a new network before the network access upper limit times, storing network information; otherwise, monitoring the channel again after the preset delay time, and adding the third father node into the network if the third father node which meets the requirement is detected.
In the implementation process, after the ZigBee terminal node is added into a network of a father node, corresponding network information can be stored, and the ZigBee terminal node is convenient to directly establish connection with the father node after power failure and restart; meanwhile, the ZigBee terminal node can monitor whether the father node of the ZigBee terminal node is disconnected. If the father node of the ZigBee terminal node is disconnected, the ZigBee terminal node tries to reconnect the original father node according to the set reconnection times; if the ZigBee terminal node is still not connected with the original father node after the set reconnection times are reached, the ZigBee terminal node clears the network information of the original father node, then the channel is monitored, other father nodes meeting the requirements are searched according to the preset network access upper limit times to establish a new network, if the new father node is not found after the network access upper limit times are reached, the channel is monitored after the dormancy is carried out according to the set delay time, and the father node meeting the requirements is searched; by the mode, network connection can be established in time after the ZigBee terminal node loses the father node, and meanwhile, the power consumption of the ZigBee terminal node is reduced.
Further, if the father node is disconnected, the ZigBee terminal node executes a reconnection process according to a preset reconnection upper limit number of times, and the step of analyzing whether reconnection is successful includes: executing a reconnection process according to a preset first counting variable, reconnection upper limit times and a first time delay event, accumulating the first counting variable once in the reconnection process every time of executing, and then starting the first time delay event to execute reconnection operation; meanwhile, whether the reconnection operation is successful after the reconnection operation is executed is analyzed; and stopping executing the reconnection process when the first counting variable is equal to the reconnection upper limit times.
In the implementation process, the ZigBee terminal node executes a reconnection process according to a preset first counting variable, reconnection upper limit times and a first time delay event; if the reconnection operation is not performed once, the first counting variable is increased by one; however, in order to avoid that the reconnection of the parent node cannot be completed for a long time after the power failure, the power consumption of the ZigBee terminal node is increased, and when the first counting variable reaches the preset reconnection upper limit times, the reconnection process is stopped.
Further, the method further comprises: and if the number of the ZigBee terminal nodes connected with the first father node is lower than a preset value, the reconnection upper limit number is set to be zero.
In the implementation process, if the number of the ZigBee terminal nodes connected with one father node is small, the ZigBee terminal nodes do not automatically execute a reconnection process, and a worker can manually reconnect the ZigBee terminal nodes.
Further, the step of adding a new network by the ZigBee terminal node according to a parent node meeting requirements in a preset network access upper limit number detection channel includes: executing a network access process according to a preset second counting variable, the network access upper limit times and a second time delay event, accumulating the second counting variable once when the network access process is executed once, and then starting the second time delay event to execute the network access operation; meanwhile, whether reconnection is successful after the network access operation is executed is analyzed; and stopping executing the network access process when the second counting variable is equal to the network access upper limit times.
In the implementation process, after the ZigBee terminal node cannot be connected to the original father node, the network information of the original father node is cleared, the storage space is released, and then the network access process is executed according to the second counting variable, the network access upper limit times and the second time delay event. And adding one to the second counting variable every time the network access process is carried out, and stopping executing the network access process when the second counting variable reaches the network access upper limit times, so that the power consumption of the ZigBee terminal node is reduced.
Further, the method further comprises: and if the network recovery of the ZigBee terminal node fails in a preset network automatic recovery time period, ending the network recovery process.
In the implementation process, a network automatic recovery time period can be set, and if the network recovery of the ZigBee terminal node fails in the preset network automatic recovery time period, the network recovery process is ended, so that the power consumption of the ZigBee terminal node is reduced.
Further, the method further comprises: after the first father node is disconnected, the sink node connected with the first father node detects whether the first father node is reconnected within a preset on-line time period; and if the first father node is not reconnected in the preset online time period, the sink node sends alarm information to a control terminal connected with the sink node.
In the implementation process, if the sink node connected with the original father node of the ZigBee terminal node detects that the original father node is still not re-connected with the sink node within a preset online time period, the sink node sends alarm information to the control terminal connected with the sink node, and timely notifies a worker to overhaul.
Further, the method further comprises: and if the ZigBee terminal node fails to reconnect, the ZigBee terminal node stores the original network information and monitors the channel, and a new network adding process is executed.
In the implementation process, if the reconnection of the ZigBee terminal node and the original father node fails, the network information of the original father node can be stored, and then whether the father node meeting the requirements exists in the channel is monitored, and a new network adding process is executed; in this way, the communication connection can be established with the original father node in time after the original father node is recovered.
In a second aspect, an embodiment of the present application provides a ZigBee terminal node network management system, including a plurality of ZigBee terminal nodes; a plurality of father nodes correspondingly connected with the ZigBee terminal nodes; the ZigBee terminal node is added into a first father node network, then network information is stored, the first father node is monitored, and whether the first father node is disconnected or not is analyzed; if the first father node is disconnected, the ZigBee terminal node executes a reconnection process according to a preset reconnection upper limit number, and analyzes whether reconnection is successful; if the ZigBee terminal node is failed to reconnect, the ZigBee terminal node clears the network information, monitors a channel and executes a new network adding process; the ZigBee terminal node detects a second father node meeting the requirement in a channel according to a preset network access upper limit number, and adds a new network; if the ZigBee terminal node is added into a new network before the network access upper limit times, storing network information; otherwise, monitoring the channel again after the preset delay time, detecting a third father node meeting the requirement, and joining the network again.
In the implementation process, the embodiment of the application also provides a system using the ZigBee terminal node network management method, the ZigBee terminal node in the system is connected with the corresponding father node, the ZigBee terminal node stores network information after being added into the network of the first father node, and meanwhile, the ZigBee terminal node monitors the first father node and analyzes whether the first father node is disconnected. If the first father node is disconnected, trying to reconnect; if the reconnection is not carried out for a long time, the original network information is removed, then the channel is monitored, a father node which meets the requirement is searched, and the network connection is reestablished. If the network connection cannot be established after the network connection is tried for many times, the ZigBee terminal node sleeps according to the set delay time, so that the power consumption is reduced; and after the dormancy is finished, trying to establish network connection with the new father node.
Further, the ZigBee terminal node network management system further includes: a sink node connected to each of the parent nodes; the control terminal is connected with the aggregation node; the sink node detects whether the first father node is reconnected within a preset online time period after the first father node is disconnected; and if the first father node is not reconnected in the preset online time period, the sink node sends alarm information to the control terminal.
In the implementation process, the father node of each ZigBee terminal node is also connected with a sink node, and the sink node is connected with a control terminal; when the original father node of the ZigBee terminal node is not re-connected with the sink node within the preset on-line time period, the sink node sends alarm information like the control terminal, and staff are informed to overhaul in time.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic general flow chart of a network management method for ZigBee terminal nodes according to an embodiment of the present application;
fig. 2 is a schematic flow chart of an embodiment of a network management method for a ZigBee terminal node according to an embodiment of the present application;
fig. 3 is a schematic view of a topology structure of a ZigBee terminal node network management system according to an embodiment of the present application.
Icon: 10-a ZigBee terminal node network management system; 100-a parent node; 200-ZigBee terminal nodes; 300-sink nodes; 400-control terminal.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Referring to fig. 1, fig. 1 is a schematic general flow chart of a network management method for a ZigBee terminal node according to an embodiment of the present application.
The research of the applicant finds that in the ZigBee network, the terminal node can only directly communicate with the father node, the communication with other nodes needs to be forwarded through the father node, but two terminals of different father nodes cannot communicate with each other, and the terminals need to be the same father node to realize the communication. Once the parent node of the end node drops, the end node cannot communicate. Therefore, in order to solve the problem, embodiments of the present application provide a ZigBee terminal node network management method, which is described in the following.
Step S101, a ZigBee terminal node is added into a first father node network, then network information is stored, the first father node is monitored, and whether the first father node is disconnected or not is analyzed;
in the ZigBee wireless network, after a ZigBee terminal node is added into a coordinator (father node) network, network information is stored firstly, and meanwhile, the coordinator (father node) is monitored to analyze whether the network is disconnected.
In one implementation mode, a polling mechanism is arranged between a terminal node and a father node in a ZigBee network, a data request packet is periodically sent to the father node, the father node can judge that the terminal is still online after receiving the data request packet, information of the terminal node is continuously stored in a terminal management table of the father node, meanwhile, a confirmation data packet is returned to the terminal node to tell that the terminal has received the data request packet, and the terminal node knows that the father node is still online after receiving a reply. If the father node is disconnected, the terminal node sends a data request packet to the father node to obtain the reply of the father node, and the terminal knows that the father node is disconnected after a period of time and still cannot obtain the reply.
Step S102, if the first father node is disconnected, the ZigBee terminal node executes a reconnection process according to a preset reconnection upper limit number, and whether reconnection is successful is analyzed;
if the ZigBee terminal node detects that the father node is disconnected, the ZigBee terminal node tries to reestablish network connection with the original father node according to the set reconnection upper limit times, and meanwhile, whether the connection with the father node is successfully reestablished is analyzed.
Step S103, if the ZigBee terminal node is failed to reconnect, the ZigBee terminal node clears the network information, monitors a channel and executes a new network adding process;
and if the ZigBee terminal node is not connected with the original father node after being reconnected according to the set reconnection upper limit times, removing the original network information, monitoring the channel and executing a new network adding process.
Step S104, the ZigBee terminal node detects a second father node meeting the requirement in the channel according to the preset network access upper limit times, and a new network is added;
after a new network adding process is executed by the ZigBee terminal node, a parent node meeting the requirements in a channel is detected according to the preset network access upper limit times, and connection is reestablished.
S105, if the ZigBee terminal node is added into a new network before the network access upper limit times, storing network information; otherwise, monitoring the channel again after the preset delay time, detecting a third father node meeting the requirement, and joining the network again.
And if the ZigBee terminal node does not reach the network access upper limit times, successfully adding a new network, and then storing the network information. Otherwise, the low-power consumption sleep state is entered according to the set delay time, the channel is monitored after the delay time is over, and the father node meeting the requirement is searched.
Please refer to fig. 2, which is a schematic flow chart illustrating an implementation manner of a ZigBee terminal node network management method according to an embodiment of the present application.
In order to more clearly understand the ZigBee terminal node network management method provided by the present application, the present application provides the following embodiments for detailed description.
Step one, defining time T1 and T2 (unit minute or second), counting variables N1 and N2 (initial value is 0), constants MAX1 and MAX2, and defining a delay event E1 which has the function of rejoining (reconnecting) the network and a delay event E2 which joins the new network, wherein the delay time is T1 and T2 respectively. The meaning of a delay event, an event executed with a delay of a period of time. The meaning of network rejoining (reconnection) is that after a node joins the network for the first time, all network parameters are memorized and stored in a power-down mode, if the network parameters are not cleared, the node rejoins the network, namely, the node can only join the network which stores the network data before, and meanwhile, the power consumption is low when the network entering steps such as channel scanning, key transmission, network address distribution, network parameter transmission and the like are omitted. The meaning of adding a new network is to remove the network information stored before, and the power consumption required for scanning the new network to obtain a complete network access process of the network parameters is relatively large.
Step two, the coordinator 1 firstly establishes a star network, network nodes comprise the coordinator 1 (father nodes) and a series of terminals (ZigBee terminal nodes), the coordinator 1 is powered off abnormally or is off line due to other reasons, the terminal nodes cannot detect qualified father nodes, and the terminal nodes feed back the state that whether the network exists or not (the network exists means that stored network information exists).
And step three, judging the value of N1, if the value of the variable N1 is less than MAX1, executing step four, and entering a flow of rejoining the stored network. If the value of the variable N1 is greater than or equal to MAX1 (not equal to 0), step seven is executed, and the saved network rejoin times out and is ready to enter a new network joining flow. If MAX1 equals 0, then step twelve is performed and the network auto-recovery flow is not open.
And step four, starting a delay event E1, and after T1 time, executing the action of rejoining the network by the terminal node, and automatically adding 1 to the variable N1 when MAX1 is not equal to 0 xFFFF. If the coordinator 1 is powered on again and is on line again, the terminal node can detect the qualified father node, if the network parameters are stored, the network is directly on line, and the network state is switched to the network. If the coordinator 1 still does not recover, the terminal does not detect a qualified father node, and the network state is still whether a network exists or not.
And step five, judging whether the network is recovered successfully, if the coordinator 1 is not on line, the recovery fails and the step three is skipped, and if the coordinator 1 is on line, the network is recovered successfully, and the step six is executed.
And sixthly, successfully restoring the terminal node network, and carrying out zero clearing operation on the variables N1 and N2.
And seventhly, if the MAX2 is not equal to 0, clearing the stored coordinator 1 network information, switching the network state to a non-network state, and executing the step eight to enter a new network adding process. If MAX2 equals 0, then the flow to join the new network is not entered for step twelve.
And step eight, judging the value of N2, executing step nine if the value of the variable N2 is less than MAX2, executing step twelve if the value of N2 is greater than or equal to MAX2, and automatically recovering the timeout of the network.
And step nine, starting a delay event E2, and after the time T2 elapses, the terminal node executes the action of adding a new network, and automatically adding 1 to the variable N2 when the MAX2 is not equal to 0 xFFFF. If the coordinator 1 is powered on and comes online again (the coordinator 1 network comes online, at this time, the network information stored in the terminal is cleared, so the terminal considers that the terminal is also a new network) or the coordinator 2 creates a new network, the terminal node can detect a qualified father node and join a new network, and the network state is switched to the network online. And if the terminal does not detect the qualified father node, the network state is still network-free.
Step ten, judging whether the new network is successfully added, if no coordinator fails to be added into the network, jumping back to the step eight, and if the coordinator is successfully added into the network, executing the step eleven.
And step eleven, adding a new network into the terminal node, and performing zero clearing operation on the variable N1N 2.
Step twelve, the terminal node does not open the network automatic recovery flow, or the network recovery overtime is caused by no detection of the qualified father node online in the network recovery flow, the network automatic recovery fails, and the variables N1 and N2 are cleared.
Please refer to fig. 3, fig. 3 is a schematic diagram of a topology structure of a ZigBee terminal node network management system according to an embodiment of the present application.
The ZigBee terminal node network management system 10 provided in the embodiment of the present application includes: a plurality of ZigBee terminal nodes 200; a plurality of parent nodes 100 correspondingly connected to the respective ZigBee terminal nodes 200; the ZigBee terminal node 200 saves network information after joining a father node 100 network, monitors the father node 100 and analyzes whether the father node 100 is disconnected; if the father node 100 is disconnected, the ZigBee terminal node 200 executes a reconnection process according to a preset reconnection upper limit number, and analyzes whether reconnection is successful; if the ZigBee terminal node 200 fails to reconnect, the ZigBee terminal node 200 clears network information, monitors a channel and executes a new network adding process; the ZigBee terminal node 200 detects another father node 100 meeting the requirements in the channel according to the preset network access upper limit times, and adds a new network; if the ZigBee terminal node 200 is added into a new network before the network is accessed for the upper limit times, storing network information; otherwise, monitoring the channel again after the preset delay time, detecting the father node 100 meeting the requirement, and adding a new network.
The ZigBee terminal node network management system 10 provided in the embodiment of the present application further includes a sink node 300 connected to each parent node 100; a control terminal 400 connected with the sink node 300; the sink node 300 detects whether the father node 100 is reconnected within a preset online time period after the father node 100 is disconnected; if the father node 100 is not reconnected within a preset online time period, the sink node 300 sends alarm information to the control terminal 400; the staff who is convenient for control terminal 400 overhauls in time.
In summary, the embodiments of the present application provide a ZigBee terminal node network management method and system, including that a ZigBee terminal node joins a first father node network, stores network information, monitors the first father node, and analyzes whether the first father node is disconnected; if the first father node is disconnected, the ZigBee terminal node executes a reconnection process according to the preset reconnection upper limit times and analyzes whether reconnection is successful or not; if the ZigBee terminal node is failed to reconnect, the ZigBee terminal node clears network information, monitors a channel and executes a new network adding process; the ZigBee terminal node detects a second father node meeting the requirement in a channel according to a preset network access upper limit number, and adds a new network; if the ZigBee terminal node is added into a new network before the network access upper limit times, storing network information; otherwise, monitoring the channel again after the preset delay time, detecting a third father node meeting the requirement, and adding a new network; the ZigBee terminal nodes can be accessed to the network in time after the ZigBee terminal nodes lose the father nodes.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (9)
1. A ZigBee terminal node network management method is characterized by comprising the following steps:
the ZigBee terminal node is added into a first father node network, then network information is stored, the first father node is monitored, and whether the first father node is disconnected or not is analyzed;
if the first father node is disconnected, the ZigBee terminal node executes a reconnection process according to a preset reconnection upper limit number, and analyzes whether reconnection is successful;
if the ZigBee terminal node is failed to reconnect, the ZigBee terminal node clears the network information, monitors a channel and executes a new network adding process;
the ZigBee terminal node detects a second father node meeting the requirement in a channel according to a preset network access upper limit number, and adds a new network;
if the ZigBee terminal node is added into a new network before the network access upper limit times, storing network information; otherwise, monitoring the channel again after the preset delay time, detecting a third father node meeting the requirement, and adding a new network.
2. The method according to claim 1, wherein if the parent node is disconnected, the ZigBee terminal node executes a reconnection procedure according to a preset reconnection upper limit number, and the step of analyzing whether reconnection is successful comprises:
executing a reconnection process according to a preset first counting variable, reconnection upper limit times and a first time delay event, accumulating the first counting variable once in the reconnection process every time of executing, and then starting the first time delay event to execute reconnection operation; meanwhile, whether the reconnection operation is successful after the reconnection operation is executed is analyzed; and stopping executing the reconnection process when the first counting variable is equal to the reconnection upper limit times.
3. The method of claim 2, further comprising:
and if the number of the ZigBee terminal nodes connected with the first father node is lower than a preset value, the reconnection upper limit number is set to be zero.
4. The method according to claim 1, wherein the ZigBee terminal node detects a parent node meeting requirements in a channel according to a preset network access upper limit number, and the step of adding a new network comprises the following steps:
executing a network access process according to a preset second counting variable, the network access upper limit times and a second time delay event, accumulating the second counting variable once when the network access process is executed once, and then starting the second time delay event to execute the network access operation; meanwhile, whether reconnection is successful after the network access operation is executed is analyzed; and stopping executing the network access process when the second counting variable is equal to the network access upper limit times.
5. The method of claim 1, further comprising:
and if the network recovery of the ZigBee terminal node fails in a preset network automatic recovery time period, ending the network recovery process.
6. The method of claim 1, further comprising:
after the first father node is disconnected, the sink node connected with the first father node detects whether the first father node is reconnected within a preset on-line time period; and if the first father node is not reconnected in the preset online time period, the sink node sends alarm information to a control terminal connected with the sink node.
7. The method of claim 1, further comprising:
and if the ZigBee terminal node fails to reconnect, the ZigBee terminal node stores the original network information and monitors the channel, and a new network adding process is executed.
8. A ZigBee terminal node network management system is characterized by comprising a plurality of ZigBee terminal nodes; a plurality of father nodes correspondingly connected with the ZigBee terminal nodes;
the ZigBee terminal node is added into a first father node network, then network information is stored, the first father node is monitored, and whether the first father node is disconnected or not is analyzed;
if the first father node is disconnected, the ZigBee terminal node executes a reconnection process according to a preset reconnection upper limit number, and analyzes whether reconnection is successful;
if the ZigBee terminal node is failed to reconnect, the ZigBee terminal node clears the network information, monitors a channel and executes a new network adding process;
the ZigBee terminal node detects a second father node meeting the requirement in a channel according to a preset network access upper limit number, and adds a new network;
if the ZigBee terminal node is added into a new network before the network access upper limit times, storing network information; otherwise, monitoring the channel again after the preset delay time, detecting a third father node meeting the requirement, and adding a new network.
9. The ZigBee terminal node network management system of claim 8, wherein: the ZigBee terminal node network management system further comprises:
a sink node connected to each of the parent nodes;
the control terminal is connected with the aggregation node;
the sink node detects whether the first father node is reconnected within a preset online time period after the first father node is disconnected; and if the first father node is not reconnected in the preset online time period, the sink node sends alarm information to the control terminal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911221700.2A CN110972163A (en) | 2019-12-03 | 2019-12-03 | ZigBee terminal node network management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911221700.2A CN110972163A (en) | 2019-12-03 | 2019-12-03 | ZigBee terminal node network management method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110972163A true CN110972163A (en) | 2020-04-07 |
Family
ID=70032728
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911221700.2A Pending CN110972163A (en) | 2019-12-03 | 2019-12-03 | ZigBee terminal node network management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110972163A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111741541A (en) * | 2020-06-10 | 2020-10-02 | 国网湖南省电力有限公司 | Frequent reconnection method and system based on wireless communication module of power distribution terminal |
| CN111757324A (en) * | 2020-06-28 | 2020-10-09 | 四川长虹电器股份有限公司 | NB-IOT equipment identity activation method |
| CN114245483A (en) * | 2021-12-23 | 2022-03-25 | 广州思德医疗科技有限公司 | Communication monitoring reconnection method and system for gastrointestinal endoscopy capsule |
| CN114827240A (en) * | 2022-06-30 | 2022-07-29 | 成都云智北斗科技有限公司 | Network disconnection reconnection method and system |
| CN115550908A (en) * | 2022-11-28 | 2022-12-30 | 成都无声讯通科技有限责任公司 | 2.4G network communication system and method based on TDMA |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102711159A (en) * | 2012-05-11 | 2012-10-03 | 中国科学院微电子研究所 | ZigBee protocol-based method and system for processing lost node |
| JP2015035807A (en) * | 2013-08-08 | 2015-02-19 | 富士通株式会社 | Multi-hop network failure detection method and node |
| CN106255134A (en) * | 2016-08-17 | 2016-12-21 | 惠州市物联微电子有限公司 | Tree topology Wireless ad hoc networks address distribution method |
| CN107148027A (en) * | 2017-06-20 | 2017-09-08 | 钟小磊 | Solve the method and device of ZigBee internetwork communications |
-
2019
- 2019-12-03 CN CN201911221700.2A patent/CN110972163A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102711159A (en) * | 2012-05-11 | 2012-10-03 | 中国科学院微电子研究所 | ZigBee protocol-based method and system for processing lost node |
| JP2015035807A (en) * | 2013-08-08 | 2015-02-19 | 富士通株式会社 | Multi-hop network failure detection method and node |
| CN106255134A (en) * | 2016-08-17 | 2016-12-21 | 惠州市物联微电子有限公司 | Tree topology Wireless ad hoc networks address distribution method |
| CN107148027A (en) * | 2017-06-20 | 2017-09-08 | 钟小磊 | Solve the method and device of ZigBee internetwork communications |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111741541A (en) * | 2020-06-10 | 2020-10-02 | 国网湖南省电力有限公司 | Frequent reconnection method and system based on wireless communication module of power distribution terminal |
| CN111741541B (en) * | 2020-06-10 | 2023-11-17 | 国网湖南省电力有限公司 | Frequent reconnection method and system based on wireless communication module of power distribution terminal |
| CN111757324A (en) * | 2020-06-28 | 2020-10-09 | 四川长虹电器股份有限公司 | NB-IOT equipment identity activation method |
| CN114245483A (en) * | 2021-12-23 | 2022-03-25 | 广州思德医疗科技有限公司 | Communication monitoring reconnection method and system for gastrointestinal endoscopy capsule |
| CN114245483B (en) * | 2021-12-23 | 2023-12-12 | 广州思德医疗科技有限公司 | Communication monitoring reconnection method and system for gastroenteroscope capsule |
| CN114827240A (en) * | 2022-06-30 | 2022-07-29 | 成都云智北斗科技有限公司 | Network disconnection reconnection method and system |
| CN115550908A (en) * | 2022-11-28 | 2022-12-30 | 成都无声讯通科技有限责任公司 | 2.4G network communication system and method based on TDMA |
| CN115550908B (en) * | 2022-11-28 | 2023-04-18 | 成都无声讯通科技有限责任公司 | 2.4G network communication system and method based on TDMA |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110972163A (en) | ZigBee terminal node network management method and system | |
| CN100466536C (en) | System and method for managing protocol network failures in a cluster system | |
| CN104320311A (en) | Heartbeat detection method of SCADA distribution type platform | |
| CN109104351B (en) | Train network node and train network node monitoring method based on CANopen protocol | |
| CN105635248A (en) | Method and system for releasing TCP (Transmission Control Protocol) connection resources | |
| CN105915426B (en) | The fault recovery method and device of loop network | |
| CN105095008B (en) | A kind of distributed task scheduling fault redundance method suitable for group system | |
| EP2892274B1 (en) | Fault recovery method of operation and maintenance channel and network management terminal | |
| CN102025562A (en) | Path detection method and device | |
| CN103795554A (en) | Terminal state managing method, device and system | |
| CN114866365B (en) | Arbitration machine election method, device, intelligent equipment and computer readable storage medium | |
| CN103139818A (en) | Method, system, area of effect (AOE), always on line (AOG) and terminal of maintaining long connection in acquisition of signal (AOS) | |
| CN104980693A (en) | Media service backup method and system | |
| CN112398661B (en) | Equipment dormancy processing method and device, ioT equipment and storage medium | |
| CN103441870A (en) | Intelligent real-time seamless switching two unit standby method | |
| CN108289030B (en) | Base station fault identification processing method and device | |
| CN111935517A (en) | Awakening method and device of intelligent set top box, electronic equipment and storage medium | |
| CN102905351A (en) | Base station and energy saving method thereof | |
| CN103118387A (en) | Lightweight access point (AP) redundancy access control method of active standby mode | |
| CN101183996A (en) | Cluster information monitoring method | |
| CN103037422B (en) | Dynamic adaptive service recovery method and dynamic adaptive service recovery device for mobile ad hoc network | |
| CN104579428A (en) | PLC equipment automatic pairing method | |
| CN110493070A (en) | Suspension notification method and its application system | |
| CN106304241B (en) | Data transmission method, repeater and gateway | |
| CN113625946A (en) | Method, system and computer equipment for implementing arbitration of storage cluster |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200407 |