CN103995745B - IP hard disk task execution method and IP hard disk - Google Patents

Abstract

The embodiment of the invention discloses an IP hard disk task execution method, which is used to avoid waste of hard disk execution result data. The method in the embodiment of the present invention includes: receiving a work task and a work identification sent by an external node, where the work identification is used to identify the work task; judging whether the external node is an available external node; when the external node is available For an external node, obtain the intermediate execution result corresponding to the work identifier, the intermediate execution result is the intermediate execution result corresponding to the work task; complete the execution of the work task according to the intermediate execution result, and obtain the The final execution result corresponding to the work task; sending the final execution result to the external node. The embodiment of the present invention also provides a related IP hard disk.

Description

IP hard disk task execution method and IP hard disk

technical field

The invention relates to the communication field, in particular to an IP hard disk task execution method and an IP hard disk.

Background technique

With the development of science and technology, cloud storage technology is rising day by day, which accelerates the application of Key-Value-based interfaces. The Internet Protocol (IP, Internet Protocol) hard disk based on Key-Value semantics has emerged in the industry, abandoning the traditional SCSI interface and protocol standards, and using IP for external communication.

Currently released IP hard disks provide an open Key-Value semantic interface, and can also support more service capabilities, such as hard disk built-in compression, encryption, and full-disk integrity check. Because the IP hard disk has a certain built-in computing power and is not interconnected with the external processor through the traditional direct connection method, some operations of the external processor on the hard disk can be transferred to the hard disk for operation, such as anti-virus, compression for local data, and reloading. Delete, full-disk verification, etc., such operations can be dynamically loaded by the external processor by means of mobile virtual machine or mobile code, or local Firmware can be statically loaded to the computing unit of the IP hard disk for execution, and the external processor will be notified of the execution result.

However, since the IP hard disk is separated from the external processor when performing the above operations, when the IP hard disk performs the above operations for a long time, the external processor may be offline or invalid. At this time, if the IP hard disk needs to notify the external node of the intermediate execution result, the operation of notifying the external node will not be completed. This leads to the inability to output or even lose the intermediate execution results of the IP hard disk, resulting in waste of execution result data.

Contents of the invention

Embodiments of the present invention provide an IP hard disk task execution method and an IP hard disk, which can avoid waste of IP hard disk execution result data.

The first aspect of the embodiments of the present invention provides a method for executing an IP hard disk task, including:

The network interconnection protocol IP hard disk receives the work task and the work identification sent by the external node, and the work identification is used to identify the work task;

judging whether the external node is an available external node;

When the external node is an available external node, acquire an intermediate execution result corresponding to the work identifier, where the intermediate execution result is an intermediate execution result corresponding to the work task;

completing the execution of the work task according to the intermediate execution result, and obtaining a final execution result corresponding to the work task;

Send the final execution result to the external node.

In combination with the first aspect of the embodiments of the present invention, in the first implementation manner of the first aspect of the embodiments of the present invention, the work task includes multiple execution steps, and the IP hard disk receives the work task and the work identification sent by the external node Previously also included:

Executing at least one of the execution steps in the plurality of execution steps to obtain the intermediate execution result;

The corresponding relationship between the job identifier and the intermediate execution result is saved.

With reference to the first aspect of the embodiments of the present invention, in the second implementation manner of the first aspect of the embodiments of the present invention, the external node has a node identifier;

The judging whether the external node is an available external node includes:

Comparing the node identifier of the external node with the node identifier of the available external node preset by the IP hard disk, if the node identifier of the external node is the same as the node identifier of the available external node preset by the IP hard disk , it is determined that the external node is an available external node.

Combining the first aspect of the embodiments of the present invention, the first implementation of the first aspect and the second implementation of the first aspect, in the third implementation of the first aspect of the embodiments of the present invention, the task An association identifier is included, and the association identifier is used to identify other tasks associated with the work task; the method further includes:

Save the corresponding relationship between the final execution result and the association identifier, so that other tasks associated with the work task can obtain the final execution result according to the association identifier, and use the final execution result as the execution condition, execute the execution steps included in other tasks associated with the work task.

A second aspect of the embodiments of the present invention provides an IP hard disk, including:

A receiving module, configured to receive a work task and a work identification sent by an external node, and the work identification is used to identify the work task;

A judging module, configured to judge whether the external node is an available external node;

An acquisition module, configured to acquire an intermediate execution result corresponding to the work identifier when the external node is an available external node, where the intermediate execution result is an intermediate execution result corresponding to the work task;

A result execution module, configured to complete the execution of the work task according to the intermediate execution result, and obtain a final execution result corresponding to the work task;

An output module, configured to send the final execution result to the external node.

In conjunction with the second aspect of the embodiments of the present invention, in the first implementation manner of the second aspect of the embodiments of the present invention, the work task includes multiple execution steps, and the IP hard disk further includes:

an intermediate execution module, configured to execute at least one of the execution steps in the plurality of execution steps, and obtain the intermediate execution result;

A saving module, configured to save the corresponding relationship between the job identifier and the intermediate execution result.

With reference to the second aspect of the embodiments of the present invention, in a second implementation manner of the second aspect of the embodiments of the present invention, the external node has a node identifier;

The judgment module is specifically used for:

Comparing the node identifier of the external node with the node identifier of the available external node preset by the IP hard disk, if the node identifier of the external node is the same as the node identifier of the available external node preset by the IP hard disk , it is determined that the external node is an available external node.

Combining the second aspect of the embodiments of the present invention, the first implementation of the second aspect and the second implementation of the second aspect, in the third implementation of the second aspect of the embodiments of the present invention, the task Including an association identifier, the association identifier is used to identify other tasks associated with the work task; the saving module is also used for:

Save the corresponding relationship between the final execution result and the association identifier, so that other tasks associated with the work task can obtain the final execution result according to the association identifier, and use the final execution result as the execution condition, execute the execution steps included in other tasks associated with the work task.

As can be seen from the above technical solutions, in the embodiment of the present invention, the IP hard disk receives the work task and the work identification sent by the external node; judges whether the external node is an available external node; when the external node is an available external node , obtain an intermediate execution result according to the work identification; complete all execution steps corresponding to the work task according to the intermediate execution result, and obtain the final execution result corresponding to the work task; send the final execution result to the external node. Among them, in the embodiment of the present invention, after the IP hard disk receives the work task and the work identification sent by the external node, it can obtain the intermediate execution result of the work task according to the work identification, so that the IP hard disk can continue to use the first task in subsequent operations. Intermediate execution results. This ensures that the intermediate execution results saved in the IP hard disk can continue to be used after the IP hard disk establishes a connection with an available node, so that the intermediate execution results of the IP hard disk can be output without being lost, and the waste of execution result data on the IP hard disk is avoided.

Description of drawings

Fig. 1 is a flow chart of an embodiment of an IP hard disk task execution method in an embodiment of the present invention;

Fig. 2 is the flow chart of another embodiment of the IP hard disk task execution method in the embodiment of the present invention;

Fig. 3 is an embodiment structural diagram of IP hard disk in the embodiment of the present invention;

Fig. 4 is another embodiment structural diagram of IP hard disk in the embodiment of the present invention;

Fig. 5 is a structural diagram of another embodiment of the IP hard disk in the embodiment of the present invention.

detailed description

The embodiment of the present invention provides an IP hard disk task execution method, which can avoid the waste of IP hard disk execution result data. The embodiment of the present invention also provides a related IP hard disk, which will be described separately below.

Please refer to Figure 1 for the basic flow of the IP hard disk task execution method provided by the embodiment of the present invention, including:

101. Receive the work task and work identification sent by the external node;

The external nodes described in the embodiments of the present invention are used to send information such as work tasks to the IP hard disk, and receive execution results obtained by executing the work tasks on the IP hard disk. Wherein, the external nodes include, but are not limited to, PCs, servers, central processing units, and other devices with computing, processing, or task delivery functions. When the external node is connected to the IP hard disk, the work task and the work identification of the work task are sent to the IP hard disk, wherein the work identification is used to identify the work task.

The IP receives the work task and the work identification sent by the external node.

102. Determine whether the external node is an available external node;

