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

Abstract

Methods, apparatuses, devices, media, and program products for interface interaction are provided. The method includes presenting a first interface, the first interface being for interacting with a smart system, the first interface including a first component, the first component being associated with a first application, the first application including at least one functional unit, the at least one functional unit being invocable by the smart system; and in response to a triggering operation on the first component, presenting a first region for presenting first interface content of the first application.

Description

Technical Field

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

[0002] As the types of functional units that intelligent systems can call and the number of applications associated with intelligent systems increase, how to provide corresponding components and interface content for different applications in the interactive interface of intelligent systems has become a difficult problem to be solved in the interface interaction process. Summary of the Invention

[0003] In a first aspect of this document, a method for interface interaction is provided. The method includes: presenting a first interface for interacting with an intelligent system, the first interface including a first component associated with a first application, the first application including at least one functional unit capable of being invoked by the intelligent system; and, in response to a triggering operation on the first component, presenting a first area for displaying the first interface content of the first application.

[0004] In a second aspect of this document, an apparatus for interface interaction is provided. The apparatus includes a first presentation module and a second presentation module. The first presentation module is configured to present a first interface for interacting with an intelligent system. The first interface includes a first component associated with a first application, the first application including at least one functional unit capable of being invoked by the intelligent system. The second presentation module is configured to present a first area in response to a triggering operation on the first component. The first area is used to display the content of the first interface of the first application.

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

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

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

[0008] In this way, the interactive interface of the intelligent system can present the area carrying the application's interface content through a first component associated with the invoked application, and organize the interface content and the functional units that the intelligent system can invoke through the same application relationship. Furthermore, electronic devices can reduce the number of times additional pages need to be loaded to locate application interface content, and reduce the rendering overhead and communication data volume caused by interface switching.

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

[0010] The above and other features, advantages, and aspects of the various examples herein will become more apparent when taken in conjunction with the accompanying drawings and the following detailed description. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein: Figure 1 A schematic diagram of an example environment in which multiple examples can be implemented is shown; Figures 2A to 2C The diagram shows some possible interface scenarios; Figure 2D A schematic diagram illustrating the relationships between the intelligent system and multiple applications is shown. Figure 2E The diagram shows some possible interface scenarios; Figures 3A to 3B Schematic diagrams of interfaces for other scenarios are shown; Figure 4 The diagram shows some scenarios of the application creation interface; Figure 5 Flowcharts are shown for methods used in interface interaction in some scenarios; Figure 6 Block diagrams of devices for interface interaction in several scenarios are shown; and Figure 7 A block diagram is shown of an electronic device capable of implementing one or more examples. Detailed Implementation

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

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

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

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

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

[0016] In one context, an intelligent system is an information processing system. This intelligent system uses at least one or more models to process one or more inputs. The intelligent system may include the one or more models as components, or it may use models external to the system for processing. Those skilled in the art will recognize that there are various implementations of intelligent systems in the industry, including but not limited to agents, artificial intelligence (AI) assistants, AI workers, copilot systems, and chatbots. The inputs include data in one or more modalities. The modal data includes, but is not limited to, text, audio, images, video, application-specific data, or scientific computing data. The models include, but are not limited to, one or more combinations of the following: large-scale parametric models, deep learning models, neural network models, machine learning models, statistical models, rule-based models, or other models capable of processing the inputs. The specific implementation of the models can employ various existing or improved models. The intelligent system may involve one or more of the following operations: receiving single-round or multi-round input; recognizing and / or understanding the input; generating answers, decisions, or processing results using one or more models; invoking one or more external tools, interfaces, knowledge bases, or other systems to obtain information or perform operations; processing in a self-decision-making or human-machine collaborative manner, or transferring tasks to human or other systems for processing. Self-decision-making refers to execution without human intervention. Human-machine collaboration refers to partial human participation or confirmation. The above explanation of "intelligent system" is illustrative, and each description is an example, not necessarily necessary, and does not constitute an exhaustive list.

[0017] As mentioned above, with the continuous increase in functional units available for intelligent systems to invoke, various plugins or applications can be pre-configured to support these invocations. However, the invocation process and results of these plugins or applications are usually invisible to the user. The intelligent system ultimately aggregates the invocation results and provides the response in its interactive interface. In other words, plugins or applications invoked by the intelligent system typically cannot provide a personalized interface to display their content.

[0018] To address this, a scheme for interface interaction is proposed. According to this scheme, electronic device 110 presents a first interface for interacting with intelligent system 120, in which a first component associated with a first application is displayed. The first application includes at least one functional unit that can be invoked by intelligent system 120. In response to user 140 triggering the first component, electronic device 110 presents a first area and displays the first interface content of the first application in the first area.

[0019] Through the above solution, for applications that use intelligent system calls to execute tasks, a corresponding first component can be provided for viewing the application's interface content. Furthermore, the application's first component, interface content, and callable functional units are organized within the same application relationship, thus solving the difficulty of locating the corresponding interface content within the interactive context due to the dispersed nature of interface components and processing capabilities.

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

[0021] Figure 1 A schematic diagram of an example environment 100 is shown, in which multiple examples can be implemented. For example... Figure 1 As shown, the example environment 100 may include an electronic device 110, an intelligent system 120, a server 130, a user 140, and an interface 150.

[0022] In example environment 100, intelligent system 120 may at least partially operate on electronic device 110. Alternatively or additionally, some processing power of intelligent system 120 may be provided by server 130. Electronic device 110 may present interface 150 by running intelligent system 120 or by accessing intelligent system services provided by server 130.

[0023] User 140 can interact with smart system 120 via electronic device 110 and / or its attached devices. Electronic device 110 can receive input from user 140 through interface 150 and present interactive content of smart system 120, first components associated with the application, and interface content of the application through interface 150.

[0024] The electronic device 110 and the server 130 can transmit application declaration information, interface resources, function unit call requests, and function unit call results. The server 130 can determine the application runtime instance corresponding to the request based on the declaration information and route the request to that runtime instance. The server 130 can also return interface resources or processing results to the electronic device 110. A "running instance" refers to an execution entity formed during application runtime for handling interface content loading requests or function unit call requests. The same application can have one or more running instances.

[0025] Electronic device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, handheld computers, portable gaming terminals, virtual reality (VR) / augmented reality (AR) devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some cases, electronic device 110 may also support any type of user-facing interface (such as "wearable" circuitry).

[0026] Server 130 can be a single physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and artificial intelligence platforms. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for the intelligent system 120 in electronic device 110 and applications associated with the intelligent system 120.

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

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

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

[0030] The examples described herein can be implemented at electronic device 110. It should be noted that the operations described relative to electronic device 110 can be performed by intelligent system 120 or related applications running on electronic device 110. The interface described relative to electronic device 110 can be provided by intelligent system 120 or related applications; for example, electronic device 110 presents the corresponding interface by running intelligent system 120. Furthermore, some operations described relative to electronic device 110 may require the assistance of server 130 to complete.

