Vehicle event data recording method, system and device and storage medium

Abstract

The invention discloses a vehicle event data recording method, system and device and a storage medium, and the method comprises the steps: confirming a first event type of first vehicle event data, obtaining a first available storage capacity of the first preset storage space, a first uploading state of each piece of second vehicle event data and first vehicle event data generation time, and when the first event type is a serious event and the first available storage capacity is smaller than the first preset available storage capacity, sending the first vehicle event data to the first preset storage space; second vehicle event data uploaded to the cloud storage platform through the vehicle-mounted terminal and earliest in all first vehicle event data generation time are screened out to serve as first to-be-covered vehicle event data, the first vehicle event data are stored in a first preset storage space, the first to-be-covered vehicle event data are covered, and the first to-be-covered vehicle event data are stored in a second preset storage space; and the requirement on the storage space of the local memory is reduced, and the cost of nonvolatile storage is saved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle event data recording, and in particular to a vehicle event data recording method, system, device and storage medium. BACKGROUND

[0002] With the rapid development of intelligent and networked vehicles, vehicle event data recording systems have become a core component for ensuring driving safety, tracing accident responsibility, and optimizing vehicle performance. Such systems need to collect and store a large amount of vehicle dynamic data (such as steer-by-wire system data and vehicle power supply data) in real time, which is the key basis for restoring the scene after an accident.

[0003] Currently, existing technologies mainly rely on local storage and do not implement data backup to the cloud. Once the local storage medium is damaged due to collision or aging, the key event data will be permanently lost, losing the value of tracing. Some solutions support data uploading to the cloud, but do not dynamically manage local storage. After cloud backup is completed, the local still retains full historical data, resulting in invalid occupation of storage space, not only aggravating the write wear of the storage medium (shortening the service life), but also requiring frequent data cleaning through manual or additional mechanisms, increasing system maintenance costs.

[0004] Therefore, in the vehicle event data recording scenario, how to ensure the traceability of key data (ensure safety through cloud backup) and local real-time access requirements (retain necessary data) under the premise of optimizing local storage strategies, dynamically releasing storage space, reducing dependence on available storage capacity of the controller, and saving hardware costs and maintenance costs of non-volatile storage has become a technical problem to be solved in the field. SUMMARY

[0005] The present application aims to at least solve the technical problems existing in the prior art. To this end, the present application proposes a vehicle event data recording method, system, device and storage medium, which can combine a cloud storage platform with a local storage device to cover early data stored in the local storage device with new data according to a coverage rule, reduce the demand for local storage space, and save the cost of non-volatile storage.

[0006] In a first aspect, the present application provides a vehicle event data recording method applied to a vehicle event data recording device, the vehicle event data recording device comprising a vehicle non-volatile storage, a vehicle terminal and a cloud storage platform, the vehicle non-volatile storage comprising a first preset storage space and a second preset storage space, and comprising the following steps: In the case of receiving first vehicle event data of a current data collection period, the first event type of the first vehicle event data is confirmed, wherein the event type comprises a serious event and a general event; obtaining a first available storage capacity of the first preset storage space, a first upload state of each second vehicle event data, and a first vehicle event data generation time of each second vehicle event data, wherein the second vehicle event data is historical vehicle event data stored in the first preset storage space, and the first upload state includes that the second vehicle event data has been uploaded to the cloud storage platform through the vehicle terminal and that the second vehicle event data has not been uploaded to the cloud storage platform through the vehicle terminal; In a case where the first event type is the serious event and the first available storage capacity is less than a first preset available storage capacity, filtering, from all the second vehicle event data, second vehicle event data whose first upload state is that the second vehicle event data has been uploaded to the cloud storage platform through the vehicle terminal and whose first vehicle event data generation time is the earliest among all the first vehicle event data generation times, as first to-be-covered vehicle event data, storing the first vehicle event data in the first preset storage space, and covering the first to-be-covered vehicle event data.

