HK40091078A - Notification message processing method, apparatus, computer device, and storage medium - Google Patents

Description

Methods, apparatus, computer equipment, and storage media for processing notification messages

Technical Field

This application relates to the field of Internet technology, and in particular to a method, apparatus, computer device, and storage medium for processing notification messages.

Background Technology

With the continuous development of internet and software technologies, enterprises in various fields can assign tasks through web-based business systems or business clients, and then send notification messages to staff via communication applications. Staff can then switch from the communication application to the web-based business system or business client to view and process the assigned tasks. However, this method of requiring a switch from a communication application to a web-based business system or business client reduces task processing efficiency.

Summary of the Invention

Therefore, it is necessary to provide a method, apparatus, computer device, and storage medium for processing notification messages that can improve task processing efficiency in response to the above-mentioned technical problems.

Firstly, this application provides a method for processing notification messages. The method includes:

Receive notification messages from sub-applications pushed by the intelligent robot;

The notification message is displayed as a target message card in the parent application's session page;

In response to an interactive operation triggered on the target message card, the intelligent robot sends an interactive request to the application backend of the sub-application.

Receive the processing result of the interaction request returned by the intelligent robot;

The processing status of the notification message is updated and displayed based on the processing result.

Secondly, this application also provides a notification message processing apparatus. The apparatus includes:

The receiving module is used to receive notification messages pushed by the intelligent robot to the sub-application;

The message display module is used to display the notification message in the form of a target message card in the session page of the parent application;

The sending module is used to respond to the interactive operation triggered on the target message card and send an interactive request to the application background of the sub-application through the intelligent robot;

The receiving module is also configured to receive the processing result of the interaction request returned by the intelligent robot;

The update display module is used to update and display the processing status of the notification message based on the processing result.

Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

Receive notification messages from sub-applications pushed by the intelligent robot;

The notification message is displayed as a target message card in the parent application's session page;

In response to an interactive operation triggered on the target message card, the intelligent robot sends an interactive request to the application backend of the sub-application.

Receive the processing result of the interaction request returned by the intelligent robot;

The processing status of the notification message is updated and displayed based on the processing result.

Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

Receive notification messages from sub-applications pushed by the intelligent robot;

The notification message is displayed as a target message card in the parent application's session page;

In response to an interactive operation triggered on the target message card, the intelligent robot sends an interactive request to the application backend of the sub-application.

Receive the processing result of the interaction request returned by the intelligent robot;

The processing status of the notification message is updated and displayed based on the processing result.

Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

Receive notification messages from sub-applications pushed by the intelligent robot;

The notification message is displayed as a target message card in the parent application's session page;

In response to an interactive operation triggered on the target message card, the intelligent robot sends an interactive request to the application backend of the sub-application.

Receive the processing result of the interaction request returned by the intelligent robot;

The processing status of the notification message is updated and displayed based on the processing result.

The aforementioned notification message processing method, apparatus, computer equipment, storage medium, and computer program product receive notification messages pushed by an intelligent robot to a sub-application, display the notification message in the form of a target message card, thereby reaching the target object through the notification message and informing the target object that another object has performed an operation in the sub-application. Furthermore, it can also notify the target object to perform corresponding interactions, thus avoiding missed interactions due to failure to reach the target object. In addition, by performing interactive operations on the target message card, the interaction request is sent to the application background of the sub-application via the intelligent robot, thus eliminating the need to switch from the parent application to the sub-application for interactive operations, improving interaction efficiency. Moreover, upon receiving the processing result of the interaction request returned by the intelligent robot, the processing status of the notification message is updated and displayed on the conversation page, thereby informing the target object that the notification message has been processed after completion, preventing the target object from being unaware whether their interaction request has been executed, and improving user experience. Finally, using intelligent robots as a communication bridge between the parent and child applications can effectively ensure data communication between them, so that operations performed on the child application can reach the corresponding target objects in a timely and effective manner, enabling the target objects to interact in a timely manner based on the notification messages, which helps to improve interaction efficiency.

Sixthly, this application provides a method for processing notification messages. The method includes:

Push notification messages from child applications to target objects in the parent application, so that the parent application displays the notification messages in the form of target message cards on the session page;

Receive an interaction request initiated by the parent application; the interaction request is generated by the parent application upon detecting an interaction operation triggered on the target message card;

The interaction request is forwarded to the application backend of the sub-application, so that the application backend executes the interaction request, obtains the processing result, and provides feedback.

When the processing result is received from the application's backend, the processing result is pushed to the target object so that the parent application updates and displays the processing status of the notification message based on the processing result.

Seventhly, this application also provides a notification message processing apparatus. The apparatus includes:

The push module is used to push notification messages from the child application to target objects in the parent application, so that the parent application displays the notification messages in the form of target message cards on the conversation page;

A receiving module is used to receive an interaction request initiated by the parent application; the interaction request is generated by the parent application when it detects an interaction operation triggered on the target message card;

The forwarding module is used to forward the interaction request to the application backend of the sub-application, so that the application backend can execute the interaction request, obtain the processing result, and provide feedback.

The push module is further configured to push the processing result to the target object when it receives the processing result from the application's backend, so that the parent application updates and displays the processing status of the notification message based on the processing result.

Eighthly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

Push notification messages from child applications to target objects in the parent application, so that the parent application displays the notification messages in the form of target message cards on the session page;

Receive an interaction request initiated by the parent application; the interaction request is generated by the parent application upon detecting an interaction operation triggered on the target message card;

The interaction request is forwarded to the application backend of the sub-application, so that the application backend executes the interaction request, obtains the processing result, and provides feedback.

When the processing result is received from the application's backend, the processing result is pushed to the target object so that the parent application updates and displays the processing status of the notification message based on the processing result.

Ninthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

Push notification messages from child applications to target objects in the parent application, so that the parent application displays the notification messages in the form of target message cards on the session page;

Receive an interaction request initiated by the parent application; the interaction request is generated by the parent application upon detecting an interaction operation triggered on the target message card;

The interaction request is forwarded to the application backend of the sub-application, so that the application backend executes the interaction request, obtains the processing result, and provides feedback.

When the processing result is received from the application's backend, the processing result is pushed to the target object so that the parent application updates and displays the processing status of the notification message based on the processing result.

Tenthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

Push notification messages from child applications to target objects in the parent application, so that the parent application displays the notification messages in the form of target message cards on the session page;

Receive an interaction request initiated by the parent application; the interaction request is generated by the parent application upon detecting an interaction operation triggered on the target message card;

The interaction request is forwarded to the application backend of the sub-application, so that the application backend executes the interaction request, obtains the processing result, and provides feedback.

When the processing result is received from the application's backend, the processing result is pushed to the target object so that the parent application updates and displays the processing status of the notification message based on the processing result.

The aforementioned notification message processing method, apparatus, computer equipment, storage medium, and computer program product establish a data communication bridge between the parent application and the child application. When another object performs an operation in the child application, a notification message can be promptly pushed to the target object in the parent application. The parent application then displays the notification message as a target message card on the session page, thereby reaching the target object and informing them that another object has performed an operation in the child application. Furthermore, it can notify the target object to perform a corresponding interaction, thus preventing missed interactions due to failure to reach the target object. In addition, when the target object triggers an interaction operation on the target message card, it receives an interaction request initiated by the parent application and forwards the request to the child application's application backend. The application backend then processes the interaction request, obtains the processing result, and provides feedback, allowing interaction without switching from the parent application to the child application, improving interaction efficiency. Moreover, pushing the processing result from the application backend to the target object allows the parent application to update and display the notification message processing status on the session page. After processing is complete, the parent application can notify the target object that the notification message has been processed, ensuring the target object is aware of whether their interaction request has been executed, thus improving user experience.

Attached Figure Description

Figure 1 is an application environment diagram of a notification message processing method in one embodiment;

Figure 2 is a flowchart illustrating a notification message processing method in one embodiment;

Figure 3 shows a session page intent in one embodiment where notification messages are displayed in the form of target message cards;

Figure 4 shows a session page intent in another embodiment where notification messages are displayed in the form of target message cards;

Figure 5 shows a session page intent in another embodiment where notification messages are displayed in the form of target message cards;

Figure 6 shows a session page intent in one embodiment that displays notification messages and notification messages after updating the processing status;

Figure 7 shows a session page intent in another embodiment that displays notification messages and notification messages after updating the processing status;

Figure 8 shows a session page intent in another embodiment where notification messages are displayed in the form of target message cards;

Figure 9 shows a session page intent in one embodiment that displays notification messages and notification messages after updating the processing status;

Figure 10 shows a session page intent in another embodiment where notification messages are displayed in the form of target message cards;

Figure 11 shows the intent of a session page displaying the processing results and corresponding notification messages in one embodiment;

Figure 12 is a flowchart illustrating the steps for configuring an intelligent robot in another embodiment;

Figure 13 is a flowchart illustrating a notification message processing method in another embodiment;

Figure 14 is a structural block diagram of the FunView cross-platform framework in one embodiment;

Figure 15 is a structural block diagram of a notification message processing device in one embodiment;

Figure 16 is a structural block diagram of a notification message processing device in another embodiment;

Figure 17 is a structural block diagram of a notification message processing device in another embodiment;

Figure 18 is an internal structure diagram of a computer device in one embodiment;

Figure 19 is an internal structural diagram of a computer device in another embodiment.

Detailed Implementation

To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

The notification message processing method provided in this application embodiment can be applied to the application environment shown in Figure 1. The terminal 102 communicates with the application backend 104 of the sub-application and the backend of the intelligent robot (hereinafter referred to as the robot backend) 106 via a network. A data storage system can store the data that the application backend 104 needs to process. The data storage system can be integrated into the application backend 104 or placed in the cloud or other network servers. The terminal 102 receives notification messages from the sub-application pushed by the robot backend 106 corresponding to the intelligent robot; displays the notification messages as target message cards in the session page of the parent application; responds to interactive operations triggered on the target message card, sends an interaction request to the application backend 104 of the sub-application through the intelligent robot; receives the processing result returned by the robot backend 106 corresponding to the intelligent robot in response to the interaction request; and updates and displays the processing status of the notification messages based on the processing result.

The terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices, etc.

Application backend 104 and robot backend 106 can be independent physical servers or service nodes in a blockchain system. The service nodes in the blockchain system form a peer-to-peer (P2P) network. The P2P protocol is an application layer protocol that runs on top of the Transmission Control Protocol (TCP).

