Personnel positioning and safety monitoring system based on LoRa communication

Abstract

The invention discloses a personnel positioning and safety monitoring system for LoRa communication, relates to the technical field of communication positioning, and is used for solving the problem of communication congestion when uplink data is dense or abnormal events occur intensively. The method comprises the following steps: counting the number of monitoring data frames in a counting period and calculating uplink receiving frequency to judge whether to enter a congestion judgment stage, analyzing repeated receiving frames in the congestion judgment stage to obtain a repeated reporting index, calculating the average air time length of the monitoring data frames, generating a gateway congestion level based on the repeated reporting index and the average air time length, and sending the gateway congestion level to a server. Meanwhile, the alarm frame trigger statistics and the data frame uplink number are obtained, the reporting period reference is called to generate the scheduling priority score, the reporting period is corrected accordingly, whether the alarm prompt is generated or not is judged, and channel occupation caused by invalid reporting can be reduced while priority transmission of alarm information is guaranteed.

Description

Technical Field

[0001] This invention relates to the field of communication and positioning technology, and more specifically, to a LoRa communication-based personnel positioning and safety monitoring system. Background Technology

[0002] With the widespread application of IoT technology in complex work scenarios such as mining operations, tunnel construction, petrochemical plants, underground pipe corridors and large factories, LoRa communication technology has become an important technical means to ensure the personal safety of workers. Due to its advantages such as low power consumption, long distance and flexible networking, it is widely used in the reporting of location information of personnel wearable terminals.

[0003] The existing technology has the following shortcomings: Currently, existing technologies mostly manage the uplink communication of personnel terminals using fixed reporting cycles or simple rate limiting methods. They lack sophisticated detection and dynamic hierarchical assessment mechanisms for the uplink congestion status of communication access nodes, making it difficult to accurately identify the true congestion level of the gateway under different load conditions. This leads to transmission delays or even data loss when critical alarm information competes for channel resources with ordinary monitoring data during periods of dense uplink data or concentrated abnormal events, exacerbating communication congestion. Therefore, this paper proposes a LoRa communication-based personnel positioning and safety monitoring system.

[0004] The information disclosed in the background section is only intended to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a LoRa communication personnel positioning and safety monitoring system. This system addresses the problems mentioned in the background art by employing a congestion determination mechanism based on uplink receiving frequency, a multi-dimensional congestion level assessment method combining repeated reporting index and average airtime, and a dynamic adjustment strategy for reporting cycle based on alarm priority.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a LoRa communication-based personnel positioning and safety monitoring system, comprising a data detection module, a congestion detection module, a level assessment module, and a reporting and adjustment module, the functions of which are as follows: The data detection module obtains the monitoring data frames of each personnel terminal through the uplink data received by the communication access node under test, divides the monitoring data frames into data frame queues, sets a statistical period, collects the number of monitoring data frames in the data frame queue within the statistical period and calculates the uplink receiving frequency, and transmits the uplink receiving frequency to the congestion detection module. The congestion detection module is used to determine whether to enter the congestion determination stage based on the uplink receiving frequency. In the congestion determination stage, it detects duplicate received frames of monitoring data frames and analyzes the duplicate reporting index, collects channel occupancy duration information of monitoring data frames and calculates the average air time, and transmits the duplicate reporting index and average air time to the level evaluation module. After receiving the repeated reporting index and average airtime, the level assessment module analyzes the congestion status characteristics of the communication access node under test, generates the gateway congestion level based on the congestion status characteristics, detects the alarm frame trigger statistics and data frame uplink quantity of each personnel terminal, and transmits them to the reporting and adjustment module. The reporting adjustment module is used to retrieve the reporting cycle benchmark, generate a scheduling priority score by combining alarm frame trigger statistics and data frame uplink quantity, generate a reporting adjustment coefficient by combining the gateway congestion level, and use the reporting adjustment coefficient to correct the reporting cycle benchmark and determine whether to generate an alarm prompt.

