Method, device, equipment and storage medium for information interaction

Abstract

According to embodiments of this disclosure, a method, apparatus, device, and storage medium for information interaction are provided. The method includes: in response to detecting a trigger operation by a first user on a scene recommendation page, presenting at least one scene on the scene recommendation page; and based on the first user's trigger operation on a first scene among the at least one scenes, adding the first scene to a scene list associated with the first user for subsequent selection, or selecting the first scene for interaction between the first user and a first digital assistant. Each of the at least one scene is configured to perform a task related to that scene during the interaction between the first user and the first digital assistant. Therefore, this method facilitates users in selecting desired scenes through the scene recommendation page for interaction with the digital assistant.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of computers, and particularly to methods, apparatuses, devices, and computer-readable storage media for information interaction. Background Technology

[0002] With the rapid development of internet technology, the internet has become a crucial platform for people to access and share content. Users can access the internet through terminal devices to enjoy various internet services. Terminal devices present relevant content and facilitate interaction with users through application user interfaces, providing services as well. Therefore, rich and varied application interfaces are an important means of enhancing user experience. With the development of information technology, various terminal devices can provide various services to people in work and life. For example, applications that provide services can be deployed on terminal devices. Terminal devices or applications can provide users with digital assistant functions to assist them in using the terminal devices or applications. How to improve the flexibility of user interaction with digital assistants is a technical issue that needs to be explored. Summary of the Invention

[0003] In a first aspect of this disclosure, a method for information interaction is provided. The method includes: in response to detecting a triggering operation by a first user on a scene recommendation page, presenting at least one scene on the scene recommendation page; and based on the first user's triggering operation on a first scene among the at least one scenes, adding the first scene to a scene list associated with the first user for subsequent selection, or selecting the first scene for interaction between the first user and a first digital assistant, wherein the at least one scene is configured to perform a task related to the corresponding scene during the interaction between the first user and the first digital assistant.

[0004] In a second aspect of this disclosure, a method for information interaction is provided. The method includes: in response to an operation of publishing a first scenario, obtaining first publishing information for the first scenario; wherein the first scenario is configured with corresponding configuration information to perform a task of a corresponding type, the configuration information including at least one of the following: scenario setting information and plugin information, wherein the scenario setting information describes information related to the corresponding scenario, and the plugin information indicates at least one plugin used to perform a task in the corresponding scenario; and publishing the first scenario to a target digital assistant based on the first publishing information, so that the target digital assistant can perform related tasks based on the first scenario.

[0005] In a third aspect of this disclosure, an apparatus for information interaction is provided. The apparatus includes: a detection module configured to present at least one scene in a scene recommendation page in response to detecting a trigger operation by a first user on the scene recommendation page; and an adding module configured to add the first scene to a list of scenes associated with the first user for subsequent selection based on the first user's trigger operation on the first scene among the at least one scenes, or to select the first scene for interaction between the first user and a first digital assistant, wherein each of the at least one scene is configured to perform a task related to the corresponding scene during the interaction between the first user and the first digital assistant.

[0006] In a fourth aspect of this disclosure, an apparatus for information interaction is provided. The apparatus includes: an information acquisition module configured to acquire first release information for a first scenario in response to an operation of releasing a first scenario; wherein the first scenario is configured with corresponding configuration information to perform a task of a corresponding type, the configuration information including at least one of the following: scenario setting information and plugin information, wherein the scenario setting information describes information related to the corresponding scenario, and the plugin information indicates at least one plugin used to perform a task in the corresponding scenario; and a scenario release module configured to release the first scenario to a target digital assistant based on the first release information, so that the target digital assistant can perform related tasks based on the first scenario.

[0007] In a fifth aspect of this disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the methods of the first aspect and / or the second aspect.

[0008] In a sixth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program that can be executed by a processor to implement the methods of the first and / or second aspects.

[0009] It should be understood that the description in this section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

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

[0012] Figures 2A to 2D A schematic diagram of an example client interface for an interactive window according to some embodiments of the present disclosure is shown;

[0013] Figures 3A to 3C A schematic diagram of an example client interface for creating a scenario according to some embodiments of the present disclosure is shown;

[0014] Figure 4A A flowchart illustrating an information interaction process according to some embodiments of the present disclosure is shown;

[0015] Figure 4B A flowchart illustrating an information interaction process according to other embodiments of the present disclosure is shown;

[0016] Figure 5A A block diagram of an apparatus for information interaction according to some embodiments of the present disclosure is shown;

[0017] Figure 5B Block diagrams of apparatuses for information interaction according to other embodiments of the present disclosure are shown; and Figure 6 A block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented is shown; Detailed Implementation

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

[0019] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

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

[0021] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0022] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, relevant users should be informed of the type, scope of use, and usage scenarios of the information involved in this disclosure through appropriate means in accordance with relevant laws and regulations, and authorization should be obtained from the relevant users. Among them, relevant users may include any type of rights holder, such as individuals, enterprises, and groups.

[0023] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly inform the user that the requested operation will require obtaining and using the user's information, thereby enabling the relevant user to choose whether to provide information to the software or hardware such as the electronic device, application, server, or storage medium that performs the operation of the technical solution disclosed herein based on the prompt message.

[0024] As an optional but non-restrictive implementation, in response to a user's active request, a prompt message can be sent to the user, such as a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide information to the electronic device.

[0025] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

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

[0027] In some embodiments, the digital assistant 120 and application 125 can be downloaded and installed on the terminal device 110. In some embodiments, the digital assistant 120 and application 125 can also be accessed in other ways, such as through a web page. Figure 1 In environment 100, in response to application 125 being launched, terminal device 110 can present the interface 150 of digital assistant 120 and application 125.

[0028] Applications 125 include, but are not limited to, one or more of the following: chat applications (also known as instant messaging applications), document applications, audio and video conferencing applications, email applications, task applications, calendar applications, goal and key results (OKR) applications, etc. Although Figure 1 The image shows a single application, but in reality, multiple applications can be installed on the terminal device 110. In some embodiments, application 125 may include a multi-functional collaboration platform, such as an office collaboration platform (also known as an office suite), which can provide integration of various types of applications or components to facilitate people's office work, communication, and other activities. In a multi-functional collaboration platform, people can launch different applications or components as needed to complete corresponding information processing, sharing, communication, etc.

[0029] Application 125 can provide content entity 126. Content entity 126 can be a content instance created by user 140 or other users on application 125. For example, depending on the type of application 125, content entity 126 can be a document (e.g., a Word document, a PDF document, a presentation, a spreadsheet document, etc.), email, message (e.g., a conversation message on an instant messaging application), calendar, schedule, task, audio, video, image, etc.

[0030] In some embodiments, the digital assistant 120 may be provided by a standalone application or may be integrated into an application 120 capable of providing content entities. The application providing the client interface for the digital assistant may correspond to a single-function application or a multi-functional collaboration platform, such as an office suite or other collaboration platforms capable of integrating multiple components. In some embodiments, the digital assistant 120 supports the use of plugins. Each plugin can provide one or more functions of the application. Such plugins include, but are not limited to, one or more of the following: search plugins, contact plugins, messaging plugins, document plugins, form plugins, email plugins, calendar plugins, schedule plugins, task plugins, etc.

