CN111339031A

CN111339031A - Task processing method and device, electronic equipment and computer readable storage medium

Info

Publication number: CN111339031A
Application number: CN202010117323.4A
Authority: CN
Inventors: 不公告发明人
Original assignee: Guangzhou Lakala Information Technology Co ltd
Current assignee: Guangzhou Lakala Information Technology Co ltd
Priority date: 2020-02-25
Filing date: 2020-02-25
Publication date: 2020-06-26

Abstract

The embodiment of the disclosure discloses a task processing method, a task processing device, an electronic device and a computer readable storage medium, wherein the method comprises the following steps: the method comprises the steps that a task is obtained by accessing a first file synchronously downloaded from a cloud to the local; executing the task to obtain a second file; and storing the second file to the local and uploading the second file to the cloud.

Description

Task processing method and device, electronic equipment and computer readable storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a task processing method and apparatus, an electronic device, and a computer-readable storage medium.

Background

In the field of computer technology, tasks (tasks) refer to units of work that can be performed by a computer. Tasks can be executed through specific programs installed on a computer, and the execution of the tasks can occupy certain computer resources, including CPU resources, storage resources (including memory resources and hard disk resources), network resources and the like.

When a task is executed locally, the computer that receives the task must rely on its own resources to process the task, including occupying its own memory resources to install a specific program for executing the task, and occupying its own CPU resources to execute the task, resulting in a large amount of resources being occupied.

In order to reduce the resource occupation of the computer receiving the task, the task may be executed in a Client/Server mode (Client/Server), the Client receives the task, and the Server executes the task. As can be seen, the client/server mode may take up more storage resources than the local execution mode due to the need to additionally install task specific client-side and server-side programs. Furthermore, since the server is often used to process a variety of tasks due to its high processing power, storage resource utilization is an important issue, and if a low-frequency task is executed in a client/server mode, the utilization of the storage resources of the server that are occupied for processing the low-frequency task is low (because of being executed rarely), thereby resulting in a waste of valuable resources of the server.

However, the server is often used to perform various tasks and/or high frequency tasks, and resources are inherently tight, which may result in more tight server resources if the server resources are occupied for processing low frequency tasks. In addition, installing a specific program for sending a task and receiving a task execution result occupies a storage resource of a client, and when the number of clients is large, the total occupied storage resource is also considerable.

Disclosure of Invention

In view of the above technical problems in the prior art, embodiments of the present disclosure provide a task processing method and apparatus, an electronic device, and a computer-readable storage medium, so as to reduce resource occupation.

A first aspect of an embodiment of the present disclosure provides a task processing method, including:

a task is obtained by accessing a first file synchronously downloaded from a cloud to a local,

the task is performed to obtain a second file,

and storing the second file to the local and uploading the second file to the cloud.

In some embodiments, the obtaining the task by accessing the first file synchronously downloaded from the cloud to the local includes:

acquiring a task by accessing a first file synchronously downloaded from a first cloud disk to a local area;

the storing the second file to a local and uploading to a cloud end comprises:

and storing the second file to the local for synchronous uploading to the first cloud disk.

the storing the second file to a local and uploading to a cloud end comprises:

and storing the second file locally to upload to a second cloud disk different from the first cloud disk.

In some embodiments, after the step of performing the task to obtain the second file, the method further comprises:

acquiring address information of the second file on the second cloud disk;

and writing the address information of the second file on the second cloud disk into a third file and storing the third file locally so as to synchronously upload the third file to the first cloud disk.

A second aspect of the embodiments of the present disclosure provides a method for task processing, including:

synchronously uploading a first file for storing task information to a cloud;

downloading a second file from a cloud, the second file being a file obtained by performing the task according to the method of the foregoing embodiments

A third aspect of the embodiments of the present disclosure provides a task processing apparatus, including:

the task obtaining module is used for obtaining a task by accessing a first file synchronously downloaded from a cloud to the local;

the task execution module is used for executing the task to acquire a second file;

and the first storage module is used for storing the second file to the local and uploading the second file to the cloud.

In some optional embodiments, the task obtaining module is configured to: acquiring a task by accessing a first file synchronously downloaded from a first cloud disk to a local area; the first storage module is configured to: and storing the second file to the local for synchronous uploading to the first cloud disk.