[0007] In a preferred embodiment, the data detection module performs application layer protocol parsing and frame reconstruction on the uplink data received by the communication access node under test to obtain the monitoring data frames of each personnel terminal. The monitoring data frame includes the data frame type, personnel terminal identifier, and time identifier; Based on the data frame type, the monitoring data frames of each personnel terminal are divided, and monitoring data frames with the same type identifier are grouped into the same data frame queue, which is divided into the location frame queue and the alarm frame queue. Set a statistical period, and within the statistical period, count the number of members in the location frame queue and the alarm frame queue; The number of members in the location frame queue and the alarm frame queue are added together, and the result is divided by the statistical period to obtain the uplink receiving frequency.

[0008] In a preferred embodiment, in the congestion detection module, if the uplink receiving frequency is greater than or equal to a preset receiving frequency threshold, it is determined that the congestion determination stage has been entered. Conversely, if the condition is not met, the congestion assessment phase will not be initiated. Based on personnel terminal identifiers and time identifiers, duplicate received frames of monitoring data frames are detected using a frame consistency determination method. Monitoring data frames with the same personnel terminal identifier are integrated into a monitoring data frame queue.

[0009] In a preferred embodiment, in the congestion detection module, the monitoring data frames are sorted according to the time identifier, and monitoring data frames with the same time identifier are determined to be consistent frames. In a consistent frame, the first received monitoring data frame is taken as the valid received frame, and the remaining monitoring data frames are determined to be duplicate received frames. Statistically monitor the number of members in the data frame queue and the number of duplicate received frames; The number of repeatedly received frames is divided by the number of members in the monitoring data frame queue to obtain the repeated reporting index.

[0010] In a preferred embodiment, the channel occupancy duration information in the congestion detection module includes the data frame over-the-air transmission duration; The timestamps for the start and end of transmission of each monitoring data frame are obtained through the timestamp recording unit. Subtract the start time stamp and the completion time stamp of each monitoring data frame to obtain the air transmission duration of each monitoring data frame. The average airtime is obtained by averaging the airtime of each monitoring data frame.

[0011] In a preferred embodiment, in the grade assessment module, the duplicate reporting index and the average airtime are standardized to obtain the duplicate factor and the duration factor. The congestion state characteristics of the communication access node under test are calculated by combining the repetition factor and the duration factor. If the congestion state characteristics are less than the preset second congestion state characteristic threshold, the gateway congestion level is determined to be the first level. If the congestion state characteristic is greater than or equal to the preset second congestion state characteristic threshold and less than the preset first congestion state characteristic threshold, then the gateway congestion level is determined to be the second level. If the congestion state characteristics are greater than or equal to the preset first congestion state characteristic threshold, the gateway congestion level is determined to be the third level. Among them, the preset first congestion state feature threshold is greater than the preset second congestion state feature threshold.

[0012] In a preferred embodiment, in the level assessment module, the alarm trigger identification information written in each monitoring data frame of the personnel terminal is read. When the alarm trigger identification information indicates that an alarm trigger event has occurred, the monitoring data frame is determined to be a valid alarm trigger; otherwise, it is an invalid alarm trigger. The number of valid alarm triggers in a single monitoring data frame is used as the alarm frame trigger statistics for personnel terminals; The number of monitoring data frames from each personnel terminal is counted as the number of uplink data frames from each personnel terminal.

[0013] In a preferred embodiment, in the level assessment module, the personnel terminal identifier of each personnel terminal is matched with the reporting cycle benchmark configuration database to obtain the reporting cycle benchmark of each personnel terminal. The alarm frame trigger statistics and data frame uplink quantity of each personnel terminal are standardized to obtain the trigger factor and uplink factor; The scheduling priority score for each personnel terminal is calculated by combining the triggering factor and the uplink factor. Map the gateway congestion levels as 1, 2, and 3 from low to high; The numerical values ​​corresponding to the gateway congestion level and the scheduling priority score are standardized to obtain the congestion factor and scheduling factor. The reporting adjustment coefficient of each personnel terminal is calculated by combining the congestion factor and the scheduling factor.

