Method, device, equipment, storage medium and program product for interface interaction

Abstract

A method, apparatus, device, storage medium, and program product for interface interaction are provided. The method includes: in a first interface, presenting a plurality of identifiers, the plurality of identifiers including a first identifier and a second identifier, the first identifier corresponding to a first object, and the second identifier corresponding to a second object; in response to a first triggering operation on the first identifier, presenting a first session with a virtual object in the first interface, the first session being associated with the first object; and in response to a second triggering operation on the second identifier, presenting a second session with the virtual object in the first interface, the second session being associated with the second object, the first session being independent of the second session. In this way, the interaction efficiency with the virtual object can be improved.

Description

Technical Field

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

[0002] With the development of artificial intelligence technology, virtual objects are gradually being introduced into human-computer interaction scenarios to accompany users and provide diverse services. For example, users can interact with virtual objects through dialogue. In some scenarios where interaction relies on virtual objects, users may need to communicate with multiple different virtual objects. Therefore, improving the efficiency of interaction with virtual objects is a topic worthy of attention. Summary of the Invention

[0003] In a first aspect of this document, a method for interface interaction is provided. The method includes: presenting a plurality of identifiers on a first interface, the plurality of identifiers including a first identifier and a second identifier, the first identifier corresponding to a first object and the second identifier corresponding to a second object; displaying a first session with a virtual object on the first interface in response to a first triggering operation on the first identifier, the first session being associated with the first object; and displaying a second session with the virtual object on the first interface in response to a second triggering operation on the second identifier, the second session being associated with the second object, the first session being independent of the second session.

[0004] In a second aspect of this document, an apparatus for interface interaction is provided. The apparatus includes: a first presentation module configured to present a plurality of identifiers on a first interface, the plurality of identifiers including a first identifier and a second identifier, the first identifier corresponding to a first object and the second identifier corresponding to a second object; a first display module configured to display a first session with a virtual object on the first interface in response to a first triggering operation on the first identifier, the first session being associated with the first object; and a second display module configured to display a second session with the virtual object on the first interface in response to a second triggering operation on the second identifier, the second session being associated with the second object, the first session being independent of the second session.

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

[0006] In a fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions that can be executed by a processor to implement the method of the first aspect.

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

[0008] In this way, the identifiers corresponding to different objects can be displayed on the same interface. By triggering the identifier, the conversations of different objects can be switched, thus isolating the conversation content and context of each object from each other and preventing them from mixing. This helps to clearly distinguish and manage the communication process for different 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 2J Example interfaces for some scenarios are shown; Figure 3 Flowcharts illustrating example processes for interface interaction in several scenarios are shown; Figure 4 Schematic block diagrams of example devices for interface interaction in some scenarios are shown; and Figure 5 A block diagram of an electronic device capable of implementing multiple illustrative scenarios is shown. Detailed Implementation

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

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

[0016] As used in this document, the term "interface" refers to a visual view used to present information to a user and / or receive user actions. It can include, but is not limited to, pages, windows, pop-ups, panels, cards, or combinations thereof. An interface can present one or more elements, such as icons, conversations, messages, controls, entry points, prompts, etc. The primary interface is typically a human-computer interaction interface that carries multiple icons and displays conversations; for example, it can be a main dialogue interface for interacting with virtual objects. Its form is unrestricted; it can be a full-screen page, a window, or a panel.

[0017] As used in this article, the term "identifier" refers to a visual entry point on the interface that can be triggered to enter a corresponding session. Its presentation is unrestricted and may include, but is not limited to, text, avatars, icons, tabs, or combinations thereof. Different identifiers can be distinguished from each other and can each correspond to different objects.

[0018] The term “object” as used in this article refers to the subject to which the session serves or is directed, namely the user or entity to whom information is communicated or recorded.

[0019] As used in this document, the term "virtual object" refers to a non-human interactive party that engages in conversational interaction with a user, which may be driven by a backend processing entity. Virtual objects may include, but are not limited to, virtual assistants, virtual customer service representatives, virtual assistants, or other forms of virtual interactive parties. In some cases, the backend processing entity driving the virtual object may include, but is not limited to, processing entities implemented based on machine learning models or other models.

[0020] As used in this article, a "session" refers to a communication process between a user and a virtual object surrounding a particular object, or a view that carries such a communication process. In some cases, a session may belong to at most one object. Two sessions being independent can mean that the content and context of the two sessions are not mixed up.

[0021] The term “triggering action” (which may also be referred to as “action” in some contexts) as used in this article refers to an input behavior that a user applies to an interface or an element on the interface to trigger a corresponding action. Its form is not limited and may include, but is not limited to, clicking, long pressing, swiping, dragging, selection, text input, voice commands, or combinations thereof.

[0022] The term "session entry" as used in this article refers to a visual entry point used to access or display a particular session, which is typically located in the session list or record area. Session entry points are distinct from identifiers: identifiers correspond to objects, while session entry points correspond to a specific session.

[0023] The term "element" as used in this document refers to a visual component that is presented together with the session entry and is used to represent the object corresponding to the session entry. Its form is not limited, and may include, but is not limited to, text labels, avatars, logos, color marks, or combinations thereof.

[0024] The term "identification information" as used in this article refers to information used to identify an object, which can be the specific content of an element, such as including but not limited to the object's name, nickname, avatar, number, or a combination of the above.

[0025] As used in this article, the term "input component" refers to a visual element on an interface used to receive user input, and its form is not limited, such as including but not limited to text input boxes, voice input controls, or combinations thereof.

[0026] The term "hint" as used in this article refers to feedback or guidance given to the user, which can be used to represent a state, relationship, or suggestion, and can be presented in the form of a message, text, icon, control, or a combination of the above.

