TWI840194B - Driving recording file management method and system - Google Patents

Abstract

In a driving recording file management method and system, a processor divides a storage space of a storage medium into a plurality of large blocks, and divides each large block into a plurality of regions, each of which corresponds to a respective one of a plurality of recording modules and is further divided into multiple file blocks with the same storage capacity. The processor assigns, using the principle of priority, a respective block access sequence to each area of the storage space. When the processor obtains multiple pieces of driving/parking record data that are obtained by the recording modules within each first/second unit time during the driving/parking of the vehicle or within a time period associated with an event of the vehicle during the driving of the vehicle, the processor stores the pieces of driving/parking record data as current files into corresponding file blocks accessed according respectively to block access sequences assigned to the areas of a corresponding large block.

Description

Driving record file management method and system

The present invention relates to the storage of driving record files, and in particular to a driving record file management method and system.

At present, the recorded files (including video files and driving track files) obtained by vehicle dash cams are usually stored in storage media such as SD (Secure Digital) cards according to the data format of the file system such as FAT (File Allocation Table) 32. However, FAT has a serious disadvantage, that is, when the old files (stored) in the SD card are to be deleted to write new data, FAT will not organize the new files to be written into complete segments before writing them to the SD card. Therefore, after long-term use, the file data stored in the SD card will gradually become scattered, which is the so-called fragmentation, thereby reducing the reading and writing efficiency of the SD card.

In order to solve the problem of SD card fragmentation, the SD card must be formatted frequently to maintain the original reading and writing efficiency. And since the SD card formatting process is relatively time-consuming (about 20 seconds/file), it causes inconvenience in use.

Therefore, how to invent a driving record file management method that can avoid the file fragmentation problem of the storage medium and ensure the reading and writing efficiency of the storage medium has become one of the issues that the relevant technical fields want to solve.

Therefore, the purpose of the present invention is to provide a driving record file management method and system, which can overcome at least one shortcoming of the prior art.

Therefore, the present invention provides a driving record file management method for managing a storage medium installed in a vehicle with multiple different recording modules, and is executed by a processor, and includes the following steps: dividing a storage space of the storage medium into at least a normal large block, an event large block, and a parking large block corresponding to normal use, event use, and parking use, respectively, and dividing each of the normal large block, the event large block, and the parking large block into multiple The areas corresponding to the recording modules are each divided into a plurality of file blocks having the same storage capacity; a corresponding block access sequence is assigned to all the file blocks in each area of the storage space of the storage medium according to a priority principle; when a plurality of driving record data acquired by the recording modules in each first unit time during the driving of the vehicle is acquired, each driving record is assigned to the normal large block according to the respective block access sequence of the areas. The recorded data is stored as a corresponding current normal file in a retrieved file block in one of the corresponding areas of the areas of the normal large block; when a plurality of driving record data acquired by the recording modules in a time period from a first time point earlier than an event time point when an event occurs to a second time point later than the event time point is acquired, each driving record data is used as a corresponding current normal file in accordance with the access sequence of the respective plurality of blocks of the areas of the event large block. The event file is stored in an accessed file block in one of the corresponding areas of the areas of the event large block; and when a plurality of parking record data acquired by the recording modules in each second unit time during the parking period of the vehicle are acquired, each parking record data is stored as a corresponding current parking file in an accessed file block in one of the corresponding areas of the areas of the parking large block according to the respective block access sequence of the areas assigned to the parking large block.

In some embodiments, the priority policy includes (i) a file block in the area that has never been written with any file has a first priority, (ii) a file block in the area that stores an incomplete or damaged historical record file has a second priority, and (iii) a file block in the area that stores a relatively earliest historical record file has a third priority. The processor determines the access file block in the corresponding area of the normal large block according to the corresponding block access sequence, so that the historical normal file stored in the corresponding area of the normal large block can be retained for the longest period of time. The processor determines the file block to be used in the corresponding area of the event block according to the corresponding block access sequence, so that the retention period of the historical event file stored in the corresponding area of the event block can be extended to the longest. The processor determines the file block to be used in the corresponding area of the parking block according to the corresponding block access sequence, so that the retention period of the historical parking file stored in the corresponding area of the parking block can be extended to the longest.

