A task status query method, device and storage medium

Abstract

The present disclosure relates to a method, device and storage medium for querying task status, and relates to the field of computer technology. The embodiments of the present disclosure at least solve the problem of long waiting time for users to query task status in related technologies. The method comprises: in response to the user's operation of performing the task to be queried, sending a task status change message to the server, and obtaining the response time corresponding to the task type of the task to be queried; the task status change message includes the task type of the task to be queried, and the response time is used to reflect the average time of changing the task status of tasks of the same task type as the task to be queried; after the response time has passed, querying the task status of the task to be queried.

Description

Technical Field

[0001] The present disclosure relates to the computer field, and in particular to a task status query method, device and storage medium. Background Art

[0002] When a user checks the task status of a completed task in the terminal's application (APP), the terminal will request the server to return the task status of the task. Since the task status update on the server requires a certain delay, the task status viewed by the user may not be updated. In order to ensure that the user can view the task status updated by the server, the terminal usually presets a maximum delay and queries the task status from the server after this preset maximum delay.

[0003] However, for tasks with relatively small delay requirements, or when the network is not congested and the task status update time on the server is relatively short, the above-mentioned preset maximum delay is still used, which may cause the user to wait for a long time. Summary of the invention

[0004] The present disclosure provides a task status query method, device and storage medium to at least solve the problem of long waiting time for users to query task status in related technologies. The technical solution of the present disclosure is as follows:

[0005] According to a first aspect of an embodiment of the present disclosure, a method for querying a task status is provided, which is applied to a client, and comprises: in response to a user's operation of performing a task to be queried, sending a task status change message to a server, and obtaining a response time corresponding to the task type of the task to be queried; the task status change message comprises the task type of the task to be queried, and the response time is used to reflect the average time for changing the task status of tasks of the same task type as the task to be queried; after the response time has passed, querying the task status of the task to be queried.

[0006] Optionally, the above-mentioned obtaining of the response time corresponding to the task to be queried includes: receiving the response time sent by the server; the response time is determined by the server according to multiple change time corresponding to the task type of the task to be queried within the historical statistical period, and each change time includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed.

[0007] Optionally, the above-mentioned obtaining of the response time corresponding to the task to be queried includes: receiving multiple change time periods within a historical statistical period sent by the server; the multiple change time periods correspond to the task type of the task to be queried, and each change time period includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed; determining the response time based on the multiple change time periods.

[0008] Optionally, determining the response time based on multiple change time periods includes: determining a target change time whose value is within a preset range from the multiple change time periods; and determining an average value of the target change time periods as the response time.

[0009] Optionally, the above-mentioned task status change message also includes the time when the user executes the task to be queried in the client; the task status change message is used to instruct the server to determine the change duration of the task to be queried and store the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client and the time when the server determines that the task to be queried is successfully executed.

[0010] Optionally, after querying the task status of the task to be queried, the method further includes: when it is determined that the task status of the task to be queried is not successfully executed, re-querying the task status of the task to be queried after a preset time period.

[0011] Optionally, the method further includes: when it is determined that the task status of the task to be queried is not successfully executed, and the number of re-queries is greater than or equal to a preset threshold, displaying the task status of the task to be queried as not successfully executed.

[0012] According to a second aspect of an embodiment of the present disclosure, a method for querying a task status is provided, which is applied to a server, and the method includes receiving a task status change message sent by a client; the task status message is generated by the client in response to a user's operation of performing a task to be queried, and the task status change message includes the task type of the task to be queried; based on the task type of the task to be queried, time information corresponding to the task type of the task to be queried is determined, and the time information is sent to the client; the time information is used to indicate that after a response time, the task status of the task to be queried is queried; the response time is used to reflect the average time for changing the task status of tasks of the same task type as the task to be queried.

[0013] Optionally, the above time information includes the response time of the task to be queried; the above-mentioned determining the time information corresponding to the task type of the task to be queried based on the task type of the task to be queried includes: obtaining multiple change durations corresponding to the task type of the task to be queried within the historical statistical period; each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed; based on the multiple change durations, determining the response time of the task to be queried.

[0014] Optionally, determining the response time of the task to be queried based on multiple change time periods includes: determining a target change time whose value is within a preset range from the multiple change time periods; and determining an average value of the target change time periods as the response time.

[0015] Optionally, the above time information includes the task type of the task to be queried, and multiple corresponding change durations within the historical statistical period; each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task execution is successful; the above-mentioned determining the time information corresponding to the task type of the task to be queried based on the task type of the task to be queried includes: according to the task type of the task to be queried, querying the multiple corresponding change durations of the task type of the task to be queried within the historical statistical period.

[0016] Optionally, the task status change message also includes the time when the user executes the task to be queried in the client; the method also includes: determining that the task to be queried has been successfully executed, and determining the time when the server determines that the task to be queried has been successfully executed; determining the change duration of the task to be queried, and storing the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client and the time when the server determines that the task to be queried has been successfully executed.

[0017] Optionally, the above method also includes: determining the statistical period in which the change duration of the task to be queried lies according to the time when the user executes the task to be queried in the client, or the time when the server determines that the task to be queried is successfully executed, and updating the mapping relationship between the statistical period and the change duration based on the change duration of the task to be queried and the determined statistical period.

[0018] According to a third aspect of an embodiment of the present disclosure, a client is provided, comprising a sending unit, an acquiring unit and a querying unit; the sending unit is used to send a task status change message to a server in response to a user's operation of performing a task to be queried; the task status change message includes the task type of the task to be queried; the acquiring unit is used to acquire a response time corresponding to the task type of the task to be queried; the response time is used to reflect the average time for changing the task status of tasks of the same task type as the task to be queried; the querying unit is used to query the task status of the task to be queried after the response time has passed.

[0019] Optionally, the above-mentioned acquisition unit is specifically used to: receive the response duration sent by the server; the response duration is determined by the server according to multiple change durations corresponding to the task type of the task to be queried within the historical statistical period, and each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed.

[0020] Optionally, the above-mentioned acquisition unit is specifically used to: receive multiple change durations within a historical statistical period sent by the server; the multiple change durations correspond to the task type of the task to be queried, and each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed; determine the response duration based on the multiple change durations.

[0021] Optionally, the acquisition unit is specifically used to: determine a target change duration whose value is within a preset range from multiple change durations; and determine an average value of the target change durations as the response duration.

