CN113886432A

CN113886432A - Task state query method, equipment and storage medium

Info

Publication number: CN113886432A
Application number: CN202111166826.1A
Authority: CN
Inventors: 马宏智; 顾佳怡
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2022-01-04

Abstract

The disclosure relates to a task state query method, a task state query device and a storage medium, and relates to the technical field of computers. The embodiment of the disclosure at least solves the problem of long waiting time of the user query task state in the related technology. The method comprises the following steps: responding to the operation of executing the task to be inquired by the user, sending a task state change message to the server, and acquiring a response time length corresponding to the task type of the task to be inquired; the task state change message comprises the task type of the task to be inquired, the response time length is used for reflecting the task of the same task type as the task to be inquired, and the average time length of the task state is changed; and after the response time length, inquiring the task state of the task to be inquired.

Description

Task state query method, equipment and storage medium

Technical Field

The present disclosure relates to the field of computers, and in particular, to a method, an apparatus, and a storage medium for querying a task state.

Background

When a user checks a task state of a task executed in an Application (APP) of a terminal, the terminal requests a server to return the task state of the task. Due to the fact that a certain time delay is needed for updating the task state in the server, the task state which is viewed by the user may be an un-updated state. In order to ensure that the user can check the updated task state of the server, the terminal usually presets a maximum time delay, and after the preset maximum time delay, the task state is inquired from the server.

However, for a task with a smaller delay requirement, or under the condition that the network is not congested, the update duration of the task state of the server is shorter, and still adopting the preset maximum delay may cause the user to wait longer.

Disclosure of Invention

The present disclosure provides a task state query method, device and storage medium, to at least solve the problem of long waiting time for a user to query a task state in the related art. The technical scheme of the disclosure is as follows:

according to a first aspect of the embodiments of the present disclosure, there is provided a method for querying a task state, which is applied to a client, the method including: responding to the operation of executing the task to be inquired by the user, sending a task state change message to the server, and acquiring a response time length corresponding to the task type of the task to be inquired; the task state change message comprises the task type of the task to be inquired, the response time length is used for reflecting the task of the same task type as the task to be inquired, and the average time length of the task state is changed; and after the response time length, inquiring the task state of the task to be inquired.

Optionally, the obtaining of the response time corresponding to the task to be queried includes: receiving a response time length sent by a server; the response time length is determined by the server according to a plurality of change time lengths corresponding to the task type of the task to be inquired in the historical statistic period, and each change time length comprises a time interval between a first time when the user executes the task in the client and a second time when the server determines that the task is successfully executed.

Optionally, the obtaining of the response time corresponding to the task to be queried includes: receiving a plurality of change durations sent by a server in a historical statistic period; the method comprises the following steps that a plurality of change time lengths correspond to task types of tasks to be inquired, and each change time length comprises a time interval between a first moment when a user executes the tasks in a client and a second moment when a server determines that the tasks are executed successfully; and determining the response time length according to the plurality of change time lengths.

Optionally, the determining the response time length according to the multiple change time lengths includes: determining a target change duration with a numerical value within a preset range from a plurality of change durations; and determining the average value of the target change time length as the response time length.

Optionally, the task state change message further includes a time when the user executes the task to be queried in the client; the task state change message is used for indicating the server to determine the change duration of the task to be inquired and storing the change duration of the task to be inquired; the time length of the change of the task to be inquired comprises the time interval between the time when the user executes the task to be inquired in the client and the time when the server determines that the task to be inquired is successfully executed.

Optionally, after querying the task state of the task to be queried, the method further includes: and under the condition that the task state of the task to be inquired is determined to be not successfully executed, re-inquiring the task state of the task to be inquired after the preset time length.

Optionally, the method further includes: and displaying that the task state of the task to be inquired is not successfully executed under the condition that the task state of the task to be inquired is determined to be not successfully executed and the number of times of re-inquiry is greater than or equal to a preset threshold value.

According to a second aspect of the embodiments of the present disclosure, a method for querying a task state is provided, which is applied to a server, and the method includes receiving a task state change message sent by a client; the task state information is generated by the client end responding to the operation of the user for executing the task to be inquired, and the task state change information comprises the task type of the task to be inquired; determining time information corresponding to the task type of the task to be queried according to the task type of the task to be queried, and sending the time information to the client; the time information is used for indicating the task state of the task to be inquired after the response time length is searched; the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state.

Optionally, the time information includes a response duration of the task to be queried; the determining 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: acquiring a plurality of change durations corresponding to the task type of the task to be queried in a historical statistical period; each change duration comprises a time interval between a first time when a user executes a task in the client and a second time when the server determines that the task is successfully executed; and determining the response time length of the task to be inquired according to the plurality of change time lengths.

Optionally, the determining the response time of the task to be queried according to the multiple change time durations includes: determining a target change duration with a numerical value within a preset range from a plurality of change durations; and determining the average value of the target change time length as the response time length.

Optionally, the time information includes a task type of the task to be queried and a plurality of corresponding change durations in a historical statistics period; each change duration comprises a time interval between a first time when a user executes a task in the client and a second time when the server determines that the task is successfully executed; the determining 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: and inquiring a plurality of change durations corresponding to the task type of the task to be inquired in the historical statistical period according to the task type of the task to be inquired.

Optionally, the task state change message further includes a time when the user executes the task to be queried in the client; the method further comprises the following steps: determining that the task to be queried is successfully executed, and determining the moment when the server determines that the task to be queried is successfully executed; determining the change duration of the task to be queried, and storing the change duration of the task to be queried; the time length of the change of the task to be inquired comprises the time interval between the time when the user executes the task to be inquired in the client and the time when the server determines that the task to be inquired is successfully executed.

