KR101698936B1 - Data storage system and method thereof - Google Patents

Abstract

The present invention relates to a file system module for restoring a directory entry based on the existence of an old rename file log for responding to an abnormal event, a file system module for restoring a directory entry (old temp file log) A file manager module for providing a first interface for determining at least one of a format for a memory card in which the legitimate temporary file log exists and a creation for a new temp file log based on whether or not the legitimate temporary file log exists, And a recording manager module for providing file name request information on the data to the file manager module.

Description

[0001] DATA STORAGE SYSTEM AND METHOD THEREOF [0002]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data storage system and an operation method thereof, and more particularly, to a data storage system and an operation method thereof, in which at least one file among previously stored data is renamed and reused.

A conventional data storage system records recording data including at least one of image, video and audio, records attribute information of a file of recording data in a directory entry, and records the recorded recording data in a database And adopts a method of updating.

However, if the data storage system is stopped due to an abnormal event (for example, an event in which power is forcibly cut off due to a power failure) before being updated in the database, the attribute information of the file is not recorded and the recording data can not be reproduced Can occur.

Also, when a data storage system based on a file allocation table (FAT) newly generates and stores files corresponding to a plurality of recording data, file fragmentation may occur due to each of the scattered recording data For this reason, there is a problem that the storage speed is decreased and the performance of the system is deteriorated.

Korean Patent No. 100844058 (2008.07.07). "File deletion method, file open method, file deletion program, and file open program" Korean Patent No. 100628543 (September 19, 2006). "Recording medium &

The present invention provides a data storage system compatible with a file allocation table-based file system by renaming and reusing the name of at least one file among previously stored data, and an operation method thereof.

The present invention provides a data storage system for restoring a directory entry using a rename file log in a process of booting a system when attribute information included in the directory entry is lost due to an abnormal event, and an operation method thereof.

The present invention provides a data storage system and method for efficiently managing recording data by determining whether a temporary file log is formatted or not based on the presence or absence of a temporary file log.

The data storage system according to an embodiment of the present invention includes a file system module for restoring a directory entry based on the existence of an old rename file log for responding to an abnormal event, A first interface for determining at least one of a format for the memory card in which the legitimate temporary file log exists and a new temp file log based on whether the old temp file log exists; And a recording manager module for providing the file manager module with the file name request information about the recording data.

Wherein the file manager module provides a second interface for renaming at least one file among the pre-stored data in response to the file name request information, and the file system module renames the at least one file Records a new rename file log to be acquired, and the recording manager module can record the recording data corresponding to the rename file.

The second interface displays list information of at least one of name information, extension information, date information, time information, size information, and weight information of the at least one file in response to the file name request information, Selects the at least one file in consideration of the selected file, renames the selected file, and provides the path of the rename file to the recording manager module.

Wherein the file manager module provides a third interface for storing the recorded recording data in a database, the file system module records the recorded new rename file log in the directory entry, When completed, the recorded new rename file log can be removed.

The file system module may restore the directory entry in which the recording is not completed using the new rename file log if the recording of the directory entry is not completed due to the abnormal event.

In addition, if the creation of the new temporary file log is not completed due to the abnormal event, the file manager module updates the format of the memory card in which the new temporary file log has not been generated and the new temporary file log renew temp file log) to the first interface.

The file system module according to an embodiment of the present invention includes a restoration unit for restoring a directory entry based on whether an old name file log for responding to an abnormal event exists or not, An entry recorder for recording the new rename file log recorded in the directory entry, and a new rename file log for recording the new rename file log when the recording of the directory entry is completed And a liner removal section.

If the recording of the directory entry is not completed due to the abnormal event, the restoring unit may restore the directory entry in which the recording is not completed using the new rename file log.

In addition, the restoring unit may be interlocked with a file manager module for providing a first interface for determining at least one of a format of the temporary temporary file log and a creation of a new temporary file log based on the existence of the temporary temporary file log .

The file manager module according to an embodiment of the present invention may be configured to record at least one of a format for a memory card in which the legitimate temporary file log exists and a new temporary file log A first interface for providing a first interface for determining one, and a second interface for renaming at least one file of previously stored file data in response to the file name request information provided by the recording manager module And a third interface for providing a third interface for storing the recorded recording data in a database.

If the creation of the new temporary file log is not completed due to the abnormal event, the first interface unit performs a format for the memory card in which the new temporary file log that has not been generated exists and a new temporary file log Lt; RTI ID = 0.0 > 1 < / RTI >

The second interface unit displays list information of at least one of name information, extension information, date information, time information, size information and weight information of the at least one file in response to the file name request information; A selection unit for selecting the at least one file in consideration of the list information, a rename unit for renaming the selected file, and a path providing unit for providing the path of the rename file to the recording manager module.

