Distributed position information aggregation reporting method and system based on group collaboration

Abstract

The invention relates to the technical field of emergency location uploading, and provides a distributed location information aggregation reporting method and system based on group collaboration. The method comprises the following steps: when a trigger device detects a preset emergency event, generating a cooperative discovery beacon frame, and sending first position information and event session information corresponding to the preset emergency event to response devices in an effective cooperative area; the response device generates response data information containing second position information based on the first position information and the event session information, and sends the response data information to the trigger device; and the trigger device generates aggregation position information based on the first position information and the second position information, and sends the aggregation position information and the event session information to a server. According to the method, the problems that position information reporting of single equipment is limited and position information reporting of a fixed group is lack of flexibility are solved.

Description

Technical Field

[0001] This application relates to the field of emergency event location uploading technology, and in particular to a distributed location information aggregation and reporting method and system based on group collaboration. Background Technology

[0002] With the increasing demand for modern emergency rescue and team safety monitoring, mobile terminal-based location reporting systems are widely used. Existing technologies typically rely on individual devices independently reporting their location information to a central server, or using predefined fixed groups for simple location sharing.

[0003] However, in the event of a sudden emergency, existing methods struggle to gather comprehensive location information on relevant personnel in the vicinity of the emergency. Information provided by a single reporting source is limited and may be inaccurate, while fixed group mechanisms lack adaptive coordination capabilities for temporary and regional events. This prevents rescue centers from quickly obtaining comprehensive and reliable information on the distribution of personnel on-site, thereby affecting the timeliness and accuracy of rescue or command decisions. Summary of the Invention

[0004] This application provides a distributed location information aggregation and reporting method and system based on group collaboration, in order to solve the problems mentioned in the background.

[0005] In a first aspect, this application provides a distributed location information aggregation and reporting method based on group collaboration, used in a collaborative location reporting system, the system comprising multiple member devices, the method comprising: When a triggering device detects a preset emergency event, it generates a collaborative discovery beacon frame and sends the collaborative discovery beacon frame to each responding device within the effective collaborative area; wherein, the triggering device is any one of the member devices, and the responding device is one or more of the remaining member devices other than the triggering device, and the collaborative discovery beacon frame includes the first location information of the triggering device and the event session information corresponding to the preset emergency event; The response device generates response data information based on the cooperative discovery beacon frame and sends the response data information to the triggering device; wherein, the response data information includes the second location information of the response device; The triggering device generates aggregated location information based on the first location information and each of the second location information, and sends the aggregated location information and the event session information to the server.

[0006] Secondly, this application provides a distributed location information aggregation and reporting system based on group collaboration, the system comprising multiple member devices, the system being used to implement: When a triggering device detects a preset emergency event, it generates a collaborative discovery beacon frame and sends the collaborative discovery beacon frame to each responding device within the effective collaborative area; wherein, the triggering device is any one of the member devices, and the responding device is one or more of the remaining member devices other than the triggering device, and the collaborative discovery beacon frame includes the first location information of the triggering device and the event session information corresponding to the preset emergency event; The response device generates response data information based on the cooperative discovery beacon frame and sends the response data information to the triggering device; wherein, the response data information includes the second location information of the response device; The triggering device generates aggregated location information based on the first location information and each of the second location information, and sends the aggregated location information and the event session information to the server.

[0007] This application provides a method and system for distributed location information aggregation and reporting based on group collaboration. The method first involves a triggering device generating a collaborative discovery beacon frame upon detecting a preset emergency event and sending it to all responding devices within the effective collaborative area. This dynamically initiates a collaborative request network at the event location, establishing a communication foundation for collecting location information from surrounding devices. Next, each responding device generates response data containing its own second location information based on the received collaborative discovery beacon frame and replies to the triggering device, converging scattered and isolated device location data towards the event's central point, providing raw data for forming an overall situational awareness. Finally, the triggering device generates aggregated location information based on the collected first and second location information and sends it to the server. This integrates multiple discrete locations into a single situational report containing a center, range, and scale of participation, allowing the server to understand the personnel distribution at the event site based on a single, integrated report, rather than multiple scattered reports. This process overcomes the limitations of single-device location reporting and the lack of flexibility in fixed-group location reporting, achieving dynamic aggregation and reporting of personnel locations in sudden, regional events. Attached Figure Description

[0008] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0009] Figure 1 This is a flowchart illustrating the distributed location information aggregation and reporting method based on group collaboration provided in an embodiment of this application. Detailed Implementation

[0010] 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, not all, of the embodiments of the present invention. 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.

[0011] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it require execution in the described order. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0012] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0013] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the relevant listed items and all possible combinations, and includes such combinations.

[0014] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0015] Please see Figure 1 , Figure 1 This is a flowchart illustrating a distributed location information aggregation and reporting method based on group collaboration provided in an embodiment of this application. The method is used in a collaborative location reporting system, which includes multiple member devices, such as... Figure 1 As shown, the distributed location information aggregation and reporting method based on group collaboration provided in this application includes steps S1 to S3.

[0016] Step S1: When the triggering device detects a preset emergency event, it generates a collaborative discovery beacon frame and sends the collaborative discovery beacon frame to each responding device in the effective collaborative area; wherein, the triggering device is any one of the member devices, and the responding device is one or more of the other member devices besides the triggering device, and the collaborative discovery beacon frame includes the first location information of the triggering device and the event session information corresponding to the preset emergency event.

