Task interaction method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a task interaction method and device, equipment and a storage medium. The method comprises the following steps: in response to a request for a task of an intelligent agent, presenting first information related to an execution process of the task in an interface interacting with the intelligent agent, and requesting task information indicating the task; causing execution of the task to be paused in response to a pause condition of the task being satisfied; and in response to receiving adjustment or recovery of the task in the pause state of the task, recovering execution of the task, and presenting second information related to an execution process or an execution result of the recovered task in the interface. In this way, in the execution process or in the execution process of the task, the user can pause and modify execution of the task at any time so as to obtain a result meeting the requirement of the user.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and particularly to methods, devices, electronic devices, computer-readable storage media, and computer program products for task interaction. Background Art

[0002] With the development of information technology, more and more intelligent systems can complete various complex tasks based on user input. Such systems usually interact with users in the form of conversations, generating response content according to users' natural language requests, thus forming question-and-answer conversations. However, in practical applications, the user's goal is often not just to obtain a single reply, but to hope that the system can complete a complete plan and execution around a certain task. Therefore, how to complete the execution of a specific task based on a task-goal-driven model and improve the structural degree and user controllability of the execution process has become an issue worthy of attention. Summary of the Invention

[0003] In a first aspect of the present disclosure, there is provided a method for task interaction, including: in response to a request for a task of an agent, presenting first information related to an execution process of the task in an interface for interacting with the agent, the request indicating task information of the task; in response to a suspension condition of the task being satisfied, suspending the execution of the task; and in response to receiving an adjustment or recovery of the task in a suspended state of the task, resuming the execution of the task, wherein second information related to an execution process or an execution result of the resumed task is presented in the interface.

[0004] In a second aspect of the present disclosure, there is provided a device for task interaction, including: a first information presentation module configured to present first information related to an execution process of a task in an interface for interacting with an agent in response to a request for a task of the agent, the request indicating task information of the task; an execution suspension module configured to suspend the execution of the task in response to a suspension condition of the task being satisfied; and an execution recovery module configured to resume the execution of the task in response to receiving an adjustment or recovery of the task in a suspended state of the task, wherein second information related to an execution process or an execution result of the resumed task is presented in the interface.

[0005] In a third aspect of the present disclosure, there is provided an electronic device. The device includes at least one processor; and at least one memory, the at least one memory being coupled to the at least one processor and storing instructions for execution by the at least one processor. The instructions, when executed by the at least one processor, cause the device to execute the method of the first aspect.

[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided. Computer-executable instructions are stored on the computer-readable storage medium, and the computer-executable instructions can be executed by a processor to implement the method of the first aspect.

[0007] According to a fifth aspect of the present disclosure, a computer program product is provided, including computer-executable instructions, where the computer-executable instructions implement the method of the first aspect when executed by a processor.

[0008] It should be understood that the content described in this part is not intended to define the key features or important features of the embodiments of the present disclosure, nor is it used to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In combination with the accompanying drawings and with reference to the following detailed description, the above and other features, advantages, and aspects of the embodiments of the present disclosure will become more apparent. In the drawings, the same or similar reference numerals represent the same or similar elements, where:

[0010] Figure 1 A schematic diagram showing an example environment in which the embodiments of the present disclosure can be implemented;

[0011] Figures 2A to 2I A schematic diagram showing an example interface for interacting with an agent according to some embodiments of the present disclosure;

[0012] Figure 3 A flowchart showing a process for task interaction according to some embodiments of the present disclosure;

[0013] Figure 4 A block diagram showing a device for task interaction according to some embodiments of the present disclosure; and

[0014] Figure 5 A block diagram showing an electronic device capable of implementing one or more embodiments of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0015] The embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0016] In the description of the embodiments of the present disclosure, the term "including" and its similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". There may also be other explicit and implicit definitions hereinafter.

[0017] In this article, unless otherwise specified, performing a step "in response to A" does not mean that the step is immediately performed after "A", but may include one or more intermediate steps.

[0018] It can be understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of the corresponding laws, regulations and related provisions.

[0019] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner according to relevant laws and regulations.

[0020] For example, when a user's active request is received, a prompt message is sent to the user to clearly prompt the user that the operation requested by the user will require the acquisition and use of the user's personal information, so that the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, an application program, a server, or a storage medium that performs the operations of the technical solution of the present disclosure according to the prompt message.

[0021] As an optional but non-limiting implementation manner, the manner of sending a prompt message to the user in response to receiving the user's active request may be, for example, in the form of a pop-up window, and the prompt message may be presented in text in the pop-up window. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0022] It can be understood that the above process of notifying and obtaining the user's authorization is only illustrative and does not limit the implementation manner of the present disclosure, and other manners that meet the relevant laws and regulations can also be applied to the implementation manner of the present disclosure.

[0023] As used herein, the term "model" can learn the corresponding association between inputs and outputs from training data, so that after training, for a given input, the corresponding output can be generated. The generation of the model can be based on machine learning techniques. Deep learning is a machine learning algorithm that processes inputs and provides corresponding outputs by using multiple layers of processing units. A neural network model is an example of a model based on deep learning. In this document, "model" can also be referred to as "machine learning model", "learning model", "machine learning network", or "learning network", and these terms are used interchangeably herein.

[0024] A "neural network" is a machine learning network based on deep learning. A neural network can process inputs and provide corresponding outputs, and it generally includes an input layer and an output layer, as well as one or more hidden layers between the input layer and the output layer. Neural networks used in deep learning applications usually include many hidden layers, thus increasing the depth of the network. The layers of the neural network are connected in sequence, so that the output of the previous layer is provided as the input of the next layer, where the input layer receives the input of the neural network, and the output of the output layer is the final output of the neural network. Each layer of the neural network includes one or more nodes (also called processing nodes or neurons), and each node processes the input from the previous layer.

[0025] Generally, machine learning can roughly include three stages, namely, a training stage, a testing stage, and an application stage (also called an inference stage). In the training stage, a given model can be trained using a large amount of training data, and the parameter values are continuously iteratively updated until the model can obtain consistent inferences that meet the expected goals from the training data. Through training, the model can be considered to be able to learn the association from inputs to outputs (also called the mapping from inputs to outputs) from the training data. The parameter values of the trained model are determined. In the testing stage, the test inputs are applied to the trained model to test whether the model can provide the correct outputs, so as to determine the performance of the model. In the application stage, the model can be used to process actual inputs based on the parameter values obtained through training and determine the corresponding outputs.

[0026] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. In this example environment 100, an application 125 is installed in the terminal device 110. The user 140 can interact with the application 125 via the terminal device 110 and / or an attached device of the terminal device 110.

