Agent-based data processing method, apparatus, device, medium, and product

Abstract

Embodiments of the present application provide a kind of data processing method, device, equipment, medium and product based on agent, which comprises: display the session page of target agent;Session page includes the session data of target agent;In response to the publishing operation of session data, publish target publishing content, the cover image of target publishing content is generated based on session data, and the content page of target publishing content includes the session entry of target agent.Using the embodiments of the present application, the cover image of publishing content can be generated based on the session data of agent, and the publishing content containing the cover image is published, the utilization rate of the session data of agent in application program is improved, and the intelligent degree of the business function of application program itself can also be improved.

Description

Data processing methods, devices, equipment, media, and products based on intelligent agents. Technical Field

[0001] This application relates to the field of computer technology, and in particular to data processing methods, apparatus, devices, media and products based on intelligent agents. Background Technology

[0002] With the rapid development of computer technology, the application scenarios of intelligent agents are becoming increasingly diverse, such as the ability to converse with intelligent agents within applications. Currently, after conversing with an intelligent agent within an application, it is impossible to integrate the conversation data between the application's users and the intelligent agent with the application's own business functions. This results in low utilization of the conversation data between the application's users and the intelligent agent within the application, and also a low level of intelligence in the application's own business functions. Summary of the Invention

[0003] This application provides a data processing method, apparatus, device, medium, and product based on intelligent agents. It can generate a cover image of published content based on conversation data with intelligent agents and publish the published content containing the cover image. This can improve the utilization rate of conversation data with intelligent agents in applications and also improve the intelligence level of the application's business functions.

[0004] On one hand, embodiments of this application provide a data processing method based on intelligent agents, which includes:

[0005] In response to a session request for a target agent triggered in the parent application, obtain page template data, which is used to generate a session page for having a session with at least one agent, the target agent being any one of the at least one agents;

[0006] The page template data is rendered to obtain the conversation page with the target agent, and the conversation page is displayed.

[0007] In response to dialogue information entered on the conversation page, the sub-application calls the conversation model corresponding to the target agent to generate the corresponding response information. The sub-application and the parent application have a subordinate relationship.

[0008] The reply information is rendered onto the chat page.

[0009] Accordingly, embodiments of this application provide an agent-based data processing device, which includes:

[0010] The processing unit is configured to, in response to a session request for a target agent triggered in the parent application, obtain page template data, which is used to generate a session page for engaging in a session with at least one agent, the target agent being any one of the at least one agents.

[0011] The display unit is used to render the page template data to obtain the conversation page with the target intelligent agent and display the conversation page;

[0012] The processing unit is also used to respond to the dialogue information entered in the conversation page, and generate the corresponding response information through the conversation model corresponding to the target intelligent agent by calling the sub-application. The sub-application and the parent application have a subordinate relationship.

[0013] The display unit is also used to render the reply information onto the conversation page.

[0014] On the other hand, embodiments of this application provide a data processing method based on intelligent agents, which includes:

[0015] The sub-application displays a conversation page with the target agent, which includes conversation data between the target agent and dialogue information and response information.

[0016] In response to a publish operation on session data, receive session data sent by the sub-application;

[0017] The parent application transforms and processes the session data to obtain multiple images to be published, determines the target content to be published including the multiple images to be published, and publishes the target content; there is a subordinate relationship between the parent application and the child application.

[0018] Accordingly, embodiments of this application provide an agent-based data processing apparatus, the agent-based data processing method comprising:

[0019] The display unit is used to display a conversation page with the target intelligent agent through a sub-application. The conversation page includes conversation data with the target intelligent agent, including dialogue information and response information.

[0020] The processing unit is used to receive session data sent by the sub-application in response to the operation of publishing session data;

[0021] The processing unit is also used to transform and process the session data through the parent application to obtain multiple images to be published, determine the target publishing content including the multiple images to be published, and publish the target publishing content; wherein, there is a subordinate relationship between the parent application and the child application.

[0022] On the other hand, embodiments of this application provide a computer device, which includes: a processor adapted to execute a computer program; and a computer-readable storage medium storing the computer program, wherein when the computer program is executed by the processor, it implements the above-described data processing method based on an intelligent agent.

[0023] On the other hand, embodiments of this application provide a computer-readable storage medium storing a computer program that is loaded by a processor and executed for the aforementioned agent-based data processing.

[0024] On the other hand, embodiments of this application provide a computer program product, which includes a computer program or computer instructions, which, when executed by a processor, implement the above-described agent-based data processing method.

[0025] In this embodiment, in response to a session request for a target agent triggered in the parent application, page template data can be obtained. The page template data can be used to generate a session page for engaging in a session with at least one agent. The page template data can be rendered to obtain the session page with the target agent and displayed. In response to dialogue information entered in the session page, a response message corresponding to the dialogue information can be generated by calling the session model corresponding to the target agent through a sub-application. The sub-application and the parent application have a subordinate relationship. The response message can be rendered onto the session page. As can be seen, the application can be used as the parent application, and smart agents can be accessed through sub-applications within the parent application. This allows smart agents to be integrated into the application. Furthermore, after a smart agent is integrated into the application, in response to a session request triggered within the application, a session page for the smart agent can be rendered within the application, enabling conversations with the smart agent within the application. In other words, the session page for the smart agent can be displayed directly within the application, and conversations can be conducted directly without navigating to other business platforms, thus improving the efficiency of conversations with smart agents within the application. In addition, for at least one smart agent integrated into the parent application, a session page for engaging with at least one smart agent can be rendered based on the same page template data. This ensures that the session pages for at least one smart agent integrated into the parent application have a unified style, improving the standardization of smart agent integration into the application. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1a is a schematic diagram of the architecture of a data processing system provided in an embodiment of this application;

[0028] Figure 1b is a schematic diagram of the architecture of another data processing system provided in an embodiment of this application;

[0029] Figure 2 is a flowchart illustrating the first agent-based data processing method provided in this application embodiment;

[0030] Figure 3a is a schematic diagram of an interface provided in an embodiment of this application, showing how a session request with an agent is triggered from the personal page of a parent application.

[0031] Figure 3b is a schematic diagram of an interface provided in an embodiment of this application, showing how a session request with an agent is triggered from the published content page of a parent application.

[0032] Figure 3c is a schematic diagram of an interface provided in an embodiment of this application, showing how a session request with an agent is triggered from the message page of a parent application.

[0033] Figure 3d is a schematic diagram of an interface provided in an embodiment of this application, showing a session request with an agent triggered from the search page of a parent application.

[0034] Figure 3e is a schematic diagram of an interface provided in an embodiment of this application, showing how a session request with an agent is triggered from the comment page of a parent application.

[0035] Figure 4 is a flowchart illustrating the second agent-based data processing method provided in the embodiments of this application;

[0036] Figure 5 is a schematic diagram of the calling process in a parent application client provided in an embodiment of this application;

[0037] Figure 6 is a schematic diagram of a technical framework for conversing with an intelligent agent in a parent application client according to an embodiment of this application.

[0038] Figure 7 is a flowchart illustrating the third agent-based data processing method provided in the embodiments of this application;

[0039] Figure 8a is a flowchart illustrating the fourth agent-based data processing method provided in the embodiments of this application;

[0040] Figure 8b is a schematic diagram of an interface for publishing session data as published content according to an embodiment of this application;

[0041] Figure 8c is a schematic diagram of an interface for selecting session data to be published according to an embodiment of this application;

[0042] Figure 8d is a schematic diagram of an interface where the number of selectable session data groups is fixed, according to an embodiment of this application.

[0043] Figure 8e is a schematic diagram of an interface for copying and deleting session data provided in an embodiment of this application;

[0044] Figure 9 is a flowchart illustrating the fifth agent-based data processing method provided in the embodiments of this application;

[0045] Figure 10 is a schematic diagram of a technical framework for integrating an intelligent agent in a parent application according to an embodiment of this application.

[0046] Figure 11 is a schematic diagram of a unified rendering standard provided in an embodiment of this application;

[0047] Figure 12 is a schematic diagram of another unified rendering standard provided in an embodiment of this application;

[0048] Figure 13 is a schematic diagram of the rendering result under a unified rendering standard provided in an embodiment of this application;

[0049] Figure 14 is a schematic diagram of the structure of a data processing device based on an intelligent agent provided in an embodiment of this application;

[0050] Figure 15 is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0051] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0052] This application proposes an agent-based data processing method. This method uses an application as a parent application, and at least one agent is accessed within the parent application through a sub-application, thereby improving the intelligence level of the parent application. Furthermore, to reduce the access cost of agents, a chatbox component can be used to provide standardized open capabilities for the access of at least one agent, enabling at least one agent to access the parent application in a standardized manner. The chatbox component can also manage the accessed at least one agent in a unified manner according to a unified standard.

[0053] Furthermore, this agent-based data processing method can respond to a session request triggered in the parent application for any connected agent (taking the connected agent as the target agent as an example). The parent application renders and presents the session page with the target agent through a sub-application. In other words, the session page with the target agent can be displayed directly in the parent application without jumping to the agent business platform outside the application, thereby improving the efficiency of the session with the agent in the application.

[0054] Furthermore, this agent-based data processing method can integrate the conversation data between the application's users and the agent with the application's own business functions. For example, it can be integrated with the application's content publishing function, allowing conversation data with the agent to be published as content (e.g., notes or social media updates); or it can be integrated with the application's sharing function, allowing conversation data with the agent to be shared as chat content; and so on. By integrating with the application's own business functions, not only can the utilization rate of conversation data with the agent be improved within the application, but the intelligence level of the application's own business functions can also be enhanced.

[0055] In the agent-based data processing method proposed in this application embodiment, technical terms such as application, parent application, child application, agent, and chatbox are involved. For ease of understanding, these technical terms are first introduced here:

[0056] ① An application program (APP) is a computer program developed to accomplish a specific task. The client for an application can run on a terminal device. Users of the application can interact with it through the client. The client can provide local services to users of the application on the terminal device. The client can also communicate with the server of the application through a communication network, and the server can provide service support to the client.

[0057] ② There can be a subordinate relationship between the parent application and the child application. The so-called subordinate relationship means that one application depends on another application in terms of functionality, resources or data. The dependent application can be called the child application (i.e., the subordinate application), and the application that is depended on can be called the parent application (i.e., the controlling application). For example, a map service application can be connected to a social media application in the form of a mini-program. There is a subordinate relationship between the social media application and the map service application.

[0058] In this context, the client corresponding to the parent application can be called the parent application client, and the server corresponding to the parent application can be called the parent application server. Similarly, the client corresponding to the child application can be called the child application client, and the server corresponding to the child application can be called the child application server.

[0059] Based on the hierarchical relationship between the parent and child applications, the parent application client can provide a child application container for running the child application client. The child application container is a lightweight application container technology that allows the child application client to run within the parent application client. It packages the child application client code together with the runtime environment provided by the parent application, forming a container that can run on the parent application client. When an object using the parent application opens the child application client on the parent application client, the parent application client can load the child application container and run the child application client code within it, thus enabling the child application client to run.

[0060] ③ An intelligent agent refers to an intelligent system with autonomous perception, decision-making, and execution capabilities. It can achieve goals through interaction with the environment. Essentially, it is a digital entity simulating the human cognitive framework, possessing a closed-loop capability of "perception → planning → action." In this application embodiment, the intelligent agent specifically refers to an AI (Artificial Intelligence) intelligent agent, which is an intelligent agent incorporating AI. The basis for the intelligent agent to engage in dialogue with the user of the parent application is the corresponding dialogue model. The corresponding dialogue model can be an AI model with language generation capabilities, used to generate response information corresponding to the dialogue information of the user. This application embodiment does not limit the type of dialogue model; for example, the dialogue model can be an LLM (Large Language Model).

[0061] ④ A chatbox is a tool within the parent application that provides users of the parent application with the ability to communicate with agents. To achieve this communication capability, the chatbox can provide the parent application with standardized access and management capabilities for agents. Furthermore, the chatbox can be used to carry the communication link between the agent and users of the parent application; the communication link refers to the complete communication process between the parent application and the corresponding communication model of the agent.

[0062] ⑤ Published content refers to content published within the parent application. For example, published content may include notes or social media updates published within the parent application.