After receiving the work task sent by the external node, the IP hard disk needs to judge whether the external node is an available external node. There are many specific judgment methods, which will be described in detail in the following embodiments, and are not limited here.

103. When the external node is an available external node, obtain an intermediate execution result corresponding to the work identifier;

Before the IP hard disk accepts the work task sent by the external node, the IP hard disk may receive the work task sent by other nodes, and execute some execution steps of the work task, obtain the intermediate execution result, and then save the intermediate execution The corresponding relationship between the result and the work ID of the work task. However, due to the failure of the other node, the intermediate execution result cannot be output.

In this embodiment, the IP hard disk establishes a connection with the external node, and receives the work task and the work identification sent by the external node. If the IP hard disk has executed the work task sent by other nodes before, it can be determined according to the work identification. Get the intermediate execution result corresponding to the job identifier. Wherein, the intermediate execution result is an intermediate execution result corresponding to the work task stored in the IP hard disk.

104. Complete the execution of the work task according to the intermediate execution result, and obtain the final execution result corresponding to the work task;

After obtaining the intermediate execution result, the IP hard disk completes the execution of the work task according to the intermediate execution result, and obtains the final execution result corresponding to the work task. Preferably, since the intermediate execution result is obtained by the IP hard disk executing part of the execution steps of the work task, the IP hard disk can obtain the final execution result only by executing the remaining unexecuted steps of the work task. In particular, if the intermediate execution result is obtained by the IP hard disk executing all execution steps of the work task, the IP hard disk takes the intermediate execution result as the final execution result.

105. Send the final execution result to the external node.

After obtaining the final execution result, the IP hard disk sends the final execution result to the external node.

In this embodiment, the IP hard disk receives the work task and the work identification sent by the external node; judges whether the external node is an available external node; when the external node is an available external node, obtains the intermediate execution according to the work identification Result; complete all execution steps corresponding to the work task according to the intermediate execution result, and obtain a final execution result corresponding to the work task; send the final execution result to the external node. Wherein, in this embodiment, after the IP hard disk receives the work task and the work identification sent by the external node, it can obtain the intermediate execution result of the work task according to the work identification, so that the IP hard disk can continue to use the first intermediate execution result in subsequent operations. Results of the. This ensures that the intermediate execution results saved in the IP hard disk can continue to be used after the IP hard disk establishes a connection with an available node, so that the intermediate execution results of the IP hard disk can be output without being lost, and the waste of execution result data on the IP hard disk is avoided.

The embodiment shown in Figure 1 provides the basic flow of the IP hard disk task execution method provided by the present invention, wherein the IP hard disk, after receiving the work identification and the work task sent by the external node, completes the task according to the intermediate execution result of the work task. Execution of the work task. The following embodiments will provide the specific flow for the IP hard disk to obtain the intermediate execution result of the work task. Referring to FIG. 2, another IP hard disk task execution method provided by the present invention includes:

201. Execute at least one of the multiple execution steps of the work task to obtain an intermediate execution result;

In this embodiment, the work task includes multiple execution steps. The IP hard disk first executes at least one execution step of the multiple execution steps to obtain an intermediate execution result.

In this step, the work task can be delivered to the IP hard disk by any node, which is not limited here. Preferably, when the IP hard disk receives the work task, it can simultaneously receive the work identification of the work task, or assign a work identification to the work task, which is not limited here.

Preferably, after obtaining the intermediate execution result, the IP hard disk saves the intermediate execution result.

202. Save the correspondence between the work identifier and the intermediate execution result;

After obtaining the intermediate execution result, the IP hard disk saves the corresponding relationship between the intermediate execution result and the work ID.

Wherein, during the execution of step 201 and step 202, the node that sends the work task to the IP hard disk may remain connected to the IP hard disk, or may be disconnected from the IP hard disk, which is not limited in this embodiment.

203. Receive the work task and the work identification sent by the external node;

Wherein, the external node may or may not be the same node as the node that issues the work task to the IP hard disk in step 201, which is not limited in this embodiment.

204. Determine whether the external node is an available external node;