[0022] Optionally, the above-mentioned task status change message also includes the time when the user executes the task to be queried in the client; the task status change message is used to instruct the server to determine the change duration of the task to be queried and store the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client and the time when the server determines that the task to be queried is successfully executed.

[0023] Optionally, the query unit is further configured to, when it is determined that the task status of the task to be queried is not successfully executed, re-query the task status of the task to be queried after a preset period of time.

[0024] Optionally, the client further includes a display unit; the display unit is configured to display the task status of the task to be queried as unsuccessful execution when it is determined that the task status of the task to be queried is unsuccessful execution and the number of re-queries is greater than or equal to a preset threshold.

[0025] According to a fourth aspect of an embodiment of the present disclosure, a server is provided, comprising a receiving unit, a determining unit and a sending unit; the receiving unit is used to receive a task status change message sent by a client; the task status message is generated by the client in response to a user's operation of performing a task to be queried, and the task status change message includes the task type of the task to be queried; the determining unit is used to determine, according to the task type of the task to be queried, the time information corresponding to the task type of the task to be queried; the time information is used to indicate that after a response time, the task status of the task to be queried is queried; the response time is used to reflect the average time for changing the task status of tasks of the same task type as the task to be queried; the sending unit is used to send the time information to the client.

[0026] Optionally, the above-mentioned time information includes the response time of the task to be queried; the above-mentioned determination unit is specifically used to: obtain multiple change durations corresponding to the task type of the task to be queried within the historical statistical period; each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed; determine the response time of the task to be queried based on the multiple change durations.

[0027] Optionally, the above-mentioned determination unit is specifically used to: determine a target change duration whose value is within a preset range from multiple change durations; and determine an average value of the target change durations as the response duration.

[0028] Optionally, the above-mentioned time information includes the task type of the task to be queried and multiple corresponding change durations within the historical statistical period; each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed; the above-mentioned determination unit is specifically used to: according to the task type of the task to be queried, query the multiple corresponding change durations of the task type of the task to be queried within the historical statistical period.

[0029] Optionally, the above-mentioned task status change message also includes the time when the user executes the task to be queried in the client; the above-mentioned server also includes a storage unit; the determination unit is also used to determine that the task to be queried has been successfully executed, and to determine the time when the server determines that the task to be queried has been successfully executed; the determination unit is also used to determine the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client and the time when the server determines that the task to be queried has been successfully executed; the storage unit is used to store the change duration of the task to be queried.

[0030] Optionally, the above-mentioned server also includes an update unit; the determination unit is also used to determine the statistical period in which the change duration of the task to be queried belongs according to the time when the user executes the task to be queried in the client, or the time when the server determines that the task to be queried is successfully executed; the update unit is used to update the mapping relationship between the statistical period and the change duration based on the change duration of the task to be queried and the determined statistical period.

[0031] According to a fifth aspect of an embodiment of the present disclosure, a client is provided, comprising: a processor and a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement the task status query method provided in the first aspect.

[0032] According to the sixth aspect of an embodiment of the present disclosure, a server is provided, comprising: a processor and a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement a task status query method as provided in the second aspect.

[0033] According to the seventh aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When the instructions in the computer-readable storage medium are executed by a processor of a client, the client is enabled to execute a method for querying task status as provided in the first aspect and any possible design thereof.

[0034] According to the eighth aspect of the embodiment of the present disclosure, a computer-readable storage medium is provided. When the instructions in the computer-readable storage medium are executed by the processor of the server, the server can execute the task status query method provided by the second aspect and any possible design method thereof.

[0035] According to the ninth aspect of the embodiments of the present disclosure, a computer program product is provided, which includes computer instructions. When the computer instructions are executed on a server, the server executes a method for querying the task status as provided in the first aspect and any possible design thereof.

[0036] According to the tenth aspect of an embodiment of the present disclosure, a computer program product is provided, which includes computer instructions. When the computer instructions are executed on a server, the server executes a method for querying the task status as provided in the second aspect and any possible design method thereof.

[0037] The technical solution provided by the present disclosure brings at least the following beneficial effects: after the user executes the task to be queried, the client can obtain the response time corresponding to the task type of the task to be queried, and after the response time has passed, query the task status of the task to be queried. Since the response time is used to reflect the average time of changing the task status of tasks of the same task type as the task to be queried, different response times can be obtained for different task types, so that different response delays can be allocated to tasks of each task type, which can further ensure that the user waits for the shortest time while ensuring that the task status in the server has been updated, and at the same time, it can also ensure that the task status obtained by the client is relatively accurate.

[0038] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0040] Figure 1 is a structural diagram of a task query system according to an exemplary embodiment;

[0041] Figure 2 This is one of the flowchart diagrams of a method for querying a task status according to an exemplary embodiment;

[0042] Figure 3 is a second flowchart of a method for querying a task status according to an exemplary embodiment;

[0043] Figure 4 This is a third flow chart of a method for querying a task status according to an exemplary embodiment;

[0044] Figure 5 This is a fourth flowchart of a method for querying a task status according to an exemplary embodiment;

[0045] Figure 6 is a fifth flowchart of a method for querying a task status according to an exemplary embodiment;

[0046] Figure 7 This is a sixth flowchart diagram of a method for querying a task status according to an exemplary embodiment;

[0047] Figure 8 is a seventh flow chart of a method for querying a task status according to an exemplary embodiment;

[0048] Fig. 9 is an eighth flowchart diagram of a method for querying a task status according to an exemplary embodiment;

[0049] Fig.10 is a ninth flowchart of a method for querying a task status according to an exemplary embodiment;

[0050] Fig.11 is a tenth flowchart of a method for querying a task status according to an exemplary embodiment;

[0051] Fig.12 is one of the structural schematic diagrams of a client according to an exemplary embodiment;

[0052] Fig.13 is a structural diagram of a server according to an exemplary embodiment;

[0053] Fig.14 This is a second structural diagram of a client according to an exemplary embodiment. DETAILED DESCRIPTION

[0054] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0055] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0056] In addition, in the description of the embodiments of the present disclosure, unless otherwise specified, " / " means or, for example, A / B can mean A or B. "And / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present disclosure, "multiple" means two or more than two.

[0057] The task status query method provided by the embodiment of the present disclosure may be applicable to a task query system. Figure 1 A structural diagram of the task query system is shown in FIG. Figure 1 As shown, the task query system 10 is used to solve the problem of long waiting time for querying task status in the related art. The task query system 10 includes a server 11 and a server 12. The client 11 is connected to the server 12. The client 11 and the server 12 can be connected in a wired manner or in a wireless manner, which is not limited in the embodiment of the present disclosure.

