Method, device, equipment and program product for interface interaction

Abstract

A method, apparatus, device, and program product for interface interaction are provided. The method includes: receiving a first input on a first interface, the first input triggering an intelligent system to execute a first task, the first task being used to perform an operation associated with a service; in response to the first task satisfying a triggering condition, presenting a first interactive component on the first interface, the type of the first interactive component being associated with the first task; receiving a second input through the first interactive component, the second input being associated with a service; and presenting first content, the first content indicating the execution of the first task based on the second input. This approach can improve the efficiency of interface interaction.

Description

Technical Field

[0001] The examples in this article generally relate to the field of computer science, and in particular to methods, apparatuses, devices, and computer program products for user interface interaction. Background Technology

[0002] With the development of computer technology, users can access services provided by service platforms. Typically, users can configure services on these platforms, requiring them to navigate between multiple graphical user interfaces and manually configure each service step by step. Furthermore, data queries, maintenance operations, and write operations are scattered across different interface entry points. Some users hope to improve the efficiency of service configuration. Summary of the Invention

[0003] In a first aspect of this document, a method for interface interaction is provided. The method includes: receiving a first input on a first interface, the first input triggering an intelligent system to execute a first task, the first task being used to perform an operation associated with a service; in response to the first task satisfying a triggering condition, presenting a first interactive component on the first interface, the type of the first interactive component being associated with the first task; receiving a second input through the first interactive component, the second input being associated with a service; and presenting first content, the first content indicating that the first task is executed based on the second input.

[0004] In a second aspect of this document, an apparatus for interface interaction is provided. The apparatus includes: a first receiving module configured to receive a first input on a first interface, the first input triggering an intelligent system to execute a first task, the first task being used to perform an operation associated with a service; a first presenting module configured to present a first interactive component on the first interface in response to the first task satisfying a triggering condition, the type of the first interactive component being associated with the first task; a second receiving module configured to receive a second input through the first interactive component, the second input being associated with a service; and a second presenting module configured to present first content, the first content indicating the execution of the first task based on the second input.

[0005] In a third aspect of this document, an electronic device is provided. The device includes 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. When executed by the at least one processor, the instructions cause the device to perform the method of the first aspect.

[0006] In a fourth aspect of this document, a computer program product is provided, which is tangibly stored in a computer storage medium and includes computer-executable instructions that, when executed by a device, cause the device to perform the method of the first aspect.

[0007] In this way, some examples in this paper can replace page-by-page navigation and manual configuration between multiple interfaces with interaction between the user and the intelligent system. User feedback can be obtained through interactive components during task execution, thereby reducing the number of interface navigations and operation steps required to complete the task, improving the efficiency of configuration services, and improving the efficiency of interface interaction.

[0008] It should be understood that the content described in this section is not intended to limit the key or important features of the examples in this article, nor is it intended to restrict the scope of the solution. Other features will become readily apparent from the following description. Attached Figure Description

[0009] The above and other features, advantages, and aspects of the various examples herein will become more apparent when taken in conjunction with the accompanying drawings and the following detailed description. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein: Figure 1 A schematic diagram of the example environment is shown; Figures 2A to 2K Example interfaces are shown based on some scenarios; Figure 3 The flowcharts show some methods for interface interaction in various scenarios; Figure 4 Block diagrams of devices for interface interaction in several scenarios are shown; and Figure 5 A block diagram of an electronic device capable of implementing multiple illustrative scenarios is shown. Detailed Implementation

[0010] The examples in the text will now be described in more detail with reference to the accompanying drawings. While some examples are shown in the drawings, it should be understood that solutions can be implemented in various forms and should not be construed as limited to the examples presented herein. Rather, these examples are provided to provide a more thorough and complete understanding of the solutions. It should be understood that the drawings and examples in this document are for illustrative purposes only and are not intended to limit the scope of protection of the solutions.

[0011] It should be noted that the headings of any section / subsection provided herein are not restrictive. Various examples are described throughout this document, and examples of any type may be included under any section / subsection. Furthermore, examples described in any section / subsection may be combined in any way with any other examples described in the same section / subsection and / or different sections / subsections.

[0012] In the description of the examples in this document, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an example" or "the example" should be understood as "at least one example". The term "some examples" should be understood as "at least some examples". Other explicit and implicit definitions may also be included below. The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0013] The examples in this article may involve user data, data acquisition, and / or use. All of these aspects comply with relevant laws, regulations, and rules. In the examples, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, when implementing each example, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained through appropriate means, in accordance with relevant laws and regulations. The specific methods of notification and / or authorization can vary depending on the actual situation and application scenario; the scope of the solution is not limited in this regard.

[0014] In this manual and the sample solutions, any processing of personal information will be conducted only under legal grounds (such as obtaining the consent of the data subject or being necessary for the performance of a contract) and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.

[0015] As used in this document, the term "intelligent system" refers to a system capable of autonomous control based on machine learning models. An intelligent system is, for example, a virtual object or physical entity that can make decisions and autonomously execute actions based on machine learning models to achieve preset goals or complete preset tasks. An intelligent system can be an automated program that understands user intent and can utilize models or invoke tools to complete various types of tasks. In some contexts, examples of intelligent systems may include, but are not limited to: agents, bots, chatbots, digital avatars, intelligent customer service, digital assistants, etc. Alternatively, an intelligent system can also be an intelligent role implemented based on machine learning models. An "intelligent system" can process user requests based on generative models (e.g., language models, multimodal models) to perform specified types of tasks. In some cases, an intelligent system may also relate to virtual accounts, which may have corresponding avatars or nicknames.

[0016] The term "natural language" as used in this article refers to input expressed by users in everyday language, which may not follow a preset fixed format, and may include, but is not limited to, text, speech-to-text, etc.

[0017] The term "token" as used in this article refers to the basic unit into which natural language text is divided when it is processed by the model. It may include, but is not limited to, the segmentation results of characters, sub-words, words, or punctuation marks.

