WO2015117426A1

WO2015117426A1 - File management method and device

Info

Publication number: WO2015117426A1
Application number: PCT/CN2014/090068
Authority: WO
Inventors: 黄勤波; 钟声; 王巍
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-07-24
Filing date: 2014-10-31
Publication date: 2015-08-13
Also published as: CN105302832A

Abstract

Provided are a file management method and device. The method comprises: acquiring indexes of application identifiers corresponding to a designated application on a terminal from a pre-set index database, wherein there is an association relationship between the indexes and file information generated when the designated application is installed or operated, and the indexes are in one-to-one correspondence with the application identifiers; and according to the indexes and the association relationship, managing the file information. By means of the technical solution provided in the present invention, the technical problem in the related art that the workload for manual maintenance is relatively large when files related to applications are managed is solved, thereby saving manual workload for file management, increasing the disk usage rate and improving the user experience.

Description

File management method and device

Technical field

The present invention relates to the field of communications, and in particular, to a file management method and apparatus.

Background technique

With the increasing popularity of smart phones and related smart terminals, smart terminals (mobile phones, etc.) have become an indispensable communication, entertainment and even work tool in people's daily lives. The invention takes a mobile phone of a smart terminal as an example. Mobile phones have not only greatly improved people's work efficiency, but also changed people's lifestyles.

With the rapid development of smart phones, mobile phone services or communication services are becoming more and more abundant. The use of mobile applications such as e-shopping applications (such as Taobao, Jingdong Mall), social applications (such as WeChat, Weibo), various music video software, and various mobile games has brought great convenience to the majority of smartphone users. It also brings a lot of fun to the user and brings a lot of troubles.

At present, the application of smart phones has a very big drawback, that is, the application installation package is getting bigger and bigger, an Android installation package (AndroidPackage, abbreviated as apk) is tens of hundreds of MB, and many files generated by the application after not being used. More and more, and these files (especially those placed on sd cards) cannot be deleted automatically. Nowadays, there are many kinds of applications, more and more new applications, and the frequency of replacing applications is getting faster and faster. As time goes on, the terminal system space and sd card space will be quickly consumed, and users do not know which files are useful. Which files are useless and I dare not delete files at will. Experience shows that 80% of the data on the sd card is the application data, especially audio, video or photos, user documents, etc. It is possible that the application of the data has already been uninstalled and not used. Users can't use these files, but they still occupy the user's valuable disk space for a long time. Because these files lack useful information and unified portal management, users have no way of dealing with these files that occupy their own smart terminals. These are a problem that plagues smartphone users.

Although there are some cleaning and acceleration third-party software on the market, most of these softwares are analyzed by artificially collecting a large number of application data file directory information to form a corresponding index for file management. The shortcomings here are obviously that the labor maintenance is very large, and it is obviously not sustainable in the context of such an explosive growth of information.

There is no effective solution to the above problems in the related art.

Summary of the invention

For the related art, the management of the file related to the application has technical problems such as a large manual maintenance workload, and the present invention provides a file management method and device to solve at least the above technical problem.

According to an embodiment of the present invention, a file management method is provided, including: obtaining an index of an application identifier corresponding to a specified application on a terminal from a preset index database, wherein the index and the specified application are installed or running The generated file information has an association relationship, and the index is in one-to-one correspondence with the application identifier; the file information is managed according to the index and the association relationship.

Preferably, before the index of the application identifier corresponding to the current application is obtained from the preset index database, the method includes: allocating the index to the application identifier; and establishing file information and the index generated by the application during installation or operation. Association relationship; storing the association relationship into the preset index database.

After the association relationship is stored in the preset index database, the method further includes: uploading the preset index database to the network side.

Preferably, the method further includes: storing, in the terminal, the file information in the preset index library of the network side that the frequency of use is greater than a specified threshold.

Preferably, the file information is managed according to the index and the association relationship: a query operation, a deletion operation, and a backup transfer.

