Methods, apparatuses, devices, media, and program products for interface interaction

Abstract

Methods, apparatus, devices, media, and program products for interface interaction are provided. The method includes: presenting first information on a first interface, the first interface displaying a first session, the first session being associated with a first intelligent system, and the first information indicating the creation of a second session; receiving a first operation associated with the first information, the first operation being used to create the second session, the participants in the second session including at least the first intelligent system; and presenting a session entry point for the second session, and in response to triggering the session entry point, presenting a second interface for displaying the second session. This approach improves the convenience of the session.

Description

Technical Field

[0001] The examples in this paper generally relate to the field of computer science, and in particular to methods, apparatuses, devices, and computer-readable storage media for user interface interaction. Background Technology

[0002] With the development of intelligent interaction technology, users can interact with intelligent systems in a conversational interface to complete various processes with the help of these systems. During the interaction between users and intelligent systems, there are often processing needs that are relatively complex and require continuous progress. Summary of the Invention

[0003] In a first aspect of this disclosure, a method for interface interaction is provided. The method includes: presenting first information on a first interface, the first interface being used to display a first session, the first session being associated with a first intelligent system, and the first information indicating the creation of a second session; receiving a first operation associated with the first information, the first operation being used to create the second session, the participants in the second session including at least the first intelligent system; and presenting a session entry point for the second session, and in response to triggering the session entry point, presenting a second interface, the second interface being used to display the second session.

[0004] In a second aspect of this disclosure, an apparatus for interface interaction is provided. The apparatus includes: a first presentation module configured to present first information on a first interface, the first interface being used to display a first session, the first session being associated with a first intelligent system, and the first information indicating the creation of a second session; a receiving module configured to receive a first operation associated with the first information, the first operation being used to create a second session, the participants in the second session including at least the first intelligent system; and a second presentation module configured to present a session entry point for the second session, and in response to triggering the session entry point, present a second interface, the second interface being used to display the second session.

[0005] In a third aspect, 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, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions that can be executed by a processor to implement the method of the first aspect.

[0007] In a fifth aspect, 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.

[0008] In this way, the creation of a second session can be conveniently initiated on the first interface used to display the first session, based on the first information indicating the creation of the second session and the first operation associated with the first information. The second session, with participants including at least the first intelligent system, can be displayed on the second interface through the session entry. This allows the second session to be smoothly introduced during the interaction of the first session, which helps to carry out relatively complex processing requirements in an independent second session, improves the efficiency of interaction organization, and reduces the operational overhead required by the user to carry out processing requirements.

[0009] 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

[0010] 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 2E Example interfaces for some scenarios are shown; Figure 3 Flowcharts illustrating example processes for interface interaction in several scenarios are shown; Figure 4 Schematic block diagrams of example devices for interface interaction in some scenarios are shown; and Figure 5 A block diagram of an electronic device capable of implementing multiple illustrative scenarios is shown. Detailed Implementation

[0011] 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.

[0012] 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.

[0013] 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.

[0014] The examples in this document may involve user data, data acquisition, and / or use. All of these aspects comply with relevant laws, regulations, and provisions. In the examples presented herein, 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.

[0015] 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.

[0016] In this paper, an 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 capable of making decisions and autonomously executing 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.

[0017] The term "session" as used in this article refers to the logical process of interaction between a user and one or more objects, or the object that carries out the interaction process. A session can include, but is not limited to, one-on-one chat between a user and an intelligent system, or group chat between multiple participants. This article may refer to a first session and a second session, which may belong to different session types.

[0018] The term "interface" as used in this article refers to a visual area used to present information to users and receive user actions. Interfaces may include, but are not limited to, session interfaces, project management interfaces, member management interfaces, etc.

[0019] The term "first information" as used in this document refers to information presented in a first interface that indicates the creation of a second session. First information may include, but is not limited to, prompts presented in the form of messages, cards, components, or a combination thereof.

[0020] The term "session entry" as used in this article refers to a triggerable object used to access a corresponding session. By triggering the session entry, an interface for displaying the corresponding session can be presented. The session entry may be one or a combination of list items, icons, links, etc.

[0021] The term "session entry" as used in this article refers to a triggerable object used to access a corresponding session. By triggering the session entry, an interface for displaying the corresponding session can be presented. The session entry may be one or a combination of list items, icons, links, etc.

[0022] As mentioned above, users can continuously interact with the intelligent system through a conversational interface to complete different types of tasks such as content creation, program development, data analysis, and solution planning. In practical applications, users often interact with the intelligent system multiple times around a specific goal, gradually accumulating contextual information related to that goal.

[0023] As the interaction continues, some of the conversation content may correspond to a task that needs to be continuously pursued. For example, users may continue to discuss implementation solutions for a development requirement, continuously improve content for a creative requirement, or gradually supplement data and form results for an analysis requirement.

[0024] In some cases, such processing needs may be mixed into the interaction process of ordinary conversations, making it difficult to effectively organize and handle the interaction content, deliverables, and participants related to the processing needs. In some current solutions, users often need to manually initiate separate conversations and reorganize the relevant interaction content, which is cumbersome and inefficient in handling processing needs.

[0025] This paper proposes a scheme for interface interaction. According to the scheme, a first information indicating the creation of a second session is presented in a first interface for displaying a first session, wherein the first session is associated with a first intelligent system; a first operation associated with the first information is received, the first operation being used to create a second session with participants including at least the first intelligent system; and a session entry point for the second session is presented, and a second interface for displaying the second session is presented in response to triggering the session entry point.

[0026] In this way, the creation of a second session can be conveniently initiated during the user's interaction with the intelligent system. This allows users to create new session environments around their target processing needs, enabling relatively complex processing requirements to be carried out continuously within an independent second session. Furthermore, by presenting a second interface for showcasing the second session, content related to the target processing needs and subsequent processing procedures can be organized and implemented, thereby improving the interaction efficiency and session management efficiency for complex processing needs.

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

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

[0029] In this example environment 100, electronic device 110 may run an application 120 that supports interface interaction. Application 120 may be any suitable type of application for interface interaction. User 140 may interact with application 120 via electronic device 110 and / or its attached devices.

[0030] exist Figure 1 In environment 100, if application 120 is active, electronic device 110 can use application 120 to present interface 150 for supporting interface interaction.

[0031] 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).

[0032] 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 in electronic devices 110 that support user interface interaction.

[0033] 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 (Wi-Fi) connections. In some cases, server 130 and electronic device 110 can exchange signaling information through their communication connection.

[0034] 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.

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

[0036] Figures 2A to 2EExample interfaces 200A to 200E are shown according to some scenarios. Interfaces 200A to 200E can, for example, be provided by... Figure 1 The interface is provided by the electronic device 110 shown, for example, by the application 120 running on the electronic device 110. It should be understood that the interface shown in the figures is merely an example, and various interface designs may exist in practice. The various graphic elements in the interface may have different arrangements and different visual representations, one or more of which may be omitted or replaced, and one or more other elements may also be present.