[0014] In a preferred embodiment, in the level assessment module, the ratio of the reporting cycle benchmark of each personnel terminal to the reporting adjustment coefficient is used as the corrected reporting cycle benchmark of each personnel terminal. If the corrected reporting cycle benchmark for each personnel terminal is greater than or equal to the preset cycle benchmark threshold, an alarm will be generated. Conversely, no alarm message will be generated.

[0015] The technical effects and advantages of this invention are as follows: This invention acquires monitoring data frames from various personnel terminals by receiving uplink data from the communication access node under test. Within a statistical period, it counts the number of monitoring data frames and calculates the uplink receiving frequency to determine whether congestion has entered the assessment phase. During the congestion assessment phase, it analyzes repeatedly received frames to obtain a repeated reporting index and calculates the average airtime of the monitoring data frames. Based on the repeated reporting index and average airtime, it generates a gateway congestion level. Simultaneously, it acquires alarm frame trigger statistics and the number of uplink data frames, retrieves the reporting period benchmark to generate a scheduling priority score, and adjusts the reporting period accordingly to determine whether to generate an alarm notification. This achieves precise identification and hierarchical control of the congestion status of the communication access node, ensuring priority transmission of alarm information while reducing the channel occupation caused by invalid reporting. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating the implementation of a LoRa communication-based personnel positioning and safety monitoring system according to the present invention.

[0017] Figure 2 This is a module framework diagram of a LoRa communication-based personnel positioning and safety monitoring system according to the present invention. Detailed Implementation

[0018] 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. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] This invention acquires monitoring data frames from various personnel terminals by receiving uplink data from the communication access node under test. Within a statistical period, it counts the number of monitoring data frames and calculates the uplink receiving frequency to determine whether the congestion assessment stage has begun. In the congestion assessment stage, it analyzes repeated received frames to obtain a repeated reporting index and calculates the average airtime of the monitoring data frames. Based on the repeated reporting index and the average airtime, it generates a gateway congestion level. Simultaneously, it acquires alarm frame trigger statistics and the number of uplink data frames, retrieves the reporting period benchmark to generate a scheduling priority score, and corrects the reporting period accordingly to determine whether to generate an alarm prompt. This enables precise identification and hierarchical control of the congestion status of the communication access node.

[0020] Example 1, as Figures 1 to 2 As shown, a LoRa communication-based personnel positioning and safety monitoring system includes a data detection module, a congestion detection module, a level assessment module, and a reporting and adjustment module. The modules are electrically connected, and the functions of each module are as follows: The data detection module obtains the monitoring data frames of each personnel terminal through the uplink data received by the communication access node under test, divides the monitoring data frames into data frame queues, sets a statistical period, collects the number of monitoring data frames in the data frame queue within the statistical period and calculates the uplink receiving frequency, and transmits the uplink receiving frequency to the congestion detection module. The congestion detection module is used to determine whether to enter the congestion determination stage based on the uplink receiving frequency. In the congestion determination stage, it detects duplicate received frames of monitoring data frames and analyzes the duplicate reporting index, collects channel occupancy duration information of monitoring data frames and calculates the average air time, and transmits the duplicate reporting index and average air time to the level evaluation module. After receiving the repeated reporting index and average airtime, the level assessment module analyzes the congestion status characteristics of the communication access node under test, generates the gateway congestion level based on the congestion status characteristics, detects the alarm frame trigger statistics and data frame uplink quantity of each personnel terminal, and transmits them to the reporting and adjustment module. The reporting adjustment module is used to retrieve the reporting cycle benchmark, generate a scheduling priority score by combining alarm frame trigger statistics and data frame uplink quantity, generate a reporting adjustment coefficient by combining the gateway congestion level, and use the reporting adjustment coefficient to correct the reporting cycle benchmark and determine whether to generate an alarm prompt.