[0007] The control method according to the embodiments of the present application has at least the following beneficial effects: The method can confirm the first event type of the first vehicle event data in a case where the first vehicle event data of the current data collection period is received, obtain the first available storage capacity of the first preset storage space, the first upload state of each second vehicle event data, and the first vehicle event data generation time of each second vehicle event data, filter, in a case where the first event type is a serious event and the first available storage capacity is less than a first preset available storage capacity, second vehicle event data whose first upload state is that the second vehicle event data has been uploaded to the cloud storage platform through the vehicle terminal and whose first vehicle event data generation time is the earliest among all the first vehicle event data generation times, as first to-be-covered vehicle event data, store the first vehicle event data in the first preset storage space, and cover the first to-be-covered vehicle event data, so that new data can be made to cover early data stored in the local storage in a case where the local storage is used as a basic storage of data, in combination with the cloud storage platform and in accordance with a covering rule. In this way, the demand for the storage space of the local storage is reduced, and the cost of nonvolatile storage is saved.

[0008] According to some embodiments of the present application, the method further includes: obtaining a second available storage capacity of the second preset storage space and a second vehicle event data generation time of each third vehicle event data, wherein the third vehicle event data is historical vehicle event data stored in the second preset storage space; In a case that the first event type is the general event and the second available storage capacity is less than a second preset available storage capacity, from all the third vehicle event data, third vehicle event data with a second vehicle event data generation time being the earliest among all the second vehicle event data generation times is screened out as second to-be-covered vehicle event data, the first vehicle event data is stored in the second preset storage space, and the second to-be-covered vehicle event data is covered.

[0009] According to some embodiments of the present application, the method further comprises: In a case that the first event type is the serious event and the first available storage capacity is greater than or equal to the first preset available storage capacity, the first vehicle event data is stored in unused storage space of the first preset storage space.

[0010] According to some embodiments of the present application, the method further comprises: In a case that the first event type is the general event and the second available storage capacity is greater than or equal to the second preset available storage capacity, the first vehicle event data is stored in unused storage space of the second preset storage space.

[0011] According to some embodiments of the present application, the first vehicle event data comprises a vehicle flag bit signal value, and the confirmation of the first event type of the first vehicle event data comprises: In a case that the vehicle flag bit signal value of the first vehicle event data is a first preset vehicle flag bit signal value, the first event type of the first vehicle event data is a serious event; In a case that the vehicle flag bit signal value of the first vehicle event data is a second preset vehicle flag bit signal value, the first event type of the first vehicle event data is a general event.

[0012] According to some embodiments of the present application, the method further comprises: In a case that the vehicle terminal establishes a communication link connection with the cloud storage platform, vehicle event data with an upload state being the not passing the vehicle terminal in the vehicle nonvolatile memory is uploaded to the cloud storage platform through the vehicle terminal, wherein the vehicle event data comprises the first vehicle event data, the second vehicle event data and the third vehicle event data.

[0013] According to some embodiments of the present application, the method further comprises: The vehicle event data received by the cloud storage platform is verified to obtain a verification result; and the verification result is fed back to the vehicle terminal.

[0014] In a second aspect of the present application, a vehicle event data recording system is provided for a vehicle event data recording device, the vehicle event data recording device comprising a vehicle non-volatile memory, a vehicle terminal and a cloud storage platform, the vehicle non-volatile memory comprising a first preset storage space and a second preset storage space, the vehicle event data recording system comprising: a first event type confirmation module configured to, in a case where first vehicle event data of a current data collection period is received, confirm a first event type of the first vehicle event data, wherein the event type comprises a serious event and a general event; a data acquisition module configured to acquire a first available storage capacity of the first preset storage space, a first upload state of each second vehicle event data and a first vehicle event data generation time of each second vehicle event data, wherein the second vehicle event data is historical vehicle event data stored in the first preset storage space, and the first upload state comprises having been uploaded to the cloud storage platform through the vehicle terminal and not having been uploaded to the cloud storage platform through the vehicle terminal; a data upload module configured to, in a case where the first event type is the serious event and the first available storage capacity is less than a first preset available storage capacity, filter, from all the second vehicle event data, second vehicle event data having the first upload state of having been uploaded to the cloud storage platform through the vehicle terminal and the first vehicle event data generation time of being the earliest among all the first vehicle event data generation times, as first to-be-covered vehicle event data, store the first vehicle event data in the first preset storage space, and cover the first to-be-covered vehicle event data.