After receiving the work task sent by the external node, the IP hard disk needs to judge whether the external node is an available external node. There are many specific judgment methods, including: the external node has a node ID, the IP hard disk is preset with the node ID of the available external node, and the IP hard disk combines the node ID of the external node with the node ID of the available external node preset in the IP hard disk The identification is compared, and if the node identification of the external node is the same as the node identification of the available external node preset in the IP hard disk, it is determined that the external node is an available external node.

Among them, there are many forms of the node identification, such as the IP address of the node, the URL of the node, etc., and may also be in other forms, which are not limited here.

Other methods may also be used for the IP hard disk to determine whether the external node is an available external node, which is not limited in this embodiment.

205. When the external node is an available external node, obtain an intermediate execution result corresponding to the work identifier;

When the IP hard disk determines that the external node is an available external node, according to the work identification provided by the external node, the intermediate execution result corresponding to the work identification is obtained. The intermediate execution result is obtained by the IP hard disk in step 201 .

206. Complete the execution of the work task according to the intermediate execution result, and obtain the final execution result corresponding to the work task;

Since the IP hard disk only executes at least one execution step among the multiple execution steps of the work task when obtaining the intermediate execution result, the IP hard disk can obtain the final execution result only by executing the remaining unexecuted steps of the work task. In particular, if the intermediate execution result is obtained by the IP hard disk executing all execution steps of the work task, the IP hard disk takes the intermediate execution result as the final execution result.

207. Send the final execution result to the external node.

After obtaining the final execution result, the IP hard disk sends the final execution result to the external node.

On the basis of the embodiment shown in FIG. 1 , this embodiment further describes the steps for the IP hard disk to obtain intermediate execution results. Wherein, the IP hard disk executes at least one execution step of the work task, obtains an intermediate execution result, and stores the corresponding relationship between the intermediate execution result and the work identifier. Through this method, after receiving the work task and work ID sent by the external node, the IP hard disk can obtain the intermediate execution result of the work task according to the work ID, so that the IP hard disk can continue to use the first intermediate execution in subsequent operations. result. This ensures that the intermediate execution results saved in the IP hard disk can continue to be used after the IP hard disk establishes a connection with an available node, so that the intermediate execution results of the IP hard disk can be output without being lost, and the waste of execution result data on the IP hard disk is avoided.

Preferably, the work task can also include an association identifier, which is used to identify other tasks associated with the work task, and the association identifier can be obtained from the node that issued the work task by the IP hard disk, or can be obtained by the IP Hard disk specified, not limited here. Wherein, other tasks associated with the work task include: tasks whose execution condition is the final execution result of the work task. After step 207 is completed, the IP hard disk can also save the final execution result, and save the corresponding relationship between the final execution result and the association identifier, so that other tasks associated with the work task can obtain the execution result according to the association identifier. The final execution result, and using the final execution result as an execution condition, execute the execution steps included in other tasks associated with the work task.

In order to facilitate understanding of the above embodiment, a specific application scenario of the above embodiment will be taken as an example for description below:

There are multiple IP addresses preset in the IP hard disk, and the nodes corresponding to these IP addresses are external nodes available by default for the IP hard disk.

Node A issues three tasks to the IP hard disk, namely task 1, task 2 and task 3. Among them, task 1 is to disinfect the target file 1, task 2 is to disinfect the target file 2, and task 3 is to compress the sterilized target file 1 and the sterilized target file 2 into a compressed file and output it to the external node .

After receiving task 1, task 2, and task 3, the IP hard disk specifies job IDs for the three tasks as Job1, Job2, and Job3, respectively. Wherein, Job1 is used to identify task 1, Job2 is used to identify task 2, and Job3 is used to identify task 3. Since the three tasks are related, the IP hard disk specifies that the associated identifiers of the three tasks are all JobListOne.

The hard disk executes task 1 and task 2, that is, respectively disinfects the target file 1 and target file 2, and the target file 1 after disinfection, the associated identifier of the target file 1 JobListOne, the target file 2, and the associated identifier of the target file 2 JobListOne It is stored in the dedicated "intermediate execution result storage area" divided by the hard disk.

At this time, the IP hard disk needs to perform task 3. Since the associated identifier JobListOne of task 3 is the same as the associated identifier of task 1 and task 2, the IP hard disk obtains the execution results corresponding to Job1 and Job2 from the "intermediate execution result storage area", that is, the disinfected target file 1 and the disinfected target file2.