[0063] ⑥ In response to the conditions or states on which the performed operation depends, one or more operations may be performed in real time or with a set delay when the conditions or states are met; unless otherwise specified, there is no restriction on the order in which the multiple operations are performed. For example, for "in response to a session request for the target agent triggered in the parent application, retrieve page template data", the operation is "retrieve page template data", and the condition on which this operation depends is "a session request for the target agent triggered in the parent application".

[0064] ⑦ Triggering Operation: A triggering operation refers to an action performed by a user object of the parent application on the parent application (including child applications). For example, a triggering operation is an action performed by a user object of the parent application on a control within the parent application. Triggering operations here could include single-click, double-click, and long-press.

[0065] The architecture of the data processing system provided in the embodiments of this application will now be described with reference to the accompanying drawings.

[0066] Intelligent agents can access a parent application through sub-applications. Specifically, the access methods can include either of the following: First, an intelligent agent can access the parent application as a sub-application; second, at least one intelligent agent can access the same sub-application of the parent application as an intelligent agent instance, where one intelligent agent corresponds to one intelligent agent instance in the sub-application. Here, an intelligent agent instance refers to the access method of the intelligent agent in the sub-application, and the intelligent agent instance can provide the interaction capability between the user objects of the parent application and the intelligent agent within the sub-application. The architecture of the data processing system under these two access methods is described below:

[0067] As shown in Figure 1a, an intelligent agent accesses the data processing system of the parent application as a sub-application. The data processing system may include a terminal device 101, a sub-application server 102, a parent application server 103, and a business server 104. Devices that need to communicate can establish direct communication connections via wired communication or indirect communication connections via wireless communication. This embodiment of the application does not limit the specific method used.

[0068] Terminal device 101 can run a client corresponding to a parent application (i.e., parent application client), and the parent application client can run a client corresponding to a sub-application (i.e., sub-application client). Taking the integration of a first intelligent agent and a second intelligent agent in the parent application as an example, the parent application client can run a client corresponding to the first sub-application of the first intelligent agent (hereinafter referred to as the first sub-application client), and a client corresponding to the second sub-application of the second intelligent agent (hereinafter referred to as the second sub-application client).

[0069] Sub-application server 102 can be used to provide service support for sub-application clients. Taking the integration of a first agent and a second agent in the parent application as an example, sub-application server 102 can include server 1021 corresponding to the first sub-application of the first agent (hereinafter referred to as first sub-application server 1021) and server 1022 corresponding to the second sub-application of the second agent (hereinafter referred to as second sub-application server 1022). Parent application server 103 can be used to provide service support for parent application clients. The data processing system shown in Figure 1a takes the integration of sub-application server 102 and parent application server 103 in different devices as an example. Optionally, sub-application server 102 and parent application server 103 can also be integrated in the same device. For example, sub-application server 102 can be integrated into parent application server 103. It can be understood that sub-application server 102 can be integrated into parent application server 103 as a service module of parent application server 103.

[0070] The session model corresponding to the intelligent agent can be deployed in the application server (e.g., in the sub-application server 102), or it can be deployed in the business server that provides the relevant services for the intelligent agent. The data processing system shown in Figure 1a takes the example of deploying the session model corresponding to the first intelligent agent in the first sub-application server 1021 and the session model corresponding to the second intelligent agent in the business server 104 that provides the relevant services for the second intelligent agent.

[0071] In the data processing system shown in Figure 1a, taking the first intelligent agent as an example (the second intelligent agent is similar to the first intelligent agent), the process of waking up the conversation page with the first intelligent agent in the parent application client may include: responding to the conversation request for the first intelligent agent triggered in the parent application client, obtaining page template data, rendering the page template data to obtain the conversation page with the first intelligent agent, and displaying the conversation page with the first intelligent agent.

[0072] In the data processing system shown in Figure 1a, taking the first intelligent agent as an example, the conversation flow between the intelligent agent and the corresponding conversation model deployed in the sub-application server 102 in the parent application may include: responding to the dialogue information entered in the conversation page with the first intelligent agent, the first sub-application client calls the conversation model corresponding to the first intelligent agent in the first sub-application server 1021 to generate the reply information corresponding to the dialogue information; the reply information may be rendered to the conversation page with the first intelligent agent.

[0073] In the data processing system shown in Figure 1a, taking the second agent as an example, the conversation flow between the agent and the corresponding conversation model deployed in the business server 104 in the parent application can include: responding to the dialogue information entered in the conversation page with the second agent, sending the dialogue information to the second sub-application server 1022 through the second sub-application client; the second sub-application server 1022 can call the conversation model corresponding to the second agent in the business server 104 to generate the reply information corresponding to the dialogue information; the second sub-application server 1022 can send the reply information to the second sub-application client, and can render the reply information in the conversation page with the second agent.

[0074] In the data processing system shown in Figure 1a, taking the first intelligent agent as an example (the second intelligent agent is similar to the first intelligent agent), the process of publishing the session data with the first intelligent agent as published content in the parent application can include: in response to the publishing operation of the session data, the parent application client can receive the session data sent by the first sub-application client; the parent application client can send the session data to the parent application server 103, and the parent application server 103 can perform conversion processing on the session data to obtain multiple images to be published, and determine the published content including the multiple images to be published; the parent application server 103 can send the published content to the parent application client, and the parent application client renders the published content to the published content page to publish the published content.

[0075] As can be seen, in the data processing system shown in Figure 1a, agents can be accessed as sub-applications within the parent application, with one agent corresponding to one sub-application. A session request triggered within the parent application can quickly launch a session page with the agent, enabling dialogue and improving session efficiency. Furthermore, session data with the agent can be published within the parent application, making the published content of the parent application intelligent and diverse.

[0076] As shown in Figure 1b, at least one intelligent agent accesses the data processing system within the same sub-application of the parent application as an intelligent agent instance. The data processing system may include a terminal device 101, a sub-application server 102, a parent application server 103, and a business server 104. Devices requiring communication can establish direct communication connections via wired communication or indirect communication connections via wireless communication; this embodiment does not limit the specific method used.

[0077] Terminal device 101 can run a client corresponding to a parent application (i.e., the parent application client), and the parent application client can run a client corresponding to a sub-application (i.e., the sub-application client). Taking the integration of a first agent and a second agent in the same sub-application of the parent application as an example, the sub-application client can include an agent instance corresponding to the first agent (hereinafter referred to as the first agent instance) and an agent instance corresponding to the second agent (hereinafter referred to as the second agent instance). The first agent instance can be used to provide the interaction capability between the user of the parent application and the first agent, and the second agent instance can be used to provide the interaction capability between the user of the parent application and the second agent.

[0078] Sub-application server 102 can be used to provide service support for sub-application clients, and parent application server 103 can be used to provide service support for parent application clients. The data processing system shown in Figure 1b takes the integration of sub-application server 102 and parent application server 103 in different devices as an example. Optionally, sub-application server 102 and parent application server 103 can also be integrated in the same device. For example, sub-application server 102 can be integrated into parent application server 103. This can be understood as sub-application server 102 being integrated into parent application server 103 as a service module of parent application server 103.

[0079] The session model corresponding to the intelligent agent can be deployed in the application server (e.g., in the sub-application server 102), or it can be deployed in the business server that provides the relevant services for the intelligent agent. The data processing system shown in Figure 1b takes the deployment of the session model corresponding to the first intelligent agent in the sub-application server 102 and the deployment of the session model corresponding to the second intelligent agent in the business server 104 that provides the relevant services for the second intelligent agent as an example.

[0080] In the data processing system shown in Figure 1b, taking the first intelligent agent as an example (the second intelligent agent is similar to the first intelligent agent), the process of activating the conversation page with the first intelligent agent in the parent application client may include: responding to the conversation request for the first intelligent agent triggered in the parent application client, obtaining page template data; rendering the page template data to obtain the conversation page with the first intelligent agent, and displaying the conversation page with the first intelligent agent.

[0081] In the data processing system shown in Figure 1b, taking the first intelligent agent as an example, the conversation flow between the intelligent agent in the parent application and the corresponding conversation model deployed in the sub-application server 102 may include: responding to the dialogue information entered in the conversation page with the first intelligent agent, the first intelligent agent instance in the sub-application client calls the conversation model corresponding to the first intelligent agent in the sub-application server 102 to generate the reply information corresponding to the dialogue information; the reply information may be rendered to the conversation page with the first intelligent agent.

[0082] In the data processing system shown in Figure 1b, taking the second agent as an example, the conversation flow between the agent and the corresponding conversation model deployed in the business server 104 in the parent application can include: responding to the dialogue information entered in the conversation page with the second agent, the dialogue information can be sent to the sub-application server 102 through the second agent instance in the sub-application client; the sub-application server 102 can call the conversation model corresponding to the second agent in the business server 104 to generate the reply information corresponding to the dialogue information; the reply information can be rendered on the conversation page with the second agent.

[0083] In the data processing system shown in Figure 1b, taking the first intelligent agent as an example (the second intelligent agent is similar to the first intelligent agent), the process of publishing the session data with the first intelligent agent as published content in the parent application can include: in response to the publishing operation of the session data, the parent application client can receive the session data sent by the first intelligent agent instance; the parent application client can send the session data to the parent application server 103, and the parent application server 103 can perform conversion processing on the session data to obtain multiple images to be published, and determine the published content including the multiple images to be published; the parent application server 103 can send the published content to the parent application client, and the parent application client renders the published content to the published content page to publish the published content.

[0084] As can be seen in the data processing system shown in Figure 1b, at least one agent can be integrated into the same sub-application within the parent application. Each agent corresponds to an instance of an agent within the sub-application. By triggering a session request in the parent application, a session page with the agent can be quickly invoked, enabling a conversation with the agent and improving the efficiency of the conversation. Furthermore, the session data with the agent can be published within the parent application, making the published content of the parent application intelligent and diversified.

[0085] The data processing systems shown in Figures 1a and 1b are intended to more clearly illustrate the technical solutions of the embodiments of this application and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0086] The terminal devices mentioned in the embodiments of this application include, but are not limited to, smartphones, tablets, smart wearable devices, smart voice interaction devices, smart home appliances, personal computers, vehicle terminals, smart cameras, etc., and this application does not impose any limitations on them. A server 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, CDN (Content Delivery Network), and big data and artificial intelligence platforms, but is not limited to these.

[0087] The data processing method based on intelligent agents provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0088] This application proposes a data processing method based on an intelligent agent. The method may include: triggering the display of a conversation page with the intelligent agent from different pages of a parent application, and the technical process of conversing with the intelligent agent within the parent application. This data processing method can be executed by a terminal device, specifically by a parent application running on the terminal device. As shown in Figure 2, the data processing method may include, but is not limited to, the following steps S201-S204:

[0089] S201, in response to a session request for a target agent triggered in the parent application, obtain page template data, which is used to generate a session page for having a session with at least one agent, the target agent being any one of the at least one agents.

[0090] S202, render the page template data to obtain the conversation page with the target agent, and display the conversation page.

[0091] In steps S201-S202, a session request for the target agent can be triggered on different pages of the parent application (specifically, the parent application client). For example, a session request for the target agent can be triggered on any page of the parent application, such as the personal page, content posting page, message page, search page, and comment page, thereby triggering the display of the session page with the target agent. The triggering methods for session requests for the target agent on these pages are described below:

[0092] (1) Personal Page:

[0093] The target agent's personal page can be displayed through the parent application. A session request can be generated in response to a session trigger action on the personal page, triggering the display of the session page with the target agent. Here, the personal page refers to the page in the parent application used to display personal information and published content. The target agent's personal page refers to the page using the target agent as the account holder, used to display the target agent's introductory information and published content.

[0094] The session triggering operation for the personal page can include any of the following: First, as shown in FIG3a, the personal page 30 of the target intelligent agent can include a session entry 301 with the target intelligent agent. In response to the triggering operation of the session entry 301, a session request can be generated, triggering the display of the session page 80 with the target intelligent agent. The triggering operation here can include, for example, a single click, a double click, and a long press, etc., which are not limited in this embodiment. Second, during the process of the parent application displaying the personal page of the target intelligent agent, a session request can be generated in response to the gravity sensing operation performed on the terminal device running the parent application. For example, the gravity sensing operation can include a shaking operation and a rotation operation, etc., which are not limited in this embodiment. Third, a session request can be generated in response to a gesture triggering operation performed on the personal page of the target intelligent agent. A gesture triggering operation refers to the operation of drawing a specific pattern on the personal page using a specific gesture, for example, the operation of drawing the letter "A" on the personal page using the index finger.

