A Wireless Node Communication Management Method for Field Construction Monitoring

Abstract

The present invention relates to a wireless node communication management method for field construction monitoring, belonging to the field of wireless communication. The method divides the monitoring data into ordinary data and emergency data. The gateway calculates the time slice T of node i according to the communication cycle, the number of nodes, and the node serial number i , where T i consists of the ordinary data time slice T i1 of the node itself and the common time slice T i2 of the emergency data in the network, and T i determines the sequence of arrangement of T i1 and T i2 according to the parity of its serial number i; when node i monitors ordinary data, it sends the data during T i1 , and enters communication sleep at other times; when node i monitors emergency data, it sends the data by preempting a suitable common time slice for emergency data; regardless of the type of data monitored, the node has to receive the message from the gateway during the gateway time slice. The present invention improves the reliability of ordinary data transmission and the real-time performance of emergency data transmission in field construction monitoring, and at the same time extends the service life of the node.

Description

Technical Field

[0001] The present invention belongs to the field of wireless communication and relates to a wireless node communication management method for field construction monitoring. Background Art

[0002] Monitoring field construction is a necessary means to ensure the efficiency and safety of field construction. However, how to reliably transmit the data monitored in field construction is a problem that needs to be solved. Generally, the transmission of field construction operation data has low requirements for transmission rate, but requires a long transmission distance and high communication reliability. Based on this characteristic, wireless communication is often used in real-time monitoring of field construction. In traditional wireless communication, monitoring nodes actively initiate data communication with the gateway in a random manner. Since all nodes send information to the gateway randomly and the gateway has no corresponding method to control the nodes to send data, it is very easy to cause communication failure due to interference between signals and cannot guarantee the reliability of communication. At the same time, the monitoring nodes in field construction usually use batteries for power supply, so strict requirements are imposed on the power consumption of the nodes. If the wireless communication module of the node is turned on for a long time, it will increase the power consumption of the node and shorten the service life of the node, which is not conducive to the use of field construction monitoring.

[0003] In summary, there is an urgent need for a wireless node communication management method that can simultaneously solve the problems of large interference of wireless communication signals and high power consumption in field construction monitoring. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a wireless node communication management method for field construction monitoring, so as to solve the problem of large interference of wireless communication signals in field construction monitoring, improve the reliability of ordinary data transmission and the real-time performance of emergency data transmission in field construction monitoring, and at the same time let the node enter the communication sleep state during the time slice that has nothing to do with itself, reduce the power consumption of the node and thus extend the service life of the node.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] A wireless node communication management method for field construction monitoring divides the field construction monitoring data into ordinary data and emergency data. The gateway calculates the time slice T of node i according to the communication cycle, the number of nodes and the node serial number i , where T i consists of the ordinary data time slice T of the node itself i1 and the common time slice T of the emergency data in the network i2 , and T i determines the sequence of arrangement of T i1 and T i2 according to the parity of its serial number i; when node i monitors ordinary data, it is in the time slice T i1Send data and enter communication sleep during the remaining time; when node i detects emergency data, preempt an appropriate common time slice T for emergency data a to send data, where one common time slice T for emergency data a is composed of two adjacent time slices T (i-1)2 and T i2 ; regardless of the type of data detected by the node, it must receive messages from the gateway during the gateway time slice T 01 Receive messages from the gateway

[0007] Furthermore, the method specifically includes the following steps:

[0008] S1: The node applies to join the wireless network, including:

[0009] S11: The node listens in real time for the time slice configuration message sent by the gateway and waits to join the wireless network;

[0010] S12: After receiving the time slice configuration message sent by the gateway, the node starts to periodically send an access request message to the gateway;

[0011] S13: After receiving the access request message sent by the node, the gateway sends an access confirmation message to the node;

[0012] S14: If the node receives the access confirmation request message sent by the gateway, it indicates that the network joining is successful;

[0013] S2: The gateway calculates the time slice T of node i based on the relevant information of the node i and forms a time slice configuration message, and then sends the time slice configuration message to all the nodes that have joined the network. The period for the gateway to send the time slice configuration message is T, in milliseconds;