[0017] The preset emergency event refers to a specific situation that requires initiating the collaborative location reporting process; the effective collaborative area refers to the physical space range centered on the geographical location of the triggering device, where its signal broadcast can reach and participation in the collaboration is meaningful; the first location information refers to data output by the positioning module of the triggering device, which includes geographical coordinates, timestamps, and estimated positioning accuracy; the event session information refers to data used to uniquely identify and describe this collaborative reporting event, including at least an event session identifier and an event type. Specifically, when a background process running on a member device acting as a trigger analyzes the data stream from its built-in sensors (such as accelerometers) and identifies an abnormal waveform matching a preset impact pattern, or receives a clear alarm command from the user interface, the process determines that a preset emergency event has occurred. Subsequently, the process calls the device's global navigation satellite system module to obtain the current latitude and longitude coordinates and records the acquisition time and positioning error value, constituting the first location information. Simultaneously, the process combines the device's unique identifier with a real-time generated random number, using hash calculations to generate a globally unique string as an event session identifier. This identifier is then mapped to the corresponding event type (e.g., "device drop" or "manual assistance") based on the trigger source (sensor malfunction or user command), and both constitute the event session information. Finally, the process serializes the first location information and the event session information according to a preset protocol format, encapsulates them into a data packet, and begins periodically broadcasting this data packet via its Bluetooth or Wi-Fi module at a set power and frequency. This data packet is the cooperative discovery beacon frame, and the geographical area covered by the broadcast constitutes the initial effective cooperative area.

[0018] Step S2: The response device generates response data information based on the cooperative discovery beacon frame and sends the response data information to the triggering device; wherein, the response data information includes the second location information of the response device.

[0019] The response data information refers to the data packet generated by the responding device to reply to the triggering device in order to participate in the collaboration; the second location information refers to the data output by the positioning module of the responding device, which includes its own geographic coordinates, timestamp, and estimated positioning accuracy. Specifically, when the short-range communication module of another member device acting as the responding device receives the collaboration discovery beacon frame, its system layer parses the data packet to extract the event type and event session identifier; then, the application layer program of the device queries whether it is authorized or needs to respond to the event type according to the locally stored configuration file; if the response is confirmed, the program immediately requests the positioning service to obtain its current latitude and longitude coordinates and related positioning data, which constitute the second location information; subsequently, the program encapsulates its own device code, the second location information, and the event session identifier parsed from the beacon frame according to a response format compatible with the receiving beacon to generate response data information; finally, the program instructs the communication module to send the encapsulated response data information back to the source address of the beacon, i.e., the triggering device.

[0020] Step S3: The triggering device generates aggregated location information based on the first location information and each of the second location information, and sends the aggregated location information and the event session information to the server.

[0021] The aggregated location information refers to a structured data report reflecting the group's location status, generated by comprehensively calculating the first location information and all received second location information. The server refers to a remote computer system deployed in the network, responsible for receiving and processing reported information. Specifically, the triggering device starts a data receiving timer that lasts for several seconds while broadcasting a collaborative discovery beacon frame. During the timer's operation, the triggering device collects its own first location information and the second location information contained in all successfully received and parsed response data. After collection, the triggering device performs aggregation calculations: First, it calculates weights based on the estimated positioning accuracy in each location information, and performs a weighted average of all latitude and longitude coordinates to obtain an aggregation center coordinate. Second, it traverses all coordinate points to find the minimum and maximum longitude and latitude values, thereby determining a minimum boundary moment that can completely cover all coordinate points. The process involves: first, counting the number of valid location information entries to obtain the total number of member devices participating in the collaboration; then, integrating the aggregation center coordinates, the diagonal coordinates of the minimum boundary rectangle, the total number of member devices, and all original location information (after anonymization) into a structured data object, which is the aggregated location information; after generating the aggregated location information, triggering the device to evaluate the status of its cellular mobile network and Wi-Fi connection, selecting the link with the best signal quality as the uplink channel according to the preset priority, packaging the aggregated location information together with the event session information, and transmitting it to the designated network server address, i.e., the server, through the uplink channel.

[0022] The method provided in this embodiment firstly, when a triggering device detects a preset emergency event, it generates a collaborative discovery beacon frame and sends it to each responding device within the effective collaborative area, dynamically initiating a collaborative request network at the event location and establishing a communication foundation for collecting location information of surrounding related devices. Then, the responding devices generate response data information containing their own second location information based on the received collaborative discovery beacon frame and reply to the triggering device, aggregating scattered and isolated device location data towards the event's central point, providing raw data for forming an overall situational awareness. Finally, the triggering device generates aggregated location information based on the collected first and second location information and sends it to the server, comprehensively calculating multiple discrete location points into a situational report containing a center, range, and scale of participation. This allows the server to understand the personnel distribution at the event site based on a single integrated report, rather than multiple scattered reports. This process solves the limitations of single device reporting location information and the lack of flexibility in fixed group reporting of location information, achieving dynamic aggregation and reporting of personnel locations in sudden and regional events.

[0023] In some embodiments, when the triggering device detects a preset emergency event, it generates a cooperative discovery beacon frame, including: Step S111: Continuously monitor the data acquisition information of the built-in sensors and the status of the command interface.