In addition, the application backend 104 and the robot backend 106 can be server clusters composed of multiple physical servers, and can be cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

In one embodiment, as shown in FIG2, a method for processing notification messages is provided. Taking the application of this method to terminal 102 in FIG1 as an example, the method includes the following steps:

S202, Receive notification messages from the intelligent robot pushing sub-applications.

The intelligent robot can be a virtual robot in the background, configured with a communication account on the parent application (such as a communication application). Operators can interact with the intelligent robot on the parent application. For example, an operator can @ the intelligent robot on the conversation page of a communication group or the conversation page of a member in their address book, thus enabling real-time interaction, such as asking the intelligent robot a question. Another example is when another operator initiates a task in a sub-application; the intelligent robot can receive a notification message for that task and push it to the communication account of the person responsible for handling it. Furthermore, the intelligent robot can also interact with the application's backend.

Sub-applications can refer to applications running within the system environment provided by the parent application, such as cloud storage applications, smart transportation applications, enterprise to-do list applications, screen mirroring applications, live streaming applications, conferencing applications, and other mobile applications. Additionally, a sub-application can also refer to a public account applied for within the parent application. The parent application can be an application that provides the system environment for the sub-application, including communication applications, office applications, or payment applications; the communication application can be an enterprise communication application or a personal communication application.

The notification message can be: a message requesting the target object to grant file access permissions, a message inviting the target object to join the target task group, a message prompting the target object to complete the pending task, and a message notifying the target object that another object has performed a first operation or a second operation on the target file. The target file can be a document of the target. The first operation can be editing, liking, saving, or commenting on the target file. The second operation can be uploading the target file.

In one embodiment, S202 may specifically include: the terminal receiving a notification message obtained when a sub-application pushed by a smart robot triggers a target event. For example, the terminal receives a notification message through the parent application when a sub-application pushed by a smart robot to a target communication group or group member object triggers a target event.

The target events include: inviting the target object to join the target task group, requesting the target object to grant file access permissions, prompting the target object to complete the pending task, and other objects performing at least one of the first or second operations on the target file. Target events correspond to notification messages; for example, if the target event is inviting the target object to join the target task group, then the notification message will be the message inviting the target object to join the target task group.

The target task group can be a communication group, task team, or personal or shared space on a cloud drive for handling the target task.

File access permissions are the permission information required to access a target file. Those with the required permissions are allowed to access the target file, while those without the required permissions will not be able to access the target file.

Tasks to be done can be tasks initiated by operators (i.e., initiators) through sub-applications that require approval from the target (such as the person in charge), such as applying for a promotion, requesting leave, and financial insurance.

S204, In the parent application's session page, the notification message is displayed as a target message card.

The target message card can be a carrier for displaying notification messages; that is, the notification message is displayed in the target message card, thus appearing as a card on the parent application's session page. The target message card can be a template card for a cross-platform application generated based on a cross-platform engine, meaning it can be applied to parent applications on different operating systems. The card type of the target message card can be interactive, graphic/text, selection-based, or text notification, or a hybrid of two or more of these types.

A conversation page can be a page for conversations between members of the target communication group (including the target object) and the intelligent robot, or a page for interaction between the target object and the intelligent robot.

In one embodiment, upon receiving a notification message, the terminal can display the keyword of the notification message on the parent application's message homepage, such as displaying the keyword in the message entry bar of the smart robot on the message homepage, or displaying the keyword in the message entry bar of the target communication group. When the message entry bar of the smart robot or the message entry bar of the target communication group is triggered, the user is directed to the conversation page of the smart robot or the conversation page of the target communication group.

In one embodiment, the terminal can determine the service type based on the notification message; obtain a matching target message card based on the service type, and then display the notification message in the form of a target message card in the session page of the parent application. This service type can be, for example, a service to join a task group, a request for file access permissions, a notification for pending tasks, a file interaction service, or a notification for uploading files.

Different business types can correspond to different template message cards. For example, when the business type is to invite a target object to join a target task group, the target message card can be an interactive model card. When the target object clicks on the target message card, it can view the information of the target task group and join the target task group.

Different business types can correspond to different card types. Specifically: business types that involve joining a task group can use text notification or interactive card types; business types that request file access permissions can use interactive or selection card types; business types that provide reminders for pending tasks can use interactive or graphic card types; and business types that involve file interaction and file upload reminders can use text notification card types.

Next, S204 will be explained in different scenarios, as follows:

Scenario 1: Text notification application scenario

In one instance, when a text notification-type target message card is obtained based on the business type corresponding to the notification message, the target message card is displayed on the parent application's session page, and the notification message is also displayed within that target message card. Furthermore, when the object of interaction is a file, the file information of that file is also displayed in the target message card.

For example, when an operator (such as Zhang San) uploads a document introducing the cloud storage product through a cloud storage application, the cloud storage application generates a notification message and sends it to the intelligent robot, or the cloud storage application sends an upload message to the intelligent robot, causing the intelligent robot to generate a notification message. The intelligent robot then pushes this notification message to a designated target or to the target communication group where the operator is located. In addition, the document can also be pushed along with the notification message. This notification message is used to inform the target that Zhang San has uploaded a document. The corresponding business type is the document upload notification business type. The system retrieves the target message card corresponding to this business type and then displays the notification message and document information on the target message card, as shown in Figure 3(a).

When an operator edits a version of the requirements document, the cloud storage application sends a notification message containing the document's edited content to the intelligent robot, or directly sends the edited content. This allows the intelligent robot to generate a notification message based on the edited content, which is then pushed to the target user or to the target communication group where the operator is located. Specifically, this notification message informs the target user that Zhang San has uploaded and edited a document; the corresponding business type is the document interaction business type. The application retrieves the target message card corresponding to this business type and displays the notification message containing the edited content on the target message card, as shown in Figure 3(b).

When an operator initiates a resignation application in the to-do list application, a resignation document is generated based on the filled-in resignation information. The resignation document and notification message are then sent to the intelligent robot, or the operator sends the resignation document, prompting the intelligent robot to generate a notification message based on the resignation document. The intelligent robot then pushes the notification message and resignation document to the target recipient. The notification message serves as a prompt to the target recipient regarding the resignation application. The corresponding business type is the prompt business type of the to-do list task. The system retrieves the target message card corresponding to this business type and then displays the resignation document and notification message on the target message card, as shown in Figure 3(c).

When an operator initiates a task in a task application, such as an iterative task of an application, a notification message including the task name, the list to which it belongs, the participants, and the due date is sent to the intelligent robot, or the task name, the list to which it belongs, the participants, and the due date are sent to the intelligent robot, so that the intelligent robot can generate a notification message based on this information, and then push the notification message to the target object. The terminal displays the notification message pushed to the target object in the target message card through the parent application, as shown in Figure 3(d).

Scenario 2: Image and text-based application scenarios

In one instance, when the notification message is an invitation to a target object to join a target task group, the terminal obtains a graphic target message card based on the service type corresponding to the notification message. The terminal divides the target message card into a first area and a highlighted second area; the notification message is displayed in the first area; and then, the icon and keywords associated with the target task group are displayed in the second area.

The first area of the target message card is mainly used to display text content; the second area can refer to the main area, which is mainly used to display graphics, or a mixture of graphics and text.

For example, if an operator has a space in their cloud storage application, the operator can request a target (such as a colleague) to join that space. If the target is invited, the cloud storage application sends a notification message generated based on the invitation to the intelligent robot, or sends an invitation so that the intelligent robot generates a notification message upon receiving the invitation. The intelligent robot then sends this notification message to the target's communication account. The parent application can then display the main information of the notification message in the first area, such as "Zhang San invites you to join the space." Additionally, the second area displays the space name and icon from the notification message, as shown in Figure 4(a). The second area uses a different color than the first area to emphasize the main theme and create a sense of occasion.

Furthermore, if an operator invites a target to join a list in a to-do application, the list can be a task group for a target task (hereinafter referred to as the target task group). In this case, the to-do application sends a notification message generated based on the join message to the intelligent robot, or sends join information so that the intelligent robot can generate a notification message based on the join information. Then, the intelligent robot pushes the notification message to the target's communication account. At this time, the parent application can display the subject information of the notification message in the first area and display the group name, creator name, and member identifier of the target task group in the notification message in the second area, as shown in Figure 4(b).

Scenario 3: Interactive Application Scenarios

In interactive application scenarios, interaction can be achieved through controls, which display the corresponding functional controls in the target message card. Alternatively, interaction can be conducted in a conversation-like format, displaying the message in a similar structure and providing quick access to comments or replies. These two methods will be explained in detail below:

(1) Interaction scenarios using controls

In one embodiment, when the notification message is a message requesting the target object to grant file access permissions, the terminal obtains an interactive target message card based on the service type corresponding to the notification message, displays the notification message and an authorization consent control in the target message card, and may also display candidate authorization options and an authorization denial control in the target message card.

The authorization control triggers an authorization request, allowing the application backend to grant file access permissions to operators (such as those requesting file access). Operators with file access permissions can then access the corresponding file.

The Deny Authorization control is used to trigger a denial authorization request, so that the application backend can deny file access permissions to the operator based on the denial authorization request. Operators who do not have the necessary file access permissions will not be able to access the corresponding file.

The candidate authorization options can include editable permissions and preview-only permissions, as well as a deny authorization option. The editable permission authorization option triggers an editable authorization request, granting the operator editable and access permissions, allowing them to access and edit the corresponding file. The preview-only permission authorization option triggers a preview-only authorization request, granting the operator preview-only access permissions, allowing them to access the corresponding file but not edit it.

For example, an operator initiates a document access permission request in a document application. The document application then sends a notification message generated based on this request to the intelligent robot, or sends the request to cause the intelligent robot to generate a notification message based on the request. The intelligent robot then sends the notification message to the target object. The parent application displays the target message card on the conversation page between the parent and document applications, and then displays the notification message in a structured format within the target message card. This includes extracting the name of the document to be requested, the applicant's name, and the reason for the request. Additionally, the target card displays "deny authorization" and "accept authorization" controls, as shown in Figure 5.

In addition to displaying the deny authorization control and the agree authorization control in the target message card, candidate authorization options can also be displayed. These candidate authorization options are displayed in the target message card in the form of a drop-down menu, as shown in Figures 6(a) and (b).

(2) Interactive scenarios similar to conversations

