CN110083573B

CN110083573B - File management method and mobile terminal

Info

Publication number: CN110083573B
Application number: CN201910360397.8A
Authority: CN
Inventors: 郭纯海
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2019-04-30
Filing date: 2019-04-30
Publication date: 2021-08-17
Anticipated expiration: 2039-04-30
Also published as: CN110083573A

Abstract

The invention discloses a file management method, which comprises the following steps: receiving a file management request generated by a file application layer based on current user operation; determining a target storage area corresponding to a target file requested to be managed by the file management request; if the target storage area is the first type storage area, file management is carried out according to the file management request under the condition that the file management request has the access right to the target storage area, and the importance degree value of the target file is higher than a preset value. By adopting the embodiment of the invention, the effective management of the file can be realized, and the reliability and the safety of the file are improved, so that the use safety and the operation stability of the mobile terminal are effectively ensured.

Description

File management method and mobile terminal

Technical Field

The present invention relates to the field of terminals, and in particular, to a file management method and a mobile terminal.

Background

With the development of terminal technology, mobile terminals become more and more popular due to more and more diversified functions, and the degree of dependence of users on mobile terminals such as smart phones is higher and higher.

Taking the storage function of the mobile terminal as an example, it is known that the storage space of the mobile terminal is getting larger and larger along with the rapid development of the mobile terminal, and more files can be stored, while the importance of different types of files is different, and the damage and loss of the files with higher importance may cause irreparable loss to the mobile terminal or the user. Therefore, as the number of files stored in the mobile terminal increases and the types of the files become rich, the management requirements for the files are continuously upgraded.

Therefore, how to effectively manage files in the mobile terminal to improve the reliability and the security of the files, so that the use security and the operation stability of the mobile terminal are effectively guaranteed, and a technical problem to be solved is urgently needed.

Disclosure of Invention

The embodiment of the invention provides a file management method and a mobile terminal, and aims to solve the problem that file management with higher importance degree in the mobile terminal is not in place.

In order to solve the technical problem, the invention is realized as follows:

in a first aspect, a file management method is provided, and the method includes:

receiving a file management request generated by a file application layer based on current user operation;

determining a target storage area corresponding to a target file requested to be managed by the file management request;

and if the target storage area is the first type storage area, under the condition that the file management request has the access authority to the target storage area, file management is carried out according to the file management request, and the importance degree value of the target file is higher than a preset value.

In a second aspect, a mobile terminal is provided, which includes:

the receiving module is used for receiving a file management request generated by the file application layer based on the current user operation;

a determining module, configured to determine a target storage area corresponding to a target file requested to be managed by the file management request;

and the management module is used for managing files according to the file management request under the condition of verifying that the file management request has the access right to the target storage area if the target storage area is the first type storage area, wherein the importance degree value of the target file is higher than a preset value.

In a third aspect, a mobile terminal is provided, comprising a processor, a memory and a computer program stored on the memory and being executable on the processor, the computer program, when executed by the processor, implementing the steps of the method according to the first aspect.

In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of the method according to the first aspect.

In the embodiment of the invention, when a file management request generated by a file application layer based on current user operation is received, type judgment is carried out on a target storage area corresponding to a target file requested to be managed, and when the target storage area is determined to be a first type storage area of a file management system, namely the importance degree value of the target file is determined to be higher than a preset value, the access authority of the file management request to the first type storage area needs to be verified, and specific file management is allowed to be carried out according to the file management request under the condition that the access authority is verified to pass, so that the file with a higher importance degree value is prevented from being damaged due to the fact that the first type storage area is accessed by mistake. Therefore, by additionally arranging the mapping management layer between the file application layer of the mobile terminal and the file management system, the specific file management process is transparent to the file application layer of the mobile terminal, namely the file application layer only needs to know the content of the file management request and does not need to pay attention to the specific file management process, at least, the association between the file application layer and the storage area where the file with the higher importance value is located is cut off, and in combination with the strict access authority control of the storage area where the file with the higher importance value is stored, the effective management of the important file is realized, the reliability and the safety of the file are improved, so that the use safety and the operation stability of the mobile terminal are effectively guaranteed.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:

FIG. 1 is a flowchart illustrating a file management method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of file management related partitioning and hierarchical relationships, according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a file creation flow in an embodiment of the invention;

FIG. 4 is a schematic diagram of a processing interface with insufficient memory space according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating an interface for file creation permission control in an embodiment of the invention;

FIG. 6 is a schematic diagram of another processing interface when the storage space is insufficient in the embodiment of the present invention;