[0095] Optionally, in addition to being set on the target intelligent agent's personal page, the session entry point with the target intelligent agent can also be set on the personal page of any object in the parent application. In response to the triggering operation of the session entry point with the target intelligent agent on the personal page of any object, a session request can be generated, and a session can be initiated with the target intelligent agent. Alternatively, a session can be initiated with the target intelligent agent based on the content in the object's personal page.

[0096] (2) Content publishing page:

[0097] A publishing content page can be displayed through the parent application. This publishing content page may include a session entry point with the target agent. A session request can be generated in response to a session trigger operation on the session entry point. Here, the publishing content page refers to the page in the parent application used to display the published content. Specifically, as shown in Figure 3b, the publishing content page 31 of any object (e.g., the first object in Figure 3b) may include an agent invocation entry point 311. In response to a trigger operation on the agent invocation entry point 311, an agent entry list 312 can be displayed. The agent entry list 312 may include session entries with at least one agent. Among the session entries with at least one agent, there may be a session entry point 301 with the target agent. A session request can be generated in response to a trigger operation on the session entry point 301, triggering the display of the session page 80 with the target agent.

[0098] (3) Messages page:

[0099] As shown in Figure 3c, message page 32 can be displayed through the parent application. Message page 32 refers to a page in the parent application used to display conversation messages with at least one object. Message page 32 may include conversation messages with at least one object (e.g., a target agent and a first object). The at least one object may include a target agent, that is, the message page may include conversation message 321 with the target agent. A conversation request can be generated in response to a conversation triggering operation for the target agent in message page 32. Here, the conversation triggering operation may refer to the triggering operation for the conversation message 321 with the target agent in message page 32. This can trigger the display of conversation page 80 with the target agent.

[0100] (4) Search page:

[0101] A search page can be displayed through the parent application. The search page may include a session entry point with the target agent. A session request can be generated in response to a session trigger operation on the session entry point. Here, the search page refers to the page in the application used to provide search functionality. Specifically, as shown in Figure 3d, the search page 33 of the parent application may include an agent entry list 312. The agent entry list 312 may include session entries with at least one agent. The session entries with at least one agent may include a session entry point 301 with the target agent. A session request can be generated in response to a trigger operation on the session entry point 301, triggering the display of the session page 80 with the target agent.

[0102] (5) Comments page:

[0103] A comment page can be displayed through the parent application. The comment page refers to the page within the parent application used for posting and interacting with comments. The comment page can include comment content with the target agent and can generate a session request in response to a session trigger operation on the target agent within the comment page. Specifically, as shown in Figure 3e, the comment page 34 of the parent application can include comment content 341 with the target agent. The comment content 341 with the target agent can include a session entry point 301 with the target agent. A session request can be generated in response to a trigger operation on the session entry point 301, triggering the display of the session page 80 with the target agent.

[0104] As can be seen, the embodiments of this application can support triggering session requests for the target intelligent agent in different pages of the parent application, which can improve the efficiency of waking up the intelligent agent in the parent application, thereby improving the session efficiency with the intelligent agent in the parent application.

[0105] In step S201, in response to a session request triggered in the parent application for the target agent, page template data can be obtained. This page template data can be used to generate a session page for engaging with at least one agent. The page template data can define a unified page framework for the session page engaging with at least one agent. This unified page framework refers to the various areas included in the session page and the information that can be displayed in each area. This allows the page template data to be used to generate a session page for engaging with at least one agent according to a unified session page style; that is, the session page style for engaging with at least one agent is consistent.

[0106] In detail, the page template data may include basic area data, conversation information area data, and input area data. The unified page framework may include a basic area, a conversation information area, and an input area. The basic area can be used to display global control controls for the agent (e.g., controls that trigger reporting of the agent, viewing historical conversation data, etc.), the conversation information area can be used to display conversation data, and the input area can be used to display input boxes for dialogue information, conversation control controls (e.g., new dialogue controls and extended function controls (e.g., deep thinking controls and network search controls)), and controls that trigger external sending functions (e.g., controls that trigger sending dialogue information, and controls that trigger album and photo functions, etc.).

[0107] In step S202, after obtaining the page template data, the page template data can be rendered to obtain the conversation page with the target agent, and the conversation page can be displayed. Specifically, the base area data can be rendered to obtain the base area of ​​the conversation page with the target agent, the conversation information area data can be rendered to obtain the conversation information area of ​​the conversation page with the target agent, and the input area data can be rendered to obtain the input area of ​​the conversation page with the target agent. It can be seen that in this case, the conversation pages with each agent are rendered based on the same page template data. This not only ensures that the style of the conversation pages with each agent is consistent, but also that the content of the conversation pages with each agent is completely identical.

[0108] Optionally, page content data corresponding to the target agent can also be obtained. The page content data may include at least one of the following: configuration data corresponding to the target agent and historical session data with the target agent. The configuration data corresponding to the target agent may be customized during the access process of the target agent. The configuration data corresponding to the target agent may include, but is not limited to: basic area configuration data corresponding to the target agent (e.g., may include the identifier of the target agent displayed in the basic area), welcome information configuration data corresponding to the target agent (e.g., may include the welcome message displayed when having the first session with the target agent in the session information area), and extended function control configuration data corresponding to the target agent (e.g., may include extended function controls displayed in the input area).

[0109] In this scenario, the page template data and the page content data corresponding to the target agent can be rendered to obtain the conversation page with the target agent. Specifically, the basic area data and the basic area configuration data corresponding to the target agent can be rendered to obtain the basic area of ​​the conversation page with the target agent; the conversation information area data and the historical conversation data with the target agent (or the welcome message configuration data corresponding to the target agent) can be rendered to obtain the conversation information area of ​​the conversation page with the target agent; and the input area data and the extended function control configuration data corresponding to the target agent can be rendered to obtain the input area of ​​the conversation page with the target agent. As can be seen, in this case, the conversation pages with each agent are rendered based on the same page template data. This ensures that the style of the conversation pages with each agent is consistent. Furthermore, since the page content data corresponding to each agent is custom-configured and can be different, the page content of the conversation pages with each agent can be different. For example, the identifiers of each agent in the basic area are different, the historical conversation data with each agent in the conversation information area are different, the welcome messages for each agent in the conversation information area can be different, and the extended function controls for each agent in the input area can be different. This improves the flexibility of agent access.

[0110] S203, in response to the dialogue information entered on the conversation page, the sub-application calls the conversation model corresponding to the target agent to generate the response information corresponding to the dialogue information. The sub-application and the parent application have a subordinate relationship.

[0111] Before step S203, the dialogue information can be preprocessed by a sub-application to obtain preprocessed dialogue information. After preprocessing, in step S203, the sub-application can call the conversation model corresponding to the target agent to generate response information corresponding to the preprocessed dialogue information. Preprocessing refers to assembling information into the dialogue information that helps the conversation model corresponding to the target agent generate response information. During preprocessing, the information assembled into the dialogue information may include reference information and / or response patterns. Wherein:

[0112] ①Reference Information:

[0113] For cases where reference information is assembled for dialogue information, the reference information can be obtained through a sub-application (specifically, a sub-application server). The sub-application then assembles and processes the reference information and dialogue information to obtain preprocessed dialogue information. Subsequently, the sub-application can call the dialogue model corresponding to the target agent to generate response information based on the reference information and dialogue information.

[0114] The reference information refers to the information consulted by the conversation model corresponding to the target agent when generating response information for the dialogue. Reference information may include, but is not limited to, at least one of the following: contextual information of the interaction between the user and the target agent (e.g., historical conversation data between the user and the target agent, and historical comment interaction data between the user and the target agent, etc.), the content published by the target agent, the object characteristic information of the user, and the operational characteristic information of the user (e.g., published content previously visited by the user, etc.). By providing reference information to the conversation model corresponding to the target agent, the conversation model can learn the knowledge provided by the reference information and generate response information for the dialogue based on the learned knowledge, thereby improving the accuracy of the response information and the adaptability of the response information to the user.

[0115] Furthermore, the reference information can be matched with the triggering scenario corresponding to the session request. The triggering scenario refers to the context of the page that generated the session request, such as a personal page scenario, a message page scenario, or a comment page scenario. Matching means that different triggering scenarios can correspond to different types of reference information, and the type of reference information obtained corresponds to the triggering scenario of the current session request. For example, if the triggering scenario for the session request is a personal page scenario, then the obtained reference information may include the content published by the target agent and the historical session data between the user and the target agent; similarly, if the triggering scenario for the session request is a comment page scenario, then the obtained reference information may include the historical comment interaction data between the user and the target agent on the comment page. By specifying that the reference information matches the triggering scenario corresponding to the session request, the accuracy of the reference information can be improved, thereby improving the accuracy of the response information.

[0116] ② Answer format:

[0117] When assembling response patterns for dialogue information, the response patterns can be obtained through a sub-application (specifically, a sub-application server). The sub-application then assembles the response patterns and dialogue information to obtain pre-processed dialogue information. Subsequently, the sub-application can call the dialogue model corresponding to the target agent to generate response information based on the response patterns.

[0118] In this context, "response pattern" refers to the information pattern of the reply message, specifically its style. The response pattern instructs the conversational model corresponding to the target agent to generate reply messages according to a specified style. Response patterns can include, but are not limited to, any of the following: chat mode and associated word mode. Chat mode instructs the conversational model to return a more casual and lighthearted reply message, while associated word mode instructs the model to predict, based on context, what the user wants to know and generate at least one associated text (each associated text not exceeding 16 characters), separated by commas. By providing the response pattern to the conversational model of the target agent, the model can generate reply messages in a specified style, thus improving the accuracy of the replies.

[0119] Furthermore, the response pattern can be matched with the corresponding conversation scenario of the conversation page. The conversation scenario refers to the type of conversation triggered by the user on the conversation page. For example, manually entering dialogue information on the conversation page triggers a chat type, and the corresponding conversation scenario is a chat scenario. Similarly, automatically entering dialogue information through preset automatic questioning methods on the conversation page (e.g., clicking the "Learn More" control) triggers a word association scenario, and the corresponding conversation scenario is a word association scenario. Matching means that different conversation scenarios can correspond to different response patterns. The obtained response pattern corresponds to the current conversation scenario; for example, a chat scenario corresponds to a chat mode, and a word association scenario corresponds to a word association mode. By specifying that the response pattern matches the corresponding conversation scenario, the adaptability between the response pattern and the conversation scenario can be improved, thereby increasing the accuracy of the reply information and ensuring that the reply information is adapted to the conversation scenario.

[0120] Optionally, at least one extended function control (included in the previously mentioned conversation operation controls) can also be displayed on the conversation page. Each extended function control can correspond to a different answer generation strategy. The answer generation strategy refers to the strategy adopted by the conversation model when generating response information corresponding to the dialogue information. It can be used to instruct the conversation model on the thinking process used when generating response information. For example, at least one extended function control can include a deep thinking control and a web search control. The answer generation strategy corresponding to the deep thinking control is a deep thinking strategy, and the answer generation strategy corresponding to the web search control is a web search strategy. The deep thinking strategy can instruct the conversation model to analyze the dialogue information based on the training knowledge base and logical reasoning when generating response information, providing logically rigorous and well-organized response information. The web search strategy can instruct the conversation model to enhance the timeliness and data support of the response by acquiring internet information in real time.

[0121] Based on this, in response to a trigger operation on a target extended function control in at least one extended function control, and dialogue information entered on the conversation page, the sub-application can call the conversation model corresponding to the target agent to generate reply information corresponding to the dialogue information according to the answer generation strategy corresponding to the target extended function control.

[0122] As can be seen, users can control whether the response generation strategy corresponding to the extended function control is enabled or disabled by triggering or not triggering the extended function control. This controls whether the conversation model generates the response information corresponding to the dialogue information according to the corresponding response generation strategy. This can improve the controllability of the conversation between users and the agent and make the response information more compatible with the needs of users.