[0015] The system can confirm the first event type of the first vehicle event data when receiving the first vehicle event data of the current data collection period, acquire the first available storage capacity of the first preset storage space, the first upload state of each second vehicle event data, and the first vehicle event data generation time of each second vehicle event data, filter out the second vehicle event data with the first upload state being uploaded to the cloud storage platform through the vehicle terminal and the first vehicle event data generation time being the earliest among all first vehicle event data generation times as the first to-be-covered vehicle event data from all second vehicle event data when the first event type is a serious event and the first available storage capacity is less than the first preset available storage capacity, store the first vehicle event data in the first preset storage space, and cover the first to-be-covered vehicle event data, so that the new data can cover the early data stored in the local storage according to the covering rule in combination with the cloud storage platform when the local storage is used as the basic storage of the data, thereby reducing the demand for the storage space of the local storage and saving the cost of the nonvolatile storage.

[0016] In a third aspect, the present application provides a vehicle event data recording electronic device, comprising at least one control processor and a memory in communication connection with the at least one control processor; the memory stores instructions executable by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to perform the vehicle event data recording method described above.

[0017] In a fourth aspect, the present application provides a computer readable storage medium, which stores computer executable instructions for causing a computer to perform the vehicle event data recording method described above.

[0018] It should be noted that the beneficial effects between the second aspect to the fourth aspect of the present application and the prior art are the same as the beneficial effects between the vehicle event data recording system described above and the prior art, which will not be described here in detail.

[0019] Additional aspects and advantages of the present application will be in part apparent and in part pointed out hereinafter. BRIEF DESCRIPTION OF DRAWINGS

[0020] The above and / or additional aspects and advantages of the present application will become apparent and be readily appreciated from the following description, including the accompanying drawings, in which: Figure 1 is a flowchart of the vehicle event data recording method provided by the present application; Figure 2 is a structural schematic diagram of an embodiment of the vehicle event data recording system provided by the present application; Figure 3 FIG. 1 is a structural schematic diagram of an embodiment of an electronic device provided in the present application. DETAILED DESCRIPTION

[0021] Embodiments of the present application are described in detail below with reference to the accompanying drawings, in which examples of embodiments are shown, and like or similar elements or elements having like or similar functions are denoted throughout the figures by like reference numerals. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application and cannot be understood as limiting the present application.

[0022] In the description of the present application, if there is a description of first, second, etc., it is only for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features or the sequence of indicated technical features.

[0023] In the description of the present application, it should be understood that the position description, such as up, down, etc., or the first position relationship indicated by the position or the first position relationship shown in the drawings is only for the convenience of describing the present application and simplifying the description, and does not indicate or imply that the device or element indicated must have a specific position, be constructed and operated in a specific position, and therefore cannot be understood as limiting the present application.

[0024] In the description of the present application, it should be noted that, unless otherwise explicitly limited, the words such as setting, installing, connecting, etc. should be broadly understood, and those skilled in the art can reasonably determine the specific meaning of the above words in the present application in combination with the specific content of the technical solution.

[0025] With the rapid development of intelligent and networked vehicles, vehicle event data recording systems have become a core component for ensuring driving safety, tracing accident responsibility, or optimizing vehicle performance. Such systems need to collect and store massive amounts of vehicle dynamic data (such as steer-by-wire system data and vehicle power supply data) in real time, which is the key basis for restoring the scene after an accident.