[0018] The term "Model as a Service (MaaS)" used in this article refers to the way that provides model-related capabilities to users in the form of a service. The corresponding service platform can provide capabilities such as model activation, invocation, access configuration, usage and cost query, and running status viewing.

[0019] The term "first interface" as used in this article refers to the interface presented by an electronic device to a user for human-computer interaction, which may include, but is not limited to, a dialogue interface, a dialogue homepage, and a dialogue sidebar embedded in other interfaces; the first interface may include a first area for displaying the conversation with the intelligent system, and a second area for displaying content such as task status.

[0020] The term "service" as used in this article refers to functions or resources that can be operated or queried by an intelligent system, typically including but not limited to model-related calling capabilities, creation and configuration of service interfaces or access points related to services, querying of usage and costs, diagnosis and troubleshooting of runtime errors, etc.

[0021] The term "task" as used in this article refers to a task performed by an intelligent system, which can be triggered by user input or based on task execution. Tasks may include, but are not limited to, platform access, service interface creation, access point creation, usage and cost querying, and error troubleshooting. One or more tasks can be executed asynchronously by the intelligent system.

[0022] The term "triggering condition" as used in this article refers to the conditions that must be met for the intelligent system to present the first interactive component on the first interface. These conditions may include, but are not limited to, situations where the execution of the first task depends on user input or where the first task involves operations that require user approval or authorization.

[0023] As used in this document, the term "interactive component" refers to a visual interactive component presented on the first interface for obtaining user feedback during the execution of the first task. Its types may include, but are not limited to: clarification components for obtaining supplementary information from the user when necessary for execution is lacking; confirmation components for obtaining user approval when all parameters are available; and authorization components for obtaining user authorization when performing high-impact or irreversible operations. Additionally, the first interactive component and the second interactive component may be different interactive components, which may be presented together on the first interface, for example, through tiling, stacking, or other styles.

[0024] As used herein, the term "first content item" refers to an interface element used to indicate the execution status of a first task, which may include, but is not limited to, a task panel used to present the task name and its execution process. The first content item may be presented in a second area of ​​the first interface, rather than in the session area with the intelligent system (i.e., the first area). The first content item may be dynamically updated during the execution of the first task to display in real time the steps or outputs currently being performed by the first task.

[0025] As used herein, the terms "first content," "second content," and "third content" refer to: the content instructing the first task to be performed based on the second input; the content associated with the service's permissions and presented via the first interactive component; and the content obtained by performing the first task and presented in the first area after the first task is completed. The content, including but not limited to text, images, and files, can be presented, for example, through structured content cards.

[0026] As used in this document, the term "permission" refers to the right granted to an intelligent system to perform operations associated with a service. Permissions may include, but are not limited to: first permission for obtaining parameter information related to the service, second permission for creating service interfaces related to the service, and third permission for editing at least one configuration piece of information related to the service.

[0027] As used herein, the term "supplementary information" refers to supplementary information provided in connection with the first task for the purpose of performing the first task, and may include, but is not limited to, at least one parameter used to configure the service. Parameters used to configure the service may include, but are not limited to, first configuration parameters indicating the model associated with the service, and second configuration parameters indicating the access method of the service.

[0028] The term "stacked style" as used in this article refers to a style in which multiple interactive components are presented on top of each other on a first interface. In this style, the interactive component in front can obscure at least part of the interactive components behind it, and the multiple interactive components can be switched back and forth through specified operations.

[0029] As mentioned above, with the development of computer technology, users can access services provided by service platforms. Typically, users can configure services on these platforms, requiring them to navigate between multiple graphical user interfaces and manually configure each service step by step. Furthermore, data queries, maintenance operations, and write operations are scattered across different interface entry points. Some users hope to improve the efficiency of service configuration.

[0030] This paper proposes a user interface interaction scheme. The scheme includes: receiving a first input on a first interface, the first input triggering an intelligent system to execute a first task, the first task being used to perform an operation associated with a service; responding to the first task meeting a triggering condition, presenting a first interactive component on the first interface, the type of the first interactive component being associated with the first task; receiving a second input through the first interactive component, the second input being associated with a service; and presenting first content, the first content indicating that the first task should be executed based on the second input.

[0031] Through the above solutions, some examples in this paper can replace page-by-page navigation and manual configuration between multiple interfaces with interaction between the user and the intelligent system. Furthermore, user feedback can be obtained through interactive components during task execution, thereby reducing the number of interface navigations and operation steps required to complete the task, improving the efficiency of configuration services, and enhancing the efficiency of interface interaction.

[0032] The following describes various examples of this scheme in further detail with reference to the accompanying drawings.

[0033] Figure 1 A schematic diagram of example environment 100 is shown. (e.g.) Figure 1 As shown, the example environment 100 may include an electronic device 110.

[0034] In example environment 100, electronic device 110 can run application 120 that supports user interface interaction. Application 120 can be any suitable type of application for implementing user interface interaction. Application 120 can, for example, be used to configure services in a service platform, and user 140 can interact with application 120 via electronic device 110 and / or its attached devices.

[0035] exist Figure 1 In environment 100, if application 120 is active, electronic device 110 can present interface 150 to support user interface interaction through application 120. For example, electronic device 110 can present messages, entries, lists, and interactive components through interface 150, and receive input from user 140 through interface 150.

[0036] In some cases, electronic device 110 communicates with server 130 to provide services to application 120. Electronic 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, handheld computers, portable gaming terminals, VR / AR devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio 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 cases, electronic device 110 can also support any type of user-facing interface (such as "wearable" circuitry).

[0037] Server 130 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for applications 120 that support user interface interaction in electronic devices 110.

[0038] A communication connection can be established between server 130 and electronic device 110. This communication connection can be established via wired or wireless means. The communication connection can include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections. In some cases, server 130 and electronic device 110 can exchange signaling information through their communication connection.

[0039] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the scheme.