[0024] The built-in sensors refer to the hardware components in the device used to sense physical motion; the data acquisition information refers to the raw data sequence periodically sampled and output by the built-in sensors; and the command interface refers to the software or hardware channel for receiving external control commands. Specifically, a resident monitoring service runs in the background of the device's operating system. This service reads the three-axis raw data from the accelerometer and gyroscope sensors at a fixed frequency (e.g., 10 times per second) and stores the numerical group (x, y, z) and timestamp of each reading into a circular buffer, forming a continuously updated data acquisition information stream. At the same time, the service listens for a specific message queue or interrupt signal managed by the system kernel. This queue or signal is defined as the command interface, and any alarm commands generated from user interface applications or physical button triggers are sent through this interface.

[0025] Step S112: When the data collection information matches the preset abnormal information, or when the command interface receives an alarm command triggered by the user, it is determined that a preset emergency event has been detected.

[0026] The abnormal information refers to predefined sensor data patterns within the system that indicate the device is in an abnormal state; the user refers to the person operating the device. Specifically, the monitoring service analyzes the latest data acquisition information in the circular buffer in real time and compares it with a set of pre-stored abnormal information patterns. For example, an abnormal information pattern might be defined as "within 100 milliseconds, the increment of the acceleration vector sum exceeds twice the gravitational acceleration." If the current sensor data sequence matches any abnormal information pattern, an internal trigger signal is generated. At the same time, if the monitoring service detects a new alarm command message arriving in the message queue of the command interface (this message is generated by the user clicking the emergency button on the screen or pressing and holding a specific hardware button), another internal trigger signal is generated. As long as either of the above two trigger signals becomes valid, the monitoring service makes a logical judgment of "detecting a preset emergency event" and wakes up the subsequent emergency processing thread.

[0027] Step S113: Obtain first location information including geographic coordinates, positioning timestamp, and positioning accuracy estimate through the positioning module. Here, the positioning module refers to the hardware or software component responsible for determining the device's geographic location; the positioning accuracy estimate refers to the quantitative assessment of the reliability of the coordinates provided by the positioning module. Specifically, after a preset emergency event is determined, the awakened emergency processing thread immediately initiates a high-priority positioning request to the device's positioning service (such as a GPS chip driver or network positioning service API); the positioning service comprehensively processes information such as satellite signals, base station triangulation, or Wi-Fi fingerprints, and returns a data packet; after parsing, the data packet extracts the latitude and longitude coordinates expressed in decimal degrees, the positioning completion time in Coordinated Universal Time (UTC) format, and a value representing the horizontal positioning error radius (e.g., in meters), which is the positioning accuracy estimate; the coordinates, timestamp, and positioning accuracy estimate are combined to form the data structure of the first location information.

[0028] Step S114: Generate a globally unique event session identifier composed of a trigger device code and a random number, and generate an event type for the emergency event based on the data acquisition information or the alarm command triggered by the user; wherein, the event session identifier and the event type constitute the event session information.

[0029] The trigger device code refers to a string or number used to uniquely identify the device; the random number refers to an unpredictable sequence of numbers generated by a random number generator; the event session identifier refers to a string used to uniquely identify the event throughout its entire lifecycle; and the event type refers to a classification description of the nature of the emergency event. Specifically, the emergency processing thread reads the device's unique serial number from its non-volatile memory as the basis for triggering device encoding; simultaneously, it calls the cryptographically secure pseudo-random number generator provided by the operating system to generate a 128-bit random number; it concatenates the device serial number, the random number, and the current high-precision timestamp, and performs a SHA-256 hash operation on the concatenated string, taking the first 16 characters of the hash value as the final event session identifier; regarding the generation of the event type, the system branches according to the determination source in step S12: if triggered by data acquisition information, the predefined label associated with the matched abnormal information pattern (such as "SENSOR_FALL") is used as the event type; if triggered by the command interface, the command code in the alarm command message is parsed and mapped to the corresponding label (such as "USER_SOS"); finally, the generated event session identifier and the event type are combined into a key-value pair, which constitutes the complete event session information.

[0030] Step S115: Encapsulate the first location information and the event session information to form the collaborative discovery beacon frame.

[0031] Specifically, the emergency processing thread creates a new memory buffer and serializes the first location information data structure (including coordinates, timestamp, and precision) obtained in step S113 and the event session information key-value pairs (including identifier and type) obtained in step S114 into the buffer according to a pre-designed binary or JSON protocol format. Then, a protocol header is added to the front of the data payload. The protocol header contains a frame start identifier, data length, and frame type (identifying this as a discovery beacon). A checksum calculated based on the cyclic redundancy check algorithm is appended to the back of the data payload. Finally, this complete data packet with a header, payload, and trailer is submitted to the device's short-range wireless communication module for transmission. This data packet is defined as a cooperative discovery beacon frame.

[0032] The method provided in this embodiment firstly provides real-time, multi-source data input for event detection by continuously monitoring the data acquisition information from the built-in sensors and the status of the command interface. Then, by comparing the acquired data with preset anomaly information or recognizing user commands, it automatically determines preset emergency events, thereby triggering subsequent processes. Secondly, it obtains first location information containing an estimated positioning accuracy through the positioning module, providing a precise spatiotemporal reference point for collaboration. Thirdly, it generates a globally unique event session identifier by combining device coding and random numbers, and constructs event session information based on the event type generated from the trigger source, establishing a non-repeatable, categorized global logical identifier for the entire collaborative event. Finally, it encapsulates the first location information and event session information into a collaborative discovery beacon frame, generating a broadcast data unit with a unified format containing all necessary initial information. This series of steps achieves a fully automated and standardized process from event perception to collaborative request data packet generation, ensuring the accuracy and efficiency of collaborative initiation.