The IP hard disk executes task 3, compresses the anti-virus target file 1 and the anti-virus target file 2 into a compressed file, and saves the compressed file and the corresponding job ID Job3 in the "intermediate execution result storage area". At this time, node A is offline, and the IP hard disk cannot output the compressed file.

After 10 minutes, node B establishes a connection with the IP hard disk, and sends task 3 and job ID Job3 to the IP hard disk. The IP hard disk receives task 3 and job ID Job3.

The IP hard disk determines that the IP address of node B is within the preset IP addresses in the IP hard disk, and thus determines that node B is an available external node. The IP hard disk obtains the above-mentioned compressed file stored in the "intermediate execution result storage area", uses the compressed file as the final execution result of Job3, and outputs the compressed file to node B.

The embodiment of the present invention also provides related IP hard disk, its basic structure sees Fig. 3, mainly comprises:

A receiving module 301, configured to receive a work task and a work identification sent by an external node, where the work identification is used to identify the work task;

Judging module 302, configured to judge whether the external node is an available external node;

An acquisition module 303, configured to acquire an intermediate execution result corresponding to the work identifier when the external node is an available external node, where the intermediate execution result is an intermediate execution result corresponding to the work task;

The result execution module 304 is configured to complete the execution of the work task according to the intermediate execution result, and obtain the final execution result corresponding to the work task;

An output module 305, configured to send the final execution result to the external node.

In this embodiment, the receiving module 301 receives the work task and the work identifier sent by the external node; the judging module 302 judges whether the external node is an available external node; when the external node is an available external node, the obtaining module 303 according to The work identification obtains an intermediate execution result; the result execution module 304 completes all execution steps corresponding to the work task according to the intermediate execution result, and obtains the final execution result corresponding to the work task; the output module 305 outputs the final execution result sent to the external node. Wherein, in this embodiment, after the IP hard disk receives the work task and the work identification sent by the external node, it can obtain the intermediate execution result of the work task according to the work identification, so that the IP hard disk can continue to use the first intermediate execution result in subsequent operations. Results of the. This ensures that the intermediate execution results saved in the IP hard disk can continue to be used after the IP hard disk establishes a connection with an available node, so that the intermediate execution results of the IP hard disk can be output without being lost, and the waste of execution result data on the IP hard disk is avoided.

The embodiment shown in Figure 3 provides the basic structure of the IP hard disk provided by the present invention, and the following embodiments will provide a more specific structure of the IP hard disk, please refer to Figure 4, another kind of IP hard disk provided by the present invention IP hard drives include:

An intermediate execution module 401, configured to execute at least one execution step in a plurality of execution steps of a work task, and obtain an intermediate execution result;

A saving module 402, configured to save the corresponding relationship between the work identifier and the intermediate execution result;

A receiving module 403, configured to receive a work task and a work identification sent by an external node, where the work identification is used to identify the work task;

Judging module 404, configured to judge whether the external node is an available external node;

Preferably, the judgment module 404 may be specifically configured to: compare the node identifier of the external node with the node identifier of the available external node preset by the IP hard disk, if the node identifier of the external node is the same as that preset by the IP hard disk If the node identifiers of the configured available external nodes are the same, it is determined that the external node is an available external node.

An acquisition module 405, configured to acquire an intermediate execution result corresponding to the work identifier when the external node is an available external node, where the intermediate execution result is an intermediate execution result corresponding to the work task;

The result execution module 406 is configured to complete the execution of the work task according to the intermediate execution result, and obtain the final execution result corresponding to the work task;

An output module 407, configured to send the final execution result to the external node.

This embodiment proposes a more detailed IP hard disk on the basis of the embodiment shown in FIG. Correspondence between intermediate execution results and job identifiers. Through this method, after receiving the work task and work ID sent by the external node, the IP hard disk can obtain the intermediate execution result of the work task according to the work ID, so that the IP hard disk can continue to use the first intermediate execution in subsequent operations. result. Even if the IP hard disk is disconnected from other nodes when performing work tasks, the intermediate execution results obtained by the IP hard disk can continue to be used after the IP hard disk establishes a connection with an available external node, so that the intermediate execution results of the IP hard disk can be output to the available external nodes External nodes will not be lost, avoiding the waste of IP hard disk execution result data.