In one embodiment, when the notification message is a prompt message for commenting on or replying to a target file, the terminal obtains an interactive target message card based on the service type corresponding to the notification message. The target message card displays the comment information or reply information from the notification message in a conversation-like manner, as shown in Figures 7(a), (b), and (c). Here, an underlined comment can refer to commenting on a specific part of the document. Therefore, the target user can view the comment information or reply information of the target file, and can also reply to the comment information and reply information on the page displaying the notification message.

In another embodiment, when the notification message is initiated by the operator for a pending task, the terminal obtains an interactive target message card based on the service type corresponding to the notification message, and displays the notification content about the operator in the notification message in the target message card in a conversation-like manner, as shown in Figure 7(d).

Furthermore, when the notification message is a prompt message indicating a "like" to the target file, the "like" information from the notification message is displayed in the target message card in a conversation-like manner, as shown in Figures 8(a) and 8(b). Figure 8(a) shows a "like" for a document, and Figure 8(b) shows a "like" for a comment on a document.

Scenario 4, Selective Application Scenarios

In one embodiment, when the notification message is a progress message indicating the task to be performed by the target object, the terminal obtains an interactive target message card based on the service type corresponding to the notification message, and displays the notification message and corresponding selection controls in the target message card.

For example, when an operator initiates a progress query for a task in the to-do list application, or when the application automatically initiates a progress query, the application sends a notification message to the intelligent robot based on the task's progress information, task name, belonging list, participants, and due date. Alternatively, it sends the same information to the intelligent robot so that the robot can generate a notification message. The intelligent robot then pushes this notification message to the target object, and displays the task's status, the notification message, a "Remind Later" control, and a "Completed" control on the target message card, as shown in Figure 9. The task's status can be displayed as a title in the target message card to highlight its position.

S206, in response to an interactive operation triggered on the target message card, sends an interactive request to the application backend of the sub-application via the intelligent robot.

The application backend of a sub-application can be the backend server of the sub-application.

In one embodiment, S206 may specifically include: the terminal generating a matching interaction message in response to an interaction operation triggered on the target message card; encrypting the interaction message; encapsulating the encrypted interaction message as a message body to obtain an interaction request; and sending the interaction request to the application backend of the sub-application through the intelligent robot.

The interactive message can be information obtained by performing the interactive operation, such as information about opening a file or granting file access permissions. The encryption of the interactive message can be based on either symmetric or asymmetric encryption methods.

Specifically, in response to an interactive operation triggered on the target message card, the terminal sends an interactive request to the background of the intelligent robot through the parent application, and the background of the intelligent robot sends the interactive request to the application background of the sub-application.

In one embodiment, when the notification message requests file access permissions from the target object, the terminal displays an authorization control in the target message card. S206 may specifically include: in response to the triggering of the authorization control, the terminal sends an authorization request to the application backend of the sub-application via a smart robot, as shown in Figure 5. Thus, the operator requesting file access permissions can obtain them.

In one embodiment, when the notification message is a request for file access permissions from the target object, in addition to displaying an authorization control on the target message card, candidate authorization options can also be displayed in the target message card, as shown in Figure 5; the terminal responds to the selection operation of the candidate authorization options and selects the target authorization item. S206 may specifically include: the terminal responds to the triggering operation of the authorization control, generates an authorization request based on the target authorization item, and sends the authorization request to the application backend of the sub-application through the intelligent robot.

The candidate authorization options can include editing permissions and preview-only permissions. Therefore, the above scheme allows you to select one of the permissions to grant file access permissions to the operator requesting the permission. This allows you to develop different permissions for different people according to the actual situation, which can not only share information with relevant people, but also effectively improve information security.

If it's necessary to deny permissions to operators requesting file access, authorization denial can be quickly achieved by setting up a denial control. Specifically, this involves displaying a denial control on the terminal in the location corresponding to the grant-grant control; and, in response to triggering the denial control, sending a denial request to the application's backend via a smart chatbot. Therefore, this solution allows for authorization denial on the session page, improving operational efficiency.

In one embodiment, when the notification message is an invitation for a target object to join a target task group, the terminal divides the target message card into a first area and a highlighted second area; the notification message is displayed in the first area; and the icon and keywords associated with the target task group are displayed in the second area, as shown in Figure 4. S206 may specifically include: the terminal responding to an interactive operation triggered on the second area of the target message card by displaying a join page or confirmation window; responding to a join operation triggered on the join page or confirmation window by sending a join request to the application backend of the sub-application via a smart robot; or, responding to a refuse join operation triggered on the join page or confirmation window by sending a refuse join request to the application backend of the sub-application via a smart robot.

In one embodiment, when the notification message is a message prompting the target object to complete a pending task; S206 may specifically include: the terminal responding to a display operation triggered on the target message card and displaying the pending task on the task processing page of the parent application; when the pending task is completed, sending a task status change request to the application background of the sub-application through the intelligent robot.

S208, Receive the processing result of the interaction request returned by the intelligent robot.

The processing result can be the result of the application backend processing the interaction. For example, if the interaction request is an authorization request, the processing result could be granting file access permissions to the operator requesting the file access permission; this file access permission could be the permission to edit the file or the permission to preview the file only. As another example, if the interaction request is a request to join a target task group, the processing result would be the result of the operator requesting to join the target task group being added to that target task group.

S210, Update and display the processing status of the notification message based on the processing result.

In one embodiment, after receiving the processing result, the terminal can update the processing status of the notification message based on the processing result, and then display the updated notification message as a target message card on the session page.

For example, as shown in Figure 5, when the target user clicks the "Agree to Authorize" control in Figure 5, the terminal sends an authorization request to the document application's backend via the intelligent robot, agreeing to grant permissions to the requester (i.e., the operator requesting file access permissions). Upon receiving the authorization request, the application backend grants the requester file access permissions, thus granting the requester file access rights. Furthermore, the application backend returns the processing result to the target user's terminal, updating the processing status of the notification message based on this result. The updated notification message is then displayed as a target message card on the conversation page, as shown in Figure 5. Similarly, when the target user selects the editable or preview-only authorization option in Figure 6, the updated processing status notification message is displayed on the conversation page, indicating whether editable permissions or preview-only permissions have been granted, as detailed in Figure 6.

In addition, the application backend will send the processing result to the requester's terminal, update the status of the notification message based on the processing result, and display the updated notification message as a target message card on the session page, as shown in Figure 11.

In one embodiment, when an interactive message is sent to the intelligent robot, or when the intelligent robot's communication account is added to the communication group of the parent application, or when the intelligent robot's communication account is removed from the communication group, or when a session page for interacting with the intelligent robot is entered, the terminal generates an interactive event; the interactive event is encrypted to obtain an encrypted interactive event; the encrypted interactive event is called back to the intelligent robot so that the intelligent robot can decrypt the encrypted interactive event and process the decrypted interactive event.

For example, when a target sends a text message or a mixed text/image message to the intelligent robot in a communication group, or sends a text message or a mixed text/image message to the intelligent robot on a conversation page, an interaction event is generated based on the text message or mixed text/image message. This interaction event is then encrypted and sent to the intelligent robot, which decrypts it to obtain the interaction event, and subsequently the text message or mixed text/image message, from which it replies. Alternatively, when adding an intelligent robot's communication account to a communication group, an interaction event for binding is generated based on the group's account. This interaction event is then encrypted and sent to the intelligent robot, which decrypts it to obtain the group's account, and subsequently binds the group's account to the intelligent robot's communication account.

In the above embodiments, by receiving notification messages from the intelligent robot pushed to the sub-application, and displaying these notification messages as target message cards, the target object is reached through notification messages. This notifies the target object that another object has performed an operation in the sub-application, and also notifies the target object to perform the corresponding interaction, thus preventing missed interactions due to failure to reach the target object. Furthermore, by performing interaction operations on the target message card, the interaction request is sent to the sub-application's application background via the intelligent robot, eliminating the need to switch from the parent application to the sub-application, improving interaction efficiency. Moreover, upon receiving the processing result of the interaction request from the intelligent robot, the processing status of the notification message is updated and displayed on the conversation page. This notifies the target object that the notification message has been processed, preventing the target object from being unaware that their interaction request has been executed, thus improving user experience. Finally, using the intelligent robot as a communication bridge between the parent and sub-applications effectively ensures data communication between them, allowing operations performed on the sub-application to reach the corresponding target object in a timely and effective manner, enabling the target object to perform timely interaction operations based on the notification messages, further improving interaction efficiency.

To better understand the above scheme, we will explain it in conjunction with Figures 6 and 11, as follows:

When a requester wants access to a document with the name 'a', they request access from the target object within the cloud storage application (i.e., the sub-application). At this time, the cloud storage application's intelligent robot sends a notification message requesting file access to the target object's communication application (i.e., the parent application). The parent application receives the notification message pushed by the intelligent robot to the sub-application and then displays the notification message as a target message card in the parent application's conversation page, as shown in Figure 6. If the target object wants to grant the requester editing permissions, they can select the editable authorization option in Figure 6; if they want to grant the requester only preview permissions, they can select the preview-only authorization option in Figure 6 and then click the "Agree to Authorization" control. The intelligent robot then sends an authorization request to the cloud storage application's backend, which grants the requester either editable or preview-only permissions based on the authorization request. After granting the corresponding permissions, the processing result is sent to the target object. The communication application on the target object's side receives the processing result returned by the intelligent robot and updates the processing status of the notification message based on the processing result, such as updating it to "editable permission granted" or "preview-only permission granted," and then displays it, as shown in Figure 6. On the other hand, the cloud storage application can also send the processing result to the requester through the intelligent robot and display it in combination with the notification message and the processing result. For example, when the target object agrees to grant editable permission, "Access request approved" is displayed as the subject information along with the processor, access permissions, and the name of the requested document in the notification message, as shown in Figure 11(a). As another example, when the target object refuses the requester's permission to obtain the document, "Access request denied" is displayed as the subject information along with the processor and the name of the requested document in the notification message, as shown in Figure 11(b).

In one embodiment, prior to S202, the intelligent robot can be configured, and the specific configuration process includes:

S1202, Displaying the robot details page.

The robot details page can be a page that displays various information about the intelligent robot, including the robot's interface address.

In one embodiment, the intelligent robot can send notification messages to the corresponding target communication group or target object. The terminal displays the corresponding message card on the session page of the parent application, and then displays the notification message in the message card. When the mouse pointer is detected above the message card, the terminal displays the robot details page through the parent application.

S1204, in response to a configuration request triggered on the robot details page, displays the robot configuration page.

The robot configuration page can be a page used to configure robot parameters.