[0037] The following text uses an interactive interface in a conversational scenario as an example for illustration. Figure 2A In this example, interface 200A includes a sample session interface. Through interface 200A, session content can be displayed and information exchange between session participants can be supported.

[0038] In some cases, interface 200A also provides an input area 205 for task input, where the user can enter the content to be sent and send the session message via the "Send" control 202. Input area 205 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. Furthermore, input area 205 can also provide an upload control to support uploading attachments to indicate the user's task request.

[0039] In some cases, electronic device 110 can display user-sent conversational messages in a conversational interface. Conversational messages may include information used to express the content of the communication. For example, in interface 200A, electronic device 110 can receive a conversational message sent by user 140. After receiving the message, electronic device 110 can display the user-sent message 201 in interface 200A.

[0040] In some scenarios, a session may include an intelligent system, allowing users to initiate task requests to the system and receive processing results during the session. Session messages may also include content indicating task requests. For example, a session message might involve consulting about an object, requesting information related to that object (e.g., recommendations, comparisons, or reviews), or requesting the intelligent system to process relevant content.

[0041] In some examples, the intelligent system can participate in a session in response to at least one message in the session; that is, when a session message meets predetermined conditions (such as containing specific content, referencing a specific resource, or indicating a task request), the intelligent system is triggered to perform a corresponding processing action or provide a response. For example, the response could be a reply message 202 to a user request.

[0042] The following examples, with reference to the accompanying drawings, illustrate some of these practices. These examples can be implemented in electronic device 110. It should be noted that the operations performed by electronic device 110 may specifically be performed by relevant applications installed on electronic device 110. Some operations described herein with reference to electronic device 110 may require the assistance of server 130.

[0043] In some situations, electronic device 110 may present first information on first interface 200A, indicating the creation of a second session. For example, during continuous interaction between the user and the intelligent system, electronic device 110 may discover that the current session has formed a relatively clear task around a certain goal, and that this task may need to be continuously advanced. At this time, electronic device 110 may automatically present the first information on first interface 200A to proactively prompt the user to create a second session for performing this task.

[0044] In some scenarios, the initial information is associated with the initial task. The initial task can be the processing objective involved in the interaction between the user and the initial intelligent system during the initial session. For example, the initial task could be a content creation task, a code development task, an information analysis task, a solution planning task, a multi-step processing task, or other processing tasks that require continuous progress. By associating the initial information with the initial task, the created second session can revolve around the initial task, helping to make the progress of the initial task more targeted and improve its processing efficiency.

[0045] In some examples, electronic device 110 can determine the first task based on the content of the first session. For example, electronic device 110 can identify the target processing requirement involved in the current interaction based on the historical interaction content between the user and the first intelligent system, and determine the first task corresponding to the target processing requirement.

[0046] For example, a user can make requests to the intelligent system during a conversation, such as "Help me develop an application" or "Help me develop a market research plan." As the interaction continues, the user and the intelligent system may engage in multiple rounds of discussion around the same goal, gradually forming background information, constraints, and interim results related to that goal. Based on the current conversation content, the electronic device 110 can determine that there is a first task that needs to be continuously pursued, and present the first information related to the first task on the first interface 200A, prompting the user to carry out relatively complex or large-scale processing requests in a separate second conversation.

[0047] In some scenarios, the second session is used to perform the first task. Compared to the first session, the second session can serve as a dedicated session space established around the first task. For example, the first session can be used for daily interactions between the user and the intelligent system, while the second session is used for ongoing interactions around a specific task, organizing task-related information, and advancing the task execution process.

[0048] In some scenarios, the second session can be understood as a project session, which is a different type of session from the first session. The first session can be used for real-time interaction between the user and the intelligent system. For example, a user can ask questions, obtain information, initiate task requests, or engage in discussions with the intelligent system in the first session. In contrast, a project session can be built around a specific task and includes content items or contextual information scattered across one or more historical sessions. The task corresponding to the project session can be a suitable task discovered by the intelligent system through automatic analysis of the historical session content of one or more sessions during the interaction in the first session.

[0049] In some scenarios, the second session can be associated with the project space. The second session serves to host the interactions surrounding the first task, while the project space hosts content items, resources, and task deliverables related to the first task. The project space acts as a container for organizing resources around the task, holding various task-related information, thereby centralizing and managing task-related content that was originally scattered across different interaction rounds, time stages, and resource carriers. Furthermore, as the task progresses, the project space can continuously receive and manage new resources and information, thus forming a management space corresponding to the task's lifecycle.

[0050] In some situations, electronic device 110 may present first information on first interface 200A in response to the first task meeting preset conditions. Preset conditions may include at least one of the following: the estimated completion time of the first task exceeds a duration threshold, the number of processing steps required for the first task exceeds a quantity threshold, or the number of pending objects associated with the first task exceeds an object threshold. As an example, when electronic device 110 determines, based on the session content of the first session, that the first task is a relatively complex processing requirement that needs to be continuously advanced, it may determine that the first task meets the preset conditions and present the first information accordingly.

[0051] Alternatively or additionally, the preset conditions may also include the conversation content of the first session meeting semantic depth conditions, the number of interaction rounds reaching a round threshold, or the presence of keywords related to task initiation in the conversation content. For example, during the first session, the user may initially only ask the first intelligent system a simple question. As the interaction continues, the user may further request the generation of multiple processing results, continuously modify existing content, associate multiple objects to be processed, or conduct long-term interactions around the same topic. In this case, the electronic device 110 can determine that the current interaction has gradually evolved from instant question and answer to a continuously progressing first task, and further present the first information on the first interface 200A to guide the user to create a second session.

[0052] By automatically identifying the first task suitable for continuous progress based on the interaction process in the first session, and automatically presenting the first information to trigger the second session corresponding to the first task, the complexity of manually organizing the task context and reorganizing the interaction environment for users can be reduced, thereby improving the capacity to handle complex processing needs and the efficiency of continuous interaction.

[0053] like Figure 2A As shown, in some examples, the first information is presented in the first component 215 of interface 200A. The first component 215 can also be called a prompt component. The first component 215 can be presented as a message card component and displayed in the message flow of the first session to prompt the user 140 to create a second session. By presenting the first information indicating the creation of a second session, the user can be proactively guided to create a second session during the interaction of the first session, thereby reducing the operational overhead caused by the user's own judgment on whether to create a new session and manually creating a new session. Especially when the user and the intelligent system have already carried out multiple rounds of interaction around a specific goal, the electronic device 110 can promptly prompt the user to migrate the relevant processing needs to the second session for continued progress, thereby improving task organization efficiency.