[0031] Digital assistant 120 is a user's intelligent assistant, possessing intelligent dialogue and information processing capabilities. In embodiments of this disclosure, digital assistant 120 is used to interact with user 140 to assist user 140 in using terminal devices or applications. An interaction window with digital assistant 120 can be presented in the client interface. In the interaction window, user 140 can converse with digital assistant 120 by inputting natural language to instruct digital assistant to assist in completing various tasks, including operations on content entity 126.

[0032] In some embodiments, digital assistant 120 may act as a contact for user 140, being included in the current user 140's contact list in the office suite or in the chat component's message stream. In some embodiments, user 140 and digital assistant 120 have a corresponding relationship. For example, a first digital assistant corresponds to a first user, a second digital assistant corresponds to a second user, and so on. In some embodiments, the first digital assistant may uniquely correspond to the first user, the second digital assistant may uniquely correspond to the second user, and so on. That is, the first digital assistant for the first user may be specific to or exclusive to the first user. For example, in the process of the first digital assistant providing assistance or services to the first user, the first digital assistant may utilize its historical interaction information with the first user, the data authorized by the first user that it can access, its current interaction context with the first user, etc. If the first user is an individual, the first digital assistant may be considered a personal digital assistant. It is understood that in the disclosed embodiments, the first digital assistant accesses data with granted permissions based on the first user's authorization. It should be understood that the terms "uniquely corresponding" or similar expressions in this disclosure are not intended to limit the first digital assistant to being updated accordingly based on the interaction process between the first user and the first digital assistant. Of course, depending on the actual application needs, the digital assistant 120 does not necessarily have to be specific to the current user 140, but can be a general digital assistant.

[0033] In some embodiments, multiple interaction modes can be provided for the user 140 and the digital assistant 120, and the user can flexibly switch between these modes. When a certain interaction mode is triggered, a corresponding interaction area is presented to facilitate interaction between the user 140 and the digital assistant 120. The interaction methods between the user 140 and the digital assistant 120 differ under different interaction modes, thus flexibly adapting to the interaction needs of different application scenarios.

[0034] In some embodiments, information processing services specific to user 140 can be provided based on historical interaction information between user 140 and digital assistant 120 and / or data ranges specific to user 140. In some embodiments, historical interaction information of user 140 interacting with digital assistant 120 in multiple interaction modes can all be associated with user 140 and stored. Thus, in one of the multiple interaction modes (any or a specified interaction mode), digital assistant 120 can provide services to user 140 based on the historical interaction information associated with user 140 stored therein.

[0035] The digital assistant 120 can be invoked or activated by an appropriate means (e.g., keyboard shortcuts, buttons, or voice) to present an interaction window with the user 140. The interaction window can be opened by selecting the digital assistant 1201. The interaction window may include interface elements for information interaction, such as input boxes, message lists, message bubbles, etc. In other embodiments, the digital assistant 120 can be invoked through entry controls or menus provided on the page, or by inputting preset commands.

[0036] The interaction window between the digital assistant 120 and the user 140 may include a session window, such as a session window in an instant messaging application or the instant messaging module of a target application. In some embodiments, the interaction window between the digital assistant 120 and the user 140 may include a floating window corresponding to the digital assistant.

[0037] In some embodiments, the digital assistant 120 may support a conversation window interaction mode, also known as conversation mode. In this interaction mode, a conversation window is presented between the user 140 and the digital assistant 120, in which the user 140 and the digital assistant 120 interact through conversation messages. In conversation mode, the digital assistant 120 can perform tasks based on the conversation messages in the conversation window.

[0038] In some embodiments, the conversation mode between user 140 and digital assistant 120 can be invoked or activated by an appropriate means (e.g., shortcut keys, buttons, or voice) to present a conversation window. A conversation window with digital assistant 120 can be opened by selecting digital assistant 120. The conversation window may include interface elements for information interaction, such as input boxes, message lists, message bubbles, etc.

[0039] In some embodiments, the digital assistant 120 may support a floating window (or floating window) interaction mode, also known as a floating window mode. When the floating window mode is triggered, an operation panel (also known as a floating window) corresponding to the digital assistant 120 is presented, and the user 140 can issue commands to the digital assistant 120 based on the operation panel. In some embodiments, the operation panel may include at least one candidate shortcut command. Alternatively or additionally, the operation panel may include input controls for receiving commands. In floating window mode, the digital assistant 120 can perform tasks according to the commands issued by the user 140 through the operation panel.

[0040] In some embodiments, the floating window mode of user 140 and digital assistant 120 can also be invoked or activated by appropriate means (e.g., shortcut keys, buttons, or voice) to present the corresponding operation panel. In some embodiments, activating digital assistant 120 can be supported in specific applications, such as document applications, to provide floating window mode interaction. In some embodiments, to trigger the floating window mode to present the operation panel corresponding to digital assistant 120, an entry control for digital assistant 120 can be presented in the application interface. In response to detecting a trigger operation on the entry control, it can be determined that the floating window mode has been triggered, and the operation panel corresponding to digital assistant 120 is presented in the target interface area.

[0041] In some embodiments described below, for ease of discussion, the example of a session window serving as the interaction window between the user and the digital assistant will be used.

[0042] In some embodiments, terminal device 110 communicates with server 130 to provide services to digital assistant 120 and application 125. Terminal device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, terminal device 110 can also support any type of user-facing interface (such as "wearable" circuitry). Application 130 can be various types of computing systems / servers capable of providing computing power, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, etc.

[0043] 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 this disclosure.

[0044] As briefly mentioned earlier, digital assistants can help users use terminal devices or applications. Some applications offer integration capabilities for different plugins. Besides engaging in free conversation with the digital assistant, users can also use natural language commands to instruct it to perform more complex business-related operations using different plugins, such as creating documents, scheduling appointments, and creating tasks. However, since most users cannot explore the use cases of digital assistants through interaction, targeted guidance is needed. Furthermore, traditionally, when using digital assistants to perform tasks in different scenarios, users often need to interact with different digital assistants (i.e., each digital assistant is only used to perform tasks in one scenario). This results in information not being stored in one place, and these multiple digital assistants not being able to share information. All of this makes the interactive functions of digital assistants inflexible.

[0045] According to some embodiments of this disclosure, an improved scheme for information interaction is proposed. In the embodiments of this disclosure, in response to detecting a trigger operation of a first user on a scene recommendation page, at least one scene is presented on the scene recommendation page; and based on the first user's trigger operation on a first scene among the at least one scenes, the first scene is added to a scene list associated with the first user for subsequent selection, or the first scene is selected for interaction between the first user and the first digital assistant, wherein the at least one scene is configured to perform a task related to the corresponding scene in the interaction between the first user and the first digital assistant. Therefore, in this way, users can conveniently select the desired scene through the scene recommendation page to interact with the digital assistant.

[0046] According to other embodiments of this disclosure, upon publishing a scene, in response to the operation of publishing a first scene, first publishing information of the first scene is obtained. Based on the first publishing information, the first scene is published to the target digital assistant, so that the target digital assistant can perform related tasks based on the first scene. According to this scheme, when a user creates a scene for a specific digital assistant, the created scene can be published to the specific digital assistant for use. This can continuously enrich the interactive capabilities of the target digital assistant.