[0058] The client 11 can be used to exchange data with the server 12. For example, the client 11 can send a task status change message to the server. Accordingly, the client 11 can also receive a response duration or multiple change durations sent by the server 12.

[0059] The client 11 may also execute the method for querying the task status in the embodiment of the present disclosure, for example, after receiving the response time sent by the server 12, query the task status of the task to be queried after the response time has elapsed.

[0060] The server 12 is used to respond to the response time request sent by the client 11, obtain multiple change time periods, and determine the response time period corresponding to the task type of the task to be queried according to the multiple change time periods.

[0061] It should be noted that the server 12 may be a server for executing a task status query method, or a server cluster composed of multiple servers, or a cloud computing service center.

[0062] In practical applications, the task status query method provided by the embodiment of the present invention can be applied to the client or the server. The task status query method provided by the embodiment of the present invention is described below in conjunction with the accompanying drawings.

[0063] like Figure 2 As shown, the method for querying the task status provided by the embodiment of the present disclosure includes the following S201-S203.

[0064] S201. In response to a user's operation of executing a task to be queried, the client sends a task status change message to the server.

[0065] The task status change message includes the task type of the task to be queried. The task status change message is used to indicate that the user has completed the task to be queried in the client.

[0066] As a possible implementation method, after the user completes the task to be queried in the client APP, the client generates a task status change message in response to the user's operation of executing the task to be queried, and sends the task status change message to the server.

[0067] S202: The client obtains the response time corresponding to the task type of the task to be queried.

[0068] The response time is used to reflect the average time it takes to change the task status of tasks of the same task type as the task to be queried.

[0069] As a possible implementation manner, the client may receive the response time corresponding to the task type of the task to be queried sent by the server.

[0070] As another possible implementation manner, the client may also obtain multiple change durations from the server, and determine the response duration of the task type of the task to be queried according to the obtained multiple change durations.

[0071] For example, the task to be queried may be a like task in the APP, a follow task in the APP, or a video of a certain length of time watched in the APP. The user's operation to perform the task to be queried may be to like or follow in the client, or to watch a video of a certain length of time in the APP.

[0072] For the specific implementation of this step, please refer to the subsequent description of the embodiment of the present disclosure, which will not be repeated here.

[0073] S203: After the response time has passed, the client queries the task status of the task to be queried.

[0074] As a possible implementation method, the client starts timing based on the timer therein, and after the timing response time has elapsed, starts sending a query request for the task status to the server.

[0075] The query request includes the identifier of the task to be queried, and the query request is used to request the server to return the task status of the task to be queried.

[0076] Correspondingly, the server queries the task status of the task to be queried from the database of the server according to the identifier of the task to be queried in the query request, and sends the task status of the task to be queried to the client.

[0077] For example, after the client responds to the user's operation on the like task, the response time for obtaining the like task is 2 seconds. After 2 seconds, the client sends a query request to the server to query the task status of the user's like task, and after obtaining the task status of the like task, the client displays the task status of the like task to the user.

[0078] At the same time, while the user is waiting, the client can display a message "loading" to the user to prompt the user to wait.

[0079] The technical solution provided by the above embodiment has at least the following beneficial effects: after the user executes the task to be queried, the client can obtain the response time corresponding to the task type of the task to be queried, and after the response time has passed, query the task status of the task to be queried. Since the response time is used to reflect the average time of changing the task status of tasks of the same task type as the task to be queried, different response times can be obtained for different task types, so that different response delays can be allocated to tasks of each task type, which can further ensure that the user waits for the shortest time while ensuring that the task status in the server has been updated, and at the same time, it can also ensure that the task status obtained by the client is relatively accurate.

[0080] In one design, in order to enable the client to obtain the response time corresponding to the task type of the task to be queried, such as Figure 3 As shown, the query method of task status provided by the implementation example of the present disclosure also includes the following S301-S303.

[0081] S301. The client sends a task status change message to the server.

[0082] The task status change message includes the task type of the task to be queried.

[0083] As a possible implementation method, after receiving the user's operation of the task to be queried, the client sends a task status change message to the server.

[0084] The specific implementation method of this step is the same as the specific implementation method of the above S201.

[0085] Correspondingly, the server receives the task status change message sent by the client.

[0086] It should be noted that a consumer device is provided in the server to monitor received messages.

[0087] S302: The server determines the time information corresponding to the task type of the task to be queried according to the task type of the task to be queried.

[0088] As a possible implementation manner, the server queries a database of the server for multiple change durations corresponding to the task type of the task to be queried according to the task type of the task to be queried in the task status change message to determine the time information.

[0089] It should be noted that the time information of tasks of each task type in different statistical periods is pre-stored in the database of the server.

[0090] The implementation method of this step can be specifically referred to the subsequent description of the embodiment of the present disclosure, and will not be repeated here.

[0091] S303: The server sends time information to the client.

[0092] Accordingly, the client receives the time information sent by the service to determine the response time corresponding to the task type of the task to be queried.

[0093] Since the above time information can be multiple change durations or response durations, the specific implementation methods of the above steps S301-S303 in different situations can refer to the subsequent description of the embodiments of the present disclosure and will not be repeated here.

[0094] The technical solution provided by the above embodiment has at least the following beneficial effects: after receiving the task status change message sent by the client, the server returns the time information to the client. Since the time information is used to indicate the task status of the task to be queried after the response time, and the response time is used to reflect the average time for changing the task status of tasks of the same task type as the task to be queried, different response times can be obtained for different task types, so that different response delays can be allocated to tasks of each task type, which can further ensure that the user waits for the shortest time while ensuring that the task status in the server has been updated, and at the same time, it can also ensure that the task status obtained by the client is relatively accurate.

[0095] In one design, the time information is the response time corresponding to the task type of the task to be queried. In order to enable the client to obtain the response time corresponding to the task type of the task to be queried, Figure 4 As shown, the above query method in the embodiment of the present disclosure may also include the following S401-S404.

[0096] S401. The client sends a task status change message to the server.

[0097] The specific implementation method of this step can refer to S201 or S301 mentioned above in the embodiment of the present disclosure, and will not be repeated here.

[0098] Correspondingly, the server receives the task status change message sent by the client.

[0099] S402: The server obtains multiple change durations corresponding to the task type of the task to be queried within a historical statistical period.

[0100] Each change duration includes the time interval between a first moment when the user completes the task in the client and a second moment when the server determines that the task is successfully executed.