[0054] In some cases, the first information may also indicate at least one configuration parameter of the second session, and this at least one configuration parameter is determined based on the session content of the first session. In this document, configuration parameters can be understood as information used to describe, identify, or organize the second session. For example, configuration parameters may be used to determine the name, description, type, participants, associated tasks, or other information related to the second session.

[0055] In some cases, at least one configuration parameter may include at least one of the following: the session name of the second session, the description information of the second session, the type of the second session, or the participants of the second session.

[0056] As an example, a session name can be used to identify a second session and can be a general description of the first task. For instance, if the first task is to develop an application, the session name could be "Application Development Project." If the first task is to create project documentation, the session name could be "Project A Documentation," and so on. Through the session name, users can quickly identify the task content corresponding to different second sessions.

[0057] In some situations, descriptive information can be used to describe the background, objectives, or core requirements of the first task. For example, descriptive information may include phrases such as "continuously collecting and organizing relevant information around the target topic" or "generating and continuously optimizing code implementation schemes for the target object." By presenting descriptive information, users can understand the processing requirements of the second session before creating it.

[0058] In some cases, the type of the second session can be used to characterize the task category corresponding to the second session. For example, the type of the second session may include content creation, program development, data analysis, product design, operational planning, or other types. This disclosure does not limit this. The type of the second session can be determined based on the content of the first session, thereby making the subsequently presented interface layout, functional components, and related resources more closely matched to the current task.

[0059] The term "component" as used in this article refers to a visual unit in an interface that carries information presentation or interactive functions, and the term "control" refers to an interactive unit in a component or interface that receives user operations. Controls may include, but are not limited to, one or a combination of buttons, switches, input boxes, links, etc.

[0060] In some cases, the first information may also indicate the source information for the second session. The source information may indicate the basis for presenting the prompt information for creating the second session. For example, the source information may include at least a portion of the session content from the first session. For instance, the source information may include messages related to the first task, keywords related to the first task, interactive summaries related to the first task, or other content related to the first task.

[0061] In some cases, participants in the second session may include the intelligent system or other collaborating users who participated in the first task. For example, electronic device 110 may determine the intelligent system suitable to participate in the first task based on the task attributes of the first task and present the relevant participant information in the first component 215. In some cases, participants may also include other users from the first session or collaborating objects that will subsequently participate in the processing of the first task.

[0062] In some scenarios, participants may include a second intelligent system, which is added to the participant list of the second session in response to the first operation. As an example, electronic device 110 can determine a suitable second intelligent system to participate in the first task based on the session content of the first session. For instance, electronic device 110 can determine that the first task involves processing requirements from multiple different areas and further determine multiple intelligent systems suitable for each of these different processing requirements. When creating the second session, electronic device 110 can add these intelligent systems to the participant list of the second session. By automatically identifying and introducing intelligent systems suitable for participating in the first task, the second session can be created with processing capabilities matching the first task, reducing the need for users to search for and add intelligent systems one by one, and improving the efficiency of second session creation and task execution.

[0063] In some scenarios, participants may include at least one user. For example, electronic device 110 may determine that the first task may require the participation of multiple users, or that the first session itself is a group session or a multi-person collaborative session. In some examples, electronic device 110 may determine suitable users to participate in the first task based on the session content of the first session and present a list of recommended participants in the first component 215. For example, the first component 215 may display a prompt message such as "Recommended invitation to user 1 and user 2 to participate in the current project." After confirming the creation of the second session, invitation messages can be sent to the recommended participants. The invitation messages are used to invite the corresponding users to join the second session. Electronic device 110 can add the users who confirm the invitation to the participant list of the second session.

[0064] By automatically determining the intelligent systems and users suitable for participating in the first task based on the content of the first session, the matching degree between the second session and the first task can also be improved, thereby improving the efficiency of collaborative processing around the first task.

[0065] In some scenarios, electronic device 110 can receive a first operation associated with the first information, the first operation being used to create a second session, the participants of which include at least the first intelligent system. For example, in response to the first operation, electronic device 110 can create a second session based on configuration parameters indicated in the first information. By creating a second session, tasks originally formed in the first session can be gradually migrated to a dedicated session space corresponding to that task, thereby providing a unified organizational framework for the continuous advancement of the task.

[0066] As an example, continue to refer to Figure 2AThe first component 215 may include a first control 211. The electronic device 110 may receive a first operation associated with the first information via the first control 211. By receiving the first operation via the first control 211 in the first component 215, the operation of creating a second session can be carried out nearby in the first component that presents the first information, making it convenient for the user to initiate creation directly after viewing the first information, thus improving the continuity of the interaction.

[0067] In some cases, the first component 215 may also include a second control 212. The electronic device 110 may receive a second operation via the second control 212, the second operation being used to refuse the creation of a second session; and in response to the second operation, update the display style of the first information. As an example, in response to the second operation received via the second control 212, the electronic device 110 may update the first information to an ignored state. For example, the first information may be collapsed, grayed out, moved to the history suggestion area, or its display may be stopped. By receiving the second operation via the second control 212 and updating the display style of the first information, clear interactive feedback can be provided when the user does not expect the creation of a second session, and the interference of the first information on the first session interaction process can be reduced.

[0068] In some cases, the first component 215 may also include a third control 213. The electronic device 110 may receive a third operation via the third control 213, the third operation indicating modification of at least one configuration parameter of the second session. Further, the electronic device 110 may present updated first information indicating the creation of a second session based on the modified at least one configuration parameter.

[0069] As an example, modifiable configuration parameters include session name, description, session type, participants, or other information related to the second session. For instance, electronic device 110 can initially generate a second session named "Product Analysis Project," which the user can then change to "Second Quarter Product Analysis Project." As another example, electronic device 110 can recommend multiple participants, and the user can use the third control 213 to select which participants to retain or add others, such as adding collaborating users (e.g., user A), removing or replacing users or intelligent systems participating in the second session. By supporting the modification of configuration parameters via the third control 213, the second session can further adapt to user needs while inheriting the context of the first session, improving the usability and flexibility of the second session.

[0070] In some examples, where the modified participants include collaborating users, electronic device 110 can send an invitation message to the added user A. For example, the invitation message can be sent via private message, system notification, or other message format. This invitation message invites user A to join the second session and may include the name, description, participant information, or information related to the first task of the second session. User A can view the relevant information of the second session through this invitation message and confirm joining. In response to receiving user A's confirmation, electronic device 110 can add user A to the participant list of the second session.

[0071] In some scenarios, the first session can be a one-on-one chat between user 140 and the first intelligent system, or it can be a group chat involving multiple participants. For example, the first session can be a collaborative session involving multiple users and at least one intelligent system, or a group session where multiple users interact around the same topic. In the case where the first session is a group chat, the first information can be presented as a message in the group chat message stream. For example, electronic device 110 can determine based on the content of the group chat that there is a first task suitable for independent implementation, and present the first component 215 in the group chat interface to prompt the creation of a second session corresponding to the first task.

