A method, apparatus, device, and medium for managing stored files.

Abstract

This specification discloses a method, apparatus, device, and medium for managing stored files. The method includes: obtaining an application instruction for a file to be received; determining the application space for the file to be received based on the application instruction; obtaining the remaining storage space of the disk corresponding to the file to be received based on a preset program; if it is determined that the remaining storage space is less than the application space, obtaining the priority of files already stored on the corresponding disk, deleting the files based on the priority, and obtaining the corresponding application space to store the file to be received. This alleviates the problem of accidental deletion of important stored files and improves the reliability of disk storage.

Description

Technical Field

[0001] This specification relates to the field of file storage technology, and in particular to a method, apparatus, device and medium for managing stored files. Background Technology

[0002] With the rapid development of internet technology and the arrival of the big data era, the number of users is growing rapidly, and user demands are gradually increasing. Higher IT infrastructure standards and massive data storage, processing, and analysis capabilities are inevitable requirements for enterprise development. Therefore, storage, as a crucial component of IT infrastructure, is receiving increasing attention.

[0003] The flash storage space used in current embedded devices is often limited due to cost constraints or specific project requirements for particular device models, resulting in very small storage spaces in actual projects. Different business needs vary; sometimes it's necessary to display multimedia files such as images, audio, and video. In such cases, microcontrollers with limited storage space cannot store the files according to the actual business requirements, making it impossible to use the corresponding materials. Furthermore, deleting stored materials based solely on the required storage space can easily lead to the accidental deletion of important files. Summary of the Invention

[0004] To address the aforementioned technical problems, this specification provides one or more embodiments of a method, apparatus, device, and medium for managing stored files.

[0005] One or more embodiments of this specification employ the following technical solutions:

[0006] This specification provides one or more embodiments of a file storage management method, the method comprising:

[0007] Obtain the request instruction for the storage file to be received, and determine the requested space for the storage file to be received based on the request instruction;

[0008] The remaining storage space of the disk corresponding to the file to be received is obtained based on a preset program;

[0009] If it is determined that the remaining storage space is less than the requested space, then the priority of the files already stored in the corresponding disk is obtained, and the stored files are deleted based on the priority to obtain the corresponding requested space to store the files to be received.

[0010] Optionally, in one or more embodiments of this specification, before the step of obtaining the priority of the files already stored in the corresponding disk and deleting the stored files based on the priority to obtain the corresponding requested space for storing the files to be received, if it is determined that the remaining storage space is less than the requested space, the method further includes:

[0011] Obtain the space request level of the storage file to be received according to the application instruction;

[0012] Obtain the preset request level table for the corresponding storage disk;

[0013] If the space request level of the storage file to be received is determined to be the lowest level based on the preset request level table, then it is determined whether there is a cache file in the corresponding storage disk;

[0014] If it exists, the file to be received is stored in the cache space corresponding to the cache file.

[0015] Optionally, in one or more embodiments of this specification, storing the file to be received based on the cache space corresponding to the cache file specifically includes:

[0016] Obtain the total cache space corresponding to each of the aforementioned cache files;

[0017] If the total cache space is greater than the requested space for the storage file to be received, then the cache files are deleted in sequence to store the storage file to be received in the cache space.

[0018] If the total cache space is less than the requested space of the storage file to be received, then the storage file to be received is added to the preset waiting sequence.

[0019] Optionally, in one or more embodiments of this specification, the step of obtaining the priority of the files already stored on the corresponding disk if it is determined that the remaining storage space is less than the requested space, and deleting the stored files based on the priority to obtain the corresponding requested space to store the files to be received, specifically includes:

[0020] If it is determined that the remaining storage space is less than the requested space, then the priority of the stored files is determined based on the file type of each stored file in the corresponding disk and the user's historical access information;

[0021] The priority of the storage file to be received is obtained based on the application instruction;

[0022] If the priority of the file to be received is greater than the priority of the already stored file, the already stored file is deleted in sequence according to the priority, so that the file to be received is stored in the corresponding disk.

[0023] If the priority of the file to be received is lower than the priority of the already stored file, then the file to be received is added to the preset waiting sequence.

[0024] Optionally, in one or more embodiments of this specification, determining the priority of the stored files based on the file types of the corresponding stored files on the disk and the user's historical access information specifically includes:

[0025] The material type corresponding to the stored file is determined based on the file type of the stored file;

[0026] Obtain the business project corresponding to the corresponding disk, and determine the first priority of each material type based on the business project;

[0027] The likelihood of calling each of the stored files is obtained based on the user's historical call information, and a second priority of each of the stored files is determined based on the likelihood of calling.

[0028] The priority of the stored file is determined by multiplying the second priority of the stored file with the first priority of the material type of the stored file.

[0029] Optionally, in one or more embodiments of this specification, obtaining the call probability of each of the stored files based on the user's historical call information specifically includes:

[0030] Determine the preset statistical period for the corresponding disk;

[0031] Based on the user's historical call information, obtain the number of times the stored files were called within each preset statistical period, and the number of files called within each preset statistical period;

[0032] Based on the ratio of the number of calls within each preset statistical period to the number of files called within each preset statistical period, the historical call percentage sequence of the stored files is determined;

[0033] The historical call percentage sequence is predicted based on a preset whale algorithm to obtain the call percentage of each of the stored files in the current statistical period, and the call percentage is used as the call probability of each of the stored files.

[0034] Optionally, in one or more embodiments of this specification, before determining the historical call percentage sequence of the stored files based on the ratio of the number of calls within each preset statistical period to the number of files called within each preset statistical period, the method further includes:

[0035] The number of times the stored files are called in each preset statistical period is sorted according to time order to determine the last statistical period for the calls of the stored files.

[0036] Obtain the statistical cutoff time corresponding to the last statistical period and the start time of the current statistical period;

[0037] If the difference between the statistical cutoff time and the start time of the current statistical period is greater than a preset time threshold, then the priority of the stored file is determined to be the lowest level.

[0038] This specification provides one or more embodiments of a file storage management device, the device comprising:

[0039] A determining unit is used to obtain an application instruction for a storage file to be received, and to determine the application space for the storage file to be received based on the application instruction.

[0040] The acquisition unit is used to acquire the remaining storage space of the disk corresponding to the storage file to be received based on a preset program;

[0041] The deletion unit is configured to, if it is determined that the remaining storage space is less than the requested space, obtain the priority of the files already stored in the corresponding disk, delete the stored files based on the priority, and obtain the corresponding requested space to store the files to be received.

[0042] This specification provides one or more embodiments of a communication acquisition device for a programmable controller, the device comprising:

[0043] At least one processor; and,

[0044] A memory communicatively connected to the at least one processor; wherein,

[0045] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0046] Obtain the request instruction for the storage file to be received, and determine the requested space for the storage file to be received based on the request instruction;

[0047] The remaining storage space of the disk corresponding to the file to be received is obtained based on a preset program;

[0048] If it is determined that the remaining storage space is less than the requested space, then the priority of the files already stored in the corresponding disk is obtained, and the stored files are deleted based on the priority to obtain the corresponding requested space to store the files to be received.

[0049] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0050] Obtain the request instruction for the storage file to be received, and determine the requested space for the storage file to be received based on the request instruction;

[0051] The remaining storage space of the disk corresponding to the file to be received is obtained based on a preset program;

[0052] If it is determined that the remaining storage space is less than the requested space, then the priority of the files already stored in the corresponding disk is obtained, and the stored files are deleted based on the priority to obtain the corresponding requested space to store the files to be received.

[0053] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

[0054] By determining the requested space for the file to be received and the corresponding remaining space on the disk, it is determined whether the remaining storage space is less than the requested space. This allows the priority of the files already stored on the disk to be obtained, and the stored files are deleted according to the priority. The requested space is then used to store the file to be received, ensuring that important files are preserved. This avoids the problem of losing important materials due to deleting files based solely on space size and mitigates the adverse effects of accidentally deleting important materials. Attached Figure Description

[0055] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0056] Figure 1 This is a schematic flowchart of a file storage management method provided in an embodiment of this specification;

[0057] Figure 2 This is a flowchart illustrating a file storage management method in a specific application scenario provided in an embodiment of this specification.

[0058] Figure 3 This specification provides an internal structural diagram of a file storage management device according to an embodiment of the present invention.