[0014] S3: If the joined node i receives the time slice configuration message sent by the gateway, it parses the message to obtain the normal data time slice T belonging to node i i1 and the time slice T for receiving the time slice configuration message 01 , T 01 is also called the gateway time slice. If the node detects normal data, the node starts communication sleep and jumps to S4; if the node detects emergency data, it jumps to S5; where normal data refers to data from field construction monitoring that has not reached the threshold, and emergency data refers to data from field construction monitoring that has reached the threshold;

[0015] S4: When node i detects normal data, node i actively sends data to the gateway, including:

[0016] S41: Node i is awakened during its own normal data time slice T i1 ;

[0017] S42: After node i is awakened, it sends normal data to the gateway;

[0018] S43: After the sending is completed, node i enters the communication sleep state and jumps to S6;

[0019] S5: When node i detects emergency data, node i obtains the common time slice for sending emergency data in the network through the time slice configuration message, and preempts the nearest common time slice T for emergency data a to send emergency data to the gateway, and does not enter the communication sleep state during the period of detecting emergency data. The frequency of the node sending emergency data is set locally by the node. If node i has not reached time slice T 01 , then continue to loop and execute S5; if node i detects normal data during this period, then jump to S4; if node i reaches time slice T 01 , then jump to S6;

[0020] S6: When node i reaches time slice T 01 , it starts to receive the time slice configuration message and jumps to step S3. If the time slice configuration message is not received within a certain time or the time slice belonging to itself cannot be parsed from the message, then node i actively withdraws from the network and jumps to step S1.

[0021] Furthermore, in step S2, the node-related information includes the communication cycle T, the number of nodes n, and the node network access serial number i. The communication cycle is equal to the cycle of the gateway sending the time slice configuration message. The node network access serial number increases sequentially from 1 according to the node network access order. The gateway reserves serial number 0 and does not allocate it to the networked nodes. All nodes receive the time slice configuration message sent by the gateway at the time slice T corresponding to serial number 0. 01 Receive the time slice configuration message sent by the gateway.

[0022] Furthermore, in step S2, calculate the time slice T of node i i and form a time slice configuration message, including:

[0023] 1) Divide the communication cycle evenly according to the number of nodes. The calculation formula is:

[0024]

[0025] where T is the communication cycle, in milliseconds, n is the number of networked nodes, is the average length of the time slice, in milliseconds. Since it takes a certain amount of time for the node to send all the data, this time is determined by the amount of data sent by the node. Therefore, the average length of the time slice cannot be too small. Therefore, the maximum value of n (i.e., the maximum number of nodes that the gateway can manage) and the value of the communication cycle T need to be determined according to the time required for the node to send data;

[0026] 2) Allocate the normal data time slice \(T\) of node \(i\) according to the node network access sequence number i1 and the common time slice \(T\) of the emergency data in the network i2 , where \(T\) i1 and \(T\) i2 both have a length of \(T\) i Arrange \(T\) i1 and \(T\) i2 according to the parity of its sequence number \(i\). When \(i\) is even, \(T\) i1 is in the front and \(T\) i2 is in the back. When \(i\) is odd, \(T\) i2 is in the front and \(T\) i1 is in the back. Combine the time slices of all nodes into a time slice configuration message according to this arrangement rule.

[0027] Furthermore, the normal data time slice \(T\) of node \(i\) i1 is:

[0028]

[0029] where is the average length of the time slice, \(i\) is the time slice sequence number, that is, the node network access sequence number, and the length of the time slice \(T\) i1 is in milliseconds.

[0030] Furthermore, in step S3, during the process of the node receiving the time slice configuration message sent by the gateway, the node locally needs to maintain a timer, and the total timing duration is \(T\). When the timing reaches \(T\), the timer is reset to 0. When reaching the time slice \(T\) 01 later, the node starts to receive the time slice configuration message. After receiving the time slice configuration message, the timer is refreshed and reset to 0.

[0031] Furthermore, in step S5, the method of preempting the nearest emergency data time slice \(T\) a to send emergency data to the gateway. A common emergency data time slice \(T\) a is composed of two adjacent time slices \(T\) (i-1)2 and \(T\) i2 with a length of in milliseconds. The method of preempting the emergency data time slice is as follows: Node \(i\) first judges the time required to send the emergency data. If it can be sent within the time , it can preempt the common emergency data time slice \(T\) a to send the emergency data, or it can also use the normal data time slice \(T\) of node \(i\) i1 to send the emergency data. If it cannot be sent within the time , it can only preempt the common emergency data time slice \(T\) aSend emergency data. When a node needs to preempt the common time slice for emergency data, the node first sends a message for preempting the common time slice for emergency data to the gateway. If the node receives a reply message indicating successful preemption, then the preemption is successful. If the node does not receive a reply message within the specified time, it resends the message for preempting the common time slice for emergency data. If it still does not receive a reply, it jumps to the next common time slice for emergency data to perform preemption.

