A low-power LoRa communication system, method, gateway and node terminal

Abstract

The embodiment of the present application provides a low-power LoRa communication system, method, gateway and node terminal, and relates to the technical field of Internet of Things communication. The LoRa communication system comprises a LoRa gateway and a LoRa node terminal. The LoRa gateway is used for constructing a wake-up instruction according to whether the LoRa node terminal needs to communicate after receiving a batch node communication instruction. The LoRa node terminal is used for receiving the wake-up instruction and judging whether the LoRa node terminal needs to communicate according to the wake-up instruction. When it is judged that the LoRa node terminal does not need to communicate, the LoRa node terminal directly enters a sleep state. When it is judged that the LoRa node terminal needs to communicate, the LoRa node terminal calculates a communication window time of the LoRa node terminal according to the wake-up instruction and sleeps according to the communication window time. The LoRa gateway is also used for sequentially sending communication data not containing a long preamble according to the batch node communication instruction. The LoRa node terminal is also used for waking up at the latest communication window time and entering a receiving state to receive the communication data.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) communication technology, and more specifically, to a low-power LoRa communication system, method, gateway, and node terminal. Background Technology

[0002] LoRa technology is currently widely used in low-power IoT applications, with low-power technology being of paramount importance in battery-powered nodes. LoRa consumes significant power when sending and receiving data, so it should remain in sleep mode as much as possible in low-power scenarios. If a node in sleep mode needs to receive data from a gateway, it must first be woken up over the air to enable data communication.

[0003] The wake-up process is as follows: The LoRa chip (i.e., the node) periodically enables CAD detection. Before sending data, the gateway adds a long preamble of not less than the period. When the node enables CAD detection, if it detects the long preamble, it will wake up and receive subsequent data.

[0004] In existing technologies, when communication with a batch of nodes is required, the gateway sends data in a certain order to wake up the terminals and initiate communication. During this process, every time a connection is established, all nodes connected to the gateway are woken up and must determine whether the data sent by the gateway is intended for them, significantly increasing the nodes' energy consumption.

[0005] In view of this, the applicant hereby submits this application after studying the existing technology. Summary of the Invention

[0006] The present invention provides a low-power LoRa communication system, method, gateway, and node terminal to improve at least one of the above-mentioned technical problems.

[0007] In a first aspect, embodiments of the present invention provide a low-power LoRa communication system, comprising a LoRa gateway and a LoRa node terminal. The LoRa node terminal and the LoRa gateway are communicatively connected.

[0008] The LoRa gateway is used to execute step S1. S1: After receiving the batch node communication command, a wake-up command is constructed based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air waking of the LoRa node terminal.

[0009] The LoRa node terminal is used to execute step A1. A1: Receive the wake-up command and determine whether it needs to communicate based on the wake-up command. If it determines that it does not need to communicate, it directly enters a sleep state. If it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode based on the communication window time.

[0010] The LoRa gateway is also used to execute step S2. S2: According to the batch node communication instructions, communication data without long preambles is sent sequentially.

[0011] The LoRa node terminal is also used to execute step A2. A2: Wake up and enter the receiving state no later than the communication window time to receive communication data.

[0012] Secondly, embodiments of the present invention provide a low-power LoRa gateway, comprising:

[0013] The LoRa gateway is used to execute step S1. S1: After receiving the batch node communication command, a wake-up command is constructed based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air wake-up of the LoRa node terminal. The wake-up command is received by the LoRa node terminal, and the LoRa node terminal can determine whether it needs to communicate based on the wake-up command. When it determines that it does not need to communicate, it directly enters a sleep state. When it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode according to the communication window time.

[0014] The LoRa gateway is also used to execute step S2. S2: According to the batch node communication instructions, communication data without a long preamble is sent sequentially. This communication data is intended to be received by the LoRa node terminal that is woken up and enters the receiving state no later than the communication window time.

[0015] Thirdly, embodiments of the present invention provide a low-power LoRa node terminal, comprising:

[0016] The LoRa node terminal is used to execute step A1. A1: Receive a wake-up command and determine whether it needs to communicate based on the wake-up command. If it determines that it does not need to communicate, it directly enters a sleep state. If it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode based on the communication window time. The wake-up command is constructed by the LoRa gateway after receiving batch node communication commands, based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air waking of the LoRa node terminal.

[0017] The LoRa node terminal is also used to execute step A2. A2: Wake up and enter the receiving state no later than the communication window time to receive communication data. The communication data does not contain a long preamble and is sent sequentially by the LoRa gateway according to the batch node communication instructions.