Optionally, the method further includes: and determining a statistical period in which the change time length 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 determines that the task to be queried is successfully executed, and updating the mapping relation between the statistical period and the change time length based on the change time length of the task to be queried and the determined statistical period.

According to a third aspect of the embodiments of the present disclosure, a client is provided, which includes a sending unit, an obtaining unit, and a querying unit; the sending unit is used for responding to the operation of executing the task to be inquired by the user and sending a task state change message to the server; the task state change message comprises the task type of the task to be inquired; the acquiring unit is used for acquiring the response time length corresponding to the task type of the task to be inquired; the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state; and the query unit is used for querying the task state of the task to be queried after the response time length.

Optionally, the obtaining unit is specifically configured to: receiving a response time length sent by a server; the response time length is determined by the server according to a plurality of change time lengths corresponding to the task type of the task to be inquired in the historical statistic period, and each change time length comprises a time interval between a first time when the user executes the task in the client and a second time when the server determines that the task is successfully executed.

Optionally, the obtaining unit is specifically configured to: receiving a plurality of change durations sent by a server in a historical statistic period; the method comprises the following steps that a plurality of change time lengths correspond to task types of tasks to be inquired, and each change time length comprises a time interval between a first moment when a user executes the tasks in a client and a second moment when a server determines that the tasks are executed successfully; and determining the response time length according to the plurality of change time lengths.

Optionally, the obtaining unit is specifically configured to: determining a target change duration with a numerical value within a preset range from a plurality of change durations; and determining the average value of the target change time length as the response time length.

Optionally, the querying unit is further configured to, after a preset time duration, re-query the task state of the task to be queried when it is determined that the task state of the task to be queried is not successfully executed.

Optionally, the client further includes a display unit; and the display unit is used for displaying that the task state of the task to be inquired is not successfully executed under the condition that the task state of the task to be inquired is determined to be not successfully executed and the number of times of re-inquiry is greater than or equal to a preset threshold value.

According to a fourth aspect of the embodiments of the present disclosure, a server is provided, which includes a receiving unit, a determining unit, and a sending unit; the receiving unit is used for receiving a task state change message sent by the client; the task state information is generated by the client end responding to the operation of the user for executing the task to be inquired, and the task state change information comprises the task type of the task to be inquired; the determining unit is used for determining time information corresponding to the task type of the task to be inquired according to the task type of the task to be inquired; the time information is used for indicating the task state of the task to be inquired after the response time length is searched; the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state; and the sending unit is used for sending the time information to the client.

Optionally, the time information includes a response duration of the task to be queried; the determining unit is specifically configured to: acquiring a plurality of change durations corresponding to the task type of the task to be queried in a historical statistical period; each change duration comprises a time interval between a first time when a user executes a task in the client and a second time when the server determines that the task is successfully executed; and determining the response time length of the task to be inquired according to the plurality of change time lengths.

Optionally, the determining unit is specifically configured to: determining a target change duration with a numerical value within a preset range from a plurality of change durations; and determining the average value of the target change time length as the response time length.

Optionally, the time information includes a task type of the task to be queried and a plurality of corresponding change durations in a historical statistics period; each change duration comprises a time interval between a first time when a user executes a task in the client and a second time when the server determines that the task is successfully executed; the determining unit is specifically configured to: and inquiring a plurality of change durations corresponding to the task type of the task to be inquired in the historical statistical period according to the task type of the task to be inquired.

Optionally, the task state change message further includes a time when the user executes the task to be queried in the client; the server also comprises a storage unit; the determining unit is further used for determining that the task to be queried is successfully executed and determining the time when the server determines that the task to be queried is successfully executed; the determining unit is also used for determining the change duration of the task to be inquired; the changing duration of the task to be queried comprises a 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; and the storage unit is used for storing the change duration of the task to be inquired.

Optionally, the server further includes an updating unit; the determining unit is further used for determining a 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 determines that the task to be queried is successfully executed; and the updating unit is used for updating the mapping relation between the statistical period and the change time length based on the change time length of the task to be inquired and the determined statistical period.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a client, including: a processor, a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the method of querying a task state as provided by the first aspect.

According to a sixth aspect of the embodiments of the present disclosure, there is provided a server, including: a processor, a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the method of querying a task state as provided by the second aspect.

According to a seventh aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein instructions of the computer-readable storage medium, when executed by a processor of a client, enable the client to perform a method of querying a task state as provided by the first aspect and any one of its possible design approaches.

According to an eighth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein instructions of the computer-readable storage medium, when executed by a processor of a server, enable the server to perform a method for querying a task state as provided in the second aspect and any one of the possible design manners thereof.

According to a ninth aspect of the embodiments of the present disclosure, there is provided a computer program product, which includes computer instructions, when the computer instructions are executed on a server, the server executes the method for querying the task state provided in the first aspect and any possible design manner thereof.

According to a tenth aspect of the embodiments of the present disclosure, there is provided a computer program product, which includes computer instructions, when the computer instructions are executed on a server, the server executes the method for querying the task state as provided in the second aspect and any possible design manner thereof.