[0072] In some examples, multiple members of a group chat can see the first information presented as the first component 215 and can perform corresponding operations via the first control 211, the second control 212, or the third control 213. For example, if a member of the group chat triggers the first control 211 in the first component 215, that member can be added to the created second session in response to the trigger. Additionally or alternatively, other group chat members can trigger a first operation via the first control 211 to join the second session.

[0073] By supporting the presentation of the first information in a group chat scenario, the guidance for creating a second session can be applied to multi-party collaborative scenarios, thereby expanding the applicability of the solution. Furthermore, by presenting the first component 215 as part of the group chat message flow, the creation process of the second session can also remain associated with the group chat context, reducing the operational complexity for users in multi-party collaborative scenarios of reorganizing participants and re-establishing the collaborative environment, thereby improving the efficiency of collaborative processing around the first task.

[0074] In some scenarios, electronic device 110 can create a second session in response to a first operation received via first control 211. For example, after user 140 triggers first control 211 in first component 215 to confirm the creation of a second session, electronic device 110 can establish the second session and create a session environment associated with the second session. The created second session can serve not only as a new interaction space but also as a project session to host the first task, supporting ongoing follow-up processing around the first task.

[0075] like Figure 2B As shown, electronic device 110 can present a session entry 221 for the second session and, in response to a trigger on session entry 221, present a second interface 200B for displaying the second session. Session entry 221 can also be called an item entry. In some cases, session entry 221 can be presented in a session entry list, which can include multiple session entries for accessing multiple second sessions, thus supporting switching between multiple second sessions. For example, electronic device 110 can present a session entry list in the sidebar, navigation area, tab area, or other interface areas for users to access different second sessions. (Alternatively, the second interface can be automatically presented after creation.) In some examples, the session entry point 221 may display the name of the second session, an icon corresponding to the type of the second session, and, in the case of a group chat, identifiers of active members in the second session. For example, if the second session is a code development type, the session entry point 221 may display icons related to code development. If the second session is a content creation type, the session entry point 221 may display icons related to content creation. Additionally or alternatively, the session entry point 221 may also display status information related to the second session, such as the last update time, the number of unread messages, the current task status, or recently active members.

[0076] In some cases, electronic device 110 can also automatically present the second interface 200B after the second session is created. For example, after user 140 triggers the first control 211 and confirms the creation of the second session, electronic device 110 can automatically switch from the first interface 200A to the second interface 200B, allowing the user to directly enter the project session environment corresponding to the first task. By automatically presenting the second interface 200B, the number of steps required for the user to search for and enter the second session can be reduced, improving the efficiency of entering the second session and the efficiency of continuous interaction around the first task.

[0077] like Figure 2BAs shown, upon triggering a session entry, the electronic device 110 can display a second interface 200B. The second interface 200B is used to display a second session. Compared to the first session, the second session corresponds to a project session established around the first task. Therefore, the second interface 200B is not only used to carry session interactions, but also to organize members, resources, and processes related to the first task.

[0078] In some cases, the second interface 200B may display session information 222. Session information 222 is used to display information related to the second session. For example, session information 222 may include the session name, description, task type, creation time, currently participating intelligent system, and the current state of the intelligent system.

[0079] In some cases, the second interface 200B may also display participant identifiers 224. Participant identifiers 224 are used to display the current participants in the second session. For example, participants may include the user who initiated the first task, other collaborating users, and one or more intelligent systems. Different participants may correspond to different identifier formats. For example, users may be represented by a user avatar or user name, and intelligent systems may be represented by an intelligent system identifier or capability identifier. By displaying participant identifiers 224, users can intuitively understand the objects currently collaborating on the first task, thereby improving information transparency in multi-participant collaboration scenarios.

[0080] In some cases, the second interface 200B may also display control 225. Control 225 is used to manage the participants in the second session. For example, users can add new participants, remove participants, or adjust participant permissions via control 225. New participants may include new intelligent systems or new user accounts. In some examples, electronic device 110 may recommend new participants based on the progress of the first task. For example, during task progress, electronic device 110 may determine that it is necessary to introduce an intelligent system with specific processing capabilities or to introduce new collaborating users, and provide the corresponding addition entry via control 225. By providing control 225, the participants in the second session can be dynamically adjusted according to the progress of the task, thereby improving the flexibility of the project collaboration process.

[0081] In some cases, the second interface 200B can also display conversation messages 227. Conversation messages 227 are used to carry interactive content related to the first task. For example, conversation messages 227 may include task instructions sent by the user, processing results returned by the intelligent system, discussion content between participants, intermediate results during task execution, or other information related to the first task. Conversation messages in the second session can revolve around the first task and can continuously accumulate processing procedures and execution results related to the first task. By recording the task progress through conversation messages 227, the second session can become a unified interactive space for collaboration around the first task.

[0082] In some cases, the first task may belong to the first type, and the page layout of the second interface may match the first type. In this article, the first type can be used to characterize the task category to which the first task belongs. For example, the first type may include content creation, program development, data analysis, product design, operations planning, or other types, which are not limited in this article.

[0083] In some situations, different types of primary tasks can correspond to different page layouts. For example, when the primary task is a collaborative creation type, the secondary interface 200B can adopt a page layout suitable for content organization and collaborative editing; when the primary task is a program development type, the secondary interface 200B can adopt a page layout suitable for code viewing, code editing, and debugging analysis; when the primary task is a data analysis type, the secondary interface 200B can adopt a page layout suitable for displaying data results, analysis processes, and data resources. In other words, the electronic device 110 can not only create a secondary session, but also adapt the project space corresponding to the secondary session according to the type of the primary task, so that different types of tasks correspond to different interface organization methods. By matching the page layout of the secondary interface with the primary type of the primary task, the secondary interface can be more closely aligned with the actual processing scenario of the primary task, improving the efficiency of users in obtaining information and performing operations.

[0084] In some cases, presenting the second interface 200B may include: presenting at least one functional component 226 in the second interface 200B, the at least one functional component 226 being used to perform the first task, and the type of the at least one functional component 226 matching the first type. For example... Figure 2BAs shown, functional component 226 may include one or more functional entry points, resource entry points, or processing tools required during the execution of the first task. For example, in the case where the first task is of the press release creation type, functional component 226 may include components related to document editing, file management, schedule management, email processing, or information retrieval. In the case where the first task is of the code refactoring type, functional component 226 may be automatically replaced with components related to code repositories, code editing, compilation and debugging, test analysis, or version management.

