Application creating method and device, equipment and storage medium
By configuring multiple agents and jump information in the application, the problem of single agent applications processing complex requests is solved, achieving wider scenario coverage and more efficient information processing.
Patent Information
- Application Number
- CN202410083404.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-19
- Publication Date
- 2025-07-22
AI Technical Summary
Existing applications are usually based on a single agent, making it difficult to effectively handle complex requests, and scene coverage is limited.
By acquiring the configuration information, indicating the jump information between the multiple agents, the first agent is allowed to switch to the second agent to process the request, and create a multi-agent-based application.
It improves the application's scenario coverage and problem-solving capabilities, and enhances the accuracy of the application's agent switching and information processing.
Smart Images

Figure CN120353492A_ABST
Abstract
Description
Technical Field
[0001] Example embodiments of the present disclosure generally relate to the field of computers, and particularly to methods, apparatuses, devices, and computer-readable storage media for creating applications. Background Art
[0002] With the development of computer technology, people can create and publish various types of applications through some platforms. For example, with the development of machine learning technology, people can quickly create applications by configuring the parameters of the applications, such as the models used by the applications, available plugins, etc. Summary of the Invention
[0003] In a first aspect of the present disclosure, a method for creating an application is provided. The method includes: obtaining configuration information, where the configuration information indicates a plurality of agents used for creating an application and jump information associated with the plurality of agents, and the jump information at least indicates that a first agent among the plurality of agents can switch to a second agent to process a request; and creating a target application based on the configuration information.
[0004] In a second aspect of the present disclosure, an apparatus for creating an application is provided. The apparatus includes: an obtaining module configured to obtain configuration information, where the configuration information indicates a plurality of agents used for creating an application and jump information associated with the plurality of agents, and the jump information at least indicates that a first agent among the plurality of agents can switch to a second agent to process a request; and a creating module configured to create a target application based on the configuration information.
[0005] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory, where the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the device executes the method of the first aspect.
[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided. A computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.
[0007] It should be understood that the content described in this content part is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it used to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. Brief Description of the Drawings
[0008] In conjunction with the accompanying drawings and with reference to the following detailed description, the above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent. In the drawings, the same or similar reference numerals denote the same or similar elements, where:
[0009] Figure 1 A schematic diagram showing an example environment in which embodiments according to the present disclosure can be implemented is presented;
[0010] Figure 2 A flowchart showing an example process for creating an application according to some embodiments of the present disclosure is presented;
[0011] Figures 3A to 3F An example interface according to some embodiments of the present disclosure is presented;
[0012] Figure 4 A schematic structural block diagram showing an example apparatus for creating an application according to some embodiments of the present disclosure is presented; and
[0013] Figure 5 A block diagram of an electronic device capable of implementing multiple embodiments of the present disclosure is presented. Detailed Embodiments
[0014] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.
[0015] It should be noted that the titles of any sections / subsections provided herein are not restrictive. Various embodiments are described throughout this document, and any type of embodiment can be included under any section / subsection. Additionally, the embodiments described in any section / subsection can be combined with any other embodiments described in the same section / subsection and / or different sections / subsections in any manner.
[0016] In the description of the embodiments of the present disclosure, the term "including" and its like shall be understood as open inclusion, i.e., "including but not limited to". The term "based on" shall be understood as "at least partially based on". The term "one embodiment" or "the embodiment" shall be understood as "at least one embodiment". The term "some embodiments" shall be understood as "at least some embodiments". There may also be other explicit and implicit definitions hereinafter. The terms "first", "second", etc. may refer to different or the same objects. There may also be other explicit and implicit definitions hereinafter.
[0017] Embodiments of the present disclosure may involve user data, data acquisition and / or use, etc. All of these aspects comply with the corresponding laws, regulations and related provisions. In the embodiments of the present disclosure, the collection, acquisition, processing, processing, forwarding, use, etc. of all data are carried out on the premise that the user is aware and confirms. Accordingly, when implementing the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the data or information that may be involved should be informed to the user and the user's authorization should be obtained through appropriate means according to the relevant laws and regulations. The specific notification and / or authorization methods may vary according to the actual situation and application scenarios, and the scope of the present disclosure is not limited in this regard.
[0018] In the solutions of this specification and embodiments, if personal information processing is involved, it will be processed on the premise of having a legal basis (such as obtaining the consent of the personal information subject, or being necessary for performing a contract), and will only be processed within the specified or agreed scope. If the user refuses to process personal information other than the necessary information required for the basic functions, it will not affect the user's use of the basic functions.
[0019] Traditionally, users support configuring models, plugins, etc. used by an application to quickly create an application, for example, a bot. However, such an application usually corresponds to a single agent. Since an agent usually has strong processing capabilities in a specific field, this results in the requests that the application can handle being limited and it is difficult to effectively handle relatively complex requests.
[0020] Embodiments of the present disclosure propose a solution for creating an application. According to this solution, configuration information can be obtained, and the configuration information indicates multiple agents used for creating an application and jump information associated with the multiple agents. The jump information at least indicates that a first agent among the multiple agents can switch to a second agent to process a request. Further, a target application can be created based on the configuration information.
[0021] In this way, the embodiments of the present disclosure can support users to create an application based on multiple agents (for example, a bot based on multiple agents), and the application can process tasks by switching agents. Thus, the embodiments of the present disclosure can improve the scenario coverage of the application, thereby improving the problem handling ability of the application.
[0022] The following further describes various example implementations of this solution in detail with reference to the accompanying drawings.
[0023] Example environment
[0024] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. As Figure 1As shown, the example environment 100 may include an electronic device 110.
[0025] In this example environment 100, the electronic device 110 may run an application 120 that supports interface interaction. The application 120 may be any suitable type of application for interface interaction, examples of which may include, but are not limited to: development applications or other suitable applications that support application development. The user 140 may interact with the application 120 via the electronic device 110 and / or its attached devices.
[0026] In Figure 1 the environment 100, if the application 120 is active, the electronic device 110 may present an interface 150 for supporting the creation of an application through the application 120.
[0027] In some embodiments, the electronic device 110 communicates with the server 130 to implement the supply of services for the application 120. The electronic device 110 may 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 game terminals, VR / AR devices, Personal Communication System (PCS) devices, personal navigation devices, Personal Digital Assistant (PDA), audio / video players, digital cameras / video cameras, positioning devices, television receivers, radio broadcast receivers, e-book devices, game devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the electronic device 110 is also capable of supporting any type of interface for the user (such as a "wearable" circuit, etc.).
[0028] The server 130 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. The server 130 may include, for example, a computing system / server, such as a mainframe, an edge computing node, a computing device in a cloud environment, and so on. The server 130 may provide background services for the application 120 that supports virtual scenarios in the electronic device 110.
[0029] A communication connection can be established between server 130 and electronic device 110. The communication connection can be established by wired or wireless means. The communication connection can include, but is not limited to, a Bluetooth connection, a mobile network connection, a Universal Serial Bus (USB) connection, a Wireless Fidelity (WiFi) connection, etc., and the embodiments of the present disclosure are not limited in this regard. In the embodiments of the present disclosure, server 130 and electronic device 110 can implement signaling interaction through the communication connection therebetween.
[0030] It should be understood that the structures and functions of the various elements in environment 100 are described only for exemplary purposes, without implying any limitation to the scope of the present disclosure.
[0031] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.
[0032] Example process
[0033] Figure 2 A flowchart of a process 200 for creating an application according to some embodiments of the present disclosure is shown. Process 200 can be implemented at electronic device 110. The following will refer to Figure 1 to describe process 200.
[0034] As Figure 2 shown, at block 210, electronic device 110 obtains configuration information, where the configuration information indicates a plurality of agents used to create the application and jump information associated with the plurality of agents. In some embodiments, the jump information at least indicates that a first agent among the plurality of agents can switch to a second agent to process a request.
[0035] In some embodiments, electronic device 110 can support a user to configure a plurality of agents (e.g., two or more agents) included in the application and the jump relationship between the agents to create the application. The following will describe an example process of obtaining configuration information according to some embodiments of the present disclosure in conjunction with Figures 3A to 3F to describe.
[0036] In some embodiments, electronic device 110 can provide an editing interface 300A as Figure 3A shown. In interface 300A, electronic device 110 can support a user to create a node connection diagram 312. Such a node connection diagram can include a start node 302 and a plurality of nodes corresponding to a plurality of agents, for example, a node 304 corresponding to "agent 1", etc.
[0037] Additionally, electronic device 110 can also support indicating the jump relationship between the corresponding agents by adding connections between the nodes.
[0038] In some embodiments, the electronic device 110 may support a user in creating a new application. As an example, the electronic device 110 may create a first initial connection graph based on a request for creating a new application. Figure 3A As an example, the first initial connection graph may include a first initial node (e.g., node 304). For the scenario of creating a new application, the attribute information of the first initial node (e.g., node 304) may be empty.
[0039] Further, the electronic device 110 may create a final node connection graph 312 based on an editing operation on the first initial connection graph.
[0040] In some embodiments, the electronic device 110 may support a user in converting an existing application based on a single agent into an application based on multiple agents.
[0041] Specifically, the electronic device 110 may create a second initial connection graph based on a conversion request for an existing application associated with a single agent. In some embodiments, the second initial connection graph may include a second initial node (e.g., node 304 as shown) created based on the existing application. Figure 3A shown as node 304).
[0042] In some embodiments, different from the scenario of creating a new application, the attribute information of the agent (e.g., agent 1) corresponding to the second initial node may be determined based on the attributes of the existing application. That is, at least part of the attribute information associated with the existing application may be synchronized to the newly created application.
[0043] In some examples, the agent automatically created by converting an application based on a single agent may inherit the model information of the existing application. For example, in the case where the existing application is implemented based on a specific model, the agent may also be implemented based on that model.
[0044] In some other examples, the automatically created agent may inherit the plugin information of the existing application. For example, in the case where the existing application is configured with a set of plugins, the agent may also be correspondingly configured with that set of plugins.
[0045] In some other examples, the automatically created agent may inherit the workflow information of the existing application. For example, in the case where the existing application is configured with a specific workflow, the agent may also be correspondingly configured with that workflow.
[0046] In some other examples, the automatically created agent may inherit the knowledge information of the existing application. For example, in the case where the existing application is configured with a specific knowledge base, the agent may also be correspondingly configured with that specific knowledge base.
[0047] In some embodiments, the application to be converted may also inherit the guidance information of an existing application. For example, the guidance words for setting the existing application are used.
[0048] Based on this approach, the embodiments of the present disclosure can support converting an existing single-agent application into a multi-agent application and can improve the configuration efficiency of agents through information inheritance.
[0049] Continuing to refer to Figure 2 , the electronic device 110 can support a user to add one or more new nodes to the node connection graph 312 through the control 310. For example, the user can add new nodes corresponding to agents through the control 306.
[0050] As an example, as Figure 3B shown, the user can add a node 314 corresponding to "Agent 2" to the node connection graph 312 through the control 306.
[0051] Furthermore, as Figure 3C shown, the user can perform an attribute editing operation on a specific node included in the node connection graph. Taking the node 314 as an example, the electronic device 110 can support the user to edit the attributes of "Agent 2" corresponding to the node 314.
[0052] For example, the electronic device 110 can obtain the guidance information (also referred to as guidance words or guidance items) for this "Agent 2" through the control 316. This guidance information can be used to set the identity or capabilities of "Agent 2", for example.
[0053] In some embodiments, the guidance items obtained through the control 316 are also referred to as the private guidance items of "Agent 2", which are dedicated to "Agent 2". In some embodiments, during the actual operation of "Agent 2", the guidance information for "Agent 2" can be determined by splicing the global guidance items for the application to be created and this private guidance item. This guidance information can be provided to the model corresponding to "Agent 2" to set information such as its identity or capabilities.
[0054] In some embodiments, the electronic device 110 can support the user to input or edit the global guidance items for the application to be created. These global guidance items can act on all agents. For example, they are spliced with the private guidance items of the corresponding agents to generate the final guidance information.
[0055] Continuing to refer to Figure 3C , the electronic device 110 can also add corresponding capabilities for "Agent 2" through the control 318. Such capabilities can include, but are not limited to: plug-in capabilities, tool capabilities, and knowledge capabilities, etc.
[0056] Specifically, the electronic device 110 can configure, for example, the plug-in information, tool information, or knowledge base information of "Agent 2" through the control 318. The electronic device 110 can support adding one or more plug-ins, adding one or more tools, and / or adding one or more knowledge bases for "Agent 2".
[0057] Additionally, the electronic device 110 can also support the user to modify other attributes of "Agent 2" through the controls in the window 322. For example, the electronic device 110 can modify the name of "Agent 2" through the control 324; add a new agent with the same attributes to the node connection graph through the control 326; and delete the node 314 through the control 330.
[0058] Additionally, the electronic device 110 can also modify the model information of "Agent 2" through the control 328. As Figure 3D shown, the electronic device 110 can determine the model corresponding to "Agent 2" through the control 332, and modify the relevant parameters of the model through the control 334 or the control 336. For example, temperature and maximum response length.
[0059] In some embodiments, the attributes configured for the corresponding agent based on the node 314 above can be referred to as the private attribute information of the agent. The user can configure different private attribute information for different agents.
[0060] In addition to the private attribute information for the agent, the electronic device 110 can also support the user to configure global attribute information about the application to be created, which can act on all agents associated with the application. As an example, such global attribute information can include the global guidance items introduced above.
[0061] In some embodiments, the global attribute information can also include variable information associated with the application to be created. For example, the user can define global environment variables, user variables, etc., and such variables can be used by each agent.
[0062] In some embodiments, the global attribute information can also include the opening information associated with the application to be created. For example, such opening information can include the opening remarks when the application has its first conversation with the user. In some embodiments, the electronic device 110 can also support the user to configure opening information for a specific one or more agents, so that when such agents are activated, they can output the corresponding opening remarks.
[0063] In some embodiments, the global attribute information may further include suggested item information associated with the application to be created. For example, such suggested item information may include suggested interaction items provided when the application interacts with the user. In some embodiments, the electronic device 110 may also support the user to configure suggested item information for a specific one or more agents, so that when such an agent is activated, it can display corresponding suggested interaction items.
[0064] Continuing to refer to Figure 3C , the electronic device 110 can also configure the connection relationship of the nodes in the node connection diagram 312 through the control 320. Specifically, as Figure 3B shown, the electronic device 110 can establish a connection between the node 304 and the node 314 based on the jump condition (for example, condition 1) associated with the node 304 configured by the user.
[0065] As an example, this connection can indicate the jump relationship between "Agent 1" and "Agent 2", indicating that "Agent 1" can switch to "Agent 2" to process requests or execute tasks when "condition 1" is satisfied.
[0066] In some embodiments, the electronic device 110 can support the user to input text content through the control 320 to define any appropriate jump condition. As an example, the content of "condition 1" can be, for example, "when the user asks about the weather". Thus, "Agent 1" can switch to "Agent 2" to respond to the inquiry when it determines that the user's inquiry content is related to the weather.
[0067] In some embodiments, in order to support the jump from "Agent 1" to "Agent 2", a jump plugin corresponding to the jump condition (for example, condition 1) from "Agent 1" to "Agent 2" can be created. This enables "Agent 1" to independently determine whether to use this jump plugin in the current scenario to perform the switch from "Agent 1" to "Agent 2". In some examples, when a jump condition is created for "Agent 1", a suggested interaction item for "Agent 1" can also be generated based on this jump condition.
[0068] In some embodiments, the electronic device 110 can also support the user to only add connections between nodes without configuring corresponding jump conditions. For example, after the user configures the jump relationship from "Agent 1" to "Agent 2", "Agent 1" can determine whether to switch to "Agent 2" based on the description information of "Agent 2".
[0069] As an example, such descriptive information can, for example, indicate the capabilities of "Agent 2". For example, the descriptive information of "Agent 2" can indicate that "Agent 2" is suitable for tasks such as weather queries. Accordingly, when "Agent 1" receives an inquiry about the weather, it can determine that "Agent 2" is suitable for handling the inquiry and switch to "Agent 2".
[0070] Considering that as the number of nodes increases, in some scenarios, users may expect to configure global jump conditions. As Figure 3A shown, the electronic device 110 can also support the user to configure global jump information through the control 308. The global jump information can indicate that at least one other agent in the node connection graph except the target agent can switch to the target agent under a unified specific condition to process requests. In some embodiments, the global jump information can indicate that all agents in the node connection graph except the target agent can switch to the target agent under a unified specific condition to process requests.
[0071] As Figure 3E shown, after receiving the selection of the control 308, the electronic device 110 can add a global jump node 338 to the node connection graph 312. Further, the electronic device 110 can establish a connection from the global jump node 338 to the node 314 based on the user's configuration operation, and obtain the corresponding jump condition through the control 340.
[0072] Based on this configuration operation, for the application to be created, when all other agents except "Agent 2" are running, they can determine whether to switch to "Agent 2" based on the "global jump condition 2". This can also be understood as establishing jump relationships between all other nodes and the node 314.
[0073] By supporting the user to create global jump nodes, the embodiments of the present disclosure can further improve the user's editing efficiency.
[0074] In some embodiments, after the target application is published based on the node connection graph 312, the target application can perform switching between agents during the process of processing the target request. For example, the target application switches from "Agent 1" to "Agent 2" to process the target request. In this case, the context information associated with "Agent 1" can be provided to "Agent 2" for processing the target request. Such context information can include, for example, information such as the user's historical conversation with "Agent 1".
[0075] Thus, the embodiments of the present disclosure can not only achieve switching between agents, but also improve the accuracy of information processing by exchanging the context information of agents.
[0076] Thus, as discussed above, the electronic device 110 can support various types of editing operations by the user on the node connection diagram 312, such as adding new nodes, deleting existing nodes, editing node attributes, modifying node connection relationships, and so on.
[0077] In some embodiments, the electronic device 110 can also support the user in debugging the node connection diagram 312. As Figure 3F shown, the electronic device 110 can present a debugging interface 300F, which can include a dialogue area 342.
[0078] As Figure 3F shown, the electronic device 110 can obtain input information via an input control 344 in the dialogue area 342, and can display the output information of the application to be debugged in the dialogue area 342, such as output information 346 or output information 348.
[0079] In some embodiments, the electronic device 110 can display the agent that generates the output information 346 (e.g., "from agent 1") and the agent that generates the output information 348 (e.g., "from agent 2"), thus facilitating the user to debug the switching between agents.
[0080] In some embodiments, when a specific agent (e.g., agent 2) is used to process the corresponding input information, the electronic device 110 can also display indication information (e.g., "chat") in the corresponding node 314 to characterize that the "agent 2" corresponding to the node 314 is in a responsive state.
[0081] Additionally, the electronic device 110 can also support the user in switching to a specific agent in the node connection diagram 312. For example, the electronic device 110 can select the node 304 to indicate that "agent 1" is used for debugging. Further, when the user inputs new test content in the dialogue area 342, "agent 1" will be used to respond to the test content to generate the corresponding output content or switch to other agents according to the jump relationship.
[0082] It should be understood that although the acquisition of configuration information is discussed above with reference to the node connection diagram, the electronic device 110 can also support the user in inputting configuration information in other appropriate ways, for example.
[0083] As an example, the electronic device 110 can support the user in configuring multiple agents and the jump information between agents in a code editing manner, for example. Or, the electronic device 110 can also configure each agent and jump information through a data table or the like.
[0084] Continuing to refer to Figure 2, at block 220, the electronic device 110 creates a target application based on the configuration information.
[0085] As an example, the electronic device 110 may create a corresponding target application based on the configuration information. For example, a bot. Further, the bot may be published or shared with other users, for example.
[0086] In some embodiments, with the permission of the publisher, for example, it is also possible to support other users to create templates of published applications, and new applications can be created by editing the corresponding node connection diagram, thereby improving the efficiency of the application.
[0087] Example device and equipment
[0088] Embodiments of the present disclosure also provide corresponding devices for implementing the above methods or processes. Figure 4 FIG. shows a schematic structural block diagram of an example device 400 for creating an application according to certain embodiments of the present disclosure. The device 400 may be implemented as or included in the electronic device 110. Each module / component in the device 400 may be implemented by hardware, software, firmware, or any combination thereof.
[0089] As shown in Figure 4 , the device 400 includes an acquisition module 410 configured to acquire configuration information, where the configuration information indicates a plurality of agents for creating an application and jump information associated with the plurality of agents, and the jump information at least indicates that a first agent among the plurality of agents can switch to a second agent to process a request; a creation module 420 configured to create a target application based on the configuration information.
[0090] In some embodiments, the acquisition module 410 is specifically configured to: create a node connection diagram via an editing interface, where the node connection diagram includes a plurality of nodes corresponding to the plurality of agents, and the node connections in the node connection diagram indicate the jump relationships between the nodes; and determine the configuration information based on the node connection diagram.
[0091] In some embodiments, the acquisition module 410 is specifically configured to: receive a set of editing operations via an editing interface to create a node connection diagram, where the set of editing operations includes at least one of the following: adding a new node to the node connection diagram; deleting an existing node in the node connection diagram; editing the attributes of a node in the node connection diagram; modifying the connection relationship of a node in the node connection diagram.
[0092] In some embodiments, the acquisition module 410 is specifically configured to: create a first initial connection diagram based on a request for a new application, where the first initial connection diagram includes a first initial node and the attribute information of the first initial node is empty; and create a node connection diagram based on the first initial connection diagram.
[0093] In some embodiments, the obtaining module 410 is specifically configured to: create a second initial connection graph based on a conversion request for an existing application associated with a single agent, the second initial connection graph including second initial nodes created based on the existing application; and create a node connection graph based on the second initial connection graph.
[0094] In some embodiments, the second initial node corresponds to a third agent, and at least one attribute of the third agent is determined based on the attribute information of the existing application.
[0095] In some embodiments, the at least one attribute includes at least one of the following: model information associated with the third agent; plugin information associated with the third agent; workflow information associated with the third agent; knowledge information associated with the third agent.
[0096] In some embodiments, a first guiding item associated with a target application to be created is determined based on a second guiding item associated with the existing application.
[0097] In some embodiments, the configuration information includes global attribute information for multiple agents in the application.
[0098] In some embodiments, the global attribute information includes at least one of the following: a global guiding item associated with the target application; variable information associated with the target application; opening information associated with the target application; recommended item information associated with the target application.
[0099] In some embodiments, the configuration information includes private attribute information about multiple agents.
[0100] In some embodiments, the private attribute information includes at least one of the following: a private guiding item associated with the corresponding agent; model information associated with the corresponding agent; plugin information associated with the corresponding agent; workflow information associated with the corresponding agent; knowledge information associated with the corresponding agent.
[0101] In some embodiments, the guiding information of the corresponding agent is determined based on the private guiding item and the global guiding item associated with the target application.
[0102] In some embodiments, the apparatus 400 further includes a first receiving module configured to: receive a first configuration operation associated with a first agent, the first configuration operation indicating a first condition for switching from the first agent to a second agent.
[0103] In some embodiments, the first configuration operation includes inputting text content for indicating the first condition.
[0104] In some embodiments, the apparatus 400 further includes a plug-in creation module, configured to: create a jump plug-in corresponding to a first condition, such that a first agent can switch to a second agent by invoking the jump plug-in.
[0105] In some embodiments, whether the first agent switches to the second agent is determined based on the description information of the second agent.
[0106] In some embodiments, the configuration information includes global jump information, and the global jump information indicates that at least one other agent among a plurality of agents except a fourth agent can switch to the fourth agent under a second condition to process a request.
[0107] In some embodiments, the apparatus 400 further includes a node creation module, configured to: create a global jump node corresponding to the global jump information in an editing interface.
[0108] In some embodiments, during the process of a target application processing a target request, in response to the target application switching from a first agent to a second agent to process the target request, the context information associated with the first agent is provided to the second agent for processing the target request.
[0109] In some embodiments, the apparatus 400 further includes a first presentation module, configured to: present a debugging interface, the debugging interface including a dialogue area; a second receiving module, configured to receive first input information via the dialogue area; and a second presentation module, configured to present first output information of the target application and the agent that generates the first output information.
[0110] In some embodiments, the apparatus 400 further includes a third receiving module, configured to receive a selection of a target agent among a plurality of agents; a fourth receiving module, configured to receive second input information via the dialogue area; and a processing module, configured to process the second input information by using the target agent.
[0111] In some embodiments, the debugging interface further indicates the agent currently used to process the first input information.
[0112] Figure 5 A block diagram of an electronic device 500 in which one or more embodiments of the present disclosure can be implemented is shown. It should be understood that Figure 5 The illustrated electronic device 500 is merely exemplary and should not constitute any limitation to the functions and scopes of the embodiments described herein. Figure 5 The illustrated electronic device 500 can be used to implement Figure 1 the electronic device 110.
[0113] As Figure 5As shown, the electronic device 500 is in the form of a general-purpose electronic device. The components of the electronic device 500 may include, but are not limited to, one or more processors or processing units 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 may be an actual or virtual processor and is capable of performing various processes according to the programs stored in the memory 520. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing ability of the electronic device 500.
[0114] The electronic device 500 generally includes multiple computer storage media. Such media can be any accessible media that can be obtained by the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 may be a volatile memory (such as registers, caches, random access memory (RAM)), a non-volatile memory (such as read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 may be a removable or non-removable medium and may include a machine-readable medium, such as a flash drive, a magnetic disk, or any other medium that can be used to store information and / or data and can be accessed within the electronic device 500.
[0115] The electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in Figure 5 , a disk drive for reading from or writing to a removable, non-volatile magnetic disk (such as a "floppy disk") and an optical disk drive for reading from or writing to a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 520 may include a computer program product 525 having one or more program modules that are configured to perform the various methods or actions of the various embodiments of the present disclosure.
[0116] The communication unit 540 enables communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 500 may be implemented by a single computing cluster or multiple computer machines that are capable of communicating through a communication connection. Thus, the electronic device 500 may operate in a networked environment using a logical connection to one or more other servers, network personal computers (PCs), or another network node.
[0117] The input device 550 can be one or more input devices, such as a mouse, a keyboard, a trackball, etc. The output device 560 can be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 500 can also communicate with one or more external devices (not shown) as needed through the communication unit 540. The external devices such as a storage device, a display device, etc., communicate with one or more devices that enable a user to interact with the electronic device 500, or communicate with any device (e.g., a network card, a modem, etc.) that enables the electronic device 500 to communicate with one or more other electronic devices. Such communication can be performed via an input / output (I / O) interface (not shown).
[0118] According to an exemplary implementation of the present disclosure, there is provided a computer-readable storage medium having computer-executable instructions stored thereon, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, there is also provided a computer program product, the computer program product being tangibly stored on a non-transitory computer-readable medium and including computer-executable instructions, and the computer-executable instructions being executed by a processor to implement the method described above.
[0119] Aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.
[0120] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, when executed by the processing unit of the computer or other programmable data processing apparatus, generate an apparatus for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer-readable program instructions can also be stored in a computer-readable storage medium, which instructions cause a computer, a programmable data processing apparatus, and / or other devices to operate in a particular manner, so that the computer-readable medium storing the instructions includes a manufacture, which includes instructions for implementing various aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.
[0121] The computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device, such that a series of operation steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.
[0122] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various implementations of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a part of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions noted in the blocks may occur in a different order than noted in the accompanying drawings. For example, two consecutive blocks may actually be executed substantially in parallel, or they may sometimes be executed in the 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 by a dedicated hardware-based system that performs the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.
[0123] The various implementations of the present disclosure have been described above. The above description is exemplary, not exhaustive, and is not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art in the field of the present technology without departing from the scope and spirit of the described implementations. The choice of terms used herein is intended to best explain the principles of the implementations, the practical application, or the improvement of the technology in the market, or to enable other ordinary skilled persons in the field of the present technology to understand the various implementation manners disclosed herein.
Claims
1. A method for creating an application, comprising: Obtaining configuration information, where the configuration information indicates multiple agents used for creating the application and jump information associated with the multiple agents, and the jump information at least indicates that a first agent among the multiple agents can switch to a second agent to process a request; And Based on the configuration information, creating a target application.
2. The method according to claim 1, wherein obtaining the configuration information includes: Creating a node connection diagram via an editing interface, the node connection diagram including multiple nodes corresponding to the multiple agents, and the node connections in the node connection diagram indicating the jump relationships between the nodes; And Based on the node connection diagram, determining the configuration information.
3. The method according to claim 2, wherein creating a node connection diagram via an editing interface includes: Receiving a set of editing operations via the editing interface to create the node connection diagram, where the set of editing operations includes at least one of the following: Adding a new node to the node connection diagram; Deleting an existing node in the node connection diagram; Editing the attributes of a node in the node connection diagram; Modifying the connection relationships of the nodes in the node connection diagram.
4. The method according to claim 2, wherein creating a node connection diagram via an editing interface includes: Based on a request for creating a new application, creating a first initial connection diagram, the first initial connection diagram including a first initial node, and the attribute information of the first initial node being empty; And Based on the first initial connection diagram, creating the node connection diagram.
5. The method according to claim 2, wherein creating a node connection diagram via an editing interface includes: Based on a conversion request for an existing application associated with a single agent, creating a second initial connection diagram, the second initial connection diagram including a second initial node created based on the existing application; And Based on the second initial connection diagram, creating the node connection diagram.
6. The method according to claim 5, wherein the second initial node corresponds to a third agent, and at least one attribute of the third agent is determined based on the attribute information of the existing application.
7. The method according to claim 6, wherein the at least one attribute includes at least one of the following: Model information associated with the third agent; Plugin information associated with the third agent; Workflow information associated with the third agent; Knowledge information associated with the third agent.
8. The method according to claim 6, wherein a first guidance item associated with the target application to be created is determined based on a second guidance item associated with the existing application.
9. The method according to claim 1, wherein the configuration information includes global attribute information, and the global attribute information is for the multiple agents in the application.
10. The method according to claim 9, wherein the global attribute information includes at least one of the following: Global guidance item associated with the target application; Variable information associated with the target application; Opening information associated with the target application; Suggestion item information associated with the target application.
11. The method according to claim 1, wherein the configuration information includes private attribute information about the plurality of agents.
12. The method according to claim 11, wherein the private attribute information includes at least one of the following: A private boot item associated with the corresponding agent; Model information associated with the corresponding agent; Plugin information associated with the corresponding agent; Workflow information associated with the corresponding agent; Knowledge information associated with the corresponding agent.
13. The method according to claim 12, wherein the boot information of the corresponding agent is determined based on the private boot item and a global boot item associated with the target application.
14. The method according to claim 1, further comprising: Receiving a first configuration operation associated with the first agent, the first configuration operation indicating a first condition for switching from the first agent to the second agent.
15. The method according to claim 14, wherein the first configuration operation includes inputting text content for indicating the first condition.
16. The method according to claim 14, further comprising: Creating a jump plugin corresponding to the first condition, such that the first agent can switch to the second agent by invoking the jump plugin.
17. The method according to claim 1, wherein whether the first agent switches to the second agent is determined based on the description information of the second agent.
18. The method according to claim 1, wherein the configuration information includes global jump information, the global jump information indicating that at least one other agent among the plurality of agents except the fourth agent can switch to the fourth agent under a second condition to process a request.
19. The method according to claim 18, further comprising: Creating a global jump node corresponding to the global jump information in an editing interface.
20. The method according to claim 1, wherein: During the process of the target application processing a target request, in response to the target application switching from the first agent to the second agent to process the target request, the context information associated with the first agent is provided to the second agent for processing the target request.
21. The method according to claim 1, further comprising: Presenting a debugging interface, the debugging interface including a dialogue area; Receiving first input information via the dialogue area; And Presenting the first output information of the target application and the agent that generates the first output information.
22. The method according to claim 21, further comprising: Receiving a selection of a target agent among the plurality of agents; Receiving second input information via the dialogue area; And Processing the second input information using the target agent.
23. The method according to claim 21, wherein the debugging interface further indicates the agent currently used to process the first input information.
24. A device for creating an application, comprising: An acquisition module, configured to acquire configuration information, the configuration information indicating information for creating a plurality of agents in an application and jump information associated with the plurality of agents, the jump information at least indicating that: a first agent among the plurality of agents can switch to a second agent to process a request; And A creation module, configured to create a target application based on the configuration information.
25. An electronic device, comprising: At least one processing unit; And At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the electronic device to perform the method according to any one of claims 1 to 23.
26. A computer-readable storage medium, having stored thereon a computer program, the computer program being executable by a processor to implement the method according to any one of claims 1 to 23.
Citation Information
Cited By
Application creation method and apparatus, device, and storage medium
WO2025152665A1