[0031] As used herein, the term "application" refers to a set of functional units capable of providing at least one callable functional unit and / or interface content to the intelligent system 120. An application may be implemented from one or more of application packages, declaration information, interface resources, program resources, configuration data, and runtime instances. In some cases, such applications may also be plug-ins, extensions, etc. "Interface" refers to a graphical interface capable of facilitating interaction between the user and the intelligent system. A first interface may include a session interface, task interface, work interface, application management interface, or a combination of the foregoing.

[0032] Assume that the intelligent system 120 is associated with a first application. "Association" can mean that the first application is installed on the intelligent system 120 and can be invoked by the intelligent system 120 to execute corresponding tasks. The following will use the first application as an example to explain the "application" in detail.

[0033] In some cases, the first application can be described by both an application package and declaration information. The application package can encapsulate interface resources used to provide the content of the first interface and program resources used to implement at least one functional unit. The declaration information can describe one or more of the following: the name, version, first component, functional unit type, location of interface resources, service address, permission requirements, activation events, and configuration items of the first application.

[0034] Server 130 can provide application registration service, application routing service, runtime environment, configuration storage service, and permission proxy service. The application registration service can perform format validation on application packages and declaration information and save version information. The application routing service can route UI content loading requests and function unit call requests to the corresponding runtime instances based on the declaration information. The runtime environment can provide isolated execution spaces for different applications and can monitor the resource consumption, processing time, and running status of runtime instances.

[0035] In one deployment method, a running instance of the first application can be executed independently on electronic device 110. Electronic device 110 loads interface resources based on declaration information and processes at least one functional unit of the first application locally. In another deployment method, a running instance of the first application can be executed independently on server 130. Electronic device 110 sends an interface content loading request or a functional unit call request to server 130 and presents the interface resources or processing results returned by server 130. In yet another deployment method, electronic device 110 and server 130 can jointly execute the first application. Electronic device 110 is responsible for interface presentation and some input processing, while server 130 is responsible for functional unit processing and runtime status maintenance, etc. The two exchange requests and results through a communication connection.

[0036] The first application can undergo state changes including registration, association, activation, execution, pause, version switching, deactivation, and unassociation. Registration makes the first application an associatable application object. Association establishes a callable relationship between the first application and the intelligent system 120. Activation loads the first application into the runtime environment. Pausing temporarily stops the first application from processing new requests while retaining configuration data. Version switching routes new requests to a new running instance, while allowing currently running tasks to continue to be processed by the original running instance.

[0037] In some cases, a first application may include one or more functional units for performing corresponding tasks. The term "functional unit" as used herein refers to a processing capability that can be triggered by an intelligent system or user and produce processing results. Specific functional units can be configured by the application's creator. In some examples, when interfacing with the intelligent system 120, a unified encapsulation of application capabilities can be provided. For example, multiple capability types can be provided for configuration into the application to be created. Capability types may include service functional units, command functional units, event interception functional units, specialized skills, or other functional unit types that can be provided by the application. Service functional units can be used to perform data processing, data access, or interface processing. Command functional units can be used to respond to commands received from the input area of ​​the first interface. Event interception functional units are functional units that perform additional processing before or after a target operation in response to a preset event; this additional processing may include parameter validation, information transformation, confirmation request generation, result processing, or other controlled processing. Specialized skills can be selected by the intelligent system 120 based on the task content and used to perform processing corresponding to the task type. Specialized skills can be implemented through rule processing, model processing, tool invocation, or a combination thereof.

[0038] In some scenarios, the intelligent system 120 can provide an application management interface that displays a list of associated applications, application categories, application descriptions, version information, and status indicators. The application management interface can also provide search, category filtering, and sorting functions. Searches can determine matching results based on one or more of the following: application name, application description, and application tags. Sorting can be based on the number of associated applications, publication time, or most recent usage time.

[0039] During interaction with the intelligent system 120, a first component associated with the first application can be provided for accessing the interface content of the first application. In this way, the first application can not only be invoked by the intelligent system 120 to execute tasks, but also provide corresponding interface content for the user to view. In some cases, the interface content can be associated with specific functional units of the first application to display the execution status or results of the functional units in response to the invoked tasks. Alternatively or additionally, the interface content can display the overall status of the first application. In some cases, multiple components can be provided for accessing different interface contents of the first application.

[0040] As used herein, the term "first component" refers to an interface component associated with a first application and capable of locating, loading, or presenting the interface content of the first application in response to a triggering action. A first component may serve as an entry point to the first application and may include icons, buttons, cards, menu items, shortcut commands, text links, or other interactive components. A "triggering action" refers to a user action or input event that causes an interface component to enter a corresponding processing flow. Triggering actions may include clicks, touches, presses, focus selection, gesture input, voice input, command input, or other actions that activate the interface component.

[0041] In some situations, the interface content of the first application displayed can take multiple presentation forms. For example, for content with limited information, the interface content can be presented as a conversation flow card. For content requiring continuous operation, the interface content can be presented in a side area or full-screen area. For content requiring confirmation, the interface content can be presented in a confirmation panel. The interface content can also be presented in a new tab or embedded in the interface.

[0042] The following section will discuss, with examples, the triggering of different first components of the application and the corresponding UI content. "UI content" refers to the visual content provided by the application. In some cases, UI content may be associated with at least one functional unit of the application. UI content may include a homepage, task details, processing results, action components, status information, or UI elements for receiving input.

[0043] Figure 2AA schematic diagram of a first interface 200A is shown according to some scenarios. The first interface 200A may include a first region 220 and a second region 210.

[0044] like Figure 2A As shown, the second area 210 can be used for user 140 to interact with the intelligent system 120. In some cases, the first interface 200A may include an input area 212 and multiple application-related first components, including first component 201, first component 202, first component 203, and first component 204. The input area 212 can receive user input to the intelligent system 120. First components 201 and 202 may be located at the top of the second area 210 and the side area of ​​the first interface 200A, respectively. First component 203 may be associated with first interactive content 205 provided by the intelligent system 120. First component 204 may be associated with the input area 212. It should be understood that... Figures 2A to 2E The positions of the multiple first components shown are merely examples. In other cases, the first components may be located in locations other than those shown in the figures, and the number of positions in the first interface used to present the first components may be more or less than those shown in the figures.

[0045] In some cases, the first component can be used as an entry point associated with the homepage of the first application, or it can be used as a general entry point for accessing the first application. Figures 2A to 2C as well as Figure 2E The first component 201 and the first component 202 can each correspond to examples of different presentation positions or presentation forms of the first component of this type.