[0101] As a possible implementation manner, the server queries a database of the server for multiple change durations corresponding to the task type in a historical statistical period corresponding to the task type of the task to be queried according to the task type of the task to be queried.

[0102] It should be noted that for any task type, the server database includes statistical data of multiple statistical periods corresponding to the task type. Each statistical period in the multiple statistical periods is counted according to the time when the task is successfully executed. Each statistical data includes multiple change durations corresponding to the task type.

[0103] The specific implementation methods of changing the duration corresponding to each task type are stored in the database of the server. Please refer to the subsequent description of the implementation example of the present disclosure, and will not be repeated here.

[0104] In one case, the above historical statistical period may be the previous statistical period of the current moment.

[0105] It is understandable that, since the resource pressure of the server in the previous statistical period is quite self-similar to the resource pressure at the current moment, using multiple change durations in the previous statistical period can make the determined response duration more accurate.

[0106] S403: The server determines a response duration according to multiple change durations.

[0107] As a possible implementation method, the server may determine an average value of multiple change durations as the response duration.

[0108] It should be noted that the steps provided in the above S402-S403 may be a specific implementation method of the above S302 in the embodiment of the present disclosure.

[0109] Since the change durations corresponding to tasks at different times may be different, in order to eliminate the differences between different change durations and make the response duration more accurate, another possible implementation method is as follows: Figure 5 As shown, S403 provided in the embodiment of the present disclosure may also include the following S4031-S4032.

[0110] S4031. The server determines a target change duration whose value is within a preset range from multiple change durations.

[0111] As a possible implementation manner, the server may determine the target change duration from multiple change durations according to a preset range.

[0112] The above preset range can be set in advance by the operation and maintenance personnel in the server, and can also be determined by the server.

[0113] A specific example of determining a target change duration by the server is shown below.

[0114] The server sorts the multiple change durations according to the length of time, removes 0.25% of the data at the beginning and end of the sorting result, and determines the remaining 99.5% of the change duration as the target change duration.

[0115] It can be understood that, in the above example, the maximum value and the minimum value of the preset range correspond to 0.25% of the values ​​at the beginning and the end of the sorting result, respectively.

[0116] S4032. The server determines the average value of the target change duration as the response duration.

[0117] The technical solution provided by the above embodiment has at least the following beneficial effects: determining a target change duration within a preset range from multiple change durations can eliminate data with obvious individual differences from the data set, thereby ensuring that the calculated response duration is more accurate.

[0118] It should be noted that the steps performed by the server in the above S402-S403 can also be used as the specific implementation method of the above S302.

[0119] S404: The server sends a response to the client.

[0120] Correspondingly, the client receives the response time sent by the server.

[0121] Among them, the response duration is determined by the server based on multiple change durations corresponding to the task type of the task to be queried within the historical statistical period. Each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed.

[0122] The technical solution provided by the above embodiment has at least the following beneficial effects: the server obtains multiple change durations, and determines the response duration of the task to be queried based on the obtained multiple change durations, so as to send the response duration to the client, providing a specific implementation method for obtaining the response duration of the task to be queried.

[0123] In one design, the time information is the task type of the task to be queried, and the corresponding multiple change durations in the historical statistical period. In order to enable the client to obtain the change duration corresponding to the task type of the task to be queried, such as Figure 6 As shown, the query method provided by the embodiment of the present disclosure may further include the following S501-S504.

[0124] S501. The client sends a task status change message to the server.

[0125] The specific implementation method of this step can refer to the specific implementation methods of S201 and S301 mentioned above in the embodiment of the present disclosure, and will not be repeated here.

[0126] Correspondingly, the server receives the task status change message sent by the client.

[0127] S502: The server queries, according to the task type of the task to be queried, a plurality of change durations corresponding to the task type of the task to be queried within a historical statistical period.

[0128] The implementation method of this step can refer to the specific description in S402 above in the embodiment of the present disclosure, and will not be repeated here.

[0129] It should be noted that, in some embodiments, this step can also be used as a specific implementation method of the above S302 of the present disclosure.

[0130] S503: The server sends to the client a plurality of change durations corresponding to the task type of the task to be queried within a historical statistical period.

[0131] In some embodiments, this step can also serve as a specific implementation method of the above S303 of the present disclosure.

[0132] Correspondingly, the client receives multiple change durations corresponding to the task type of the task to be queried within the historical statistical period sent by the server.

[0133] S504: The client determines a response duration according to multiple change durations.

[0134] The specific implementation of this step can refer to the specific implementation of S403 in the embodiment of the present disclosure, and will not be repeated here. The difference is that the execution subject in S504 is different from that in S403.

[0135] The technical solution provided by the above embodiment has at least the following beneficial effects: the client can receive multiple change durations sent by the server, and determine the response duration based on the received multiple change durations, providing another implementation method for obtaining the response duration of the task to be queried.

[0136] In one design, Figure 7 As shown, S504 provided in the embodiment of the present disclosure may specifically include the following S5041-S5042:

[0137] S5041. The client determines a target change duration whose value is within a preset range from multiple change durations.

[0138] The specific implementation and corresponding examples of this step can refer to the specific description and examples in S4031 of the embodiment of the present disclosure, and will not be repeated here. The difference lies in the different execution entities.

[0139] S5042. The server determines the average value of the target change duration as the response duration.

[0140] The specific implementation method and corresponding examples of this step can refer to the specific description and examples in S4032 of the embodiment of the present disclosure, and will not be repeated here. The difference lies in the different execution entities.

[0141] The technical solution provided by the above embodiment has at least the following beneficial effects: determining a target change duration within a preset range from multiple change durations can eliminate data with obvious individual differences from the data set, thereby ensuring that the calculated response duration is more accurate.

[0142] In one design, in order to ensure that the client can query the updated task status, such as Figure 8 As shown, the method for querying the task status provided by the embodiment of the present disclosure also includes the following S601-S603.

[0143] S601. After querying the task status of the task to be queried, the client receives the task status of the task to be queried sent by the server.

[0144] It is understandable that the task status sent by the server can be either successfully executed or not successfully executed.

[0145] S602: When it is determined that the task status of the task to be queried is not successfully executed, the client re-queries the task status of the task to be queried after a preset time period.

[0146] It should be noted that the preset duration can be pre-set by the operation and maintenance personnel in the client or the client's APP.

[0147] Exemplarily, the preset duration may be 1 second.

[0148] S603: When it is determined that the task status of the task to be queried is successfully executed, the client displays the task status of the task to be queried as successfully executed.