[0027] In some embodiments, the application 125 can be downloaded and installed in the terminal device 110. In some embodiments, the application 125 can also be accessed in other ways, such as by web access, etc. In Figure 1In the environment 100, in response to the application 125 being launched, the terminal device 110 can present the interface 150 of the application 125.

[0028] In some embodiments, the terminal device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / video cameras, positioning devices, television receivers, radio broadcast receivers, e-book devices, gaming devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the terminal device 110 can also support any type of user interface (such as a "wearable" circuit, etc.).

[0029] In some embodiments, the terminal device 110 communicates with the server 130 to implement the service provision of the application 125. The terminal device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / video cameras, television receivers, radio broadcast receivers, e-book devices, gaming devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the terminal device 110 can also support any type of user interface (such as a "wearable" circuit, etc.). The application 125 can be various types of computing systems / servers capable of providing computing capabilities, including but not limited to mainframes, edge computing nodes, computing devices in a cloud environment, and the like.

[0030] In the embodiments of the present disclosure, the application 125 can provide an interaction function with the agent. The application 125 can be an application dedicated to providing agent services, or an application integrated with an agent (that is, it can provide other functions or services in addition to the agent). Although Figure 1 a single application is shown, in fact, multiple applications can be installed on the terminal device 110.

[0031] In the present disclosure, the agents 160-1, 160-2,... 160-N (collectively or individually referred to as the agent 160) can be deployed locally on the terminal device 110 or remotely deployed. In the case of remote deployment, the terminal device 110 can directly call the agent, or can call the agent via the server 130.

[0032] In an embodiment of the present disclosure, the agent 160 may have the capabilities of intelligent conversation and task processing. The terminal device 110 provides an interface 150 that can present the interaction with the agent 160. In the interface 150, the user 140 can input a task request for the agent 160 by inputting natural language (text input or voice input), and can also upload an input online or offline file for conversation to instruct the agent 160 to assist in completing various tasks.

[0033] In an embodiment of the present disclosure, during the interaction with the user 140, the agent 160 can, in response to the request of the user 140, process the task indicated by the user. In some embodiments, during the task processing, the agent 160 can call one or more tools 165-1, 165-2,..., 165-M (collectively or individually referred to as tools 165) according to the task requirements to assist in the execution of the task and the provision of the task result. These tools 165 can be any type of tool, such as a weather query tool, a flight query tool, an information search tool, an online or offline database, an image processing tool, a chart generation tool, a web page production tool, and so on.

[0034] In some embodiments, the environment 100 may further include a management node for multiple agents 160-1, 160-2,..., 160-N, and this management node can interact with the multiple agents 160-1, 160-2,..., 160-N. In some examples, the management node can, in response to the task request of the user 140, determine the task requirements corresponding to the task request. Thereafter, the management node can, based on the task requirements, assign the task request to the agent 160 that matches the task requirements to request the agent 160 to execute the task. In other examples, the management node can also, based on the task requirements, determine the execution plan of the task. The execution plan of the task can indicate one or more subtasks required to complete the task. The management node can assign the one or more subtasks to one or more agents 160, and the one or more agents 160 can execute their respective corresponding subtasks respectively. Regarding this management node, in some examples, the management node can be implemented by one of the multiple agents 160-1, 160-2,..., 160-N (in this case, this agent 160 is also referred to as the management agent 160). In other examples, the management node can be implemented by a machine learning model, for example, it can be implemented by a language model (LM) or a large language model (LLM).

[0035] In some embodiments, the agent 160 can be constructed based on one or more machine learning models. In some embodiments, the machine learning models on which the agent 160 is based can at least include a language model (LM). These machine learning models include content generation models that can generate corresponding outputs based on model inputs. In some embodiments, the machine learning models based on the language model can receive model inputs in text modalities (e.g., natural language and / or machine language) and / or non-text modalities (e.g., images, speech, videos, etc.), and can obtain corresponding model outputs according to the model inputs and prompt words, so as to complete the execution of tasks. The prompt words here are used to guide the machine learning model to generate responses that can solve the user queries indicated by the model inputs. In an application scenario for supporting user conversations, the input of the user 140 can be provided to the machine learning model 160 as at least a part of the model input (the other part can include prompt words). This user input is regarded as a question or a query request. Based on the model output, a corresponding response can be provided to the user 140.

[0036] It should be understood that the structures and functions of the various elements in the environment 100 are described only for exemplary purposes, without implying any limitation on the scope of the present disclosure.

[0037] As briefly mentioned above, a user may initiate a task request within an application. In some scenarios, the user can input task requirements in the user interface provided by the application, and the application can provide services that can meet the task requirements according to the user's task requirements. Conventionally, the user can initiate a question in an application that provides a question-and-answer service to obtain a corresponding answer. However, by the operation method, the user cannot perceive the execution process of the question. Further, in some scenarios, after the task is initiated, the user cannot control and modify the execution process of the task and can only wait for the task to be executed to completion. Alternatively, after the task is initiated, the user can choose to interrupt the current task and initiate a new task.

[0038] According to some embodiments of the present disclosure, an improved solution for task interaction is proposed. According to the solution of the embodiments of the present disclosure, if a request for a task of an agent is received, first information related to the execution process of the task is presented in the interface for interacting with the agent, and the request indicates the task information of the task. When the pause condition of the task is satisfied, the execution of the task is paused. Further, if an adjustment or resume of the task is received in the paused state of the task, the execution of the task can be resumed. Correspondingly, if the execution of the task is resumed, second information related to the execution process or execution result of the resumed task is presented in the interface.

[0039] In this way, by presenting the task execution process and execution results in the interface for interacting with the agent, the user can learn about the disassembly process and execution process of the agent for this task. Further, during the task execution process or disassembly process, the user can pause, adjust, or resume the disassembly or execution of the task at any time to obtain a result that meets their own needs.

[0040] In the present disclosure, "trigger" refers to one or more interaction operations of the user on the terminal device. Further, these interaction operations can be triggered within the same user interface / popup window or within different user interfaces / popup windows. The present disclosure is not limited in this regard.

[0041] Some embodiments of the present disclosure will be described below with reference to the accompanying drawings. For ease of understanding, the following will refer to Figures 2A to 2I Examples of interfaces for interacting with the agent in some embodiments of the present disclosure will be described. These example interfaces can be presented by the application 125 in the terminal device 110. It should be understood that the interfaces shown in the drawings are merely examples, and various interface designs can actually exist. The various graphical elements in the interface can have different arrangements and different visual representations, one or more of which can be omitted or replaced, and there can also be one or more other elements. The embodiments of the present disclosure are not limited in this regard.