[0021] The specific implementation is as follows: In the data detection module, in the application scenario where personnel terminals use low-power wide-area communication networks for positioning and safety information reporting, the communication access node under test needs to receive uplink data from multiple personnel terminals simultaneously. Different terminals generate monitoring information periodically or in an event-triggered manner according to the communication protocol. The uplink data exhibits diverse characteristics in terms of time distribution and frame type. By identifying the monitoring data frame type, terminal identifier, and time identifier of each personnel terminal, different types of data frames are distinguished and statistically analyzed, and the corresponding uplink reception characteristics are obtained, providing basic data support for subsequent communication status analysis and adjustment. The uplink data received by the communication access node under test is parsed using application layer protocols and reconstructed to obtain the monitoring data frames of each personnel's terminal. Monitoring data frames refer to structured uplink data units that are generated and reported by personnel terminals after they access the LoRa communication network, according to the communication protocol periodically or by event triggering. These data frames include data frame type, personnel terminal identifier, and time identifier. The monitoring data frames of each personnel terminal are parsed by pre-defined field positions, and the data frame type, personnel terminal identifier and time identifier in the monitoring data frames of each personnel terminal are read. Based on the data frame type, the monitoring data frames of each personnel terminal are divided, and monitoring data frames with the same type identifier are grouped into the same data frame queue, which is divided into the location frame queue and the alarm frame queue. Set a statistical period, and within the statistical period, count the number of members in the location frame queue and the alarm frame queue; The number of members in the location frame queue and the alarm frame queue are added together, and the result is divided by the statistical period to obtain the uplink receiving frequency.

[0022] It needs to be explained that the uplink data received by the communication access node under test refers to the original digital communication message initiated and sent by the personnel terminal device, transmitted via the wireless air interface, and finally successfully received by the communication access node under test; application layer protocol parsing and frame reconstruction is a software processing method that extracts business information from the original communication data packet and assembles it into a standardized internal data structure, used to obtain the monitoring data frames of each personnel terminal from the uplink data received by the communication access node under test; preset field position refers to the starting offset and length of various data fields in the original byte stream, which are predefined in the application layer protocol and can be set according to the communication protocol specification, the physical meaning and order of the data fields, and byte alignment optimization requirements; the statistical period can be comprehensively set according to the network monitoring granularity, terminal reporting mode, and congestion detection sensitivity requirements.

[0023] By parsing the uplink data, reconstructing the frames, and classifying the types, we can accurately obtain the monitoring data frames and their distribution characteristics of each personnel terminal, realize the classification and statistics of positioning frames and alarm frames, provide a reliable basis for calculating the uplink receiving frequency, and improve the accuracy of the basic operating status perception of the communication access node.

[0024] In the congestion detection module, the uplink receiving frequency is compared with a preset receiving frequency threshold for judgment: If the uplink receiving frequency is greater than or equal to the preset receiving frequency threshold, the congestion determination stage is entered. If the uplink receiving frequency is less than the preset receiving frequency threshold, it is determined that the congestion determination stage will not be entered. Based on personnel terminal identifiers and time identifiers, duplicate received frames of monitoring data frames are detected using a frame consistency determination method. The specific method for determining frame consistency is as follows: Integrated monitoring data frames with the same personnel terminal identifier into a monitoring data frame queue; The monitoring data frames are sorted according to their time identifiers, and monitoring data frames with the same time identifiers are identified as consistent frames. In a consistent frame, the first received monitoring data frame is taken as the valid received frame, and the remaining monitoring data frames are determined to be duplicate received frames. Statistically monitor the number of members in the data frame queue and the number of duplicate received frames; The number of repeatedly received frames is divided by the number of members in the monitoring data frame queue to obtain the repeated reporting index; Channel occupancy duration information refers to the length of time a single monitoring data frame occupies the LoRa communication channel during wireless transmission, including the data frame's air transmission duration. The timestamps for the start and end of transmission of each monitoring data frame are obtained through the timestamp recording unit. Subtract the start time stamp and the completion time stamp of each monitoring data frame to obtain the air transmission duration of each monitoring data frame. The average airtime is obtained by averaging the airtime of each monitoring data frame.