[0149] Exemplarily, when the client displays a task list to the user, the button of the task to be queried in the task list is set to be inoperable, such as gray, or displays the word "completed" or the like.

[0150] It should be noted that the above S601 may be directly placed after S203, or may be repeatedly executed after S602.

[0151] The technical solution provided by the above embodiment has at least the following beneficial effects: when a query once determines that the task status is not successfully executed, in order to eliminate errors caused by inadequate response time calculation, re-querying after a preset time can correspondingly improve the accuracy of the acquired task status.

[0152] In one design, after the client repeatedly queries the task status of the task to be queried, Figure 8 ,like Fig. 9 As shown, the method for querying the task status provided by the embodiment of the present disclosure further includes the following S604 after S601.

[0153] S604: When it is determined that the task status of the task to be queried is not successfully executed, and the number of re-queries is greater than or equal to a preset threshold, the client displays the task status of the task to be queried as not successfully executed.

[0154] As a possible implementation method, when it is determined that the task status of the task to be queried is not successfully executed, the client obtains the number of re-queries, and when the number of queries is greater than or equal to a preset threshold, displays the task status of the task to be queried as not successfully executed.

[0155] It should be noted that the above preset threshold can be set in advance by the operation and maintenance personnel in the client or the client's APP.

[0156] Exemplarily, the preset threshold may be 3. That is, after the client requeries 3 times at an interval of 1 second, if the queried task status is still unsuccessful, the task is displayed to the user as unsuccessful.

[0157] When the above example is displayed to the user in the task list, the operation button of the task to be queried may be in an operable state, or display an unfinished prompt message.

[0158] In some embodiments, S604 involved in the embodiments of the present disclosure may also be executed after S602.

[0159] The technical solution provided by the above embodiment has at least the following beneficial effects: after multiple queries, if it is determined that the task status of the task to be queried is still in the unsuccessful execution state, it indicates that the task is indeed unsuccessful execution, just like the user shows that the task is unsuccessful execution. In this way, continuous queries caused by the task status being unsuccessful execution can be avoided, and the user's time is not wasted.

[0160] In one design, in order to enable the server to store the change duration corresponding to each task type, such as Fig.10 As shown, the method for querying the task status provided by the embodiment of the present disclosure also includes the following S701-S705.

[0161] S701: The server receives a task status change message sent by the client.

[0162] Among them, the task status change message also includes the time when the user executes the task to be queried in the client; the task status change message is used to instruct the server to determine the change duration of the task to be queried and store the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client and the time when the server determines that the task to be queried is successfully executed.

[0163] As a possible implementation, after the user completes the task to be queried, the client obtains the time when the user executes the task to be queried, and generates a task status change message according to the obtained time. Further, the client sends the task status message to the server. Correspondingly, the server receives the task status change message.

[0164] Exemplarily, taking the like task as an example, when the user opens a preset multimedia resource and clicks the like button, the client obtains the time when the user clicks the like button and the task type of the like task, and generates a task status change message.

[0165] In some embodiments, the task status change message includes information such as the identifier of the task to be queried, the identifier of the user, and the task type of the preset task.

[0166] S702: The server determines that the task to be queried has been executed successfully.

[0167] As a possible implementation, after receiving the task status change message, the server loads the task status change message into the message queue in the server. Further, after the message consumption service in the server reads the task status change message from the message queue in a preset reading order, it determines whether the task to be queried is executed successfully.

[0168] It should be noted that the message queue can contain multiple messages that need to be processed at the same time. The message consumption service reads the messages from the message queue one by one in chronological order and processes them accordingly.

[0169] S703: The server determines the time when the server determines that the task to be queried has been successfully executed.

[0170] As a possible implementation manner, the server determines the moment when the message consumption service determines that the task to be queried has been successfully executed.

[0171] S704: The server determines the change duration of the task to be queried.

[0172] The change duration of the task to be queried includes the time interval between the moment when the user executes the task to be queried in the client and the moment when the server determines that the task to be queried is successfully executed.

[0173] As a possible implementation manner, the server determines the difference between the time when the server determines that the task to be queried has been successfully executed and the time when the user executes the task to be queried, and determines it as the change duration corresponding to the task type of the task to be queried.

[0174] Exemplarily, the time when the user executes the task to be queried is t1, and the time when the server determines that the task to be queried has been successfully executed is t2, then the change duration of the task to be queried is t2-t1.

[0175] It is understandable that the change duration corresponding to the task type of a task may include the transmission delay of the task change message of the task, the queuing time of the message in the message queue of the server, and the processing time of the message consumption service of the server. When the resource pressure on the server increases, the queuing time in the change duration will also increase accordingly.

[0176] S705: The server stores the changed duration of the task to be queried.

[0177] As a possible implementation manner, the server stores the change duration of the task to be queried in the statistical data of the statistical period corresponding to the task type of the task to be queried.

[0178] The technical solution provided by the above embodiment has at least the following beneficial effects: the server can obtain the first moment and the second moment of the task to be queried, determine that the difference between the second moment and the first moment is the change duration corresponding to the task type of the pre-task, and store the change duration corresponding to the task type, which can ensure that the subsequent client or server can determine the response duration based on the change duration.

[0179] In one design, in order to facilitate querying the statistical data of any statistical period, such as Fig.11 As shown, the method for querying the task status provided by the embodiment of the present disclosure also includes the following S801-S802.

[0180] S801. The server determines the statistical period in which the change duration of the task to be queried lies according to the time when the user executes the task to be queried in the client, or the time when the server determines that the task to be queried is successfully executed.

[0181] For example, taking the statistical period of 1 minute as an example, if the time when the user executes the task to be queried in the client is 12 minutes and 32 seconds, and the time when the server determines that the task to be queried is successfully executed is 12 minutes and 34 seconds, then the change duration of the task to be queried is 2 seconds, and the change duration of the task to be queried is within the statistical period corresponding to 12 minutes.

[0182] S802: The server updates the mapping relationship between the statistical period and the change duration based on the change duration of the task to be queried and the determined statistical period.

[0183] As a possible implementation manner, the server maps the change duration of the task type of the task to be queried with the determined statistical period, and updates the mapping result to the above mapping relationship.

[0184] It is understandable that the above mapping relationship also includes the task type corresponding to the statistical period and the statistical data within the statistical period. When the server queries the multiple change durations corresponding to the task type in the historical period, the previous statistical period at the current moment can be directly determined, and the statistical data corresponding to the previous statistical period can be obtained, which is the above multiple change durations.