FIG. 7 is a diagram illustrating a file reading process according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a file modification flow in an embodiment of the invention;

FIG. 9 is a schematic diagram of a file deletion flow in an embodiment of the invention;

fig. 10 is a schematic structural diagram of a mobile terminal in an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a mobile terminal in an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

There are differences in the importance of the different types of files set forth in the background section, and if mismanagement of an importance file results in file corruption, the problem of irreparable losses to the mobile terminal or the user can be solved by managing different types of files differently according to importance, based on the memory performance of the mobile terminal, such as confidential files created by some users, which if damaged or lost may cause a significant economic loss, or configuration files created by some application programs, if the damage may cause the application programs to be unable to be opened normally or to crash randomly, or some key files built in the operating system, if the damage may cause the system to be unable to be opened due to physical aging, etc., then, important files for users, applications and operating systems can be managed belonging to the same area.

From the dimension of reliability, the method of performing differential management according to importance can avoid important files for users, application programs and operating systems, and compared with common junk files, for example, temporary files which are created by users, application programs and operating systems, can be cleaned at any time and cannot be affected are treated equally, so that the situation that the probability that all files are damaged is basically the same as the memory of the mobile terminal ages is avoided.

Specifically, a non-volatile flash Memory (hereinafter referred to as "Memory") commonly used in existing mobile terminals supports setting a certain partial Area as an Enhanced Area to store files important to a User, an application program, and an operating system, such as an Enhanced User Data Area (Enhanced User Data Area) of an eMMC (embedded multimedia Card) and an Enhanced Memory Type (Enhanced Memory Type) of a UFS (unified mobile phone) file system. When the enhanced characteristics of the memory are implemented, it is currently common to convert a part of the area of the memory based on a TLC (Triple Level Cell) flash memory into an SLC (Single Level Cell) flash memory for use. Comparison of TLC flash and SLC flash is as follows in table 1:

TABLE 1

Flash memory type	SLC	TLC
			Number of bits per unit	1	3
Number of times of erasing	10 ten thousand times	1000 times (one time)
			Read time (microsecond)	25	75
Programmed time (microsecond)	300	900
			Erase time (microsecond)	300	4500
Data retention capability	High strength	Weak (weak)

As shown in table 1, it can be seen that SLC is more stable, data retention is stronger, reading and the like are faster, but the disadvantage is that the capacity of storage is only one third of that of TLC.

That is, referring to the way of setting up the enhanced area by means of the characteristics of the memory, the usable capacity of the mobile terminal is reduced, so that the size of the enhanced area is also relatively limited; and under the condition that the mobile terminal has two areas, namely an enhanced area and a common data area, the two areas need to be specially distinguished when an upper application program and a system service in the mobile terminal access the enhanced area, namely all file storage paths need to be distinguished, so that the use is inconvenient, and the access error is easily caused by disorder management.

Therefore, a new file management scheme is needed, which can effectively manage files in the mobile terminal under the characteristic that the enhanced area of the compatible memory is limited, so as to improve the reliability and the safety of the files, and thus, the use safety and the operation stability of the mobile terminal are effectively guaranteed.

The technical solutions provided by the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

Referring to fig. 1, an embodiment of the present invention provides a file management method, which can be executed by a mobile terminal. The method may specifically comprise:

step 101: and receiving a file management request generated by the file application layer based on the current operation of the user.

It can be understood that the file application layer may include an application program, a system service, and the like of an upper layer in the mobile terminal, and in the embodiment of the present invention, a uniform file management request output interface is provided for the entire file application layer, so that in the process of implementing the file management method according to the embodiment of the present invention, the file application layer only needs to generate and output a file management request according to an actual requirement corresponding to a current operation of a user, and does not need to participate in a specific file management process according to the file management request. Therefore, by realizing the unified receiving and management of different file management requests, the file application layer is provided with file management convenience, and meanwhile, the subsequent specific file management according to the file management requests is more convenient.

Step 103: and determining a target storage area corresponding to the target file requested to be managed by the file management request.

Step 105: if the target storage area is the first type storage area, file management is carried out according to the file management request under the condition that the file management request has the access right to the target storage area, and the importance degree value of the target file is higher than a preset value.

In the file management method according to the embodiment of the present invention, the importance degree value of the file may be represented by the score of the importance score or the size of the importance level of the file. For example, the importance score may be determined by detecting the number or proportion of preset keywords contained in the name or content of the target file, and using the number or proportion as the importance value of the file, for example, a score corresponding to an interval in which the number or proportion of the contained preset keywords is located may be determined as the importance score of the target file, where the preset keywords are words capable of representing the importance of the file; in addition, the final importance score of the target file can be comprehensively determined by combining the importance scores corresponding to the file types to which the target file belongs. Further, the importance level corresponding to the importance score can be determined according to the corresponding relation between the score and the level, so as to obtain the importance level of the file.