In some optional embodiments, the task obtaining module is configured to: acquiring a task by accessing a first file synchronously downloaded from a first cloud disk to a local area; the first storage module is configured to: and storing the second file locally to upload to a second cloud disk different from the first cloud disk. Optionally, the task processing device may further include: the address acquisition module is used for acquiring the address information of the second file on the second cloud disk; and the second storage module is used for writing the address information of the second file in the second cloud disk into a third file and storing the third file locally so as to synchronously upload the third file to the first cloud disk.

A fourth aspect of the embodiments of the present disclosure provides a task processing apparatus, including:

the uploading module is used for synchronously uploading a first file for storing the task information to the cloud;

and a downloading module, configured to download a second file from a cloud, where the second file is obtained by executing the task according to the method described in each of the foregoing embodiments.

A fifth aspect of an embodiment of the present disclosure provides an electronic device, including:

a memory and one or more processors;

wherein the memory is communicatively coupled to the one or more processors, and the memory stores instructions executable by the one or more processors, and when the instructions are executed by the one or more processors, the electronic device is configured to implement the method according to the foregoing embodiments.

A sixth aspect of the embodiments of the present disclosure provides a computer-readable storage medium having stored thereon computer-executable instructions, which, when executed by a computing apparatus, may be used to implement the method according to the foregoing embodiments.

A seventh aspect of embodiments of the present disclosure provides a computer program product comprising a computer program stored on a computer-readable storage medium, the computer program comprising program instructions which, when executed by a computer, are operable to implement a method as in the preceding embodiments.

In the embodiment of the disclosure, a program for synchronization, which is pre-installed by a plurality of terminals, is utilized, and except for the pre-installed program, the terminal interacting with the user does not need to install a specific program for executing the task or other programs such as a client program required by a client/server mode, so that the occupation of storage resources of the terminal is reduced, and CPU resources of the terminal are not occupied for executing the task; the terminal for actually executing the task only needs to install a specific program for executing the task, and does not need to install other programs such as a server-side program and the like required by a client/server mode, so that the occupation of storage resources of the terminal is reduced, and the occupation of computer resources is reduced as a whole.

Drawings

The features and advantages of the present disclosure will be more clearly understood by reference to the accompanying drawings, which are illustrative and not to be construed as limiting the disclosure in any way, and in which:

FIG. 1 is a schematic diagram of a computer system suitable for use in accordance with the present disclosure;

FIG. 2 is a flow diagram of a method of task processing, shown in accordance with some embodiments of the present disclosure;

FIG. 3 is a flow diagram of a method of task processing according to some further embodiments of the present disclosure;

FIG. 4 is a schematic diagram of a task processing device according to some embodiments of the present disclosure;

FIG. 5 is a schematic diagram of a task processing device according to some further embodiments of the present disclosure;

FIG. 6 is a schematic diagram of an electronic device shown in accordance with some embodiments of the present disclosure.

Detailed Description

In the following detailed description, numerous specific details of the disclosure are set forth by way of examples in order to provide a thorough understanding of the relevant disclosure. However, it will be apparent to one of ordinary skill in the art that the present disclosure may be practiced without these specific details. It should be understood that the use of the terms "system," "apparatus," "unit" and/or "module" in this disclosure is a method for distinguishing between different components, elements, portions or assemblies at different levels of sequence. However, these terms may be replaced by other expressions if they can achieve the same purpose.

It will be understood that when a device, unit or module is referred to as being "on" … … "," connected to "or" coupled to "another device, unit or module, it can be directly on, connected or coupled to or in communication with the other device, unit or module, or intervening devices, units or modules may be present, unless the context clearly dictates otherwise. For example, as used in this disclosure, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of the present disclosure. As used in the specification and claims of this disclosure, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are inclusive in the plural, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" are intended to cover only the explicitly identified features, integers, steps, operations, elements, and/or components, but not to constitute an exclusive list of such features, integers, steps, operations, elements, and/or components.

These and other features and characteristics of the present disclosure, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will be better understood by reference to the following description and drawings, which form a part of this specification. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the disclosure. It will be understood that the figures are not drawn to scale.

Various block diagrams are used in this disclosure to illustrate various variations of embodiments according to the disclosure. It should be understood that the foregoing and following structures are not intended to limit the present disclosure. The protection scope of the present disclosure is subject to the claims.