[0185] Exemplarily, the server receives the duration request sent by the client at 13 minutes and 11 seconds, and then obtains statistical data of the task type of the task to be queried within a statistical period of 12 minutes as multiple change durations corresponding to the task type of the task to be queried.

[0186] The technical solution provided by the above embodiment has at least the following beneficial effects: mapping the change duration of the task with different statistical periods can make it more convenient and faster to query the statistical data.

[0187] Fig.12FIG. 1 is a schematic diagram showing a structure of a client according to an exemplary embodiment. Fig.12 As shown, the client 90 provided in the embodiment of the present disclosure includes a sending unit 901 , an acquiring unit 902 and a querying unit 903 .

[0188] The sending unit 901 is used to send a task status change message to the server in response to the user's operation of performing the task to be queried; the task status change message includes the task type of the task to be queried; for example, Figure 2 As shown, the sending unit 901 can be used to execute S201.

[0189] The acquisition unit 902 is used to obtain the response time corresponding to the task type of the task to be queried; the response time is used to reflect the average time for changing the task status of the task of the same task type as the task to be queried; for example, Figure 2 As shown, the acquisition unit 902 can be used to execute S202.

[0190] The query unit 903 is used to query the task status of the task to be queried after the response time has passed. Figure 2 As shown, the query unit 903 can be used to execute S203.

[0191] Optional, such as Fig.12 As shown, the acquisition unit 902 provided in the embodiment of the present disclosure is specifically used for:

[0192] Receive the response duration sent by the server; the response duration is determined by the server according to the multiple change durations corresponding to the task type of the task to be queried in the historical statistical period, and each change duration includes the time interval between the first moment when the user executes the task in the client 90 and the second moment when the server determines that the task is successfully executed. Figure 4 As shown, the acquisition unit 902 can be used to execute S404.

[0193] Optional, such as Fig.12 As shown, the acquisition unit 902 provided in the embodiment of the present disclosure is specifically used for:

[0194] Receive multiple change durations within a historical statistical period sent by the server; the multiple change durations correspond to the task type of the task to be queried, and each change duration includes the time interval between the first moment when the user executes the task in the client 90 and the second moment when the server determines that the task is successfully executed; for example, Figure 6 As shown, the acquisition unit 902 can be used to execute S503.

[0195] Determine the response time based on multiple change durations. Figure 6 As shown, the acquisition unit 902 can be used to execute S504.

[0196] Optional, such as Fig.12 As shown, the acquisition unit 902 provided in the embodiment of the present disclosure is specifically used for:

[0197] Determine a target change duration whose value is within a preset range from multiple change durations; for example, Figure 7 As shown, the acquisition unit 902 can be used to execute S5041.

[0198] The average of the target change duration is determined as the response duration. Figure 7 As shown, the acquisition unit 902 can be used to execute S5042.

[0199] Optional, such as Fig.12 As shown, in the client 90 provided by the embodiment of the present disclosure, the task status change message also includes the time when the user executes the task to be queried in the client 90; the task status change message is used to instruct the server to determine the change duration of the task to be queried, and store the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client 90 and the time when the server determines that the task to be queried is successfully executed.

[0200] Optional, such as Fig.12 As shown, the query unit 903 provided in the embodiment of the present disclosure is also used to re-query the task status of the task to be queried after a preset time period when it is determined that the task status of the task to be queried is not successfully executed. Figure 8 As shown, the query unit 903 can be used to execute S602.

[0201] Optional, such as Fig.12 As shown, the client 90 provided in the embodiment of the present disclosure further includes a display unit 904 .

[0202] The display unit 904 is used to display the task status of the task to be queried as unsuccessful execution when it is determined that the task status of the task to be queried is unsuccessful and the number of re-queries is greater than or equal to a preset threshold. Figure 8 As shown, the display unit 904 can be used to execute S603.

[0203] In addition, the present disclosure also provides a server for executing the query method of the task status executed by the server provided in the embodiment of the present disclosure, referring to Fig.13 As shown, the server 100 includes a receiving unit 1001 , a determining unit 1002 and a sending unit 1003 .

[0204] The receiving unit 1001 is used to receive a task status change message sent by a client; the task status message is generated by the client in response to the user's operation of performing the task to be queried, and the task status change message includes the task type of the task to be queried; for example, Figure 3 As shown, the receiving unit 1001 can be used to execute S301.

[0205] The determination unit 1002 is used to determine the time information corresponding to the task type of the task to be queried according to the task type of the task to be queried; the time information is used to indicate that after the response time, the task status of the task to be queried is queried; the response time is used to reflect the average time for tasks of the same task type as the task to be queried to change the task status; for example, Figure 3 As shown, the determining unit 1002 can be used to execute S302.

[0206] The sending unit 1003 is used to send time information to the client. Figure 3 As shown, the sending unit 1003 can be used to execute S303.

[0207] Optional, such as Fig.13 As shown, the time information provided by the embodiment of the present disclosure includes the response time of the task to be queried; the determination unit 1002 is specifically used to:

[0208] Obtain multiple change durations corresponding to the task type of the task to be queried within the historical statistical period; each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server 100 determines that the task is successfully executed; for example, Figure 4 As shown, the determining unit 1002 can be used to execute S402.

[0209] Determine the response time of the task to be queried based on multiple change times. Figure 4 As shown, the determining unit 1002 can be used to execute S403.

[0210] Optional, such as Fig.13 As shown, the determining unit 1002 provided in the embodiment of the present disclosure is specifically used for:

[0211] Determine a target change duration whose value is within a preset range from multiple change durations; for example, Figure 5 As shown, the determining unit 1002 can be used to execute S4031.

[0212] The average of the target change duration is determined as the response duration. Figure 5 As shown, the determining unit 1002 can be used to execute S4032.

[0213] Optional, such as Fig.13As shown, the time information provided by the embodiment of the present disclosure includes the task type of the task to be queried and multiple corresponding change durations within the historical statistical period; each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server 100 determines that the task is successfully executed.

[0214] The determining unit 1002 is specifically configured to:

[0215] According to the task type of the task to be queried, query the multiple change durations corresponding to the task type of the task to be queried in the historical statistical period. For example, Figure 7 As shown, the determining unit 1002 can be used to execute S502.

[0216] Optional, such as Fig.13 As shown, the task status change message provided by the embodiment of the present disclosure also includes the time when the user executes the task to be queried in the client; the server 100 also includes a storage unit 1004.