The preset keywords, the number or the proportion of the preset keywords, the interval, the corresponding relation between the interval and the score, the corresponding relation between the file type and the importance score, the corresponding relation between the score and the grade and the like can be specifically set according to the actual situation of file management so as to distinguish the importance degree of different files.

Optionally, the file management method provided in the embodiment of the present invention may further include the following steps:

and if the target storage area is the second type storage area, performing file management in the target storage area according to the file management request, wherein the importance degree value of the file in the first type storage area is higher than that of the file in the second type storage area.

It can be understood that, according to the difference of the importance degree of the file, the file can be divided into at least two types of storage areas, namely a first type storage area and a second type storage area, and specifically, the file with a higher importance degree value can be stored in the first type storage area, and the file with a lower importance degree value can be stored in the second type storage area, so as to implement partition management on the file; further, when the target storage area corresponding to the target file is the first type storage area, the access authority of the file management request needs to be verified to ensure the security and stability of the file management based on the first type storage area, and when the target storage area corresponding to the target file is the second type storage area, the file management can be directly performed in the target storage area without verifying the access authority to ensure the efficiency of the file management.

Optionally, the first type storage area may correspond to an enhanced data storage area in the mobile terminal, and the second type storage area may correspond to a general data storage area in the mobile terminal; the enhanced data storage area is usually invisible to the user, for example, for a mobile terminal with 64GB storage space, the storage space available to the user may be only 58GB, and another limited storage space of 6GB corresponds to the enhanced data storage area.

It should be noted that in other embodiments of the present invention, more than two types of storage areas may be divided according to different importance levels of files, so as to adapt to different document management requirements.

It can be understood that, according to different specific contents of the file management request, file management of different aspects of the target file can be realized based on the file management request to meet diversified file management requirements, and a specific process of the file management is described below in combination with a case that the target storage area corresponding to the target file is the first type storage area and it is verified that the file management request has an access right to the target storage area.

In an embodiment of the present invention, the file management request may be a file creation request, that is, a target file needs to be created based on a request of a file application layer, that is, a corresponding current user operation is to create, that is, store, a new file in the first type storage area.

Further, in this embodiment, the step 105 may be specifically executed as: and creating the target file according to the type of the target file and the target storage space required by the creation of the target file.

The created target file has a target link file which forms a mapping relation with the target file, and the target link file comprises storage path information of the target file.

It can be understood that, when a file application layer needs to create a new file in a target storage area (i.e. a first type storage area) for storing a file with a higher importance value, the type of the target file to be created and the target storage space required for creating the target file need to be further considered to achieve stricter file management for the target storage area, that is, by managing and controlling the file types and occupied spaces allowed to be stored in the target storage area, effective creation management of important files of a specified type is achieved, so as to improve the reliability and security of the file in the target storage area.

It is further understood that, in this specific embodiment, the file management method may further include the following steps:

and after the target file is created, creating a target link file having a mapping relation with the target file, wherein the target link file comprises the storage path information of the target file.

It can be understood that after the creation of the target file is completed in the target storage area, a target link file including storage path information of the target file may be further created, so as to implement mapping management on the files stored in the first type storage area, so as to facilitate efficient management on the target file already stored in the target storage area based on the target link file.

Preferably, the object link file corresponding to the object file may be stored in a second type storage area for storing files with lower importance, and thus, management of the files stored in the first type storage area and the second type storage area may be implemented based on the second type storage area.

In addition, optionally, the target link file corresponding to the target file may also be stored in the first type storage area for storing the file with higher importance or in the mapping management layer.

Optionally, the step of creating the target file according to the type of the target file and the target storage space required for creating the target file may be specifically executed as:

and if the type of the target file is the first type, if the residual storage space of the first sub-area for creating the target file is larger than or equal to the target storage space, creating the target file in the first sub-area, wherein the first sub-area is one of the plurality of sub-areas of the target storage area.

And under the condition that the type of the target file is a second type, if the size of the target storage space is smaller than or equal to a first set threshold, creating the target file in a second sub-area of the target storage area, wherein the first set threshold is related to the type of the target file, and the second sub-area is different from the first sub-area.