[0040] The following description of the example will continue with reference to the accompanying drawings.

[0041] Figures 2A to 2KExample interfaces 200A to 200K are shown, illustrating interface interactions under various scenarios. Interfaces 200A to 200K can, for example, be... Figure 1 The electronic device 110 shown is provided by application 120.

[0042] In some situations, electronic device 110 may present as follows Figure 2A The interface 200A shown may include an interface for user interaction. As an example, such an interface 200A may be an implementation of a first interface, which may be associated with an intelligent system and used to interact with the intelligent system. For example, the first interface may support conversational or graphical interaction between the user and the intelligent system, etc. As an example, such as... Figure 2A As shown, interface 200A may include a first area for displaying the conversation between user 140 and the intelligent system, and an input component 202 for receiving input.

[0043] like Figure 2A As shown, the electronic device 110 can receive a first input 212-1 in the interface 200A, and the first input 212-1 can be natural language input (in the form of...). Figure 2A (Taking the question "I want to start calling the platform's model, how do I access it?" as an example). The first input 212-1 can trigger the intelligent system to execute a first task, which can be used to perform operations associated with the service. Additionally, in response to receiving the first input 212-1, the electronic device 110 can present a first message 214-1 from the intelligent system related to the first task in a first area. Figure 2A (For example, "Okay, I'll walk you through the entire platform integration process... First, let me check your account status.")