The second interface unit records the new rename file log obtained by the rename file, records the new rename file log in the directory entry, removes the new rename file log File system module.

A method of operating a data storage system according to an exemplary embodiment of the present invention includes restoring a directory entry based on the existence of an old name file log for responding to an abnormal event through a file system module, Providing a first interface for determining at least one of a format for a memory card in which the legitimate temporary file log exists and a new temporary file log based on the presence or absence of a file log; And providing file name request information for the data to the file manager module.

The present invention can be compatible with a file allocation table based file system by renaming and reusing the name of at least one file among pre-stored data.

In a case where attribute information included in a directory entry is lost due to an abnormal event, the present invention can restore the directory entry using the rename file log during the booting of the system.

The present invention can efficiently manage the recording data by determining whether the temporary file log is formatted or not based on the existence of the temporary file log or not.

1 is a block diagram illustrating a data storage system in accordance with an embodiment of the present invention.
2 is a block diagram illustrating a file system module according to an embodiment of the present invention.
3 is a block diagram illustrating a file manager module according to an embodiment of the present invention.
4 is a block diagram illustrating the second interface unit of FIG.
5 is a flow chart illustrating a method of operating a data storage system.
6 is a flowchart illustrating an operation method of a data storage system according to another embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and accompanying drawings, but the present invention is not limited to or limited by the embodiments.

In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The terminology used herein is a term used for appropriately expressing an embodiment of the present invention, which may vary depending on the user, the intent of the operator, or the practice of the field to which the present invention belongs. Therefore, the definitions of these terms should be based on the contents throughout this specification.

1 is a block diagram illustrating a data storage system in accordance with an embodiment of the present invention.

Referring to FIG. 1, a data storage system 100 includes a file system module 200, a file manager module 300, and a recording manager module 400.

The data storage system 100 records recording data including at least one of image, video and audio, records attribute information of a file of recording data in a directory entry, The recording data can be updated in the database.

Here, the directory entry is a data structure used to represent a directory, and may be attribute information including at least one of name information, extension information, date information, time information, and size information of a file.

In addition, the data storage system 100 may rename at least one of the pre-stored data to be compatible with a file allocation table (FAT) -based file system, The recording data can be stored or updated.

Also, the data storage system 100 can be included in a black box mounted on a vehicle, can set a recording mode, and can record a situation occurring around the vehicle based on a set recording mode.

Here, the recording mode may include at least one of a normal recording mode, a motion recording mode, and a manual recording mode.

The continuous recording mode may include a function of recording a situation occurring around the vehicle in a state in which the vehicle is in a turned off state and in a running state in real time, and the motion recording mode may include a function of recording a situation occurring around the vehicle in a running state , And the manual recording mode may include the ability to record a situation occurring around the vehicle forcefully in response to a user (e.g., a vehicle driver) request.

Recording data can be used as a means of solving traffic accident disputes and a means of solving crime cases that protect the user's interests.

Each recording mode may be recorded in a temporary file log and the data storage system 100 may generate a temp file log.

According to the embodiment, the data storage system 100 may store at least one of a process of recording a directory entry (a first process), a process of generating a temporary file log (a second process) and a process of recording recording data (a third process) There may be an unusual event (e.g., an event that the black box vehicle is turned off due to a power failure, an event in which the power is forcibly turned off by the system's own power failure, etc.).

The abnormal events in the first and second processes can be solved by restoring the directory entry using the rename file log, the format for the memory card in which the temporary file log exists, and regenerating the temporary file log. In the third process, The event may not be a problem since a part of the recording data is stored in the database and there is no difficulty in reproducing it.

Here, the rename file log (or the old / new rename file log) can be used to recover an unrecorded directory entry when an abnormal event occurs.

More specifically, when an abnormal event occurs before the recording of the directory entry is completed, the data storage system 100 may be difficult to reproduce the recording data because the attribute information included in the directory entry is lost. You can restore the directory entry using the file log.

In addition, if an abnormal event occurs before the generation of the temporary file log is completed, the data storage system 100 may be unable to record the recording data because the attribute information of the recording mode included in the temporary file log is lost, The temporary file log can be overcome by using the format of the memory card in which the temporary file log exists and by regenerating the temporary file log. Here, the memory card may be a secure digital (SD) card. Hereinafter, a process of processing an abnormal event will be described in detail.

The file system module 200 restores the directory entry based on whether an old rename file log exists for responding to an abnormal event.

According to the embodiment, the file system module 200 can determine whether there is an old name file log in the system booting process. If the old name file log exists, the file system module 200 can restore the directory entry. If there is no log, it is determined that an abnormal event has not occurred, and the directory entry restoration process can be omitted.

The file manager module 300 determines whether or not the format of the memory card in which the legitimate temporary file log exists is based on whether or not the old temp file log exists and whether or not the new temp file log is generated And provides a first interface for determining at least one.

According to the embodiment, the file manager module 300 can format the whole memory card in which the legitimate temporary file log exists if the legitimate temporary file log exists, and judges that the abnormal event does not occur if the legitimate temporary file log does not exist So that the formatting process can be omitted.

Also, the file manager module 300 can generate a new temporary file log according to the format of the memory card in which the legitimate temporary file log exists, and generate a new temporary file log based on the user selected input.

Here, the temporary file log (the guideline temporary file log or the new temporary file log) may be generated based on the above-described recording mode, and may be reference information of the recording data recorded according to the recording mode, The reference information used to rename the file of the file.

The recording manager module 400 provides the file manager 300 with the file name request information for the recording data.

According to an embodiment, the recording manager module 400 may record recording data corresponding to the recording mode by referring to at least one of the archived temporary file log and the new temporary file log.

Since the recording manager module 400 is required to store the recording data recorded in the rename file in the database, the recording manager module 400 can generate the file name request information and send the generated file name request information to the file manager module 300).

