Collaborative data acquisition method and system and vehicle

Abstract

The invention provides a collaborative data acquisition method and system and a vehicle. The collaborative data acquisition method comprises the following steps: in response to a sentry mode trigger signal of a target vehicle, sending a collaborative acquisition request to all vehicles in a preset range through the target vehicle; wherein the vehicle receiving the collaborative acquisition request is used as a collaborative vehicle; then cooperative verification is executed through the cooperative vehicle, and when the cooperative verification is passed, vehicle recording data in a preset time period is sent to the target vehicle; and further collecting the vehicle recording data and the current recording data through the target vehicle to obtain target recording data. The method can achieve the full coverage of a scene, and can effectively avoid the interference of the current visual angle or ambient light of the target vehicle. Meanwhile, image information from multiple visual angles can be integrated to form more comprehensive and complete target recording data, so that the subsequent process of the event is completely restored.

Description

Technical Field

[0001] This application relates to the field of data acquisition technology, and in particular to a collaborative data acquisition method, system and vehicle. Background Technology

[0002] Sentry mode is an important safety feature that is gradually becoming a standard feature in many vehicles. It uses a series of cameras and sensors on the vehicle to monitor abnormal behavior around the vehicle. When abnormalities such as collisions or suspicious persons approaching are detected, it will quickly trigger the recording function to provide traceable data for the owner in case of an accident.

[0003] However, despite the significant role that Sentinel mode plays in vehicle safety, there are still some issues with the footage it records that need to be addressed.

[0004] (1) Due to the limitations of the installation location and viewing angle, the cameras on vehicles inevitably have certain blind spots. At present, most vehicle cameras are mainly concentrated around the vehicle body, while the monitoring of the roof and under the vehicle is relatively weak. In real life, the roof area may be hit by falling objects from above, and the under the vehicle area may be hit by animals or foreign objects. Since the cameras cannot cover the roof and under the vehicle area, once an abnormal situation occurs in these areas, the cameras will not be able to capture the relevant images, and the car owner will lose the possibility of tracing the cause of the incident and determining responsibility.

[0005] (2) Ambient light conditions have a significant impact on the image quality captured by the camera. For example, in poor lighting conditions, the images captured by the camera often have problems such as being blurry, too dark, or overexposed; this not only affects the driver's identification and judgment of the image content, but may also make it impossible to see the facial features of suspicious persons, license plate numbers, and other key information.

[0006] (3) When the sentry mode is triggered, although it can record the images of the event, it cannot track the whereabouts of the person who triggered the sentry mode. In some cases, suspicious persons may flee the scene quickly after triggering the sentry mode, and the vehicle's camera can only record their brief activities around the vehicle and cannot provide information on their whereabouts after they leave. This makes it impossible to fully reconstruct the subsequent process of the event.

[0007] These issues limit the effectiveness of Sentry Mode. When encountering a vehicle accident, the driver may not receive comprehensive and accurate video footage, affecting the handling of the incident and the determination of liability. Summary of the Invention

[0008] This application provides a collaborative data acquisition method, system, and vehicle to solve the aforementioned technical problems.

[0009] Specifically, this application provides a collaborative data acquisition method, comprising the following steps: in response to a sentry mode trigger signal of a target vehicle, sending a collaborative acquisition request to all vehicles within a preset range through the target vehicle; wherein, the vehicles receiving the collaborative acquisition request are designated as collaborative vehicles; performing collaborative verification through the collaborative vehicles, so that when the collaborative verification passes, vehicle recording data within a preset time period is sent to the target vehicle; and, aggregating the vehicle recording data with the current recording data through the target vehicle to obtain target recording data.