[0018] Fourthly, embodiments of the present invention provide a low-power LoRa communication method, which includes steps S1, A1, S2 and A2.

[0019] S1. Upon receiving the batch node communication command, construct a wake-up command based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air waking of the LoRa node terminal.

[0020] A1. Receive the wake-up command and determine whether it needs to communicate based on the wake-up command. If it determines that it does not need to communicate, it directly enters a sleep state. If it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode based on the communication window time.

[0021] S2. According to the batch node communication instructions, send communication data without long preambles in sequence.

[0022] A2. Wake up and enter the receiving state no later than the communication window time to receive communication data.

[0023] By adopting the above technical solution, the present invention can achieve the following technical effects:

[0024] When the low-power LoRa communication system of this invention needs to communicate with a batch of nodes, it only needs to wake up all nodes at once. Then, the nodes calculate an approximate communication time window based on the wake-up packet, enter a sleep state during the waiting period, and start receiving data when the time window is about to expire. This greatly reduces the number of times LoRa node terminals are woken up and significantly reduces node power consumption.

[0025] Furthermore, long preambles are no longer sent during communication with nodes, which shortens the data length compared to existing technologies that send long preambles every time. This effectively shortens the communication time, thereby improving the performance of the system's communication data volume, reducing node power consumption, improving product battery life, and saving energy. Attached Figure Description

[0026] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a communication logic block diagram of the LoRa communication system.

[0028] Figure 2 This is a schematic diagram of the star network topology of the LoRa communication system.

[0029] Figure 3 This is a CAD detection wake-up current diagram between the LoRa gateway and the LoRa node terminal.

[0030] Figure 4 This is a batch wake-up communication current diagram of the LoRa communication system.

[0031] Figure 5 This is a flowchart of the low-power LoRa communication method. Detailed Implementation

[0032] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0033] Example 1, please refer to Figures 1 to 4 The first embodiment of the present invention provides a low-power LoRa communication system. The LoRa communication system includes a LoRa gateway and a LoRa node terminal. The LoRa node terminal and the LoRa gateway are communicatively connected. Preferably, as follows... Figure 2 As shown, the LoRa communication system is a star network, comprising at least one LoRa gateway and at least two LoRa node terminals. The LoRa node terminals are capable of periodically activating channel activity detection to support over-the-air wake-up.

[0034] Specifically, a LoRa communication system can include a small number of gateways, a large number of nodes, and a network server. The nodes are low-power battery-powered products and periodically activate CAD detection to support over-the-air wake-up. The LoRa communication system of this embodiment can adopt other topologies, and this invention does not specifically limit it.

[0035] If the server needs to actively notify the nodes, it must first wake the nodes up over the air and establish communication. When a gateway needs to communicate with multiple nodes, batch communication is often required, and the communication content for each node may differ. Therefore, it cannot be broadcast all at once; individual communication with each node is necessary. However, each gateway is associated with a batch of nodes with identical communication parameters (channel, rate, etc.). When the gateway wakes up with a long preamble, all nodes are awakened, resulting in high power consumption. Therefore, to ensure low power consumption, the number of wake-ups should be minimized, keeping nodes in a sleep state as much as possible.

[0036] Preferably, during the deployment of the LoRa communication system, the gateway assigns addresses to nodes sequentially. When calculating the address mask, the gateway assigns one bit to each node's address in the address mask; a value of 0 indicates no communication is needed, and a value of 1 indicates communication is required.

[0037] Figure 2 This diagram illustrates the current characteristics of the gateway and node in LoRa's commonly used Wake-up-in-the-Air (WAIR) technology. The node is mostly in sleep mode, only periodically activating LoRa Channel Activity Detection (CAD detection) to check for the presence of a long preamble in the air. When the gateway needs to send data to the node, it adds a long preamble, at least equal to the node's CAD period, to the data to ensure the node can detect it. Once the node detects the long preamble after activating CAD, it continues receiving data until reception is complete, thus achieving WAIR and data reception.

[0038] The LoRa gateway is used to execute step S1. S1: After receiving the batch node communication command, a wake-up command is constructed based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air waking of the LoRa node terminal. Preferably, step S1 specifically includes steps S11 and S12.

[0039] S11. Upon receiving the batch node communication command, calculate the address mask based on whether the LoRa node terminal needs to communicate and the address of the LoRa node terminal. The addresses of the LoRa node terminals are allocated sequentially during the deployment of the communication system.