[0046] In other cases, the first component may be associated with the first interactive content provided by the intelligent system. Figures 2A to 2C as well as Figure 2E The first component 203 and the first component 206 can each correspond to examples of different presentation positions or presentation forms of this type of first component. This type of first component can be located in the session flow, task flow, or intelligent system output content, and locate the first interface content to the task information associated with the first interactive content.

[0047] In other cases, the first component may be associated with an input area of ​​the first interface. The first component may be used to receive commands associated with the first application and to display interface content corresponding to those commands in the first area. Figures 2A to 2C as well as Figure 2E The first component 204 in the text can correspond to an example of the presentation position or presentation form of the first component of that class.

[0048] In response to a trigger operation on any of the first components, the electronic device 110 can display the first interface content of a first application in the first area 220. The first area 220 has a first positional relationship with a second area 210 for interacting with the intelligent system. Figure 2A In the example, the first region 220 is separate from the second region 210. In some cases, the first region 220 may be hidden when no first component is triggered. After the first component is triggered, the first interface content of the first application is displayed in the first region 220.

[0049] In some cases, in response to a trigger operation on the first component 201 or the first component 202, the electronic device 110 can determine the first application associated with the first component and display the homepage of the first application in the first area 220. At this time, the displayed first interface content includes the homepage of the first application. In some cases, in response to a trigger operation on the first component 201 or the first component 202, the electronic device 110 can obtain the declaration information of the first application and determine the interface resources of the first application based on the declaration information. The first component 201 and the first component 202 can correspond to different presentation forms of the first component. The first component 201 can be used as an entry point to directly open the first application. The first component 202 can be used as a general entry point to present multiple associated applications. In response to the user 140 selecting the first application from multiple applications via the first component 202, the electronic device 110 can determine this selection as a trigger operation on the first component associated with the first application.

[0050] In some cases, the first component 203 and / or the first component 206 of the first application may be associated with the first interactive content 205 provided by the intelligent system 120. "First interactive content" refers to response content provided by the intelligent system in the first interface, which may be, for example, provided in response to a user request. The first interactive content may also be referred to as an interactive message, a message, or a dialogue, etc. The first interactive content 205 may be associated with a first task. The intelligent system 120 may invoke a first functional unit in at least one functional unit of the first application to perform the first task. For example, the first interactive content may include intermediate task events, task results, subtask information, prompt cards, or other content associated with the interaction context. In some examples, the first component 203 of the first application may be located in separate interactive content, such as in interactive content adjacent to the first interactive content 205. In some examples, the first component 206 of the first application may be provided as part of the first interactive content 205.

[0051] In response to a trigger operation on the first component 203 or the first component 206, the electronic device 110 can determine the first application associated with the first component, and further determine that the first component specifically corresponds to a specific page in the first application, and present the specific page of the first application in the first area 220, the interface content of which is associated with the first interactive content 205. In some cases, the electronic device 110 can obtain the task identifier of the first task from the first interactive content 205, and provide the task identifier and the identifier of the first application together to the application routing service. The application routing service can route the interface content loading request to the running instance of the first application based on the two identifiers. The first interface content presented in the first area 220 may include the task information of the first task. That is, starting from the first component corresponding to the first interactive content, the specific task information related to the first task in the first application can be directly located and presented. The task information may include, but is not limited to, one or more of the following: the identifier of the first task, input, processing status, processing result, or related interface data.

[0052] In some cases, the first component 204 may be associated with the input area 212 of the first interface and may receive commands associated with the first application. A "command" refers to input used to specify an application functional unit, processing action, or processing parameter. A command may include one or more of the following: command name, parameters, target application identifier, and context information. In response to user 140 selecting or entering the command in the input area 212, electronic device 110 can determine the corresponding page based on the mapping relationship between the command and interface content, and present the first interface content corresponding to the command in the first area 220. The command may also carry parameters, which the running instance can use to determine the range of data or processing status to be presented.

[0053] Through the above solution, the first interface 200A can provide multiple first components of the first application within the same interactive context, and enable different first components to locate the content corresponding to the homepage, task information, or command. This solves the difficulties of insufficient interface component forms and the need to search for target content across multiple pages in related solutions. The electronic device 110 can directly generate interface content loading requests based on the context information carried by the first components, reducing the loading of irrelevant pages. As a result, the number of page renderings on the client, cache usage, and the number of page requests sent to the server 130 can all be reduced.

[0054] Figure 2B A schematic diagram of a first interface 200B is shown according to some scenarios. The first interface 200B may include a second region 210 and a first region 220. Figure 2B Another positional relationship between the first region and the second region is shown, wherein the first region 220 may be included within the second region 210.

[0055] exist Figure 2B In the example, in response to a trigger on a first component associated with the first application, the first interface content of the first application can be presented in the second area 210 as part of the interactive content of the smart system 120. For example, the first area 220 can take the form of a session flow card or an embedded panel. The electronic device 110 can receive operations on the components in the first area 220 without leaving the first interface 200B and provide the operation data to the running instance of the first application. In some cases, the first area 220 can be embedded in the session flow in response to a trigger on the first component 203 corresponding to the first interactive content 205 to present the first interface content. As mentioned above, in this case, the first interface content can present task information of a first task, where the first task refers to the task associated with the first interactive content 205.

[0056] In some scenarios, in response to updated data returned by a running instance of the first application (e.g., as the execution of the first task progresses), the electronic device 110 may update only the interface content in the first area 220, while keeping other interactive content in the second area 210 unchanged. The first area 220 can thus be presented in conjunction with the session context of the intelligent system 120.

[0057] Through the above solution, the interface content of the first application can be included within the interactive area of ​​the smart system 120, thereby solving the difficulty for users to switch back and forth between the smart system interface and the application page. The electronic device 110 can update only the interface nodes corresponding to the first area 220 without reloading the entire first interface 200B. As a result, the interface rendering overhead, memory usage, and page update time of the electronic device 110 can be reduced.

[0058] Figure 2C A schematic diagram of the first interface 200C and the second interface is shown according to some scenarios. Figure 2C In the example, the first region 220 may be included in a second interface that is different from the first interface 200C.

[0059] In response to a trigger operation on any of the first components 201, 202, 203, or 204, the electronic device 110 may present a second interface in addition to the first interface 200C, and present a first area 220 within the second interface. The second interface may be a separate window, a new tab, or a site page that can be hosted by other interfaces.

[0060] In some cases, the second interface can be presented as an embedded interface within the third interface. An "embedded interface" refers to an interface presented as part of another interface. Embedded interfaces can be implemented through embedded pages, controlled display containers, or other interface embedding methods. The third interface can be provided by another application or site different from the intelligent system 120. The electronic device 110 can load the interface resources of the second interface through a controlled display container and provide interactive data from the third interface to the running instance of the first application via a preset interface.