[0042] In Figure 2A The shown interface 200A can present the interaction interface 200A between the user 140 and the agent 160. In this interaction interface 200A, a request for a new task initiated by the user can be received. As Figure 2A shown, the user can trigger a new task by triggering the "New Task" control 211. In response to the triggering of the "New Task" control 211, an interaction interface specific to the task is presented in the interface 200A, such as Figure 2B the shown interaction interface 200B, to initiate a new task in the interaction interface 200B. In some embodiments, an input area 215 for task input is also provided in the interface 200A. In the input area 215, the user can input a request for the task to be triggered and initiate the task request through the "Send" control 216. The input area 215 can support text input, such as entering text in a text input box, and can also support voice input, such as by triggering a voice control 217. In addition, the input area 215 can also provide an upload control 216 to support uploading an attachment to indicate the user's task request. In some embodiments, the interaction interface 200A also provides a task list 212 initiated by the agent 160. The task list 212 indicates each initiated task and the execution status of the task (e.g., interrupted status, in-progress status, completed status, etc.).

[0043] In some embodiments, multiple operation modes of the user 140 and the agent 160 can be provided, and flexible switching between the multiple operation modes can be performed, for example, via Figure 2A the mode switching control 218 shown. When a certain mode is triggered, a corresponding interaction area is presented to facilitate the interaction between the user 140 and the agent 160. The interaction manners between the user 140 and the agent 160 are different in different operation modes, so that the interaction requirements in different application scenarios can be flexibly adapted. In some embodiments, different operation modes may include an automatic mode and a collaborative mode. In the automatic mode, the agent 160 can continuously execute the task automatically until the task is completed. In the coordination mode, after the agent 160 completes an action of the task execution, it can pause the task execution and provide modification and confirmation options for the user to check whether the execution of the current action meets the expectation and whether the execution of the action needs to be modified. If no modification is required, after receiving the user confirmation, the agent 160 will continue to execute the next action of the task until the task is completed.

[0044] In some embodiments, during the process of task execution by the agent 160, it can be in a paused state. Options such as modification and resume can be provided during the paused state for the user to check whether the execution of the current action meets the expectation and whether the execution of the action needs to be modified. Then, in the case of modifying the task, the modified task can be passed to the management agent 160. The management agent 160 can allocate the modification of the task to other agents. During the task execution, the user 140 can add a new task, for example, add an XX subtask. In this scenario, the terminal device 110 can call the management agent 160 to add the XX subtask. After receiving the XX subtask, the management agent 160 can modify the entire task. Subsequently, the management agent 160 can re-allocate the task to each agent. In some embodiments, the terminal device 110 can call the agent that can solve the XX subtask to process it.

[0045] In some embodiments, the management agent 160 can determine a prompt word corresponding to additional task information indicating the modification or addition of a subtask. This prompt word can be spliced into the original prompt word as a component of the system prompt (SP) to provide context guidance for subsequent task execution. Alternatively or additionally, the prompt word corresponding to the additional task information is directly spliced into the task prompt word of the agent corresponding to the subtask, so that the corresponding agent can consider the new context content when executing the task.

[0046] After triggering a request for the task of the agent, the terminal device 110 presents Figure 2BThe interactive interface 200B shown. In the interactive interface 200B, requests for tasks initiated by the user can be presented, such as message 221, and task execution information during the execution of tasks by the agent can also be presented. The task execution information can be presented in the interactive interface 200B in the form of one or more messages. During the execution of the task, the agent 160 can analyze the task request initiated by the user to determine the task requirements, thereby generating an execution plan for the task. The execution plan of the task can indicate one or more subtasks required to complete the task. To enable the user to more clearly understand the execution process of the task by the agent, a message 221 indicating the generation of the execution plan can be presented in the interactive interface 200B. After the execution plan is determined, messages 223 indicating each subtask in the execution plan (such as subtask 224, subtask 225, and other subtasks) can be presented in the interactive interface 200B. Next, the agent 160 will automatically or in response to the user's confirmation continue to execute each subtask, and the execution process and execution results of each subtask can be presented in the interactive interface 200B. After the execution of the entire task is completed, the execution result of the task or an access entry to the execution result (if the execution result needs to be presented on another interface) can be presented in the interactive interface 200B. In this way, during the execution of the entire task, the user can intuitively understand how the agent specifically breaks down the user's task requirements and the specific execution steps of each subtask, so as to facilitate the user to confirm or adjust the execution process of the task or subtask, and thus obtain the desired execution result.

[0047] In some embodiments, the process of determining one or more subtasks required to complete the task in the execution plan of the task based on the task request of the user 140 can be implemented by a machine learning model deployed at the server 130 or called by the server 130. Further, after determining the specific task execution plan, the machine learning model can assign each subtask to one or more suitable agents 160 for specific task execution.

[0048] Alternatively or additionally, the user's task request can also be sent to the management agent 160. The process of determining one or more subtasks in the execution plan of the task can be implemented by the management agent 160. The management agent 160 can be used to parse the user's task request based on the task request of the user 140, thereby determining one or more subtasks required to complete the task in the execution plan of the task. Further, the management agent 160 can assign the subtasks to one or more suitable agents 160 for specific task execution according to different task execution requirements and capabilities.

[0049] Some exemplary embodiments of the present disclosure will be further described below with reference to the accompanying drawings. The embodiments related to the present disclosure can be implemented in the terminal device 110. It should be noted that the operations performed by the terminal device 110 can specifically be performed by relevant applications (such as application 120) installed on the terminal device 110. Some operations described with reference to the terminal device 110 may require the assistance of the server 130 to complete.

[0050] In this document, the application 120 that supports task processing functions is deployed in the terminal device 110, and the user 140 can use the application 120 to process some tasks, such as including but not limited to information query (for example, obtaining real-time information such as weather forecasts, news summaries, etc.), data processing (for example, analyzing the sales report for the XX quarter), code execution (for example, generating and executing simple code snippets), and so on. However, these are only exemplary, and the present disclosure does not limit this.