It can be understood that according to the difference of file types, the target storage area is further subjected to area division, and meanwhile, the size of the storage area used for storing the file with the higher importance degree value is limited, so that different sub-areas of the target storage area can be used for correspondingly storing different types of files, the requirement of partition storage on different types of files is met, and meanwhile, effective management and control on the files are further realized through management and control on the size of the storage space occupied by the files.

Specifically, when a file of a first type is created in a target storage area, it is necessary to determine a size relationship between a target storage space required for creating the target file and a remaining storage space of a first sub-area allocated for the file of the first type, and if the remaining storage space is sufficient, the target file is allowed to be created in the first sub-area of the target storage area.

Optionally, if the remaining storage space is not enough to create the object file, the cleaning of the storage space of the first sub-area may be prompted to make enough storage space for creating the object file, or the creation of the object file in the object storage area may be abandoned, for example, the creation of the object file in the second type storage area may be selected.

Alternatively, the first type of document may include a user-important document, such as a contract document, a security document, and the like.

When a file of a second type is created in a target storage area, it is necessary to determine a size relationship between a target storage space required for creating the target file and a storage space having a first set threshold value and matching the type of the target file, and if the size of the target storage space is within the first set threshold value, the target file is allowed to be created in a second sub-area of the target storage area, which is different from the first sub-area.

Optionally, if the size of the target storage space is larger than the first set threshold, the first set threshold may be prompted to be modified to a value larger than the size of the storage space required by the target file, or the occupied storage space corresponding to the type of the target file may be prompted to be cleared to make up enough storage space for creating the target file, or the creation of the target file in the target storage area may be abandoned, for example, the creation of the target file in the second type storage area may be selected.

Optionally, the second type of file may include a key configuration file corresponding to the application program, and specifically, the corresponding first setting threshold may be set for different application programs, that is, the type of the target file corresponds to the specific application program.

It is to be understood that, in the case where the file management request is a file creation request, the target file is a file that is not stored in the target storage area, and based on the above, the target file may be stored in the target storage area in accordance with the file management request, in the case where a certain condition is satisfied.

Then, optionally, in the file management method provided in the embodiment of the present invention, the target file may also be a file already stored in a target storage area that is a first-type storage area, that is, the target file already stored in the target storage area needs to be subjected to file management according to a request of a file application layer; wherein the process of storing the object file in the object storage area, which is the first-type storage area, may be performed with reference to the contents of the creation object file.

Further, step 105 may be specifically executed as:

determining a created link file corresponding to the target file;

searching a target file according to the storage path information contained in the created link file;

and operating the target file according to the file management request.

It can be understood that when the file application layer needs to perform file management on a target file with a higher importance value stored in a target storage area (i.e., a first-type storage area), the created link file corresponding to the target file can enter the corresponding file storage area, so that the target file can be accurately and efficiently found, and then the target file can be operated according to the specific content of the file management request, thereby achieving efficient file management.

Optionally, in the file management method provided in the embodiment of the present invention, the file management request may be any one of a file reading request, a file renaming request, a file modifying request, and a file deleting request.

In another embodiment of the present invention, when the file management request is a file modification request, the target file needs to be modified based on a request of the file application layer, that is, the corresponding current user operation is to modify the stored file in the first type storage area.

Further, the step of operating the target file according to the file management request may be specifically implemented as:

in the process of modifying the target file, acquiring the size of the storage space actually occupied by the target file;

and under the condition that the size of the storage space actually occupied by the target file exceeds a second set threshold, determining a target processing mode based on the type of the target file, and finishing the modification of the target file based on the target processing mode, wherein the second set threshold corresponds to the type of the target file.

It can be understood that, in consideration of the limitation of the storage space of the first type storage area for storing the file with a higher importance value, in the process of modifying the target file, the size of the storage space actually occupied by the target file needs to be accurately detected, so that under the condition that the size of the storage space actually occupied by the target file exceeds the corresponding second set threshold, the modification of the target file can be completed by respectively adopting different processing modes according to different types of the target file; therefore, the modification requirements of the files of different types can be met by respectively matching the files of different types with the corresponding storage space processing modes, and the effect of efficient file management is achieved.

Specifically, in the case that the type of the target file is the first type, it is necessary to check whether the size of the storage space actually occupied by the target file in the modification process exceeds the size (i.e., the second set threshold) of the remaining storage space of the first sub-area partitioned from the target storage area and used for storing the first type of file, that is, to determine whether the first sub-area has enough remaining storage space for storing the modified target file. Further, if the target file is not exceeded, the modification of the target file can be completed in the target storage area, and if the target file is exceeded, the cleaning of the storage space of the first sub-area can be prompted to make up enough storage space for storing the modified target file.

