Message processing method and device based on agent building platform, equipment, medium and product

Abstract

The invention discloses a message processing method and device based on an agent building platform, equipment, a medium and a product, in response to receiving demand information input by a user, a first message corresponding to the demand information is determined, the demand information is received through an agent built by the agent building platform, and the first message is sent to the user. The demand information comprises a first user identifier and a first channel, the first user identifier is used for identifying a target user of the first message, and the first channel is used for indicating a target client of the first message; determining a second user identifier based on the first user identifier and the first channel, the second user identifier being used for identifying a target user corresponding to the first channel; and sending the first message to a target user of the target client based on the second user identifier. Therefore, the user identifier in the to-be-processed message can be converted into the user identifier of the target user on the target client of the message, and the difference between the user identifiers on the source client and the target client of the message is broken through, so that the message reflecting the user demand on the intelligent agent can be effectively processed.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a message processing method, apparatus, device, medium, and product based on an intelligent agent platform. Background Technology

[0002] An intelligent agent building platform is the infrastructure used to build, manage, and apply intelligent agents. Based on artificial intelligence technology, it integrates data, algorithms, and tools to support intelligent agents in autonomously perceiving, making decisions, and executing tasks in specific scenarios, helping users (such as enterprises) efficiently develop professional intelligent applications. Currently, messages on the intelligent agent building platform can only be executed on a single client, failing to achieve cross-client processing. However, in many cases, user messages need to be processed across clients. Summary of the Invention

[0003] This application provides a message processing method, apparatus, device, medium, and product based on an intelligent agent platform. The intelligent agent can effectively process messages according to the user identifier of the target user on the destination client of the message. In particular, it can effectively process cross-client messages (i.e., messages that are different between the source client and the destination client), thereby improving the user experience brought by the intelligent agent platform.

[0004] To achieve the above objectives, the technical solutions provided in this application are as follows:

[0005] In a first aspect of this application, a message processing method based on an intelligent agent platform is provided, comprising:

[0006] In response to receiving user input demand information, a first message corresponding to the demand information is determined. The demand information is received by an intelligent agent built by an intelligent agent building platform. The demand information includes a first user identifier and a first channel. The first user identifier is used to identify the target user of the first message, and the first channel is used to indicate the destination client of the first message.

[0007] Based on the first user identifier and the first channel, a second user identifier is determined, wherein the second user identifier is used to identify the target user corresponding to the first channel;

[0008] Based on the second user identifier, the first message is sent to the target user of the destination client.

[0009] In some implementations, the demand information further includes a second channel, which indicates the source client of the first message, and the first user identifier indicates the target user corresponding to the second channel. Therefore, determining the second user identifier based on the first user identifier and the first channel includes:

[0010] The second user identifier is determined based on the first user identifier, the first channel, and the second channel.

[0011] As an example, determining the second user identifier based on the first user identifier, the first channel, and the second channel includes:

[0012] If the first channel is different from the second channel, then the second user identifier corresponding to the first user identifier is determined based on the pre-saved first mapping relationship.

[0013] As another example, determining the second user identifier based on the first user identifier, the first channel, and the second channel includes:

[0014] If the first channel is the same as the second channel, then the first user identifier is used as the second user identifier.

[0015] In some other implementations, before determining the first message corresponding to the demand information, the method further includes:

[0016] The target user and the second channel are obtained from the demand information, wherein the second channel is used to indicate the source client of the first message;

[0017] Based on a pre-saved second mapping relationship, the first user identifier corresponding to the third user identifier is determined, and the third user identifier is used to indicate the target user corresponding to the second channel.

[0018] Optionally, in this example, the first user identifier is a generic user identifier.

[0019] As an example, determining the second user identifier based on the first user identifier and the first channel includes:

[0020] Based on the pre-saved third mapping relationship, the second user identifier corresponding to the first user identifier is obtained, and the second user identifier is the user identifier corresponding to the first channel.

[0021] In some implementations, sending the first message to the target user of the destination client based on the second user identifier includes:

[0022] The first message is sent to the smart agent on the target client, causing the smart agent to send the first message to the target user indicated by the second user identifier.

[0023] In some implementations, a media interaction application corresponding to the source client of the first message is created on the destination client, and the media interaction application is allowed to receive push messages from the source client. In this case, the media interaction application on the target client of the target user receives the first message.