[0061] Through the above solution, the interface content of the first application can be presented in both the interactive interface of the intelligent system 120 and another interface, thus solving the difficulty of the application interface content being limited to a single interface container. Different presentation forms can reuse the same interface resources and running instances, reducing the amount of processing required to repeatedly generate interface data. As a result, the number of repeated calculations by the server 130 and the amount of repeated data transmission between the electronic device 110 and the server 130 can be reduced.

[0062] The above explanation uses the first application as an example. In reality, the intelligent system 120 can be associated with multiple applications. Depending on how the intelligent system 120 uses different applications, the provided first component can also be associated with different applications and used as the entry point for the corresponding application. Figure 2D The diagram illustrates the relationship between the intelligent system 120 and multiple applications 230-1, 230-2 to 230-N. Any one of these applications can serve as the first application.

[0063] In some cases, the intelligent system 120 can be associated with multiple applications simultaneously. The electronic device 110 can provide a first component associated with any of the multiple applications during interaction with the intelligent system 120; this first component can serve as an entry point for the corresponding application. The electronic device 110 can also provide a master entry point for multiple applications and, in response to a triggering operation on the master entry point, present a list of applications to receive a selection of a target application. For example, first components 201 and 202 can be used to view a list of all associated applications. The user can select a specific application from this list to view its homepage. The application associated with first component 203 or 206 may depend on the application invoked by the intelligent system 120 when generating the first interactive content 205. The application associated with first component 204 may be an application that the user expects to access when inputting interactive content with the intelligent system 120, or an application pre-configured or automatically recommended near the input area of ​​the intelligent system 120.

[0064] Electronic device 110 can determine a first application from multiple applications based on the current interactive content, commands input by user 140, recent usage information of the application, or the activation status of the application, and present a first component associated with the first application. Electronic device 110 can also present first components associated with multiple applications separately on the same first interface, allowing user 140 to select the application to access.

[0065] Through the above solution, the intelligent system 120 can manage multiple applications through a unified association relationship, and provide the first component associated with any application or the overall entry point for multiple applications as needed during the interaction process. This solves the problem of scattered entry points and difficulty in locating target applications when the number of applications increases. The electronic device 110 can reuse application association data to determine the available first component without having to request the entry point configuration for each application separately. As a result, the number of queries and the amount of communication data required for application entry initialization can be reduced.

[0066] In some embodiments, while displaying the application's interface content, it can also support the linkage between the interface content and the intelligent system interaction. Figure 2E A schematic diagram of a first interface 200E is shown according to some scenarios. The first interface 200E may include a second area 210, an input area 212, a first area 220, a second component 222, and first information 214.

[0067] As used herein, the term "second component" refers to an interface component within the content of the first interface that is associated with at least one functional unit of the first application and is capable of triggering corresponding processing in response to user actions. The second component may include buttons, selection items, switches, input controls, or other operable elements.

[0068] like Figure 2E As shown, the second component 222 can be presented in the first interface content of the first area 220 and associated with at least one functional unit of the first application. In some cases, the electronic device 110 can present first information 214 in the input area 212 in response to a trigger operation on the second component 222. The first information refers to information presented in the input area in response to a trigger operation on the second component, used to request the intelligent system to invoke at least one functional unit. The first information can be generated by the first application or determined by the first application based on the first interface content and user operation.

[0069] In some cases, the first information 214 may include a query requesting the intelligent system 120 to invoke at least one functional unit. In some cases, the user 140 may modify the first information 214. In some cases, the user 140 may provide the first information 214 or a modified first information 214 to the intelligent system 120 by sending an operation.

[0070] In some scenarios, in response to a triggering operation on the second component 222, the electronic device 110 can generate a call request for at least one functional unit and provide the call request to a running instance of the first application. The running instance can execute at least one functional unit and return a call result. The electronic device 110 can update the content of the first interface in the first area 220 based on the call result.

[0071] In response to the transmission of first information 214, electronic device 110 can provide first information 214 to intelligent system 120. Intelligent system 120 can determine, based on first information 214, the first application and at least one functional unit to be invoked, and send a functional unit invocation request to the running instance of the first application. Intelligent system 120 can generate first response content based on the invocation result returned by the running instance. Electronic device 110 can present the first response content in first area 220.

[0072] The second component provided in the first interface content may depend on the specific design and configuration of the first application, and there are no restrictions here.

[0073] In some scenarios, requests to load the content of the first interface and requests to invoke at least one functional unit can be routed to the same running instance of the first application based on declaration information. Declaration information may include a mapping between the interface resource addresses and service addresses of the first application. The application routing service can use this mapping to ensure that interface loading data and functional unit processing data are accessed by the same running instance, thereby reducing cross-instance state synchronization.

[0074] In some scenarios, a runtime instance can be executed within a runtime environment, which provides the primary application with an execution space isolated from other applications. The runtime environment can separately configure the resource quotas, configuration storage, and request queues for the primary application. This allows the exception handling or resource consumption of one application to be separated from the execution process of other applications.

[0075] In some cases, at least one functional unit of the application may include an event interception functional unit. In response to a confirmation request associated with the event interception functional unit, the electronic device 110 may present confirmation information. In response to the user 140's confirmation operation on the confirmation information, the running instance may continue executing at least one functional unit, and the electronic device 110 may present the execution result of at least one functional unit. In response to the user 140 not confirming or selecting cancel, the running instance may stop continuing to execute the corresponding operation.

[0076] Through the above solution, the interface content of the first application can form a two-way linkage with the intelligent system 120, thereby solving the difficulties of the separation of the application interface and the intelligent system call chain in related solutions, and the need for repeated input or repeated loading of processing results. The data triggered by the second component 222 can flow between the first area 220 and the input area 212 through the same running instance, reducing cross-instance data copying and repeated functional unit calls. As a result, the interface update time of the electronic device 110, the number of requests processed by the server 130, and the amount of communication data between the two can be reduced.

[0077] In some cases, the applications associated with the intelligent system, or the specific interface content of those applications, can also support sharing capabilities. Figure 3A and Figure 3B The interface states for linking a second application via a share link are shown, depending on certain scenarios. Figure 3A The first interface 300A is shown. The first interface 300A may include a second area 210, an input area 212, a sharing link 240, and an installation confirmation panel 242.

[0078] A shareable link is a link that carries information for locating a second application and can trigger the association process with that application. A shareable link can point to details of the second application, its installation contents, or an address that can be used to obtain the second application's resource package.

[0079] In response to a triggering operation on the sharing link 240, the electronic device 110 can obtain the identifier of the second application from the sharing link 240 and determine whether the second application has been associated with the smart system 120. In some cases, if the second application is not yet associated, the electronic device 110 can present an installation confirmation panel 242 to receive an operation to confirm associating the second application with the smart system 120. In response to the user 140 performing a confirmation operation via the installation confirmation panel 242, the electronic device 110 or the server 130 can obtain the resource package of the second application. In some cases, if the second application is not yet associated, installation confirmation may not be required. In response to a triggering operation on the sharing link 240, the electronic device 110 or the server 130 can obtain the resource package of the second application. The electronic device 110 or the server 130 can create a configuration storage associated with the second application based on the resource package, and establish the association between the second application and the smart system 120 based on the configuration storage. The configuration storage can be used to store the running configuration and permission configuration of the second application.