[0085] In some situations, different types of first tasks may correspond to different functional components. Electronic device 110 can automatically determine the functional components to be presented based on the type of the first task and display them in the second interface. Therefore, the second session not only provides a conversational area for interaction but also further provides processing capabilities matching the first task, enabling the project space corresponding to the second session to directly support the execution of the first task. By presenting functional components matching the first type in the second interface, the second interface can possess the capabilities required to execute the first task, reducing the operational overhead of switching between different tools.

[0086] In some cases, presenting the second interface 200B may include presenting contextual information in the second interface 200B, the contextual information being derived from the session content of the first session and related to the first task. As an example, the electronic device 110 may carry the session content related to the first task from the first session to the second session and present the contextual information in the second interface.

[0087] For example, if a user has already engaged in multiple rounds of discussions with the first intelligent system regarding a product solution in the first session, the electronic device 110 can incorporate the product requirements, design goals, and discussion results as contextual information into the second session. Similarly, if a user has already conducted requirements analysis regarding a development task in the first session, the electronic device 110 can incorporate the relevant requirements specifications and analysis results as contextual information 228 into the second session. By presenting the contextual information from the first session in the second interface, the second session can inherit the interactive context accumulated in the first session, reducing the need for the user to provide background information again in the second session.

[0088] In some cases, the second interface may include components for accessing the first content item management space. In response to a triggering of the file-related component in functional component 226, electronic device 110 may present the first content item management space associated with the second session. Electronic device 110 may present one or more content items stored in the first content item management space. For example, content items may include background information synchronized from the first session, requirement documents, reference files, image resources, historical discussion results, or drafts, intermediate results, and final deliverables generated during the execution of the first task.

[0089] The term "content item" as used in this article refers to a data object involved in the interaction of a session. Content items may include, but are not limited to, one or a combination of images, documents, audio, video, code snippets, etc.

[0090] like Figure 2C As shown, the electronic device 110 can present a session entry 231 for another second session, and in response to triggering the session entry 231, present a second interface 200C for displaying the second session. Figure 2C In the example shown, the first task corresponding to session entry 231 is a video clip type. Session entry 231 can display an icon corresponding to the video clip type to identify the type of the second session and can serve as a persistent revisit entry point for the video project.

[0091] For example, session entry 231 can display the name of a "short video editing project" or other project related to the video processing task, along with icons, thumbnails, or visual identifiers corresponding to the video editing type, to help users quickly distinguish between different types of second sessions. In some cases, session entry 231 can also display status information related to the video project, such as the current editing progress, the last update time, the most recently active participants, or the current generation status.

[0092] like Figure 2C As shown, the second interface 200C can display session information 232, which can be used to display the project name of the second session and the intelligent system responsible for video processing. For example, session information 232 can display the status information of the video generation intelligent system, audio processing intelligent system, or subtitle processing intelligent system currently participating in the video project. Additionally or alternatively, session information 232 can also be used to display video processing-related information such as the video duration, current processing stage, or target output format corresponding to the current video project.

[0093] In some examples, the second interface 200C can also display a video type function component 236. This differs from... Figure 2BThe second interface 200C automatically reconstructs the functional components 226 shown in the diagram as video editing components, matching them to the first type of the first task. The video type functional component 236 may include timeline editing components, media management components, audio processing components, subtitle editing components, etc. Users can use these functional components to edit, adjust, or manage video materials in the second session and collaborate with the intelligent system to complete video creation tasks.

[0094] In some examples, electronic device 110 can automatically adjust the page layout in the second interface 200C based on the task type corresponding to the second session. For example, when the first task is video editing, electronic device 110 can prioritize displaying the video preview area, timeline area, and media management area in the second interface 200C; while when the first task is code development, electronic device 110 can prioritize displaying the code editing area, debugging area, or file directory area. In this way, different types of second sessions can correspond to different interface structures and functional component configurations.

[0095] In some examples, the second interface 200C may also display conversation messages 237. These conversation messages 237 may include interactive messages between the intelligent system and the user regarding specific editing elements such as the timeline, background music, and subtitles, supporting interactive manipulation of underlying video parameters and status confirmation. For example, the user can request the intelligent system to "insert a transition effect at 10 seconds," "replace the background music," or "adjust the subtitle style" through conversation message 237. The intelligent system can then return processing results, parameter confirmation information, or modification suggestions based on the corresponding request. Additionally or alternatively, conversation messages 237 may also include status feedback related to the video generation process, such as rendering progress, missing material alerts, or parameter conflict alerts.

[0096] Therefore, for different types of first tasks, the page layout and functional component types of the second interface can be different accordingly, thus ensuring a high degree of matching between the second interface and the processing scenario of the first task. Compared to a uniform ordinary conversational interface, the second interface in this solution can dynamically construct an interactive environment adapted to the task scenario based on the task attributes of the first task, thereby improving the processing efficiency of complex tasks, interface organization efficiency, and human-computer collaborative interaction efficiency.

[0097] In some cases, the electronic device 110 may receive a fourth operation on the second interface, the fourth operation being used to request the presentation of at least one content item related to the second session. The at least one content item is stored in a first content item management space. The lifecycle management of the first content item management space is independent of the lifecycle management of the second session. Further, the electronic device 110 may present a first area on the second interface, the first area being used to manage the at least one content item.

[0098] like Figure 2C As shown, the session message 237 may include a control 238. In response to a triggering of the control 238, the electronic device 110 may display a first area for managing content items. In some embodiments, the first area may be presented as a sidebar, a standalone panel, a resource list, or other form, which is not limited herein.

[0099] In some cases, creating a second session involves not only creating a session interface for interaction but also creating a content item management space associated with that second session. This content item management space, also known as a project space, can be understood as a resource management space built around the first task, used to uniformly store and manage process data and task deliverables related to the first task.

[0100] As an example, while creating the second session, electronic device 110 can create a first content item management space in the file system that is bound to the second session. For example, electronic device 110 can create a directory, folder, or other storage unit corresponding to the first task in the file system and establish an association between the storage unit and the second session. In other words, creating a second session of the project session type not only means creating a new interactive interface, but also means automatically creating a project directory corresponding to the first task. All content generated around this task during the subsequent second session can be uniformly collected and managed in this project directory.

[0101] In some scenarios, the first content item management space and the second session can maintain a binding relationship. Users can access content in the first content item management space through the second session, and can also re-access the first content item management space through the project entry. Furthermore, the lifecycle management of the first content item management space can be independent of the lifecycle management of the second session. In other words, even if the second session ends, closes, or is not accessed for a long time, the first content item management space associated with the second session can still exist and retain the content items that have been created within it. For example, users can re-access the corresponding project after several days, weeks, or even months, and the historical interaction records in the session and the task artifacts in the project space can still be accessed and used. By making the lifecycle management of the first content item management space independent of the lifecycle management of the second session, the process data and task artifacts of the first task can be continuously preserved, avoiding the loss of related content due to the end of the session, thereby supporting the continuous progress of long-term tasks.