[0024] In some implementations, the mapping relationship between user identifiers corresponding to different clients is stored in an identity identification service, which is used to convert between user identifiers corresponding to different clients.

[0025] In a second aspect of this application, a message processing device based on an intelligent agent platform is provided, comprising:

[0026] The first obtaining unit is configured to, in response to receiving user input demand information, determine the first message corresponding to the demand information, wherein the demand information is received through an intelligent agent built by an intelligent agent building platform, and the demand information includes a first user identifier and a first channel, wherein the first user identifier is used to identify the target user of the first message, and the first channel is used to indicate the destination client of the first message;

[0027] The second obtaining unit is configured to determine a second user identifier based on the first user identifier and the first channel, wherein the second user identifier is used to identify the target user corresponding to the first channel;

[0028] The sending unit is configured to send the first message to the target user of the destination client based on the second user identifier.

[0029] In some implementations, the demand information further includes a second channel, which indicates the source client of the first message, and the first user identifier indicates the target user corresponding to the second channel. Therefore, the second obtaining unit is specifically used for:

[0030] The second user identifier is determined based on the first user identifier, the first channel, and the second channel.

[0031] As an example, the second obtaining unit is specifically used for:

[0032] If the first channel is different from the second channel, then the second user identifier corresponding to the first user identifier is determined based on the pre-saved first mapping relationship.

[0033] As another example, the second obtaining unit is specifically used for:

[0034] If the first channel is the same as the second channel, then the first user identifier is used as the second user identifier.

[0035] In some implementations, the first user identifier is a generic user identifier, and the apparatus further includes a third obtaining unit. The third obtaining unit is configured to:

[0036] Before obtaining the first message corresponding to the demand information, the target user and the second channel are obtained from the demand information, and the second channel is used to indicate the source client of the first message;

[0037] Based on a pre-saved second mapping relationship, the first user identifier corresponding to the third user identifier is obtained, and the third user identifier is used to indicate the target user corresponding to the second channel.

[0038] As an example, the second obtaining unit is specifically used for:

[0039] Based on the pre-saved third mapping relationship, the second user identifier corresponding to the first user identifier is obtained, and the second user identifier is the user identifier corresponding to the first channel.

[0040] In some implementations, the sending unit is specifically used for:

[0041] The first message is sent to the smart agent on the target client, causing the smart agent to send the first message to the target user indicated by the second user identifier.

[0042] In some implementations, a media interaction application corresponding to the source client of the first message is created on the destination client, and the media interaction application is allowed to receive push messages from the source client. In this case, the media interaction application on the target client of the target user receives the first message.

[0043] In some implementations, the mapping relationship between user identifiers corresponding to different clients is stored in an identity identification service, which is used to convert between user identifiers corresponding to different clients.

[0044] In a third aspect of this application, an electronic device is provided, comprising: a processor and a memory; the memory for storing instructions or computer programs; and the processor for executing the instructions or computer programs in the memory to cause the electronic device to perform the method provided in the first aspect or any implementation thereof.

[0045] In a fourth aspect of this application, a computer-readable storage medium is provided, wherein instructions are stored therein, which, when executed on a processor, cause the processor to perform the method provided by the first aspect or any implementation thereof.

[0046] In a fifth aspect of this application, a computer program product is provided, the computer program product comprising a computer program or instructions, which, when executed by a processor, implement the method provided by the first aspect or any implementation thereof.

[0047] Therefore, this application has the following beneficial effects:

[0048] This application provides a message processing method based on an intelligent agent platform. This method can be applied to a message processing device based on an intelligent agent platform. The method may include, for example, the following steps: In response to receiving user-inputted request information, determining a first message corresponding to the request information, wherein the request information is received by an intelligent agent built by the intelligent agent platform, and the request information may include at least a first user identifier and a first channel, wherein the first user identifier identifies the target user of the first message, and the first channel indicates the destination client of the first message; then, based on the first user identifier and the first channel, determining a second user identifier, which identifies the target user corresponding to the first channel; and then, based on the second user identifier, sending the first message to the target user of the destination client. In this way, the message processing device of the intelligent agent building platform can convert the user identifier in the message to be processed into the user identifier of the target user on the destination client of the message. This eliminates the difference between the user identifiers on the source client and the destination client of the message, and overcomes the difficulty of message processing being impossible because the user identifiers are different when the source client and the destination client are different. This enables messages that reflect user needs on the intelligent agent to be processed effectively, especially messages across clients (i.e. messages where the source client and the destination client are different). As a result, the user experience brought by the intelligent agent building platform is improved. Attached Figure Description