[0033] In some embodiments, the event type for generating an emergency event based on the data acquisition information or a user-triggered alarm command includes: When an emergency event is determined to be triggered by the data acquisition information, the data acquisition information is matched with multiple preset sensor anomaly patterns. The event type associated with the sensor anomaly pattern that successfully matches the data acquisition information is determined as the event type of the current emergency event. Here, the sensor anomaly pattern refers to a mathematical model or set of rules used to describe the characteristics of sensor data under specific dangerous or abnormal conditions. Specifically, during system initialization, a set of sensor anomaly patterns and their associated event types are preloaded into memory. Each sensor anomaly pattern may consist of one or more judgment rules. For example, the rule for pattern A is "the combined acceleration of 5 consecutive sampling points is greater than 3g and the rate of change of angular velocity is greater than 100 degrees / second". 2 The associated event type is "severe impact". When it is determined that the emergency event is triggered by data acquisition information, the system will compare the data acquisition information (such as the acceleration and gyroscope data sequence of the most recent second) within the time window near the trigger time with each preset sensor anomaly mode in turn. If all the judgment rules of a certain mode are met, it is determined that the match is successful. The system then reads the event type string (such as "severe impact") bound in the configuration of the successfully matched sensor anomaly mode and determines this string as the event type of this emergency event.

[0034] When an emergency event is determined to be triggered by an alarm command initiated by the user, a predefined command code is parsed from the alarm command received from the command interface. Based on a preset command code-event type mapping relationship, the command code is mapped to the corresponding event type. The command code refers to a specific numerical value or string encoded in the alarm command message to distinguish different alarm operations. Specifically, when an emergency event is determined to be triggered by the command interface, the alarm command message is retrieved from the message queue of the command interface. The message is parsed, and the command code field carried in the message body is extracted. This command code may be an enumerated value (e.g., value 1 represents "medical assistance," value 2 represents "security threat"). The system maintains a command code-event type mapping table, which defines the event type string corresponding to each valid command code. The system uses the parsed command code as an index to query this mapping table, obtains the event type string associated with that command code (e.g., command code 1 is mapped to "medical assistance"), and determines this string as the event type of this emergency event.

[0035] The method provided in this embodiment first determines the event type by matching real-time data acquisition information with preset sensor anomaly patterns, automatically classifying physical sensor signals into event descriptions with clear semantics. Then, it determines the event type by parsing the command code in the user's alarm command and querying the mapping relationship, thereby accurately converting the user's intent into system-recognizable classification information. This process provides standardized classification identifiers for different types of emergency events, enabling subsequent steps such as response strategy configuration and collaborative area determination to be differentiated based on clear event categories, enhancing the targeting and intelligence level of the entire collaborative reporting system.

[0036] In some embodiments, the triggering device sends the cooperative discovery beacon frame to each responding device within the effective cooperative area, including: Step S121: Determine the communication distance threshold based on the event type, and determine the effective cooperation area based on the communication distance threshold.

[0037] The communication distance threshold refers to the distance value used to limit the broadcast range of the collaborative discovery beacon frame. Specifically, the system maintains a configuration table of event types and communication distance thresholds; for example, the event type "medical assistance" may be associated with a threshold of 500 meters, while the event type "device drop" may be associated with a threshold of 50 meters. After generating event session information, the system uses the determined event type as the key to query this configuration table and obtain the corresponding communication distance threshold (in meters). Subsequently, the system defines a circular area in space with the geographical coordinates in the triggering device's first location information as the center and the queried communication distance threshold as the radius. This circular geographical range is then determined as the effective collaborative area for this collaboration.

[0038] Step S122: Broadcast the cooperative discovery beacon frame to each responding device within the effective cooperative area.

[0039] Specifically, the triggering device adjusts its transmission power to a level that theoretically covers the communication distance threshold determined in step S121 (considering environmental attenuation) based on the technical characteristics of its short-range wireless communication module (such as Bluetooth 5.0 or Wi-Fi); then, the device instructs its communication module to periodically (e.g., twice per second) broadcast encapsulated cooperative discovery beacon frame data packets; the broadcast signal propagates outward from the device in all directions, and its physical coverage is designed to match the previously calculated effective cooperative area, so that responding devices located within this circular area that have activated their corresponding communication modules and are running the listening service have a probability of receiving the beacon frame.

[0040] The method provided in this embodiment first determines a communication distance threshold based on the event type, dynamically setting a reasonable collaborative spatial range for different types of emergency events. Then, based on this communication distance threshold, an effective collaborative area is determined, and this range guides the broadcasting of beacon frames, limiting collaborative requests to a reasonable geographical range related to the event. This process achieves dynamic adaptation of the collaborative range, avoiding resource waste (too large a range) or incomplete information collection (too small a range) that may be caused by a fixed range, thus improving the efficiency and targeting of the collaboration.