In some embodiments, the recording modules include multiple image capture modules and a geolocation module. The driving record data corresponding to the first unit time include multiple driving video data of the vehicle obtained by the image capture modules in the first unit time and the driving track data of the vehicle obtained by the geolocation module in the first unit time. The driving record data corresponding to the time period include multiple driving video data of the vehicle obtained by the image capture modules in the time period and the driving track data of the vehicle obtained by the geolocation module in the time period. The driving record data corresponding to the second unit time include multiple parking video data of the vehicle obtained by the image capturing modules within the second unit time.

In some embodiments, the areas in the normal large block include multiple video file areas corresponding to the image capture modules, and a track file area corresponding to the geolocation module, wherein the storage capacity of each file block in each video file area is related to the frame rate, the pixels per frame and the first unit time of a corresponding one of the image capture modules and is slightly larger than the size of the driving video data obtained by the corresponding image capture module within the first unit time, and the storage capacity of each file block in the track file area is larger than the size of the driving track data obtained within the first unit time. The areas in the event large block include multiple video file areas corresponding to the image capture modules and a track file area corresponding to the geolocation module, wherein the storage capacity of each file block in each video file area is related to the frame rate of a corresponding one of the image capture modules, the pixels of each frame image and the time period and is slightly larger than the size of the driving video data obtained by the corresponding image capture module during the time period, and the storage capacity of each file block in the track file area is larger than the size of the driving track data obtained during the time period. The areas in the large parking area include a plurality of video file areas corresponding to the image capturing modules, and the storage capacity of each file block in each of them is related to the frame rate, the pixels per frame and the second unit time of one of the corresponding image capturing modules and is slightly larger than the size of the parking video data obtained by the corresponding image capturing module in the second unit time.

In some embodiments, the driving record file management method further includes the following steps: periodically confirming whether each file stored in the storage medium is damaged, and when a damaged file is confirmed, updating the block access sequence corresponding to the area to which the damaged file belongs.

Therefore, the present invention provides a driving record file management system, which is suitable for being installed in a vehicle equipped with multiple different recording modules, and includes a storage medium and a processor.

The storage medium has a storage space. The storage space is divided into at least a normal large block, an event large block and a parking large block corresponding to normal use, event use and parking use respectively. Each of the normal large block, the event large block and the parking large block is further divided into a plurality of areas corresponding to the recording modules respectively, and each of them is further divided into a plurality of file blocks with the same storage capacity.

The processor is adapted to be electrically connected to the recording modules and the storage medium and the storage module, and to assign corresponding block access sequences to all file blocks in each area of the storage space of the storage medium according to a priority principle.

When the processor receives a plurality of record data acquired by the recording modules at each first unit time during the driving of the vehicle, the processor stores each driving record data as a corresponding current normal file in an accessed file block in one of the corresponding areas of the areas of the normal large block according to the respective block access order of the areas assigned to the normal large block.

When the processor obtains a plurality of driving record data acquired by the recording modules in a time period from a first time point earlier than an event time point when an event occurs to a second time point later than the event time point, the processor stores each driving record data as a corresponding current event file in an accessed file block in one of the corresponding areas of the areas of the event large block according to the respective block access order of the areas assigned to the event large block.

When the processor receives a plurality of parking record data acquired by the recording modules at each second unit time during the parking period of the vehicle, the processor stores each parking record data as a corresponding current parking file in an accessed file block in one of the corresponding areas of the areas of the parking block according to the respective block access order of the areas assigned to the parking block.