[0047] Some exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0048] As described above, in the embodiments of this disclosure, a digital assistant is used for interaction with a user. An interaction window between the user and the digital assistant can be presented in the client interface. This interaction window may include a session window, in which the interaction between the user and the digital assistant can be presented in the form of session messages. Alternatively or additionally, the interaction window may also include other types of windows, such as a floating window, where the user can trigger the digital assistant to perform corresponding operations by inputting commands, selecting shortcuts, etc. As an intelligent assistant, the digital assistant has intelligent dialogue and information processing capabilities. In the interaction window, the user inputs interactive messages, and the digital assistant responds to the user's input by providing reply messages. The client interface used to provide the digital assistant can correspond to a single-function application or a multi-functional collaboration platform, such as an office suite or other collaboration platforms capable of integrating multiple components.

[0049] In some embodiments, terminal device 110 may present a conversation window between a user and one or more other users. For example, a conversation window between a user and one other user could be a one-on-one chat window between user A and user B, while a conversation window between a user and multiple other users could be a group chat window between user A and a group of other users. Users can interact with at least one other user by sending and / or receiving messages in the conversation window. For example, terminal device 110 may determine the message content to be sent by the user in response to detecting text entered by the user in an input box. Terminal device 110 may also collect user audio in response to detecting a trigger operation on the audio space. Terminal device 110 may determine the audio or the corresponding text content as the message content to be sent by the user. It should be noted that the operations performed by terminal device 110 as described above and in subsequent descriptions may specifically be performed by relevant applications installed on terminal device 110.

[0050] Within a conversation window, users can input messages via input boxes or other appropriate means (e.g., voice), and the digital assistant can provide a response message based on the input message and relevant knowledge. Messages within a conversation window are typically conversational messages. Such conversational messages can be considered as part of a specific topic.

[0051] Figures 2A to 2D A schematic diagram of an example client interface 200 with an interactive window according to some embodiments of the present disclosure is shown. The client interface 200 can be implemented at a terminal device 110. References are made below. Figure 1 describe Figures 2A to 2C Examples.

[0052] In a conversation window between a user and at least one other user, terminal device 110 (e.g., an instant messaging application installed on terminal device 110, or a suite application integrated with an instant messaging application installed on terminal device 110) may present a trigger control for a digital assistant (e.g., a first digital assistant) in response to detecting a preset input in an input box of the conversation window. Figure 2A As shown, the entry point for the instant messaging application is presented in area 230 of interface 200, and the instant messaging application's feed is presented in area 220 of interface 200. In response to a user selecting any contact or group in the instant messaging application's feed, terminal device 110 can present a corresponding conversation window in area 210 of interface 200. For example, in response to a user activating a digital assistant through a preset operation (e.g., selecting a digital assistant from a contact list), terminal device 110 can present a conversation window (also called the main conversation window) showing the user's interaction with the digital assistant in area 210 of interface 200.

[0053] In some embodiments, in response to the digital assistant being invoked, the terminal device 110 may, by default, open a new topic (e.g., the first topic) in the conversation window and display the dividing line corresponding to the first topic in the conversation window. Figure 2A As shown, in response to the digital assistant being activated, the terminal device 110 can by default display a dividing line 211 corresponding to the new topic and a message card 212 associated with the new topic in the interface 200.

[0054] In this document, a “topic” corresponds to a specific context of the interaction. During each topic-based interaction, the interaction information between the user and the digital assistant is treated as contextual information to help the digital assistant determine subsequent conversational messages. In some embodiments, topics are sometimes also referred to or presented as themes.

[0055] In some embodiments, if the user has prior historical interaction information or topics with the digital assistant, the terminal device 110 may display a portion of the historical interaction information or topics in the session window in response to the digital assistant being invoked. Figure 2B As shown, terminal device 110 may display a portion of the user's previous historical interaction information with the digital assistant in the main session window of interface 200. Alternatively or additionally, in some embodiments, in response to the digital assistant being invoked, terminal device 110 may also not display message card 212 and historical interaction information in the main session window.

[0056] In some embodiments, terminal device 110 may, in response to receiving an operation to start a new topic, start a new topic (e.g., a first topic) in the conversation window between the user and the digital assistant. The conversation window may include an input field, through which terminal device 110 may receive user input, for example. If terminal device 110 detects that the user input is an indication to start a new topic, it determines that an operation to start a new topic has been received. In some embodiments, the conversation window may also include operation controls for starting a new topic (e.g., ...). Figure 2B (The operation control 201 in the middle). For example, the terminal device 110 can determine that an operation to start a new topic has been received in response to detecting a trigger operation on the operation control 201. The terminal device 110 can then present, as follows: Figure 2A Or such as Figure 2C The main session window shown.

[0057] like Figure 2A and Figure 2C As shown, in response to the operation of starting a new topic, terminal device 110 starts a first topic in the main session window, presents a dividing line 211 between the new topic and the previous topic in interface 200, and presents at least one selectable scenario in the session area of ​​the first topic. The session area of ​​the first topic can be, for example, a message card 212. In some embodiments, terminal device 110 may also present a dividing line 211 between the previous topic and the new topic in response to starting a new topic (e.g., ...). Figure 2C (As shown). Terminal device 110 may present at least one scene (e.g., scene 213 and scene 214) in message card 212.

[0058] In this article, within the context of user-digital assistant interaction, a "scenario" refers to a collection of tasks of the same type; that is, one scenario corresponds to multiple tasks of the same type. One or more scenarios can be configured with corresponding configuration information to execute tasks of the corresponding type. For ease of understanding, we will first briefly introduce the scenarios used in user-digital assistant interaction.

[0059] The scenario configuration information includes at least one of the following: scenario setting information and plugin information. Scenario setting information describes information related to the corresponding scenario. Plugin information indicates at least one plugin used to perform tasks in the corresponding scenario. As will be discussed below, the scenario configuration information may also include, for example, instructions for the selected model (where the model is invoked to determine the response to the user in the corresponding scenario), scenario guidance information (presented to the user after the corresponding scenario is selected), at least one recommended question for the digital assistant (presented to the user for selection after the corresponding scenario is selected), and so on. In some embodiments, the scenario setting information and configuration information can be configured, for example, through natural language, allowing scenario creators to easily constrain model output and configure diverse scenarios.

[0060] The scenario configuration information includes at least one of the following: scenario setting information and plugin information. Scenario setting information describes information related to the corresponding scenario. The scenario setting information can influence the digital assistant's response to the user to a certain extent, or be used to determine the digital assistant's response to the user. In some embodiments, scenario setting information is used to construct prompt input to provide to the model used in the corresponding scenario. The digital assistant's response to the user is based on the model's output. Scenario setting information may include, for example, a description of the corresponding type of task, the digital assistant's response style in the scenario, a definition of the workflow to be executed in the corresponding scenario, a definition of the digital assistant's response format in the corresponding scenario, etc. In some embodiments, the digital assistant will use the model to understand user input and provide a response to the user based on the model's output. The model used by the digital assistant can run locally on the terminal device 110 or on a remote server. By utilizing scenario setting information to construct a portion of the model's prompt input, the model can be guided to complete the task to be performed in the corresponding scenario. In some embodiments, the model can be a machine learning model, a deep learning model, a learning model, a neural network, etc. In some embodiments, the model can be based on a language model (LM). Language models can acquire question-answering capabilities by learning from large corpora. Models can also be based on other appropriate models.