[0040] S12. Construct the wake-up command based on the address mask and the long preamble used to wake up the LoRa node terminal over the air.

[0041] Specifically, when the server needs to actively notify the nodes of instructions, it first sends a batch of instructions to the gateway via the network. After receiving the server's instructions, the gateway calculates the address mask.

[0042] For simplicity, this example uses a gateway bound to 8 nodes. In practical applications, the number of nodes can be increased by adding bytes. In a gateway bound to 8 nodes, if communication with nodes 1, 3, and 4 is required, the address mask is 0b00001101, or 0x0D. The address mask 0x0D is added to the wake-up packet, allowing the nodes to determine the order in which they receive data and thus calculate the approximate time of data reception. Since a long preamble is no longer sent during communication, the data length is reduced, thus reducing communication time. While ensuring successful communication, this not only reduces energy consumption but also significantly improves communication efficiency.

[0043] The LoRa node terminal is used to execute step A1. A1: Receive the wake-up command and determine whether it needs to communicate based on the wake-up command. When it determines that it does not need to communicate, it directly enters a sleep state. When it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode based on the communication window time. Preferably, step A1 specifically includes steps A11 to A16.

[0044] A11. Periodically perform CAD channel activity detection to continue receiving the wake-up command when a long preamble is detected.

[0045] A12. Determine whether you need to communicate based on the address mask in the wake-up command.

[0046] A13. When it determines that it does not need to communicate, it enters hibernation.

[0047] A14. When it is determined that it needs to communicate, calculate the communication sequence number based on the address mask.

[0048] A15. Calculate the communication window time based on the communication data transmission interval, the minimum communication duration, and the communication sequence number. Where ts = index * (t + sendInterval), where ts is the communication window time, index is the communication sequence number, t is the minimum communication duration, and sendInterval is the communication data transmission interval.

[0049] A16. Set a timer based on the communication window time and the early wake-up time difference, and enter sleep mode.

[0050] Specifically, such as Figure 4 As shown, nodes periodically perform CAD checks. When a long preamble is detected, the node continues to receive and parse the wake-up packet. The node uses the address mask in the wake-up packet to determine whether it needs to open a receiving window to receive data. If no data needs to be received, the node enters sleep mode (e.g., node 2), and will not be falsely woken up since the gateway will not send long preambles afterward. If data needs to be received, the node calculates the communication sequence number index using the address mask (e.g., index = 0 for node 1, index = 1 for node 3), and then calculates the communication window time ts = index * (t + sendInterval) by combining the minimum communication duration t for each data item and the interval sent by the gateway to the node. After calculation, the node sets a timer based on the communication window time and the early wake-up time difference and enters sleep mode.

[0051] Based on the above embodiments, in an optional embodiment of the present invention, the wake-up instruction further includes a minimum data length. Step A14 is specifically used for: when it is determined that communication is required, calculating a communication sequence number based on the address mask, and calculating the minimum communication duration for receiving the communication data based on the minimum data length.

[0052] Specifically, by incorporating a minimum data length `len` into the wake-up packet, nodes can more accurately calculate the minimum communication duration `t` for each data segment. This not only ensures that all nodes receive the data but also allows gateways and nodes to transmit data of varying lengths based on the different communication data, further improving the accuracy of the node's communication window time calculation and reducing node power consumption, which has significant practical implications. Preferably, in other embodiments, the minimum data length `len` can be set to a default value and does not need to be included in the wake-up packet every time.

[0053] The LoRa gateway is also used to execute step S2. S2: According to the batch node communication instructions, communication data without long preambles is sent sequentially. Preferably, step S2 is specifically used to: according to the batch node communication instructions, send communication data without long preambles in the address order of the LoRa node terminals.

[0054] Specifically, the communication data includes a short preamble used to identify the data packet information. The short preamble contains information such as the recipient of the communication data and the start position of the data content. It should be noted that short preambles generally do not have the function of waking up node terminals, while long preambles do. Long preambles have longer data, resulting in a longer reception time and requiring more power consumption during reception.

[0055] The LoRa node terminal is also used to execute step A2. A2: Wake up and enter the receiving state no later than the communication window time to receive communication data. Preferably, step A2 specifically includes steps A21 to A25.

[0056] A21. Wake up and enter the receiving state no later than the communication window time to receive communication data.

[0057] A22. When receiving communication data, determine whether the received communication data was sent to itself.