[0049] 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 recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 This is a schematic diagram of a system architecture applicable to an embodiment of this application;

[0051] Figure 2 A flowchart illustrating a message processing method based on an intelligent agent platform, provided as an embodiment of this application;

[0052] Figure 3 A schematic diagram of a message processing flow provided in an embodiment of this application;

[0053] Figure 4 A schematic diagram of another message processing flow provided in an embodiment of this application;

[0054] Figure 5 A schematic diagram of the structure of a message processing device 500 based on an intelligent agent building platform provided in this application embodiment;

[0055] Figure 6 This is a schematic diagram of the structure of an electronic device 600 provided in an embodiment of this application. Detailed Implementation

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

[0057] Low-code development platforms (LCDPs) are development platforms that allow for the rapid generation of applications with no coding (i.e., zero code) or minimal coding. Users can develop applications through a visual approach, enabling developers of varying experience levels to create web and mobile applications using drag-and-drop components and model-driven logic through a graphical user interface. Due to these characteristics, LCDPs have gained widespread popularity. For example, the ApaaS platform, as a low-code development platform, aims to provide enterprises and developers with an environment for rapidly building, deploying, and managing applications without requiring users to write large amounts of low-level code from scratch.

[0058] The intelligent agent building platform, also known as the intelligent agent development platform, focuses on building artificial intelligence (AI) capabilities. It provides functions such as AI skill orchestration, knowledge data processing, and effect optimization. It aims to quickly generate intelligent applications (such as meeting minutes generation and schedule management) through large language models (LLMs), making it a popular choice for enterprise users to develop intelligent applications.

[0059] Low-code development platforms and agent building platforms are two popular and complementary development tools. Their collaborative application can meet the full lifecycle needs of enterprise users, from lightweight assistants to complex systems. For example, the AI ​​capabilities of agent building platforms can be embedded into low-code development platforms, such as generating components through natural language or automatically correcting code, thus improving development efficiency. Alternatively, agent building platforms and low-code development platforms can be integrated into the same ecosystem. For instance, a customer relationship management (CRM) system built on a low-code development platform can utilize the intelligent analysis functions of the agent building platform to automate the processing of user data. Therefore, research and development of low-code development platforms, agent building platforms, or ecosystems integrating both are crucial for improving the quality of services provided to users.

[0060] Currently, the intelligent agent building platform can only process messages from a single client. That is, messages triggered by a user on the source client of the intelligent agent building platform cannot be processed across clients. For example, if a user enters a request on client A of the intelligent agent building platform: "Add schedule 1 to client A of the first group members," the intelligent agent building platform can complete this request because message 1 carrying schedule 1 needs to be sent to client A, and the user identifier of each member of the first group on client A is known. However, if a user enters a request on client A of the intelligent agent building platform: "Send meeting link 2 to client B of the first group members," the intelligent agent building platform needs to know the user identifier of each member on client B, as message 2 carrying meeting link 2 needs to be sent to client B of each member of the first group. This is unknown to the intelligent agent building platform, so the current intelligent agent building platform cannot handle cross-client messages like message 2. However, with the proliferation of clients that provide convenience for users' work and life, it is not uncommon for users to conduct cross-client message transmission between different clients. Therefore, realizing cross-client message transmission through intelligent agents has become an urgent problem to be solved.

[0061] Based on this, embodiments of this application provide a message processing method based on an intelligent agent building platform. This method may include, for example, the following: First, in response to receiving user-inputted request information, a message processing device based on the intelligent agent building platform (hereinafter referred to as the message processing device) determines a first message corresponding to the request information. This request information is received by an intelligent agent built by the intelligent agent building platform. The request information may include at least a first user identifier and a first channel, wherein the first user identifier is used to identify the target user of the first message, and the first channel is used to indicate the destination client of the first message; Next, the message processing device determines a second user identifier based on the first user identifier and the first channel. The second user identifier is used to identify the target user corresponding to the first channel; Thus, the message processing device sends the first message to the target user of the destination client based on the second user identifier.