[0059] Figure 4 This specification provides an internal structural diagram of a file management device as an embodiment of the present invention.

[0060] Figure 5 This is a schematic diagram of the internal structure of a non-volatile storage medium provided in the embodiments of this specification. Detailed Implementation

[0061] This specification provides a method, apparatus, device, and medium for storing files.

[0062] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0063] like Figure 1 As shown, one or more embodiments of this specification provide a method for managing stored files, the method comprising the following steps:

[0064] S101: Obtain the request instruction for the storage file to be received, and determine the request space for the storage file to be received based on the request instruction.

[0065] To facilitate determining the storage space required for a file to be received and allocate it accordingly, this embodiment first obtains the request instruction for the file to be received, and then determines the requested space for the file based on the request instruction. This is to subsequently determine whether there is remaining space on the corresponding disk to store the file to be received.

[0066] S102: Obtain the remaining storage space of the disk corresponding to the file to be received based on a preset program.

[0067] In order to determine whether the disk corresponding to the file to be received has sufficient free space to store the file, the embodiments of this specification obtain the remaining storage space of the disk corresponding to the file to be received according to a pre-set program.

[0068] S103: If it is determined that the remaining storage space is less than the requested space, then the priority of the files already stored in the corresponding disk is obtained, and the stored files are deleted based on the priority to obtain the corresponding requested space to store the files to be received.

[0069] Based on the requested storage space for the file to be received and the corresponding remaining disk space determined in steps S101 and S102 respectively, in order to ensure that important file materials are preserved and avoid the problem of losing important materials due to deleting files solely based on space size, in this embodiment of the specification, if it is determined that the remaining storage space is less than the requested space, then the priority of the files already stored on the corresponding disk is obtained, and the stored files are deleted according to the priority, thereby obtaining the corresponding requested space to store the file to be received, thus mitigating the problem of important materials being mistakenly deleted.

[0070] Specifically, in one or more embodiments of this specification, if it is determined that the remaining storage space is less than the requested space, the priority of the corresponding files already stored on the disk is obtained, and the stored files are deleted based on the priority to obtain the corresponding requested space to store the files to be received. This specifically includes the following steps:

[0071] If the remaining storage space is determined to be less than the requested space, the priority of the already stored files is determined based on their file types and the user's historical access information. Then, the priority of the file to be received is obtained according to the request instruction. If the priority of the file to be received is higher than that of the already stored files, the already stored files are deleted sequentially according to their priority, and the file to be received is stored on the corresponding disk. This means that when deleting stored files, deletion starts with the lowest priority file, thus preserving important files and reducing the risk of accidental deletion. Conversely, if the priority of the file to be received is lower than that of any of the already stored files, it means that the resource request priority for this file is the lowest. In this case, the file to be received is added to a pre-set waiting sequence, waiting for available space on the corresponding disk before being stored. It should be noted that, in one or more embodiments of this specification, determining the priority of stored files based on the file types of each stored file in the corresponding disk and the user's historical access information specifically includes the following process: First, determine the material type corresponding to the stored file based on its file type. For example, determine that the material type corresponding to the stored file is image, audio, video, or multimedia. Then, obtain the business project corresponding to the disk, and determine the first priority of each material type based on the business project. Then, obtain the access probability of each stored file based on the user's historical access information, and determine the second priority of each stored file based on the access probability. Finally, determine the priority of the stored file based on the product of the second priority of the stored file and the first priority of the material type of the stored file.

[0072] Furthermore, in one or more embodiments of this specification, obtaining the likelihood of calling each stored file based on the user's historical call information specifically includes the following steps:

[0073] First, the preset statistical period for the corresponding disk is determined. Then, based on the user's historical call information, the number of times the stored files were called within each preset statistical period, as well as the number of files called within each preset statistical period, are obtained. Then, based on the ratio of the number of calls to the number of files called within each preset statistical period, the historical call percentage sequence of the stored files is determined. For example, if the number of calls to stored file A within each preset statistical period is a, b, c, d, and the total number of files called within each preset statistical period is X, Y, Z, L, then the historical call percentage sequence of stored file A is "a / X, b / Y, c / Z, d / L". The historical call percentage sequence is then predicted using a pre-set whale algorithm to obtain the call percentage of each stored file within the current statistical period, and this call percentage is used as the probability of calling each stored file.