[0123] S204, render the reply information to the chat page.

[0124] In step S204, the content type of the reply information can be determined, and a rendering service matching the content type of the reply information can be called to render the reply information, thereby obtaining the rendered reply information, which can then be displayed on the session page.

[0125] In other words, this application embodiment can provide multiple rendering services, each corresponding to a specific content type. Each rendering service can provide rendering capabilities for its corresponding content type, and can invoke the rendering capabilities provided by the rendering service corresponding to the content type of the reply information to render the reply information onto the conversation page. Therefore, by providing rendering capabilities for multiple content types, a better rendering effect can be achieved for reply information containing multiple content types.

[0126] For example, services such as Markdown content rendering, rich text content rendering, thought chain content rendering, and thinking content rendering can be provided. Markdown is a lightweight markup language; Markdown content refers to content written in Markdown, and the Markdown content rendering service provides rendering capabilities for Markdown content. Rich text is a text format that includes various formats; rich text content is content written in rich text, and the rich text content rendering service provides rendering capabilities for rich text content. Thought chain is an artificial intelligence technology that simulates human thinking steps to break down logically complex problems. Through a series of logically related thoughts, a complete thinking process is formed, enabling the corresponding conversation model of the intelligent agent to understand the problem more deeply and provide answers; thought chain content refers to content organized in the form of thought chains, and the thought chain rendering service provides rendering capabilities for thought chain content. Thinking content refers to content used to describe the thinking process of the conversation model in generating response information; the thinking content rendering service can be set up for deep thinking strategies, and it provides rendering capabilities for thinking content.

[0127] In this embodiment, an agent can be accessed through a sub-application that depends on the parent application. This allows for conversations with the agent within the parent application without needing to navigate outside of it, improving the efficiency of conversations within the parent application. Furthermore, it supports triggering conversation requests for a target agent from different pages within the parent application, further improving the efficiency of invoking the agent within the parent application and thus enhancing conversation efficiency. The sub-application can assemble reference information and / or a response model for the dialogue information input by the user object. When the conversation model corresponding to the agent is called to generate response information for the dialogue information, the conversation model can learn the instructions in the reference information and / or generate response information according to the style indicated by the response model, improving the accuracy of the response information. Additionally, the reference information can be matched with the triggering scenario of the conversation request, ensuring that the response information generated based on the reference information is adapted to the triggering scenario, thus improving the generation effect of the response information. The response mode can be matched with the conversation scenario of the conversation page, ensuring that the response information generated based on the response mode is adapted to the style of the conversation scenario, further improving the generation effect of the response information. In addition, the conversation page can provide extended functionality controls to users. Users can use these controls to enable or disable the corresponding answer generation strategy, thereby controlling whether the conversation model generates response information according to the corresponding response generation strategy, so that the response information can better meet the needs of users.

[0128] This application proposes a data processing method based on an intelligent agent. The method may include: an intelligent agent accessing the rendering and session processes of a parent application as a sub-application. As shown in Figure 4, this data processing method may include, but is not limited to, the following steps S401-S404:

[0129] S401, in response to a session request for a target agent triggered in the parent application, the sub-application corresponding to the target agent is invoked to obtain page template data. The page template data is used to generate a session page for having a session with at least one agent, where the target agent is any one of the at least one agents.

[0130] In step S401, one agent accessing the parent application corresponds to one sub-application. This can be understood as the agent accessing the parent application as a sub-application. Page template data can be stored in the sub-application container or session component. In response to a session request triggered in the parent application (specifically, the parent application client) for the target agent, the sub-application corresponding to the target agent can be invoked to retrieve the page template data from the sub-application container or session component.

[0131] Optionally, the sub-application corresponding to the target agent (specifically, the sub-application client corresponding to the target agent) can be invoked to obtain the page content data corresponding to the target agent, that is, to obtain the configuration data and historical session data with the target agent (if historical session data with the target agent exists). The configuration data corresponding to the target agent can be managed by the sub-application server corresponding to the target agent, and the sub-application client can be invoked to obtain the configuration data from the sub-application server. The historical session data with the target agent can be managed by the parent application (specifically, the parent application server), and the sub-application client can be invoked to obtain the historical session data from the parent application server; alternatively, the historical session data with the target agent can be managed by the sub-application server corresponding to the target agent, and the sub-application client can be invoked to obtain the historical session data from the sub-application server.

[0132] S402, call the sub-application corresponding to the target agent to render the page template data, obtain the session page corresponding to the target agent, and display the session page.

[0133] In step S402, the sub-application corresponding to the target agent (specifically, the sub-application client corresponding to the target agent) can be invoked to render the page template data and the page content data corresponding to the target agent, thereby obtaining a conversation page with the target agent. The sub-application corresponding to the target agent (specifically, the sub-application client corresponding to the target agent) can then be invoked to display the conversation page. The specific rendering process of the conversation page can be found in the description of step S202 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0134] The above steps S401-S402 describe how the conversation page with the target intelligent agent can be rendered by the sub-application corresponding to the target intelligent agent. Optionally, the conversation page with the target intelligent agent can also be rendered by the parent application (specifically, the parent application client). Specifically, the parent application (specifically, the parent application client) can obtain page template data and page content data. The page content data may include configuration data corresponding to the target agent and historical session data with the target agent (if historical session data with the target agent exists). For page template data, the parent application client can receive page template data sent by the sub-application client corresponding to the target agent, or the parent application client can obtain page template data from the parent application server. The page template data may be stored in the parent application server after the parent application client first receives the page template data from the sub-application client corresponding to the target agent. For configuration data corresponding to the target agent, the parent application client can obtain the configuration data corresponding to the target agent from the sub-application server corresponding to the target agent, or the parent application client can obtain the configuration data corresponding to the target agent from the parent application server. The configuration data corresponding to the target agent may be stored in the parent application server after the parent application client first obtains the configuration data corresponding to the target agent from the sub-application server corresponding to the target agent. The historical session data with the target intelligent agent can be managed by the parent application server, and the parent application client can obtain the historical session data from the parent application server. Alternatively, the historical session data with the target intelligent agent can be managed by the sub-application server corresponding to the target intelligent agent, and the parent application client can obtain the historical session data from the sub-application server corresponding to the target intelligent agent. The parent application (specifically, the parent application client) can render the page template data and the page content data corresponding to the target intelligent agent to obtain the session page with the target intelligent agent. The specific rendering process of the session page can be found in the relevant description of step S202 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0135] The steps S401-S402 above detail the technical process of triggering the display of the conversation page with the target agent in the parent application. It should be noted that in this technical process, the process of the parent application calling the sub-application corresponding to the target agent may include: the container of the parent application client (also called the end container) can launch the container of the sub-application client (also called the sub-application container or applet container), the container of the sub-application client can launch the conversation component (chatbox), and the conversation component may include the sub-application corresponding to each agent in at least one agent, that is, the conversation component may include the sub-application corresponding to the target agent; wherein, the container of the parent application client can be used to provide a runtime environment for the parent application client, and the container of the sub-application client can be used to provide a runtime environment for the sub-application client.

[0136] As shown in Figure 5, taking triggering a session request for a target agent in the comment page of the parent application client as an example, the user object can interact with the target agent through comments on the comment page. After the user object triggers the session entry point with the target agent on the comment page, it can launch the container of the parent application client. The container of the parent application client can launch the container of the child application client. The container of the child application client can launch the session component. The sub-application corresponding to the target agent in the session component can render the page template data and the page content data corresponding to the target agent to obtain the session page. Alternatively, the sub-application corresponding to the target agent in the session component can send the page template data and the page content data corresponding to the target agent to the parent application, which will then render the page template data and the page content data corresponding to the target agent to obtain the session page. Furthermore, if there is historical session data between the user object and the target agent, the sub-application client corresponding to the target agent can be called to retrieve the historical session data from the sub-application server corresponding to the target agent. The historical session data can be included in the page content data corresponding to the target agent.

[0137] Figure 5 illustrates this using the example of a session component being a functional component within a container of a sub-application client. Optionally, the session component can also serve as a container for a native sub-application client within the parent application. In this case, the process of the parent application calling the sub-application corresponding to the target agent can include: the container of the parent application client (also known as the end container) can launch the container of the sub-application client (also known as the sub-application container or mini-program container, i.e., the session component). The container of the sub-application client can include the sub-application corresponding to each agent in at least one agent, i.e., the sub-application client can include the sub-application corresponding to the target agent.

[0138] S403, in response to the dialogue information entered on the conversation page, the sub-application corresponding to the target agent calls the conversation model corresponding to the target agent to generate the response information corresponding to the dialogue information. The sub-application and the parent application have a subordinate relationship.

[0139] In step S403, the way the sub-application corresponding to the target agent invokes the session model corresponding to the target agent can include any of the following:

[0140] The first approach involves deploying the conversation model corresponding to the target agent within a sub-application server. This model responds to dialogue information entered on the conversation page of the sub-application client. The sub-application client can then invoke the conversation model on the sub-application server to generate a response. The invocation method can include: the sub-application client sending the dialogue information to the sub-application server, which then invokes the conversation model to generate the response; or, the sub-application client using the model invocation interface provided by the sub-application server to invoke the conversation model and generate the response.

[0141] The second approach involves deploying the session model corresponding to the target agent on the business server. This model responds to dialogue information entered on the session page of the sub-application client. The sub-application client can send the dialogue information to the sub-application server, which can then invoke the session model on the business server to generate a response. The invocation method can include: the sub-application server sending the dialogue information to the business server, which then invokes the session model to generate the response; or, the sub-application server using the model invocation interface provided by the business server to invoke the session model to generate the response.

[0142] Optionally, the preprocessing of dialogue information can be performed by the sub-application server corresponding to the target intelligent agent. The preprocessing of dialogue information can be found in the relevant description of step S203 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0143] S404, invoke the sub-application corresponding to the target agent to render the reply information to the conversation page.

[0144] In step S404, the sub-application corresponding to the target agent (specifically, the sub-application client corresponding to the target agent) can be invoked to obtain the reply information, and the reply information can be rendered onto the conversation page. The specific rendering process of the reply information can be found in the relevant description in step S204 above, and will not be repeated here.

[0145] Corresponding to the invocation method of the session model corresponding to the target agent, the method by which the sub-application client corresponding to the target agent obtains response information from the session model corresponding to the target agent may include any of the following:

[0146] The first approach involves deploying the session model corresponding to the target agent on a sub-application server. The sub-application client can then retrieve response information from this server. This retrieval can be achieved either by the sub-application client receiving response information from the sub-application server itself, or by the sub-application client retrieving response information through a model call interface provided by the sub-application server.

[0147] The second approach involves deploying the session model corresponding to the target agent on the business server corresponding to the target agent. The sub-application server corresponding to the target agent can obtain response information from the business server. This acquisition can be achieved either by the sub-application server receiving response information sent by the business server, or by the sub-application server obtaining response information through a model call interface provided by the business server. The sub-application client corresponding to the target agent can receive response information sent by the sub-application server corresponding to the target agent.

[0148] The above step S404 describes how the response information can be rendered by the sub-application corresponding to the target intelligent agent. Optionally, the response information can be rendered by the parent application (specifically, the parent application client). Specifically, the parent application client can receive the response information sent by the sub-application corresponding to the target intelligent agent, and the parent application client can render the response information onto the conversation page. The specific rendering process of the response information can be found in the relevant description of step S204 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0149] The above steps S403-S404 detail the technical process of having a conversation with the target agent in the parent application. It should be noted that in this technical process, the process of the parent application calling the child application may include: as shown in Figure 5, the parent application client can launch the conversation component, the child application corresponding to the target agent can call the conversation model corresponding to the target agent to generate the response information corresponding to the dialogue information, and the response information can be rendered into the conversation page.