Preferably, deleting the file information according to the index and the association relationship, including one of: prompting a user in a list form for specifying file information in all the file information triggered by a specified event Select whether to delete, and delete all the information in the file information except the specified file information; delete all the file information under the trigger of the specified event.

Preferably, the list includes description information of at least one of the following file information: a name of the specified file information, a frequency of use of the specified file information, an access time of the specified file information, the specified file The effect of the information and the result of the deletion of the specified file information.

Preferably, the specified event includes one of: detecting that the application is uninstalled, detecting that a system space of the terminal is less than a preset threshold.

Preferably, the application identifier comprises: an application package name.

Preferably, the file information includes at least one of: an application package name of the application, a read/write frequency of the file information, a read/write time of the file information, a file directory path of the file information, and the The role of data message information.

According to another embodiment of the present invention, a file management apparatus is provided, including: an obtaining module, configured to acquire an index of an application identifier corresponding to a specified application on a terminal from a preset index database, wherein the index and the designation There is an association relationship between the file information generated by the application during installation or operation, and the index is in one-to-one correspondence with the application identifier; the management module is configured to manage the file information according to the index and the association relationship. .

According to the present invention, the technical means for establishing an index of the related file information of the specified application and managing the related file information of the specified application according to the index solves the related art, and the manual management of the file related to the application is manually maintained. Technical problems such as a large workload, which saves the manual workload of file management, improves disk usage, and improves user experience.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flow chart of a file management method according to an embodiment of the present invention;

2 is a block diagram showing the structure of a file management apparatus according to an embodiment of the present invention;

3 is a schematic diagram showing the principle of file management implementation according to a preferred embodiment of the present invention;

4 is a schematic diagram of a file index establishment process according to a preferred embodiment of the present invention;

FIG. 5 is a schematic diagram of a file cleaning process according to a preferred embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

FIG. 1 is a flow chart of a file management method according to an embodiment of the present invention. As shown in Figure 1, the method includes the following processing steps:

Step S102: Obtain an index of the application identifier corresponding to the specified application on the terminal from the preset index database, where the index is associated with the file information generated by the specified application during installation or operation, and the index and the application identifier are corresponding;

Step S104, managing the file information according to the index and the association relationship.

Through the foregoing various processing steps, since the related file can be managed according to the index of the unique identifier corresponding to the application, the related file of the application can be automatically managed, and since the application file can be managed according to the index, the saving is achieved. The amount of manual maintenance work.

In a preferred embodiment, in order to implement index-based management, before obtaining an index of the application identifier corresponding to the current application from the preset index database, the following processing may be performed:

Allocating the foregoing index to the application identifier; establishing an association relationship between the file information generated by the application in the installation or running and the index; storing the association relationship in the preset index database. Here, it can be understood that the index associated with the above file information is stored in the preset index database, but is not limited thereto.

In order to better manage the related files of the application, after the foregoing association relationship is stored in the preset index database, the preset index database may also be uploaded to the network side, so that the sharing of the index database may be implemented.

In a preferred embodiment of the present embodiment, in order to improve the efficiency of the disk management, the file information in the preset index library on the network side that is greater than the specified threshold may be stored in the terminal.

In a preferred embodiment, the foregoing file information may be managed according to the foregoing index and the foregoing association relationship: a query operation, a deletion operation, and a backup transfer.

The deleting operation of the file information according to the foregoing index and the foregoing association relationship may be expressed as one of the following processing procedures, but is not limited thereto:

(1) under the trigger of the specified event, prompt the user to select whether to delete the specified file information in all the above file information, and delete all the information except the specified file information in the above file information; The description information of at least one of the following file information includes: a name of the specified file information, a frequency of use of the specified file information, an access time of the specified file information, a role of the specified file information, and a deletion of the specified file information. The result. (2) Delete all the above file information under the trigger of the specified event.

The specified event may include, but is not limited to, one of the following: detecting that the application is uninstalled, and detecting that the system space of the terminal is less than a preset threshold.