Preferably, the work task can also include an association identifier, which is used to identify other tasks associated with the work task, and the association identifier can be obtained by the IP hard disk from the node that issued the work task, or can be specified by the IP hard disk , is not limited here. Wherein, other tasks associated with the work task include: tasks whose execution condition is the final execution result of the work task. The saving module 402 can also be used to: save the corresponding relationship between the final execution result and the association identifier, so that other tasks associated with the work task can obtain the final execution result according to the association identifier, and take the final execution result as The execution condition is to execute the execution steps included in other tasks associated with the work task.

In order to facilitate understanding of the above embodiment, a specific application scenario of the above embodiment will be taken as an example for description below:

There are multiple IP addresses preset in the IP hard disk, and the nodes corresponding to these IP addresses are external nodes available by default for the IP hard disk.

Node A issues three tasks to the IP hard disk, namely task 1, task 2 and task 3. Among them, task 1 is to disinfect the target file 1, task 2 is to disinfect the target file 2, and task 3 is to compress the sterilized target file 1 and the sterilized target file 2 into a compressed file and output it to the external node .

After receiving task 1, task 2, and task 3, the IP hard disk specifies job IDs for the three tasks as Job1, Job2, and Job3, respectively. Wherein, Job1 is used to identify task 1, Job2 is used to identify task 2, and Job3 is used to identify task 3. Since the three tasks are related, the IP hard disk specifies that the associated identifiers of the three tasks are all JobListOne.

The middle execution module 401 of this IP hard disk executes task 1 and task 2, promptly carries out antivirus to target file 1 and target file 2 respectively, and the target file 1 after the virus removal, the association mark JobListOne of target file 1, target file 2, target The associated identifier JobListOne of file 2 is stored in the dedicated "intermediate execution result storage area" divided by the hard disk.

At this time, the IP hard disk needs to perform task 3. Since the associated identifier JobListOne of task 3 is the same as the associated identifier of task 1 and task 2, the IP hard disk obtains the execution results corresponding to Job1 and Job2 from the "intermediate execution result storage area", that is, the disinfected target file 1 and the disinfected target file2.

The intermediate execution module 401 of the IP hard disk executes task 3, and compresses the target file 1 and the target file 2 through the antivirus into a compressed file, and the preservation module 402 saves the compressed file and the corresponding job identification Job3 in the "intermediate execution result" storage area". At this time, node A is offline, and the IP hard disk cannot output the compressed file.

After 10 minutes, node B establishes a connection with the IP hard disk, and sends task 3 and job ID Job3 to the IP hard disk. The receiving module 403 receives the task 3 and the job ID Job3.

Judging module 404 determines that the IP address of node B is in the IP address preset in the IP hard disk, and then determines that node B is an available external node, and obtaining module 405 obtains the above-mentioned compressed file stored in the "intermediate execution result storage area", The result execution module 406 takes the compressed file as the final execution result of Job3, and the output module 407 outputs the compressed file to Node B.

The IP hard disk in the embodiment of the present invention has been described above from the perspective of unitized functional entities, and the IP hard disk in the embodiment of the present invention is described below from the perspective of hardware processing. Please refer to FIG. 5, the IP hard disk in the embodiment of the present invention Another embodiment of 500 includes:

An input device 501 , an output device 502 , a processor 503 and a memory 504 (the number of processors 503 in the IP hard disk 500 can be one or more, one processor 503 is taken as an example in FIG. 5 ). In some embodiments of the present invention, the input device 501 , the output device 502 , the processor 503 and the memory 504 may be connected through a bus or in other ways, wherein connection through a bus is taken as an example in FIG. 5 .