[0027] As used in this document, "descriptive information" (which in some cases may also refer to an object's "attributes") refers to information associated with an object and used to characterize that object. This information can constitute an object's profile, and may include, but is not limited to, basic information about the object and relevant information accumulated from interactions. In some cases, at least one attribute of an object can be updated based on multiple sessions associated with that object.

[0028] The term "request" as used in this article refers to an instructional input used to trigger corresponding processing (such as creating an object, creating a session, or removing an object), and its triggering source is unrestricted, such as including but not limited to triggering operations on controls, menu items, or gestures.

[0029] The term "message" as used in this article refers to a unit of content that carries information in a conversation. Its source and form are interpreted broadly, and it can come from the user or from virtual objects. Messages can include, but are not limited to, text, icons, cards, or combinations thereof.

[0030] As mentioned above, with the development of artificial intelligence technology, virtual objects are gradually being introduced into human-computer interaction scenarios to accompany users and provide diverse services. For example, users can interact with virtual objects through dialogue. In some scenarios where interaction is facilitated by virtual objects, users may need to communicate with multiple different virtual objects. In this approach, communication content related to different objects is often intertwined and aggregated within the same conversation, leading to the following difficulties: Firstly, the conversation content and context of each object are intertwined and mixed, making it difficult to clearly distinguish and manage the corresponding communication process; secondly, due to the lack of clear object attribution for the communication content, subsequent queries, retrieval, or retention of relevant context can easily result in unclear attribution, potentially affecting the virtual object's utilization of relevant context during the interaction. Therefore, improving the efficiency of interaction with virtual objects is a crucial issue.

[0031] Furthermore, under the above-described approach, users find it difficult to easily switch between communications with different recipients, and also find it difficult to autonomously organize and manage the context of a conversation. The examples described below can at least partially alleviate one or more of the above-mentioned difficulties.

[0032] A user interface interaction scheme is proposed. According to this scheme, multiple identifiers can be presented on a first interface. These identifiers include a first identifier corresponding to a first object and a second identifier corresponding to a second object. In response to a user's first trigger operation on the first identifier, a first session with the virtual object can be displayed on the first interface. The first session is associated with the first object. In response to a user's second trigger operation on the second identifier, a second session with the virtual object can be displayed on the first interface. The second session is associated with the second object, and the first session is independent of the second session.

[0033] Through the above scheme, the sessions corresponding to different objects can be organized and displayed independently within the same interface. Users can switch between sessions of different objects by triggering the corresponding identifiers, so that the session content and context of each object are isolated from each other and do not mix. This helps to clearly distinguish and manage the communication process facing multiple objects, and facilitates the subsequent attribution, querying and accumulation of relevant contexts by object.

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

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

[0036] In this example environment 100, electronic device 110 can run an application 120 that supports user interface interaction. Application 120 can be any suitable type of application for user interface interaction, including but not limited to: session applications, virtual object applications, or other suitable applications. User 140 can interact with application 120 via electronic device 110 and / or its attached devices.

[0037] exist Figure 1 In environment 100, if application 120 is active, electronic device 110 can use application 120 to present interface 150 for supporting user interface interaction. In some examples, interface 150 may include a first interface, a second interface, etc., as mentioned in the scheme. It can be used to present multiple icons, sessions, prompts, etc.

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

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

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

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

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

[0043] Example Interaction Figures 2A to 2JExample interfaces 200A to 200J are shown according to some scenarios. Interfaces 200A to 200J can, for example, be derived from... Figure 1 The electronic device 110 shown is provided.

[0044] The following is for reference. Figures 2A to 2J This paper describes an example interaction process of this solution in a scenario where multiple objects interact. In this scenario, the virtual object can be, for example, a virtual interaction party used to provide consultation (illustratively represented as "XX Assistant" in the diagram).

[0045] like Figure 2A As shown, the electronic device 110 can present an interface 200A. Interface 200A corresponds to a schematic scenario of the first interface. As an example, the first interface can be implemented as a conversational interface with a virtual object. The first interface can be used for dialogue interaction with the virtual object.

[0046] As an example, electronic device 110 may display multiple identifiers in interface 200A. For example, the multiple identifiers may include identifiers 202-1 to 202-3, etc. For example, the multiple identifiers may correspond to different objects. For example, identifier 202-1 (e.g., "Temporary Inquiry") may not be associated with an object. As an example, identifier 202-2 (e.g., "Myself") may correspond to a first object. Alternatively, identifier 202-3 (e.g., "User 1") may correspond to a second object. As an example, identifiers may include graphic identifiers and / or text identifiers. As an example, electronic device 110 may, in response to a triggering operation on an identifier (e.g., a click operation, etc.), display a session associated with the corresponding object in a first interface. For example, identifier 202-2 is used to trigger the presentation of a session associated with a first object (e.g., "Myself"). For example, identifier 202-3 is used to trigger the display of a session associated with a second object (e.g., "User 1"). For example, identifier 202-1 is used to trigger the display of a session without a specified object (e.g., a temporary session).

[0047] Additionally, such as Figure 2A As shown, electronic device 110 can also present entry point 204 (e.g., "Create Consultant"). For example, electronic device 110 can trigger the creation of a new object based on a triggering operation on entry point 204. The process of creating a new object via this entry point will be discussed below. Figure 2I and Figure 2J Further description.

[0048] In some cases, such as Figure 2AAs shown, before selecting an object, the electronic device 110 can also present a greeting from the virtual object in the interface 200A (illustratively represented in the figure as "Hello, who would you like to consult for today?"). The user can perform a trigger operation on any of the multiple identifiers to enter the corresponding session.

[0049] As an example, such as Figure 2B As shown, electronic device 110 can present interface 200B. For example, Figure 2B Another implementation of the first interface is shown, namely interface 200B. Electronic device 110 may display multiple icons on interface 200B (e.g., at the top). For example, icons 206-1 to 206-3. As an example, electronic device 110 may display entry 208 (e.g., "Create Consultant") on interface 200B. Figure 2B The identifiers 206-1 to 206-3 in the text can correspond to Figure 2A The identifiers 202-1 to 202-3 are listed. For example, Figure 2B Entry 208 in the middle can correspond to Figure 2A Entry 204 in the middle.

[0050] As an example, electronic device 110 can respond to... Figure 2A The triggering of any of the identifiers in the table will result in the following: Figure 2B The interface shown is 200B. For example, for... Figure 2A Taking the triggering of identifier 202-1 as an example, electronic device 110 can present identifier 206-1 in a first style on interface 200B. For example, the first style can indicate that identifier 206-1 is selected. For example, the first style can be implemented by presenting a border, bold text, or a preset background color, etc. Alternatively, electronic device 110 can present other identifiers in interface 200B (e.g., identifiers 206-2 and 206-3, etc.) in a second style. The second style is different from the first style, thereby distinguishing the selected identifier (e.g., identifier 206-1).

[0051] In some scenarios, electronic device 110 may, in response to the selection of identifier 206-1, display a session associated with identifier 206-1 (e.g., a temporary session without a specified object) on a first interface (e.g., interface 200B). For example, a user can interact with a virtual object through a temporary session. The virtual object's response in the temporary session (e.g., a reply to the user's input) is independent of the object (e.g., a first object, a second object, etc.). As an example, electronic device 110 may, in response to the selection of identifier 206-1, present prompt text 210 on interface 200B (e.g., "Select a consultant and consult with the corresponding profile") to remind the user to select an object and consult with the corresponding object's profile.