[0051] In the embodiments of the present disclosure, if the terminal device 110 determines that the task suspension condition is met, the execution of the task is suspended. In some embodiments, if the terminal device 110 determines that the task suspension condition is met, at least one interaction element may be presented in the interface, where the execution of the task is suspended. The at least one interaction element is at least configured to adjust or resume the task in the suspended state of the task. In some scenarios, during the process when the terminal device 110 calls the agent 160 to determine the task plan of the task and execute the task, the user 140 can pause and adjust the task at any time to obtain a result that meets the needs of the user 140. In the scenario where the terminal device 110 needs the user 140 to input additional task information or take over, the progress of the task can be suspended, and the execution of the task can be adjusted or resumed based on the next interaction operation of the user 140. In the scenario where the execution duration of a certain subtask of the task exceeds the duration threshold, the terminal device 110 can suspend the progress of the task and adjust or resume the execution of the task based on the next interaction operation of the user 140. The above scenarios are only exemplary, and the present disclosure does not limit this. Below, with reference to the accompanying drawings, it will be described in detail under what conditions the terminal device 110 suspends the task and how the user 140 can interact with the agent 160 for the task in the suspended state.

[0052] In an embodiment of the present disclosure, if the terminal device 110 receives an adjustment or resumption of a task in a paused state of the task, the execution of the task is resumed. Correspondingly, if the terminal device 110 determines the resumption of the execution of the task, it may present second information related to the execution process or execution result of the resumed task in the interface. In some embodiments, based on the interaction operation of the user 140 after the execution of the task is paused, the terminal device 110 may determine that the execution of the task is resumed. Furthermore, the terminal device 110 may continue to present information related to the execution process or execution result of the task in the interface (such as the example interface 200B).

[0053] The following will refer to Figures 2B to 2I describe under what conditions the terminal device 110 pauses a task and how the user 140 can interact with the agent 160 for a task in a paused state.

[0054] In some embodiments, when the terminal device 110 invokes the agent 160 to generate a task plan for a task, it may determine that the pause condition of the task is met, thereby pausing the execution of the task. Correspondingly, the terminal device 110 may present in the interface task information indicating at least one subtask as indicated by the task plan. The terminal device 110 may present a first interaction element and a fifth interaction element for starting the execution of the task plan in the interface. In some embodiments, the first interaction element is used to trigger an adjustment of the task information of the task in the paused state of the task. The first interaction element may be used to receive trigger input of additional task information for the task, that is, to adjust the task information of the task based on the additional task information. In some examples, at least one subtask is determined during the execution of the task. After requesting the execution of the task, the agent 160 may first analyze the request from the user and determine the execution plan of the task. The execution plan of the task indicates one or more subtasks included in the task.

[0055] As Figures 2C to 2D shown in the example interfaces 200C to 200D, when the terminal device 110 determines that the task has been disassembled into subtasks such as subtask 223, subtask 224, subtask 3, subtask 4, etc., it may present in the interface (such as the example interface 200C) the task information 223 corresponding to each subtask respectively. In this scenario, the terminal device 110 may determine that the current task is in a paused state and may present in the interface (such as the example interface 200C) an interaction element 231 (for example, a "Modify Task" control) and an interaction element 232 (for example, a "Start Task" control). The user 140 can click the interaction element 232 to enable the terminal device 110 to start executing each subtask.

[0056] If the terminal device 110 receives a click on the interaction element 231 by the user 140, it can present an input box 241 in the interface (such as the example interface 200D). The user 140 can enter additional task information for the task in the input box 241. For example, the user 140 can enter some modification suggestions. Although not shown in the figure, in addition to direct input in the text input box, the interaction element 241 can also support other input methods, such as voice input, or providing modification suggestions by uploading attachments, providing web links, etc. Subsequently, if the terminal device 110 receives the additional task information entered by the user 140, it can use the agent 160 to continue the execution of the task based on the additional task information entered by the user 140 and the information of the task execution process or the execution result that has been generated currently.

[0057] In some embodiments, the terminal device 110 can also present a cancel control 242 and a confirmation control 243 in the interaction interface 200D. The cancel control 242 is used to revoke the modification process carried by the current input box 241 and return to the presentation interface of the original task plan when the user abandons the modification operation. The confirmation control 243 is used to confirm the submission of the modified content after the user finishes inputting.

[0058] In some embodiments, referring to Figure 2B and Figure 2E the example interfaces 200B and 200E shown, during the execution of the task, the terminal device 110 can present a pause control 226 in the interface. If the terminal device 110 receives a trigger on the pause control 226, it can determine that the pause condition of the task is met, thereby pausing the execution of the task. That is to say, during the execution of the task, the user 140 can click the pause control 226 to make the task in a paused state. For example, during the process of the terminal device 110 generating a task plan, if the user 140 needs to supplement some information, then the user 140 can click the pause control 226 to supplement this information based on the interaction elements provided by the terminal device 110 (such as an "input box"). Another example is that during the process of the terminal device 110 executing a subtask, if the user 140 needs to supplement some information, then the user 140 can also click the pause control 226 to supplement this information based on the interaction elements provided by the terminal device 110 (such as an "input box"). In these scenarios, the terminal device 110 can present an interaction element 231 (such as an "input box") and an interaction element 252 (such as a "continue" control) in the interface (such as the example interface 200E). The interaction element 252 (i.e., the second interaction element) can be used to trigger the resume of the task execution in the paused state of the task.

[0059] In some embodiments, if the terminal device 110 receives additional task information via the first interaction element, it may resume the execution of the task. Accordingly, the terminal device 110 may present second information related to the execution process or execution result of the resumed task in the interface, where the second information is determined based on the additional task information and the first information. As Figure 2E shown, the user 140 may input the requirement information of the user 140 in the interaction element 231 (e.g., "input box") presented in the interface (such as the example interface 200E) to resume the execution of the task. If the terminal device 110 receives the additional task information input by the user 140, it may use the agent 160 to generate the second information based on the additional task information input by the user 140 and the information of the task process that has been executed or the information of the execution result that has been generated for the current task. Accordingly, the terminal device 110 may continue to present the second information in the interface.

[0060] In some embodiments, if the terminal device 110 receives the trigger of the user 140 on the interaction element 252 (e.g., "continue" control), it may also resume the execution of the task. At this time, since the user 140 does not input additional task information, the second information presented continuously in the interface is generated by the agent 160 based on the previous first information and the execution plan of the task. In some embodiments, if the terminal device 110 detects that the execution of the task is paused, it may present an interaction element 251 (e.g., "terminate" control) for stopping the execution of the task in the interface (such as the example interface 200E). If the terminal device 110 receives the trigger of the user 140 on the interaction element 251 (e.g., "terminate" control), it may terminate the execution of the task. Thus, the user can interrupt, adjust, or resume the execution of the task at any time to obtain a result that meets their own needs.