[0026] Currently, existing technologies mainly rely on local storage and do not implement data backup to the cloud. Once the local storage medium is damaged due to collision or aging, etc., the key event data will be permanently lost, losing the value of tracing; some solutions also support data uploading to the cloud, but do not dynamically manage local storage. After cloud backup is completed, the local still retains full historical data, resulting in invalid occupation of storage space, not only exacerbating the write wear of the storage medium (shortening the service life), but also requiring frequent data cleaning through manual or additional mechanisms, increasing system maintenance costs.

[0027] Therefore, in the vehicle event data recording scene, how to ensure the traceability of key data (safety guaranteed by cloud backup) and the demand for local real-time access (necessary data reserved), release storage space dynamically, reduce the dependence on the available storage capacity of the controller, and save the hardware cost and maintenance cost of non-volatile storage by optimizing the local storage strategy has become a technical problem to be solved in the field.

[0028] To solve the above technical defects, the embodiments of the present application provide a vehicle event data recording method, system, device and storage medium.

[0029] Please refer to Figure 1 , which is a flowchart of a vehicle event data recording method provided by the embodiments of the present application, as Figure 1 shown, applied to a vehicle event data recording device, the vehicle event data recording device including a vehicle non-volatile memory, a vehicle terminal and a cloud storage platform, the vehicle non-volatile memory including a first preset storage space and a second preset storage space, the vehicle event data recording method including: Step S101, in the case of receiving first vehicle event data of a current data collection period, confirming a first event type of the first vehicle event data, wherein the event type includes a serious event and a general event; Step S102, obtaining a first available storage capacity of the first preset storage space, a first upload state of each second vehicle event data and a first vehicle event data generation time of each second vehicle event data, wherein the second vehicle event data is historical vehicle event data stored in the first preset storage space, and the first upload state includes having been uploaded to the cloud storage platform through the vehicle terminal and not having been uploaded to the cloud storage platform through the vehicle terminal; Step S103, in the case of the first event type being a serious event and the first available storage capacity being less than a first preset available storage capacity, screening out, from all the second vehicle event data, second vehicle event data whose first upload state is having been uploaded to the cloud storage platform through the vehicle terminal and whose first vehicle event data generation time is the earliest among all the first vehicle event data generation times, as first to-be-covered vehicle event data, storing the first vehicle event data in the first preset storage space, and covering the first to-be-covered vehicle event data.

[0030] The above data collection period can be one hour or 1 minute.

[0031] Each of the above second vehicle event data is historical vehicle event data collected according to the above data collection period.

[0032] The above first preset available storage capacity can be a value set in advance according to actual needs.

[0033] The first preset storage space can be a value set in advance according to actual needs.

[0034] The second preset storage space can be a value set in advance according to actual needs.

[0035] The vehicle non-volatile memory is used for local storage of data.

[0036] In the step S102, the vehicle control instruction generated based on the voice instruction can be a vehicle control instruction corresponding to the voice instruction in response to the voice instruction.

[0037] The method can confirm the first event type of the first vehicle event data when the first vehicle event data of the current data collection period is received, obtain the first available storage capacity of the first preset storage space, the first upload state of each second vehicle event data, and the first vehicle event data generation time of each second vehicle event data, filter out, from all second vehicle event data, the second vehicle event data whose first upload state is uploaded to the cloud storage platform through the vehicle terminal and whose first vehicle event data generation time is the earliest among all first vehicle event data generation times as the first vehicle event data to be covered in a case where the first event type is a serious event and the first available storage capacity is less than the first preset available storage capacity, store the first vehicle event data in the first preset storage space, and cover the first vehicle event data to be covered. Thus, the new data can cover the early data stored in the local memory according to the covering rule in combination with the cloud storage platform in the case of using the local memory as the basic storage of data. In this way, the demand for the storage space of the local memory is reduced, and the cost of non-volatile storage is saved.