[0032] Furthermore, in step S6, the certain time is expressed as m×T, where m is a coefficient greater than 0 and T is the communication period.

[0033] The beneficial effects of the present invention are as follows: By allocating time slices for data transmission to the nodes that have joined the network, the present invention can effectively solve the problem of mutual interference when wireless communication nodes send data to the gateway, and improve the reliability of communication between the nodes and the gateway. At the same time, it allows the nodes to enter the communication sleep state during the time slices that are not related to themselves, reduces the power consumption of the nodes, and thus extends the service life of the nodes. At the same time, according to the different states of the monitored objects, the data monitored by the nodes is divided into ordinary data and emergency data, and they are sent in different time slices, which ensures the real-time transmission of emergency data while managing the data transmission of the nodes.

[0034] Other advantages, objectives and features of the present invention will be described to some extent in the subsequent specification, and to some extent, will be obvious to those skilled in the art based on the study of the following text, or can be taught from the practice of the present invention. The objectives and other advantages of the present invention can be realized and obtained through the following specification. Brief Description of the Drawings

[0035] In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be described in detail preferably with reference to the accompanying drawings, where:

[0036] Figure 1 Schematic diagram of the time slice allocated for the gateway;

[0037] Figure 2 Flowchart of the wireless node communication management method for field construction monitoring of the present invention. Detailed Embodiments

[0038] The following describes the implementation manners of the present invention through specific examples. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific implementation manners. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the diagrams provided in the following embodiments only illustrate the basic concept of the present invention in a schematic manner. Without conflict, the following embodiments and the features in the embodiments can be combined with each other.

[0039] Please refer to Figures 1 to 2 , this embodiment provides a wireless node communication management method for field construction monitoring. As Figure 2 shown, it specifically includes the following steps:

[0040] S1: The node applies to join the wireless network and starts waiting to receive the time slice configuration message from the gateway. After receiving it, it immediately sends an access request message to the gateway. After the gateway receives the access request message, it replies with a confirmation access message to the node. If the node receives the confirmation access message sent by the gateway, it indicates that the node has successfully accessed the network and starts waiting for the gateway to allocate a time slice.

[0041] S2: The gateway calculates the time slice T i of node i according to the node-related information, and forms a time slice configuration message, and then sends the time slice configuration message to all the nodes that have accessed the network. The time slice configuration method is as Figure 1 shown. The gateway allocates a time slice for each node that has accessed the network and arranges them in order in the time slice configuration message. The size of the entire cycle is T, and the average time slice length is time slice T 01 for the node to receive the time slice configuration message, time slice T i1 for node i to send its own normal data, time slice T i2 is the common time slice for sending emergency data in the network. One emergency data common time slice T a sends emergency data in a preemptive manner by adjacent nodes. Among them, the calculation method of time slice T i is as follows:

[0042] 1) Calculate the average time slice length The calculation formula is:

[0043]

[0044] Among them, T is the communication cycle, with the unit of millisecond; n is the number of nodes that have accessed the network; is the average time slice length, with the unit of millisecond; Since it takes a certain amount of time for the node to send all the data, this time is determined by the amount of data sent by the node. Therefore, the average time slice length It cannot be too small. Therefore, the maximum value of n (i.e., the maximum number of nodes that the gateway can manage) and the value of the communication cycle T need to be determined according to the time required for the nodes to send data.

[0045] 2) Allocate the normal data time slice T of node i according to the node access sequence number i1 and the common emergency data time slice T i2 , where T i1 and T i2 are both of length T i Arrange T i1 and T i2 according to the parity of its sequence number i. When i is even, T i1 is in the front and T i2 is in the back. When i is odd, T i2 is in the front and T i1 is in the back. Combine the time slices of all nodes into a time slice configuration message according to this arrangement rule. For the setting of the node access sequence number, the gateway increments the node access sequence number from 1 in the order of node access, and the gateway reserves the sequence number 0 and does not assign it to the accessed nodes. All nodes receive the time slice configuration message sent by the gateway in the time slice T 01 corresponding to the sequence number 0.

