A traffic balancing method based on multiple LoRa centralized controllers

Abstract

The present invention discloses a traffic balancing method based on multiple LoRa centralized controllers, and relates to the technical field of LoRa centralized controllers. The method comprises the following steps: S1: terminal data acquisition; S2: intermediate data processing; S3: traffic balance control; S4: server storage; and S5: terminal device display. The LoRa server performs intermediate node preprocessing by LoRa node devices, which is more conducive to system stability and balanced transmission. Each LoRa centralized controller can independently complete data acquisition and control tasks for various states of the control terminal. The terminal device achieves stable LoRa wireless communication with the LoRa centralized controller through regular inquiries, performs logical analysis based on the collected real-time traffic status, and sends the control results to the LoRa centralized controller via the LoRa server, thus achieving automated control and management.

Description

Technical Field

[0001] The present invention relates to the technical field of LoRa centralized controllers, and in particular to a traffic balancing method based on multiple LoRa centralized controllers. Background Art

[0002] Application number CN201720710190.5 discloses a multi-channel Lora concentrator and an IoT system using the Lora concentrator, including a main controller, the main controller is connected to a key input module, a 485 communication interface, a USB debugging interface, a power input port and a data storage module, the main controller is also connected to an RTC clock module, a hardware watchdog and a status indicator light; the main controller is embedded with a WIFI network port and an ETH network port, and the main controller is connected to a SIM card reading module and a communication wireless network module. It effectively avoids the disadvantage of small Lora point-to-point communication capacity. When communicating, the Lora radio frequency transceiver uses a private configuration communication protocol for wireless connection to effectively avoid the disadvantages of co-frequency interference and unstable data transmission, and effectively ensures the stability of data transmission. However, the multi-LoRa centralized controller still has the following problems in the process of fluid data control:

[0003] 1. In actual use, the data of the LoRa centralized controller is transmitted based on the network. However, in the multi-link transmission process, it is usually difficult to achieve a balance between performance and overhead. Traditional computing performance is limited, and the controller needs to issue forwarding rules to each node on the path;

[0004] 2. In the existing technology, when monitoring traffic data, the LoRa centralized controller is unable to balance and adjust the traffic when the actual operating traffic is inconsistent with the designed traffic. The adjustment cycle is long, and users cannot retrieve data in real time. Summary of the Invention

[0005] The object of the present invention is to provide a traffic balancing method based on multiple LoRa centralized controllers, which are connected to LoRa servers through multiple LoRa centralized controllers. The LoRa servers are pre-processed by LoRa node devices as intermediate nodes, which is more conducive to system stability and balanced transmission. Each LoRa centralized controller can independently complete data collection and control tasks for various states of the control terminal; the terminal device realizes stable LoRa wireless communication with the LoRa centralized controller in a regular inquiry manner, performs logical analysis based on the real-time traffic status collected, and sends the control results to the LoRa centralized controller through the LoRa server, thereby realizing automatic control management to solve the problems raised in the above background technology.

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

[0007] A traffic balancing method based on a multi-LoRa centralized controller is applied to a terminal device connecting to a server via a low-power wide area network. The method comprises the following steps:

[0008] S1: Terminal data collection: After the LoRa centralized controller is installed, the corresponding parameters are configured, including the IMEI number, IP address and port number, and the clock of the LoRa centralized controller is calibrated;

[0009] The LoRa centralized controller collects flow data of the measured fluid and its bound time data, and sends the flow data and time data to the LoRa node device;

[0010] The number of nodes accessed by the LoRa concentrator is determined by the channel resources it can provide and the channel resources occupied by a single LoRa terminal;

[0011] S2: Intermediate data processing: The LoRa node device converts the traffic data into LoRa data and sends the LoRa data to the LoRa server;

[0012] The LoRa node device converts the time data into a time axis, inputs the LoRa data into the time axis, and establishes a LoRa data curve;

[0013] The terminal device uses single-hop wireless communication to one or more LoRa concentrators;