[0058] A23. When the received communication data is data sent to itself, it will enter sleep mode after processing the data.

[0059] A24. If the received data is not the data sent to itself, then continue receiving data.

[0060] A25. If no data is received within the preset time, it is determined that the reception has timed out and enters sleep mode.

[0061] Specifically, a node is woken up by a timer before the communication window opens and enters the receiving state. If no data is received from the gateway within the timeout period, it enters sleep mode (to prevent infinite waiting). Upon receiving data, it further determines whether it is its own data. If so, it processes the data and enters sleep mode. If not, it continues to receive data until the timeout expires and it enters sleep mode again, or it receives its own data.

[0062] The possibility of receiving data from other nodes arises because the communication duration of each node may vary, making it impossible to accurately calculate the wake-up time for each node. To ensure that nodes receive downlink data, the minimum communication time is used for calculation. This means there is a possibility of premature wake-up and erroneous reception of data from other nodes. The node simply needs to filter the data and continue receiving. Since long preambles are no longer sent during communication, the process can be completed in a shorter time, improving communication efficiency and significantly reducing node power consumption.

[0063] This invention combines and optimizes common LoRa over-the-air wake-up technology to achieve low-power batch wake-up communication. For example... Figure 4 As shown, when the gateway needs to send batch data (to communicate with nodes 1, 3, and 4), it first sends a batch wake-up packet (containing a long preamble) to wake up all nodes. Upon receiving the packet, a node determines that it does not need to communicate with itself and enters sleep mode (node ​​2). Otherwise, it calculates the receiving window and remains in sleep mode until it enters receiving mode before the receiving window opens (nodes 1, 3, and 4). The gateway does not send the long preamble during data communication with the nodes, thus speeding up communication and preventing accidental wake-up of other sleep nodes.

[0064] Specifically, the low-power LoRa communication system of this invention, when needing to communicate with a batch of nodes, only requires waking up all nodes at once. The nodes calculate an approximate communication time window based on the wake-up packet, enter a sleep state during the waiting period, and activate the receiving state to complete data reception just before the time window expires. This significantly reduces the number of times LoRa node terminals are woken up, greatly reducing node power consumption. Furthermore, long preambles are no longer sent during communication with nodes, shortening the data length compared to existing technologies that send long preambles every time, effectively reducing communication time, thereby improving the system's communication data volume performance, reducing node power consumption, extending product battery life, and saving energy.

[0065] Example 2: This embodiment of the invention provides a low-power LoRa gateway.

[0066] The LoRa gateway is used to execute step S1. S1: After receiving the batch node communication command, a wake-up command is constructed based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air wake-up of the LoRa node terminal. The wake-up command is received by the LoRa node terminal, and the LoRa node terminal can determine whether it needs to communicate based on the wake-up command. When it determines that it does not need to communicate, it directly enters a sleep state. When it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode according to the communication window time.

[0067] The LoRa gateway is also used to execute step S2. S2: According to the batch node communication instructions, communication data without a long preamble is sent sequentially. This communication data is intended to be received by the LoRa node terminal that is woken up and enters the receiving state no later than the communication window time.

[0068] Specifically, the gateway no longer sends long preambles when communicating with nodes, thus completing data communication with nodes more quickly. Furthermore, during this process, there is only one wake-up, and the nodes remain in sleep mode for most of the time, significantly shortening the overall communication time and enabling batch wake-up communication under low power conditions.

[0069] Example 3: This embodiment of the invention provides a low-power LoRa node terminal.

[0070] The LoRa node terminal is used to execute step A1. A1: Receive a wake-up command and determine whether it needs to communicate based on the wake-up command. If it determines that it does not need to communicate, it directly enters a sleep state. If it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode based on the communication window time. The wake-up command is constructed by the LoRa gateway after receiving batch node communication commands, based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air waking of the LoRa node terminal.

[0071] The LoRa node terminal is also used to execute step A2. A2: Wake up and enter the receiving state no later than the communication window time to receive communication data. The communication data does not contain a long preamble and is sent sequentially by the LoRa gateway according to the batch node communication instructions.

[0072] Example 4, please refer to Figure 5 This invention provides a low-power LoRa communication method, which includes steps S1, A1, S2 and A2.

[0073] S1. Upon receiving the batch node communication command, construct a wake-up command based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air waking of the LoRa node terminal.