[0080] like Figure 3B As shown, after the second application is associated with the smart system 120, the electronic device 110 can present the second interface content 244 of the second application in the first area. The second interface content 244 can be generated from the interface resources of the second application and can be associated with at least one functional unit of the second application.

[0081] In some cases, the sharing link 240 can be sent by another electronic device. The electronic device 110 receiving the sharing link 240 can, in response to a trigger operation, sequentially complete resource acquisition, association establishment, and the presentation of the second interface content 244. The electronic device 110 can also associate the second application with the smart system selected by the user 140 based on the target information carried in the sharing link 240.

[0082] In some cases, the presentation of the installation confirmation panel 242 can also be used for the confirmation processing of the event interception function unit. The electronic device 110 can replace the prompts on the panel with confirmation information associated with the confirmation request, and continue to execute the corresponding function unit in response to the confirmation operation.

[0083] Through the above solution, the sharing link 240 can simultaneously provide the location information and association trigger path of the second application, thereby solving the multi-stage processing difficulties of related solutions that require first finding the application, then performing the association, and finally returning to the interactive interface to open the application. The electronic device 110 can reuse the information carried by the sharing link 240 to complete resource acquisition and configuration creation, reducing application retrieval requests and page jumps. As a result, the number of communication rounds, interface loading times, and processing time required to associate the second application can be reduced.

[0084] Figure 4 A fourth interface 400 for creating a first application is shown, depending on certain circumstances. The fourth interface 400 may include a first creation method option 410, a second creation method option 420, a special skill option 430, a service function unit option 432, a command function unit option 434, and an event interception function unit option 436.

[0085] In one creation method, electronic device 110 may receive a first request for creating a first application, the first request including a description of the requirements for the first application. The description of requirements may be entered by user 140 after selecting the first creation method option 410, or it may be obtained from document content provided by user 140.

[0086] The intelligent system 120 can generate declaration information for a first application based on a requirements description. The declaration information can describe at least one functional unit, a first component, and interface resources of the first application. During the generation of the declaration information, the intelligent system 120 can also determine at least one functional unit that the first application needs to implement based on the requirements description. For example, the intelligent system 120 can determine that the first application needs one or more of the following: service functional unit, command functional unit, event interception functional unit, specialized skills, and interface resources. In some cases, the intelligent system 120 can further generate an application package for the first application based on the generated declaration information. An application package refers to a collection of resources that can be registered, installed, or loaded to provide application functional units. An application package can include one or more of the following: program resources, interface resources, configuration templates, and declaration information. An application package can include interface resources used to provide the interface content of the first application. Interface resources can include interface structure data, style data, interaction logic, script resources, or interface configurations for accessing backend services.

[0087] In another creation method, electronic device 110 may, in response to a triggering operation of second creation method option 420, present multiple options corresponding to multiple capability types. The multiple options may include dedicated skill option 430, service function unit option 432, command function unit option 434, and event interception function unit option 436. Electronic device 110 may receive a selection operation on at least one option, and at least one function unit of the first application may correspond to at least one capability type indicated by the at least one option. Electronic device 110 may generate declaration information of the first application based on the at least one option, and may further generate an application package of the first application based on the declaration information.

[0088] In some cases, at least one functional unit may include at least one of a service functional unit, a command functional unit, an event interception functional unit, or a dedicated skill. Dedicated skill option 430 can be used to select a specific processing capability provided to the intelligent system 120. Service functional unit option 432 can be used to select a service processing capability that is resident or started on demand. Command functional unit option 434 can be used to select commands that can be invoked from the input area 212. Event interception functional unit option 436 can be used to select the ability to perform additional processing in response to preset events.

[0089] In some cases, the first request may also include service interface information for implementing at least one functional unit of the first service. The intelligent system 120 can generate program resources for calling the first service based on a preset application development framework and service interface information. The program resources may be included in an application package, and declaration information may describe the calling relationship between the program resources and the first service.

[0090] In some cases, the first application, once created, can be registered as an associable object. Electronic device 110 or server 130 can obtain the application package and declaration information of the first application, perform format verification and version registration on the application package and declaration information, and provide an installation entry point associated with the first application. An "installation entry point" refers to the interface element used to initiate application resource acquisition or establish the association between the application and the intelligent system. The installation entry point can be provided through the application management interface, the interface corresponding to a sharing link, or the application details content.

[0091] In some cases, the declaration information may also include permission requirements. The first application can access the controlled resource through a permission proxy based on these requirements. The permission proxy can first verify the first application's identity and the authorization information of the operating account, and then provide the first application with temporary access information or forward the controlled resource access request on its behalf.

[0092] In some scenarios, the first application may be loaded into the runtime environment and set to an active state in response to an activation event. Activation events may include first component trigger events, command invocation events, task dispatch events, or preset state change events. In response to session switching events, idle events, or resource reclamation events, the first application may be set to a paused state, and its configuration data may be retained in this paused state. A "paused state" refers to a state in which the application temporarily stops processing new functional unit calls but at least retains its configuration data. An application in a paused state may re-enter an active state in response to a resume event. In response to subsequent first component trigger events or functional unit call events, the first application may resume its active state based on the retained configuration data.

[0093] In some cases, the first interface may also include an uninstallation entry. An "uninstallation entry" refers to an interface element used to initiate application deassociation or unavailability processing. In response to a triggering operation on the uninstallation entry, the electronic device 110 may display a data processing confirmation area, which may include a delete control. In response to a triggering operation on the delete control, the electronic device 110 may stop displaying the first component and first interface content of the first application and display a prompt message indicating that the first application is in an unavailable state. The server 130 may retain or delete the associated data of the first application based on the confirmation result.

[0094] In some cases, electronic device 110 may receive an association request to associate a third application with intelligent system 120, the association request including the name of the third application. In response to the third application's name being the same as the first application's name, electronic device 110 may present a conflict warning, indicating that the association between the third application and intelligent system 120 has failed. Server 130 may maintain the original association between the first application and intelligent system 120 unchanged.

[0095] In some cases, the original running instance of the first application can continue to handle the tasks being run. The first interface may include a version update identifier and an upgrade entry. In response to a trigger operation on the upgrade entry, the electronic device 110 can display the new version interface content of the first application, which can be associated with the new running instance. The new running instance may correspond to the new version of the first application, and the original running instance may correspond to the original version of the first application.