[0074] Furthermore, to save computational resources, in one or more embodiments of this specification, before determining the historical call percentage sequence of stored files based on the ratio of the number of calls within each preset statistical period to the number of files called within each preset statistical period, the method further includes the following process:

[0075] First, the number of times stored files are called within each preset statistical period is sorted according to time sequence to determine the last statistical period for each stored file. Then, the statistical cutoff time corresponding to the last statistical period and the start time of the current statistical period are obtained. If it can be determined that the difference between the statistical cutoff time and the start time of the current statistical period is greater than a preset time threshold, then the priority of the stored file is determined to be the lowest level. It should be noted that to ensure the receipt of important files, sufficient space must be ensured. Therefore, when resources are limited, space allocation will be performed. Different resource allocation levels can be configured with different allocation levels, and different allocation levels have different operation permissions for different files. The lowest allocation permission only deletes some lowest-level file materials.

[0076] Furthermore, to avoid the impact on business resources caused by deleting already stored files on the disk to obtain remaining space when the priority of the file to be received is too low, in one or more embodiments of this specification, if it is determined that the remaining storage space is less than the requested space, the method further includes the following process before obtaining the priority of the corresponding already stored files on the disk to delete the already stored files based on the priority and before obtaining the corresponding requested space to store the file to be received:

[0077] Based on the request instruction for the storage file to be received, the space request level of the storage file to be received is obtained. Then, the preset request level table of the corresponding storage disk is obtained. If, after comparison based on the preset request level table, it is determined that the space request level of the storage file to be received is the lowest level, then it is determined whether a cache file exists in the corresponding storage disk. If it exists, then the storage file to be received is stored according to the cache space corresponding to the cache file. It should be noted that, in one or more embodiments of this specification, storing the storage file to be received based on the cache space corresponding to the cache file specifically includes the following steps:

[0078] First, obtain the total cache space corresponding to each cached file. If the total cache space is greater than the requested space for the file to be received, it means that the file to be received can be stored on disk. Therefore, the corresponding cached files on disk are deleted one by one, thus storing the file to be received in the cache space. If the total cache space is less than the requested space for the file to be received, the file to be received is added to a pre-set waiting sequence to wait for the availability of remaining space before being stored.

[0079] like Figure 2 The diagram shows a file storage management device for a specific application scenario provided in one or more embodiments of this specification. Figure 2 As can be seen, in a certain application scenario, when receiving and storing a file (i.e., media), the system first checks the remaining disk space to determine if it exceeds the requested space. If so, the request is terminated, and the file to be received is stored on the disk. If the remaining disk space is less than the requested space, media files with priority 0 are deleted sequentially, followed by media files with priority 1, to determine if the remaining disk space after deletion exceeds the requested space and whether the file to be received can be successfully stored. If the required priority of the file to be received is determined to be the lowest, higher-priority media files cannot be deleted, and the request for storage space for the file to be received fails. Then, it checks if the required priority of the file to be received is the highest. If not, media files with priority 3 are deleted, and the remaining disk space after deletion exceeds the requested space and whether the file to be received can be successfully stored.

[0080] like Figure 3 As shown, this specification provides a schematic diagram of the internal structure of a file storage management device in one or more embodiments. Figure 3 It is known that a file storage management device includes:

[0081] The determining unit 301 is used to obtain the application instruction of the storage file to be received, and determine the application space of the storage file to be received based on the application instruction;

[0082] The acquisition unit 302 is used to acquire the remaining storage space of the disk corresponding to the storage file to be received based on a preset program;

[0083] The deletion unit 303 is used to, if it is determined that the remaining storage space is less than the requested space, obtain the priority of the files already stored in the corresponding disk, delete the files already stored based on the priority, and obtain the corresponding requested space to store the files to be received.

[0084] like Figure 4 As shown, this specification provides a schematic diagram of the internal structure of a file storage management device in one or more embodiments. Figure 4 It can be seen that a file storage management device includes:

[0085] At least one processor 401; and,

[0086] The memory 402 is communicatively connected to the at least one processor 401; wherein,

[0087] The memory 402 stores instructions that can be executed by the at least one processor 401, the instructions being executed by the at least one processor 401 to enable the at least one processor 401 to:

[0088] Obtain the request instruction for the storage file to be received, and determine the requested space for the storage file to be received based on the request instruction;

[0089] The remaining storage space of the disk corresponding to the file to be received is obtained based on a preset program;

[0090] If it is determined that the remaining storage space is less than the requested space, then the priority of the files already stored in the corresponding disk is obtained, and the stored files are deleted based on the priority to obtain the corresponding requested space to store the files to be received.

[0091] like Figure 5 As shown, this specification provides a schematic diagram of the internal structure of a non-volatile storage medium according to one or more embodiments. Figure 5 It is known that a non-volatile storage medium stores computer-executable instructions 501, which are capable of:

[0092] Obtain the request instruction for the storage file to be received, and determine the requested space for the storage file to be received based on the request instruction;

[0093] The remaining storage space of the disk corresponding to the file to be received is obtained based on a preset program;

[0094] If it is determined that the remaining storage space is less than the requested space, then the priority of the files already stored in the corresponding disk is obtained, and the stored files are deleted based on the priority to obtain the corresponding requested space to store the files to be received.

[0095] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0096] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0097] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A management method of a storage file, characterized by, The method comprises: obtaining an application instruction of a to-be-received storage file, determining an application space of the to-be-received storage file based on the application instruction; obtaining a remaining storage space of a corresponding disk of the to-be-received storage file based on a preset procedure; if it is determined that the remaining storage space is less than the application space, obtaining a priority of a stored file in the corresponding disk, deleting the stored file based on the priority, and obtaining a corresponding application space to store the to-be-received storage file; wherein, before the step of if it is determined that the remaining storage space is less than the application space, obtaining a priority of a stored file in the corresponding disk, deleting the stored file based on the priority, and obtaining a corresponding application space to store the to-be-received storage file, the method further comprises: obtaining a space application level of the to-be-received storage file according to the application instruction; obtaining a preset application level table of the corresponding storage disk; if it is determined that the space application level of the to-be-received storage file is the lowest level based on the preset application level table, determining whether there is a cache file in the corresponding storage disk; if there is, storing the to-be-received storage file based on a cache space corresponding to the cache file.

2. The management method of a storage file according to claim 1, wherein The step of storing the to-be-received storage file based on the cache space corresponding to the cache file comprises: obtaining a total cache space corresponding to each cache file; if the total cache space is greater than the application space of the to-be-received storage file, deleting the cache files in turn to store the to-be-received storage file in the cache space; if the total cache space is less than the application space of the to-be-received storage file, adding the to-be-received storage file to a preset waiting sequence.

3. The management method of a storage file according to claim 1, wherein The step of if it is determined that the remaining storage space is less than the application space, obtaining a priority of a stored file in the corresponding disk, deleting the stored file based on the priority, and obtaining a corresponding application space to store the to-be-received storage file comprises: if it is determined that the remaining storage space is less than the application space, determining the priority of the stored file based on a file type of each stored file in the corresponding disk and historical calling information of a user; obtaining a priority of the to-be-received storage file based on the application instruction; if the priority of the to-be-received storage file is greater than the priority of the stored file, deleting the stored file in turn according to the priority to store the to-be-received storage file in the corresponding disk; if the priority of the to-be-received storage file is less than the priority of the stored file, adding the to-be-received storage file to a preset waiting sequence.

4. The management method of a storage file according to claim 3, wherein The step of determining the priority of the stored file based on a file type of each stored file in the corresponding disk and historical calling information of a user comprises: determining a material type corresponding to the stored file according to the file type of the stored file; obtaining a business item corresponding to the corresponding disk to determine a first priority of each material type based on the business item; The calling possibility of each of the stored files is obtained according to historical calling information of the user, so as to determine a second priority of each of the stored files based on the calling possibility; The priority of the stored file is determined based on the product of the second priority of the stored file and the first priority of the material type of the stored file.