[0061] In some embodiments, the agent 160 may execute these subtasks step by step based on the determined execution plan, thereby gradually completing the execution of the entire task. In some embodiments, in order to achieve human-machine collaboration and dynamic control during the task execution process and strengthen the controllability of the user over the task execution process of the agent, when the current action of the agent 160 is completed, it may enter the intermediate interaction stage. In this stage, the terminal device 110 may cache the execution result of the current action and pause the automatic advancement of the subsequent actions in the task flow. The user 140 may adjust the execution of the current action in the intermediate interaction stage, such as modifying, replacing, or regenerating the execution content. The following will refer to Figure 2F to describe the task interaction process in the intermediate interaction stage.

[0062] Refer to Figure 2FIn the example interface 200F shown, during the execution of a task, if the terminal device 110 determines that a third subtask (e.g., subtask 261) among at least one subtask of the task requires auxiliary information (i.e., additional task information), it may determine that the pause condition of the task is satisfied, thereby pausing the execution of the task. That is to say, during the execution of the task, if the terminal device 110 determines that it is necessary to collect some additional task information from the user 140 (such as supplementary constraints, description of the expected structure, addition of missing subtasks, etc.), it may put the task in a paused state. In some embodiments, if the terminal device 110 receives the auxiliary information, it may resume the execution of the third subtask. In some embodiments, if the terminal device 110 determines that it is necessary to collect some additional task information from the user 140, it may provide the user 140 with an interaction element 231 for obtaining the auxiliary information (i.e., additional task information). In some embodiments, the interaction element 231 may present information in an input box to guide the user 140 to input. After the user 140 confirms the input auxiliary information, the execution of the task is resumed. In some embodiments, the terminal device 110 may also present a prompt message 262 in the interface associated with the interaction element 231 (such as an "input box") to prompt the user 140 that they can input their required information in the interaction element 231 (such as an "input box").

[0063] In some embodiments, if the terminal device 110 receives the auxiliary information via the first interaction element, it may resume the execution of the third subtask. Correspondingly, the terminal device 110 may present second information related to the execution process or execution result of the task in the interface, where the second information is determined based on the auxiliary information and the first information. As Figure 2F shown, the user 140 may input the required information of the user 140 in the interaction element 231 (such as an "input box") presented in the interface (such as the example interface 200F) to resume the execution of the subtask 261. If the terminal device 110 receives the auxiliary information input by the user 140, it may use the agent 160 to generate second information based on the auxiliary information input by the user 140 and the information of the task process that has been executed or the information of the execution result that has been generated for the current task. Correspondingly, the terminal device 110 may continue to present the second information in the interface. Thus, the terminal device 110 may interrupt the execution of the task, allowing the user to choose to adjust or resume the execution of the task, so as to provide the user with a result that meets their own needs.

[0064] During the execution of the task, the execution of some subtasks included in the task may require access rights to an information source. In such a scenario, the terminal device 110 may pause the execution of the task and provide an entry for authorization to the user 140. The following refers to Figure 2G to describe the task interaction in such a scenario.

[0065] Referring to Figure 2G In the example interface 200G shown, during the execution of a task, if the terminal device 110 determines that the first subtask (e.g., subtask 271) among at least one subtask requires access permission to an information source, it may determine that the suspension condition of the task is satisfied, thereby suspending the execution of the task. That is, during the execution of the task, if the terminal device 110 determines that subtask 271 requires access permission to the information source, then it may suspend the execution of the task. In such a scenario, the terminal device 110 may present an interaction element 231 (e.g., "Take over immediately" control) and an interaction element 252 (e.g., "Skip" control) in the interface (such as the example interface 200G). The interaction element 231 (e.g., "Take over immediately" control) may be an entry for authorizing access to the information source.

[0066] In some embodiments, if the terminal device 110 receives an access authorization for the information source to be accessed, it may resume the execution of the first subtask. In some embodiments, if the terminal device 110 receives a trigger for the interaction element 231 (e.g., "Take over immediately" control), it may present a configuration panel. The configuration panel may receive an access authorization for the information source to be accessed as additional task information. In some examples, the user 140 may authorize the terminal device 110 to access the information source through the configuration panel. For example, the user 140 may authorize by scanning a predetermined code corresponding to the information source, by entering a mobile phone number, etc. However, these are merely exemplary, and the present disclosure does not limit this.

[0067] Further, if the terminal device 110 receives an access authorization via the configuration panel, it may resume the execution of the first task. Correspondingly, the terminal device 110 may present second information related to the execution process or execution result of the resumed task in the interface, where the second information is determined based on the information obtained from the information source and the first information. As Figure 2G shown, the user 140 may click on the interaction element 231 (e.g., "Take over immediately") to authorize access to the information source, so as to resume the execution of subtask 271. If the terminal device 110 determines that the user 140 has authorized access to the information source, it may use the agent 160 to generate second information based on the information obtained from the information source and the information of the task process that has been executed or the execution result information that has been generated for the current task. Correspondingly, the terminal device 110 may continue to present the second information in the interface.

[0068] In some embodiments, if the terminal device 110 receives a resume of a task in a paused state of the task, it may skip the execution of the first subtask and continue to execute the second subtask after the first subtask. In some embodiments, if the terminal device 110 receives a trigger from the user 140 on the interaction element 252 (e.g., the "skip" control), it may skip the execution of the first subtask. Accordingly, the terminal device 110 continues to execute the second subtask after the first subtask. As Figure 2G shown in the example interface 200G, if the user 140 clicks on the interaction element 252 (e.g., the "skip" control), the terminal device 110 may be caused to skip the execution of the subtask 271 and continue to execute the subtask subsequent to the subtask 271.

[0069] In some embodiments, if the terminal device 110 receives a trigger from the user 140 on the interaction element 252 (e.g., the "skip" control), it may also resume the execution of the task. That is, in the case where information authorization cannot be obtained, some or all of the steps of the first subtask may need to be skipped. At this time, after resuming the execution of the task, the second subtask after the first subtask can be continued. The second information presented in the interface is generated by the agent based on the previous first information and the execution of the second subtask. In some embodiments, if the terminal device 110 determines that the execution of a subtask requires access rights to an information source, it may present a prompt message 272 for prompting the user to confirm authorization in the interface (such as the example interface 200G). Thus, during the execution of the task, the agent can call some other information sources that the user has authorized, thereby improving the accuracy of the result.

[0070] In the case where the execution duration of the task and the subtasks of the task exceeds the duration threshold, the terminal device 110 may also put the task in a paused state. The following continues to refer to Figures 2H to 2I to describe the task interaction process in this case.

[0071] In some embodiments, if the terminal device 110 determines that the execution duration of the fourth subtask in at least one subtask is greater than the first duration threshold, it may determine that the pause condition of the task is satisfied, thereby pausing the execution of the task. Accordingly, the terminal device 110 may present a second interaction element and a third interaction element in the interface, where the third interaction element is configured to trigger the stop of the execution of the task. As Figure 2H shown in the example interface 200H, if the terminal device 110 determines that the execution duration of the fourth subtask (e.g., the XX subtask) is greater than the first duration threshold (e.g., 30 minutes or any other appropriate duration threshold), it may put the task in a paused state.