[0217] The determination unit 1002 is further configured to determine whether the task to be queried has been successfully executed, and to determine the time at which the server 100 determines that the task to be queried has been successfully executed; for example, Fig.10 As shown, the determining unit 1002 can be used to execute S702-S703.

[0218] The determination unit 1002 is further used to determine the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client and the time when the server 100 determines that the task to be queried is successfully executed; for example, Fig.10 As shown, the determining unit 1002 can be used to execute S704.

[0219] The storage unit 1004 is used to store the change duration of the task to be queried. Fig.10 As shown, the storage unit 1004 can be used to execute S705.

[0220] Optional, such as Fig.13 As shown, the server 100 provided in the embodiment of the present disclosure also includes an updating unit 1005 .

[0221] The determination unit 1002 is further used to determine the statistical period in which the change duration of the task to be queried is located according to the time when the user executes the task to be queried in the client, or the time when the server 100 determines that the task to be queried is successfully executed; for example, Fig.11 As shown, the determining unit 1002 can be used to execute S801.

[0222] The updating unit 1005 is used to update the mapping relationship between the statistical period and the change duration based on the change duration of the task to be queried and the determined statistical period. Fig.11 As shown, the determining unit 1002 can be used to execute S802.

[0223] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0224] Fig.14 Schematic diagram of the structure of a client provided by the present disclosure. Fig.14 The client 110 may include a processor 1101 and a memory 1103 for storing processor executable instructions. The processor 1101 is configured to execute instructions in the memory 1103 to implement the task status query method in the above embodiment.

[0225] In addition, the client 110 may further include a communication bus 1102 and a communication interface 1104 .

[0226] The processor 1101 may be a central processing unit (CPU), a microprocessing unit, an ASIC, or one or more integrated circuits for controlling the execution of the program of the disclosed solution.

[0227] The communication bus 1102 may include a pathway for transmitting information between the above-mentioned components.

[0228] The communication interface 1104 uses any transceiver or other device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0229] The memory 1103 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processing unit through a bus. The memory may also be integrated with the processing unit.

[0230] The memory 1103 is used to store instructions for executing the solution of the present disclosure, and the execution is controlled by the processor 1101. The processor 1101 is used to execute the instructions stored in the memory 1103, thereby realizing the functions in the method of the present disclosure.

[0231] As an example, combining Fig.11 The functions implemented by the sending unit 901, the obtaining unit 902, the query unit 903 and the display unit 904 in the client 90 are similar to those Fig.14 The function of processor 1101 in is the same.

[0232] In a specific implementation, as an embodiment, the processor 1101 may include one or more CPUs, such as Fig.14 CPU0 and CPU1 in.

[0233] In a specific implementation, as an embodiment, the client 110 may include multiple processors, such as Fig.14 1 and 1107. Each of these processors may be a single-CPU processor or a multi-CPU processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0234] In a specific implementation, as an embodiment, the client 110 may further include an output device 1105 and an input device 1106. The output device 1105 communicates with the processor 1101 and may display information in a variety of ways. For example, the output device 1105 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 1106 communicates with the processor 1101 and may receive user input in a variety of ways. For example, the input device 1106 may be a mouse, a keyboard, a touch screen device, or a sensor device.

[0235] Those skilled in the art will understand that Fig.14 The structure shown in the figure does not constitute a limitation on the client 110, and the client 110 may include more or less components than those shown in the figure, or combine some components, or adopt a different component arrangement.

[0236] At the same time, the structural diagram of another hardware of the server provided by the present disclosure can also refer to the above Fig.14 The description of the client 90 in the embodiment will not be repeated here. The difference is that the processor included in the server is used to execute the steps performed by the server in the above embodiment.

[0237] In addition, the present disclosure also provides a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by a processor of a client, the client can execute the task status query method provided in the above embodiment.

[0238] In addition, the present disclosure also provides a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by a processor of the server, the server can execute the task status query method provided in the above embodiment.

[0239] In addition, the present disclosure also provides a computer program product, including computer instructions. When the computer instructions are executed on a client, the client executes the task status query method provided in the above embodiment.

[0240] In addition, the present disclosure also provides a computer program product, including computer instructions. When the computer instructions are executed on a server, the server executes the task status query method provided in the above embodiment.

[0241] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims.

Claims

1. A task status query method, applied to a client, characterized in that: include: In response to the user's operation of executing the task to be queried, a task status change message is sent to the server, and the response time corresponding to the task type of the task to be queried is obtained; The task status change message includes the task type of the task to be queried, and the response duration is used to reflect the average duration of changing the task status of tasks of the same task type as the task to be queried; the response duration is determined according to a plurality of change durations corresponding to the task type of the task to be queried within a historical statistical period, and each change duration includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed; After the response time has elapsed, the task status of the task to be queried is queried.

2. The method for querying task status according to claim 1, characterized in that: The obtaining the response time corresponding to the task to be queried includes: Receive the response duration sent by the server.

3. The method for querying task status according to claim 1, characterized in that: The obtaining the response time corresponding to the task to be queried includes: Receiving the multiple change durations sent by the server; The response duration is determined according to the multiple change durations.

4. The method for querying task status according to claim 3, characterized in that: The step of determining the response duration according to the multiple change durations includes: Determine a target change duration whose value is within a preset range from the multiple change durations; An average value of the target change durations is determined as the response duration.

5. The method for querying task status according to claim 1, characterized in that: The task status change message also includes the time when the user executes the task to be queried in the client; the task status change message is used to instruct the server to determine the change duration of the task to be queried and store the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client and the time when the server determines that the task to be queried is successfully executed.

6. The method for querying task status according to any one of claims 1 to 5, characterized in that: After querying the task status of the task to be queried, the method further includes: When it is determined that the task status of the task to be queried is not successfully executed, the task status of the task to be queried is requeried after a preset time period.

7. The method for querying task status according to claim 6, characterized in that: The method further comprises: When it is determined that the task status of the task to be queried is not successfully executed, and the number of re-queries is greater than or equal to a preset threshold, the task status of the task to be queried is displayed as not successfully executed.

8. A task status query method, applied to a server, characterized in that: include: Receive task status change messages sent by the client; The task status message is generated by the client in response to the user's operation of performing the task to be queried, and the task status change message includes the task type of the task to be queried; According to the task type of the task to be queried, the time information corresponding to the task type of the task to be queried is determined, and the time information is sent to the client; the time information is used to indicate that after the response time, the task status of the task to be queried is queried; the response time is used to reflect the average time duration for changing the task status of tasks of the same task type as the task to be queried; the response time is determined according to multiple change times corresponding to the task type of the task to be queried within a historical statistical period, each change time duration including the time interval between a first moment when the user executes the task in the client and a second moment when the server determines that the task is successfully executed.