[0025] It should be explained that the preset receiving frequency threshold can be set comprehensively based on the theoretical processing capability of the communication access node under test, the physical layer capacity of the LoRa wireless channel, and empirical data in actual deployment scenarios; the timestamp recording unit is a functional unit combining hardware and software, which automatically adds high-precision timestamps during the transmission and reception of data frames to obtain the transmission start timestamp and transmission completion timestamp of each monitoring data frame.

[0026] By introducing an uplink receiving frequency determination mechanism and combining it with duplicate receiving frame identification and over-the-air transmission duration analysis, data retransmission and channel occupancy anomalies can be effectively identified, enabling timely detection of the congestion status of communication access nodes and providing objective quantitative indicators for subsequent congestion assessment.

[0027] In the rating assessment module, the duplicate reporting index and average airtime are standardized to obtain the duplicate factor and duration factor. The congestion state characteristics of the communication access node under test are calculated by combining the repetition factor and the duration factor. The calculation formula is as follows: ,in, As the repeating factor, For duration factor, and To preset the weighting coefficients, The congestion state characteristics of the communication access node under test; It should be noted that the preset weighting coefficients can be set based on network reliability requirements, channel resource utilization targets, and statistical analysis of historical operating data.

[0028] The larger the repetition factor and the longer the duration factor, the more severe the network data retransmission phenomenon, the higher the channel resource occupancy rate, and the greater the congestion state characteristics of the communication access node under test; the smaller the repetition factor and the shorter the duration factor, the milder the network data retransmission phenomenon, the lower the channel resource occupancy rate, and the smaller the congestion state characteristics of the communication access node under test. The congestion status characteristics of the communication access node under test reflect the overall network congestion level of the node within the statistical period and its relative severity level in the evaluation system. The larger the congestion status characteristic value, the higher the data retransmission rate and channel occupancy rate of the node, and the more severe its network congestion level is in the evaluation. The smaller the congestion status characteristic value, the better the network transmission quality and the healthier the channel utilization of the node, and the relatively mild or smooth network congestion level is. The congestion state characteristics of the communication access node under test are compared with preset first congestion state characteristic thresholds and preset second congestion state characteristic thresholds for judgment: It should be noted that the preset first congestion state feature threshold is greater than the preset second congestion state feature threshold.

[0029] If the congestion status characteristics of the communication access node under test are less than the preset second congestion status characteristic threshold, the gateway congestion level is determined to be the first level. If the congestion status characteristics of the communication access node under test are greater than or equal to the preset second congestion status characteristic threshold and less than the preset first congestion status characteristic threshold, then the gateway congestion level is determined to be the second level. If the congestion status characteristics of the communication access node under test are greater than or equal to the preset first congestion status characteristic threshold, the gateway congestion level is determined to be the third level. Read the alarm trigger identification information written in each monitoring data frame of the personnel terminal. When the alarm trigger identification information indicates that an alarm trigger event has occurred, the monitoring data frame is determined to be a valid alarm trigger; otherwise, it is an invalid alarm trigger. The number of valid alarm triggers in a single monitoring data frame is used as the alarm frame trigger statistics for that person's terminal; Repeat the above steps to obtain the alarm frame trigger statistics for each person's terminal; The number of monitoring data frames from each personnel terminal is counted as the number of uplink data frames from each personnel terminal.

[0030] It should be explained that the standardization processing methods include, but are not limited to, standard linear transformation based on interval scaling, Z-Score standardization based on statistics, or normalization based on nonlinear mapping functions. The application methods of standardization processing will not be elaborated here. The preset first congestion state characteristic threshold and the preset second congestion state characteristic threshold can be comprehensively set according to the network service quality target, the distribution of historical congestion characteristic data, and the control strategy requirements corresponding to different levels.