Preferably, the foregoing application identifier includes but is not limited to: an application package name.

In a preferred implementation, the file information includes at least one of the following: an application package name of the application, a read/write frequency of the file information, a read/write time of the file information, a file directory path of the file information, and the foregoing data file. The role of information.

The embodiment of the present invention further provides a file management apparatus, which is used to implement the foregoing method. As shown in FIG. 2, the method includes:

The obtaining module 20 is configured to obtain, from the preset index database, an index of the application identifier corresponding to the specified application on the terminal, where the index is associated with the file information generated by the specified application during installation or operation, and the index is as described above. Application identifiers are one-to-one correspondence;

The management module 22 is connected to the obtaining module 20 and configured to manage the file information according to the index and the association relationship.

It should be noted that each of the foregoing modules may be implemented by using software or hardware. The latter may be implemented by the following methods, but is not limited thereto: the obtaining module 20 is located in the first processor, and the management module 22 is located in the first In the second processor, the acquisition module 20 and the management module 22 are located in the same processor.

In order to better understand the above embodiments, the following detailed description will be given in conjunction with the preferred embodiments.

In view of the above drawbacks, the embodiment provides a method for automatically establishing a corresponding file index when creating a file in a mobile phone application, and updating corresponding index data when reading and writing these files. The following takes the file deletion as an example.

As shown in Figure 3:

The mobile phone application is a function module that is preset by the mobile phone or installed by the user through various channels and can be operated by the user, and generates various user or application data in the mobile phone system space or the sd card space through various forms.

The file reading and writing module is a platform interface used by the mobile phone platform to read/write files/directories in the disk space of the mobile phone.

The file index database is used to record the file index of the system space or the sd card disk space, including but not limited to the following information, the created application package name, the file detailed path, the specific data item name, the data usage frequency, and the latest access time. , the role of the data item, and the possible consequences of the data item being cleaned up.

The Cloud File Index Database is a larger and more complete database that integrates more end file data indexes for further document management.

Application files apply application data and user data generated during runtime;

System data is a data file generated in the system space, which may cause the application or system to run abnormally after being cleaned up;

User data refers to non-essential data or temporary data stored in an sd card, etc., and will only cause the application to reload or re-update the input after cleaning;

Based on the above principles, the embodiment provides a method for automatically establishing a file index for user data management. include:

The index database is preset to the terminal, that is, the index database that has been established before is preset in the mobile phone version.

The index database is built to establish a unique index for each application package name.

By extending the file read/write interface of the platform, the file name, the read/write frequency, the last write time, the file directory path, the application information, and the purpose of the file are updated to the index database when the file is read or written;

Further, the database can be synchronized to the cloud, and after more users share the data, the residual data of the sd card can be better cleaned up.

Further, the disk file monitoring mode can be adopted. When the disk file has read and write operations, the disk file is passively received and read and written information, and the file index database is updated to reduce the amount of CPU calculation or time cost caused by the scanning.

Further, when the terminal system version is upgraded, the more commonly used application data in the cloud database can be preset in the terminal, thereby improving the disk management efficiency, and not greatly increasing the size of the database and occupying too much disk space.

Further, if the user requests deeper cleanup, the cloud query can be performed to obtain the most valuable information with less traffic.

Further, after the application is uninstalled, the user is notified in time to clean up the corresponding file; or all the recommended cleanup items may be listed according to the database information when the user performs the cleanup scan.

Further, the scanned recommended cleaning item can list the detailed path of the item to be cleaned, the specific data item name of the application, the frequency of data usage, the last access time, the role of the data item, and the data item is cleaned up. Possible results. This information can effectively give users suggestions for managing files. Of course, it is also possible to extend some other field information that may be obtained.

Further, by using the data, when the remaining amount of the system space is insufficient, the user-set strategy is automatically adopted for data cleaning or backup transfer.

