Methods, apparatuses, devices, media, and program products for session management

Abstract

Methods, apparatuses, devices, media, and program products for session management are provided. The method includes receiving a first operation, the first operation indicating to view information related to a first intelligent system, and presenting at least one content item, the at least one content item respectively corresponding to at least one session, a content item of the at least one content item displaying information related to a corresponding session, each session of the at least one session being participated by the first intelligent system and at least two objects, the at least two objects being different from the first intelligent system.

Description

Technical Field

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

[0002] With the development of artificial intelligence technology, intelligent systems are widely used in scenarios such as information acquisition, content generation, task execution, and collaborative work. In some scenarios, intelligent systems can not only provide services in one-to-one conversations between users and the system, but also participate in conversations involving multiple parties. For example, an intelligent system can join a conversation involving multiple users as a member, responding to messages, providing information, performing tasks, and participating in collaborative work. Summary of the Invention

[0003] In a first aspect, a session management method is provided. The method includes: receiving a first operation, the first operation instructing the viewing of information related to a first intelligent system; and presenting at least one content item, each of the at least one content item corresponding to at least one session, the content items displaying information related to the corresponding session, each of the at least one session involving the first intelligent system and at least two objects, the at least two objects being different from the first intelligent system.

[0004] In a second aspect, an apparatus for session management is provided. The apparatus includes: a receiving module configured to receive a first operation instructing the viewing of information related to a first intelligent system; and a presentation module configured to present at least one content item, each content item corresponding to at least one session, the content items displaying information related to the corresponding session, each session involving the first intelligent system and at least two objects, the at least two objects being different from the first intelligent system.