FIG. 1 is a schematic diagram of a computer system to which the present disclosure is applicable. In the system shown in fig. 1, a first terminal (a1, a2, A3,. ann, n is a natural number) and a second terminal (C1, C2, C3,. Cm, m is a natural number) respectively perform independent data interaction with a cloud disk B (only 1 cloud disk is illustrated in fig. 1, and may include a plurality of cloud disks independent from each other). Data interaction between the terminal and the cloud disk is also called data interaction between the local and the cloud.

The terminal may be a mobile terminal such as a mobile phone, a Personal Digital Assistant (PDA), a notebook computer, or a fixed terminal such as a desktop computer, and a plurality of terminals may be the same or different regardless of the first terminal or the second terminal. The cloud disk may be composed of a single server or a server group, and the server group may be centralized or distributed.

In order to perform data interaction with the cloud disk, the terminal needs to install a corresponding client program. For example, if the terminal is a PC and the cloud disk is OneDrive, the OneDrive client PC version needs to be installed on the terminal.

According to different services provided by the cloud disk, data interaction between the terminal and the cloud disk is different. For example, when a cloud disk (e.g., a hundred-degree cloud disk) is only used as a cloud storage space, as with a local storage space, a user needs to give a specific instruction (e.g., copy, cut); when a cloud disk (such as a Dropbox, a Google Drive, an iCloud Drive and an OneDrive) provides a synchronization service for a file/folder/disk partition/disk, data interaction is performed according to a preset synchronization rule, and can be performed automatically or according to a request of a user (the user only needs to give a 'synchronization' instruction and does not need to give a specific instruction).

FIG. 2 illustrates a task processing method that may be performed by the system shown in FIG. 1, according to some embodiments of the present disclosure. As shown in fig. 2, the task processing method may include the steps of:

s201, the first terminal writes the task information into a task file and stores the task file locally so as to synchronously upload the task information to a cloud. Wherein the first terminal is a terminal that interacts with the user and receives the task first.

According to the aforementioned prior art, if a task is executed locally, the first terminal needs to install a specific program for executing the task; if the task is executed in the client/server mode and the first terminal acts as a client, the first terminal still needs to install a specific program for sending the task to the server and receiving the task execution result returned by the server. It can be seen that according to the foregoing prior art, the first terminal always needs to install the foregoing specific program for the task, and if the task belongs to a low-frequency task, the utilization rate of the specific program is low, so that the utilization rate of the storage space of the specific program is low, and the storage resource is wasted. In view of the above problem, the inventors have found that, since "synchronization" generally belongs to a high-frequency task, many terminals pre-install a program for synchronization (including one drive, a Dropbox, and other cloud synchronization programs dedicated for synchronization, and an Evernote, one root, a Google Keep, and other programs that support a cloud synchronization function) and use the program frequently, so that when a first terminal sends a task and receives a task execution result by using the pre-installed program for synchronization, it is not necessary to additionally install the aforementioned specific program for the task, and waste of storage resources can be reduced.

Specifically, after the first terminal receives a task provided by the user through interaction with the user, information of the task can be written into the task file. In some embodiments, the task may be to obtain a file, for example, the task "obtain an accompaniment version of song X" is to obtain a music file, the task "obtain a photo at a shop near the geographic point Y" is to obtain a photo file, and accordingly, the file name of the task file may correspond to the task, for example, "accompaniment" or "photo at a shop" and the like, and the task file may be a synchronization file already set by the cloud synchronization program, or stored in a synchronization folder already set by the cloud synchronization program, or a file storing records of a program that supports the cloud synchronization function. Therefore, in the subsequent steps, the task file can be automatically uploaded to the cloud.

S202, the first terminal synchronously uploads the task file to a cloud. This step is the first step in the task transfer.

The number of the first terminals may be multiple, and the synchronization rule of each first terminal may be the same or different. However, in order for the synchronization of the task file to be smooth, the synchronization rule of the first terminal should include at least one of the following rules:

1. when the local file exists and the cloud end does not have the file with the same name, uploading the local file to the cloud end;