Wherein, by calling the operation instruction stored in the memory 504, the processor 503 is used to perform the following steps: receiving the work task and the work identification sent by the external node; judging whether the external node is an available external node; when the external node is available When the external node of the work identifier is used, the intermediate execution result corresponding to the work identifier is obtained; the execution of the work task is completed according to the intermediate execution result, and the final execution result corresponding to the work task is obtained; the final execution result is sent to to the external node; execute at least one of the execution steps in the plurality of execution steps to obtain the intermediate execution result; save the corresponding relationship between the work identifier and the intermediate execution result; The node ID is compared with the node ID of the available external node preset in the IP hard disk, and if the node ID of the external node is the same as the node ID of the available external node preset in the IP hard disk, then it is determined that the external node The node is an available external node; save the correspondence between the final execution result and the association identifier, so that other tasks associated with the work task can obtain the final execution result according to the association identifier, and use The final execution result is an execution condition, and the execution steps included in other tasks associated with the work task are executed.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk, and other media that can store program codes.

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still understand the foregoing The technical solutions recorded in each embodiment are modified, or some of the technical features are replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims (6)

1. A kind of IP hard disk task execution method, it is characterized in that, comprising: The network interconnection protocol IP hard disk receives the work task and the work identification sent by the external node, and the work identification is used to identify the work task; The IP hard disk determines whether the external node is an available external node; When the external node is an available external node, the IP hard disk acquires an intermediate execution result corresponding to the work identifier, where the intermediate execution result is an intermediate execution result corresponding to the work task; The IP hard disk completes the execution of the work task according to the intermediate execution result, and obtains the final execution result corresponding to the work task; The IP hard disk sends the final execution result to the external node; The work task includes a plurality of execution steps, and before the IP hard disk receives the work task and the work identification sent by the external node, it also includes: The IP hard disk receives the work task delivered by other nodes, and executes at least one of the execution steps in the plurality of execution steps to obtain the intermediate execution result, and the failure of the other nodes causes the intermediate The execution result cannot be output; The IP hard disk saves the corresponding relationship between the work identifier and the intermediate execution result. 2. IP hard disk task execution method according to claim 1, is characterized in that, described external node has node identification; The judging whether the external node is an available external node includes: Comparing the node identifier of the external node with the node identifier of the available external node preset by the IP hard disk, if the node identifier of the external node is the same as the node identifier of the available external node preset by the IP hard disk , it is determined that the external node is an available external node. 3. The IP hard disk task execution method according to any one of claims 1 to 2, wherein the work task includes an association identifier, and the association identifier is used to identify other tasks associated with the work task ; The method also includes: Save the corresponding relationship between the final execution result and the association identifier, so that other tasks associated with the work task can obtain the final execution result according to the association identifier, and use the final execution result as the execution condition, execute the execution steps included in other tasks associated with the work task. 4. A kind of IP hard disk, is characterized in that, comprises: A receiving module, configured to receive a work task and a work identification sent by an external node, and the work identification is used to identify the work task; A judging module, configured to judge whether the external node is an available external node; An acquisition module, configured to acquire an intermediate execution result corresponding to the work identifier when the external node is an available external node, where the intermediate execution result is an intermediate execution result corresponding to the work task; A result execution module, configured to complete the execution of the work task according to the intermediate execution result, and obtain a final execution result corresponding to the work task; an output module, configured to send the final execution result to the external node; Described working task comprises multiple execution steps, and described IP hard disk also comprises: an intermediate execution module, configured to receive the work task issued by other nodes, execute at least one of the execution steps in the plurality of execution steps, and obtain the intermediate execution result, and the failure of the other nodes causes the intermediate The execution result cannot be output; A saving module, configured to save the corresponding relationship between the job identifier and the intermediate execution result. 5. IP hard disk according to claim 4, is characterized in that, described external node has node identification; The judgment module is specifically used for: Comparing the node identifier of the external node with the node identifier of the available external node preset by the IP hard disk, if the node identifier of the external node is the same as the node identifier of the available external node preset by the IP hard disk , it is determined that the external node is an available external node. 6. The IP hard disk according to any one of claims 4 to 5, wherein the work task includes an association identifier, and the association identifier is used to identify other tasks associated with the work task; The save module is also used to: Save the corresponding relationship between the final execution result and the association identifier, so that other tasks associated with the work task can obtain the final execution result according to the association identifier, and use the final execution result as the execution condition, execute the execution steps included in other tasks associated with the work task.