In some embodiments, the priority policy includes (i) a file block in the area that has never been written with any file has a first priority, (ii) a file block in the area that stores an incomplete or damaged historical record file has a second priority, and (iii) a file block in the area that stores a relatively earliest historical record file has a third priority. The processor determines the accessed file block in the corresponding area of the normal large block according to the corresponding block access sequence, so that the historical normal file stored in the corresponding area of the normal large block can be retained for the longest period of time. The processor determines the file block to be used in the corresponding area of the event block according to the corresponding block access sequence, so that the retention period of the historical event file stored in the corresponding area of the event block can be extended to the longest. The processor determines the file block to be used in the corresponding area of the parking block according to the corresponding block access sequence, so that the retention period of the historical parking file stored in the corresponding area of the parking block can be extended to the longest.

In some embodiments, the recording modules include multiple image capture modules and a geolocation module. The driving record data corresponding to the first unit time include multiple driving video data of the vehicle obtained by the image capture modules within the predetermined first unit time and the driving track data of the vehicle obtained by the geolocation module within the predetermined first unit time. The driving record data corresponding to the predetermined time period include multiple driving video data of the vehicle obtained by the image capture modules within the predetermined time period and the driving track data of the vehicle obtained by the geolocation module within the predetermined time period. The driving record data corresponding to the predetermined second unit time include multiple parking video data of the vehicle obtained by the image capturing modules within the predetermined second unit time.

In some embodiments, the areas in the normal large block include multiple video file areas corresponding to the image capturing modules, and a track file area corresponding to the geolocation module, wherein the storage capacity of each file block in each video file area is related to the frame rate, the pixels per frame and the predetermined first unit time of a corresponding one of the image capturing modules and is slightly larger than the size of the driving video data obtained by the corresponding image capturing module within the predetermined first unit time, and the storage capacity of each file block in the track file area is larger than the size of the driving track data obtained within the predetermined first unit time. The areas in the event large block include multiple video file areas corresponding to the image capture modules and a track file area corresponding to the geolocation module, wherein the storage capacity of each file block in each video file area is related to the frame rate, the pixels of each frame image and the predetermined time period of a corresponding one of the image capture modules and is slightly larger than the size of the driving video data obtained by the corresponding image capture module within the predetermined time period, and the storage capacity of each file block in the track file area is larger than the size of the driving track data obtained within the predetermined time period. The areas in the large parking area include a plurality of video file areas corresponding to the image capturing modules, and the storage capacity of each file block in each of them is associated with the frame rate, the pixels per frame and the predetermined second unit time of a corresponding one of the image capturing modules and is slightly larger than the size of the parking video data obtained by the corresponding image capturing module within the predetermined second unit time.

In some embodiments, the processor also periodically confirms whether each file stored in the storage medium is damaged, and when a damaged file is confirmed, updates the block access sequence corresponding to the area to which the damaged file belongs.

The effect of the present invention is that: since the storage space of the storage medium has been planned into a plurality of large blocks corresponding to a plurality of different purposes, and each large block is also planned to have a plurality of areas corresponding to the recording modules, and each area is further divided into a plurality of file blocks with the same storage capacity according to the recording specifications and recording time periods of the corresponding recording modules, The processor can store record files with substantially similar file sizes in the accessed file blocks according to the corresponding block access order. This can not only ensure that the historical record files stored in each area are retained for the longest period of time, but also effectively avoid the file fragmentation problem encountered by the existing technology, while ensuring the reading and writing efficiency of the storage medium.

Before the present invention is described in detail, it should be noted that similar components are represented by the same reference numerals in the following description.

Referring to FIG. 1 , a driving record file management system 100 according to an embodiment of the present invention is exemplarily illustrated, as well as a plurality of recording modules disposed in a vehicle (not shown), such as first to third image capturing modules 201-203 and a geolocation module 204, but not limited thereto. The first to third image capturing modules 201-203 may be a front lens module for capturing images in front of the vehicle (such as but not limited to a CMOS lens module), an interior lens module for capturing images in the vehicle (such as but not limited to a CMOS lens module), and a rear lens module for capturing images behind the vehicle (such as but not limited to a CMOS lens module). The driving record file management system 100 is suitable for being disposed in the vehicle, and comprises a storage medium 2 and a processor 1.