The technical scheme provided by the disclosure at least brings the following beneficial effects: after the user executes the task to be queried, the client can obtain the response time length corresponding to the task type of the task to be queried, and query the task state of the task to be queried after the response time length. The response time length is used for reflecting the tasks of the same task type of the tasks to be inquired, and the average time length of the task state is changed, so that different response time lengths can be obtained for different task types, different response time delays can be distributed to the tasks of each task type, the user can wait for the minimum time length under the condition that the task state in the server is ensured to be updated, and meanwhile, the task state obtained by the client side can be ensured to be relatively accurate.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

FIG. 1 is a block diagram illustrating a task query system in accordance with an exemplary embodiment;

FIG. 2 is one of the flow diagrams illustrating a method of querying a task state in accordance with an exemplary embodiment;

FIG. 3 is a second flowchart illustrating a task state query method according to an exemplary embodiment;

FIG. 4 is a third flowchart illustrating a task state query method according to an exemplary embodiment;

FIG. 5 is a fourth flowchart illustrating a task state query method in accordance with an exemplary embodiment;

FIG. 6 is a fifth flowchart illustrating a method of querying a task state, according to an exemplary embodiment;

FIG. 7 is a sixth flowchart illustrating a method of querying task states in accordance with an exemplary embodiment;

FIG. 8 is a seventh flowchart illustrating a task state query method in accordance with an exemplary embodiment;

FIG. 9 is an eighth flowchart illustration of a method of querying a task state, in accordance with an illustrative embodiment;

FIG. 10 is a ninth flowchart illustration of a method of querying a task state, in accordance with an exemplary embodiment;

FIG. 11 is a tenth flowchart illustration of a method of querying a task state, according to an example embodiment;

FIG. 12 is one of the schematic structural diagrams of a client shown in accordance with an exemplary embodiment;

FIG. 13 is a block diagram illustrating a server in accordance with an exemplary embodiment;

fig. 14 is a second schematic diagram illustrating a structure of a client according to an exemplary embodiment.

Detailed Description

In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

In addition, in the description of the embodiments of the present disclosure, "/" indicates an OR meaning, for example, A/B may indicate A or B, unless otherwise specified. "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present disclosure, "a plurality" means two or more than two.

The task state query method provided by the embodiment of the disclosure can be applied to a task query system. Fig. 1 shows a schematic structural diagram of the task query system. As shown in fig. 1, a task query system 10 is used to solve the problem of long waiting time of query task status in the related art. The task query system 10 includes a server 11 and a server 12. The client 11 is connected with the server 12. The client 11 and the server 12 may be connected in a wired manner or in a wireless manner, which is not limited in this disclosure.

The client 11 may be used for data interaction with the server 12, for example, the client 11 may send a task state change message to the server. Accordingly, the client 11 may also receive the response duration or the plurality of change durations sent by the server 12.

The client 11 may also execute the task state query method in the embodiment of the present disclosure, for example, after receiving the response time length sent by the server 12, the task state of the task to be queried is queried after the response time length elapses.

The server 12 is configured to respond to the response duration request sent by the client 11, obtain a plurality of change durations, and determine, according to the plurality of change durations, a response duration corresponding to the task type of the task to be queried.

It should be noted that the server 12 may be a server for executing the query method of the task state, may also be a server cluster composed of a plurality of servers, and may also be a cloud computing service center.

In practical applications, the method for querying a task state provided by the embodiment of the present invention may be applied to a client or a server, and the method for querying a task state provided by the embodiment of the present invention is described below with reference to the accompanying drawings.

As shown in fig. 2, the method for querying a task state provided by the embodiment of the present disclosure includes the following steps S201 to S203.

S201, the client responds to the operation of the user for executing the task to be inquired and sends a task state change message to the server.

The task state change message comprises the task type of the task to be inquired. The task state change message is used for indicating that the user executes the task to be inquired in the client.

As a possible implementation manner, after a user executes a task to be queried in an APP of a client, the client generates a task state task change message in response to an operation of the user to execute the task to be queried, and sends the task state change message to a server.

S202, the client side obtains the response time length corresponding to the task type of the task to be inquired.

The response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state.

As a possible implementation manner, the client may receive a response time length corresponding to a task type of a task to be queried, which is sent by the server.

As another possible implementation manner, the client may further obtain a plurality of change durations from the server, and determine a response duration of the task type of the task to be queried according to the obtained plurality of change durations.

For example, the task to be queried may be a praise task in the APP, or an attention task in the APP, or a video watched for a certain duration in the APP. The operation of the user for executing the task to be queried can be to execute praise and attention in the client, and can also be to watch a video with a certain duration in the APP.

The specific implementation manner of this step may refer to the subsequent description of the embodiment of the present disclosure, and is not described herein again.

S203, after the response time length, the client queries the task state of the task to be queried.

As a possible implementation manner, the client starts timing based on a timer therein, and starts sending a task state query request to the server after timing the response duration.

The query request comprises an identifier of the task to be queried, and the query request is used for requesting the server to return the task state of the task to be queried.

Correspondingly, the server side inquires the task state of the task to be inquired from the database of the server side according to the identification of the task to be inquired in the inquiry request, and sends the task state of the task to be inquired to the client side.

Illustratively, after responding to an operation of a user for a praise task, a client acquires that the response time of the praise task is 2 seconds, and then the client sends a query request for querying the task state of the praise task of the user to a server after 2 seconds, and displays the task state of the praise task to the user after acquiring the task state of the praise task.

Meanwhile, in the process of waiting for the user, the client can display loaded medium characters to the user to prompt the user to wait.