[0046] S3: If the accessed node i receives the time slice configuration message sent by the gateway, then parse the message to obtain the normal data time slice T i1 belonging to node i and the time slice T 01 for receiving the time slice configuration message. The arrangement of the time slices T i1 and T 01 is as shown in Figure 1 . If the node monitors normal data, the node starts communication sleep and jumps to S4. If the node monitors emergency data, it jumps to S5. Among them, normal data refers to data that has not reached the threshold in field construction monitoring, and emergency data refers to data that has reached the threshold in field construction monitoring. The normal data time slice T i1 of node i can be calculated by the following formula:

[0047]

[0048] where, is the average length of the time slice, and i is the time slice sequence number (i.e., the node access sequence number); the length of the time slice T i1 is in milliseconds.

[0049] S4: If the data monitored by a node is ordinary data, the node is woken up during its own time slice. After being woken up, it immediately sends the data packet to be sent to the gateway. After sending is completed, it enters the communication sleep state again and waits for the gateway time slice to arrive.

[0050] S5: When node i monitors emergency data, node i obtains the common time slice for sending emergency data in the network through the time slice configuration message and preempts the nearest common time slice T for emergency data. a Send the emergency data to the gateway, T a The arrangement of which is as Figure 1 shown, and communication sleep is not performed during the period of monitoring emergency data. The frequency of a node sending emergency data is set locally by the node. If node i has not reached time slice T 01 , then continue to loop and execute S5. If ordinary data is monitored by node i during this period, then jump to S4. If node i reaches time slice T 01 , then jump to S6.

[0051] The method for preempting the emergency data time slice is as follows: Node i first judges the time required to send the emergency data. If it can be sent within the time , then it can preempt the common time slice T for emergency data to a send the emergency data, or it can also use the ordinary data time slice T of node i i1 to send the emergency data. If it cannot be sent within the time , then it can only preempt the common time slice T for emergency data to a send the emergency data. When a node needs to preempt the common time slice for emergency data, the node first sends a message for preempting the common time slice for emergency data to the gateway. If the node receives a successful preemption reply message, then the preemption is successful. If the node does not receive a reply message within the specified time, then it resends the message for preempting the common time slice for emergency data. If it still does not receive a reply, then jump to the next common time slice for emergency data for preemption.

[0052] S6: After node i reaches time slice T 01 , it starts to receive the time slice configuration message and jumps to step S3. If the time slice configuration message is not received within a certain time or the time slice belonging to itself cannot be parsed from the message, then node i takes the initiative to withdraw from the network and jumps to step S1.

[0053] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the purpose and scope of the present technical solution, and they should all be covered within the scope of the claims of the present invention.

Claims