In one embodiment, the configuration request operation includes clicking on the robot interface address in the robot details page; S1204 may specifically include: displaying the robot configuration page in response to the click on the robot interface address in the robot details page. For example, when the target object clicks on the robot interface address in the robot details page with the mouse, the system switches from the robot details page to the robot configuration page.

S1206, in response to a configuration operation triggered on the robot configuration page, configures the message receiving parameters and message sending parameters of the intelligent robot, as well as the frequency parameters for the intelligent robot to send messages.

Among them, the message receiving parameters can be parameters used by the robot to receive messages. For example, after configuring the message receiving parameters, it can receive information sent by the corresponding sub-application, such as receiving information from the cloud storage application requesting to obtain file access permissions.

The message sending parameters can be to push notification messages to the communication group or target object bound to the smart robot after receiving information from the sub-application.

Frequency parameters can be the maximum frequency at which the intelligent robot broadcasts messages to various communication groups in the parent application, the maximum frequency at which it sends messages to a single communication group, the maximum number of messages sent by calling the interface per unit time, and the maximum number of concurrent requests when sending messages with the same message body.

In one embodiment, the step of configuring the frequency parameter for the intelligent robot to send messages in S1206 may specifically include: configuring the terminal to ensure that the frequency of the intelligent robot broadcasting messages to each communication group in the parent application does not exceed a first threshold; configuring the intelligent robot to send messages to a single communication group does not exceed a second threshold; configuring the intelligent robot to send messages by calling the interface per unit time does not exceed a third threshold; and configuring the intelligent robot to make concurrent requests when sending messages with the same message body does not exceed a fourth threshold.

In one embodiment, the configuration request operation includes clicking on the robot interface address in the robot details page; when the configuration of the intelligent robot's message receiving parameters, message sending parameters, and frequency parameters is completed, the terminal initiates a data transmission request to the intelligent robot's reverse interface address; wherein, the data transmission request is used to instruct the intelligent robot to push a notification message to the target communication group or group member object in the parent application when it detects that the sub-application has triggered a target event.

In one embodiment, the terminal obtains the response address of the intelligent robot; and uploads updated control text and message card through the response address; wherein, the control text is used to update the control text displayed on the target message card.

For example, after obtaining the response URL, you can actively change the control text of the original message card, or change the message card itself. Furthermore, the response URL can be obtained from two sources: one is by setting a delay when actively sending a message; the response URL will be obtained in the response after successful message sending, and this response URL is valid for 3 months and can be used once. The other source is the callback event triggered when the target object interacts with the target message card, which includes the response URL; this response URL is valid for 24 hours and can be used once.

In the above embodiments, by setting parameters for the intelligent robot, when a related operation occurs in the sub-application, the intelligent robot can be triggered to push a notification message to the parent application, thereby reaching the target object via message. Furthermore, it can receive information generated by the parent application's interactive operations based on the notification message, thus realizing interaction between the parent and sub-applications. Moreover, the frequency of the intelligent robot's message pushes is configured, effectively preventing network impact caused by the intelligent robot pushing a large number of notification messages.

In one embodiment, as shown in Figure 13, a method for processing notification messages is provided. Taking the application of this method to an intelligent robot, specifically the robot virtualized by the robot backend 106 in Figure 1, as an example, the method includes the following steps:

S1302, push the notification message of the child application to the target object in the parent application so that the parent application displays the notification message on the session page in the form of a target message card.

The parent application can be an application that provides the system environment for the child applications, including communication applications, office applications, or payment applications. The communication application can be an enterprise communication application or a personal communication application. The child application can refer to an application that runs in the system environment provided by the parent application, such as cloud storage applications, transportation applications, enterprise to-do list applications, screen mirroring applications, live streaming applications, conferencing applications, and other mobile applications; in addition, the child application can also refer to a public account applied for in the parent application.

The notification message can be: a message requesting the target object to grant file access permissions, a message inviting the target object to join the target task group, a message prompting the target object to complete the pending task, and a message notifying the target object that another object has performed a first operation or a second operation on the target file. The target file can be a document of the target. The first operation can be editing, liking, saving, or commenting on the target file. The second operation can be uploading the target file.

In one embodiment, the intelligent robot receives a notification message containing event content sent by a sub-application when a target event is triggered, or receives event content sent by a sub-application when a target event is triggered, generates a notification message based on the event message, and then pushes the notification message to the target object in the parent application so that the parent application displays the target message card on the session page and displays the notification message on the target message card. The specific form and content of the display can be referred to the relevant embodiment in Figure 2.

The target events include: inviting the target object to join the target task group, requesting the target object to grant file access permissions, prompting the target object to complete the pending task, and other objects performing at least one of the first or second operations on the target file. It should be noted that the target events correspond to notification messages; for example, if the target event is inviting the target object to join the target task group, then the notification message will be the message inviting the target object to join the target task group.

The target task group can be a communication group, task team, or personal or shared space on a cloud drive for handling the target task.

File access permissions are the permission information required to access a target file. Those with the required permissions are allowed to access the target file, while those without the required permissions will not be able to access the target file.

Tasks to be done can be tasks initiated by operators (i.e., initiators) through sub-applications that require approval from the target (such as the person in charge), such as applying for a promotion, requesting leave, and financial insurance.

S1304, Receive an interaction request initiated by the parent application; the interaction request is generated by the parent application when it detects an interaction operation triggered on the target message card.

Different notification messages may correspond to different interaction requests. For example, a notification message requesting file access permissions may request authorization or deny authorization; while a notification message inviting someone to join a target task group may request to join or deny joining.

In one embodiment, after a notification message is displayed as a target message card on the parent application's session page, the target object can perform corresponding interactive operations on the target message card. At this time, the terminal generates an interaction request through the parent application and then sends the interaction request to the intelligent robot. Thus, the intelligent robot receives the interaction request sent by the terminal's parent application.

S1306, forward the interaction request to the application backend of the sub-application so that the application backend can execute the interaction request, obtain the processing result, and provide feedback.

In one embodiment, S1306 may specifically include: the intelligent robot decapsulating the interaction request to obtain an encrypted interaction message; decrypting the encrypted interaction message to obtain a decrypted interaction message; and forwarding the decrypted interaction message to the application backend of the sub-application so that the application backend processes the interaction information to obtain a processing result and provides feedback.