[0038] In some embodiments, the method further comprises: In step S201, the second available storage capacity of the second preset storage space and the second vehicle event data generation time of each third vehicle event data are obtained, wherein the third vehicle event data is historical vehicle event data stored in the second preset storage space. In step S202, in a case where the first event type is a general event and the second available storage capacity is less than the second preset available storage capacity, the third vehicle event data whose second vehicle event data generation time is the earliest among all second vehicle event data generation times is filtered out from all third vehicle event data as the second vehicle event data to be covered, the first vehicle event data is stored in the second preset storage space, and the second vehicle event data to be covered is covered.

[0039] Each third vehicle event data is historical vehicle event data collected according to the data collection period.

[0040] The second preset available storage capacity can be a value set in advance according to actual needs.

[0041] The application can reduce the demand for local memory storage space and save the cost of non-volatile storage by covering the early data stored in the local memory with new data according to the coverage rule in the case of storing data based on the local memory.

[0042] In some embodiments, the method further comprises: Step S301, in the case that the first event type is a serious event and the first available storage capacity is greater than or equal to the first preset available storage capacity, storing the first vehicle event data in the unused storage space of the first preset storage space.

[0043] In some embodiments, the method further comprises: Step S401, in the case that the first event type is a general event and the second available storage capacity is greater than or equal to the second preset available storage capacity, storing the first vehicle event data in the unused storage space of the second preset storage space.

[0044] The application can effectively utilize the storage space of the local memory and improve the utilization rate of the local memory.

[0045] In some embodiments, the first vehicle event data includes a vehicle flag bit signal value, and confirming the first event type of the first vehicle event data comprises: Step S501, in the case that the vehicle flag bit signal value of the first vehicle event data is the first preset vehicle flag bit signal value, the first event type of the first vehicle event data is a serious event; Step S502, in the case that the vehicle flag bit signal value of the first vehicle event data is the second preset vehicle flag bit signal value, the first event type of the first vehicle event data is a general event.

[0046] The first preset vehicle flag bit signal value can be a value set in advance according to actual needs, and can include a vehicle collision signal sent by the ACU with the flag bit set to 1.

[0047] The second preset vehicle flag bit signal value can be a value set in advance according to actual needs, and can include a vehicle braking system fault signal with the flag bit set to 1.

[0048] The application can improve the utilization rate of the storage space by guaranteeing the priority of the key data.

[0049] In some embodiments, the method further comprises: Step S601, in the case that the vehicle terminal and the cloud storage platform establish a communication link connection, upload the vehicle event data in the vehicle non-volatile memory whose upload state is not passed by the vehicle terminal to the cloud storage platform through the vehicle terminal, wherein the vehicle event data includes first vehicle event data, second vehicle event data and third vehicle event data.

[0050] The above-mentioned upload state includes uploading to the cloud storage platform through the vehicle terminal and uploading to the cloud storage platform through the vehicle terminal.

[0051] The above-mentioned vehicle event data can be data within a fixed time period when the vehicle flag bit signal value is the first preset vehicle flag bit signal value or the second preset vehicle flag bit signal value, such as data within 10 seconds before and after.

[0052] The above-mentioned vehicle event data can also include driver manipulation state data, vehicle power supply and intelligent driving whole vehicle key data, and steer-by-wire system itself data elements.

[0053] In some embodiments, the method further comprises: Step S701, checking the received vehicle event data through the cloud storage platform to obtain a checking result; Step S702, and feeding back the checking result to the vehicle terminal.

[0054] Specifically, the vehicle terminal initiates a communication connection request to the cloud storage platform, establishes a communication link connection, and the vehicle terminal platform sends login information to the cloud storage platform for verifying its legal identity. Then the vehicle terminal sends a data packet to the cloud storage platform, the cloud storage platform checks the received data, and feeds back a successful response. If the cloud storage platform fails to check, it feeds back an error response to the vehicle terminal, at which time the vehicle terminal should resend the vehicle event data.

[0055] Specifically, the application layer of the present application adopts UDS protocol, and the transmission layer adopts DoIP protocol to meet the requirements of fast reading of a large amount of storage data and data integrity. When reading, UDS 38 service is used to request file transmission, then 36 service and 37 service are used to start data transmission, and after the transmission is completed, the transmission service is requested to exit.