[0061] The plugin information indicates at least one plugin used to perform tasks in a given scenario. The plugin information for a scenario allows configuration of the plugins to be used in that scenario. In some embodiments, during plugin execution within the given scenario, the plugin can also invoke a model to complete the corresponding task. In some embodiments, a plugin can also invoke open interfaces provided by other applications (e.g., document, calendar, meeting applications) to complete corresponding tasks, such as modifying documents, creating schedules, or summarizing meetings.

[0062] In some embodiments, the scenario configuration information may also include the scenario name, scenario description information, and so on.

[0063] In some embodiments, terminal device 110 may provide a message card to the user in a session window, the message card presenting at least some of a set of scenes. Terminal device 110 may present the scene name and / or scene description information associated with the scene in the message card. For example, the user may select a scene that meets their needs based on the scene name and / or scene description information presented in the message card.

[0064] In some embodiments, the scenario configuration information may include, but is not limited to: the selected model (here, the model is invoked to determine the response to the user in the corresponding scenario), scenario guidance information (the scenario guidance information is presented to the user after the corresponding scenario is selected), at least one recommended question for the digital assistant (at least one recommended question is presented to the user for selection after the corresponding scenario is selected), any combination of one or more of the foregoing, etc. Scenario guidance information may, for example, be descriptive information about task instances that can be performed in the scenario. In some embodiments, the scenario setting information and configuration information can be configured, for example, through natural language, allowing scenario creators to easily constrain the model's output and configure diverse scenarios.

[0065] In some embodiments, the scene configuration information may also indicate at least one operational control associated with the scene. As will be described in detail below, at least one operational control associated with a scene may be presented to the user when the scene is selected for interaction, facilitating the user's interaction with the digital assistant within the corresponding scene. That is, during scene creation, the scene creator can configure at least one operational control associated with the corresponding scene. In some embodiments, the scene setting information and configuration information may be configured by the scene creator, for example, through natural language. This allows the scene creator to easily constrain the model's output and configure diverse scenes.

[0066] In some embodiments, if a scenario is selected for interaction between a first user and a first digital assistant, the interaction between the user and the digital assistant is performed in the session window based at least on the configuration information of the selected scenario. The scenario settings, plugin information, selected model, etc., of the selected scenario are used to guide the interaction within that scenario.

[0067] In some embodiments, the terminal device 110 may also present a scene viewing control 215 in the message card 212. The terminal device 110 may trigger the presentation of more scenes in response to a detected trigger operation on the scene viewing control 215. For example, to ensure the simplicity of the main session window, in the case of multiple scenes, the terminal device 110 may only present some scenes in the operation card 212 and present more scenes in response to a detected trigger operation on the scene viewing control 215.

[0068] In addition to providing access to more scenes in the message cards of the conversation window, in some embodiments, the terminal device may also present a scene dialogue entry 202 in the conversation window or a scene dialogue control 204 in the function bar associated with the conversation window. More scenes can be triggered to appear via the scene dialogue entry 202 or the scene dialogue control 204.

[0069] In embodiments of this disclosure, terminal device 110, in response to detecting a trigger operation by a first user on the scene recommendation page, presents the scene recommendation page corresponding to the first user. For example... Figure 2D As shown, in response to detecting that a user clicks on the scene dialogue entry 202 in the conversation window presented in area 210 of the interface 200 by the terminal device 110, or that the user clicks on the scene conversation control 244 in the conversation window (or a trigger operation on the scene viewing control 215 is detected), the terminal device 110 presents a scene recommendation page 240. In some embodiments, through the triggering of the scene dialogue entry 202, the scene conversation control 244, or the scene viewing control 215, a scene list page associated with the first user can be presented by default (e.g., Figure 2D The "My Scenes" tab shown corresponds to page 242). Users can switch to the scene recommendation page 240 by clicking the "Discover" tab. Besides... Figures 2A to 2D In addition to the access points shown, other access points for scenario-based recommendation pages may also be provided. The embodiments disclosed herein do not limit this in this respect. Furthermore, although in Figure 2D In this embodiment, the scenario recommendation page is shown alongside the session window. However, in other embodiments, the scenario recommendation page may also be presented independently of the session window, as if it were overlaying the session window, or in any other appropriate manner, depending on the specific application configuration.

[0070] Terminal device 110 presents at least one scenario on scenario recommendation page 240 for users to select for interaction or add to their own scenario list. For example, scenario names presented on scenario recommendation page 240 by terminal device 110 include: copywriting scenario 250, English learning scenario 260, company regulations consultation scenario, form learning scenario, HCM analysis scenario, professional learning scenario, etc. In some embodiments, terminal device 110 may present scene icons for each of at least one scenario on scenario recommendation page 240, such as... Figure 2D The icon for copywriting creation 250 is 258. Terminal device 110 can display one or more scene descriptions on the scene recommendation page 240.

[0071] In some instances, terminal device 110 may also display at least one access point for each scene on scene recommendation page 240. By triggering the scene access point, the corresponding scene can be selected for the interaction between the first user and the first digital assistant. For example... Figure 2D As shown, the card corresponding to copywriting creation scenario 250 is configured as the access point for this scenario. The first user can enter the copywriting creation scenario by clicking on it, making this scenario used for the interaction between the first user and the digital assistant in the conversation window. For example, in the conversation window between the first user and the first digital assistant, a new topic can be started based on the copywriting creation scenario. In the newly started topic, the conversation between the first user and the first digital assistant is executed based on the configuration information of the copywriting creation scenario.

[0072] In some embodiments, the terminal device 110 may also display at least one scene-specific add control on the scene recommendation page 240, such as... Figure 2D As shown, the first user clicks the add control in copywriting creation scenario 250 to add copywriting creation scenario 250 to the first user's associated scenario list ("My Scenarios"). The terminal device 110 will display an add success control 252 in copywriting creation scenario 250. Note that in Figure 2D Assuming that copywriting scenario 250 has already been added to the first user's list of associated scenarios, the add control for this scenario is modified into an add success control. Similarly, the first user can also click the add control 262 for English learning scenario 260 to add English learning scenario 262 to the list of scenarios associated with the first user ("My Scenarios").

[0073] In some embodiments, the terminal device 110 may also display at least one creation source for each scene on the scene recommendation page 240, where the creation source indicates the creator of the scene. For example, the creation source could be: a certain team, a certain user, etc. Figure 2DAs shown, terminal device 110 displays creation source 256 in copywriting creation scenario 250. For example, when Zhang San creates copywriting creation scenario 250, terminal device 110 will display creation source 256 in the form of "@Zhang San" in copywriting creation scenario 250. Similarly, when Li Si creates English learning scenario 260, terminal device 110 will display creation source 256 in the form of "@Li Si" in English learning scenario 260, and so on.

[0074] The terminal device 110 can also display the addition count of at least one scene on the scene recommendation page 240. The addition count of each scene indicates how many users have added the scene, that is, how many users have added the scene to their respective scene lists. Figure 2D As shown, if the number of additions in copywriting creation scenario 250 is 3232, then terminal device 110 will be presented in copywriting creation scenario 250 in the form of "+3232" 254. If the number of additions in English learning scenario 260 is 3232, then terminal device 110 will be presented in English learning scenario 260 in the form of "+3232" 256.