[0031] By standardizing the duplicate reporting index and average airtime and constructing a comprehensive congestion status feature, a hierarchical expression of the congestion level of communication access nodes is realized, enabling the network congestion status to have comparable and quantifiable assessment results, while providing a clear hierarchical basis for terminal-side scheduling decisions.

[0032] In the reporting and adjustment module, the personnel terminal identifier of each personnel terminal is matched with the reporting cycle benchmark configuration database to obtain the reporting cycle benchmark of each personnel terminal. The alarm frame trigger statistics and data frame uplink quantity of each personnel terminal are standardized to obtain the trigger factor and uplink factor; The scheduling priority score for each personnel's terminal is calculated by combining the triggering factor and the uplink factor. The calculation formula is as follows: ,in, As a triggering factor, As an upside factor, Priority scoring is assigned to the scheduling of each personnel's terminal; The larger the trigger factor and the larger the uplink factor, the higher the frequency of terminal alarm triggering, the larger the amount of data uplinked, and the higher the scheduling priority score of each personnel's terminal; the smaller the trigger factor and the smaller the uplink factor, the lower the frequency of terminal alarm triggering, the smaller the amount of data uplinked, and the lower the scheduling priority score of each personnel's terminal. The scheduling priority score of each personnel terminal reflects the business urgency of the terminal within the statistical period and its relative priority level in the network. The higher the scheduling priority score, the greater the alarm trigger frequency and data uplink volume of the terminal, and its business urgency and resource requirements are among the highest in the system. The lower the scheduling priority score, the more relaxed the business activities and the smaller the data traffic of the terminal, and its business urgency and resource requirements are relatively low. Map the gateway congestion levels as 1, 2, and 3 from low to high; The numerical values ​​corresponding to the gateway congestion level and the scheduling priority score are standardized to obtain the congestion factor and scheduling factor. The reporting adjustment coefficient for each personnel terminal is calculated by combining the congestion factor and the scheduling factor. The calculation formula is as follows: ,in, As the scheduling factor, For congestion factor, The adjustment coefficient for each personnel's terminal; The larger the scheduling factor and the smaller the congestion factor, the higher the urgency of the terminal service, the lower the degree of network congestion, and the larger the reporting adjustment coefficient; the smaller the scheduling factor and the larger the congestion factor, the lower the urgency of the terminal service, the higher the degree of network congestion, and the smaller the reporting adjustment coefficient. The reporting adjustment coefficient of each personnel terminal reflects the final scheduling adjustment intensity of that terminal under a specific network congestion level. The larger the reporting adjustment coefficient, the higher the transmission priority should be given under the current network conditions after comprehensively considering the urgency of its business, that is, a shorter reporting cycle, in order to ensure its communication needs. The smaller the reporting adjustment coefficient, the lower the transmission priority can be accepted under the current network conditions after comprehensively considering the urgency of its business, that is, a longer reporting cycle, in order to serve the overall network congestion relief. The ratio of the reporting cycle benchmark of each personnel terminal to the reporting adjustment coefficient is used as the corrected reporting cycle benchmark of each personnel terminal. The revised reporting cycle baseline for each personnel terminal is compared with the preset cycle baseline threshold for judgment: If the corrected reporting cycle benchmark for each personnel terminal is greater than or equal to the preset cycle benchmark threshold, an alarm will be generated. If the revised reporting cycle benchmark for each personnel terminal is less than the preset cycle benchmark threshold, no alarm will be generated.