In this embodiment, the mobile phone platform needs to be cleaned mainly with system space, mainly the built-in storage space of the mobile phone, and the storage space of the sd card (including built-in and external), and the built-in storage space is mainly stored by the system component. Application data, which needs to be subdivided, is generally related to the application function; sd card storage space is generally the data downloaded or saved by the user through the application, and the amount of data may be relatively large.

As shown in Figure 4, a method of creating a file index (index database) is shown:

Step S402, the mobile phone version preset index database: pre-scans the system space and the sd card, and imports all /data partitions, that is, system space and sd card (inside and outside) directories, into the database, if it is a new version and an empty sd Card, this index database will not have a new directory.

However, the index database has a preset index, and the source of the preset index is the following steps, which are implemented in the cloud and then preset to the mobile phone version.

Step S404, installing a third-party application: entering a mobile phone application, such as WeChat, and performing certain operations through the WeChat application;

General applications generate some files during the operation, such as WeChat will have image cache, monitor log, local log, web cache, game download cache, game center icon, address cache, star user icon, other cache and so on.

In step S406, the package name is obtained by parsing the configuration item of the application: the package name of the application is obtained through the platform interface, and the package name of the WeChat in this embodiment is: com.tencent.mm;

Such as:

Step S408, creating a unique database index for the package name: querying the index of the package name in the index database, and if not, creating the application information, including a directory, etc.;

Of course, the specific package name, directory name, etc. are stored in the index database, MD5 encryption is required to prevent the indexed database from being maliciously used.

Step S410, generating an apk file /data/app: when the application is installed, the platform generates an application directory such as /data/app;

When the system caches the directory file generated by the Android platform, it needs to pass the application package name, so that it can clearly know which application created the file, but it still needs to pass the function of the file and the cleaning result through the translation interface of the platform transformation.

Step S412, generating a user data directory /data/data/com.zte.xxx: synchronously generating an application system data directory such as /data/data/com.tencent.mm and an sd card file such as /storage/tencent/micromsg;

Since the file on the Sd card does not have the path of the superior package name, the platform needs to be modified to write the file interface, and the file name and file function are added when the file is created, and the consequences after the cleaning are obtained.

Step S414, the user uses: the user inputs some personal data by using WeChat, and the WeChat application synchronizes the corresponding WeChat server data, such as a chat record or a WeChat address book, through the personal information;

These user data are generally in the three-level directory, so there is no need to pass more information through the platform to write the file interface, only need to monitor the three-level directory of WeChat through the directory monitoring tool such as JNotify method, and update other index fields, such as Last access time, frequency of access, etc. No need to update the app information. On the one hand, avoiding too deep directories leads to an oversized index database and avoids frequent system access performance caused by frequent access to the index database.

Step S416: The file generated by the user in the setting item of the application: the application data is generated by the file reading and writing module of the terminal platform, and the data generated by the WeChat in this embodiment has a photo taken by WeChat, a crash log generated by WeChat, and a WeChat Monitoring logs, WeChat game download cache, local logs, chat files, subscription cache, address book backup, etc.

Step S418: Update the index database after writing the file/directory: synchronously update the index database when these files are generated, and update the following fields but are not limited to these fields: the created application package name, the file detailed path, the specific data item name, and the data usage frequency. The last access time, the role of the data item, and the possible consequences of the data item being cleaned up;

Step S420: Synchronize to the cloud database when appropriate: synchronously update with the cloud index database if necessary;

The index database is updated and ends.

At some point, such as system space or when users need to clean up the sd card or when users want to find some files through the index database, they can make full use of the index database. Figure 3 is file management/cleanup according to the application name created by the file. As shown in FIG. 5, the file cleaning process provided in this embodiment includes the following steps:

Step S502, the background task scans all system space and sd card files when the index database is used for the first time;

Step S504, obtaining an application package name created by the file/directory in the index database;

Step S506, scanning all pre-installed software and third-party software of the mobile phone;

Step S508, obtaining a package name of all software;