[0041] In some embodiments, the response device generates response data information based on the collaborative discovery beacon frame, including: step S211, determining whether to respond collaboratively to the event type based on a locally preset response policy configuration file. Specifically, after parsing the collaborative discovery beacon frame and obtaining the event type field contained therein, the response device accesses the response policy configuration file stored in the device's local file system. This file is a structured data file that defines the device's response behavior to different event types. The response device uses the obtained event type as the query key to search in the configuration file; the search process matches the corresponding configuration section according to the event type to determine whether it is authorized to respond to the event.

[0042] Step S212: If a coordinated response is determined, the second location information is obtained through the positioning module. Specifically, when the judgment logic output result of step S211 is "coordinated response", the location acquisition process is triggered; the device's positioning service API is called to initiate a real-time positioning request; the positioning service comprehensively processes information from GNSS satellites, mobile network base stations, or Wi-Fi access points, calculates and returns the device's current location data; the system receives this data and parses out the geographic coordinates, positioning timestamp, and positioning accuracy estimate from it, and encapsulates this data into structured second location information.

[0043] Step S213: Encapsulate the corresponding response device code, the second location information, and the event session identifier to generate the response data information.

[0044] Specifically, the system reads the device's unique device identifier string from its read-only memory or secure storage area as the response device code; simultaneously, it obtains the event session identifier from the parsed cooperative discovery beacon frame; the system creates a new data buffer, and sequentially writes the response device code, the second location information data structure generated in step S212, and the event session identifier into the buffer according to the predefined response data frame format; a protocol header is added before the data payload to identify the frame type and length, and a checksum is appended after the payload; the final complete data packet is the response data information, which is transmitted to the device's short-range wireless communication module for transmission.

[0045] The method provided in this embodiment first involves the responding device determining the type of the received collaborative request event based on a locally pre-configured response strategy configuration file, thus enabling autonomous decision-making regarding whether to participate in the collaboration. Then, after deciding to respond, it immediately obtains its own secondary location information through the positioning module, providing the core data required for participation in the collaboration. Finally, it encapsulates its own device code, location information, and event identifier into standard response data, thereby generating a formatted and complete reply data packet. This process ensures the orderliness of the response behavior and the uniformity of the data format, enabling the triggering device to efficiently receive and process feedback information from different responding devices.

[0046] In some embodiments, determining whether to coordinate a response to the event type based on a locally pre-configured response strategy configuration file includes: Step S2111: Based on the event type, perform a matching query in the response strategy configuration file to obtain the response rule corresponding to the event type.

[0047] The response rules refer to the set of specific instructions defined in the response policy configuration file for a specific event type, guiding how the device should respond. These instructions include response indications and execution condition thresholds. Specifically, after loading the response policy configuration file, the system parses it into an internal lookup table or rule tree. When a query is needed, the system takes the event type string as input and performs an exact match search within this data structure. The search operation returns one or more response rule objects associated with that event type. Each response rule object contains at least two core fields: a "response indication" field (whose value is "allow response", "force response", or "prohibit response") and an "execution condition threshold" structure (which defines thresholds such as "minimum battery level" and "maximum CPU load rate").

[0048] Step S2112: Obtain the current status parameters of the response device; the current status parameters include at least the battery level and CPU load rate.

[0049] Specifically, the system calls the operating system's power management interface to read the current percentage of battery power remaining; at the same time, it calls the system performance monitoring interface to obtain the current average load rate of the central processing unit or the percentage of usage rate in a recent period; the battery power percentage and CPU load rate, together with other possible status parameters (such as memory usage), constitute a set of current status parameters that characterize the current state of the device.

[0050] Step S2113: Compare the current state parameter with the execution condition threshold in the acquired response rule.

[0051] Specifically, the system extracts the "execution condition threshold" structure from the response rule object obtained in step S2111; for each item in the current state parameter set, it compares it with the corresponding threshold in the threshold structure; for example, it compares the read battery percentage with the "minimum battery percentage" threshold (e.g., 20%) defined in the threshold structure to determine whether the battery percentage is greater than or equal to the threshold; it compares the read CPU load rate with the "maximum CPU load rate" threshold (e.g., 80%) defined in the threshold structure to determine whether the load rate is less than or equal to the threshold; these comparison operations produce a series of Boolean (true / false) results.

[0052] Step S2114: When the queried response rule indicates that the response is allowed or forced, and the current status parameter meets the execution condition threshold, it is determined to perform a coordinated response to the event type.

[0053] Specifically, the system first checks the "Response Indication" field in the response rule object; if the value of this field is "Disable Response", it directly determines that no coordinated response will be performed and terminates the process; if the value of this field is "Allow Response" or "Force Response", the system continues to check a series of Boolean comparison results generated in step S2113; only when all the necessary comparison results are "true" (i.e. all the checked current state parameters meet their corresponding execution condition thresholds) will the system finally output the logical conclusion of "determine to perform a coordinated response to the event type"; if the "Response Indication" is "Allow Response" but any state parameter does not meet the threshold, or the "Response Indication" is "Force Response" but the state parameter does not meet the threshold (in which case exceptions such as low power mode may be triggered, but under the basic rules), it is usually determined that no response will be performed to ensure the basic functions of the device.