[0044] In some cases, when creating a first task, the electronic device 110 can display a first content item 222 on a first interface, the first content item 222 indicating the execution status of the first task. For example... Figure 2A As shown, the first content item 222 can be displayed in the "Tasks in Progress" panel, which may include, for example, the task name 222-1 of the first task ( Figure 2A The middle section is for "New User Access Platform".

[0045] In some scenarios, electronic device 110 can present the execution process of the first task in a first content item 222, with the execution process dynamically updated based on the execution of the first task. For example, the first content item 222 may include the current execution node 222-2 (e.g., "Check inference service activation"), which can switch dynamically as the first task progresses. In this way, user 140 can be informed of the task's progress in real time while it is being executed asynchronously in the background, without having to wait or repeatedly query, thus reducing the extra operations required to obtain information about the task's progress.

[0046] In some cases, the first interface may include a first area and a second area, with the first area displaying the conversation with the intelligent system and the first content item 222 presented in the second area of ​​the first interface. For example... Figure 2A As shown, the first content item 222 can be displayed in a second area on one side of the conversation area, without obscuring the conversation history, and may not be counted in the conversation history. Alternatively or additionally, the electronic device 110 may stop displaying the first content item 222 after the first task is completed. For example, the first content item 222 may be automatically collapsed. In this way, the user 140 can continue to input or switch operations in the first area during task execution, and the presentation of the task status is independent of the conversation content. Furthermore, since the first content item 222 is displayed independently of the conversation area and may not be counted in the conversation history, the readability of the interface can be improved, and the context length in the conversation can be reduced.

[0047] In some cases, the first content item 222 may also include a stop control 222-3. The electronic device 110 may trigger termination of the first task in response to an operation on the stop control 222-3. Alternatively or additionally, the electronic device 110 may also stop presenting the corresponding first interactive component or trigger termination of the first task in response to not receiving a preset operation associated with the first interactive component within a preset time (e.g., automatically handling the task in a preset manner when the user does not provide feedback on the interactive component awaiting confirmation for an extended period; the preset manner could be, for example, automatically denying authorization, automatically denying reply information, etc.). In this way, the user 140 can stop tasks that are no longer needed at any time, and tasks that have not received feedback for a long time can also be automatically handled, preventing tasks from being suspended in the background for a long time and improving the utilization of computing resources.

[0048] In some embodiments, the first input 212-1 may originate from user input (e.g., input by the user through input component 202), or from the user's selection of preset candidate options. For example, according to Figure 2BAs shown in interface 200B, electronic device 110 can present candidate options 216-1 to 216-4 on the first interface. The content of candidate options 216-1 to 216-4 can be preset or matched to the user. For example, when a user interacts with the intelligent system for the first time, electronic device 110 can present candidate options 216-1 to 216-4 on the first interface, which can be randomly assigned or assigned based on preset rules. Alternatively, if the user has used the intelligent system before, according to... Figure 2C The interface 200C shown indicates that the electronic device 110 can display candidate options 218-1 to 218-8, which may be related to the user, for example, they may be associated with services that the user has configured or viewed. In this way, some examples in this paper can further improve service configuration efficiency.

[0049] In some situations, the primary task may require user assistance. According to... Figure 2D As shown in the interface 200D, when the first task is executed to the point where user confirmation is required, the electronic device 110 can present a first interactive component on the first interface to obtain user feedback.

[0050] As an example, such as Figure 2D As shown, the electronic device 110 can respond to the first task meeting the trigger condition by presenting a first interactive component 232 on a first interface. The type of the first interactive component 232 is associated with the first task. For example, the currently executing node in the first content item 222 can be updated to node 222-4, which indicates that the task is paused pending user confirmation. Figure 2D The middle part reads "Waiting for your confirmation of the interface configuration," indicating that the execution of the first task depends on user input.

[0051] In some situations, electronic device 110 may present first interactive component 232 on a first interface in response to the execution of a first task depending on user input. For example, the first task may require user authorization, require user-provided information, etc. Figure 2D As shown, the first task can be to create a service interface related to the service (e.g., to create an interface key for inference calls), and the first interaction component 232 can be a corresponding confirmation card. Figure 2D Taking "Your confirmation is required to create an interface" as an example, its type (confirmation / authorization class) corresponds to the first task.

[0052] In some scenarios, electronic device 110 can receive a second input via the first interaction component 232, the second input being associated with a service. As an example, electronic device 110 can present second content in the first interaction component 232, the second content being associated with permissions for a service. Additionally, electronic device 110 can receive a second input via the first interaction component 232, the second input being used to grant appropriate permissions to the intelligent system. Figure 2D As shown, the first interactive component 232 may present parameter information 232-1 (e.g., including name, permissions, project, validity period, etc., where the "permissions" item can be a second type of content associated with the service's permissions, such as "inference call (read-only)"). As an example, the user 140's triggering operation on the confirmation creation control 232-2 can be a second input, used to grant the intelligent system permission to create the service interface and confirm the execution of the operation. Alternatively or as an adjunct, the first interactive component 232 may also include a cancellation control 232-3, which the user can trigger to refuse authorization for the intelligent system to create the service interface.

[0053] In some cases, the aforementioned permissions may include at least one of the following: a first permission for obtaining service-related parameter information, a second permission for creating service-related service interfaces, and a third permission for editing at least one configuration piece of information related to the service. For example, Figure 2D The creation of the service interface shown corresponds to the situation of granting a second permission to the intelligent system.

[0054] In some scenarios, the first interaction component 232 can describe at least one operation associated with the service, while the second input indicates confirmation of performing that operation. That is, confirming the creation of control 232-2 can simultaneously confirm the execution of the described operation. In this way, the user 140 can grant the corresponding permissions and confirm the operation directly within the current conversation without needing to navigate to a dedicated permission or key management interface. This is only interrupted when the task truly requires feedback, reducing unnecessary interruptions and interface jumps, thereby further improving interface interaction efficiency.

[0055] In some cases, the first interactive component may also employ a step-by-step control presentation approach when collecting supplementary user information. As an example, the electronic device 110 may present a first control within the first interactive component for obtaining a first type of information, and obtain a first portion of the supplementary information through the first control. Additionally, the electronic device 110 may stop presenting the first control in the first interactive component and present a second control for obtaining a second type of information, obtaining a second portion of the supplementary information through the second control.

[0056] For example, when the requirements of the first task are vague (such as not specifying the target model, purpose, or whether to reuse existing access points), the intelligent system can generate several clarifying questions based on the gap between the first input and the information required to perform the task, and present them step by step with controls such as single selection, multiple selection, or text input, presenting one question at a time and displaying progress such as "current / total".

[0057] In some cases, after receiving user feedback through the first interaction component 232, the first task can continue to execute, and the execution node in the first content item 222 can be updated accordingly. See below for relevant examples. Figure 2E The example described.

[0058] like Figure 2E In the interface 200E shown, the currently executing node in the first content item 222 is updated to node 222-5. Figure 2E The middle section is for "Preparing Inference Access Point Configuration," compared to... Figure 2D Nodes 222-4 in the first content item 222 are further advanced. Thus, the execution node in the first content item 222 is accessed via... Figure 2A Node 222-2 in Figure 2D Node 222-4 in Figure 2E Nodes 222-5 in the table are updated sequentially, and the execution process in the first content item can be dynamically updated as the first task is executed. In this way, user 140 can continuously know the progress of the task without querying it one by one, thus helping the user to understand the execution progress of the first task more intuitively.

[0059] In some cases, electronic device 110 may, in response to the completion of the first task, stop displaying the first content item and display third content in the first area, the third content being obtained by performing the first task. For example... Figure 2F As shown in interface 200F, after the first task is completed, the task panel (first content item) can stop displaying, and electronic device 110 can display the third content 242 in the first area. Figure 2F (For example, "All done... Here is the ready-to-run calling code... Copy and use"). Alternatively or additionally, the third content 242 also indicates that the first task has been executed based on the second input.

[0060] In some cases, third-party content can be presented as structured content cards rather than plain text. For example... Figure 2F As shown, the third content 242 may include a result card 242-1 rendered in the form of a code block within the dialog bubble, which may carry a call example containing real parameters (such as the created service interface, access point identifier, and selected model, etc.) so that the user can use it directly without having to replace the placeholders.

[0061] Alternatively or additionally, for query-type tasks that typically do not require user confirmation, electronic device 110 may not present the first interactive component, but can directly provide the service content. As an example, such as... Figure 2G The interface shown is 200G, and the electronic device 110 receives the first input 212-2 ( Figure 2G The message reads "Please check if my recent usage is abnormal," and the first message 214-2 is displayed in the first area. Figure 2G The first task, which is "This will help you check the recent usage of lexical terms, please wait," can be performed without further user input and does not require meeting any triggering conditions.

[0062] Additionally, after the first query task is completed, the electronic device 110 presents the third content 244 in the first area. Figure 2G The first part, "Check complete. This week's usage increased compared to last week...", indicates that the first task has been completed and is presented as a structured result card. Alternatively or additionally, the result card may include graphs 244-1 (e.g., trend charts), lists 244-2, etc. It should be understood that the third part, 242, may also present trend charts, lists, indicator charts, etc.

[0063] In some cases, the second input can be used to provide additional information related to the first task. For example, such as... Figure 2H As shown in the interface 200H, in response to the first input 212-2, the electronic device 110 presents the first interactive component 246 on the first interface. Figure 2H Taking "Creating an inference access point (to be created)" as an example, the type of the first interactive component 246 is associated with the first task (creating an access point); the first interactive component 246 can present a pre-filled configuration parameter form 247.

[0064] In some cases, the aforementioned additional information may include at least one parameter for configuring the service, which may include at least one of the following: a first configuration parameter indicating the model associated with the service, and a second configuration parameter indicating the access method of the service. As an example, such as Figure 2H As shown, the configuration parameter form 247 may include items such as access model, access point name, call rate parameters (e.g., number of requests per minute and number of terms per minute), project and purpose, etc., where the access model corresponds to the first configuration parameter indicating the model associated with the service, and the access point name and call rate parameters correspond to the second configuration parameters indicating the access method of the service.

[0065] Alternatively or additionally, the parameters in the form can be pre-filled with reasonable default values ​​by the intelligent system, which user 140 can then modify inline. User 140's operation on the confirmation creation control 248-1 can be considered a second input, which can be used to provide the aforementioned additional information and confirm the execution of the access point creation operation. The first interaction component 246 may also include a cancellation control 248-2.

[0066] In some scenarios, the first interactive component 246 can describe the operation of creating an access point associated with the service, and the second input indicates confirmation of the operation. In this way, the user 140 does not need to jump to a separate access point creation interface and fill in the blanks one by one, but only needs to check or make minor adjustments on the pre-filled form and then confirm, which reduces the steps of manual filling and interface jumping, and can improve the efficiency of interface interaction.

[0067] In some situations, users can initiate multiple tasks through an intelligent system. For example, such as... Figure 2I The interface 200I shown indicates that the intelligent system can process multiple tasks concurrently and can present multiple interactive components awaiting confirmation. As an example, multiple interactive components awaiting confirmation can be presented in a stacked style.

[0068] As an example, such as Figure 2I As shown, user 140 can initiate multiple inputs in the same conversation, such as inputting 212-3, 212-4, and 212-5, thereby triggering multiple tasks concurrently. Electronic device 110 can correspondingly display the first content items 223, 224, and 225 of each first task (labeled as "Task in Progress", including task name and execution node), so that multiple first tasks can proceed in parallel in the background.

[0069] As an example, when there are multiple first interactive components to be processed, the electronic device 110 can display a component list in a stacked style. The component list includes multiple interactive components, and the multiple interactive components include at least a first interactive component and a second interactive component. The stacked style indicates that the first interactive component occludes at least a portion of the second interactive component. Figure 2I As shown, the card at the front of the stack and fully presented is the first interactive component 234. Figure 2I The first interactive component 234 may include a confirmation creation control 234-2 and a cancellation control 234-3. (The first interactive component 234 is labeled "Problem A").

[0070] In some cases, electronic device 110 can receive a first operation, which may be associated with a list of components. Additionally, electronic device 110 can present a second interactive component that obscures at least a portion of the first interactive component. Figure 2JAs shown, through the first operation of switching between before and after, the second interactive component 236 ( Figure 2J The component labeled "Problem B" can be moved to the front and fully displayed, obscuring at least a portion of the original first interactive component 234. Additionally, the second interactive component 236 may include a confirmation creation control 236-2 and a cancellation control 236-3.

[0071] In some cases, the electronic device 110 can also, in response to receiving a second input, stop presenting the first interactive component and present the second interactive component. That is, when the user 140 makes a second input confirming or rejecting the first interactive component 234 located at the front, the presentation of the first interactive component 234 can be stopped, and the second interactive component 236 can be moved to the front for presentation, thereby processing each interactive component in the stack one by one. In some cases, the second input can also represent multiple feedbacks to multiple interactive components. For example, the second input can provide a feedback method for uniformly confirming or rejecting multiple interactive components in the stack at once. For consecutive similar operations, after the user makes an input, subsequent similar operations in this round can be executed sequentially instead of popping up one by one. In this way, the user 140 can both switch and process each interactive component as needed, and can also input multiple feedbacks to multiple interactive components at once when appropriate, reducing repetitive confirmation operations in batch scenarios, thereby further improving the efficiency of interface interaction.

[0072] In some cases, after user 140 selects text (e.g., error messages in a log) on ​​an interface (such as the first interface or another appropriate interface), electronic device 110 can display a floating control 256 next to the selected text for initiating a question. Additionally, according to... Figure 2K The interface 200K shown, in response to an operation on the floating control 256, allows the electronic device 110 to open the dialog sidebar and automatically populate the selected content as a reference block 262. Additionally, the electronic device 110 can inject the page identifier and content context of the current page into the current dialogue round. Thus, the reference block 262 can serve as a form of first input carrying page context. Furthermore, the electronic device 110 can present an assistant response 264 combining the referenced content and the current page context, as well as a structured result card 266 such as a "solution". In some cases, the message history of the sidebar session and the main dialog can be synchronized bidirectionally, and the sidebar session can be switched to the main dialog via control 272, so that the context is not lost when the user 140 switches between the sidebar and the main dialog.

[0073] In this way, some examples in this paper can replace page-by-page navigation and manual configuration between multiple interfaces with interaction between the user and the intelligent system. User feedback can be obtained through interactive components during task execution, thereby reducing the number of interface navigations and operation steps required to complete the task, improving the efficiency of configuration services, and improving the efficiency of interface interaction.

[0074] Figure 3 A flowchart of an example process 300 for interface interaction is shown, based on some scenarios. Process 300 can be implemented at electronic device 110. See below for reference. Figure 3 To describe process 300.

[0075] like Figure 3 As shown in box 310, electronic device 110 receives a first input on the first interface. The first input triggers the intelligent system to execute a first task, which is used to perform an operation associated with the service. Its interactive presentation can be seen in the above text. Figure 2A The example described.

[0076] In box 320, in response to the first task meeting the trigger condition, electronic device 110 presents a first interactive component on the first interface. The type of the first interactive component is associated with the first task. Its interactive presentation can be referenced above. Figure 2D , Figure 2H The example described.

[0077] In box 330, electronic device 110 receives a second input via a first interactive component, and the second input is associated with a service. The interactive presentation can be found above. Figure 2D , Figure 2H The example described.

[0078] In box 340, electronic device 110 displays first content, which indicates the execution of a first task based on a second input. Its interactive presentation can be referenced above. Figure 2F , Figure 2G The example described.

[0079] In this way, user 140 can replace page-by-page navigation and manual configuration between multiple interfaces with a single continuous dialogue. When feedback is needed, confirmation or supplementation can be completed on-site through interactive components associated with the type and task, reducing the number of interface jumps and operation steps required to complete the task. Furthermore, since the steps scattered across multiple independent interface pages are converged into a single interface, there is no need to load and render independent pages for each step, nor is there a need to send page-level requests to the backend for each page jump. This reduces the page loading and rendering overhead on the client side, reduces the number of requests sent to the server, and thus reduces the server's query load and the bandwidth usage of the end-to-cloud communication.

[0080] In some cases, the electronic device 110 may present a first interactive component on a first interface in response to the execution of the first task depending on user input; specific interactive presentation can be found above. Figure 2D The example described illustrates this approach. By presenting interactive components only when user feedback is truly required for a task, unnecessary interruptions to the user are reduced. Furthermore, presenting and rendering interactive components when no user feedback is needed avoids reducing rendering overhead and unnecessary end-to-cloud confirmation round trips.

[0081] In some cases, the electronic device 110 may present second content associated with service permissions through the first interactive component, and receive second input for granting such permissions to the intelligent system through the first interactive component; specific interactive presentation can be found above. Figure 2D The example described illustrates this. In this way, user 140 can be granted permissions locally without being redirected to the permission management interface, reducing interface redirection; and without loading a separate permission management interface, the loading and rendering overhead of the corresponding interface and page-level requests can be reduced.

[0082] In some cases, the aforementioned permissions may include at least one of the following: a first permission for obtaining service-related parameter information, a second permission for creating service-related service interfaces, and a third permission for editing at least one configuration piece of information related to the service; specific interaction presentation can be found above. Figure 2D The example described illustrates this. In this way, the appropriate type of permission can be granted locally as needed, reducing switching between multiple management interfaces; and by prioritizing explicit authorization, invalid write requests caused by unauthorized write operations are reduced, lowering the corresponding server processing load and mitigating the risk of unauthorized access.

[0083] In some cases, the second input can be used to provide additional information related to the first task; specific interactive presentation can be found above. Figure 2H The example described illustrates this. In this way, user 140 can supplement the information needed to perform the task in-situ during the conversation, reducing the need for interface jumps to supplement information; and without loading a separate configuration interface, it can reduce the corresponding loading and rendering overhead and page-level requests.

[0084] In some cases, the electronic device 110 may present a first control for obtaining a first type of information and obtain a first part of the additional information on a first interactive component, then stop presenting the first control and present a second control for obtaining a second type of information to obtain a second part of the additional information; specific interactive presentation can be found above. Figure 2DThe described step-by-step clarification example. In this way, user 140 only needs to focus on one issue at a time, reducing the information density on a single screen and the possibility of mis-filling; and by rendering only the current control at a time, the number of interface elements on the same screen can be reduced, the single rendering overhead can be reduced, and the requests caused by repeated submissions and repeated processing can be reduced due to the reduction of mis-filling.

[0085] In some cases, the aforementioned additional information may include at least one parameter for configuring the service, which may include at least one of a first configuration parameter indicating the model associated with the service and a second configuration parameter indicating the access method of the service; specific interactive presentation can be found above. Figure 2H The example described. In this way, user 140 can check or fine-tune based on pre-filled parameters and then confirm, reducing the steps of filling in from scratch; and replacing the separate interface with pre-filled default values ​​can reduce the loading and rendering overhead of the form interface, and reduce duplicate requests caused by invalid submissions due to reduced filling errors.

[0086] In some cases, the first interactive component may describe at least one operation associated with the service, and the second input indicates confirmation of performing that at least one operation; specific interaction presentation can be found above. Figure 2D , Figure 2H The example described illustrates this. By explicitly acknowledging write operations in advance, accidental operations can be prevented; and invalid write requests and erroneous creations caused by accidental operations can be reduced, thereby reducing the corresponding processing load on the server side, reducing invalid writes to data storage, and lowering the risk surface of high-impact operations.

[0087] In some cases, electronic device 110 may, in response to the creation of a first task, present a first content item on a first interface indicating the execution status of the first task; specific interactive presentation can be found above. Figure 2A The example described illustrates this. In this way, user 140 can be informed in real time of the progress of tasks executed asynchronously in the background, reducing the extra operations required to obtain progress information; and the tasks can proceed in parallel in the background without blocking the user's continued input, which can improve concurrency throughput and reduce the number of rounds of end-to-cloud interaction required to query progress.

[0088] In some cases, the electronic device 110 may present the execution process of the first task in the first content item, and the execution process may be dynamically updated based on the execution of the first task; for specific interactive presentation, please refer to the above. Figure 2A , Figure 2D , Figure 2EThe example described illustrates this. In this way, user 140 can continuously monitor task progress, reducing sequential queries; and by updating execution nodes incrementally instead of redrawing the entire process, rendering overhead and refresh frequency are reduced, as well as the need for end-to-cloud interactions to obtain progress information.

[0089] In some cases, the first interface may include a first area displaying the conversation with the intelligent system, and the first content item is presented in a second area of ​​the first interface; specific interactive presentation can be found above. Figure 2A The example described illustrates this. In this way, the task state and session content are presented independently of each other, allowing user 140 to continue inputting or switching operations during task execution; and the first content item is independent of the session area and is not included in the session history, thus not increasing the storage and rendering burden of the session history, thereby reducing the corresponding overhead on the client side.

[0090] In some cases, electronic device 110 may, in response to the completion of the first task, stop displaying the first content item and display the third content obtained by performing the first task in the first area; for specific interactive presentation, please refer to the above. Figure 2F , Figure 2G The example described illustrates this. In this way, the interface can be reclaimed and the focus can be placed on the results after the task is completed, reducing the need for users to manually organize the results; and stopping the presentation of the first content item after the task is completed can release the rendering resources it occupies, reducing continuous rendering overhead and memory usage.

[0091] In some cases, the electronic device 110 may display a component list in a stacked style. The component list includes multiple interactive components, each including at least a first interactive component and a second interactive component. The stacked style indicates that the first interactive component obscures at least a portion of the second interactive component. For specific interaction presentation, please refer to the above. Figure 2I The example described. In this way, user 140 can centrally handle multiple pending confirmations, reducing the need to search for tasks between different tasks; and by using stacking instead of tiling on the same screen, the number of interface elements on the same screen can be reduced, and the initial screen rendering overhead and memory usage can be lowered.

[0092] In some cases, the electronic device 110 can receive a first operation associated with the component list and present a second interactive component that obscures at least a portion of the first interactive component; specific interaction presentation can be found above. Figure 2J The example described illustrates this. In this way, user 140 can switch between multiple interactive components as needed and process them one by one, reducing interference from irrelevant components; and when switching, only one card is fully rendered at a time, which can reduce the overhead of simultaneous rendering.

[0093] In some cases, the electronic device 110 may present a first prompt indicating the number of multiple interactive components, or a second prompt indicating that the first interactive component corresponds to the first task; specific interactive presentation can be found above. Figure 2I The example described illustrates this. In this way, user 140 can clearly see the number of tasks yet to be processed and the tasks corresponding to each card, reducing the need to look through the backlog; and the prompts are presented in lightweight elements, adding almost no additional rendering and request overhead.

[0094] In some cases, the second input can represent multiple responses to multiple interactive components; specific interaction presentations can be found above. Figure 2J The example described illustrates this. In this way, for consecutive similar operations, user 140 can confirm or reject all at once, reducing duplicate confirmations in batch scenarios; and multiple feedbacks can reduce the number of end-to-cloud interaction rounds required for confirmation one by one, thereby reducing the number of requests and processing load required by the server to handle multiple confirmations.

[0095] In some cases, electronic device 110 may, in response to receiving a second input, stop presenting the first interactive component and present the second interactive component; for specific interaction presentation details, please refer to the above. Figure 2J The example described illustrates this. In this way, user 140 can process the next component sequentially after processing the current one, reducing the need for repeated locating of pending tasks; and processing one card at a time means rendering only one complete card at a time, which can reduce rendering overhead.

[0096] In some cases, the electronic device 110 may stop presenting the first interactive component or trigger the termination of the first task in response to not receiving a preset operation associated with the first interactive component within a preset time; for specific interactive presentation details, please refer to the above. Figure 2A The example described illustrates this. In this way, tasks that have not received feedback for a long time can be handled automatically, preventing tasks from suspending in the background and occupying the user's attention; and timely stopping or terminating suspended tasks can release the computing and storage resources they occupy on the client and server sides, and reduce the overhead caused by maintaining connections for a long time.

[0097] A corresponding apparatus for implementing the above methods or processes is also provided.

[0098] Figure 4 A block diagram of a device 400 for interface interaction in several scenarios is shown. Device 400 can be implemented as or included in electronic device 110. The various modules / components in device 400 can be implemented by hardware, software, firmware, or any combination thereof.

[0099] like Figure 4As shown, the device 400 includes a first receiving module 410 configured to receive a first input on a first interface, the first input triggering an intelligent system to execute a first task, the first task being used to perform an operation associated with a service; a first presentation module 420 configured to present a first interactive component on the first interface in response to the first task meeting a trigger condition, the type of the first interactive component being associated with the first task; a second receiving module 430 configured to receive a second input through the first interactive component, the second input being associated with a service; and a second presentation module 440 configured to present first content, the first content indicating the execution of the first task based on the second input.

[0100] In some cases, the first presentation module 420 may also be configured to present a first interactive component in a first interface in response to user input dependent on the execution of a first task.

[0101] In some cases, the second presentation module 440 may also be configured to present second content associated with the permission of the service in the first interactive component; the second receiving module 430 may also be configured to receive second input for granting the permission to the intelligent system through the first interactive component.

[0102] In some cases, the aforementioned permissions include at least one of the following: a first permission for obtaining service-related parameter information, a second permission for creating service-related service interfaces, and a third permission for editing at least one configuration information related to the service.

[0103] In some cases, the second input received by the second receiving module 430 can also be used to provide additional information associated with the first task.

[0104] In some cases, the second receiving module 430 may also be configured to present a first control for obtaining a first type of information and obtain a first part of the additional information in the first interactive component, stop presenting the first control and present a second control for obtaining a second type of information to obtain a second part of the additional information.

[0105] In some cases, the aforementioned additional information includes at least one parameter for configuring the service, which includes at least one of a first configuration parameter indicating the model associated with the service and a second configuration parameter indicating the access method of the service.

[0106] In some cases, the first interactive component presented by the first presentation module 420 describes at least one operation associated with the service, and the second input indication received by the second receiving module 430 confirms the execution of the at least one operation.

[0107] In some cases, the first presentation module 420 may also be configured to present a first content item indicating the execution status of the first task on the first interface in response to the creation of the first task.

[0108] In some cases, the first presentation module 420 can also be configured to present the execution process of the first task in the first content item, and the execution process is dynamically updated based on the execution of the first task.

[0109] In some cases, the first interface includes a first area displaying the conversation with the intelligent system, and the first presentation module 420 can also be configured to present the first content item in a second area of ​​the first interface.

[0110] In some cases, the second presentation module 440 may also be configured to stop presenting the first content item in response to the completion of the first task, and present the third content obtained by performing the first task in the first area.

[0111] In some cases, the first presentation module 420 may also be configured to display a component list in a stacked style, the component list including multiple interactive components, the multiple interactive components including at least a first interactive component and a second interactive component, the stacked style indicating that the first interactive component occludes at least a portion of the second interactive component.

[0112] In some cases, the second receiving module 430 may also be configured to receive a first operation associated with the component list, and the first presentation module 420 may also be configured to present a second interactive component that obscures at least a portion of the first interactive component.

[0113] In some cases, the first presentation module 420 may also be configured to present a first prompt representing the number of multiple interactive components, or to present a second prompt representing that the first interactive component corresponds to a first task.

[0114] In some cases, the second input received by the second receiving module 430 represents multiple feedbacks to multiple interactive components.

[0115] In some cases, the first presentation module 420 may also be configured to stop presenting the first interactive component and present the second interactive component in response to receiving the second input.

[0116] In some cases, the first presentation module 420 may also be configured to stop presenting the first interactive component or trigger the termination of the first task in response to not receiving a preset operation associated with the first interactive component within a preset time.

[0117] The modules included in device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some cases, one or more 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 machine-executable instructions, some or all of the units in device 400 can be implemented at least partially 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 Parts (ASSPs), Systems on a Chip (SOCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0118] Figure 5 A block diagram of an electronic device 500 in which one or more examples may be implemented is shown. It should be understood that... Figure 5 The electronic device 500 shown is merely exemplary and should not be construed as limiting the functionality and scope of the examples described herein. Figure 5 The electronic device 500 shown can be used to implement the electronic device 110 described above.

[0119] like Figure 5 As shown, electronic device 500 is in the form of a general-purpose electronic device. Components of electronic device 500 may include, but are not limited to, one or more processing units or processors 510, memory 520, storage devices 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. Processor 510 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 520. In a multiprocessor system, multiple processors execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 500.

[0120] Electronic device 500 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 520 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof). Storage device 530 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data and can be accessed within electronic device 500.

[0121] Electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 5 As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 520 may include computer program product 525 having one or more program modules configured to perform various methods or actions of various examples.

[0122] The communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functionality of the components of the electronic device 500 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 500 can operate in a networked environment using logical connections to one or more other servers, networked personal computers, or another network node.

[0123] Input device 550 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 560 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 500 can also communicate with one or more external devices (not shown) via communication unit 540 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 500, or with any device that enables electronic device 500 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interfaces (not shown).

[0124] A computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. A computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above.

[0125] The flowcharts and / or block diagrams of the methods, apparatus, devices, and computer program products referred to herein describe various aspects. It should be understood that each block of the flowcharts and / or block diagrams, as well as combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0126] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions 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 that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0127] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause 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, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0128] The flowcharts and block diagrams in the accompanying figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products under various scenarios. In this respect, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the figures. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0129] Various examples have been described above. The foregoing descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for interface interaction, comprising: On the first interface, a first input is received, which triggers the intelligent system to execute a first task, which is used to perform an operation associated with the service; In response to the first task meeting the triggering condition, a first interactive component is presented on the first interface, and the type of the first interactive component is associated with the first task; The second input is received through the first interactive component, and the second input is associated with the service; as well as Present first content, which instructs the execution of the first task based on the second input.