[0010] The above technical solution eliminates blind spots in the target vehicle's blind spots, achieving full scene coverage. It allows for viewing the vehicle from a third-party perspective, increasing the likelihood of seeing the roof and underside. Furthermore, it effectively avoids interference from the target vehicle's current viewpoint or ambient light, resulting in clearer and more comprehensive image data. Simultaneously, it integrates vehicle recording data sent by collaborating vehicles with the target vehicle's own current recording data, consolidating image information from multiple perspectives to form a more comprehensive and complete target recording data. This enables the capture of the object's whereabouts and a complete reconstruction of the subsequent events. Moreover, this application requires no major hardware modifications to the vehicle; only software upgrades are needed to ensure the vehicle adheres to relevant collaborative acquisition protocols, enabling collaborative data acquisition. In short, this application provides strong protection for vehicle safety and efficiently enhances the functionality of the sentry mode at low cost.

[0011] Furthermore, the collaborative data collection request includes at least the vehicle identifier, trigger timestamp, and real-time vehicle location.

[0012] In the above technical solution, the vehicle identifier is a unique identifier for the target vehicle. The collaborating vehicle can accurately identify which target vehicle sent the collaborative data collection request through the vehicle identifier, ensuring that the data is accurately sent to the target vehicle. The trigger timestamp records the specific time when the target vehicle's sentry mode is triggered. The collaborating vehicle can determine which time period of recording data needs to be provided based on this timestamp, avoiding the provision of a large amount of irrelevant recording data and improving the efficiency of data transmission. Real-time vehicle positioning allows the collaborating vehicle to know the location of the target vehicle. Based on its own location and the real-time positioning of the target vehicle, the collaborating vehicle can determine whether it is in a suitable location to provide collaborative data collection services to the target vehicle, providing an important basis for subsequent collaborative verification.

[0013] Furthermore, the collaborative verification includes at least one verification and a second verification; before performing the collaborative verification, it also includes: determining whether the current collaborative vehicle has performed a collaborative data collection within a set time range; if so, then performing the first verification; otherwise, ignoring the collaborative data collection request.

[0014] In the above technical solution, if the collaborative vehicles frequently perform collaborative data collection tasks in a short period of time, it will lead to excessive consumption of vehicle resources (such as power consumption) and affect the normal operation of the vehicles. By judging whether the current collaborative vehicle has performed collaborative data collection once within the set time range, it is possible to avoid the collaborative vehicles from participating in collaborative collection tasks excessively and ensure the rational use of vehicle resources. Only vehicles that have not performed collaborative data collection tasks within the set time range are likely to participate in collaborative collection. This can filter out vehicles with sufficient resources and capabilities to provide effective collaborative collection services to the target vehicle, thereby improving the efficiency and quality of collaborative collection.

[0015] Furthermore, the first verification includes: determining whether the current collaborative vehicle is in sentry mode; if so, performing a second verification; otherwise, ignoring the collaborative data collection request.

[0016] In the above technical solution, the collaborative vehicle in sentry mode will continuously record image data of the surrounding environment. Only when the collaborative vehicle is in sentry mode can it provide valid recorded data within the sentry mode trigger time period of the target vehicle. If the collaborative vehicle is not in sentry mode, its recorded data may be incomplete or inaccurate and cannot provide valuable information for the target vehicle. Therefore, ignoring the collaborative acquisition request can avoid invalid data transmission.

[0017] Furthermore, the secondary verification includes: determining whether the actual distance between the current cooperating vehicle and the target vehicle is less than or equal to a preset distance based on the real-time positioning of the vehicle; if so, the cooperation verification is deemed successful; otherwise, the cooperation collection request is ignored.

[0018] In the above technical solution, the closer the collaborative vehicle is to the target vehicle, the greater the coverage and supplementation effect of the recorded data on the surrounding scene of the target vehicle. By judging whether the actual distance is less than or equal to the preset distance, it can be ensured that the collaborative vehicle is close enough to the target vehicle, and the recorded data can be related to the scene of the target vehicle, providing effective supplementary information for the target vehicle. If the collaborative vehicle is too far away from the target vehicle, the recorded data may not be of much reference value to the surrounding scene of the target vehicle. Ignoring the collaborative collection requests of collaborative vehicles that are too far away can reduce unnecessary data transmission, reduce network bandwidth occupation, and improve data transmission efficiency.