[0075] Terminal device 110 can add a first scene to a scene list associated with the first user based on a trigger operation by the first user on a first scene in at least one scenario. In some embodiments, in response to detecting a trigger operation by the first user on the add control of the first scene, terminal device 110 adds the first scene to a scene list (“My Scenes”) associated with the first user. For example, terminal device 110 can display the added scene in a floating display in the “My Scenes” list. The at least one scene presented by terminal device 110 is configured to perform a task related to the corresponding scene in the interaction between the first user and the digital assistant. For example, when terminal device 110 detects a trigger operation on the access entry of the first scene, it selects the first scene for the interaction between the first user and the first digital assistant. For example, if the first user clicks the add operation 262 corresponding to the copywriting creation scene 250, terminal device 110 adds the first scene to the “My Scenes” list 242 based on the first user's click operation and presents it as a checkmark 252 on the scene recommendation page 240.

[0076] In some embodiments, the terminal device 110 adds the first scene to the scene list associated with the first user, which facilitates the first user's subsequent selection. Adding the first scene to the scene list associated with the first user also facilitates the first user's selection of the first scene for interaction with the first digital assistant. Scenes added to the scene list associated with the first user can be recommended to the user during subsequent interactions with the first digital assistant, presented in scene guidance cards, or selected by the first user for interaction with the first digital assistant whenever needed.

[0077] In some embodiments, public permission type information is used to describe under what conditions at least one scenario can be used by a user. Terminal device 110 determines whether the public permission type for each of the at least one scenario is a specified type. The specified type of public permission can be used to instruct terminal device 110 to allow the corresponding scenario to be provided on the scenario recommendation page 240; the specified type of public permission can also be used to instruct terminal device 110 to allow the corresponding scenario to be shared via a link. Terminal device 110 presents at least one scenario on the scenario recommendation page 240 based on the determined public permission type to be a specified type.

[0078] Terminal device 110 can determine whether the usability scope of at least one scenario includes the first user. When terminal device 110 determines whether the usability scope of at least one scenario includes the first user, terminal device 110 presents at least one scenario on scenario recommendation page 240. At least one of the scenario's public permission type and usability scope can be included in the scenario's configuration information. In other words, when a scenario is created, the scenario's public permission type and usability scope can be indicated in the configuration information.

[0079] In some embodiments, the public permission type may include: a first type indicating that the corresponding scene is allowed to be provided in the scene recommendation page 240 of the users within the scope of access, and a second type indicating that the corresponding scene is allowed to be shared by users within the scope of access via a link. In some embodiments, the public permission of a scene may include both the first and second types, or may include only one of them. In some embodiments, if the public permission type of a scene is a specified type, i.e., the first type indicating that the corresponding scene is allowed to be provided in the scene recommendation page 240 of the users within the scope of access, then the scene may be presented in the scene recommendation page of the users within the scope of access.

[0080] The above describes how created scenes are displayed to users on the scene recommendation page. Below, we will combine this with... Figures 3A to 3C To describe the creation of the scene.

[0081] Figures 3A to 3C A schematic diagram of an example client interface 300 for creating a scenario according to some embodiments of the present disclosure is shown. The client interface 300 can be implemented at a terminal device 110. References are made below. Figure 1 describe Figures 3A to 3C Examples.

[0082] In response to receiving a trigger operation from the first user, the terminal device 110 may, for example, provide... Figure 3A , Figure 3B or Figure 3CThe interface 300 shown includes a page 310 for presenting scenes added by the user. In some embodiments, the interface 300 provided by the terminal device 110 may also include only page 310. Page 310 includes multiple scenes for the user and operation controls 301 for creating scenes. In some embodiments, page 310 may be referred to as a page for presenting a list of scenes. The list of scenes may include, for example, all scenes that the user can select for interacting with the digital assistant.

[0083] Terminal device 110 can respond to detecting the first user's input Figures 3A to 3C The triggering operation of the operation control 301 in the interface 300 shown confirms that a scene creation operation has been received. Alternatively or additionally, in some embodiments, the terminal device 110 may also confirm that a scene creation operation has been received in response to receiving user input indicating scene creation in the session window. In response to receiving a scene creation operation, the terminal device 110 may present a page for creating the target scene. Such a page may be, for example, as shown in... Figure 3B The interface 300 is shown. The terminal device 110 presents a configuration information page for receiving custom scenarios on interface 300. In some embodiments, scenarios can be created by a first user or any other user. Hereinafter, for illustrative purposes only, the creation of a scenario by a first user via terminal device 110 will be described.

[0084] Terminal device 110 can obtain scene creation information for a target scene via a configuration information page. In some embodiments, scene creation information may include basic settings for the target scene. Basic settings include: public permission type information, usability scope information, scene setting information, etc. Scene setting information is used to describe information related to at least one scene. In some embodiments, scene setting information may also include a description of a target type task corresponding to at least one scene, the response style of the digital assistant in at least one scene, a definition of the workflow to be executed in at least one scene, a definition of the response format of the digital assistant in at least one scene, etc.

[0085] In some embodiments, the public permission type of the target scenario to be created can also be configured on the configuration information page. For example... Figure 3B As shown, based on the user checking the selection box 320 before "Terminal device 110 allows the corresponding scenario to be provided in the scenario recommendation page 240 ("Publish as a public scenario")", the public permission of the scenario can be determined to be of the specified type, namely the first type. Based on the user checking the selection box 322 before "Terminal device 110 allows the corresponding scenario to be shared via link", the public permission of the scenario can be determined to be of the second type.

[0086] In one example, the public access permission type for at least one scenario is configured by the corresponding creator. For instance, when an individual user customizes their own scenario, they can specify whether they want to configure the scenario's public access permission as "public scenario," thus ensuring it is displayed on the scenario recommendation page for applicable users.

[0087] In some embodiments, the public permission type for certain scenarios is defaulted to having a specified type. For example, besides references... Figures 3A to 3B In addition to the user-defined scenarios described, some system-configured scenarios (also known as officially configured scenarios) can also be provided. These scenarios may be provided by the digital assistant's operations team, for example. For these scenarios, their public access type can be defaulted to having a specified type, namely "Publish as Public Scenario". These scenarios can always be presented in the scenario recommendation page within their usage scope. In some embodiments, the usage scope of system-configured scenarios may include individual users of the digital assistant.

[0088] In some embodiments, when the terminal device 110 determines that the public access permission of a scene is of the first type (i.e., the specified type) based on the first user's choice to publish a scene as a public scene, it instructs the created scene to appear on the user's scene recommendation page for other users to add and use within the scope of usability. When the terminal device 110 determines that the public access permission of a scene is of the second type based on the first user's choice to share a scene via a link, it instructs the first user to share the scene via a link within the scope of usability, and other users who have the link can also continue to share it with other users. When a user outside the scope of usability clicks the link, the terminal device 110 will display a prompt: "You do not yet have access permission for this scene. You can contact @scene creator to apply."

[0089] like Figure 3B and Figure 3C As shown, based on the first user's trigger operation on the scene recommendation page 240, the terminal device 110 presents an information box 314 on the interface 300. The information box 314 indicates that the terminal device 110 has determined whether the usability scope of at least one scene includes at least the first user. Based on the user clicking the edit control 312 in the information box 314, the terminal device 110 will present an edit page 302 of the usability scope. In the edit page 302, the scene creator can select the usability scope of the created scene, such as specifying one or more users or user groups (e.g., a part of a company, etc.) within the usability scope. After receiving confirmation of the edit of the usability scope, the usability scope of the created scene can be determined.