[0062] In this way, the message processing device based on the intelligent agent building platform can convert the user identifier in the message to be processed into the user identifier of the target user on the destination client of the message. This eliminates the difference between the user identifiers on the source client and the destination client of the message, and overcomes the difficulty of message processing being impossible because the user identifiers are different when the source client and the destination client are different. This enables messages reflecting user needs on the intelligent agents built by the intelligent agent building platform to be processed effectively, especially messages across clients (i.e. messages where the source client and the destination client are different). As a result, the user experience provided by the intelligent agents built by the intelligent agent building platform is improved.

[0063] It should be noted that in this embodiment, when a user has a need to initiate a session on the intelligent agent building platform from the source client, they input a request, triggering a message processing device to obtain a message (such as a first message) corresponding to that request. The request information could be, for example, voice or text input by the user on the intelligent agent building platform where client A is located, such as "Send my schedule for today to my client B." Alternatively, it could be a user triggering (e.g., clicking) a "Create Route" button or other control on the intelligent agent building platform where client A is located to share the route with the default client C of the "Route," or prompting the user to select client D to open the "Route" via a pop-up window, thereby sharing the route with client D. In the above examples, client A is the source client, and clients B, C, and D are all destination clients. Typically, source client A can be a client on the intelligent agent building platform. If the source client and destination client are different, then even if it is the same user, the corresponding user identifier is likely to be different.

[0064] It should be noted that the entity implementing the message processing method based on the intelligent agent platform can be the message processing device based on the intelligent agent platform provided in the embodiments of this application. This message processing device based on the intelligent agent platform can be housed in an electronic device or a functional module of an electronic device. For example, this message processing device can be a functional module on a network device such as a server corresponding to the intelligent agent platform or a terminal device such as a mobile phone, used to implement the message processing function based on the intelligent agent platform provided in the embodiments of this application.

[0065] It should be noted that the message processing device provided in this application embodiment can be a function within the ecosystem of intelligent agents built by the intelligent agent building platform and the low-code development platform, designed to help users perform more convenient and faster requirement transformation. For example, within the ecosystem of intelligent agents and the low-code development platform, users can achieve message push between a single client or multiple clients based on simple operations, providing convenience for users' work and life. The term "intelligent agent" in this document can be understood to include at least the ecosystem built by the intelligent agent building platform; for example, it can refer to the ecosystem of intelligent agents and the low-code development platform.

[0066] For example, embodiments of this application can be applied to Figure 1 The system architecture is shown below. Figure 1 As shown, the system may include, but is not limited to, an intelligent agent building platform 10 and an intelligent agent 20 built through the intelligent agent building platform 10. The intelligent agent 20 may possess AI capabilities, which can be implemented by calling model 21. The developer 1 of the intelligent agent 20 can develop and build the intelligent agent 20 through page 30; once built, the intelligent agent 20 can be used by user 2 through page 40, providing capabilities such as AI capabilities.

[0067] Figure 2 This application provides a schematic flowchart of a message processing method based on an intelligent agent platform. This method can be applied to a message processing device based on an intelligent agent platform, which may include, for example, the following... Figure 5 The message processing device 500 shown is based on an intelligent agent platform.

[0068] like Figure 2 As shown, the method may include, for example, the following steps S101 to S103:

[0069] S101, in response to receiving the user input demand information, determine the first message corresponding to the demand information. The demand information is received by an intelligent agent built by the intelligent agent building platform. The demand information includes a first user identifier and a first channel. The first user identifier is used to identify the target user of the first message, and the first channel is used to indicate the destination client of the first message.

[0070] Among them, the users in S101 can correspond to Figure 1 User 2 in the application inputs requirement information through page 40. The method provided in this embodiment can correspond to the capabilities provided by the intelligent agent 20.

[0071] Request information can be understood as a task proposed by a user on an intelligent agent built on an intelligent agent building platform, requiring the assistance of that intelligent agent to complete. This request information may include, for example, the target user, the target action, and the target client for the task, instructing the target user to perform the target action on the target client.