[0019] Furthermore, the step of sending vehicle recording data within a preset time period to the target vehicle includes: obtaining vehicle recording data within a preset time period based on the trigger timestamp, and sending the vehicle recording data to the target vehicle based on the vehicle identifier.

[0020] In the above technical solution, based on the trigger timestamp, the collaborative vehicle can accurately obtain the recorded data within a preset time period before and after the target vehicle's sentry mode is triggered, avoiding the provision of a large amount of irrelevant recorded data and improving the relevance and effectiveness of the data; through vehicle identification, the collaborative vehicle can accurately send the recorded data to the target vehicle, ensuring the accuracy and reliability of data transmission.

[0021] Furthermore, after obtaining the target recording data, the method also includes storing the target recording data.

[0022] In the above technical solution, after the target recording data is stored, the vehicle owner or relevant personnel can query and use this data at any time when needed. For example, in the event of a vehicle accident or dispute, the stored target recording data can be retrieved as evidence to help determine the responsible party and resolve the problem. In addition, timely storage of target recording data can also prevent data loss or damage. Even if the current recording data of the target vehicle is lost for some reason, the stored target recording data can still provide relevant information at the time of the event, providing more reliable protection for vehicle safety.

[0023] Based on the same concept, this application also provides a collaborative data acquisition system, the system comprising: a request module, configured to send a collaborative acquisition request to all vehicles within a preset range in response to a sentry mode trigger signal of a target vehicle; wherein, vehicles receiving the collaborative acquisition request are designated as collaborative vehicles; a verification and acquisition module, configured to perform collaborative verification when a vehicle is designated as a collaborative vehicle, and after successful collaborative verification, send vehicle recording data within a preset time period to the target vehicle; and a receiving module, configured to aggregate the vehicle recording data with the current recording data to obtain the target recording data.

[0024] In the above technical solution, vehicles equipped with sentry mode and cooperative communication functions can be used as target vehicles or cooperative vehicles, and the cooperative data acquisition system configured in each vehicle is the same. The cooperative data acquisition system can effectively eliminate blind spots in the environment where the target vehicle is located, achieve full scene coverage, and obtain multi-view recording data through cooperative vehicles in different locations. While avoiding the limitations of the current perspective, it can also effectively ensure the integrity of the monitoring events, thereby ensuring vehicle safety.

[0025] Furthermore, the system also includes a storage module for storing the target recording data.

[0026] In the above technical solution, by storing the target recording data, users can not only easily retrieve it at any time, but also prevent the loss of vehicle recording data, so that relevant information about the event can still be extracted.

[0027] Based on the same concept, this application also provides a vehicle equipped with a collaborative data acquisition system to achieve collaborative data acquisition in sentry mode using the aforementioned collaborative data acquisition method.

[0028] Compared with the prior art, the beneficial effects of this application are as follows: This application can achieve full coverage of the scene and effectively avoid interference from the target vehicle's current perspective or ambient light; at the same time, it can integrate image information from multiple perspectives to form a more comprehensive and complete target recording data, thereby fully restoring the subsequent process of the event. Attached Figure Description

[0029] Figure 1 This is a flowchart of the collaborative data acquisition method described in this application.

[0030] Figure 2 This is a framework diagram of the collaborative data acquisition system described in this application.

[0031] Figure 3 This is a schematic diagram of the system communication between vehicles described in this application. Detailed Implementation

[0032] The following describes in further detail a collaborative data acquisition method, system, and vehicle of this application, with reference to specific embodiments and accompanying drawings.

[0033] Please see Figure 1 This application provides a collaborative data acquisition method, including the following steps S100-S300.

[0034] In one feasible implementation, when the target vehicle's sentry mode is triggered, the target vehicle immediately initiates a collaborative data acquisition process: It sends a "collaborative acquisition request" to all vehicles within a 10-meter radius of the target vehicle via an onboard communication module (such as Bluetooth, UWB, or V2X). Upon receiving the "collaborative acquisition request," the collaborating vehicle determines whether it is currently in sentry mode (only vehicles in sentry mode have data acquisition capabilities) and whether the actual distance between the collaborating vehicle and the target vehicle is within, for example, 10 meters. If all conditions are met, the collaborating vehicle's sentry mode recording function is triggered. Once the collaborating vehicle completes data acquisition, it automatically sends the data to the target vehicle. The target vehicle receives the data and stores it in the same location as the data it recorded.