[0033] It should be explained that the reporting cycle baseline configuration database is a dedicated data storage system that centrally stores and manages the default reporting cycle baseline values ​​of all personnel terminals under different business scenarios, and is used to obtain the reporting cycle baseline of each personnel terminal; the preset cycle baseline threshold can be comprehensively set according to the maximum response latency allowed by the business, the minimum data refresh rate requirement of the terminal type, and the service baseline that the network can guarantee under the worst congestion conditions; the alarm prompt is a structured early warning information that the system automatically generates and sends to the operation and maintenance personnel or the superior system when it detects an abnormal state that may affect the effectiveness of monitoring or network security. Its purpose is to proactively notify relevant personnel of potential risks so that timely intervention can be carried out.

[0034] By combining the business urgency characteristics of personnel terminals with the gateway congestion level, the terminal reporting cycle is dynamically adjusted and alarm prompts are generated. While ensuring the communication needs of high-priority business, low-urgency terminals are guided to reasonably extend their reporting cycle, thereby improving the overall network resource utilization efficiency and communication stability.

[0035] Finally, it should be noted that in this paper, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0036] Furthermore, 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. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0037] In this document, the singular forms “a,” “an,” and “the” may also include the plural forms unless the context clearly indicates otherwise. It should also be understood that terms such as “comprising / including” or “having” specify the presence of the stated features, integrals, steps, operations, components, parts, or combinations thereof, but do not preclude the possibility of the presence or addition of one or more other features, integrals, steps, operations, components, parts, or combinations thereof. Meanwhile, the term “and / or” as used in this specification includes any and all combinations of the associated listed items.

[0038] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referred to each other.

[0039] The above description of the disclosed embodiments will enable those skilled in the art to make or use various modifications to these embodiments. It will be readily apparent to those skilled in the art that the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A LoRa communication-based personnel positioning and safety monitoring system, characterized in that: It includes a data detection module, a congestion detection module, a level assessment module, and a reporting and adjustment module. The functions of each module are as follows: The data detection module obtains the monitoring data frames of each personnel terminal through the uplink data received by the communication access node under test, divides the monitoring data frames into data frame queues, sets a statistical period, collects the number of monitoring data frames in the data frame queue within the statistical period and calculates the uplink receiving frequency, and transmits the uplink receiving frequency to the congestion detection module. The congestion detection module is used to determine whether to enter the congestion determination stage based on the uplink receiving frequency. In the congestion determination stage, it detects duplicate received frames of monitoring data frames and analyzes the duplicate reporting index, collects channel occupancy duration information of monitoring data frames and calculates the average air time, and transmits the duplicate reporting index and average air time to the level evaluation module. After receiving the repeated reporting index and average airtime, the level assessment module analyzes the congestion status characteristics of the communication access node under test, generates the gateway congestion level based on the congestion status characteristics, detects the alarm frame trigger statistics and data frame uplink quantity of each personnel terminal, and transmits them to the reporting and adjustment module. The reporting adjustment module is used to retrieve the reporting cycle benchmark, generate a scheduling priority score by combining alarm frame trigger statistics and data frame uplink quantity, generate a reporting adjustment coefficient by combining the gateway congestion level, and use the reporting adjustment coefficient to correct the reporting cycle benchmark and determine whether to generate an alarm prompt.

2. The LoRa communication personnel positioning and safety monitoring system according to claim 1, characterized in that: In the data detection module, the uplink data received by the communication access node under test is parsed using the application layer protocol and reconstructed to obtain the monitoring data frames of each personnel terminal. The monitoring data frame includes the data frame type, personnel terminal identifier, and time identifier; Based on the data frame type, the monitoring data frames of each personnel terminal are divided, and monitoring data frames with the same type identifier are grouped into the same data frame queue, which is divided into the location frame queue and the alarm frame queue. Set a statistical period, and within the statistical period, count the number of members in the location frame queue and the alarm frame queue; The number of members in the location frame queue and the alarm frame queue are added together, and the result is divided by the statistical period to obtain the uplink receiving frequency.