The technical scheme provided by the embodiment at least has the following beneficial effects: after the user executes the task to be queried, the client can obtain the response time length corresponding to the task type of the task to be queried, and query the task state of the task to be queried after the response time length. The response time length is used for reflecting the tasks of the same task type of the tasks to be inquired, and the average time length of the task state is changed, so that different response time lengths can be obtained for different task types, different response time delays can be distributed to the tasks of each task type, the user can wait for the minimum time length under the condition that the task state in the server is ensured to be updated, and meanwhile, the task state obtained by the client side can be ensured to be relatively accurate.

In one design, in order to enable the client to obtain the response time length corresponding to the task type of the task to be queried, as shown in fig. 3, the query method for the task state provided by the embodiment of the present disclosure further includes the following steps S301 to S303.

S301, the client sends a task state change message to the server.

The task state change message includes a task type of the task to be queried.

As a possible implementation manner, after receiving an operation of a user to wait for a task, the client sends a task state change message to the server.

The specific implementation manner of this step is the same as that of S201 described above.

Correspondingly, the server receives the task state change message sent by the client.

It should be noted that, the service end is provided with a consumer device for monitoring the received message.

S302, the server determines time information corresponding to the task type of the task to be inquired according to the task type of the task to be inquired.

As a possible implementation manner, the server side queries a plurality of change durations corresponding to the task types of the tasks to be queried from a database of the server side according to the task types of the tasks to be queried in the task state change message to determine time information.

It should be noted that the database of the server stores the time information of the task of each task type in different statistical periods in advance.

The implementation manner of this step may specifically refer to the subsequent description of the embodiment of the present disclosure, and is not described herein again.

S303, the server side sends the time information to the client side.

Correspondingly, the client receives the time information sent by the service to determine the response time length corresponding to the task type of the task to be queried.

Since the time information may be a plurality of change durations or response durations, specific implementation manners of the steps in S301 to S303 in different situations may refer to the following description of the embodiment of the present disclosure, and details are not repeated here.

The technical scheme provided by the embodiment at least has the following beneficial effects: and after receiving the task state change message sent by the client, the server returns time information to the client. The time information is used for indicating that the task state of the task to be inquired is inquired after the response time length, the response time length is used for reflecting the task of the same task type of the task to be inquired, and the average time length of the task state is changed, so that different response time lengths can be obtained aiming at different task types, different response time delays can be distributed to the tasks of each task type, the user can wait for the minimum time length under the condition that the task state in the server is ensured to be updated, and meanwhile, the task state obtained by the client side can be ensured to be relatively accurate.

In one design, the time information is a response time corresponding to a task type of a task to be queried. In order to enable the client to obtain the response time length corresponding to the task type of the task to be queried, as shown in fig. 4, the querying method in the embodiment of the present disclosure may further include the following steps S401 to S404.

S401, the client sends task state change information to the server.

For a specific implementation manner of this step, reference may be made to S201 or S301 described above in this disclosure, and details are not described here.

S402, the server side obtains a plurality of change durations corresponding to the task types of the tasks to be inquired in the historical statistic period.

Each change duration comprises a time interval between a first time when a user finishes executing a task in the client and a second time when the server determines that the task is successfully executed.

As a possible implementation manner, the server side queries a plurality of change durations corresponding to the task types in the historical statistical period corresponding to the task types of the tasks to be queried from the database of the server side according to the task types of the tasks to be queried.

It should be noted that, for any task type, the database of the server includes statistical data of a plurality of statistical periods corresponding to the task type. And each statistical period in the plurality of statistical periods is counted according to the successful execution time of the task. Each statistical data comprises a plurality of change durations corresponding to the task type.

The specific implementation manner of the change duration corresponding to each task type is stored in the database of the server, and the following description of the implementation example of the present disclosure may be referred to, and is not repeated here.

In one case, the historical statistical period may be a last statistical period of the current time.

It can be understood that, since the resource pressure of the server has a self-similarity with the resource pressure at the current time in the previous statistical period, the determination of the obtained response time length can be made more ready by using a plurality of changed time lengths in the previous statistical period.

And S403, the server determines the response time length according to the plurality of change time lengths.

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

It should be noted that the steps provided in S402-S403 may be a specific implementation manner of S302 in the embodiment of the present disclosure.

As there may be a certain difference in the change durations corresponding to the tasks at different times, in order to eliminate the difference between different change durations and make the obtained response duration more accurate, as another possible implementation manner, as shown in fig. 5, S403 provided in the embodiment of the present disclosure may further include the following S4031-S4032.

S4031, the server determines a target change duration having a numerical value within a preset range from the plurality of change durations.

As a possible implementation manner, the server may determine the target change duration from the plurality of change durations according to a preset range.

The preset range can be set in the server by operation and maintenance personnel in advance, or can be determined by the server.

In the following, a specific example of the server determining the target change duration is shown.

The server side sorts the plurality of change durations according to the duration, 0.25% of data at the head end and the tail end of the sorting result are removed from the sorting result, and the remaining 99.5% of the change durations are determined as target change durations.

It is understood that, in the above example, the maximum value and the minimum value of the preset range correspond to the values of 0.25% at the head and the tail ends of the sorting result, respectively.

S4032, the server determines the average value of the target change duration as the response duration.

The technical scheme provided by the embodiment at least has the following beneficial effects: the target change duration within the preset range is determined from the multiple change durations, so that data with obvious individual differences can be removed from the data set, and the calculated response duration can be ensured to be more accurate.

It should be noted that the steps executed by the server in S402-S403 may also be implemented as the specific implementation manner in S302.

S404, the server side sends response duration to the client side.

Correspondingly, the client receives the response time length sent by the server.