[0074] A1. Receive the wake-up command and determine whether it needs to communicate based on the wake-up command. If it determines that it does not need to communicate, it directly enters a sleep state. If it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode based on the communication window time.

[0075] S2. According to the batch node communication instructions, send communication data without long preambles in sequence.

[0076] A2. Wake up and enter the receiving state no later than the communication window time to receive communication data.

[0077] Specifically, the low-power LoRa communication method of this invention, when needing to communicate with a batch of nodes, only requires waking up all nodes at once. Each node calculates an approximate communication time window based on the wake-up packet, enters a sleep state during the waiting period, and activates the receiving state to complete data reception just before the time window expires. This significantly reduces the number of times LoRa node terminals are woken up, greatly reducing node power consumption. Furthermore, long preambles are no longer sent during communication with nodes, shortening the data length compared to existing technologies that send long preambles every time, effectively reducing communication time, thereby improving the system's communication data volume performance, reducing node power consumption, extending product battery life, and saving energy.

[0078] In the several embodiments provided in this invention, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus and method embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0079] In addition, the functional modules in the various embodiments of the present invention can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0080] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, electronic device, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks. It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. In the absence of further restrictions, an element defined by the phrase "comprising a..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0081] The terminology used in the embodiments of this invention is for the purpose of describing particular embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” as used in the embodiments of this invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0082] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0083] Depending on the context, the word "if" as used here can be interpreted as "when," "when," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrase "if determination" or "if detection (of the stated condition or event)" can be interpreted as "when determination," "in response to determination," "when detection (of the stated condition or event)," or "in response to detection (of the stated condition or event)."

[0084] The use of "first" and "second" in the embodiments is merely to distinguish similar objects and does not represent a specific ordering of objects. It is understood that "first" and "second" can be interchanged in a specific order or sequence where permitted. It should be understood that the objects distinguished by "first" and "second" can be interchanged where appropriate so that the embodiments described herein can be implemented in an order other than those illustrated or described herein.

[0085] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A low-power LoRa communication system, characterized in that, It includes a LoRa gateway and a LoRa node terminal; wherein the LoRa node terminal and the LoRa gateway are communicatively connected; The LoRa gateway is used to construct a wake-up command based on whether the LoRa node terminal needs to communicate after receiving a batch of node communication commands; wherein, the wake-up command includes a long preamble for waking up the LoRa node terminal over the air; The LoRa node terminal is used to receive the wake-up command and determine whether it needs to communicate based on the wake-up command; when it determines that it does not need to communicate, it directly enters a sleep state; when it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters a sleep state based on the communication window time. The LoRa gateway is also used to send communication data without long preambles in sequence according to the batch node communication instructions. The LoRa node terminal is also used to wake up and enter the receiving state no later than the communication window time to receive communication data. The LoRa node terminal is specifically used for: CAD channel activity detection is performed periodically to continue receiving the wake-up command when a long preamble is detected; Based on the address mask in the wake-up command, determine whether you need to communicate. When it determines that it does not need to communicate, it enters hibernation mode; When it is determined that it needs to communicate, the communication sequence number is calculated based on the address mask, and the minimum communication duration for receiving the communication data is calculated based on the minimum data length. The communication window time is calculated based on the communication data transmission interval, the minimum communication duration, and the communication sequence number; where ts = index * (t + sendInterval), ts is the communication window time, index is the communication sequence number, t is the minimum communication duration, and sendInterval is the communication data transmission interval; Set a timer based on the communication window time and the early wake-up time difference, and then enter sleep mode.

2. The low-power LoRa communication system according to claim 1, characterized in that, The LoRa gateway, upon receiving a batch of node communication commands, constructs a wake-up command based on whether the LoRa node terminal needs to communicate; wherein, the wake-up command includes a long preamble for over-the-air wake-up of the LoRa node terminal, specifically including: Upon receiving a batch node communication command, the address mask is calculated based on whether the LoRa node terminal needs to communicate and the address of the LoRa node terminal; wherein, the addresses of the LoRa node terminals are allocated sequentially during the deployment of the communication system; The wake-up command is constructed based on the address mask and the long preamble used to wake up the LoRa node terminal over the air.

3. The low-power LoRa communication system according to claim 1, characterized in that, The wake-up command also includes a minimum data length.