Step S510, judging whether the created application of the file exists by comparing the two lists;

In step S512, a file management suggestion is given, and the file/directory that the creator does not already exist is cleared by default. Users can view the details and decide whether to clean up;

Step S514, according to the file size, read and write frequency sorting, the user can clearly see which files/directories are not used for a long time or which ones occupy too much space;

Step S516, the user determines to clear;

Step S518, the user independently selects a list of file directories to be cleaned;

In step S520, all the files that confirm the cleaning are deleted.

The above technical solution provided by the embodiment can enable the mobile phone user to fully index the database for various operations and improve the user experience. Of course, data operations can also be performed in other similar manners, and the present invention will not be described one by one.

In summary, the embodiments of the present invention achieve the following beneficial effects:

It can effectively prevent historical data from occupying too much disk space and affect the user experience; it is convenient to clean up files by package name. In particular, the application corresponding to the package name generates a large number of files through network or user operations. After the user uninstalls the application without using the application, the residual files can be quickly located for cleaning; different from the prior art, The index database of the embodiment of the present invention generates application information, file purpose, cleanup effect, and directory information at the beginning of creation. These index data can be shared by multiple terminals. It is convenient to clean up files by the frequency of use of the files. Mobile phone users can use the index database to clean application files, making disk usage more efficient and greatly improving the user experience.

In another embodiment, software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments.

In another embodiment, a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or separate them into individual integrated circuit modules, or Multiple of these modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

According to the foregoing technical solution provided by the embodiment of the present invention, a technical means for establishing an index of related file information of a specified application and managing related file information of the specified application according to the index is used to solve the related technology and related to the application. The management of the file has technical problems such as large manual maintenance workload, thereby saving the manual workload of file management, improving the disk usage rate and improving the user experience.

Claims

A file management method, including:

An index of the application identifier corresponding to the specified application on the terminal is obtained from the preset index database, where the index is associated with the file information generated by the specified application during installation or operation, and the index and the application identifier are corresponding;

The file information is managed according to the index and the association relationship.
The method according to claim 1, wherein before the index of the application identifier corresponding to the current application is obtained from the preset index database, the method includes:

Allocating the index to the application identifier;

Establishing an association relationship between file information generated by the application during installation or operation and the index;

The association relationship is stored in the preset index database.
The method of claim 2, after storing the association relationship in the preset index database, further comprising:

Upload the preset index database to the network side.
The method of claim 3, wherein the method further comprises:

And storing, in the terminal, the file information in the preset index library on the network side that the frequency of use is greater than a specified threshold.
The method of claim 1, wherein the file information is managed according to the index and the association relationship:

Query operation, delete operation, backup transfer.
The method according to claim 5, wherein the deleting the file information according to the index and the association relationship comprises one of the following:

In the triggering of the specified event, the specified file information in all the file information is prompted in a list to prompt the user to select whether to delete, and delete all the information in the file information except the specified file information;

Delete all the file information triggered by the specified event.
The method according to claim 6, wherein the list includes description information of at least one of the following file information: a name of the specified file information, a frequency of use of the specified file information, and the specified file information. The access time, the role of the specified file information, and the result of the deletion of the specified file information.
The method of claim 6 wherein said specified event comprises one of:

It is detected that the application is uninstalled, and the system space of the terminal is detected to be less than a preset threshold.
The method of any of claims 1 to 8, wherein the application identification comprises: an application package name.
The method according to any one of claims 1 to 8, wherein the file information comprises at least one of the following:

The application package name of the application, the read/write frequency of the file information, the read/write time of the file information, the file directory path of the file information, and the role of the data message information.
A file management device comprising:

The obtaining module is configured to obtain an index of the application identifier corresponding to the specified application on the terminal from the preset index database, where the index is associated with the file information generated by the specified application during installation or operation, and the index is associated with The application identifiers are one-to-one correspondence;

And a management module, configured to manage the file information according to the index and the association relationship.