[0052] As an example, multiple identifiers may include a first identifier and a second identifier. For example, identifier 206-2 may correspond to the first identifier. Identifier 206-3 may correspond to the second identifier. For example, electronic device 110 may display a first session with a virtual object on a first interface in response to a first triggering operation (e.g., a click operation, etc.) on the first identifier (e.g., identifier 206-2).

[0053] like Figure 2C As shown, electronic device 110 can present interface 200C. For example, in response to a first trigger operation on identifier 206-2 (first identifier), electronic device 110 can display a first session with a virtual object on a first interface (e.g., interface 200C). The first session is associated with a first object (e.g., "myself"). Figure 2C As shown, electronic device 110 can present identifier 206-2 in a first style to indicate that identifier 206-2 has been selected. Accordingly, electronic device 110 displays a first session associated with a first object (represented as "the self" in the figure). For example, the first object may be associated with one or more sessions. For example, the first session may be the latest session among one or more sessions associated with the first object. For example, a latest session refers to a conversation record that is most recently occurred or most recently updated, arranged in chronological order. For example, electronic device 110 may present information such as recently sent or received message content, session summary, or interaction timestamps in the first session.

[0054] In some cases, electronic device 110 can display session messages from the first session on interface 200C, such as session messages 216-1 to 216-3. For example, session message 216-1 comes from a user. For example, session messages 216-2 and 216-3 come from a virtual object. As an example, session messages 216-2 and 216-3 can be responses to session message 216-1. For example, session messages from a virtual object can be generated by the virtual object based on context information (e.g., historical session messages) in the first session. Alternatively, session messages from a virtual object can be generated by the virtual object based on at least one attribute associated with the first object. For example, at least one attribute associated with the first object can be obtained from descriptive information associated with the first user. In the session associated with the first object, at least one attribute associated with the first object can be provided to the virtual object to provide a reference for generating response content (e.g., a reply message) for the virtual object. As an example, at least one attribute may include descriptive labels, parameter information, etc., associated with the first object.

[0055] For example, a first object can be associated with multiple sessions. As an example, at least one attribute associated with the first object can be updated based on multiple sessions. For example, at least one attribute associated with the first object can be determined based on session messages in multiple sessions. For example, server 130 can obtain session messages from multiple sessions associated with the first object and perform semantic analysis or keyword extraction on these session messages to identify information related to the first object (e.g., interaction mode, entity name, operation type, or status identifier). Further, server 130 can compare the identified information with the currently stored attributes of the first object; if there are differences or new information, the at least one attribute can be supplemented or corrected. For example, if a virtual object repeatedly responds to a specific piece of content in multiple sessions, and this content is not recorded in the current attribute, then this content can be associated with the first object as a new attribute. In this way, the at least one attribute can dynamically evolve as the number of sessions the first object participates in increases, thereby more accurately reflecting the information associated with the first object and providing richer reference for the virtual object to generate subsequent responses.

[0056] In some cases, such as Figure 2C As shown, the electronic device 110 can display an input component 214 on the first interface, which is used to receive user input (illustratively represented in the figure as an input box for "Enter a question or press and hold to speak"). Furthermore, the electronic device 110 can display prompt text 212 on the interface 200C. The prompt text 212 is associated with the conversation displayed on the first interface (illustratively represented in the figure as "Consulting for myself"). The prompt text 212 can change accordingly with the currently displayed conversation or object; for example, when switching to a conversation associated with another object, the prompt text 212 can change accordingly to indicate that other object. In this way, the user can easily know which object they are currently inputting to, thereby helping to reduce the possibility of mis-input when communicating with multiple objects.

[0057] Alternatively, the electronic device 110 may present a prompt (also known as a third prompt) in the input component 214. For example, the third prompt may be associated with a session displayed on the first interface. For example, the third prompt may indicate an object associated with the displayed session. For example, the electronic device 110 may present preset text in the input component 214. The preset text may correspond to the third prompt. For example, such preset text may include a name identifier associated with a first object (e.g., "me"). Alternatively, when the displayed session is associated with a second object, the preset text corresponding to the third prompt may include a name identifier associated with the second object (e.g., "User 1"). Alternatively, the third prompt may also include a summary of historical session messages for the currently displayed session (e.g., "Last time we talked about XXX").

[0058] In some cases, such as Figure 2C As shown, the electronic device 110 may also present an entry point 218 (e.g., a "New Session Control"). For example, entry point 218 is used to create a new session associated with the current object. For example, the first object may be associated with multiple sessions with virtual objects. Exemplarily, the multiple sessions may include a first session and a third session. In some cases, the electronic device 110 may receive a third request. For example, the third request is used to create a third session. In response to this third request, the electronic device 110 may create the third session and present the first session entry point associated with the third session (the presentation of the first session entry point will be discussed below). Figure 2E (Further description). As an example, a third request may include a triggering action (e.g., a click action, etc.) on entry 218.