[0014] S3: Traffic balancing control: After the LoRa server receives the uploaded LoRa data, it generates event metadata from the LoRa data and marks the event metadata. The event metadata is grouped according to multiple time periods, and the LoRa data is judged according to the preset threshold to determine whether it is within the scheduling threshold, and a balancing scheduling instruction is issued;

[0015] S4: Server storage: The LoRa server receives the event metadata and saves the LoRa data according to the tag and multiple time periods;

[0016] S5: Terminal device display: The terminal device displays the traffic device data and the usage status of the control terminal. At the same time, it can calculate the usage report for any specified time period and query all records of each LoRa centralized controller on a daily, monthly and annual basis at any time.

[0017] Furthermore, in S1, the LoRa centralized controller further includes:

[0018] At least one of the LoRa centralized controllers uses RF devices and spreading factors that are different from those of the terminal device nodes;

[0019] The spreading factors are orthogonal to each other, and multiple signals with different spreading factors are demodulated in the same channel;

[0020] All nodes of the LoRa node device are two-way communication.

[0021] Furthermore, in S2, the LoRa node device further includes:

[0022] The LoRa node device establishes no less than one node, a link is formed between the nodes, and the data flow is forwarded from the source node to another node, and the path passes through each node in succession;

[0023] The LoRa centralized control sends the corresponding forwarding path code and the corresponding segment list to the source node;

[0024] A plurality of the LoRa centralized controllers and the LoRa servers are interconnected to form a data collection node, and the LoRa servers are located at the data collection node.

[0025] Furthermore, the LoRa centralized control sends the corresponding forwarding path code and the corresponding segment list to the source node, including:

[0026] Establishing a calculation model in the segment list, determining the source node and the target node, and inputting the target node into the calculation model in the segment list;

[0027] Determine by calculation the shortest path from the source node to the destination node or a redundant equal-cost shortest path with load balancing;

[0028] The shortest path algorithm is used to obtain the shortest path or multiple equal-cost shortest paths between all the nodes; and no loop exists in the shortest path.

[0029] Furthermore, in S2, the LoRa data curve further includes:

[0030] A plurality of time periods pre-set in the time axis are used to collect data of each LoRa centralized controller and all working states according to different time periods;

[0031] Match any time period and data one by one to create a report;

[0032] At the same time, the usage time of each LoRa centralized controller control terminal will be accurately recorded, and the control terminal traffic status of each LoRa centralized controller will be statistically analyzed on a daily, annual and monthly basis based on the power of the load.

[0033] Furthermore, in S3, judging whether the LoRa data is within the scheduling threshold according to the preset threshold and issuing the balancing scheduling instruction includes:

[0034] Determine whether the LoRa data uploaded by the LoRa node device is greater than a preset upper scheduling threshold. If so, issue a preset traffic balancing strategy to the LoRa centralized controller. After receiving the instruction, the LoRa centralized controller performs traffic scheduling according to the traffic balancing strategy.

[0035] Determine whether the LoRa data uploaded by the LoRa node device is less than a preset lower scheduling threshold. If so, send a traffic balancing strategy deletion instruction to the LoRa centralized controller. After receiving the instruction, the LoRa centralized controller stops traffic scheduling according to the traffic balancing strategy.

[0036] Furthermore, the traffic balancing strategy includes:

[0037] Input the event metadata tag of the LoRa data into a preset strategy model database for matching;

[0038] and segmenting the LoRa data based on the matching result to generate a first target traffic data segment and a second target traffic data segment;

[0039] Determine the LoRa data balance adjustment value based on the first target traffic data segment and the second target traffic data segment input into the strategy model for calculation;

[0040] and comparing the balance adjustment value with a preset balance adjustment threshold to determine whether the LoRa data is within a balance range;

[0041] When the balance adjustment value is within the preset balance adjustment threshold, it is determined that the LoRa data is within the balance range;

[0042] Otherwise, it is determined that the LoRa data is not within the balance range. At the same time, when the LoRa data is within the balance range, an early warning report is generated, and the IMEI number, IP address and port number corresponding to the LoRa centralized controller are obtained;