[0096] In some scenarios, the application routing service can select a running instance based on the task identifier during version switching. Requests associated with a running task can continue to be routed to the original running instance, while newly received requests can be routed to the new running instance. When the original running instance no longer hosts a running task, the runtime environment can stop that original running instance.

[0097] Through the above solution, the fourth interface 400 can support creation paths based on requirement descriptions and creation paths based on capability type selection. The generated results include declaration information, and in some cases, application packages, interface resources, and functional unit resources corresponding to the declaration information. This solves the problem of inconsistent correspondences caused by separate configurations of interface resources and callable functional units in related solutions. The intelligent system 120 or electronic device 110 can complete registration, routing, permission processing, and state switching based on unified declaration information, reducing the processing load of repeatedly parsing application configurations and repeatedly establishing service connections. Therefore, the loading time after application creation, the number of routing queries, and the overhead of cross-instance state synchronization can be reduced.

[0098] In some cases, the application management interface can also display installed applications and associated applications. Installed applications can be presented in the form of cards, which may include one or more of the following: application name, category information, description information, version information, and number of functional units. In response to a triggering operation on a card, the electronic device 110 can display application details or open the application's first interface content.

[0099] In some cases, the electronic device 110 can sort the first components that serve as application entry points based on recent usage time, and provide a scrollable area when the number of first components exceeds the number that can be displayed. The electronic device 110 can also present a master entry point in the application list for accessing the application management interface or the application collection interface.

[0100] In some scenarios, the primary application may provide its initial interface content through session flow cards, sidebars, confirmation panels, full-screen areas, new tabs, or command entry points. Different presentation formats can share the primary application's declaration information and runtime instance. The electronic device 110 can select the presentation format based on content complexity, interaction type, or available interface space.

[0101] In some scenarios, the first application can obtain the interaction context of the intelligent system 120 through preset events. The event interception function unit can generate event data before and after task state changes, message processing, or tool invocation. The running instance of the first application can determine the first interface content to be presented or the service function unit to be invoked based on the event data.

[0102] In some scenarios, the service function unit can first obtain the target data through programmatic processing, and then the intelligent system 120 can generate interactive content based on the target data. By delegating steps that do not require model processing to the service function unit, the number of times the intelligent system 120 calls the model can be reduced, and the processing time required to generate interactive content can be shortened.

[0103] In some cases, application creators can define the layout, controls, and data processing logic of the first interface content. The intelligent system 120 can then present different application interface content based on the interface resources provided by the application creator, without modifying the basic interaction structure of the first interface.

[0104] In some cases, the first application can provide a development interface on the second interface for debugging interface resources or calling functional units. The electronic device 110 can decide whether to present the development entry point based on the permission information corresponding to the operating account. Operating accounts without the corresponding permissions can use the functional units of the first application and the content of the first interface, but the development entry point will not be presented.

[0105] In some scenarios, electronic device 110 can display a version update indicator when a new version of the application is available, and provide options to switch immediately, process later, or ignore the update. Version switching can be performed gradually based on the status of the running instance to avoid interrupting running tasks.

[0106] In some cases, server 130 can verify command names within an application, application names associated with the same intelligent system, and conflicts between application functional units and built-in functional units of the intelligent system. For duplicate command names within an application, server 130 can refuse to register the application as an associable object. For a third application with the same name as the first application, server 130 can refuse to establish an association between the third application and the intelligent system 120. In cases where application functional units conflict with built-in functional units of the intelligent system 120, the intelligent system 120 can prioritize the processing path corresponding to the built-in functional unit.

[0107] In some cases, the running instance of the first application can execute in a controlled process, or it can execute as a service or function provided by server 130. Regardless of the execution method, UI content loading requests and functional unit call requests can be routed to the corresponding running instance based on the declaration information.

[0108] In some scenarios, the above solutions can also be applied to task processing, data querying, content generation, document processing, code processing, and workflow execution. The first application can provide interface content and functional units that can be invoked by the intelligent system 120 for the corresponding scenario. It should be understood that the above application scenarios are merely illustrative and not restrictive.

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

[0110] like Figure 5 As shown, in box 510, the electronic device 110 presents a first interface for interacting with the intelligent system. The first interface includes a first component, which is associated with a first application. The first application includes at least one functional unit, which can be invoked by the intelligent system. Its interactive presentation can be seen above. Figures 2A to 2E The example described.

[0111] In frame 520, the electronic device 110, in response to a trigger operation on the first component, presents a first area, which is used to display the first interface content of the first application. Its interactive presentation can be found above. Figures 2A to 2E The example described.

[0112] In some cases, the first interface may include a second area for interacting with the intelligent system, and the first and second areas have a primary positional relationship. For specific presentation details, please refer to the above. Figure 2A and Figure 2B The example described.

[0113] In some cases, the first positional relationship indicates one of the following: the first region may be included within the second region, or the first region is separate from the second region. See above for a specific example. Figure 2A and Figure 2B The example described.

[0114] In some cases, the first area may be included within a second interface, which is different from the first interface. See above for specific examples. Figure 2C The example described.

[0115] In some cases, the second interface can be presented as an embedded interface within the third interface. See the above text for specific examples. Figure 2C The example described.

[0116] In some cases, the first component can be one of multiple components of the first application, with each component associated with different UI content of the first application. See the above for a specific example. Figures 2A to 2E The example described.

[0117] In some cases, the content of the first interface may include the homepage of the first application. See above for specific presentation examples. Figures 2A to 2E The example described.

[0118] In some scenarios, the first component may be associated with first interactive content, which is provided by the intelligent system and is related to a first task. The intelligent system invokes at least one first functional unit from at least one functional unit to execute the first task, and the content of the first interface includes task information for the first task. For a specific presentation, please refer to the above. Figures 2A to 2E The example described.

[0119] In some cases, the first component can be associated with the input area of ​​the first interface. The first component is used to receive commands associated with the first application, and the content of the first interface corresponds to the commands. See the above text for a specific example. Figures 2A to 2E The example described.

[0120] In some cases, the first region includes a second component associated with at least one functional unit, and method 500 further includes: updating the content of the first interface in response to a triggering operation on the second component, wherein the updated content of the first interface is associated with the invocation result of at least one functional unit. For specific interactive presentation details, please refer to the above. Figure 2E The example described.

[0121] In some cases, method 500 further includes: in response to a triggering operation on the second component, presenting first information in the input area of ​​the first interface, the first information being used to request the intelligent system to invoke at least one functional unit. For specific interactive presentation details, please refer to the above. Figure 2E The example described.

[0122] In some cases, method 500 further includes: in response to a sending operation of the first information, presenting first response content in a first area, the first response content being obtained based on the first information. For specific interactive presentation details, please refer to the above. Figure 2E The example described.

[0123] In some cases, method 500 further includes: receiving a shareable link associated with a second application; in response to a triggering operation on the shareable link, associating the second application with the smart system; and presenting the second interface content of the second application in a first area. Specific interactive presentation can be found above. Figure 3A and Figure 3B The example described.