4. The low-power LoRa communication system according to claim 1, characterized in that, The LoRa node terminal is also used to wake up and enter the receiving state no later than the communication window time to receive communication data, specifically including: It must wake up and enter the receiving state no later than the communication window time to receive communication data; When communication data is received, determine whether the received communication data was sent to itself; When the received communication data is data sent to itself, it will enter sleep mode after processing the data; If the received data is not the data sent to itself, then continue receiving data; If no data is received within the preset time, it is determined that the reception has timed out and enters sleep mode.

5. A low-power LoRa communication system according to any one of claims 1 to 4, characterized in that, The LoRa communication system is a star network, which includes at least one LoRa gateway and at least two LoRa node terminals; wherein, the LoRa node terminals can periodically enable channel activity detection to support over-the-air wake-up; The LoRa gateway is also used to send communication data without a long preamble in sequence according to the batch node communication instructions, specifically including: According to the batch node communication instructions, communication data without long preambles is sent in the address order of the LoRa node terminals.

6. A low-power LoRa gateway, characterized in that, Include: The LoRa gateway, upon receiving a batch of node communication commands, constructs a wake-up command based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for over-the-air wake-up of the LoRa node terminal. The wake-up command is received by the LoRa node terminal, which can determine whether it needs to communicate based on the wake-up command. When it determines that it does not need to communicate, it directly enters a sleep state. When it determines that it needs to communicate, it calculates its communication window time based on the wake-up command and enters sleep mode based on the communication window time. The LoRa gateway is also used to send communication data without a long preamble in sequence according to the batch node communication instructions; wherein the communication data is used to be received by the LoRa node terminal that is woken up and enters the receiving state no later than the communication window time.

7. A low-power LoRa node terminal, characterized in that, Include: The LoRa node terminal is used to receive a wake-up command and determine whether it needs to communicate based on the wake-up command. When it determines that it does not need to communicate, it directly enters a sleep state. When it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters sleep mode based on the communication window time. The wake-up command is constructed by the LoRa gateway after receiving a batch of node communication commands, based on whether the LoRa node terminal needs to communicate. The wake-up command includes a long preamble for waking up the LoRa node terminal over the air. The LoRa node terminal is also used to wake up and enter the receiving state no later than the communication window time to receive communication data; wherein, the communication data does not contain a long preamble and is sent sequentially by the LoRa gateway according to the batch node communication instructions; The LoRa node terminal is specifically used for: CAD channel activity detection is performed periodically to continue receiving the wake-up command when a long preamble is detected; Based on the address mask in the wake-up command, determine whether you need to communicate. When it determines that it does not need to communicate, it enters hibernation mode; When it is determined that it needs to communicate, the communication sequence number is calculated based on the address mask, and the minimum communication duration for receiving the communication data is calculated based on the minimum data length. The communication window time is calculated based on the communication data transmission interval, the minimum communication duration, and the communication sequence number; where ts = index * (t + sendInterval), ts is the communication window time, index is the communication sequence number, t is the minimum communication duration, and sendInterval is the communication data transmission interval; Set a timer based on the communication window time and the early wake-up time difference, and then enter sleep mode.

8. A low-power LoRa communication method, characterized in that, Include: S1. After receiving the batch node communication instruction, construct a wake-up instruction based on whether the LoRa node terminal needs to communicate; wherein, the wake-up instruction includes a long preamble for waking up the LoRa node terminal over the air; A1. Receive the wake-up command and determine whether it needs to communicate based on the wake-up command; when it determines that it does not need to communicate, it directly enters a sleep state; when it determines that it needs to communicate, it calculates its own communication window time based on the wake-up command and enters a sleep state based on the communication window time. S2. According to the batch node communication instructions, send communication data without long preamble in sequence; A2. Wake up and enter receiving mode no later than the communication window time to receive communication data; A1 specifically includes: CAD channel activity detection is performed periodically to continue receiving the wake-up command when a long preamble is detected; Based on the address mask in the wake-up command, determine whether you need to communicate. When it determines that it does not need to communicate, it enters hibernation mode; When it is determined that it needs to communicate, the communication sequence number is calculated based on the address mask, and the minimum communication duration for receiving the communication data is calculated based on the minimum data length. The communication window time is calculated based on the communication data transmission interval, the minimum communication duration, and the communication sequence number; where ts = index * (t + sendInterval), ts is the communication window time, index is the communication sequence number, t is the minimum communication duration, and sendInterval is the communication data transmission interval; Set a timer based on the communication window time and the early wake-up time difference, and then enter sleep mode; S1 and S2 are suitable for execution by the LoRa gateway; A1 and A2 are suitable for execution by the LoRa node terminal.

Images