[0056] Specifically, in the process of checking the received vehicle event data through the cloud storage platform, 31 routine control service is adopted, the CRC32 value of the file is requested from the local data storage controller to provide the reading device for checking whether the file transmission is complete. If the return value is invalid or returns a negative response, the event reading device should terminate this reading process.

[0057] In addition, with reference to Figure 2In one embodiment of the present application, a vehicle event data recording system is provided for a vehicle event data recording device, the vehicle event data recording device comprising a vehicle non-volatile memory, a vehicle terminal and a cloud storage platform, the vehicle non-volatile memory comprising a first preset storage space and a second preset storage space, the vehicle event data recording system comprising a first event type confirmation module 1100, a data acquisition module 1200 and a data uploading module 1300, wherein: The first event type confirmation module 1100 is configured to, in the case of receiving first vehicle event data of a current data collection period, confirm a first event type of the first vehicle event data, wherein the event type comprises a serious event and a general event. The data acquisition module 1200 is configured to acquire a first available storage capacity of the first preset storage space, a first uploading state of each second vehicle event data and a first vehicle event data generation time of each second vehicle event data, wherein the second vehicle event data is historical vehicle event data stored in the first preset storage space, and the first uploading state comprises having been uploaded to the cloud storage platform through the vehicle terminal and not having been uploaded to the cloud storage platform through the vehicle terminal. The data uploading module 1300 is configured to, in the case of the first event type being a serious event and the first available storage capacity being less than a first preset available storage capacity, from all the second vehicle event data, screen out second vehicle event data whose first uploading state is having been uploaded to the cloud storage platform through the vehicle terminal and whose first vehicle event data generation time is the earliest among all the first vehicle event data generation times, as first to-be-covered vehicle event data, store the first vehicle event data in the first preset storage space, and cover the first to-be-covered vehicle event data.

[0058] The system confirms the first event type of the first vehicle event data in the case of receiving the first vehicle event data of the current data collection period, acquires the first available storage capacity of the first preset storage space, the first uploading state of each second vehicle event data and the first vehicle event data generation time of each second vehicle event data, in the case of the first event type being a serious event and the first available storage capacity being less than the first preset available storage capacity, from all the second vehicle event data, screens out second vehicle event data whose first uploading state is having been uploaded to the cloud storage platform through the vehicle terminal and whose first vehicle event data generation time is the earliest among all the first vehicle event data generation times, as first to-be-covered vehicle event data, stores the first vehicle event data in the first preset storage space, and covers the first to-be-covered vehicle event data, thereby being able to, in the case of using the local memory as the basic storage of data, in combination with the cloud storage platform, according to the covering rule, make the new data cover the early data stored in the local memory, thus reducing the demand for the storage space of the local memory and saving the cost of non-volatile storage.

[0059] It should be noted that the system embodiments and the above-mentioned method embodiments are based on the same inventive concept, and therefore the related content of the above-mentioned method embodiments is also applicable to the system embodiments, which will not be described here again.

[0060] Figure 3 A hardware structure schematic diagram of vehicle event data recording provided by the embodiments of the application is shown.

[0061] The vehicle event data recording device can include a processor 301 and a memory 302 having computer program instructions stored therein.

[0062] Specifically, the processor 301 can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured as one or more integrated circuits that implement the embodiments of the application.

[0063] The memory 302 can include a mass storage for data or instructions. By way of example and not limitation, the memory 302 can include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. Where appropriate, the memory 302 can include removable or non-removable (or fixed) media. Where appropriate, the memory 302 can be internal or external to the integrated gateway disaster recovery device. In some embodiments, the memory 302 is a non-volatile solid-state memory.

[0064] In some embodiments, the memory 302 can include read-only memory (ROM), random access memory (RAM), a disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software that, when executed (e.g., by one or more processors), is operable to perform operations described with reference to the methods according to an aspect of the present disclosure.