[0102] In some cases, at least one content item is formed based on a first task in at least one of the first and second sessions. For example, a content item could be data transmitted during the interaction of the first session or data generated during the interaction of the second session. By making content items formed based on a first task in at least one of the first and second sessions, data related to the first task can be completely aggregated into the first content item management space, facilitating unified management of the process data of the first task.

[0103] In some scenarios, at least one content item may include at least one of the following: a first content item, a second content item, or a third content item. In some examples, the first content item is included in the interaction process of the first session and is related to the first task. In response to the creation of the second session, the electronic device 110 can automatically add the first content item to the first content item management space. For example, the first content item may include documents, images, videos, data files, link information, or other data related to the first task uploaded by the user in the first session. By automatically synchronizing the relevant content in the first session to the first content item management space, the second session can directly inherit the existing data foundation of the first task after its creation.

[0104] In some examples, the second content item can be received via the first area. For instance, a user can continuously upload new documents, materials, images, videos, or other resources during project execution and add them to the first content item management space.

[0105] In other examples, the third content item may be content generated through the interaction process of the second session. For example, the third content item may include documents, code files, design schemes, analysis reports, video files, image files, or other task deliverables generated by the intelligent system. Thus, the content in the first content item management space includes not only data that existed before the task started, but also data added during task execution and deliverable data generated after task completion.

[0106] As used in this document, the term "content item management space" refers to the logical or storage space used for storing and managing content items. Content item management space may include, but is not limited to, persistent storage paths within a file system, such as folders.

[0107] The term "lifecycle management" as used in this article refers to the management of the lifecycle of an object from its creation to its end (e.g., archiving, release, or deletion).

[0108] By supporting the unified management of content items from multiple sources into the first content item management space, the first content item management space can become an information center organized around the first task, thereby improving the efficiency of resource management and the traceability of task results during the execution of long-term tasks.

[0109] like Figure 2D As shown, the electronic device 110 can display an interface 200D for managing the second session. The interface 200D can serve as the project management interface for the second session, used to view and manage configuration information, participant information, and project space information related to the second session.

[0110] In some examples, the project management component 241 can be presented in the interface 200D. The project management component 241 can display basic information about the second session. For example, the project management component 241 can present the session name (e.g., "Project C"), description, task type, creation time, current status, or other information related to the second session.

[0111] In some examples, project management component 241 may include modification controls for modifying project configurations. In response to triggering these modification controls, electronic device 110 may present an interactive interface for modifying configuration parameters in a second session. For example, a user can modify the project name, project description, project type, or other configuration parameters.

[0112] In some examples, configuration parameters modified via the project management component 241 can be synchronously updated to the corresponding second session. For instance, in response to a user modifying the project name, the electronic device 110 can synchronously update the session information in the second interface and the project name displayed in the corresponding session entry. In response to a user modifying the project description information, the electronic device 110 can synchronously update the task descriptions related to the project. Through the project management component, users can centrally view and modify the attribute information of the second session, facilitating the management of the second session.

[0113] In some examples, the interface 200D may also display a member management control 242. The member management control 242 is used to display a list of participants currently in the second session. For example, the member management control 242 may display user accounts and smart systems participating in the second session, and show the status information of each participant.

[0114] In some examples, the member management control 242 can also provide entry points for adding, removing, or adjusting participants' permissions. For instance, a user can use the member management control 242 to send an invitation to a new collaborating user and add them to a second session after receiving confirmation. The member management control 242 enables dynamic adjustment of collaborating members around the primary task, improving flexibility in multi-participant collaboration scenarios.

[0115] In some examples, the interface 200D may also display an intelligent system management control 243. The intelligent system management control 243 is used to display the intelligent systems currently participating in the second session and supports the management of these intelligent systems. For example, different intelligent systems can be responsible for different task capabilities. Users can dynamically add new intelligent systems or remove existing ones through the intelligent system management control 243. In response to a newly added intelligent system, the electronic device 110 can add the new intelligent system to the participant list of the second session, enabling the new intelligent system to participate in subsequent task processing. Thus, the second session not only supports multi-user collaboration but also allows multiple intelligent systems to collaboratively process the same task, thereby forming a task-oriented collaborative environment.

[0116] In some examples, the interface 200D may also display other settings areas. These other settings areas can provide management access points for the second session and the first content item management space. For example, other settings areas may include archiving the second session, restoring the second session, deleting the second session, exporting the second session, configuring storage path, or configuring permissions.

[0117] In some examples, management operations for the second session and management operations for the first content item management space can be independent of each other. For example, a user can end the second session while retaining the first content item management space, or perform an archiving operation on the first content item management space while keeping the second session available. As another example, a user can export content items from the first content item management space through an export entry point without depending on the existence state of the second session. Therefore, the first content item management space can be persistently retained as a resource management space independent of the second session.

[0118] like Figure 2E As shown, the electronic device 110 can present an interface 200E for member management. Interface 200E can serve as the member management interface for the second session, used to manage collaborating members participating in the first task. For example, interface 200E can present a member search control 251 and an add control 252. The member search control 251 can provide a search box to support locating collaborating users through specific search criteria. For example, users can search for potential participants based on user identifiers, organizational information, job information, historical collaboration records, or other criteria. The add control 252 is used to trigger a member invitation operation to determine whether to send a request to the located user to join the second session.

[0119] In some examples, interface 200E may also display list 253. List 253 is used to display members who have joined the second session and members who are awaiting confirmation of joining the second session. For example, list 253 may display member name, member type, member status, and other information. Member status may include, for example, "awaiting confirmation," "joined," "rejected," or "exited." By displaying list 253, the current participants can promptly understand the status of collaborating members in the second session.

[0120] In some scenarios, similar to the process described above in conjunction with the third control 213, in response to adding a collaborating member (e.g., user A) via the add control 252, electronic device 110 can send an invitation message to user A. As an example, electronic device 110 can send user A a private message, in-app notification, message alert, or other form of invitation message. The invitation message may include information related to the second session. For example, the invitation message may include the name of the second session, a description of the first task, information about the current participants, and an entry point for joining the second session.

[0121] In some examples, in response to user A triggering the project entry or performing a confirmation join operation, electronic device 110 can add user A to the participant list of the second session. Accordingly, the status of user A in list 253 can be updated from "Pending Confirmation" to "Joined". If user A refuses to join, the status of user A in list 253 can be updated to "Refused". In this way, collaborative users added via member management can join the second session after confirmation, ensuring the controllability of member joining.

[0122] In some scenarios, electronic device 110 can also automatically recommend suitable intelligent systems to participate in the task based on the task requirements of the first task, and present the recommendations in interface 200E. In response to the user selecting a corresponding intelligent system, electronic device 110 can add that intelligent system to the second session. By supporting unified management of user members and intelligent system members, the second session can form a task-oriented collaborative processing environment.