9. The method for querying task status according to claim 8, characterized in that: The time information includes the response time of the task to be queried; and determining the time information corresponding to the task type of the task to be queried according to the task type of the task to be queried includes: Obtaining the multiple change durations; The response duration of the task to be queried is determined according to the multiple change durations.

10. The method for querying task status according to claim 9, characterized in that: The step of determining the response duration of the task to be queried according to the multiple change durations includes: Determine a target change duration whose value is within a preset range from the multiple change durations; An average value of the target change durations is determined as the response duration.

11. The method for querying task status according to claim 8, characterized in that: The time information includes the multiple change durations; The determining, according to the task type of the task to be queried, time information corresponding to the task type of the task to be queried includes: The multiple change durations are queried according to the task type of the task to be queried.

12. The method for querying task status according to any one of claims 8 to 11, characterized in that: The task status change message also includes the time when the user executes the task to be queried in the client; the method also includes: Determining that the task to be queried has been successfully executed, and determining the time when the server determines that the task to be queried has been successfully executed; Determine the change duration of the task to be queried and store the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the moment when the user executes the task to be queried in the client and the moment when the server determines that the task to be queried is successfully executed.

13. The method for querying task status according to claim 12, characterized in that: The method further comprises: According to the time when the user executes the task to be queried in the client, or the time when the server determines that the task to be queried is successfully executed, the statistical period in which the change duration of the task to be queried lies is determined, and based on the change duration of the task to be queried and the determined statistical period, the mapping relationship between the statistical period and the change duration is updated.

14. A client, characterized in that: It includes a sending unit, an acquiring unit and a querying unit; The sending unit is used to send a task status change message to the server in response to the user's operation of performing the task to be queried; the task status change message includes the task type of the task to be queried; The acquisition unit is used to acquire the response time corresponding to the task type of the task to be queried; the response time is used to reflect the average time for changing the task status of tasks of the same task type as the task to be queried; the response time is determined according to a plurality of change times corresponding to the task type of the task to be queried within a historical statistical period, each change time including the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed; The query unit is used to query the task status of the task to be queried after the response time has passed.

15. The client according to claim 14, characterized in that: The acquisition unit is specifically used for: Receive the response duration sent by the server.

16. The client according to claim 14, characterized in that: The acquisition unit is specifically used for: Receive the multiple change durations; and determine the response duration based on the multiple change durations.

17. The client according to claim 16, characterized in that: The acquisition unit is specifically used for: Determine a target change duration whose value is within a preset range from the multiple change durations; An average value of the target change durations is determined as the response duration.

18. The client according to claim 14, characterized in that: The task status change message also includes the time when the user executes the task to be queried in the client; the task status change message is used to instruct the server to determine the change duration of the task to be queried and store the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the time when the user executes the task to be queried in the client and the time when the server determines that the task to be queried is successfully executed.

19. The client according to any one of claims 14 to 18, characterized in that: The query unit is further configured to, when it is determined that the task status of the task to be queried is not successfully executed, re-query the task status of the task to be queried after a preset time period.

20. The client according to claim 19, characterized in that: The client also includes a display unit; The display unit is used to display the task status of the task to be queried as unsuccessful execution when it is determined that the task status of the task to be queried is unsuccessful execution and the number of re-queries is greater than or equal to a preset threshold.

21. A server, characterized in that: It includes a receiving unit, a determining unit and a sending unit; The receiving unit is used to receive a task status change message sent by a client; the task status message is generated by the client in response to a user's operation of performing a task to be queried, and the task status change message includes a task type of the task to be queried; The determining unit is used to determine the time information corresponding to the task type of the task to be queried according to the task type of the task to be queried; the time information is used to indicate that after the response time, the task status of the task to be queried is queried; the response time is used to reflect the average time for changing the task status of tasks of the same task type as the task to be queried; the response time is determined according to multiple change times corresponding to the task type of the task to be queried within a historical statistical period, each change time includes the time interval between the first moment when the user executes the task in the client and the second moment when the server determines that the task is successfully executed; The sending unit is used to send the time information to the client.

22. The server according to claim 21, characterized in that: The time information includes the response time of the task to be queried; the determination unit is specifically used to: Acquire the multiple change durations; and determine the response duration of the task to be queried based on the multiple change durations.

23. The server according to claim 22, characterized in that: The determining unit is specifically configured to: Determine a target change duration whose value is within a preset range from the multiple change durations; An average value of the target change durations is determined as the response duration.

24. The server according to claim 21, characterized in that: The time information includes the multiple change durations; The determining unit is specifically configured to: The multiple change durations are queried according to the task type of the task to be queried.

25. The server according to any one of claims 21-24, characterized in that: The task status change message also includes the time when the user executes the task to be queried in the client; the server also includes a storage unit; The determining unit is further used to determine whether the task to be queried has been successfully executed, and to determine the time when the server determines that the task to be queried has been successfully executed; The determining unit is further used to determine the change duration of the task to be queried; the change duration of the task to be queried includes the time interval between the moment when the user executes the task to be queried in the client and the moment when the server determines that the task to be queried is successfully executed; The storage unit is used to store the change duration of the task to be queried.

26. The server according to claim 25, characterized in that: The server also includes an updating unit; The determining unit is further used to determine the statistical period in which the change duration of the task to be queried belongs according to the time when the user executes the task to be queried in the client, or the time when the server determines that the task to be queried is successfully executed; The updating unit is used to update the mapping relationship between the statistical period and the change duration based on the change duration of the task to be queried and the determined statistical period.

27. A client, characterized in that: include: A processor and a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement the task status query method according to any one of claims 1 to 7.

28. A server, characterized in that: include: A processor and a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement the task status query method as described in any one of claims 8-13.

29. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by the processor of the client, the client is enabled to execute the method for querying the task status as described in any one of claims 1-7; or, when the instructions in the computer-readable storage medium are executed by the processor of the server, the server is enabled to execute the method for querying the task status as described in any one of claims 8-13.

30. A computer program product comprising instructions, characterized in that The computer program product includes computer instructions, which, when executed on a client, cause the client to execute a method for querying the task status as described in any one of claims 1 to 7; or, when executed on a server, cause the server to execute a method for querying the task status as described in any one of claims 8 to 13.

Images