[0072] The source client can refer to the client on the intelligent agent where the user inputs the required information. The destination client can refer to the client to which the first message needs to reach, or it can be considered the client for which the required information demands the execution of the target action. The destination client and the source client can be the same or different.

[0073] As an example, the interactive interface of an intelligent agent may include an input box for entering requirements, where users can enter their requirements based on those requirements.

[0074] As another example, the interactive interface of an intelligent agent can include controls corresponding to different needs. Users can operate the corresponding controls based on their needs, either directly or through pop-up windows to guide users to continue making selections and input their needs.

[0075] When a user completes the input of the demand information, the message processing device based on the intelligent agent platform can obtain the first message corresponding to the demand information. The first message may include relevant content from the demand information. Therefore, "the demand information includes a first user identifier and a first channel" in S101 can also be understood as "the first message includes a first user identifier and a first channel". For example, the first message may include, but is not limited to: a first user identifier that can identify the target user, a first channel that can instruct the target client, and a target action. The first message may also include a second channel that can instruct the source client. Optionally, the first message may also include other information on performing the target action on the target user of the target client, which is not limited in this embodiment.

[0076] In some possible implementations, the first user identifier can be an identifier indicating the target user corresponding to the second channel. For example, the source client of the first message is client A, and the second channel is used to indicate the channel of client A. The second channel can be channel A. The first user identifier can be the identifier of a legitimate target user B who has been registered on client A, which can be represented as channel A.user B id. This channel A.user B id can indicate the target user B on client A. It can be the username, account, or other information of the target user B on client A that can uniquely identify the target user B on client A. It can be understood as the identity information of the target user B on client A.

[0077] In some implementations, the first user identifier can be a generic user identifier, indicating the target user under a generic type. This generic user identifier is designed for converting and associating user identifiers across various clients, not a specific user identifier on a particular client. Still assuming the source client of the first message is client A, the second channel is channel A, and the identifier of the legitimate target user B already registered on client A is the third user identifier, which can be represented as channel A.user B id. The Identity Service can store the mapping relationship between the generic user identifier and the user identifiers of other clients. For example, a user's ID card number, phone number, or other uniquely identifying information can be directly used as the generic identifier for the user. Alternatively, the aforementioned identity information can be processed (e.g., hashed) to obtain the generic identifier for the user. Then, after the user inputs their request information, the conversation service can convert channel A.user B id to K.user B id.

[0078] As an example, prior to S101, the method may further include: S11, obtaining the target user and the second channel from the demand information, the second channel indicating the source client of the first message; S12, obtaining the first user identifier corresponding to the third user identifier based on a pre-saved second mapping relationship, the third user identifier indicating the target user corresponding to the second channel. The second mapping relationship may be stored in an Identity Service, the demand information indicating the target user corresponding to the second communication type, and the message processing device executing S11 may include: obtaining channel A.user B id based on the demand information. Therefore, S12 may involve converting channel A.user B id to K.user B id using the second mapping relationship stored in the Identity Service, where channel A.user B id may correspond to the third user identifier, and K.user B id may correspond to the first user identifier.

[0079] It should be noted that the number of target users can be one or more. If there are multiple target users, they can be related to each other, such as belonging to the same work group or department; or they can be unrelated, and users can select different target users when entering their requirements.

[0080] It is evident that obtaining the first message through S101 provides a data foundation for the target user on the destination client to fulfill their user needs, and also prepares the necessary work.

[0081] S102, based on the first user identifier and the first channel, determine the second user identifier, which is used to identify the target user corresponding to the first channel.

[0082] The Identity Service can store mapping relationships between user identifiers corresponding to different clients, used to implement conversion between user identifiers corresponding to different clients. Prior to S102, the method may also include: collecting user identifiers corresponding to each user on different clients on the Identity Service and constructing mapping relationships, which may include the first mapping relationship, second mapping relationship, and third mapping relationship mentioned herein. The first mapping relationship may include multiple sets of correspondences between user identifiers corresponding to the first channel and user identifiers corresponding to the second channel; the second mapping relationship may include multiple sets of correspondences between general-type user identifiers and user identifiers corresponding to the second channel; the third mapping relationship may include multiple sets of correspondences between general-type user identifiers and user identifiers corresponding to the first channel. Formally, each mapping relationship can be stored in an entity (such as a table), and different mapping relationships can be represented through different parts of this entity; alternatively, each mapping relationship can be stored in different entities.