In addition, in the case where the type of the target file is the second type described above, it is necessary to check whether the size of the storage space actually occupied by the target file in the modification process exceeds the size of the storage space having the second set threshold value matching the type of the target file, that is, to determine whether the size of the storage space actually occupied by the modified target file exceeds the upper limit of the storage space that can be divided therefrom from the target storage area (that is, the second set threshold value). Further, if the target file is not exceeded, the target file can be modified in the target storage area, if the target file is exceeded, the second set threshold value can be prompted to be modified to a value larger than the size of the storage space actually occupied by the modified target file, or the occupied storage space corresponding to the type of the target file can be prompted to be cleared, so that enough storage space is reserved for storing the modified target file, or the target file is abandoned to be modified in the target storage area, and the target file is transferred to the second type storage area to be modified, and meanwhile, the target file and the created link file corresponding to the target file can be selected to be correspondingly deleted from the target storage area which is the first type storage area.

In another embodiment of the present invention, the file management request may be a file deletion request, that is, a target file needs to be deleted based on a request of a file application layer, that is, the corresponding current user operation is to delete a stored file in the first type storage area.

the target file is deleted and the link file is created.

It can be understood that when a target file does not need to be stored in a target storage area for storing a file with higher importance, that is, the importance of the target file does not need to be stored in the target storage area when the target file changes, the created link file containing the storage path information of the target file can be deleted at the same time of deleting the target file, so as to make up a storage space for continuously storing other files, and realize efficient management of the files.

Optionally, in the file management method provided in the embodiment of the present invention, the following steps may be further included:

and all files stored in the first type storage area are backed up to the cloud end, so that the reliability and the safety of file management are improved.

The file management method according to the embodiment of the present invention will be described in detail with reference to fig. 2 to 9, referring to fig. 2, in the embodiment of the invention, a mapping management layer is added between an upper application program and system service (which is called an upper layer, namely a file application layer) and a file storage area of a file management system, wherein the file storage area comprises an enhanced area (i.e. a first type storage area) and a normal area (i.e. a second type storage area), so that the operation of the upper layer on all the files stored in the file storage area needs to be performed through the mapping management layer, that is, the upper layer does not need to call a corresponding file management interface to manage the files in the file storage area, but through the mapping management layer, so that the difference between the enhanced area and the normal area can be hidden for the upper layer, as if only one normal area is used for the upper layer.

It is understood that the added mapping management layer can be used to implement at least the following two functions:

(1) controlling access to authority to upper layer

Given the limited and confidential storage space of the enhanced region, all upper layer applications and system services need strict access control to access it, and access is allowed only after permission.

For the enhanced area shown in fig. 2, since the size of the enhanced area cannot be dynamically adjusted according to the characteristics of the memory, the enhanced area needs to be pre-divided before the mobile terminal (such as a mobile phone) is shipped. The size of the enhanced area must be carefully set since one unit of enhanced area may reduce the user-usable capacity by three units. The device manufacturer can set the size of the enhanced area according to the function positioning of the mobile terminal and the oriented customer group and referring to the actual situation.

Specifically, the enhanced region may be mainly used for storing three types of files, that is, may be specifically divided into a user important file reserved region (i.e., a first sub-region), an application key file reserved region (i.e., a second sub-region), and a system file reserved region, and is respectively used for correspondingly storing a user important file (i.e., a first type of file), an application key file (i.e., a second type of file), and a system preset file, so as to perform control management respectively.

The system file reserved area for storing the system preset file can be preset when the mobile terminal leaves a factory, is controlled by a manufacturer, and is authorized to access the core operating system service by default, and other non-core services and applications cannot access the core operating system service, so that the reliability of the system preset file is ensured, and the safety of the system preset file is also ensured.