2. when a file exists locally and the cloud also has a file with the same name, comparing versions of the file and the cloud (the file version is usually related to the last update time of the file but is not necessarily determined by the file version, that is, the more recent file version is not necessarily the later update time, generally, the version of the file is changed by the file saving operation of a user), and if the version of the local file is more recent, uploading the local file to the cloud to update (specifically including operations such as replacement and combination, which are not described any more) the file with the same name of the cloud.

It should be noted that the synchronization operation does not change the version of the synchronized file, and the version of a file before synchronization is retained after synchronization.

In some embodiments, the task file is uploaded to the cloud synchronously, which means to a specific cloud disk, for example, the first cloud disk.

S203, the second terminal synchronously downloads the task file to the local from the cloud. Wherein the second terminal is a terminal that performs a task. This step is the last step in the task delivery.

It should be noted that the cloud does not distinguish whether the terminal is the first terminal or the second terminal, and is only a client for the cloud regardless of whether the terminal is the first terminal or the second terminal. The first terminal and the second terminal are different in that: the first terminal does not have a specific program installed to perform the task, and the version of the task file stored therein may be changed by interaction with the user (e.g., the user has performed a "save" operation); the second terminal has installed a specific program to perform the task and the version of the task file it stores does not generally change (the second terminal generally does not have to interact with the user) unless the task file is updated by synchronization.

The number of the second terminals may be multiple, similar to the first terminal, and the synchronization rule of each second terminal may be the same or different. Also for smooth synchronization of the task file, the synchronization rules of the second terminal should include at least one of the following rules:

1. when no file exists in the local area and a file exists in the cloud end, downloading the cloud end file to the local area;

2. and when the local file exists and the cloud end has the file with the same name, comparing the versions of the local file and the cloud end file, and downloading the cloud end file to the local to update the local file with the same name if the version of the cloud end file is newer.

In some embodiments, the synchronization of the second terminal is automatic, without human intervention.

In some embodiments, the step of synchronously downloading the task file from the cloud refers to downloading the task file from a specific cloud disk, for example, the first cloud disk in step S202, which provides the synchronization service and belongs to the synchronized cloud disk.

And S204, the second terminal accesses the task file to acquire the task.

In order to perform a task, the second terminal should install a specific program (task execution program) for performing the task. In some embodiments, the task executive may run all the time to automatically retrieve and execute tasks.

Specifically, in order to acquire a task, the task execution software may preset an address (e.g., an address of a local synchronization folder) and a format requirement (e.g., a file name is "accompaniment" or "photo at head of door"), and acquire a file (i.e., a task file) meeting the format requirement at the address according to a preset rule (e.g., timing or triggered by an event). After the task file is obtained, the content of the task file can be read and the task information can be analyzed, so that the task is obtained.

In some embodiments, to avoid repeatedly executing tasks, a task execution log may be created to record tasks that have already been executed and to retrieve new tasks that have not been executed by comparing the tasks retrieved from the task file to the tasks recorded in the task execution log.

And S205, the second terminal executes the task. And the task is locally executed through a task execution program installed in the second terminal.

And S206, the second terminal saves the result obtained by executing the task as a file and stores the file locally so as to synchronously upload the file to the cloud. When the task is to acquire a certain file, the result of executing the task is the certain file, such as the aforementioned music file or photo file.

Although the second terminal is the terminal that first obtains the task execution result, since the first terminal is the terminal that interacts with the user, the result also needs to be finally transferred to the first terminal. In order to transmit the data to the first terminal, the data needs to be uploaded to the cloud end at first, because the first terminal and the second terminal cannot communicate directly.

It should be noted that the task execution and the synchronous uploading are two independent processes, which respectively correspond to the task execution program and the synchronous program, and since the second terminal is unattended, seamless connection between the two processes is very important. Therefore, the storage address of the result file (i.e., the file storing the result) of the task execution program needs to be preset as the synchronization folder of the synchronization program, so that the result file can be directly stored in the synchronization folder of the synchronization program to be synchronously uploaded to the cloud.

And S207, the second terminal synchronously uploads the file for storing the result to a cloud.

In some embodiments, the synchronization program does not distinguish between the task files and the result files, i.e., the synchronization rules to which the task files and the result files apply are the same. Therefore, the synchronization rule applicable for the second terminal to synchronously upload the result file to the cloud and the synchronization rule applicable for the task file to be synchronously downloaded to the local in step S203 do not conflict with each other, but the following rules are added:

and when the local file exists and the cloud does not have the file with the same name, uploading the local file to the cloud.

In other embodiments, the synchronization program may apply different synchronization rules to different folders. Thus, the synchronization folders can be divided into task folders and result folders, and different synchronization rules can be applied. For example, the task folder of the second terminal can only be downloaded from the cloud and cannot be uploaded to the cloud, and as a result, the task folder can only be uploaded to the cloud and cannot be downloaded from the cloud; the task folder of the first terminal can only be uploaded to the cloud and cannot be downloaded from the cloud, and as a result, the task folder can only be downloaded from the cloud and cannot be uploaded to the cloud. Therefore, the occupation of network/storage resources can be reduced to a certain extent.

In some embodiments, uploading the result file to the cloud refers to uploading to a specific cloud disk, for example, the first cloud disk in step S202.

And S208, the first terminal synchronously downloads and stores the result file from the cloud. This step is the last step of the result file transfer, whereby the result file is finally transferred to the first terminal, so that the user interacting with the first terminal can obtain the result file.

This step is also implemented by the aforementioned pre-installed program for synchronization of the first terminal, and the setting of the program is similar to step S207 and will not be described again.

Further, the synchronization rule of the program does not conflict with the synchronization rule in step S202, and the following rule is added:

and when the cloud has the file but the local file has no same name, downloading the cloud file to the local.

Compared with the prior art local execution or client/server mode, the task processing method according to the embodiment of the present disclosure utilizes a program for synchronization (e.g., OneDrive, etc.) pre-installed by many terminals, in addition to the pre-installed program for synchronization, as a terminal (i.e., a first terminal) interacting with a user, it does not need to install a specific program for performing the task or other programs such as a client program required by the client/server model, thereby reducing the occupation of the storage resource, and being used as the terminal (namely the second terminal) which actually executes the task without occupying the CPU resource of the terminal to execute the task, it only needs to install a specific program for performing the task, does not need to install other programs such as a server-side program required by the client/server model, thereby reducing the occupation of the storage resources thereof and reducing the occupation of the computer resources as a whole. In addition, since the server is not required to execute the task (it is enough to find a terminal capable of executing the task as the second terminal at will), the problem of low utilization rate of server resources is not caused.

In the task processing method of the embodiment of the invention, although the data cannot be directionally transferred only between the first terminal which initially receives the task and the second terminal which executes the task due to the unidirectional transfer of the task data and the task execution result data, but a plurality of terminals may synchronously download the task and/or the task execution result, thereby possibly causing the occupation of some extra storage/network resources, due to the temporary property of the data, the occupied storage resources can be released by regular cleaning. On the other hand, cleaning of the program is much more complicated than cleaning of temporary data.

In the task processing method of the embodiment shown in fig. 2, the task file and the result file can both be synchronized by the same cloud disk, which has the advantages of low system complexity and simple interaction. However, the synchronization operation may consume a large amount of resources of the system, especially large files. Therefore, in the above embodiment, if the result file is too large, the resources of the whole system are occupied too much, and a heavy burden is imposed on the system.

In order to reduce the occupation of system resources, the transfer of the result file in the system may be limited appropriately, as shown in the task processing method of another embodiment shown in fig. 3. The method may comprise the steps of:

s301, the first terminal writes the information of the task into the task file and stores the task file locally to upload the task file to the cloud synchronously, and the specific content may refer to the description in step S201.

S302, the first terminal uploads the task file to the first cloud disk synchronously, and the specific content may refer to the description in step S202.

S303, the second terminal synchronously downloads the task file from the first cloud disk, and the specific content may refer to the description in step S203.

S304, the second terminal accesses the task file to obtain the task, and the specific content may refer to the description in step S204.

S305, the second terminal executes the task, and the specific content may refer to the description in step S205.

And S306, the second terminal saves the result obtained by executing the task as a file, stores the file locally and uploads the file to a second cloud disk.

As previously mentioned, if the result file is too large, synchronizing the result file may take up too much resources of the overall system. In order to reduce the occupation of resources, the result file can be downloaded at the first terminal according to the needs of the user instead of being automatically downloaded synchronously. In some embodiments, a first cloud disk that is a synchronous cloud disk may provide on-demand download functionality, such as OneDrive 'file on-demand', where files are downloaded from the cloud to the local only when needed by the user (e.g., the user opens the file), in which embodiments the cloud disk (second cloud disk) that delivers the result file may be the same as the first cloud disk. In other embodiments, however, the first cloud disk, which is a synchronous cloud disk, does not provide similar functionality, and as a result, files are not suitable for transfer through the first cloud disk as well.

