KR20040087161A - File content management method for mobile communication terminal - Google Patents

Abstract

PURPOSE: A method for managing a file capacity of a mobile terminal is provided to prevent a waste of a space for storing a file by checking an available capacity of a file system to manage a file. CONSTITUTION: It is checked whether total bytes for storage is smaller than the sum of total bytes of a stored file and total requested bytes in order to determine whether to generate a file(S41). If generating a file is determined, a name, a file name and a generation mode are designated and a file is generated(S42). And then a newly generated file handle is allocated to a file handle(S43). The number of generated files is increased, the total requested bytes are added to the total stored bytes, and the generated file is registered for an open file table(S44). If generating a file is refused, null is allocated to the file handle to inform that file cannot be generated(S45).

Description

FILE CONTENT MANAGEMENT METHOD FOR MOBILE COMMUNICATION TERMINAL}

The present invention relates to a file capacity management method of a mobile communication terminal, and more particularly, to a file capacity management method of a mobile communication terminal capable of managing information stored in a file system by a storage file capacity of a file management method of a mobile communication terminal. It is about.

The file size management method of the conventional mobile communication terminal manages the file capacity by grasping the number of files to be stored. The file size management method using the number of files manages the file storage capacity using the number of files defined by the file system regardless of the size of the file and the capacity of the file system. Therefore, if the size of the content stored in the individual file is smaller than the initial expected size, waste of storage space may occur.

The file management method of the conventional file system designates the number of files to be managed, assigns IDs and storage spaces for each file according to the number of files, retrieves empty file IDs when storing new files, and obtains file IDs and stores files. . The file ID is then used to access the file. At this time, the file ID is declared and used as enumeration data.

1 is a flowchart illustrating a file generation method in a file management method of a conventional mobile communication terminal. As shown in FIG. 1, it is determined whether a file is generated by determining whether the number of generated files is smaller than the allowed file number before generating a file. Determine (S11).

If it is determined to create a file, a name is directly designated, a file name, a generation mode, and a file is generated (S12). When the file is generated, the newly generated file handle is allocated to the file handle (S13). Then, the number of generated files is increased and a file ID disposed in the generated file is allocated (S14).

On the contrary, if file creation is rejected, a null is assigned to the file handle to inform that a file cannot be generated (S15).

2 is a flowchart illustrating a file access method in the conventional file capacity management method. As shown in FIG. 2, before accessing a file, it is determined whether an ID of a file to be accessed exists in the arranged file ID to determine whether to access the file ( S21).

When the file access is determined, the file is directly designated by the name, the file name, and the open mode (S22). When the file is opened, the open file handle is allocated to the file handle (S23). Then, the file handle is registered in the open file table (S24).

On the contrary, if the file access is denied, a null is assigned to the file handle to inform that the file cannot be accessed (S25).

3 is a flowchart illustrating a file recording method in the conventional file capacity management method. As shown in FIG. 3, a file handle, a request_content, and a request_byte are specified before recording a file (S31).

As described above, the file creation, access, and recording operations of the conventional file management method can be seen that the file is managed using the file ID when the file is created or accessed.

However, in the prior art as described above, although the application program of the mobile communication terminal accesses the file using the file ID, the user has to display the file using an access method using the file name, thereby increasing the complexity of the file management. .

In addition, even if the user changes or moves a specific file name, there is a problem that the complexity of file management is further increased.

Accordingly, the present invention has been made in view of the above problems, and an object thereof is to provide a file capacity management method of a mobile communication terminal which enables file management using a storage capacity of a file system.

1 is a flowchart illustrating a file generation method in a file capacity management method of a conventional mobile communication terminal.

2 is a flowchart illustrating a file access method in the conventional file capacity management method.

3 is an operation flowchart showing a file recording method in the conventional file capacity management method.

4 is a flowchart illustrating a file generation method in a file capacity management method of a mobile communication terminal according to the present invention;

5 is an operation flowchart showing a file access method in a file capacity management method according to the present invention;

6 is an operation flowchart showing a file recording method in the file capacity management method according to the present invention;

The present invention for achieving the above object, the step of generating a file by checking the available capacity of the file system when the file generation is requested; Accessing a file by checking whether a file name exists in a directory when a file access is requested from the file system; When the file recording is requested in the file system, the method may include verifying the available capacity of the file system and performing file recording.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

The present invention manages the available file capacity by using the capacity of the file stored in the mobile communication terminal. In addition, accessing files using file names and directory names eliminates the complexity of associating file names with file IDs.

The file capacity management method of the file system according to the present invention defines the total capacity and available capacity of the file system. When a new file is created, the available capacity of the file system is checked and the size and the available capacity of the file to be created are compared. If the file system does not have enough available space, it will refuse to create the file. On the contrary, if the available capacity is sufficient, a file is created and the generated file size is subtracted from the available capacity.

The data structure used to manage a file declares the variables as the total bytes that can be stored, the total bytes of the files that are stored, and the number of files that are stored.