5. The management method of a storage file according to claim 4, wherein The calling possibility of each of the stored files is obtained according to historical calling information of the user, and specifically includes: A preset statistical period of the corresponding disk is determined; The number of calls of the stored file in each preset statistical period is obtained based on the historical calling information of the user, and the number of called files in each of the preset statistical periods is obtained; A historical calling proportion sequence of the stored file is determined based on the ratio of the number of calls in each preset statistical period to the number of called files in each of the preset statistical periods; The historical calling proportion sequence is predicted according to a preset whale algorithm to obtain the calling proportion of each of the stored files in a current statistical period, and the calling proportion is taken as the calling possibility of each of the stored files.

6. The management method of a storage file according to claim 5, wherein Before the historical calling proportion sequence of the stored file is determined based on the ratio of the number of calls in each preset statistical period to the number of called files in each of the preset statistical periods, the method further includes: The number of calls of the stored file in each preset statistical period is sorted based on time sequence to determine the last calling statistical period of the stored file; The statistical end time corresponding to the last calling statistical period and the start time of the current statistical period are obtained; If it is determined that the difference between the statistical end time and the start time of the current statistical period is greater than a preset time threshold, the priority of the stored file is determined to be the lowest level.

7. A management apparatus of a storage file, characterized by, The device includes: A determination unit is configured to obtain an application instruction of a to-be-received stored file, and determine an application space of the to-be-received stored file based on the application instruction; A obtaining unit is configured to obtain a remaining storage space of a disk corresponding to the to-be-received stored file based on a preset program; A deletion unit is configured to, if it is determined that the remaining storage space is less than the application space, obtain a priority of a stored file in the corresponding disk, delete the stored file based on the priority, and obtain a corresponding application space to store the to-be-received stored file. If it is determined that the remaining storage space is less than the application space, the priority of the stored file in the corresponding disk is obtained, the stored file is deleted based on the priority, and the corresponding application space is obtained to store the to-be-received stored file, the method further includes: The space application level of the to-be-received stored file is obtained according to the application instruction; A preset application level table of the corresponding storage disk is obtained; If it is determined that the space application level of the to-be-received stored file is the lowest level based on the preset application level table, it is determined whether there is a cache file in the corresponding storage disk; If there is, the to-be-received stored file is stored based on the cache space corresponding to the cache file.

8. A management apparatus of a storage file, characterized by, The device includes: at least one processor; and A memory in communication connection with the at least one processor; wherein The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: Obtain an application instruction of a to-be-received storage file, determine an application space of the to-be-received storage file based on the application instruction; Obtain the remaining storage space of the corresponding disk of the to-be-received storage file based on a preset procedure; If it is determined that the remaining storage space is less than the application space, obtain the priority of the stored file in the corresponding disk, delete the stored file based on the priority, and obtain the corresponding application space to store the to-be-received storage file; Wherein, before the step of if it is determined that the remaining storage space is less than the application space, obtaining the priority of the stored file in the corresponding disk, deleting the stored file based on the priority, and obtaining the corresponding application space to store the to-be-received storage file, the method further comprises: Obtaining the space application level of the to-be-received storage file according to the application instruction; Obtaining the preset application level table of the corresponding storage disk; If it is determined that the space application level of the to-be-received storage file is the lowest level based on the preset application level table, determining whether there is a cache file in the corresponding storage disk; If there is, storing the to-be-received storage file based on the cache space corresponding to the cache file.

9. A non-transitory storage medium storing computer-executable instructions, the computer-executable instructions comprising: The computer executable instructions can: Obtain an application instruction of a to-be-received storage file, determine an application space of the to-be-received storage file based on the application instruction; Obtain the remaining storage space of the corresponding disk of the to-be-received storage file based on a preset procedure; If it is determined that the remaining storage space is less than the application space, obtain the priority of the stored file in the corresponding disk, delete the stored file based on the priority, and obtain the corresponding application space to store the to-be-received storage file; Wherein, before the step of if it is determined that the remaining storage space is less than the application space, obtaining the priority of the stored file in the corresponding disk, deleting the stored file based on the priority, and obtaining the corresponding application space to store the to-be-received storage file, the method further comprises: Obtaining the space application level of the to-be-received storage file according to the application instruction; Obtaining the preset application level table of the corresponding storage disk; If it is determined that the space application level of the to-be-received storage file is the lowest level based on the preset application level table, determining whether there is a cache file in the corresponding storage disk; If there is, storing the to-be-received storage file based on the cache space corresponding to the cache file.

Images