After receiving the encrypted interaction message, the intelligent robot can also verify the identity of the target object (such as verifying whether the target object's identity is legitimate). After the verification is successful, the encrypted interaction message can be decrypted.

In one embodiment, after sending the interaction request to the application backend and before receiving the processing result from the application backend, the intelligent robot can also reply with an empty packet to the target object's communication account to notify the target object that the interaction request has been sent to the application backend, serving as a prompt. The intelligent robot can subsequently proactively send prompt messages to the target object's communication account via the robot interface (webhook) address, or it can directly reply with the processing result when responding to this interaction request.

S1308, when the processing result is received from the application background, the processing result is pushed to the target object so that the parent application updates and displays the processing status of the notification message based on the processing result.

In one embodiment, when the processing result is received from the application's backend, the intelligent robot pushes the processing result to the target object's communication account, so that the target object's terminal updates the processing status of the notification message based on the processing result after receiving the processing result, and then displays the updated notification message in the form of a target message card on the parent application's session page.

For example, as shown in Figure 5, when the target user clicks the "Agree to Authorize" control in Figure 5, the terminal sends an authorization request to the intelligent robot, agreeing to grant permissions to the requester (i.e., the operator requesting file access permissions). At this time, the intelligent robot sends an authorization request to the application's backend. After receiving the authorization request, the application backend grants the requester file access permissions, thus granting the requester file access permissions. Furthermore, the application backend returns the processing result to the target user's communication account through the intelligent robot. The target user's terminal then updates the processing status of the notification message based on this result, displaying the updated notification message as a target message card on the conversation page, as shown in Figure 5. Similarly, when the target user selects the editable or preview-only authorization option in Figure 6, the updated processing status notification message is displayed on the conversation page, indicating whether editable permissions or preview-only permissions have been granted. See Figure 6 for details.

In addition, the intelligent robot sends the processing result to the requester's terminal so that the requester's terminal can update the status of the notification message based on the processing result, and display the updated notification message as a target message card on the session page, as shown in Figure 11.

In one embodiment, the target object is a member object within a communication group; the frequency at which the intelligent robot broadcasts messages to each communication group in the parent application does not exceed a first threshold; the frequency at which the intelligent robot sends messages to a single communication group does not exceed a second threshold; the number of messages sent by the intelligent robot through the interface per unit time does not exceed a third threshold; and the number of concurrent requests made by the intelligent robot when sending messages with the same message body does not exceed a fourth threshold.

The frequency and number of messages sent by the intelligent robot can be configured through the robot configuration page. Specifically, in response to the configuration operation triggered on the robot configuration page, the frequency parameter for the intelligent robot to send messages can be configured. In addition, the message receiving parameters and message sending parameters of the intelligent robot can also be configured.

Among them, the frequency parameter can be the maximum frequency at which the intelligent robot broadcasts messages to each communication group in the parent application (i.e., the first threshold), the maximum frequency at which it sends messages to a single communication group (i.e., the second threshold), the maximum number of messages sent by calling the interface per unit time (i.e., the third threshold), and the maximum number of concurrent requests when sending messages with the same message body (i.e., the fourth threshold).

The message receiving parameter can be a parameter used by the robot to receive messages. For example, after configuring this message receiving parameter, it can receive information sent by the corresponding sub-application, such as receiving information from the cloud storage application requesting access to files.

The message sending parameters can be to push notification messages to the communication group or target object bound to the smart robot after receiving information from the sub-application.

In one embodiment, the step of configuring the frequency parameters for the intelligent robot to send messages may specifically include: configuring the frequency at which the intelligent robot broadcasts messages to each communication group in the parent application to not exceed a first threshold; configuring the frequency at which the intelligent robot sends messages to a single communication group to not exceed a second threshold; configuring the number of messages sent by the intelligent robot by calling the interface per unit time to not exceed a third threshold; and configuring the number of concurrent requests made by the intelligent robot when sending messages with the same message body to not exceed a fourth threshold.

In the above embodiments, a data communication bridge is established between the parent application and the child application. When another object performs an operation in the child application, a notification message can be promptly pushed to the target object in the parent application. The parent application then displays the notification message as a target message card on the conversation page, thus reaching the target object and informing them that another object has performed an operation in the child application. Furthermore, it can also notify the target object to perform a corresponding interaction, preventing missed interactions due to failure to reach the target object. In addition, when the target object triggers an interaction operation on the target message card, it receives an interaction request initiated by the parent application and forwards it to the application's backend. The application backend then processes the interaction request, processes the result, and provides feedback, allowing interaction without switching from the parent application to the child application, improving interaction efficiency. Moreover, pushing the processing result from the application backend to the target object allows the parent application to update and display the processing status of the notification message on the conversation page. After processing is complete, the parent application can notify the target object that the notification message has been processed, ensuring the target object is aware of whether their interaction request has been executed, thus improving user experience.

As an example, let's take a communication application as the parent application for illustration, as follows:

The technical solution of this application is based on various card templates provided by the FunView cross-platform engine, including interactive, graphic, selection, and text notification message cards with various capabilities, so that the intelligent robot can complete the interaction with the target object through callback events and message push. The technical process involved is as follows:

S1. After adding a smart robot to a communication group on the terminal, you can view the robot's unique webhook address on the robot's details page. You can send messages to the target object or communication group by following these steps to initiate an HTTP POST request to the webhook address.

S2: In a group chat session, hovering the mouse over a message card will bring up the robot's profile page. Clicking the webhook address on the robot profile page will redirect you to the robot configuration page. On the robot configuration page, you can set message push parameters and send an HTTP POST request to the webhook URL to send messages to the target object or communication group. Furthermore, you can set the robot's message receiving parameters on the robot profile page to receive and process callback events from the target object and the robot, enabling customized interactive functions.

S3, currently the custom intelligent robot supports sending six message types to communication groups or target objects: text, markdown, image, news, file, and template card.

The restrictions on the frequency of API requests are as follows:

(1) The frequency of intelligent robots sending messages to specific communication groups shall not exceed 20 messages per minute.

(2) The frequency of intelligent robots broadcasting messages to all communication groups shall not exceed 20 messages per minute.

(3) The number of messages sent by the intelligent robot through the interface per minute shall not exceed 10,000 per minute.

(4) Intelligent robots send messages with the same request body, and there are no more than two concurrent requests.

S4. After obtaining the response URL (response_url), you can actively change the button text of the original message card or change some message cards. The response_url can be obtained from two sources: one is by setting a delay when actively sending a message, and the response_url will be obtained in the return after the message is successfully sent. This response_url is valid for 3 months and can be used once; the other is by including the response_url in the callback event triggered when the user interacts with the message card. This response_url is valid for 24 hours and can be used once.

In S5, the URL for receiving messages is set in the robot configuration interface. When a user interacts with the robot, the interaction event will be encrypted and sent back to the robot's message receiving URL. The robot service can receive, decrypt, and process the callback event to achieve richer customization functions.

Currently supported interactive event callbacks:

(1) The target object @ the intelligent robot in the communication group, or sends a text message or a mixed text and image message to the intelligent robot in the one-on-one chat page (i.e. the page where the target object has a conversation with the intelligent robot);

(2) Add a smart robot to a communication group, or remove a smart robot from a communication group;

(3) The target user enters the one-on-one chat page of the intelligent robot;

(4) The target user sends an image message to the intelligent robot in the one-on-one chat page;

(5) The target object clicks the interactive control in the message card.

S6 verifies URL validity, receives and decrypts data, and encrypts and replies. You can directly use the encryption/decryption libraries provided by communication applications (such as enterprise communication applications) for sub-applications. Note that the encryption/decryption library requires a `receiveid` parameter. In the application scenario of a smart robot in a communication group, you can directly pass an empty string when passing the `receiveid` parameter.

S7 requires you to fill in three parameters for the group robot: URL, Token, and EncodingAESKey.

A URL is the access protocol and address used by the intelligent robot in a communication group to receive push interaction requests from communication applications. It supports either HTTP or HTTPS protocols.

Tokens can be used to generate signatures, with a length of 3 to 32 alphanumeric characters.

EncodingAESKey is used for encrypting the message body. It is a Base64 encoded AES key, consisting of 43 characters of alphanumeric characters.

After receiving the request, the robot backend needs to perform the following operations:

(1) Perform URL decoding on the received request.

(2) Verify the request using the parameter msg_signature to confirm the legitimacy of the caller.

(3) Decrypt the echostr parameter to obtain the message content (i.e., the msg field).

(4) Respond to the GET request within 1 second. The response content is the plaintext message content obtained in the previous step. The plaintext message content does not include quotation marks, BOM headers, or newline characters.

In S9, after decrypting the data to obtain the user's message content, the developer can choose to directly reply with an empty packet and then proactively send the message to the group via the webhook address later, or they can directly reply with a message when responding to this request. The reply message needs to first construct an XML data packet according to the plaintext protocol, then encrypt the plaintext message, and finally reply with the final ciphertext XML data packet.

S10: The application backend and the intelligent robot backend can communicate data through the service of responding to callbacks to complete the user's operation or update logic in the session, use the robot's message channel to update the card status on the user side, and at the same time, the application backend updates the data status changes generated after the user's operation.

Next, the technical solution of the FunView cross-platform framework will be described with reference to Figure 14:

FunView is a lightweight UI rendering engine with cross-platform (i.e., across various operating system platforms, including mobile and desktop operating systems) capabilities, enabling dynamic rendering and updating of the user interface (UI). FunView is a low-granularity UI component at the view level, requiring no further adaptation and can be directly used in current business applications. It can also be seamlessly nested with various native Views, dynamically updating online UI styles and even adding new UI views without updating versions, achieving true cross-platform dynamic UI capabilities.

FunView is built on Kotlin-MultiPlatform, unifying the differences across platforms in rendering processes, UI layout, and UI style descriptions to achieve basic cross-platform UI rendering capabilities. Building upon this, it provides a dynamically extensible view description-to-view tree parsing and construction scheme, and supports dynamic modification of UI views via data-driven approaches, achieving complete dynamism from view construction to updates. In FunView's multi-layered architecture, each layer employs a pluggable design. In each stage of FunView—parsing and construction, data-driven processes, layout, measurement, and rendering—customization can be tailored to specific business needs, creating more possibilities and achieving a higher level of dynamism.

By distributing templates, the engine dynamically parses the templates to obtain a view tree. Then, the view tree is measured, laid out, and drawn to complete the entire dynamic rendering process.

FunView employs a layered framework design, divided from bottom to top into: implementation layer, platform layer, parsing layer, business layer, and exception handling system. The platform layer, parsing layer, and business layer are fully cross-platform compliant. Platform-specific features are designed as interfaces in each layer, with these interfaces implemented differently in the implementation layer.

The main functions of each layer are as follows:

Platform Layer: This is the core foundational module of the entire solution, primarily implementing basic view-related functions such as view definition, description, measurement, layout, drawing, event handling, and view state management. In the entire rendering process, the measurement, drawing, and task queue steps may not be fully implemented in the same layer due to differences in platform APIs. Therefore, this part is abstracted as an interface, and the entire rendering process is completed by implementing these interfaces through an implementation layer.

Implementation Layer: Primarily used to smooth out differences between modules that cannot be directly implemented in the cross-platform base module, providing support for the entire solution. It mainly implements differentiated APIs such as text measurement, UI rendering, task queue, logging, file loading, and image loading.

The parsing layer is the dynamic management module in the entire solution. Through template, resource, and style management, it realizes the dynamic parsing and creation process from template to view tree. During the view tree creation process, an expression calculation engine is added, which can make certain properties of the view more dynamic through data-driven methods, dynamically calculating specific values based on data. This transforms the UI template from static to dynamic, improving template reusability and reducing costs.

Business layer: Implements customized logic related to business operations, mainly serving customized needs related to business operations, such as message patterns specific to communication applications (e.g., enterprise communication applications), Markdown parsing, JSON class template parsing, etc.

Exception handling: Code logic may encounter exceptional boundary conditions. If any exception directly causes a crash, it negatively impacts user experience. For example, errors in data or unrecognized expressions during evaluation are considered exceptions. In such cases, default values should be provided instead of immediate crashes. The exception handling system intercepts crashes and determines how to handle them based on the actual runtime situation.

The interface-based design of each logic layer in FunView ensures that any stage other than the main flow can be customized and extended. For example, in the rendering layer, if the existing solution is not optimal, the rendering interface can be reimplemented to allow integration with rendering solutions such as Flutter or Skia. Similarly, when the default layout solution cannot meet the requirements, the layout interface can be customized to extend the layout solution, and so on. This design makes the entire solution more user-friendly and flexible.

The above technical solution can achieve the following beneficial effects:

1) Based on the cross-platform FunView engine, different types of message cards can be developed, which greatly improves the R&D efficiency and the flexibility of iteration updates. In the future, it will support the ability to dynamically adjust the background to meet the customization of different card types without relying on version updates.

2) Intelligent robots have the ability to interact with target objects within communication groups, which allows sub-applications to reach users with more flexible application scenarios. By interacting with target objects within communication groups, they can meet specific functional scenarios.

3) Through the interactive card capabilities and callback update mechanism of the intelligent robot, transactions can be processed within the session without having to return to the corresponding sub-application, avoiding cumbersome switching processes and providing users with a better experience.

It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

Based on the same inventive concept, this application also provides a notification message processing apparatus for implementing the notification message processing method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations of one or more notification message processing apparatus embodiments provided below can be found in the limitations of the notification message processing method described above, and will not be repeated here.

In one embodiment, as shown in FIG15, a notification message processing apparatus is provided, including: a receiving module 1502, a message display module 1504, a sending module 1506, and an update display module 1508, wherein:

The receiving module 1502 is used to receive notification messages from the intelligent robot pushing sub-applications;

The message display module 1504 is used to display notification messages in the form of target message cards in the session page of the parent application;

The sending module 1504 is used to respond to the interactive operation triggered on the target message card and send an interactive request to the application background of the sub-application through the intelligent robot.

The receiving module 1502 is also used to receive the processing results of the interaction request returned by the intelligent robot;

The update display module 1508 is used to update and display the processing status of the notification message based on the processing result.

In one embodiment, the receiving module 1502 is further configured to receive a notification message obtained when the intelligent robot pushes a sub-application that triggers a target event; wherein the target event includes at least one of the following: inviting a target object to join a target task group, requesting the target object to grant file access permissions, prompting the target object to complete a pending task, or other objects performing a first operation or a second operation on the target file.

In one embodiment, the sending module 1504 is further configured to generate a matching interactive message in response to an interactive operation triggered on the target message card; encrypt the interactive message; encapsulate the encrypted interactive message as a message body to obtain an interactive request; and send the interactive request to the application backend of the sub-application through the intelligent robot.