[0035] The specific implementation methods of steps S100-S300 will be described in detail below.

[0036] Step S100: In response to the sentry mode trigger signal of the target vehicle, a collaborative acquisition request is sent from the target vehicle to all vehicles within a preset range; wherein, the vehicle that receives the collaborative acquisition request is designated as the collaborative vehicle.

[0037] The collaborative data collection request includes at least the vehicle identifier, trigger timestamp, and real-time vehicle location.

[0038] In some embodiments, assuming the target vehicle is currently in a parking lot, when its sensors detect an abnormal event (such as the vehicle being hit), the sentry mode is triggered, and then immediately a collaborative collection request is sent to vehicles within a preset range (such as within a 10-meter radius centered on the target vehicle) via an in-vehicle communication module (such as Bluetooth, UWB, or V2X). Assuming that multiple other vehicles in the current parking lot receive the collaborative collection request, these vehicles will become collaborative vehicles.

[0039] Preferably, the vehicle identifier is such as a license plate number, the timestamp indicates the time that triggers the sentry mode to the second, and the real-time vehicle location is such as the latitude and longitude information of the target vehicle.

[0040] Furthermore, those skilled in the art can set the preset range according to actual application needs, and it is not limited to only one of the above.

[0041] In the above technical solution, the vehicle identifier is a unique identifier for the target vehicle. The collaborating vehicle can accurately identify which target vehicle sent the collaborative data collection request through the vehicle identifier, ensuring that the data is accurately sent to the target vehicle. The trigger timestamp records the specific time when the target vehicle's sentry mode is triggered. The collaborating vehicle can determine which time period of recording data needs to be provided based on this timestamp, avoiding the provision of a large amount of irrelevant recording data and improving the efficiency of data transmission. Real-time vehicle positioning allows the collaborating vehicle to know the location of the target vehicle. Based on its own location and the real-time positioning of the target vehicle, the collaborating vehicle can determine whether it is in a suitable location to provide collaborative data collection services to the target vehicle, providing an important basis for subsequent collaborative verification.

[0042] Step S200: Perform collaborative verification through the collaborative vehicle, so that when the collaborative verification is successful, the vehicle recording data within a preset time period is sent to the target vehicle.

[0043] The collaborative verification includes at least one verification and two verifications. Before performing the collaborative verification, it also includes: determining whether the current collaborative vehicle has performed a collaborative data collection within a set time range. If so, the one-time verification is performed; otherwise, the collaborative data collection request is ignored.

[0044] In some embodiments, assuming that multiple vehicles have received a collaborative data collection request, each vehicle will self-verify whether it has performed collaborative data collection within a set time range (e.g., 4 hours). If it has, the collaborative data collection request will be ignored. If the vehicle log is queried and it is determined that the current collaborative vehicle has not performed collaborative data collection within the set time range, the next verification process can be executed.

[0045] It should be noted that each time a collaborative data collection request is received, the vehicle records the relevant information from the request to facilitate determining whether the vehicle has already performed collaborative data collection and to trace the specific details of the entire system's data collection process. Furthermore, those skilled in the art can set the specified time range according to actual application needs, and it is not limited to the one described above.

[0046] In the above technical solution, if the collaborative vehicles frequently perform collaborative data collection tasks in a short period of time, it will lead to excessive consumption of vehicle resources (such as power consumption) and affect the normal operation of the vehicles. By judging whether the current collaborative vehicle has performed collaborative data collection once within the set time range, it is possible to avoid the collaborative vehicles from participating in collaborative collection tasks excessively and ensure the rational use of vehicle resources. Only vehicles that have not performed collaborative data collection tasks within the set time range are likely to participate in collaborative collection. This can filter out vehicles with sufficient resources and capabilities to provide effective collaborative collection services to the target vehicle, thereby improving the efficiency and quality of collaborative collection.