[0123] In some situations, when a member invitation is first initiated via the member search control 251 and the add control 252, the electronic device 110 may display a prompt message. The prompt message may explain the collaboration rules, member permissions, or task assignment information corresponding to the second session. For example, the prompt message may indicate that the second session is a multi-person collaboration mode, and that newly added members can access content items related to the first task and historical interaction records.

[0124] In some situations, when a new member or a new intelligent system joins the second session, the electronic device 110 can automatically display corresponding prompt messages in the session flow of the second session. For example, the prompt messages may indicate: a user has joined the second session; a user has left the second session; an intelligent system has joined the second session; an intelligent system has been removed; or the second session has switched to collaborative mode.

[0125] In some scenarios, if the second session transitions from an interaction mode between the initiator and a single intelligent system to a multi-participant collaborative mode, the prompt message can also include interactive guidance corresponding to the collaborative mode. For example, the prompt message could instruct new members on how to view historical content, how to access the first content item management space, and how to collaborate with the intelligent system to complete the first task. By automatically presenting system messages in the session flow, all participants can promptly perceive changes in members and collaborative status during the second session, improving the transparency and continuity of the collaborative process.

[0126] In summary, during the initial interaction between the user and the intelligent system, by proactively presenting the initial information for creating the second session and supporting the creation of a second session corresponding to the first task based on user actions, tasks originally scattered across ordinary sessions can be automatically organized into dedicated project sessions for continuous progress. By inheriting the task context, task configuration, and participant information from the first session when creating the second session, the system reduces the operational costs for users to repeatedly organize task backgrounds and reconfigure the collaboration environment, thereby improving the efficiency of the transition from requirements discussion to task execution.

[0127] Furthermore, by providing the second session with page layouts, functional components, and collaboration capabilities that match the task type, the second session can build corresponding processing environments for different types of tasks, thereby improving the interaction and processing efficiency during task execution.

[0128] Therefore, the proposed solution enables a natural transition from instant dialogue to project-based collaboration, allowing the intelligent system to not only participate in problem-solving but also continuously organize resources, accumulate results, and advance task execution around user tasks, thereby enhancing the intelligent interactive system's ability to support long-term and complex tasks.

[0129] 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.

[0130] like Figure 3 As shown in box 310, electronic device 110 presents first information on a first interface. The first interface is used to display a first session, which is associated with a first intelligent system. The first information indicates the creation of a second session.

[0131] In box 320, electronic device 110 receives a first operation associated with first information, the first operation being used to create a second session, the participants of which include at least the first intelligent system.

[0132] In box 330, electronic device 110 presents the session entry point for the second session and, in response to the triggering of the session entry point, presents a second interface for displaying the second session. In this manner, the creation of the second session can be conveniently initiated during the interaction of the first session, and the second session, with participants including at least the first intelligent system, can be carried out via the session entry point and the second interface, thereby improving the efficiency of interaction organization and reducing the operational overhead required for users to handle processing needs.

[0133] In some cases, the first piece of information can be associated with the first task, and the second session can be used to execute the first task. In this way, the second session can be organized around the first task, improving the processing efficiency of the first task.

[0134] In some cases, the first information may also indicate at least one configuration parameter for the second session, and this at least one configuration parameter is determined based on the session content of the first session. In this way, the second session can inherit the interaction context accumulated in the first session, improving the creation efficiency of the second session.

[0135] In some cases, at least one configuration parameter may include the session name of the second session, descriptive information describing the first task, the type of the second session related to the content of the first session, or at least one of the participants in the second session. This allows users to intuitively understand the overview of the second session before creating it, facilitating their decision-making.

[0136] In some scenarios, participants may include a second intelligent system, which is added to the participant list of the second session in response to the first operation. This enables the second session to possess the collaborative capabilities required to perform the first task, reducing the need for users to manually add participants.

[0137] In some cases, the first information is presented in a first component of a first interface. This first component includes a first control, and receiving the first operation may include receiving the first operation via the first control. In this way, the operation of creating a second session can be carried out in the first component that presents the first information, improving the continuity of the interaction.

[0138] In some cases, the first component may also include a second control, via which the electronic device 110 can receive a second operation to refuse the creation of a second session and update the display style of the first information in response to the second operation. In this way, clear interactive feedback can be provided when the user does not expect the creation of a second session, and the interference of the first information on the first session interaction process can be reduced.

[0139] In some cases, the first component may also include a third control, through which the electronic device 110 can receive a third operation instructing the modification of at least one configuration parameter of the second session, and present updated first information indicating the creation of the second session based on the modified configuration parameter. In this way, the configuration of the second session can be more closely aligned with the user's actual intent, improving the usability of the second session.

[0140] In some cases, the first task can belong to the first type, and the layout of the second interface can match the first type. This allows the second interface to better suit the actual processing scenario of the first task, improving its processing efficiency.

[0141] In some cases, presenting a second interface may include presenting at least one functional component on the second interface, the at least one functional component being used to perform the first task, and the type of the at least one functional component matching the first type. In this way, the second interface can be equipped with the capabilities required to perform the first task, reducing the operational overhead of users switching between different tools.

[0142] In some cases, presenting a second interface may include displaying contextual information on the second interface. This contextual information comes from the session content of the first session and is related to the first task. In this way, the second session can inherit the interaction context accumulated in the first session, reducing the need for the user to provide background information again in the second session.

[0143] In some cases, the electronic device 110 can also receive a fourth operation on the second interface. This fourth operation requests the presentation of at least one content item related to the second session. The at least one content item is stored in a first content item management space, whose lifecycle management is independent of the second session's lifecycle management. The electronic device 110 can also present a first area on the second interface for managing the at least one content item. In this way, the process data and outputs of the first task can be persistently saved, preventing the loss of content items due to the end of the session.

[0144] In some cases, at least one content item is formed based on the first task in at least one of the first and second sessions. In this way, data related to the first task can be completely collected into the first content item management space, facilitating unified management of the process data of the first task.

[0145] In some scenarios, at least one content item may include at least one of a first content item, a second content item, or a third content item. The first content item is included during the interaction of a first session and is related to a first task, and is added to the first content item management space in response to the creation of a second session. The second content item is received via a first area, and the third content item is generated via the interaction of the second session. This approach enables the first content item management space to be compatible with content items from multiple sources, improving the completeness of content item management.

[0146] In some cases, presenting the first information on the first interface may include: responding to the first task meeting preset conditions, whereby the first information is presented on the first interface, and the preset conditions include at least one of the following: the estimated completion time of the first task exceeds a time threshold, the number of processing steps required by the first task exceeds a quantity threshold, or the number of pending objects associated with the first task exceeds an object threshold. In this way, guidance can be provided only when the first task is indeed suitable for being carried out in a separate second session, avoiding unnecessary prompts and improving the accuracy of guidance.

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