[0150] Taking the rendering by the sub-application client corresponding to the target intelligent agent as an example, the process of steps S401-S404 above can be summarized as the technical architecture shown in Figure 6: The user can trigger a session request for the target intelligent agent in the parent application client's personal page, content publishing page, or message page; in response to the session request, the parent application client can launch the sub-application client corresponding to the target intelligent agent through a deep link, call the sub-application client corresponding to the target intelligent agent to render and display the session page with the target intelligent agent, the session page can provide session services (i.e., session function) with the target intelligent agent, sharing services for session data with the target intelligent agent (i.e., sharing function), and trigger the target intelligent agent to generate associations. The text association service (i.e., the association function) responds to the dialogue information entered by the user in the conversation page. The sub-application client corresponding to the target agent can send the dialogue information to the sub-application server corresponding to the target agent. The sub-application server corresponding to the target agent can preprocess the dialogue information, assembling reference information (i.e., context records) and / or response patterns to ensure the generation effect of the conversation model corresponding to the target agent. The sub-application server corresponding to the target agent can call the conversation model corresponding to the target agent to generate the response information corresponding to the dialogue information, and send the response information to the sub-application client corresponding to the target agent. The sub-application client corresponding to the target agent can render and display the response information in the conversation page.

[0151] In this embodiment, an intelligent agent can be accessed in the parent application. Furthermore, an intelligent agent can be accessed in the parent application as a sub-application. After the intelligent agent is accessed in the parent application, in response to a session request for the intelligent agent triggered in the parent application, the session page with the intelligent agent can be rendered in the parent application or by calling the corresponding sub-application of the intelligent agent. Thus, a session with the intelligent agent can be conducted in the parent application. In other words, the session page with the intelligent agent can be displayed and the session with the intelligent agent can be conducted directly in the parent application without jumping to other business platforms from the parent application. This can improve the efficiency of the session with the intelligent agent in the application.

[0152] This application proposes a data processing method based on intelligent agents. The method may include: at least one intelligent agent accessing the rendering and session processes of the same sub-application of a parent application as an intelligent agent instance. As shown in Figure 7, this data processing method may include, but is not limited to, the following steps S701-S704:

[0153] S701, in response to a session request for a target agent triggered in the parent application, the agent instance corresponding to the target agent in the sub-application is invoked to obtain page template data. The page template data is used to generate a session page for having a session with at least one agent, where the target agent is any one of the at least one agents.

[0154] In step S701, at least one agent can access the parent application by accessing a sub-application. Each agent accessing the sub-application corresponds to one agent instance. Page template data can be stored in the sub-application container or session component. In response to a session request triggered in the parent application (specifically, the parent application client) for the target agent, the agent instance corresponding to the target agent in the sub-application (specifically, the sub-application client) can be invoked to retrieve the page template data from the sub-application container or session component.

[0155] Optionally, the system can also call the agent instance corresponding to the target agent in the sub-application (specifically, the sub-application client) to obtain the page content data corresponding to the target agent, that is, to obtain the configuration data and historical session data with the target agent (if historical session data with the target agent exists). The configuration data corresponding to the target agent can be managed by the sub-application server, and the system can call the agent instance corresponding to the target agent to obtain the configuration data from the sub-application server. The historical session data with the target agent can be managed by the parent application (specifically, the parent application server), and the system can call the agent instance corresponding to the target agent to obtain the historical session data with the target agent from the parent application server; alternatively, the historical session data with the target agent can be managed by the sub-application server, and the system can call the agent instance corresponding to the target agent to obtain the historical session data with the target agent from the sub-application server.

[0156] S702, the agent instance corresponding to the target agent in the sub-application is called to render the page template data, obtain the session page corresponding to the target agent, and display the session page.

[0157] In step S702, the agent instance corresponding to the target agent in the sub-application (specifically, the sub-application client) can be invoked to render the page template data and the page content data corresponding to the target agent, thereby obtaining a conversation page with the target agent. The agent instance corresponding to the target agent in the sub-application can then be invoked to display the conversation page. The specific rendering process of the conversation page can be found in the description of step S202 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0158] The steps S701-S702 above describe how the conversation page with the target agent can be rendered by the agent instance corresponding to the target agent in the sub-application. Optionally, the conversation page with the target agent can be rendered by the parent application (specifically, the parent application client). Specifically, the parent application (specifically, the parent application client) can obtain page template data and page content data. The page content data may include configuration data corresponding to the target agent and historical session data with the target agent (if historical session data with the target agent exists). For page template data, the parent application client can receive page template data sent by the agent instance corresponding to the target agent, or the parent application client can obtain page template data from the parent application server. The page template data may be stored in the parent application server after the parent application client first receives the page template data from the agent instance corresponding to the target agent. For configuration data corresponding to the target agent, the parent application client can obtain the configuration data corresponding to the target agent from the sub-application server, or the parent application client can obtain the configuration data corresponding to the target agent from the parent application server. The configuration data corresponding to the target agent may be stored in the parent application server after the parent application client first obtains the configuration data corresponding to the target agent from the sub-application server. Regarding historical session data with the target agent, this data can be managed by the parent application server, from which the parent application client can retrieve it. Alternatively, it can be managed by the child application server, from which the parent application client can retrieve it. The parent application (specifically, the parent application client) can render the page template data and the page content data corresponding to the target agent to obtain the session page with the target agent.

[0159] Optionally, the conversation page with the target agent can also be rendered by a sub-application (specifically, a sub-application client). Specifically, the sub-application (specifically, a sub-application client) can obtain page template data and page content data. The page content data may include configuration data corresponding to the target agent and historical conversation data with the target agent (if historical conversation data with the target agent exists). For page template data, the sub-application client can obtain the page template data from the sub-application container or the conversation component. For configuration data corresponding to the target agent, the sub-application client can obtain the configuration data corresponding to the target agent from the sub-application server. Regarding historical conversation data with the target agent, this historical conversation data can be managed by the parent application server, and the sub-application client can obtain it from the parent application server; alternatively, the historical conversation data can be managed by the sub-application server, and the sub-application client can obtain it from the sub-application server. The sub-application (specifically, a sub-application client) can render the page template data and the page content data corresponding to the target agent to obtain the conversation page with the target agent. The specific rendering process of the session page can be found in the description of step S202 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0160] The above steps S701-S702 detail the technical process of triggering the display of the conversation page with the target agent in the parent application. It should be noted that in this technical process, the process of the parent application calling the agent instance corresponding to the target agent in the child application may include: the container of the parent application client (also called the end container) can launch the container of the child application client (also called the child application container or applet container), the container of the child application client can launch the child application client, the child application client can launch the conversation component (chatbox), and the conversation component may include the agent instance corresponding to each agent in at least one agent, that is, the conversation component may include the agent instance corresponding to the target agent.

[0161] S703, in response to dialogue information entered on the conversation page, calls the conversation model corresponding to the target intelligent agent through the intelligent agent instance corresponding to the target intelligent agent in the sub-application to generate reply information corresponding to the dialogue information. There is a subordinate relationship between the sub-application and the parent application.

[0162] In step S703, the way the agent instance corresponding to the target agent invokes the session model corresponding to the target agent can include any of the following:

[0163] The first approach involves deploying the conversation model corresponding to the target agent on a sub-application server. This model responds to dialogue information entered on the conversation page of the sub-application client. The agent instance corresponding to the target agent can invoke the conversation model on the sub-application server to generate a response to the dialogue information. The invocation method can include: the agent instance sending the dialogue information to the sub-application server, which then invokes the conversation model to generate the response; or, the agent instance using the model invocation interface provided by the sub-application server can invoke the conversation model to generate the response.

[0164] The second approach involves deploying the conversation model corresponding to the target agent on the business server. This model responds to dialogue information entered on the conversation page of the sub-application client. The agent instance can send the dialogue information to the sub-application server, which can then invoke the conversation model on the business server to generate a response. The invocation method can include: the sub-application server sending the dialogue information to the business server, which then invokes the conversation model to generate the response; or, the sub-application server using the model invocation interface provided by the business server to invoke the conversation model to generate the response.

[0165] Optionally, the preprocessing of dialogue information can be performed by the sub-application server. The preprocessing of dialogue information can be found in the relevant description of step S203 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0166] S704, invoke the agent instance corresponding to the target agent in the sub-application to render the reply information to the conversation page.

[0167] In step S704, the agent instance corresponding to the target agent in the sub-application can be invoked to obtain the response information, and the agent instance corresponding to the target agent can be invoked to render the response information to the conversation page. The specific rendering process of the response information can be found in the relevant description in step S204 above, and will not be repeated here.

[0168] Corresponding to the invocation method of the session model corresponding to the target agent, the way the agent instance corresponding to the target agent obtains the response information from the session model corresponding to the target agent can include any of the following:

[0169] The first approach involves deploying the session model corresponding to the target agent on a sub-application server. The agent instance corresponding to the target agent can obtain response information from the sub-application server. This acquisition can be achieved either by the agent instance receiving response information sent by the sub-application server, or by the agent instance obtaining response information through a model call interface provided by the sub-application server. The second approach involves deploying the session model corresponding to the target agent on the business server corresponding to the target agent. The sub-application server can obtain response information from the business server. Again, this acquisition can be achieved either by the sub-application server receiving response information sent by the business server, or by the sub-application server obtaining response information through a model call interface provided by the business server. The agent instance corresponding to the target agent can also receive response information sent by the sub-application server.

[0170] The above step S704 describes how the response information can be rendered by the agent instance corresponding to the target agent in the sub-application. Optionally, the response information can be rendered by the parent application (specifically, the parent application client). Specifically, the sub-application client can receive the response information sent by the agent instance corresponding to the target agent, the parent application client can receive the response information sent by the sub-application client, and the parent application client can render the response information onto the session page. Optionally, the response information can also be rendered by the sub-application (specifically, the sub-application client). Specifically, the sub-application client can receive the response information sent by the agent instance corresponding to the target agent, and the sub-application client can render the response information onto the session page. The specific rendering process of the response information can be found in the description of step S204 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0171] The above steps S703-S704 detail the technical process of having a conversation with the target agent in the parent application. It should be noted that in this technical process, the process of the parent application calling the agent instance corresponding to the target agent may include: the parent application client can launch the conversation component, the agent instance corresponding to the target agent can call the conversation model corresponding to the target agent to generate response information for the dialogue, and the response information can be rendered into the conversation page.

[0172] Taking the rendering of the agent instance corresponding to the target agent as an example, the process of steps S701-S704 above can be summarized as follows: The user can trigger a session request for the target agent on the parent application client's personal page, content publishing page, or message page; in response to the session request, the parent application client can launch a child application client via a deep link. The child application client can launch the agent instance corresponding to the target agent, call the agent instance corresponding to the target agent to render and display the session page with the target agent. The session page can provide session services (i.e., session functionality) with the target agent, including the distribution of session data with the target agent. The system includes a sharing service (i.e., sharing function) and an association service (i.e., association function) that triggers the target agent to generate associated text. In response to dialogue information entered by the user in the conversation page, the agent instance corresponding to the target agent can send the dialogue information to the sub-application server. The sub-application server can preprocess the dialogue information, assembling reference information and / or response patterns to ensure the generation effect of the conversation model corresponding to the target agent. The sub-application server can call the conversation model corresponding to the target agent to generate response information corresponding to the dialogue information and send the response information to the agent instance corresponding to the target agent. The agent instance corresponding to the target agent can render and display the response information in the conversation page.

[0173] In this embodiment, an intelligent agent can be accessed in the parent application, and at least one intelligent agent can be accessed in the parent application and placed in the same sub-application. After the intelligent agent is accessed in the parent application, in response to a session request for the intelligent agent triggered in the parent application, a session page with the intelligent agent can be rendered in the parent application through the parent application, the sub-application, or the intelligent agent instance corresponding to the intelligent agent. Thus, a session with the intelligent agent can be conducted in the parent application. In other words, the session page with the intelligent agent can be displayed and a session with the intelligent agent can be conducted directly in the parent application without jumping from the parent application to other business platforms. This can improve the efficiency of the session with the intelligent agent in the application.

[0174] This application proposes a data processing method based on an intelligent agent. The method may include a technical process of publishing conversation data with the intelligent agent as content published by a parent application. This data processing method can be executed by a terminal device, specifically by a parent application running on the terminal device. As shown in Figure 8a, the data processing method may include, but is not limited to, the following steps S801-S803:

[0175] S801 displays a conversation page with the target agent through a sub-application. The conversation page includes conversation data with the target agent, including dialogue information and response information.