In one embodiment, the notification message is a message requesting the target object to grant file access permissions;

The message display module 1504 is also used to display an consent/authorization control in the target message card;

The sending module 1504 is also used to send an authorization request to the application backend of the sub-application via the intelligent robot in response to the triggering operation of the consent authorization control.

In one embodiment, as shown in FIG16, the device further includes:

The message display module 1504 is also used to display candidate authorization options in the target message card;

Selection module 1510 is used to select a target authorization item in response to a selection operation on candidate authorization options;

The sending module 1504 is also used to generate an authorization request based on the target authorization item in response to the trigger operation of the consent authorization control, and send the authorization request to the application backend of the sub-application through the intelligent robot.

In one embodiment, the message display module 1504 is further configured to display a deny authorization control at a position corresponding to the consent authorization control;

The sending module 1504 is also used to send a denial of authorization request to the application backend of the sub-application via the intelligent robot in response to the triggering operation of the denial of authorization control.

In one embodiment, the notification message is an invitation to the target object to join the target task group; as shown in Figure 16, the device further includes:

The segmentation module 1512 is used to divide the target message card into a first region and a highlighted second region; the notification message is displayed in the first region;

The message display module 1504 is also used to display icons and keywords associated with the target task group in the second area.

In one embodiment, the message display module 1504 is further configured to display a join page or confirmation window in response to an interactive operation triggered on a second area of the target message card;

The sending module 1504 is also used to send a join request to the application backend of the sub-application via the intelligent robot in response to a join operation triggered on the join page or confirmation window; or, in response to a refuse join operation triggered on the join page or confirmation window, send a refuse join request to the application backend of the sub-application via the intelligent robot.

In one embodiment, the notification message is a message prompting the target object to complete the pending task;

The sending module 1504 is also used to respond to the display operation triggered on the target message card and display the pending task on the task processing page of the parent application; when the pending task is completed, it sends a task status change request to the application background of the sub-application through the intelligent robot.

In one embodiment, as shown in FIG16, the device further includes:

Module 1514 is used to determine the service type based on the notification message;

The first acquisition module 1516 is used to acquire a matching target message card based on the business type; wherein, the target message card is a template card of a cross-platform application generated by a cross-platform engine.

In one embodiment, the processing module is configured to generate an interaction event when sending an interaction message to the intelligent robot, adding the intelligent robot's communication account to the communication group of the parent application, removing the intelligent robot's communication account from the communication group, or entering a session page for interacting with the intelligent robot; encrypt the interaction event to obtain an encrypted interaction event; and send the encrypted interaction event back to the intelligent robot so that the intelligent robot can decrypt the encrypted interaction event and process the decrypted interaction event.

In the above embodiments, by receiving notification messages from the intelligent robot pushed to the sub-application, and displaying these notification messages as target message cards, the target object is reached through notification messages. This notifies the target object that another object has performed an operation in the sub-application, and also notifies the target object to perform the corresponding interaction, thus preventing missed interactions due to failure to reach the target object. Furthermore, by performing interaction operations on the target message card, the interaction request is sent to the sub-application's application background via the intelligent robot, eliminating the need to switch from the parent application to the sub-application, improving interaction efficiency. Moreover, upon receiving the processing result of the interaction request from the intelligent robot, the processing status of the notification message is updated and displayed on the conversation page. This notifies the target object that the notification message has been processed, preventing the target object from being unaware that their interaction request has been executed, thus improving user experience. Finally, using the intelligent robot as a communication bridge between the parent and sub-applications effectively ensures data communication between them, allowing operations performed on the sub-application to reach the corresponding target object in a timely and effective manner, enabling the target object to perform timely interaction operations based on the notification messages, further improving interaction efficiency.

In one embodiment, as shown in FIG16, the device further includes:

Page display module 1518 is used to display the robot details page; in response to a configuration request triggered on the robot details page, it displays the robot configuration page;

The configuration module 1520 is used to configure the message receiving parameters and message sending parameters of the intelligent robot, as well as the frequency parameters of the intelligent robot sending messages, in response to the configuration operation triggered on the robot configuration page.

In one embodiment, the configuration module 1520 is further configured to configure the frequency at which the intelligent robot broadcasts messages to each communication group in the parent application not to exceed a first threshold; configure the frequency at which the intelligent robot sends messages to a single communication group not to exceed a second threshold; configure the number of messages sent by the intelligent robot by calling the interface per unit time not to exceed a third threshold; and configure the number of concurrent requests made by the intelligent robot when sending messages with the same message body not to exceed a fourth threshold.

In one embodiment, the configuration request operation includes clicking on the robot interface address in the robot details page;

The sending module 1504 is also used to initiate a data transmission request to the reverse interface address of the intelligent robot when the configuration of the message receiving parameters, message sending parameters and frequency parameters of the intelligent robot is completed; wherein, the data transmission request is used to instruct the intelligent robot to push a notification message to the target communication group or group member object in the parent application when it detects that the sub-application has triggered a target event.

In one embodiment, as shown in FIG16, the device further includes:

The second acquisition module 1522 is used to acquire the response address of the intelligent robot;

The upload module 1524 is used to upload updated control text and message cards via the response address; among them, the control text is used to update the control text displayed on the target message card.

In the above embodiments, by setting parameters for the intelligent robot, when a related operation occurs in the sub-application, the intelligent robot can be triggered to push a notification message to the parent application, thereby reaching the target object via message. Furthermore, it can receive information generated by the parent application's interactive operations based on the notification message, thus realizing interaction between the parent and sub-applications. Moreover, the frequency of the intelligent robot's message pushes is configured, effectively preventing network impact caused by the intelligent robot pushing a large number of notification messages.

In one embodiment, as shown in FIG17, a notification message processing apparatus is provided, including: a push module 1702, a receiving module 1704, and a forwarding module 1706, wherein:

The push module 1702 is used to push notification messages from the child application to the target object in the parent application, so that the parent application can display the notification message in the form of a target message card on the conversation page.

The receiving module 1704 is used to receive interaction requests initiated by the parent application; the interaction request is generated by the parent application when it detects an interaction operation triggered on the target message card;

The forwarding module 1706 is used to forward the interaction request to the application backend of the sub-application, so that the application backend can execute the interaction request, obtain the processing result, and provide feedback.

The push module 1702 is also used to push the processing result to the target object when it receives the processing result from the application background, so that the parent application can update and display the processing status of the notification message based on the processing result.

In one embodiment, the method is applied to an intelligent robot, and the target object is a member object within a communication group; the frequency at which the intelligent robot broadcasts messages to each communication group in the parent application does not exceed a first threshold; the frequency at which the intelligent robot sends messages to a single communication group does not exceed a second threshold; the number of messages sent by the intelligent robot by calling the interface per unit time does not exceed a third threshold; and the number of concurrent requests made by the intelligent robot when sending messages with the same message body does not exceed a fourth threshold.

In one embodiment, the forwarding module 1706 is further configured to decapsulate the interaction request to obtain an encrypted interaction message; decrypt the encrypted interaction message to obtain a decrypted interaction message; and forward the decrypted interaction message to the application backend of the sub-application so that the application backend can process the interaction information to obtain a processing result and provide feedback.

In the above embodiments, a data communication bridge is established between the parent application and the child application. When another object performs an operation in the child application, a notification message can be promptly pushed to the target object in the parent application. The parent application then displays the notification message as a target message card on the conversation page, thus reaching the target object and informing them that another object has performed an operation in the child application. Furthermore, it can also notify the target object to perform a corresponding interaction, preventing missed interactions due to failure to reach the target object. In addition, when the target object triggers an interaction operation on the target message card, it receives an interaction request initiated by the parent application and forwards it to the application's backend. The application backend then processes the interaction request, processes the result, and provides feedback, allowing interaction without switching from the parent application to the child application, improving interaction efficiency. Moreover, pushing the processing result from the application backend to the target object allows the parent application to update and display the processing status of the notification message on the conversation page. After processing is complete, the parent application can notify the target object that the notification message has been processed, ensuring the target object is aware of whether their interaction request has been executed, thus improving user experience.

Each module in the aforementioned notification message processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

In one embodiment, a computer device is provided, which can be a robot backend, and its internal structure diagram is shown in Figure 18. The computer device includes a processor, memory, input/output interfaces (I/O), and a communication interface. The processor, memory, and I/O interfaces are connected via a system bus, and the communication interface is connected to the system bus via the I/O interfaces. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes non-volatile storage media and internal memory. The non-volatile storage media stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device stores notification messages. The I/O interfaces of the computer device are used for exchanging information between the processor and external devices. The communication interface of the computer device is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a notification message processing method.

In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram is shown in Figure 19. The computer device includes a processor, memory, input/output interface, communication interface, display unit, and input device. The processor, memory, and input/output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input/output interface. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input/output interface of the computer device is used for exchanging information between the processor and external devices. The communication interface of the computer device is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a method for processing notification messages. The display unit of the computer device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

Those skilled in the art will understand that the structures shown in Figures 18 and 19 are merely block diagrams of some structures related to the present application and do not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than shown in the figures, or combine certain components, or have different component arrangements.

In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to perform the following steps: receiving a notification message pushed by a smart robot to a sub-application; displaying the notification message as a target message card in a session page of the parent application; in response to an interactive operation triggered on the target message card, sending an interaction request to the application background of the sub-application through the smart robot; receiving a processing result returned by the smart robot for the interaction request; and updating and displaying the processing status of the notification message based on the processing result.

In one embodiment, when the processor executes the computer program, it further implements the following steps: receiving a notification message obtained when the intelligent robot pushes a sub-application that triggers a target event; wherein the target event includes at least one of inviting a target object to join a target task group, requesting the target object to grant file access permissions, prompting the target object to complete a pending task, or other objects performing a first operation or a second operation on the target file.

In one embodiment, when the processor executes the computer program, it further performs the following steps: generating a matching interactive message in response to an interactive operation triggered on the target message card; encrypting the interactive message; encapsulating the encrypted interactive message as a message body to obtain the interactive request; and sending the interactive request to the application backend of the sub-application through the intelligent robot.

In one embodiment, the notification message is a message requesting the target object to grant file access permissions; when the processor executes the computer program, it further implements the following steps: displaying an authorization control in the target message card; in response to the triggering operation of the authorization control, sending an authorization request to the application background of the sub-application through the intelligent robot.