1. A wireless node communication management method for field construction monitoring, characterized in that, This method classifies the field construction monitoring data into ordinary data and emergency data. The gateway calculates the time slice T of node i according to the communication cycle, the number of nodes, and the node serial number. i , where T i consists of the ordinary data time slice T i1 of the node itself and the common time slice T i2 of the emergency data in the network, and T i determines the order of arrangement of T i1 and T i2 according to the parity of its serial number i; when node i monitors ordinary data, it sends the data in the time slice T i1 and enters communication sleep at other times. When node i detects emergency data, it preempts a suitable common time slice T for emergency data a to send data, where a common time slice T for emergency data a is composed of two adjacent time slices T (i-1)2 and T i2 ; regardless of the type of data detected, the node must receive messages from the gateway during the gateway time slice T 01 ; The method specifically includes the following steps: S1: A node applies to join the wireless network, including: S11: The node listens in real time for the time slice configuration message sent by the gateway and waits to join the wireless network; S12: After receiving the time slice configuration message sent by the gateway, the node starts to periodically send an access request message to the gateway; S13: After receiving the access request message sent by the node, the gateway sends an access confirmation message to the node; S14: If the node receives the access confirmation request message sent by the gateway, it indicates that the network joining is successful; S2: The gateway calculates the time slice \(T\) of node \(i\) according to the node-related information i and forms a time slice configuration message, and then sends the time slice configuration message to all the nodes that have joined the network. The period for the gateway to send the time slice configuration message is \(T\); The node-related information includes the communication period T, the number of nodes n, and the node network access sequence number i. The communication period is equal to the period of the gateway sending the time slice configuration message. The node network access sequence number increases sequentially from 1 according to the node network access order. The gateway reserves the sequence number 0 and does not allocate it to the nodes accessing the network. All nodes are in the time slice T corresponding to the sequence number 0 01 Receive the time slice configuration message sent by the gateway; Time slice T of computing node i i And form a time slice configuration message, including: 1) Divide the communication cycle evenly according to the number of nodes. The calculation formula is: Among them, is the average length of a time slice, T is the communication period, n is the number of nodes that have joined the network. The maximum value of n and the value of the communication period T need to be determined according to the time required for a node to send data once; 2) Allocate the normal data time slice T of node i according to the node network access sequence number i1 and the common time slice T of the emergency data in the network i2 , where the lengths of T i1 and T i2 are both , and T i is arranged with T i1 and T i2 according to the parity of its sequence number i. When i is even, T i1 is in the front and T i2 is in the back. When i is odd, T i2 is in the front and T i1 is in the back. And the time slices of all nodes are combined into a time slice configuration message according to this arrangement rule; The normal data time slice T of node i i1 is as follows: Among them, is the average length of the time slice, i is the time slice serial number, that is, the node access network serial number, and the time slice T i1 has a length of ; S3: If the networked node i receives the time slice configuration message sent by the gateway, parse the message to obtain the normal data time slice T belonging to node i i1 and the time slice T for receiving the time slice configuration message 01 , T 01 which is also called the gateway time slice. If the node detects normal data, the node starts communication sleep and jumps to S4; if the node detects emergency data, it jumps to S5; where normal data refers to data that has not reached the threshold in field construction monitoring, and emergency data refers to data that has reached the threshold in field construction monitoring; S4: When node i detects ordinary data, node i actively sends data to the gateway, including: S41: Node i is woken up during its own normal data time slice T i1 and S42: After being awakened, node i sends ordinary data to the gateway; S43: After the sending is completed, node i enters the communication sleep state and jumps to S6; S5: When the emergency data is detected at node i, node i obtains the common time slice for sending emergency data in the network through the time slice configuration message, and preempts the nearest common time slice T of the emergency data. a Send the emergency data to the gateway, and do not enter the communication sleep mode during the detection of the emergency data. The frequency of sending the emergency data by the node is set locally by the node. If node i has not reached the time slice T 01 , then continue to loop and execute S5; if the ordinary data is detected at node i during this period, then jump to S4; if node i reaches the time slice T 01 , then jump to S6; The preempted nearest emergency data time slice T a Send emergency data to the gateway, with a common time slice T for emergency data a Consisting of two adjacent time slices T (i-1)2 and T i2 The length is , where the method for preempting the emergency data time slice is as follows: Node i first judges the time required to send the emergency data. If it can be sent within the time , then preempt the common time slice T for emergency data a to send the emergency data, or use the ordinary data time slice T of node i i1 to send the emergency data; if it cannot be sent within the time , then only preempt the common time slice T for emergency data a to send the emergency data. When a node needs to preempt the common time slice for emergency data, the node first sends a message to the gateway to preempt the common time slice for emergency data. If the node receives a successful preemption reply message, the preemption is successful; if the node does not receive a reply message within the specified time, it resends the message to preempt the common time slice for emergency data. If it still does not receive a reply, it jumps to the next common time slice for emergency data to preempt; S6: Node i reaches time slice T 01 After that, it starts to receive the time slice configuration message and jumps to step S3. If it does not receive the time slice configuration message or fails to parse its own time slice from the message within a certain period of time, node i actively withdraws from the network and jumps to step S1.

2. The wireless node communication management method according to claim 1, characterized in that, In step S3, during the process of a node receiving a time slice configuration message sent by a gateway, the node locally maintains a timer with a total timing duration of T. When the timing reaches T, the timer is reset to 0. When the time slice T 01 has passed, the node starts to receive the time slice configuration message. After receiving the time slice configuration message, the timer is refreshed and reset to 0.

3. The wireless node communication management method according to claim 1, wherein In step S6, the certain time is expressed as , where m is a coefficient greater than 0 and T is a communication period.

Images