[0124] In some cases, the first application may also include declaration information describing at least one functional unit, a first component, and interface resources, which are used to provide the interface content of the first application. For specific presentation details, please refer to the above. Figures 2A to 2E and Figure 4 The example described.

[0125] In some cases, method 500 further includes: receiving a first request for creating a first application, the first request including a requirement description for the first application; and generating declaration information for the first application based on the requirement description. For specific interactive presentation, please refer to the above. Figure 4 The example described.

[0126] In some cases, method 500 further includes: presenting a fourth interface, the fourth interface including multiple options corresponding to multiple capability types respectively; receiving a selection operation on at least one option, the multiple options including at least one option, at least one functional unit corresponding to at least one capability type indicated by at least one option; and generating declaration information of the first application based on at least one option. Specific interactive presentation can be found above. Figure 4 The example described.

[0127] In some cases, requests to load the content of the first interface and requests to invoke at least one functional unit are routed to the same running instance of the first application based on declaration information. For specific interaction presentation details, please refer to the above. Figure 2E The example described.

[0128] In some scenarios, runtime instances execute within a runtime environment, which can provide the primary application with an execution space isolated from other applications. See the above text for a detailed explanation. Figure 2E The example described.

[0129] In some cases, at least one functional unit may include at least one of the following: a service functional unit, a command functional unit, an event interception functional unit, or a specialized skill. See above for a detailed presentation. Figure 4 The example described.

[0130] In some cases, at least one functional unit includes an event interception functional unit, and method 500 further includes: presenting confirmation information in response to a confirmation request associated with the event interception functional unit; and presenting the execution result of at least one functional unit in response to a confirmation operation on the confirmation information. Specific interactive presentation details can be found above. Figure 2E and Figure 3A The example described.

[0131] In some cases, the first request may also include service interface information for implementing at least one functional unit of the first service; generating the application package and declaration information of the first application includes: generating program resources for calling the first service based on a preset application development framework and service interface information. For specific interactive presentation, please refer to the above. Figure 4 The example described.

[0132] In some cases, registering the first application includes: obtaining the application package and declaration information of the first application; performing format verification and version registration on the application package and declaration information; and providing an installation entry point associated with the first application. For specific interactive details, please refer to the above text. Figure 4 The example described.

[0133] In some cases, associating a second application with an intelligent system includes: obtaining a resource package for the second application; creating a configuration store associated with the second application based on the resource package; and establishing a relationship between the second application and the intelligent system based on the configuration store. Specific interaction presentations can be found above. Figure 3A and Figure 3B The example described.

[0134] In some cases, the first application is loaded into the runtime environment in response to the activation event and set to the active state. For specific interaction details, please refer to the above text. Figure 4 The example described.

[0135] In some scenarios, in response to session switching events, idle events, or resource reclamation events, the first application is set to a paused state, and its configuration data is retained during this paused state. For specific interaction details, please refer to the above text. Figure 4 The example described.

[0136] In some cases, the first interface also includes an uninstallation entry. The method further includes: in response to a triggering operation on the uninstallation entry, presenting a data processing confirmation area, which includes a delete control; and in response to a triggering operation on the delete control, stopping the presentation of the first component and the first interface content of the first application, and presenting a prompt message indicating that the first application is unavailable. For specific interactive presentation details, please refer to the above. Figures 2A to 2E Examples of alternative interface states described.

[0137] In some scenarios, an association request is received to link a third application to the intelligent system, the association request including the name of the third application; and in response to the third application's name being identical to the first application's name, a conflict warning is displayed, indicating that the association between the third application and the intelligent system has failed. For specific interaction details, please refer to the above. Figure 3A Examples of alternative interface states described.

[0138] In some scenarios, the running instance is the original running instance of the first application, and the first interface includes a version update identifier and an upgrade entry. In response to a trigger operation on the upgrade entry, the new version interface content of the first application is presented, and this new version interface content is associated with the new running instance. Among these, the currently running tasks are associated with the original running instance; the new running instance corresponds to the new version of the first application, and the original running instance corresponds to the original version of the first application. For specific interaction presentation details, please refer to the above. Figures 2A to 2E Examples of alternative interface states described.

[0139] Through the above scheme, after user 140 triggers the first component associated with the application in the first interface used to interact with the intelligent system 120, electronic device 110 can present the corresponding interface content in a first area adapted to the interaction context. In some cases, the correspondence between the first component, declaration information, and running instance allows electronic device 110 to directly determine the processing path of interface resources and functional units, reducing unrelated page loading, cross-instance data synchronization, and duplicate requests. Therefore, the interface rendering overhead of electronic device 110, the number of processing operations of server 130, and the amount of communication data between them can be reduced.

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

[0141] Figure 6 Block diagrams of a device 600 for user interface interaction are shown for several scenarios. Device 600 can be implemented as or included in electronic device 110 or server 130. Various modules or components in device 600 can be implemented by hardware, software, firmware, or any combination thereof.

[0142] like Figure 6 As shown, the device 600 includes a first presentation module 610 configured to present a first interface for interacting with an intelligent system. The first interface includes a first component associated with a first application. The first application includes at least one functional unit that can be invoked by the intelligent system. The device also includes a second presentation module 620 configured to present a first area in response to a triggering operation on the first component. The first area is used to display the content of the first interface of the first application.

[0143] In some cases, the first interface may include a second area for interacting with the intelligent system, and the first area and the second area have a first positional relationship.

[0144] In some cases, the first positional relationship indicates one of the following: the first region may be included in the second region, or the first region is separate from the second region.

[0145] In some cases, the first area may be included within a second interface, which is different from the first interface.

[0146] In some cases, the second interface can be presented as an embedded interface within the third interface.

[0147] In some cases, the first component can be one of multiple components of the first application, with each component associated with different interface content of the first application.

[0148] In some cases, the content of the first interface may include the homepage of the first application.

[0149] In some cases, the first component may be associated with the first interactive content, which is provided by the intelligent system and is related to the first task. The intelligent system calls the first functional unit in at least one functional unit to execute the first task, and the first interface content includes the task information of the first task.

[0150] In some cases, the first component may be associated with the input area of ​​the first interface. The first component is used to receive commands associated with the first application, and the content of the first interface corresponds to the commands.

[0151] In some cases, the first region includes a second component associated with at least one functional unit. The apparatus 600 also includes an update module configured to update the content of the first interface in response to a triggering operation on the second component, the updated content of the first interface being associated with the result of a call to at least one functional unit.

[0152] In some cases, the second presentation module 620 may also be configured to perform the following processing: in response to a triggering operation on the second component, presenting first information in the input area of ​​the first interface, the first information being used to request the intelligent system to invoke at least one functional unit.