The response time length is determined by the server according to a plurality of change time lengths corresponding to the task type of the task to be inquired in the historical statistic period, and each change time length comprises a time interval between a first time when the user executes the task in the client and a second time when the server determines that the task is successfully executed.

The technical scheme provided by the embodiment at least has the following beneficial effects: the server side obtains a plurality of change durations, determines the response duration of the task to be inquired according to the obtained change durations, and sends the response duration to the client side.

In one design, the time information is a task type of a task to be queried, and a plurality of corresponding change durations are obtained in a 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, as shown in fig. 6, the querying method provided in the embodiment of the present disclosure may further include the following steps S501 to S504.

S501, the client sends a task state change message to the server.

The specific implementation manner of this step may refer to the specific implementation manners of S201 and S301 described above in the embodiments of the present disclosure, and details are not described here again.

S502, the server side inquires a plurality of change durations corresponding to the task type of the task to be inquired in the historical statistic period according to the task type of the task to be inquired.

The implementation manner of this step may refer to the specific description in S402 in this embodiment of the disclosure, and details are not repeated here.

It should be noted that, in some embodiments, this step may also be implemented as a specific implementation manner of the above-mentioned S302 of the present disclosure.

S503, the server side sends a plurality of change durations corresponding to the task types of the tasks to be inquired in the historical statistic period to the client side.

In some embodiments, this step may also be implemented as a specific implementation of S303 described above in this disclosure.

Correspondingly, the client receives a plurality of change durations which correspond to the task types of the tasks to be inquired and are sent by the server in the historical statistic period.

S504, the client determines the response time according to the plurality of change times.

The specific implementation manner of this step may refer to the specific implementation manner of S403 described above in this embodiment of the disclosure, and details are not described here. The difference is that the execution subject in S504 is different from that in S403.

The technical scheme provided by the embodiment at least has the following beneficial effects: the client can receive the plurality of change durations sent by the server, and determines the response duration according to the received plurality of change durations, so that another implementation mode for acquiring the response duration of the task to be queried is provided.

In one design, as shown in fig. 7, S504 provided in the embodiment of the present disclosure may specifically include the following S5041-S5042:

s5041, the client determines a target change duration having a value within a preset range from the plurality of change durations.

The specific implementation manner and the corresponding example in this step may refer to the specific description and example in S4031 in the embodiment of the present disclosure, and are not described again here. The difference is that the execution body is different.

S5042, the server determines the average value of the target change duration as the response duration.

Specific implementation manners and corresponding examples of this step may refer to the specific description and examples in S4032 described above in this embodiment of the disclosure, and are not described again here. The difference is that the execution body is different.

In one design, in order to ensure that the client can query the updated task state, as shown in fig. 8, the task state querying method provided in the embodiment of the present disclosure further includes the following steps S601 to S603.

S601, after the client side inquires the task state of the task to be inquired, the client side receives the task state of the task to be inquired sent by the server side.

It can be understood that the task status sent by the server may be successful in execution or unsuccessful in execution.

S602, under the condition that the task state of the task to be inquired is determined to be not successfully executed, the client re-inquires the task state of the task to be inquired after a preset time length.

It should be noted that the preset duration may be preset in the client or the APP of the client by the operation and maintenance staff.

For example, the preset time period may be 1 second.

And S603, under the condition that the task state of the task to be inquired is determined to be successfully executed, the client displays that the task state of the task to be inquired is successfully executed.

For example, in the case where the client displays the task list to the user, a button of the task to be queried in the task list is set to be inoperable, for example, gray, or a word pattern of completed is displayed.

S601 may be directly after S203, or may be repeatedly executed after S602.

The technical scheme provided by the embodiment at least has the following beneficial effects: when the task state is determined to be not successfully executed once by querying, in order to eliminate an error caused by the fact that the response time length is not calculated, the task state is queried again after the preset time length, and accordingly the accuracy of the obtained task state can be improved.

In one design, after the client repeatedly queries the task state of the task to be queried for multiple times, with reference to fig. 8 and as shown in fig. 9, the method for querying the task state according to the embodiment of the present disclosure further includes, after S601, the following step S604.

S604, under the condition that the task state of the task to be inquired is determined to be not successfully executed and the number of times of re-inquiry is greater than or equal to a preset threshold value, the client displays that the task state of the task to be inquired is not successfully executed.

As a possible implementation manner, when it is determined that the task state of the task to be queried is not successfully executed, the client obtains the number of times of re-query, and when the number of times of query is greater than or equal to a preset threshold, displays that the task state of the task to be queried is not successfully executed.

It should be noted that the preset threshold may be set in the client or the APP of the client in advance by the operation and maintenance staff.

Illustratively, the preset threshold may be 3. That is, after the client re-queries for 3 times at intervals of 1 second, if the queried task state is still not successfully executed, the task is displayed to the user that the task is not successfully executed.

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 incomplete prompt information.

In some embodiments, S604 referred to in the embodiments of the present disclosure may be specifically executed after S602.

The technical scheme provided by the embodiment at least has the following beneficial effects: after a plurality of queries, the task status of the task to be queried is determined to be still in the non-execution success status, which indicates that the task is not executed successfully indeed, just like the user shows that the task is not executed successfully. Therefore, continuous query caused by the fact that the task state is not successfully executed can be avoided, and time of the user is not wasted.

In one design, in order to enable the server to store the change duration corresponding to each task type, as shown in fig. 10, the method for querying the task state according to the embodiment of the present disclosure further includes following steps S701 to S705.

S701, the server receives a task state change message sent by the client.