In this embodiment, the storage medium 2 is, for example but not limited to, an SD card, and is electrically connected to the processor 1. The storage medium 2 has a storage space for storing data or recording files.

Before the driving record file management system 100 is used, the processor 1 divides the storage space of the storage medium 2 into, for example, a normal large block, an event large block, a parking large block and a reserved large block corresponding to normal use, event use, parking use and reserved use, respectively. For example, as shown in FIG. 2 , the storage space has a storage capacity of, for example, 119 GB, wherein the normal large block has a storage capacity of, for example, 60 GB and is used to store image data (i.e., driving video data) acquired by the first to third image capturing modules 201-203 during driving of the vehicle and geographic location data (i.e., driving track data) acquired by the geographic positioning module 204; the event large block has a storage capacity of, for example, 40 GB and is used to store the location data (i.e., driving track data) acquired by the geographic positioning module 204 each time an event occurs to the vehicle from a first time point earlier than the event time point when the event occurs (e.g., 15 seconds before the event time point) to a time point later than the event time point. The image data (i.e., driving video data) acquired by the first to third image capturing modules 201-203 and the geographic location data (i.e., driving trajectory data) acquired by the geographic positioning module 204 within a time period (e.g., 30 seconds) from a second time point (e.g., 15 seconds after the event time point); the parking large block has, for example, a storage capacity of 10 GB and is used to store image data (i.e., parking video data) acquired by the first to third image capturing modules 201-203 during the period when the vehicle is parked (i.e., during a period of complete stillness); and the reserved large block has, for example, a storage capacity of 9 GB and is used to store files or data that need to be retained.

In addition, the processor 1 further divides each of the normal large block, the event large block, and the parking large block into, for example, a first video file area, a second video file area, a third video file area, and a track file area, which correspond to the first to third image capturing modules 201-203 and the geolocation module 204, respectively, as shown in Figure 3. Furthermore, for the normal large block, the processor 1 further divides each of the first to third video file areas into a plurality of file blocks having the same storage capacity (e.g., 330MB), and further divides the track file area into a plurality of file blocks having the same storage capacity (e.g., 512KB). Therefore, if the normal large block has 60GB, each of the first to third video file areas can be divided into, for example, 60 file blocks of 330MB, and the track file area can be divided into, for example, 60 file blocks of 512KB (see FIG. 4). For the event large block, the processor 1 further divides each of the first to third video file areas into multiple file blocks with the same storage capacity (e.g., 55MB), and also further divides the track file area into multiple file blocks with the same storage capacity (e.g., 512KB). Therefore, if the event block has 40GB, each of the first to third video file areas can be divided into, for example, 240 file blocks with 330MB, and the track file area can be divided into 240 file blocks with 512KB (see FIG. 4). For the parking block, the processor 1 further divides each of the first to third video file areas into a plurality of file blocks with the same storage capacity (e.g., 270MB). Therefore, if the parking block has 10GB, each of the first to third video file areas can be divided into, for example, 12 file blocks with 270MB (see FIG. 4).