[0054] The method provided in this embodiment firstly provides specific behavioral basis and constraints for decision-making by querying the corresponding response rules in the configuration file based on the event type. Then, by acquiring real-time battery power and CPU load rate, the device's resource status at the time of decision-making is assessed. Secondly, by comparing the real-time status parameters with the execution condition thresholds in the rules, the device's current ability to execute a response is quantitatively evaluated. Finally, by combining the response indication (willingness) and capability assessment (conditions), a final determination is made on whether to conduct a collaborative response. This process achieves refined and conditional response decision-making, preventing devices from blindly participating in collaboration when resources are insufficient, thus affecting their main functions and improving the robustness and practicality of the entire collaborative system.

[0055] In some embodiments, the triggering device generates aggregated location information based on the first location information and each of the second location information, including: Step S311: While broadcasting the collaborative discovery beacon frame, a data receiving window with a preset duration is opened. The data receiving window refers to a time interval reserved by the triggering device specifically for receiving response data. Specifically, at the same moment the emergency processing thread of the triggering device instructs the communication module to start broadcasting the collaborative discovery beacon frame, the thread initializes and starts a countdown timer. The duration of this countdown timer is preset to a fixed value (e.g., 5 seconds), and this time interval is the data receiving window. During this period, the communication module of the triggering device maintains a state of listening to and receiving reply signals from the responding device during the intervals between intermittent beacon frame broadcasts. When the countdown timer reaches zero, the thread closes the logic for receiving response data, marking the end of the data collection phase.

[0056] Step S312: Within the data receiving window, the triggering device gathers its own first location information and the response data information containing second location information received from each response device. Specifically, after the data receiving window opens, the triggering device first stores its own first location information generated in step S113 into a temporary set; simultaneously, for each data packet received through the communication module during the window period, the system unpacks and parses the protocol. If it is confirmed to be valid response data information, the system extracts the data structure of the second location information and adds this data structure as a new entry to the aforementioned temporary set; when the data receiving window closes, this temporary set contains the triggering device's own first location information and the second location information of all successfully received response devices, and this set is the basic dataset for subsequent calculations.

[0057] Step S313: Using the reciprocal of the estimated positioning accuracy in each location information as the weight, perform a weighted average calculation on the geographic coordinates of all location information to obtain the aggregation center coordinates. Specifically, the system iterates through each entry in the location information set collected in step S312; for each entry, read its estimated positioning accuracy (denoted as e, in meters) and calculate its weight w = 1 / e; then, perform a weighted average calculation on the longitude and latitude values ​​of all entries respectively: aggregation longitude = Σ[longitude(i) × w(i)] / Σ[w(i)], aggregation latitude = Σ[latitude(i) × w(i)] / Σ[w(i)]; the calculated (aggregate longitude, aggregation latitude) coordinates are the aggregation center coordinates, which represent the geographic center position of the entire group under the premise of considering the positioning reliability of each point.

[0058] Step S314: Calculate the minimum boundary rectangle based on the geographic coordinates of all location information; the minimum boundary rectangle is the smallest rectangular area that can cover all the geographic coordinates.

[0059] Step S315: Integrate the aggregation center coordinates, the minimum boundary rectangle, the total number of member devices participating in the collaboration, and all original location information to generate the aggregated location information.

[0060] The method provided in this embodiment first establishes a clear time boundary for the collection of response information by opening a data receiving window simultaneously with the broadcast beacon, ensuring the timeliness of the process. Then, it aggregates all location information within the window to construct a complete dataset for aggregation calculation. Next, it calculates the aggregation center coordinates using a weighted average weighted by the reciprocal of positioning accuracy, taking into account the reliability differences of data from different locations when determining the group center, resulting in a more representative center point. Third, it visually depicts the geographical distribution range of group members by calculating the minimum boundary rectangle. Finally, it generates aggregated location information by integrating the center coordinates, distribution range, participation scale, and original data, forming a complete situation report containing core conclusions and original evidence. This series of steps achieves automated and intelligent aggregation from raw location data to high-level situation information, providing decision-makers with comprehensive, reliable, and easily understandable location intelligence.

[0061] In some embodiments, calculating the minimum boundary rectangle based on geographic coordinates of all location information includes: Step S3141: Extract the geographic coordinates from each location information.

[0062] Step S3142: Determine the minimum and maximum longitude values ​​among the longitude values ​​corresponding to each geographic coordinate point, and determine the minimum and maximum latitude values ​​among the latitude values ​​corresponding to each geographic coordinate point.

[0063] Step S3143: Determine the coordinates of the lower left corner vertex of the minimum boundary rectangle based on the minimum longitude value and the minimum latitude value.

[0064] Step S3144: Determine the coordinates of the upper right corner vertex of the minimum boundary rectangle based on the maximum longitude value and the maximum latitude value.

[0065] Step S3145: Determine the minimum boundary rectangle based on the coordinates of the lower left corner vertex and the coordinates of the upper right corner vertex.

[0066] Specifically, the coordinates of the lower left corner vertex determined in step S3143 and the coordinates of the upper right corner vertex determined in step S3144 are taken as a pair of diagonal vertices. In a two-dimensional Cartesian coordinate system (here, the latitude and longitude plane is abstractly represented), this pair of diagonal vertices can uniquely determine a rectangular region whose sides are parallel to the coordinate axes. The span of this rectangle in the east-west direction is from the minimum longitude value to the maximum longitude value, and the span in the north-south direction is from the minimum latitude value to the maximum latitude value. This rectangular region is defined as the minimum boundary rectangle because it is the rectangle with the smallest area under the conditions of "all sides are parallel to the coordinate axes" and "completely covers all given geographic coordinate points".