[0153] In some cases, the second presentation module 620 may also be configured to perform the following processing: in response to the sending operation of the first information, presenting first response content in the first area, the first response content being obtained based on the first information.

[0154] In some cases, device 600 further includes a receiving module configured to receive a sharing link associated with a second application; and an association module configured to associate the second application with the smart system in response to a triggering operation on the sharing link. The second presentation module 620 is configured to present the second interface content of the second application in a first area.

[0155] In some cases, the first application may also include declaration information describing at least one functional unit, a first component, and a interface resource, which is used to provide the interface content of the first application.

[0156] In some cases, the apparatus 600 further includes: a receiving module configured to receive a first request for creating a first application, the first request including a requirement description for the first application; and a generating module configured to generate declaration information for the first application based on the requirement description.

[0157] In some cases, the second presentation module 620 may also be configured to present a fourth interface, the fourth interface including multiple options corresponding to multiple capability types respectively. The apparatus 600 further includes: a receiving module configured to receive a selection operation on at least one option, the multiple options including at least one option, at least one functional unit corresponding to at least one capability type indicated by the at least one option; and a generating module configured to generate declaration information for a first application based on at least one option.

[0158] In some cases, requests to load the content of the first interface and requests to invoke at least one functional unit are routed to the same running instance of the first application based on declaration information. In other cases, the running instance executes in a runtime environment that can provide the first application with an execution space isolated from other applications.

[0159] In some cases, the device 600 further includes: a registration module configured to obtain the application package and declaration information of the first application; perform format verification and version registration on the application package and declaration information; and provide an installation entry associated with the first application.

[0160] In some cases, associating a second application with an intelligent system includes: obtaining a resource package of the second application; creating a configuration store associated with the second application based on the resource package; and establishing an association between the second application and the intelligent system based on the configuration store.

[0161] In some cases, the first application is loaded into the runtime environment in response to the activation event and set to the active state.

[0162] In some cases, in response to a session switching event, an idle event, or a resource reclamation event, the first application is set to a paused state, and the configuration data of the first application is retained in the paused state.

[0163] In some cases, device 600 further includes a receiving module configured to receive an association request for associating a third application with the smart system, the association request including the name of the third application; and the second presentation module 620 may also be configured to present a conflict prompt in response to the name of the third application being the same as the name of the first application, the conflict prompt indicating that the association between the third application and the smart system has failed.

[0164] In some cases, the running instance is the original running instance of the first application, and the first interface includes a version update identifier and an upgrade entry. The second presentation module 620 can also be configured to present the new version interface content of the first application in response to a trigger operation on the upgrade entry. The new version interface content is associated with the new running instance; wherein, the running task is associated with the original running instance, the new running instance corresponds to the new version of the first application, and the original running instance corresponds to the original version of the first application.

[0165] The modules included in device 600 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some cases, one or more modules can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units in device 600 can be implemented at least partially by one or more hardware logic components. By way of example, and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard parts (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), and so on.

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

[0167] like Figure 7As shown, electronic device 700 is in the form of a general-purpose electronic device. Components of electronic device 700 may include, but are not limited to, one or more processing units or processors 710, memory 720, storage devices 730, one or more communication units 740, one or more input devices 750, and one or more output devices 760. Processor 710 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 720. In a multiprocessor system, multiple processors execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 700.

[0168] Electronic device 700 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 700, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 720 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 730 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 700.

[0169] Electronic device 700 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 7 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 720 may include computer program product 725 having one or more program modules configured to perform various methods or actions of various examples.

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

[0171] Input device 750 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 760 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 700 can also communicate with one or more external devices (not shown) via communication unit 740 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 700, or with any device that enables electronic device 700 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).

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

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

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

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

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

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

Claims

1. A method for user interface interaction, comprising: A first interface is presented, which is used to interact with the intelligent system. The first interface includes a first component, which is associated with a first application. The first application includes at least one functional unit, which can be invoked by the intelligent system. as well as In response to a trigger operation on the first component, a first area is presented, which is used to display the first interface content of the first application.

2. The method according to claim 1, wherein the first interface includes a second region for interacting with the intelligent system, and the first region and the second region have a first positional relationship.

3. The method of claim 2, wherein the first positional relationship indicates one of the following: The first region is included in the second region, or The first region is separated from the second region.

4. The method according to claim 1, wherein the first region is included within a second interface, the second interface being different from the first interface.

5. The method according to claim 4, wherein the second interface is presented as an embedded interface in the third interface.

6. The method of claim 1, wherein the first component is one of a plurality of components of the first application, the plurality of components being associated with different interface content of the first application.

7. The method according to claim 6, wherein the content of the first interface includes the homepage of the first application.

8. The method according to claim 6, wherein the first component is associated with first interactive content, the first interactive content is provided by the intelligent system, the first interactive content is related to a first task, the intelligent system calls a first functional unit among the at least one functional unit to execute the first task, and the first interface content includes task information of the first task.

9. The method of claim 6, wherein the first component is associated with an input area of ​​the first interface, the first component being configured to receive a command associated with the first application, and the content of the first interface corresponding to the command.

10. The method of claim 1, wherein the first region includes a second component associated with the at least one functional unit, the method further comprising: In response to a triggering operation on the second component, the content of the first interface is updated, and the updated content of the first interface is associated with the invocation result of the at least one functional unit.

11. The method of claim 10, further comprising: In response to a triggering operation on the second component, first information is presented in the input area of ​​the first interface, the first information being used to request the intelligent system to invoke the at least one functional unit.

12. The method of claim 11, further comprising: In response to the sending operation of the first information, a first response content is presented in the first area, the first response content being obtained based on the first information.

13. The method according to claim 1, further comprising: Receive a sharing link, which is associated with a second application; In response to a triggered operation on the shared link, the second application is associated with the smart system; as well as The second interface content of the second application is displayed in the first area.

14. The method of claim 1, wherein the first application further includes declaration information describing the at least one functional unit, the first component, and the interface resource, the interface resource being used to provide interface content for the first application.

15. The method of claim 14, further comprising: Receive a first request, the first request being used to create the first application, the first request including a description of the requirements for the first application; as well as Based on the aforementioned requirement description, the declaration information of the first application is generated.

16. The method of claim 14, further comprising: A fourth interface is presented, which includes multiple options corresponding to multiple ability types; Receive a selection operation for at least one option, the plurality of options including the at least one option, the at least one functional unit corresponding to at least one capability type indicated by the at least one option; as well as Based on the at least one of the options, the declaration information of the first application is generated.

17. A device for user interface interaction, comprising: A first presentation module is configured to present a first interface for interacting with an intelligent system. The first interface includes a first component, which is associated with a first application. The first application includes at least one functional unit that can be invoked by the intelligent system. as well as The second presentation module is configured to present a first area in response to a trigger operation on the first component, the first area being used to display the first interface content of the first application.

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

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 16.

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

Images