[0090] For example, when the user selects all members as the usable scope, the user can click the selection box 330 before "All Members," and the terminal device 110 will respond to the user's trigger operation and determine the usable scope of the scene. When the user selects some members of Department B as the usable scope, the user can click the selection box 340 before "Some Members," and then select "Department B" or select members through search. The terminal device 110 will respond to the user's trigger operation and determine the usable scope of the scene. For departments not displayed on the terminal device 110, the user can enter the full name of the department in the input box on the search page 324 for a precise search.

[0091] In some embodiments, the terminal device 110 receives configuration information such as the public permission type information and the scope of use information of at least one scenario from the configuration information (“custom scenario”) page of at least one scenario, and after the first user clicks a touch operation such as creating a control, the terminal device 110 will prompt that the creation was successful.

[0092] In some embodiments, terminal device 110 may respond to and receive a trigger operation on a cancel control, such as a trigger operation on a cancel control in the form of "-", to cancel the creation of a scene, and for at least one scene that has been canceled, terminal device 110 may display a floating display to remove it from the list of scenes ("My Scenes") associated with the first user, i.e., not display it in the "My Scenes" list.

[0093] In some embodiments, when a first scenario for interaction between the first user and the digital assistant is selected, the terminal device 110 will end the previous topic and create a new topic in the interaction window between the first user and the first digital assistant, which is associated with the first scenario.

[0094] In some embodiments, the terminal device 110 provides a resource acquisition instruction for the first scenario based on the user's triggering of the first scenario. The terminal device 110 adds the first scenario to the list of scenarios ("My Scenarios") associated with the first user based on the user's pre-required resource amount for adding the first resource. For example, the terminal device 110 sorts the scenarios from highest to lowest based on the number of scenarios added, and displays the scenario with the most added scenarios at the top.

[0095] According to some embodiments of this disclosure, at least one scenario recommended by the user is presented on the scenario recommendation page upon user triggering. Through the scenario recommendation page, users can add one or more scenarios to their scenario list for later selection, or select a scenario for interaction with the digital assistant. Therefore, in this way, the digital assistant can meet and facilitate users' needs for information interaction through the scenario recommendation page in their respective scenarios.

[0096] Upon scenario publishing, in response to the operation of publishing the first scenario, the first publishing information of the first scenario is obtained. Based on the first publishing information, the first scenario is published to the target digital assistant, allowing the target digital assistant to perform related tasks based on the first scenario. According to this scheme, when a user creates a scenario for a specific digital assistant, the created scenario can be published to that specific digital assistant for use. For example, in Figure 3A In the example, if a user of "XX Assistant" creates and publishes a first scenario for XX Assistant, then the published first scenario can be provided to "XX Assistant" to perform related tasks.

[0097] In some embodiments, when creating the first scenario, the scenario creator can specify the publishing method of the first scenario, including sharing via link, public publishing, or both. Different publishing methods correspond to different public permission types for the first scenario. For example... Figure 3B As shown, based on the user checking the selection box 320 before "Terminal device 110 allows the corresponding scene to be provided in the scene recommendation page 240 ("Publish as a public scene")", the public permission of the scene is determined to be of the specified type, namely the first type, and its corresponding publishing method is public publishing. Based on the user checking the selection box 322 before "Terminal device 110 allows the corresponding scene to be shared via link", the public permission of the scene is determined to be of the second type, and its corresponding publishing method is sharing via link. If the creator checks both types simultaneously, the published first scene can be published either via link sharing or publicly published, that is, presented in the scene recommendation page of users within the usable scope.

[0098] In some embodiments, the first release information for the first scenario may further include an availability scope to indicate the range of users who can use the first scenario. Thus, users within the specified availability scope can use the first scenario to interact with their respective digital assistants.

[0099] In some embodiments, the target digital assistants published in the first scenario may include one or more digital assistants corresponding to each user. For example, a first user may have their own first digital assistant, and a second user may have their own second digital assistant, because the digital assistants of different users are configured with their respective user permissions, historical interaction information, and other instructions. However, the digital assistants of different users can be understood as running instances of the same digital assistant application on different users' terminal devices. When the first scenario is published, one or more users who can use the first scenario are included in the scope of use of the first scenario.

[0100] According to embodiments of this disclosure, the interaction between a digital assistant and its user can be enriched by creating diverse scenarios for a specific digital assistant. As mentioned above, the scenario configuration information may include scenario setting information, plugin information, etc. By setting different configuration information for different scenarios, the digital assistant can exhibit different interactive capabilities when performing interactions based on the corresponding scenarios, helping users complete different tasks.

[0101] It should be understood that some embodiments of this disclosure have been described above with reference to specific examples in the accompanying drawings, but these specific examples are not intended to limit the scope of the embodiments of this disclosure. The described embodiments can also be implemented in various other variations.

[0102] Figure 4A A flowchart of an information interaction process 400 according to some embodiments of the present disclosure is shown. Process 400 can be implemented at terminal device 110. Reference is made below. Figure 1 Describe the process 400.

[0103] In box 410, in response to detecting a first user's trigger operation on the scene recommendation page, the terminal device 110 presents at least one scene on the scene recommendation page.

[0104] In box 420, terminal device 110 adds the first scene to the scene list associated with the first user for subsequent selection based on the first user's trigger operation on the first scene in at least one scene, or selects the first scene for the interaction between the first user and the first digital assistant, wherein at least one scene is configured to perform a task related to the corresponding scene in the interaction between the first user and the first digital assistant.

[0105] In some embodiments, presenting at least one scenario on the scenario recommendation page includes: determining whether the public permission type of each of the at least one scenario is a specified type, wherein the public permission of the specified type allows the corresponding scenario to be provided on the scenario recommendation page; and presenting at least one scenario on the scenario recommendation page based at least on determining that the public permission type of the at least one scenario is a specified type.

[0106] In some embodiments, presenting at least one scenario on a scenario recommendation page includes: determining whether the usability of each of the at least one scenario includes at least a first user; and further presenting at least one scenario on the scenario recommendation page based on determining whether the usability of each of the at least one scenario includes at least a first user.

[0107] In some embodiments, a public permission indication of a specified type allows the corresponding scenario to be provided in the scenario recommendation page of users within the scope of access.

[0108] In some embodiments, at least one scenario is configured with configuration information, which indicates at least one of the public permission type and the scope of use for each scenario.

[0109] In some embodiments, presenting at least one scenario on the scenario recommendation page includes presenting at least one of the following on the recommended scenario page: a scenario description for each of the at least one scenario, an access point for each of the at least one scenario, an add control for each of the at least one scenario, a creation source for each of the at least one scenario, and an addition quantity for each of the at least one scenario.

[0110] In some embodiments, adding a first scene to a scene list associated with a first user includes: adding the first scene to the scene list associated with the first user in response to detecting a triggering operation of an add control for the first scene.

[0111] In some embodiments, selecting a first scenario for interaction between a first user and a first digital assistant includes: in response to detecting a trigger operation of an access point to the first scenario, selecting a first scenario for interaction between the first user and the first digital assistant.

[0112] In some embodiments, process 400 further includes: in response to a first scenario being selected for interaction between a first user and a first digital assistant, creating a new topic based on the first scenario in the interaction window between the first user and the first digital assistant.