[0043] Based on the parameters corresponding to the LoRa centralized controller, the corresponding address is matched, and at the same time, the early warning report is transmitted to the terminal device based on the Internet of Things.

[0044] Furthermore, in S5, the terminal device further includes:

[0045] The terminal device includes a remote management system deployed in the cloud. The remote management system realizes stable LoRa wireless communication with multiple LoRa centralized controllers in a periodic inquiry manner. The remote management system is provided with a function for viewing the working status of each LoRa centralized controller, providing remote control, timed task control, power load management, traffic analysis and comprehensive analysis of user habits. When the system is running, the steps of the traffic balancing method of multiple LoRa centralized controllers are executed.

[0046] Compared with the prior art, the present invention has the following beneficial effects:

[0047] 1. Multiple LoRa centralized controllers are connected to the LoRa server. The LoRa server performs intermediate node pre-processing by LoRa node devices, which is more conducive to system stability and balanced transmission. Each LoRa centralized controller can independently complete data collection and control tasks for various states of the control terminal. The terminal device achieves stable LoRa wireless communication with the LoRa centralized controller through regular inquiries, performs logical analysis based on the collected real-time traffic status, and sends the control results to the LoRa centralized controller through the LoRa server to achieve automated control and management.

[0048] 2. The source node is directly encoded and instructed by the LoRa node device, without the need to issue forwarding rules to the intermediate nodes. Traffic scheduling optimization calculations are performed according to demand and constraints. Each node can act as a source node for self-control. During scheduling, it is only necessary to select the appropriate path from the candidate paths according to demand, saving the time required for the LoRa centralized controller to establish the flow forwarding path and reducing the burden on the LoRa centralized controller. It supports multiple reporting methods such as fixed monthly reports, segmented reports, and detailed reports to monitor the use of the control terminal of the LoRa centralized controller in real time, making it easier for users to understand in a timely manner and improve the interaction between users and the control terminal.

[0049] 3. Through LoRa server modeling analysis and combined with the designed algorithm, the target traffic data is substituted into the algorithm for calculation to accurately determine whether the current traffic data exceeds the balance adjustment threshold. This not only simplifies the model and reduces the difficulty of subsequent solutions, but also the traffic balance scheduling method can meet various traffic requirements and constraints to achieve the purpose of traffic balance. Administrators can query all records of each LoRa centralized controller on a daily, monthly, and annual basis at any time, which facilitates data statistics and actual operation data statistics of the LoRa centralized controller control terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 This is a flow chart of the traffic balancing method of the multi-LoRa centralized controller of the present invention. DETAILED DESCRIPTION

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

[0052] In order to solve the technical problems of short network transmission distance, high energy consumption, high construction and operation costs, and weak stability in existing technologies, please refer to Figure 1 , this embodiment provides the following technical solutions:

[0053] A traffic balancing method based on a multi-LoRa centralized controller is applied to a terminal device connecting to a server via a low-power wide area network. The method comprises the following steps:

[0054] S1: Terminal data collection: After the LoRa centralized controller is installed, the corresponding parameters are configured, including the IMEI number, IP address and port number, and the clock of the LoRa centralized controller is calibrated;

[0055] The LoRa centralized controller collects flow data of the measured fluid and its bound time data, and sends the flow data and time data to the LoRa node device;

[0056] The number of nodes accessed by the LoRa concentrator is determined by the channel resources it can provide and the channel resources occupied by a single LoRa terminal;

[0057] At least one of the LoRa centralized controllers uses RF devices and spreading factors that are different from those of the terminal device nodes;

[0058] The spreading factors are orthogonal to each other, and multiple signals with different spreading factors are demodulated in the same channel;

[0059] All nodes of the LoRa node device are two-way communication;

[0060] S2: Intermediate data processing: The LoRa node device converts the traffic data into LoRa data and sends the LoRa data to the LoRa server;