It is worth noting that the storage capacity of each file block in each video file area in the normal large block is related to the frame rate, the pixels per frame and a first unit time of one of the corresponding first to third image capturing modules 201-203 and is slightly larger than the size of the driving video data acquired by the corresponding image capturing module 201/202/203 within a first unit time; the storage capacity of each file block in each video file area in the event large block is related to the frame rate, the pixels per frame and a first unit time of one of the corresponding first to third image capturing modules 201-203. The frame rate, the pixels per frame image and the time period of the corresponding image capturing module 201/202/203 are related and are slightly larger than the size of the driving video data acquired by the corresponding image capturing module 201/202/203 in the time period; the storage capacity of each file block in each video file area in the parking large block is related to the frame rate, the pixels per frame image and a second unit time of the corresponding one of the first to third image capturing modules 201~203 and is slightly larger than the size of the parking video data acquired by the corresponding image capturing module 201/202/203 in the second unit time. In this embodiment, during the driving period of the vehicle, the frame rate and the pixels per frame of each of the first to third image capturing modules 201~203 are, for example, 30 frames/second and 1080 pixels, respectively, and the first unit time is, for example, 3 minutes and the time period is, for example, 30 seconds; and during the parking period of the vehicle, compared to the driving period of the vehicle, each of the first to third image capturing modules 201~203 can obtain each parking video data within the second unit time of, for example, 3 minutes with a smaller frame rate and a lower resolution.

Finally, the processor 1 obtains a file system according to all the file blocks of the normal block, the event block and the parking block, as well as the corresponding relationship data between the memory addresses and the usage status, and stores the file system. Thereafter, when in use, the processor 1 will obtain the memory address of the file block to be used to record the file in the storage space of the storage medium 2 according to the file system.

Please note that when the driving record file management system 100 is initially used, the processor 1 will write the file to be recorded into the accessed file block according to the arrangement order of the file blocks of each area (i.e., the first video file area, the second video file area, the third video file area, or the track file area) of each large block (i.e., the normal large block, the event large block, or the parking large block). Therefore, when initially used, the file blocks in each area will be accessed in sequence to store the files to be recorded. In addition, after the driving record file management system 100 begins to be used, the processor 1 will periodically confirm whether each file stored in the storage medium 2 is damaged. When a damaged file is confirmed, the file system will mark the usage status of the file block where the damaged file is located and update the block access sequence corresponding to the area where the damaged file belongs.

Afterwards, the processor 1 assigns corresponding block access orders to all file blocks in each area of the storage space of the storage medium 2 according to the file system and using a priority principle. In this embodiment, the priority principle includes, for example, (i) file blocks in the area that have never been written with any files have a first priority, (ii) file blocks in the area that store incomplete or damaged historical record files have a second priority, and (iii) file blocks in the area that store the earliest historical record files have a third priority, the purpose of which is to maximize the retention time of the historical record files stored in the area.

More specifically, in this embodiment, during the driving of the vehicle, when the processor 1 obtains three driving video data of the vehicle obtained by the first to third image capturing modules 201-203 in each first unit time (for example, 3 minutes) during the driving period (as driving record data) and the driving track data of the vehicle obtained by the geolocation module 204 in the first unit time (as driving record data), the processor 1 processes the first to third video files assigned to the normal large block according to the first to third video files. The block access sequence of the first to third video file areas and the track file area is determined to correspond to an accessed file block of the first unit time, and the three driving video data are respectively stored as current normal files in the accessed file blocks determined in the first to third video file areas of the normal large block, so that the retention period of the historical normal files stored in each of the first to third video file areas and the track file area of the normal large block can be extended to the longest.

On the other hand, during the driving of the vehicle, if the vehicle-mounted system (not shown), such as an event detection system, detects an event (e.g., a collision event) at a time point (hereinafter referred to as the event time point) during the driving period, the event detection system notifies the processor 1 of the event time point. Therefore, the processor 1 can extract the three driving video data and driving trajectory data from the first to third image capturing modules 201~203 and the geolocation module 204 within the unit time including the event time point, and obtain the three driving video data and driving trajectory data (as a plurality of event recording data corresponding to the time period) from a first time point earlier than the event time point, such as 15 seconds, to a second time point later than the event time point, such as 15 seconds, when the recording modules are obtained at an event time point earlier than when an event occurs to the vehicle. Afterwards, the processor 1 stores the three captured driving video data as current event files in the file blocks respectively taken from the first to third video file areas and the track file area of the event large block in accordance with the block access order assigned to the first to third video file areas and the track file area of the event large block, and stores the captured driving track data as current event file in the file block taken from the track file area of the event large block, so that the retention period of the historical event files stored in each of the first to third video file areas and the track file area of the event large block can be extended to the longest.