[0072] In such a scenario, the terminal device 110 may present an interaction element 252 (e.g., a "Continue" control) in an interface (such as the example interface 200H) for resuming the execution of a task. The terminal device 110 may present an interaction element 251 (e.g., a "Terminate" control) in an interface (such as the example interface 200H) for triggering the stop of the execution of a task. In some embodiments, the terminal device 110 may also present a prompt message 281 in the interface (such as the example interface 200H) for prompting the user 140 that the execution of the current task exceeds a duration threshold. In some embodiments, if the terminal device 110 receives a trigger to stop a task, it may stop the execution of the task. In some embodiments, if the terminal device 110 receives a trigger for a third interaction element, it may stop the execution of the task. That is, the user 140 may click on the interaction element 251 (e.g., the "Terminate" control) to stop the execution of the task.

[0073] In some embodiments, if the terminal device 110 receives a resume for a task in a paused state, it may resume the execution of the task to continue executing a fourth subtask or start a fifth subtask after the fourth subtask. In some embodiments, if the terminal device 110 receives a trigger for a second interaction element, it may resume the execution of the task to continue executing a fourth subtask or start a fifth subtask after the fourth subtask. Accordingly, the second information presented by the terminal device 110 in the interface is determined based on the execution process or execution result of the fourth subtask or the fifth subtask. As Figure 2H shown, the user 140 may click on the interaction element 252 (e.g., the "Continue" control) to resume the execution of the task. That is, if the terminal device 110 receives the user 140 clicking on the interaction element 252 (e.g., the "Continue" control), it may continue to execute the fourth subtask. Alternatively, if the terminal device 110 receives the user 140 clicking on the interaction element 252 (e.g., the "Continue" control), it may execute the subtask after the fourth subtask. If the terminal device 110 receives the user 140 clicking on the interaction element 252 (e.g., the "Continue" control), it may use the agent 160 to generate second information based on the information of the task process that has been executed for the current task or the information of the execution result that has been generated. Accordingly, the terminal device 110 may continue to present the second information in the interface.

[0074] In some embodiments, if the terminal device 110 determines that the total execution duration of a task is greater than a second duration threshold, it stops the execution of the task. In some embodiments, if the terminal device 110 determines that the total execution duration of a task is greater than a second duration threshold, it may present a sixth interaction element in the interface, where the sixth interaction element is used to trigger the start of a new task with the agent. As Figure 2IIn the example interface 200I shown, if the terminal device 110 determines that the total execution duration of the task is greater than the second duration threshold (e.g., 1.5 hours or any other appropriate duration threshold), the task can be put on hold. In such a scenario, the terminal device 110 can present an interaction element 291 (e.g., an "initiate new task" control) in the interface (such as the example interface 200I) for initiating a new task with the agent 160.

[0075] In some embodiments, if the terminal device 110 determines that the total execution duration of the task is greater than the second duration threshold, it can present a prompt message in the interface for prompting the initiation of a new task. As Figure 2I shown in the example interface 200I, the terminal device 110 can present a prompt message 292 in the interface (such as the example interface 200I) to prompt the user 140 that a new task with the agent 160 can be initiated.

[0076] In summary, through the present disclosure, the process and result of task execution can be presented in the interface for interacting with the agent, so that the user can learn about the disassembly process and execution process of the task by the agent. Further, during the execution of the task, the agent can call some other information sources authorized by the user, thereby improving the accuracy of the result. In this way, during the execution of the task, the disassembly or execution of the task can be interrupted, adjusted, or resumed at any time, so as to provide a result that meets the user's needs.

[0077] Figure 3 FIG. shows a flowchart of a process 300 for task interaction according to some embodiments of the present disclosure. The process 300 can be implemented at the terminal device 110. The following refers to Figure 1 describe the process 300.

[0078] In block 310, in response to a request for a task of the agent, the terminal device 110 presents first information related to the execution process of the task in the interface for interacting with the agent, and the request indicates the task information of the task.

[0079] In block 320, in response to the suspension condition of the task being satisfied, the terminal device 110 suspends the execution of the task.

[0080] In block 330, in response to receiving an adjustment or resume of the task in the suspended state of the task, the terminal device 110 resumes the execution of the task, where second information related to the execution process or execution result of the resumed task is presented in the interface.

[0081] In some embodiments, the process 300 further includes: in response to the suspension condition of the task being satisfied, presenting at least one interaction element in the interface, and the at least one interaction element is at least configured to adjust or resume the task in the suspended state of the task.

[0082] In some embodiments, at least one interaction element includes at least one of the following: a first interaction element for triggering an adjustment to the task information of a task in a paused state of the task, or a second interaction element for triggering the resumption of the execution of the task in a paused state of the task.

[0083] In some embodiments, during the execution of a task, the interface includes a pause control, and causing the execution of the task to be paused includes: pausing the execution of the task in response to a trigger of the pause control.

[0084] In some embodiments, resuming the execution of the task includes: resuming the execution of the task in response to receiving an adjustment to the task information, wherein a second piece of information is determined based on the adjustment to the task information and a first piece of information.

[0085] In some embodiments, a task includes at least one subtask, and wherein causing the execution of the task to be paused in the interface includes: during the execution of the task, pausing the execution of the task in response to a first subtask among the at least one subtask requiring access rights to an information source.

[0086] In some embodiments, resuming the execution of the task includes: resuming the execution of the first subtask in response to receiving an access authorization to the information source to be accessed, wherein a second piece of information is determined based on the information obtained from the information source and the first piece of information.

[0087] In some embodiments, resuming the execution of the task further includes: in response to receiving a resume of the task in a paused state of the task, skipping the execution of the first subtask and continuing to execute a second subtask after the first subtask.

[0088] In some embodiments, a task includes at least one subtask, and wherein causing the execution of the task to be paused includes: during the execution of the task, determining that the pause condition of the task is satisfied and pausing the execution of the task in response to a third subtask among the at least one subtask requiring auxiliary information.

[0089] In some embodiments, resuming the execution of the task includes: resuming the execution of the third subtask in response to receiving the input auxiliary information, wherein a second piece of information is determined based on the auxiliary information and the first piece of information.

[0090] In some embodiments, process 300 further includes: presenting a prompt message associated with the first interaction element in the interface, the prompt message indicating the need for auxiliary information.