In one embodiment, when the processor executes the computer program, it further performs the following steps: displaying candidate authorization options in the target message card; selecting a target authorization item in response to a selection operation of the candidate authorization options; generating an authorization request based on the target authorization item in response to a trigger operation of the consent authorization control, and sending the authorization request to the application background of the sub-application through the intelligent robot.

In one embodiment, when the processor executes the computer program, it further performs the following steps: displaying a deny authorization control at a location corresponding to the consent authorization control; and sending a deny authorization request to the application background of the sub-application via the intelligent robot in response to a triggering operation of the deny authorization control.

In one embodiment, the notification message is an invitation to the target object to join the target task group; when the processor executes the computer program, it further implements the following steps: dividing the target message card into a first area and a highlighted second area; the notification message is displayed in the first area; and icons and keywords associated with the target task group are displayed in the second area.

In one embodiment, when the processor executes the computer program, it further performs the following steps: in response to an interactive operation triggered on the second area of the target message card, displaying a join page or a confirmation window; in response to a join operation triggered on the join page or the confirmation window, sending a join request to the application backend of the sub-application via the intelligent robot; or, in response to a refuse join operation triggered on the join page or the confirmation window, sending a refuse join request to the application backend of the sub-application via the intelligent robot.

In one embodiment, the notification message is a message prompting the target object to complete a pending task; when the processor executes the computer program, it also implements the following steps: in response to a display operation triggered on the target message card, the pending task is displayed on the task processing page of the parent application; when the pending task is completed, a task status change request is sent to the application background of the sub-application through the intelligent robot.

In one embodiment, when the processor executes the computer program, it further performs the following steps: determining the service type based on the notification message; obtaining a matching target message card based on the service type; wherein the target message card is a template card of a cross-platform application generated by a cross-platform engine.

In one embodiment, when the processor executes the computer program, it further performs the following steps: displaying a robot details page; displaying a robot configuration page in response to a configuration request operation triggered on the robot details page; and configuring message receiving parameters and message sending parameters of the intelligent robot, as well as configuring message sending frequency parameters of the intelligent robot, in response to a configuration operation triggered on the robot configuration page.

In one embodiment, when the processor executes the computer program, it further implements the following steps: configuring the frequency at which the intelligent robot broadcasts messages to each communication group in the parent application not to exceed a first threshold; configuring the frequency at which the intelligent robot sends messages to a single communication group not to exceed a second threshold; configuring the number of messages sent by the intelligent robot by calling the interface per unit time not to exceed a third threshold; and configuring the number of concurrent requests made by the intelligent robot when sending messages with the same message body not to exceed a fourth threshold.

In one embodiment, the configuration request operation includes clicking on the robot interface address in the robot details page; when the processor executes the computer program, it also implements the following steps: when the configuration of the message receiving parameters, the message sending parameters and the frequency parameters of the intelligent robot is completed, a data transmission request is initiated to the reverse interface address of the intelligent robot; wherein, the data transmission request is used to instruct the intelligent robot to push the notification message to the target communication group or group member object in the parent application when it detects that the sub-application has triggered a target event.

In one embodiment, when the processor executes the computer program, it further performs the following steps: obtaining the response address of the intelligent robot; uploading updated control text and message card through the response address; wherein the control text is used to update the control text displayed on the target message card.

In one embodiment, when the processor executes the computer program, it further performs the following steps: when sending an interactive message to the intelligent robot, or adding the intelligent robot's communication account to the communication group of the parent application, or removing the intelligent robot's communication account from the communication group, or entering the session page for interacting with the intelligent robot, an interactive event is generated; the interactive event is encrypted to obtain an encrypted interactive event; the encrypted interactive event is called back to the intelligent robot so that the intelligent robot can decrypt the encrypted interactive event and process the decrypted interactive event.

In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon. When executed by a processor, the computer program performs the following steps: receiving a notification message pushed by a smart robot to a sub-application; displaying the notification message as a target message card in a session page of the parent application; in response to an interactive operation triggered on the target message card, sending an interaction request to the application background of the sub-application via the smart robot; receiving a processing result returned by the smart robot for the interaction request; and updating and displaying the processing status of the notification message based on the processing result.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: receiving a notification message obtained when the intelligent robot pushes a sub-application that triggers a target event; wherein the target event includes at least one of inviting a target object to join a target task group, requesting the target object to grant file access permissions, prompting the target object to complete a pending task, or other objects performing a first operation or a second operation on the target file.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: generating a matching interactive message in response to an interactive operation triggered on the target message card; encrypting the interactive message; encapsulating the encrypted interactive message as a message body to obtain the interactive request; and sending the interactive request to the application backend of the sub-application through the intelligent robot.

In one embodiment, the notification message is a message requesting the target object to grant file access permissions; when the computer program is executed by the processor, it further implements the following steps: displaying an authorization control in the target message card; and in response to a triggering operation of the authorization control, sending an authorization request to the application background of the sub-application through the intelligent robot.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: displaying candidate authorization options in the target message card; selecting a target authorization item in response to a selection operation of the candidate authorization options; generating an authorization request based on the target authorization item in response to a trigger operation of the consent authorization control, and sending the authorization request to the application background of the sub-application through the intelligent robot.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: displaying a deny authorization control at a location corresponding to the consent authorization control; and sending a deny authorization request to the application backend of the sub-application via the intelligent robot in response to a triggering operation of the deny authorization control.

In one embodiment, the notification message is an invitation to the target object to join a target task group; when the computer program is executed by the processor, it further implements the following steps: dividing the target message card into a first area and a highlighted second area; displaying the notification message in the first area; and displaying an icon and keywords associated with the target task group in the second area.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: in response to an interactive operation triggered on the second area of the target message card, displaying a join page or a confirmation window; in response to a join operation triggered on the join page or the confirmation window, sending a join request to the application backend of the sub-application via the intelligent robot; or, in response to a refuse join operation triggered on the join page or the confirmation window, sending a refuse join request to the application backend of the sub-application via the intelligent robot.

In one embodiment, the notification message is a message prompting the target object to complete a pending task; when the computer program is executed by the processor, it further implements the following steps: in response to a display operation triggered on the target message card, the pending task is displayed on the task processing page of the parent application; when the pending task is completed, a task status change request is sent to the application background of the sub-application through the intelligent robot.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: determining the service type based on the notification message; obtaining a matching target message card based on the service type; wherein the target message card is a template card of a cross-platform application generated based on a cross-platform engine.

In one embodiment, when the computer program is executed by a processor, it further performs the following steps: displaying a robot details page; displaying a robot configuration page in response to a configuration request operation triggered on the robot details page; and configuring message receiving parameters and message sending parameters of the intelligent robot, as well as configuring message sending frequency parameters of the intelligent robot, in response to a configuration operation triggered on the robot configuration page.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: configuring the frequency at which the intelligent robot broadcasts messages to each communication group in the parent application not to exceed a first threshold; configuring the frequency at which the intelligent robot sends messages to a single communication group not to exceed a second threshold; configuring the number of messages sent by the intelligent robot by calling the interface per unit time not to exceed a third threshold; and configuring the number of concurrent requests made by the intelligent robot when sending messages with the same message body not to exceed a fourth threshold.

In one embodiment, the configuration request operation includes clicking on the robot interface address in the robot details page; when the computer program is executed by the processor, it further implements the following steps: when the configuration of the message receiving parameters, the message sending parameters and the frequency parameters of the intelligent robot is completed, a data transmission request is initiated to the reverse interface address of the intelligent robot; wherein, the data transmission request is used to instruct the intelligent robot to push the notification message to the target communication group or group member object in the parent application when it detects that the sub-application has triggered a target event.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining the response address of the intelligent robot; uploading updated control text and message card through the response address; wherein the control text is used to update the control text displayed on the target message card.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: when sending an interactive message to the intelligent robot, or adding the intelligent robot's communication account to the communication group of the parent application, or removing the intelligent robot's communication account from the communication group, or entering the session page for interacting with the intelligent robot, an interactive event is generated; the interactive event is encrypted to obtain an encrypted interactive event; the encrypted interactive event is called back to the intelligent robot so that the intelligent robot can decrypt the encrypted interactive event and process the decrypted interactive event.

In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

Receive a notification message from a sub-application pushed by a smart robot; display the notification message as a target message card in the parent application's session page; respond to an interactive operation triggered on the target message card, send an interaction request to the sub-application's application backend via the smart robot; receive the processing result of the interaction request returned by the smart robot; update and display the processing status of the notification message based on the processing result.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: receiving a notification message obtained when the intelligent robot pushes a sub-application that triggers a target event; wherein the target event includes at least one of inviting a target object to join a target task group, requesting the target object to grant file access permissions, prompting the target object to complete a pending task, or other objects performing a first operation or a second operation on the target file.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: generating a matching interactive message in response to an interactive operation triggered on the target message card; encrypting the interactive message; encapsulating the encrypted interactive message as a message body to obtain the interactive request; and sending the interactive request to the application backend of the sub-application through the intelligent robot.

In one embodiment, the notification message is a message requesting the target object to grant file access permissions; when the computer program is executed by the processor, it further implements the following steps: displaying an authorization control in the target message card; and in response to a triggering operation of the authorization control, sending an authorization request to the application background of the sub-application through the intelligent robot.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: displaying candidate authorization options in the target message card; selecting a target authorization item in response to a selection operation of the candidate authorization options; generating an authorization request based on the target authorization item in response to a trigger operation of the consent authorization control, and sending the authorization request to the application background of the sub-application through the intelligent robot.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: displaying a deny authorization control at a location corresponding to the consent authorization control; and sending a deny authorization request to the application backend of the sub-application via the intelligent robot in response to a triggering operation of the deny authorization control.

In one embodiment, the notification message is an invitation to the target object to join a target task group; when the computer program is executed by the processor, it further implements the following steps: dividing the target message card into a first area and a highlighted second area; displaying the notification message in the first area; and displaying an icon and keywords associated with the target task group in the second area.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: in response to an interactive operation triggered on the second area of the target message card, displaying a join page or a confirmation window; in response to a join operation triggered on the join page or the confirmation window, sending a join request to the application backend of the sub-application via the intelligent robot; or, in response to a refuse join operation triggered on the join page or the confirmation window, sending a refuse join request to the application backend of the sub-application via the intelligent robot.

In one embodiment, the notification message is a message prompting the target object to complete a pending task; when the computer program is executed by the processor, it further implements the following steps: in response to a display operation triggered on the target message card, the pending task is displayed on the task processing page of the parent application; when the pending task is completed, a task status change request is sent to the application background of the sub-application through the intelligent robot.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: determining the service type based on the notification message; obtaining a matching target message card based on the service type; wherein the target message card is a template card of a cross-platform application generated based on a cross-platform engine.