The file manager module 300 may provide a second interface for renaming the name of at least one of the stored data in response to the file name request information.

Here, the second interface displays list information of at least one of name information, extension information, date information, time information, size information, and weight information of at least one file in response to the file name request information, Selects at least one file, renames the selected file, and provides a path of the renamed file to the recording manager module 400.

The extension information may be information that distinguishes images, video, and audio. The date information may include file creation date information and modification date information. The weight information may include information indicating the importance of the file by the user's selection input , Information indicating a file of a situation in which a traffic accident occurred in the past, or the like).

The file system module 200 can record the new rename file log obtained by renaming at least one file and the recording manager module 400 can record the recording data corresponding to the rename file .

The file manager module 300 may provide a third interface for storing the recorded recording data in the database, and the file system module 200 records the new rename file log recorded in the directory entry, When the recording is completed, the recorded new rename file log can be removed.

According to the embodiment, if the recording of the directory entry is not completed due to the abnormal event, the file system module 200 can restore the directory entry in which the recording is not completed using the new rename file log.

If the creation of the new temporary file log is not completed due to an abnormal event, the file manager module 300 may notify the format of the new temporary file log that has not yet been generated, And generating a first interface for determining at least one of the creation and the creation.

Here, the directory entry restoration process can be automatically performed during the booting process of the data storage system 100, and the format for the memory card in which the new temporary file log exists and the process for generating the new temporary file log are input to the user input Can operate on the basis of.

2 is a block diagram illustrating a file system module according to an embodiment of the present invention.

2, the file system module 200 includes a restoring unit 210, a rename recording unit 220, an entry recording unit 230, and a rename removing unit 240.

The restoring unit 210 restores the directory entry on the basis of the presence or absence of an old name file log for responding to an abnormal event.

The rename logger 220 records a new rename file log obtained by renaming at least one file among the previously stored data, and the entry logger 230 records the recorded rename file log in the directory entry, The rename removal unit 240 removes the recorded new rename file log when the recording of the directory entry is completed.

According to the embodiment, if the recording of the directory entry is not completed due to the abnormal event, the restoring unit 210 can restore the directory entry whose recording has not been completed using the new rename file log.

In addition, the restoring unit 210 may include a file manager module for providing a first interface for determining at least one of a format for a legitimate temporary file log and a creation of a new temporary file log on the basis of existence of a legitimate temporary file log, Can be interlocked. The file system module 200 will be described in detail with reference to FIG.

3 is a block diagram illustrating a file manager module according to an embodiment of the present invention.

Referring to FIG. 3, the file manager module 300 includes a first interface 310, a second interface 320, and a third interface 330.

The first interface unit 310 determines at least one of a format for a memory card in which a legitimate temporary file log exists and a generation of a new temporary file log based on whether or not a legitimate temporary file log for responding to an abnormal event exists Lt; / RTI > interface.

According to the embodiment, the first interface unit 310 may include a first interface for determining at least one of a format for a memory card in which a legitimate temporary file log exists and a new temporary file log, Can be provided.

The second interface unit 320 provides a second interface for renaming at least one file among the pre-stored file data in response to the file name request information provided by the recording manager module 400. Hereinafter, the second interface unit 320 will be described in detail with reference to FIG.