3. A LoRa communication personnel positioning and safety monitoring system according to claim 2, characterized in that: In the congestion detection module, if the uplink receiving frequency is greater than or equal to the preset receiving frequency threshold, the congestion determination stage is entered. Conversely, if the condition is not met, the congestion assessment phase will not be initiated. Based on personnel terminal identifiers and time identifiers, duplicate received frames of monitoring data frames are detected using a frame consistency determination method. Monitoring data frames with the same personnel terminal identifier are integrated into a monitoring data frame queue.

4. A LoRa communication personnel positioning and safety monitoring system according to claim 3, characterized in that: In the congestion detection module, the monitoring data frames are sorted according to their time identifiers, and monitoring data frames with the same time identifiers are identified as consistent frames. In a consistent frame, the first received monitoring data frame is taken as the valid received frame, and the remaining monitoring data frames are determined to be duplicate received frames. Statistically monitor the number of members in the data frame queue and the number of duplicate received frames; The number of repeatedly received frames is divided by the number of members in the monitoring data frame queue to obtain the repeated reporting index.

5. A LoRa communication personnel positioning and safety monitoring system according to claim 1, characterized in that: In the congestion detection module, channel occupancy duration information includes the data frame over-the-air transmission duration; The timestamps for the start and end of transmission of each monitoring data frame are obtained through the timestamp recording unit. Subtract the start time stamp and the completion time stamp of each monitoring data frame to obtain the air transmission duration of each monitoring data frame. The average airtime is obtained by averaging the airtime of each monitoring data frame.

6. A LoRa communication personnel positioning and safety monitoring system according to claim 1, characterized in that: In the rating assessment module, the duplicate reporting index and average airtime are standardized to obtain the duplicate factor and duration factor. The congestion state characteristics of the communication access node under test are calculated by combining the repetition factor and the duration factor. If the congestion state characteristics are less than the preset second congestion state characteristic threshold, the gateway congestion level is determined to be the first level. If the congestion state characteristic is greater than or equal to the preset second congestion state characteristic threshold and less than the preset first congestion state characteristic threshold, then the gateway congestion level is determined to be the second level. If the congestion state characteristics are greater than or equal to the preset first congestion state characteristic threshold, the gateway congestion level is determined to be the third level. Among them, the preset first congestion state feature threshold is greater than the preset second congestion state feature threshold.

7. A LoRa communication personnel positioning and safety monitoring system according to claim 1, characterized in that: In the level assessment module, the alarm trigger identification information written in each monitoring data frame of the personnel terminal is read. When the alarm trigger identification information indicates that an alarm trigger event has occurred, the monitoring data frame is determined to be a valid alarm trigger; otherwise, it is an invalid alarm trigger. The number of valid alarm triggers in a single monitoring data frame is used as the alarm frame trigger statistics for personnel terminals; The number of monitoring data frames from each personnel terminal is counted as the number of uplink data frames from each personnel terminal.

8. A LoRa communication personnel positioning and safety monitoring system according to claim 6, characterized in that: In the rating assessment module, the personnel terminal identifier of each personnel terminal is matched with the reporting cycle benchmark configuration database to obtain the reporting cycle benchmark of each personnel terminal. The alarm frame trigger statistics and data frame uplink quantity of each personnel terminal are standardized to obtain the trigger factor and uplink factor; The scheduling priority score for each personnel terminal is calculated by combining the triggering factor and the uplink factor. Map the gateway congestion levels as 1, 2, and 3 from low to high; The numerical values ​​corresponding to the gateway congestion level and the scheduling priority score are standardized to obtain the congestion factor and scheduling factor. The reporting adjustment coefficient of each personnel terminal is calculated by combining the congestion factor and the scheduling factor.

9. A LoRa communication personnel positioning and safety monitoring system according to claim 8, characterized in that: In the rating assessment module, the ratio of the reporting cycle benchmark of each personnel terminal to the reporting adjustment coefficient is used as the corrected reporting cycle benchmark of each personnel terminal. If the corrected reporting cycle benchmark for each personnel terminal is greater than or equal to the preset cycle benchmark threshold, an alarm will be generated. Conversely, no alarm message will be generated.

Images