[0065] The processor 301 implements any one of the vehicle event data recording methods in the above embodiments by reading and executing the computer program instructions stored in the memory 302.

[0066] In one example, the vehicle event data recording device can further include a communication interface 303 and a bus 310. Among them, as shown in the figure, the communication interface 303 is connected to the bus 310, and the bus 310 is connected to the processor 301 and the memory 302. Figure 3As shown, the processor 301, the memory 302, and the communication interface 303 are connected by the bus 310 and accomplish the communication between each other.

[0067] The communication interface 303 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiments of the present application.

[0068] The bus 310 includes hardware, software or both to couple the components of the vehicle event data recording device to each other. By way of example, and not limitation, the bus can include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or combination of two or more of these. Where suitable, the bus 310 can include one or more buses. Although particular buses are described and shown in the embodiments of the present application, the present application contemplates any suitable bus or interconnect.

[0069] The vehicle event data recording device can execute the vehicle event data recording method in the embodiments of the present application based on the three-dimensional design model, thereby realizing the vehicle event data recording method and system described in the embodiments of the present application. Figure 1 and Figure 2 The vehicle event data recording method and system described in the embodiments of the present application.

[0070] In addition, in combination with the vehicle event data recording method in the above embodiments, the embodiments of the present application can provide a computer storage medium to realize. The computer storage medium has computer program instructions stored thereon; the computer program instructions are executed by the processor to realize any one of the vehicle event data recording methods in the above embodiments.

[0071] It needs to be clear that the present application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, the detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps, after understanding the spirit of the present application.

[0072] The functional blocks shown in the structural block diagrams above can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, and the like. When implemented in software, the elements of the present application are program or code segments that are used to perform the required tasks. The program or code segments can be stored in a machine-readable medium, or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link. A "machine-readable medium" includes any medium that can store or transport information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memory, erasable ROMs (EROMs), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, and the like. The code segments can be downloaded via computer networks such as the Internet, intranets, and the like.

[0073] It is also important to note that the examples in the present application are described based on a series of steps or units for performing some methods or systems. However, the present application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the examples, or in an order different from the examples, or several steps can be performed simultaneously.

[0074] The above describes the aspects of the present application with reference to the flowcharts and / or block diagrams of the methods, apparatuses (systems) and computer program products according to the embodiments of the present application. It should be understood that each block in the flowcharts and / or block diagrams, and the combination of blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus enable the implementation of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It should also be understood that each block in the block diagrams and / or flowcharts, and the combination of blocks in the block diagrams and / or flowcharts, can also be implemented by special hardware that performs specified functions or acts, or can be implemented by a combination of special hardware and computer instructions.

[0075] The above is only a specific implementation of the present application, and those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described systems, modules and units can refer to the corresponding processes in the foregoing method embodiments, which will not be described here. It should be understood that the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be covered within the protection scope of the present application.

Claims

1. A method for recording vehicle event data, characterized in that, An application is made to a vehicle event data recording device, wherein the vehicle event data recording includes a vehicle non-volatile memory, an in-vehicle terminal, and a cloud storage platform, the vehicle non-volatile memory includes a first preset storage space and a second preset storage space, and the vehicle event data recording method includes: Upon receiving the first vehicle event data of the current data collection period, the first event type of the first vehicle event data is confirmed, wherein the event type includes serious events and general events; The system obtains the first available storage capacity of the first preset storage space, the first upload status of each second vehicle event data, and the first vehicle event data generation time of each second vehicle event data. The second vehicle event data is historical vehicle event data stored in the first preset storage space. The first upload status includes data that has been uploaded to the cloud storage platform through the vehicle terminal and data that has not been uploaded to the cloud storage platform through the vehicle terminal. When the first event type is the serious event and the first available storage capacity is less than the first preset available storage capacity, from all the second vehicle event data, the second vehicle event data whose first upload status is "already uploaded to the cloud storage platform through the vehicle terminal" and whose first vehicle event data generation time is the earliest among all the first vehicle event data generation times is selected as the first vehicle event data to be covered, the first vehicle event data is stored in the first preset storage space, and the first vehicle event data to be covered is overwritten.