The task state change message also comprises the time when the user executes the task to be inquired in the client; the task state change message is used for indicating the server to determine the change duration of the task to be inquired and storing the change duration of the task to be inquired; the time length of the change of the task to be inquired comprises the time interval between the time when the user executes the task to be inquired in the client and the time when the server determines that the task to be inquired is successfully executed.

As a possible implementation manner, after the user executes the task to be queried, the client acquires the time when the user executes the task to be queried, and generates a task state change message according to the acquired time. Further, the client sends the task state message to the server. Correspondingly, the server receives the task state change message.

Illustratively, taking praise tasks as an example, when a user opens a preset multimedia resource, after clicking a praise button, a client acquires a time when the user clicks the praise button and a task type of the praise task, and generates a task state change message.

In some embodiments, the task state change message includes information such as an identifier of the task to be queried, an identifier of the user, and a task type of the preset task.

S702, the server determines that the task to be inquired is successfully executed.

As a possible implementation manner, after receiving the task state change message, the server loads the task state change message into a message queue in the server. Further, after the message consumption service in the server reads the task state change message from the message queue according to a preset reading sequence, whether the task to be queried is executed successfully is judged.

It should be noted that, a plurality of messages to be processed may be simultaneously accommodated in the message queue. And the message consumption service reads the messages from the message queue one by one according to the time sequence and carries out corresponding processing.

S703, the server determines the time when the server determines that the task to be inquired is successfully executed.

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

S704, the server determines the change duration of the task to be inquired.

The time length of the task to be queried comprises a 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.

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

Illustratively, 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 time duration of the task to be queried is t2-t 1.

It can be understood that the change duration corresponding to the task type of a task may include a transmission delay of a task change message of the task, a queuing duration of the message in a message queue of the server, and a processing time of a message consumption service of the server. When the resource pressure of the server increases, the queuing time length in the change time length also increases.

S705, the server stores the change duration of the task to be inquired.

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

The technical scheme provided by the embodiment at least has the following beneficial effects: the server can obtain a first time and a second time of the task to be queried, determine that a difference value between the second time and the first time is a change time corresponding to the task type of the pre-task, and store the change time corresponding to the task type, so that a subsequent client or the server can determine a response time according to the change time.

In one design, in order to not facilitate querying statistical data of any statistical period, as shown in fig. 11, the task state querying method provided in this embodiment of the disclosure further includes the following steps S801 to S802.

S801, the server determines a statistical period where 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 determines that the task to be queried is successfully executed.

For example, taking a 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 32 seconds, and the time when the server determines that the task to be queried is successfully executed is 12 minutes 34 seconds, the change time length of the task to be queried is 2 seconds, and the change time length of the task to be queried is located in the statistical period corresponding to 12 minutes.

S802, the server side updates the mapping relation between the statistical period and the change time length based on the change time length of the task to be inquired and the determined statistical period.

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 mapping relationship.

It can be understood that the mapping relationship further includes a task type corresponding to the statistical period and statistical data in the statistical period. When the server side inquires a plurality of change durations corresponding to the task types in the history period, the last statistical period of the current time can be directly determined, and statistical data corresponding to the last statistical period can be obtained and are the plurality of change durations.

Illustratively, when the server receives a time length request sent by the client in 13 minutes and 11 seconds, the server obtains statistical data of the task type of the task to be queried in a statistical period of 12 minutes as a plurality of change time lengths corresponding to the task type of the task to be queried.

The technical scheme provided by the embodiment at least has the following beneficial effects: the change duration of the task is mapped with different statistical periods, so that the statistical data can be inquired more conveniently and quickly.

Fig. 12 is a schematic diagram illustrating a structure of a client according to an example embodiment. Referring to fig. 12, the client 90 provided in the embodiment of the present disclosure includes a sending unit 901, an obtaining unit 902, and an inquiring unit 903.

A sending unit 901, configured to send a task state change message to a server in response to an operation of a user to execute a task to be queried; the task state change message comprises the task type of the task to be inquired; for example, as shown in fig. 2, the transmitting unit 901 may be configured to execute S201.

An obtaining unit 902, configured to obtain a response duration corresponding to a task type of a task to be queried; the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state; for example, as shown in fig. 2, the obtaining unit 902 may be configured to execute S202.

The query unit 903 is configured to query a task state of the task to be queried after the response time length elapses. For example, as shown in fig. 2, the querying element 903 may be configured to perform S203.

Optionally, as shown in fig. 12, the obtaining unit 902 provided in the embodiment of the present disclosure is specifically configured to:

receiving a response time length sent by a server; the response time length is determined by the server according to a plurality of change time lengths corresponding to the task type of the task to be queried in the historical statistical period, and each change time length comprises a time interval between a first time when the user executes the task in the client 90 and a second time when the server determines that the task is successfully executed. For example, as shown in fig. 4, the obtaining unit 902 may be configured to execute S404.

receiving a plurality of change durations sent by a server in a historical statistic period; the plurality of change durations correspond to task types of the tasks to be queried, and each change duration comprises a time interval between a first time when the user executes the task in the client 90 and a second time when the server determines that the task is successfully executed; for example, as shown in fig. 6, the obtaining unit 902 may be configured to execute S503.

And determining the response time length according to the plurality of change time lengths. For example, as shown in fig. 6, the obtaining unit 902 may be configured to execute S504.

determining a target change duration with a numerical value within a preset range from a plurality of change durations; for example, as shown in fig. 7, fetch unit 902 may be configured to perform S5041.