Furthermore, during the parking period of the vehicle, when the processor 1 obtains three parking video data of the vehicle obtained by the first to third image capturing modules 201-203 in each second unit time (for example, 3 minutes) during the parking period (as parking record data) and the driving track data of the vehicle obtained by the geolocation module 204 in the second unit time (as parking record data), the processor 1 processes the first to third video file areas and the first to third video file areas assigned to the parking large block according to the second unit time (for example, 3 minutes). The block access sequence of each track file area determines that each of the first to third video file areas and the track file area corresponds to an accessed file block of the second unit time, and the three parking video data are respectively stored as current parking files in the accessed file blocks determined in the first to third video file areas of the parking large block, so that the retention period of the historical normal files stored in each of the first to third video file areas and the track file area of the parking large block can be extended to the longest.

In summary, since the storage space of the storage medium 2 has been planned into a plurality of large blocks corresponding to a plurality of different purposes, and each large block is also planned to have a plurality of areas (such as the first to third video file areas, and the track file area) corresponding to the recording modules (such as the first to third image shooting modules 201-203, and the geolocation module 204), and each area is further divided according to the recording specifications and recording time periods of the corresponding recording modules. There are multiple file blocks with the same storage capacity, so in the same area, the processor 1 can store the record files with substantially similar file sizes in the accessed file blocks according to the corresponding block access order, so that it can not only ensure that each historical record file stored in each area is retained for the longest period of time, but also effectively avoid the file fragmentation problem encountered by the prior art, and at the same time ensure the reading and writing efficiency of the storage medium. Therefore, the driving record file management system 100 of the present invention can indeed achieve the purpose of the present invention.

However, the above is only an embodiment of the present invention and should not be used to limit the scope of implementation of the present invention. All simple equivalent changes and modifications made according to the scope of the patent application of the present invention and the content of the patent specification are still within the scope of the present patent.

100: Driving record file management system 1: Processor 2: Storage medium 201: First image shooting module 202: Second image shooting module 203: Third image shooting module 204: Geographic positioning module

Other features and effects of the present invention will be clearly presented in the implementation method with reference to the attached drawings, in which: FIG. 1 is a block diagram, exemplarily illustrating a driving record file management system of an embodiment of the present invention, and multiple image shooting modules and a positioning module arranged on a vehicle; FIG. 2 is a schematic diagram, exemplarily illustrating the division of storage space of a storage medium of the embodiment; FIG. 3 is a schematic diagram, exemplarily illustrating the situation that each of the normal large block, the event large block and the parking large area of the embodiment is divided into multiple different areas; and FIG. 4 is a schematic diagram, exemplarily illustrating the situation that each area of each of the normal large block, the event large block and the parking large area of the embodiment is divided into multiple file blocks.

100: Driving record file management system

1: Processor

2: Storage media

201: First image shooting module

202: Second image shooting module

203: Third image shooting module

204: Geolocation module

Claims (10)