4 is a block diagram illustrating the second interface unit of FIG.

4, the second interface unit 320 may include a list display unit 321, a selection unit 322, a rename unit 330, and a path providing unit 340.

The list display unit 321 may display list information about at least one of name information, extension information, date information, time information, size information, and weight information of at least one file in response to the file name request information.

The selection unit 322 can select at least one file in consideration of the list information, the rename unit 330 renames the selected file, and the path providing unit 340 sends the path of the renamed file to the recording manager module . The file manager module 300 will be described in detail with reference to FIG.

Referring again to FIG. 3, the second interface unit 320 records a new rename file log obtained by the rename file, records the new rename file log in the directory entry, It can be associated with a file system module that removes the name file log.

The third interface unit 330 provides a third interface for storing the recorded recording data in the database.

5 is a flow chart illustrating a method of operating a data storage system.

Referring to FIG. 5, the data storage system restores the directory entry based on the presence or absence of an old name file log for responding to an abnormal event, at step 510.

According to an embodiment, the data storage system can determine whether an old name file log is present in the system boot process at step 510, restore the directory entry if an old name file log exists, If the file log does not exist, it is determined that an abnormal event has not occurred and the directory entry restoration process can be omitted.

The data storage system provides a first interface for determining at least one of whether to format the memory card in which the legitimate temporary file log exists and whether to generate a new temporary file log based on the presence or absence of the legitimate temporary file log in step 520 do.

According to the embodiment, the data storage system can format the memory card in which the legitimate temporary file log exists if the legitimate temporary file log exists, and judges that the abnormal event does not occur if the legitimate temporary file log does not exist So that the formatting process can be omitted.

In addition, the data storage system may generate a new temporary file log by the format of the memory card in which the legitimate temporary file log resides, and may generate a new temporary file log based on the user selected input.

In step 530, the data storage system provides file name request information for the recording data to the file manager module 300.

According to the embodiment, in step 530, since the recording data recorded in the rename file stored in the pre-stored data must be stored in the database, the data storage system can generate the file name request information, To the file manager module 300.

6 is a flowchart illustrating an operation method of a data storage system according to another embodiment of the present invention.

Referring to FIG. 6, the data storage system may restore the directory entry based on the existence of an old name file log for responding to an abnormal event at system startup (boot), and restore the directory entry in the file system module .

According to an embodiment, the data storage system can determine whether an old name file log is present during a boot process, restore a directory entry if an old name file log exists, and if an old name file log does not exist , It is determined that an abnormal event has not occurred and the directory entry restoration process can be omitted.

The data storage system may provide a first interface for determining at least one of whether to format a memory card in which a legitimate temporary file log exists and whether to generate a new temporary file log based on the presence or absence of a legitimate temporary file log, File manager module.

Also, the data storage system may have an application in which a file system module and a file manager module are application programs for interlocking with each other.

More particularly, the data storage system may determine at least one of whether to format the memory card in which the legitimate temporary file log is present and whether to create a new temporary file log based on various embodiments, such as a legitimate temporary file log and a user- Can provide a first interface.

In addition, the data storage system may store a legitimate temporary file log or a new temporary file log in a memory card, and may be implemented in a file manager module that provides a third interface.

If the temporary file log or the temporary temporary file log is stored in the memory card, the data storage system can generate the file name request information, provide the generated file name request information to the file manager module, have.

The data storage system may provide a second interface for renaming the name of at least one of the stored data in response to the file name request information, and may be provided in the file manager module.

Here, the second interface displays list information of at least one of name information, extension information, date information, time information, size information, and weight information of at least one file in response to the file name request information, Selects at least one file, renames the selected file, and provides a path of the renamed file to the recording manager module.

According to an embodiment, the second interface may adjust the size of the selected file.

More specifically, the second interface may adjust the size of the selected file to an original size allocated from a file allocation table (FAT). Here, adjusting the selected file to the original size allocated in the file allocation table means truncating the selected file to the original size allocated in the file allocation table.

For example, the file allocation table may allocate each file existing in the pre-stored data to a predetermined size, and the data storage system may rename the file allocated through the second interface.

In addition, the data storage system can be additionally allocated to files in the file allocation table with an increase in the size of the allocated file. If this process is repeated, file fragmentation may occur. In order to reduce file fragmentation, You can adjust the file size to the original size assigned in the file allocation table.

The data storage system can record a new rename file log obtained by renaming at least one file name and record the recorded rename file log in the directory entry. When the recording of the directory entry is completed, The new rename file log can be removed and can be done in the file system module.

