Vehicle data management method and related equipment
By classifying vehicle driving data and prioritizing the deletion of uploaded or not uploaded general data, the problem of important data loss caused by insufficient storage space is solved, and the efficiency of data management and user experience is improved.
Patent Information
- Application Number
- CN202311868081.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-29
- Publication Date
- 2025-07-01
AI Technical Summary
In the prior art, due to limited storage space during vehicle driving, important data is easily covered and lost, affecting the user experience.
The vehicle driving data is classified into uploaded data, general data not uploaded, and important data not uploaded through preset classification rules, and delete the uploaded or unuploaded general data when there is insufficient storage space to ensure that the unuploaded important data is not deleted.
While saving storage space, it avoids the loss of important data and improves the user experience.
Smart Images
Figure CN120236340A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of data storage, and in particular, to a vehicle data management method and related devices. Background Art
[0002] With the popularization of automobiles and the development of camera technology, in order to improve the safety of vehicle driving, many vehicle owners will choose to install a driving recorder in the vehicle to record the scenes around the vehicle during driving. In addition, various sensors installed in the vehicle will also record the status data during vehicle driving, and all these data will be stored in a specific storage space of the vehicle, such as stored in memory or a flash card.
[0003] Due to the limited storage space, it is necessary to perform circular storage on the data recorded during vehicle driving. That is, when the storage space is full, the newly recorded data will automatically overwrite the data with the earliest storage time. However, this method will result in the lack of pertinence of the data stored in the storage space, easily causing the loss of important data during vehicle driving, thus affecting the user experience. Summary of the Invention
[0004] In view of this, this application provides a vehicle data management method and related devices, which can save the storage space of the vehicle database while avoiding the loss of important data recorded during vehicle driving and improving the user experience.
[0005] The first aspect of this application provides a vehicle data management method, including: receiving vehicle driving data and storing the vehicle driving data in the database of the vehicle; determining the category of the vehicle driving data stored in the database according to a preset classification rule, where the category at least includes uploaded data, un-uploaded general data, and un-uploaded important data; when detecting that the remaining storage space of the database is less than or equal to a preset threshold, deleting the vehicle driving data in the database whose category is the uploaded data or the un-uploaded general data according to a preset data deletion rule.
[0006] Compared with the related art, the embodiments of this application have at least the following advantages: By determining the category of vehicle driving data according to a preset classification rule, the vehicle driving data stored in the database can be classified into uploaded data, un-uploaded general data, and un-uploaded important data. When detecting that the remaining storage space of the database is less than or equal to a preset threshold, deleting the vehicle driving data in the database whose category is the uploaded data or the un-uploaded general data can ensure that the un-uploaded important data will not be deleted, save the storage space of the vehicle database while avoiding the loss of important data recorded during vehicle driving, and improve the user experience.
[0007] In some possible implementation manners, determining the category of the vehicle driving data stored in the database according to the preset classification rule includes: detecting whether the vehicle driving data stored in the database is uploaded; classifying the vehicle driving data that has been uploaded to the cloud in the database as the uploaded data, and classifying the vehicle driving data that has not been uploaded to the cloud in the database as the un-uploaded general data or the un-uploaded important data.
[0008] In some possible implementation manners, classifying the vehicle driving data that has not been uploaded to the cloud in the database as the un-uploaded general data or the un-uploaded important data includes: transmitting the vehicle driving data that has not been uploaded to the cloud in the database to a neural network model for data classification; wherein, the neural network model is trained by historical vehicle driving data; according to the output result of the preset data classification model, classifying the vehicle driving data that has not been uploaded to the cloud in the database as the un-uploaded general data or the un-uploaded important data.
[0009] In some possible implementation manners, deleting the vehicle driving data with the category of the uploaded data or the un-uploaded general data in the database according to the preset data deletion rule includes: when there is vehicle driving data with the category of the uploaded data in the database, deleting the vehicle driving data with the category of the uploaded data; when there is no vehicle driving data with the category of the uploaded data in the database, deleting the vehicle driving data with the category of the un-uploaded general data.
[0010] In some possible implementation manners, when there is no uploaded data in the database, deleting the un-uploaded general data includes: determining the storage duration of the un-uploaded general data stored in the database, and preferentially deleting the data with the longest storage duration in the un-uploaded general data.
[0011] In some possible implementation manners, after storing the vehicle driving data in the vehicle's database, the method further includes: uploading the vehicle driving data that is stored in the database first to the cloud according to the time when the vehicle driving data is stored in the database.
[0012] In some possible implementation manners, the vehicle driving data includes vehicle state data and surrounding environment data during the vehicle driving; receiving the vehicle driving data includes: receiving the vehicle state data sent by the vehicle's sensors, and the surrounding environment data captured by the vehicle's camera.
[0013] The second aspect of the present application discloses a vehicle data management device, including: a data collection module, a data classification module, and a data deletion module; the data collection module is configured to receive vehicle driving data and store the vehicle driving data in the vehicle's database; the data classification module is configured to determine the category of the vehicle driving data stored in the database according to a preset classification rule, where the category includes at least uploaded data, un-uploaded general data, and un-uploaded important data; the data deletion module is configured to, when detecting that the remaining storage space of the database is less than or equal to a preset threshold, delete the vehicle driving data in the database whose category is the uploaded data or the un-uploaded general data according to a preset data deletion rule.
[0014] The third aspect of the present application discloses a computer-readable storage medium, including computer instructions, which, when running on an electronic device, cause the electronic device to execute the above-mentioned vehicle data management method.
[0015] The fourth aspect of the present application discloses an electronic device, the electronic device includes a processor and a memory, the memory is used to store instructions, and the processor is used to call the instructions in the memory, so that the electronic device executes the above-mentioned vehicle data management method.
[0016] It can be understood that the vehicle data management device provided in the second aspect, the computer-readable storage medium provided in the third aspect, and the electronic device provided in the fourth aspect all correspond to the method in the first aspect above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be elaborated here. Description of the Drawings
[0017] Figure 1 It is a flowchart of the vehicle data management method provided by an embodiment of the present application;
[0018] Figure 2 It is a schematic diagram of the functional modules of an in-vehicle device provided by an embodiment of the present application;
[0019] Figure 3 It is a schematic diagram of the functional modules of the in-vehicle data collection device provided by an embodiment of the present application;
[0020] Figure 4 It is a flowchart of the vehicle data management method provided by an embodiment of the present application;
[0021] Figure 5 It is a schematic diagram of the functional modules of the vehicle data management device provided by an embodiment of the present application;
[0022] Figure 6 It is a schematic diagram of the hardware structure of the electronic device provided by an embodiment of the present application. Detailed implementation manners
[0023] In order to more clearly understand the above objects, features and advantages of the present application, the present application will be described in detail below with reference to the accompanying drawings and specific implementation manners. It should be noted that, without conflict, the implementation manners of the present application and the features in the implementation manners may be combined with each other.
[0024] In the following description, many specific details are set forth in order to fully understand the present application. The described implementation manners are only a part of the implementation manners of the present application, rather than all of the implementation manners.
[0025] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which the present application belongs. The terms used in the description of the present application herein are only for the purpose of describing specific implementation manners, and are not intended to limit the present application.
[0026] Further, it should be noted that in this document, the term "comprising", "including" or any other variant thereof is intended to cover a non-exclusive inclusion, such that a process, method, article or device including a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the presence of additional identical elements in the process, method, article or device including the element.
[0027] In the present application, "at least one" means one or more, and "a plurality" means two or more than two. "And / or" describes the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B may be singular or plural. The terms "first", "second", "third", "fourth", etc. (if any) in the description, claims and drawings of the present application are used to distinguish similar objects, rather than to describe a specific order or sequence.
[0028] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific manner.
[0029] Please refer to Figure 1 , which is a flowchart of the vehicle data management method provided by the embodiment of the present application. This embodiment is applied to an in-vehicle vehicle data management device, such asFigure 1 As shown, it includes the following steps:
[0030] Step 101: Receive vehicle driving data and store the vehicle driving data in the vehicle's database.
[0031] In some embodiments, the vehicle driving data includes vehicle status data and surrounding environment data during vehicle driving; receiving the vehicle driving data includes: receiving the vehicle status data sent by the vehicle's sensors and the surrounding environment data captured by the vehicle's cameras.
[0032] Please refer to Figure 2 , which is a schematic diagram of the functional modules of the in-vehicle device provided by the embodiment of the present application. The vehicle includes various different sensors such as a vehicle speed sensor, a steering angle sensor, multiple cameras, a G sensor, and a GPS, which can detect and record the vehicle driving state and the environment state, and send this data to the in-vehicle database for storage.
[0033] Specifically, the vehicle driving data includes but is not limited to driving time, geographical location, road type, driving speed, and road condition information, etc.
[0034] In some embodiments, the database can be an in-vehicle memory card or a flash card, etc. The type of the database is not specifically limited in this embodiment.
[0035] For the sake of easy understanding, the following will specifically describe how to store the vehicle driving data in this embodiment in combination with Figure 3 :
[0036] Please refer to Figure 3 , which is a schematic diagram of the functional modules of the in-vehicle data collection device provided by the embodiment of the present application. The data collection device includes a controller and a storage unit. The controller includes a data collector, an instruction receiver, a data selector, and a data transmitter. The data receiver is used to receive vehicle driving data, the instruction receiver is used to receive user instructions, the data selector is used to select the user-specified data from the received vehicle driving data, and the data transmitter is used to transmit the user-specified data; the storage unit includes a sensor database, a vehicle information database, and a tag database. The sensor database is used to store the data sent by the in-vehicle sensors, the vehicle information database is used to store the surrounding environment data captured by the vehicle's cameras, and the tag database is used to store the classified vehicle driving data in the subsequent steps.
[0037] Step 102: Determine the category of the vehicle driving data stored in the database according to the preset classification rules, where the category includes at least uploaded data, un-uploaded general data, and un-uploaded important data.
[0038] In some embodiments, the category of vehicle driving data is determined in the following manner: detecting whether the vehicle driving data stored in the database has been uploaded; classifying the vehicle driving data that has been uploaded to the cloud and stored in the database as uploaded data, and classifying the vehicle driving data that has not been uploaded to the cloud and stored in the database as un-uploaded general data or un-uploaded important data.
[0039] In some embodiments, the vehicle driving data that has not been uploaded to the cloud and stored in the database is transmitted to a neural network model for data classification; wherein, the neural network model is trained with historical vehicle driving data; according to the output result of a preset data classification model, the vehicle driving data that has not been uploaded to the cloud and stored in the database is classified as un-uploaded general data or un-uploaded important data.
[0040] For ease of understanding, the following specifically describes how to implement the classification of vehicle driving data in this embodiment:
[0041] 1. Using analysis models such as an autonomous emergency braking (AEB) system and a blind spot detection (BSD) module of a vehicle, perform data analysis on the vehicle driving data sensed by in-vehicle sensors, thereby determining whether an accident is likely to occur or is about to occur.
[0042] 2. Input the analysis results of the foregoing analysis model, vehicle speed, etc. into the neural network model, and determine the type of the vehicle driving data according to the neural network model. The types include but are not limited to: "in an accident", "about to have an accident", and "will not have an accident". The vehicle driving data corresponding to the types of "in an accident" and "about to have an accident" is used as un-uploaded important data, and the vehicle driving data corresponding to the type of "will not have an accident" is used as un-uploaded general data.
[0043] 3. Input the vehicle driving data detected by a camera and a radar into the neural network model, and determine the type of the vehicle driving data according to the neural network model. The types include but are not limited to: "specific scenario", "non-specific scenario". The vehicle driving data corresponding to the type of "specific scenario" is used as un-uploaded important data, and the vehicle driving data corresponding to the type of "non-specific scenario" is used as un-uploaded general data.
[0044] In some embodiments, the classification method of vehicle driving data is not specifically limited, and the vehicle driving data can be classified according to other methods, as long as it is ensured that the condition of the vehicle during driving can be accurately known through the classification result.
[0045] Step 103: When it is detected that the remaining storage space of the database is less than or equal to a preset threshold, delete the vehicle driving data in the database whose category is uploaded data or un-uploaded general data according to a preset data deletion rule.
[0046] In some embodiments, the size of the preset threshold is not specifically limited and can be set according to actual requirements.
[0047] In some embodiments, vehicle driving data of the category of uploaded data or un-uploaded general data in the database is deleted according to a preset data deletion rule, including: when there is vehicle driving data of the category of uploaded data in the database, deleting the vehicle driving data of the category of uploaded data; when there is no vehicle driving data of the category of uploaded data in the database, deleting the vehicle driving data of the category of un-uploaded general data.
[0048] In some embodiments, when there is no uploaded data in the database, un-uploaded general data is deleted, including: determining the storage duration of the un-uploaded general data stored in the database, and preferentially deleting the data with the longest storage duration among the un-uploaded general data.
[0049] For the convenience of understanding, the vehicle data management method of this embodiment is specifically illustrated by examples as follows:
[0050] During the normal driving process of the vehicle, the vehicle driving data generated in real time is stored in the vehicle's database. The vehicle schedules the upload order according to the time stamp when the vehicle driving data is stored in the database, and the vehicle driving data with an earlier time stamp is uploaded to the cloud with higher priority. However, due to network anomalies, the collected vehicle driving data cannot be quickly uploaded and can only be temporarily stored in the vehicle's database. When the database stores the vehicle driving data, it will classify the vehicle driving data and divide it into uploaded data, un-uploaded general data, and un-uploaded important data.
[0051] After several hours, the vehicle detects that the remaining storage space of the database is less than the preset threshold, that is, the remaining storage space is insufficient. At this time, the vehicle deletes the vehicle driving data of the category of "uploaded data". After several more hours, since the vehicle driving data of the category of "uploaded data" has been completely deleted, but the storage space of the database is still insufficient, the vehicle driving data of the category of "un-uploaded general data" is first deleted to ensure that the storage space of the database is sufficient.
[0052] Compared with the related art, the embodiments of the present application have at least the following advantages: by determining the category of vehicle driving data according to a preset classification rule, the vehicle driving data stored in the database can be classified into uploaded data, un-uploaded general data, and un-uploaded important data. When it is detected that the remaining storage space of the database is less than or equal to the preset threshold, the vehicle driving data of the category of uploaded data or un-uploaded general data in the database is deleted, so as to ensure that the un-uploaded important data will not be deleted, while saving the storage space of the vehicle database and avoiding the loss of important data recorded during the vehicle driving process, thereby improving the user experience.
[0053] Please refer to Figure 4 , which is a flowchart of the vehicle data management method provided in an embodiment of this application. This embodiment is a further improvement on the foregoing embodiment. The main improvement lies in that: in this embodiment, the vehicle driving data that is stored in the database first will be uploaded to the cloud in real time according to the time when the vehicle driving data is stored in the database. In this way, the storage space of the database can be saved as much as possible, thereby further improving the user experience.
[0054] This embodiment is applied to a vehicle data management device, such as Figure 2 shown, and includes the following steps:
[0055] Step 201: Receive vehicle driving data and store the vehicle driving data in the vehicle's database.
[0056] Step 202: According to the time when the vehicle driving data is stored in the database, upload the vehicle driving data that is stored in the database first to the cloud in real time.
[0057] In some embodiments, the vehicle data management device includes a data transmission module. The data transmission module is responsible for transmitting the vehicle driving data on the vehicle to the cloud, managing the upload and download progress, avoiding data loss or too slow upload and download progress, and handling problems such as data congestion or deadlock, to ensure the integrity of the data.
[0058] Step 203: Determine the category of the vehicle driving data stored in the database according to a preset classification rule, where the category at least includes uploaded data, un-uploaded general data, and un-uploaded important data.
[0059] Step 204: When it is detected that the remaining storage space of the database is less than or equal to a preset threshold, delete the vehicle driving data in the database whose category is uploaded data or un-uploaded general data according to a preset data deletion rule.
[0060] Steps 201, 203, and 204 of this embodiment are similar to steps 101 to 103 of the foregoing embodiment. To avoid repetition, they will not be elaborated here.
[0061] Compared with the related art, the embodiments of the present application have at least the following advantages: By determining the category of vehicle driving data according to a preset classification rule, the vehicle driving data stored in the database can be classified into uploaded data, un-uploaded general data, and un-uploaded important data. When it is detected that the remaining storage space of the database is less than or equal to a preset threshold, the vehicle driving data with the category of uploaded data or un-uploaded general data in the database is deleted, so as to ensure that the un-uploaded important data will not be deleted, save the storage space of the vehicle database, avoid the loss of important data recorded during vehicle driving, and improve the user experience.
[0062] Please refer to Figure 5 , which is a schematic diagram of the functional modules of the vehicle data management device provided by the embodiment of the present application. The vehicle data management device 100 includes: a data collection module 1, a data classification module 2, and a data deletion module 3;.
[0063] The data collection module 1 is used to receive vehicle driving data and store the vehicle driving data in the vehicle's database; the data classification module 2 is used to determine the category of the vehicle driving data stored in the database according to a preset classification rule, where the category at least includes uploaded data, un-uploaded general data, and un-uploaded important data; the data deletion module 3 is used to delete the vehicle driving data with the category of uploaded data or un-uploaded general data in the database according to a preset data deletion rule when it is detected that the remaining storage space of the database is less than or equal to a preset threshold.
[0064] Please further refer to Figure 5 , the data classification module 2 includes an anomaly detection unit 21 and a data classification unit 22. The anomaly detection unit 21 is used to perform anomaly detection on vehicle driving data, such as active braking detection, vehicle blind spot detection, etc., and the data classification unit 22 is used to receive the detection result of the anomaly detection unit 21 and output the classification result of the vehicle driving data according to the detection result of the anomaly detection unit 21.
[0065] Please further refer to Figure 5 , the data deletion module 3 includes a storage space detection unit 31 and a data sampling unit 32. The storage space detection unit 31 is used to detect whether the remaining storage space of the database is less than or equal to a preset threshold, and when the remaining storage space of the database is less than or equal to a preset threshold, send a deletion instruction to the data sampling unit 32, and the data sampling unit 32 deletes the vehicle driving data with the category of uploaded data or un-uploaded general data in the database after receiving the deletion instruction.
[0066] Please refer to Figure 6 , which is a schematic diagram of the hardware structure of the electronic device 1000 provided by the embodiment of the present application. As Figure 6As shown, the electronic device 1000 may include a processor 1001 and a memory 1002. The memory 1002 is used to store one or more computer programs 1003. The one or more computer programs 1003 are configured to be executed by the processor 1001. The one or more computer programs 1003 include instructions that can be used to implement the vehicle data management method described above in the electronic device 1000.
[0067] It can be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 1000. In some other embodiments, the electronic device 1000 may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements.
[0068] The processor 1001 may include one or more processing units. For example, the processor 1001 may include an application processor (AP), a modem, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.
[0069] The processor 1001 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 1001 is a cache memory. This memory can save the instructions or data that the processor 1001 has just used or recycled. If the processor 1001 needs to use the instruction or data again, it can directly call it from this memory. This avoids repeated accesses, reduces the waiting time of the processor 1001, and thus improves the efficiency of the system.
[0070] In some embodiments, the processor 1001 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM interface, and / or a USB interface, etc.
[0071] In some embodiments, the memory 1002 may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
[0072] This embodiment also provides a computer-readable storage medium, in which computer instructions are stored. When the instructions are run on an electronic device, the electronic device is enabled to execute the above-mentioned related method steps to implement the vehicle data management method in the above embodiment.
[0073] Among them, the electronic device and the computer storage medium provided in this embodiment are both used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be elaborated here.
[0074] In practical applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
[0075] In several embodiments provided in this application, the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are illustrative. For example, the division of the module or unit is a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in electrical, mechanical, or other forms.
[0076] The unit described as a separate component may or may not be physically separated. The component displayed as a unit may be a physical unit or multiple physical units, that is, it can be located in one place, or it can be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0077] In addition, in each embodiment of this application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
[0078] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on such an understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions to enable a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in each embodiment of this application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs that can store program codes.
[0079] As described above, it is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be covered by the protection scope of this application.
Claims
1. A vehicle data management method, characterized in that, including: Receiving vehicle driving data and storing the vehicle driving data in the vehicle's database; Determining the category of the vehicle driving data stored in the database according to a preset classification rule, where the category at least includes uploaded data, un-uploaded general data, and un-uploaded important data; When it is detected that the remaining storage space of the database is less than or equal to a preset threshold, deleting the vehicle driving data in the database whose category is the uploaded data or the un-uploaded general data according to a preset data deletion rule.
2. The vehicle data management method according to claim 1, characterized in that The determining the category of the vehicle driving data stored in the database according to the preset classification rule includes: Detecting whether the vehicle driving data stored in the database has been uploaded; Classifying the vehicle driving data that has been uploaded to the cloud in the database as the uploaded data, and classifying the vehicle driving data that has not been uploaded to the cloud in the database as the un-uploaded general data or the un-uploaded important data.
3. The vehicle data management method according to claim 2, characterized in that, The classifying the vehicle driving data that has not been uploaded to the cloud in the database as the un-uploaded general data or the un-uploaded important data includes: Transmitting the vehicle driving data that has not been uploaded to the cloud in the database to a neural network model for data classification; where the neural network model is trained by historical vehicle driving data; According to the output result of the preset data classification model, classifying the vehicle driving data that has not been uploaded to the cloud in the database as the un-uploaded general data or the un-uploaded important data.
4. The vehicle data management method according to claim 1, characterized in that The deleting the vehicle driving data in the database whose category is the uploaded data or the un-uploaded general data according to the preset data deletion rule includes: When there is vehicle driving data in the database whose category is the uploaded data, deleting the vehicle driving data whose category is the uploaded data; When there is no vehicle driving data in the database whose category is the uploaded data, deleting the vehicle driving data whose category is the un-uploaded general data.
5. The vehicle data management method according to claim 4, wherein The deleting the un-uploaded general data when there is no uploaded data in the database includes: Determining the storage duration of the un-uploaded general data stored in the database, and preferentially deleting the data with the longest storage duration among the un-uploaded general data.
6. The vehicle data management method according to claim 1, characterized in that, After storing the vehicle driving data in the vehicle's database, the method further includes: According to the time when the vehicle driving data is stored in the database, uploading the vehicle driving data that was first stored in the database to the cloud in real time.
7. The vehicle data management method according to claim 1, wherein The vehicle driving data includes vehicle state data and surrounding environment data during vehicle driving; the receiving the vehicle driving data includes: Receiving the vehicle state data sent by the vehicle's sensors and the surrounding environment data captured by the vehicle's camera.
8. A vehicle data management device, characterized in that, including: A data collection module, a data classification module, and a data deletion module; The data collection module is used to receive vehicle driving data and store the vehicle driving data in the vehicle's database; The data classification module is used to determine the categories of the vehicle driving data stored in the database according to preset classification rules, where the categories at least include uploaded data, un-uploaded general data, and un-uploaded important data; The data deletion module is used to delete the vehicle driving data in the database whose category is the uploaded data or the un-uploaded general data according to preset data deletion rules when it is detected that the remaining storage space of the database is less than or equal to a preset threshold.
9. A computer-readable storage medium, characterized in that, It includes computer instructions that, when the computer instructions run on an electronic device, cause the electronic device to execute the vehicle data management method according to any one of claims 1 to 7.
10. An electronic device, characterized in that, The electronic device includes a processor and a memory. The memory is used to store instructions, and the processor is used to call the instructions in the memory, so that the electronic device executes the vehicle data management method according to any one of claims 1 to 7.