2. The method according to claim 1, wherein in response to the first task satisfying the triggering condition, presenting the first interactive component on the first interface includes: In response to the fact that the execution of the first task depends on user input, the first interactive component is presented on the first interface.

3. The method of claim 2, wherein receiving the second input via the first interactive component comprises: In the first interactive component, second content is presented, and the second content is associated with the permissions of the service; as well as The first interactive component receives the second input, which is used to grant the permission to the intelligent system.

4. The method of claim 3, wherein the permission includes at least one of the following: The first permission is used to obtain parameter information related to the service; The second permission is used to create service interfaces related to the service. The third permission is used to edit at least one configuration information related to the service.

5. The method of claim 2, wherein the second input is used to provide additional information associated with the first task.

6. The method of claim 5, wherein receiving the second input via the first interactive component comprises: In the first interactive component, a first control is presented, which is used to obtain information of a first type; The first part of the additional information is obtained through the first control; Stop presenting the first control in the first interactive component and present the second control, which is used to obtain the second type of information; as well as The second part of the additional information is obtained through the second control.

7. The method of claim 5, wherein the additional information includes at least one parameter for configuring the service, the at least one parameter including at least one of the following: The first configuration parameter indicates the model associated with the service; The second configuration parameter indicates the access method of the service.

8. The method of claim 2, wherein the first interactive component describes at least one operation associated with the service, and the second input indicates confirmation of performing the at least one operation.