In addition, the data storage system can record the recording data corresponding to the rename file in the recording manager module, store the recorded recording data in the database, and store it in the database simultaneously with recording in real time.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI > or equivalents, even if it is replaced or replaced.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

100: Data storage system
200: File system module
210:
220:
230: entry log
240: Rename removal
300: File manager module
310: first interface unit
320:
321: List display section
322:
323: Lineage
324:
330:
400: Recording Manager Module

Claims (15)

A file system module for restoring a directory entry based on whether an old rename file log for responding to an abnormal event exists;
A method for determining at least one of a format for a memory card in which the legitimate temporary file log exists and a generation for a new temp file log based on whether a legitimate temporary file log exists A file manager module for providing a first interface; And
A recording manager module for providing file name request information for recording data to the file manager module;
/ RTI >
The file manager module
If the creation of the new temporary file log is not completed due to the abnormal event, the format for the memory card in which the new temporary file log for which generation has not been completed and the new temporary file log for the renewed temp file log Providing the first interface for determining at least one of < RTI ID = 0.0 >
Data storage system. The method according to claim 1,
The file manager module
Providing a second interface for renaming at least one file of previously stored data in response to the file name request information,
The file system module
Recording a new rename file log obtained by renaming the name of the at least one file,
The recording manager module
And recording the recording data corresponding to the rename file
Data storage system. 3. The method of claim 2,
The second interface
And displaying list information of at least one of name information, extension information, date information, time information, size information, and weight information of the at least one file in response to the file name request information, Selects one file, renames the selected file, and provides the path of the rename file to the recording manager module
Data storage system. 3. The method of claim 2,
The file manager module
A third interface for storing the recorded recording data in a database,
The file system module
Records the new rename file log recorded in the directory entry, and deletes the recorded new rename file log when the recording of the directory entry is completed
Data storage system. 5. The method of claim 4,
The file system module
If the recording of the directory entry is not completed due to the abnormal event, the directory entry whose recording has not been completed is restored using the new rename file log
Data storage system. delete A restoration unit restoring a directory entry based on whether or not an old-style name file log for responding to an abnormal event exists;
A re-name recording unit for recording a new rename file log obtained by renaming at least one file among the pre-stored data;
An entry recording unit for recording the recorded new rename file log in the directory entry; And
When the recording of the directory entry is completed, removing the recorded new rename file log,
Lt; / RTI >
The restoring unit
If the recording of the directory entry is not completed due to the abnormal event, the directory entry whose recording has not been completed is restored using the new rename file log
File system module. delete 8. The method of claim 7,
The restoring unit
A file manager module for providing a first interface for determining at least one of a format of the temporary temporary file log and a creation of a new temporary file log based on whether or not the temporary temporary file log exists
File system module. Providing a first interface for determining at least one of a format for a memory card in which the legitimate temporary file log exists and a generation for a new temporary file log based on the presence or absence of a legitimate temporary file log for responding to an abnormal event A first interface unit;
A second interface for providing a second interface for renaming the name of at least one of the previously stored file data in response to the file name request information provided by the recording manager module; And
A third interface unit for providing a third interface for storing the recorded recording data in the database,
Lt; / RTI >
The first interface unit
If the creation of the new temporary file log is not completed due to the abnormal event, a determination is made as to at least one of a format for the memory card in which the new temporary file log has not been generated and a creation of a new temporary file log Providing the first interface for < RTI ID = 0.0 >
File manager module. delete 11. The method of claim 10,
The second interface unit
A list display unit for displaying list information of at least one of name information, extension information, date information, time information, size information and weight information of the at least one file in response to the file name request information;
A selection unit for selecting the at least one file in consideration of the list information;
A rename section for renormalizing the selected file; And
Path providing unit for providing the path of the rename file to the recording manager module,
A file manager module comprising: 11. The method of claim 10,
The second interface unit
A new rename file log obtained by the rename file is recorded, a new rename file log recorded is recorded in a directory entry, and a new rename file log
File manager module. Restoring a directory entry based on the presence or absence of an old name file log for responding to an abnormal event through a file system module;
Providing a first interface for determining at least one of a format for a memory card in which the legitimate temporary file log exists and a generation for a new temporary file log based on the existence of the legitimate temporary file log through the file manager module ; And
Providing file name request information for recording data to the file manager module through a recording manager module
Lt; / RTI >
The file manager module
If the creation of the new temporary file log is not completed due to the abnormal event, the format for the memory card in which the new temporary file log for which generation has not been completed and the new temporary file log for the renewed temp file log Providing the first interface for determining at least one of < RTI ID = 0.0 >
The method comprising the steps of: A computer-readable recording medium having recorded thereon a program for performing the method of claim 14.

Images