[0047] Furthermore, the first verification includes: determining whether the current collaborative vehicle is in sentry mode; if so, performing a second verification; otherwise, ignoring the collaborative data collection request.

[0048] In some embodiments, the cooperative vehicle in sentry mode continuously records image data of the surrounding environment. Only when the cooperative vehicle is in sentry mode can it provide valid recorded data within the sentry mode trigger time period of the target vehicle. If the cooperative vehicle is not in sentry mode, its recorded data may be incomplete or inaccurate and cannot provide valuable information to the target vehicle. Therefore, ignoring the cooperative acquisition request can avoid invalid data transmission.

[0049] Furthermore, the secondary verification includes: determining whether the actual distance between the current cooperating vehicle and the target vehicle is less than or equal to a preset distance based on the real-time positioning of the vehicle; if so, the cooperation verification is deemed successful; otherwise, the cooperation collection request is ignored.

[0050] In some embodiments, the actual distance between the target vehicle and the cooperating vehicle is calculated and determined by the vehicle-mounted GPS or Beidou positioning module. If it is within a range of 10 meters, the cooperation verification is considered successful and data collection can be performed; otherwise, it is ignored to filter out invalid requests that are outside the range.

[0051] It should be noted that those skilled in the art can set the actual distance judgment standard (preset distance) according to actual application needs, and are not limited to only the one mentioned above.

[0052] In the above technical solution, the closer the collaborative vehicle is to the target vehicle, the greater the coverage and supplementation effect of the recorded data on the surrounding scene of the target vehicle. By judging whether the actual distance is less than or equal to the preset distance, it can be ensured that the collaborative vehicle is close enough to the target vehicle, and the recorded data can be related to the scene of the target vehicle, providing effective supplementary information for the target vehicle. If the collaborative vehicle is too far away from the target vehicle, the recorded data may not be of much reference value to the surrounding scene of the target vehicle. Ignoring the collaborative collection requests of collaborative vehicles that are too far away can reduce unnecessary data transmission, reduce network bandwidth occupation, and improve data transmission efficiency.

[0053] Furthermore, the step of sending vehicle recording data within a preset time period to the target vehicle includes: obtaining vehicle recording data within a preset time period based on the trigger timestamp, and sending the vehicle recording data to the target vehicle based on the vehicle identifier.

[0054] In some embodiments, a preset time period, such as the 10 seconds before and 50 seconds after the trigger timestamp, is used to collect vehicle recording data during that time period. Based on the vehicle identifier in the received collaborative collection request, the data is automatically sent back to the target vehicle through the vehicle communication module.

[0055] It should be noted that those skilled in the art can set the preset time period according to actual application needs, and are not limited to the above-mentioned setting.

[0056] In the above technical solution, based on the trigger timestamp, the collaborative vehicle can accurately obtain the recorded data within a preset time period before and after the target vehicle's sentry mode is triggered, avoiding the provision of a large amount of irrelevant recorded data and improving the relevance and effectiveness of the data; through vehicle identification, the collaborative vehicle can accurately send the recorded data to the target vehicle, ensuring the accuracy and reliability of data transmission.

[0057] Step S300: Combine the vehicle recording data with the current recording data using the target vehicle to obtain the target recording data.

[0058] Furthermore, after obtaining the target recording data, the method also includes storing the target recording data.

[0059] In some embodiments, the target vehicle integrates the received vehicle recording data and its own current recording data, and then stores them in a local mass storage device. Typically, a filename with time and event description is automatically generated for easy retrieval later.

[0060] In the above technical solution, after the target recording data is stored, the vehicle owner or relevant personnel can query and use this data at any time when needed. For example, in the event of a vehicle accident or dispute, the stored target recording data can be retrieved as evidence to help determine the responsible party and resolve the problem. In addition, timely storage of target recording data can also prevent data loss or damage. Even if the current recording data of the target vehicle is lost for some reason, the stored target recording data can still provide relevant information at the time of the event, providing more reliable protection for vehicle safety.