In one embodiment, when the computer program is executed by a processor, it further performs the following steps: displaying a robot details page; displaying a robot configuration page in response to a configuration request operation triggered on the robot details page; and configuring message receiving parameters and message sending parameters of the intelligent robot, as well as configuring message sending frequency parameters of the intelligent robot, in response to a configuration operation triggered on the robot configuration page.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: configuring the frequency at which the intelligent robot broadcasts messages to each communication group in the parent application not to exceed a first threshold; configuring the frequency at which the intelligent robot sends messages to a single communication group not to exceed a second threshold; configuring the number of messages sent by the intelligent robot by calling the interface per unit time not to exceed a third threshold; and configuring the number of concurrent requests made by the intelligent robot when sending messages with the same message body not to exceed a fourth threshold.

In one embodiment, the configuration request operation includes clicking on the robot interface address in the robot details page; when the computer program is executed by the processor, it further implements the following steps: when the configuration of the message receiving parameters, the message sending parameters and the frequency parameters of the intelligent robot is completed, a data transmission request is initiated to the reverse interface address of the intelligent robot; wherein, the data transmission request is used to instruct the intelligent robot to push the notification message to the target communication group or group member object in the parent application when it detects that the sub-application has triggered a target event.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining the response address of the intelligent robot; uploading updated control text and message card through the response address; wherein the control text is used to update the control text displayed on the target message card.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: when sending an interactive message to the intelligent robot, or adding the intelligent robot's communication account to the communication group of the parent application, or removing the intelligent robot's communication account from the communication group, or entering the session page for interacting with the intelligent robot, an interactive event is generated; the interactive event is encrypted to obtain an encrypted interactive event; the encrypted interactive event is called back to the intelligent robot so that the intelligent robot can decrypt the encrypted interactive event and process the decrypted interactive event.

It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims (23)

1. A method for processing notification messages, characterized in that the method includes: Receive notification messages from sub-applications pushed by the intelligent robot; The notification message is displayed as a target message card in the parent application's session page; In response to an interactive operation triggered on the target message card, the intelligent robot sends an interactive request to the application backend of the sub-application. Receive the processing result of the interaction request returned by the intelligent robot; The processing status of the notification message is updated and displayed based on the processing result. 2. The method according to claim 1, wherein receiving the notification message from the intelligent robot pushing the sub-application includes: Receive notification messages obtained when a target event is triggered by a push notification from a sub-application pushed by an intelligent robot; The target events include at least one of the following: inviting the target object to join the target task group, requesting the target object to grant file access permissions, prompting the target object to complete the pending task, or other objects performing a first operation or a second operation on the target file. 3. The method according to claim 1, wherein sending an interaction request to the application backend of the sub-application via the intelligent robot in response to an interactive operation triggered on the target message card includes: In response to an interactive operation triggered on the target message card, a matching interactive message is generated; The interactive messages are encrypted; The encrypted interaction message is encapsulated as a message body to obtain the interaction request; The intelligent robot sends the interaction request to the application backend of the sub-application. 4. The method according to claim 1, wherein the notification message is a message requesting the target object to grant file access permissions; After displaying the notification message in the form of a target message card, the method further includes: A consent/authorization control is displayed in the target message card; The step of sending an interaction request to the application backend of the sub-application via the intelligent robot in response to an interactive operation triggered on the target message card includes: In response to the triggering of the consent/authorization control, the intelligent robot sends an authorization request to the application backend of the sub-application. 5. The method according to claim 4, characterized in that, after displaying the notification message in the form of a target message card, the method further includes: Candidate authorization options are displayed in the target message card; In response to the selection operation of the candidate authorization options, the target authorization item is selected; The step of sending an authorization request to the application backend of the sub-application via the intelligent robot in response to the triggering operation of the authorization control includes: In response to the triggering operation of the consent authorization control, an authorization request is generated based on the target authorization item, and the authorization request is sent to the application backend of the sub-application through the intelligent robot. 6. The method according to claim 4, characterized in that the method further comprises: Display a deny authorization control in the location corresponding to the consent authorization control; In response to the triggering operation of the denied authorization control, the intelligent robot sends a denied authorization request to the application backend of the sub-application. 7. The method according to claim 1, wherein the notification message is a message inviting the target object to join the target task group; After displaying the notification message in the form of a target message card, the method further includes: The target message card is divided into a first area and a highlighted second area; the notification message is displayed in the first area. The second area displays icons and keywords associated with the target task group. 8. The method according to claim 7, wherein sending an interaction request to the application backend of the sub-application via the intelligent robot in response to an interactive operation triggered on the target message card comprises: In response to an interactive operation triggered on the second area of the target message card, a join page or confirmation window is displayed; In response to a join operation triggered on the join page or the confirmation window, the intelligent robot sends a join request to the application backend of the sub-application; or, in response to a refuse join operation triggered on the join page or the confirmation window, the intelligent robot sends a refuse join request to the application backend of the sub-application. 9. The method according to claim 1, wherein the notification message is a message prompting the target object to complete the pending task; The step of sending an interaction request to the application backend of the sub-application via the intelligent robot in response to an interactive operation triggered on the target message card includes: In response to a display operation triggered on the target message card, the to-do task is displayed on the task processing page of the parent application; When the task is completed, the intelligent robot sends a task status change request to the application backend of the sub-application. 10. The method according to any one of claims 1 to 9, characterized in that the method further comprises: The service type is determined based on the notification message; Obtain the matching target message card based on the business type; The target message card is a template card for a cross-platform application generated based on a cross-platform engine. 11. The method according to any one of claims 1 to 9, characterized in that, before receiving the notification message from the intelligent robot pushing the sub-application, the method further comprises: Display the robot details page; In response to a configuration request triggered on the robot details page, the robot configuration page is displayed; In response to a configuration operation triggered on the robot configuration page, the message receiving parameters and message sending parameters of the intelligent robot are configured, as well as the frequency parameters for the intelligent robot to send messages are configured. 12. The method according to claim 11, wherein configuring the frequency parameters for sending messages by the intelligent robot includes: The frequency at which the intelligent robot broadcasts messages to each communication group in the parent application does not exceed a first threshold. The frequency at which the intelligent robot sends messages to a single communication group shall not exceed a second threshold. The intelligent robot is configured to send no more than a third threshold number of messages per unit time via the interface; The configuration ensures that the number of concurrent requests made by the intelligent robot when sending messages with the same message body does not exceed a fourth threshold. 13. The method according to claim 11, wherein the configuration request operation includes a click operation on the robot interface address in the robot details page; When the configuration of the message receiving parameters, message sending parameters and frequency parameters of the intelligent robot is completed, a data transmission request is initiated to the reverse interface address of the intelligent robot; The data transmission request is used to instruct the intelligent robot to push the notification message to the target communication group or group member object in the parent application when it detects that the sub-application has triggered a target event. 14. The method according to any one of claims 1 to 9, characterized in that the method further comprises: Obtain the response address of the intelligent robot; Upload updated control text and message cards via the response address; The control text is used to update the control text displayed on the target message card. 15. The method according to any one of claims 1 to 9, characterized in that the method further comprises: An interactive event is generated when an interactive message is sent to the intelligent robot, or when the intelligent robot's communication account is added to the communication group of the parent application, or when the intelligent robot's communication account is removed from the communication group, or when a session page for interacting with the intelligent robot is entered. The interaction event is encrypted to obtain an encrypted interaction event; The encrypted interaction event is then sent back to the intelligent robot, so that the intelligent robot can decrypt the encrypted interaction event and process the decrypted interaction event. 16. A method for processing notification messages, characterized in that the method includes: Push notification messages from child applications to target objects in the parent application, so that the parent application displays the notification messages in the form of target message cards on the session page; Receive an interaction request initiated by the parent application; the interaction request is generated by the parent application upon detecting an interaction operation triggered on the target message card; The interaction request is forwarded to the application backend of the sub-application, so that the application backend executes the interaction request, obtains the processing result, and provides feedback. When the processing result is received from the application's backend, the processing result is pushed to the target object so that the parent application updates and displays the processing status of the notification message based on the processing result. 17. The method according to claim 16, wherein the method is applied to an intelligent robot, and the target object is a member object within a communication group; the method further comprises: The frequency at which the intelligent robot broadcasts messages to each of the communication groups in the parent application does not exceed a first threshold. The frequency with which the intelligent robot sends messages to a single communication group does not exceed a second threshold. The number of messages sent by the intelligent robot through the interface per unit time does not exceed the third threshold. The number of concurrent requests made by the intelligent robot when sending messages with the same message body does not exceed the fourth threshold. 18. The method according to claim 16, wherein forwarding the interaction request to the application backend of the sub-application, so that the application backend executes the interaction request, obtains a processing result, and provides feedback, comprises: The interaction request is decapsulated to obtain an encrypted interaction message; The encrypted interaction message is decrypted to obtain the decrypted interaction message; The decrypted interaction message is forwarded to the application backend of the sub-application, so that the application backend processes the interaction information, obtains the processing result, and provides feedback. 19. A notification message processing apparatus, characterized in that the apparatus comprises: The receiving module is used to receive notification messages pushed by the intelligent robot to the sub-application; The message display module is used to display the notification message in the form of a target message card in the session page of the parent application; The sending module is used to respond to the interactive operation triggered on the target message card and send an interactive request to the application background of the sub-application through the intelligent robot; The receiving module is also configured to receive the processing result of the interaction request returned by the intelligent robot; The update display module is used to update and display the processing status of the notification message based on the processing result. 20. A notification message processing apparatus, characterized in that the apparatus comprises: The push module is used to push notification messages from the child application to target objects in the parent application, so that the parent application displays the notification messages in the form of target message cards on the conversation page; A receiving module is used to receive an interaction request initiated by the parent application; the interaction request is generated by the parent application when it detects an interaction operation triggered on the target message card; The forwarding module is used to forward the interaction request to the application backend of the sub-application, so that the application backend can execute the interaction request, obtain the processing result, and provide feedback. The push module is further configured to push the processing result to the target object when it receives the processing result from the application's backend, so that the parent application updates and displays the processing status of the notification message based on the processing result. 21. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 18. 22. A computer-readable storage medium having a computer program stored thereon, characterized in that, when the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 18. 23. A computer program product comprising a computer program, characterized in that, when executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 18.