In the task processing method of this embodiment, the result file may be uploaded to a second cloud disk (e.g., a hundred-degree network disk) different from the first cloud disk, and the second cloud disk may be a storage cloud disk, and the uploading and downloading of the second cloud disk are both passive (the uploading and downloading of the synchronous cloud disk are active/automatic), and need to be triggered by an external instruction, so as to implement the downloading of the result file on the first terminal as needed.

As a result, the storage path of the file in the second terminal is not particularly limited as long as the file is not a synchronization folder of the first cloud disk, so as not to be uploaded to the first cloud disk by error synchronization. For example, the result file may be stored to a certain temporary folder of the second terminal.

And S307, the second terminal uploads the file for storing the result to a second cloud disk.

Different from the first terminal, the second terminal is unattended, so that the result file needs to be automatically uploaded to the second cloud disk without a synchronization mode. In some embodiments, the functionality of automatically uploading the result file to the second cloud disk may be integrated in the task execution program. Taking the Baidu network disk as an example, according to an API (application programming interface) provided by the Baidu network disk, an access token (access token) of a specified account is obtained, and the task execution program can automatically upload the result file to the second cloud disk according to the URL address of the Baidu network disk and the access token. In other embodiments, the client program of the second cloud disk may be called by the task execution program to automatically run, and the client program obtains the result file upload task from the task execution program through the API interface and automatically executes the upload task.

And S312, the first terminal downloads the file for storing the result from the second cloud disk. Although the result files are all downloaded, unlike the synchronous download in step S208, the download in this step is initiated by a user request.

In some optional implementation manners of this embodiment, the first terminal also installs the client program of the second cloud disk, and the user logs in the client program by using the account used in the step S307 to upload the result file in the first terminal, finds the result file uploaded on the second cloud disk, and then downloads the result file to the first terminal. If the account also stores other files on the second cloud disk, the user may spend additional time finding the result file. In short, in these implementations, the user knows in advance the relatively coarse address of the result file (e.g., on which cloud disk to store), and needs to find the result file itself and download it.

Compared with the embodiment shown in fig. 2, in the embodiment, the task file is still transferred through the synchronous cloud disk, and the result file is transferred through the additional storage cloud disk, so that the result file is downloaded as required, and the occupation of the whole system resource is reduced.

In some optional implementations of this embodiment, considering that the time for uploading the result file to the second cloud disk may be difficult to determine, a mechanism for notifying/reminding the user after uploading the result file to the second cloud disk may be added; in addition, the rough address described in step S312 may not be suitable in some situations, the user may need an accurate address (for example, the link and the extraction code of the hundred-degree netdisk file, where the link is the accurate address thereof, and the extraction code is the access password thereof) to download, and providing the accurate address also plays a role in notifying/reminding the user.

Specifically, between step S307 and step S312, the following steps may be included:

and S308, the second terminal acquires the address of the file for storing the result on the second cloud disk.

Specifically, the task execution program may obtain the address of the result file on the second cloud disk through interaction with the second cloud disk (direct interaction or indirect interaction through client software of the second cloud disk).

And S309, the second terminal writes the file for storing the result into the address file at the address of the second cloud disk and stores the address file locally so as to synchronously upload the address file to the first cloud disk. Specific contents can be referred to the description of step S206, and the difference is only that the files uploaded in synchronization are different.

And S310, the second terminal synchronously uploads the address file to the first cloud disk. Specific contents can be referred to the description of step S207, and the difference is only that the files uploaded in synchronization are different.

S311, the first terminal synchronously downloads the address file from the first cloud disk. The specific content can be referred to the description of step S208, and the difference is only different in the synchronously downloaded files.

Therefore, when the user acquires the address file on the first terminal, the notification that the result file is uploaded to the second cloud disk is received. In the subsequent step S312, the user may download the result file from the second cloud disk according to the address file.

The above is a specific embodiment of the task processing method provided by the present disclosure.