[0061] In summary, the collaborative data acquisition method described in this application can eliminate blind spots of the target vehicle, achieving full scene coverage. It allows viewing the vehicle from a third-party perspective, increasing the likelihood of seeing the roof and under the vehicle. Furthermore, it effectively avoids interference from the target vehicle's current perspective or ambient light, resulting in clearer and more comprehensive image data. Simultaneously, it can aggregate vehicle recording data sent by collaborating vehicles with the target vehicle's own current recording data to integrate image information from multiple perspectives, forming a more comprehensive and complete target recording data. This enables the capture of the object's whereabouts and a complete reconstruction of the subsequent events. Moreover, this application requires no major hardware modifications to the vehicle; only software upgrades are needed to ensure the vehicle adheres to the relevant collaborative acquisition protocol, thus enabling collaborative data acquisition. In short, this application provides strong protection for vehicle safety and efficiently enhances the functionality of the sentry mode at low cost.

[0062] Based on the same concept, please refer to Figure 2 This application also provides a collaborative data acquisition system, the system comprising: a request module, configured to send a collaborative acquisition request to all vehicles within a preset range in response to a sentry mode trigger signal of a target vehicle; wherein, vehicles receiving the collaborative acquisition request are designated as collaborative vehicles; a verification and acquisition module, configured to perform collaborative verification when a vehicle is designated as a collaborative vehicle, and send vehicle recording data within a preset time period to the target vehicle after successful collaborative verification; and a receiving module, configured to aggregate the vehicle recording data with the current recording data to obtain the target recording data.

[0063] In some embodiments, the target vehicle's request module sends a collaborative collection request to all vehicles within a radius of 10 meters centered on the vehicle via a relevant communication module (such as Bluetooth, UWB, or V2X). The vehicle that receives the collaborative collection request is the collaborative vehicle.

[0064] Furthermore, the verification and data acquisition module of the collaborative vehicle will sequentially execute the verification process, including: determining whether the current collaborative vehicle has already performed collaborative data acquisition within a set time range; if so, ignoring this collaborative data acquisition to save the vehicle's battery power and other energy consumption; otherwise, determining whether the vehicle is in sentry mode; if so, determining whether the actual distance between the vehicle and the target vehicle that sent the collaborative data acquisition request is within, for example, 10 meters; if so, triggering the vehicle's sentry mode recording function to obtain the vehicle recording data for the 10 seconds before and 50 seconds after the trigger timestamp carried in the collaborative data acquisition request sent by the target vehicle; then, based on the vehicle identifier carried in the collaborative data acquisition request, sending it to the target vehicle's receiving module through the corresponding communication module, so that the target vehicle's receiving module can integrate the received vehicle recording data with its own current recording data. The collaborative data acquisition request will also carry the real-time location of the target vehicle to facilitate distance determination by the collaborative vehicle.

[0065] If the cooperating vehicle is not in sentry mode, or if the actual distance to the target vehicle is greater than 10 meters, it is considered that the conditions for collaborative data collection are not met, and the collaborative data collection request is ignored.

[0066] In the above technical solution, vehicles equipped with sentry mode and cooperative communication functions can be used as target vehicles or cooperative vehicles, and the cooperative data acquisition system configured in each vehicle is the same. The cooperative data acquisition system can effectively eliminate blind spots in the environment where the target vehicle is located, achieve full scene coverage, and obtain multi-view recording data through cooperative vehicles in different locations. While avoiding the limitations of the current perspective, it can also effectively ensure the integrity of the monitoring events, thereby ensuring vehicle safety.

[0067] Furthermore, the system also includes a storage module for storing the target recording data.

[0068] In some embodiments, the receiving module of the target vehicle aggregates the vehicle recording data and the current recording data, and then sends the aggregated result to the storage module for storage.

[0069] In the above technical solution, by storing the target recording data, users can not only easily retrieve it at any time, but also prevent the loss of vehicle recording data, so that relevant information about the event can still be extracted.