2. The vehicle event data recording method according to claim 1, characterized in that, The method further includes: Obtain the second available storage capacity of the second preset storage space and the second vehicle event data generation time for each third vehicle event data, wherein the third vehicle event data is historical vehicle event data stored in the second preset storage space; When the first event type is the general event and the second available storage capacity is less than the second preset available storage capacity, the third vehicle event data whose generation time is the earliest among all the third vehicle event data is selected from all the third vehicle event data and used as the second vehicle event data to be covered. The first vehicle event data is stored in the second preset storage space and the second vehicle event data to be covered is overwritten.

3. The vehicle event data recording method according to claim 2, characterized in that, The method further includes: If the first event type is the serious event and the first available storage capacity is greater than or equal to the first preset available storage capacity, the first vehicle event data is stored in the unused storage space of the first preset storage space.

4. The vehicle event data recording method according to claim 3, characterized in that, The method further includes: If the first event type is a general event and the second available storage capacity is greater than or equal to the second preset available storage capacity, the first vehicle event data is stored in the unused storage space of the second preset storage space.

5. A vehicle event data recording method according to claim 4, characterized in that, The first vehicle event data includes vehicle flag bit signal values, and the first event type for confirming the first vehicle event data includes: If the vehicle flag signal value of the first vehicle event data is the first preset vehicle flag signal value, then the first event type of the first vehicle event data is a serious event. If the vehicle flag signal value of the first vehicle event data is the second preset vehicle flag signal value, then the first event type of the first vehicle event data is a general event.

6. The vehicle event data recording method according to claim 5, characterized in that, The method further includes: When the vehicle terminal establishes a communication link connection with the cloud storage platform, the vehicle event data in the vehicle's non-volatile memory that has an upload status of "not passed through the vehicle terminal" is uploaded to the cloud storage platform through the vehicle terminal. The vehicle event data includes the first vehicle event data, the second vehicle event data, and the third vehicle event data.

7. A method for recording vehicle event data according to claim 6, characterized in that, The method further includes: The received vehicle event data is verified through the cloud storage platform to obtain the verification result; The verification result is then fed back to the vehicle terminal.

8. A vehicle event data recording system, characterized in that, An application is made to a vehicle event data recording device, wherein the vehicle event data recording includes a vehicle non-volatile memory, an in-vehicle terminal, and a cloud storage platform, the vehicle non-volatile memory includes a first preset storage space and a second preset storage space, and the vehicle event data recording system includes: The first event type confirmation module is used to confirm the first event type of the first vehicle event data when receiving the first vehicle event data of the current data collection period, wherein the event type includes serious events and general events; The data acquisition module is used to acquire the first available storage capacity of the first preset storage space, the first upload status of each second vehicle event data, and the first vehicle event data generation time of each second vehicle event data, wherein the second vehicle event data is historical vehicle event data stored in the first preset storage space, and the first upload status includes being uploaded to the cloud storage platform through the vehicle terminal and not being uploaded to the cloud storage platform through the vehicle terminal; The data upload module is used to, when the first event type is the serious event and the first available storage capacity is less than the first preset available storage capacity, select the second vehicle event data from all the second vehicle event data whose first upload status is "already uploaded to the cloud storage platform through the vehicle terminal" and whose first vehicle event data generation time is the earliest among all the first vehicle event data generation times, as the first vehicle event data to be covered, store the first vehicle event data in the first preset storage space, and cover the first vehicle event data to be covered.

9. A vehicle event data recording device, characterized in that, It includes at least one control processor and a memory for communicatively connecting to the at least one control processor; the memory stores instructions executable by the at least one control processor, which, when executed by the at least one control processor, enable the at least one control processor to perform a vehicle event data recording method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions for causing a computer to perform a vehicle event data recording method as described in any one of claims 1 to 7.

Images