9. The method according to claim 1, further comprising: In response to the creation of the first task, a first content item is presented on the first interface, the first content item indicating the execution status of the first task.

10. The method of claim 9, further comprising: The first content item presents the execution process of the first task, which is dynamically updated based on the execution of the first task.

11. The method of claim 9, wherein the first interface includes a first area displaying a session with the intelligent system, and presenting the first content item includes: The first content item is presented in the second area of ​​the first interface.

12. The method of claim 1, wherein presenting the first interactive component comprises: A component list is displayed in a stacked style. The component list includes multiple interactive components, including at least the first interactive component and the second interactive component. The stacked style indicates that the first interactive component occludes at least a portion of the second interactive component.

13. The method of claim 12, further comprising: Receive a first operation, which is associated with the component list; as well as The second interactive component is presented, and the second interactive component obscures at least a portion of the first interactive component.

14. The method of claim 12, further comprising: A first prompt is presented, wherein the first prompt represents the number of the plurality of interactive components; or A second prompt is presented, indicating that the first interactive component corresponds to the first task.

15. The method of claim 12, wherein the second input represents multiple feedbacks to the plurality of interactive components.

16. The method of claim 12, further comprising: In response to receiving the second input, the rendering of the first interactive component is stopped, and the second interactive component is rendered.

17. The method according to claim 1, further comprising: In response to the failure to receive a preset operation associated with the first interactive component within a preset time, the presentation of the first interactive component is stopped or the first task is terminated.

18. A device for interface interaction, comprising: The first receiving module is configured to receive a first input on a first interface, the first input triggering the intelligent system to execute a first task, the first task being used to perform an operation associated with the service; A first presentation module is configured to present a first interactive component on the first interface in response to the first task meeting a trigger condition, wherein the type of the first interactive component is associated with the first task. The second receiving module is configured to receive a second input through the first interactive component, the second input being associated with the service; as well as The second presentation module is configured to present first content, which indicates that the first task should be performed based on the second input.

19. An electronic device comprising: At least one processor; as well as At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions causing the electronic device to perform the method according to any one of claims 1 to 17 when executed by the at least one processor.

20. A computer program product tangibly stored in a computer storage medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method according to any one of claims 1 to 17.

Images