[0070] Based on the same concept, please refer to Figure 3This application also provides a vehicle equipped with a collaborative data acquisition system to achieve collaborative data acquisition in sentry mode using the aforementioned collaborative data acquisition method.

[0071] Among them, any vehicle equipped with sentry mode and wireless communication capabilities can serve as a target vehicle or a cooperative vehicle.

[0072] Although exemplary embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above exemplary embodiments are merely illustrative and are not intended to limit the scope of this application. Various changes and modifications can be made therein by those skilled in the art without departing from the scope and spirit of this application. All such changes and modifications are intended to be included within the scope of this application as claimed in the appended claims.

[0073] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0074] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed.

[0075] The various component embodiments of this application can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some modules according to the embodiments of this application. This application can also be implemented as an apparatus program (e.g., a computer program and computer program product) for performing part or all of the methods described herein. Such an implementation of this application can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0076] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. 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 limitations, 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.

[0077] Although the description of this application has been made in conjunction with the specific embodiments described above, it will be apparent to those skilled in the art that many substitutions, modifications, and variations can be made based on the foregoing. Therefore, all such substitutions, modifications, and variations are included within the spirit and scope of the appended claims.

Claims

1. A collaborative data acquisition method, characterized in that, Includes the following steps: In response to the sentry mode trigger signal of the target vehicle, a collaborative acquisition request is sent from the target vehicle to all vehicles within a preset range; wherein, the vehicle that receives the collaborative acquisition request is designated as the collaborative vehicle. The collaborative verification is performed by the collaborative vehicle, so that when the collaborative verification is successful, the vehicle recording data within a preset time period is sent to the target vehicle; Additionally, the vehicle recording data is aggregated with the current recording data using the target vehicle to obtain the target recording data.

2. The collaborative data acquisition method according to claim 1, characterized in that, The collaborative data collection request includes at least the vehicle identifier, trigger timestamp, and real-time vehicle location.

3. The collaborative data acquisition method according to claim 2, characterized in that, The collaborative verification includes at least one verification and a second verification; prior to performing collaborative verification, it also includes: Determine whether the currently cooperating vehicle has already performed a collaborative data collection within a set time range. If so, perform the verification; otherwise, ignore the collaborative data collection request.

4. The collaborative data acquisition method according to claim 3, characterized in that, The verification includes: Determine whether the currently cooperating vehicle is in sentry mode. If so, perform secondary verification; otherwise, ignore the cooperative data collection request.

5. The collaborative data acquisition method according to claim 4, characterized in that, The secondary verification includes: Based on the real-time vehicle positioning, it is determined whether the actual distance between the current cooperating vehicle and the target vehicle is less than or equal to a preset distance. If so, the cooperation verification is deemed successful; otherwise, the cooperation data collection request is ignored.

6. The collaborative data acquisition method according to claim 2, characterized in that, Sending vehicle recording data within a preset time period to the target vehicle includes: Based on the trigger timestamp, obtain vehicle recording data within a preset time period, and send the vehicle recording data to the target vehicle based on the vehicle identifier.

7. The collaborative data acquisition method according to claim 1, characterized in that, After obtaining the target recording data, the following is also included: The target recording data is stored.

8. A system employing the collaborative data acquisition method as described in any one of claims 1-7, characterized in that, The system includes: The request module is used to send a collaborative data collection request to all vehicles within a preset range in response to the sentry mode trigger signal of the target vehicle; among them, the vehicles that receive the collaborative data collection request are designated as collaborative vehicles. The verification and acquisition module is used to perform collaborative verification when the vehicle is used as a collaborative vehicle, and after the collaborative verification is passed, to send the vehicle recording data within a preset time period to the target vehicle; The receiving module is used to combine the vehicle recording data with the current recording data to obtain the target recording data.

9. The system according to claim 8, characterized in that, Also includes: The storage module is used to store the target recording data.

10. A vehicle, characterized in that, The system is equipped with a collaborative data acquisition system to achieve collaborative data acquisition in sentinel mode using the collaborative data acquisition method as described in any one of claims 1-7.

Images