[0067] The method provided in this embodiment first prepares the original geometric data for boundary calculation by extracting geographic coordinate points from all location information. Then, by traversing and comparing all coordinate points to determine the extreme values ​​in the longitude and latitude directions, four boundary values ​​required to define the rectangular area are identified. Next, the starting boundary point of the rectangular coverage area is determined by combining the minimum longitude and minimum latitude to form the lower left vertex. Third, the ending boundary point of the rectangular coverage area is determined by combining the maximum longitude and maximum latitude to form the upper right vertex. Finally, by defining the rectangular region using a pair of diagonal vertices, the geographical distribution range of group members is accurately described in a computationally simple and data-efficient manner. This process provides an efficient and standardized algorithm for generating the spatial distribution bounding box from a discrete point set, and is one of the key steps in generating aggregated location information.

[0068] In some embodiments, the triggering device sends the aggregated location information and the event session information to the server, including: Step S321: Detect the signal quality and connection status of all currently available wide-area wireless communication links.

[0069] Specifically, the system calls the operating system's network connection management interface to obtain a list of all currently active or available wide-area wireless communication links. This list may include 4G / 5G cellular networks, external networks connected via Wi-Fi (such as Wi-Fi hotspots connected to the Internet), etc. For each item in the list, the system further queries its detailed status information, which includes at least: for cellular networks, querying its received signal strength indicator, signal-to-noise ratio, and network attachment status; for Wi-Fi networks, querying its signal strength, connection speed, and whether it has successfully obtained an IP address and has a route to the Internet. The technical parameters obtained from these queries collectively characterize the signal quality and connection status of each link.

[0070] Step S322: Based on a preset channel priority strategy and the signal quality and connection status of all currently available wide-area wireless communication links, select one or more links from all available wide-area wireless communication links as uplink communication channels. The channel priority strategy refers to a predefined set of rules used to sort and select communication links of different types and statuses; the uplink communication channel refers to the network path ultimately selected to send data to the server. Specifically, the system reads the preset channel priority strategy, which may specify, for example, "priority order: 5G network > 4G network > connected Wi-Fi > others"; the system sorts all available links detected in step S321 according to their type and queried status parameters, following the priority strategy; during the sorting process, if the status parameters of a link do not meet basic communication requirements (e.g., cellular network signal strength is below a threshold or there is no data carrying capacity), it is excluded from the candidate list; from the sorted candidate list, the first link with the highest priority and available status is selected as the primary uplink communication channel; depending on the configuration, the first two links can also be selected simultaneously as primary and backup channels.

[0071] Step S323: Send the aggregated location information and the event session information to the server through the uplink communication channel.

[0072] The method provided in this embodiment first comprehensively assesses the current availability of network transmission resources by detecting the signal quality and connection status of all available wide-area wireless communication links. Then, based on a preset channel priority strategy and real-time link status, it intelligently selects one or more optimal uplink communication channels from the available resources. Finally, it sends aggregated location information and event session information to the server through the selected uplink communication channel, completing the last crucial data transmission step in the entire collaborative reporting process. This process achieves dynamic optimization of the reporting channel, adapting to changing network environments and ensuring reporting success rate and timeliness while also considering the economy and reliability of data transmission.

[0073] This application embodiment also provides a collaborative location reporting system, the system including multiple member devices, the collaborative location reporting system being used to implement: When a triggering device detects a preset emergency event, it generates a collaborative discovery beacon frame and sends the collaborative discovery beacon frame to each responding device within the effective collaborative area; wherein, the triggering device is any one of the member devices, and the responding device is one or more of the remaining member devices other than the triggering device, and the collaborative discovery beacon frame includes the first location information of the triggering device and the event session information corresponding to the preset emergency event; The response device generates response data information based on the cooperative discovery beacon frame and sends the response data information to the triggering device; wherein, the response data information includes the second location information of the response device; The triggering device generates aggregated location information based on the first location information and each of the second location information, and sends the aggregated location information and the event session information to the server.

[0074] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the system described above can be referred to the process in the aforementioned embodiment of the distributed location information aggregation and reporting method based on group collaboration, and will not be repeated here.

[0075] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A distributed location information aggregation and reporting method based on group collaboration, characterized in that, For a collaborative location reporting system, the system comprising multiple member devices, the method includes: When a triggering device detects a preset emergency event, it generates a collaborative discovery beacon frame and sends the collaborative discovery beacon frame to each responding device within the effective collaborative area; wherein, the triggering device is any one of the member devices, and the responding device is one or more of the remaining member devices other than the triggering device, and the collaborative discovery beacon frame includes the first location information of the triggering device and the event session information corresponding to the preset emergency event; The response device generates response data information based on the cooperative discovery beacon frame and sends the response data information to the triggering device; wherein, the response data information includes the second location information of the response device; The triggering device generates aggregated location information based on the first location information and each of the second location information, and sends the aggregated location information and the event session information to the server.