[0113] In some embodiments, adding a first scenario to a scenario list associated with a first user includes: providing a resource acquisition instruction for the first scenario based on a triggering operation on the first scenario; and adding the first scenario to the scenario list associated with the first user in response to receiving a predetermined amount of resources required for adding the first resource.

[0114] In some embodiments, the public permission type of one or more scenarios in at least one scenario is configured by the corresponding creator, and / or the public permission type of one or more scenarios in at least one scenario is defaulted to having a specified type.

[0115] In some embodiments, at least one scenario is configured with configuration information, which indicates at least one of the following: scenario setting information, which describes information related to the corresponding scenario; plugin information, which indicates at least one plugin used to perform tasks in the corresponding scenario; indication of the selected model, which is invoked to determine the response to the user in the corresponding scenario; scenario guidance information, which is presented to the user after the corresponding scenario is selected; and at least one recommended question for the digital assistant, which is presented to the user for selection after the corresponding scenario is selected.

[0116] Figure 4B A flowchart of an information interaction process 402 according to some embodiments of the present disclosure is shown. Process 400 can be implemented at terminal device 110. Reference is made below. Figure 1 Describe process 402.

[0117] In box 430, terminal device 110 responds to the operation of publishing the first scenario by obtaining the first publishing information of the first scenario. The first scenario is configured with corresponding configuration information to perform a corresponding type of task. The configuration information includes at least one of the following: scenario setting information and plugin information, wherein the scenario setting information is used to describe information related to the corresponding scenario, and the plugin information indicates at least one plugin used to perform the task in the corresponding scenario.

[0118] In box 440, terminal device 110 publishes the first scenario to the target digital assistant based on the first publishing information, so that the target digital assistant can perform related tasks based on the first scenario.

[0119] In some embodiments, the first published information includes a publishing method, which includes at least one of the following: sharing via a link; and public publishing.

[0120] In some embodiments, the first release information includes the scope of use, which indicates the range of users who can use the first scenario.

[0121] In some embodiments, the target digital assistant includes one or more digital assistants corresponding to each user. In some embodiments, the one or more users are determined by the scope of use of the first scenario.

[0122] Figure 5A A block diagram of an apparatus 500 for information interaction according to some embodiments of the present disclosure is shown. The apparatus 500 may be implemented in or included in a terminal device 110, for example. Various modules / components in the apparatus 500 may be implemented by hardware, software, firmware, or any combination thereof.

[0123] As shown in the figure, the device 500 includes a detection module 510, which is configured to present at least one scene in the scene recommendation page in response to detecting a trigger operation by a first user on the scene recommendation page.

[0124] The device 500 also includes an adding module 520, configured to add the first scene to a scene list associated with the first user for subsequent selection based on a triggering operation by the first user on a first scene in at least one scenario, or to select the first scene for interaction between the first user and the first digital assistant. At least one scenario is configured to perform a task related to the corresponding scenario during the interaction between the first user and the first digital assistant.

[0125] In some embodiments, presenting at least one scenario on the scenario recommendation page includes: determining whether the public permission type of each of the at least one scenario is a specified type, wherein the public permission of the specified type allows the corresponding scenario to be provided on the scenario recommendation page; and presenting at least one scenario on the scenario recommendation page based at least on determining that the public permission type of the at least one scenario is a specified type.

[0126] In some embodiments, presenting at least one scenario on a scenario recommendation page includes: determining whether the usability of each of the at least one scenario includes at least a first user; and further presenting at least one scenario on the scenario recommendation page based on determining whether the usability of each of the at least one scenario includes at least a first user.

[0127] In some embodiments, a public permission indication of a specified type allows the corresponding scenario to be provided in the scenario recommendation page of users within the scope of access.

[0128] In some embodiments, at least one scenario is configured with configuration information, which indicates at least one of the public permission type and the scope of use for each scenario.

[0129] In some embodiments, presenting at least one scenario on the scenario recommendation page includes presenting at least one of the following on the recommended scenario page: a scenario description for each of the at least one scenario, an access point for each of the at least one scenario, an add control for each of the at least one scenario, a creation source for each of the at least one scenario, and an addition quantity for each of the at least one scenario.

[0130] In some embodiments, adding a first scene to a scene list associated with a first user includes: adding the first scene to the scene list associated with the first user in response to detecting a triggering operation of an add control for the first scene.

[0131] In some embodiments, selecting a first scenario for interaction between a first user and a first digital assistant includes: in response to detecting a trigger operation of an access point to the first scenario, selecting a first scenario for interaction between the first user and the first digital assistant.

[0132] In some embodiments, the adding module 520 further includes: in response to the first scene being selected for the interaction between the first user and the first digital assistant, creating a new topic based on the first scene in the interaction window between the first user and the first digital assistant.

[0133] In some embodiments, adding a first scenario to a scenario list associated with a first user includes: providing a resource acquisition instruction for the first scenario based on a triggering operation on the first scenario; and adding the first scenario to the scenario list associated with the first user in response to receiving a predetermined amount of resources required for adding the first resource.

[0134] In some embodiments, the public permission type of one or more scenarios in at least one scenario is configured by the corresponding creator, and / or the public permission type of one or more scenarios in at least one scenario is defaulted to having a specified type.

[0135] In some embodiments, at least one scenario is configured with configuration information, which indicates at least one of the following: scenario setting information, which describes information related to the corresponding scenario; plugin information, which indicates at least one plugin used to perform tasks in the corresponding scenario; indication of the selected model, which is invoked to determine the response to the user in the corresponding scenario; scenario guidance information, which is presented to the user after the corresponding scenario is selected; and at least one recommended question for the digital assistant, which is presented to the user for selection after the corresponding scenario is selected.

[0136] Figure 5B A block diagram of an apparatus 502 for information interaction according to some embodiments of the present disclosure is shown. Apparatus 500 may be implemented in or included in terminal device 110, for example. Various modules / components in apparatus 502 may be implemented by hardware, software, firmware, or any combination thereof.

[0137] In some embodiments, the device 502 includes a publishing information acquisition module 530, configured to acquire first publishing information of the first scenario in response to an operation of publishing the first scenario; wherein the first scenario is configured with corresponding configuration information to perform a corresponding type of task, and the configuration information includes at least one of the following: scenario setting information and plugin information, wherein the scenario setting information is used to describe information related to the corresponding scenario, and the plugin information indicates at least one plugin used to perform the task in the corresponding scenario. In some embodiments, the device 502 further includes a scenario publishing module 540, configured to publish the first scenario to a target digital assistant based on the first publishing information, so that the target digital assistant can perform related tasks based on the first scenario.

[0138] In some embodiments, the first published information includes a publishing method, which includes at least one of the following: sharing via a link; and public publishing.

[0139] In some embodiments, the first release information includes the scope of use, which indicates the range of users who can use the first scenario.

[0140] In some embodiments, the target digital assistant includes one or more digital assistants corresponding to each user. In some embodiments, the one or more users are determined by the scope of use of the first scenario.

[0141] Figure 6 A block diagram of an electronic device 600 in which one or more embodiments of the present disclosure may be implemented is shown. It should be understood that... Figure 6 The electronic device 600 shown is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. Figure 6 The electronic device 600 shown can be used to achieve Figure 1 Terminal equipment 110, Figure 5A The device 500 and / or shown Figure 5B The device 502 shown.