FIG. 4 is a schematic diagram of a task processing device, shown in accordance with some embodiments of the present disclosure. As shown in fig. 4, the task processing device 400 includes a task obtaining module 410, a task executing module 420, and a first storage module 430. The functions of the task processing device may be performed by the second terminal in fig. 1. The task processing device may include:

the task obtaining module 410 is configured to obtain a task by accessing a first file synchronously downloaded from the cloud to the local. For specific content, refer to the description of step S204;

a task execution module 420, configured to execute the task to obtain the second file. The specific content can be referred to the description of step S205;

the first storage module 430 is configured to store the second file locally and upload the second file to a cloud. For details, refer to the description of step S206.

In some optional implementations of this embodiment, the task execution module 420 is configured to obtain the task by accessing a first file that is synchronously downloaded from the first cloud disk to the local, and the first storage module 430 is configured to store the second file to the local to be synchronously uploaded to the first cloud disk. Other details according to the present implementation may be understood with reference to the relevant description and effects in the embodiment shown in fig. 2, which are not described herein again.

In other alternative implementations of this embodiment, the task execution module 420 is configured to obtain the task by accessing a first file that is synchronously downloaded from a first cloud disk to a local, and the first storage module 430 is configured to store the second file to the local to be synchronously uploaded to a second cloud disk different from the first cloud disk. In an implementation, the task processing device 400 may further include: an address obtaining module 440, configured to obtain address information of a second file on the second cloud disk; the second storage module 450 is configured to write the address information of the second file in the second cloud disk into a third file and store the third file locally to be uploaded to the first cloud disk synchronously. Other details according to the present implementation may be understood with reference to the relevant description and effects in the embodiment shown in fig. 3, and are not described herein again.

FIG. 5 is a schematic diagram of a task processing device according to some further embodiments of the present disclosure. As shown in fig. 5, the task processing device 500 includes an upload module 510 and a download module 520. The functions of the task processing device may be performed by the first terminal in fig. 1. The task processing device may include:

the uploading module 510 is configured to upload a first file storing task information to the cloud synchronously;

the downloading module 520 is configured to download a second file from the cloud, where the second file is obtained by executing the task according to the task processing method shown in fig. 2 or fig. 3.

Other details of the task processing device according to the embodiment of the present invention may be understood with reference to the corresponding related description and effects in the embodiments shown in fig. 2 or fig. 3, and are not described herein again.

Fig. 6 is a schematic diagram of an electronic device shown in accordance with some embodiments of the present disclosure. As shown in fig. 6, the electronic device 600 may include a memory 610 and one or more processors 620. The memory 610 and the processor 620 may be connected via a bus or other communication means. The memory 610 stores instructions executable by the one or more processors 620, and when the instructions are executed by the one or more processors 620, the electronic device is configured to implement the task processing method as shown in fig. 2 or fig. 3.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD) or a Solid State Drive (SSD), etc.; the storage medium may also comprise a combination of memories of the kind described above.

Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A task processing method, comprising:

the task is performed to obtain a second file,

2. The method of claim 1,

the task is obtained by accessing a first file synchronously downloaded from a cloud to a local server, and the task comprises the following steps:

the storing the second file to a local and uploading to a cloud end comprises:

3. The method of claim 1,

the storing the second file to a local and uploading to a cloud end comprises:

4. The method of claim 3, further comprising, after the step of performing the task to obtain the second file:

acquiring address information of the second file on the second cloud disk;

5. A task processing method, comprising:

synchronously uploading a first file for storing task information to a cloud;

downloading a second file from a cloud, the second file being a file obtained by performing the task according to the task processing method of any one of claims 1 to 4.

6. A task processing apparatus, comprising:

7. The task processing device according to claim 6,

the task acquisition module is used for:

the first storage module is configured to:

8. The task processing device according to claim 6,

the task acquisition module is used for:

the first storage module is configured to:

9. The apparatus for task processing according to claim 8, further comprising:

the address acquisition module is used for acquiring the address information of the second file on the second cloud disk;

and the second storage module is used for writing the address information of the second file in the second cloud disk into a third file and storing the third file locally so as to synchronously upload the third file to the first cloud disk.

10. An apparatus for task processing, comprising:

a downloading module, configured to download a second file from a cloud, where the second file is obtained by executing the task according to the task processing method of any one of claims 1 to 4.