[0061] The LoRa node device converts the time data into a time axis, inputs the LoRa data into the time axis, and establishes a LoRa data curve;

[0062] The terminal device uses single-hop wireless communication to one or more LoRa concentrators;

[0063] S3: Traffic balancing control: After the LoRa server receives the uploaded LoRa data, it generates event metadata from the LoRa data and marks the event metadata. The event metadata is grouped according to multiple time periods, and the LoRa data is judged according to the preset threshold to determine whether it is within the scheduling threshold, and a balancing scheduling instruction is issued;

[0064] S4: Server storage: The LoRa server receives the event metadata and saves the LoRa data according to the tag and multiple time periods;

[0065] S5: Terminal device display: The terminal device displays the flow device data and the usage status of the control terminal. It can also calculate the usage report for any specified time period and query all records of each LoRa centralized controller on a daily, monthly, and annual basis at any time.

[0066] The terminal device also includes: the terminal device contains a remote management system deployed in the cloud, the remote management system realizes stable LoRa wireless communication with multiple LoRa centralized controllers in a periodic inquiry manner, the remote management system is provided with a function to view the working status of each LoRa centralized controller, and provides remote control, scheduled task control, power load management, traffic analysis and comprehensive analysis of user habits. Steps S1-S5 are executed when the system is running.

[0067] Specifically, multiple LoRa centralized controllers are connected to the LoRa server, and the LoRa server is pre-processed by the LoRa node device as an intermediate node, which is more conducive to system stability and balanced transmission. Each LoRa centralized controller can independently complete the data collection and control tasks of various states of the control terminal; the terminal device realizes stable LoRa wireless communication with the LoRa centralized controller in a regular inquiry manner, and performs logical analysis based on the real-time traffic status collected, and sends the control results to the LoRa centralized controller through the LoRa server to realize automatic control management.

[0068] To address the technical issues in existing technologies where it is often difficult to strike a balance between performance and overhead during multi-link transmission, traditional computing performance is limited, and the controller needs to issue forwarding rules to each node on the path, this embodiment provides the following technical solutions:

[0069] The LoRa node device also includes: the LoRa node device establishes no less than one node, a link is formed between the nodes, the data flow is forwarded from the source node to another node, and the path passes through each node in turn; the LoRa centralized control issues a corresponding forwarding path code and a corresponding segment list to the source node; a calculation model is established in the segment list to determine the source node and the target node, and the target node is input into the calculation model of the segment list; the shortest path from the source node to the target node is determined by calculation or a redundant equivalent shortest path with load balancing; the shortest path or multiple equivalent shortest paths between all the nodes are obtained by the shortest path algorithm; the shortest path does not have a loop; multiple LoRa centralized controllers are interconnected with the LoRa server to form a data aggregation node, and the LoRa server is located at the data aggregation node;

[0070] The LoRa data curve also includes: multiple time periods pre-set in the time axis, data collection of each LoRa centralized controller and all working status according to different time periods; matching the arbitrary time periods and data one by one to make a report; at the same time, the usage time of each LoRa centralized controller control terminal will be accurately recorded, and according to the power of the load, the control terminal traffic status of each LoRa centralized controller will be statistically analyzed on a daily, annual and monthly basis.

[0071] Specifically, the source node is directly encoded and instructed by the LoRa node device, without the need to send forwarding rules to the intermediate nodes. Traffic scheduling optimization calculations are performed according to demand and constraints. Each node can act as a source node for self-control. During scheduling, it is only necessary to select a suitable path from the candidate paths according to demand, which saves the time required for the LoRa centralized controller to establish a flow forwarding path and reduces the burden on the LoRa centralized controller. It supports multiple reporting methods such as fixed monthly reports, segmented reports, and detailed reports to monitor the use of the control terminal of the LoRa centralized controller in real time, so that users can understand it in time and improve the interaction between users and the control terminal.

[0072] To address the technical issues in the prior art of being unable to balance and adjust flow when the actual operating flow is inconsistent with the designed flow, having a long adjustment cycle, and being unable to retrieve data in real time, this embodiment provides the following technical solutions:

[0073] Determining whether the LoRa data is within the scheduling threshold according to a preset threshold and issuing a balancing scheduling instruction includes: determining whether the LoRa data uploaded by the LoRa node device is greater than a preset upper scheduling threshold, and if so, issuing a preset traffic balancing strategy to the LoRa centralized controller, and the LoRa centralized controller performs traffic scheduling according to the traffic balancing strategy after receiving the instruction; determining whether the LoRa data uploaded by the LoRa node device is less than a preset lower scheduling threshold, and if so, issuing a traffic balancing strategy deletion instruction to the LoRa centralized controller, and the LoRa centralized controller stops traffic scheduling according to the traffic balancing strategy after receiving the instruction;

[0074] The event metadata tag of the LoRa data is input into a preset policy model database for matching; and the LoRa data is segmented based on the matching result to generate a first target traffic data segment and a second target traffic data segment; based on the first target traffic data segment and the second target traffic data segment, the LoRa data balance adjustment value is input into the policy model for calculation to determine; and the balance adjustment value is compared with a preset balance adjustment threshold to determine whether the LoRa data is within a balance range; when the balance adjustment value is within the preset balance adjustment threshold, the LoRa data is determined to be within a balance range; otherwise, the LoRa data is determined to be not within a balance range. At the same time, when the LoRa data is within the balance range, an early warning report is generated, and the IMEI number, IP address and port number corresponding to the LoRa centralized controller are obtained; the corresponding address is matched based on the parameters corresponding to the LoRa centralized controller, and at the same time, the early warning report is transmitted to the terminal device based on the Internet of Things.

[0075] Specifically, through LoRa server modeling analysis and combined with the designed algorithm, the target traffic data is substituted into the algorithm for calculation to accurately determine whether the current traffic data exceeds the balance adjustment threshold. This not only simplifies the model and reduces the difficulty of subsequent solutions, but also the traffic balance scheduling method can meet various traffic requirements and constraints to achieve the purpose of traffic balance. Administrators can query all records of each LoRa centralized controller on a daily, monthly, and annual basis at any time, which is convenient for data statistics and actual operation data statistics of the LoRa centralized controller control terminal.

[0076] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus.

[0077] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to these embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.

Claims

1. A traffic balancing method based on multiple LoRa centralized controllers, characterized by: Applied to connecting a terminal device to a server via a low-power wide area network, the method comprises the following steps: S1: Terminal data collection: After the LoRa centralized controller is installed, the corresponding parameters are configured, including the IMEI number, IP address and port number, and the clock of the LoRa centralized controller is calibrated; The LoRa centralized controller collects flow data of the measured fluid and its bound time data, and sends the flow data and time data to the LoRa node device; The number of nodes accessed by the LoRa centralized controller is determined by the channel resources it can provide and the channel resources occupied by a single LoRa terminal; S2: Intermediate data processing: The LoRa node device converts the traffic data into LoRa data and sends the LoRa data to the LoRa server; The LoRa node device converts the time data into a time axis, inputs the LoRa data into the time axis, and establishes a LoRa data curve; The terminal device uses single-hop wireless communication to one or more LoRa centralized controllers; The LoRa node device establishes no less than one node, a link is formed between the nodes, and the data flow is forwarded from the source node to another node, and the path passes through each node in succession; The LoRa centralized controller sends the corresponding forwarding path code and the corresponding segment list to the source node; A plurality of the LoRa centralized controllers and the LoRa servers are interconnected to form a data collection node, and the LoRa server is located at the data collection node; The LoRa centralized controller sends the corresponding forwarding path code and the corresponding segment list to the source node, including: Establishing a calculation model in the segment list, determining the source node and the target node, and inputting the target node into the calculation model in the segment list; Determine by calculation the shortest path from the source node to the destination node or a redundant equal-cost shortest path with load balancing; The shortest path algorithm is used to obtain the shortest path or multiple equivalent shortest paths between all the nodes; the shortest path does not have any loops; The LoRa data curve also includes: A plurality of time periods pre-set in the time axis are used to collect data of each LoRa centralized controller and all working states according to different time periods; Match any time period and data one by one to create a report; S3: Traffic balancing control: After the LoRa server receives the uploaded LoRa data, it generates event metadata from the LoRa data and marks the event metadata. The event metadata is grouped according to multiple time periods, and the LoRa data is judged according to the preset threshold to determine whether it is within the scheduling threshold, and a balancing scheduling instruction is issued; S4: Server storage: The LoRa server receives the event metadata and saves the LoRa data according to the tag and multiple time periods; S5: Terminal device display: The terminal device displays the traffic device data and the usage status of the control terminal, and calculates the usage report for any specified time period, and queries all records of each LoRa centralized controller on a daily, monthly, and annual basis at any time.