[0083] In some implementations, when the first user identifier is used to indicate the target user corresponding to the second channel, and the first message includes the second channel, S102 may include, for example, obtaining the second user identifier based on the first user identifier, the first channel, and the second channel.

[0084] As an example, S102 may include: determining whether the first channel and the second channel indicate the same thing. If they are the same, it can be assumed that the source client and the destination client of the first message are the same, and the first message only needs to be executed on the source client. Therefore, the first user identifier can be directly recorded as the second user identifier to prepare for the execution of the target action. If the first channel and the second channel are different, it can be assumed that the source client and the destination client of the first message are different, and the first message needs to be executed on the destination client other than the source client. Therefore, the message processing device can obtain the second user identifier corresponding to the first user identifier based on the pre-saved first mapping relationship.

[0085] Still taking client A as the source client of the first message, channel A as the second channel, and channel A as the first user identifier (channel A.user B id) as an example, Figure 3As shown, if the second channel is also channel A, then the second user identifier is also channel A.user B id, and no conversion is needed. The target action can be directly executed on client A on the target user B identified by channel A.user B id. If the second channel is channel C, then the message processing device can obtain the user identifier corresponding to channel A.user B id on client C from the Identity Service, which can be represented as channel C.user B id. That is, the second user identifier is channel C.user B id. This makes it possible to execute the target action on client C on the target user B identified by channel C.user B id.

[0086] In some other implementations, if the first user identifier is a generic type user identifier, S102 may include, for example, obtaining a second user identifier corresponding to the first user identifier based on a pre-saved third mapping relationship, wherein the second user identifier is the user identifier corresponding to the first channel.

[0087] In this implementation, there is no need to determine whether the source client and the destination client are the same. The user identifier corresponding to the first user identifier in the first channel can be directly obtained from the IdentityService and recorded as the second user identifier.

[0088] Still taking client A as the source client of the first message, channel A as the second channel, and the identifier K.userB id corresponding to the general type of the first user identifier target user B as an example, Figure 4 As shown, if the first channel is channel A, the message processing device can obtain the user identifier corresponding to K.user B id on client A from the Identity Service, which can be represented as channel A.user B id. That is, the second user identifier is channel A.user B id. This makes it possible to execute the target action on the target user B identified by channel A.user B id on client A. If the second channel is channel C, the message processing device can obtain the user identifier corresponding to K.user B id on client C from the Identity Service, which can be represented as channel C.user B id. That is, the second user identifier is channel C.user B id. This makes it possible to execute the target action on the target user B identified by channel C.user B id on client C.

[0089] It is evident that the message processing device can obtain the second user identifier corresponding to the target user on the destination client based on the first user identifier in the first message, thus preparing for processing the first message.

[0090] S103, based on the second user identifier, send the first message to the target user of the destination client.

[0091] In some implementations, S103 may include: the message processing device sending a first message to a smart agent on the destination client, causing the smart agent to send the first message to the target user indicated by the second user identifier. Here, the smart agent can also be called a message push bot, which is a bot on the server corresponding to the destination client capable of pushing messages to users. After receiving the first message, the smart agent can send the first message to the target user indicated by the second user identifier.

[0092] It should be noted that in this embodiment of the application, the target user on the target client can receive the first message, requesting the creation of a media interaction application (such as a server, public account, etc.) corresponding to the source client of the first message on the target client, and allowing the media interaction application to receive push messages from the source client. In this case, the media interaction application on the target user's target client can receive the first message sent by the smart agent.

[0093] It should be noted that in the embodiments of this application, sending the first message to the target user of the target client may mean that the target user's target client has received the first message (such as an itinerary, payslip, etc.), or it may mean that a task (such as a schedule or meeting) or a tag (such as a birthday or anniversary) has been created. Therefore, it may not necessarily be presented in the form of a "message". It may also be a processing operation such as creating a task or adding a tag performed on the target client by the target action indicated by the first message. This processing operation can also be understood as the processing of the first message.