[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, by presenting information related to the first intelligent system through the content items corresponding to the session as a unified entry point, users can clearly perceive and manage the context and state of the first intelligent system in each session among multiple sessions involving the first intelligent system and at least two objects.

[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 2G The diagram illustrates sample interfaces for session management in several scenarios. Figure 3 The flowcharts show example processes for session management in several scenarios; Figure 4 Block diagrams of apparatuses for session management in several scenarios are shown; and Figure 5 A block diagram of an electronic device capable of implementing multiple illustrative scenarios is shown. Detailed Implementation

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

[0015] In this manual and the examples, any solutions involving the processing of personal information will be processed only on the premise of a legal basis (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be processed 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, "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 representatives, 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] As used in this document, the term "session" refers to an entity involving two or more objects that serves to carry out message interaction. In some examples, a session may include, but is not limited to: a session involving an intelligent system and a single user (e.g., a default session, a one-on-one chat session), and a session involving an intelligent system and at least two objects (e.g., a group chat session). The session involving a first intelligent system and at least two objects different from the first intelligent system, as described in this document, can be understood as an implementation of a group chat session.

[0018] As mentioned above, intelligent systems can generate responses or perform corresponding tasks based on interactive requests. Intelligent systems can also join multiple conversations as members and perform tasks such as information retrieval, content generation, data analysis, message notification, and automated processing in different conversations. For example, an intelligent system can be introduced into multiple group chat conversations to participate in multi-person collaboration. In this scenario where multiple intelligent systems, multiple conversations, and multiple topics may coexist, managing the context, memory, tasks, and configuration of the intelligent system presents the following difficulties.

[0019] In some solutions, as the number of sessions the intelligent system participates in increases, users find it difficult to clearly perceive which sessions the intelligent system is involved in, as well as the system's operational status and configuration in different sessions. Furthermore, the lack of a unified session management mechanism when the intelligent system runs in parallel across multiple sessions makes it difficult for users to view and manage the corresponding session information in a timely manner, thus affecting the efficiency of using and managing the intelligent system across different sessions.

[0020] A session management scheme is proposed. According to the scheme, an electronic device receives a first operation that instructs the user to view information related to a first intelligent system; in response to the first operation, the electronic device presents at least one content item, each corresponding to at least one session, the content item displaying information related to the corresponding session, and each session in the at least one session involving the first intelligent system and at least two objects, the at least two objects being different from the first intelligent system.

[0021] The above scheme uses the content items corresponding to a conversation involving the first intelligent system and at least two other objects as a unified presentation object. This allows users to view multiple conversations they participate in from the perspective of the first intelligent system, enabling them to further view and manage the first intelligent system on a conversation-by-conversation basis. By establishing a management entry point at the conversation level, it is beneficial to improve users' awareness and management capabilities regarding the first intelligent system's participation in conversations, thereby enhancing the management efficiency of the first intelligent system in multi-conversation scenarios.

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

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

[0024] In this example environment 100, electronic device 110 can run an application 120 that supports session management. Application 120 can be any suitable type of application for session management, including but not limited to: client applications running on a web platform, a personal computer (PC) platform, or other suitable platforms. User 140 can interact with application 120 via electronic device 110 and / or its attached devices.

[0025] exist Figure 1 In environment 100, if application 120 is active, electronic device 110 can present interface 150 for supporting session management through application 120.

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

[0027] 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 background services for applications 120 that support session management in electronic devices 110.

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

[0029] 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. The example will continue to be described below with reference to the accompanying drawings.

[0030] It should be understood that, in some cases, the processes described above and below can be executed locally by electronic device 110 without relying on server 130. Alternatively or additionally, the example processes described with reference to electronic device 110 can also be executed solely by server 130, or jointly by electronic device 110 and server 130. The actions described with reference to electronic device 110 can be performed by electronic device 110 by running application 120. The interface described with reference to electronic device 110 can be presented by electronic device 110 by running application 120. In some cases, application 120 can be provided by an intelligent system management service or intelligent system management platform. The intelligent system management service or intelligent system management platform can provide users with the ability to manage one or more intelligent systems.

[0031] Figure 2A A schematic diagram of the session management interface 200A based on certain scenarios is shown below. (Refer to the following...) Figure 2A To describe the session management process. Interface 200A can be... Figure 1 The electronic device 110 shown is provided via application 120.

[0032] In some scenarios, intelligent systems can participate in multiple sessions and perform tasks such as information retrieval, content generation, message notification, and automated processing in different sessions. For example, when an intelligent system participates in multiple sessions simultaneously, users typically need to enter each session separately to view the corresponding operational status of the intelligent system, thus increasing management costs. To address this, this solution provides a session management interface 200A to provide a unified presentation and management of one or more group chat sessions in which the intelligent system participates. Through the session management interface 200A, users can centrally view multiple sessions in which the intelligent system participates and further manage information, tasks, and configurations related to the corresponding sessions, thereby improving the user's management efficiency of the intelligent system.

[0033] like Figure 2A As shown, interface 200A includes a first area 211. The first area 211 can be used to trigger the viewing of one or more smart systems associated with a user account. The smart systems that the user can view can be smart systems to which the user has predefined permissions (e.g., administrative permissions). The user can switch between different smart systems through the first area 211 to view the sessions participated in by the corresponding smart system. The first smart system can correspond to the currently selected smart system. For example, in... Figure 2A In this context, the first intelligent system corresponds to the currently selected assistant B. Furthermore, the first area 211 may also include controls for creating new intelligent systems, allowing the user to create such systems.

[0034] In some cases, interface 200A may include a second area 212. The second area 212 can be used to present a conversation between the first intelligent system and a single user. For example, the user can have a one-on-one conversation with the first intelligent system through the second area 212 to issue instructions to the first intelligent system, receive responses, or perform tasks.

[0035] In some cases, electronic device 110 may display configuration control 214 in interface 200A. Configuration item 214 is used to trigger detailed configuration of the currently selected first intelligent system. For example, users can access the configuration interface of the first intelligent system through configuration item 214 to view, edit, or adjust the role settings, behavior rules, permission scope, knowledge base resources, tool capabilities, automation strategies, and other system-level configuration content of the first intelligent system.

[0036] In one scenario, electronic device 110 can receive a first operation instructing the user to view information related to a first intelligent system. As an example, this first operation could be a selection operation on the first intelligent system in a first area 211, such as a user clicking or selecting Assistant B in the first area 211. In response to this first operation, electronic device 110 can present at least one content item on interface 200A, each corresponding to at least one session. The content item corresponding to a session can be understood as an interface element representing the corresponding session. The user can view a summary of the corresponding session through this content item and further manage the corresponding session. Electronic device 110 can simultaneously present multiple content items on interface 200A to display multiple sessions in which the first intelligent system has participated, such as content item 215 corresponding to group chat session 1, and other content items.

[0037] As used in this document, the term "content item" refers to a visual entry used to represent a session on the interface for users to switch, view, and manage. It typically includes, but is not limited to, an identifier, name, summary, status, and one or more triggerable elements related to the corresponding session. Content items can serve as entry points for contextual, memory, task, and / or configuration management of the corresponding session.

[0038] In some scenarios, at least one session involves a first intelligent system and at least two objects, which are different from the first intelligent system. At least one session corresponding to at least one content item can be a group chat session. For example, a group chat session may include multiple users in addition to the first intelligent system, or it may include one or more users and other intelligent systems. The content items in interface 200A are used to display the group chat sessions that the user has participated in with the first intelligent system, allowing the user to centrally view multiple group chat sessions in which the first intelligent system participates, and further configure and manage the first intelligent system at the level of group chat sessions.

[0039] In some cases, such as Figure 2A As shown, at least one content item displays information related to the corresponding session (such as session name, participant identifier, message summary, recent activity time, and other information describing the corresponding session). In this way, users can quickly understand the basic information of each session and select a target session for further management.

[0040] By employing the above method, multiple group chat sessions involving the first intelligent system are organized into multiple content items and presented centrally, allowing users to understand the sessions in which the first intelligent system participates without having to enter each different group chat individually. Furthermore, since subsequent information management, task management, and configuration management can all be based on the sessions corresponding to the content items, a management entry point for the intelligent system can be established at the session level, thereby improving the efficiency of users in viewing and managing the intelligent system across multiple group chat sessions.

[0041] In some cases, the session corresponding to a content item can be associated with a context identifier, which is determined based on at least two of the following: a first identifier for identifying the first intelligent system, a second identifier for identifying the corresponding session, and a third identifier for identifying the user participating in the corresponding session (e.g., user 140). The electronic device 110 can generate a context identifier corresponding to the corresponding session based on at least two of the above identifiers, and use the context identifier to establish an association between the session and the runtime state of the first intelligent system.

[0042] The term "context identifier" (also known as a context key) used in this document refers to an index used to bind a session to the runtime state of an intelligent system. In some examples, the context identifier can be determined based on at least two of the following: a first identifier for identifying the intelligent system, a second identifier for identifying the session (e.g., a session identifier for a group chat session), and a third identifier for identifying the user (e.g., a user container identifier). Context identifiers can be used to isolate data and configurations from different sessions and / or different users.

[0043] In some cases, runtime state may include context information, historical information, task information, configuration information, and other information generated or used during operation related to the first intelligent system. Using the above method, the corresponding session can be bound to the runtime state of the first intelligent system based on the context identifier, thereby managing and isolating the runtime state at the session level.

[0044] As an example, during the execution of a task or generation of a response by the first intelligent system in the first session, the electronic device 110 can obtain the runtime state associated with the first session based on the context identifier corresponding to the first session. Similarly, during the execution of a task or generation of a response by the first intelligent system in the second session, the electronic device 110 can obtain the runtime state associated with the second session based on the context identifier corresponding to the second session. Since different sessions correspond to different context identifiers, information related to other sessions does not need to be loaded into the processing flow corresponding to the current session.

[0045] In this way, corresponding sessions can be bound to the runtime state (such as context, memory, tasks, and configuration) of the first intelligent system based on context identifiers, thereby isolating the runtime state at the session level. On the other hand, since different sessions are indexed through different context identifiers, irrelevant information loaded into the current processing flow can be reduced, thus lowering the data retrieval scope and the query overhead of the backend storage system.

[0046] In some scenarios, electronic device 110 may receive a second operation triggered on a first content item among at least one content item, the first content item corresponding to a first session among at least one session. In response to the second operation, electronic device 110 presents configuration information for managing the first intelligent system within the first session. For example, the configuration information may relate to the data usage scope, historical information, task information, operating status, or other management information of the first intelligent system within the first session. Users can view or adjust the actions or rules executed by the first intelligent system within the first session based on this configuration information.

[0047] In some cases, content items may be presented as cards, list items, or other forms of interface elements. For ease of illustration, the following description of the management process for a group chat session 1 will use content item 215 as an example. It should be understood that other content items may also include elements that are the same as or similar to content item 215 for configuration and management of the first intelligent system in the corresponding session.

[0048] In some cases, at least one content item is presented sequentially on interface 200A, the order of which relates to the active state of the first intelligent system in the at least one session. As an example, the content items can be rearranged according to the most recent interaction time between the user and the first intelligent system in the corresponding session, such that content items corresponding to sessions in which the user has recently interacted with the first intelligent system are ranked first.

[0049] In some cases, an active state can also be related to at least one of the following: the message sending frequency, message receiving frequency, number of tasks, number of tasks being executed, task execution frequency, task execution duration, or task processing volume of the first intelligent system in the corresponding session. For example, for sessions with ongoing tasks or high task execution frequency, electronic device 110 can increase the sorting priority of the corresponding content item; for sessions with no interaction for a long time and no active tasks, electronic device 110 can decrease the sorting priority of the corresponding content item.

[0050] In this way, users can prioritize viewing conversations that have more frequent interactions with the first intelligent system or have more active task activities, thereby reducing the number of operations required to find the target conversation among a large number of conversations and improving the efficiency of conversation location.

[0051] In some cases, at least one content item may include one or more elements corresponding to session settings, used to trigger the presentation of configuration information related to the corresponding session.

[0052] See Figure 2A Content item 215 includes a first element 215-1. The first element 215-1 is used to trigger the presentation of configuration information for managing the first intelligent system in the corresponding session. For example, the first element 215-1 may correspond to a session settings function. The electronic device 110 may receive a second operation issued to the first element 215-1, thereby presenting an interface for viewing or adjusting the configuration of the first intelligent system in the corresponding session.

[0053] The term “configuration information” as used in this document refers to information used to manage an intelligent system in a session, which may typically include, but is not limited to, information indicating the range of data available to the intelligent system in a session, and information indicating the tasks that the intelligent system performs for the session.

[0054] Figure 2B A schematic diagram of the session management interface 200B based on certain scenarios is shown. See below for reference. Figure 2B This describes the process of presenting configuration information. For example... Figure 2B As shown, in response to a second operation issued for the first element 215-1, the electronic device 110 can present configuration information. For example, the configuration information may include first information 220. The first information 220 may be used to indicate the range of data that the first intelligent system is allowed to use in the first session.

[0055] In some cases, presenting the first information includes presenting a plurality of information items 221, each corresponding to a plurality of available data ranges. The electronic device 110 may receive a third operation instructing the selection of at least one of the plurality of information items 221. The selected at least one information item corresponds to at least one available data range, and the first intelligent system is configured to perform an action based on the at least one available data range in a first session.

[0056] In some scenarios, when processing messages, generating responses, or performing tasks in a first session, the first intelligent system may access various associated data. For example, this data may include information describing the first intelligent system's behavioral rules, user-related historical context information, user profile information, long-term memory information, and other data available for use by the first intelligent system. First information 220 may be used to indicate which of the aforementioned data is permitted to be loaded and used in the first session.

[0057] In other words, the first information 220 differs from the global configuration used to define the attributes of the first intelligent system itself. For example, the global configuration of the first intelligent system can simultaneously include work rule information, long-term memory information, and user profile information. In the first information 220 corresponding to the first session, it can be configured to only allow loading of work rule information, while disallowing loading of long-term memory information and user profile information. In this case, the first intelligent system still retains all the aforementioned global configurations, but when processing the first session, it only performs actions based on the work rule information.

[0058] In this way, users can limit the range of data that the First Intelligence System can load within a single session, granularly. For example, in a group chat session, only workspace rules are enabled by default, while other configurations such as long-term memory and personal profiles are disabled. This avoids the First Intelligence System loading data irrelevant to the current session or unsuitable for sharing in multi-user collaborative scenarios. Furthermore, it allows the First Intelligence System to perform actions only based on the selected data range, thereby reducing the amount of data that needs to be loaded, retrieved, and processed, improving the targeting of data utilization, and reducing the storage and computational overhead caused by redundant data.

[0059] In some cases, multiple information items 221 may include a first information item corresponding to a first available data range. The electronic device 110 may present the first information item in a first style corresponding to a selected state; and present at least one second information item in a second style different from the first information item, the second style corresponding to an unselected state.

[0060] like Figure 2B As shown, selected and unselected information items are distinguished by different styles such as checked / unchecked. For example, the first information item corresponds to work rule information and is presented in a selected state; while the second, third, and fourth information items correspond to long-term memory information, user profile information, or other personalized information, respectively, and are presented in an unselected state by default.

[0061] In this way, users can intuitively distinguish which available data ranges are selected, reducing the need for repeated checks and accidental operations to confirm the currently effective configuration. Furthermore, by limiting the available data range of agents in group chat scenarios, the likelihood of information unrelated to the current collaboration scenario being loaded into the processing flow can be reduced, thereby improving the targeting of data usage by the First Intelligence System in multi-person collaboration scenarios.

[0062] In some cases, interface 200B may also include a cleanup context control 222, which is used to trigger the cleanup of short-term context for the first session. For example, during continuous interaction with the user, the first intelligent system can maintain a short-term context related to the first session based on recent rounds of messages. As the number of interaction rounds increases, information unrelated to the current task may accumulate in the short-term context. The user can trigger the cleanup of the aforementioned short-term context information through the cleanup context control 222. In response to the user's operation on the cleanup context control 222, electronic device 110 can delete, disable, or stop loading at least some of the short-term context information corresponding to the first session, while retaining the long-term configuration, task information, or other operational information corresponding to the first session. In this way, the user can clean up irrelevant short-term context at the session level, reducing the user's operations of distinguishing and cleaning up different session contexts.

[0063] In some cases, the configuration information may include second information, which may indicate at least one task performed by the first intelligent system for the first session. As used herein, the term "task" refers to a processing unit performed or to be performed by the intelligent system for a session. For example, during participation in a session, the first intelligent system may execute one or more tasks based on messages, user requests, or other triggering conditions within the session. These one or more tasks may be used to perform information retrieval, content generation, data analysis, message notification, automated processing, or other operations. By uniformly managing tasks associated with the first intelligent system at the session level, users do not need to access each session individually to view the task status of each session, thereby improving the management efficiency of the first intelligent system.

[0064] In some scenarios, at least one task may include at least one first-type task, which is triggered in response to at least one message in the first session. For example, if a first user sends a message in the first session requesting the first intelligent system to perform a certain operation, the first intelligent system may create a corresponding first-type task. The first-type task may correspond to a one-time task execution process and end after the corresponding operation is completed.

[0065] In some scenarios, the primary intelligent system can create multiple primary type tasks for the same session and execute different processing flows for each. For example, if a message requests the primary intelligent system to investigate multiple objects, the system can create multiple independent primary type tasks to execute the corresponding processes in parallel. Therefore, different primary type tasks can have independent execution states, processing results, and running processes.

[0066] As an example, refer to Figure 2A Content item 215 may include a second element 215-2. The second element 215-2 is used to trigger the presentation of first task information related to the first type of task. Figure 2C A schematic diagram of the session management interface 200C based on certain scenarios is shown. See below for reference. Figure 2C To describe the process of presenting the first task information.

[0067] In some cases, in response to receiving a second operation triggered by the second element 215-2, the electronic device 110 may present first task information relating to the at least one first type of task. For example... Figure 2C As shown, interface 200C may include a first task information area 230. The first task information area 230 is used to display the first task information of the first intelligent system in the first session.

[0068] In some cases, the first task information area 230 may include a task filtering control 231 and a task search control 232. The task filtering control 231 allows the user to view first-type tasks associated with the current first session. For example, the user can use the task filtering control 231 to view tasks only associated with the first session, or switch to the all-tasks view to view all first-type tasks corresponding to the first intelligent system. The task search control 232 receives search criteria to search for a target task among one or more first-type tasks. For example, the user can enter a task name, task keywords, or other search information to locate the corresponding task.

[0069] In some cases, the interface 200C may also include a task entry list 233. The task entry list 233 is used to present task entries corresponding to at least one first-type task. For example, each task entry may correspond to one first-type task and display information related to that first-type task.

[0070] As an example, the information presented in the task entry list 233 may include at least one of the following: basic information of the first type of task, such as task name, task summary or task creation time; status information of the first type of task, such as in progress, completed, failed, paused or stopped; or result information of the first type of task, such as a summary of the task execution result.

[0071] In this way, users can directly view the first type of tasks executed by the first intelligent system for that session, using the first session as the entry point, and quickly understand the execution status of each task without having to return to the corresponding session to find the source of each task. Furthermore, since the tasks in the task list are associated with the first session, tasks can be filtered and queried based on the context identifier corresponding to the first session, thereby reducing the data scope involved in the task retrieval process and improving task management efficiency.

[0072] In some cases, at least one task includes at least one second-type task, which is triggered in response to the satisfaction of at least one predetermined condition. For example, the second-type task may be pre-associated with one or more predetermined conditions. If the corresponding predetermined condition is satisfied, the first intelligent system executes the corresponding task.

[0073] As an example, the predefined conditions may include at least one of the following: reaching a predetermined time; reaching a predetermined time period; receiving a message of a predetermined type; detecting a predetermined event; or satisfying predetermined data conditions. Unlike the first type of task, the second type of task does not need to be triggered immediately by the current message, but can be executed automatically when the predefined conditions are met. Therefore, the second type of task can be used for periodic tasks, continuous monitoring tasks, automatic notification tasks, automatic synchronization tasks, and other automated processing tasks.

[0074] In some cases, refer to Figure 2A Content item 215 may include a third element 215-3. The third element 215-3 is used to trigger the presentation of second task information related to the second type of task. Figure 2D A schematic diagram of the interface 200D for session management based on certain scenarios is shown below. (Refer to the following...) Figure 2D The process of presenting the second task information is described below. In response to receiving a second operation triggered by the third element 215-3, the electronic device 110 can present the second task information in the interface 200D, which is related to the at least one second type of task.

[0075] like Figure 2D As shown, the interface 200D presents a second task area 240. The second task information area 240 is used to display and manage at least one second-type task executed by the first intelligent system in the first session. In some cases, the second task information area 240 may include a task filtering control 241 and a task search component 242. The task filtering control 241 allows the user to view second-type tasks associated with the current first session, or switch to a full task view to view all second-type tasks corresponding to the first intelligent system. The task search component 242 receives search criteria to search for a target task among one or more second-type tasks.

[0076] In some cases, the interface 200D may also include a task entry list 243. The task entry list 243 can be used to present the corresponding basic information and session information for each second-type task. As an example, the task entry list 243 may present at least one of the following: basic information of the second-type task, such as task name, task summary, or task creation time; status information of the second-type task, such as running, paused, waiting to be triggered, or stopped; predetermined conditions corresponding to the second-type task; session information corresponding to the second-type task (e.g., corresponding session identifier or session name); or summary information of the most recent execution result of the second-type task.

[0077] In this way, users can directly view the second type of task executed by the first intelligent system for that session, without having to search for the corresponding task across multiple sessions, thereby improving task management efficiency.

[0078] In some cases, electronic device 110 can receive operations on one or more of the at least one task, the operation instructing at least one of the following: pausing the execution of the one or more tasks, stopping the execution of the one or more tasks, starting the execution of the one or more tasks, or deleting the one or more tasks. As an example, task operation menu 245 may display operation items such as "Enter Session Modification," "Smart Edit," and "Delete," where "Delete" is used to delete the corresponding task.

[0079] refer to Figure 2D The electronic device 110 can display a task switch control 244 and a task operation menu 245 on the interface 200D. The task switch control 244 can receive operations for starting or pausing the corresponding second-type task. For example, in response to triggering the task switch control 244, the electronic device 110 can pause or resume the execution of the corresponding second-type task. The task operation menu 245 can receive operations for editing or deleting the corresponding second-type task.

[0080] In this way, users can manage the second type of tasks uniformly at the session level, reducing the need to switch interfaces to locate related tasks. Furthermore, by pausing, stopping, or deleting invalid tasks, the continuous consumption of computing resources by invalid tasks can be reduced, thereby lowering the processing overhead on the server side.

[0081] In some cases, the electronic device 110 may receive a fourth operation initiated by a first task in at least one second-type task, which is triggered in response to a first predetermined condition, and the fourth operation indicates an update to the first predetermined condition. This fourth operation may be triggered by the "Enter Session Modification" or "Smart Edit" operation item in the task operation menu 245.

[0082] In some cases, in response to the fourth operation, the electronic device 110 can provide a prompt message that triggers an update to the first predetermined condition. As an example, Figure 2E A schematic diagram of the interface for session management based on certain scenarios is shown.

[0083] like Figure 2E As shown, in response to receiving a fourth operation initiated by the first task in the second type of task via the task operation menu 245, the electronic device 110 provides a prompt message 246, which is used to trigger the update of the first predetermined condition.

[0084] As an example, electronic device 110 can generate modification instructions based on the task information corresponding to the first task and automatically copy the modification instructions. Prompt message 246 can instruct the user to go to the session associated with the first task and paste the corresponding modification instructions. For example, prompt message 246 may include content such as "The instructions for modifying the task have been copied; please go to group chat session 1 to paste and use them."

[0085] In some cases, the modification instruction may include information identifying the first task and context information corresponding to the first session. For example, the modification instruction may include a task identifier, a session identifier, triggering condition information, and information indicating the content to be modified. In this way, the first intelligent system can identify the target task to be modified and the corresponding modification content based on the received modification instruction.

[0086] In this way, users can quickly locate the second type of task to be modified in a unified task management interface without having to re-describe the task background information. At the same time, since the electronic device 110 automatically generates modification instructions containing task identifiers and session information, users do not need to manually enter task identifiers, task names, or other related information, thereby reducing the possibility of configuration errors.

[0087] Furthermore, since task modification requests can be submitted via the session associated with the task, the first intelligent system can use the existing context information of the session to understand the user's modification needs without having to re-establish a new task management session, thereby reducing additional context building overhead and improving task modification efficiency.

[0088] In some scenarios, electronic device 110 can associate a task triggered by a first session with a first context identifier. For example, for the aforementioned first or second type of task, the first context identifier corresponding to the task is recorded when the task is created. If a first user requests the first intelligent system to perform an information retrieval task in the first session, the first intelligent system can create a corresponding first type of task and establish an association between the first type of task and the first context identifier. Similarly, if the first user creates a second type of task in the first session, an association between the second type of task and the first context identifier can also be established. During task execution, electronic device 110 can determine the session associated with the task based on the context identifier corresponding to the task.

[0089] In this way, tasks created in different sessions can be associated with their respective sessions, thus achieving task isolation and management at the session level. Furthermore, task results can be automatically returned to the session that triggered the task, eliminating the need for users to manually locate the task source, thereby improving the traceability of task results and the efficiency of task management.

[0090] Figure 2F A schematic diagram of a session management interface 200F is shown, depending on certain scenarios. In some scenarios, in response to receiving a trigger operation on a control 213 in the interface 200A, the electronic device 110 may present a new session dialog box 260, which may include a session name input area 261 and a confirmation control 262 and a cancellation control 263 for creating a new session.

[0091] In some scenarios, electronic device 110 can receive a session name via session name input area 261 and create a corresponding session in response to a trigger operation on confirmation control 262. For example, in response to an operation on confirmation control 262, electronic device 110 can create a new group chat session and make the currently selected smart system (e.g., the first smart system) a participant in the created group chat session.

[0092] In some cases, after a new group chat session is created, electronic device 110 can generate corresponding content items based on that group chat session and add these content items to the content item list presented on interface 200A. Subsequently, users can use these content items to view and manage the context, tasks, and related configurations of the first intelligent system within that group chat session.

[0093] In this way, users can quickly and directly create new group chat sessions in the current interface, and the newly created sessions are automatically included in the unified management scope of the First Intelligent System, thereby reducing the number of steps users need to take to switch between different interfaces to create and manage sessions.

[0094] Figure 2G A schematic diagram of the 200G interface for session management based on certain scenarios is shown below. (See below for reference.) Figure 2G This describes the process of presenting task information and identification information on the first interface.

[0095] In some cases, at least one content item is presented on a first interface (e.g., interface 200G), and the electronic device 110 can display a group chat task list 270 on this first interface. The group chat task list 270 is used to present one or more tasks performed by the first intelligent system for at least one session. For example, at least one session may include multiple group chat sessions in which the first intelligent system participates, and the group chat task list 270 can centrally display the tasks performed by the first intelligent system in the aforementioned multiple group chat sessions.

[0096] In some cases, presenting a group chat task list 270 includes presenting at least one of the following: basic information about the one or more tasks, which provides an overview of the task; status information about the one or more tasks, which indicates the execution status of the task; and session information about the one or more tasks, which indicates the session associated with the task.

[0097] As an example, basic information may include task name, task creation time, task summary, or task type; status information may include statuses such as in progress, completed, waiting to be triggered, or paused, and may also include the status of the corresponding switch control; session information may include the group chat session name, session identifier, or session summary to which the task belongs.

[0098] like Figure 2G As shown, the group chat task list 270 can display task entries such as "Task A...Group Chat Session 1" and "Task B...Group Chat Session 2". Each task entry can include basic information, status information, and session information (such as the related sessions) of the corresponding task. In this way, users can view the task distribution and execution status of the First Intelligent System in multiple sessions without having to enter each group chat session separately, thereby reducing the interface jump operations caused by searching for tasks across sessions and improving the efficiency of task viewing and management.

[0099] In some cases, taking a second session within at least one session as an example, the electronic device 110 may display identification information 275 of a second intelligent system participating in the second session at an interface location associated with that second session, and this second intelligent system is different from the first intelligent system. As an example, such as... Figure 2G As shown, the identification information 275 can be presented as an intelligent system identifier displayed on the corresponding content item, such as an avatar identifier, icon identifier, or name identifier, to indicate that there are other intelligent systems participating in the collaboration in the current session besides the first intelligent system.

[0100] It should be understood that the first user (e.g., user 140) has predetermined permissions for both the first and second intelligent systems, such as viewing permissions, configuration permissions, or management permissions, thereby allowing the user to view and manage the sessions in which the respective intelligent systems participate.

[0101] In some cases, electronic device 110 can receive a fifth operation triggered by the identification information 275. Further, electronic device 110 can present one or more content items, each corresponding to one or more sessions, displaying information related to the corresponding session. Each of the one or more sessions involves the second intelligent system, and the one or more sessions include the second session. In other words, if a trigger operation is received on the identification information 275, electronic device 1110 can switch the interface to the session management view corresponding to the second intelligent system to present multiple group chat sessions in which the second intelligent system participates, and allow the user to further view and manage the configuration, tasks, and related information of the second intelligent system.

[0102] In some cases, presenting the identification information 275 at an interface location associated with the second session includes at least one of the following: presenting the identification information 275 in a second content item, which is one of the at least one content item 215 and corresponds to the second session; or presenting the identification information 275 in a second interface used to display configuration information for the second session.

[0103] In this way, users can quickly discover and locate other intelligent systems participating in the current group chat session, and further view the scope of the sessions in which these other intelligent systems participate. This enables cross-intelligent system association management and navigation without having to search or switch between intelligent systems one by one, thereby improving the efficiency of information acquisition in multi-intelligent system collaborative scenarios.

[0104] Figure 3 A flowchart of an example process 300 for session management 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.

[0105] like Figure 3 As shown, in box 310, electronic device 110 receives a first operation that instructs the user to view information related to the first intelligent system. Its interactive presentation can be found above. Figure 2A The example described.

[0106] In box 320, electronic device 110 presents at least one content item, each corresponding to at least one session. Each content item displays information related to its corresponding session, and each session involves a first intelligent system and at least two objects, which are different from the first intelligent system. The interactive presentation can be found above. Figure 2A The example described.

[0107] In this way, information related to the first intelligent system is presented through a unified entry point, using the content items corresponding to a conversation involving the first intelligent system and at least two objects. This allows users to clearly perceive and manage the context and status of the first intelligent system in each group chat conversation at the granular level of the conversation.

[0108] In some cases, the electronic device 110 can receive a second operation triggered on a first content item among at least one content item, the first content item corresponding to a first session; and present configuration information for managing the first intelligent system in the first session. Its interactive presentation can be found above. Figure 2B The example described illustrates this. In this way, users can configure the first intelligent system at the session level.

[0109] In some cases, electronic device 110 may present first information indicating the range of data permitted for use by the first intelligent system in the first session. Its interactive presentation can be found above. Figure 2B The example described illustrates this. In this way, users can limit the range of data that can be loaded at the session level.

[0110] In some cases, the first content item may include a first element corresponding to the session settings, and the electronic device 110 may present the first information in response to a first operation triggered by that first element. Its interactive presentation can be found above. Figure 2A and Figure 2B The example described illustrates this. In this way, users can directly access the data scope configuration via the session settings element within the content item, reducing the number of jumps between different pages.

[0111] In some scenarios, electronic device 110 may present multiple information items corresponding to multiple available data ranges and receive a third operation instructing the selection of at least one information item from the multiple information items that corresponds to at least one available data range, wherein a first intelligent system is configured to perform an action based on the at least one available data range in a first session. Its interactive presentation can be seen above. Figure 2B The example described illustrates this. In this way, users are able to select, as needed, the range of data loaded by the first intelligent system in the first session.

[0112] In some cases, the electronic device 110 may present a first information item corresponding to a first available data range in a first style corresponding to a selected state, and present at least one second information item different from the first information item in a second style corresponding to an unselected state. Its interactive presentation can be found above. Figure 2BThe example described illustrates this approach. In this way, users can intuitively distinguish the selected status of each available data range, reducing repeated checks and potential errors in confirming the currently effective configuration. Furthermore, since the selected and unselected states are presented in the same panel with style differences, the client does not need to load a separate page to view the configuration status, thereby reducing the number of requests to the server and lowering client-side rendering overhead.

[0113] In some cases, the electronic device 110 may present second information indicating at least one task performed by the first intelligent system for the first session. Its interactive presentation can be seen above. Figure 2C and Figure 2D The example described illustrates this. In this way, users can view the tasks performed by the First Intelligence System for a given session, reducing the number of times users need to switch between sessions and task lists.

[0114] In some cases, at least one task may include at least one first-type task triggered in response to at least one message in a first session, and the first content item includes a second element indicating the first-type task. The electronic device 110 may present first task information related to the at least one first-type task in response to a second operation triggered by the second element. Its interactive presentation can be seen above. Figure 2C The example described illustrates this. In this way, users can directly view the first type of tasks triggered by messages within a session, reducing the number of jumps required to find tasks across sessions.

[0115] In some cases, at least one task may include at least one second type of task triggered in response to the fulfillment of at least one predetermined condition. The first content item includes a third element indicating the second type of task, and the electronic device 110 may present second task information related to the at least one second type of task in response to a second operation being triggered by the third element. Its interactive presentation can be referred to above. Figure 2D The example described illustrates this. In this way, users can directly view the second type of task triggered by predetermined conditions, reducing the number of jumps required to find scheduled tasks across sessions.

[0116] In some cases, the electronic device 110 may receive a fourth operation initiated by a first task in at least one second-type task, which is triggered in response to a first predetermined condition. The fourth operation indicates an update to the first predetermined condition and provides a prompt message for triggering the update of the first predetermined condition. The interactive presentation can be found above. Figure 2D and Figure 2EThe example described illustrates this. In this way, users can be guided by the prompt to update predetermined conditions, reducing the operations required to locate the task to be updated and its session. Furthermore, since the first intelligent system is provided with anchor information for the task by triggering the corresponding task, it can directly associate with the task to be updated without performing matching searches across multiple tasks, thereby reducing the search scope, lowering the corresponding computational overhead, and reducing the probability of erroneous updates.

[0117] In some cases, at least one content item may be presented sequentially on the first interface, the order of which relates to the active state of the first intelligent system in at least one session. The interactive presentation can be referenced above. Figure 2A and Figure 2G The example described illustrates this. In this way, users can more quickly locate sessions that require management, reducing the number of times they need to search and scroll through the interface. Furthermore, in the implementation of on-demand loading of content items, items that are listed earlier in the order can be loaded first, thereby reducing the number of content items that need to be rendered on the client's first screen, shortening the first screen rendering time, and reducing client-side rendering overhead.

[0118] In some cases, at least one content item may be presented on the first interface, and the electronic device 110 may present task information on the first interface, which describes one or more tasks performed by the first intelligent system for at least one session. Its interactive presentation can be seen above. Figure 2G The example described illustrates this approach. In this way, users can directly access a task overview within the same interface that presents the content items, reducing the number of times users need to navigate between content item and task details pages. Furthermore, since task information and content items are presented on the same interface without requiring a separate page for the task overview, client-side rendering overhead and cache usage are reduced, as are server query load and end-to-cloud communication bandwidth usage.

[0119] In some cases, presenting the task information may include presenting at least one of the following: basic information about the one or more tasks, which provides an overview of the task; status information about the one or more tasks, indicating the execution status of the task; and session information about the one or more tasks, indicating the session associated with the task. The interactive presentation can be found above. Figure 2C , Figure 2D and Figure 2G The example described illustrates this approach. In this way, users can intuitively obtain basic, status, and session information about a task, reducing the need for multiple viewings and navigations to obtain a complete overview. Furthermore, because this information is presented together within the same task entry, the client does not need to make multiple requests to obtain different dimensions of information, thereby reducing the number of requests to the server and lowering the server's query load.

[0120] In some cases, at least one session may include a second session. The electronic device 110 may display identification information indicating that a second intelligent system, different from the first intelligent system, is participating in the second session at an interface location associated with that second session; receive a fifth operation triggered by the identification information; and display one or more content items corresponding to one or more sessions in which the second intelligent system participates, including the second session. Its interactive presentation can be seen above. Figure 2G The example described illustrates this approach. In this way, users can directly perceive and quickly switch between viewing sessions involving the second intelligent system within the current interface, reducing the need for users to navigate and switch between different intelligent systems. Furthermore, since switching between sessions is triggered by identifying information within the same interface without loading a separate search page, the number of requests to the server is reduced, lowering client-side rendering overhead and cloud-edge communication bandwidth usage.

[0121] In some cases, the electronic device 110 may also receive a sixth operation on one or more of the at least one task, the sixth operation instructing at least one of the following: pausing the execution of the one or more tasks, stopping the execution of the one or more tasks, starting the execution of the one or more tasks, or deleting the one or more tasks. Its interactive presentation can be seen above. Figure 2D The example described illustrates this approach. In this way, users can manage running tasks at the session level, including starting, stopping, and deleting them, reducing the amount of time and effort required to locate and manage irrelevant tasks. Furthermore, by promptly pausing, stopping, or deleting invalid or redundant tasks, the execution of invalid tasks is reduced, thereby decreasing the computing resources consumed by these tasks on the server and reducing the number of database queries and read / write operations.

[0122] In some cases, the first content item may correspond to a first context identifier, which is determined based on at least two of the following: a first identifier for identifying the first intelligent system, a second identifier for identifying the first session, or a third identifier for identifying the first user participating in the first session. Its interactive presentation can be seen above. Figure 2A The example described illustrates this. In this way, users can manage the runtime state of the first intelligent system at the session level. Furthermore, because different sessions are indexed and isolated using different context identifiers, data from unrelated sessions is not loaded into the current session's processing flow. This reduces the amount of redundant data loaded into the context window, decreases the number of database queries during retrieval, reduces computational overhead introduced by context crosstalk, and lowers the risk of sensitive data exposure across sessions.

[0123] In some cases, presenting the identification information at an interface location may include at least one of the following: presenting the identification information in a second content item, which is one of at least one content item and corresponds to a second session; or presenting the identification information on a second interface used to display configuration information for the second session. Its interactive presentation can be found above. Figure 2G The example described illustrates this approach. In this way, users can directly perceive the second intelligent system's participation in the corresponding session through content items or configuration interfaces, reducing the need for users to view and navigate to different parts of the session to confirm the participants. Furthermore, since the identification information is presented along with the content items or configuration interfaces without loading a separate page, the number of requests to the server is reduced, lowering client-side rendering overhead.

[0124] In some cases, the first available data range may correspond to the work transaction of a first user participating in a first session. The interactive presentation can be found above. Figure 2B The example described illustrates this. In this way, users can limit the range of data that the first intelligent system can load in the first session to work-related data (such as work area rules), reducing the additional configuration operations required by users to isolate sensitive personal data. Furthermore, since only work-related data is loaded by default in group chat sessions, excluding personalized data such as long-term memory, the number of times sensitive data is loaded and transmitted is reduced, lowering the persistence and exposure surface of plaintext sensitive data on the edge-cloud link.

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

[0126] Figure 4 Block diagrams of a device 400 for session management in several scenarios are shown. Device 400 can be implemented as or included in electronic device 110. The various modules / components in device 400 can be implemented by hardware, software, firmware, or any combination thereof.

[0127] like Figure 4 As shown, the device 400 includes: a receiving module 410 configured to receive a first operation, the first operation instructing the viewing of information related to a first intelligent system; and a presentation module 420 configured to present at least one content item, each of the at least one content item corresponding to at least one session, the content item displaying information related to the corresponding session, each session in the at least one session involving the first intelligent system and at least two objects, the at least two objects being different from the first intelligent system.

[0128] In some cases, the receiving module 410 may also be configured to receive a second operation triggered on a first content item among at least one content item, the first content item corresponding to a first session; and the presentation module 420 may also be configured to present configuration information for managing the first intelligent system in the first session.

[0129] In some cases, the presentation module 420 may also be configured to present first information that indicates the range of data that the first intelligent system is permitted to use for the first session.

[0130] In some cases, the first content item includes a first element corresponding to the session settings, and the presentation module 420 can also be configured to present the first information in response to a first operation being triggered on the first element.

[0131] In some cases, the presentation module 420 may also be configured to present multiple information items corresponding to multiple available data ranges, and the receiving module 410 may also be configured to receive a third operation that instructs the selection of at least one information item from the multiple information items that corresponds to at least one available data range, wherein the first intelligent system is configured to perform an action based on the at least one available data range in a first session.

[0132] In some cases, the plurality of information items includes a first information item corresponding to a first available data range, and the presentation module 420 may also be configured to present the first information item in a first style corresponding to a selected state, and to present at least one second information item different from the first information item in a second style corresponding to an unselected state.

[0133] In some cases, the presentation module 420 may also be configured to present second information indicating at least one task performed by the first intelligent system for the first session.

[0134] In some cases, at least one task includes at least one first type task triggered in response to at least one message in the first session, the first content item includes a second element indicating the first type task, and the presentation module 420 may also be configured to present first task information related to the at least one first type task in response to a second operation being triggered on the second element.

[0135] In some cases, at least one task includes at least one second type task triggered in response to the satisfaction of at least one predetermined condition, the first content item includes a third element indicating the second type task, and the presentation module 420 may also be configured to present second task information related to the at least one second type task in response to a second operation being triggered by the third element.

[0136] In some cases, the receiving module 410 may also be configured to receive a fourth operation initiated by a first task in the at least one second type of task, which is triggered in response to a first predetermined condition, the fourth operation indicating an update to the first predetermined condition; and the presentation module 420 may also be configured to provide a prompt message for triggering an update to the first predetermined condition.

[0137] In some cases, the presentation module 420 may also be configured to present at least one content item sequentially on the first interface, the order being related to the active state of the first intelligent system in at least one session.

[0138] In some cases, at least one content item is presented on the first interface, and the presentation module 420 can also be configured to present task information on the first interface, which describes one or more tasks performed by the first intelligent system for at least one session.

[0139] In some cases, the presentation module 420 is configured to present the task information, which may include being configured to present at least one of the following: corresponding basic information of the one or more tasks, which is used to summarize the corresponding task; corresponding status information of the one or more tasks, which is used to indicate the execution status of the corresponding task; and corresponding session information of the one or more tasks, which indicates the session associated with the corresponding task.

[0140] In some cases, at least one session includes a second session, and the presentation module 420 may also be configured to present identification information indicating that a second intelligent system participates in the second session at an interface location associated with the second session, the second intelligent system being different from the first intelligent system; the receiving module 410 may also be configured to receive a fifth operation triggered by the identification information; and the presentation module 420 may also be configured to present one or more content items corresponding to one or more sessions in which the second intelligent system participates, the one or more sessions including the second session.

[0141] In some cases, the receiving module 410 may also be configured to receive a sixth operation issued to one or more of the at least one task, the sixth operation indicating at least one of the following: pausing the execution of the one or more tasks, stopping the execution of the one or more tasks, starting the execution of the one or more tasks, or deleting the one or more tasks.

[0142] In some cases, the first content item corresponds to a first context identifier, which is determined based on at least two of the following: a first identifier for identifying the first intelligent system, a second identifier for identifying the first session, or a third identifier for identifying the first user participating in the first session.

[0143] In some cases, the presentation module 420 is configured to present the identification information at an interface location, which may include being configured to perform at least one of the following: presenting the identification information in a second content item, the second content item being one of at least one content items and corresponding to a second session; or presenting the identification information in a second interface used to display configuration information for the second session.

[0144] In some cases, the first available data range corresponds to the work transaction of a first user who participates in a first session.

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

[0146] Figure 5 A block diagram of an electronic device 500 in which one or more examples 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 electronic device 500 shown can be used to implement the electronic device 110 discussed above.

[0147] like Figure 5As 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.

[0148] 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 may 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.

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

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

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

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

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

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

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

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

[0157] 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 session management method, comprising: Receive a first operation, the first operation instructing you to view information related to the first intelligent system; as well as At least one content item is presented, each corresponding to at least one session. The content item displays information related to the corresponding session. Each session in the at least one session involves the first intelligent system and at least two objects, which are different from the first intelligent system.

2. The method according to claim 1, further comprising: Receive a second operation, the second operation being triggered on a first content item among the at least one content item, the first content item corresponding to a first session among the at least one session; as well as The system presents configuration information used to manage the first intelligent system during the first session.

3. The method according to claim 2, wherein presenting the configuration information includes: The system presents first information, which indicates the range of data that the first intelligent system is permitted to use for the first session.

4. The method of claim 3, wherein the first content item includes a first element, the first element corresponding to session settings, and presenting the first information includes: In response to the second operation being triggered on the first element, the first information is presented.

5. The method of claim 3, wherein presenting the first information comprises: The method presents multiple information items, each corresponding to a different range of available data, and further includes: A third operation is received, the third operation instructing the selection of at least one of the plurality of information items, the at least one information item corresponding to at least one of the plurality of available data ranges, wherein the first intelligent system is configured to perform an action based on the at least one available data range in the first session.

6. The method of claim 5, wherein the plurality of information items includes a first information item, the first information item corresponding to a first available data range, and presenting the plurality of information items includes: The first information item is presented in a first style, which corresponds to the selected state. as well as At least one second information item is presented in a second style, the at least one second information item being different from the first information item, and the second style corresponding to the unselected state.

7. The method of claim 2, wherein presenting the configuration information includes: A second message is presented, indicating at least one task, which is performed by the first intelligent system for the first session.

8. The method of claim 7, wherein the at least one task includes at least one first type task, the at least one first type task being triggered in response to at least one message in the first session, the first content item including a second element indicating the first type task, and presenting the second information including: In response to the second operation being triggered on the second element, first task information is presented, which relates to the at least one first type of task.

9. The method of claim 7, wherein the at least one task includes at least one second type of task, the at least one second task being triggered in response to the satisfaction of at least one predetermined condition, the first content item including a third element indicating the second type of task, and presenting the second information including: In response to the second operation being triggered by the third element, second task information is presented, which relates to the at least one second type of task.

10. The method of claim 9, further comprising: Receive a fourth operation, the fourth operation being initiated for a first task in the at least one second type of task, the first task being triggered in response to a first predetermined condition, the fourth operation indicating an update to the first predetermined condition; as well as A prompt message is provided, which is used to trigger an update of the first predetermined condition.

11. The method of claim 1, wherein the at least one content item is presented sequentially on the first interface, the order relating to the active state of the first intelligent system in the at least one session.

12. The method of claim 1, wherein the at least one content item is presented on the first interface, and the method further comprises: The first interface presents task information, which describes one or more tasks performed by the first intelligent system for the at least one session.

13. The method of claim 12, wherein presenting the task information includes presenting at least one of the following: The basic information corresponding to the one or more tasks, wherein the basic information is used to summarize the corresponding tasks. The status information of the one or more tasks, wherein the status information is used to indicate the execution status of the corresponding task. The corresponding session information for the one or more tasks, wherein the session information indicates a session associated with the corresponding task.

14. The method of claim 1, wherein the at least one session includes a second session, and the method further comprises: At the interface location associated with the second session, identification information is presented, indicating that a second intelligent system is participating in the second session, and the second intelligent system is different from the first intelligent system; Receive a fifth operation, which is triggered by the identification information; as well as One or more content items are presented, each corresponding to one or more sessions. The content items in the one or more content items display information related to the corresponding session. Each of the one or more sessions is participated in by the second intelligent system, and the one or more sessions include the second session.

15. An apparatus for session management, comprising: The receiving module is configured to receive a first operation, the first operation instructing the viewing of information related to the first intelligent system; as well as The presentation module is configured to present at least one content item, each of which corresponds to at least one session. The content item displays information related to the corresponding session. Each session in the at least one session involves the first intelligent system and at least two objects, which are different from the first intelligent system.

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