And determining the average value of the target change time length as the response time length. For example, as shown in fig. 7, fetch unit 902 may be configured to perform S5042.

Optionally, as shown in fig. 12, in the client 90 provided in the embodiment of the present disclosure, the task state change message further includes a time when the user executes the task to be queried in the client 90; the task state change message is used for indicating the server to determine the change duration of the task to be inquired and storing the change duration of the task to be inquired; the time length of the task to be queried includes a 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.

Optionally, as shown in fig. 12, the querying unit 903 provided in the embodiment of the present disclosure is further configured to, when it is determined that the task state of the task to be queried is not successfully executed, re-query the task state of the task to be queried after a preset time period. For example, as shown in fig. 8, the querying element 903 may be configured to perform S602.

Optionally, as shown in fig. 12, the client 90 provided in the embodiment of the present disclosure further includes a display unit 904.

The display unit 904 is configured to display that the task state of the task to be queried is not successfully executed when it is determined that the task state of the task to be queried is not successfully executed and the number of times of re-querying is greater than or equal to a preset threshold. For example, as shown in fig. 8, the display unit 904 may be configured to perform S603.

In addition, the present disclosure also provides a server, configured to execute the method for querying the task state executed by the server according to the embodiment of the present disclosure, and as shown in fig. 13, the server 100 includes a receiving unit 1001, a determining unit 1002, and a sending unit 1003.

A receiving unit 1001, configured to receive a task state change message sent by a client; the task state information is generated by the client end responding to the operation of the user for executing the task to be inquired, and the task state change information comprises the task type of the task to be inquired; for example, as shown in fig. 3, the receiving unit 1001 may be configured to perform S301.

The determining unit 1002 is configured to determine, according to a task type of a task to be queried, time information corresponding to the task type of the task to be queried; the time information is used for indicating the task state of the task to be inquired after the response time length is searched; the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state; for example, as shown in fig. 3, the determining unit 1002 may be configured to perform S302.

A sending unit 1003, configured to send the time information to the client. For example, as shown in fig. 3, the transmitting unit 1003 may be configured to execute S303.

Optionally, as shown in fig. 13, the time information provided by the embodiment of the present disclosure includes a response duration of the task to be queried; the determining unit 1002 is specifically configured to:

acquiring a plurality of change durations corresponding to the task type of the task to be queried in a historical statistical period; each change duration comprises a time interval between a first time when the user executes the task in the client and a second time when the server 100 determines that the task is successfully executed; for example, as shown in fig. 4, the determining unit 1002 may be configured to perform S402.

And determining the response time length of the task to be inquired according to the plurality of change time lengths. For example, as shown in fig. 4, the determining unit 1002 may be configured to perform S403.

Optionally, as shown in fig. 13, a determining unit 1002 provided in an embodiment of the present disclosure is specifically configured to:

determining a target change duration with a numerical value within a preset range from a plurality of change durations; for example, as shown in fig. 5, the determination unit 1002 may be configured to execute S4031.

And determining the average value of the target change time length as the response time length. For example, as shown in fig. 5, the determination unit 1002 may be configured to execute S4032.

Optionally, as shown in fig. 13, the time information provided in the embodiment of the present disclosure includes a task type of a task to be queried and a plurality of corresponding change durations in a historical statistics period; each change duration includes a time interval between a first time when the user performs the task in the client and a second time when the server 100 determines that the task is successfully performed.

The determining unit 1002 is specifically configured to:

and inquiring a plurality of change durations corresponding to the task type of the task to be inquired in the historical statistical period according to the task type of the task to be inquired. For example, as shown in fig. 7, the determining unit 1002 may be configured to perform S502.

Optionally, as shown in fig. 13, the task state change message provided in the embodiment of the present disclosure further includes a time when the user executes the task to be queried in the client; the server 100 further includes a storage unit 1004.

The determining unit 1002 is further configured to determine that the task to be queried has been successfully executed, and determine a time when the server 100 determines that the task to be queried has been successfully executed; for example, as shown in fig. 10, the determining unit 1002 may be configured to perform S702-S703.

The determining unit 1002 is further configured to determine a change duration of the task to be queried; the time length of the change of the task to be queried comprises a 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, as shown in fig. 10, the determining unit 1002 may be configured to perform S704.

The storage unit 1004 is configured to store a change duration of the task to be queried. For example, as shown in fig. 10, the storage unit 1004 may be configured to execute S705.

Optionally, as shown in fig. 13, the server 100 provided in the embodiment of the present disclosure further includes an updating unit 1005.

The determining unit 1002 is further configured to determine a statistical period in which a change duration of the task to be queried is located according to a time when the user executes the task to be queried in the client or a time when the server 100 determines that the task to be queried is successfully executed; for example, as shown in fig. 11, the determination unit 1002 may be configured to perform S801.

An updating unit 1005, configured 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. For example, as shown in fig. 11, the determining unit 1002 may be configured to perform S802.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Fig. 14 is a schematic structural diagram of a client according to the present disclosure. As shown in fig. 14, the client 110 may include a processor 1101 and a memory 1103 for storing processor-executable instructions. Wherein the processor 1101 is configured to execute instructions in the memory 1103 to implement the query method of the task state in the above-described embodiments.

In addition, client 110 may also include a communication bus 1102 and a communication interface 1104.

The processor 1101 may be a Central Processing Unit (CPU), a micro-processing unit, an ASIC, or one or more integrated circuits for controlling the execution of programs in accordance with the disclosed aspects.

Communication bus 1102 may include a path that transfers information between the aforementioned components.