[0059] As an example, electronic device 110 may, in response to receiving a trigger operation on entry 218 and a first identifier (e.g., identifier 206-2) corresponding to the first object being in a selected state (e.g., selected), create a third session and associate the third session with the first object. Alternatively, electronic device 110 may, in response to a third request, present the first session entry (e.g., Figure 2E (Session entry point 222-1). In this way, multiple independent sessions can coexist under the same object, making it easier for users to organize and manage different topics for the same object.

[0060] like Figure 2DAs shown, electronic device 110 can present interface 200D. For example, electronic device 110 can present interface 200D in response to the creation of a third session. For example, interface 200D can be implemented as a first interface. For example, electronic device 110 can display a third session with a virtual object on the first interface (e.g., interface 200D). The third session is associated with the first object. For example, the third session is independent of other sessions associated with the first object (e.g., the first session, etc.). Since the third session is a newly created session, the session messages associated with the third session are not yet displayed in interface 200D.

[0061] In some cases, electronic device 110 may display a third session on a first interface (e.g., interface 200D) in response to a triggering operation (also known as a third triggering operation) of a first session entry associated with a third session. As an example, electronic device 110 may present multiple session entries. Multiple session entries may include the first session entry. For example, electronic device 110 may present multiple session entries in response to receiving a preset operation. For example, the preset operation may include a swipe operation (e.g., a right swipe, etc.) associated with the first interface. Alternatively, electronic device 110 may present entry 220 (also known as a sidebar entry). For example, the preset operation may also include a triggering operation (e.g., a click operation, etc.) of entry 220. As an example, electronic device 110 may receive a preset operation and may accordingly present... Figure 2E The interface shown is 200E.

[0062] like Figure 2E As shown, the electronic device 110 can present multiple session entries in the interface 200E. For example, session entries 222-1 to 222-6, etc. For example, the multiple session entries can be arranged by time. For example, the multiple session entries can also be grouped according to different dates. For example, session entries 222-1 to 222-3 can correspond to the first group (e.g., "Today"). For example, session entries 222-4 to 226-6 can correspond to the second group (e.g., "Yesterday").

[0063] As an example, a session entry is used to access or display a corresponding session. In response to a triggering operation on a session entry, electronic device 110 can display the session corresponding to that session entry on a first interface. In some cases, session entry 222-1 can be a first session entry associated with a third session. For example, electronic device 110 can display a third session on the first interface in response to a third triggering operation on the first session entry (e.g., a click operation).

[0064] As an example, electronic device 110 can also display elements associated with multiple session entry points (e.g., elements 224-1 to 224-5) to characterize the object corresponding to the respective session entry point. For example, elements 224-1, 224-2, and 224-4 (illustratively represented as the "Myself" label in the figure) can be elements associated with a session entry point corresponding to a first object. Elements 224-3 and 224-5 (illustratively represented as the "User 1" label in the figure) are elements characterizing that the corresponding session entry point corresponds to a second object. In this way, users can intuitively know the object to which the corresponding session belongs from the session entry point, thereby facilitating the differentiation and management of multiple sessions by object.

[0065] For example, multiple session entry points may include a second session entry point corresponding to the first session (e.g., session entry point 222-2). Taking the second session entry point as an example, the electronic device 110 may present a first element associated with the second session entry point (e.g., element 224-2). The first element may characterize that the second session entry point corresponds to a first object. In some cases, the first element (e.g., element 224-2) may include identification information of the first object, such as the nickname of the first object ("myself" in the figure).

[0066] In some cases, electronic device 110 may also receive a first request. The first request is for removing a first object. For example, electronic device 110 may receive the first request through a first identifier associated with the first object. For example, electronic device 110 may present a delete control corresponding to the first identifier in response to a long press operation on the first identifier. For example, the first request may include a trigger operation on the delete control. In response to the removal of the first object, electronic device 110 may stop presenting the first element and continue to present the second session entry. For example, after the first object is removed, the first element used to represent the ownership of the object (e.g., the "Myself" label) is no longer presented, while the entry point of the corresponding session (e.g., the second session entry point, etc.) and its session content are still retained. In this way, the ownership relationship between the session and the object can be separated, that is, the session is not deleted while the association between the session and the object is removed, thereby avoiding the loss of session content due to the removal of the object. In some cases, the interface after the first object is removed is not shown separately in the current figure, and this interface can be obtained by correspondingly changing the aforementioned interface 200E.

[0067] like Figure 2EAs shown, the electronic device 110 can also present a viewing entry 226 (illustratively represented as "XX File" and ">" in the figure), entry 228-1 (corresponding to the first object "Myself") and entry 228-2 (corresponding to the second object "User 1"), and a new file entry 230 (illustratively represented as "+" in the figure, used to create a new object). As an example, the electronic device 110 can receive a trigger operation on the viewing entry 226 and can accordingly present... Figure 2F The interface 200F is shown. Alternatively, the electronic device 110 may, in response to a triggering of entry 228-1 or entry 228-2, present descriptive information associated with the corresponding object to indicate the attributes associated with the corresponding object.

[0068] like Figure 2F As shown, the electronic device 110 can display multiple descriptive items corresponding to multiple objects on the interface 200F. For example, descriptive item 232-1 and descriptive item 232-2. For example, descriptive item 232-1 may correspond to a first object. For example, descriptive item 232-2 may correspond to a second object. Taking descriptive item 232-1 as an example, descriptive item 232-1 may include the name identifier of the first object (e.g., "myself") and associated information, etc. For example, the electronic device 110 can display descriptive information associated with the first object in response to a trigger operation on descriptive item 232-1. Alternatively, the electronic device 110 can display descriptive information associated with the second object in response to a trigger operation on descriptive item 232-2.

[0069] For example, description items 232-1 and 232-2 can be part of the description information of the corresponding object. Taking the description information of the first object as an example, this description information can indicate at least one attribute of the first object. In some cases, at least one attribute of the first object can be updated based on multiple sessions associated with the first object. For example, the description information may include content 234-1 (illustratively represented in the figure as "[My] Consultation Records" and corresponding records). For example, multiple sessions of the first object can be aggregated in content 234-1, thus demonstrating that the attribute associated with the first object is updated based on multiple sessions. In this way, the description information related to the object can be accumulated and updated according to its associated sessions, thereby helping to provide a reference suitable for the object for subsequent communication.

[0070] In some cases, the descriptive information may include content 234-2 (illustratively represented in the diagram as "Report Folder Upload" or "My Reports," used for uploading and viewing reports for this object) and content 234-3 (illustratively represented in the diagram as "Suggestions for Adding to XX Assistant," used to provide supplementary information for the virtual object). Contents 234-2 and 234-3 can serve as sources of descriptive information, and the virtual object can generate corresponding responses based on this descriptive information. In some cases, reports uploaded under this object can be automatically stored in the object's descriptive information. Furthermore, when parsing a report, the information indicated by the report can be compared with the current object; if they do not match, the report may not be stored in the object's file. The aforementioned processes of report identification and object file maintenance and updates can be handled by the backend (e.g., server 130), and are described here only as examples in the specification.

[0071] Alternatively, the electronic device 110 may also present indicator information associated with the first object in the interface 200F. For example, the indicator information may be part of descriptive information used to determine attributes associated with the first object. For example, such indicator information may be collected based on wearable devices associated with the first object.

[0072] Continue to refer to Figure 2C The user can also perform a second trigger operation on identifier 206-3 (the second identifier). In response to the second trigger operation on identifier 206-3, electronic device 110 can display a second session with the virtual object on the first interface. The second session is associated with the second object (represented as "User 1" in the figure), and the first session is independent of the second session. Thus, when the user switches between the first and second identifiers, electronic device 110 correspondingly switches between the first session associated with the first object and the second session associated with the second object, while the content and context of these two sessions are isolated from each other and do not mix. In this way, communication with different objects can be independently organized and displayed within the same interface.

[0073] like Figure 2G As shown, electronic device 110 can present interface 200G. Interface 200G illustrates another implementation of the first interface. For example, electronic device 110 can display a second session with a virtual object on the first interface (e.g., interface 200G).

[0074] In some scenarios, electronic device 110 may receive the first input content in a fourth session. The fourth session is independent of the first object (e.g., it may be a session belonging to another object, or a session without a specified object (e.g., a temporary session)). As an example, the first input content may be a message from the user or content such as images or documents uploaded by the user. Taking the session displayed on interface 200G (e.g., the second session) corresponding to the fourth session as an example, the first input content may be message 236. In response to receiving the first input content, electronic device 110 may present message 238 from a virtual object. For example, message 238 may be a reply to message 236.

[0075] In some cases, in response to the association of the first input content with the first object, the electronic device 110 may present a first prompt 240, which guides the user to switch to a session associated with the first object (illustratively represented in the figure as "The content you provided is related to me, you can switch to a session associated with me"). Alternatively, the first prompt may also be implemented as a message from a virtual object or the like. Here, the association between the first input content and the first object can be identified by the backend (e.g., server 130), and is simply expressed as "associated with," without limiting the specific identification method. As an example, the association between the first input and the first object can be determined based on the semantic matching degree between the text in the first input content and the descriptive information (e.g., file information) or historical session records corresponding to the first object. For example, the backend may extract keywords, entity names, or phrases from the first input content and compare them with the identification information of the first object and the message content in multiple sessions associated with the first object. If there is a match or the similarity exceeds a preset threshold, it is determined that the first input content is associated with the first object. As another example, the backend can determine the association by mapping specific terms or operational intentions in the first input content to a first object based on pre-built mapping relationships. Furthermore, the association can be dynamically learned: when the electronic device 110 detects that a user has repeatedly entered similar content for the first object in different sessions, the backend can mark that type of content as associated with the first object. In this way, when the input content is more suitable for another object, the user can be promptly guided to switch to the session associated with that object, thus helping to maintain a clear understanding of the context and content of each object's session.

[0076] In some cases, in response to receiving a first operation, electronic device 110 may display a fifth session (not shown) with a virtual object on a first interface, the fifth session being associated with the first object. Alternatively, electronic device 110 may send a first message in the fifth session, the first message being associated with the first input content (e.g., message 236). In some cases, the first operation may include triggering a first prompt 240. Alternatively, the first operation may include triggering a first identifier (e.g., identifier 206-2). For example, a user may switch by triggering either the first prompt 240 or by triggering the identifier of the first object. In some cases, the fifth session may be created in response to the first operation (e.g., creating a new session to take over the input when switching to the first object). Alternatively, the fifth session may be selected from at least one session associated with the first object (e.g., entering an existing session when switching to the first object). For example, such a fifth session may be the latest session among multiple sessions associated with the first object. Alternatively, the fifth session may be the session associated with the first input content among multiple sessions associated with the first object.

[0077] For example, electronic device 110 or server 130 can acquire keywords, entities, or semantic features from the first input content and search for sessions containing messages matching the keywords, entities, or semantic features among multiple sessions associated with the first object. If at least one session exists whose historical message content shares common terms, topics, or contextual associations with the first input content (e.g., the first input content mentions an event, and the event was also discussed in a historical session), then electronic device 110 can identify that session as the fifth session. As an example, electronic device 110 or server 130 can calculate the text similarity between the first input content and each historical session and select the session with the highest similarity as the fifth session. As another example, electronic device 110 or server 130 can retrieve metadata or message records of multiple sessions associated with the first object based on entity names (e.g., people, places, item identifiers, etc.) appearing in the first input content and select the session containing that entity name and that was most recently updated as the fifth session. In this way, after switching objects, users can automatically enter the historical session most relevant to the current input content, thus continuing the previous conversation without having to manually search for or create a new session.

[0078] In some cases, associating the first message with the first input content 236 can mean that the first message is obtained based on the first input content 236. For example, the first input content 236 can be sent as a first message, modified, or summarized, or filled into the input component. In this way, after switching to a session associated with the first object, the previous input content can be carried over to that session, thereby avoiding repeated input by the user.

[0079] like Figure 2H As shown, the electronic device 110 can present an interface 200H. For example, Figure 2H Another implementation of the first interface is shown. For example, electronic device 110 may present a fourth identifier (e.g., identifier 206-1) in interface 200H. The fourth identifier is not associated with an object. For example, electronic device 110 may present a sixth session associated with a virtual object in response to a fourth triggering operation on the fourth identifier (e.g., a click operation, etc.). The sixth session is independent of the object (i.e., no object is specified). For example, identifier 206-1 (the fourth identifier) ​​may be in a selected state (e.g., a selected state).

[0080] like Figure 2H As shown, electronic device 110 can receive second input content in the sixth session. For example, the second input content can be a message from the user (e.g., message 242). Alternatively, the second input content can be a picture, video, audio, or document uploaded by the user. Furthermore, electronic device 110 can present session message 244 from a virtual object in the sixth session.

[0081] In some cases, in response to the association of the second input content with the first object, the electronic device 110 may present a second prompt 246, which guides the association of the sixth session with the first object (illustratively represented in the figure as "The content you provided is related to me, do you want to associate this temporary session with me?"). Alternatively, the second prompt may also be implemented as a message from a virtual object or the like. For example, the process of determining the association between the second input and the first object can refer to the exemplary description above regarding the determination process of the association between the first input content and the first object, and will not be repeated here. (Distinguished from...) Figure 2G The first prompt used to guide the "switch" is followed by a second prompt 246 used to guide the user to "associate" (belong to) the current temporary session to the first object. In this way, when the content of a temporary session is related to an object, the user can be guided to classify the temporary session under that object, thus facilitating the organization of related sessions by object.

[0082] In some cases, in response to receiving a second operation (e.g., a confirmation operation to the second prompt 246), the electronic device 110 can associate the sixth session with the first object. Alternatively, the electronic device 110 can present a second element associated with a third session entry. The third session entry corresponds to the sixth session. The second element indicates that the third session entry corresponds to the first object. That is, a previously unassigned temporary session is assigned to the first object, becoming a session of that object, and a visual entry (the third session entry) and a label indicating its object affiliation (the second element) are generated accordingly for that session. As described above... Figure 2E The third session entry and the second element can be connected with... Figure 2E The session entries 222-1 to 222-6 and elements 224-1 to 224-5 are presented in a similar manner. In some cases, the current figure does not show the associated session entry separately; it can be referred to the foregoing. Figure 2E Presented.

[0083] Figure 2I An implementation of the new object file interface, namely interface 200I, is shown, which illustrates the interface via the aforementioned new consultant entry (e.g. Figure 2A Entrance 204 or Figure 2B The interface invoked by entry point 208, used for creating objects. For example... Figure 2I As shown, electronic device 110 can receive a second request for creating a third object.

[0084] like Figure 2I As shown, electronic device 110 can display panel 248 (schematically represented as "Create Consultant Profile" in the figure). For example, panel 248 is used to create a third object and collect descriptive information associated with the third object. In some cases, electronic device 110 can obtain descriptive information associated with the third object through panel 248. The collected descriptive information may include, for example, nickname 250-1 ("User 2" in the figure), XX information 250-2, and XX date 250-3 ("XXXX-XX-XX" in the figure), etc. Nickname 250-1 can also be used as one of the aforementioned identification information. As an example, when a user submits relevant information through panel 248, electronic device 110 can create a third object accordingly. The changes to the first interface after creating the third object will be discussed below. Figure 2J Further description. As an example, after the third object is created, the electronic device 110 can accordingly present itself as follows: Figure 2J The state shown.

[0085] Figure 2J Another implementation of the first interface is shown, namely interface 200J, which illustrates the state of the first interface after the creation of the third object. For example... Figure 2JAs shown, after the third object (“User 2” in the figure) is created, the electronic device 110 can display an identifier 252 (also called the third identifier) ​​on the first interface, which corresponds to the third object.

[0086] like Figure 2J As shown, in response to a fifth trigger operation on identifier 252 (third identifier), electronic device 110 can display a seventh session with a virtual object on a first interface, the seventh session being associated with the third object. Figure 2J As shown, the electronic device 110 can also display prompt text 254 (illustratively represented in the figure as "Consulting User 2"). For example, prompt text 254 is used to indicate the object corresponding to the currently displayed session, which, in conjunction with the above, Figure 2C The described prompt text 212 is similar, indicating that a seventh session associated with a third object has been displayed.

[0087] In some cases, electronic device 110 can obtain descriptive information associated with a third object. Alternatively, electronic device 110 can present a second message from the seventh session on a first interface. The second message originates from the virtual object. The second message is generated based on this descriptive information. That is, the content of the response message (i.e., the second message) given by the virtual object in the seventh session associated with the third object can be determined based on the descriptive information (file) of the third object. In some cases, the specific content of the second message can be generated by the backend (e.g., server 130) based on the descriptive information; this is only described here as an example in the specification. In this way, the virtual object can provide a more targeted response by combining the object's descriptive information.

[0088] It should be understood that in the examples above, the sessions corresponding to different objects are independent and isolated from each other in terms of presentation and context. At the backend implementation level, the description information (files) of each object and the context of historical interactions can be called in a general way to support the virtual object in generating corresponding responses. For example, when a virtual object responds to a certain object, it can refer to the description information and historical context associated with that object; when information about other related objects is involved, it can also be called accordingly. The above calls are carried out by the backend and are only described here as examples in the specification. The examples in this solution are limited to the interface presentation and interaction observable on the electronic device 110 side.

[0089] Based on the process described above, the above solution allows sessions corresponding to different objects to be independently organized and displayed within the same interface. Users can switch between sessions of different objects by triggering corresponding identifiers, ensuring that the session content and context of each object are isolated and do not mix. This helps to clearly distinguish and manage communication processes involving multiple objects and facilitates subsequent attribution, querying, and storage of relevant contexts by object. Furthermore, it enables virtual objects to provide appropriate services to different objects, thus improving the quality of services provided by virtual objects.

[0090] Example process Figure 3 A flowchart illustrating an example process 300 for interface interaction under certain conditions is shown. Process 300 can be implemented at electronic device 110. See below for reference. Figure 1 To describe process 300.

[0091] In box 310, electronic device 110 can present multiple identifiers on a first interface, including a first identifier and a second identifier, where the first identifier corresponds to a first object and the second identifier corresponds to a second object.

[0092] In box 320, electronic device 110 may respond to a first trigger operation on a first identifier to display a first session with a virtual object on a first interface, the first session being associated with the first object.

[0093] In box 330, electronic device 110 can respond to a second trigger operation on a second identifier to display a second session with a virtual object on a first interface, the second session being associated with the second object and the first session being independent of the second session.

[0094] In some cases, the first object is associated with multiple sessions with the virtual object, including the first session and the third session. The process 300 also includes: presenting the first session entry associated with the third session; and displaying the third session on the first interface in response to a third triggering operation on the first session entry.

[0095] In this way, the same object can have multiple independent sessions, and users can quickly switch between them through the session entry point to meet communication needs in different scenarios.

[0096] In some cases, presenting the first session entry point associated with the third session includes: receiving a third request for creating a third session; and in response to the third request, creating the third session and presenting the first session entry point.

[0097] In this way, users can proactively create new sessions for objects, with entry points generated instantly, thus expanding the flexibility of session management.

[0098] In some cases, at least one property of the first object is updated based on multiple sessions.

[0099] In this way, object properties evolve dynamically with interactions across multiple sessions, achieving a continuous association of object state.

[0100] In some cases, process 300 further includes: presenting a second session entry point corresponding to the first session; and presenting a first element associated with the second session entry point, the first element indicating that the second session entry point corresponds to the first object.

[0101] In this way, the identifier of the subject is displayed next to the session entry, allowing users to intuitively identify the session's affiliation and reducing confusion.

[0102] In some cases, process 300 further includes: receiving a first request to remove a first object; and in response to the removal of the first object, stopping the rendering of the first element and continuing to render the second session entry.

[0103] In this way, the session entry is retained after the object is removed, but the ownership identifier is removed, which supports the decoupling of the session and the object and avoids data loss.

[0104] In some cases, the first element includes identification information of the first object.

[0105] Using identification information as the attribution element in this way is simple, intuitive, and easy to identify.

[0106] In some cases, process 300 further includes: receiving first input content in a fourth session, the fourth session being independent of the first object; and, in response to the first input content being associated with the first object, presenting a first prompt, the first prompt being used to guide a switch to the session associated with the first object.

[0107] In this way, when a user mentions an object in an unrelated conversation, the system will proactively prompt the user to switch to another object, thus improving the continuity of the interaction.

[0108] In some cases, process 300 further includes: in response to receiving a first operation, displaying a fifth session with a virtual object on a first interface, the fifth session being associated with the first object; and in the fifth session, sending a first message associated with the first input content.

[0109] In this way, after the user confirms with one click, the system automatically creates or locates the object session and sends a message, realizing rapid migration across sessions.

[0110] In some cases, the first operation includes at least one of the following: triggering a first prompt; triggering a first identifier.

[0111] In this way, multiple operation methods are provided (click the prompt or click the icon) to adapt to different user habits.

[0112] In some cases, the fifth session is created in response to the first operation; or the fifth session is selected from at least one session associated with the first object.

[0113] This method allows for the creation of new sessions or the reuse of existing sessions, thereby improving interaction efficiency.

[0114] In some cases, process 300 further includes: presenting a fourth identifier on a first interface, the fourth identifier not associated with an object; and, in response to a fourth triggering operation on the fourth identifier, presenting a sixth session with a virtual object, the sixth session being independent of the object.

[0115] In this way, general conversations without a specific target audience can be supported, meeting the communication needs of temporary or unbound scenarios.

[0116] In some cases, process 300 further includes: receiving second input content in the sixth session; and, in response to the second input content being associated with the first object, presenting a second prompt to guide the association of the sixth session with the first object.

[0117] In this way, when an object is mentioned in a general conversation, the association is suggested, guiding the user to bind the conversation to a specific object.

[0118] In some cases, process 300 further includes: in response to receiving a second operation, associating a sixth session with a first object; and presenting a second element associated with a third session entry, the third session entry corresponding to the sixth session, the second element indicating that the third session entry corresponds to the first object.

[0119] In this way, after user confirmation, the session is associated with the object, and an ownership element is added at the entry point to complete the relationship binding.

[0120] In some cases, process 300 may further include: presenting an input component in the first interface; and presenting a third prompt in the input component, the third prompt being associated with the session displayed in the first interface.

[0121] In this way, dynamic prompts are displayed within the input component to help users understand the context of the current session or available operations.

[0122] In some cases, process 300 further includes: receiving a second request for creating a third object; presenting a third identifier on a first interface, the third identifier corresponding to the third object; and, in response to a fifth triggering operation on the third identifier, displaying a seventh session with the virtual object on the first interface, the seventh session being associated with the third object.

[0123] This approach supports the creation of new objects and the automatic generation of corresponding sessions, thus expanding the object and session system.

[0124] In some cases, process 300 may further include: obtaining descriptive information associated with a third object; and on a first interface, presenting a second message from a seventh session, the second message originating from a virtual object and generated based on the descriptive information.

[0125] Example devices and equipment A corresponding apparatus for implementing the above methods or processes is also provided. Figure 4 A schematic structural block diagram of an example device 400 for interface interaction under certain conditions is shown. Device 400 can be implemented as or included in electronic device 110. The various modules / components in device 400 can be implemented by hardware, software, firmware, or any combination thereof.

[0126] like Figure 4 As shown, the device 400 includes: a first presentation module 410 configured to present a plurality of identifiers on a first interface, the plurality of identifiers including a first identifier and a second identifier, the first identifier corresponding to a first object and the second identifier corresponding to a second object; a second presentation module 420 configured to display a first session with a virtual object on the first interface in response to a first trigger operation on the first identifier, the first session being associated with the first object; and a third presentation module 430 configured to display a second session with a virtual object on the first interface in response to a second trigger operation on the second identifier, the second session being associated with the second object, and the first session being independent of the second session.

[0127] In some cases, the first object is associated with multiple sessions with the virtual object, including the first session and the third session. The device 400 also includes a fourth presentation module configured to: present the entry point of the first session associated with the third session; and display the third session on the first interface in response to a third trigger operation on the entry point of the first session.

[0128] In some cases, the fourth presentation module is also configured to: receive a third request for creating a third session; and in response to the third request, create a third session and present the first session entry.

[0129] In some cases, at least one property of the first object is updated based on multiple sessions.

[0130] In some cases, the device 400 also includes a fifth presentation module configured to: present a second session entry corresponding to the first session; and present a first element associated with the second session entry, the first element indicating that the second session entry corresponds to a first object.

[0131] In some cases, device 400 also includes a removal module configured to: receive a first request for removing a first object; and in response to the removal of the first object, stop rendering the first element and continue rendering the second session entry.

[0132] In some cases, the first element includes identification information of the first object.

[0133] In some cases, device 400 also includes a prompting module configured to: receive first input content in a fourth session, the fourth session being independent of the first object; and, in response to the first input content being associated with the first object, present a first prompt to guide a switch to a session associated with the first object.

[0134] In some cases, the device 400 also includes a sending module configured to: in response to receiving a first operation, display a fifth session with a virtual object on a first interface, the fifth session being associated with the first object; and in the fifth session, send a first message associated with the first input content.

[0135] In some cases, the first operation includes at least one of the following: triggering a first prompt; triggering a first identifier.

[0136] In some cases, the fifth session is created in response to the first operation; or the fifth session is selected from at least one session associated with the first object.

[0137] In some cases, device 400 also includes a sixth presentation module configured to: present a fourth identifier, which is not associated with an object, on a first interface; and present a sixth session with a virtual object, independent of the object, in response to a fourth trigger operation on the fourth identifier.

[0138] In some cases, device 400 also includes a second prompting module configured to: receive second input content in a sixth session; and, in response to the second input content being associated with a first object, present a second prompt to guide the association of the sixth session with the first object.

[0139] In some cases, the device 400 also includes an association module configured to: associate a sixth session with a first object in response to receiving a second operation; and present a second element associated with a third session entry corresponding to the sixth session, the second element indicating that the third session entry corresponds to the first object.

[0140] In some cases, device 400 also includes an input component module configured to: present an input component in a first interface; and present a third prompt in the input component, the third prompt being associated with the session displayed in the first interface.

[0141] In some cases, device 400 also includes a creation module configured to: receive a second request for creating a third object; present a third identifier on a first interface, the third identifier corresponding to the third object; and, in response to a fifth trigger operation on the third identifier, display a seventh session with the virtual object on the first interface, the seventh session being associated with the third object.

[0142] In some cases, device 400 also includes a messaging module configured to: acquire description information associated with a third object; and, on a first interface, present a second message from a seventh session, the second message originating from a virtual object and generated based on the description information.

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for interface interaction, comprising: On the first interface, multiple icons are presented, including a first icon and a second icon, where the first icon corresponds to a first object and the second icon corresponds to a second object. In response to a first trigger operation on the first identifier, a first session with a virtual object is displayed on the first interface, the first session being associated with the first object; as well as In response to a second triggering operation on the second identifier, a second session with the virtual object is displayed on the first interface, the second session being associated with the second object, and the first session being independent of the second session.

2. The method of claim 1, wherein the first object is associated with a plurality of sessions with the virtual object, the plurality of sessions including the first session and a third session, the method further comprising: Present the first session entry point associated with the third session; as well as In response to a third trigger operation on the first session entry point, the third session is displayed on the first interface.

3. The method of claim 2, wherein at least one attribute of the first object is updated based on the plurality of sessions.

4. The method according to claim 1, further comprising: A second session entry point is presented, which corresponds to the first session; as well as Present a first element associated with the second session entry, the first element indicating that the second session entry corresponds to the first object.

5. The method according to claim 4, further comprising: Receive a first request, the first request being used to remove the first object; as well as In response to the removal of the first object, the rendering of the first element is stopped, while the rendering of the second session entry continues.

6. The method according to claim 4, wherein the first element includes the identification information of the first object.

7. The method according to claim 1, further comprising: In the fourth session, first input content is received, and the fourth session is independent of the first object; as well as In response to the first input being associated with the first object, a first prompt is presented, which guides the user to switch to a session associated with the first object.

8. The method of claim 7, further comprising: In response to receiving the first operation, a fifth session with the virtual object is displayed on the first interface, the fifth session being associated with the first object; as well as In the fifth session, a first message is sent, which is associated with the first input content.

9. The method according to claim 8, wherein: The fifth session is created in response to the first operation; or The fifth session is selected from at least one session associated with the first object.

10. The method of claim 1, further comprising: On the first interface, a fourth identifier is presented, which is not associated with any object; as well as In response to a fourth triggering operation on the fourth identifier, a sixth session with the virtual object is presented, the sixth session being independent of the object.

11. The method of claim 10, further comprising: In the sixth session, the second input content is received; as well as In response to the association of the second input content with the first object, a second prompt is presented to guide the association of the sixth session with the first object.

12. The method according to claim 11, In response to receiving the second operation, the sixth session is associated with the first object; and A second element is presented that is associated with the third session entry, which corresponds to the sixth session, and the second element indicates that the third session entry corresponds to the first object.

13. The method of claim 1, further comprising: The input component is presented in the first interface; as well as In the input component, a third prompt is presented, which is associated with the session displayed on the first interface.

14. The method according to claim 1, further comprising: Receive a second request, which is used to create a third object; On the first interface, a third identifier is presented, which corresponds to the third object; as well as In response to a fifth trigger operation on the third identifier, a seventh session with the virtual object is displayed on the first interface, the seventh session being associated with the third object.

15. The method of claim 14, further comprising: Obtain the description information associated with the third object; as well as On the first interface, a second message from the seventh session is presented. The second message originates from the virtual object and is generated based on the description information.

16. A device for interface interaction, comprising: A first presentation module is configured to present multiple identifiers on a first interface, the multiple identifiers including a first identifier and a second identifier, the first identifier corresponding to a first object and the second identifier corresponding to a second object; The first display module is configured to display a first session with a virtual object on the first interface in response to a first trigger operation on the first identifier, the first session being associated with the first object; as well as The second display module is configured to display a second session with the virtual object on the first interface in response to a second trigger operation on the second identifier. The second session is associated with the second object, and the first session is independent of the second session.

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

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

19. 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 15.

Images