2. A flow balancing method based on a multi-LoRa centralized controller as claimed in claim 1, characterized in that: In the S1, the LoRa centralized controller further includes: At least one of the LoRa centralized controllers uses RF devices and spreading factors that are different from those of the terminal device nodes; The spreading factors are orthogonal to each other, and multiple signals with different spreading factors are demodulated in the same channel; All nodes of the LoRa node device are two-way communication.

3. A traffic balancing method based on a multi-LoRa centralized controller as claimed in claim 2, characterized in that: In S2, the LoRa data curve also includes: The usage time of each LoRa centralized controller control terminal will be accurately recorded, and the control terminal traffic status of each LoRa centralized controller will be statistically analyzed on a daily, annual and monthly basis based on the power of the load.

4. A traffic balancing method based on a multi-LoRa centralized controller as claimed in claim 3, characterized in that: In S3, judging whether the LoRa data is within the scheduling threshold according to the preset threshold and issuing a balancing scheduling instruction includes: Determine whether the LoRa data uploaded by the LoRa node device is greater than a preset upper scheduling threshold. If so, issue a preset traffic balancing strategy to the LoRa centralized controller. After receiving the instruction, the LoRa centralized controller performs traffic scheduling according to the traffic balancing strategy. Determine whether the LoRa data uploaded by the LoRa node device is less than a preset lower scheduling threshold. If so, send a traffic balancing strategy deletion instruction to the LoRa centralized controller. After receiving the instruction, the LoRa centralized controller stops traffic scheduling according to the traffic balancing strategy.

5. A traffic balancing method based on a multi-LoRa centralized controller as claimed in claim 4, characterized in that: The traffic balancing strategy includes: Input the event metadata tag of the LoRa data into a preset strategy model database for matching; and segmenting the LoRa data based on the matching result to generate a first target traffic data segment and a second target traffic data segment; Determine the LoRa data balance adjustment value based on the first target traffic data segment and the second target traffic data segment input into the strategy model for calculation; and comparing the balance adjustment value with a preset balance adjustment threshold to determine whether the LoRa data is within a balance range; When the balance adjustment value is within the preset balance adjustment threshold, it is determined that the LoRa data is within the balance range; Otherwise, it is determined that the LoRa data is not within the balance range. At the same time, when the LoRa data is within the balance range, an early warning report is generated, and the IMEI number, IP address and port number corresponding to the LoRa centralized controller are obtained; Based on the parameters corresponding to the LoRa centralized controller, the corresponding address is matched, and at the same time, the early warning report is transmitted to the terminal device based on the Internet of Things.

6. A traffic balancing method based on a multi-LoRa centralized controller as claimed in claim 5, characterized in that: In S5, the terminal device further includes: The terminal device includes a remote management system deployed in the cloud. The remote management system realizes stable LoRa wireless communication with multiple LoRa centralized controllers in a periodic query manner. The remote management system is provided with a function for viewing the working status of each LoRa centralized controller, providing remote control, scheduled task control, power load management, traffic analysis and comprehensive analysis of user habits. Steps S1-S5 are executed when the system is running.

Images