[0094] It should be noted that, in this embodiment, the ability to connect message processing functions between different clients hinges on the addition of an Identity Service to the message processing device. The mapping relationships stored in the Identity Service can be collected and recorded with user authorization. Creating these relationships can be based on user identity information, associating user identifiers of users with the same identity information across different clients to obtain a set of mapping relationships. Furthermore, for clients to process messages, users must grant each client permission to receive and send messages.

[0095] As can be seen, this method can convert the user identifier in the message to be processed into the user identifier of the target user on the destination client of the message, thus bridging the gap between the user identifiers on the source client and the destination client. This overcomes the difficulty of message processing being impossible due to different user identifiers on the source client and the destination client. It enables messages reflecting user needs on the intelligent agents built by the intelligent agent building platform to be processed effectively, especially messages across clients (i.e. messages with different source and destination clients). This improves the user experience provided by the intelligent agent building platform and the intelligent agents it builds.

[0096] Accordingly, this application also provides a message processing device 500 based on an intelligent agent platform, such as... Figure 5 As shown. The device 500 may include:

[0097] The first obtaining unit 501 is used to determine the first message corresponding to the demand information in response to receiving demand information input by the user. The demand information is received by an intelligent agent built by the intelligent agent building platform. The demand information includes a first user identifier and a first channel. The first user identifier is used to identify the target user of the first message, and the first channel is used to indicate the destination client of the first message.

[0098] The second obtaining unit 502 is used to determine a second user identifier based on the first user identifier and the first channel, wherein the second user identifier is used to identify the target user corresponding to the first channel;

[0099] The sending unit 503 is used to send the first message to the target user of the destination client based on the second user identifier.

[0100] In some implementations, the demand information (or first message) further includes a second channel, which indicates the source client of the first message, and the first user identifier indicates the target user corresponding to the second channel. Therefore, the second obtaining unit 502 is specifically used for:

[0101] The second user identifier is determined based on the first user identifier, the first channel, and the second channel.

[0102] As an example, the second obtaining unit 502 is specifically used for:

[0103] If the first channel is different from the second channel, then the second user identifier corresponding to the first user identifier is determined based on the pre-saved first mapping relationship.

[0104] As another example, the second obtaining unit 502 is specifically used for:

[0105] If the first channel is the same as the second channel, then the first user identifier is used as the second user identifier.

[0106] In some implementations, the device 500 further includes a third obtaining unit. The third obtaining unit is configured to:

[0107] Before obtaining the first message corresponding to the demand information, the target user and the second channel are obtained from the demand information, and the second channel is used to indicate the source client of the first message;

[0108] Based on a pre-saved second mapping relationship, the first user identifier corresponding to the third user identifier is determined, and the third user identifier is used to indicate the target user corresponding to the second channel.

[0109] As an example, the second obtaining unit 502 is specifically used for:

[0110] Based on the pre-saved third mapping relationship, the second user identifier corresponding to the first user identifier is determined, and the second user identifier is the user identifier corresponding to the first channel.

[0111] In some implementations, the sending unit 503 is specifically used for:

[0112] The first message is sent to the smart agent on the target client, causing the smart agent to send the first message to the target user indicated by the second user identifier.

[0113] In some implementations, a media interaction application corresponding to the source client of the first message is created on the destination client, and the media interaction application is allowed to receive push messages from the source client. In this case, the media interaction application on the target client of the target user receives the first message.

[0114] In some implementations, the mapping relationship between user identifiers corresponding to different clients is stored in an identity identification service, which is used to convert between user identifiers corresponding to different clients.

[0115] It should be noted that the specific implementation of the device 500 and the technical effects it achieves can be found in the relevant description of the method shown in the embodiments of this application.

[0116] In addition, this application also provides an electronic device, the device including a processor and a memory: the memory is used to store instructions or computer programs; the processor is used to execute the instructions or computer programs in the memory so that the electronic device performs any implementation of the method provided in this application.

[0117] See Figure 6 The diagram illustrates a structural schematic of an electronic device 600 suitable for implementing embodiments of the present disclosure. Terminal devices in embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0118] like Figure 6 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0119] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to exchange data with other devices wirelessly or via wired communication. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0120] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined in the methods of embodiments of this disclosure.

[0121] The electronic device provided in this embodiment belongs to the same inventive concept as the method provided in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0122] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium capable of being stored by a computing device, or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct a processor to execute the method provided in this application.