FIG. 4 is a flowchart illustrating a file generation method in a file capacity management method of a mobile communication terminal according to the present invention. As shown in FIG. 4, the total bytes and requests of a file in which total bytes that can be stored before the file is generated are stored. Determining whether to generate a file by determining whether the sum is less than the total number of bytes (S41); If the file generation is determined, directly specifying a name, a file name, a generation mode, and generating a file (S42); Assigning a newly created file handle to a file handle when the file is generated (S43); Increasing the number of generated files, adding the requested total bytes to the stored total bytes, and registering the generated files in the open file table (s44); If the file creation is denied, a step (S45) is performed informing that a file cannot be generated by allocating null to a file handle.

Before generating the file, it is determined whether the file is generated by determining whether the total bytes that can be stored are smaller than the sum of the total bytes of the stored file and the total bytes requested (S41).

If the file generation is determined, the name, file name, generation mode are specified directly and the file is generated (S42). When the file is generated, a newly generated file handle is allocated to the file handle (S43). The number of generated files is increased, the requested total bytes are added to the total bytes stored, and the generated files are registered in the open file table (S44).

On the contrary, if file creation is rejected, a null is assigned to the file handle to inform that the file cannot be generated (S45).

FIG. 5 is a flowchart illustrating a file access method in the file capacity management method according to the present invention. As shown in FIG. 5, a step of determining whether to access a file is determined by determining whether a file name to be accessed exists in a directory before accessing the file. (S51); If the file access is determined, directly specifying a name, a file name, an open mode, and opening the file (S52); When the file is opened, allocating the open file handle to the file handle and registering the file handle in the open file file table (S53 and S54); If the file access is denied, the step of assigning a null to the file handle indicates that the file cannot be accessed (S55).

Before accessing the file, it is determined whether the name of the file to be accessed exists in the directory to determine whether to access the file (S51).

When the file access is determined, the name is directly specified, the file name, the open mode, and the file is opened (S52). When the file is opened, the open file handle is allocated to the file handle (S53). Then, the file handle is registered in the open file table (S54).

On the contrary, if the file access is denied, a null is assigned to the file handle to inform that the file cannot be accessed (S55).

FIG. 6 is a flowchart illustrating a file recording method in the file capacity management method according to the present invention. As shown in FIG. 6, the total bytes of the file and the total bytes requested are stored. Determining whether or not to record the file by determining whether it is smaller than the sum (S61); Recording the file by specifying a file handle, a request_content, and a request_byte when the file recording is determined (S62); Adding the requested total bytes to the total bytes of the stored file (S63); If the file recording is rejected, a step (S64) is performed in which a recording error has been specified.

Before recording the file, it is determined whether the file is to be recorded by determining whether the total bytes that can be stored are smaller than the sum of the total bytes of the stored file and the total bytes requested (S61).

When the file recording is determined, the file is recorded by specifying a file handle, a request_content, and a request_byte (S62). Then, the requested total bytes are added to the total bytes of the stored file (S63).

On the contrary, if file recording is rejected, a notification is made by specifying that a recording error has occurred (S64).

As described above, in the file capacity management method, the file creation, access, and recording operations are performed to check the available capacity of the file system when creating or recording a file, thereby performing the file creation and recording operation. And, when accessing a file, we know that the file is accessed using the file name.

As described in detail above, the present invention manages the file by checking the available capacity of the file system, thereby preventing the waste of file storage space and increasing the efficiency.

In addition, since the file is accessed using the file name and the directory name when accessing the file, the file management is not duplicated, so the file name can be easily changed and the file can be frequently changed.

Claims (4)

Generating a file by checking an available capacity of the file system when a file generation is requested; Accessing a file by checking whether a file name exists in a directory when a file access is requested from the file system; And checking the available capacity of the file system when the file recording is requested in the file system, and performing file recording. 2. The method of claim 1, wherein the file generation comprises: determining whether to generate a file by determining whether the total bytes that can be stored are less than the sum of the total bytes of the stored file and the total bytes requested; If the file generation is determined, directly specifying a name, a file name, a generation mode, and generating a file; Allocating a newly created file handle to a file handle when the file is created; Increasing the number of generated files, adding the requested total bytes to the stored total bytes, and registering the generated files in an open file table; And notifying that a file cannot be generated by allocating a null to a file handle when the file generation is denied. The method of claim 1, wherein the file access comprises: determining whether to access a file by determining whether a name of a file to be accessed exists in a directory; If the file access is determined, directly specifying a name, a file name, an open mode, and opening the file; When the file is opened, allocating the open file handle to the file handle and registering the file handle in the open file table; And notifying that the file cannot be accessed by assigning a null to the file handle when the file access is denied. 2. The method of claim 1, wherein the file recording further comprises: determining whether to record the file by determining whether the total bytes that can be stored are less than the sum of the total bytes of the stored file and the total bytes requested; Recording the file by specifying a file handle, a request_content, and a request_byte when the file recording is determined; Adding the requested total bytes to the total bytes of the stored file; And notifying that a recording error has occurred when the file recording is rejected.