Communication interface 1104, which may be any transceiver or other communication network, may be used for communicating with other devices or communication networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc.

The memory 1103 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be self-contained and connected to the processing unit by a bus. The memory may also be integrated with the processing unit.

The memory 1103 is used for storing instructions for executing the disclosed solution, and the processor 1101 controls the execution. The processor 1101 is configured to execute instructions stored in the memory 1103 to thereby implement the functions in the disclosed method.

As an example, in conjunction with fig. 11, the sending unit 901, the obtaining unit 902, the querying unit 903, and the display unit 904 in the client 90 implement the same functions as the processor 1101 in fig. 14.

In particular implementations, processor 1101 may include one or more CPUs such as CPU0 and CPU1 in fig. 14, for example, as an embodiment.

In particular implementations, client 110 may include multiple processors, such as processor 1101 and processor 1107 in FIG. 14, for example, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (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).

In particular implementations, client 110 may also include an output device 1105 and an input device 1106, as an example. The output device 1105 is in communication 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, a projector (projector), or the like. The input device 1106 is in communication with the processor 1101 and can accept user input in a variety of ways. For example, the input device 1106 may be a mouse, keyboard, touch screen device or sensing device, etc.

Those skilled in the art will appreciate that the architecture shown in fig. 14 is not limiting for client 110, and may include more or fewer components than shown, or combine certain components, or employ a different arrangement of components.

Meanwhile, the structural diagram of another hardware of the server according to the present disclosure may also refer to the description of the client 90 in fig. 14, and is not repeated herein. The difference is that the server includes a processor for executing the steps performed by the server in the above embodiments.

In addition, the present disclosure also provides a computer-readable storage medium, wherein when the instructions in the computer-readable storage medium are executed by a processor of the client, the client can execute the task state query method provided in the above embodiment.

In addition, the present disclosure also provides a computer-readable storage medium, and when instructions in the computer-readable storage medium are executed by a processor of a server, the server is enabled to execute the method for querying a task state provided in the above embodiment.

In addition, the present disclosure also provides a computer program product including computer instructions, which when run on a client, cause the client to execute the query method of task status as provided in the above embodiments.

In addition, the present disclosure also provides a computer program product, which includes computer instructions, when the computer instructions are run on a server, the server executes the query method of the task state as provided in the above embodiments.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A task state query method is applied to a client and is characterized by comprising the following steps:

responding to the operation of executing the task to be inquired by the user, sending a task state change message to the server, and acquiring a response time length corresponding to the task type of the task to be inquired; the task state change message comprises the task type of the task to be inquired, and the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state;

and after the response time length, inquiring the task state of the task to be inquired.

2. The task state query method according to claim 1, wherein the obtaining of the response duration corresponding to the task to be queried includes:

receiving the response duration sent by the server; the response time length is determined by the server according to a plurality of change time lengths corresponding to the task type of the task to be inquired in a historical statistic period, and each change time length comprises a time interval between a first time when a user executes the task in the client and a second time when the server determines that the task is successfully executed.

3. A task state query method is applied to a server side and is characterized by comprising the following steps:

receiving a task state change message sent by a client; the task state message is generated by the client in response to the operation of executing the task to be queried by the user, and the task state change message comprises the task type of the task to be queried;

determining time information corresponding to the task type of the task to be queried according to the task type of the task to be queried, and sending the time information to the client; the time information is used for indicating that the task state of the task to be inquired is inquired after the response time length; and the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state.

4. The task state query method according to claim 3, wherein the time information includes the response duration of the task to be queried; the determining 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:

acquiring a plurality of change durations corresponding to the task type of the task to be queried in a historical statistical period; each change duration comprises a time interval between a first time when a user executes a task in the client and a second time when the server determines that the task is successfully executed;

and determining the response time length of the task to be inquired according to the plurality of change time lengths.

5. A client is characterized by comprising a sending unit, an obtaining unit and a query unit;

the sending unit is used for responding to the operation of executing the task to be inquired by the user and sending a task state change message to the server; the task state change message comprises the task type of the task to be inquired;

the acquiring unit is used for acquiring a response time length corresponding to the task type of the task to be inquired; the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state;

and the query unit is used for querying the task state of the task to be queried after the response time length passes.

6. A server is characterized by comprising a receiving unit, a determining unit and a sending unit;

the receiving unit is used for receiving a task state change message sent by a client; the task state message is generated by the client in response to the operation of executing the task to be queried by the user, and the task state change message comprises the task type of the task to be queried;

the determining unit is used for determining time information corresponding to the task type of the task to be inquired according to the task type of the task to be inquired; the time information is used for indicating that the task state of the task to be inquired is inquired after the response time length; the response time length is used for reflecting the task of the same task type as the task to be inquired and changing the average time length of the task state;

the sending unit is configured to send the time information to the client.

7. A client, comprising: a processor, a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement the method of querying a task state of claim 1 or 2.

8. A server, comprising: a processor, a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement the method of querying a task state of claim 3 or 4.

9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of a client, enable the client to perform a method of querying a task state according to claim 1 or 2; alternatively, the instructions in the computer-readable storage medium, when executed by a processor of a server, enable the server to perform the method of querying the task state according to claim 3 or 4.

10. A computer program product comprising instructions, characterized in that it comprises computer instructions which, when run on a client, cause the client to perform a method of querying of task status according to claim 1 or 2; alternatively, the computer instructions, when run on a server, cause the server to perform a method of querying for a task state as claimed in claim 3 or 4.