The user important file reserved area for storing the user important files can be authorized by default when the mobile terminal leaves a factory, and the user can manage personal important files, such as contract files, security files and the like, through the user important file reserved area, and specifically can manage files such as creation, sorting, cleaning, refreshing, display setting and the like. In the using process, if the size of the enhanced space (i.e. the storage space of the user's important file reserved area) is full, the system automatically pops up the box to prompt the user, and the user needs to clear the file to vacate the storage space first to continue to place the new file, as shown in fig. 3.

For the application key file reservation area for storing the application key file, when installing each application, the system automatically pops up the box to prompt the user to select whether to allow the user to use the enhanced area, as shown in fig. 4, taking the WeChat application as an example. Further, a system default value may be set for the maximum value of the storage space of the enhanced area used by each application, and a user may view the storage space occupation of each application in the system setting, and may perform configuration management separately, such as setting the maximum value of the storage space to a specific value or clearing the application content. When the storage space used by the application exceeds a set upper limit, the system may freeze the application and automatically pop up to prompt the user for a selection to let the application subsequently use the normal region, or modify the application size limit, or clear the space before continuing to use, as shown in fig. 5.

(2) Mapping management of files stored in a file storage area

By map management of the file stored in the enhanced area, the details of the enhanced area operation are hidden from the upper layer, and when the file of the enhanced area is operated according to the request of the upper layer, it is seen as if the file in the normal area is operated.

Specifically, mapping management of the files in the enhanced region can be realized in a manner that a link file can be correspondingly created in the normal region for each file in the enhanced region, where the link file at least includes file storage path information, so that a file having a mapping relationship with the link file can be found in the enhanced region based on the link file.

Alternatively, at least the following procedures can be used to achieve effective file management.

Referring to fig. 6, the file creation process specifically includes the following steps:

step 201: and starting a file creating process according to the file creating request of the upper layer.

Step 203: it is determined whether to create a file in the enhanced region, if yes, step 205 is performed, otherwise step 215 is performed.

Step 205: and judging whether the file has system default permission or user default permission or application pop-up inquiry permission for permission to access the enhanced area according to the type of the file to be created, if so, executing step 207, and otherwise, executing step 215.

Step 207: the access permission information is recorded to facilitate subsequent direct access to the enhanced area.

Step 209: it is determined whether the size of the storage space occupied by the file to be created is within the allowable usage range, if yes, step 211 is executed, otherwise, step 215 is executed.

The allowable usage range may vary according to file types, and the content description about the user important file and the application key file may be referred to above.

Step 211: a file is created in the enhanced area.

Step 213: and correspondingly creating a link file of the file in the common area.

Step 215: a file is created in the normal area.

As can be seen from the above, when creating a file of an enhanced region, a specific interface needs to be called to specify a specific region in the enhanced region, and access permission verification needs to be performed at the first access, and then the system records permission information and directly determines the permission information. After the file is successfully created in the enhanced area, the link file of the file needs to be correspondingly created under the directory specified by the upper layer of the normal area.

Referring to fig. 7, the file opening process specifically includes the following steps:

step 301: and starting a file opening process according to the file opening request of the upper layer.

Step 303: it is determined whether the file is stored in the enhanced area, if yes, step 305 is performed, otherwise step 309 is performed.

Step 305: and determining a link file corresponding to the file in the ordinary area to acquire a file storage path.

Step 307: and opening the file in the enhanced area according to the file storage path.

Step 309: the file is opened in the normal area.

As can be seen from the above, for the file stored in the enhanced area, the file storage path is obtained through the link file and then opened, and the file can be directly read after being opened.

Referring to fig. 8, the file modification process specifically includes the following steps:

step 401: and starting a file modification process according to the file modification request of the upper layer.

Step 403: it is determined whether the file is stored in the enhanced area, if yes, step 407 is executed, otherwise step 405 is executed.

Step 405: and finishing the file modification in the normal area.

Step 407: in the process of modifying the file, it is determined whether the storage space exceeds the allowable range size of the modified file, if yes, step 411 is executed, otherwise step 409 is executed.

Step 409: and finishing the file modification in the enhancement area.

Step 411: it is determined whether the file to be modified is an application critical file, if yes, step 415 is performed, otherwise step 413 is performed.

Step 413: and reminding to clear the storage space under the condition that the file needing to be modified is judged to be the important file of the user.

Further, if cleaning vacates sufficient storage space, step 409 may be performed, and if no cleaning is selected, step 405 may be performed.

Step 415: and selecting a processing mode according to the bullet frame to finish the file modification.

Specifically, the size of the storage space occupied by the application preset file may be selected to be modified, if the corresponding storage space is increased by the modification, step 409 may be executed, and if the corresponding storage space is not modified, step 405 may be executed; it is also possible to choose to clean up the occupied storage space, if cleaning up frees up sufficient storage space, step 409 can be performed, if choosing not, step 405 can be performed. Further, in the case of selecting to perform step 405, the file may be copied from the enhanced area to the normal area, and then the file may be deleted in the enhanced area, and the link file corresponding to the file may be deleted in the normal area, and then the file modification may be completed in the normal area.

From the above, in the file modification process, the storage space of the enhanced area used by the file may exceed the allowable size, and further processing is required to meet the modification requirements of different types of files.

Referring to fig. 9, the file deletion process specifically includes the following steps:

step 501: and starting a file deleting process according to the file deleting request of the upper layer.

Step 503: it is determined whether the file is stored in the enhanced area, if yes, step 505 is executed, otherwise step 509 is executed.

Step 505: and deleting the file in the enhanced area.

Step 507: and deleting the link file of the file in the normal area.

Step 509: the file is deleted in the normal area.

As can be seen from the above, deleting the file in the enhanced area requires deleting the link file corresponding to the normal data area.

In summary, by using the enhanced features of the memory, different files of users, applications and systems are managed differently according to different importance, so as to improve the reliability of important files and the stability of applications and system services.

Referring to fig. 10, an embodiment of the present invention further provides a mobile terminal, where the mobile terminal 600 may specifically include:

a receiving module 601, configured to receive a file management request generated by a file application layer based on a current user operation;

a determining module 603, configured to determine a target storage area corresponding to a target file requested to be managed by the file management request;

the management module 605 is configured to, if the target storage area is the first type storage area, perform file management according to the file management request under the condition that it is verified that the file management request has an access right to the target storage area, where an importance degree value of the target file is higher than a preset value.

Preferably, in the mobile terminal 600 according to the embodiment of the present invention, the management module 605 may be further configured to:

Preferably, in the mobile terminal 600 provided in the embodiment of the present invention, the file management request is a file creation request, where the management module 605 specifically includes:

and the creating sub-module is used for creating the target file according to the type of the target file and the target storage space required by the creation of the target file, wherein the created target file has a target link file which forms a mapping relation with the target file, and the target link file comprises the storage path information of the target file.

Preferably, in the mobile terminal 600 provided in the embodiment of the present invention, the creating sub-module may be specifically configured to:

under the condition that the type of the target file is a first type, if the residual storage space of a first sub-area used for creating the target file is larger than or equal to the target storage space, creating the target file in the first sub-area, wherein the first sub-area is one of a plurality of sub-areas of the target storage area;

Preferably, in the mobile terminal 600 provided in the embodiment of the present invention, the object file is a file already stored in an object storage area, where the management module 605 may further include:

the determining submodule is used for determining the created link file corresponding to the target file;

the searching submodule is used for searching the target file according to the storage path information contained in the created link file;

and the operation submodule is used for operating the target file according to the file management request.

Preferably, in the mobile terminal 600 according to the embodiment of the present invention, when the file management request is a file modification request, the operation sub-module may be specifically configured to:

Preferably, in the mobile terminal 600 according to the embodiment of the present invention, when the file management request is a file deletion request, the operation sub-module may be specifically configured to:

the target file is deleted and the link file is created.

It can be understood that the mobile terminal 600 provided in the embodiment of the present invention can implement each process of the file management method executed by the mobile terminal 600, and the related descriptions about the file management method are all applicable to the mobile terminal 600, and are not described herein again.

Fig. 11 is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present invention, where the mobile terminal 700 includes, but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, a processor 710, a power supply 711, and the like. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 11 is not intended to be limiting of mobile terminals, and that a mobile terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the mobile terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

The processor 710 is configured to perform the following processes:

if the target storage area is the first type storage area, file management is carried out according to the file management request under the condition that the file management request has the access right to the target storage area, and the importance degree value of the target file is higher than a preset value.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 701 may be used for receiving and sending signals during a message transmission and reception process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 710; in addition, the uplink data is transmitted to the base station. In general, radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 701 may also communicate with a network and other devices through a wireless communication system.

The mobile terminal provides the user with wireless broadband internet access via the network module 702, such as helping the user send and receive e-mails, browse web pages, and access streaming media.

The audio output unit 703 may convert audio data received by the radio frequency unit 701 or the network module 702 or stored in the memory 709 into an audio signal and output as sound. Also, the audio output unit 703 may also provide audio output related to a specific function performed by the mobile terminal 700 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 703 includes a speaker, a buzzer, a receiver, and the like.

The input unit 704 is used to receive audio or video signals. The input Unit 704 may include a Graphics Processing Unit (GPU) 7041 and a microphone 7042, and the Graphics processor 7041 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 706. The image frames processed by the graphic processor 7041 may be stored in the memory 709 (or other storage medium) or transmitted via the radio unit 701 or the network module 702. The microphone 7042 may receive sounds and may be capable of processing such sounds into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 701 in case of a phone call mode.

The mobile terminal 700 also includes at least one sensor 705, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 7061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 7061 and/or a backlight when the mobile terminal 700 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of the mobile terminal (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), and vibration identification related functions (such as pedometer, tapping); the sensors 705 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.

The display unit 706 is used to display information input by the user or information provided to the user. The Display unit 706 may include a Display panel 7061, and the Display panel 7061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 707 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071, also referred to as a touch screen, may collect touch operations by a user on or near the touch panel 7071 (e.g., operations by a user on or near the touch panel 7071 using a finger, a stylus, or any other suitable object or attachment). The touch panel 7071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 710, receives a command from the processor 710, and executes the command. In addition, the touch panel 7071 can be implemented by various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 707 may include other input devices 7072 in addition to the touch panel 7071. In particular, the other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described herein again.

Further, the touch panel 7071 may be overlaid on the display panel 7061, and when the touch panel 7071 detects a touch operation on or near the touch panel 7071, the touch operation is transmitted to the processor 710 to determine the type of the touch event, and then the processor 710 provides a corresponding visual output on the display panel 7061 according to the type of the touch event. Although the touch panel 7071 and the display panel 7061 are shown in fig. 11 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 7071 and the display panel 7061 may be integrated to implement the input and output functions of the mobile terminal, which is not limited herein.

The interface unit 708 is an interface through which an external device is connected to the mobile terminal 700. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 708 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 700 or may be used to transmit data between the mobile terminal 700 and external devices.

The memory 709 may be used to store software programs as well as various data. The memory 709 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 709 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 710 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 709 and calling data stored in the memory 709, thereby integrally monitoring the mobile terminal. Processor 710 may include one or more processing units; preferably, the processor 710 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 710.

The mobile terminal 700 may also include a power supply 711 (e.g., a battery) for powering the various components, and the power supply 711 may be logically coupled to the processor 710 via a power management system that may enable managing charging, discharging, and power consumption by the power management system.

In addition, the mobile terminal 700 includes some functional modules that are not shown, and thus will not be described in detail herein.

Preferably, an embodiment of the present invention further provides a mobile terminal, including a processor 710, a memory 709, and a computer program stored in the memory 709 and capable of running on the processor 710, where the computer program, when executed by the processor 710, implements each process of the above file management method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the file management method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A method of file management, the method comprising:

receiving a file management request generated by a file application layer based on current user operation; determining a target storage area corresponding to a target file requested to be managed by the file management request;

if the target storage area is a first type storage area, file management is carried out according to the file management request under the condition that the file management request has the access authority to the target storage area, and the importance degree value of the target file is higher than a preset value;

if the target storage area is a second type storage area, file management is carried out on the target storage area according to the file management request, and the importance degree value of the file in the first type storage area is higher than that of the file in the second type storage area;

wherein the file management request is a file creation request, and the file management according to the file management request is performed under the condition that the file management request is verified to have the access right to the target storage area, and the file management method includes:

creating the target file according to the type of the target file and a target storage space required by creating the target file;

the created target file has a target link file which forms a mapping relation with the target file, the target link file comprises storage path information of the target file, the target link file is stored in the second type storage area, and the first type storage area is invisible to a user.

2. The method of claim 1, wherein creating the object file according to the type of the object file and the object storage space required to create the object comprises:

3. The method of claim 1, wherein the target file is a file already stored in the target storage area,

wherein, the file management according to the file management request under the condition of verifying that the file management request has the access right to the target storage area comprises:

determining a created link file corresponding to the target file;

searching the target file according to the storage path information contained in the created link file;

and operating the target file according to the file management request.

4. The method according to claim 3, wherein, in a case where the file management request is a file modification request, the operating the target file according to the file management request includes:

5. The method according to claim 3, wherein, in a case where the file management request is a file deletion request, the operating the target file according to the file management request includes:

and deleting the target file and the created link file.

6. A mobile terminal, comprising:

the management module is used for managing files according to the file management request under the condition that the file management request has the access authority to the target storage area is verified if the target storage area is the first type storage area, and the importance degree value of the target file is higher than a preset value;

the management module is further configured to: if the target storage area is a second type storage area, file management is carried out on the target storage area according to the file management request, and the importance degree value of the files in the first type storage area is higher than that of the files in the second type storage area;

wherein the file management request is a file creation request, and the management module specifically includes: and the creating sub-module is used for creating the target file according to the type of the target file and a target storage space required by the creation of the target file, wherein the created target file has a target link file which forms a mapping relation with the target file, the target link file comprises storage path information of the target file, the target link file is stored in the second type storage area, and the first type storage area is invisible to a user.

7. A mobile terminal, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 5.