[0142] like Figure 6 As shown, electronic device 600 is in the form of a general-purpose electronic device. Components of electronic device 600 may include, but are not limited to, one or more processors or processing units 610, memory 620, storage device 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. Processing unit 610 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 620. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 600.

[0143] Electronic device 600 typically includes multiple computer storage media. Such media can be any available media accessible to electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 620 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 630 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media capable of storing information and / or data and accessible within electronic device 600.

[0144] Electronic device 600 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 6 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 620 may include computer program product 625 having one or more program modules configured to perform various methods or actions of various embodiments of this disclosure.

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

[0146] Input device 650 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 660 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 600 can also communicate with one or more external devices (not shown) via communication unit 640 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 600, or with any device that enables electronic device 600 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0147] According to an exemplary implementation of this disclosure, 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. According to an exemplary implementation of this disclosure, 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.

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

[0149] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit 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.

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

[0151] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, 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 indicated in the blocks may occur in a different order than those indicated in the drawings. 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, may 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.

[0152] Various implementations of this disclosure have been described above. These 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 information exchange, comprising: In response to detecting a trigger operation by a first user on a scene recommendation page, at least one scene is presented on the scene recommendation page, wherein the scene in the at least one scene indicates multiple tasks of a corresponding type, the at least one scene has associated configuration information, and each scene is configured to perform a task related to the corresponding scene based on the corresponding configuration information during the interaction between the first user and the first digital assistant. Based on the first user's triggering operation on a first scenario in the at least one scenario, the first scenario is added to a list of scenarios associated with the first user for subsequent selection, or the first scenario is selected for the interaction between the first user and the first digital assistant to create a topic associated with the first scenario; and In response to the first scenario being selected for interaction with the first digital assistant, a response message to the interaction message from the first user is determined based on the configuration information associated with the first scenario.

2. The method according to claim 1, wherein presenting at least one scene on the scene recommendation page includes: Determine whether the public permission type of each of the at least one scenario is a specified type, wherein the public permission of the specified type allows the corresponding scenario to be provided on the scenario recommendation page; as well as Based at least on the determination that the public permission type of the at least one scenario is the specified type, the at least one scenario is presented on the scenario recommendation page.

3. The method according to claim 1, wherein presenting at least one scene on the scene recommendation page includes: Determine whether the usability of each of the at least one scenario includes at least the first user; as well as Furthermore, based on determining whether the usability of each of the at least one scenario includes at least the first user, the at least one scenario is presented on the scenario recommendation page.

4. The method according to claim 2, wherein the specified type of public permission indication allows the corresponding scenario to be provided in the scenario recommendation page of the user with available access.

5. The method according to claim 2 or 3, wherein the at least one scenario is configured with configuration information, the configuration information indicating at least one of the public permission type and the scope of use for each corresponding scenario.

6. The method according to claim 1, wherein presenting the at least one scene on the scene recommendation page comprises: The scene recommendation page will display at least one of the following: The scene descriptions for each of the at least one scene. The access point for each of the at least one scenario. Add controls to each of the at least one scenario. The creation source of each of the at least one scenario The amount of each of the at least one scenario added.

7. The method of claim 6, wherein adding the first scenario to the scenario list associated with the first user comprises: In response to detecting a trigger operation for adding a control to the first scene, the first scene is added to the scene list associated with the first user.

8. The method of claim 6, wherein selecting the first scenario for the interaction between the first user and the first digital assistant comprises: In response to the detection of a trigger operation for accessing the first scenario, the first scenario is selected for the interaction between the first user and the first digital assistant.

9. The method of claim 1, wherein adding the first scenario to the scenario list associated with the first user comprises: Based on the triggering operation of the first scenario, provide resource acquisition instructions for the first scenario; as well as In response to receiving the predetermined amount of resources required to add the first scenario, the first scenario is added to the scenario list associated with the first user.

10. The method of claim 1, wherein the public permission type of one or more scenarios in the at least one scenario is configured by the corresponding creator, and / or In the case of one or more scenarios in the aforementioned at least one scenario, the public permission type of each scenario is assumed to have a specified type.

11. The method of claim 1, wherein the at least one scenario is configured with configuration information, the configuration information indicating at least one of the following: Scene setting information, which describes information related to the corresponding scene; Plug-in information, which indicates at least one plug-in used to perform the task in the corresponding scenario; The selected model is invoked to determine the response to the user in the corresponding scenario; Scene guidance information is presented to the user after the corresponding scene is selected. In response to at least one recommended question from the digital assistant, the at least one recommended question is presented to the user for selection after the corresponding scenario is selected.

12. A method for information exchange, comprising: In response to the operation of publishing a first scenario, first publishing information of the first scenario is obtained; wherein, at least one scenario indicates multiple tasks of a corresponding type, the first scenario is configured with corresponding configuration information for executing tasks of the corresponding type, and the configuration information includes at least one of the following: scenario setting information, plugin information, wherein the scenario setting information is used to describe information related to the corresponding scenario, and the plugin information indicates at least one plugin used to execute tasks in the corresponding scenario; and Based on the first release information, the first scenario is released to the target digital assistant so that the target digital assistant can execute tasks related to the first scenario based on the configuration information of the first scenario.

13. The method according to claim 12, wherein, The first published information includes a publishing method, which includes at least one of the following: Share via link; Public release method.

14. The method according to claim 12, wherein, The first release information includes the scope of use. The scope of use indicates the range of users who can use the first scenario.

15. The method according to claim 12, wherein, The target digital assistant includes one or more digital assistants corresponding to each user; The one or more users are determined by the scope of use of the first scenario.

16. An apparatus for information interaction, comprising: The detection module is configured to, in response to detecting a trigger operation by a first user on a scene recommendation page, present at least one scene on the scene recommendation page, wherein the scene in the at least one scene indicates multiple tasks of a corresponding type, the at least one scene has associated configuration information, and each scene is configured to perform a task related to the corresponding scene based on the corresponding configuration information during the interaction between the first user and the first digital assistant. The add module is configured to, based on a triggering operation by the first user on a first scenario in the at least one scenario, add the first scenario to a list of scenarios associated with the first user for subsequent selection, or select the first scenario for interaction between the first user and the first digital assistant to create a topic associated with the first scenario; and The adding module is also configured to, in response to the first scenario being selected for interaction with the first digital assistant, determine a response message to the interaction message from the first user based on configuration information associated with the first scenario.

17. An apparatus for information interaction, comprising: The information acquisition module is configured to acquire first release information of the first scenario in response to an operation of publishing the first scenario; wherein, at least one scenario indicates multiple tasks of a corresponding type, the first scenario is configured with corresponding configuration information for executing tasks of the corresponding type, and the configuration information includes at least one of the following: scenario setting information and plugin information, wherein the scenario setting information is used to describe information related to the corresponding scenario, and the plugin information indicates at least one plugin used to execute tasks in the corresponding scenario; and The scene publishing module is configured to publish the first scene to the target digital assistant based on the first publishing information, so that the target digital assistant can execute tasks related to the first scene based on the configuration information of the first scene.

18. An electronic device comprising: At least one processing unit; as well as At least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 11, and / or the method according to any one of claims 12 to 15 when executed by the at least one processing unit.

19. A computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the method according to any one of claims 1 to 11, and / or the method according to any one of claims 12 to 15.

Images