[0091] In some embodiments, a task includes at least one subtask, and causing the execution of the task to be paused includes: pausing the execution of the task in response to the execution duration of a fourth subtask among the at least one subtask being greater than a first duration threshold.

[0092] In some embodiments, the execution of the restoration task includes: in response to receiving a restoration of the task in a paused state of the task, resuming the execution of the task to continue executing the fourth subtask or starting the fifth subtask after the fourth subtask, where the second information is determined based on the execution process or execution result of the fourth subtask or the fifth subtask.

[0093] In some embodiments, process 300 further includes: in response to receiving a trigger to stop the task, stopping the execution of the task.

[0094] In some embodiments, causing the execution of the task to be paused includes: in response to generating a task plan for the task, causing the execution of the task to be paused, and presenting task information of at least one subtask indicated by the task plan in the interface.

[0095] In some embodiments, process 300 further includes: in response to the total execution duration of the task being greater than the second duration threshold, stopping the execution of the task; and presenting prompt information for prompting to start a new task in the interface.

[0096] Embodiments of the present disclosure also provide a corresponding apparatus for implementing the above method or process.

[0097] Figure 4 A schematic structural block diagram of an apparatus 400 for task interaction according to certain embodiments of the present disclosure is shown. Apparatus 400 may be implemented as or included in a terminal device 110. Each module / component in apparatus 400 may be implemented by hardware, software, firmware, or any combination thereof.

[0098] As Figure 4 shown, apparatus 400 includes a first information presentation module 410, configured to present first information related to the execution process of the task in an interface for interacting with an agent in response to a request for the task of the agent, where the request indicates the task information of the task. Apparatus 400 further includes an execution pause module 420, configured to cause the execution of the task to be paused in response to the pause condition of the task being satisfied. Apparatus 400 further includes an execution restoration module 430, configured to resume the execution of the task in response to receiving an adjustment or restoration of the task in a paused state of the task, where second information related to the execution process or execution result of the restored task is presented in the interface.

[0099] In some embodiments, process 300 further includes: in response to the pause condition of the task being satisfied, presenting at least one interaction element in the interface, where the at least one interaction element is at least configured to adjust or restore the task in a paused state of the task.

[0100] In some embodiments, at least one interactive element includes at least one of the following: a first interactive element for triggering an adjustment to the task information of a task in a paused state of the task, or a second interactive element for triggering the resumption of the execution of the task in a paused state of the task.

[0101] In some embodiments, during the execution of a task, the interface includes a pause control, and the execution pause module 420 is further configured to pause the execution of the task in response to the triggering of the pause control.

[0102] In some embodiments, the execution resume module 430 is further configured to resume the execution of the task in response to receiving an adjustment to the task information, wherein the second information is determined based on the adjustment to the task information and the first information.

[0103] In some embodiments, the task includes at least one subtask, and the execution pause module 420 is further configured to pause the execution of the task during the execution of the task in response to the first subtask in at least one subtask requiring access rights to an information source.

[0104] In some embodiments, the execution resume module 430 is further configured to resume the execution of the first subtask in response to receiving an access authorization to the information source to be accessed, wherein the second information is determined based on the information obtained from the information source and the first information.

[0105] In some embodiments, the execution resume module 430 is further configured to skip the execution of the first subtask and continue to execute the second subtask after the first subtask in response to receiving a resume of the task in a paused state of the task.

[0106] In some embodiments, the task includes at least one subtask, and the execution pause module 420 is further configured to determine that the pause condition of the task is satisfied and pause the execution of the task during the execution of the task in response to the third subtask in at least one subtask requiring auxiliary information.

[0107] In some embodiments, the execution resume module 430 is further configured to resume the execution of the third subtask in response to receiving the input auxiliary information, wherein the second information is determined based on the auxiliary information and the first information.

[0108] In some embodiments, the device 400 further includes a prompt information presentation module configured to present prompt information associated with the first interactive element in the interface, and the prompt information indicates the need for auxiliary information.

[0109] In some embodiments, the task includes at least one subtask, and the execution pause module 420 is further configured to determine that the pause condition of the task is satisfied and pause the execution of the task in response to the execution duration of the fourth subtask in the at least one subtask being greater than the first duration threshold.

[0110] In some embodiments, the execution resume module 430 is further configured to resume the execution of the task to continue executing the fourth subtask or start the fifth subtask after the fourth subtask in response to receiving a trigger to resume the task in the paused state of the task, where the second information is determined based on the execution process or execution result of the fourth subtask or the fifth subtask.

[0111] In some embodiments, the device 400 further includes an execution stop module configured to stop the execution of the task in response to receiving a trigger to stop the task.

[0112] In some embodiments, the execution pause module 420 is further configured to pause the execution of the task in response to the generation of the task plan of the task, and present the task information of at least one subtask indicated by the task plan on the interface.

[0113] In some embodiments, the prompt information presentation module is further configured to stop the execution of the task in response to the total execution duration of the task being greater than the second duration threshold; and present prompt information for prompting to start a new task on the interface.

[0114] The units and / or modules included in the device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units and / or modules can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to the machine-executable instructions, some or all of the units and / or modules in the device 400 can be at least partially implemented by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system on chips (SOCs), complex programmable logic devices (CPLDs), and so on.

[0115] It should be understood that one or more steps in the above methods can be performed by an appropriate electronic device or a combination of electronic devices. Such an electronic device or a combination of electronic devices can include, for example Figure 1 the terminal device 110 and the server 130 in

[0116] Figure 5 The block diagram of an electronic device 500 in which one or more embodiments of the present disclosure can be implemented is shown. It should be understood, Figure 5The illustrated electronic device 500 is merely exemplary and should not impose any limitation on the functionality and scope of the embodiments described herein. Figure 5 The illustrated electronic device 500 can be used to implement Figure 1 the terminal device 110 or the server 130.

[0117] As Figure 5 illustrated, the electronic device 500 is in the form of a general-purpose electronic device. The components of the electronic device 500 can include, but are not limited to, one or more processing units or processors 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 570 can be an actual or virtual processor and is capable of performing various processes according to the programs stored in the memory 520. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing ability of the electronic device 500.