[0176] In step S801, the process of displaying the conversation page with the target agent through the sub-application is recorded in steps S201-S202 of the embodiment shown in FIG2, steps S401-S402 of the embodiment shown in FIG4 (corresponding to the case of display through the sub-application corresponding to the target agent), and steps S701-S702 of the embodiment shown in FIG7 (corresponding to the case of display through the agent instance corresponding to the target agent in the sub-application). For details, please refer to the relevant descriptions of the embodiments shown in FIG2, FIG4, and FIG7, which will not be repeated here. The process of displaying the conversation data with the target agent in the conversation page is recorded in steps S203-S204 of the embodiment shown in FIG2, steps S403-S404 of the embodiment shown in FIG4 (corresponding to the case of display through the sub-application corresponding to the target agent), and steps S703-S704 of the embodiment shown in FIG7 (corresponding to the case of display through the agent instance corresponding to the target agent in the sub-application). For details, please refer to the relevant descriptions of the embodiments shown in FIG2, FIG4, and FIG7, which will not be repeated here.

[0177] S802, in response to a session data publishing operation, receives session data sent by a sub-application.

[0178] In step S802, in response to the session data publishing operation, the parent application can receive session data sent by the sub-application; specifically, the parent application client can receive session data sent by the sub-application client. When an agent accesses the parent application as a sub-application, the parent application client can receive session data sent by the sub-application client corresponding to the target agent. When at least one agent accesses the same sub-application of the parent application, the parent application client can receive session data sent by the agent instance corresponding to the target agent within the sub-application client.

[0179] The publishing operation of session data can include any of the following: First, triggering the publishing control in the session page with the target agent; specifically, as shown in FIG8b, the session page 80 between the user and the target agent may contain session data 801 with the target agent. In response to a triggering operation on the session data 801 (the triggering operation here may be, for example, a long press), a sharing control 802 is displayed in the session page 80. In response to a triggering operation on the sharing control 802 (the triggering operation here may be, for example, a click), a publishing control 803 is displayed in the session page 80. The parent application can receive the session data sent by the child application in response to a triggering operation on the publishing control 803 (the triggering operation here may be, for example, a click). Second, after selecting session data in the session page with the target agent, the parent application can receive the session data sent by the child application in response to a gravity sensor operation on the terminal device running the parent application; for example, the gravity sensor operation may include a shaking operation and a rotation operation, etc., which are not limited in this embodiment. The third method involves selecting session data on the session page with the target intelligent agent. The parent application can then receive session data sent by the child application in response to a gesture trigger operation on the session page. A gesture trigger operation refers to drawing a specific pattern on the session page using a specific gesture, such as drawing the letter "P" on the session page using the index finger.

[0180] Publishing session data can be done on all or part of the session data on the session page. Partial session data can be session data selected by the user. In the case of partial session data, as shown in Figure 8c, the user selects a set of session data consisting of a dialogue message and a reply message as the session data to be published on the session page.

[0181] Optionally, the number of groups of session data that can be supported as the session data to be published can be set (e.g., it can be set to one group). In this case, as shown in Figure 8d, if a group of session data has been selected as the session data to be published, the selection controls for other session data are set to an unselectable state (e.g., the filled state in Figure 8d), and an unselectable prompt can be output (e.g., "Only one group of sessions can be shared" in Figure 8d).

[0182] Optionally, as shown in Figure 8e, it can also support the deletion of session data. In response to a trigger operation on session data 801 (the trigger operation here may be, for example, a long press), a delete control 804 can be displayed in the session page 80. In response to a trigger operation on the delete control 804 (the trigger operation here may be, for example, a click), session data 801 can be deleted in the session page 80.

[0183] Optionally, as shown in Figure 8e, it can also support copying session data. In response to a triggering operation on session data 801 (the triggering operation here could be, for example, a long press), a copy control 805 can be displayed in the session page 80. In response to a triggering operation on the copy control 805 (the triggering operation here could be, for example, a click), session data 801 can be copied and a copy prompt (e.g., "Copied" in Figure 8e) can be displayed.

[0184] S803: The parent application transforms and processes the session data to obtain multiple images to be published, determines the target content to be published including the multiple images to be published, and publishes the target content; wherein, there is a subordinate relationship between the parent application and the child application.

[0185] In step S703, the session data can be transformed by the parent application to obtain multiple images to be published. The transformation process can include image transformation and image segmentation. Image transformation refers to converting the session data into an image containing the session data, and image segmentation refers to segmenting the image according to the image standards of the published content to obtain multiple images to be published.

[0186] The parent application can determine target content containing multiple images to be published and publish the target content. The process of determining the target content may include: the parent application acquiring a cover image and description information; the cover image may be generated based on dialogue information in the session data, and the description information may also be generated based on dialogue information in the session data; the parent application generates the target content based on the cover image, multiple images to be published, and the description information.

[0187] In detail, the interaction process between the parent application client and the parent application server during the process of publishing session data as published content can include: the parent application client can send session data to the parent application server, which can then process the session data to obtain multiple images to be published and determine the target published content including the multiple images to be published; the parent application server can then send the target published content to the parent application client, which will then render the target published content onto the published content page to publish the target published content.

[0188] The above step S703 describes the technical process of converting session data into target published content. In terms of product presentation, as shown in Figure 8b, in response to the publishing operation of session data, such as in response to the trigger operation of the publishing control 803 (the trigger operation here can be, for example, a click), the content editing page 81 can be displayed. The content editing page can include the target published content 811 and the publishing confirmation control 812. In response to the trigger operation of the publishing confirmation control 812 (the trigger operation here can be a click), the publishing content page 82 of the user can be displayed. The publishing content page 82 can include the target published content 811.

[0189] Optionally, the content publishing page that uses the conversation data with the target agent as the published content may include a conversation entry point with the target agent. In response to the triggering operation of the conversation entry point, a conversation page for conversing with the target agent may be displayed, so that a conversation can be conducted with the target agent. For example, in the content publishing page 82 shown in FIG8b, a conversation entry point 301 for conversing with the target agent is available.

[0190] In this embodiment, the session data between the user of the parent application and the intelligent agent can be combined with the business functions provided by the parent application itself. For example, the session data can be combined with the content publishing function provided by the parent application itself, and the session data can be converted into published content for publication. This allows the business functions provided by the parent application itself to use the interactive content between the parent application and the intelligent agent, thereby improving the intelligence level of the business functions provided by the parent application itself.

[0191] The embodiments shown in Figures 2, 4, 7, and 8a above are all based on the premise that an agent has already been integrated into the parent application. This application proposes an agent-based data processing method, which may include: standard access methods and unified management methods for agents in the parent application. As shown in Figure 9, this agent-based data processing method may include, but is not limited to, the following steps S901-S902:

[0192] S901, At least one agent is connected in the parent application, and the target agent is any one of the at least one agents.

[0193] In step 901, in one implementation, an agent can be accessed from the parent application as a sub-application. That is, at least one sub-application corresponding to an agent can be accessed from the parent application. In this case, the sub-application corresponding to at least one agent can specifically be accessed from the session component of the parent application's sub-application container (corresponding to the case where the session component is contained within the sub-application container), as shown in Figure 10. At least one sub-application corresponding to an agent can be accessed from the session component. Alternatively, the sub-application corresponding to at least one agent can specifically be accessed from the parent application's sub-application container, corresponding to the case where the session component is the sub-application container. In another implementation, at least one agent can be accessed from the same sub-application of the parent application, and at least one agent instance corresponding to an agent can be accessed from the sub-application of the parent application.

[0194] Integrating the intelligent agent (including the sub-application corresponding to the intelligent agent or the intelligent agent instance corresponding to the intelligent agent) involves the front-end integration of the intelligent agent. The front-end integration process of the intelligent agent may include: downloading the sub-program IDE (Integrated Development Environment) and performing custom development, referring to the code integration example; completing local development and testing; releasing a trial version for testing; and clicking "launch".

[0195] During front-end integration, the xhs-ai-chatbox component is introduced in the rendering layer to enable and disable (i.e., show or hide) extended functionality controls in the chat page. Taking extended functionality controls including deep thinking controls and online search controls as an example, the exemplary code of the xhs-ai-chatbox component is as follows:

[0196]

[0197] As shown in Figure 10, the intelligent agent can involve both front-end and back-end access. Back-end access refers to the interface between the intelligent agent (including the corresponding sub-application or intelligent agent instance) and the corresponding session model. If the session model is deployed on a sub-application server, the interface refers to deploying the session model on the sub-application server. If the session model is deployed on a business server, the interface refers to defining the calling interface between the sub-application server and the session model. This calling interface could be, for example, SPI (Serial Peripheral Interface), but this embodiment does not limit its scope.

[0198] When the session model corresponding to the agent is deployed on the business server, the sub-application server can request the session model to generate response information corresponding to the dialogue information via a request. The session model can then return the response information in the form of a response. The definition of the API call can include the definition of request parameters and response parameters. Table 1 below shows an example of request parameter definition:

[0199] Table 1

[0200]

[0201] It is worth noting that in the request parameters shown in Table 1 above, the value of the `deep_thinking` field indicates whether the user triggers the deep thinking control. The value of the `enable_search` field can indicate whether the user triggers the online search control. The value of the `generate_type` field can be the response mode mentioned above. This field can be used to request the assistant (the conversational model corresponding to the agent) to output response information that meets the requirements as much as possible; for example, the response mode can include chat mode (CHAT) and associated word mode (RELATED_WORD). The value of the `stream` field can be used to indicate the return format of the response information by the conversational model corresponding to the agent. The return format can include streaming return and non-streaming return; where streaming return means that there is no need to wait for the response information to be fully generated, and it can be returned while being generated, and non-streaming return means that the response information needs to be fully generated and all the response information is returned at once.

[0202] The following code illustrates an example of a request from a sub-application (specifically, a sub-application server) to the session model corresponding to the agent:

[0203]

[0204] Table 2 below shows an example of the definition of response parameters:

[0205] Table 2

[0206]

[0207]

[0208] The following code shows an example of the response from the agent's corresponding session model to the sub-application (specifically, the sub-application server) (corresponding to a successful (streaming) response):

[0209] data:

[0210] {"id":"12345","model":"deepseek","created":1741619203,"choices":[{"index":0,"delta":{"role":"assistant","content":movie"},"finish_reason":null}],"usage":{"prompt_tokens":10,"completion_tokens":20,"total_tokens":30},"search_web_pages":35}

[0211] data:

[0212] {"id":"12345","model":"deepseek","created":1741619203,"choices":[{"index":0,"delta":{"role":"assistant

[0213] ","content":"A"},"finish_reason":"stop"}],"usage":{"prompt_tokens":10,"completion_tokens":20,"total_tokens":30},"search_web_pages":35}

[0214] The following code shows an example of the response from the agent's corresponding session model to the sub-application (specifically, the sub-application server) (corresponding to a successful (non-streaming) response):

[0215]

[0216] The following code shows an example of the response from the agent's corresponding session model to the sub-application (specifically, the sub-application server) (corresponding to the case of response failure):

[0217]

[0218] S902, manage at least one intelligent agent in a unified manner according to a unified standard; wherein, the unified standard includes a rendering standard and a session standard, and the unified management includes rendering management corresponding to the rendering standard and session management corresponding to the session standard.

[0219] In step S902, when an agent is integrated into the parent application as a sub-application, the sub-applications corresponding to at least one agent can be managed uniformly according to a unified standard. Alternatively, when at least one agent is integrated into the same sub-application of the parent application, the agent instances corresponding to at least one agent can be managed uniformly according to a unified standard.

[0220] A unified standard refers to the use of a consistent standard for managing at least one connected agent. This improves management efficiency when dealing with a large number of connected agents. A unified standard can include rendering standards and session standards.

[0221] The rendering standard can be used to define a unified rendering method for at least one agent. Rendering management refers to rendering according to the rendering method defined by the rendering standard. Specifically, it can include page rendering standards for the conversation page and rendering standards for the conversation data in the conversation page. The page rendering standard can be used to define unified page template data, i.e., a unified conversation page style. The conversation data rendering standard can be used to define the correspondence between the content type of the conversation data and the rendering service. Figures 11 and 12 are an example of a unified rendering standard: the basic area of ​​the conversation page can include the agent's identifier (e.g., the target agent's icon and name in Figure 11), and controls to trigger global functions (e.g., settings, complaints and reports, and restarting the conversation); the conversation information area of ​​the conversation page can include functions for operating the conversation data (e.g., copying and sharing), and can also render reply information according to the unified conversation data rendering standard; the input area of ​​the conversation page can set functions for manipulating the conversation (e.g., new conversation function, deep thinking function, and online search function), and can also set functions for sending to external sources (e.g., album and photo taking). Figure 13 is an example of a conversation page rendered by different intelligent agents according to a unified rendering standard. It can be seen that by using a unified rendering standard, the overall form of the conversation pages of different intelligent agents is consistent, which can improve the user experience.

[0222] A session standard can be used to define a unified session method for at least one agent. Session management refers to engaging in conversations with agents according to the session method defined by the session standard. Session management can include: historical session management, reference information injection management, request management with agents, and response management with agents. Historical session management can be used to uniformly manage historical session data with various agents. Reference information injection management can be used to manage the types of reference information to be injected under different session request triggering scenarios. Request management with agents can be used to manage the request parameters of requests from sub-application servers to the session models corresponding to agents. Response management with agents can be used to manage the response parameters of responses from the session models corresponding to agents to the sub-application servers.

[0223] In this embodiment, for the business side of the intelligent agent, it provides a common capability for different intelligent agents to quickly access the application ecosystem, enabling rapid integration through open capabilities and interaction with application users within the application. For the application users, it allows them to access more open intelligent agent capabilities within the application, enriching the interaction scenarios between users and the application.

[0224] Please refer to Figure 14, which is a schematic diagram of a data processing device based on an intelligent agent provided in an embodiment of this application. This intelligent agent-based data processing device can be installed in a computer device provided in this embodiment, and the computer device can be a terminal device running a parent application. The intelligent agent-based data processing device shown in Figure 14 can be a computer program running in the computer device, and can be used to execute some or all of the steps in the method embodiments shown in Figures 2, 4, 7, 8a, or 9. Please refer to Figure 14; the intelligent agent-based data processing device may include the following units:

[0225] Processing unit 1401 is configured to, in response to a session request for a target agent triggered in a parent application, obtain page template data, the page template data being used to generate a session page for engaging in a session with at least one agent, the target agent being any one of the at least one agents;

[0226] Display unit 1402 is used to render page template data to obtain a conversation page with the target intelligent agent and display the conversation page;

[0227] The processing unit 1401 is also used to respond to the dialogue information entered in the conversation page, and generate the reply information corresponding to the dialogue information by calling the conversation model corresponding to the target intelligent agent through the sub-application. The sub-application and the parent application have a subordinate relationship.

[0228] The display unit 1402 is also used to render reply information to the conversation page.

[0229] In one implementation, when the display unit 1402 renders page template data to obtain a session page with the target agent, it is specifically used to perform any of the following:

[0230] The parent application renders the page template data to obtain the conversation page with the target intelligent agent;

[0231] The sub-application corresponding to the target agent is invoked to render the page template data, resulting in a session page corresponding to the target agent; wherein, one agent connected to the parent application corresponds to one sub-application;

[0232] The page data is rendered by calling the agent instance corresponding to the target agent in the sub-application to obtain the conversation page with the target agent; wherein, at least one agent accesses the parent application by accessing the sub-application, and one agent accessing the sub-application corresponds to one agent instance.

[0233] In one implementation, the display unit 1402 is further configured to perform any of the following:

[0234] The target agent's personal page is displayed through the parent application, and a session request is generated in response to a session triggering operation on the personal page;

[0235] The parent application displays a content publishing page, which includes a session entry point for the target agent. In response to a session trigger operation targeting the session entry point, a session request is generated.

[0236] A message page is displayed through the parent application, the message page including a session message of at least one object, the at least one object including a target agent; a session request is generated in response to a session triggering operation on the target agent in the message page;

[0237] The search page is displayed through the parent application. The search page includes a session entry point with the target agent. In response to a session triggering operation on the session entry point, a session request is generated.

[0238] The parent application displays a comment page, which includes comment content related to the target agent; in response to a session triggering action on the target agent in the comment page, a session request is generated.

[0239] In one implementation, the display unit 1402 is further configured to display a conversation page with the target intelligent agent through a sub-application. The conversation page includes conversation data with the target intelligent agent, and the conversation data includes dialogue information and response information.

[0240] The processing unit 1401 is also configured to receive session data sent by the sub-application in response to a session data publishing operation;

[0241] The processing unit 1401 is also used to transform and process the session data through the parent application to obtain multiple images to be published, determine the target publishing content including the multiple images to be published, and publish the target publishing content; wherein, there is a subordinate relationship between the parent application and the child application.

[0242] In one implementation, the processing unit 1401 is further configured to perform the following steps:

[0243] In response to the dialogue information entered on the conversation page, the sub-application calls the conversation model corresponding to the target agent to generate the corresponding response information.

[0244] The reply message will be rendered onto the chat page.

[0245] In one implementation, when the processing unit 1401 generates response information corresponding to the dialogue information by calling the conversation model corresponding to the target agent through a sub-application, it is specifically used to perform any of the following:

[0246] The sub-application corresponding to the target agent calls the conversation model corresponding to the target agent to generate the response information corresponding to the dialogue information; wherein, one agent connected to the parent application corresponds to one sub-application.

[0247] The corresponding response information for the dialogue information is generated by calling the conversation model corresponding to the target intelligent agent through the intelligent agent instance corresponding to the target intelligent agent in the sub-application; wherein, at least one intelligent agent accesses the parent application by accessing the sub-application, and one intelligent agent accessing the sub-application corresponds to one intelligent agent instance.

[0248] In one implementation, the processing unit 1401 is further configured to perform any of the following:

[0249] The dialogue information is preprocessed by a sub-application to obtain preprocessed dialogue information;

[0250] Processing unit 1401, when generating response information corresponding to dialogue information by calling the conversation model corresponding to the target agent through the sub-application, specifically performs the following steps:

[0251] The sub-application calls the conversation model corresponding to the target agent to generate response information corresponding to the preprocessed dialogue information.

[0252] In one implementation, the processing unit 1401 is used to preprocess the dialogue information through a sub-application program. When obtaining the preprocessed dialogue information, it specifically performs the following steps:

[0253] Reference information is obtained through sub-applications, and this reference information is matched with the triggering scenario corresponding to the session request.

[0254] The reference information and dialogue information are assembled and processed by the sub-application to obtain preprocessed dialogue information;

[0255] Among them, the conversation model corresponding to the target agent generates response information corresponding to the dialogue information based on the reference information and the dialogue information.

[0256] In one implementation, the processing unit 1401 is used to preprocess the dialogue information through a sub-application program. When obtaining the preprocessed dialogue information, it specifically performs the following steps:

[0257] The response pattern is obtained through a sub-application, and the response pattern matches the conversation scenario corresponding to the conversation page.

[0258] The sub-application assembles and processes the response pattern and dialogue information to obtain preprocessed dialogue information.

[0259] Among them, the conversation model corresponding to the target agent generates response information corresponding to the dialogue information according to the answer pattern.

[0260] In one implementation, the processing unit 1401, in response to dialogue information input on the conversation page, generates reply information corresponding to the dialogue information by calling the conversation model corresponding to the target agent through a sub-application, specifically performs the following steps:

[0261] Display at least one extended function control on the conversation page, with each extended function control corresponding to a different answer generation strategy;

[0262] In response to a trigger operation on a target extended function control in at least one extended function control, and dialogue information entered on the conversation page, the sub-application calls the conversation model corresponding to the target agent to generate reply information corresponding to the dialogue information according to the answer generation strategy corresponding to the target extended function control.

[0263] In one implementation, when rendering the reply information to the session page, the processing unit 1401 specifically performs the following steps:

[0264] Determine the type of content contained in the response message;

[0265] Call the rendering service that matches the content type to render the response information and obtain the rendered response information;

[0266] The rendered reply information will be displayed on the conversation page.

[0267] In one implementation, the processing unit 1401 is further configured to perform any of the following:

[0268] Integrate at least one sub-application corresponding to an intelligent agent into the parent application, and manage the sub-application corresponding to at least one intelligent agent in a unified manner according to a unified standard;

[0269] Alternatively, at least one agent instance corresponding to an agent can be accessed in a sub-application, and the agent instances corresponding to at least one agent can be managed in a unified manner according to a unified standard.

[0270] The unified standard includes rendering standard and session standard, and the unified management includes rendering management corresponding to the rendering standard and session management corresponding to the session standard.

[0271] According to one embodiment of this application, the various units in the agent-based data processing device shown in FIG14 can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This can achieve the same operation without affecting the technical effect of the embodiment of this application. The above units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by multiple units working together.

[0272] According to another embodiment of this application, an agent-based data processing apparatus as shown in FIG14, and an agent-based data processing method according to an embodiment of this application, can be constructed and implemented by running a computer program capable of performing some or all of the steps involved in the methods shown in FIG2, FIG4, FIG7, FIG8a, or FIG9 on a general-purpose computing device including processing elements and storage elements such as a central processing unit (CPU), random access storage medium (RAM), and read-only storage medium (ROM). The computer program can be recorded on, for example, a computer-readable storage medium, loaded into the aforementioned computing device through the computer-readable storage medium, and run therein.

[0273] In this embodiment, in response to a session request for a target agent triggered in the parent application, page template data can be obtained. The page template data can be used to generate a session page for engaging in a session with at least one agent. The page template data can be rendered to obtain the session page with the target agent and displayed. In response to dialogue information entered in the session page, a response message corresponding to the dialogue information can be generated by calling the session model corresponding to the target agent through a sub-application. The sub-application and the parent application have a subordinate relationship. The response message can be rendered onto the session page. As can be seen, the application can be used as the parent application, and smart agents can be accessed through sub-applications within the parent application. This allows smart agents to be integrated into the application. Furthermore, after a smart agent is integrated into the application, in response to a session request triggered within the application, a session page for the smart agent can be rendered within the application, enabling conversations with the smart agent within the application. In other words, the session page for the smart agent can be displayed directly within the application, and conversations can be conducted directly without navigating to other business platforms, thus improving the efficiency of conversations with smart agents within the application. In addition, for at least one smart agent integrated into the parent application, a session page for engaging with at least one smart agent can be rendered based on the same page template data. This ensures that the session pages for at least one smart agent integrated into the parent application have a unified style, improving the standardization of smart agent integration into the application.

[0274] Based on the above methods and apparatus embodiments, this application provides a computer device. Please refer to Figure 15, which is a schematic diagram of the structure of a computer device provided in this application embodiment. The computer device shown in Figure 15 includes at least a processor 1501, an input interface 1502, an output interface 1503, and a computer-readable storage medium 1504. The processor 1501, input interface 1502, output interface 1503, and computer-readable storage medium 1504 can be connected via a bus or other means.

[0275] The computer-readable storage medium 1504 can be stored in the memory of a computer device. The computer-readable storage medium 1504 is used to store computer programs, including computer instructions. The processor 1501 is used to execute the computer program stored in the computer-readable storage medium 1504. The processor 1501 (or CPU (Central Processing Unit)) is the computing and control core of the computer device, suitable for implementing computer programs, specifically for loading and executing computer programs to achieve corresponding method flows or functions.

[0276] This application also provides a computer-readable storage medium (Memory), which is a memory device in a computer device used to store programs and data. It is understood that the computer-readable storage medium here can include both built-in storage media in the computer device and extended storage media supported by the computer device. The computer-readable storage medium provides storage space that stores the operating system of the computer device. Furthermore, the storage space also stores computer programs (which may include program instructions 1-n) suitable for loading and execution by a processor. It should be noted that the computer-readable storage medium here can be high-speed RAM or non-volatile memory, such as at least one disk storage device; optionally, it can also be at least one computer-readable storage medium located remotely from the aforementioned processor.

[0277] The computer device can be a terminal device running a parent application program. Specifically, the processor 1501 can load and execute the computer program stored in the computer-readable storage medium 1504 to perform the corresponding steps in the methods shown in Figures 2, 4, 7, 8a, or 9. Specifically, the computer program in the computer-readable storage medium 1504 is loaded by the processor 1501 and executed as follows:

[0278] In response to a session request for a target agent triggered in the parent application, obtain page template data, which is used to generate a session page for having a session with at least one agent, the target agent being any one of the at least one agents;

[0279] The page template data is rendered to obtain the conversation page with the target agent, and the conversation page is displayed.

[0280] In response to dialogue information entered on the conversation page, the sub-application calls the conversation model corresponding to the target agent to generate the corresponding response information. The sub-application and the parent application have a subordinate relationship.

[0281] The reply information is rendered onto the chat page.

[0282] In one implementation, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to render page template data to obtain a session page with the target intelligent agent, it is specifically used to perform any of the following:

[0283] The parent application renders the page template data to obtain the conversation page with the target intelligent agent;

[0284] The sub-application corresponding to the target agent is invoked to render the page template data, resulting in a session page corresponding to the target agent; wherein, one agent connected to the parent application corresponds to one sub-application;

[0285] The page data is rendered by calling the agent instance corresponding to the target agent in the sub-application to obtain the conversation page with the target agent; wherein, at least one agent accesses the parent application by accessing the sub-application, and one agent accessing the sub-application corresponds to one agent instance.

[0286] In one implementation, the computer program in the computer-readable storage medium 1504 is loaded by the processor 1501 and is also used to perform any of the following:

[0287] The target agent's personal page is displayed through the parent application, and a session request is generated in response to a session triggering operation on the personal page;

[0288] The parent application displays a content publishing page, which includes a session entry point for the target agent. In response to a session trigger operation targeting the session entry point, a session request is generated.

[0289] A message page is displayed through the parent application, the message page including a session message of at least one object, the at least one object including a target agent; a session request is generated in response to a session triggering operation on the target agent in the message page;

[0290] The search page is displayed through the parent application. The search page includes a session entry point with the target agent. In response to a session triggering operation on the session entry point, a session request is generated.

[0291] The parent application displays a comment page, which includes comment content related to the target agent; in response to a session triggering action on the target agent in the comment page, a session request is generated.

[0292] In one implementation, the computer program in the computer-readable storage medium 1504 is loaded by the processor 1501 and executed as follows:

[0293] The sub-application displays a conversation page with the target agent, which includes conversation data between the target agent and dialogue information and response information.

[0294] In response to a publish operation on session data, receive session data sent by the sub-application;

[0295] The parent application transforms and processes the session data to obtain multiple images to be published, determines the target content to be published including the multiple images to be published, and publishes the target content; there is a subordinate relationship between the parent application and the child application.

[0296] In one implementation, the computer program in the computer-readable storage medium 1504 is loaded by the processor 1501 and is also used to perform any of the following:

[0297] In response to the dialogue information entered on the conversation page, the sub-application calls the conversation model corresponding to the target agent to generate the corresponding response information.

[0298] The reply message will be rendered onto the chat page.

[0299] In one implementation, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to generate response information corresponding to the dialogue information by calling the conversation model corresponding to the target intelligent agent through a sub-application, it is specifically used to perform any of the following:

[0300] The sub-application corresponding to the target agent calls the conversation model corresponding to the target agent to generate the response information corresponding to the dialogue information; wherein, one agent connected to the parent application corresponds to one sub-application.

[0301] The corresponding response information for the dialogue information is generated by calling the conversation model corresponding to the target intelligent agent through the intelligent agent instance corresponding to the target intelligent agent in the sub-application; wherein, at least one intelligent agent accesses the parent application by accessing the sub-application, and one intelligent agent accessing the sub-application corresponds to one intelligent agent instance.

[0302] In one implementation, the computer program in the computer-readable storage medium 1504 is loaded by the processor 1501 and is also used to perform any of the following:

[0303] The dialogue information is preprocessed by a sub-application to obtain preprocessed dialogue information;

[0304] When the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501, and generates response information corresponding to the dialogue information by calling the conversation model corresponding to the target intelligent agent through a sub-application program, it is specifically used to perform the following steps:

[0305] The sub-application calls the conversation model corresponding to the target agent to generate response information corresponding to the preprocessed dialogue information.

[0306] In one implementation, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to preprocess the dialogue information through a sub-application program and obtain the preprocessed dialogue information, it specifically performs the following steps:

[0307] Reference information is obtained through sub-applications, and this reference information is matched with the triggering scenario corresponding to the session request.

[0308] The reference information and dialogue information are assembled and processed by the sub-application to obtain preprocessed dialogue information;

[0309] Among them, the conversation model corresponding to the target agent generates response information corresponding to the dialogue information based on the reference information and the dialogue information.

[0310] In one implementation, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to preprocess the dialogue information through a sub-application program and obtain the preprocessed dialogue information, it specifically performs the following steps:

[0311] The response pattern is obtained through a sub-application, and the response pattern matches the conversation scenario corresponding to the conversation page.

[0312] The sub-application assembles and processes the response pattern and dialogue information to obtain preprocessed dialogue information.

[0313] Among them, the conversation model corresponding to the target agent generates response information corresponding to the dialogue information according to the answer pattern.

[0314] In one implementation, the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 in response to dialogue information input in the conversation page. When the program generates response information corresponding to the dialogue information by calling the conversation model corresponding to the target agent through a sub-application, it specifically performs the following steps:

[0315] Display at least one extended function control on the conversation page, with each extended function control corresponding to a different answer generation strategy;

[0316] In response to a trigger operation on a target extended function control in at least one extended function control, and dialogue information entered on the conversation page, the sub-application calls the conversation model corresponding to the target agent to generate reply information corresponding to the dialogue information according to the answer generation strategy corresponding to the target extended function control.

[0317] In one implementation, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to render the response information to the session page, it specifically performs the following steps:

[0318] Determine the type of content contained in the response message;

[0319] Call the rendering service that matches the content type to render the response information and obtain the rendered response information;

[0320] The rendered reply information will be displayed on the conversation page.

[0321] In one implementation, the computer program in the computer-readable storage medium 1504 is loaded by the processor 1501 and is also used to perform any of the following:

[0322] Integrate at least one sub-application corresponding to an intelligent agent into the parent application, and manage the sub-application corresponding to at least one intelligent agent in a unified manner according to a unified standard;

[0323] Alternatively, at least one agent instance corresponding to an agent can be accessed in a sub-application, and the agent instances corresponding to at least one agent can be managed in a unified manner according to a unified standard.

[0324] The unified standard includes rendering standard and session standard, and the unified management includes rendering management corresponding to the rendering standard and session management corresponding to the session standard.

[0325] In this embodiment, in response to a session request for a target agent triggered in the parent application, page template data can be obtained. The page template data can be used to generate a session page for engaging in a session with at least one agent. The page template data can be rendered to obtain the session page with the target agent and displayed. In response to dialogue information entered in the session page, a response message corresponding to the dialogue information can be generated by calling the session model corresponding to the target agent through a sub-application. The sub-application and the parent application have a subordinate relationship. The response message can be rendered onto the session page. As can be seen, the application can be used as the parent application, and smart agents can be accessed through sub-applications within the parent application. This allows smart agents to be integrated into the application. Furthermore, after a smart agent is integrated into the application, in response to a session request triggered within the application, a session page for the smart agent can be rendered within the application, enabling conversations with the smart agent within the application. In other words, the session page for the smart agent can be displayed directly within the application, and conversations can be conducted directly without navigating to other business platforms, thus improving the efficiency of conversations with smart agents within the application. In addition, for at least one smart agent integrated into the parent application, a session page for engaging with at least one smart agent can be rendered based on the same page template data. This ensures that the session pages for at least one smart agent integrated into the parent application have a unified style, improving the standardization of smart agent integration into the application.

[0326] Furthermore, it should be noted that the embodiments of this application also provide a computer-readable storage medium, which stores a computer program, and the computer program includes computer instructions. When the processor executes the above-mentioned computer instructions, it can execute the methods in the embodiments corresponding to Figures 2, 4, 7, 8a or 9 above. Therefore, it will not be described again here.

[0327] According to one aspect of this application, a computer program product is provided, comprising a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, enabling the computer device to perform the methods described in the embodiments corresponding to Figures 2, 4, 7, 8a, or 9 above; therefore, further details will not be provided here.

[0328] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. The computer-readable storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0329] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Those skilled in the art will understand that all or part of the processes for implementing the above embodiments and equivalent variations made in accordance with the claims of this application are still within the scope of this application.

Claims

1. A data processing method based on intelligent agents, characterized in that, include: Displays a conversation page with the target agent; the conversation page includes the conversation data of the target agent; In response to the publishing operation of the session data, the session data is converted into an image to be published and a content editing page is displayed. The content editing page includes the image to be published and is used to publish target content including the image to be published. The content page of the target content includes a session entry point with the target agent.

2. The method as described in claim 1, characterized in that, The conversation data includes dialogue information and response information. The method further includes: generating response information corresponding to the dialogue information in response to the dialogue information entered on the conversation page; and displaying the response information corresponding to the dialogue information on the conversation page.

3. The method as described in claim 2, characterized in that, The step of generating response information corresponding to dialogue information input on the conversation page includes: displaying at least one extended function control on the conversation page, each extended function control corresponding to a response generation strategy; generating response information corresponding to the dialogue information in response to a triggering operation of a target extended function control among the at least one extended function controls and the dialogue information input on the conversation page, wherein the response information corresponding to the dialogue information is generated according to the response generation strategy corresponding to the target extended function control.

4. The method as described in claim 1, characterized in that, The method further includes: displaying a personal page for any object, the personal page including a session entry point with the target agent; displaying a session page in response to a session triggering operation for the session entry point in the personal page; or, displaying a content page containing published content including a session entry point with the target agent, the session page being displayed in response to a session triggering operation for a session entry point in the content page; or, displaying a message page including session messages from at least one object, the at least one object including the target agent; displaying the session page in response to a session triggering operation for the target agent in the message page; or, displaying a search page including a session entry point with the target agent, the session page being displayed in response to a session triggering operation for the session entry point in the search page; or, displaying a comment page including comment content with the target agent; the session page being displayed in response to a session triggering operation for the target agent in the comment page.

5. The method as described in claim 1, characterized in that, The step of converting the session data into an image to be published in response to a publishing operation of the session data includes: converting the target session data into the image to be published in response to a selection operation of target session data in the session page and a publishing operation of the target session data.

6. The method as described in claim 5, characterized in that, The step of converting the target session data into the image to be published in response to a selection operation on the session page and a publishing operation on the target session data includes: displaying a share control on the session page in response to a selection operation on the session page; displaying a publishing control on the session page in response to a trigger operation on the share control; and converting the target session data into the image to be published in response to a trigger operation on the publishing control.

7. The method as described in claim 5, characterized in that, The session data includes dialogue information and response information. The step of responding to the selection operation of target session data in the session page includes: responding to the selection operation of at least one dialogue information and at least one response information in the session page, determining the target session data, wherein the target session data includes at least one dialogue information and at least one response information selected by the selection operation.

8. The method as described in claim 7, characterized in that, An object and a reply on the session page are treated as a set of session data. The step of determining the target session data in response to a selection operation on at least one dialogue message and at least one reply message in the session page further includes: in response to the number of groups of session data selected by the selection operation being a group, switching the display of the selection control for the unselected session data in the session page from a first style to a second style, or outputting a prompt message, wherein the first style session data is used to indicate that the corresponding session data can be selected, the second style session data is used to indicate that the corresponding session data cannot be selected, and the prompt message is used to indicate that the number of groups of session data selected by the selection operation has reached a group.

9. A data processing device based on an intelligent agent, characterized in that, include: A display unit is used to display a conversation page with the target intelligent agent, the conversation page including the conversation data of the target intelligent agent; The session data includes dialogue information and response information; A processing unit is configured to, in response to a publishing operation on the session data, convert the session data into an image to be published and display a content editing page, wherein the content editing page includes the image to be published and is used to publish target publishing content including the image to be published, and the content page of the target publishing content includes a session entry point with the target agent.

10. A computer device, characterized in that, include: A processor is used to execute computer programs; A computer-readable storage medium storing a computer program, which, when executed by the processor, performs the agent-based data processing method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, performs the agent-based data processing method as described in any one of claims 1 to 8.

12. A computer program product, characterized in that, The computer program product includes a computer program that is executed by a processor to implement the agent-based data processing method as described in any one of claims 1 to 8.

Images