A driving record file management method is used to manage a storage medium installed in a vehicle with multiple different recording modules, which is executed by a processor and includes the following steps: A storage space of the storage medium is divided into at least a normal large block, an event large block and a parking large block corresponding to normal use, event use and parking use respectively, and each of the normal large block, the event large block and the parking large block is further divided into multiple areas corresponding to the recording modules respectively, each of which is further divided into multiple file blocks with the same storage capacity; Using the priority principle, all file blocks in each area of the storage space of the storage medium are assigned a corresponding block access sequence; When multiple driving record data acquired by the recording modules at each first unit time during the driving of the vehicle are acquired, each driving record data is stored as a corresponding current normal file in a file block accessed in one of the corresponding areas of the areas of the normal large block according to the respective block access sequences of the areas of the normal large block; When obtaining a plurality of driving record data acquired by the recording modules in a time period from a first time point earlier than an event time point when an event occurs to a second time point later than the event time point, store each driving record data as a corresponding current event file in an accessed file block in one of the corresponding areas of the areas of the event large block according to the respective block access order of the areas assigned to the event large block; and When the plurality of parking record data acquired by the recording modules at each second unit time during the parking period of the vehicle is acquired, each parking record data is stored as a corresponding current parking file in an acquired file block in one of the corresponding areas of the areas of the parking area according to the respective acquisition order of the plurality of blocks of the areas assigned to the parking area. A driving record file management method as described in claim 1, wherein: The priority principle includes (i) the file blocks in the area that have never been written to any file have a first priority, (ii) the file blocks in the area that store incomplete or damaged historical record files have a second priority, and (iii) the file blocks in the area that store the earliest historical record files have a third priority; The processor determines the accessed file block in the corresponding area of the normal large block according to the corresponding block access order, so that the retention period of the historical normal files stored in the corresponding area of the normal large block can be extended to the longest; The processor determines the accessed file block in the corresponding area of the event block according to the corresponding block access sequence, so that the retention period of the historical event file stored in the corresponding area of the event block can be extended to the longest; and The processor determines the accessed file block in the corresponding area of the parking block according to the corresponding block access sequence, so that the retention period of the historical parking file stored in the corresponding area of the parking block can be extended to the longest. The driving record file management method as described in claim 1, wherein: The recording modules include multiple image capture modules and a geolocation module; The driving record data corresponding to the first unit time include multiple driving video data of the vehicle obtained by the image capture modules within the first unit time and the driving track data of the vehicle obtained by the geolocation module within the first unit time; The driving record data corresponding to the time period include multiple driving video data of the vehicle obtained by the image capture modules within the time period and the driving track data of the vehicle obtained by the geolocation module within the time period; and The driving record data corresponding to the second unit time include multiple parking video data of the vehicle obtained by the image capture modules within the second unit time. The driving record file management method as described in claim 3, wherein: The areas in the normal large block include a plurality of video file areas corresponding to the image capture modules, and a track file area corresponding to the geolocation module, wherein the storage capacity of each file block in each video file area is associated with the frame rate, the pixels per frame and the first unit time of one of the corresponding image capture modules and is slightly larger than the size of the driving video data obtained by the corresponding image capture module in the first unit time, and the storage capacity of each file block in the track file area is larger than the size of the driving track data obtained in the first unit time; The areas in the event block include a plurality of video file areas corresponding to the image capture modules and a track file area corresponding to the geolocation module, wherein the storage capacity of each file block in each video file area is associated with the frame rate, the pixels per frame and the time period of one of the corresponding image capture modules and is slightly larger than the size of the driving video data obtained by the corresponding image capture module during the time period, and the storage capacity of each file block in the track file area is larger than the size of the driving track data obtained during the time period; The areas in the parking large block include a plurality of video file areas corresponding to the image capture modules, and the storage capacity of each file block in each of them is associated with the frame rate, the pixels per frame and the second unit time of one of the corresponding image capture modules and is slightly larger than the size of the parking video data obtained by the corresponding image capture module in the second unit time. The driving record file management method as described in claim 1 further comprises the following steps: Periodically confirming whether each file stored in the storage medium is damaged, and when a damaged file is confirmed, updating the block access sequence corresponding to the area to which the damaged file belongs. A driving record file management system is suitable for being installed in a vehicle equipped with multiple different recording modules, and comprises: A storage medium having a storage space, the storage space being divided into at least a normal large block, an event large block and a parking large block corresponding to normal use, event use and parking use respectively, each of the normal large block, the event large block and the parking large block is further divided into multiple areas corresponding to the recording modules respectively, each of which is further divided into multiple file blocks with the same storage capacity; and A processor, adapted to be electrically connected to the recording modules and the storage medium and the storage module, and to assign corresponding block access sequences to all file blocks in each area of the storage space of the storage medium according to a priority principle; Wherein, when the processor receives a plurality of recorded data acquired by the recording modules in each first unit time during the driving of the vehicle, the processor stores each driving recorded data as a corresponding current normal file in a retrieved file block in one of the corresponding areas of the areas of the normal large block according to the respective block access sequences of the areas of the normal large block; Wherein, when the processor obtains a plurality of driving record data obtained by the recording modules in a time period from a first time point earlier than an event time point when an event occurs to a second time point later than the event time point, the processor stores each driving record data as a corresponding current event file in a retrieved file block in one of the corresponding areas of the areas of the event large block according to the respective block retrieval order of the areas assigned to the event large block; and When the processor receives a plurality of parking record data acquired by the recording modules at each second unit time during the parking period of the vehicle, the processor stores each parking record data as a corresponding current parking file in a retrieved file block in one of the corresponding areas of the areas of the parking large block according to the respective block retrieval order of the areas assigned to the parking large block. A driving record file management system as described in claim 6, wherein: The priority principle includes (i) the file blocks in the area that have never been written to any file have a first priority, (ii) the file blocks in the area that store incomplete or damaged historical record files have a second priority, and (iii) the file blocks in the area that store the earliest historical record files have a third priority; The processor determines the accessed file block in the corresponding area of the normal large block according to the corresponding block access order, so that the retention period of the historical normal files stored in the corresponding area of the normal large block can be extended to the longest; The processor determines the accessed file block in the corresponding area of the event block according to the corresponding block access sequence, so that the retention period of the historical event file stored in the corresponding area of the event block can be extended to the longest; and The processor determines the accessed file block in the corresponding area of the parking block according to the corresponding block access sequence, so that the retention period of the historical parking file stored in the corresponding area of the parking block can be extended to the longest. The driving record file management system as described in claim 6, wherein: The recording modules include multiple image capture modules and a geolocation module; The driving record data corresponding to the first unit time include multiple driving video data of the vehicle obtained by the image capture modules within the first unit time and the driving track data of the vehicle obtained by the geolocation module within the first unit time; The driving record data corresponding to the time period include multiple driving video data of the vehicle obtained by the image capture modules within the time period and the driving track data of the vehicle obtained by the geolocation module within the time period; and The driving record data corresponding to the second unit time include multiple parking video data of the vehicle obtained by the image capture modules within the second unit time. A driving record file management system as described in claim 8, wherein: The areas in the normal large block include a plurality of video file areas corresponding to the image capture modules, and a track file area corresponding to the geolocation module, wherein the storage capacity of each file block in each video file area is associated with the frame rate, the pixels per frame and the first unit time of one of the corresponding image capture modules and is slightly larger than the size of the driving video data obtained by the corresponding image capture module in the first unit time, and the storage capacity of each file block in the track file area is larger than the size of the driving track data obtained in the first unit time; The areas in the event block include a plurality of video file areas corresponding to the image capture modules and a track file area corresponding to the geolocation module, wherein the storage capacity of each file block in each video file area is associated with the frame rate, the pixels per frame and the time period of one of the corresponding image capture modules and is slightly larger than the size of the driving video data obtained by the corresponding image capture module during the time period, and the storage capacity of each file block in the track file area is larger than the size of the driving track data obtained during the time period; The areas in the parking large block include a plurality of video file areas corresponding to the image capture modules, and the storage capacity of each file block in each of them is associated with the frame rate, the pixels per frame and the second unit time of one of the corresponding image capture modules and is slightly larger than the size of the parking video data obtained by the corresponding image capture module in the second unit time. The driving record file management system as described in claim 6, wherein the processor also periodically confirms whether each file stored in the storage medium is damaged, and when a damaged file is confirmed, updates the block access sequence corresponding to the area to which the damaged file belongs.

Images