2. The distributed location information aggregation and reporting method based on group collaboration according to claim 1, characterized in that, When the triggering device detects a preset emergency event, it generates a cooperative discovery beacon frame, including: Continuously monitor the data acquisition information from the built-in sensors and the status of the command interface; When the data collection information matches the preset abnormal information, or when the command interface receives an alarm command triggered by the user, it is determined that a preset emergency event has been detected. The positioning module acquires first location information including geographic coordinates, positioning timestamp, and estimated positioning accuracy; generates a globally unique event session identifier composed of a trigger device code and a random number, and generates an event type for the emergency event based on the data acquisition information or the alarm command triggered by the user; wherein, the event session identifier and the event type constitute the event session information; The first location information and the event session information are encapsulated to form the collaborative discovery beacon frame.

3. The distributed location information aggregation and reporting method based on group collaboration according to claim 2, characterized in that, The event types that generate emergency events based on the data collection information or user-triggered alarm commands include: When it is determined that an emergency event is triggered by the data acquisition information, the data acquisition information is matched with multiple preset sensor anomaly patterns, and the event type associated with the sensor anomaly pattern that is successfully matched with the data acquisition information is determined as the event type of the current emergency event. When it is determined that an emergency event is triggered by an alarm command initiated by the user, a predefined command code is parsed from the alarm command received from the command interface, and the command code is mapped to the corresponding event type based on a preset command code-event type mapping relationship.

4. The distributed location information aggregation and reporting method based on group collaboration according to claim 2, characterized in that, The triggering device sends the cooperative discovery beacon frame to each responding device within the effective cooperative area, including: A communication distance threshold is determined based on the event type, and an effective cooperation area is determined based on the communication distance threshold; The cooperative discovery beacon frame is broadcast to each responding device within the effective cooperative area.

5. The distributed location information aggregation and reporting method based on group collaboration according to claim 2, characterized in that, The response device generates response data information based on the collaborative discovery beacon frame, including: determining whether to perform a collaborative response to the event type based on a locally preset response strategy configuration file; if a collaborative response is determined, obtaining second location information through a positioning module; and encapsulating its corresponding response device code, the second location information, and the event session identifier to generate the response data information.

6. The distributed location information aggregation and reporting method based on group collaboration according to claim 5, characterized in that, The determination of whether to coordinate a response to the event type based on the locally preset response strategy configuration file includes: Based on the event type, a matching query is performed in the response strategy configuration file to obtain the response rule corresponding to the event type; Obtain the current status parameters of the response device; the current status parameters include at least battery level and CPU load rate; The current state parameter is compared with the execution condition threshold in the acquired response rule; When the queried response rule indicates that the response is allowed or forced, and the current status parameter meets the execution condition threshold, it is determined to perform a coordinated response to the event type.

7. The distributed location information aggregation and reporting method based on group collaboration according to claim 4, characterized in that, The triggering device generates aggregated location information based on the first location information and each of the second location information, including: While broadcasting the collaborative discovery beacon frame, a data receiving window with a preset duration is opened; within the data receiving window, the device gathers its own first location information and response data information containing second location information received from each responding device; using the reciprocal of the estimated positioning accuracy value in each location information as a weight, a weighted average is calculated for the geographic coordinates of all location information to obtain the aggregation center coordinates; a minimum boundary rectangle is calculated based on the geographic coordinates of all location information; the minimum boundary rectangle is the smallest rectangular area that can cover all the geographic coordinates; the aggregation center coordinates, the minimum boundary rectangle, the total number of participating member devices, and all original location information are integrated to generate the aggregated location information.

8. The distributed location information aggregation and reporting method based on group collaboration according to claim 7, characterized in that, The calculation of the minimum boundary rectangle based on geographic coordinates of all location information includes: Extract geographic coordinates from each location information; Determine the minimum and maximum longitude values ​​among the longitude values ​​corresponding to each geographic coordinate point, and determine the minimum and maximum latitude values ​​among the latitude values ​​corresponding to each geographic coordinate point; The coordinates of the lower left vertex of the minimum boundary rectangle are determined based on the minimum longitude and the minimum latitude. The coordinates of the upper right corner vertex of the minimum boundary rectangle are determined based on the maximum longitude value and the maximum latitude value; The minimum boundary rectangle is determined based on the coordinates of the lower left corner vertex and the upper right corner vertex.

9. The distributed location information aggregation and reporting method based on group collaboration according to claim 1, characterized in that, The triggering device sends the aggregated location information and the event session information to the server, including: Detect the signal quality and connection status of all currently available wide-area wireless communication links; Based on a preset channel priority strategy and the signal quality and connection status of all currently available wide-area wireless communication links, one or more links are selected from all available wide-area wireless communication links as uplink communication channels; the aggregated location information and the event session information are sent to the server through the uplink communication channels.

10. A collaborative location reporting system, the system comprising multiple member devices, characterized in that, include: When a triggering device detects a preset emergency event, it generates a collaborative discovery beacon frame and sends the collaborative discovery beacon frame to each responding device within the effective collaborative area; wherein, the triggering device is any one of the member devices, and the responding device is one or more of the remaining member devices other than the triggering device, and the collaborative discovery beacon frame includes the first location information of the triggering device and the event session information corresponding to the preset emergency event; The response device generates response data information based on the cooperative discovery beacon frame and sends the response data information to the triggering device; wherein, the response data information includes the second location information of the response device; The triggering device generates aggregated location information based on the first location information and each of the second location information, and sends the aggregated location information and the event session information to the server.

Images