[0148] Figure 4 Block diagrams of a device 400 for user interface interaction are shown in several scenarios. 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.

[0149] like Figure 4 As shown, the device 400 includes a first presentation module 410 configured to present first information on a first interface, the first interface being used to display a first session, the first session being associated with a first intelligent system, and the first information indicating the creation of a second session; a receiving module 420 configured to receive a first operation associated with the first information, the first operation being used to create a second session, the participants in the second session including at least the first intelligent system; and a second presentation module 430 configured to present a session entry for the second session, and in response to triggering the session entry, present a second interface, the second interface being used to display the second session.

[0150] In some cases, the first information is associated with the first task, and the second session is used to perform the first task.

[0151] In some cases, the first information may also indicate at least one configuration parameter of the second session, and the at least one configuration parameter is determined based on the session content of the first session.

[0152] In some cases, at least one configuration parameter may include at least one of the following: the session name of the second session, descriptive information for describing the first task, the type of the second session related to the session content of the first session, or the participants of the second session.

[0153] In some cases, the participants may include a second intelligent system, and the second intelligent system is added to the participant list of the second session in response to the first operation.

[0154] In some cases, the first information is presented in a first component of the first interface, the first component including a first control, and the receiving module 420 may also be configured to receive a first operation via the first control.

[0155] In some cases, the first component may also include a second control, and the device 400 may also be configured to receive a second operation via the second control, the second operation being used to refuse to create a second session and to update the display style of the first information in response to the second operation.

[0156] In some cases, the first component may also include a third control, and the device 400 may also be configured to receive a third operation via the third control, the third operation instructing modification of at least one configuration parameter of the second session, and presenting updated first information instructing the creation of the second session based on the modified at least one configuration parameter.

[0157] In some cases, the first task belongs to the first type, and the page layout of the second interface matches the first type.

[0158] In some cases, the second presentation module 430 may also be configured to present at least one functional component on the second interface, the at least one functional component being used to perform the first task, and the type of the at least one functional component matching the first type.

[0159] In some cases, the second presentation module 430 can also be configured to present context information on the second interface, the context information being derived from the session content of the first session and related to the first task.

[0160] In some cases, the device 400 may also be configured to receive a fourth operation on a second interface, the fourth operation being used to request the presentation of at least one content item related to the second session, the at least one content item being stored in a first content item management space, the lifecycle management of the first content item management space being independent of the lifecycle management of the second session, and a first area being presented on the second interface, the first area being used to manage at least one content item.

[0161] In some cases, at least one content item is formed based on the first task in at least one of the first and second sessions.

[0162] In some cases, at least one content item may include at least one of the following: a first content item, which is included in the interaction process of a first session and is related to a first task, and is added to the first content item management space in response to the creation of a second session; a second content item, which is received via a first area; or a third content item, which is generated via the interaction process of a second session.

[0163] In some cases, the first presentation module 410 may also be configured to present first information on the first interface in response to the first task meeting preset conditions. The preset conditions include at least one of the following: the estimated completion time of the first task exceeds a time threshold, the number of processing steps required by the first task exceeds a quantity threshold, or the number of pending objects associated with the first task exceeds an object threshold.

[0164] 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.

[0165] Figure 5 A block diagram of an electronic device 500 in which multiple illustrative scenarios can 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 illustrated electronic device 500 can be used to implement the electronic device 110 or device 400 discussed above.

[0166] 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.

[0167] 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.

[0168] 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.

[0169] 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.

[0170] 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 an input / output (I / O) interface (not shown).

[0171] 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.

[0172] 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.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] 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 user interface interaction, comprising: The first interface presents first information, which is used to display a first session. The first session is associated with a first intelligent system, and the first information indicates the creation of a second session. Receive a first operation associated with the first information, the first operation being used to create a second session, the participants of the second session including at least the first intelligent system; as well as Present the session entry point of the second session, and in response to the triggering of the session entry point, present the second interface, which is used to display the second session.

2. The method of claim 1, wherein the first information is associated with a first task, and the second session is used to perform the first task.

3. The method of claim 1, wherein the first information further indicates at least one configuration parameter of the second session, and the at least one configuration parameter is determined based on the session content of the first session.

4. The method of claim 3, wherein the at least one configuration parameter includes at least one of the following: The session name of the second session. The description information of the second session, which is used to describe the first task. The type of the second session, which is related to the content of the first session, or The participants in the second session.

5. The method of claim 4, wherein the participant includes a second intelligent system, and the second intelligent system is added to the participant list of the second session in response to the first operation.

6. The method according to claim 1, wherein the first information is presented in a first component of the first interface, the first component includes a first control, and receiving the first operation includes: The first operation is received via the first control.

7. The method of claim 6, wherein the first component further comprises a second control, and the method further comprises: The second operation is received via the second control, and the second operation is used to refuse to create the second session; as well as In response to the second operation, update the display style of the first information.

8. The method of claim 6, wherein the first component further comprises a third control, and the method further comprises: A third operation is received via the third control, the third operation instructing modification of at least one configuration parameter of the second session; as well as An updated first message is presented, which indicates that the second session is created based on at least one modified configuration parameter.

9. The method according to claim 2, wherein the first task belongs to a first type, and the page layout of the second interface matches the first type.

10. The method of claim 9, wherein presenting the second interface comprises: The second interface presents at least one functional component, which is used to perform the first task, and the type of the at least one functional component matches the first type.

11. The method of claim 2, wherein presenting the second interface comprises: The second interface presents context information, which comes from the session content of the first session and is related to the first task.

12. The method according to claim 1, further comprising: The second interface receives a fourth operation, which is used to request the presentation of at least one content item related to the second session. The at least one content item is stored in a first content item management space, and the lifecycle management of the first content item management space is independent of the lifecycle management of the second session. as well as The second interface presents a first area, which is used to manage the at least one content item.

13. The method of claim 12, wherein the at least one content item is formed based on a first task in at least one of the first session and the second session.

14. The method of claim 13, wherein at least one content item comprises at least one of the following: The first content item, which is included in the interaction process of the first session and is related to the first task, is added to the first content item management space in response to the creation of the second session. The second content item, the second content item is received via the first area, or The third content item is generated through the interaction process of the second session.

15. A device for interface interaction, comprising: A first presentation module is configured to present first information on a first interface, the first interface being used to display a first session, the first session being associated with a first intelligent system, and the first information indicating the creation of a second session. The receiving module is configured to receive a first operation associated with the first information, the first operation being used to create a second session, the participants of the second session including at least the first intelligent system; as well as The second presentation module is configured to present the session entry of the second session and, in response to the triggering of the session entry, present a second interface for displaying the second session.

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

17. A computer-readable storage medium having stored thereon computer-executable instructions that can be executed by a processor to implement the method according to any one of claims 1 to 14.

18. 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 14.

Images