[0118] The electronic device 500 generally includes multiple computer storage media. Such media can be any available media accessible to the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 can be a volatile memory (such as registers, caches, random access memory (RAM)), a non-volatile memory (such as read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 can be a removable or non-removable medium and can include machine-readable media, such as a flash drive, a magnetic disk, or any other medium that can be used to store information and / or data and can be accessed within the electronic device 500.

[0119] The electronic device 500 can further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in Figure 5 it, a disk drive for reading from or writing to a removable, non-volatile magnetic disk (such as a "floppy disk") and an optical disk drive for reading from or writing to a removable, non-volatile optical disk can be provided. In these cases, each drive can be connected to a bus (not shown) by one or more data media interfaces. The memory 520 can include a computer program product 525 having one or more program modules that are configured to perform the various methods or actions of the various embodiments of the present disclosure.

[0120] The communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 500 can be implemented with a single computing cluster or multiple computing machines that are capable of communicating via a communication connection. Accordingly, the electronic device 500 can operate in a networked environment using a logical connection to one or more other servers, network personal computers (PCs), or another network node.

[0121] The input device 550 can be one or more input devices such as a mouse, keyboard, trackball, etc. The output device 560 can be one or more output devices such as a display, speakers, printer, etc. The electronic device 500 can also communicate with one or more external devices (not shown) as needed via the communication unit 540, such as storage devices, display devices, etc., communicate with one or more devices that enable a user to interact with the electronic device 500, or communicate with any device that enables the electronic device 500 to communicate with one or more other electronic devices (e.g., network cards, modems, etc.). Such communication can be performed via an input / output (I / O) interface (not shown).

[0122] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, where the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, the computer program product being tangibly stored on a non-transitory computer-readable medium and including computer-executable instructions, and the computer-executable instructions being executed by a processor to implement the method described above.

[0123] Aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0124] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, thereby producing a machine such that when the instructions are executed by the processing unit of the computer or other programmable data processing apparatus, a device is produced that implements the functions / acts specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, which instructions cause a computer, a programmable data processing apparatus, and / or other devices to operate in a particular manner, so that the computer-readable medium storing the instructions includes a manufacture that includes instructions for implementing various aspects of the functions / acts specified in one or more blocks of the flowchart and / or block diagram.

[0125] Computer-readable program instructions may be loaded onto a computer, other programmable data processing apparatus, or other device, causing a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, such that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in one or more boxes of the flowchart and / or block diagram.

[0126] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various implementations of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two consecutive blocks may in fact be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block of the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or by combinations of special purpose hardware and computer instructions.

[0127] The various implementations of the present disclosure have been described above. The above description is exemplary, not exhaustive, and is not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The choice of terms used herein is intended to best explain the principles of the implementations, the practical application, or improvement of the technology in the marketplace, or to enable other ordinary skill in the art to understand the various implementations disclosed herein.

Claims

1. A method for task interaction, comprising: In response to a request for a task of an agent, presenting first information related to the execution process of the task in an interface for interacting with the agent, the request indicating task information of the task; In response to the suspension condition of the task being satisfied, suspending the execution of the task; And In response to receiving an adjustment or resume of the task in the suspended state of the task, resuming the execution of the task, wherein second information related to the execution process or execution result of the resumed task is presented in the interface.

2. The method according to claim 1, further comprising: In response to the suspension condition of the task being satisfied, presenting at least one interaction element in the interface, the at least one interaction element being at least configured to adjust or resume the task in the suspended state of the task.

3. The method according to claim 2, wherein the at least one interaction element includes at least one of the following: A first interaction element for triggering an adjustment of the task information of the task in the suspended state of the task, or A second interaction element for triggering resuming the execution of the task in the suspended state of the task.

4. The method according to claim 1, wherein during the execution process of the task, the interface includes a suspension control, and suspending the execution of the task includes: In response to triggering of the suspension control, suspending the execution of the task.

5. The method according to claim 1, wherein resuming the execution of the task includes: In response to receiving an adjustment of the task information, Resuming the execution of the task, wherein the second information is determined based on the adjustment of the task information and the first information.

6. The method according to claim 1, wherein the task includes at least one subtask, and suspending the execution of the task includes: During the execution process of the task, in response to the first subtask among the at least one subtask requiring access rights to an information source, suspending the execution of the task.

7. The method according to claim 6, wherein resuming the execution of the task includes: In response to receiving an access authorization for the information source to be accessed, resuming the execution of the first subtask, Wherein the second information is determined based on the information obtained from the information source and the first information.

8. The method according to claim 7, wherein resuming the execution of the task further includes: In response to receiving a resume of the task in the suspended state of the task, Skipping the execution of the first subtask, and Continuing to execute the second subtask after the first subtask.

9. The method according to claim 1, wherein the task includes at least one subtask, and suspending the execution of the task includes: During the execution process of the task, in response to the third subtask among the at least one subtask requiring auxiliary information, suspending the execution of the task.

10. The method according to claim 9, wherein resuming the execution of the task includes: In response to receiving the auxiliary information, resume the execution of the third subtask, where the second information is determined based on the auxiliary information and the first information.

11. The method according to claim 9, further comprising: Presenting a prompt message associated with the first interaction element in the interface, the prompt message indicating the need for the auxiliary information.

12. The method according to claim 1, wherein the task includes at least one subtask, and pausing the execution of the task includes: In response to the execution duration of a fourth subtask in the at least one subtask being greater than a first duration threshold, pausing the execution of the task.

13. The method according to claim 12, wherein resuming the execution of the task includes: In response to receiving a resume of the task in the paused state of the task, resuming the execution of the task to continue executing the fourth subtask or start a fifth subtask after the fourth subtask, where the second information is determined based on the execution process or execution result of the fourth subtask or the fifth subtask.

14. The method according to claim 12, further comprising: In response to receiving a trigger to stop the task, stopping the execution of the task.

15. The method according to claim 1, wherein pausing the execution of the task includes: In response to the generation of a task plan for the task, pausing the execution of the task, and presenting task information of at least one subtask indicated by the task plan in the interface.

16. The method according to claim 1, further comprising: In response to the total execution duration of the task being greater than a second duration threshold, stopping the execution of the task, and presenting a prompt message for prompting to start a new task in the interface.

17. An apparatus for task interaction, comprising: A first information presentation module configured to, in response to a request for a task of an agent, present first information related to the execution process of the task in an interface for interacting with the agent, the request indicating the task information of the task; An execution pause module configured to, in response to the pause condition of the task being satisfied, pause the execution of the task; And An execution resume module configured to, in response to receiving an adjustment or resume of the task in the paused state of the task, resume the execution of the task, where second information related to the execution process or execution result of the resumed task is presented in the interface.

18. An electronic device, comprising: At least one processor; And At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions, when executed by the at least one processor, cause the electronic device to execute the method according to any one of claims 1 to 16.

19. A computer-readable storage medium having computer-executable instructions stored thereon, the computer-executable instructions being executable by a processor to implement the method according to any one of claims 1 to 16.

20. A computer program product comprising computer-executable instructions which, when executed by a processor, implement the method according to any one of claims 1 to 16.

Images