[0123] This application also provides a computer program product comprising one or more computer instructions. When the computer instructions are loaded and executed on a processor, the method provided in this application is performed, in whole or in part.

[0124] The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, or data center to another website, computer, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0125] When the computer program product is executed by a computer, the computer performs any of the aforementioned task flow optimization methods. The computer program product can be a software installation package; when any of the aforementioned task flow optimization methods is required, the computer program product can be downloaded and executed on the computer.

[0126] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0127] The units described in the embodiments of this application can be implemented in software or hardware. The names of the units / modules do not necessarily limit the specific unit itself.

[0128] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0129] In the context of embodiments of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0130] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems or apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.

[0131] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0132] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0133] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0134] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A message processing method based on an intelligent agent platform, characterized in that, include: In response to receiving user input demand information, a first message corresponding to the demand information is determined. The demand information is received by an intelligent agent built by an intelligent agent building platform. The demand information includes a first user identifier and a first channel. The first user identifier is used to identify the target user of the first message, and the first channel is used to indicate the destination client of the first message. Based on the first user identifier and the first channel, a second user identifier is determined, wherein the second user identifier is used to identify the target user corresponding to the first channel; Based on the second user identifier, the first message is sent to the target user of the destination client.

2. The method according to claim 1, characterized in that, The demand information also includes a second channel, which indicates the source client of the first message, and the first user identifier indicates the target user corresponding to the second channel. Determining the second user identifier based on the first user identifier and the first channel includes: The second user identifier is determined based on the first user identifier, the first channel, and the second channel.

3. The method according to claim 2, characterized in that, The step of determining the second user identifier based on the first user identifier, the first channel, and the second channel includes: If the first channel is different from the second channel, then the second user identifier corresponding to the first user identifier is determined based on the pre-saved first mapping relationship.

4. The method according to claim 2, characterized in that, The step of determining the second user identifier based on the first user identifier, the first channel, and the second channel includes: If the first channel is the same as the second channel, then the first user identifier is used as the second user identifier.

5. The method according to claim 1, characterized in that, Before determining the first message corresponding to the demand information, the method further includes: The target user and the second channel are obtained from the demand information, wherein the second channel is used to indicate the source client of the first message; Based on a pre-saved second mapping relationship, the first user identifier corresponding to the third user identifier is determined, and the third user identifier is used to indicate the target user corresponding to the second channel.

6. The method according to claim 5, characterized in that, The step of determining the second user identifier based on the first user identifier and the first channel includes: Based on the pre-saved third mapping relationship, the second user identifier corresponding to the first user identifier is determined, and the second user identifier is the user identifier corresponding to the first channel.

7. The method according to claim 1, characterized in that, Sending the first message to the target user of the destination client based on the second user identifier includes: The first message is sent to the smart agent on the target client, causing the smart agent to send the first message to the target user indicated by the second user identifier.

8. The method according to claim 1, characterized in that, The target client creates a media interaction application corresponding to the source client of the first message, and allows the media interaction application to receive push messages from the source client. The media interaction application on the target user's target client receives the first message.

9. The method according to any one of claims 1-8, characterized in that, The mapping relationship between user identifiers corresponding to different clients is stored in the identity identification service, which is used to realize the conversion between user identifiers corresponding to different clients.

10. A message processing device based on an intelligent agent platform, characterized in that, include: The first obtaining unit is configured to obtain a first message corresponding to the user-inputted demand information in response to the user's demand information. The demand information is received by an intelligent agent built by an intelligent agent building platform. The first message includes a first user identifier and a first channel. The first user identifier is used to identify the target user of the first message, and the first channel is used to indicate the destination client of the first message. The second obtaining unit is configured to obtain a second user identifier based on the first user identifier and the first channel, wherein the second user identifier is used to identify the target user corresponding to the first channel; The sending unit is configured to send the first message to the target user of the destination client based on the second user identifier.

11. An electronic device, characterized in that, The electronic device includes: a processor and a memory; The memory is used to store instructions or computer programs; The processor is configured to execute the instructions or computer program in the memory to cause the electronic device to perform the method according to any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a processor, cause the processor to perform the method according to any one of claims 1-9.

13. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed by a processor, implement the method described in any one of claims 1-9.

Images